yashsingh1/xdaforums huggingface dataset:
[Verizon HTC One (M8)] shojus:
+1 Can we use the recovery for the other variants or we just now have S-Off? Thanks

I guess this should be moved to Q&A
[Verizon HTC One (M8)] Sonic2756:
You might be able to use a recovery from the sprint variant, but I'm not sure.
[Verizon HTC One (M8)] sorcerer86:
What about root? Is it permanent?
[Verizon HTC One (M8)] Sonic2756:
If you do it from recovery, yes.
[Verizon HTC One (M8)] MultiDev:
Once you are s-off, you don't need weaksauce anymore.

Just flash su through a custom recovery like you would normally do when rooting an android device.
[Verizon HTC One (M8)] sfreemanoh:
Not that there's a custom recovery for the VZW M8 yet...
[Verizon HTC One (M8)] sorcerer86:
What if I don't want custom recovery? I come from a long line of Motorola devices, I'm use to just rooting and I'm done. I don't need/want custom roms, just want full root.
[Verizon HTC One (M8)] lucky_strike33:
Then you don't need s off. Just use weaksauce for root.

My All New One
[Verizon HTC One (M8)] sorcerer86:
Weaksauce isn't full root, or I guess it doesn't allow write to system anyway... that's what I need. I want to use adaway....
[Verizon HTC One (M8)] steelersmb:
You can install Xposed and use minminguard. It works great.
[Verizon HTC One (M8)] lucky_strike33:
Look up Xposed installer. There is a thread about what works with Xposed. I think I saw adaway was being used

My All New One
[Verizon HTC One (M8)] sorcerer86:
I've been using xposed for a while. Didn't notice that module I guess...

Ill ckeck it out. Thanks.
[Verizon HTC One (M8)] steelersmb:
The module is no longer being worked on but so far, it's been working for me still.
[Verizon HTC One (M8)] scotty1223:
this thread should answer most of your general java card questions. ill bring it over here as well in the next couple days since sonic has a new card :)

http://xdaforums.com/showthread.php?t=2441299
[Verizon HTC One (M8)] Mike02z:
Is HTC ModSource Sonic? I would assume so given the CO address. Might have to send my phone to him :)
[Verizon HTC One (M8)] steelersmb:
My question is, how much support for custom ROM's and kernel's are going to be around with such a limited number of people being able to do this?
[Verizon HTC One (M8)] scotty1223:
support thread is live

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

i cant speak for sonic,but in the past he has been willing to do a couple dev phones for free. i wouldnt worry too much about support... either a software exploit will be found,or more folks will get tired of waiting and use his service. either way,there will eventually be support.

