yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] mj0528:
and you confirmed that by going to "about phone" or did something start happening to make you think you lost the modem?
[Moto X Android Development] drksilenc:
yea nothing would connect or start aka no data from wifi or sim. Im good now though i just rsded my device and everything is back. Now that i am 100% stock im going to give it a go again. Ok im good now i got it to work somehow my modem flash didnt go through when i went to the new version.

steps to solve if you lose your modem

rsd lite back to stock v1 os

reflash using steps in guide....
[Moto X Android Development] HeroSon:
After doing freak4dell steps for flashing kit kat leak, it seem i cant get write protect mode to turn off. Anyone have any idea about this, even in bootloader I chose recovery and it still wont turn off, safe strap say that I'm in write protected mode and no way to turn it off.
[Moto X Android Development] mj0528:
looks like this may be the only way to have root and kit kat, jcase is not going to be releasing another root method for kit kat for the moto x.

Thanks ctrl freak!
[Moto X Android Development] Ctrl-Freak:
I have successfully changed things on /system.

Is it possible that you left the 4.2.2 kernel in the recovery partition after PwnMyMoto/RockMyMoto? (If so, it might be trying to boot to recovery, crashing, then rebooting back to the normal kernel.)
[Moto X Android Development] HeroSon:
Dont know. I follow these step below by freak4dell. is it because i didnt flash recovery boot.img in step 7 which he left out. also i use the boot.img from the OTA patch to flash instead of the leak one.

1. Root and install SS.

2. Boot to SS recovery.

3. Flash the leak.

4. Flash SU.

5. Flash the OTA patch.

6. Use the SS reboot options to reboot to bootloader.

7. Fastboot flash the newest boot.img and the modem (NON-HLOS.bin).

8. Fastboot reboot, and select recovery when the SS prompt comes up.

9. Flash the modem patch.

10. Wipe cache and reboot to system.
[Moto X Android Development] Ctrl-Freak:
Not flashing recovery with the latest (ota patch) boot.img is likely your problem. Boot to the bootloader, and: fastboot flash recovery boot.img
[Moto X Android Development] HeroSon:
Thanks Ctrl-Freak, everything working now I got write mode turn off now.
[Moto X Android Development] freak4dell:
Yeah, I skipped that step because I had no idea what it was for, and I just did not want to mess with my recovery. My biggest concern with updates is whether I'll be able to go back, so recovery stays untouched for me unless I know what it's for.

My problem is actually the opposite. I can't get into write protect off mode. It reboots and hangs on the boot animation, then reboots back into the normal mode. I'm not terribly worried about it right now, though.
[Moto X Android Development] Ctrl-Freak:
Actually, you and HeroSon seem to be experiencing the same isssue.

FYI, once you ran PnwMyMoto, you already "messed with" your recovery, and now you should bring it up to date. Flash the 4.4 ota boot.img -> recovery to get into /system into RW mode. You can always flash the original 4.2.2 recovery -> recovery if needed (fastboot flash recovery recovery.img)
[Moto X Android Development] freak4dell:
Ah, I must have misunderstood that post.

Yeah, I know PwnMyMoto modifies the recovery, but it was done in a way that made sure I can go back. I suppose it makes sense that flashing boot.img to recovery would still keep the ability to flash the actual recovery back. I'll do it when I have some time later.
[Moto X Android Development] Ctrl-Freak:
You can definitely go back. I reverted back to the original recovery several times during my testing.
[Moto X Android Development] mj0528:
Can't decide on taking the soak test or run with this method?
[Moto X Android Development] BrokenWall:
Im sure Ctrl-Freak will find a way to get the full OTA and rebuild it so we can use this method again for the upgrade and keeping root.
[Moto X Android Development] dima0988:
Camera app makes the phone soft reboot

before updating to the leaked 4.4, i installed camera app, hangouts, google search and google home from nexus 5 kitkat leaks. everything worked great. Didnt particularly liked the stock app for camera, so decided to just ignore it. After updating the phone to the leaked kitkat, camera app, that was from nexus 5 is still there, and working fine, but if i want to go ahead and uninstall it, it causes the phone to soft reboot every time. Any ideas to why is it happening?:confused:
[Moto X Android Development] agent852:
Probably because you are trying to uninstall a system app? I would try manually removing it via Root Explorer from system/apps or wherever it's apk is
[Moto X Android Development] dima0988:
Ok, so now, I tired to uninstall any app, and it forces the phone to reboot. hmm..

UPDATE: I wiped data/cache clean, so i can start from scratch with 4.4. Still will force soft reboot when uninstalling app downloaded from Store
[Moto X Android Development] mj0528:
I thought I read this from earlier that seems like it applies to your situation

"Flash the 4.4 ota boot.img -> recovery to get into /system into RW mode. You can always flash the original 4.2.2 recovery -> recovery if needed (fastboot flash recovery recovery.img)"
[Moto X Android Development] hansmrtn:
I attempted this. It stopped halfway through and rebooted. Now I am sitting here, looking at a Motorola logo that doesn't change. No matter what I do, it boots here. Any help?
[Moto X Android Development] mj0528:
First boot takes a few min
[Moto X Android Development] hansmrtn:
Yeah, definitely not 2 hours.
[Moto X Android Development] dima0988:
Thanks. I didnt notice that my modem patch was not installed correctly. rolled back to 4.2.2 because of some other issues, and updated to 4.4 from scratch. working great now!)
[Moto X Android Development] HeroSon:
I also have the same problem when i first attempted this, guess safe strap didnt finish flashing the leak what i did to fix it is download the Moto X Toolkit v1.2.1 and flash back to stock ota in the tool kit, (warning you will lose all your data), then flash the leak all over again.
[Moto X Android Development] hansmrtn:
Fixed it. Thanks!
[Moto X Android Development] dudumaroja:
I've instaled the rom from Dev XT1053 on my XT1058, its working great.. im here thinking if its ok to flash this modem on this rom.. any thoughs?!

edit: Can someone discribe At&t crapyware and modification on this rom?!
[Moto X Android Development] mj0528:
Ctrl-Freak,

Do you have any plans on taking the full OTA from T-mobile or AT&T when it gets here and updating this?

Thanks for your work man!
[Moto X Android Development] freak4dell:
Came here to ask if Ctrl-Freak would maybe be able to make a ROM like this out of the T-Mobile final build. I'd rather run that than AT&T, and now the FXZ is available. I'd attempt to do it myself, but I simply cannot seem to get that system.img file extracted...nothing I try works for whatever reason.
[Moto X Android Development] rmead01:
Any chance to make a new flashable version of the att official? The build is just a tad but newer so I wonder I'd they worked a kink or 2 out. Now that I have safe strap may as well attempt to hang onto it
[Moto X Android Development] dew.man:
I tried using the tmo released ROM with this modem, but there's more to it than just flashing NON-HLOS. Resulted in various FCs including not being able to get in to security settings. Ended up going back to the tmo modem and it's working fine on at&t.
[Moto X Android Development] Ctrl-Freak:
All we need are the files...
[Moto X Android Development] Ctrl-Freak:
Look for "simg2img.py" and run it [in linux]: ./simg2img.py system.img system-ext4.img
[Moto X Android Development] freak4dell:
I've tried. It just returns an error:

820554520
Not a compressed ext4 file!!

There are several threads on XDA that provide guides on extracting imgs, and I've tried all of them. None work for me.
[Moto X Android Development] matt68000:
Has anyone else had issues with VPN, Settings->Security and uninstalling crashing the UI after using this method? The bug has been commented on in this xda thread for T-mobile Moto X'ers but I have it on my AT&T Moto X after using the method in this thread.

ShorlineDroid suggested that the issue could be resolved by flashing fsg.mbn and NON-HLOS.bin. I got the fsg.mbn from the original source of this thread's method but flashing those two files did not resolve the VPN, Security or Uninstall issues on the AT&T Moto X.
[Moto X Android Development] freak4dell:
You can't just flash the modem files. You have to flash the patch that the OP posted, too.
[Moto X Android Development] matt68000:
<sigh> Yes, of course, if the implication was not clear already, I flashed and installed the original KitKat leak, the OTA update and the modem update exactly as stated in the OP. Everything up to and including installing the modem patch in the OP's "Update 11/18/2013" went off without a hitch. My phone is running KitKat in a, mostly, usable state except for the aforementioned 3 buggy functions.

I did not perform the "fastboot erase userdata" in part 1, step 12 as the OP and many others have stated, it was not necessary. I downloaded all files (leak, OTA update, modem, SuperSU) from the OP's links.

Now that that is all clear. Anyone else have these bugs and a resolution for them yet? I'll continue to play with it. I just wanted to see if I was alone in my quest. :)
[Moto X Android Development] Ctrl-Freak:
I wish I could be more helpful, but here are my comments:

VPN: not sure...

