Related
Hey, I'm gonna come with a really noobish question I gues... I've read alot of guides and such about this, but I still don't find anything that states it clearly, and it can get kinda confusing.
I have an HTC Desire that I want to root, it has HBoot 0.92 and OTA Froyo 2.2, I don't think this is a problem anymore though?
Now, I believe my phone is unbranded/unlocked - any way to check?
And what radio would I need to use? I'm from denmark and the tele company is called Telia... Does it matter?
And since I'm from denmark, I can't buy any paid apps off the market, and it pisses me off, rooting will fix that right?
I'd like to use the OpenDesire ROM. But it's a bit confusing with all kinds of topics refering to eachother, and the "Ultimate guide on rooting" says that I need HBoot 0.80 and a current rom of 1.15 (or something like that), I have 2.2 >.<
Thanks in advance.
Go to Settings>About phone>Software information
If your phone has S/W 2.09.405.8 then you're on a generic Desire - which is a good thing!!
Next is to check the box specification - if it says you've got a 3.7" AMOLED screen then you can downgrade the HBOOT and root your phone. If it doesn't say AMOLED then you've got a bit more work involved and the information you need is in the ROM Development forum
Hey, thanks for the quick reply!
I got everything you said.
So that means I can just use Unrevoked?
And how about the market? That's one of the main reasons for me to root, so that I'd be able to access the full market?
Bump? Or something
there's no way to root a Desire with the Bootloader HBoot 0.92 known yet, which you got after you've upgraded to Android 2.2.
This means you have to downgrade the bootloader first, root it with unrevoked, ...
There are several guides out there.
But the important thing is, that you must downgrade the Bootloader in order to root your device.
UpSpin said:
there's no way to root a Desire with the Bootloader HBoot 0.92 known yet, which you got after you've upgraded to Android 2.2.
This means you have to downgrade the bootloader first, root it with unrevoked, ...
There are several guides out there.
But the important thing is, that you must downgrade the Bootloader in order to root your device.
Click to expand...
Click to collapse
Aye, I kinda wrote that
I'm interested in the market problem for me.
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Manarch101 said:
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Click to expand...
Click to collapse
Are you following the guide in the wiki?
Sent from my T-Mobile G2 using XDA App
Manarch101 said:
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Click to expand...
Click to collapse
First, yes you need S-Off to do a nandriod back up.
Second, you do not have permroot if you do not have S-Off. To get S-off there are several ways but I recommend using Rage+gfree found Here: in sub section "Rooting the Vision (G2/DZ) and DHD" This by far is the safest way to root.
But to let you make an informed decision there is also Visionary, now people in properly using this method, has produced a lot of soft bricks, I my self rooted this way, but again I still recommend using Rage+Gfree. But if you wish to still give Visionary a shot, Heres a link on how to properly use Visionary, make sure you follow everything to the "T". Read everything I have written in the post, do everything I have written in the post, then follow the videos exactly. But just to be clear, I am still recommending using the Rage+Gfree method. Happy Rooting.
ok joemm I tried the rage directions that you told me and I am not sure if it worked is there a way of knowing if it worked or not
Edit: nvm I can now get into CWM area which I could not get into before thanxs for the help and info.
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
This is a technical forum not some fire and brimstone 'do it or you'll die' sermon. Let's not construe fact and fiction/personal opinion on here. Just dish the facts unless otherwise rerquested.
As for gaining s-off, follow the wiki, push the files and you can literally copy and paste the commands if you need to (I suggest that so you don't screw up and brick your phone).
KCRic said:
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
This is a technical forum not some fire and brimstone 'do it or you'll die' sermon. Let's not construe fact and fiction/personal opinion on here. Just dish the facts unless otherwise rerquested.
As for gaining s-off, follow the wiki, push the files and you can literally copy and paste the commands if you need to (I suggest that so you don't screw up and brick your phone).
Click to expand...
Click to collapse
LOL..........how does he flash a custom CWM recovery with out having a rooted phone? Remember he is using ClockWorkMod to do a back up?
KCRic said:
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
Click to expand...
Click to collapse
S-OFF lets you flash unsigned images and overrides version checking ,it isn't just about writing to the system while booted. I think you may be confusing defeating the NAND write protection with the actual S-OFF.
As far as I know you need S-OFF to flash a custom recovery, and you need CWM recovery to do a nandroid backup. I have never tried flash_image but I would be suprised if that let you flash a custom recovery while S-ON, because flash_image is just a regular binary.
Sent from my HTC Desire Z
steviewevie said:
S-OFF lets you flash unsigned images and overrides version checking ,it isn't just about writing to the system while booted. I think you may be confusing defeating the NAND write protection with the actual S-OFF.
As far as I know you need S-OFF to flash a custom recovery, and you need CWM recovery to do a nandroid backup. I have never tried flash_image but I would be suprised if that let you flash a custom recovery while S-ON, because flash_image is just a regular binary.
Sent from my HTC Desire Z
Click to expand...
Click to collapse
True you can't flash a custom recovery and have it stick after a reboot but you can package it into an update.zip and flash it when you get into recovery. Aside from that you're phone performs the same. That's how we did everything on the MT slide before some one found a method to gain s-off. Of course there were no custom MTD partitions and we couldn't change the splash but that falls into the 1% of things the average 'rooter' will not attempt. The only reason we needed the ENG hboot was so that adb would catch our phone in recovery every time without running a loop.bat and praying to god. As far as NAND write protection, normally when a dev manages to break s-on they also break the write protection. At least that's what I've seen in phones with s-off. Are there any not like that?
Hopefully I didn't come off as an ass earlier, didn't mean it. I got 3 hours of sleep and I'm pulling a 13 hour day with a foot of fresh snow outside
I think you might be drawing too much comparison with earlier phones. The DZ and DHD have much stronger security than earlier phones. People familiar with experience of older HTC Android phones have often made incorrect assumptions about how things work on the DZ, some things are quite different (and typically much more complicated to unlock)
Sent from my HTC Desire Z
steviewevie said:
People familiar with experience of older HTC Android phones have often made incorrect assumptions...
Click to expand...
Click to collapse
Hell yes! And I'm one of them!
Last night I put some Cyanogen 6.1 flavoured ROM on my Magic/Sapphire. It was so easy: like 2 years ago or so I flashed some S-OFF ENG hboot, put some nice custom recovery on the phone and there I went, peacefully since ever. Reason for flashing the 6.1 CM was me giving the fone to my GF so that I can pick up a brand new Desire Z.
I came here, wanted to quickly crack that thing to play around with it and I find some gFree, Visionary, adb push stuff blah blah blah (I know my way around adb, that's not the point), it seems to have become alot more difficult than back in the days, as pointed out by steviewevie.
So, anyone willing to *quickly* summarize what has changed in the last 12 months regarding "rooting", "cracking" and ROM-customizing HTC devices for me...? I'm still, uhm... well, I'm shocked and overwhelmed. In the store I thought: cool, 7pm, device mine, home by 7:30, rooted by 8, Gingerbread-flavour on it by 8:30-9pm, ROM customization (settings and such) from 9-10, sleepy time by 10:30pm. Nah, it's past 10:30 and I'm still trying to figure out what's what with the new devices...
schaggo said:
Hell yes! And I'm one of them!
Last night I put some Cyanogen 6.1 flavoured ROM on my Magic/Sapphire. It was so easy: like 2 years ago or so I flashed some S-OFF ENG hboot, put some nice custom recovery on the phone and there I went, peacefully since ever. Reason for flashing the 6.1 CM was me giving the fone to my GF so that I can pick up a brand new Desire Z.
I came here, wanted to quickly crack that thing to play around with it and I find some gFree, Visionary, adb push stuff blah blah blah (I know my way around adb, that's not the point), it seems to have become alot more difficult than back in the days, as pointed out by steviewevie.
So, anyone willing to *quickly* summarize what has changed in the last 12 months regarding "rooting", "cracking" and ROM-customizing HTC devices for me...? I'm still, uhm... well, I'm shocked and overwhelmed. In the store I thought: cool, 7pm, device mine, home by 7:30, rooted by 8, Gingerbread-flavour on it by 8:30-9pm, ROM customization (settings and such) from 9-10, sleepy time by 10:30pm. Nah, it's past 10:30 and I'm still trying to figure out what's what with the new devices...
Click to expand...
Click to collapse
Its become more difficult because device manufacturers have made it more difficult. The "official" means to root the Vision is posted on the Vision wiki page here at XDA.
Sent from my T-Mobile G2 using XDA App
Thanks for the answer. I got the thing cracked in the meantime. The device feels so much smoother without Sense... and Gingerbread is good for one's soul
Is this even possible to RUU back to the old OS then root? I downloaded this file
RUU_Vivo_W_VERIZON_WWE_1.34.605.3_Radio_0.99.01.02 25_2_NV_VZW1.92_release_181303_signed.exe
I want to try it but I don't want to brick my device of only 2 days old... lol
Come on! Be bold for the rest of us! Lol..I think someone said they tried it and it didn't work with s-on, however it does work with s-off.
I've also read that it fails when trying to flash the Froyo RUU over GB. It didn't brick it or anything, though.
If it does work with S-Off, in theory, if you have 2.3, you could use at XTC clip to achieve S-Off, then use the RUU to downgrade to Froyo, then root, CWM, etc. Right?
beenz said:
I've also read that it fails when trying to flash the Froyo RUU over GB. It didn't brick it or anything, though.
If it does work with S-Off, in theory, if you have 2.3, you could use at XTC clip to achieve S-Off, then use the RUU to downgrade to Froyo, then root, CWM, etc. Right?
Click to expand...
Click to collapse
I think what they are primarily looking for right now is a temp root for 2.3.3 so we can use the s-off tool. The old root exploit was patched with the 2.3.3 update, without that we can't downgrade and use the tool to achieve s-off, correct me if I'm wrong.
Whatever they do I hope they do it quick I cannot take sense for another day lol.
Yeah, I think it may fail too. I like Sense, I just want to remove the garbage that comes on this thing.
Any RUU from Verizon suck as the one mentioned above, will work on S-OFF, that's the beauty of S-OFF you don't need a file signed by HTC... with S-ON that RUU should flash since it is by HTC, it may say main bootloader is older and fail I'm not sure... I'd put it into a PG32IMG.zip and flash in hboot.. you can do this with the .3 RUU and the .4 exe
andybones said:
Any RUU from Verizon suck as the one mentioned above, will work on S-OFF, that's the beauty of S-OFF you don't need a file signed by HTC... with S-ON that RUU should flash since it is by HTC, it may say main bootloader is older and fail I'm not sure... I'd put it into a PG32IMG.zip and flash in hboot.. you can do this with the .3 RUU and the .4 exe
Click to expand...
Click to collapse
I'm actually downloading it right now, going to try and just flash it, if that fails then going to try it with GoldCard.
Let us know if it works for you.
Sent from my ADR6350 using XDA Premium App
rm2011 said:
Let us know if it works for you.
Sent from my ADR6350 using XDA Premium App
Click to expand...
Click to collapse
Tried .exe method, no go. Tried regular method by renaming, no good, funny part is it doesn't even give a error or nothing when it loads it up, it just goes back to the Bootloader menu. Then i tried the Gold Card method, no go, although i did format my card, but i read that once you have a Gold Card it stays a Gold card. So unfortunately, even if i did root this phone and didn't upgrade to 2.3, because i'm getting a much needed replacement i'm doomed for 2.3 anyway. Whelp i tried.
shoman24v said:
Is this even possible to RUU back to the old OS then root? I downloaded this file
RUU_Vivo_W_VERIZON_WWE_1.34.605.3_Radio_0.99.01.02 25_2_NV_VZW1.92_release_181303_signed.exe
I want to try it but I don't want to brick my device of only 2 days old... lol
Click to expand...
Click to collapse
You try this yet?
EDIT: Sorry, when I was reading this thread the only post that came up was the original. Once I replied they all showed up. Weird, but apologies.
shoman24v said:
Is this even possible to RUU back to the old OS then root? I downloaded this file
RUU_Vivo_W_VERIZON_WWE_1.34.605.3_Radio_0.99.01.02 25_2_NV_VZW1.92_release_181303_signed.exe
I want to try it but I don't want to brick my device of only 2 days old... lol
Click to expand...
Click to collapse
I tried this way back before I got my xtc clip and the answer is no it will not work with s-on. It looks like its going to work and then displays a message about bootloader or something to that affect. I have it somewhere in these threads.
So here's a question off the top of my head. Probably not possible, but I'll ask anyway.
So the bootloader will only install HTC signed files, and we have HTC signed files of FroYo that the bootloader rejects. So there must be some kind of version check where it'll only flash a file with a higher version number than what's currently on the phone. If we knew where it was checking, would it be possible to modify a FroYo RUU file to report a higher version than the current GB so the bootloader thinks it's installing an upgrade instead of a downgrade?
Like I said, probably not possible, but it would seem to be logical.
ChrisDDD said:
So here's a question off the top of my head. Probably not possible, but I'll ask anyway.
So the bootloader will only install HTC signed files, and we have HTC signed files of FroYo that the bootloader rejects. So there must be some kind of version check where it'll only flash a file with a higher version number than what's currently on the phone. If we knew where it was checking, would it be possible to modify a FroYo RUU file to report a higher version than the current GB so the bootloader thinks it's installing an upgrade instead of a downgrade?
Like I said, probably not possible, but it would seem to be logical.
Click to expand...
Click to collapse
It does make sense, however the signature is generated from the contents of the file. If you change the contents of the file, it invalidates the signature and the boot loader won't load it. That is how HTC prevents you from modifying official HTC files.
ChrisDDD said:
So here's a question off the top of my head. Probably not possible, but I'll ask anyway.
So the bootloader will only install HTC signed files, and we have HTC signed files of FroYo that the bootloader rejects. So there must be some kind of version check where it'll only flash a file with a higher version number than what's currently on the phone. If we knew where it was checking, would it be possible to modify a FroYo RUU file to report a higher version than the current GB so the bootloader thinks it's installing an upgrade instead of a downgrade?
Like I said, probably not possible, but it would seem to be logical.
Click to expand...
Click to collapse
If you modified the file. It wouldn't be signed by HTC anymore.
If it is checked by md5, it can be spoofed.
http://www.win.tue.nl/hashclash/SoftIntCodeSign/
Sent from my ADR6350 using XDA App
slydweis said:
If it is checked by md5, it can be spoofed.
http://www.win.tue.nl/hashclash/SoftIntCodeSign/
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
I remember this being discussed before in the Eris forum. I can't find the thread, but I believe that the signature is somehow encrypted, and you would need the encryption key. I believe they even discussed if you could crack the encryption code, and although possible, it was not likely.
tpbklake said:
It does make sense, however the signature is generated from the contents of the file. If you change the contents of the file, it invalidates the signature and the boot loader won't load it. That is how HTC prevents you from modifying official HTC files.
Click to expand...
Click to collapse
I figured that, I just wondered if since all that would presumably need to be changed would be a single digit, if there would be any way to do it without screwing up the signature, like with a hex editor or something.
But, like I said, I figured it wasn't possible...
Hi, I'm a complete noob to modifying smartphones and my knowledge is very limited.
I wish to install a custom rom to my HTC Desire.
One of the reasons is that the device is overheating and falling into a reboot loop and I beleive that to be a software glitch and hope this would help (not sure, but could be).
Anyway, I've found a really nice tutorial made by linkslovesandroid, http://forum.xda-developers.com/showthread.php?t=1016084 and have come to a stop at the very beginning since it says:
"**This method only works for users with hboot 0.93 and lower. Sorry 1.06 users, but until unrevoked updates, your stuck on stock htc***"
I've looked up my hboot and it's 6.93.
I presume that it will not work then.
So...can I modify my hboot, if yes how, is there another workaround or another tutorial (understandable for my level of knowledge which is close to 0) I may follow?
Please help!
if you will check hboot(power and vol -)/fastboot(power+back) screen it will say S-OFF
so you don't need to do anything just access recovery and flash any rom you like just keep in mind you have to adhere any developer requirements
RagnarokCosmos said:
One of the reasons is that the device is overheating and falling into a reboot loop and I beleive that to be a software glitch and hope this would help (not sure, but could be).
Click to expand...
Click to collapse
The reason the device is overheating and rebooting is due to a very well known hardware fault with the Bravo. Changing ROMs won't help.
Thanks to the both of you.
Indeed it is S-off..
I've researched the matter further and I fear it is as you say, a hardware error, there are numerous reports about faulty motherboards if that is what you mean.
I got the device 2nd hand so no warranty or anything, hope it's not too expensive to fix it, although if it is a motherboard issue, I'm afraid of the price.
Does anyone know aprox. how much does it cost to fix this?
No idea. Ebay is your best bet.
RagnarokCosmos said:
"**This method only works for users with hboot 0.93 and lower. Sorry 1.06 users, but until unrevoked updates, your stuck on stock htc***"
I've looked up my hboot and it's 6.93.
I presume that it will not work then.
So...can I modify my hboot, if yes how, is there another workaround or another tutorial (understandable for my level of knowledge which is close to 0) I may follow?
Please help!
Click to expand...
Click to collapse
My desire has same hboot. I made S-OFF with revolutionary method (check alpharev webpage).
Once you are S-OFF you can change your hboot just by downloading the hboot image from alpharev. Rename zip to PB99IMG.zip and place it at your sd-card. Reboot on bootloader, zip will be detected and you will be asked if you want to apple update, answer yes. And that's all, enjoy your new hboot.
Howdy! Lemme preface all of this by saying that I'm less than a noob here....really inexperienced. Here's the background......
I rooted my DInc and I can't even remember which unrevoked tool I used. I was just reading along and punching commands and when the process was done I was rooted. I installed CWM successfully and flashed to CM7.2 which I've been running for quite some time. Lately I got an itch to try a JB ROM like infected, so when I looked into it, it clearly says I need S-off to accomplish that flash so I checked and realized I was S-on still.
At this point, I added the unrevoked-forever.zip to my sdcard root and tried to flash that ZIP by way CWM and i get these error messages:
E: unsupported radio version
E: update failed. Check/sdcard/soff.log
E: error in /sdcard/unrevoked-forever.zip (Status 42)
I am running Android version 2.3.7 and radio baseband version 2.15.10.12.20
Is this one of those things that I shouldn't be trying from CM7.2 and I should've dealt with before my initial flash to CM7.2?? Basically I'm totally freakin lost and in WAAAAY over my element, so any guidance would be duly appreciated. Thanks in advance!
Scott
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
PonsAsinorem said:
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
Click to expand...
Click to collapse
Sorry....i guess it pays to be extra thorough in the description of the problem. The link you left me is the one that I followed. I researched achieving S-Off on the DInc first and found this same page in my research. I followed the process and all went smooth right up until i started to flash the unrevoked-forever.zip from my sdcard via CWM. The aforementioned error messages came up on my phone and it said the process failed.
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
smvogel73 said:
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
Click to expand...
Click to collapse
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
PonsAsinorem said:
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
Click to expand...
Click to collapse
Yes thx....I'm gathering that! So this is where terminology gets so dang confusing for me. I didn't think unlocking my bootloader meant the same thing as achieving S-Off?? I already thought my bootloader was unlcoked, as I was able to flash CM7.2, which I didnt think I would be able to do if I had a locked bootloader. So wicked confused!!! And try as I miught to educate myself in these forums, I haven't located a sticky or guide that really thoroughly explains all the vernacular regarding android dev/modding/rooting/flashing/etc
So this other method will work with any radio baseband version then?? Or is it important to check compatibility there too??
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
PonsAsinorem said:
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
Click to expand...
Click to collapse
It says "UNLOCKED" and below that it says "S-ON
Thank u for the materials too!
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run. I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.
The ROM I'm looking to flash is Infection JB 4.2.2. The instructions say that if you're coming from. A non-AOSP ROM and are S-On that you've gotta extract boot.img and fastboot it after the ROM flash......whatever the heck that means???
smvogel73 said:
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run.???
Click to expand...
Click to collapse
Correct. Staying S-ON minimizes the danger. It locks your radio, and HBOOT, which are the main dangers.
smvogel73 said:
I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.???
Click to expand...
Click to collapse
Not really ROM flashing, but radio and HBOOT flashing, which is what unrevoked-forever tweaks.
I'd try to flash it one more time. When you do, what, if anything, are you wiping? You should be doing a factory reset, system, and boot wipe/format, then flash the ROM.
If that doesn't work (it might not, it's been awhile since I've worked with S-ON devices), then we'll move on to S-OFF (if you want).
Oh no.....I didn't even attempt to flash the Infection JB ROM specifically because I was not able to achieve S-Off. Whether it was intended or not, yea.....u sufficiently scared me about bricking the phone if I'm not to spec per the developer.
Are u saying I should wipe and then try to flash this ROM despite still being S-On?
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
PonsAsinorem said:
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
Click to expand...
Click to collapse
Well there you have it....I will trust your wisdom (as it is far supperior to my own) and I shall flash this ROM tonight!! I already have a nandroid backup of CM7.2 that Im running, as well as a Titanium backup of all my user apps/files.
Sincerest thanks for all your help!!
Hello. Im no expert but i think Cyanogenmod is aosp so you should be good.
I was where you were 2 yrs ago when I rooted my 1st phone: a friends froyo Dinc (ahhh...froyo). A few months ago I aquired my own and went to research how to root GB and everything has changed and is now vastly more complicated. Also I think every phone has a locked bootloader but not encrypted and I think Soff is extra security since I've only encountered it on htc phones. Anyway I've managed to get my inc to Soff but its still locked, idk how lol
Sent from my ADR6300 using Tapatalk 2