Hi,I want to install custom rom. (like most people) but, With htc one m7 I used the warranty, so, I want to be able to use it with the M8. My question is. to return full stock, its need s off right? Right now I cant afford 25 for the soff (in my country, outside of USA is a little more difficult because the conversion). So, if I use the dev unlock bootloader, Can I install custom any rom ( i ask because I dont know where I saw custom rom requiring S-OFF) and then do the s off after a while (maybe 2 o 3 months). If I use dev unlock from htc, they will be able to track that I install custom roms? And how about bricks, wich side is safest (only unlock bootloader or Soff) and wich side is more easy to recover?.
Thanks in advance
lorddavid said:
Hi,I want to install custom rom. (like most people) but, With htc one m7 I used the warranty, so, I want to be able to use it with the M8. My question is. to return full stock, its need s off right? Right now I cant afford 25 for the soff (in my country, outside of USA is a little more difficult because the conversion). So, if I use the dev unlock bootloader, Can I install custom any rom ( i ask because I dont know where I saw custom rom requiring S-OFF) and then do the s off after a while (maybe 2 o 3 months). If I use dev unlock from htc, they will be able to track that I install custom roms?
Click to expand...
Click to collapse
HTC will typically not honor a warranty for a device purchased from and intended for another country. However, how HTC handles warranty seems to vary from one location to another. Did you buy the M7 from the US?
Along those lines, how HTC handles bootloader unlocks via HTCDev.com also seems to vary from one country to another. Yes, they can and will track the phones IMEI by HTCDev.com, and know you requested a bootloader unlock code. Some folks have had their warranty claims denied that way. But others are successful returning the phone to bootloader LOCKED (not RELOCKED, s-off required to make it LOCKED after unlocking it), stock software, possibly s-on.
You don't need s-off to flash ROM. But you will want to make sure your firmware is up to date. If the phone is on stock Lollipop, the firmware is probably up to date (especially if the phone was purchased new, not used). Otherwise, s-off makes it a bit easier to update firmware, but its also possible with s-on.
lorddavid said:
And how about bricks, wich side is safest (only unlock bootloader or Soff) and wich side is more easy to recover?.
Click to expand...
Click to collapse
Are you talking about recovering from no-boot conditions? s-off always gives more options. But most cases of no boot are solved by flashing custom recovery again, flashing a ROM, or other functions possible with s-on.
Yes, with M7 I bought it from ATT, and they honor the warranty, but IN USA. I was there in vacation and send it. I'm in kitkat, I didnt update with RUU because dont know if sunshine works on latest firmware. So, even if I unlock with dev unlock. And after that I use S-OFF to make it Locked, they still can track it? In theory is better to go with S-OFF directly?
lorddavid said:
Yes, with M7 I bought it from ATT, and they honor the warranty, but IN USA. I was there in vacation and send it.
Click to expand...
Click to collapse
Based on reports I've seen on XDA, your warranty won't be honored since you are not located in the US. Of course, if you travel back to the US, or send it to a US friend to send in for warranty, that might work.
lorddavid said:
I'm in kitkat, I didnt update with RUU because dont know if sunshine works on latest firmware. So, even if I unlock with dev unlock. And after that I use S-OFF to make it Locked, they still can track it? In theory is better to go with S-OFF directly?
Click to expand...
Click to collapse
Sunshine s-off function still works on Lollipop. However, the root function does not (and root is needed to s-off). Some folks have temp rooted, and able to get s-off to work (then bootloader unlock).
But I would recommend using sunshine to root, s-off then bootloader unlock (bypassing HTCDev.com) all those things with sunshine; while still on KitKat (before RUU to Lollipop), if you are worried about warranty.
lorddavid said:
So, even if I unlock with dev unlock. And after that I use S-OFF to make it Locked, they still can track it?
Click to expand...
Click to collapse
Yes, they can still track it. The bootloader unlock code is based on your IMEI, and they are probably tracking/recording the IMEI numbers that go through HTCDev.com.
I think some folks have been successful making the phone back to LOCKED (and even s-off) and of course also stock software, and getting the warranty honored. But I'd say its no guarantee. Some folks will also say they can't "legally" void your warranty for requesting an unlock bin code (as long as you return to "full" stock) as they can only prove you requested a code, not that you actually used it.
But at that point, its your word against there's. HTC holds the cards here. You can try to fight it, but in the meantime you still don't have a working phone.
To some degree, when we all mod our phones, we have to assume that there is some risk that warranty will be void.
Ok, so I think that I will save mone for S-OFF, better play safe. Just a question, to update firmware I need to RUU? (After S-Off of course) Or can you point me to a guide to flash latest sense and lollipop rom? (I know how to flash recovery, s off, etc. but not sure about the match of firmware or what firmware/radio to use). THanks
lorddavid said:
Ok, so I think that I will save mone for S-OFF, better play safe. Just a question, to update firmware I need to RUU? (After S-Off of course) Or can you point me to a guide to flash latest sense and lollipop rom? (I know how to flash recovery, s off, etc. but not sure about the match of firmware or what firmware/radio to use).
Click to expand...
Click to collapse
You can update firmware (after s-off) with AT&T Lollipop RUU, or by flashing a firmware.zip in fastboot.
Flashing AT&T firmware will keep the same band support. If you want to change the band support, you can flash another version's firmware. But it depends on what bands your carrier uses for 3G and 4G (LTE).
redpoint73 said:
You can update firmware (after s-off) with AT&T Lollipop RUU, or by flashing a firmware.zip in fastboot.
Flashing AT&T firmware will keep the same band support. If you want to change the band support, you can flash another version's firmware. But it depends on what bands your carrier uses for 3G and 4G (LTE).
Click to expand...
Click to collapse
Its more fast to just flash the firmware i think, because I dont need to download all the RUU.
And with the HTC really can change the band support? I think that is something of hardware. But if that can be done I want to try it.
I will search for the Firmware for flash. If I have problems I will ask. Thanks again
EDIT: I'm preparing , found some firmware but cant see from wich carrier are. Are those https://www.androidfilehost.com/?w=files&flid=32780
EDIT 2: I found that the numbers means the region. So, whats the latest firmware? Can I flash it even if my phone is ATT? Because I saw Just 1 for ATT
lorddavid said:
And with the HTC really can change the band support? I think that is something of hardware. But if that can be done I want to try it.
Click to expand...
Click to collapse
You are somewhat correct, in that before the M8, band support was set in hardware on most (or all?) phones.
But a new feature of the Snapdragon 801 chipset, is that band support is set in software. Flashing another CID's firmware will change the band support (may need to change CID and MID, and s-off required to change CID/MID).
lorddavid said:
EDIT: I'm preparing , found some firmware but cant see from wich carrier are. Are those https://www.androidfilehost.com/?w=files&flid=32780
Click to expand...
Click to collapse
AT&T is 502. But that thread only has 1.54.502 (which is same or probably even older than current firmware), and what you want (latest) is 4.28.502.
You can get the 4.28.502 firmware on the following thread, but you have to download the ROM with it (all packed in the same zip):
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Not sure if 4.28.502 firmware is posted by itself anywhere else (I haven't seen so).
redpoint73 said:
You are somewhat correct, in that before the M8, band support was set in hardware on most (or all?) phones.
But a new feature of the Snapdragon 801 chipset, is that band support is set in software. Flashing another CID's firmware will change the band support (may need to change CID and MID, and s-off required to change CID/MID).
AT&T is 502. But that thread only has 1.54.502 (which is same or probably even older than current firmware), and what you want (latest) is 4.28.502.
You can get the 4.28.502 firmware on the following thread, but you have to download the ROM with it (all packed in the same zip):
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Not sure if 4.28.502 firmware is posted by itself anywhere else (I haven't seen so).
Click to expand...
Click to collapse
Thanks, thats new to me. And yes I found under 1540 a more recent firmware. So there is 0 risk of brick flashing other firmware right? I need SuperCID? Or is the same with ATT? (I'm curious for trying because with my phone my 3G speed is capped to 1mb dont know why, and other friends, same plan, other phone, have more speed)
lorddavid said:
Thanks, thats new to me. And yes I found under 1540 a more recent firmware. I need SuperCID? Or is the same with ATT?
Click to expand...
Click to collapse
Pretty sure you need to change your CID either to Dev Edition CID or SuperCID.
lorddavid said:
So there is 0 risk of brick flashing other firmware right?
Click to expand...
Click to collapse
There is never zero brick risk. Your phone can brick just sitting there, doing nothing (very unlikely, but its possible). In particular, flashing hboot (which firmware does) if anything goes wrong (for instance, don't disconnect the phone while its flashing!) while writing hboot, it will brick.
But flashing another CID's firmware is low risk. Probably no more risk than flashing the proper CID firmware, or doing an official RUU or OTA.
Have a carrier unassigned H932. I've managed to unlock the bootloader, but I'm not sure if the TWRP recovery used for other variants will work. Anyone have any idea as to whether it will work?
jt1954 said:
Have a carrier unassigned v932. I've managed to unlock the bootloader, but I'm not sure if the TWRP recovery used for other variants will work. Anyone have an idea as to whether it will work?
Click to expand...
Click to collapse
Ha! You mean a T-Mobile H932? If you can get TWRP to install that is indeed the correct version for all the V30 variants.
How do you plan to install it? You have no fastboot flash commands.
Ease-up. I made a mistake. If it's true than I guess I'm SOL. Thanks for your feedback...
If
jt1954 said:
Ease-up. I made a mistake. If it's true than I guess I'm SOL. Thanks for your feedback...
Click to expand...
Click to collapse
All V30/V30+/V30S variants in the world can be bootloader unlocked and rooted -- except for T-Mobile H932.
Sorry for jumping, it's just there is a prominent 144 page thread on how the H932 can NOT be rooted (yet), and you opened a new thread about rooting it.
https://forum.xda-developers.com/lg-v30/how-to/progress-root-twrp-roms-achieved-t3690577/page144
I hope TWRP can be installed someday and it can be rooted.
Hi I recently bought a new G5 H830 (TMO version) off eBay, accidentally I let it upgrade the software and so now it is H830 20n. (I believe it came with 20m).
I searched and found most posts say this version cannot be rolled back and root.
Is this version still rootable?
Many thanks,
You should try to unlock the bootloader with the official LG method, and if you can unlock the bootloader and then install TWRP, you can also root the phone with SuperSU or Magisk.
T-Mobile H830 should be supported, but you have to check if LG allows bootloader unlocking for your specific IMEI.
tremalnaik said:
You should try to unlock the bootloader with the official LG method, and if you can unlock the bootloader and then install TWRP, you can also root the phone with SuperSU or Magisk.
T-Mobile H830 should be supported, but you have to check if LG allows bootloader unlocking for your specific IMEI.
Click to expand...
Click to collapse
He will be able to unlock the bootloader but he can't flash twrp you have to downgrade to 20a
tremalnaik said:
You should try to unlock the bootloader with the official LG method, and if you can unlock the bootloader and then install TWRP, you can also root the phone with SuperSU or Magisk.
T-Mobile H830 should be supported, but you have to check if LG allows bootloader unlocking for your specific IMEI.
Click to expand...
Click to collapse
H830 variant is not supported by official bootloader unlock.
cheeze.keyk said:
H830 variant is not supported by official bootloader unlock.
Click to expand...
Click to collapse
It should be I unlocked mine and installed linage os
wolf45801 said:
It should be I unlocked mine and installed linage os
Click to expand...
Click to collapse
of course yes using the unofficial one.
cheeze.keyk said:
of course yes using the unofficial one.
Click to expand...
Click to collapse
Not all the H830 have the same possibility to be unlocked. On earlier versions of the bootloader "fastboot oem unlock" was enough, for newer versions, depending on the market (Asia, Europe, phones for exposition in the stores) LG allows or not the unlocking. Have you already tried the official method with your IMEI?
tremalnaik said:
Not all the H830 have the same possibility to be unlocked. On earlier versions of the bootloader "fastboot oem unlock" was enough, for newer versions, depending on the market (Asia, Europe, phones for exposition in the stores) LG allows or not the unlocking. Have you already tried the official method with your IMEI?
Click to expand...
Click to collapse
i dont own a G5 now. I unlocked the bootloader of my previous G5 but its an H830 variant.
cheeze.keyk said:
i dont own a G5 now. I unlocked the bootloader of my previous G5 but its an H830 variant.
Click to expand...
Click to collapse
How did you unlock your phone? I just bought a H830 with Android 8 installed and I am struggling to unlock it...
Anyone aware of an exploit or known good method to sim unlock my AT&T V30 H931?
nofroyo said:
Anyone aware of an exploit or known good method to sim unlock my AT&T V30 H931?
Click to expand...
Click to collapse
Yes. You Frankenstein to carrier unlocked firmware, like US998. There are several North America carrier unlocked variants you can convert to, but US998 also has the necessary fastboot flash commands if you ever want to bootloader unlock and root.
SEE Frankenstein thread.
Sent via open market LG US998 V30/V30+