yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo General] liquidburns:
Im seriously in love with the droid but after checking out the specs of the Sony Z3 then playing and holding one, Im wondering if I made a bad decision. I kinda just rushed into the upgrade, I've been using a droid ultra for so long and loved it so I figured the upgrade would be even sweeter. My girlfriend got an iPhone 6 and wanted me to get one too so we can have a secure end to end conversation when I'm out of town but I can just do that from my iPad. So my phone gets here tomorrow and I was actually considering taking it straight to the Verizon store and exchanging it for a Z3v but what do you guys think. Are you loving your phones enough that the slight battery and screen improvements are worth the width and girth of the turbo over the slender sexy IPS water resistant up to 30 minutes Sony Z3v? The waterproof rating is tipping the scales for me but maybe Ill try it for a few days, if I hate it I think I have up to 14 days to exchange. Also No wireless charging or DLNA from the droid turbo COM' ON MAN!!!!
[Verizon Motorola Droid Turbo General] crowax:
Can't really say since I haven't seen a Z3, but I love the turbo and it does have wireless charging.
[Verizon Motorola Droid Turbo General] cold21blooded:
It has wireless charging and dlna
[Verizon Motorola Droid Turbo General] adrynalyne:
It has miracast, not DLNA. That said, DLNA can be added with an application.
[Verizon Motorola Droid Turbo General] fatasian:
Wireless charging lol. Dat turbo charger.
[Verizon Motorola Droid Turbo General] thegrants82:
Z3v better in everything
[Verizon Motorola Droid Turbo General] liquidburns:
Seems like most people are pro droid turbo, so DLNA is covered with an app which is comforting as well as the reminder that turbo chargers and a massive battery means the phone wont really spend much time resting on a wireless charging mat. But damn dat V3 is freaking sexy.

[IMG="Z3v"]http://cdn2.gsmarena.com/vv/pics/sony/sony-xperia-z3v-1.jpg[/IMG]
[Verizon Motorola Droid Turbo General] Apsalus:
The Sony Z3v is a hybrid between the Z2 and the real Z3. It's heavier and fatter than both. It has a bigger battery than the Z3 (3200 vs 3100), but does not last as long as the Z3 according to its specs. Its camera is also more or less a tweaked Z2 camera AFAIK.
[Verizon Motorola Droid Turbo General] liquidburns:
Yea that solidifies my choice, I'm sticking with my droid turbo when it gets in tomorrow. Im sooooo excited now, I don't know why I freaked out at the last second. I guess its because I usually comprehensively research all the choices before I buy a new phone and I loved my Ultra so much I just figured on paper the turbo was going to be more of what I love so I didnt look at anything else. Then I held the new moto X with bamboo, then I got my hands on a Nexus 6. Then I got my hands on an Z3 (admittedly not the Z3v so I didn't know it was suckier than the Z3)

I really came away impressed with the Nexus 6 and Moto X, but I'm more about substance so I think I'm going to love the Turbo although the former two options are so sleek and sexy but admittedly too freaking large in the sense of the Nexus 6. The turbo feels like it would be a better fit even though its larger than the Ultra. But I loved my ultra soooooooooo much. Another plus is that if the screen breaks in the first two years from accidental drops you get a free replacement. After just reading that a few hours ago Im totally sold. And I don't even know why I'm paying $11 a month in insurance now, I guess in-case someone steals my phone but still that's a pretty bad ass guarantee from Motorola. I think Im in love with Moto all over again. :)
[Verizon Motorola Droid Turbo General] zed011:
Z3 seems like a fragile phone to use if you don't use a case. That's one reason I avoided it is because it seems like the back glass is fragile and cracks easily when it is handled carefully. It's a slippery phone as well. I don't like sony's post processing on images, kinda noisy. Z3 has the looks going for it but I don't see much else.
[Verizon Motorola Droid Turbo General] adrynalyne:
It doesn't last as long as the Z3 because its on Verizon and using CDMA.
[Verizon Motorola Droid Turbo General] adrynalyne:
Silly statement. I know for a fact its not better in battery life. I am sure I can find other places.

http://www.gsmarena.com/battery-test.php3
[Verizon Motorola Droid Turbo General] zathus:
Look at 99% of his posts. There all ridiculous. He clearly is not a fan of the DT but spends most of his time on the DT forms.
[Verizon Motorola Droid Turbo General] ria4life:
I just swapped the Z3 for the Droid Turbo.

I previously had the tmobile Z3 which felt great in the hands...the verizon Z3 is significantly thicker that the tmo version. It generally felt bulky being that i came from a slimmer model.

The Droid Turbo feels great in the hands

I got the ballastic nylon and haven't regretted yet. Great battery life and feels good in the hand.
[Verizon Motorola Droid Turbo General] YoungAceAtlanta:
The Turbo is a great device.. But if you're into flashing Roms and adding a bunch of tweaks to your device then you made the wrong choice with both. Both devices are locked down and no sign of root to be seen.. Or even lollipop for that fact anytime soon.

But its a great device I prefer it over the Z3v.. You're getting a better device in my eyes..
[Verizon Motorola Droid Turbo General] gordonzhao:
Moto maxx if you're on a gsm network. Had the turbo, sending it back since I got the maxx in. It's so bs that vzw has moto connect locked down, I can't use it unless activated on vzw, but everything else worked. Using on tmobile
[Verizon Motorola Droid Turbo General] gqskrub:
If you're looking for root, you chose poorly.
[Verizon Motorola Droid Turbo General] vcolon12:
You'll be happy with the Droid Turbo. Just be prepared for the long waits to upgrade to lollipop and other updates. It is a Verizon exclusive and may be held up longer for testing prior to releasing the upgrade.

:) my2cents
[Shield Tablet Q&A, Help & Troubleshooting] Reis:
Hi

