Database Users

Bricked Galaxy S4

This is extremely frustrating.
I successfully rooted my galaxy s4.
I then downloaded CMW and touch, and downloaded this rom: http://forum.xda-developers.com/showthread.php?t=2341376
I then booted into recovery, and wiped etc and then installed the rom. I read on the later part of that page that there wasn't a need for loki so I did not download loki.
I then rebooted, and got the yellow triangle sign saying that the software is not approved by ATT.
This is where I am stuck. I have a mac and am running vmware windows 8.
I tried downloading kies on the mac, and it does not recognize the phone. I did not try kies for windows yet, nor do I know what to do after if I am able to get kies to recognize the s4.
I also downloaded odin, and the firmware, but odin is not recognizing the phone under windows even when I select to use the phone under windows.
I tried the stock usb cable, and a different usb cable, and 2 different usb ports. I do not have a regular windows computer. Is there a way to do this with a mac?
Guess I should have downloaded the loki, is not downloading the loki the whole reason this is happening?
I appreciate everyones help! I just wanted stock android! :good:

I do not have a s4 but have a s2 but its like the same.
1. Why would you not already have Odin installed and kies?! Just in case
2. No backup made?...
3. Can you still get into recovery and download mode if so then you have hope.. wait for someone to give you steps to get out of this
4. If you can't get into either... well :banghead:
Sent from my SPH-D710 using Tapatalk 2

XxlemonxX said:
I do not have a s4 but have a s2 but its like the same.
1. Why would you not already have Odin installed and kies?! Just in case
2. No backup made?...
3. Can you still get into recovery and download mode if so then you have hope.. wait for someone to give you steps to get out of this
4. If you can't get into either... well :banghead:
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Thanks,
1. I have odin and kies installed, they are just not recognizing the phone.
2. I made a backup using titanium backup but not really sure how it works... I've never restored from a backup using titanium
3.Yes I am able to get into download mode by holding the volume, home and power key...

drew1204 said:
Thanks,
1. I have odin and kies installed, they are just not recognizing the phone.
2. I made a backup using titanium backup but not really sure how it works... I've never restored from a backup using titanium
3.Yes I am able to get into download mode by holding the volume, home and power key...
Click to expand...
Click to collapse
Mmm alright... Go into download mode and take out your SD card and download the Loki file in the ROM thread then transfer to sdcard on PC. Then place back in phone.. Then go intro recovery and flash the file and it should work.
But wait before anything can you get into recovery? If so then you go to mounts and storage and mount sdcard and transfer the Loki file from your PC right there.
Sent from my SPH-D710 using Tapatalk 2

I have installed kies on the windows version and it notices the phone is connected, but it just keeps saying "connecting..." and a little thing spinning. Not sure how long it should take to connect...

why not download the loki zip to sd card, then put back on phone, reboot to recovery and install from sd card...

XxlemonxX said:
Mmm alright... Go into download mode and take out your SD card and download the Loki file in the ROM thread then transfer to sdcard on PC. Then place back in phone.. Then go intro recovery and flash the file and it should work.
But wait before anything can you get into recovery? If so then you go to mounts and storage and mount sdcard and transfer the Loki file from your PC right there.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Yes I can boot into recovery.
Wow I didn't even think of that... Sorry I am a noob.
Okay I fixed it (you fixed it thank you so much!) I booted into recovery, and then into the zip file and installed loki, and all is well.
STOCK ANDROID!!! Whew that was scary...

drew1204 said:
Yes I can boot into recovery.
Wow I didn't even think of that... Sorry I am a noob.
Okay I fixed it (you fixed it thank you so much!) I booted into recovery, and then into the zip file and installed loki, and all is well.
STOCK ANDROID!!! Whew that was scary...
Click to expand...
Click to collapse
Welcome
Sent from my SPH-D710 using Tapatalk 2

XxlemonxX said:
Welcome
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Because noobs don't get it.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

jd1639 said:
Because noobs don't get it.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Cool

drew1204 said:
Cool
Click to expand...
Click to collapse
You could thank him for helping you. Or is that too hard for you? There's even a thanks button to make it easy
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

