Rooted with CF-AutoRoot, now every single new app is FCing - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

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

Related

Wtf samsung?

I'm having nothing but problems with this update. Feels like samsung just took dk28 and renamed it eb13. I went back to di18 from dk28 so that my phone can work properly thinking that eb13 would be worth the wait but nooooooooo now I'm back to frustration I felt using dk28. Damn samsung did y'all even try to test this or did y'all just rename and called it official?
Sent from my SPH-D700 using XDA App
Would help if you would at least list said problems.
Sent from my SPH-D700 using XDA App
mc-fine said:
Would help if you would at least list said problems.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Here go. Bluetooth once again will not stay connected. Facebook sync force closing checker board web is back wifi is dropping 4g is not worth a damn. volume levels adjust for no reason sms app hangs when sending a text gps takes for ever to lock. I'm going play around with this some more and see what else happens
Sent from my SPH-D700 using XDA App
I installed EB13 using the windows installer, which totally wipes the phone and I'm having none of those problems. Not knowing how you installed the update it's hard to know what happened but perhaps clearing the caches would help.
i used odin which does a full wipe and im having no issues. im loving this
I updated using the .exe file on the Samsung site and I'm not having any of the issues you listed. And after wiping my memory card it would appear my issues with my media files are gone as well...
Sounds like you should wipe, reinstall and see what happens.
I updated no problem...and ill be damned....I can play farmvile on my phone now...FML
Sent from my Epic 4g Runnin Froyo...rooted for my pleasure!!
Tbtltdts said:
I updated no problem...and ill be damned....I can play farmvile on my phone now...FML
Sent from my Epic 4g Runnin Froyo...rooted for my pleasure!!
Click to expand...
Click to collapse
Kinda makes one think Apple may have actually been on to something lol
poit said:
I installed EB13 using the windows installer, which totally wipes the phone and I'm having none of those problems. Not knowing how you installed the update it's hard to know what happened but perhaps clearing the caches would help.
Click to expand...
Click to collapse
Just did that seem to run a lot better now
Sent from my SPH-D700 using XDA App
The more I'm reading the more it sounds like the safest, cleanest way to go is the full flash/wipe. I guess I'll have to test how good my data backups are after all...
How do you do a full wipe!?
Sent from my SPH-D700 using XDA App
slevenkelevra said:
How do you do a full wipe!?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Basically the full Sammy installer through a PC *sounds* like it will do it. But the recovery boot menu also has an option for clearing the cache and I wonder if that is good to do also before that, just to be thorough.
DroidApprentice said:
The more I'm reading the more it sounds like the safest, cleanest way to go is the full flash/wipe. I guess I'll have to test how good my data backups are after all...
Click to expand...
Click to collapse
I think that's true about the full wipe method. The update.zip method assumes that you've got a fully stock phone that you haven't messed around with. That assumption doesn't work all that well with the types who visit xda.
On the plus side, I was using a DK28 rom (quantum) and did a backup in clockwork. After I did the "full wipe" (.exe) method and then did the old 1-click to get root and clockwork back, I was able to go to "advanced" restore in clockword and restore just my data. It worked absolutely perfectly.
Please...please. I beg of you haha. Explain howexactly I would wipe my phone so that I would be able to get te update. I was fooling around and deleted the nascar app and because of this I'm not able to dowload it without and error messege.
Sent from my SPH-D700 using XDA App
slevenkelevra said:
How do you do a full wipe!?
Click to expand...
Click to collapse
sleven, you really should do some reading on the forums and you could easily figure it out: [GUIDE] How To Update Your Samsung Epic 4G to Official "EB13" Android 2.2.1 in the Epic 4G Android Development forum is a pretty damn good place to start. I'd use the Last Resort (Easiest) method if I were you, since you don't seem to be big on figuring things out. CAUTION!!! All three methods listed here will reset your phone to stock, though they will leave your SD card and it's contents alone.
If you want to "upgrade" rather than do a clean install so that you can save your settings & programs, follow this guide:
Download the update.zip file from http://www.multiupload.com/K1MHLS6SNX
Boot into recovery by
Power off your phone
Hold [Volume Down] + [Camera] + [Power] until you're in recovery
Clear cache 3x
Apply update.zip
DroidApprentice said:
Basically the full Sammy installer through a PC *sounds* like it will do it. But the recovery boot menu also has an option for clearing the cache and I wonder if that is good to do also before that, just to be thorough.
Click to expand...
Click to collapse
Droid, from what I understand the "full Sammy installer" completely reformats the partitions and installs a fresh copy of EB13 on Epics. However, I know there's a number of people who recommend booting into recovery (stock or CWM) and clearing the caches 3x in a row. I haven't always done that, but it does seem to clear up a lot of issues that people are having, especially if they flash with Odin / Heimdall.
slevenkelevra said:
Please...please. I beg of you haha. Explain howexactly I would wipe my phone so that I would be able to get te update. I was fooling around and deleted the nascar app and because of this I'm not able to dowload it without and error messege.
Click to expand...
Click to collapse
sleven, I guess I'm taking pity on you, cuz here's a guide to fix your little problem. Be advised, you'll need to have root privileges and a file manager that can navigate root, such as Root Explorer. If you need help getting rooted, see One Click Root & Recovery for the Epic 4G! v2.5.5 Now has ClockworkMod Redirector!
In the Wiki, check out All *.apks & Framework / Apps safe to remove
Download the Epic System Apps.rar file from http://www.megaupload.com/?d=20HJ9004
Unrar it with 7zip, Winrar, Winzip, etc.
Find the Nascar app you deleted and copy it to /system/app
As long as your /system/app folder is identical to the Epic System Apps folder from the .rar (it's ripped straight from a phone), you should be good to follow the guide I gave you in my previous post. Good luck!
Credit where credit is due: obviously I linked to many other people's guides, wikis, etc. Thanks a lot, cuz that's how I learned to do all this!
I didn't wipe and I have no problems at all. All I did was install and run gps status and now I get instant lock even in my house. It think it is going to take awhile for everyone to get use to the setting.
DroidApprentice said:
The more I'm reading the more it sounds like the safest, cleanest way to go is the full flash/wipe. I guess I'll have to test how good my data backups are after all...
Click to expand...
Click to collapse
With some people around here you might need to clarify that you mean to wipe the phone, not wipe with the phone....
Everything has been better than 2.1 for me (GPS, browser, etc), except bluetooth. Bluetooth still can't connect in my car.
If bluetooth would work, this ROM would be perfect.
Sent from my SPH-D700 using XDA App
at first my GPS seemed to be much faster and more accurate (locked into 2 meters!) but now this morning I can't seem to get a lock at all...wtf???
I used samsungs pc installer by the way. Maybe I'll try using Odin instead today...
other than that, which is a huge other, the ROM is running great. I did have to root and run the manual sensor calibration utility though to fix the screen lag
edit: Just did a battery-pull reboot and all seems to be well in epic FROYO land.

[Q] FROYO after root did not work

I was the stock ROM with my epic rooted ( so i could use wifi hotspot). I got a notice saying 2.2 was finally available, clicked install now and my phone downloaded and then restarted. Then it said install failed and gave me the option to reboot now.
thoughts on how to get froyo working?
Bj
Supposedly , it might be because the root deleted thbe bloatware. I reinstalled all te bloatware ad tried themanual install and it failed. I think you have to remove root and reset phone to stock
Sent from my SPH-D700 using XDA App
Samsung.exe
Its a pain...but once it updates the phone and you unplug it, its root galore!
Sent from my SPH-D700 using XDA App
will I lose all my apps and date files on my phone?
Yeah. That's why I said its a pain
Sent from my SPH-D700 using XDA App
Its basically odin
It puts it into factory settings and th flashes for a clean install
Sent from my SPH-D700 using XDA App
If you used one click root, and it deleted the Asphalt Demo, give this a shot. Also take a look at richse's post. This will keep you from having to wipe off your phone completely.
http://forum.xda-developers.com/showthread.php?p=11539382#post11539382
Use Backup to gmail to save your phone log and sms. Use tb or my backup to save your files and data. Odin to eb13 (get .exe file from samsung, install on windows, find .tar file in folder) and do your restores. Restoring data across different firmware is sometimes eventful.
Sent from my SPH-D700 using Tapatalk
as Klownin says, it's probably the asphalt demo missing. Why they have it set to remove that app when it's known to cause issues in the future with updates is beyond me. Should be left there for the user to back it up and remove it much like all the other crap is left!
99.999% sure the missing demo is your issue, and it can be fixed
To be fair, having clockworkmod in the one-click also breaks updates. If the updates are going to be broken already, why not remove useless files?
Get the cwm flashable eb13 from this thread and flash it with clockworkmod. It will update you from di18->eb13. You don't need to reinstall asphalt. You won't lose your apps and settings.

[Q] jflteatt not liking any kitkat roms

Hi, I was hoping to get some help and insight with the situation I've been dealing with. I'll give as much information as possible so that someone might be able to point me in the right direction.
I have an att galaxy s4 that was purchased and rooted before the mf3 ota that made everything so difficult. I've flashed several roms and decided to go with liquidsmooth 2.37 atm and I'm experiencing a few odd issues (stock mss not working) that no one else seems to have, but for the most part it's running very well. Lately I've wanted to go with a rom using the new 4.4 and I've tried a handful no matter what rom I try I have the same issues. so far I've tried CM 11, Omnirom and Gummy. With all of them everything runs very laggy and glitchy and will frequently freeze until it crashes and reboots. Every single time I've used whatever gapps are linked in the op for every rom and followed flashing instructions to the letter (wipe data/factory reset, wipe cache, wipe dalvik, flash rom , flash gapps, flash super su (if needed) and reboot) and I've even tried different recoveries (both cwm recovery 6.0.4.4 and the latest philz cwm recovery) same results every time. This part shouldn't matter, but I tried flashing these roms while on the original mdl modem and after upgrading to mj9. Let me know any other info you need, but I've tried to be thorough. I appreciate the help.
So what firmware are you on right now?
scott14719 said:
So what firmware are you on right now?
Click to expand...
Click to collapse
I'm guessing mdb
sorry thought i mentioned the firmware is mdl
Rockman195 said:
sorry thought i mentioned the firmware is mdl
Click to expand...
Click to collapse
Looks like you're doing everything right. Have you checked md5's of your downloads?
I don't know how to do that or else I would
Sent from my SGH-I337 using xda app-developers app
Rockman195 said:
I don't know how to do that or else I would
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
http://onlinemd5.com/
Thanks for the link. I'm looking into md5 checking and I downloaded the hash droid app. My only question is when I calculate the md5 of a file what am I supposed to compare it to?
Sent from my SGH-I337 using xda app-developers app
Rockman195 said:
Thanks for the link. I'm looking into md5 checking and I downloaded the hash droid app. My only question is when I calculate the md5 of a file what am I supposed to compare it to?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
You should compare it to the md5 typically posted where you download the file from
Ok so the dl site like devhost or whatever
Sent from my SGH-I337 using xda app-developers app
Rockman195 said:
Ok so the dl site like devhost or whatever
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Correct. I usually just compare the last 5 or 6 characters. If they match it's very unlikely the others won't too.
tried going back and looking in all the threads that I downloaded roms from, can't find md5s for any of them with one exception and thats an outdated version of a rom I'm not currently trying to flash, so I don't see the point in downloading it just to compare the md5
Downloaded an omnirom build and checked the md5 and everything was good, plus I would be surprised if the md5s were bad on all the roms I've tried. Any other suggestions? Should I try two recovery instead of coming?
Sent from my SGH-I337 using xda app-developers app
Rockman195 said:
Downloaded an omnirom build and checked the md5 and everything was good, plus I would be surprised if the md5s were bad on all the roms I've tried. Any other suggestions? Should I try two recovery instead of coming?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'm running out of ideas try twrp recovery. Here is a zip you can flash in your current recovery http://forum.xda-developers.com/showthread.php?p=45511518
flashed twrp and that royally screwed up the phone. opened recovery using twrp and made a back up then did a system wipe and went to install the rom and when I went to do that, the list of all teh files you have to choose from was blank. I could go through different folder levels but the part where it shows the contents was always emtpy. Sometimes I could touch the area and see I portion highlight like it was making a selection but it wouldnt do anything and there was no file name there. Went to restore the backup I made and there was nothing in the list of backups to restore from. Rebooted the phone and liquid smooth 2.37 loaded like a clean flash with none of my info, files, apps, etc so I downloaded rom manger from the playstore and put the latest cwm touch on there. When I went in recovery none of my cwm backups where there or anything so i went to reboot and it only shows the samsung boot screen. Downloaded a few different roms and gapps on my sd card from y computer and put them on the phone and flashed the roms and gapps and still can't get past the boot screen. I'm really open to suggestions on this one.
If it was me, at this point I'd Odin the stock mdl firmware and start all over again. Something's not right with your phone. But it scares me a little since things aren't flashing correctly and there could be something wrong with your internal memory. If memory is bad it could make things worse.
I think your right. Do you know where I can find the stock firmware and instructions for flashing it? I haven't used Odin in a while.
Sent from my GT-N8013 using xda app-developers app
Rockman195 said:
I think your right. Do you know where I can find the stock firmware and instructions for flashing it? I haven't used Odin in a while.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
You can get the stock firmware at sammobile.com. it's free but you have to register. You'll download a zip file. Use 7-zip to extract the .tar.md5 file from it and use that in Odin, PDA slot. This is a guide that is not for the s4 but the procedure is the same. It has screen shots in it that help. Don't use any files in it though other than odin. Good luck. http://forum.xda-developers.com/showthread.php?p=26056924
I haven't read the whole thread, so hopefully these haven't already been covered.
1) Make sure your recovery supports 4.4. Not all of them do. Stay the heck away from TWRP because it's done nothing but suck for Galaxy S4, while it was absolute king for the S3. The wrong recovery can still flash a ROM but that ROM may not work very well.
2) Ensure you do a COMPLETE wipe. As in wipe /system and /data. Make sure your internal SD card is formatted. 4.4 may not use some things & folders that 4.2 and 4.3 did, which might cause problems.
3) If you have an external SD, then make sure 4.4 is using the right path for it to access any important files you may have on it, like apps2sd & such.
Well since screwing things up with twrp I'm back to having a working phone again. I didn't have to use Odin but I still might just to go back to stock and then try kit kat. I went into cwm recovery and formatted the system then flashed liquidsmooth 2.37 which is what I was running. Everything works fine with that except when I use the rom manager widget to boot into recovery, it goes to the boot screen with booting recovery at the top but doesn't go further. I have to use the 3 button method to get into recovery. The other odd thing is that mms works for me now.
I tried flashing gummy 4.4 again since everything is fine in jb but I still have the same jittery twitchiness. One thing I noticed is that when I go into the performance settings in 4.4 the current cpu reading will jump from 300 mhz to 1200 to 400 to 1800 etc just at idle. Is that normal. My note 10.1 holds steady when it's just sitting there.
To answer your questions, I'm using cwm 6.0.4.4 which is kit kat approved and I formatted and wiped everything before flashing and it didn't change anything. I appreciate your help so far and look forward to more insight.
Sent from my SGH-I337 using xda app-developers app