i have used his service as well. there is no disasembly of your shiny new phone,and he is trustworthy individual. as long as you also pay for enuff insurance youve nothing to lose but a few days away from your new baby :D
[Verizon HTC One (M8)] shojus:
I already miss mine as I sent it out today... :( lol
[Verizon HTC One (M8)] ed-flip:
Sending mine out tomorrow. :laugh:
[One (M8) Q&A, Help & Troubleshooting] lunercrab:
Ok so I know there was a thread started on this awhile ago...but I noticed on my one that my speakers seem extremely blocked...would u exchange if u were me? I don't think it's supposed to be like that correct? Also I'm unlocked...does att ever bother checking that stuff if I want to exchange?
[One (M8) Q&A, Help & Troubleshooting] jaythenut:
mine was the same a quarter on top and half on bottom took it back to store and got a new phone opened it up and was the same:(

if you hold the phone to the right you can see there are not blocked

hope that helps a bit
[One (M8) Q&A, Help & Troubleshooting] lunercrab:
Yeah that's what I was afraid of that it was just a common issue...maybe I'll go by and look at the display for comparison...
[One (M8) Q&A, Help & Troubleshooting] jaythenut:
heres mine
[One (M8) Q&A, Help & Troubleshooting] chaps:
Mine is the same. By same, I mean EXACTLY the same, with the exact same holes blocked and unblocked. I'm not concerned though. it still sound fine. Maybe this is normal?
[One (M8) Q&A, Help & Troubleshooting] lunercrab:
Yeah I never remembered it I've owned 3 M 7 over the past year and never saw that before. I may still exchange it because I notice there's some lag and my bottom buttons aren't very responsive
[One (M8) Q&A, Help & Troubleshooting] sixstring:
The speaker is only under a part of the cover.

Check the ifixit tear down.

The other "unblocked" holes are the mic {on bottom) and notification led (on top}.
[One (M8) Q&A, Help & Troubleshooting] GuestK0062:
Well this is because it's NOT a defect, it's made that way, speaker is only under the left side of the grill, on right are other components underneath, so it looks blocked, it's not. :fingers-crossed:
[One (M8) Q&A, Help & Troubleshooting] Traceamount:
For sure. The speakers are only half the length of the grill, if that. Hah nvm pics have been posted :)
[One (M8) Q&A, Help & Troubleshooting] lunercrab:
Yeah thanks guys...yeah even on a video review said those holes are just there to make the speaker openings symmetrical looking...
[One (M8) Q&A, Help & Troubleshooting] skokielad:
Thanks for this thread. I had visited my local Verizon store this weekend and asked them about the "blocked" speaker holes and of course they had no clue. But their demo looked just like mine, and just like all the pics posted here. This saved me a call to cust service (which probably would have gone nowhere anyways, lol).
[Nexus 4 Q&A, Help & Troubleshooting] biodegraded:
In brief:

The N4 is stuck on the whirling circles during boot. It is likely due to some broken bit of hardware. I would like to determine where it's stuck. After that I can decide if repair is possible or if I don't need that feature and it can be skipped one way or another or toss the brick altogether.

In full:

While out of town S.O. dropped the phone and the digitizer shattered. She said the screen appeared to still work, but no input was possible. She ordered a new digitizer and dumped it on me to repair, little realizing the difficulty of replacing only the digitizer. Still, I gave it the ol' college try on a slow day at work, heating the glass shards to yield the glue and get them off the screen. After installing new digitizer I was not surprised that I had damaged the screen and just a few colored stripes displayed.

So I ordered and installed a digi/lcd assembly and I now have a functioning screen and digitizer. The problem is the system won't completely boot and is stuck on the infamous whirling circles. I am fairly certain that during boot some device is being queried and is broken, and the boot has no timeout to skip it and move on. I would like to know where it's stuck. I *think* the way to do that is to somehow direct kernel messages out the phone's USB so I can use PuTTY to display them on a workstation. I do not know how to do that. If there's some other way, like getting the messages to display on the phone's screen, I don't know that either. Hence my post.

The techie bits:

Long story short here's a summary of relevant actions I've done so far.

Phone still goes into the mako bootloader and I can use fastboot.

Used TWRP recovery to wipe everything (including itself)

Flashed factory 4.4.2 OS

Reinstalled TWRP recovery and had it root for me

I now have two ways to access the phone - fastboot when in the stock mako bootloader, and adb when I fire up TWRP.

Now what can I do to find where the system boot is hanging? Suggestions welcome.
[Nexus 4 Q&A, Help & Troubleshooting] RolF2:
first thing to look at - proximity / light sensors connector . phone will not boot if they are disconnected from mainboard.
[Nexus 4 Q&A, Help & Troubleshooting] biodegraded:
I will check that. Thanks for the reply.

Edit: I just checked, and you were right on the money. The tab with the connector for that device had flipped under the mainboard so I didn't connect it. All fixed now and I have a working phone. I owe you a couple beers. Thanks.
[Nexus 4 Q&A, Help & Troubleshooting] Lei M:
Hi, you are lucky ;)

I have a similar problem.

Yesterday i restarted my phone and >problem, stuck at X-boot-logo<

Already tried different roms.

Can get into fastboot-mode and therefore can have ADB with CMW-recovery.

I replaced my screen a few months ago.

Already checked proximity sensor cable.

btw:

at the beginning, one time I got it to "optimizing apps...", but it was stuck at "starting apps"

How can I see if my proximity/light sensor is dead?

can I use the Nexus 4 serial?

Any other solution?

Regards
[Nexus 4 Q&A, Help & Troubleshooting] RolF2:
You can try to downgrade to stock 4.2 android, phone most likelly will boot, but looks like you have lost your IMEI.
[Nexus 4 Q&A, Help & Troubleshooting] Lei M:
OK, I'll try to go back to 4.2.

Anything I can do if I really lost IMEI?

I think you could be right.

I rebooted my phone because i got no network connection. (even after airplanemode on/off)

---------- Post added at 07:05 PM ---------- Previous post was at 06:45 PM ----------

OK, 4.2 booted successfully ;)

Thanks.

but phone does not connect to network.