After the upgrade using full zip, I'm not able anymore to detect my 5ghz Wi-Fi. From my other devices everything is fine pinky my tablet is not showing it...

Even choosing the option to show only 5ghz networks I see every network except 5 ghz...

Help?!

Thanks
[Shield Tablet Q&A, Help & Troubleshooting] Reis:
nobody?
[Shield Tablet Q&A, Help & Troubleshooting] t1mz0r:
Pretty sure you're not the only one with this problem. Check out this thread: http://xdaforums.com/shield-tablet/general/5ghz-wireless-detection-lollipop-t2945899
[8525, TyTN, MDA Vario II, JasJam ROM Development] Cuivienor:
Hey all,

I am posting this as an independent thread to be sure it gets some visibility. If an admin judges it should be put into the main LVSW thread, then he is welcome to move it within the LVSW thread. However I'm pretty sure I stumbled onto something that can prevent a lot of pain for some people.

Here is the scenario which occurred to three different people:

- SuperCID device.

- LVSW full version is installed with no problem => SPL 1.09

- Downgrade to any Official ROM using the provided normal RUU. Flashing goes 100% fine, not a single problem

- But upon reboot, we have a brick: Corrupted CID, SPL 1.09, No GSM, and depending on the Official ROM flashed KITL or no KITL (if the former, recoverable through hours of work with Platform Builder, if the later, unrecoverable). Since the flashing went 100% fine, that's weird, to say the least.

This same identical scenario has generated three bricks thus far:

- myself, repaired after a sleepless night spent on Platform Builder (my gratitude goes to Allan's most excellent post)

- lebogus, complete brick, no KITL, unrecoverable

- otto26, KITL, recoverable with Platform Builder

IMHO, three cases like that is too much to be a coincidence, especially after a 100% problem-free flashing of an official ROM.

Therefore, to anyone wishing to downgrade from a full version of LVSW (with SPL 1.09), he should make sure that before downgrading, he replaces the 1.09 SPL with Olipro's Hard-SPL to be sure that even if this scenario repeats itself, he doesn't have to go through Platform Builder.

I hope this thread won't be judged to be abusive and misplaced, if so I apologize.

Anyway maybe this will help someone.

Cheers

Yannick
[8525, TyTN, MDA Vario II, JasJam ROM Development] jcespi2005:
I don't think this thread abusive, but can help noob users. Really the HardSPL must convert in "the standar" for upgrading to WM6 in cooking. If someone cook any WM6 ROM, HardSPL must be part of package...

So thanks for your advice.
[8525, TyTN, MDA Vario II, JasJam ROM Development] mrvanx:
Heres a quick guide to flashing HardSPL to help users on the way.

;)
[8525, TyTN, MDA Vario II, JasJam ROM Development] jcespi2005:
Goooood work, man.....

Now lets the cookers to include HardSPL into his cooked ROMs to get the maximun protection against dead hermes...
[8525, TyTN, MDA Vario II, JasJam ROM Development] jasjamming:
Dears,

Black 1.2 now comes bumdled with Oli's 1.13.Oli Hard SPL for securiry measures and to avoid bad block problems.
[8525, TyTN, MDA Vario II, JasJam ROM Development] jcespi2005:
This is the correct way.... thanks :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] Olipro:
I think you're talking out your bloody arse frankly.

I have no idea how you managed to **** up your radio, but that's what you've done, something definitely went tits up and I don't really think it's lwvs's fault unless he disassembled the radio and edited the bloody thing to deliberately corrupt a flash
[8525, TyTN, MDA Vario II, JasJam ROM Development] Cuivienor:
Thanks for letting me know :) I was just pretty unsure of where to put my message and whether it deserved a full-fledged thread...

Anyway I'm glad this can be of help and I hope it won't disappear too quickly into the depth of this forum (not at least until LVSW includes Olipro's bootloader...)

Yannick
[8525, TyTN, MDA Vario II, JasJam ROM Development] LegolasTheElf:
I'm going to post a rom of lvsw 3-20 that includes oli's 1.13 BL and the OS with extra ram ONLY. No radio, no IPL, no extrom. hang tight, I'm uploading now :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] Cuivienor:
OK if so I'm sorry. It's just that three apparently successful flashings of official ROMs ending up in bricks look strange to me. Maybe it's theoretically impossible and it must mean that there was some external reason. But you have to admit that three times the same scenario within the last 2 days is an improbable coincidence.

I am not blaming lwvs by the way, his ROM is most excellent, I loved it, but needed to downgrade because of a problem I had with some of my software (WM6's fault, not lwvs's).

As said, maybe it's a completely external reason. Who knows? What I care about is that I noticed it happened following this scenario several times in a very short span. Make what you will out of it.

Just see it as a warning, and anyone is free to do as he or she wishes.

Cheers

Yannick
[8525, TyTN, MDA Vario II, JasJam ROM Development] mrvanx:
URL please for the wiki ?
[8525, TyTN, MDA Vario II, JasJam ROM Development] jcespi2005:
Thanks for your work.. sure this help more than one...starting with me :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] jpvdp:
I had exactly the same problem, going from lvsw to an older official wm5 rom.

All went fine, 100%, reboot and NO GSM.

Recovered with KITL.
[8525, TyTN, MDA Vario II, JasJam ROM Development] LegolasTheElf:
@jpvdb Did you install OS only, or the full package?
[8525, TyTN, MDA Vario II, JasJam ROM Development] mrvanx:
Gotta ask, when downgrading to WM5 obviously this will flash a new SPL, Radio and OS to the device correct?? Because by the sounds of it people are using the full RUU package and not splitting into seperate nb files)

So firstly if it is 1.09 this WILL NOT be downgraded, and if the radio being flashed is of loader 0107 could this be the reason?

Since Most people now have a radio version with loader 0108 this might be the reason behind it??

If im GROSSLY incorrect please correct me right now (im after some of that olipro charm!!!! :D)
[8525, TyTN, MDA Vario II, JasJam ROM Development] mfabre:
I've done the downgrade twice without any problem. I am now back to 3-20 version. In case it helps to identify the problem, I have used Hard-SPL every time and I have flashed the different components separately.

I stayed with radio 1.35.00.11 and I only flashed the different OSs (extracting them from original ROMs when needed). No problems at all.
[8525, TyTN, MDA Vario II, JasJam ROM Development] LegolasTheElf:
New ROM download!

I have created a lvsw 3-20 that installs ONLY Oli's 1.13 BL and OS with Extra ROM Storage ONLY!

Get it from here:

http://rapidshare.com/files/22731195/lvsw3-20.with.oli1.13.and.os.with.extra.ram.only.rar

** Please note, if you already have Oli's 1.13, choose 1.11 and HARD. **

** Thanks goes to the_passenger for creating the extra-ram version of the OS! Works like a champ on my two devices :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] Cuivienor:
@mrvanx: correct, we are talking about full upgrades and downgrades. Your point is pretty interesting by the way, and it seems that mfabre's case goes in the way of this theory. But indeed you should wait for Olipro's expert opinion :)

@LegolasTheElf: talk about reactivity... You rule, man!
[8525, TyTN, MDA Vario II, JasJam ROM Development] LegolasTheElf:
Already done! :D
[8525, TyTN, MDA Vario II, JasJam ROM Development] mrvanx:
I think it is a tad premature to announce that there is a problem with the LVWS ROM sir. It is more than likely that the problems experienced are due to people trying to reflash an old SPL, and a radio with loader 0107 (which CANNOT be downgraded).

I would recommend removing the line from your sig since we have only reports of THREE cases of this happening. We dont want to cause alarm to people who have been running this ROM without any problems.
[8525, TyTN, MDA Vario II, JasJam ROM Development] LegolasTheElf:
Flashing an older radio is no problem. 0108 just isn't downgraded.

Old SPL's aren't a problem. It just wont downgrade (unless you know how).

Radio is the only thing that can cause bricks in this equation. It's definately that.

And lvsw says that he modified the radio! It's a bad mod.. I'm sure he tried as hard as he could to make it perfect; his OS is awesome! But, the radio is causing problems.

Besides, this will get you the 1.13.Oli which will prevent bricks, and give you an extra 10MB of ROM. It's all good.
[8525, TyTN, MDA Vario II, JasJam ROM Development] Cuivienor:
Four with jpvdp. But I agree for all we know it could be another problem...
[8525, TyTN, MDA Vario II, JasJam ROM Development] LegolasTheElf:
Bottom line is this:

INSTALLING OLIPRO'S 1.13.OLI BOOT LOADER IS THE SINGLE BEST THING YOU CAN DO TO PREVENT BRICKS!

My LVSW upload INCLUDES the 1.13.Oli Boot Loader.
[8525, TyTN, MDA Vario II, JasJam ROM Development] Cuivienor:
hahaha correct LegolasTheElf!
[8525, TyTN, MDA Vario II, JasJam ROM Development] jcespi2005:
Perhaps it is premature, but i'm rigth if i put people in way to make better ROM, and i think put HardSPL is a good idea.

There is the better idea can extract on this thread, not the bad or less bad ROM, but how to make better and secured ROMs.

EDITED: Take a look at http://xdaforums.com/showthread.php?t=299564 Seems like LVSW put HardSPL in his new ROM. Good idea ;)
[8525, TyTN, MDA Vario II, JasJam ROM Development] Olipro:
I compared the radio and SPL from lvsw and guess what? they're identical to the retail ones

