yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Questions & Answers] wingzfan:
Dependant on the T-Mobile network he's on. With At&t, if you select slot 1 (Verizon) as your data you will get nothing on slot 2 as it converts slot 2 to 2g only and At&t removed 2g from their service. This is the issue I ran into with running a CDMA card in slot 1. 2 GSM cards works fine but once you run a CDMA it severely limits slot 2. Running data on slot 2 allowed Verizon to use calling and texts fine.
[ZTE Axon 7 Questions & Answers] Flapjack:
Awesome info. Thanks so much to both of you. I still haven't had any free time to mess with it, but I will this weekend.
[ZTE Axon 7 Questions & Answers] Flapjack:
I took a ton of flipping back and forth, but finally got LTE working with your trick. I switched it back to LATE/GSM/CDMA auto, but it still says "missing or error" for the TMO SIM in slot 2. :(
[ZTE Axon 7 Questions & Answers] CuDem:
I have same problem, any one has a solution?
[ZTE Axon 7 Questions & Answers] Flapjack:
I had to RMA my phone.
[Shield Android TV General] oldshanshi:
After the final version of the 16G will continue to modify the shield upgraded to 32G. after the.128G can also be changed to 64G.EMMC5.1 may also test. With reference to the forum 3 master modification method [MENTION=7386697]Tilator[/MENTION]@Luxferro@hallydamaster Thanks..

32G EMMC5.0 write speed increased to 74M/S, the original 16G EMMC5.0 write speed is only 45M/S
[Shield Android TV General] oldshanshi:
:D
[Shield Android TV General] gutter:
None of your images load. Can you explain how to do this?
[Shield Android TV General] Ichijoe:
Most likely he resoldered the original 16Gb EMMC, and replaced it for a larger one presumably taking clues from the SSD Migration Thread(s). Which makes me wonder if he managed to successfully transfer the Security Sectors form the original EMMC to the new EMMC?
[Shield Android TV General] oldshanshi:
How to confirm the security sector no problem?
[Shield Android TV General] oldshanshi:
Remove the original 16G EMMC, read the BIN file with a dedicated device. Methods refer to the PRO version of the modified SSD. and then modify the BIN file EFI partition table, 2 locations. Will change the FRISTPART.BIN and LADTPART.BIN by the new EMMC size to write in different locations. Install back, start to do factory reset
[Shield Android TV General] oldshanshi:
If you can't see the picture, you can see this link

http://pan.baidu.com/s/1geRRay3

https://mega.nz/#!d4lX0B5T!GJz-Yr0951z9CWWIxImyva3eM8Z0v5sAzEKEIbLRhww https://mega.nz/#!YlsC3RQA!uutnGBIx0FttyGQ-L1SRuawEM6CTnLpILwTgnbA8vXQ https://mega.nz/#!1wsQADJZ!xmAlgAf43EaPqIC9RaNjaHvnb8zMDyEqAKMbEkZEy_8 https://mega.nz/#!t9VhCRZT!UBfw98cBSk861jncljgBtm5yy4dmS2QAQZ18XfGsJAY https://mega.nz/#!EgcXmaob!KGj9v_fF7Fdz8K-0QJW55M-EZICmg2HSgsdHO9edf50 https://mega.nz/#!sxdxjYZC!-hXk45OWM9D8XGXLHNESpyr_Wdis-h5XlL5Fq0cQd68 https://mega.nz/#!cpUVHDQY!zbXKx7O0tF5wzp4UXKG6ukB3jgrFDUsnUll-gDN4eE0 https://mega.nz/#!R0Mn0J5Q!TCyXpNbpfkblVS7BrYrVEsgeyL2Ac2fgA3VOfYWGQcs https://mega.nz/#!UgkEnT4Q!3nRflanWx5o8ZokUgY3f72gReuwIFk1daE3pT8CfNrA https://mega.nz/#!Fs0xiAqQ!giQVSlLO9OVEG4Sc2ZrC1zJeBGEHHMlaaHhnP1nJm1A
[Shield Android TV General] Ichijoe:
By Security Sectors I mean that the Shield TV has managed to survive being a Widevine L1 Device. You can check this by installing DRM Info (From the PlayStore). You'll either retain the L1 Status, or you'll find yourself degraded down to L3.

The practical upshot of all this is if you want to ever use, or plan on ever using either Amazon, or Netflix, than you'll need to be at Widevine L1. As Widevine L3 will not play anything at all from such services.
[Shield Android TV General] Mogster2K:
That page does not exist :(
[Shield Android TV General] Ichijoe:
It does you might have to click the Chinese Pop Up off that's hiding the link. But as hosting providers go.... I would recommend something like Image Frog.
[Shield Android TV General] Mogster2K:
Strange, it wasn't working when I posted, but it seems to be working now.
[Shield Android TV General] DummyPLUG:
That page, baidu, sometime are very slow and hard to connect, mostly when at night (china time, UTC +8)
[Shield Android TV General] oldshanshi:
Would you like to try these links?

https://mega.nz/#!d4lX0B5T!GJz-Yr095...5sAzEKEIbLRhww https://mega.nz/#!YlsC3RQA!uutnGBIx0...LpILwTgnbA8vXQ https://mega.nz/#!1wsQADJZ!xmAlgAf43...yEqAKMbEkZEy_8 https://mega.nz/#!t9VhCRZT!UBfw98cBS...2QAQZ18XfGsJAY https://mega.nz/#!EgcXmaob!KGj9v_fF7...2HSgsdHO9edf50 https://mega.nz/#!sxdxjYZC!-hXk45OWM...h5XlL5Fq0cQd68 https://mega.nz/#!cpUVHDQY!zbXKx7O0t...UsnUll-gDN4eE0 https://mega.nz/#!R0Mn0J5Q!TCyXpNbpf...2fgA3VOfYWGQcs https://mega.nz/#!UgkEnT4Q!3nRflanWx...k1daE3pT8CfNrA https://mega.nz/#!Fs0xiAqQ!giQVSlLO9...MlaaHhnP1nJm1A
[Shield Android TV General] techjunky90:
I've thought about trying this on my 2015 16gb but I think I'm just going to get a good ssd, put it inside the shield, get a USB 3.0 adaptor, cut the end off that goes in to USB port, solder the wires to the board
[Shield Android TV General] Ichijoe:
Decryption Key?! Really, is it that hard to use Image Frog?
[Shield Android TV General] bubbablacksmith:
I took his images and reuploaded them to imgur.

Here's where they are located:

imgur.com/a/chfdP
[Shield Android TV General] oldshanshi:
That site do not know how to use, is it free?
[Shield Android TV General] Ichijoe:
Ok Image Frog, was confused on my part with ImageShack. Which now requires you to login. So that's likely right out. A quick shufti for free Image Hosting on Google did however turn this up.

https://imgsafe.org

The only problem with that method though is you have to copy paste the links into a Notepad Page. If your gonna want to link to them over multiple Boards. As these Hosts tend to be more fire, and forget hosters.

On a slightly different train, you could also host those Pics from within your own Google Drive. Should you wish to retain whatever control over those Images.
[Shield Android TV General] oldshanshi:
[IMG="http://i.imgur.com/3dXRr2t.jpg"]http://i.imgur.com/3dXRr2t.jpg[/IMG]

[IMG="http://i.imgur.com/9ky6P5n.jpg"]http://i.imgur.com/9ky6P5n.jpg[/IMG]

[IMG="http://i.imgur.com/n4OdvzW.jpg"]http://i.imgur.com/n4OdvzW.jpg[/IMG]

[IMG="http://i.imgur.com/vsAYGIH.jpg"]http://i.imgur.com/vsAYGIH.jpg[/IMG]

[IMG="http://i.imgur.com/d0Nxdwd.jpg"]http://i.imgur.com/d0Nxdwd.jpg[/IMG]

[IMG="http://i.imgur.com/Q9mBFuY.jpg"]http://i.imgur.com/Q9mBFuY.jpg[/IMG]

[IMG="http://i.imgur.com/HvNcaLi.jpg"]http://i.imgur.com/HvNcaLi.jpg[/IMG]

[IMG="http://i.imgur.com/FcAWpSv.jpg"]http://i.imgur.com/FcAWpSv.jpg[/IMG]
[Shield Android TV General] Jackie393:
can you give me all partition and partition table of shield tv 2017 16gb?. thank
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Mikeapollo:
Radio confirmed in 6 dead GSM cases : 1.54.30.10

Radio stated in 5 dead GSM cases : 1.54.7

1.54.30.10 and 1.54.00.10 are known to have stability issues

Other 1.54 varients may have issues which are killing the radio hardware

As has been mentioned in other threads elsewhere and on another forum (win4mobiles) - there is presently an epidemic of GSM problems that seem to be plaguing users and either killing or bricking Hermes.

There are at least 14 cases around the Hermes area on this board now of people running a varient of radio 1.54 as their last radio then ending up with intermittent GSM or no radio - many being unable to roll back when problems start or finding bad blocks when telnetting into their phone to try and unbrick it.

I also have just learnt of another case here running 1.54.30.10 that's just died over xmas.

For technical discussion on these issues - see this thread

This is the one thing they all have in common and it's starting to look suspiciously like there may either be an issue with this radio or an issue with the radio when used on certain networks or combination of issues. Certainly, up to the 1.50 dying GSM modules was a little more uncommon and now there has been a splurge of them.

Just to remind some of the more inexperienced ROM experimenters out there - Hermes has a firmware driven radio in a custom chip and the radio images change how the hardware within the chip functions. It is quite possible for a bug in a radio to damage the hardware over time.

If the radio hardware itself gets fried then the only cure is a new motherboard, if the flash goes bad but the hardware isn't damaged then using the unbricking guide in the wiki you may be able to get some life back into it or roll it back.

So experienced users be careful until we know more, and inexperienced users please bear in mind that once you've found a radio that is good for you and works there is not much further point in trying every other radio.

Especially use caution with any versions of 1.54 at the moment until there has been more information collected about this.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] galaxys:
Good to know...I'm staying away from that bad boy! It was odd that so many were having radio issues lately. thx for the notice!
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] CRCinAU:
A little alarmist..... That being said, read this:

