yashsingh1/xdaforums huggingface dataset:
[Moto G General] lost101:
There was a recent case of an XT1031 ACG US (C Spire) user who flashed the XT1031 Boost US firmware, including Bootloader. They could not get service (no Boost coverage in that area) - and restoring the original Firmware was apparently not possible. The Bootloader appears to play a role in connectivity.

Fastboot flashing a Factory Firmware Image does not require an Unlocked Bootloader. However if you are try to downgrade Android version, flashing will often fail.

It seems to me it would be possible to convert any locked XT1031 running 4.4.4, to another carrier - if there is a 5.0.2 or newer Firmware Image for that carrier available. At this time, there are no XT1031 Lollipop Firmware Images available.

EDIT: Even flashing one of the current XT1031 4.4.4 firmware images may be an option.

Related: [INDEX] Moto G [Falcon][Peregrine] Factory Firmware Images
[XDA Assist] abdul mannan attari:
My tab s 8.4 LTE not working...just on then off by self I can't data factroy reset...plzzz tell me how I can solve my problem..
[XDA Assist] jackeagle:
Hi,

Thanks for using XDA Assist :) please post here Samsung Galaxy Tab Pro 12.2, 10.1, 8.4 Help and Troubleshooting were experts using your device will help you :)

Good Luck!
[Xperia Z2 Q&A, Help & Troubleshooting] NirmalSitaldin:
Hi guys! I have a question. Let's say I want to do a factory reset on my Z2 or a system repair (which also wipes all the data I guess), what data will be stored back into the phone after I want to restore via the Back Up & Restore app? Because I read somewhere that not your apps nor app data will be in the saved data . Rookie here haha. Thanks in advance :)
[Moto X General] asdadfad:
This can also be found on the Moto G general, reddit, and on RW forums. Can't link them yet since I don't have 10 posts in.

All new service lines will be on the Republic 2.0 plans and members on the 1.0 plan have until August 1st, 2016 to switch.

Many of you aren't happy about the new plans and coupled with the many glitches in service, see this as an incentive to finally switch. The problem is that RW phones are locked in to RW service.

We know that "the ROM isn’t in fact entirely CyanogenMod." Also, "The software on your republic phone has been created specifically for Hybrid Calling." Note that this says software, not hardware, so it should be possible to flash RW phones to work on other carriers and flash your own device to work on RW (disregarding any unique device identifiers)

A big concern RW has with flashing is that "it negates the premise of our entire community... reducing your cellular footprint". But by the time August 1, 2016 rolls around, those of us that want to switch will be stuck with useless devices. If we were able to switch carriers, this wouldn't harm (it could even benefit) RWs premise of offloading to WiFi. I'm also sure none of us would have the audacity to try and return a flashed RW phone after we've terminated our service with them and are (hopefully) on another carrier.

When we finally get the ability to use our RW phones on another carrier I don't think RW would care for feedback from us (imagine installing OSX on a windows device and still getting a microsoft nag for sending an error report) nor would anybody in the right mind try to get troubleshooting and service from RW. Finally, by August 1st, 2016 most of us will be far out of the 30 day money back guarantee and any warranty we might have. Why should you expect continuous support from RW after the 2.0 plans become mandatory and you're already looking for another plan?

