Related
Hello. I have just received a new G2 (aka Hero) on T-mobile UK.
I am planning on doing this, please can you tell me if this would work:
1.Installing a recovery image
2.Booting into recovery and making a Nandroid backup
3.Installing a generic HTC Rom which has been packed into update.zip NB.Rom is a stock rom and therefore not rooted
As I understand after flashing I would lose rooting and would need to root again if I need to. However, I don't need to so am not too bothered.
I am hoping that this would remove T-Mobile branding, but mainly make the phone quicker as it is running the latest ROM. Would this technique work?
I would also like to know wether my sim-lock status would be affected?
Also if Donut/Android 1.6 is released OTA by HTC would my phone update OTA?
Finally, does that mean once I have flashed it, I will not be able to access the recovery partition thing which includes Nandroid etc.?
Please answer my questions and comment if you have any reservations/concerns about this. All comments are much appreciated.
@baggy111
from what i have researched the steps that you have put down would work. This would remove the t-mobile branding.
again from my research the sim-lock would not be affected. once un-locked the phone is un-locked for good.
the question about OTA i am not sure because apparetnly after de-branding your phone should act as a generic HTC hero so it stands to reason that it would act like one too and update OTA.
no idea about the last one
however, i have not performed these steps myself. what i told you is from what i have read on xda and other sites. i would suggest you take a look at www.theunlockr.com too
Anyone else?
come on people
I just got an Aria via a trade (with an older phone I had - but the person really wanted). I was interested in playing with CM7 and thought this phone would be a decent candidate. I don't know the history of the phone other than "like new" - and it really is like new (not a scratch). I'm wondering if it might be a warranty replacement though, because I cannot root it using the Unrevoked method. I loaded the "driver" and it showed up as an Android Phone without issue. However, it still does not root? The Firmware version is: 2.1-update1. It has HBOOT-0.57.0000 so presumably it's rootable. I found this thread: http://forum.xda-developers.com/showthread.php?t=991557&highlight=HBOOT - but I've never loaded HTC-sync. I do have ADB loaded (use with my Moto Bravo). Could that be an issue? When I ran unrevoked, my Device Manager looked exactly like this: http://www.unrevoked.com/rootwiki/lib/exe/detail.php/public/end.png?id=public%3Awindows_hboot_driver_install. Sorry if this has been addressed. I've been searching here for two days, but found no other things to try?
tboydva said:
I just got an Aria via a trade (with an older phone I had - but the person really wanted). I was interested in playing with CM7 and thought this phone would be a decent candidate. I don't know the history of the phone other than "like new" - and it really is like new (not a scratch). I'm wondering if it might be a warranty replacement though, because I cannot root it using the Unrevoked method. I loaded the "driver" and it showed up as an Android Phone without issue. However, it still does not root? The Firmware version is: 2.1-update1. It has HBOOT-0.57.0000 so presumably it's rootable. I found this thread: http://forum.xda-developers.com/showthread.php?t=991557&highlight=HBOOT - but I've never loaded HTC-sync. I do have ADB loaded (use with my Moto Bravo). Could that be an issue? When I ran unrevoked, my Device Manager looked exactly like this: http://www.unrevoked.com/rootwiki/lib/exe/detail.php/public/end.png?id=public%3Awindows_hboot_driver_install. Sorry if this has been addressed. I've been searching here for two days, but found no other things to try?
Click to expand...
Click to collapse
You need to load HTC Sync because it loads some drivers that are needed. Once you get HTC Sync installed, you can uninstall it but the drivers will remain in place and then Unrevoked will work.
You must install HTC Sync, but then uninstall it. If done correctly you will still have an entry in the Start Menu for HTC Driver.
You also need to install the HBOOT drivers as instructed here: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
If you've done that, you shouldn't have any problems.
Ugh - I guess I didn't see that in any of my searching (just that you MUST uninstall HTC Sync - so I thought great, I'll just never install it). All rooted now! Thanks so much. On to CM7....
So I just got a new moto e 2nd gen just a few days ago.
Currently running 5.0.2.
Hardware SKU XT1511.
As far as I understand the 5.1 OTA came out a few months ago, correct?
But when I go to the system update, it just says "Your device's software is up to date"
What's going on here? Is there a link to download the ota zip so I can just run adb and flash it myself???
Sent from my MotoE2 using XDA Free mobile app
Same thing happening here, but with XT1526 I live in another region, so I don't know if that has anything to do.
For what it's worth, I live in the USA and purchased this device brand new from best buy just a few days ago.
So yeah, not sure what is going on with the update.
This phone is the 3G version, the retail US model that has LTE connectivity is the one with the 5.1 update.
This phone model has been seemingly neglected by Motorola, this thread in the Motorola Forum has info about the updates of the Moto E 2015, no updates at all for the 3G model
I just purchased the XT1527 LTE model off Amazon for $100 for my grandma to use instead of her crappy ZTE flip phone. She is on my aunt's AT&T 60GB plan for her small business and when the phone first arrived, I signed into her Google account and got everything setup but when I tried to pull the 5.1 update, it wasn't getting it yet and said it was already up-to-date with 5.0.2.
Later that day we finally went to the AT&T store to get a SIM put in it and her number transferred over, but still, no 5.1 update for it yet.
Does anyone know why my XT1527 model can't pull the update yet? I thought for sure it would have been able to pull it when I first turned it on, before even getting the SIM for it.
Is there anyway for me to manually install the OTA without unlocking the bootloader or flashing TWRP or are we just stuck waiting?
dabug91 said:
I just purchased the XT1527 LTE model off Amazon for $100 for my grandma to use instead of her crappy ZTE flip phone. She is on my aunt's AT&T 60GB plan for her small business and when the phone first arrived, I signed into her Google account and got everything setup but when I tried to pull the 5.1 update, it wasn't getting it yet and said it was already up-to-date with 5.0.2.
Later that day we finally went to the AT&T store to get a SIM put in it and her number transferred over, but still, no 5.1 update for it yet.
Does anyone know why my XT1527 model can't pull the update yet? I thought for sure it would have been able to pull it when I first turned it on, before even getting the SIM for it.
Is there anyway for me to manually install the OTA without unlocking the bootloader or flashing TWRP or are we just stuck waiting?
Click to expand...
Click to collapse
Same thing here. I'm not getting 5.1 or any other update. XT1527 from Amazon. System version is 22.36.1.surnia_retus.retus.en.US Build LXI22.50-24.1.
Kernel is dated Feb 7 2015. Does anybody know why this is happening? Sorry to bump an old thread but I firmly believe this is relevant today.
By the way, I contacted Motorola support but they gave me a nonsense answer (i.e. that my phone is fine as it is with no 5.1.)
I have the XT1528 model and it says I have 5.1, but my phone still seems to be affected by stagefright 2.0. I assumed that 5.1 would fix that problem, but I am worried Motorola isnt even going to fix the issue.
That guy earlier said look at the link to see who is getting the 5.1 update rollup.
Don't expect to get it if your not only the list.
Also i seen myself that there was more than 1 stage fright update for 5.0.2
because there was more versions of the exploit that needed to be patched as time went on.
SO there was separate stage-fright updates for 5.0.2 and 5.1 respectively.
in other words you did not have to have 5.1 installed to get stage fright patched with an update.
They probably did that because they know most carriers are not pushing out 5.1 to their customers.
Which leads me to my next point..
It's not up to Motorola..
They can offer the update to any specific carrier but it's up to the carrier to decide if it is rolled out to customers.
It's been a long time now and most carriers did not get the 5.1 update.
It is doubtful i think anyone new is going on that list of who gets it.
For example my carrier in Canada Telus never rolled it out.
I had to get a stock firmware package for another carrier for 5.1 and put it on myself.
I chose to use the generic USA Retail Firmware package.
All has worked well but my phone model is suppose to be using LTE/cdma (surnia_umts)
But i have struggled to get it back on cdma.. with nobody out there with any suggestions on how to fix it.
Had i not tried to switch it over manually to GSM after install i would have given up.
Luckily my Carrier Telus supports CDMA and GSM.
I only found 1 guy who left a comment i seen way back saying he fixed his radio issue
by having his stock 5.0.2 Radio left intact then flashing all else to update.
That did not do me any good.. i have tried many variations with no difference.
I can confirm i was getting a new recent stage fright update OTA prmpt.
And there was a new updated firmware package shared recently that included this newer update.
I installed it and used a Stagefright checker App that scanned for about 10 variations of the exploit
and my phone was reported by the app as safe. (patched)
This version was just recently put on the web by someone..
XT1527_SURNIA_RETUS_5.1_LPI23.29-18.9_cid9_subsidy-DEFAULT_CFC.xml
MD5: 586d4a4888a570e6119c60d7437b6bcc
It has this OTA patch update integrated..
Blur_Version.23.11.15.surnia_retus.retus.en.US
MD5: 7b74752978545ccd0100c3d236cc88f6
xpmule said:
That guy earlier said look at the link to see who is getting the 5.1 update rollup.
Don't expect to get it if your not only the list.
Click to expand...
Click to collapse
My phone is on that list but it's not getting the 5.1 OTA.
xpmule said:
in other words you did not have to have 5.1 installed to get stage fright patched with an update.
They probably did that because they know most carriers are not pushing out 5.1 to their customers.
Which leads me to my next point..
It's not up to Motorola..
They can offer the update to any specific carrier but it's up to the carrier to decide if it is rolled out to customers.
Click to expand...
Click to collapse
It's not getting Stagefright patches either. Regarding the carrier, XT1527 is factory unlocked, which means it's not tied to a specific carrier.
Motorola should provide the updates since they say they do have a 5.1 update on their support site.
xpmule said:
I had to get a stock firmware package for another carrier for 5.1 and put it on myself.
All has worked well but my phone model is suppose to be using LTE/cdma (surnia_umts)
But i have struggled to get it back on cdma.. with nobody out there with any suggestions on how to fix it.
Click to expand...
Click to collapse
Did you try with 4G LTE Switch app? Its ID is com.tapbase.LTEswitcher
xpmule said:
I can confirm i was getting a new recent stage fright update OTA prmpt.
And there was a new updated firmware package shared recently that included this newer update.
XT1527_SURNIA_RETUS_5.1_LPI23.29-18.9_cid9_subsidy-DEFAULT_CFC.xml
It has this OTA patch update integrated..
Blur_Version.23.11.15.surnia_retus.retus.en.US
Click to expand...
Click to collapse
Interesting. Do you know if I can do this update to my phone without unlocking the bootloader? I don't want to void the warranty.
yituge said:
My phone is on that list but it's not getting the 5.1 OTA.
It's not getting Stagefright patches either. Regarding the carrier, XT1527 is factory unlocked, which means it's not tied to a specific carrier.
Motorola should provide the updates since they say they do have a 5.1 update on their support site.
Did you try with 4G LTE Switch app? Its ID is com.tapbase.LTEswitcher
Interesting. Do you know if I can do this update to my phone without unlocking the bootloader? I don't want to void the warranty.
Click to expand...
Click to collapse
Don't count on what i am saying i am a noob eh..
But yeah i think you can just flash that version i did.
Even if your bootloader is locked.
From the sounds of it i think that firmware i used on my Telus carrier phone
was actually originally intended for YOUR phone !
And 4G LTE Switch app?
Hmm no i have not seen that.. i should check it out thanks.
---------- Post added at 08:30 PM ---------- Previous post was at 08:16 PM ----------
I checked out that APP and all it does is open the settings menu for you.
You can just use the dialer instead..
*#*#INFO#*#*
That gives the same thing as that APP
I also have found it to be -read only- on my phone.
So if you change the option it actually doesn't work.
If you REALLY want to change it for real you have to use an alternate method such as..
connect with ADB using your computer.
then use this command..
Code:
adb shell
settings put global preferred_network_mode 9
settings put global preferred_network_mode1 9
Note: That will force LTE/GSM (auto PRL)
you don't need root to do that in the cmd prompt either.
and most guys out there say do another cmd line..
Code:
settings put global preferred_network_mode2 9
But i had checked and that line did not exist so i doubt adding it will do anything.
Change those lines to "get" and look at the value currently set before changing them.
When i ran the 3rd line it said that key does not exist.
Also the number 9 is LTE/GSM (auto PRL)
SO if you use that dialer command or that app you can count down the drop down list
to see what option is what number (to force it via command line)
For example..
no. 8 is..
LTE/cdma (auto PRL)
xpmule said:
Don't count on what i am saying i am a noob eh..
But yeah i think you can just flash that version i did.
Even if your bootloader is locked.
From the sounds of it i think that firmware i used on my Telus carrier phone
was actually originally intended for YOUR phone !
Click to expand...
Click to collapse
Don't worry, I'm a noob too, just trying to read a lot before doing anything.
I checked my phone and everything matches to this ROM:
SURNIA_RETUS_5.0.2_LXI22.50-24.1_cid9_subsidy-DEFAULT_CFC.xml.zip
I also installed CID Getter for further confirmation and ro.boot.cid is 0x9 (i.e. CID9.)
Which ROM I should flash to my phone:
the older SURNIA_RETUS_5.1_LPI23.29-15_cid9_subsidy-DEFAULT_CFC.xml.zip
or the newer XT1527_SURNIA_RETUS_5.1_LPI23.29-18.9_cid9_subsidy-DEFAULT_CFC.xml.zip ?
Does the last one contain Stagefright patches?
My main concern is -if I'm not mistaken- that either one should be 100% official Motorola or it won't flash with a locked bootloader.
xpmule said:
I checked out that APP and all it does is open the settings menu for you.
You can just use the dialer instead..
*#*#INFO#*#*
That gives the same thing as that APP
I also have found it to be -read only- on my phone.
So if you change the option it actually doesn't work.
Click to expand...
Click to collapse
I see. I thought it could work for you, but at least you know a workaround. Thanks for sharing.
Hello everyone
I am making this post because from reading discussions, there seems to be a large degree of confusion circulating regarding the differences between Verizon branded HTC 10 and the unlocked edition HTC 10, and what software can be used on either and what works on the Verizon network and doesn't. None of the information below is officially endorsed or supported, and I make no guarantees that it will work on your device-- can only vouch what works on mine.
Firstly...if you own an HTC 10 and are a Verizon customer, and your device is S-OFF, this applies to you. Whether it was purchased as an unlocked edition or a Verizon branded edition, the hardware is identical (as far as I understand), and if your device is S-OFF then you can put any software on the device as you so desire. This means when you travel, you can flash GSM firmware, then buy a cheap local prepaid SIM card in your destination country. Or if you get tired of Verizon, you can switch to ATT or TMobile-- or, vice versa, you can switch to Verizon from AT&T or TMobile.
When we get to the subject of firmware, the waters start to get muddy. Generally you are told that if you are on Verizon's network, you must flash only Verizon firmware or your device will not work on their network. This kinda sucks for us Verizon customers, because Verizon is known to be painfully slow at rolling out updates, and there could be serious security holes that are left unpatched while waiting for them to come through.
*However*, I have found that this device runs perfectly fine on Verizon's network with the unlocked-edition firmware (which is significantly more up-to-date as the Verizon firmware), as long as your RADIO partition is flashed with Verizon-specific radio firmware. But aside from the radio partition, none of the software on the other partitions need be Verizon-specific software. This is the method I use for updating to the latest unlocked firmware and Verizon radio (S-OFF requred):
--to update to the latest Verizon radio, flash the latest Verizon firmware-- just search for Verizon htc 10 firmware updates downloads, and you should be able to find it.. I will update this post later with a direct link to that thread..
--next step-- copy your radio partition to a disk image file. boot into recovery, then from adb shell run :
dd if=/dev/block/mmcblk0p30 of=radio.img
exit the shell, use adb pull to pull the radio.img file onto your PC
--step 3. flash the newest firmware for the unlocked-edition...
--step 4. flash the radio.img that you extracted earlier. Fastboot flash from bootloader mode (not RUU mode, not download mode-- just regular bootloader mode with the white screen and the tiny menu). 'fastboot flash radio radio.img'
And that's it.. you're good to go.. again, these instructions assume you are S-OFF and are familiar with the basic procedures for flashing firmware. If you wish to do this, it is done at your own risk.
Happy to answer any questions...hopefully some folks here will find this useful .
Well written, appreciate the info. [emoji106]
Sent from my HTC 10 using Tapatalk
Excellent guide, especially for those of us on Verizon who might want to test the waters with other 10-based ROMs. Since Verizon disables certain functions on its own devices (e.g. "Powersaver," SystemUI Tuner), one might want to look at the unlocked ROMs for full features. Thanks.:good:
I'm googling like crazy how to do the ADB Pull part up. lol I'm in bootloader with CMD promt open and i dont know what to type to ADB pull (never attempted this before).
EDIT: So apparently you need supercid to do this and when i try to modify the cid through "htc_fastboot oem writecid 11111111" it fails and I cannot continue. Anyone have luck doing this?
EDIT2: After a reboot, it allowed me to changed the CID. I tried to flash the firmware first (which crashed and I wasn't able to) so that must have caused the inability to change CID.
Answer to my Question by user @sbong
To Backup your Radio:
1. adb shell
2. su (if needed to get a #)
3. dd if=dev/block/mmcblk0p30 of=/sdcard/radio.img
4. exit
5. You'll find the radio image on the internal sd card
Flashing Latest unlocked firmware WIPED my ROM so just a heads up to anyone trying this.
I ran through these steps and flashed the international firmware version 1.95.401.4 and then flashed the radio I had while still on my VZW firmware. I did have to change my MID and CID before the firmware would flash but after I did it flashed successfully. Then I went back to bootloader (white screen with options) and flashed the radio.img file. After doing that and rebooting I am now sitting at the HTC splash screen with the white background and the red text saying this build is for dev purposes only. Any idea what to do at this point? Thanks!
EDIT: I am trying in TWRP to wipe system, data, and boot and then restore my ROM from a TWRP backup. Will post if it boots after doing this.
EDIT 2: Wiping my partitions in TWRP and the doing a restore allowed me to boot...interesting to note I got my firmware from here: https://docs.google.com/spreadsheets/d/1EdAHLDDxqf9jH65me_8bY9oXdaYusI0eedpwO6yUY2s/pubhtml under the NoWipe section so it shouldn't have messed with my ROM.
I'm hoping this helps with battery life as previously I was on old VZW firmware but my ROM was running a newer FW base. I heard that could cause battery drain. Now my phone FW matches the FW my ROM was based off of.
Unlocked software doesn't support Verizon advanced calling features. Which is a pretty big no for perfect. Just saying...
Sent from my HTC6545LVW using Tapatalk
dottat said:
Unlocked software doesn't support Verizon advanced calling features. Which is a pretty big no for perfect. Just saying...
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
I'm running unlocked US firmware version 1.95.401.4, but what I did do was extract the radio.img from my VZW firmware first, flashed the US unlocked, then flashed the VZW radio.img and booted up. My HD and WiFi calling is activated and working.
pettigrew95 said:
I'm running unlocked US firmware version 1.95.401.4, but what I did do was extract the radio.img from my VZW firmware first, flashed the US unlocked, then flashed the VZW radio.img and booted up. My HD and WiFi calling is activated and working.
Click to expand...
Click to collapse
You still didn't say what rom/software you are running. You can run the firmware from unlocked minus radio while on a Verizon rom and still have these features (why one would do this I have no clue). The unlocked os itself does no have advanced calling built in for Verizon unless it's a custom ROM like what @santod040 built where he added those features back in.
Sent from my HTC6545LVW using Tapatalk
dottat said:
You still didn't say what rom/software you are running. You can run the firmware from unlocked minus radio while on a Verizon rom and still have these features (why one would do this I have no clue). The unlocked os itself does no have advanced calling built in for Verizon unless it's a custom ROM like what @santod040 built where he added those features back in.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
The reason I flashed the US unlocked 1.95.401.4 is because I am running LeeDroid 2.7.0 which is based off of that firmware. I wanted the FW my ROM was based off of to match the firmware my phone was running. Also, VZW is way behind on FW updates for the 10 and I like to be somewhat up to date on the latest security patches from Google.
pettigrew95 said:
The reason I flashed the US unlocked 1.95.401.4 is because I am running LeeDroid 2.7.0 which is based off of that firmware. I wanted the FW my ROM was based off of to match the firmware my phone was running. Also, VZW is way behind on FW updates for the 10 and I like to be somewhat up to date on the latest security patches from Google.
Click to expand...
Click to collapse
Those security updates will be covered on the os side. While leedroid may be based off a 401 build make no mistake that most ril functions required for it to work on Verizon have been carved in from an actual Verizon rom. So in a sense, the parts that actually matter for connectivity are still going to interface best with Verizon firmware.
Sent from my HTC6545LVW using Tapatalk
dottat said:
Those security updates will be covered on the os side. While leedroid may be based off a 401 build make no mistake that most ril functions required for it to work on Verizon have been carved in from an actual Verizon rom. So in a sense, the parts that actually matter for connectivity are still going to interface best with Verizon firmware.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Thank you for that info. So is there any benefit then to what I did? Is anything broken in my phone that I don't know about? I have heard that if the FW a ROM was based off didn't match the FW your phone was running it could be a rogue battery drainer, is this true?
pettigrew95 said:
Thank you for that info. So is there any benefit then to what I did? Is anything broken in my phone that I don't know about? I have heard that if the FW a ROM was based off didn't match the FW your phone was running it could be a rogue battery drainer, is this true?
Click to expand...
Click to collapse
I would say likely not. As to whether anything is broken... if it's working it hasn't broken anything yet. You have to be careful though when running bits and pieces of mixed firmware because partition structure of the phone can change on htc phones based on aboot/hboot. So you can run into a scenario where a phone might not be partitioned to allow certain size images to flash successfully. Me personally, I would run one or the either. In this case, while on verizon, I would use the verizon firmware even if on a custom based rom. The one exception to this would be a built from the ground up rom like CM or AOSP. Some of these were developed to work solely on specific firmware.. One such variant of this in the htc m8 days was super popular. It was also the number one killer of m8's due to the specific/custom firmware flashing that was recommended in the OP. I can't tell you how many users i attempted to help fix their phones that either would not boot at all or that the phone itself was in a full write protected state.
When we get to the subject of firmware, the waters start to get muddy. Generally you are told that if you are on Verizon's network, you must flash only Verizon firmware or your device will not work on their network. This kinda sucks for us Verizon customers, because Verizon is known to be painfully slow at rolling out updates, and there could be serious security holes that are left unpatched while waiting for them to come through.
Click to expand...
Click to collapse
I find this statement sort of funny. Since we are talking firmware and not OS here it's not muddy at all. Verizon is behind on OS updates. Yes they toss in the HTC provided firmware updates as HTC requires.. but make not mistake the OS itself carries the security patches. So thinking you've somehow patched yourself by flashing firmware only is false re-assurement.
If somehow this statement refers to flashing the entire unlocked RUU/ROM/firmware all together and flashing the verizon radio by itself then i stand by my original note that this will get you the latest OS/firmware from HTC which will likely have the best chance at patching security flaws overall.. but the trade off will be advanced calling which is huge for most users.
dottat said:
I would say likely not. As to whether anything is broken... if it's working it hasn't broken anything yet. You have to be careful though when running bits and pieces of mixed firmware because partition structure of the phone can change on htc phones based on aboot/hboot. So you can run into a scenario where a phone might not be partitioned to allow certain size images to flash successfully. Me personally, I would run one or the either. In this case, while on verizon, I would use the verizon firmware even if on a custom based rom. The one exception to this would be a built from the ground up rom like CM or AOSP. Some of these were developed to work solely on specific firmware.. One such variant of this in the htc m8 days was super popular. It was also the number one killer of m8's due to the specific/custom firmware flashing that was recommended in the OP. I can't tell you how many users i attempted to help fix their phones that either would not boot at all or that the phone itself was in a full write protected state.
I find this statement sort of funny. Since we are talking firmware and not OS here it's not muddy at all. Verizon is behind on OS updates. Yes they toss in the HTC provided firmware updates as HTC requires.. but make not mistake the OS itself carries the security patches. So thinking you've somehow patched yourself by flashing firmware only is false re-assurement.
If somehow this statement refers to flashing the entire unlocked RUU/ROM/firmware all together and flashing the verizon radio by itself then i stand by my original note that this will get you the latest OS/firmware from HTC which will likely have the best chance at patching security flaws overall.. but the trade off will be advanced calling which is huge for most users.
Click to expand...
Click to collapse
When you say:
"If somehow this statement refers to flashing the entire unlocked RUU/ROM/firmware all together and flashing the verizon radio by itself then i stand by my original note that this will get you the latest OS/firmware from HTC which will likely have the best chance at patching security flaws overall.. but the trade off will be advanced calling which is huge for most users."
Is this correct? I thought flashing the VZW radio.img would enable advanced calling features to work? I am on a US unlocked FW with VZW radio.img flashed and my advanced calling features are functional on LeeDroid 2.7.0.
pettigrew95 said:
When you say:
"If somehow this statement refers to flashing the entire unlocked RUU/ROM/firmware all together and flashing the verizon radio by itself then i stand by my original note that this will get you the latest OS/firmware from HTC which will likely have the best chance at patching security flaws overall.. but the trade off will be advanced calling which is huge for most users."
Is this correct? I thought flashing the VZW radio.img would enable advanced calling features to work? I am on a US unlocked FW with VZW radio.img flashed and my advanced calling features are functional on LeeDroid 2.7.0.
Click to expand...
Click to collapse
Again,, I will restate it. You are NOT on unlocked. You have pieces of the firmware and a custom rom. That custom rom was based off international rom ( Not even the unlocked version as 401 is international and 617 is the actual unlocked variant).
Don't believe me this is a result of custom rom work and not firmware? Flash the unlocked RUU and then the verizon radio to get service. You will notice that advanced calling doesn't exist in the menu for you.
dottat said:
Again,, I will restate it. You are NOT on unlocked. You have pieces of the firmware and a custom rom. That custom rom was based off international rom ( Not even the unlocked version as 401 is international and 617 is the actual unlocked variant).
Don't believe me this is a result of custom rom work and not firmware? Flash the unlocked RUU and then the verizon radio to get service. You will notice that advanced calling doesn't exist in the menu for you.
Click to expand...
Click to collapse
Ok, sorry if my confusion is frustrating ...So basically my advanced calling features are operable due to my ROM and not the fact that I flashed a VZW radio.img on top of the non VZW firmware I flashed? In a nutshell...Is what I have done beneficial in any way or should I just flash back to the VZW 1.85 FW? Thank you for the help here, it is much appreciated!
pettigrew95 said:
Ok, sorry if my confusion is frustrating ...So basically my advanced calling features are operable due to my ROM and not the fact that I flashed a VZW radio.img on top of the non VZW firmware I flashed? In a nutshell...Is what I have done beneficial in any way or should I just flash back to the VZW 1.85 FW? Thank you for the help here, it is much appreciated!
Click to expand...
Click to collapse
Not frustrating at all. Don't take my responses as that way and certainly don't stop asking questions because of it. I'm still waking up here today so it's probably how i'm writing my responses lol. Personally I would just run the stock verizon firmware and enjoy your custom rom.
Your advanced call features are working due to leedroid splicing in the functional pieces of the advanced call features from the current verizon rom. I remember using an earlier version of his rom that lacked this feature set. I bailed on his rom pretty quickly when that was the only offering available as i needed advanced calling. A month or so later he added it to the rom later. @santod040 is one verizon dev who can comment here further when he sees this to attest to the fact the only way advanced calling works on verizon while on a non-verizon rom is that the DEV must enable it.
On the CM side of the house i have been involved in tracking down pieces of volte/advanced calling even back on the m9 in order to get it functional and I can tell you there it's not easy. So if you're on a non-vzw based rom and have advanced calling... make sure you thank the guys who baked your rom.
dottat said:
Not frustrating at all. Don't take my responses as that way and certainly don't stop asking questions because of it. I'm still waking up here today so it's probably how i'm writing my responses lol. Personally I would just run the stock verizon firmware and enjoy your custom rom.
Your advanced call features are working due to leedroid splicing in the functional pieces of the advanced call features from the current verizon rom. I remember using an earlier version of his rom that lacked this feature set. I bailed on his rom pretty quickly when that was the only offering available as i needed advanced calling. A month or so later he added it to the rom later. @santod040 is one verizon dev who can comment here further when he sees this to attest to the fact the only way advanced calling works on verizon while on a non-verizon rom is that the DEV must enable it.
On the CM side of the house i have been involved in tracking down pieces of volte/advanced calling even back on the m9 in order to get it functional and I can tell you there it's not easy. So if you're on a non-vzw based rom and have advanced calling... make sure you thank the guys who baked your rom.
Click to expand...
Click to collapse
Ok awesome, that pretty much sums up what I needed to hear! My last question, I have heard in the past that if the phone FW does not match the ROMs FW base it could be a rogue battery drainer, is this true? Part of the reason of me flashing the matching FW that LeeDroid 2.7.0 runs is in case mismatched ROM FW and phone FW does cause some kind of battery drain. I have to say, my phones battery is pretty pathetic even with Amplify, Greenify, Power Nap, etc. Thanks again!
Wow. I don't think I could be more confused. I'm humbly asking for clarity
I've got a Verizon 10 that is s-off, rooted, unlocked and running LeeDroid. The download screen shows 1.19 for the OS and @60504 for the radio. If I don't care about preserving the contents of the internal card, what's the simple path to get the fw/radio updated (looks like 1.85.605.8) and back to LeeDroid? If extracting the radio.img is a requirement, usually that kind of file is linked inline with the threads to root or update the fw. It's not, so alarms are going off in my head that there is a reason a flashable radio isn't right next to the RUU which would be next to the instructions for going from a custom rom like LeeDroid or Viper -> update fw/radio -> back to custom rom.
It took me an hour of reading, and not working, just to figure out I have an old fw/radio and one wrong move would commit myself to a day of reading and trying random things.
I can't stress the humble position I'm in and I did search and try to find the clear path, but I can't see it. Help?
jimbob_sf said:
Wow. I don't think I could be more confused. I'm humbly asking for clarity
I've got a Verizon 10 that is s-off, rooted, unlocked and running LeeDroid. The download screen shows 1.19 for the OS and @60504 for the radio. If I don't care about preserving the contents of the internal card, what's the simple path to get the fw/radio updated (looks like 1.85.605.8) and back to LeeDroid? If extracting the radio.img is a requirement, usually that kind of file is linked inline with the threads to root or update the fw. It's not, so alarms are going off in my head that there is a reason a flashable radio isn't right next to the RUU which would be next to the instructions for going from a custom rom like LeeDroid or Viper -> update fw/radio -> back to custom rom.
It took me an hour of reading, and not working, just to figure out I have an old fw/radio and one wrong move would commit myself to a day of reading and trying random things.
I can't stress the humble position I'm in and I did search and try to find the clear path, but I can't see it. Help?
Click to expand...
Click to collapse
For you just flash the custom firmware zip for Verizon that's been posted. You want the one without stock recovery and bootloader.
Going that route updates your phones firmware and saves you from wiping and flashing.
Sent from my HTC6545LVW using Tapatalk
Thank you! Now to figure out which thread has the file you're referring to. I've looked at them all and I can't tell which one does what you're saying.
Hi,
First some intel:
I got my Duo device in a raffle and it happened to come from AT&T. It is locked to the AT&T network and unlocking had to be done via the helpdesk and couldn't be done for their website. The IMEI number isn't recognized. So, be aware that you really need to direct the helpdesk what to do in order to get it unlocked; they will tell you it's not an AT&T device.
So, finally, I got it unlocked. Yet....now there's AT&T bloatware on the device. So, what I want to do is put the original MS image back on the device. I have the following questions:
I need to supply the serial number in order to download the image from the Microsoft site. When I do that, it gives me the AT&T image.
1) if I put the AT&T image on the phone (which is already there, so I don't want to do that), will it root my phone?
2) what about the original MS image? Will it make permanent changes to the bootloader? Will it root my phone? (I don't want my phone rooted - I want a Duo with the original MS software, not with the AT&T nonsense installed).
Finally, where do I get the original image? I emailed Microsoft, but they say "it may damage the software" if I put the non AT&T image on the device. This is obviously a weird answer, but it shows they can't advise me on how to proceed.
Thank you!
Nothing about flashing stock firmware will root your device. That requires an explicit action aimed at rooting. As for flashing the non-att firmware, it should work just fine, if you cant get the phone to accept it. You could try using a serial number from a non-att device. At some point im sure there will be flashable firmware posted up here...it may require unlocking bootloader, then relocking when you have switched. Is OEM-unlocking available on the att model?
mastibeta said:
Is OEM-unlocking available on the att model?
Click to expand...
Click to collapse
Thank you for your clear reply. I understand things better now.
Yes, the AT&T version looks to have an unlockable bootloader, although I haven't activated it.
anyone try this yet? does it work? would love to lose the att bloat ware. also still looking for an unlocking solution (recieved a replacement from microsoft that att will not unlock, device is paid for etc)
jeremiahscomputerstore said:
anyone try this yet? does it work? would love to lose the att bloat ware. also still looking for an unlocking solution (recieved a replacement from microsoft that att will not unlock, device is paid for etc)
Click to expand...
Click to collapse
I too would be interested in any reports. I'm expecting the AT&T version from the Woot.com special last week, but am not an AT&T customer. My planned usage will be to use the Duo on WiFi only. Getting rid of the AT&T bloatware would be ideal. Thanks in advance....
So can someone who has unlocked version download from Microsoft website using his serial number the non att version of image and share with us?
here is the link to get image
Surface Recovery Image Download - Microsoft Support
support.microsoft.com
It would be great if someone can get us a copy to try. I'd also like to see what version comes down for everyone. The latest I can get from the recovery site is 2021.419.71, but an update to 2021.525.63 is available. When I spoke to Microsoft, they said that recovery image won't be available until August at the earliest... So I can't even restore my device if needed.
Veritas06 said:
It would be great if someone can get us a copy to try. I'd also like to see what version comes down for everyone. The latest I can get from the recovery site is 2021.419.71, but an update to 2021.525.63 is available. When I spoke to Microsoft, they said that recovery image won't be available until August at the earliest... So I can't even restore my device if needed.
Click to expand...
Click to collapse
I will like to try the Microsoft image on my unlocked AT&T phone. Anyone can help to pull down the image? Do not understand why Microsoft remove eSim from AT&T variant
Hi,
Are you still willing to download stuff and try to flash your AT&T with non AT&T firmware ?
I'd be very much interested in the result and can provide the recovery image from non AT&T version.
Regards.
H again,
So no one who tried this ? If someone did, can he share results please ? That would be super interesting for the whole community I guess.
Regards.
NexusPenguin said:
H再次，
所以没有人尝试过这个？如果有人这样做了，他可以分享结果吗？我想这对整个社区来说都非常有趣。
问候。
Click to expand...
Click to collapse
900176502367
Used OEM SIM tray for Microsoft Surface Duo TGL-00001
900537402467 256 GB TGM-00001 Network:Unlocked
Surface Duo - 128GB - Android 11 - GEN - 2022.517.57
912262603467
olav said:
Hi,
First some intel:
I got my Duo device in a raffle and it happened to come from AT&T. It is locked to the AT&T network and unlocking had to be done via the helpdesk and couldn't be done for their website. The IMEI number isn't recognized. So, be aware that you really need to direct the helpdesk what to do in order to get it unlocked; they will tell you it's not an AT&T device.
So, finally, I got it unlocked. Yet....now there's AT&T bloatware on the device. So, what I want to do is put the original MS image back on the device. I have the following questions:
I need to supply the serial number in order to download the image from the Microsoft site. When I do that, it gives me the AT&T image.
1) if I put the AT&T image on the phone (which is already there, so I don't want to do that), will it root my phone?
2) what about the original MS image? Will it make permanent changes to the bootloader? Will it root my phone? (I don't want my phone rooted - I want a Duo with the original MS software, not with the AT&T nonsense installed).
Finally, where do I get the original image? I emailed Microsoft, but they say "it may damage the software" if I put the non AT&T image on the device. This is obviously a weird answer, but it shows they can't advise me on how to proceed.
Thank you!
Click to expand...
Click to collapse
900176502367
Used OEM SIM tray for Microsoft Surface Duo TGL-00001
900537402467 256 GB TGM-00001 Network:Unlocked
下载：Surface Duo - 128GB - Android 11 - GEN - 2022.517.57
912262603467