Flash Gordon has ruined my note 3

Well...(ruined) hopefully it's nothing that can't be remedied........?
I must have done something wrong. I installed busy box and downloaded inverted hangouts, selected the zip in Flash Gordon and wiped dalvik and pulled the trigger. My note 3 does nothing but display errors I guess system iu is screwed.......help!!!
Nothing will run getting the "unfortunately fill in the blank has stopped" error. I am afraid to reboot.
Am I hosed?
also I only have access to a Mac...does that make this worse?
Sent from my (inferior) iPad using Tapatalk HD
What update are you on. worse comes to worse put it in download mode (vol down+home button+power button from phone off) and odin the pit file and tar for the update you are on
http://forum.xda-developers.com/showthread.php?t=2483380
I am still on 4.3 I have never messed with Odin ....coming off of a galaxy nexus I don't remember what I used to obtain root and unlock boot loader on gnex.
Can this be accomplished using Mac?
Sent from my iPad using Tapatalk HD
mtnbst said:
Well...(ruined) hopefully it's nothing that can't be remedied........?
I must have done something wrong. I installed busy box and downloaded inverted hangouts, selected the zip in Flash Gordon and wiped dalvik and pulled the trigger. My note 3 does nothing but display errors I guess system iu is screwed.......help!!!
Nothing will run getting the "unfortunately fill in the blank has stopped" error. I am afraid to reboot.
Am I hosed?
also I only have access to a Mac...does that make this worse?
Sent from my (inferior) iPad using Tapatalk HD
Click to expand...
Click to collapse
Some bit of info is missing sir.
1. What Build you on? MJ7, MJE?
2. Rooted?
3. SafeStrap installed?
You dont need to wipe dalvik in Flash Gordon.. Just flash the the zip. Flash Gordon will not flash any flashable 100%. Check with dev of flashabel to see if compatiable.. If flashable is not written well it will not work. However the flashable(unless it messes with SystemUI) will not cause harm to phone.
Was is causing all the issues most likely is you wiped Dalvik... Just a shot in the dark sir.
Yes rooted
No safe strap
Mj7 (pretty sure)
Sent from my iPad using Tapatalk HD
Gunthermic said:
Some bit of info is missing sir.
1. What Build you on? MJ7, MJE?
2. Rooted?
3. SafeStrap installed?
You dont need to wipe dalvik in Flash Gordon.. Just flash the the zip. Flash Gordon will not flash any flashable 100%. Check with dev of flashabel to see if compatiable.. If flashable is not written well it will not work. However the flashable(unless it messes with SystemUI) will not cause harm to phone.
Was is causing all the issues most likely is you wiped Dalvik... Just a shot in the dark sir.
Click to expand...
Click to collapse
So, with the provided information...what is the fastest why out of this mess. I have windows on vm on my Mac but USB connection is flakey
Sent from my iPad using Tapatalk HD
I guess I am used to flashing on the gnex,,,wipe dalvik was common practice. FG is a different beast...I should read more carefully. If anyone can help turn this $700 paper weight into a functioning device again. I will hit you up with a little something via paypal. I feel dumb I did this....Got into a few hairy situations with the Gnex also. One day I might learn. Its hard when you have crackflash tendencies.
Thanks all
Sent from my iPad using Tapatalk HD
I could be wrong here but I've read time and time again about failures using virtual machine in lieu of the real thing. good luck.
Sent from my SM-N900V using XDA Premium 4 mobile app
I think you are right. ... kingo would not work on vm. Had to use a relatives pc over Thanksgiving:/
Sent from my SM-N900V using Tapatalk
mtnbst said:
I think you are right. ... kingo would not work on vm. Had to use a relatives pc over Thanksgiving:/
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
You're able to boot to Android, but can't navigate around correct? Everything just FCs and doesn't allow for input?
Sent from my SM-N900V using Tapatalk
Yes, exactly. ... pulled sim and battery. . And it all came back. And yes. .. hangouts is now inverted. I am safe straped and nandroided. Can't receive ota because I deleted bloat ware. I can live with mj7. Phew. ... Thanks for the reply
Sent from my SM-N900V using Tapatalk
Just FYi... I use a Mac, don't know about using a regular VM... but parallels desktop works perfectly for everything. You can get it free from everyone's favorite torrent site.
toddnbrown said:
Just FYi... I use a Mac, don't know about using a regular VM... but parallels desktop works perfectly for everything. You can get it free from everyone's favorite torrent site.
Click to expand...
Click to collapse
Wow parallels is legit!! VM firmware was not getting the job done. I was able to Odin MJE update then kingo back to root access. Thank you sir!!
Sent from my iPad (DON'T JUDGE) using Tapatalk HD

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...

Categories

Resources