jd1639 said:
You could thank him for helping you. Or is that too hard for you? There's even a thanks button to make it easy
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Mate don't be so arrogant, he did thank him.
Sent from my GT-I9305 using xda premium

ozgame said:
Mate don't be so arrogant, he did thank him.
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Mate,I don't see that
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

drew1204 said:
Yes I can boot into recovery.
Wow I didn't even think of that... Sorry I am a noob.
Okay I fixed it (you fixed it thank you so much!) I booted into recovery, and then into the zip file and installed loki, and all is well.
STOCK ANDROID!!! Whew that was scary...
Click to expand...
Click to collapse
the OP of that ROM lists these specific installation instructions:
HOW TO INSTALL:
* Download the ROM (NO NEED FOR GAPPS)
* Reboot to Recovery
* Wipe data/factory reset
* Flash the ROM
* U.S. MODELS - Flash Loki Patch - http://tau.shadowchild.nl/files/loki-doki.zip (CANADIAN USERS DO NOT INSTALL)
* Reboot your Galaxy S4
* Enjoy
remember to read everything first and understand what you are doing before proceeding. cheers

And only 5 simple steps. One sec of reading. And it matters. Or kaboom.

[Help Needed] Infinite Bootloop on Nexus 4

I have a N4 which was unlocked and rooted after updating to 4.3. I figured, I'd give Franco Kernel a shot so I proceeded to download the Franco Updater from Google Play.
Selected automatic flash and reboot and now it's stuck in a perpetual boot state. I attempted to proceed with a hard reset through the recovery mode; using ClockworkMod Recovery. I wiped my data, cache and dalvik cache and then went on to reboot system.
Up till' now, my N4 is on the boot Google screen. I tried doing the above steps multiple times but the results remain the same.
I'd appreciate if any help is directed on how I would be able to reset my device to factory settings. I don't mind going through the unlocking and rooting process again; I just need it to get through the boot screen

Go to the bootloader and run this tool: https://developers.google.com/android/nexus/images#occamjwr66v
It works every time.
Something went wrong with the flash for sure, I can tell in many ways so wiping will not help anyway unless you flash an other kernel.
This will wipe EVERYTHING so I don't know if it is worth flashing or flash an other kernel, you choose.
Sent from my Nexus 4 using Tapatalk 4 Beta

andyabc said:
Go to the bootloader and run this tool: https://developers.google.com/android/nexus/images#occamjwr66v
It works every time.
Something went wrong with the flash for sure, I can tell in many ways so wiping will not help anyway unless you flash an other kernel.
This will wipe EVERYTHING so I don't know if it is worth flashing or flash an other kernel, you choose.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Alright so I've downloaded the necessary file from your link, how do I go about running it? I apologize if this is a silly question to surface.

omgzam said:
Alright so I've downloaded the necessary file from your link, how do I go about running it? I apologize if this is a silly question to surface.
Click to expand...
Click to collapse
Make sure it is Mako/Occam.
What ever android version you chose extract the file twice until you get to the contents and run flash_all.bat, if the script says that you are missing the Fastboot file you have to get it from the SDK.
Make sure your device is on the bootloader which is unlocked.
Sent from my Nexus 4 using Tapatalk 4 Beta

andyabc said:
Make sure it is Mako/Occam.
What ever android version you chose extract the file twice until you get to the contents and run flash_all.bat, if the script says that you are missing the Fastboot file you have to get it from the SDK.
Make sure your device is on the bootloader which is unlocked.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm guessing this doesn't work on Mac? Because I'm currently on my Mac machine at work. If it's only for Windows, I gotta try it when I get home later.

omgzam said:
I'm guessing this doesn't work on Mac? Because I'm currently on my Mac machine at work. If it's only for Windows, I gotta try it when I get home later.
Click to expand...
Click to collapse
There is .sh has well which should work on Mac BUT you have to go though a lot with drivers.
FACT: Google Developers use Mac.
Sent from my Nexus 4 using Tapatalk 4 Beta