http://xdaforums.com/showthread.php?t=349461

Boiling it down, it doesn't seem to have any reliance on specific radio rom versions...
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] scousemartin:
Hello mikeapollo, why apollo do you live in beswick :D

Anyway back on topic ,i have upgraded to 1.54 and then down graded to 1.50 and have had no problems with either radio and i have flashed my device more times than i can remember over the last few months, so maybe i am just lucky.

What type of herme's are the ones that are being bricked hermes 100 or hermes 300?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] eagercrow:
mine died way before I upgraded to the 1.5x radio, I believe it first started showing problems with 1.38, or 1.4something.

I don't think it has anything to do with the radio, simply people upgrade, hoping the latest and greatest radio will solve or help their problems. Then the radio completly dies and they are stuck with the last radio flashed.

If the latest radio was 1.12, I think you would see the same thing happening.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Ree-shar:
Well, there is an implication from that thread that the problem is 1.54.xx based.

But the core of Mike's post is that programming/reprogramming radio ROMs is not the same as flashing the OS. The radio ROM drives the radio output directly so if it accidentally sets too high a level then it can be like turning up your home hifi amp too high. And just like your home hifi, you can blow it up.

So being more cautious with radio ROMs is sensible advice. If a radio works for you don't go seeking even better performance because that "better performance" might be at the cost of increased gain and eventual failure of the radio hardware.

