hello I want to use this guide :
http://forum.xda-developers.com/att-htc-one-m8/general/lolipop-ruu-htc-att-m8-t3075854
I have two questions,
1: I have an att device but I am not on att network, im in Israel, I will be able to keep it this way?
2: I booted into Hboot - up its written locked and s-on, I will only need to connect the device and run the exe file?
1) Your phone will still be SIM unlocked, if that is what you mean.
2) Correct.
Related
Hi guys, i recently got a legend with hboot 1.01.0000 and s-on. From what i understand after looking through the forum, s-on shows that the phone is "attached" to a certain wireless carrier and is only compatible with that carrier's SIM card, and that hboot 1.01 can't be reversed and thus can't be s-off except with xta clip or an unlock code.
However, just out of my curiosity, i borrowed my cousin's active t-mobile SIM card (prepared) and plugged into my htc...here the strange part, instead of having "no-signal/service," the phone was getting t-mobile services and I was able to make calls & texts! So can anyone tell me why is that because i want to understand the situation before i run off to get a t-mobile or at&t SIM card for it seems to work even with s-on.
Thanks!
(The phone was previously using SIM card from Taiwan mobile if thats any help.)
PSHSU said:
... s-on shows that the phone is "attached" to a certain wireless carrier and is only compatible with that carrier's SIM card ... can't be s-off
Click to expand...
Click to collapse
No, that is not correct. S-ON just means that you do not have write access to system partition even on a rooted device. That is the default state of all HTC devices. Not to be mixed up with a sim-lock as you wrote above.
In case you want to get rid of the write protection, you can easily update the bootloader via HTCdev. Once updated, bootloader can be unlocked so that you can get write access to system partition. That's comparable to S-OFF (even if it is not the same, as it does not allow e.g. to remove sim-locks).
Hope that helped.
(SOLVED)
Im in stock 4.1.2 whit S-OFF, unlocked bootloader (1.55) and then RELOCKED.
¿Can i take the last OTA?
Im not rooted, and i dont have custom recoverys (i recently flashed a RUU.zip to return to stock, but i could not remove the S-OFF and RELOCKED status because the hboot 1.55).
I have economic (health) problems and I'll really need to sell my phone, but I'm afraid that the new owner will come out error when trying to update.
conquesoextra said:
Im in stock 4.1.2 whit S-OFF, unlocked bootloader (1.55) and then RELOCKED.
¿Can i take the last OTA?
Im not rooted, and i dont have custom recoverys (i recently flashed a RUU.zip to return to stock, but i could not remove the S-OFF and RELOCKED status because the hboot 1.55).
I have economic (health) problems and I'll really need to sell my phone, but I'm afraid that the new owner will come out error when trying to update.
Click to expand...
Click to collapse
Yes. You can get OTAs while S-OFF. And assuming you haven't unlocked the bootloader since flashing the RUU, all the system files it verifies should be in place to accept OTAs. However, considering you are currently on 4.1.2, you'll need to run through a progression of OTAs to get up to the latest version, 4.4.2 w/ Sense 6. Might be better to just run the latest RUU to bring it up to 4.4.2 w/ Sense 5.5 then OTA to Sense 6. Be aware that you'll need to be on the AT&T network in order to get the updates OTA. If you're not on AT&T, you'll need to flash the updates manually, in which case you'll need to be S_OFF.
Also, once the phone is S-OFF there is no good reason to change that back to S-ON. There's the potential of bricking the phone by doing so. And even if it doesn't brick, the updates in firmware may make it more difficult to obtain S-OFF again.
Thank you very much.
At the begining i did this:
1- Unlocked bootloader and flashed TWRP.
2- Root
3- Gained S-Off
When i decide to sell it i did this:
1- Removed xposed and root.
2 - Relocked bootloader.
3 - Flashed RUU.zip (4.1.2)
¿What do you mean whit AT&T network? I unlocked the phone vía imei (using it in mexico whit Telcel) and still have the update appearing.
Sorry for my terrible english
conquesoextra said:
Thank you very much.
At the begining i did this:
1- Unlocked bootloader and flashed TWRP.
2- Root
3- Gained S-Off
When i decide to sell it i did this:
1- Removed xposed and root.
2 - Relocked bootloader.
3 - Flashed RUU.zip (4.1.2)
¿What do you mean whit AT&T network? I unlocked the phone vía imei (using it in mexico whit Telcel) and still have the update appearing.
Sorry for my terrible english
Click to expand...
Click to collapse
First off, since you are S-OFF there is no need to relock the bootloader in order to flash an RUU. It will run just fine with an unlocked bootloader. Also when you flash an RUU, all the partitions get wiped so there is no need to do anything within the ROM such as remove xposed & root prior to flashing. The RUU will set the device essentially in a factory state.
As far as I understand it, the OTAs for carrier specific devices are served up by the carrier. So if the phone has been SIM unlocked and is being used on another network, if you go into Settings>AT&T software update, it will not receive any available OTA update. You will need to flash the update file manually using the information in this thread, http://forum.xda-developers.com/showthread.php?t=2659374.
Since you are still on 4.1.2, you will need to run one of the recent RUUs in order to manually flash the OTA updates in that thread. The latest RUU available for AT&T devices is KK4.4.2 w/Sense 5.5.
http://androidruu.com/getdownload.p...09_10.26.1718.01L_release_356565_signed_2.exe
Flash that then you can manually flash the OTA update to get Sense 6.
You are the man.
THANK YOU SO MUCH!
I have an at&t branded phone. I recently switched to T-Mobile and would like to get T-Mobile ROM installed on it.
I started with a phone which was NOT rooted, had stock AT&T rom.
I have done the following so far:
*
Unlocked my boot loader - worked flawlessly
Installed TWRP - worked flawlessy
Attempted to install Super SU - I think it worked
Attempted to install a T-Mobile ROM - Getting a "Error flashing zip" error
I download official T-Mobile ROM installer from HTC website. I let the installer run until I saw "Rom.zip" in the temp folder.
A website on google told me that i can use this file to flash my phone. I did have some doubts about this file as I am able to unzip only half the file's contents using winrar. But anyways, I went ahead and used this ROM file.
I rebooted my phone in Recovery mode (TWRP). I clicked on Install and selected rom.zip from my SD Card. When I attempt to install rom.zip, I received following messages:
Installing '/external_sd/tmobile_rom.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip 'external_sd/tmobile_rom.zip'
Updating partition details...
....done
I tried a few different ROM's I found on the internet with the same error message.
So now I am stuck with no OS on the phone. I can only go to bootloader or TWRP.
If someone can suggest a more appropriate ROM file, I can give that a try.
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
I have s-on. Yes, I want the full T-Mobile firmware...mixing up my terms as I am new to this.
Since I don't have an OS right now, I will first try to restore to AT&T firmware by using the stock RUU on htc website. If that's successful, I will proceed with rest of the steps.
redpoint73 said:
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
Click to expand...
Click to collapse
So I was able to get back to AT&T firmware using below steps:
booted my phone to boot fastboot mode
I re-locked my bootloader using following command: fastboot oem lock
I download the AT&T HTC One M8 Stock RUU
Ran the installation until my firmware was flashed again
I am just so happy to have a phone that works now. I will continue soon with the rest of your instructions to get T-Mobile firmware.
redpoint73 said:
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
Click to expand...
Click to collapse
After spending few hours, I have successfully installed T-Mobile firmware on my AT&T M8.
I pretty much followed your instructions. For anyone else looking to this this, here are the complete instructions.
Unlocked boot loader
Installed TWRP recovery
Installed Super User
Changed to T-Mobile CID
Changed to T-Mobile MID
Used sunshine to get Security Off (paid $25)
Ran official HTC M8 T-Mobile RUU
And now I am enjoying a beer
Thanks redpoint73 for your helpful reply.
deepak528 said:
Unlocked boot loader
Installed TWRP recovery
Installed Super User
Changed to T-Mobile CID
Changed to T-Mobile MID
Used sunshine to get Security Off (paid $25)
Ran official HTC M8 T-Mobile RUU
Click to expand...
Click to collapse
I think this is slightly out of sequence. You need to s-off before changing CID and MID. CID and MID cannot be modified with s-on.
wouldnt a simple rom without the firmware provide wifi calling?
PunishedSnake said:
wouldnt a simple rom without the firmware provide wifi calling?
Click to expand...
Click to collapse
Yes. But this thread is from last May, when I think having the 3G AWS band was more of an issue than it is now.
redpoint73 said:
Yes. But this thread is from last May, when I think having the 3G AWS band was more of an issue than it is now.
Click to expand...
Click to collapse
Agreed
anyone know how to get this phone off alltel and on any other carrier? I have the bootloader unlocked, twrp and root. I cant get it to accept any other networl. this is the cdma version. I cant even get into diagnostic mode to connect to dfs. HELP
You will need to unlock it. Go to your carrier, and ask them to unlock it for you. Don't try unlocking it yourself, as it is illegal.
Unlocked bootloader: Allows you to flash custom ROMS and custom recovery.
Unlocked phone: Allows you to use your phone with any carrier.
ok i have a htc one M8 AT&T i have 4.4.4 android o.s. its rooted and unlocked (network).
I just need some help ive tried to update it with ruu but i get a connection error 170 and when i turn my phone off and boot to fast boot usb it verifys info on my device and starts to update but never gets passed 1/7 update signatures
also another thing id like help with is my m8 is AT&T but if i could id like to flash it(if thats correct termi) to a tmobile rom because i have tmobile also for mms capabilities please someone help and be as thorough as possible im not stpid but i cant follow steps if you skip something
Is your bootloader locked or unlocked? Is S-on or S-off?
troysyx said:
Is your bootloader locked or unlocked? Is S-on or S-off?
Click to expand...
Click to collapse
boot loader is unlocked but tampered and s-on
Have you verified the CID is correct?
sniper7777777 said:
boot loader is unlocked but tampered and s-on
Click to expand...
Click to collapse
RUU you alway fail with an unlocked bootloader.
You need to relock the bootloader with fastboot command: fastboot oem lock
---------- Post added at 10:14 AM ---------- Previous post was at 10:10 AM ----------
sniper7777777 said:
also another thing id like help with is my m8 is AT&T but if i could id like to flash it(if thats correct termi) to a tmobile rom because i have tmobile also for mms capabilities please someone help and be as thorough as possible im not stpid but i cant follow steps if you skip something
Click to expand...
Click to collapse
Those statements don't tell me what you actually want to do. You should be able to get MMS working on T-Mobile by one of the following:
1) Enter the proper T-Mob APN. Although I think I might recall that some folks still have trouble with MMS on T-Mob using the AT&T version M8, even when the correct APN is used (so that may be what you are talking about).
2) Flash a custom ROM that specifically supports the T-Mob network.
3) "Fully convert" your phone to the T-Mob version. This may be the most desirable option, as it allows you to get future OTA updates for the T-Mob version, ensures the best compatibility with T-Mobs network. In order to fully convert, you need s-off (by sunshine), and to change the CID and MID. The following thread describes the process. But you only have to do steps 1 and 2 (change to T-Mob CID and MID) and after that you can flash the latest T-Mob RUU: http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567