andyabc said:
Go to the bootloader and run this tool: https://developers.google.com/android/nexus/images#occamjwr66v
It works every time.
Something went wrong with the flash for sure, I can tell in many ways so wiping will not help anyway unless you flash an other kernel.
This will wipe EVERYTHING so I don't know if it is worth flashing or flash an other kernel, you choose.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Just to be clear, this solution is just to flash your device back to stock.

Rooted with CF-AutoRoot, now every single new app is FCing

I just rooted my Sprint S4 (MF9 FW) using CF-AutoRoot. Everything appeared to work - SU was installed, my file browser had root access, and I was able to turn on free wifi tethering.
However, literally every single application I have installed (sideloaded or through Play) since rooting is force closing. I even tried something really standard - the official Facebook app. No dice.
The only applications that work are those that I installed prior to rooting.
I used Titanium Backup to remove a handful of things - Sprint Zone, Sprint International, TripAdvisor, FlipBoard, and some of the preinstalled games. I haven't touched any system stuff or even any of the Samsung apps.
Help!

Best thing to do is start from scratch. DIAL ##786# and reset everything. After that if you still have problems, download latest firmware and Odin install it.
Sent from my SPH-L720 using xda app-developers app

Nautilusus said:
Best thing to do is start from scratch. DIAL ##786# and reset everything. After that if you still have problems, download latest firmware and Odin install it.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
What should I use for MSL?

shifuimam said:
What should I use for MSL?
Click to expand...
Click to collapse
Before you did the root did everything work okay?
Sent from my SPH-L720 using xda app-developers app

Nautilusus said:
Before you did the root did everything work okay?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Yep. Any app that I installed prior to running CF-AutoRoot loads just fine. The only application that I installed after rooting that DOESN'T force close is Titanium Backup.

First try this, reboot into recovery, twrp or cwm, and wipe just dalvik and cache but not data. This will force your phone to rebuild its app index and cache and should fix your problem. If that doesn't help see below.
Sounds like you may have deleted the wrong file using TB. You may want to download one of the stock rooted roms either odex or deodex (your choice) and dirty flash it. In other words don't wipe anything but cache and dalvik, don't wipe data. This way the install will replace the files you deleted and you should be up and running.

cruise350 said:
First try this, reboot into recovery, twrp or cwm, and wipe just dalvik and cache but not data. This will force your phone to rebuild its app index and cache and should fix your problem. If that doesn't help see below.
Sounds like you may have deleted the wrong file using TB. You may want to download one of the stock rooted roms either odex or deodex (your choice) and dirty flash it. In other words don't wipe anything but cache and dalvik, don't wipe data. This way the install will replace the files you deleted and you should be up and running.
Click to expand...
Click to collapse
Well, crap. I don't have CWM installed yet. Since I just got the phone yesterday, I don't really have anything on it - I'm fine with wiping it completely back to factory defaults.
I made backups of everything I uninstalled in TB. Should I restore all that first?
ETA:
I cleared my davlik cache via ADB. Rebooted, and now EVERYTHING - including system processes, like com.android.phone - is FCing.

You can try restoring, but I bet wiping cache and dalvik might be the problem. If you have the pro version of TB I believe you can do it from TB without installing a custom recovery. Also, make sure you do a reboot since that will often fix force closing apps.
Sent from my SPH-L720 using Tapatalk 4

Odin install the latest firmware.
Sent from my SPH-L720 using xda app-developers app

Nautilusus said:
Odin install the latest firmware.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
That's what I'm doing now. Still trying to find a copy of the official MF9 firmware that will actually download, though.

Try here...
http://www.sammobile.com/firmwares/1/
Sent from my SPH-L720 using xda app-developers app

Nautilusus said:
Try here...
http://www.sammobile.com/firmwares/1/
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I accidentally cancelled my hotfile download, so I couldn't restart it.
Is there a reason why these firmware files aren't on Bittorrent? It seems like a significantly faster and more efficient way to access such large files.

shifuimam said:
Yeah, I accidentally cancelled my hotfile download, so I couldn't restart it.
Is there a reason why these firmware files aren't on Bittorrent? It seems like a significantly faster and more efficient way to access such large files.
Click to expand...
Click to collapse
Just wait 30 minutes..... it should refresh. A torrent download of the firmware may be tampered with, so I would not mess with a firmware from there. It could potentially brick your phone.
Sent from my SPH-L720 using xda app-developers app