The worst part to me about this mandatory 2.0 switch is having to buy another device to use on another carrier especially when the RW phone is physically the same. What I propose is that we put together a bounty on XDA in hopes that someone can figure out how to get RW devices (specifically those on 4.4.4 since there's supposed to be a working method of flashing on 4.2 and below) working on another carriers. I would be willing to chip in up to the cost of a 3rd gen moto g since that's the device I'd buy if this doesn't work out. Please let me know if you'd also be interested in such a thing or of your plans come August 1st, 2016 if you're in a similar situation. I'll also be posting this in XDA and on republics forums.

tl;dr RWs reasoning against rooting/flashing doesn't really apply to those of us that don't want a 2.0 plan. Let's put together a bounty to get RW devices working on other carriers and save money.
[Galaxy S 5 Q&A, Help & Troubleshooting] icytalentpwns:
Even if i make it silen/vibrate it still stops my music and says received message. I dont know how to disable it after installing lollipop.
[Nexus 5 Q&A, Help & Troubleshooting] Ashleyware:
Hello xda, I have a problem!

My Nexus 5 is only six months old and aside from typical Nexus 5 shenanigans (the camera seizing upon lock, requiring a reset) it has worked fine. (though I have been very discontent with this device) Last night I was using my Nexus 5 as usual and I was tired, but too lazy to plug it into the charge port. By morning my phone died as expected, so I plug the charger in and lo-and-behold, it's stuck in boot up.

So naturally I freak the f*** out; I wait. To no avail.

I wait some more. Nix.

It's still f***ing booting.

So I know something's wrong with my phone and I said "f*** it; I'm just going to factory reset it" because knowing my luck, my phone decided to say "f*** you" and kill itself the night prior. (My affinity with technology is poor.)

So I wipe the damn thing.

I boot it up.

Loop. You've got to be kidding me.

I wipe the cache (don't tell me I should have done this first); nada.

I get flustered, chuck the black pice of s*** down the stairs, get desperate, pick it back up, take it to work with me (while it was still booting), I left for work at 12:00PM, it's now 7:04PM, I'm home and it's STILL BOOTING.

So what's a girl to do?

And I'm going to answer the fusillade of questions I know I'm going to get in response to my peril, so before you all premeditate; here's what I've done to my phone:

I rooted it THREE WEEKS AGO with KingRoot to turn off my proximity sensor. Why? Because I Skype and like to use my device at the same time, and Microsoft thought it would be brilliant to have the screen shut off any time something crosses slightly in front of the Nexus 's two stupid sensors, so horizontal use of the device gets thrown out of the window. (if any muppets at Microsoft are reading this, you're f***ing idiots! If I really wanted to turn my screen off to conserve battery power, I would lock the f***ing screen! I don't need YOU nannying me!)

I wasn't able to shut off the proximity sensor with root permissions so I got cheesed and unrooted, then uninstalled the application.

Things have been working perfectly fine. (And yes, my phone has been rebooted in that three week span.)

Up until last night, my phone was working perfectly normal. I did what I usually did.

Listened to music, checked my work schedule, text, watched YouTube videos, played Gameboy games on an emulator, and that's it.

Someone please help me with this phone so I can at least fix it and sell the wretched thing to some muppet for some money to put towards a REAL phone.

Thanks.

~ Ashley

And it finally died, just as I finished writing this.
[Nexus 5 Q&A, Help & Troubleshooting] funnel71:
Since you've already wiped data, have you tried unlocking the bootloader and flashing the Google factory image
[Nexus 5 Q&A, Help & Troubleshooting] Ashleyware:
I haven't because I can't. I'm on a Macbook and the Nexus 5 drivers aren't compatible with Macs apparently =/
[Nexus 5 Q&A, Help & Troubleshooting] Ashleyware:
Wait okay, so I misread what I looked at this morning.

So it says I have to flash a new rom to my phone O.K. but every website says I have to turn on USB debugging--how am I supposed to turn on USB debugging to unlock the bootloader if my phone is bricked to begin with? This doesn't make any f***ing sense!

HELP.

Also, my Mac doesn't recognize my device in fastboot mode; what am I supposed to do?!
[Nexus 5 Q&A, Help & Troubleshooting] ldubs:
Try this? It has Mac instructions too.

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

---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------

I was able to unlock my bootloader on my Mac with no problems...
[Nexus 5 Q&A, Help & Troubleshooting] Ashleyware:
Don't you understand? I can't enable USB debugging because I can't ACCESS my phone! It's stuck in bootloop! I can't unlock the bootloader to begin with! Unless you know how to unlock the bootloader from the fastboot menu, you saying that you unlocked your bootloader doesn't help me. I tried everything in that thread and nothing works, I tried the terminal bull**** and the only thing that happens as I can get into the folder where the factory rom is, but I can't get it to flash, I can't get anything to happen--I don't know what the hell I'm doing.

Is there a way to start over without all of this stupid bootloader crap?
[Nexus 5 Q&A, Help & Troubleshooting] galakanokis:
As far as I know ADB is not active in fastboot, it is not recognized. In fact I just flashed TWRP again with ADB off. You do need the fastboot drivers on your Mac installed correctly but that's no big deal. If you have access to your phone in fastboot it is simply fastboot oem unlock to unlock your bootloader.
[Nexus 5 Q&A, Help & Troubleshooting] Ashleyware:
PROGRESS REPORT

So last night I stayed up trying to fix my issue, and I've had no success. I've managed to flash back to Kitkat 4.4.4 but as soon as the phone boots into set up, immediately I get the error messages "unfortunately Camera has stopped working", "unfortunately Gallery has stopped working", and "unfortunately Google Playstore has stopped working". After setting up, my phone has NO service! It doesn't even recognize if there's a SIM card even inserted, or if I remove it.

I cannot open Playstore, it immediately crashes and my phone believes that it has no storage now, even though I see 12GB of space free. I tried flashing multiple roms and nothing beyond Kitkat will work, otherwise I get caught in a bootloop.

I tried installing Cyanogen mod and although it worked, I had the same issue--no service, no Playstore no storage.

I tried clearing the cache, the Dalvik and factory resetting several times and nothing works. I just flashed 4.4 and I'm updating it to 4.4.3 as we speak.

Also I think it's worth mentioning that every time I got caught in bootloop after flashing a new rom (and I tried all of them, including Lolipop, which always hangs) that when I boot in Recovery mode it says something along the lines of:

Invalid arguement couldn't mount blahblahblahgeniusspeak

Invalid arguement blahblahblahgeniuspeak

and so on. Does this have something to do with my lack of service, camera not working, Playstore not working and storage not working? I'm desperate people.
[Nexus 5 Q&A, Help & Troubleshooting] republicano:
Have you got an imei number?,settings/about phone

Usually you just flash factory ROM, extract the file and then the second archive and flash each individual file and it should boot, factory reset and wipe cache to fix storage

I do this on my mac

If you can't do this then you may have a hardware issue

How did you try to turn off proximity sensor. There would be another way to keep screen on while skyping (keep screen on wake lock)
[Nexus 5 Q&A, Help & Troubleshooting] ldubs:
Also it sounds like you flashed custom roms without flashing gapps...
[Nexus 5 Q&A, Help & Troubleshooting] galakanokis:
Definitely sounds like no gapps.
[Nexus 5 Q&A, Help & Troubleshooting] Ashleyware:
What's gapps? And I have no IMEI number (unknown), it says my (with my SIM inserted) Network is: Unknown

Mobile Network Type: Unknown

Mobile State is disconnected

Out of Service

Phone number is unknown

IMEI SV is unknown

IMEI is unknown

Not roaming either

What's the second archive? Every guide I used said use the flash-all.script and that's all you have to do, what're all these extra steps? How do I flash gapps, I don't even know what that is; I don't see the file anywhere in the factory image folder.

=/
[Nexus 5 Q&A, Help & Troubleshooting] Ashleyware:
I flashed again (back to stock; 4.4) and did everything manually instead of using the script, I even flashed the cache.img, recovery.img etc . . . and it's still the same issue. No service. No external storage available. No Google Playstore.

=/

I didn't flash a custom rom, I only flashed the official factory image from Google. Why doesn't anything ****ing work.

Is gapps going to return my storage and service?
[Nexus 5 Q&A, Help & Troubleshooting] shri_chanakya:
Gapps is only for custom ROM. Since your imei etc is unknown seems like you have bad efs partition. I am not 100% sure. May be others can help.
[Desire 626 Q&A, Help & Troubleshooting] champ1919:
Was this the app or pc version of kingroot that failed?
[Desire 626 Q&A, Help & Troubleshooting] brad65807:
Anyone able to root this yet ?
[Desire 626 Q&A, Help & Troubleshooting] lox2013:
http://xdaforums.com/showthread.php?t=3181038 I made a thread got the stock recovery
[Desire 626 Q&A, Help & Troubleshooting] yousuc:
Just picked up this phone, awaiting a way to root, kingroot and kingoroot do not work. Cricket 626S. Already ran htcdev on it, need recovery to install supersu.
[Desire 626 Q&A, Help & Troubleshooting] Josh561:
Update on Root?

I was hesitant to buy a new phone from MetroPCS lineup given that I was aware a root would not be available. This phone is great but has so much more capability. Not writing to SD card is crazy. You can trasnfer files on a PC between internal storage and SD. Anyway enough said. Does anyone have any updates on a root?
[Desire 626 Q&A, Help & Troubleshooting] threesix10:
i found a thread with the stock recovery, i do not understand how to create a custom recovery ive gone over it over and over. i also tried the clockworkmod builder but it doesnt seem to be working i just get 404 errors. here is the link to the thread its the op. hopefully some one can make a custom recovery

http://xdaforums.com/general/xda-assist/htc-desire-626s-cwm-build-t3181038
[Desire 626 Q&A, Help & Troubleshooting] locofocos:
I'm also interested in this. I spent most of my time trying to extract the stock recovery from the RUU (which you can download from HTC's website, then extract using instructions here on XDA. It's basically starting the exe, then going to your temp directory). Some of the files can be extracted, but I think the others are encrypted. I've read that HTC started doing this a while back.

If the above link really is a copy of the stock recovery (and I'm curious to know how this was obtained), then we may be able to build CWM following these instructions- http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device

Or maybe we also need the boot.img. I can't remember if this was one of the files I was able to extract from the RUU. Either way, there's some process by which we should be able to create a custom recovery.

Once we have something built and want to test it, you can try to boot your phone into the recovery without actually flashing it by running

fastboot boot recovery.img

. See these links- https://aubykhan.wordpress.com/2013/07/21/android-tip-boot-into-twrp-or-cwm-recovery-without-flashing/ http://androidforums.com/threads/stock-recovery-partition-image-backup.612148/ http://optionkey.blogspot.com/2013/12/backing-up-your-android-phones-stock.html

I'm kinda busy the next few weeks, but I definitely want to work on this when I get the chance some time. This is about the extent of what I know at this point. Have at it.
[Desire 626 Q&A, Help & Troubleshooting] DamianSixSixSix:
i tried that one, wont boot with fastboot boot cmd, says its a incomplete boot image :(
[Desire 626 Q&A, Help & Troubleshooting] locofocos:
Here's something else worth looking into -https://twitter.com/srsroot/status/639544040489357312?s=09 which links to http://www.srsroot.com

If that doesn't work, it appears we can modify the boot.img file to gain root adb. I found it here http://androidforums.com/threads/htc-desire-626s-root.946455/ with more detailed instructions here http://android.stackexchange.com/questions/28653/obtaining-root-by-modifying-default-propro-secure

Again, I'll try this sometime, but I'll be pretty busy for a while.
[Desire 626 Q&A, Help & Troubleshooting] DamianSixSixSix:
k, ill take a looksie :)

edit: problem with this is, we need boot.img, but we can only get that with root xd
[Desire 626 Q&A, Help & Troubleshooting] locofocos:
I might have that file. HTC posts their RUU files on their developer website. There are instructions floating around here showing how to extract them. It didn't have recovery, but it might have had boot.img. I just got to work, but I'll check when I get home.

Edit: Just check on TeamViewer. I've got a boot_signed.img file. We might be in business.
[Desire 626 Q&A, Help & Troubleshooting] DamianSixSixSix:
k man, that root kit doesnt work either im afraid :(

tried a few times :P

but is there a safe way to test the bootimg? can we boot that like we do recovery?
[Desire 626 Q&A, Help & Troubleshooting] locofocos:
Perhaps you could boot it through fastboot, but I'm not finding any mention of it online. I'll probably give it a shot. Whenever I get to make it, I'll flash it on my device. Even if it's bad, we ought to be able to boot into fastboot and reflash the stock boot image. If that even fails, we have an RUU from HTC that should completely restore everything. And if THAT fails, then I wouldn't mind helping myself to the new Nexus 5X :D
[Desire 626 Q&A, Help & Troubleshooting] DamianSixSixSix:
lolol, i see how it is xD

here is hoping that it goes bad huh? :P
[Desire 626 Q&A, Help & Troubleshooting] locofocos:
I tried modding the boot.img file I pulled from the RUU. I flashed it, and my phone booted fine, but didn't seem to have any root access via adb or terminal. I tried "adb root", but apparently you need a modded version of the adbd binary per this page- http://bclary.com/blog/2014/04/14/splitting-and-packing-android-boot-images/. I followed these instructions http://xdaforums.com/showthread.php?t=2593581 and included an insecure adbd, but this made my phone go into a bootloop.

I was able to reflash the stock boot.img (from the RUU) after each time with no troubles. So, no bricks, but no root yet either. I notice that my device still has "s-on". Haven't been an HTC guy before, but I think that needs to be "s-off". I'll try again some other time.

Just to be thorough (in case anyone else wants to try), these tools helped to unpack the boot.img file - http://xdaforums.com/showthread.php?t=1494036
[Desire 626 Q&A, Help & Troubleshooting] DamianSixSixSix:
i been a htc user for a few years now, and although i always got s-off before, im almost 100% certain that for gaining root its not needed.

unlocking bootloader should be enough, if we can get a custom recovery on it that is...
[Desire 626 Q&A, Help & Troubleshooting] locofocos:
It may be worth investigating other ways of modifying the boot.img to give us root access over adb, but it seems that we need a version of adbd that won't cause a bootloop. I should mention that whenever I used the modified adbd binary (which always made it bootloop), I got a red warning/copyright message really quickly. It said something like "this HTC development something is property of HTC". I never got that message when I only modified default.prop.

A custom recovery would be the best option for sure. There's a post on XDA University about making CWM for a new device, and this method needs the boot.img (unlike the other method, which needs the recovery.img we don't have apparently). Reading the instructions, I'm not entirely sure it works for devices CM doesn't support, since it makes mention of the device codename, but I'm hopeful. Since I know for a fact we have a working stock boot.img (my phone is using it to boot now, lol), this looks like a good option.

---------- Post added at 08:57 AM ---------- Previous post was at 08:57 AM ----------

It may be worth investigating other ways of modifying the boot.img to give us root access over adb, but it seems that we need a version of adbd that won't cause a bootloop. I should mention that whenever I used the modified adbd binary (which always made it bootloop), I got a red warning/copyright message really quickly. It said something like "this HTC development something is property of HTC". I never got that message when I only modified default.prop.

A custom recovery would be the best option for sure. There's a post on XDA University about making CWM for a new device, and this method needs the boot.img (unlike the other method, which needs the recovery.img we don't have apparently). Reading the instructions, I'm not entirely sure it works for devices CM doesn't support, since it makes mention of the device codename, but I'm hopeful. Since I know for a fact we have a working stock boot.img (my phone is using it to boot now, lol), this looks like a good option.
[Desire 626 Q&A, Help & Troubleshooting] DamianSixSixSix:
well, we could always try TWRP recovery, if CWM doesnt work :)

Edit, thanx to another member here, i got files from a RUU, for the 626s, dont think that changes much, that "S" :P

anyway, in it i got boot, aboot, recovery etc, do you think we can do stuff with it?
[Desire 626 Q&A, Help & Troubleshooting] hackvcs:
From my understanding you need to set Selinux to permissive for an insecure boot.img to work on lollipop. I am unaware on how to do this but I believe we need to wait for HTC to post the Kernel source on HTCdev in order to do this.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] mbasi:
Hello all,

