Related
Hey everyone! I have a question that I couldn't find the answer to in the General or Dev forums.
My brother asked me if I could root his phone. I have experience with rooting, CWM, etc on my phone (Atrix), so I told him that I could, but I'd have to do some research first.
He did install the 2.3.3 update, so I understand permanent root is not possible yet. So here's my question-
Is there anything that would stop me from executing the following sequence and successfully getting CM7 onto the phone?
Gain Temp root
Rename install_recovery.sh to something else
Install ROM manager
Install CWM Recovery
Have ROM manager download CM7
Flash CM7
Done
Thank you in advance!
DK
Will not work, the bootloader is locked so flashing roms isn't gonna happen.
I dont think that would work... The shift is as locked down as the atrix was. I am pretty sure the partitions would still be write protected with only temp root...
Sent from my PG06100 using Tapatalk
I didn't even think about the bootloader possibly being locked. I always thought HTC had unlocked bootloaders until very recently (Evo 3D) when they released locked bootloaders, then announced that they would allow you to unlock them.
According to this page:
http://wiki.cyanogenmod.com/wiki/HTC_Evo_Shift_4G:_Full_Update_Guide#Flashing_the_Engineering_HBoot
Flashing that will unlock the boot loader. So I should be able to change my steps to:
[Edit: That site is basically instructions on how to install CM7 onto the Shift, and those steps only require temporary root to execute.]
Gain Temp root
Flash HBoot
Rename install_recovery.sh to something else
Install ROM manager
Install CWM Recovery
Have ROM manager download CM7
Flash CM7
Done
Is there anything else that would stop my process above from working?
EDIT - MY Atrix had a new bootloader installed when I did the OTA to Gingerbread several months ago. If the Evo Shift also got a new bootloader with their GB update, three is a chance that flashing HBoot could brick the phone. I'm going to start looking into this now, however if someone knows the answer to this I'd appreciate an answer
Wont work... We have an emmc partitioned phone just like the evo 3d. The o.t.a. to 2.3.3 included a new locked/encrypted bootloader. The partitions are write protected and encrypted. Flashing the eng hboot with a locked/encrypted recovery partition could equal brick...
Sent from my PG06100 using Tapatalk
Thanks for that info, I couldn't find confirmation either way on the bootloader. I was going to check check MD5Sums before flashing the HBoot just in case.
So can I restore back to Froyo and the old bootloader? On the Atrix you could do this (as long as you didn't unlock your bootloader) by using RSD Lite and flashing the stock SBF file. A quick search on the Evo Shift implies that I can do something similar with the Evo Shift - RUU back to stock Froyo? I admit I know nothing about how that works, I'll start searching now, and any additional info would be great!
Edit: Looks like there is no way to do that either, there doesn't seem to be a way to go back. Interesting that the phone got a new bootloader with the OTA update. My Atrix got a new bootloader with its 2.3 update too, but that was because the new bootloader allowed the users to unlock it. I also see that HTC's online unlocker doesn't list the Evo Shift. So it looks like my brother installing the OTA screwed himself out of getting to run any custom ROMs.
DK
You got it man... Sorry to be the bearer of bad news... Htc went all moto on us... They even used the same style of 256 bit encryption... Effing ****ty!
Sent from my PG06100 using Tapatalk
I've searched (both xda and external sites) and I've read through many threads but I still don't have clear answers to these questions so I'd appreciate any help anyone can provide. I'm an Atrix user so I'm assuming a worst-case scenario mindset in order to properly weigh my options before upgrading.
1. What issues would HOX users face if the devs are never able to achieve S-OFF?
I think the normal behavior for S-ON is that you are not able flash kernels or radios. However, the devs have currently figured out a way to flash kernels on the HOX despite the lack of S-OFF. Similarly, there may also be a way to flash radios despite the lack of S-OFF too but this has not yet been achieved. I think S-OFF also lets a user resize partitions but I'm not sure why this would be a huge issue. Is this all more or less correct?
2. 1.85 devices can have their bootloaders unlocked once a new root exploit is found for that firmware, right?
My concern is that I'll get a 1.85 and be permanently stuck with an AT&T/HTC ROM.
This all comes down to the HOX vs. SGS3 for me. I really prefer the HOX but I'm not willing to risk being stuck with the AT&T ROM. Of course, this could be moot because we don't yet know whether or not AT&T will be able to convince Samsung to make an exception to their bootloader policy like they were able to do with HTC.
Thanks again for your help.
I think AT&T phones are being shipped with 1.73 right now which is capable of being rooted. Someone correct me if I'm wrong.
Yes if the htc has 1.73 it can be rooted. Then the cid can be changed to unlock the bootloader through htc dev. After that you lock the bootloader back and upgrade to 1.85. Then you re unlock the bootloader and install cwm and after installing cwm flash SU for root on 1.85. As for Samsung EHH..
1. As far as I know all you've stated is correct, if a dev wants to pop in to correct me by all means you can. There are some kernels that are "flashable" not neccessarily stable though just because of the lack of a source code. And the DCM by viperboy is pretty awesome.
2. Yes they will be able to. Most people are stuck on 1.85 because they were too eager and updated before any development. They're not really all to blame it's just human nature. But as far as I know there is no current development for root because the method from 1.73> to root> to CWM is getting the primary focus. Phones as of right now are being shipped with 1.73 IF you can even get your hands on one. It's hard because of all the customs issues.
Both phones will be excellent and both will get great development. I've just been an HTC guy so I like the HOX. However if you want "right now development" the GS3 might be a better choice in all honesty depending on what AT&T decides on the BL. But HOX development is moving along quite nicely. My phone kicks ass!
Thanks, everyone.
@Shaddy-Z
So in your opinion the lack of progress in obtaining root for 1.85 is mainly due to a smaller current need and not because of some new or challenging hurdle? Would you expect a new method to pop up once a majority of phones begin shipping with 1.85? What would you put the odds at? I know this is not apples to apples but I have residual skepticism carried over from the Atrix bootloader affair. The devs were basically thwarted/defeated and the unlock was only achieved as a result of an anonymous/unsanctioned leak.
Just saw this post: http://forum.xda-developers.com/showthread.php?t=1693624 It appears they are shipping now with 1.85...
You do not need s-off to flash kernels. You can flash them through fastboot just fine, as long as you have an unlocked bootloader. You just can't flash them through recovery until we have s-off. I really don't think s-off is even needed. It would be nice to have but it doesn't stop you from doing anything except flashing radios. I was in the same situation when I was using the Vivid. I didn't even s-off my Vivid when the tool was released because I didn't need it.
pside15 said:
You do not need s-off to flash kernels. You can flash them through fastboot just fine, as long as you have an unlocked bootloader. You just can't flash them through recovery until we have s-off. I really don't think s-off is even needed. It would be nice to have but it doesn't stop you from doing anything except flashing radios. I was in the same situation when I was using the Vivid. I didn't even s-off my Vivid when the tool was released because I didn't need it.
Click to expand...
Click to collapse
Actually they have found a way to.flash kernels and radios in recovery.
Sent from my HTC One X using xda premium
In this thread it is mentioned that everything can be flashed though custom recovery now http://forum.xda-developers.com/showthread.php?t=1639972&page=99
so s-off is not limiting us anymore
So... No need for s-off now then? :thumbup:
Sent from my HTC One X using xda premium
So Guys black friday is around the corner and I plan to upgrade from my dated HTC Aria. I'm obviously looking at the HOX and the S3 and just by personal preference am leaning towards the HOX (ATT version). However what is really worrying me is that the HOX seems to be locked down quite a bit. I'm not a dev or anything I just want to be able to flash custom rom and experience senseless android in jellybean. So I have some questions...
1) If I buy a HOX with the 2.02 version what are my options rooting wise or am I just screwed?
2) I'm coming from a rooted Aria where rom flashing was easy with clockworkmod recovery. I been lurking this forum and it seems like a painful process now and what is this boot.img thing.
3) Also if anyone isn't to annoyed by my lack of knowledge could you explain what the "S-ON/S-OFF" is as well as the limitation with the fact that HTC locked the boot loader?
I like the HOX but am getting scared away by the fact that this phone is so locked up.
sunny342 said:
So Guys black friday is around the corner and I plan to upgrade from my dated HTC Aria. I'm obviously looking at the HOX and the S3 and just by personal preference am leaning towards the HOX (ATT version). However what is really worrying me is that the HOX seems to be locked down quite a bit. I'm not a dev or anything I just want to be able to flash custom rom and experience senseless android in jellybean. So I have some questions...
1) If I buy a HOX with the 2.02 version what are my options rooting wise or am I just screwed?
2) I'm coming from a rooted Aria where rom flashing was easy with clockworkmod recovery. I been lurking this forum and it seems like a painful process now and what is this boot.img thing.
3) Also if anyone isn't to annoyed by my lack of knowledge could you explain what the "S-ON/S-OFF" is as well as the limitation with the fact that HTC locked the boot loader?
I like the HOX but am getting scared away by the fact that this phone is so locked up.
Click to expand...
Click to collapse
First off, when you get it rooted... DONT FLASH ICJ.
Second, when you get it downgrade you hboot via the JET tool or manually through the WIP Unbrick evita thread by Absolutelygrim. Then in the JET tool thread, you'll find a way to RUU down grade. Choose 1.85 Then you won't have to worry about flashing the boot.img in fastboot. All that is, is a way to bypass AT&T's safe gaurd programming. They tried to make it so the boot.img couldn't be formed in recovery. That's only with the 2.20 firmware though.
Third, IDK. I'm still learning why S-OFF is like gold. Someone else might be able to answer that one but, not me.
1) 2.20 firmware is fully rootable, and has been for a few weeks now. Worries about there not being a root method for 2.20 are outdated, and no longer apply.
2) First off, CWM is not recommended for this device. It never officially supported the Snapdragon S4 variant, and was just a port, with serious known issues. A different custom recovery, TWRP is recommended, and works great.
With the 1.14 hboot that comes with the 2.20 firmware, the hole by which boot.img was flashed via recovery was plugged. So whenever you flash a new ROM, you need to extract boot.img from the ROM zip, and flash it separately via fastboot (phone connected to your PC). Or as previously mentioned, you can downgrade the hboot to eliminate this step.
Aside from that, flashing ROMs on TWRP is just as easy as CWM on your Aria (once you have bootloader unlocked and TWRP installed).
3) S-Off means all security off. It hasn't yet been achieved yet on this device. But with an unlocked bootloader, you can flash ROMs and other mods. With a downgraded hboot, you can flash radios. So there isn't much that S-Off would give you, that isn't already possible. Being able to get SIM unlock for free might be possible with S-Off, as well as turning off the warning flag that the bootloader was unlocked. But for the most part, that is really it. For most uses, S-Off simply is not needed. S-On and bootloader unlock fulfills most needs.
All that said, are you aware the One X+ is being released by AT&T tomorrow? It features a slightly faster CPU/GPU and much more internal storage. Unless you are on a budget, that is probably the phone I would go for at this point. But I think it also remains to be seen about root and bootloader unlock for the One X+.
Another aria convert, yay. As stated above, you shouldn't have any concerns about this device. TWRP is actually much easier to use than CWM. The flashing boot.IMG separately is something you won't need to do once you downgrade the firmware.
And as said above, I'd just get a one x+ if I had the money. We only get 9.93GB of SD storage space on this phone.
Sent from my HTC One XL
Hello guys, i am also thinking about getting this phone, but i've been searching this forum and it seems that flashing ROMs is a bit complicated, and i'm not sure..
What are the pros and cons of unlocking the bootloader? could i brick the phone by doing that?
Is there a guide for noobies like me, a tutorial or something? sorry.. i'm new to this.. :fingers-crossed:
p3terr said:
Hello guys, i am also thinking about getting this phone, but i've been searching this forum and it seems that flashing ROMs is a bit complicated, and i'm not sure..
What are the pros and cons of unlocking the bootloader? could i brick the phone by doing that?
Is there a guide for noobies like me, a tutorial or something? sorry.. i'm new to this.. :fingers-crossed:
Click to expand...
Click to collapse
Would you be getting the AT&T version, or another variant?
Setting the phone up for flashing ROMs is a bit more complicated than some other manufacturers. But this is just how it is for HTC, they have an increasing degree of security on their phones.
You have to unlock the bootloader, which really isn't all that hard. Then install custom recovery and you can flash ROMs. The AT&T version has the extra steps of temp root, SuperCID before you can unlock the bootloader.
Once the phone is setup, flashing ROMs is just like any other phone. With the exception of having to extract boot.img from the ROM zip and flashing via fastboot. But I believe this only applies to the AT&T version with the 1.14 hboot. Even so, you can downgrade the hboot, so you don't have to do the extra step of manually flashing boot.img.
Bricking the phone while unlocking the bootloader is unlikely. But its always a possibility with any mods. Unlocking the bootloader wipes the phone (not really an issue if you are doing it right away after buying) and you also have to confirm that you understand that unlocking the bootloader may void your warranty. Other than that, there is no real "con" to it.
I just finished unlocking bootloader, rooting, installing venom Rom and putting beastmode custom kernel on my [email protected] hox. It's easy now even with 2.2. Just download the all in one tool kit found in the stickied thread for the hox. Does almost all work for you.
Flashing Rom there after word was very similar to cwm was. Loaded it on my internal storage and flashed via recovery
Sent from my HTC One XL using xda app-developers app
redpoint73 said:
1) 2.20 firmware is fully rootable, and has been for a few weeks now. Worries about there not being a root method for 2.20 are outdated, and no longer apply.
2) First off, CWM is not recommended for this device. It never officially supported the Snapdragon S4 variant, and was just a port, with serious known issues. A different custom recovery, TWRP is recommended, and works great.
With the 1.14 hboot that comes with the 2.20 firmware, the hole by which boot.img was flashed via recovery was plugged. So whenever you flash a new ROM, you need to extract boot.img from the ROM zip, and flash it separately via fastboot (phone connected to your PC). Or as previously mentioned, you can downgrade the hboot to eliminate this step.
Aside from that, flashing ROMs on TWRP is just as easy as CWM on your Aria (once you have bootloader unlocked and TWRP installed).
3) S-Off means all security off. It hasn't yet been achieved yet on this device. But with an unlocked bootloader, you can flash ROMs and other mods. With a downgraded hboot, you can flash radios. So there isn't much that S-Off would give you, that isn't already possible. Being able to get SIM unlock for free might be possible with S-Off, as well as turning off the warning flag that the bootloader was unlocked. But for the most part, that is really it. For most uses, S-Off simply is not needed. S-On and bootloader unlock fulfills most needs.
All that said, are you aware the One X+ is being released by AT&T tomorrow? It features a slightly faster CPU/GPU and much more internal storage. Unless you are on a budget, that is probably the phone I would go for at this point. But I think it also remains to be seen about root and bootloader unlock for the One X+.
Click to expand...
Click to collapse
I am aware of the One X+ but I am on a budget and the slight performance boost to me doesn't justify the price. Radio shack will have the HOX for free on blackfriday. Also thanks for the answers to the questions your comment cleared up alot for me.
ECEXCURSION said:
Another aria convert, yay. As stated above, you shouldn't have any concerns about this device. TWRP is actually much easier to use than CWM. The flashing boot.IMG separately is something you won't need to do once you downgrade the firmware.
And as said above, I'd just get a one x+ if I had the money. We only get 9.93GB of SD storage space on this phone.
Sent from my HTC One XL
Click to expand...
Click to collapse
ARIA FTW lol. I need the upgrade to the HOX. Only 9.9GB sucks pretty bad but I can make it work. If only I too had the money for the one X+
You don't need to wait for black friday to get the HOX for free. It's currently free on ATT on Amazon Wireless, and has been for a couple weeks.
If you follow instructions properly and read up on everything necessary, unlocking, rooting, and flashing the HOX is a breeze; 2.20 only introduces one additional, straightforward step.
exygenysys said:
You don't need to wait for black friday to get the HOX for free. It's currently free on ATT on Amazon Wireless, and has been for a couple weeks.
Click to expand...
Click to collapse
Im eligible for a qualified upgrade on my family plan so I can't take advantage of the new contract deal.
Hello Guys.... M really new to XDA as well as HTC devices.... had a Sony and a Samsung before... Seems HTC is entirely different!
i just needed some expertise on following questions i had in my mind:
1) i have bought an HTC one xl (snapdragon version) that is unlocked.. will a "FACTORY DATA RESET" or flashing of a custom rom lock it again??
(does this phone need to have an unlocked bootloader)
2) what is the best and most secure way to root it? (link to any guides will be much appreciated)
3) things that can possibly brick the phone and i should AVOID?
4) the best custom rom in terms of speed?
5) any necessary mods for stock rom?
PLEASE i neeed some help!
You need to find the correct root method for your current hboot. If your phone is the at&t model, click the link in my signature, then find the right root method for you. If it's not, just go to htcdev.com and unlock your bootloader, then you can flash TWRP recovery, and flash a custom ROM.
Sent from my Evita
1)Factory data reset in bootloader just clears the /data partition but does not function correctly at all if you unlock the bootloader for this device.
The only way to relock the bootloader is to do fastboot oem lock
2)As timmaaa said, follow the index. You want to unlock bootloader, flash ROM with root, get supercid, s-off.
The catches are:
AT&T devices need to gain temp root to get supercid before they can unlock bootloader.
Newer HTC updates eg new 3.17 and 5.xx updates may prevent you from getting supercid even with root, you may need to investigate downgrading things to get supercid.
With an unlocked bootloader, you are well on your way. You should check if you have supercid and if you are s-off.
3)Do not attempt to install HTC updates after you modify the phone. OTA is particular can be dangerous but even RUU's can be dangerous under some circumstances. OTA have many rules which are easy to follow once you have an idea of what they do, best bet is to just ignore them, RUU is fine if you have both s-off and supercid.
4)You can not ask that question and we can not answer it. It is unfair for someone to rate ROM's over other ROMs as the devs put a lot of effort in to these things. Each ROM is special in its own way, you need to check them out yourself.
A typical vibe is HTC stock ROMs will typically give the most reliable experience, eg less crashes, less bugs, etc, but tend to also lack features.
Unlocking your phone and modding it requires you to read and understand what you are getting yourself in to. It is not a perfect smooth ride, it is not for the average "non technical" user.
5)Not really
twistedddx said:
1)Factory data reset in bootloader just clears the /data partition but does not function correctly at all if you unlock the bootloader for this device.
The only way to relock the bootloader is to do fastboot oem lock
2)As timmaaa said, follow the index. You want to unlock bootloader, flash ROM with root, get supercid, s-off.
The catches are:
AT&T devices need to gain temp root to get supercid before they can unlock bootloader.
Newer HTC updates eg new 3.17 and 5.xx updates may prevent you from getting supercid even with root, you may need to investigate downgrading things to get supercid.
With an unlocked bootloader, you are well on your way. You should check if you have supercid and if you are s-off.
3)Do not attempt to install HTC updates after you modify the phone. OTA is particular can be dangerous but even RUU's can be dangerous under some circumstances. OTA have many rules which are easy to follow once you have an idea of what they do, best bet is to just ignore them, RUU is fine if you have both s-off and supercid.
4)You can not ask that question and we can not answer it. It is unfair for someone to rate ROM's over other ROMs as the devs put a lot of effort in to these things. Each ROM is special in its own way, you need to check them out yourself.
A typical vibe is HTC stock ROMs will typically give the most reliable experience, eg less crashes, less bugs, etc, but tend to also lack features.
Unlocking your phone and modding it requires you to read and understand what you are getting yourself in to. It is not a perfect smooth ride, it is not for the average "non technical" user.
5)Not really
Click to expand...
Click to collapse
thanks a lot man....
i appreciate since u elaborated on every aspect...!! =)
btw m sorry if i am wrong but what i meant in my first question was does rooting or a reset or flashing affect the "sim unlock" (or the factory unlock or jailbreak)? [the vendor says its unlocked to work on all networks]
besides you are right i was wrong with the approach.. every developer puts in a lot of efforts in ROM development and its not fair to rate it!
the only reason i would possibly root is to remove bloatware.
and rvhaval
timmaaa said:
You need to find the correct root method for your current hboot. If your phone is the at&t model, click the link in my signature, then find the right root method for you. If it's not, just go to htcdev.com and unlock your bootloader, then you can flash TWRP recovery, and flash a custom ROM.
Sent from my Evita
Click to expand...
Click to collapse
thanks i will surely go through that!
the thing that actually haunts me is this phone doesn't have a removable battery so if anything goes wrong and i have some boot loops i would be in a very hopeless situation.. So I need to go through everything!
Sonone said:
thanks i will surely go through that!
the thing that actually haunts me is this phone doesn't have a removable battery so if anything goes wrong and i have some boot loops i would be in a very hopeless situation.. So I need to go through everything!
Click to expand...
Click to collapse
You can simulate a battery pull by holding volume down and power buttons together. When you do this the button lights will start flashing, when they stop flashing you can let go of the power button but keep holding volume down. This will take you to the bootloader.
Sent from my Evita
Sim unlock is unrelated to bootloader unlock, ROM flashing, etc etc.
The sim unlock should survive most everything you will do. Although I have not tested as my device was never locked.
thanks!! i hope it survives!
timmaaa said:
You can simulate a battery pull by holding volume down and power buttons together. When you do this the button lights will start flashing, when they stop flashing you can let go of the power button but keep holding volume down. This will take you to the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
that sounds good!!
the people on this device forum seem very helpful:good::angel::highfive:
timmaaa said:
You can simulate a battery pull by holding volume down and power buttons together. When you do this the button lights will start flashing, when they stop flashing you can let go of the power button but keep holding volume down. This will take you to the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
that sounds good!!
the people on this device forum seem very helpful:good::angel::highfive:
so Timaaaa i have done the following...
please i would like to give you a brief update of the following things..
1)Unlocked Bootloader
2)i have s-off
3)supercid is 11111111
4) installed twrp version 6.xx.xxx
5)my radio is 1.30a.32.45.18
6)hboot is 2.15.0000
7)device is now rooted
so m i good to flash custom roms like Cm,PAC,SLIM?
That all looks fine apart from two things.
The TWRP version you mentioned doesn't look right, the latest TWRP is 2.6.3, could you double check that?
Also, your hboot is 2.15 which will be ok for flashing cm, but I think PAC still has a restriction to hboot 2.14 and I'm not sure about Slim. Hboot 2.15 is perfect for running the latest Sense 5 ROMs though.
Sent from my Evita
timmaaa said:
That all looks fine apart from two things.
The TWRP version you mentioned doesn't look right, the latest TWRP is 2.6.3, could you double check that?
Also, your hboot is 2.15 which will be ok for flashing cm, but I think PAC still has a restriction to hboot 2.14 and I'm not sure about Slim. Hboot 2.15 is perfect for running the latest Sense 5 ROMs though.
Sent from my Evita
Click to expand...
Click to collapse
As u said i checked again its 2.5.0.0 how to update twrp?
it actually works well......
btw is it possible to change hboot version?
and thanks as always!
TWRP 2.5 is full of bugs, you should update to at least 2.6, here's how:
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you'll have a much better version of TWRP.
You can upgrade and downgrade your hboot, there's a thread on our forum somewhere but I can't remember where, just search downgrade hboot within our forum and it should appear.
Sent from my Evita
did that... btw when i installed it... and tried to clear the cache partition and dalvik cache it said it "failed"...!!
Btw also i wanted to know..
since i had a Samsung before flashing a rom just meant copying the zip file and installing it through cwm followed by a resets (if needed)
is this the same way for HTC ONE xl. or like Sony do i have to first unzip the downloaded rom.. and flash the "boot.img" separately??
So even after putting TWRP 2.6 on your phone you get a failed message when trying to wipe?
With this phone all you need to do is copy the ROM zip onto the phone and install it, you are s-off so you don't need to worry about flashing the boot.img via fastboot.
Sent from my Evita
i tried it again mate and it works absolutely fine!
yay!!!! :laugh: flashing roms will be great!:good:
wish if we had a dual boot interface like we have on our computers installing every single app again becomes so inconvenient!:fingers-crossed:
btw m really sorry to bombard you with all the quetions:silly: i just needed to ask one thing that do we have a list of bloatware apps which are safe to remove..
i did google it but then it was very specific to carrier bloatware. as i have got an unlocked version there are no carrier bloatware apps but i do have some apps which seem useless at the moment.. i did freeze a few... but it would have helped if there would have been a list!
I'd love a dual boot setup too. In terms of bloatware, you can remove a fair bit but be careful while doing it. Removing anything that is integral to the running of the ROM will cause problems. Things like Stocks, Picasa, Talkback can be removed if you don't use them. Obviously don't remove anything like Phone or Messages lol.
Sent from my Evita
timmaaa said:
I'd love a dual boot setup too. In terms of bloatware, you can remove a fair bit but be careful while doing it. Removing anything that is integral to the running of the ROM will cause problems. Things like Stocks, Picasa, Talkback can be removed if you don't use them. Obviously don't remove anything like Phone or Messages lol.
Sent from my Evita
Click to expand...
Click to collapse
ya i wont ripp off phone or system ui etc :laugh:
m thinking of flashing clean rom 7.0.1 but den it seems it has an at&t bootscreen or something like that during start up which m not very inclined to have....
so i will stick to the rules not asking for any advice on which rom is preffered as every one of dem i great and i will check them out one by one.
I haven't tried the new Cleamrom, it's a very stock kind of ROM which isn't really my flavour but it's a very popular ROM.
Sent from my Evita
All, please be aware that S-OFF is not a trivial thing to do - once you are S-OFF, you will NOT be able to go S-ON again, try and you'll have a nice mini paperweight!
You'll find that S-OFF can cause more problems than it can "solve" - a quick search will show that you may (actually, most likely will) have to keep your bootloader LOCKED to boot your ROM - a locked bootloader = no fastboot = no flashing new boot or recovery images. UNLOCKED = boot loop city, with you as the mayor!
The only way to use fastboot would be to run revone via adb shell or the TWRP built-in terminal, boot to hboot, do your fastboot stuff, then revone again to relock the bootloader so you can actually boot your ROM.
The reason that S-OFF became a popular was to remove HTC's system protection - system protection basically removes any changes made to the system and reverts to the original system image every time you reboot. REALLY annoying. S-OFF allows system mods, which is a good thing, BUT: It's NOT necessary, as the proper solution is a custom kernel which removes the system protection without you risking a bricked phone.
Bottom line is, AVOID S-OFF if you can.
S-OFF does have benefits and is very handy in certain situations, but felt that people should also be aware of the risks, and think before doing it, "Do I REALLY need to do this, or can I wait a short time after an Android version upgrade for a modded kernel, or ROM with kernel mods?"
I've now helped 16 members out of soft bricks, it's a long and laborious process - everybody wants the latest and greatest (I know I do!), but a little forethought and patience may save you £500 buying a new phone to get the latest and greatest. There is no claiming on warranty or asking for a refund for your brick.
Is this true, you can't turn s-on again without bricking the phone?
Also I'm currently s-off with an unlocked boot loader and don't suffer any boot loops. Using Magio R3 JB4.22 and JMZ kernel. Maybe you would suffer boot loops with a different setup, I don't know..
Also the kernel I'm using I'm sure has system protection disabled. Does this make s-off pointless for me? Does this do the same as s-off?
cheers.
Sent from my HTC One using Xparent Green Tapatalk 2
You my friend, are a smart man. You've stuck with a stable ROM which has a lot of solid development work which had been tested and verified. JMZ knows exactly what he is doing, and produced a kernel which, as you correctly pointed out, negated the need to s-off. ALL of the issues reported for 4.3 are down to people buggering about with something they don't really understand.
Stay stable.
Just in case I did at some point want to update my rom at a later date to 4.3 or maybe 4.4 when it's released, will I have issues being s-off? And is it possible to undo s-off? Or could I leave it as is without issues? I just want to be clear on this. Cheers.
Sent from my HTC One using Xparent Green Tapatalk 2
RuffBuster said:
Just in case I did at some point want to update my rom at a later date to 4.3 or maybe 4.4 when it's released, will I have issues being s-off? And is it possible to undo s-off? Or could I leave it as is without issues? I just want to be clear on this. Cheers.
Sent from my HTC One using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
There are roms for 4.3 (stock deodexed by tr1gg3r) which have a modded kernel which removes system protection, so no need for s-off - there is a new 4.3 magio rom coming very soon, I've been beta testing for a week.... It's sweeeeeeet! It's going to be about 60% smaller than the usual mini ROM due to getting rid of the massive amount of bloat.... Fast, trim, and battery life is a good 40% better!
When kitkat arrives (in February apparently!), it will be system protected, so I don't doubt the whole "stock/s-off" thing will kick off again - my advice to everyone is to have patience, a modded kernel included in a rom will be available a few days after the OTA....
Going s-off then attempting s-on is very risky.....
Hope this helps!
nelvinchi said:
There are roms for 4.3 (stock deodexed by tr1gg3r) which have a modded kernel which removes system protection, so no need for s-off - there is a new 4.3 magio rom coming very soon, I've been beta testing for a week.... It's sweeeeeeet! It's going to be about 60% smaller than the usual mini ROM due to getting rid of the massive amount of bloat.... Fast, trim, and battery life is a good 40% better!
When kitkat arrives (in February apparently!), it will be system protected, so I don't doubt the whole "stock/s-off" thing will kick off again - my advice to everyone is to have patience, a modded kernel included in a rom will be available a few days after the OTA....
Going s-off then attempting s-on is very risky.....
Hope this helps!
Click to expand...
Click to collapse
so once u s-off, is better to stay s-off right? Unless u have to exchange for warranty or something then u would have to take the risk to s-on. And btw what is that 4.3 Rom? Is it like a stock Rom or sense Rom?
@abzboi "And btw what is that 4.3 Rom? Is it like a stock Rom or sense Rom?"
it is the 4.3 rom that you have been discussing with tr1gg3r84 on his magiorom thread !!
abzboi said:
so once u s-off, is better to stay s-off right? Unless u have to exchange for warranty or something then u would have to take the risk to s-on. And btw what is that 4.3 Rom? Is it like a stock Rom or sense Rom?
Click to expand...
Click to collapse
Warranty - If you touch the bootloader in ANY way, s-off/s-on, whatever, the device is MARKED and no tool or method to re-stock can hide this - if it goes back to HTC and is checked, they WILL know you have messed about with it. Fact.
For whatever reason someone has gone s-off, it's best not to mess about with it, the more modding the messier it gets. Google "back to s-on" and you'll see so many horror stories, and so many "HOW to return to 100% STOCK - 100% working!". Yeah, right.
S-OFF is unnecessary UNLESS you are an actual DEVELOPER, and have a full understanding of android and HTC system. 4.3 came out, people posted OTA's, then everyone found that they couldn't flash it as they were rooted/custom rom/custom recovery - ooooh, if i go back to "stock" i'll be able to install it. Errrr, I think you'll find that the majority of people who attempted to "re-stock" found that, "re-stock" = soft brick.
Stock rom IS sense rom
Braddison said:
@abzboi "And btw what is that 4.3 Rom? Is it like a stock Rom or sense Rom?"
it is the 4.3 rom that you have been discussing with tr1gg3r84 on his magiorom thread !!
Click to expand...
Click to collapse
Indeed it is. I've been beta testing versions for the past couple of weeks, and can confirm it's fast, slim, and de-bloated. Battery life is around 40% better....
@nelvinchi brilliant ! i've came from an galaxy s3 running slim rom and been looking for a superslim rom since gettin a one mini (as we are restricted with storage space).i hope tr1gg3r84 uploads the rom this weekend.
Re: S-off... i have no issues with s-off at the moment(no boot loops etc).will find out if i run in to difficulty when i flash the new MagioRom .
cheers
Braddison said:
@nelvinchi brilliant ! i've came from an galaxy s3 running slim rom and been looking for a superslim rom since gettin a one mini (as we are restricted with storage space).i hope tr1gg3r84 uploads the rom this weekend.
Re: S-off... i have no issues with s-off at the moment(no boot loops etc).will find out if i run in to difficulty when i flash the new MagioRom .
cheers
Click to expand...
Click to collapse
You are s-off - you'll be fine with this as it doesn't require a fastboot flash of the boot.img, so no bootloader unlocking/relocking necessary....
Can I ask (just out of curiosity):
If you are LOCKED/UNLOCKED
hboot version
SuperCID
Current ROM and recovery
Thanks!
cool.
S-off unlocked (used ramrunner not revone)
hboot- 2.19.00
supercid- no
rom- stock sense 5.5 4.3 deodex by tr1gg3r84
recovery- twrp not cwm
i did run into a few issues throughout the whole process to be honest though...After running superwipe it deleted everything,even the rom i was going to flash on sd.
i had to push rom to phone but it failed to flash. i then had to push rom and supersu to /data/local, then rom flashed from there but
couldnt find the md5 but it has worked without any issue since (you had helped me out by this point,thanks again)
cheers
I've just discovered that if you have hboot version 2.21 you will NOT need to re-lock your bootloader to prevent boot loops after going S-Off. However, in order to update your hboot to 2.21, you have to go S-off first, LOL. Just know that you won't be able to boot to anything other than recovery or fastboot until you update your hboot to 2.21. Hope this helps someone some day
Hum...
If i'm :
HBOOT 2.19
S-OFF
SUPERCID
Bootloader unlocked with htcdev
Root
On the stock 4.2.2 rom after purchase
I can't flash the stock rom of tr1gg3r84 or i may brick or have boot loops ?
@PuffDaddy_d Hey im currently S-off, unlocked bootloader ,hboot- 2.19.00 . never had any issues with bootloops no matter what rom I've tried. never had to flash the boot.img via fastboot either!
i take it that you mean we have to update our hboot for tr1gg3r84s new stock 4.4.2 rom or we will face bootloops ??
cheers
Braddison said:
@PuffDaddy_d Hey im currently S-off, unlocked bootloader ,hboot- 2.19.00 . never had any issues with bootloops no matter what rom I've tried. never had to flash the boot.img via fastboot either!
i take it that you mean we have to update our hboot for tr1gg3r84s new stock 4.4.2 rom or we will face bootloops ??
cheers
Click to expand...
Click to collapse
You might be right - I didn't go S-Off until I tried the new 4.4.2 Rom, so it very well could've worked with previous versions.
For the "boot loop city" you refer to while being s-off and unlocked. remove the file /system/bin/hcheck. It will fix that problem. No need to relock and unlock all the time
And why can you NOT go back S-ON?
And the write protection is in kernel and has nothing to do with S-OFF. Well, actually, kernel checks status of S-OFF/S-ON. If its on then don't allow system edits. If it is OFF then allow system edits. You can be s-on with a modified kernel and make changes to system