Nautilusus said:
Just wait 30 minutes..... it should refresh. A torrent download of the firmware may be tampered with, so I would not mess with a firmware from there. It could potentially brick your phone.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
No moreso than downloading Ubuntu off Bittorrent.
It's pretty easy to verify that a file on BT hasn't been tampered with - verify the hash of the file. If it doesn't match the original file, it's not valid. Hosting on a crappy site like Hotfile with ungodly slow download speeds in no way verifies that the file hasn't been tampered with. Since these firmware files aren't coming from Samsung or the carrier directly, you can never be completely certain that the file is valid and untouched.
I'd much rather see this stuff on BT where downloads don't take two hours. It's no less trustworthy than downloading from a horrible file upload site with ridiculous limitations.
ETA: the root I downloaded from XDA bricked my phone (even though the thread said multiple times that my version of the stock FW wouldn't brick). Can't trust anything on the Internet...

shifuimam said:
No moreso than downloading Ubuntu off Bittorrent.
It's pretty easy to verify that a file on BT hasn't been tampered with - verify the hash of the file. If it doesn't match the original file, it's not valid. Hosting on a crappy site like Hotfile with ungodly slow download speeds in no way verifies that the file hasn't been tampered with. Since these firmware files aren't coming from Samsung or the carrier directly, you can never be completely certain that the file is valid and untouched.
I'd much rather see this stuff on BT where downloads don't take two hours. It's no less trustworthy than downloading from a horrible file upload site with ridiculous limitations.
ETA: the root I downloaded from XDA bricked my phone (even though the thread said multiple times that my version of the stock FW wouldn't brick). Can't trust anything on the Internet...
Click to expand...
Click to collapse
Sorry to here that....... my reasoning for the torrent answer was to provide an explanation, I also would like a faster download speed but we are in, how shall I say, shady areas of the internet and taking a download from a familiar site and wait a while than a questionable download that takes 5 minutes especially when you could possibly permanently brick your phone (or worst..... do something that has you wondering what the hell is going on.)
Sent from my SPH-L720 using xda app-developers app

Nautilusus said:
Sorry to here that....... my reasoning for the torrent answer was to provide an explanation, I also would like a faster download speed but we are in, how shall I say, shady areas of the internet and taking a download from a familiar site and wait a while than a questionable download that takes 5 minutes especially when you could possibly permanently brick your phone (or worst..... do something that has you wondering what the hell is going on.)
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I guess what I'm getting at is that if the community used BT, it wouldn't be a questionable source.
Content on BT is not inherently questionable or risky. Canonical uses Bittorrent as both the official and the preferred method of downloading Ubuntu LiveCDs because it is so much more efficient and low-cost than traditional direct downloads over HTTP.
I get the feeling that the XDA community has developed the misconception that Bittorrent is only used for porn and pirated media, and has no legitimate or safe purpose - that's just not true at all. You also aren't required to use TPB as a tracker for a torrent you create.
Most major torrent clients include file hash checking as part of the standard download process, for the very purpose of preventing people from changing files mid-download or during seeding.
It would make quite a difference in how ROMs are distributed. I can guarantee you that downloading off Hotfile is no more secure than using BT. Just because you've download files off one of these "stock ROM" sites before doesn't mean that all their ROMs are clean and safe, and it doesn't in any way guarantee that the files they're hosting came from a reliable source.

OK, so for anyone with this issue:
You're pretty much SOL on trying to retain the rooted ROM as-is. The only thing I was able to do successfully was use Odin3 to reflash my phone with a stock Sprint ROM. For the record, my phone was running MF9 when I attempted to root it. I was able to reflash it with stock, unrooted MDC, and basic stuff appeared to work (I didn't test much; I was just trying to make sure the phone worked before flashing with a custom ROM).
I originally had no plans to install a custom ROM right away, because I wanted to mess around with the special "features" in the Samsung firmware. After this fiasco I didn't want to risk the same problems rooting stock, so I just flashed CWM in Odin3 and upgraded to the latest CM10 nightly. It's been stable so far.

You could have tried to fix permissions too.

Definitely tried that multiple times. I've noticed in other threads that CF-AutoRoot is unreliable on MF9, too.
Sent from my SPH-L720 using Tapatalk 4

shifuimam said:
Definitely tried that multiple times. I've noticed in other threads that CF-AutoRoot is unreliable on MF9, too.
Sent from my SPH-L720 using Tapatalk 4
Click to expand...
Click to collapse
So whats the best way to root the s4 on mf9?
Sent from my SPH-L720 using xda app-developers app

MJ7 Root........

For those who have taken the MJ7 update and realized that you can't regain root. Kingo is working on a solution. Verizon likes to lock their loaders so it takes a little time to break them. I had to take my note to a Best Buy store about an hour from where I live to have them reset my phone from what is being labeled a Softbrick. If anyone knows a way to root the SM-900V with MJ7 please let me know.
Thanks,
GoNavyMike

I took the update a week ago and just rooted with kingo yesterday..all I did was follow instructions withing the app and was rooted minutes later . ... Installed safe strap with beans on slot 2..all is well except I can't get the custom logo to go away from the boot up screen but I don't really care
Sent from my SM-N900V using Tapatalk

I have no idea why people claim kingo doesn't work. It works fine, I and many others have used it on newest update without issue. Also, this isn't development.
Sent from my SM-N900V using xda app-developers app

custom logo
gcforreal said:
I took the update a week ago and just rooted with kingo yesterday..all I did was follow instructions withing the app and was rooted minutes later . ... Installed safe strap with beans on slot 2..all is well except I can't get the custom logo to go away from the boot up screen but I don't really care
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
If you run Triangle Away app, from App Store, it will get rid of custom lock logo on boot up screen

GoNavyMike said:
For those who have taken the MJ7 update and realized that you can't regain root. Kingo is working on a solution. Verizon likes to lock their loaders so it takes a little time to break them. I had to take my note to a Best Buy store about an hour from where I live to have them reset my phone from what is being labeled a Softbrick. If anyone knows a way to root the SM-900V with MJ7 please let me know.
Thanks,
GoNavyMike
Click to expand...
Click to collapse
The Kingo does work for the Verizon Note 3. I literally just did it. At first, it kept saying not supported, but I tried it again with my screen timeout off and I saw that when my phone was connected to Kingo, something popped up warning me something was trying to exploit my phone, click on the box and hit install. Then not long after that your phone will reboot and grant permission stuff will come up. You can either do it this way, or under security uncheck verify apps located under unknown sources.

So on the kingo screen,when selecting the OS mine only goes up to 4.2.2. I am obviously running 4.3 on the note 3. Do I pull the trigger? Or am I missing an update?
Sent from my SM-N900V using Tapatalk

mtnbst said:
So on the kingo screen,when selecting the OS mine only goes up to 4.2.2. I am obviously running 4.3 on the note 3. Do I pull the trigger? Or am I missing an update?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Worked for me and mine said the same thing. "4.2.2" Took me a couple minutes or so and all is good!

I have been hung up on "waiting for device" (after fetching scripts) for about 10 minutes now. Wondering when I should pull the plug. ...
It's a no go... Maybe because it's VZ?
Sent from my SM-N900V using Tapatalk

Kingo works for mj7, if you get hung up on waiting for device, close the kingo app restart computer, open kingo, plug phone into a different usb port.
Sent from my SM-N900V using Xparent Green Tapatalk 2

YES guys, you can root your phone VIA Kingo even if you updated to the newer firmware. My scenario, got my N3 bone stock, rooted it on MJ9 via kingo and worked. Applied OTA update to version to MJ7 and lost root. Used kingo again and gained root. Works totally fine and SS works fine as well.

Still nothing. .I am running win 8 through VM firmware. I wonder if that's my prob. I get all the way to the last step and it hangs. I rooted my Galaxy nexus with this virtual win machine. I might have to borrow a windows laptop
Sent from my SM-N900V using Tapatalk

Kingo
Does anyone have a link to Kingo. I can't get mine to go in Odin, I click to import the file, hit start, and it doesn't do anything. Does the De la Vega file have to be renamed? I'm usually pretty good at getting these things rooted, this seems to be dealing me fits. I NEED ROOT lol
Other issue is that 7zip will not extract the de la Vega file, says it can't open as a archive

Why is this thread so long? Kingo works with MJ7. Nuff said. If the OP would of read the Verizon Note 3 threads for 10-15 minutes he/she would of found this out.

It works for most. I am not most
Sent from my SM-N900V using Tapatalk

mtnbst said:
Still nothing. .I am running win 8 through VM firmware. I wonder if that's my prob. I get all the way to the last step and it hangs. I rooted my Galaxy nexus with this virtual win machine. I might have to borrow a windows laptop
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
VM could definitely be part of your problem, especially if you do not have Internet access through it. USB connections can sometimes be flaky as well.
musicman625 said:
Does anyone have a link to Kingo. I can't get mine to go in Odin, I click to import the file, hit start, and it doesn't do anything. Does the De la Vega file have to be renamed? I'm usually pretty good at getting these things rooted, this seems to be dealing me fits. I NEED ROOT lol
Other issue is that 7zip will not extract the de la Vega file, says it can't open as a archive
Click to expand...
Click to collapse
RDLV does not work on MJ7, unless they have released an update.
http://lmgtfy.com/?q=kingo+root
Sent from my SM-N900V using Tapatalk

I have Internet through it. .. But the USB connection is extremely flakey. I wonder if I try 100 times. .. It's bound to take
Edit: Using the original USB cable for my galaxy nexus gets me 95% through the process vs 50% through the process with the Note 3 cable.
Siiiiiigh,
perhaps my nexus 7 cable will be the ticket...
This will be my first android device that does not have root privileges. $#%@
Sent from my SM-N900V using Tapatalk

The kingo app will do it, make take a few tries and you'll probably have to do it from an actual Windows PC, but it should work. I'd probably try to use a USB 2.0 port rather than a 3.0, if possible.
Sent from my SM-N900V using Tapatalk

Thanks, I won't have access to a PC for a few weeks. I will patiently wait
Sent from my SM-N900V using Tapatalk

Kingo does work. I tried literally 40 times no luck on new ota. Battery pull took out sd card rebooted. First try rooted.
Sent from my SM-N900V using Tapatalk

Ahhh, so there is hope! As soon as I get home I'm trying. Fingers crossed
Nope, tried all that. .. Nothing
Edit: I think Im on at least my 85th attempt...battery pulls, SD pulls computer reboots, different usb cables (note 3 cable is the least effective) Im even alternating USB inputs. anything I'm leaving out?
Sent from my SM-N900V using Tapatalk

Trouble Updating S4 AT&T

So I've had this problem for a while and I think at one point I knew what the issue was, but things came up and I guess I lost my place. I have a GS4 running 4.3 on AT&T, but if I recall correctly it took a long time (longer than it was supposed to in US) for even that update to become available to me. I'm not sure if this phone is set as a different country or something, but I seem to think that had something to do with it when I checked last time. Now when I check for updates, it does say I have an available update (KitKat?) but fails when attempting to update. Download is successful, but install is not. Baseband is I337ucuemk2 if that helps anything. Any help here would be appreciated, thanks.

Install is failing as some of the files it is trying to update has been modified. You would have to be on stock for the update to work.
Remember that there is no direct root method for KitKat yet.
http://forum.xda-developers.com/showthread.php?t=2616221 for more info
Sent from my GT-I9505 using Tapatalk

jmjoyas said:
Install is failing as some of the files it is trying to update has been modified. You would have to be on stock for the update to work.
Remember that there is no direct root method for KitKat yet.
http://forum.xda-developers.com/showthread.php?t=2616221 for more info
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I'm actually not rooted, already stock and still having errors still...any idea why that would be?

Anyone have any advice?

Anyone have any advice?
Click to expand...
Click to collapse
Have you changed any system files and do you have xposed running? They'll break the ota.
Edit, I should have read closer. I think there is an update.zip file you could flash in the general forum. I'll look and see if I can find it.
See post 2 http://forum.xda-developers.com/showthread.php?p=50667360
Sent from my Nexus 5

jd1639 said:
Have you changed any system files and do you have xposed running? They'll break the ota.
Edit, I should have read closer. I think there is an update.zip file you could flash in the general forum. I'll look and see if I can find it.
See post 2 http://forum.xda-developers.com/showthread.php?p=50667360
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks for the link, so I should just flash the md5 with Odin? Appreciate the help.

Imnice777 said:
Thanks for the link, so I should just flash the md5 with Odin? Appreciate the help.
Click to expand...
Click to collapse
No, flash the update.zip in the stock recovery
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
No, flash the update.zip in the stock recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok cool, thanks again...however now another issue. I've tried several times, I can not boot into recovery. Any time I try to the phone just goes black until I let go and then reboots. Even if I get the blue print in the top left, the phone does not boot into recovery. Any idea why this would be?

Imnice777 said:
Ok cool, thanks again...however now another issue. I've tried several times, I can not boot into recovery. Any time I try to the phone just goes black until I let go and then reboots. Even if I get the blue print in the top left, the phone does not boot into recovery. Any idea why this would be?
Click to expand...
Click to collapse
If you can get into download mode you may be better off flashing the md5 and Odin. Don't know why you can't get into recovery
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If you can get into download mode you may be better off flashing the md5 and Odin. Don't know why you can't get into recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Me either, guess I'd just flash normally like I would a rom? Or would an update be different. I haven't done this in a while.

Imnice777 said:
Me either, guess I'd just flash normally like I would a rom? Or would an update be different. I haven't done this in a while.
Click to expand...
Click to collapse
If you flash the tar in Odin it's going to wipe your device so backup what you can. You'll need to download the tar file to your pc and download Odin to it too if you don't already have it. You run Odin from the pc
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If you flash the tar in Odin it's going to wipe your device so backup what you can. You'll need to download the tar file to your pc and download Odin to it too if you don't already have it. You run Odin from the pc
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok so I finally got into recovery, but am I supposed to rename the file or anything? It keeps telling me:
"-- Verify the file type of MD5, Before Install /sdcard ...
-- Install /sdcard"

Imnice777 said:
Ok so I finally got into recovery, but am I supposed to rename the file or anything? It keeps telling me:
"-- Verify the file type of MD5, Before Install /sdcard ...
-- Install /sdcard"
Click to expand...
Click to collapse
Anyone ever see that error before?

Imnice777 said:
Anyone ever see that error before?
Click to expand...
Click to collapse
Are you trying to flash the update.zip? I'd re-download it. It could be a bad download
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Are you trying to flash the update.zip? I'd re-download it. It could be a bad download
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So... pretty unhappy. Downloaded the update.zip and flashed in stock recovery, it wiped my whole phone and still didn't update. I saw a couple error messages appear as it was "updating" so now I'm still on old firmware and lost everything on my phone. Luckily I did a Kies backup but still pretty ridiculous. I still lose all save data from apps and all convenience that there was from using my phone for as long as I did. Just wanted to update, shouldn't be this big of a mess. Not sure what to do next.

Imnice777 said:
So... pretty unhappy. Downloaded the update.zip and flashed in stock recovery, it wiped my whole phone and still didn't update. I saw a couple error messages appear as it was "updating" so now I'm still on old firmware and lost everything on my phone. Luckily I did a Kies backup but still pretty ridiculous. I still lose all save data from apps and all convenience that there was from using my phone for as long as I did. Just wanted to update, shouldn't be this big of a mess. Not sure what to do next.
Click to expand...
Click to collapse
Well that sucks. No idea how it works wipe you're device. It shouldn't touch the userdata. If it's truly wiped I'd Odin the nb1 tar at this point. Get it updated and start over
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Well that sucks. No idea how it works wipe you're device. It shouldn't touch the userdata. If it's truly wiped I'd Odin the nb1 tar at this point. Get it updated and start over
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That's what I did and I'm finally updated, but pretty disappointed that it took all that just for an update. Hopefully things like that don't continue in future updates...