Settings->Security: Do you mean a Settings->security causes a force close of Settings? If so, this problem is still likely related to the modem. I would try re-flashing the NON-HLOS.bin (from the modem patch zip), and re-running the patch. When you run the modem patch, watch for 'failed' or 'successful' in SS:TWRP. Also, I personally have not updated fsg.mbn, and I am still running the 4.2.2 .54 version.

Uninstalling app problem: Some users have reported a 'soft reboot' after uninstalling apps, but I have not reproduced this problem. (For example, I have installed and removed "Android Terminal Emulator" without issue.) My observation is that testers have resolved this issue by starting from scratch (applying 4.2.2 sbf), so I suspect erasing userdata (not in SS:TWRP but in fastboot) may be related to this issue. (If you decide to go this route, be sure and make a backup any valuable data.)
[Moto X Android Development] matt68000:
Right, trying to uninstall apps caused a soft reboot. Trying to open Settings->(Wireless & Networks)More...->VPN simply quit the settings app as did the Settings->Security.

I flashed fsg.mbn and NON-HLOS.bin again, booted to TWRP and re-installed your OP modem archive there again, then booted normally and the issue is resolved. I can't re-create the conditions now but at least re-flashing and including the fsg.mbn in the process and a re-install worked! :)

Thanks for your hard work!
[Moto X Android Development] Ctrl-Freak:
The official ATT SBF is out. Thanks Pzyduck.

I could not, however, get it to work by flashing the rom through SS:TWRP plus the modem and boot images through fastboot. The phone booted, but neither mobile data nor wifi worked. I tried flashing the new "fsg.mbn", and I tried the modem from the leak-ota, but neither fixed the problem.

At this point I would guess that the bootloader needs to be updated, but I am unwilling to try that until someone confirms that you can downgrade...
[Moto X Android Development] mj0528:
you can downgrade, i've downgraded at least 3 or 4 times getting root on 4.4 from 4.2.2. You just have to use RSD and erase userdata. If you don't erase userdata, you'll boot loop. jcase method downgrades the bootloader during the process as well
[Moto X Android Development] flashallthetime:
Downgrading doesn't always work, I have a unlocked boot loader and tried to downgrade from the camera ota to pre camera sbf and it failed, ota 's are the issue on some carriers.

On another point, I just rsdlite the AT&T sbf file, you need to put your apn's in if your not on AT&T, WiFi will work afterwards too

Sent on my Moto X
[Moto X Android Development] Ctrl-Freak:
Just to be clear:

- I never tried it, but apparently the att 4.4 leak bootloader lets you downgrade if you ran "flashall" from the leak

- of course my method of installing/rooting the att 4.4 leak lets your downgrade, because it didn't touch the bootloader