While tinkering with my new Trion, i noted that no-one had apparently dumped a UK version of the ROM. So here you go:

!! [DUMPED English ROM from O2 XDA Trion (HERM100)| ftp://xdaupload:xda@ftp.xda-develop..._XDA_Trion_ENG_2.15.206.1_2007-03-23_WM5.rar]

ROM version 2.15.206.1<br>

ROM date 03/23/2007<br>

I've updated the wiki accordingly.

NB: I'm Michael - hi! :) Have been a member for ages, but not posted for years :o Used to deconstruct my original XDA / II all the time, but for over a year with my Mini-S (Wizard), i just stuck with the operator standard for over a year after getting annoyed with making the last "tinkered" unit (XDA IIs) unstable.

The bug is back though, and I've tinkered again. Hacked around and the best Hermes tweek, IMHO, is Schap's WM6: incredibly stable - obviously i've tweeked it a bit, but sheesh, things haven't half moved on since the XDA II days!
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] D_JWhite:
hey the link doesn't quite work if you could remove the %5d at the end it would work ta!
[XDA Assist] XDA Visitor:
Its a galaxy s6 edge sm-g925t version 5.1.1
[XDA Assist] GuestK0087:
Hi, thanks for using XDA assist! :)

First, please create an account so you can post in other forums.

Here is your device's main forum area:

(You should bookmark this)

http://xdaforums.com/galaxy-s6-edge

After creating your account, please post your question here:

http://xdaforums.com/galaxy-s6-edge/help

The experts for your device are located there and will help guide you.

Good luck! :)
[Nexus 6 Q&A, Help & Troubleshooting] xt99ikd:
I've been trying to get a ROM on my nexus 6, but as I go to unlock the bootloader, I enable usb debugging but get no prompt to authorize my computer's RSA Fingerprint. Any Ideas would be helpful. I've Tried all different combinations of connections (MTP+USB Debugging, etc.), and it still will not prompt me to authorize it. Thanks.
[Nexus 6 Q&A, Help & Troubleshooting] alfa799:
Have you tried Nexus Root Toolkit? I used that back in January to unlock and root my Nexus 6.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
Reboot the device. Set switches for USB debug and bootloader unlock. Plug in phone. If don't work there a driver problem. If see your drive on PC don't worry about it. If it sees adb and/or fastboot don't worry about it. Don't use toolkit unless already know how to fastboot. If it screws up you are screwed cause don't know what happened.:cool: