Related
Future of this rom and me - https://plus.google.com/u/0/100983447046094793882/posts/7YtTFWWgT1C
Hope this helps people others comming sooon i have slow internet
Let's hope that nobody will be needing these with the exception of obtaining S-OFF and ROM production.
I added some tags for you too.
All ruus released enjoy
md5's for the ruu's added so enjoy but remeber you need to htc relock your boot loader before you can restore
Have you are anyone tested the relock? Frrom what I remember on previous ones I thought you could not relock like the nexus one.
But basically relock then flash these thru bootloader and you are back to the way has came out the box?
M9x3mos said:
Have you are anyone tested the relock? Frrom what I remember on previous ones I thought you could not relock like the nexus one.
But basically relock then flash these thru bootloader and you are back to the way has came out the box?
Click to expand...
Click to collapse
yep you got it and me and binary both tested the relock scripts they are good to go
xboarder56 said:
yep you got it and me and binary both tested the relock scripts they are good to go
Click to expand...
Click to collapse
I tested that script on an unbiased Windows 7 machine.
Unbiased means that it had nothing but the drivers installed. No adb or fastboot files.
I wanted to clean it up and make it look better but x was in a hurry to release it for whatever reason.
Well clean up and I will reupdate it
Sent from my HTC Amaze 4G using xda premium
xboarder56 said:
Well clean up and I will reupdate it
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
Nah. It's it's not broke, don't fix it.
Lol ok
Sent from my HTC Amaze 4G using xda premium
more various roms/ruus coming wendsday
more ruu's released
Sorry for sounding like a n00b and redundancy but just wanted to make sure I understand this right before I make any changes on device.
The relocker posted by xboarder and binary, does that completely reverse the HTC bootloader unlock done the HTC dev site?
Assuming it does, that does mean we can get the regular updates to device again?
Sorry again if is redundant but just want to make sure there is a 100% way of returning to stock software very much like my vibrant / g2 / hd2
TheArtiszan said:
Sorry for sounding like a n00b and redundancy but just wanted to make sure I understand this right before I make any changes on device.
The relocker posted by xboarder and binary, does that completely reverse the HTC bootloader unlock done the HTC dev site?
Assuming it does, that does mean we can get the regular updates to device again?
Sorry again if is redundant but just want to make sure there is a 100% way of returning to stock software very much like my vibrant / g2 / hd2
Click to expand...
Click to collapse
yes it will let you do updates again if you follow the guide
I've tried installing this via hboot both unlocked and relocked and it doesn't actually do anything. it checks the image then just goes back to hboot. Any Idea what I'm doing wrong?
I am trying to get my Telus Amaze back to stock. I have re locked the phone it says so in the hboot menu. I have downloaded the RRU for Telus and it is on the root of my SD card. When I boot into hboot I see the progress bar in blue on the right hand side, then it goes into yellow verifiying, then it just stops no option to install the update.... It just isn't working.. any thoughts?
gmarcoux said:
I've tried installing this via hboot both unlocked and relocked and it doesn't actually do anything. it checks the image then just goes back to hboot. Any Idea what I'm doing wrong?
Click to expand...
Click to collapse
I am in the same boat. Let me if you figure it out.
hello to every one, can anyone help me with installing the stock rom?
the problem is that after i relock my phone & put the RUU file in the root folder ( with root explorer), i turn of, got in to the bootloder and nothing happened.
what do i need to do from here?
Sent from my HTC_Amaze_4G using XDA App
So, if I were to flash the 1.26 or 1.35, I wonder if I'd get working WiFi calling? Anyone that is still on 1.36.531.4, does your WiFi calling still work?
So like most users, I was very excited to hear about the ICS leak by Football since I've been waiting MONTHS for some sort of development on that.
Getting impatient on waiting for CM9 and Evervolv builds for the Amaze, I really wanted to try this new leak for T-Mobile. So I figured that in order to do that, I must get S-Off.
It seemed like a tedious process so I've been holding it off for a while. Now that I've got a copper wire and everything, I wanted to do the deed once and for all.
So I accidentally flashed a stock rom (which I thought was a good thing since the instructions said I needed a stock rom), but I seem to have lost root access. Superuser runs, but battery calibration says I need to have root first and Titanium Backup doesn't work. However, my phone still says unlocked and I can still run ClockworkMod Recovery. The S-Off program tells me that there's an error. Is there anyone that can help?
bri.kwong94 said:
So like most users, I was very excited to hear about the ICS leak by Football since I've been waiting MONTHS for some sort of development on that.
Getting impatient on waiting for CM9 and Evervolv builds for the Amaze, I really wanted to try this new leak for T-Mobile. So I figured that in order to do that, I must get S-Off.
It seemed like a tedious process so I've been holding it off for a while. Now that I've got a copper wire and everything, I wanted to do the deed once and for all.
So I accidentally flashed a stock rom (which I thought was a good thing since the instructions said I needed a stock rom), but I seem to have lost root access. Superuser runs, but battery calibration says I need to have root first and Titanium Backup doesn't work. However, my phone still says unlocked and I can still run ClockworkMod Recovery. The S-Off program tells me that there's an error. Is there anyone that can help?
Click to expand...
Click to collapse
Well you are on T-mobile so you have two choices here. you can S-off if you want to have total freedom or you can revert your phone to stock and relock your bootloader and flash it and then re-unlock again. but remember flashign this without s-off may prevent you from getting s-off later on.
Ray196 said:
Well you are on T-mobile so you have to choices here. you can S-off if you want to have total freedom or you can revert your phone to stock and relock your bootloader and flash it and then reunlock again.
Click to expand...
Click to collapse
Well, I can't flash the PH85IMG without S-Off, right? Because on the HBoot screen, it would load the file but i wouldn't be asked if I wanted to install it. So I had no idea what to do. I thought I had to have S-Off to install it. Does this really mean I've lost root even though my phone says unlocked and I can run Clockworkmod?
bri.kwong94 said:
Well, I can't flash the PH85IMG without S-Off, right? Because on the HBoot screen, it would load the file but i wouldn't be asked if I wanted to install it. So I had no idea what to do. I thought I had to have S-Off to install it. Does this really mean I've lost root even though my phone says unlocked and I can run Clockworkmod?
Click to expand...
Click to collapse
you can if you lock your boot loader and revert the phone to stock.
Ray196 said:
you can if you lock your boot loader and revert the phone to stock.
Click to expand...
Click to collapse
Well, how do i revert it to stock and reroot it exactly?
bri.kwong94 said:
Well, how do i revert it to stock and reroot it exactly?
Click to expand...
Click to collapse
i think you can use this. http://forum.xda-developers.com/showthread.php?t=1493905
bri.kwong94 said:
Well, how do i revert it to stock and reroot it exactly?
Click to expand...
Click to collapse
Pretty sure you just use fastboot to lock, open a command prompt with your phone attached in debugging mode, type in fastboot oem lock, then install the stock rom listed in the development section. (If I am wrong on this, someone please feel free to correct me.)
Just my luck that Verizon puts this new OTA out the day before I was going to root this thing! It looks to me like we have no option now to root these updated devices. Anyone have any ideas?
therreid said:
Just my luck that Verizon puts this new OTA out the day before I was going to root this thing! It looks to me like we have no option now to root these updated devices. Anyone have any ideas?
Click to expand...
Click to collapse
You either need to wait, or try search how to revert the update.
dafuzzbudd said:
You either need to wait, or try search how to revert the update.
Click to expand...
Click to collapse
I tried to wipe/factory reset then install stock 2.17.605.2 RUU last night from .exe file. Wouldn't let it load due to updated bootloader. I also tried flashing unlock_code.bin from previous unlock experience with Hasoon2000's toolkit without luck as well as running through mdmower's unlock script with attempt to change CID. Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. I'm guessing I probably need root to modify bootloader to revert to old to unlock it... so probably just screwed until someone smarter figures out a way to unlock the new bootloader...
dkkunkel said:
Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. ..
Click to expand...
Click to collapse
Did you make sure your copy and paste to HTC was correct? That was my problem a couple of weeks ago. A single <space> was the culprit for me.
pmcall said:
Did you make sure your copy and paste to HTC was correct? That was my problem a couple of weeks ago. A single <space> was the culprit for me.
Click to expand...
Click to collapse
Yes, it was correct; just like other successful times... Did yours unlock after the latest OTA or was it prior to the update?
dkkunkel said:
I tried to wipe/factory reset then install stock 2.17.605.2 RUU last night from .exe file. Wouldn't let it load due to updated bootloader. I also tried flashing unlock_code.bin from previous unlock experience with Hasoon2000's toolkit without luck as well as running through mdmower's unlock script with attempt to change CID. Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. I'm guessing I probably need root to modify bootloader to revert to old to unlock it... so probably just screwed until someone smarter figures out a way to unlock the new bootloader...
Click to expand...
Click to collapse
Were you rooted with s-off, or s-on?
dkkunkel said:
I tried to wipe/factory reset then install stock 2.17.605.2 RUU last night from .exe file. Wouldn't let it load due to updated bootloader. I also tried flashing unlock_code.bin from previous unlock experience with Hasoon2000's toolkit without luck as well as running through mdmower's unlock script with attempt to change CID. Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. I'm guessing I probably need root to modify bootloader to revert to old to unlock it... so probably just screwed until someone smarter figures out a way to unlock the new bootloader...
Click to expand...
Click to collapse
dkkunkel said:
Yes, it was correct; just like other successful times... Did yours unlock after the latest OTA or was it prior to the update?
Click to expand...
Click to collapse
Prior to update coming out, I have not installed the OTA.
junkmail9 said:
Were you rooted with s-off, or s-on?
Click to expand...
Click to collapse
Rooted, s-on. had avatar nightly installed//had issues with no data service and eventually re-loaded stock RUU with hopes to find a fix (after wiping, clean install, flash/re-flash firmware multiple times) and put avatar back on.... but then the OTA hit and here I am... unable to unlock bootloader.
dkkunkel said:
Rooted, s-on. had avatar nightly installed//had issues with no data service and eventually re-loaded stock RUU with hopes to find a fix (after wiping, clean install, flash/re-flash firmware multiple times) and put avatar back on.... but then the OTA hit and here I am... unable to unlock bootloader.
Click to expand...
Click to collapse
Hopefully you at least have data service now. Unless you can manage SuperCID, you might be out of luck for a while. I hope I'm wrong about that.
I am now curious if anyone who is s-off installed the OTA (either accidentally or intentionally) and retained s-off. In theory, if you're s-off you can recover from nearly anything. (I will admit that I have absolutely no desire to try it for myself)
junkmail9 said:
Hopefully you at least have data service now. Unless you can manage SuperCID, you might be out of luck for a while. I hope I'm wrong about that.
I am now curious if anyone who is s-off installed the OTA (either accidentally or intentionally) and retained s-off. In theory, if you're s-off you can recover from nearly anything. (I will admit that I have absolutely no desire to try it for myself)
Click to expand...
Click to collapse
How were you able to get the CID to change? I followed the CID change script manually using temp-root and DD commands through shell with a hex editor and it would NOT change the CID although I was given no errors. Crazy.
stevey500 said:
How were you able to get the CID to change? I followed the CID change script manually using temp-root and DD commands through shell with a hex editor and it would NOT change the CID although I was given no errors. Crazy.
Click to expand...
Click to collapse
I used DirtyRacun back on the 2nd OTA to obtain s-off, and DirtyRacun does not require the SuperCID method. I have not done anything with the latest OTA, as it isn't worth the risk to me... I somehow doubt that the DirtyRacun will work with the latest OTA, but I do not recall seeing anyone post that they have tried it, either.
junkmail9 said:
I used DirtyRacun back on the 2nd OTA to obtain s-off, and DirtyRacun does not require the SuperCID method. I have not done anything with the latest OTA, as it isn't worth the risk to me... I somehow doubt that the DirtyRacun will work with the latest OTA, but I do not recall seeing anyone post that they have tried it, either.
Click to expand...
Click to collapse
Ah... I'll go ahead and give it a try. This phone bone-stock is nearly unbearably slow. HTC bloating the hell out of these phone and then locking the bootloaders is a sad marketing scheme.
stevey500 said:
Ah... I'll go ahead and give it a try. This phone bone-stock is nearly unbearably slow. HTC bloating the hell out of these phone and then locking the bootloaders is a sad marketing scheme.
Click to expand...
Click to collapse
Anyone figure out if this works?? DirtyRacun after OTA I mean. thanks
join in for the unbelievable ... post2014-OTA [S-OFF] has been achieved
http://forum.xda-developers.com/showthread.php?t=2664460
I was previously on the original HBOOT (first one) and S-Off.
I did NOT have the "TAMPERED" flag on my phone.
After upgrading to latest release I am on the latest HBOOT but now it's also flagged as "TAMPERED".
My understanding is being S-off a way to remove this should exists.
I've never done the HTC unlock as have always been S-Off.
Is it possible to get this removed on latest release without being 100% stock?
I know on some phones like the One you can modify a flag in one of the partitions.
I am on a stock rom just rooted so beyond seeing that flag it's not obvious I am rooted.
Thx
See this post
http://forum.xda-developers.com/showthread.php?p=50112366
Captain has included this mod l
Sent from my EVO using xda app-developers app
JManekia said:
See this post
http://forum.xda-developers.com/showthread.php?p=50112366
Captain has included this mod l
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Nope, he says:
Q8: My bootloader says "TAMPERED" after flashing the firmware. How to fix?
A: Just ignore it. It's no big deal.
Someone did a mod to remove the developer text but that's it. My understanding is the flag doesn't reside in the HBOOT directly but in some other area of the phone?
Run a RUU. It will remove the *TAMPERED* status. Your phone will remain unlocked, and it be displayed as such.
If you don't have easy access to a PC, one of the easiest solutions is to download the VipeRUU zip to your phone, extract the rom.zip to your ext SD, rename it to PJ75IMG.zip, and flash it through the bootloader. The next time that you reboot into the bootloader after the process is completed, then TAMPERED should be gone.
I'm just speculating, but maybe you removed the tampered status before by using the Regaw Bootloader Customizer, which only edits the bootloader info, and doesn't actually change anything for the phone itself. It's only a cosmetic change.
aarsyl said:
Run a RUU. It will remove the *TAMPERED* status. Your phone will remain unlocked, and it be displayed as such.
If you don't have easy access to a PC, one of the easiest solutions is to download the VipeRUU zip to your phone, extract the rom.zip to your ext SD, rename it to PJ75IMG.zip, and flash it through the bootloader. The next time that you reboot into the bootloader after the process is completed, then TAMPERED should be gone.
I'm just speculating, but maybe you removed the tampered status before by using the Regaw Bootloader Customizer, which only edits the bootloader info, and doesn't actually change anything for the phone itself. It's only a cosmetic change.
Click to expand...
Click to collapse
That's what I did - noticed after the 4.3 RUU that it went from "Unlocked/Tampered" to just "Unlocked." I kinda want to also modify the "Unlocked" text as I did before with Regaw's tool, I'll have to look into whether it will work.
SilverZero said:
That's what I did - noticed after the 4.3 RUU that it went from "Unlocked/Tampered" to just "Unlocked." I kinda want to also modify the "Unlocked" text as I did before with Regaw's tool, I'll have to look into whether it will work.
Click to expand...
Click to collapse
There's a reason why I didn't suggest using that tool. You kinda need to MAKE SURE that you know your bootloader status. If you activate S-On twice in a row, that baby's definitely gonna brick. I rather know what my bootloader is supposed to say, because I'm really the only person looking at it. What difference will it really make?
aarsyl said:
There's a reason why I didn't suggest using that tool. You kinda need to MAKE SURE that you know your bootloader status. If you activate S-On twice in a row, that baby's definitely gonna brick. I rather know what my bootloader is supposed to say, because I'm really the only person looking at it. What difference will it really make?
Click to expand...
Click to collapse
Well that's why I said I'd have to look into it. I assumed it wouldn't work with the new HBOOT, and I guess I don't care one way or the other. But for anybody else reading this, don't try it.
On the other hand, I climb mountains because they're there. If I want it to say "Hacked" instead of "Unlocked" and I can do it without screwing things up, I might do it just to screw with the guy who buys it from me down the road.
bryanu said:
I was previously on the original HBOOT (first one) and S-Off.
I did NOT have the "TAMPERED" flag on my phone.
After upgrading to latest release I am on the latest HBOOT but now it's also flagged as "TAMPERED".
My understanding is being S-off a way to remove this should exists.
I've never done the HTC unlock as have always been S-Off.
Is it possible to get this removed on latest release without being 100% stock?
I know on some phones like the One you can modify a flag in one of the partitions.
I am on a stock rom just rooted so beyond seeing that flag it's not obvious I am rooted.
Thx
Click to expand...
Click to collapse
comment withdrawn after further investigation.
redm1st said:
Originally for Hboot 2.09 but should work for Hboot 2.10. (don't quote me on that though)
Click to expand...
Click to collapse
Please don't anyone on the 2.10 HBOOT flash this! Please remove this attachment.
EDIT: This post is what I mean. You have to understand what the Bootloader Customizer actually does (which is explained in the thread) and know that flashing this would bork all the things. This is literally a 2.09 HBOOT. The 2.10 HBOOT is what accommodates the new partition layout, so flashing this will break that and prevent the device from booting up. The issue is the signed boot.img. That's why you see the tampered flag. I assume you're not using my stock rooted? You updated directly from RUU, and then rooted it manually? The signed boot.img sees unsigned recovery img and throws up that tampered flag. It's not going to affect the working of the device, so why worry about it? You can flash the boot image from my stock rooted if you want it to go away.
Captain_Throwback said:
Please don't anyone on the 2.10 HBOOT flash this! Please remove this attachment.
EDIT: This post is what I mean. You have to understand what the Bootloader Customizer actually does (which is explained in the thread) and know that flashing this would bork all the things. This is literally a 2.09 HBOOT. The 2.10 HBOOT is what accommodates the new partition layout, so flashing this will break that and prevent the device from booting up. The issue is the signed boot.img. That's why you see the tampered flag. I assume you're not using my stock rooted? You updated directly from RUU, and then rooted it manually? The signed boot.img sees unsigned recovery img and throws up that tampered flag. It's not going to affect the working of the device, so why worry about it? You can flash the boot image from my stock rooted if you want it to go away.
Click to expand...
Click to collapse
I flashed everything from your post.
I just want the word Tampered gone, don't care if it's done officially or just visually through some other mod.
I currently am S-Off, Locked and says Tampered.
bryanu said:
I flashed everything from your post.
I just want the word Tampered gone, don't care if it's done officially or just visually through some other mod.
I currently am S-Off, Locked and says Tampered.
Click to expand...
Click to collapse
Do a nandroid and then unlock your bootloader.
Captain_Throwback said:
Do a nandroid and then unlock your bootloader.
Click to expand...
Click to collapse
So I have "Tampered" because I am not unlocked?
Take this from a guy who has had 6 replacement phones and 4 of them hard bricked. QualcomDownload Mode. Lol.
Anyways I wanted to get rid of the tampered flag so I did what shouldnt be done and used the One's tool with aroma and only chose to remove rltampered flag.
It worked.
Note that that was my other phone before I hard bricked it but that was because I messed up my EFS folder.
Im not saying that anyone should use it. Do at your own risk I sure did and I just used it on my replacement evo after doing soff.
Sent from my EVO using Tapatalk
chemjb said:
Take this from a guy who has had 6 replacement phones and 4 of them hard bricked. QualcomDownload Mode. Lol.
Anyways I wanted to get rid of the tampered flag so I did what shouldnt be done and used the One's tool with aroma and only chose to remove rltampered flag.
It worked.
Note that that was my other phone before I hard bricked it but that was because I messed up my EFS folder.
Im not saying that anyone should use it. Do at your own risk I sure did and I just used it on my replacement evo after doing soff.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
I had already given up and just installed terminal emulator on my phone and ran the following as su:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
that got rid of it properly without requiring any flashing, fake boot loader modifications etc.
@bryanu: just for my own education, what does that actually do when you type that in terminal. Meaning, I know you said it removes the "tamper" word, but how does it do it. If it is to lengthy to answer, no problem. Just wondering... Thanks!
Sent from my EVO using Tapatalk 2
puhiniho said:
@bryanu: just for my own education, what does that actually do when you type that in terminal. Meaning, I know you said it removes the "tamper" word, but how does it do it. If it is to lengthy to answer, no problem. Just wondering... Thanks!
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
It resets the flag that controls that showing or not essentially.
bryanu said:
I had already given up and just installed terminal emulator on my phone and ran the following as su:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
that got rid of it properly without requiring any flashing, fake boot loader modifications etc.
Click to expand...
Click to collapse
Worked like a charm ,
Thanks
Hi, what is about S-OFF for our device?
Anyone have S-OFF?, As he did? Thanks
For S-Off visit here:
http://forum.xda-developers.com/showthread.php?t=2847983
Sent from my HTC Desire 610 using XDA Premium 4 mobile app
That's incorrect information. There is nothing about s-off in that thread and it doesn't exist yet for our phone. That thread is about system write protection, which is something entirely different.
My bad, copied the wrong post
Sent from my HTC Desire 610 using XDA Premium 4 mobile app
I wish we had s-off, it'd make life easier.
Would have been great to s-off with sunshine but i guess our device is not supported
Someone working on s-off for our device?
Jcase and beaups are working on Sunshine S-off version 3.0, which will most likely support our device. It isn't out yet though, but should be soon. Whatever you do, DO NOT post in the sunshine thread asking anything about it.
$ 25 is a lot for a 610 Thanks for reply
Any advantages now that we can s-off with sunshine?
You can remove that ugly htc red text splash screen for starters
ClearD said:
You can remove that ugly htc red text splash screen for starters
Click to expand...
Click to collapse
Having s-off is news to me. @ClearD, did you purchase this? If so how did you implement it? I went to what I think is the thread but didn't see any notice of how to buy it...
Nevermind. Found it here. And the list confirms our phone. I don't think I'll be buying it because I'm not sure what else I can do that I'm not already doing. Good to know its there though.
http://www.androidpolice.com/2015/03/20/sunshine-3-0-released-with-ability-to-unlock-and-s-off-many-motorola-and-almost-all-htc-handsets/
ClearD said:
You can remove that ugly htc red text splash screen for starters
Click to expand...
Click to collapse
Went and removed red text and added a new splash
With it, you can also change the radio. And bootloader I think. And pretty much anything.
I assume just running the app will remove the red message, but can we just run this with our bootloaders already unlocked and rooted?
And is there anything that changes as far as how we update firmware in the future? I noticed some people were waiting for new exploits, meaning root might've been broken by updates so there must be some more info to it. It'd be great if it had a built in way to take otas even if it means automating the lock/return to stock to do this...
Thats the only thing I'm worried about, I'll s-off, do the whole recovery and mods, Lollipop drops and the only way to update is to relock and RUU. Then be stuck unrooted.
KLit75 said:
I assume just running the app will remove the red message, but can we just run this with our bootloaders already unlocked and rooted?
And is there anything that changes as far as how we update firmware in the future? I noticed some people were waiting for new exploits, meaning root might've been broken by updates so there must be some more info to it. It'd be great if it had a built in way to take otas even if it means automating the lock/return to stock to do this...
Click to expand...
Click to collapse
No, you've gotta flash a new splash screen with the command: fastboot flash splash splash.img
Yes, run it unlocked and rooted. That's optimal.
The current way to root should be fine for the life of the phone. Root tool v4 should be finer, actually. Use it instead. It's easier. No root is broken that I'm aware of.
To get an OTA, you will need to relock and ruu, plain and simple. It's always been that way. I don't know if s-off will affect that or not.
phatmanxxl said:
Thats the only thing I'm worried about, I'll s-off, do the whole recovery and mods, Lollipop drops and the only way to update is to relock and RUU. Then be stuck unrooted.
Click to expand...
Click to collapse
And then when you get the update, you unlock again and re root. Then use titanium backup to restore your apps. It's that easy.
ClearD said:
No, you've gotta flash a new splash screen with the command: fastboot flash splash splash.img
Yes, run it unlocked and rooted. That's optimal.
The current way to root should be fine for the life of the phone. Root tool v4 should be finer, actually. Use it instead. It's easier. No root is broken that I'm aware of.
To get an OTA, you will need to relock and ruu, plain and simple. It's always been that way. I don't know if s-off will affect that or not.
***I actually misspoke there...what I meant was the current version of sunshine wasn't working on the latest firmware (not our phone I don't think) and they were going to release a new version shortly.
That fastboot command you gave me...do I need to put a specific splash img in my fast boot folder or does just typing that in fast boot get it done?
Click to expand...
Click to collapse
You have to have a specific splash screen. So, someone with a stock one can pull theirs hopefully and we can reflash that.