A little while ago, I rooted my S4 Mini and installed Android 5 custom firmware. However, my online banking app didn't like root, so I reverted back to standard firmware and removed the root. The phone works fine.
However, when running the OTA update, the phone tells me it cannot update due to root, and I should try using Kies.
I've installed Kies on my PC; plugging the phone in Kies tells me there is an update. It appears to download the required file but the phone does not update. I have tried with SmartSwitch also, but the same happens.
Can anyone please advise me on the following:
What is the latest official update for the S4 Mini; is it Android 5?
How can I update the phone? I thought flashing with Odin, but googling for various permutations of 'S4 Mini Official ROM, S4 Mini Android 5' etc. tends to yield results for the S4 and not the Mini...
Any help here would be great!
There is no official Android 5 lollipop for our S4 Mini. Best place to look is http://www.sammobile.com/firmwares/ should have all available firmwares for your model of S4 Mini. Flash the corresponding model of your S4 Mini and country code to your device and do this a couple of times over to fully restore your stock OS. I find without using an xposed module like rootcloak which doesn't always work that's stock is usually the only option to run apps that don't like root. I have the same issue with an app called channel 4 on demand which will only run on stock OS.
Related
Hello,
This is going to come off as noob-ish:
How can I flash a 4.3 TW-based ROM onto my rooted Canadian (Bell) Note 2?
I was running CeanROM5 for a while, flashed SlimKat 4.4 last weekend but I'd like to go back to TW.
I'm usually pretty familiar with rooting and flashing ROMs (Desire Z, Note 10.1, Nexus 7...etc.), but I've read too many horror stories of people loosing their modems, IMEI going wrong...etc. with the Note 2, especially since there's a few variations of the device, so I want to be careful.
I was going to flash the stock firmware from Sammobile via Kies but my phone is being detected as a i317 and not a i317m and I'm wondering if that's a problem? (I know I could use ODIN, but again, I'm worried about screwing up the modem with what little I know right now) I was then going to use CF-Auto-Root (as I'm sure I'll lose root) to clean things up.
TL;DR I've got a Canadian (Bell) Note 2 running SlimKat, how to get onto a TW-based 4.3 rom without screwing anything up?
Thanks guys!
So, after waiting hours for the stock 4.3 firmware to download from Sammobile - it was corrupt, so I'm re-downloading, therefore I can't flash via odin just yet (apparently I still have another 2 hours on this download).
Kies won't recognize my phone either (I suspect this might be due to the whole i317 vs i317m thing?). I've tried uninstalling and reinstalling kies on my PC, using different USB ports, and rebooting my phone...etc.
Again, any help would be super appreciated! Thanks!
Alright, so I'm running 4.3 and everything is working (wifi, modem...etc) but I can access superSU.
I used CF-Auto Root and it looked like it flashed the stock recovery. I have superSU installed but I can only open (not uninstall) it from the Play Store.
However, every time I do try to open it I get the pop up window "unfortunately, SuperSU has stopped".
So what am I doing wrong?
I guess this thread can be deleted as I seem to have sorted things out.
Philz recovery is very nice BTW.
After browsing the internet all day yesterday I never did see an actual fix for this issue for this specific model. I did see a lot of random ones for different carriers which would probably work. But not for Sprint specifically.
Problem? My Sprint Galaxy Tab 3 7" failed at 27% whenever I attempted to update it.
Issue: The Tab was Rooted by my brother - who then Un-Rooted and returned it back to Factory before giving it to me. Then failed to mention he had rooted the thing to begin with.
Fix: Re-Flash using Odin and stock 4.2 image.
So I tried getting Kies installed and working. Tab would NEVER connect no matter what I did. I tried installing the USB drivers again (though the computer recognized the damn thing), reinstalling Kies, trying to put Kies into Compatibility mode (since I'm on Windows 8.1)
After ALL that I finally called my brother who gave it to me as a gift. Found out the thing may or may not have been Rooted. But he thought he had reverted it back to stock and un-rooted it.
So back to searching on the internet. Finally found this article: http://theunlockr.com/2014/03/21/unroot-samsung-galaxy-tab-3-7-0-sprint/ which suggested I try re-flashing using Odin to get rid of Root on the device.
I followed the steps in the article (Tip: Do a search on Google for the correct image zip for your model tablet and download it from androidhostfiles) Example for my specific model T217SVPUANB8: http://www.androidfilehost.com/?fid=23329332407579787
Was able to restore it back to "true stock" and was able to update to KitKat. Kies started working finally. And all was well with the world again.
Oh, and I uninstalled Kies immediately after I was done with that POS software. :silly:
Hopefully this will help the I dunno the two other people that still have one of these that they received for free from Sprint.
Hi,
After upgrading OTA to kitkat (australia version) one of my favourite apps stopped working and caused constant reboots to my tab3.
I tried to downgrade with odin to the stock 4.2.2 (auatralia, from sammobile) but I could not. After flshing, the "samsung galaxy tab 3" logo appeared but the tab never turned on, it kept rebooting and rebooting from ours. I tried the same with other 4.2.2 roms with the same results. However I was able to flash any 4.4.2 rom from sammobile.
After that I tried to flash some 4.2.2 roms using twrp and bindroid, I had the same rebooting problems. However, with twrp I can flash 4.4.2 based roms as pimpdroid.
So, I do not why, apparently my tab only accepts 4.4.2 roms... Any suggestions about what should I do to go back to 4.2.2?
Thanks for your time,
A.
Bootloop in P5210
Hi I'm trying to get back to 4.4.2 to 4.2.2 works because although there are excellent applications like Facebook that are causing me problems. But in trying to make the retoroceso as I usually do with ODIN stock form and I was left in a permanent reboot and does not pass the SAMSUNG logo .... solution? Thank you!:crying:
@planinsky, Have you tried a firmware for another region in the world? I live in the United States but have found firmware for the United Kingdom or Canada works best when I flash. There should not be any difference in the firmwares except for regionalization, but it seems some work and some don't work for me. Regional settings can always be tweaked in the Settings panel after install. Do you have a nandroid backup made in TWRP? Those usually always recover a device. I too had a problem having anything flash when I first started making my rom. 3 weeks I had a device that would not boot. So it is recoverable. Odin will save your device.
@planinsky and @MDCB try to download this firmware from Sammobile. This is for the UK 4.2.2 version. http://www.sammobile.com/firmwares/download/28243/P5210XXUANB4_P5210BTUANB1_BTU.zip/
I usually use ODIN 3.07. I assume you know the following but just in case. Remember to flash it in the PDA slot. Only have "Auto reboot" and "F. Reset time" checked.
Using Odin will reset anything the 4.4.2 builds have done to the partitions. If it doesn't work, I can only suggest to try again. When it comes to flashing, sometimes the TWRP builds for our device can be a little goofy in writing. I have not investigated completely. In the 4.2.2 roms I have flashed pimpdroid and cagrom, they seem to flash good with Moonbutt77's philz recovery with very little problems. I however cannot get 4.4 roms to flash in philz but only in TWRP. So sometimes the recovery itself seems to have a problem with the android version, or so it seems.
The above is only written from my experience on this device and cannot predict every situation.
Good luck.
Hi! Thanks for the tips.
Ufortunately, I have already tried 4.2.2 ROMS from different countries (from Sammobile): Australia (the original country of my Tab), UK, New Zealand, Belgium and US. None of them worked. I'm still downloading other ROMS but I'm startin to lose the faith... The custom ROMS I have tried, neither work and get into the bootloop.
The backup I have from TWRP is from a 4.4.2 so it's not a solution.
On the other hand, I can flash almost any 4.4.2 ROM with odin and/or TWRP. So I'm afraid I'll soon give up and I will accept that my Tab will not longer run the app I loved (Movistar TV)... Hopefully with the arrival of lollypop the developers will update the app and the bug which causes the crash will disappear.
Hello Everybody,
I rooted my SM-G960F without problems few months ago. I tried LineageOS but I cannot cope with the camera quality. Then I tried Ambassadii Rom which was working great, till the phone started deleted some of the apps data.
For example, I downloaded maps on Here WeGo, after 1 day they were gone. Same issue happened with Spotify, every day I had to redownload all the playlist that I saved for offline use and often I ended up without music when travelling.
So I decided to flash the Stock Firmware again, but losing all the privileges of the ROOT (i.e. Magisk, Netflix, Samsung Pay, etc.).
I tried to repeat the root process to install Magisk, but I found out that the build number is 7CSJ3 and EX Kernel is not available yet.
Therefore I tried to downgrade the firmware first, however, I could not find any old firmware with binary 7 or above and hence it seems rooting is not possible.
Does anybody have a solution for any of the above?
Thanks.
Spanish ROM , find the suitable for you
Hi Zoira,
The only available rom is the 7CSJ3 and there is no EX Kernel available for that. All the other firmwares have a bootloader binary lower than 7, therefore I cannot flash it.
Any other solution?
I have an old Samsung Galaxy Pro 8.4 Tablet (the model is SM-T320 and called mondrianwifi) that I'm trying to breath life into. I rooted it with ODIN + CF AutoRoot and then installed TWRP. I was able to successfully install Lineage OS several times, but I never got the sound to work.
First I tried Lineage 17.0-20191204-UNOFFICIAL-mondrianwifi (Android 11) with the corresponding GAPPS for Android. I had no sound in the Samsung media player, when playing VLC, etc.
So I wiped it clean and tried Lineage lineage-13.0-20180121-nightly-mondrianwifi (Android 6) with the corresponding "gapps-arm-6.0-pico-20220215" ... I booted it up and all programs seem to run fine...except it also doesn't play any sound.
Both versions are supposed to be supported and compatible according to forums at xda-developers.com and the website I got it off of.
I then tried ColtOS v6.5Euphoria-mondrianwifi-20201109-Official - and that also installs with programs running but the speaker sound doesn't exist.
The only way to get sound is to plug a headphone into the 3.5mm jack or use a bluetooth speaker.
Googling lineageosroms.com shows the Galaxy Tab Pro 8.4 (SM-T320) is called Mondrianwifi, so the Roms I downloaded that have Mondrianwifi in their names should be correct. https://lineageosroms.com/mondrianwifi/#start-the-build
Any help would be appreciated.
@Intranetusa
The chosen ROMs are correct for your device.
To exclude the possibilty of a hardware problem I think it might be helpful to return to stock via Odin, test speakers and start all over again.
Btw. CF-Autoroot is afaik only necessary if you want a rooted stock ROM.
When planning to flash a custom ROM anyway there's no need for that.