But the bootloader from the official 4.4 sbf could be different. It might not let you downgrade. We will have to watch and see. (I'm not going to try it. I like to keep my options open.)
[Moto X Android Development] mj0528:
I can personally say it will as I have downgraded from the official 4.4 on several occasions. Jcase has mentioned this as well. It's in many different threads so don't just take my word for it. Look around the moto x forums.
[Moto X Android Development] flashallthetime:
I couldn't , so its carrier based, I accepted the camera ota from rogers and afterwards I flashed a ROM but it resulted in bootloops , same with my nandroid, so I had the pre camera sbf file that would not flash gpt.bin failed. DE phones can if you only accepted the DE ota's. Every phone is different, so please use caution. My boot loader is unlocked also

Sent on my Moto X
[Moto X Android Development] Ctrl-Freak:
Thanks. (I thought you meant root on the leak via SS:TWRP. I didn't realize you meant root on the official 4.4 via SlapMyMoto.)
[Moto X Android Development] mj0528:
yea, sorry I should have mentioned that the locked variations can. Ctrl-Freaks creation was for AT&T (locked and able to downgrade) so that was what my comment was based on. I went through the downgrade to 4.2.2 from 4.4 several times before I could get slapmymoto to work. After downgrading 3 times, i finally got slapmymoto to work.

sent from my slapped at&t kitkat moto x
[Moto X Android Development] dudumaroja:
I really wish for a AT&T unbranded rom, is there a way to take a Verizon rom with AT&T radio?

Enviado de meu XT1058 usando Tapatalk
[Moto X Android Development] freak4dell:
It has been established that the camera OTA upgraded the bootloader to a version that would NOT allow downgrading back to the first build. This was true on any carrier. However, the 4.4 OTA allows downgrading to the 4.2.2 build with the camera update. This is true on both AT&T and Verizon, and I'd be very surprised if it isn't true for Rogers when that update comes out. It will not allow downgrading to the very first build, as far as I know. Basically, they didn't update the build date check on the bootloader this time around.
[Moto X Android Development] flashallthetime:
Thanks for the clarification, not planning on downgrading to jb anyways

Sent on my Moto X
[Moto X Android Development] mj0528:
Yup, that's what I said
[Moto X Android Development] Ctrl-Freak:
I fixed the modem issue, and uploaded the official att kitkat rom. As before, this method does not require you to update the bootloader and uses safestrap to install the rom and SuperSU.
[Moto X Android Development] mj0528:
you rock!! I rather use this than the traditional route from some reason so I appreciate it!
[Verizon Samsung Galaxy S 4] samsung_development:
I just bought a new Verizon Samsung Galaxy S4 and its running android 4.3 [MJ7] and after some research here and there I've found that ppl managed to keep rooted while updating to this version but what can I do in my case to root my device and install a custom ROM like the following http://xdaforums.com/showthread.php?t=2524644 since I already purchase the phone like that. Sorry if this might have already been posted or something...I've done some research ut I'm not quite familiar with the XDA-Forums. Once Again! Thank you! ;)
[Verizon Samsung Galaxy S 4] th3bl3d:
so far for MJ7 root there is only a method that is frowned upon at the moment called VRoot.

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

i reccomend reading the entire thread before attempting that method because its still up in the air on how safe it is. it has been confirmed working by several people though.

at the moment all you can do is root mj7 you cannot replace the bootloader and install custom roms unless a method came out overnight which i am unaware of. safestrap is not yet supported for mj7 either.
[Verizon Samsung Galaxy S 4] samsung_development:
Thank you! I will definitely take a close look to VRoot and see how it goes.
[Verizon Samsung Galaxy S 4] th3bl3d:
good luck! let me know how it goes, also hopeing for unlocked bootloader so i can start installing stock google roms!
[Verizon Samsung Galaxy S 4] dowens9603:
Root

To root or not to root. That is the questions.
[Android Q&A, Help & Troubleshooting] mtxx1:
i'm looking for one that does NOT replace my default camera from my aosp rom.

prefer to have 2 separate camera app,

currently i'm using the 4.2 photosphere cam, i flash it from a zip with aroma installer, it creates another camera & gallery app, and i can retain my original aosp camera from any rom i use.

it is said that the 4.3 photosphere is much better at stitching and better exposure control.

i want to try it, but without losing my original camera.

so far all the ones that i found must replace the original camera app to function on aosp rom.
[Vibrant Q&A, Help & Troubleshooting] akshayam:
Alright. let us get this straight. I have searched in countless number of forums for solving my issue but I'm NOT able to fix it.

I have a Samsung Galaxy S Vibrant T959. It currently seems to be "soft-bricked" (I always see a mobile connected to a computer and an exclamation icon in between). So to reset it, I have left almost not stone unturned. But no luck so far :(

As far as I remember, I happened to land it in trouble while I was trying to flash some secondary bootloader using ODIN.

I also tried the micro-USB JIG method by building a 300k-Ohm USB JIG on my own (using three 100k-Ohm resistors), but even that is not working for me. Whenever I connect my phone to my computer, it starts up and shows those three icons. The same happens when I remove the battery, insert it back and start the phone up again. The same happens for each of the numerous key sequences mentioned online for download/recovery mode. So literally NOTHING is working for me. I also tried OneClick.jar, Heimdall. None of them are making me lucky as the phone is not getting detected.

I believe there has to be a way to reset it somehow (although I seem to have screwed something seriously) but nothing seems to work for me. What can I possibly do now?

Attached images show the micro-USB jig that I made and the icon on my phone I see.
[Vibrant Q&A, Help & Troubleshooting] jrongi1:
From my experience if you can get that far you don't need a jtag. But you did say that you flash bootloader. So you ether need to get the right combo to get to download mode or you are done with out working bootloader. The only other thing that I can think of would be to do the unbrickable mod.

Sent from my Nexus 4
[Vibrant Q&A, Help & Troubleshooting] akshayam:
Thanks jrongi1 for the reply.

>> So you ether need to get the right combo to get to download mode or you are done with out working bootloader.

I have tried many, many combos for getting the download mode but no luck so far :( Can you suggest some if you are aware of one?

The only other thing that I can think of would be to do the unbrickable mod.

>> I tried to know about this but I did not understand what this exactly means? I believe this involves some sort of hardware rework. Can you please point me to steps to do this? Are you referring to this procedure? If yes, I don't believe it's a solution since that procedure is just a preventive measure and not a solution (that's what I understand after reading that whole thing out).
[Vibrant Q&A, Help & Troubleshooting] testomat:
Try that.

reboot computer, turn off phone, take out battery, put the battery back, hold volume up and down buttons and then plug in usb.
[Vibrant Q&A, Help & Troubleshooting] Woody:
This is from N00B_IN_N33D's MIUI guide stickied at the top.

Sometimes the key combo can be a bit precarious and the timing needs to be precise. I know that when I have taken my Vibes back to stock, it takes me more than a few tries to get it right. You've said you have tried the key combos several time, I think you should keep trying them and get your timing right. I would hate for you to screw up your phone when doing the Unbrickable hardware mod, when it could be something as simple as a timing thing.
[Vibrant Q&A, Help & Troubleshooting] jrongi1:
As the other guys said work with the buttons and only try the unbrickable mod as a last resort.

Sent from my Nexus 4
[Vibrant Q&A, Help & Troubleshooting] akshayam:
Thanks guys for responses.

testomat/Woody, I tried as per your steps almost 8-10 times, but that does not work either :(

jrongi1,

I do not wish to go for Unbrickable mod either. Anyway, I have contacted a local repairs guy for this issue. He said he can fix this issue using JTAG interface. That costs me 1500INR. That's the only solution I have I guess.
[Vibrant Q&A, Help & Troubleshooting] jrongi1:
Good luck with the repair I hope that you can get going soon.

Sent from my Nexus 4
[Vibrant Q&A, Help & Troubleshooting] akshayam:
Thank you so much again! :)
[Vibrant Q&A, Help & Troubleshooting] adrianhall06:
This worked for me.....Many thanks :o
[Galaxy Note 3 Q&A, Help & Troubleshooting] RawR Cheeze:
Hi, theres almost a million threads like this but i have a simple question! im also new to XDA so excuse me if this is a stupid question...

I want to restore to a stock firmware but cant seem to find the stock firmware for my Note-3, I live in Finland so should i use the

Nordic Countries -IEE one or is there a firmware for Note-3's from finland?

Thank you.
[Galaxy Note 3 Q&A, Help & Troubleshooting] jaythenut:
try here www.sammobile.com
[One (M7) Q&A, Help & Troubleshooting] cr7hg:
Hi,

How stupid I was. I was trying to root my new unlocked htc one.. Unfortunately something went wrong and cannot get into system now at all.. Little phone comes up with red triangle in the middle and after a while it reboots itself and same thing happens again. I can go into fastboot mode, bit either factory reset or recovery end woth red triangle. Bootlocker is unlocked, Im able to lock it again, S-on and I cannot turn it off. I heard about ruu files but as far as I know I cannot downgrade when S-on. My os version is 2.24.401.8 and the newest I could find was 1.38 (something like this). My question is: can anyone do something about it? Is onlu solution to wait for newer ruu version than 2.24? Will it ever come out? If someone will help me bring my phone back to life I will pay you for your time.. Thanks
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Slow down mate, take it easy!!

Are you

1- unlocked (most important)

2- you said S-On

3- can you post a "fastboot getvar all" (remove IMEI and s/n)
[One (M7) Q&A, Help & Troubleshooting] cr7hg:
1- Yes

2 -Yes( tried to switch it off with no success)

3- I will do it as soon as I get back from work

Fs. Who buy a phone and break it same day
[One (M7) Q&A, Help & Troubleshooting] nkk71:
You're unlocked, so no worries you should be able to get your phone up and running. post back the getvar and we'll take it from there
[One (M7) Q&A, Help & Troubleshooting] PcFish:
That screen with the red triangle is stock recovery. Hold Power+Vol keys together to get into the menu to reset, etc.
[One (M7) Q&A, Help & Troubleshooting] cr7hg:
Thanks for giving me a hope. I will post it as soon as possible. I was pulling my hair out after I did it.. I wanted to get android 4.3 and did it with no problem on my samsung tab. I didn't think it will be so different. Well I was wrong
[One (M7) Q&A, Help & Troubleshooting] nkk71:
No hair pulling please :silly:

Since you're unlocked you can easily flash any ROM and get your phone up and running again, I do suggest (if you are willing) to get S-Off which will allow you a bit more flexibility now and in the future.

But one step at a time!! so, no hasty flashing, etc. and DO NOT lock your bootloader unless you are S-Off, otherwise there may be a chance you won't get it unlocked again.

How long till you get off work?