Hi everyone, just tried to root my i9507 S4 for the first time. Went really awful. I used the Chainfire Auto Root from his website for Android Lollipop (this one to be precise) and attempted to get it up and running through the included Samsung Odin. It booted in successfully and I could reach the home screen. I had SuperSU and could open it - but I think something stopped working along the way and everything crashed at once after just a few moments (whether I opened SuperSU or not). Google Play didn't open. I attempted to do a full-install from SuperSU, which got rid of SuperSU but the problems remained, awesome. Rebooting now changed nothing. So I went to Sammobile and downloaded the correct firmware (this one), and I attempted to restore with Odin using the same method as I did rooting. Everything seemed to be going to plan with Android "updating" and the like, and SuperSU is still gone, but the same problem remains. As expected all of my data remained. I'm tempted to do a full-reset at this point but I'd like you guys' opinion first. I'm new to all this - as you have probably guessed! - so please be nice-ish (I deserve some of the flack I'm sure). Thanks guys
Just attempted clearing cache thru recovery (stock) - no changes.
Full wipe then install firmware with Odin.
Through recovery I presume?
Do this: open Odin, uncheck everything except f reset time. Flash ROM. When you see the word reset in the Odin status window, remove USB cable from the phone, remove battery, replace battery, boot into stock recovery, perform a data/factory reset, reboot.
This method will wipe all of your data.
audit13 said:
When you see the word reset in the Odin status window, remove USB cable from the phone...
Click to expand...
Click to collapse
Would this not brick the device? Thanks though.
You only see the word reset if the firmware was flashed. I do this for the note 1, note 2, note 3, s2, s3, and s4.
Related
ATT Galaxy S4 currently running Goldeneye 6.0 and TWRP 2.6.0.0 (never installed MF3 base, but have tried both MF3 and MDL modems)
First odd thing...
[About->Status->Device Status] is listed as "Sd card" instead of the more common "Official" or "Custom".
Anybody know what that means or is telling me?
This is the latest thing I've noticed with my phone, which has been having all sorts of issues lately that I cannot seem to figure out. My main problem is, I can reinstall a new ROM, boot into the ROM, change settings around, reboot just fine, but, as soon as I install anything from the Play Store, the next reboot will hang on the initial Samsung splash screen. Wiping is the only fix I've found, and fixing permissions in TWRP errors out with an error that it cannot chown one of the new/updated .apk files.
Both Goldeneye 5 and 6 are doing this now (5.0 was installed and rock solid for several weeks before this all showed up...it started sometime after I decided to try out a couple of the aroma roms and then came back to GE).
Used ODIN to go back to factory rom, re-rooted/installed TWRP, then reinstalled GE6.0, but the same thing happened. Everything looked good until I ran updates from the store, then I was stuck again (note: used Root Explorer to check to permissions on the updated apks before rebooting and they were all correct (755)).
Other things I've noticed are:
1. Sometimes, on any reboot, the startup locks at the initial Samsung screen and I have to long press the power button to get it to reboot. It usually boots the second time around (this is before I install any additional apps and am completely unable to reboot).
2. Sometimes when wiping cache, davlik, and/or data, TWRP will seem to hang for up to a minute when trying to initialize the partition. A couple of times it even hard reboot my phone when I did a cache+davlik wipe.
3. I rolled back to a recovery image just fine; however, it was a couple months old. Everything started off looking great, but once I updated to a new ROM, my issues returned.
Trying Heimdall to go back to factory; however, I'm having issue with my laptop and getting the Zadig drivers installed. While I'm working that out, figured I'd see if anyone else has any suggestions on what else I should be trying or looking out.
thx
I would flash your phone back to MDL stock with odin using the mdl tar. This should format your paritions correctly. You could also reinstall MDL using kies since they still don't support MF3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I have galaxy s4 gt i9500 and I m from india. I recently updated to lollipop and rooted by phone and installed philz recovery but later decided to unroot it using supersu unroot option. The strange thing is that i never got philz recovery but my phone was always rooted. All root apps worked fine. Anyways i decided to unroot it.
Now, after unrooting using supersu complete unroot option, i checked for updates and downloaded and ran the 326mb update available in india but the update always fails at 25% and when my phone boots normally , all apps force stop - yes all apps, i see only a black screen and errors of all apps that have forced stoped and only thing i can do is click on ok and power off or reboot my phone.
I cant boot into recovery as if i do that it goes to system update and throws an error at 25%
Please help, i have some imp data which i did not back up - phone is not detected in the pc / kies etc.
Extra info: I once did wipe cache partition and got the exact same issue when of all apps force stoppin on boot but then i went into recovery mode and did factory reset and all was fine.
Thanks - all replies appreciated.
you can't install official updates using a custom recovery
Sent from my GT-I9505 using XDA Free mobile app
Just download the firmware from sammobile or another source!
Download Odin v3.09
Extract (unzip) the firmware file and the odin
Turn off the phone and go into download mode by pres and hold the (Volume down key+Home key+Power key)
Run the Odin and add the firmware file in AP/PDA section
Connect the phone when you get the blue icon in com-id (Before connecting please make sure you installed the proper drivers of your phone. Recommended to install samsung kies3 it will automatically installs all the drivers)
Tick only auto reboot and F. Reset time boxes
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes.
This will install the stock firmware and all the errors will be gone after installing.
^^ Thanks!!
Will this process wipe all data of my phone or all the data will be intact ??
Sammobile has the version 5.0.1 and I am already on 5.0.1 - will it cause any issue ??
techspark said:
^^ Thanks!!
Will this process wipe all data of my phone or all the data will be intact ??
Sammobile has the version 5.0.1 and I am already on 5.0.1 - will it cause any issue ??
Click to expand...
Click to collapse
Its better to make a backup of your data. But this process will not wipe ur data. Better you do factory reset after installing the firmware because u r experiencing errors. No issue u can still install 5.0.1
Hi I was wondering if you were able to fix your problem. I have the exactly same symptoms with my phone however I got there in a different way.
I got myself in a big problem when trying to change the SuperUS app that go installed with [GT-I9500] CF-Auto-Root method.
I was able to root my S4 i9500 following the "[GT-I9500] CF-Auto-Root" threat a few days ago and everything was good.
Then for some reason (I still want to remember what was the reason) I decided to change the superUS app with Superuser clockworkmod app (I am a noob and I deserve this I know). anyway I downloaded the other app from google play and when I opened it say it has to instal the binaries, I said ok and the phone reset and went directly to download mode I believe.
It was doing something but whatever it did it failed. So I said ok not big deal I will reset the phone and end of story. However now when I boot up the phone when it passes the samsung logo and start to load up the OS every single app fails to load, "unfortunaly xxxxx has stopped" I press ok and then it goes to the next "unfortunaly yyyyyy has stopped" and the next and the next and the OS never loads. The screen just remain black until I press power and gave me the option to power off, reset, airplane mode, etc.
IS there a way to fix o revert this. I am able to get to download mode but ODIN does not detect the phone (odin detects the phone when the phone is in normal mode tho???)
I am able to get to the stock recovery too. Can i fix this from sd card?
any guidance would be appreciated.
Hey guys,
So I've got a problem. When I had originally rooted my phone in the beginning, I hadn't installed safestrap; I installed everything else: busybox, superuser, etc. So I kept on regularly using my phone and what not, updating and making sure I kept root. I was able to follow muniz_ri's tutorials to stay up to date and keep root. So eventually I was on OE1 stock rooted rom and had stopped there (accidentally accepted an OTA update after OE1 so I quickly froze the update thing [forget what it's called] through TiBU, hence not being on the most current firmware).
I wanted Snapprefs but needed Xposed. And to get Xposed, you need safestrap (from my understanding). I followed this to get safestrap (I think that's what the overall goal of the tutorial was for) and got safestrap working. Then, tried to install xposed using this and this. Successfully got the app, but then it said something along the lines of "you have not installed the framework" or something like that (that would be the zip file that I had to download right? The file that came from following the flow chart?). Used safestrap to install the framework (aforementioned zip file), then rebooted. However, after the Samsung Galaxy S5 menu and the safestrap menu, the screen just stays black. There is nothing. When I have my phone connected to the computer, the computer makes its jingle like it recognizes it (however, nothing comes up on the computer), the phone stays black for 2-3 minutes maybe, then boots into recovery mode (not safestrap recovery but stock recovery, where you use the volume buttons). I did a wipe data/factory reset (or whatever the option is called) in the stock recovery menu hoping it would fix something but it didn't. Just trying to include as much info as possible. Would flashing with this in Odin help? Read somewhere that it would put me back at square one so I could do everything over again, which I am not opposed to. However, I thought you couldn't downgrade from OE1 or anything higher?
I'm at a loss as to what to do next. Searched everywhere but couldn't find anyone with the same problem as me. Any help would be appreciated.
Thanks guys!
P.S. Sorry for going parentheses crazy
Found out what to do right after posting. Had to flash the BOE1 factory tar image in ODIN so back to stock, unrooted with all this bloat
Will be checking back periodically in hopes of a root method for latest firmware.
I have a Samsung Galaxy Tab 4 8” SM-T330NU running 5.1.1. The box tells me the ‘real’ model is SM-T330NYKAXAR. I decided to root the phone, because I want to get to Marshmallow and to get rid of this extra bloat where. (I will mention I have a good amount of experience rooting, including just rooting my Droid Turbo).
Anyway, after a lot of looking around the forums, I decided to use the CF-AutoRoot method (CF-Auto-Root-milletwifiue-milletwifiue-smt330nu) to root. I got Odin and installed it (along with the Samsung drivers) onto my Windows 10 PC; set debugging, on; and ran Odin. I followed the directions and it appeared to root properly; and I got to CWM recovery. Woo hoo! (Or so I thought)
So then after making sure I can get into recovery, I rebooted back into my stock ROM. Unfortunately, I got stuck at the Samsung logo; tried rebooting multiple times; even did a factory reset/wipe (as per instructions I saw on the forum) but to no avail. (Even let it set for over an hour but it never got past the Samsung logo).
After some more reading, I figured I might as well go ahead and flash a new ROM; so I think (if I remember correctly) I tried the JazzROM. It got up to about 69% and then it just quit - screen went black, and then it rebooted back to Odin mode. Obviously it didn’t work; then when I tried to get back into recovery to wipe and try the flash again, I got the message ‘Cannot mount \system - invalid argument’.
Again, after much reading and trying, I was able to get TWRP recovery installed and then wiped/formatted the system partition, which I had read would help get rid of that error. And it did seem to fix it.
So I can re-root with Odin without any issues; I can get to Recovery (either CWM or TWRP depending on which I flash), but no matter what I do, it either gets about 2/3 the way thru the flash process and then reboots back to Odin mode; or (using TWRP) I can get it certain ROMS to flash successfully, but after rebooting it goes right to Odin mode (saying it could not do normal boot). I even tried loading a stock, with the same result.
Which leads me to my first question: Exactly which ‘stock’ file should I be loading? I am having a hard time finding one - either it leads me to a dead end, or the download doesn’t work.
- When in CWM recovery, it shows the following:
At the top:
LMY47X.T330NUUEU1BOI1
Bottom:
#Manual Mode#
— Applying Multi-CSC...
Applied the CSC-code : XAR
Successfully applied multi-CSC.
Are these correct?
- When TWRP is installed (3.0.0-3) it starts by asking me about the ‘Unmodified System Partition’ and whether it should be kept read-only or allow modifications. I assume allow mods? Otherwise I don’t see how you could apply a new ROM? (I haven’t seen this in a while, not in my install of TWRP to the Droid Turbo). So just want to make sure I am selecting the right option.
- I am also concerned about whether I am using the right packages for this tablet. Based upon what I see on the box and sticker (which I still have) this should use the stock ROM LMY47K.T330NUUEU1BOI1 model; but I’ve also seen things referring to a BOG1 model? Mine is the T330NU English and (I assume) US model since I am in the US.
Any ideas as to what is going on? If I can at least get back to stock I could then start from scratch with the appropriate info; or just install one of the new ROMS (I’ve tried Jazz, Dirty Unicorns, UltraStock). I don’t think I am ‘bricked’ because if so I wouldn’t be able to get to Odin or recovery. Any help appreciated here. Thanks!
-Tom (Chimp)
NM, finally got it working, running DU and running fantastically, if I may say so. Getting TWRP to install finally fixed everything.
Sent from my SM-T530 using XDA-Developers mobile app
Hello there,
Today I flashed TWRP 3.0.2-1 using Odin 3.10.7 on my sisters Galaxy A5 2016 (sm-a510f). After that, I installed SuperSU 2.78 using TWRP.
Since that, the WiFi does not turn on. When you press the button to turn it on, it shows the "loading circle", and seems to do nothing. The circle stays forever.
Other than that, the phone appears to work fine. It did never report any error messages.
I already tried wiping cache, dalvik and data. I also made a factory reset using the option in the settings.
Later I found a newer version of TWRP (3.1.1-0) by Zonik . Flashing this did not fix the problem.
Do you have any ideas on what I could do to make it work again?
Edit:
In the meantime, I flashed a custom rom. Everything appears to work fine at the moment.
I didn't want to do that initially, so the phone could get the stock updates without me doing anything.
But still I am interested, what steps should I have done, to keep stock? And where might I be able to download the stock rom?
You should have flashed a later version of SuperSU.
You can use Samsung Smart Switch to restore factory settings.
Alternatively you can always find the latest firmwares on updato.com
Oh, I have just seen that I forgot to reply to that. I'm sorry.
@ashyx Thank you, I'm going to do that the next time. I was following a manual someone wrote on the Internet. I should have been smart enough not to trust a manual that's been lying around for some time.
@Vinhixus I tried that. Samsung Smart Switch did not like to do that (Don't ask me why, it said the device is not supported for factory reset).
Finally I "fixed" the wifi-bug by installing a custom rom wich i did not want to do in the first place because I did not want to change the OS on the device, just the bloatware samsung puts on their device.
Not much of a fix, more like a dirty hack to me
Thank you for your support
Actually you needed to flash correct modem. The custom ROM fixes it because modem was compatible for it. For the stock one you need modem that matches it i guess.