IMEI seems to be lost (*#06# shows nothing for imei)

What do you think about restoring IMEI with dd-command from "somewhere"?
[Nexus 4 Q&A, Help & Troubleshooting] RolF2:
take a look here : http://xdaforums.com/wiki/LG_Nexus_4/Partition_Layout

do you have baseband version unknown too ?

if yes, first I would try dd mmcblk0p1 (modem / radio.img) and only after that next step would be m9kefs1/mmcblk0p8 , m9kefs2/mmcblk0p9 = IMEI

this is only speculation, never tried that ...
[Nexus 4 Q&A, Help & Troubleshooting] Lei M:
no baseband too.

imei empty, not zero

I don't think dd mmcblk0p1 would be useful as it is only the radio.img.

You can find it in the stock image :)

The first step now is backupping the efs-partitions :)

do you mean directly writing IMEI to it?

I can try to copy the IMEI(or all partitions) from my brother's phone to mine

Thx
[Nexus 4 Q&A, Help & Troubleshooting] RolF2:
don't hurt to try dd modem partition first, maybe it's corrupted in some way ... why it's unknown ?
[Sprint Samsung Galaxy Note 3] Arjun607:
I forgotten password on note3 and hence have done hard reset using stock recovry.But all my data has gone :(:(:( it was very imp is there any way to get it back please help me friends....
[Sprint Samsung Galaxy Note 3] rpenrod23:
Define hard reset but unless you made a Nandroid backup, no
[Sprint Samsung Galaxy Note 3] kaos420:
Not if you factory reset in stock recovery. You wouldn't of had a nandroid option. I'm afraid your up a Creek without a paddle. Other words no.

Sent From My 0x1 Note 3.i love tep....
[Sprint Samsung Galaxy Note 3] micmars:
There are a ton of recovery software companies claiming that you can do this with their particular software they are pitching, but most charge for the promise.

If a well known name in the data recovery software business (like Phoenix, among other) offers something, give it a shot.

Seems like it could work similarly to other such processes, but I'd take my time before spending the money.

Sent from my SM-N900P using Xparent BlueTapatalk 2
[Moto X Q&A] Arak-Nafein:
I'm unfamiliar with how this all fits together. For example, I don't understand how if the bootloader is unlocked, why will it still brick the device if the bootloader is mismatched? Why would the BL version matter if it's unlocked? If the BL will still cripple the device, then it's not really "unlocked", is it?

Also, what does this mean in the future after Motorola stops updating the X? I know we can flash ROMs, but will we be stuck using the base of whatever update Moto/Verizon decides to put out?

The more detailed the better. I've tried googling and searching here, but I can't find any sort of place where this info is gathered & presented in a digestible format....all I'm finding is little pieces of info here & there. I don't even know enough to properly ask for more info. Any help, explanations, or links would be greatly appreciated.
[Moto X Q&A] Arak-Nafein:
Thank you for your reply! It has helped clear up most of my confusion.

Can you elaborate a little bit on this? What changes were made, and why does it brick your phone? (If the bootloader is unlocked, this shouldn't be an issue.....but this is not the case, obviously.) What makes this different than loading a ROM? Is there the same chance to brick your phone from flashing a ROM?
[Moto X Q&A] KidJoe:
I didn't create the bootloader, so I can't elaborate on what exactly was changed. Moto doesn't post release notes. As why it bricks, I could only tell you what I've read. And the thread that was here discussing it in details has vanished for some reason. I do know things like GPT.BIN also come into play, but I don't remember ALL of the details.

As for this shouldn't be an issue with the bootloader being unlocked.. Well, I can tell you unlocked bootloader or not, the long thread that vanished was reports of both those who used the unlock code from Moto to unlock their bootloader, and those who still had a locked bootloader.

The bootloader is unlocked at least to the point that it disables the write protection and you can flash roms, recoveries, etc that are NOT signed by Moto. Is that "fully unlocked" I'll let someone else answer that.

If the 3rd party rom you are trying to install tries to revert the bootloader to a lower level or tries to downgrade the security files (GPT.BIN and a few others), then yes, you have a chance to brick. But most likely only the System partition will be written on 3rd party rom.
[Moto X Q&A] Arak-Nafein:
Thanks again!

I would love to read that thread if anyone has it archived or something.
[Moto X Q&A] Slim706:
Question. Do you need a custom recovery to root? Can you root the Dev edition with stock recovery? I had a locked edition before and rooted it using the exploit method. Now i'm contemplating a Dev edition but don't want to use a custom recovery to root it.
[Moto X Q&A] KidJoe:
You must root via custom recovery. But after you are rooted, you can flash stock recovery back on if you wish and remain rooted.
[Moto X Q&A] krazzyvishal:
I just got my Moto X in India and it bears the model number XT1052, it is the officially available model in India.

But, I saw no mention of this on XDA anywhere, so also I wasn't able to find any root methods for it. Can you suggest anything?
[Moto X Q&A] Darth:
Root methods are all the same....one way for locked bootloader and one way for unlocked bootloaders.

Read the complete moto x guide stickied in the general section for how to. ?

Sent from my N5, N7, Moto X, G Tab 3 or S2.....

---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------

Here,

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

Sent from my N5, N7, Moto X, G Tab 3 or S2.....
[Moto X Q&A] Arak-Nafein:
So, no one knows why downgrading bricks the device? I mean, I know it's because of the bootloader mismatch.....but that's unlocked so why is it being bricked? It seems "unlocked" is not really unlocked....I tried searching, is this efuse that's bricking the phone? If so, WTF? Why would they make something that destroys your phone?
[Moto X Q&A] Darth:
Its just how it is. These aren't nexus phones. They made the 4.4.2 bootloader in a way that if you downgrage, then most commonly try to upgrade again...by ota for sure anyway, boom. Brick.. I'm sure it wasnt made that way intentionally. Personally I just think phone companies just don't care or support what we do. So they don't create anything thinking in terms of rooting and flashing this or that. Its not their concern....since 98 percent of their customers update their unmodified phones over ota and thats it.

Have to remember we're an extremely small percentage of phone users. They aren't even thinking of us when they make stuff. ?

Sent from my N5, N7, Moto X, G Tab 3 or S2.....
[Moto X Q&A] Arak-Nafein:
Yet, they made the developer edition.

I know this isn't a nexus device, but I was expecting nexus-like functionality with the dev edition bootloader unlocked, I know this is not the case now. (Although, you get most of the functionality)

Well, they make a "developer edition" that bricks when you try to downgrade. That seems counter-intuitive.

That's why I'm trying to find the technical details of what causes the brick. Why does it brick? What are they trying to protect? The boot partition? I don't understand the whole point of it or why it happens. Why make a developer edition if it gets bricked like a non-dev edition when flashing? This may have been already answered when the first dev phones came out, but I missed that train. I only upgrade my phone every 2 years or so and this is my first "dev edition" so it's all new to me. I've done a bit of reading, but nothing explicitly states what's cause the brick, just that "it happens". What's causing it?

My main reason for asking is just because I'm curious & would like to understand.

The second is, I'm wondering what happens when we stop getting updates. Will we be stuck on the last version of Android that is given to us?
[Moto X Q&A] Darth:
I doubt they meant it to be that way....it just turned out that way. And again, I doubt they care. Dev editions are just made to make more money. And keep up to competitors who make them. You keep your warranty, but other than that....nothing is special about them. ?

Why it works that way? Dunno. Lol

Sent from my N5, N7, Moto X, G Tab 3 or S2.....
[Moto X Q&A] KidJoe:
You have to keep in mind, other than unlocking the bootloader, and Moto Maker customizations, the Developer Edition is the same as the "retail" edition phones except that you can get the unlock code from Moto for free without voiding your warranty and are stuck with the black front, woven white back, and silver accents.

Order a Verizon X via Moto Maker, its an XT1060, order a Dev Edition for Verizon its an XT1060, and they use the same Rom/SBF/FXZ files. GSM side, the "Unlocked GSM" model that comes with a T-Mobile SIM is an XT1053, a GSM Dev Edition is a XT1053, and again, they use the same rom/sbf/fxz. Did moto do this to "save cost" maybe?

The Dev Editions are unlocked just enough to allow you to flash stuff not signed by Moto. That is it. Moto makes no promises that you can successfully downgrade, or anything. If you have a Dev Edition and brick it, its covered under warranty.

As for why it works this way, only Moto knows. We can only speculate, guess and such, which was done in a big long thread that has since disappeared (not sure why it disappeared). Beyond that, we can only relay the cautions we know of, and tell you how it works based on the experience of several people. I'm sorry if that is not enough. If you want the real answer, you'l have to call Moto directly, or see if you can post on G+ tagging some of the Moto people, but they likely wont tell you.

I can tell you this.. My Moto Xoom was unlocked, needed no code to do so, and was virtually "un-brickable." The X does not work that same way. I can only GUESS why. (carrier request maybe? something else?)
[Moto X Q&A] Arak-Nafein:
Argh, so frustrating! Now I REALLY wanna see that thread. XDA isn't archived on the wayback machine is it?
[Moto X Q&A] KidJoe:
the thread was cached in google at one point, now its not, it only comes up with link to XDA but when you click on it, XDA says the thread does not exist.

See the OP here -> http://xdaforums.com/moto-x/moto-x-qa/informative-thread-t2658742
[Moto X Q&A] Darth:
People that REALLY love flashing and tinkering.....need a nexus. Bottom line. Nothing else compares....today anyway.

As much as I LOVED my X....this is why my wife has it now and i have the N5. ;)

Sent from my N5, N7, Moto X, G Tab 3 or S2.....
[Moto X Q&A] Arak-Nafein:
If Verizon would allow it I would have already done it. :D

I did some more reading, it appears it all comes from motoboot.img(motoboot partition) & gpt.bin("partition" partition). As long as you don't mess with those & their respective partitions you shouldn't have to worry about bricking your phone. You can still access & read/write the boot partition & the system partition & everything else when unlocked. The OTAs will modify these (And check for certain versions of these) which can leave you in a nasty catch-22 situation & thus the brick. It's not the actual downgrade that bricks it, it's the security from the OTAs that error out & leave you stranded. You can still flash the OTA if you do it manually & leave out the bootloader stuff.(EDIT: This isn't entirely true) You can flash any other ROM because they don't have the built in security like the OTAs. So, if you flip over to an AOSP or CM ROM or anything not based on Motos stuff you needn't worry about nazi bootloaders & OTAs bricking your device. The only problem with going to those ROMs is the loss of Active Display & Touchless control. :( I'm guess Moto isn't releasing anything on the X8?

Does this sound correct? That's what I've collected from my readings. Feel free to correct me.
[Moto X Q&A] Darth:
I've said before....and I stand by it. Downgrading from 4.4.2 on any moto x is like playing russian roulette. And I simply say, don't. Lol

But.....its each person's phone and they can do what they want with it. ?

Sent from my N5, N7, Moto X, G Tab 3 or S2.....
[Moto X Q&A] Arak-Nafein:
That kinda came out wrong and I've tried to edit my post to better explain it.

The motoboot.img & the gpt.bin go together. For example, if you are on 4.4, you can manually flash all the parts except the motoboo.img & gpt.bin from 4.4.2 and it will work, and you'll retain the dowgradability of 4.4. But, you're setting yourself up for disaster should you accept an OTA (Which will be looking for the updated motoboot.img & gpt.bin. gpt.bin will be updated, but the bootloader will fail. This leaves you with a mismatched motoboot.img & gpt.bin and boom brick on next restart.)

You're right tho, it's best not to play with that. Unless you disable Motos OTA & treat it like a ROM that you have to return to stock before taking an OTA.

The bootloader is unlocked....but Motorola's software has built-in checks that only allow it to overwrite a specific version (cumulative changes?).

At least, that's the way I understand it. I'm probably way wrong here.
[Galaxy S 4 Q&A, Help & Troubleshooting] geekytech:
I was on custom Rom and I restore my nandroid image backup and my s4 reboot with no problems. Running touchwiz 4.4.2 I restore all of my apps using titanium backup, and when I open instagram my feed won't refresh and a pop up would come up saying instagram stop working every time I open instagram. Please I need some help
[Galaxy S 4 Q&A, Help & Troubleshooting] geekytech:
Thanks I tried that but it didn't work so I just flashed a rom and also the latest Gapps and it work
[Android Q&A, Help & Troubleshooting] artssa:
What do think about UC Browser (not the regular version, but the HD version)? I have been using Dolphin for almost 3 years (but testing every new well evaluated browser app) and that's the first browser that actually made me think about leaving Dolphin aside (even tough it consumes some more ram - like 20% more than Dolphin).

What are your thoughts about UC Browser HD?
[Android Q&A, Help & Troubleshooting] Gutterballz:
Faced same dilemma!

I was facing the same dilemma as you currently are, especially with the new UI changes made to Dolphin. I had been using Dolphin as my main browser for years, but I made the switch to UC, and I haven't looked back since! The only thing that seems to be missing that Dolphin had are the add ons, and i have heard that there are add ons that can be implemented into UC as well. If true, then this is definitely my new browser of choice! Play around with it for a while and I think you'll like it.