I did my pre-order my zenfone 3 deluxe. I got the snapdragon 821 with 256 GB internal. Who else ditch Samsung for not having an unlock bootloader?
killerdvd said:
I did my pre-order my zenfone 3 deluxe. I got the snapdragon 821 with 256 GB internal. Who else ditch Samsung for not having an unlock bootloader?
Click to expand...
Click to collapse
Where did you pre order from? I haven't seen this out yet.
Im hoping the Canadian note 7 is not locked down but the asus has certainly got my attention regardless. It has alot to offer and for alot less than the note
Asus may also lock the BL though, we dont know yet.
Sent from my SM-N910T using Tapatalk 2
force70 said:
Where did you pre order from? I haven't seen this out yet.
Im hoping the Canadian note 7 is not locked down but the asus has certainly got my attention regardless. It has alot to offer and for alot less than the note
Asus may also lock the BL though, we dont know yet.
Sent from my SM-N910T using Tapatalk 2
Click to expand...
Click to collapse
I pre ordered from this web http://www.expansys-usa.com/asus-ze...locked-256gb-titanium-gray-ww-version-291308/
I had been loyal to Samsung note since the note 2 but I'm a flashaholic. I need an unlock bootloader.
Using note 2 atm with aosp 6.0.1 ROM ... I can wait for the zenfone 3 deluxe release because I want to ditch Samsung as well
I'm thinking of same thing. On a Note 4 now. Although I will miss the stylus.
Are any of you speaking of a U.S. version?
I looked at the Zen 2 forums...didn't look like a lot of community support out there.
killerdvd said:
I did my pre-order my zenfone 3 deluxe. I got the snapdragon 821 with 256 GB internal. Who else ditch Samsung for not having an unlock bootloader?
Click to expand...
Click to collapse
Former Note 2 user here (Mine died after 3 years, fell to the ground to never to boot-up again)
It is not certain yet that the Zenfone 3 series will come with an unlockable bootloader.
I wish YouTube reviewers who get their hands on devices first would be so smart to get into fastboot and show us the fastboot variables.
I'm tending between the Zenfone 3 Deluxe and the Google Marlin.
celoxocis said:
I wish YouTube reviewers who get their hands on devices first would be so smart to get into fastboot and show us the fastboot variables.
I'm tending between the Zenfone 3 Deluxe and the Google Marlin.
Click to expand...
Click to collapse
Google Marlin will net you an unlockable BL, but ASUS has usually been flash friendly, which is why I'm hoping the ZFD to be unlockable.
I moved from a Huawei P8Max (6.8") to a Xiaomi Mi5 (5.15"), but can't get used to the smaller screen, hence my investigating the Zenfone 3 Deluxe, Moto Z Force, or waiting for the Marlin.
Choices choices -_-
adwinp said:
Google Marlin will net you an unlockable BL, but ASUS has usually been flash friendly, which is why I'm hoping the ZFD to be unlockable.
I moved from a Huawei P8Max (6.8") to a Xiaomi Mi5 (5.15"), but can't get used to the smaller screen, hence my investigating the Zenfone 3 Deluxe, Moto Z Force, or waiting for the Marlin.
Choices choices -_-
Click to expand...
Click to collapse
Since when doesn't Google "not" unlock the bootloader or the OEM which is HTC?
Both of those companies always allowed for unlockable bootloader. Wherever you read your news I would change that site.
Asus on the other hand only released an unlockable option only for their Zenfone 2 series "later in the game".
Meaning when users constantly complained about their ZenUI.
Asus changed it's direction with Zenfone 3. From affordable Zenfone 2 series to (what they think) IPhone 7 killers. The deluxe got released just after the I7 had been announced. That's no coincidence that's market strategy. Also look at their prices for their midranges tiers compared to the Z2 series. They are outrageous.
I highly doubt the Z3 series will have an unlockable bootloader from the start. They will try to go the "fruit company" name. Not just on market prices but also on Software strategy which includes locked bootloader.
Did you get the Phone
killerdvd said:
I did my pre-order my zenfone 3 deluxe. I got the snapdragon 821 with 256 GB internal. Who else ditch Samsung for not having an unlock bootloader?
Click to expand...
Click to collapse
Did you ever get your pre-ordered phone?
If not, what is the ETA?
If do you have it, any first impressions?
I would like to get one but no info on USA release date...
Thanks!
gatorgal88 said:
Did you ever get your pre-ordered phone?
If not, what is the ETA?
If do you have it, any first impressions?
I would like to get one but no info on USA release date...
Thanks!
Click to expand...
Click to collapse
I haven't get my unit yet. :'(
ETA is for September 30th. It has been shipped from china already. It comes with all the pre-order gifts. I can't wait to have it.
I'll keep you guys update.
adwinp said:
Google Marlin will net you an unlockable BL, but ASUS has usually been flash friendly, which is why I'm hoping the ZFD to be unlockable.
I moved from a Huawei P8Max (6.8") to a Xiaomi Mi5 (5.15"), but can't get used to the smaller screen, hence my investigating the Zenfone 3 Deluxe, Moto Z Force, or waiting for the Marlin.
Choices choices -_-
Click to expand...
Click to collapse
I can't do a screen smaller than 5.7. Even the 5.7 feels a bit to smaller. A 6 would be perfect.
Former Note4 user here too, I would have gotten the Note7 but Samsung dropped the ball so hard I can't even see where it rolled to anymore.
Just received my Z3D yesterday. How do I check if the bootloader is locked or not?
EDIT: Nevermind, found out... As expected it's locked out of the box. Grr.
shirakani said:
Former Note4 user here too, I would have gotten the Note7 but Samsung dropped the ball so hard I can't even see where it rolled to anymore.
Just received my Z3D yesterday. How do I check if the bootloader is locked or not?
EDIT: Nevermind, found out... As expected it's locked out of the box. Grr.
Click to expand...
Click to collapse
They didnt drop the ball they threw it away lol
Im thinking of just unloading my new note 7 when it comes for this but if the BL is locked and not unlockable forget it.
Absolute beast of a device but useless if its locked.
Sent from my SM-N930F using Tapatalk 2
shirakani said:
Former Note4 user here too, I would have gotten the Note7 but Samsung dropped the ball so hard I can't even see where it rolled to anymore.
Just received my Z3D yesterday. How do I check if the bootloader is locked or not?
EDIT: Nevermind, found out... As expected it's locked out of the box. Grr.
Click to expand...
Click to collapse
What are your first impressions on the Z3D? How is the camera?
Solid build?
Where did you order from?
What country are you located?
Wondering how long before I can order here in the USA.
I would think that they will release a bootloader unlock like they did for the Z2.
I currently have a Galaxy S7 Edge and I love then phone and camera but hate that it is locked bootloader.
gatorgal88 said:
What are your first impressions on the Z3D? How is the camera?
Solid build?
Where did you order from?
What country are you located?
Wondering how long before I can order here in the USA.
I would think that they will release a bootloader unlock like they did for the Z2.
I currently have a Galaxy S7 Edge and I love then phone and camera but hate that it is locked bootloader.
Click to expand...
Click to collapse
My first immediate impressions are its one hell of a nice phone. Its thinner feeling and lighter than the Note4. Camera had a few stability issues which were solved after running a software update to the latest OTA update.
Build is very solid feeling. For those who are fans of the form factor/feel of the iPhone 6 Plus it'll feel more or less the same except solid metal. The look is extremely sleek.
The front metal is not the same brushed metal as the back, and fingerprints horribly, ugh... But I guess its a case of find me a phone that doesn't fingerprint.
Not sure why ppl 'absolutely hate' the ZenUI, its lightweight and fully customizable... Coming from a Samsung phone, this is absolutely nothing compared to Samsung's bloat.
There were only a handful of chinese installed apps which were not 'system locked' so did not require root to uninstall. It comes with a very handy little app management tool too that prevents apps from 'auto starting' as a default.
Haven't faffed around w/ the camera much as I spent all night looking for a way to root the thing before realizing the phone was way too new and there's practically nothing available....
As for where I got it, I'm in Australia... but I have relatives in Taiwan. I simply asked an uncle to walk into a retail store, buy one and send it to me via Fed Ex. No idea when it will be internationally available.
---------- Post added at 11:10 AM ---------- Previous post was at 10:48 AM ----------
force70 said:
Absolute beast of a device but useless if its locked.
Click to expand...
Click to collapse
That's the thing, we don't know if it can/can't be unlocked. Right now it seems like practically nobody has the phone or nobody w/ developer skills has had a chance to play with it.
We need to get a unit into the hands of a skilled dev to be sure....
shirakani said:
Former Note4 user here too, I would have gotten the Note7 but Samsung dropped the ball so hard I can't even see where it rolled to anymore.
Just received my Z3D yesterday. How do I check if the bootloader is locked or not?
EDIT: Nevermind, found out... As expected it's locked out of the box. Grr.
Click to expand...
Click to collapse
Just curious as how you checked it.
Where did you check it? Did you enter fastboot and check the output of the variables?
Which is "fastboot getvar all"?
Because if the bootloader is locked I'm fine with it as long as there are fastboot binarys. Which means we could receive official unlock sometime in the future. If not Google Pixel XL here I come.
celoxocis said:
Just curious as how you checked it.
Where did you check it? Did you enter fastboot and check the output of the variables?
Which is "fastboot getvar all"?
Because if the bootloader is locked I'm fine with it as long as there are fastboot binarys. Which means we could receive official unlock sometime in the future. If not Google Pixel XL here I come.
Click to expand...
Click to collapse
I'm a noob at this stuff so you tell me, this is the output (I've removed the serial, obviously):
C:\Windows\system32>fastboot getvar all
(bootloader) cputype:8996pro
(bootloader) version:1.0
(bootloader) cpusn:1023896535
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4251000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:APD:ext4
(bootloader) partition-size:APD: 0xd700000
(bootloader) partition-type:ADF:ext4
(bootloader) partition-size:ADF: 0x2800000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x39c54af000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xf3c00000
(bootloader) serialno:<REMOVED>
(bootloader) kernel:lk
(bootloader) product:MSM8996
all:
finished. total time: 0.262s
Doing a fastboot oem device-info gives me this, and 'fastboot oem unlock' doesn't work as expected.
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Device oem_adb_enable: false
OKAY [ 0.066s]
finished. total time: 0.067s
shirakani said:
I'm a noob at this stuff so you tell me, this is the output (I've removed the serial, obviously):
C:\Windows\system32>fastboot getvar all
(bootloader) cputype:8996pro
(bootloader) version:1.0
(bootloader) cpusn:1023896535
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4251000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:APD:ext4
(bootloader) partition-size:APD: 0xd700000
(bootloader) partition-type:ADF:ext4
(bootloader) partition-size:ADF: 0x2800000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x39c54af000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xf3c00000
(bootloader) serialno:<REMOVED>
(bootloader) kernel:lk
(bootloader) product:MSM8996
all:
finished. total time: 0.262s
Doing a fastboot oem device-info gives me this, and 'fastboot oem unlock' doesn't work as expected.
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Device oem_adb_enable: false
OKAY [ 0.066s]
finished. total time: 0.067s
Click to expand...
Click to collapse
Thanks a lot!
This actually is really good. It means proper fastboot binarys are available. So my guess is that Asus keeps its options open for a bootloader unlock tool! Which will allow for "fastboot OEM unlock". So for now all we can do is wait for Asus to release it.
celoxocis said:
Thanks a lot!
This actually is really good. It means proper fastboot binarys are available. So my guess is that Asus keeps its options open for a bootloader unlock tool! Which will allow for "fastboot OEM unlock". So for now all we can do is wait for Asus to release it.
Click to expand...
Click to collapse
Well, yeah, they released said bootloader unlock tool for the Zenfone 2 remember?
The question is how long do we have to wait for them to release said unlock tool before we can have basic root....
shirakani said:
Well, yeah, they released said bootloader unlock tool for the Zenfone 2 remember?
The question is how long do we have to wait for them to release said unlock tool before we can have basic root....
Click to expand...
Click to collapse
I would say as much as the time waited for the old unlock tool. Which was about a year?
One could try to see if the old tool works for the Z3. Which I guess doesn't but hey you never know.
The Zuk Z2 got its bootloader unlocked with the unlock tool for the Zuk Z1. Guess they forgot to change the method.
Related
Hello,
Sorry if sounds stupid or not, but I was wondering if having access to fastboot means having an unlocked bootloader?
I ran fastboot getvar and got this result
version-bootloader: 1000
product: olympus
secure: no
version: 0.4
serialno:
version-baseband: currently un-upported
all: Done
This is on an AT&T branded Atrix OLYFR or something
mowassasin said:
Hello,
Sorry if sounds stupid or not, but I was wondering if having access to fastboot means having an unlocked bootloader?
I ran fastboot getvar and got this result
version-bootloader: 1000
product: olympus
secure: no
version: 0.4
serialno:
version-baseband: currently un-upported
all: Done
This is on an AT&T branded Atrix OLYFR or something
Click to expand...
Click to collapse
I'm probably wrong, but when it says "secure: no" then I think that might mean that your phone has an unlocked bootloader. im 0.1% sure.
Short answer is no.
I believe this is the same conversation as is posted in this thread
Hey guys,
I bought my unlocked m8 from Amazon and according to model number I guess it's an at&t model even though
I got a clean sense 6 and not a custom at&t.
Can I root it and install custom rooms normally? I mean download it from here and install it? Or I need to download it from
A different m8 forum(Verizon, Sprint etc)?
ishaycc said:
Hey guys,
I bought my unlocked m8 from Amazon and according to model number I guess it's an at&t model even though
I got a clean sense 6 and not a custom at&t.
Can I root it and install custom rooms normally? I mean download it from here and install it? Or I need to download it from
A different m8 forum(Verizon, Sprint etc)?
Click to expand...
Click to collapse
I assume you have a gsm unlocked phone. Yes, you can flash international roms. You can flash at&t roms if you are using at&t, if not, most at&t roms do not allow you to edit apn settings easily. Most people just flash the international roms unless you are one of these people who just can't live without there voicemail popping up in their messages. Do not flash sprint or verizon. You need to unlock boot loader, then root, then i would soff if your phone allows it. Even if soff doesn't work, you can still flash any rom. Remember to do backup as soon as you get into custom recovery.
Load CDMA radoi on unlocked M8
I have a factory unlocked international version of M* for GSM, would like to use it in CDMA in India, pl. help how can I achieve this.
lopesh007 said:
I have a factory unlocked international version of M* for GSM, would like to use it in CDMA in India, pl. help how can I achieve this.
Click to expand...
Click to collapse
If the CDMA radio isn't already supported in hardware, you can't add it simply by flashing a file or other software change. And as far as I can tell, from looking at specs, the T-Mobile and Sprint versions are the only ones that support CDMA.
an0ther said:
I assume you have a gsm unlocked phone. Yes, you can flash international roms. You can flash at&t roms if you are using at&t, if not, most at&t roms do not allow you to edit apn settings easily. Most people just flash the international roms unless you are one of these people who just can't live without there voicemail popping up in their messages. Do not flash sprint or verizon. You need to unlock boot loader, then root, then i would soff if your phone allows it. Even if soff doesn't work, you can still flash any rom. Remember to do backup as soon as you get into custom recovery.
Click to expand...
Click to collapse
Thx for the reply. Actually after talking to a HTC representative I found out I have the dev edition device
Which according to them has an unlocked bootloader. Can anyone explain what it means and
What can I do with it?
ishaycc said:
Thx for the reply. Actually after talking to a HTC representative I found out I have the dev edition device
Which according to them has an unlocked bootloader. Can anyone explain what it means and
What can I do with it?
Click to expand...
Click to collapse
Then you are already unlocked. You need to get a custom recovery and root. There are plenty of guides on this, but if you have any specific questions msg me.
an0ther said:
Then you are already unlocked. You need to get a custom recovery and root. There are plenty of guides on this, but if you have any specific questions msg me.
Click to expand...
Click to collapse
I'll sure do that if I have one. Many thanks.
GSM to CDMA
redpoint73 said:
If the CDMA radio isn't already supported in hardware, you can't add it simply by flashing a file or other software change. And as far as I can tell, from looking at specs, the T-Mobile and Sprint versions are the only ones that support CDMA.
Click to expand...
Click to collapse
Thanks for the update,
Will the following help to identify my model :
C:\Program Files (x86)\Minimal ADB and Fastboot>fas
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.56.720.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also if the processor (SOC) for AT&T, Sprint and international version is Snapdragon 801, will the support both radios.
lopesh007 said:
Also if the processor (SOC) for AT&T, Sprint and international version is Snapdragon 801, will the support both radios.
Click to expand...
Click to collapse
The fact they share the 801 SoC doesn't mean anything. The AT&T versions does not support CDMA.
I'm not particularly knowledgeable if the info you supplied will answer the question definitely or not. But if it is the international version, I highly doubt CDMA is supported.
Sent from my HTC One_M8 using XDA Free mobile app
[Q&A] [RADIO & FIRMWARE]HTC One Radio's | Firmware | Other Useful Files | Updated 6/
Q&A for [RADIO & FIRMWARE]HTC One Radio's | Firmware | Other Useful Files | Updated 6/6/14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RADIO & FIRMWARE]HTC One Radio's | Firmware | Other Useful Files | Updated 6/6/14. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
HTC One Factory reset T-Mobile Baseband: 4T.20.3218.13_10.12.1718.01L
Hi,
I need help with factory reset on my HTC One. I am new to this process. The person I bought it from said all I need to do is flash the radio. Appreciate your guidance in doing so. I have so far took backup of Contacts, Media. I need steps to flash the radio. Please find below baseband information:
HTC One
T-Mobile
Baseband Version : 4T.20.3218.13_10.12.1718.01L
Thanks in advance.
htconeuser81 said:
Hi,
I need help with factory reset on my HTC One. I am new to this process. The person I bought it from said all I need to do is flash the radio. Appreciate your guidance in doing so. I have so far took backup of Contacts, Media. I need steps to flash the radio. Please find below baseband information:
HTC One
T-Mobile
Baseband Version : 4T.20.3218.13_10.12.1718.01L
Thanks in advance.
Click to expand...
Click to collapse
Go to this post: Latest T-Mo Radios pick a radio
Download radio to your sdcard
Boot into custom recovery
Select Install or Install from SDCARD
Find the file you downloaded
Select the file
majmoz said:
Go to this post: Latest T-Mo Radios pick a radio
Download radio to your sdcard
Boot into custom recovery
Select Install or Install from SDCARD
Find the file you downloaded
Select the file
Click to expand...
Click to collapse
Thanks a lot for the reply. The link you provided do not have the radio for T-Mobile 4T.20.3218.13_10.12.1718.01L. Can I still use either
T-Mobile Radio 4T.28.3218.04_10.33E.1718.01L - From RUU 6.10.531.9 (Latest)
Or
T-Mobile Radio 4T.27.3218.14_10.33C.1718.01L - From RUU 5.14.531.1 (I believe) for my baseband version ?
htconeuser81 said:
Thanks a lot for the reply. The link you provided do not have the radio for T-Mobile 4T.20.3218.13_10.12.1718.01L. Can I still use either
T-Mobile Radio 4T.28.3218.04_10.33E.1718.01L - From RUU 6.10.531.9 (Latest)
Or
T-Mobile Radio 4T.27.3218.14_10.33C.1718.01L - From RUU 5.14.531.1 (I believe) for my baseband version ?
Click to expand...
Click to collapse
The radios in the post are from the last two updates. Yes, you can use them your choice.
Unlocked M7 Firmware Needed
Hello everyone.
I have been using my unlocked M7 (international variant) on T-mobile's network for a while, but now i'm figuring I may need updated Firmware. I haven't been able to find anything for it since my OS- in hboot is blank and so is Mainvers- in fastboot. If anyone can point me in the right direction it would be appreciated. Ill list my specs below as well.
BOOTLOADER
Unlocked
M7_UL PVT SHIP S-OFF
CID CWS__001
HBOOT 1.5.0000
RADIO-4T.20.3218.13
OS-
EMMC-boot 2048MB
Oct, 4 2013
Also MID is PN0712000
Im currently running Viperone 7.0.1 (stock sense setup) with TWRP 8.3.0
On a side note: The lates TWRP was flashed after i dirty flashed viperone. Could this be why my mainvers is missing?
thanks
htc one m7
Hi ,
I have a second hand htc one m7 . I am not able to install OTA updates on my phone and I later found out that the previous owner had installed custom recovery.
Therefore I wanted to know which stock recovery should I flash. I donot have much idea, can you please help
This is what I got from getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader:
(bootloader) version-baseband: 4A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.7
(bootloader) version-misc: PVT SH
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 378
(bootloader) partition-layout: Ge
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Please let me know
shantanu.das2 said:
Hi ,
I have a second hand htc one m7 . I am not able to install OTA updates on my phone and I later found out that the previous owner had installed custom recovery.
Therefore I wanted to know which stock recovery should I flash. I donot have much idea, can you please help
This is what I got from getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: Missing Data
(bootloader) version-baseband: 4A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.7 Missing Data
(bootloader) version-misc: PVT SH
(bootloader) serialno: Remove
(bootloader) imei: Remove
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 378
(bootloader) partition-layout: Ge
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Please let me know
Click to expand...
Click to collapse
You should edit your first post to remove your imei and serialno from the internet. You have some important missing data so it would be hard to recommend a stock recovery. The complete version-main number will tell you which stock recovery you should use. It should either be the same number or the next version up. Once you have those numbers you can look here to see it one is available.
majmoz said:
You should edit your first post to remove your imei and serialno from the internet. You have some important missing data so it would be hard to recommend a stock recovery. The complete version-main number will tell you which stock recovery you should use. It should either be the same number or the next version up. Once you have those numbers you can look here to see it one is available.
Click to expand...
Click to collapse
Hi @majmoz
Thank you so much for your help.
I have flashed the stock recovery. Now it could successfully install one OTA update but my phone has updated only to 4.2 i.e Jelly Bean.
Now when I check for the next kitkat updates, it says no update found
Can you let me know where the problem lies, as my previous HTC one had kitkat in it but with this one am not able to update
shantanu.das2 said:
Hi @majmoz
Thank you so much for your help.
I have flashed the stock recovery. Now it could successfully install one OTA update but my phone has updated only to 4.2 i.e Jelly Bean.
Now when I check for the next kitkat updates, it says no update found
Can you let me know where the problem lies, as my previous HTC one had kitkat in it but with this one am not able to update
Click to expand...
Click to collapse
If you were able to update once, then you should be able to continue the updates. Sometimes, it takes a couple of hours or more before you will see the next update. If after a day or so still no update then we might have to look into it further. As long as you didn't unlock your bootloader and install a custom recovery you should be OK.
htc one e8 m8s
Which one I must choose for my device HTC one e8 m8sd,thanks before
I'm so confused because I lost my signal when accidentally choosed USA bands
sprint version
what is the baseband for open all bands posible in htc one sprint?.
HTC One Signal
My HTC One barely & inconsistently connects to the network. Data connectivity is completely dead. I am out of contract and have changed network provider so I know the issue is with the phone. I am hoping it is a radio issue but have no clue how to deal with it. I had it 'S-off'-ed today but do not know how to proceed.
I am looking for noob/dummy steps to find an alternative radio, add it to the phone and 'flash' it.
Any takers?
Cheers
It seems after countless bootloops, I've discovered that my phone is NOT the international version, or the standard one anyway. After pulling the getvar from my phone, it stated that my phone is t6u, not t6ul like Hong Kong or international version. It seems phones purchased in Vietnam all share these same specs
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: t6u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: 0P3P60000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3987mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
So far, Nusense Rom is working and the phone is working fine but any kernel and hboot will leads to softbrick and bootloops. My ROM version and baseband has disappeared from getvar and Bootloader due to flashing incompatible firmware and getting bootloops on the first flash .The original version as I've found out through Google is 3.24.707.102. I made the mistake of not backing up the original firmware and now I'm stuck with custom roms until I can find a way to restore to the original T6U compatible stock ROM. When I find the original firmware or RUU of this variant I will upload it here in hope of helping the devs in troubleshooting problems.
Here is a link to the hboot I've managed to pull from my phone before attempting to flash the nored hboot of international variant which led to a softbrick stockhboot.img
Interesting... u is the 3G version & ul is the LTE version.
This phone seems to be a non retail version - did you actually buy it retail? it seems like it was dev phone. It has Engg HBOOT and its s-off
Code:
(bootloader) platform: HBOOT-8064 is engineering HBOOT!
(bootloader) security: off
HTC 044 CID is Europe and that is something you cannot buy in Vietnam
If you got Chinese friends, you can ask them for a RUU
3.24.707.102 is not Vietnamese, 707 is Indian if i remember correctly.
This is one hell of a variant lol!
pradeepvizz said:
Interesting... u is the 3G version & ul is the LTE version.
This phone seems to be a non retail version - did you actually buy it retail? it seems like it was dev phone. It has Engg HBOOT and its s-off
Code:
(bootloader) platform: HBOOT-8064 is engineering HBOOT!
(bootloader) security: off
HTC 044 CID is Europe and that is something you cannot buy in Vietnam
If you got Chinese friends, you can ask them for a RUU
3.24.707.102 is not Vietnamese, 707 is Indian if i remember correctly.
This is one hell of a variant lol!
Click to expand...
Click to collapse
Nope. I bought it retail. Here is a getvar from another user of this variant (Vietnamese also)
INFOversion: 0.5
INFOversion-bootloader: 2.49.0000
INFOversion-baseband: 4T.27.3218.14
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.24.707.102
INFOversion-misc: PVT SHIP S-ON
INFOserialno: FA3BGWG01421
INFOimei: 3573--4252
INFOmeid: 00000000000000
INFOproduct: t6u
INFOplatform: HBOOT-8064
INFOmodelid: 0P3P60000
INFOcidnum: HTC__044
INFObattery-status: good
INFObattery-voltage: 4108mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-0e1af350
INFOhbootpreupdate: 11
Click to expand...
Click to collapse
HTC_044 is what it says so I wish my phone was European
From my memory, the original firmware does support LTE but I can't test at the moment because Vietnam doesn't have LTE yet. I was able to S-OFF with Sunshine but no idea if the Hboot is engineer or not. From the getvar of the other user, if it is correct then it is one hell of a variant indeed. The 3.24.707.102 is the latest OTA update . I've already tried searching for RUU of this phone but nothing came up and pretty sure Chinese variants are different.
leminhnguyen0703 said:
Nope. I bought it retail. Here is a getvar from another user of this variant (Vietnamese also)
HTC_044 is what it says so I wish my phone was European
From my memory, the original firmware does support LTE but I can't test at the moment because Vietnam doesn't have LTE yet. I was able to S-OFF with Sunshine but no idea if the Hboot is engineer or not. From the getvar of the other user, if it is correct then it is one hell of a variant indeed. The 3.24.707.102 is the latest OTA update . I've already tried searching for RUU of this phone but nothing came up and pretty sure Chinese variants are different.
Click to expand...
Click to collapse
Here is the RUU file name - you will need to find the way to download
0P3PIMG_T6_U_K44_SENSE60_MR_hTC_Asia_WWE_3.24.707.102_Radio_4T.27.3218.14_10.33C.1718.01_release_395549_combined_signed_2_4.zip
pradeepvizz said:
Here is the RUU file name - you will need to find the way to download
0P3PIMG_T6_U_K44_SENSE60_MR_hTC_Asia_WWE_3.24.707.102_Radio_4T.27.3218.14_10.33C.1718.01_release_395549_combined_signed_2_4.zip
Click to expand...
Click to collapse
Yeah I've already found that mobilefileserver website. It requires a paid membership so I'm not sure of authenticity. I'll give it a try when I find out
leminhnguyen0703 said:
Yeah I've already found that mobilefileserver website. It requires a paid membership so I'm not sure of authenticity. I'll give it a try when I find out
Click to expand...
Click to collapse
If you manage to get it, you shouldn't be worried. It's a encrypted zip and HBoot wont allow flash an improper file.
pradeepvizz said:
If you manage to get it, you shouldn't be worried. It's a encrypted zip and HBoot wont allow flash an improper file.
Click to expand...
Click to collapse
Thank you for the help Can I ask if my phone does have an ENG HBOOT, what would the difference be compared to a normal unlocked and S-Off device ?
leminhnguyen0703 said:
Thank you for the help Can I ask if my phone does have an ENG HBOOT, what would the difference be compared to a normal unlocked and S-Off device ?
Click to expand...
Click to collapse
Looking at 8064 it looks like it is. a method to confirm would be to try changing your MID and if it allows then it is ENGG hboot
Code:
fastboot oem writemid xxxxx
Please look at the forums & warnings before you attempt this
It returned an Error. Also i searched throughout the forum and seems most getvar returns this same HBOOT-8064 result so it looks like it's not an Eng Hboot afterall
please.. i need this stock rom
3.24.707.102
Here
http://forum.xda-developers.com/htc-one-max/general/stock-rom-one-max-t6-wwe-3-24-707-102-t3087475
pradeepvizz said:
Here is the RUU file name - you will need to find the way to download
0P3PIMG_T6_U_K44_SENSE60_MR_hTC_Asia_WWE_3.24.707.102_Radio_4T.27.3218.14_10.33C.1718.01_release_395549_combined_signed_2_4.zip
Click to expand...
Click to collapse
here the file you want:
drive.google.com/open?id=0B1QRy4thJUMbbUNyUDlqWWwwSTA&authuser=0
I got this device from AT&T last year. I went to htc-dev to unlock the bootloader, then I installed CyanogenMod. It hasn't been without problems but I have been relatively happy. However, to upgrade to the latest CM12, I need to update the bootloader. The most reliable way to do that is to return to stock and do the OTA.
I want to return my device to stock temporarily. I've looked through the forums and it seems like it should be possible. There are RUU available, but only for certain CIDs (not mine). The other option is to use a Nandroid backup. Apparently these are touchy. It's best to have your own (I don't), because you have to match the proper versioning or else you might have a brick. I went to check my phone information with
Code:
fastboot getvar all
and the result was strange compared to what I have seen elsewhere:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [[B]redacted[/B]]
(bootloader) imei: [[B]redacted[/B]]
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.006s
The all-important "version-main" is missing, and the baseband-version is marked invalid. I'm not really sure where to go from here. I really want to update the bootloader so that I can get the next CyanogenMod build. (It fails to install with a complaint about the bootloader version. It wants 3.18 or 3.19, while I have 3.16.
I don't really know where to go or what to do now. Advice?
(Finally, I have a custom recovery [Team Win]. My phone is currently S-On)
justine_d said:
There are RUU available, but only for certain CIDs (not mine).
Click to expand...
Click to collapse
Not sure where you've been looking, or why you think that. But RUUs are readily available for the AT&T version for every software version since release. And one of the few M8 versions that has consistently had RUUs. AT&T RUUs are listed on my Index tread, sticky at the top of the General AT&T forum section: http://forum.xda-developers.com/showthread.php?t=2751432
justine_d said:
The all-important "version-main" is missing, and the baseband-version is marked invalid. I'm not really sure where to go from here.
Click to expand...
Click to collapse
Your hboot number corresponds to software 1.xx, but it might be 1.12 (less common) or 1.58 (probably).
Restoring to stock using a nandroid is an option, but IMO more complicated than RUU. You will need to restore the stock nandroid, stock recovery, then OTA twice (to software 3.x then 4.x) in order to make your firmware (including hboot) current. Then flash TWRP and flash CM12.
For the RUU route, you will need to relock the bootloader, RUU, then unlock the bootloader (go through the HTCDev.com process) again. Then flash TWRP and CM12. But the downside to RUU is that it will wipe the phone, but that might not be much of an issue if you are a ROM flasher.
redpoint73 said:
Not sure where you've been looking, or why you think that. But RUUs are readily available for the AT&T version for every software version since release. And one of the few M8 versions that has consistently had RUUs. AT&T RUUs are listed on my Index tread, sticky at the top of the General AT&T forum section: http://forum.xda-developers.com/showthread.php?t=2751432
Click to expand...
Click to collapse
Oh, I must have been looking in the wrong place. Somehow I found myself on the other (non-AT&T specific) index.
Your hboot number corresponds to software 1.xx, but it might be 1.12 (less common) or 1.58 (probably).
<snip>
For the RUU route, you will need to relock the bootloader, RUU, then unlock the bootloader (go through the HTCDev.com process) again. Then flash TWRP and CM12. But the downside to RUU is that it will wipe the phone, but that might not be much of an issue if you are a ROM flasher.
Click to expand...
Click to collapse
Wiping the phone is not an issue for me.. So then, I just pick one (I'm leaning toward 1.58 bootable RUU) and flash it, and that's it. I think I can figure it out. Does it matter which one I pick? Anything else I should know?
Thank you!
Just checking in to say that everything worked perfectly, I am in the process of taking OTA updates now.
justine_d said:
Wiping the phone is not an issue for me.. So then, I just pick one (I'm leaning toward 1.58 bootable RUU) and flash it, and that's it. I think I can figure it out. Does it matter which one I pick?
Click to expand...
Click to collapse
I know you've already got it sorted out. But just for your info:
The only restriction on RUUs (in addition to the fact that they need to match your phone's CID and MID) is that with s-on, you cannot run an RUU that is an earlier version than is on the phone (hboot, OS number), meaning you cannot "downgrade". Seeing as you had either version 1.12 or (probably) 1.58; and the only 1.x version RUU released was 1.58, any AT&T RUU would work in your case.
This also means that any equal or greater version AT&T RUU will work. Meaning with RUUs you can even have just skipped up to the latest Lollipop RUU (software 4.28) without running any "intermediate" RUUs or OTA updating up to LP. I would have pointed this out earlier, but I wasn't sure which method (RUU versus OTA) you preferred to use.
RUUs are in contrast to OTAs, which normally need to be installed in sequence.
Thanks for clearing that up. There was definitely some underlying confusion on my part. In essence, there was no reason to flash the earliest RUU and then install the OTAs, when instead I could have flashed the latest RUU and achieved an equivalent result. Oh well, no harm (and I learned something).
I wish phones were as simple as PCs. Or rather, that phones were as difficult to screw up as PCs.
As an aside, do you have any personal favorite OS to flash to the M8?
justine_d said:
Oh well, no harm (and I learned something).
Click to expand...
Click to collapse
Very true. And in regards to doing OTAs or RUUs, you now know how to do both!
justine_d said:
As an aside, do you have any personal favorite OS to flash to the M8?
Click to expand...
Click to collapse
That's always a tough one. Its so personal. Some folks like AOSP or GPE, while some prefer Sense. Folks are looking for different features (customization, performance, etc.).
Personally, I'm not an AOSP/GPE person at all, and actually like Sense. And tend towards pretty stock ROMs, with maybe a few added customizations and performance tweaks, but otherwise pretty clean ROMs. I was on the stock Dev Edition Sense ROM for a while, than more recently SkyDragon Sense (so I could use Sense 7) and then LeeDroid.
That probably doesn't help you much , as it appears you may be more of an AOSP fan. You might check out the GPE ROMs, if you haven't already. IGPE is closer to stock Android than Sense, but should be more stable and bug-free than CM12, since its based on official HTC software.
redpoint73 said:
Very true. And in regards to doing OTAs or RUUs, you now know how to do both!
That's always a tough one. Its so personal. Some folks like AOSP or GPE, while some prefer Sense. Folks are looking for different features (customization, performance, etc.).
Personally, I'm not an AOSP/GPE person at all, and actually like Sense. And tend towards pretty stock ROMs, with maybe a few added customizations and performance tweaks, but otherwise pretty clean ROMs. I was on the stock Dev Edition Sense ROM for a while, than more recently SkyDragon Sense (so I could use Sense 7) and then LeeDroid.
That probably doesn't help you much , as it appears you may be more of an AOSP fan. You might check out the GPE ROMs, if you haven't already. IGPE is closer to stock Android than Sense, but should be more stable and bug-free than CM12, since its based on official HTC software.
Click to expand...
Click to collapse
Thanks for your input after I thought I was done, I managed to break it, fix it, break it again, and so on. I ran into a problem with receiving calls on CyanogenMod so I flashed back to Sense. I decided to shell $2.5 x 10**1 out for Sunshine S-OFF so that I could restore to any software with the RUUs. Then I just kept chasing the rabbit down the hole: SuperCID and Dev Edition. Then I tried a highly modded ROM (Viper One) to see what it had to offer. Finally I flashed back to CynogenMod because I've used it so long it feels most like home. The incoming call problem is absent in the Dev Edition radio firmware (but I've had to contend with other bugs in the past, only steady use will tell if things have gotten better or worse).
I definitely prefer the more stock feeling. The HTC Dev Edition Sense ROM was by far my favorite over either Viper One or the bloated AT&T stock software. I haven't tried any other AOSP based OS. The first time around I was content to HTCDev unlock and flash CM. I didn't even wait a week; I picked this device because I knew it was unlockable.
justine_d said:
Finally I flashed back to CynogenMod because I've used it so long it feels most like home. The incoming call problem is absent in the Dev Edition radio firmware (but I've had to contend with other bugs in the past, only steady use will tell if things have gotten better or worse).
I definitely prefer the more stock feeling. The HTC Dev Edition Sense ROM was by far my favorite over either Viper One or the bloated AT&T stock software. I haven't tried any other AOSP based OS.
Click to expand...
Click to collapse
Then you really should check out the stock Google Play Edition (GPE) ROM or a custom GPE based ROM. GPE is supposed to be a AOSP type experience, no Sense and basically like a Nexus ROM. But its official HTC software, so should be pretty bug-free in comparison to CM12. Not to knock CM12 (I love it on my Samsung Tab Pro 8.4), but I know its had its share of bugs on the M8 (at least from my understanding).