therefore, one can only assume you're not doing something right or your Hermes is screwy... I suggest this thread be deleted, it's misinformation of a very worrying and dangerous kind.
[8525, TyTN, MDA Vario II, JasJam ROM Development] shogunmark:
out of curiosity... has anyone tried to load the 1.01MFG bootloader on their device prior to flashing the OEM rom?? i bring this up cause i wonder if it has something do to with the oli bootloader??? Not cutting on oli as he has done wonderful things for us, but if there is a flaw with it somewhere then we need to find it and fix it.... anyone willing to risk their device to try this? :D
[8525, TyTN, MDA Vario II, JasJam ROM Development] Cuivienor:
I'll just repeat myself. At least I'm not trying to mislead people or anything. I'm just seeing what happened to several people (not just me). People assumed the radio was wrong you proved it wasn't. We don't know if this WM6 ROM is directly connected to the problem or is its indirect cause or is not related whatsoever, a reaction of the device I don't know... and again I don't care.

I'm just seeing that a certain sequence of events caused several bricks within the last few days whereas this sequence of events shouldn't have. It may be wrong or misleading to mention LVSW, but I think censorship is worse in that there is a non-negligible chance that my thread will prevent bricks. I'm reporting what happened, and people draw the consequences from that or not. They're intelligent enough to do that on their own. If you want to delete this thread then I want you to realize that it is a form of censorship.

You don't agree with whatever is written in there. You have a lot of expertise to back that up. FINE! You made your point. Your opinion backed by a lot of technical expertise, etc VS my layman report backed by nothing but observations available in written form in this thread and the bricked Hermes thread. People can choose.

Finally the whole point is moot now with the release of LVSW 03-25. Your Bootloader rules, and I'm sure you're the first one to admit that putting it on the Hermes if there's any intent to flash ROMs is a Good Thing (tm).

Cheers

Yannick
[8525, TyTN, MDA Vario II, JasJam ROM Development] Halldor:
I agree! I started to sweat and this seems to have no merit at all.
[8525, TyTN, MDA Vario II, JasJam ROM Development] pof:
@Cuivienor: I just flashed lvsw 20070320 including it's 1.09 bootloader and radio, then went back to older WM5 rom. I had no problem at all.

What I think, is same problem as when the SA 1.35 rom was released: bootloader 1.09 is a very good brick-maker... and lvsw included this SPL in his rom, so more chances of bricking with 1.09 than with any other bootloader.
[8525, TyTN, MDA Vario II, JasJam ROM Development] Cuivienor:
@pof: You probably are right. Thanks for doing this on your side as well.

It's just that I still don't get how a successful flash can lead to a brick (actually several successful flashes to several bricks as I've been roaming in the brick thread for the last 2 days).

Maybe I cried wolf too early I don't know, but if it were to be done again, I would do it again simply because too many coincidences may mean something, and they didn't just jump out of my own imagination.

Anyway thanks again for trying the thing yourself and I can only praise LVSW for his hard work and his latest ROM.

Yannick
[8525, TyTN, MDA Vario II, JasJam ROM Development] jpvdp:
Seems there are quite some "defensive" reactions to this.

Really I think nobody is trying to flame the lvsw rom or anything.

Just strange it happened to 4 people.

I did use a full wm5 install, guess that was wrong, but I am sure others will do in the future, isnt some sort of warning about that in place then?

Anyways, as far as I can tell the ts only wanted to put a warning out..
[8525, TyTN, MDA Vario II, JasJam ROM Development] ach2:
I'm probably going to get flamed a bit here for not reading the rest of the thread, but... 3 friends upgrading ok then downgrading and producing 3 bricks is a bit of a coincidence... Usually friends feed from each other so the less experienced copy the most experienced (or adventurous)

Can you remember EXACTLY how you all downgraded and on what phones? There must be a common denominator. I've done this a few times (WM5 to WM6 and back) without problems.

BTW, Your thread isn't abusive, it's obvious you've done some reading and experimenting , and have expressed the results well:)
[8525, TyTN, MDA Vario II, JasJam ROM Development] Cuivienor:
@ach2

As far as I can tell, we four (yeah it's up to four now) are not especially friends (we don't know each other, it's just the bricked hermes thread (and one in this thread) which are a testimony to those bricks).

To tell you *exactly* how I downgraded: I downloaded the French Qtek ROM from the wiki (1.18.256.2), connected my device with ActiveSync 4.5. I double-clicked on the exe, followed the steps as usual (next next update) and the flashing went perfectly fine (with the Qtek installer even going as far as telling me the flashing was successful).

I thought it was until I was blocked on the WM5 startup screen and No GSM, CID corrupt. This on a previously SuperCIDed HTC TyTN HERM200.

One of the others (lebogus) did the same, from what I gathered: same device, one of the wiki's 2 French ROMs (not sure which, presumably the Orange/Vodafone 1.23.163.5 one because it didn't have KITL activated and I am SURE the Qtek ROM has it), same method of downgrading. Successful, but brick nonetheless.

Still one of the others (otto26) used the German HTC ROM (1.18.257.2) from the wiki, on a HERM200 device (presumably an HTC TyTN as well since it's Germany, but it would have to be asked). Again flashing successful but brick anyway.

I don't know what ROM the last one used (jpvdp) but as far as I can tell, same method of downgrading. Since he reads the thread, maybe he can give us more details. You guessed it, 100% successful is a brick.

That's about it

Yannick

PS: for more details, pages 71 to 77 of the bricked hermes thread
[8525, TyTN, MDA Vario II, JasJam ROM Development] ach2:
Normally I'll support Olipro and LegolasTheElf because I think they're gods (like Hermes himself, or at least his dad:) ), but on this ocassion I think they're wrong to call for this thread to be closed...

@Cuivienor - Sorry, when you were talking about 'friends' I imagined people you knew with the same phone, not other forum members.

I can only think that if the flashing process (WM5 to WM6) and re-flashing process (WM6 to WM5) was identical then something in the pre-conditioning (ie, in-between flashing and re-flashing) was different.

What were the bootloaders just before flashing? I ALWAYS check this before an upgrade or change because I have overwritten the SPL in the past and want to make sure I have one of Olipro's BL's before upgrading.

Anyway, this is a bit moot at the moment because there are 4 bricks out there which need (or needed repairing) so maybe we concentrate on that for now.

4 similar (but not necessarily identical) flashing processes have caused bricks (out of the thousands of successful flashes). This doesn't mean that the ROM is faulty, but may mean that our descriptions of the process with which we flash are not specific enough. However, it also doesn't mean that the ROM is perfect, there MAY be certain times when (even if only a small percentage) that the ROM causes the problem. If we ignore the few times then we become like M$ where an accepted failure rate is ok as long as it's small enough.

Please don't close this thread because we may actually discover the root cause of these bricks - even if it is '****wit' errors (sorry Olipro - like the phrase:) )
[8525, TyTN, MDA Vario II, JasJam ROM Development] Cuivienor:
Isn't it "****tard errors"? :D

Anyway for the four of us it was the LSVW WM6 full ROM installed, therefore SPL 1.09. At the time when I downgraded I thought SuperCID was protection enough and since I was flashing an official ROM on a laptop (so no risk of power shortage) I was OK. And I was "right" since the flashing went "successfully"......

Anyway for all of us it was SPL 1.09. As pof suggested earlier in the thread it might just be the fault of SPL 1.09, which is as he said "a very good brick-maker". Pof himself tried the full upgrade and downgrade, and his device didn't brick.

If you need any more data about it, go right ahead and ask

Yannick
[8525, TyTN, MDA Vario II, JasJam ROM Development] shafez:
This exactly what happend to me too.

Now I am stuck with my Jasjam not working in my drawer.

Thanks and Regards