Incidentally, my son works in radio design and tells me that radio circuits are very sensitive to heat and can be damaged by overheating.

Richard
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Mikeapollo:
LOL! Went to school in Beswick - but given the Apollo is in Ardwick... :D

It's a nickname that just stuck from yonks ago during a more theatrical time of my life.. (and I live in Moston now).

From what I've cross referenced so far, 3 deaths have been Herm300 and 1 was stated to be a Herm200.

I'm trying to collate as much info as possible on this to find out if there is a definite correlation between this radio and certain models/networks/areas,

We've had dodgy radios released before but never a potential "suicide-bomb" radio hence my interest - (I'm still on 1.43 here with over 500hrs talk on the life timer and it's still going strong:eek:).

<conspiracy> On the other hand... Could 1.54.x have leaked out to help sales of the TyTN II ;) </conspiracy>
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] KarhU:
Man, this should be put to the wiki or to the every new Radio ROM thread.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Mikeapollo:
Updated the wiki page with general advice.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] gnahc79:
I have been using 1.54.07.00 pretty much since I got my 8525 a few months ago and haven't any issues...yet :). I flashed the 1.54.x radio when I tried out the official AT&T WM6 ROM, but since have been using schap's ROMs (no radio update). My question: is the official 1.54.07.00 radio from the AT&T WM6 ROM the same as getting a 1.54.07.00 from elsewhere?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Mikeapollo:
Yes. The official AT&T 1.54.07.00 will be identical to the extracted 1.54.07.00 as thats where it was extracted from - the clue is in the numbers :D

