Related
Telstra in Australia have re-branded this phone. I am wondering if it is unlockable and supports HTC A9 ROMs? is anyone using it?
https://www.telstra.com.au/mobile-phones/mobiles-on-a-plan/telstra-signature-premium
syl0n said:
Telstra in Australia have re-branded this phone. I am wondering if it is unlockable and supports HTC A9 ROMs? is anyone using it?
https://www.telstra.com.au/mobile-phones/mobiles-on-a-plan/telstra-signature-premium
Click to expand...
Click to collapse
Boot into download mode and Run the fastboot command : "fastboot getvar all" or
"fastboot oem getvar all"
Paste results in this thread.
I haven't bought the phone yet. Wanted to ask first before buying.
syl0n said:
I haven't bought the phone yet. Wanted to ask first before buying.
Click to expand...
Click to collapse
Can you go into the store? Look at the bottom of the phone and tell us what the model no. Is.
The_scam said:
Can you go into the store? Look at the bottom of the phone and tell us what the model no. Is.
Click to expand...
Click to collapse
77HD2500-06M Rev A.
Band support looks same as International http://i.imgur.com/wz8DvyD.jpg
syl0n said:
77HD2500-06M Rev A.
Band support looks same as International http://i.imgur.com/wz8DvyD.jpg
Click to expand...
Click to collapse
Sorry, as the model is not the same, I would not risk buying a phone which doesn't support the ROM you deserve. Can you get it somewhere else as an a9?
I believe that you can buy it from htc's website. If your looking for installments/monthly payments. They offer PayPal's installment program
syl0n said:
77HD2500-06M Rev A.
Band support looks same as International http://i.imgur.com/wz8DvyD.jpg
Click to expand...
Click to collapse
Technically speaking, the phone is considered the HTC One A9s, model 2PQ9100, FCCID NM82PQ9100. The hardware is identical to any other A9 UHL variant.
IF the phone can be can be rooted, I'm pretty certain that you'll be able to s-off with Sunshine and do a full conversion. Maybe @jcase knows more.
CSnowRules said:
Technically speaking, the phone is considered the HTC One A9s, model 2PQ9100, FCCID NM82PQ9100. The hardware is identical to any other A9 UHL variant.
IF the phone can be can be rooted, I'm pretty certain that you'll be able to s-off with Sunshine and do a full conversion. Maybe @jcase knows more.
Click to expand...
Click to collapse
Never heard of it, what CPU does it have?
jcase said:
Never heard of it, what CPU does it have?
Click to expand...
Click to collapse
MSM8952, it's a rebadged HIA_AERO_UHL.
CSnowRules said:
MSM8952, it's a rebadged HIA_AERO_UHL.
Click to expand...
Click to collapse
yeah if htcdev.com doesnt work, sunshine could do it if root was achieved
CSnowRules said:
MSM8952, it's a rebadged HIA_AERO_UHL.
Click to expand...
Click to collapse
jcase said:
yeah if htcdev.com doesnt work, sunshine could do it if root was achieved
Click to expand...
Click to collapse
Even if you couldn't flash cm13, it would definitely be able to run Supersu, as it is obviously some variation of hiae, you could flash TWRP.
The_scam said:
Even if you couldn't flash cm13, it would definitely be able to run Supersu, as it is obviously some variation of hiae, you could flash TWRP.
Click to expand...
Click to collapse
Here's the catch...
Unlock bootloader>flash TWRP>install SuperSU>use Sunshine to s-off ---the device could then (in theory) be converted to the desired A9 MID/CID, and be like any other non-Sprint A9
OR
(Somehow) get root with locked bootloader>Sunshine bootloader unlock and s-off ---same result
If the bootloader can't be unlocked, and there's no way to root otherwise, then the device will be locked down tight until a root exploit is achieved.
CSnowRules said:
Here's the catch...
Unlock bootloader>flash TWRP>install SuperSU>use Sunshine to s-off ---the device could then (in theory) be converted to the desired A9 MID/CID, and be like any other non-Sprint A9
OR
(Somehow) get root with locked bootloader>Sunshine bootloader unlock and s-off ---same result
If the bootloader can't be unlocked, and there's no way to root otherwise, then the device will be locked down tight until a root exploit is achieved.
Click to expand...
Click to collapse
It should still be able to be unlocked, it is solely based off a model number.
The_scam said:
It should still be able to be unlocked, it is solely based off a model number.
Click to expand...
Click to collapse
That's true, unless the carrier has prohibited unlocking and/or htcdev doesn't support this carrier branded variant, which is possible. There's just no way to know without additional information.
I wonder if there's a RUU for this device...
CSnowRules said:
That's true, unless the carrier has prohibited unlocking and/or htcdev doesn't support this carrier branded variant, which is possible. There's just no way to know without additional information.
I wonder if there's a RUU for this device...
Click to expand...
Click to collapse
I would go for it, you can always return it if it doesn't work.
I have this device and its rootable also have Oct update too. do not much different from unlock device.
anunknwon said:
I have this device and its rootable also have Oct update too. do not much different from unlock device.
Click to expand...
Click to collapse
Awesome! That means that a full conversion to unlocked should be possible. Are you going to have the first known converted Signature Premium?
Haha thanks I think. The difference here when I flash recovery and unlock I needed to go to bootloader mode not in download mode. (similar to another device)
My phone full root now. And well function. About conversion? Maybe if this model no longer receiving updated (I mean unlocked device)
anunknwon said:
Haha thanks I think. The difference here when I flash recovery and unlock I needed to go to bootloader mode not in download mode. (similar to another device)
My phone full root now. And well function. About conversion? Maybe if this model no longer receiving updated (I mean unlocked device)
Click to expand...
Click to collapse
It's pretty strange that fastboot is implemented differently than with the A9. It would be logical for the Telstra to share a similar firmware base.
Do you mind posting the output of fastboot getvar all and cat /proc/emmc? (remove your IMEI of course)
CSnowRules said:
It's pretty strange that fastboot is implemented differently than with the A9. It would be logical for the Telstra to share a similar firmware base.
Do you mind posting the output of fastboot getvar all and cat /proc/emmc? (remove your IMEI of course)
Click to expand...
Click to collapse
Here hope you can help for future dev :fingers-crossed:
I'm in a Verizon pixel and installed "v" version instead of "u" everything is working. What's different about the international version?
Just a fix for European carriers. I'm using the same on Verizon as well with no issues. You're good.
Nick_Gl said:
I'm in a Verizon pixel and installed "v" version instead of "u" everything is working. What's different about the international version?
Click to expand...
Click to collapse
Nothing it will work just fine. From what I understand just a slight difference for Europe. It will be fine.
What I'd like to know is if I were completely stock on V, bootloader relocked, what updates would I get, if any? Would I get the next version for Europe, or would it be the other? I'm in the US on Verizon (device from Google).
jesssiii said:
What I'd like to know is if I were completely stock on V, bootloader relocked, what updates would I get, if any? Would I get the next version for Europe, or would it be the other? I'm in the US on Verizon (device from Google).
Click to expand...
Click to collapse
You probably wouldn't get any updates. The trigger for that version probably wouldn't get to you. But I am not certain on that. Might be able to pull it via wifi with no SIM in it.
Do NOT relock your bootloader unless it is just before you are going to put it in a box to send back for warranty.
jesssiii said:
What I'd like to know is if I were completely stock on V, bootloader relocked, what updates would I get, if any? Would I get the next version for Europe, or would it be the other? I'm in the US on Verizon (device from Google).
Click to expand...
Click to collapse
Why would you think you'd get the European version if you are in the US? Did I miss something in your question? You'd get the U version if you're on Verizon and you can lock and relock the bootloader at your discretion since you have the Google Pixel. I mean if you want to keep wiping your data each time, that is.
bobby janow said:
Why would you think you'd get the European version if you are in the US? Did I miss something in your question? You'd get the U version if you're on Verizon and you can lock and relock the bootloader at your discretion since you have the Google Pixel. I mean if you want to keep wiping your data each time, that is.
Click to expand...
Click to collapse
He made it sound like his pixel is from Verizon. In that case he can't lock and unlock the bootloader whenever he wants.
To the OP. What are you trying to do? It doesn't matter if you are on V. If it makes you feel better just flash U then. As long as you don't have twrp or root you will still get OTAs. Why would you want to lock your bootloader? You can have an unlocked bootloader and still take normal OTAs just fine . it its a Verizon sold pixel you won't be able to unlock once you lock.
fritzgerald said:
Just a fix for European carriers. I'm using the same on Verizon as well with no issues. You're good.
Click to expand...
Click to collapse
Thanks wasn't sure. I'll just remember to side load the correct one in February.
aholeinthewor1d said:
He made it sound like his pixel is from Verizon. <snip>
Click to expand...
Click to collapse
It was certainly a little bit confusing, however, the last part of his post it said.. (device from Google) so I figured it was a GPixel activated on Verizon.
Hello guys.
I'm going to buy used and bootloader unlocked Verizon Pixel tomorrow and I'm interested in couple of things:
1. Can I flash all the ROMs that are available for Pixel on Verizon version too?
2. Can I properly install TWRP, root using Magisk, etc?
3. Can I properly flash (and downgrade if needed) official system images (and are they ever available for Verizon models?)
4. Can I take part in Android Beta program?
5. Is there anything I should be afraid of?
Thanks in advance.
Make sure it is bootloader unlocked, and not just SIM unlocked. There are not many VZ ones around that are bootloader unlocked. You need that to do the items on you list.
TonikJDK said:
Make sure it is bootloader unlocked, and not just SIM unlocked. There are not many VZ ones around that area bootloader unlocked. You need that to do the items on you list.
Click to expand...
Click to collapse
As I already stated, bootloader is already unlocked.
No one has an answer?
If it's bootloader u locked then yeah u can do all those things. Just do not ever for any reason ever relock the bootloader. Also I believe there have been a few cases where ppl have had semibricks or other issues which required locked stock to fix or somehow resulted in locked stock
I got a replacement about a month ago on my small Pixel and that one was unlocked. However, the one I got from Verizon in store did not have an unlocked bootloader. I'm not sure what the deal is, but maybe getting a replacement from an "accidental" break might do the trick. just to clarify, my first Pixels' usb port got completely fried and started to smell bad whenever it charged, and the phone would get really hot. I am now on 8.1 with an unlocked bootloader but have yet to actually root the phone
KittyRgnarok said:
If it's bootloader u locked then yeah u can do all those things. Just do not ever for any reason ever relock the bootloader. Also I believe there have been a few cases where ppl have had semibricks or other issues which required locked stock to fix or somehow resulted in locked stock
Click to expand...
Click to collapse
Thank you!
gb_14 said:
Thank you!
Click to expand...
Click to collapse
Np
I've been looking for a google purchased Pixel XL 128GB locally for a little while now and I've come across a verizon version that was unlocked when they were first released and is now updated to the latest OS.
Since the bootloader is unlocked is there any difference now between the verizon version and the google purchased version? Any chance to revert back on updated or once the bootloader is loaded it is good to go and nothing to worry about from that point forward?
Thanks for any input on this. I've searched, but couldn't find anything regarding this topic.
live4soccer7 said:
I've been looking for a google purchased Pixel XL 128GB locally for a little while now and I've come across a verizon version that was unlocked when they were first released and is now updated to the latest OS.
Since the bootloader is unlocked is there any difference now between the verizon version and the google purchased version? Any chance to revert back on updated or once the bootloader is loaded it is good to go and nothing to worry about from that point forward?
Thanks for any input on this. I've searched, but couldn't find anything regarding this topic.
Click to expand...
Click to collapse
Nothing to worry about going forward except on thing. If YOU relock it you won't be able to unlock it again. They won't relock it.
TonikJDK said:
Nothing to worry about going forward except on thing. If YOU relock it you won't be able to unlock it again. They won't relock it.
Click to expand...
Click to collapse
Thanks! Is there a failsafe I could add in so that it WON'T LET ME LOCK IT?
live4soccer7 said:
Thanks! Is there a failsafe I could add in so that it WON'T LET ME LOCK IT?
Click to expand...
Click to collapse
It requires a manual command in fastboot. Doubt you'll do that accidently.
you definitely dont need a failsafe to avoid relocking it as its really not something you can do accidentally. since you are getting an unlocked version i also assume you will be loading custom firmware in which case it is common sense not to relock it or you will literally brick the phone anyways
KittyRgnarok said:
you definitely dont need a failsafe to avoid relocking it as its really not something you can do accidentally. since you are getting an unlocked version i also assume you will be loading custom firmware in which case it is common sense not to relock it or you will literally brick the phone anyways
Click to expand...
Click to collapse
Thanks everyone, that's exactly what I was looking for. I'm curious, what happens if I toggle the OEM unlock option on/off?
live4soccer7 said:
I'm curious, what happens if I toggle the OEM unlock option on/off?
Click to expand...
Click to collapse
That switch has been grayed out after the Verizon unlock, and it reads "Bootloader is already unlocked", so as far as I know it's not possible to toggle.
Thanks! Much appreciated.
Enjoy your Pixel and happy modding mate
First of all:
I'm no Dev...just someone who likes to play lego.
From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk.
I've read a good startup here.
Hopefully this makes this thread clear enough so that i dont need to describe the whole procedure step by step.
(https://www.naldotech.com/root-samsung-galaxy-z-flip-3-5g-magisk/)
(1.OEM-Unlock,2.BL-Unlock,3.extract boot.img,4.patch boot.img via magisk on the unrooted mobile,5.patch boot.img.tar to AP&BL via Odin, 6.pray)
Anyways...here are maybe small hints to avoid a few traps.
a) Just do the oem-unlock in the dev-options (enabled by tapping buildnumber 5 times) is just half of the rent.
Afterwards i had to go in Download-mode (switch of mobile, press volUp+volDown and connect PC-cable.)
There appears a possibility of choice.
Press VolUp short: get the mobile on standby to flash the rom via odin.
Press VolUp LOONG: get the mobile to the menu where the bootloader can finally get unlocked. (Otherwhise every try to patch a rooted img will be blocked by bootloader-protection.)
Of course this can possibly be done via adb/fastboot commands.
Funny side note: OEM-Unlock-option will completely disappear from Dev-options and waranty is lost. Also the mobile stops to get Updates OTA which means that you have to update manually whenever a new version will appear in the net.
b) patching boot.img via magisk should work as described in many other magisk-rooting-manuals.
Flashing the tar back to the mobile via odin was little bit tricky.
It doesnt reach out just to provide the magisk_patched.tar to Odin just on the AB-line.
I had to patch it to BL too.
Cheers
MikGx
When you boot into bootloader after unlocking, is the message something about "a custom OS can cause critical problems"?
As it stands now, the only reason I have to believe the US bootloader can't be unlocked (or isn't already) was the lack of an OEM unlock button and some cranky kid on the internet saying it hasn't been possible since the S7.
It doesn't make sense why I would have a warning about a custom OS if there is no possible way to install one, though.
@boot into bootloader after unlocking it...:
Yess you are right. Thats exactly the message.
Then you can enter the Device unlock mode again (long press VolUp) to lock bootloader again (then it resets automaticaly to factory-defaults and all work is gone.)
or
continue to flash something (short press VolUp).
Dont know about the US versions. Could be that there is a difference to my EU-models.
But either i rooted nearly every every mobile since the S2
MikGx said:
@boot into bootloader after unlocking it...:
Yess you are right. Thats exactly the message.
Then you can enter the Device unlock mode again (long press VolUp) to lock bootloader again (then it resets automaticaly to factory-defaults and all work is gone.)
or
continue to flash something (short press VolUp).
Dont know about the US versions. Could be that there is a difference to my EU-models.
But either i rooted nearly every every mobile since the S2
Click to expand...
Click to collapse
I think you misunderstood what I was asking, but ended up answering it anyway.
It seems the message about installing custom OS versions may be a boilerplate for the bootloader, not any indication that it's possible.
naldotech.com, the link you provide is pretty clear about the process. What it doesnt say is what to do at the end. When you untick "reboot" in odin, and you finish flashing, your phone will stay in download mode. Then what to do?. Press power and volume down to leave and restart the phone? or, power and volume down, screen goes black imediately power and volume up, enter recovery and restart from there.? please someone ?
Press the power and volume down buttons for about 7 seconds and it will reboot
beanbean50 said:
Press the power and volume down buttons for about 7 seconds and it will reboot
Click to expand...
Click to collapse
I did as you mention but it didnt work. It made me reset the system. But I Fallowed the naldotech.com guide. At the end, being in dawnload mode, I pressed power and volume down, when the screen got black I pressed power and volumen up, I entered recovery mod, cleared cache and re- started the system: Voila my phone is rooted
Hello.
Can someone pleas provide a working link for frija download? The one referring from naldotech seems to be broken (https://www.naldotech.com/download-samsung-galaxy-stock-firmware-frija-tool/)
Update: Found a link via google -> https://technastic.com/odin-download-samsung-latest-all-versions/
twistedumbrella said:
When you boot into bootloader after unlocking, is the message something about "a custom OS can cause critical problems"?
As it stands now, the only reason I have to believe the US bootloader can't be unlocked (or isn't already) was the lack of an OEM unlock button and some cranky kid on the internet saying it hasn't been possible since the S7.
It doesn't make sense why I would have a warning about a custom OS if there is no possible way to install one, though.
Click to expand...
Click to collapse
The USA version (snapdragon soc) can't be rooted as far as I know. There is no way to unlock the bootloader in dev options, at least on Verizon and that holds true even if you bought a unlocked phone. As soon as you insert a Verizon sim and the phone updates it's all over.
I had the same issue with the original Pixel. I bought it unlocked but before rooting it I allowed it to update like a fool. Luckily my son wanted the same phone so I gave him mine then rooted and installed TWRP before putting a Verizon sim in.
Back to Samsung...as far as I know you haven't been able to root the USA version since the note 8. The rest of the planet gets the Exynos SOC but we get the snapdragon and no root method works. My note 9, 10+ and z Flip3 didn't have an unlock bootloader option even before putting a sim in it.
d0x360 said:
The USA version (snapdragon soc) can't be rooted as far as I know. There is no way to unlock the bootloader in dev options, at least on Verizon and that holds true even if you bought a unlocked phone. As soon as you insert a Verizon sim and the phone updates it's all over.
I had the same issue with the original Pixel. I bought it unlocked but before rooting it I allowed it to update like a fool. Luckily my son wanted the same phone so I gave him mine then rooted and installed TWRP before putting a Verizon sim in.
Back to Samsung...as far as I know you haven't been able to root the USA version since the note 8. The rest of the planet gets the Exynos SOC but we get the snapdragon and no root method works. My note 9, 10+ and z Flip3 didn't have an unlock bootloader option even before putting a sim in it.
Click to expand...
Click to collapse
twistedumbrella said:
I think you misunderstood what I was asking, but ended up answering it anyway.
It seems the message about installing custom OS versions may be a boilerplate for the bootloader, not any indication that it's possible.
Click to expand...
Click to collapse
I have to be a little skeptical when my rooted Note 8 came out a year after the S7. There are other reasons, but they tend to make the trolls restless. We'll skip them.
twistedumbrella said:
I have to be a little skeptical when my rooted Note 8 came out a year after the S7. There are other reasons, but they tend to make the trolls restless. We'll skip them.
Click to expand...
Click to collapse
Ok I might be off by a year or 2 but I can say with 100% certainty that the note 9, 10, 10+ and flip3 don't have an unlock bootloader option.
I bought all 4 from Samsung all unlocked and not tied to any carrier. First boot with no sim I checked dev options and there was no option to unlock the bootloader. My note 9 might have had the option in the menu but it was grayed out and I couldn't find anyway to make it work.
A quick Google search for rooting the snapdragon version of any of these devices essentially says "NOPE".
The only way to root one is to buy a non US version. If it has a snapdragon soc you're out of luck.
d0x360 said:
Ok I might be off by a year or 2 but I can say with 100% certainty that the note 9, 10, 10+ and flip3 don't have an unlock bootloader option.
I bought all 4 from Samsung all unlocked and not tied to any carrier. First boot with no sim I checked dev options and there was no option to unlock the bootloader. My note 9 might have had the option in the menu but it was grayed out and I couldn't find anyway to make it work.
A quick Google search for rooting the snapdragon version of any of these devices essentially says "NOPE".
The only way to root one is to buy a non US version. If it has a snapdragon soc you're out of luck.
Click to expand...
Click to collapse
You got where I said "I guess the disclaimer is misleading" right?
twistedumbrella said:
You got where I said "I guess the disclaimer is misleading" right?
Click to expand...
Click to collapse
I didn't see that sentence in any of the posts but perhaps I just missed it.
It doesn't change anything either way. Anything is possible, even you somehow getting a device with this setting. That being said you also seem to be the only person ever to receive a USA device with said option.
It's hard to believe because it would mean the wrong firmware was installed (which makes no sense in itself) but with that firmware the device should have been a brick. The soc is completely different. It would be somewhat like trying to use Nvidia drivers on an AMD GPU... It just wouldn't work.
I dunno... I don't disbelieve you but I don't believe you either. It's just so far fetched for many reasons
d0x360 said:
I didn't see that sentence in any of the posts but perhaps I just missed it.
It doesn't change anything either way. Anything is possible, even you somehow getting a device with this setting. That being said you also seem to be the only person ever to receive a USA device with said option.
It's hard to believe because it would mean the wrong firmware was installed (which makes no sense in itself) but with that firmware the device should have been a brick. The soc is completely different. It would be somewhat like trying to use Nvidia drivers on an AMD GPU... It just wouldn't work.
I dunno... I don't disbelieve you but I don't believe you either. It's just so far fetched for many reasons
Click to expand...
Click to collapse
Lucky? I dunno. Had I known it would cause this much trolling, I wouldn't have bothered to mention it.
I have a general question. I am unfamiliar with rooting/unlocking bootloader on Samsung devices. Is it possible to revert unlocking the bootloader and going back to stock traceless?
david.siebauer said:
I have a general question. I am unfamiliar with rooting/unlocking bootloader on Samsung devices. Is it possible to revert unlocking the bootloader and going back to stock traceless?
Click to expand...
Click to collapse
Partially. I just did that: I have AfWall running on my old phone, tried to unlock the Flip with this manual here in order to use the firewall there, did something wrong - and stumbled upon Netguard while searching what might have happened and decided to give it a try first. (Unless there is a custom ROM for the phone available, I have no other need for root or an unlocked bootloader.)
From what I could find on my Flip 3, you can unlock and relock the bootloader as you like - but as soon as you install a non-genuine bootloader (i.e. one chnaged by Magisk) you will trip Knox - and this cannot be reverted.
In such a case you can still re-lock your bootloader and unlock it later (on my phone, that "7-day-no-switch-indeveloper-options" routine kicked in, but you can circumvent that) - but Knox will stay in its state. From what I read this means some things will not work such as Samsung Pay, but I do not know the details (yet) apart from that it does not bother me ;-), and the nag screen during boot is gone.
Thanks for your reply. Kinda sucks. Never had problems with my former mobiles to get back totally to stock without traces. Guess I disregard rooting for now
david.siebauer said:
Thanks for your reply. Kinda sucks. Never had problems with my former mobiles to get back totally to stock without traces. Guess I disregard rooting for now
Click to expand...
Click to collapse
Well, it's better than my Sony - there it is "once unlocked, always unlocked" with no way back at all
But I have to admit I understand the logic why the manufacturers do that, at least to the degree that they trip a fuse as Samsung does.
By rooting the phone, you shift the responsibility for the software state of the phone from the manufacturer to the user, so I think it is okay to implement something to make it clear to possible future buyers that it is or has been in that state.
(This does not include however all the other stones they put in the way of people wanting to develop or use custom ROMs!)
I remember I also had a Xperia Z3 compact.
Main reason for me for rooting, is the ability to use tools like tasker without non root restrictions or just trying customs roms without bloat, but usefull features. Guess u shouldn't have bought a Samsung lol.
david.siebauer said:
I remember I also had a Xperia Z3 compact.
Main reason for me for rooting, is the ability to use tools like tasker without non root restrictions or just trying customs roms without bloat, but usefull features.
Click to expand...
Click to collapse
Oh, trust me - as soon as I hear there is a custom ROM that works as a daily driver I will root mine as well. I really hope that there will be one for this phone
david.siebauer said:
Guess u shouldn't have bought a Samsung lol.
Click to expand...
Click to collapse
Sadly there is no Fairphone mini or Fairphone Flip - or would it be Fairfliphone? ... Flipfairphone?... - yet (if ever), so the only current alternative would be Motorola. And the price tag for the Razr is simply too much, even if I personally think it looks better than the Samsung. Additionally, I do not know if they are in any way better when it comes to rooting or loading custom ROMs.