Also, if you are using the official radio update for your device on your network you should nothave nothing to worry about - and of course if it turns out there is a problem with this bit of firmware you'll be well covered by your network & waranty anyway.

Incidentally, quite a few people who have suffered the mysterious sudden "NO GSM" death problem can still boot their phones to the OS but generally have been unable to re-flash the radio so in the event of death it still seems possible to "roll back" the OS ROM to "the proper one" for waranty reasons <ahem>:rolleyes:
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Mikeapollo:
Further update - possible resolution to try if you've having intermittent problems and a very long theory posted here

In short - My thinking is if there is a bug in this radio it will be something to do with the PIC16LF72 chip with the D/A and A/D stuff that drives and measures outputs from the phyiscal hardware radio chips (the Qualcomm ones and the Anadigics amplifiers) on the main mobo.

A small firmware bug affecting values returned from D/A and A/D measurements

This bug or whatever causes either false return values or bad data

This causes radio to work harder

This then either causes wear or heat based issues on the PIC effecting the storage area and causing bad blocks (death) or causes damage to the rest of the radio chipset (qualcomm and anadigics amps).

PS. If any tech support desk needs a bum on seat in either North-West or the South East of the UK - I am now OFFICIALLY AVAILABLE FOR HIRE as I'm officially unemployed from tomorrow morning! I don't have a degree so never get through the paper sift (hence unemployed) but do have the experience and skills and plenty of developers certificates..I-thank-you.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] timbouk:
Mike,

Heres another UK Tmobile Herm 300 thats Died :rolleyes:

For the record this phone was brand new on 17th December 2007; only been flashed once to the official T-Mobile WM6.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Mikeapollo:
God they're dropping like flies! Sorry to hear about that :(

Bit concerning though as IIRC the TMUK rom is radio 1.50 but that's the 3rd report of someone having problems introduced by it. (will have to pull the .nhb apart and check). Cheers for the tipoff.

I fear the Hermes will soon be an endangered species - must be a marketing plan by HTC to flog the kieser :D

Edit :: durr - of course it's radio 1.50 - even your sig says that - I'm rebooting my braincell as I type :o
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] timbouk:
Yes, its the 1.50 (My signiture has correct details)

Not sure if this is worthy info; but at work one side of my building has a very low signal strength, so the radio works very hard to keep up the connection. I can tell it is as my battery can be virtually flat after, say, 6 hours!

Maybe its poor signal areas accelerating the radio deterioration?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Prerna:
I got 1.50, and I still have occasional issues, such as hardware buttons that stop functioning.

What other radio could possibly be safer? Maybe 1.43 or 1.47. I kind of remember they used to serve me well.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Prerna:
Would be glad to propose you such offer if I could... In the mean time, you definitely should post the same in the main section, given most viewers here are in the tech industry.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] vpsreejith1:
im using the 1.54.30.10 for last 2 months and its workg absolutely fine!!!!!!!!!!!!!!!!!!
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] dominicong:
I have flashed the latest Radio 1.54.30.10. One day, I made a phone call. One of my staff acted so strange and I asked him what happen????

He passes me his earphone while he is chatting skype with his buddy.

:eek: I got a shock because my phone conversation can be heard from his ear phone.

I made a test and I flashed back from the older radio version: 1.41.00.10.

I made a phone again and ask him if he can hear my phone conversation or not.

He replied me no.

I will stick to this old version of radio. Did someone have the same incident?

Can someone explain why this can be happen?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] yurz:
oh no..I posted in the other thread and was given the impression that the radio chip might not be the culprit..which was reassuring. But now it seems I could be replacing the motherboard. I'm from Brunei and my Dopod 838pro just went dead while it was still on it's original WM5 rom. I flashed it with HTC official rom (I think it had radio in it) and it worked but only for 2 weeks and went dead again. Now when I tried to reflash it would stay at 12%. Question is..where can I get it repaired and any idea how much it would cost ? Nearest country I could send this would be Singapore,Malaysia,Thailand or even the UK....but where ?Thanks.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Mikeapollo:
It does work fine for a lot of people - however, itpotentially also is linked to a number of failures in some European countries - particularly cases have been reported in UK, Germany and Netherlands but there is no concrete evidence yet however looking ever deeper into the issue, it would seem that in most circumstances the phones that died while using 1.54 were :

* Used in areas of variable / poor reception

* Regularly switching to and from the Edge network.

* They were slow deaths - working fine for a while then suddenly dying for no reason

* Most struggle to be reflashed (radio bootloader damage) or report bad blocks when probed (intermittent problems)

* One or two in early stages of death have been recovered by multiple radio flashes - Most though were completely unrecoverable.

* Many users who rolled back after experiencing unexpected hardware isues whlie running radio 1.54+ found that rolling back to a known good radio did not cure the symptoms that started after trying 1.54 indicating a level of hardware damage possibly instigated by firmware.

If you read my long post in the sudden radio death syndrome thread - you will see a few technical reasons why things might fail for some and not for others.

As ever - the best advice is to just experiment cautiously, don't fix what isn't broken, look out for any unusual behaviour when trying new radios and most of all, remember that higher verion numbers do not always mean something will be "better" for your particular situation. Radios don't conjour up a signal where there isn't one - they just affect how the signal is processed by the hardware and how the hardware and firmware interact.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Mikeapollo:
Unfortunately, if it's getting stuck at 12% on a full ROM it does sound like there is a radio bootloader problem as that's about the point where the radio itself gets flashed. Would also get stuck when trying to flash a radio only upgrade.

As for repair, because it's Dopod branded it's unlikely HTC in the UK will repair it. However, have you tried banging an email to dopod themselves to seek their advice? <there is a contact button on the top of that page>
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Hyins:
Mikeapollo talks too ***** much ~

Moderation Edit:

Hyins - watch your language, don't be rude and constructive posts please.

Some members may be used to the kind of post you made above, but others have formally reported the post as unacceptable.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Mikeapollo:
Thanks for your input... So you've gone through the hardware specs of the chipsets involved in the radio, referenced the datasheets, cross referenced dead radio cases looking for trends, approached a couple of networks, and posted your results have you?

No... Thought not. The reason I talk so much is because I'm researching a problem and posting my responses/suggestions and solutions which may help someone. Not just posting thank yous (which appear to make up the bulk of your posts). I thank people by donating cash, time or resources and try to help others out where I can by pointing them in the right direction to find solutions to their problems on the way... And if you check the timings of my posts you'll see I spend a limited "block" of time here at the weekends usually overnight. I don't live on the board...

I usually stay fairly dorment until I'm actively involved in a topic. This is one I've taken on board, most of my posts are within 2 threads relating to this issue while I've been cross-referencing cases.

Why do I normally stay fairly dorment most of the time on this board...? Purely because of idiots like you that have nothing constructive to add and to avoid getting involved in flamewars.

If you've got a problem with my posts or have something unconstructive to say, then send it to me by PM rather than clogging up threads with pointless junk. End Of.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] F2504x4:
Ahh wheres the ban hammer? Seriously!!!!

or can the admin at least turn his name to Pink lettering ? :D

Mike thanks for your time and info on many threads that I have been reading here, do not let this idiot dissuade you from what you do.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] F2504x4:
did a search of his postings, it looks like all he can ad is...cool...thanks...etc etc...

not really..
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Mikeapollo:
LOL! - I don't think it's a banning offence, it's a public forum and people are allowed to judge and pass comment even when their comments may not be appropriate. It's all part of the forum experience ;)

People like that don't dissuade me - but they do get my back up as surely it takes more effort to post something unconstructive than to just stay silent :D
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] copden:
radio 1.54 problem

I start having problem with 8525 a week after i use 1.54,,my wifi keep on and off. anyone have any stable radio (1.47 or 1.48) please post up

thanks you
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Mikeapollo:
The radios are available for download here.

If you're having wifi problems though - these will NOT be fixed by radio updates as radio updates do not change the wifi or bluetooth stack.