Ok so as the title says im completely new to android os, and im alittle confused. But there is a very good reason for that. I bought my HTC One-x in china (i work and live here) and it is a Vietnamese vr. that came out of the box rooted and with a custom rom.
Now i have no idea what rom it is, but i know for a fact since i get a message telling me im not on official firmware when i try and update (i get an update request every time i connect to wifi very annoying).
basically i just want to update my rom to the latest if i have to go back to stock then so be it but if there is a good homebrew rom that will allow me all the features i had and doesnt have to many problems i would rather do that.
and ive been searching around for a guide on changing my rom but being in china alot of stuff is blocked or just a pain to go to and my vpn isnt always the best.
so the information that i do know:
software number: 1.28.707.10
android vr. 4.0.3
anything else that is needed i can post up. thanks for the help
Head to one of the other forums and follow the instructions for flashing a new rom 'to the letter'
http://forum.xda-developers.com/showthread.php?t=1786696 - this is recommended as a decent advanced Rom but there are plenty to choose from.
If you bought the phone and it already had a custom rom on then your device is Unlocked and rooted already....
Just make sure you;
Make a back up of current rom, in recovery.
Place the new rom on your phones sd,
Flash the correct boot.img to your phone whilst connected with usb and in fastboot mode.
Clear cache,wipe data in recovery
Flash your new Rom in recovery
Flash gApps if neccessary
Reboot phone and give a while for first boot to do its thing - perhaps 5 minutes.
Make sure you understand 100% what you are doing before you commit to any flashing beforehand
All the best
You have a pretty old version of firmware anyway. It was released in April. If you want the best stable Custom ROM, you may try ARHD 7.2.2 Just check it here in your search box. If you want to flash it, check if you have CWM. Just turn off your phone, then press volume - button and power (all together), then in white MENU (it is called Bootloader) check if your phone have unlocked bootloader (check for word "unlocked). Then select in menu RECOVERY. If you get in Blue menu you are in CWM recovery. You may flash custom ROMs from there. But any way to flash custom ROM or stock firmware you will need a PC. If you have any questions, just reply here... By the way, as i know all Developers put there ROM's names instead of sowtware version. You may have ROOTED and UNLOCKED phone but still running a stock firmware. Then you need to relock bootloader and flash RUU file (respectivly to your CID version) to get fully stock rom and you can get OTA updates after that.
Wow thanks guys this helps tremendously.
One quick question i see it kinda mixed all over the place but i am assuming i will have to back up all my files and what not for they will all be wiped?
but i guess i gotta do some focused research and i should be good to go soon. thanks again
When you wipe your data all of your apps will be wiped. So when installing a new Rom it will load a brand new set of the 'basic' apps so your phone is functional. There is an app - Titanium Backup - which can be used to backup and restore apps each side of the flashing process - the apps backed up by Titanium are untouched in the wiping process but instead are protected and can be restored as and when you need.
Also pictures / music / video is left untouched during a wipe as this is in a separate section from the 'wiped section'
Sent from my HTC One X using xda app-developers app
will contacts and all that be wiped as well?
jajangmien said:
will contacts and all that be wiped as well?
Click to expand...
Click to collapse
You can back up all your contacts with your gmail account and that will sync when you log in to the new rom. As for messages you can download a range of sms backup apps from google play
cool cool. well i think im about ready to give it a shot. thanks for all the help guys
Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
frankieGom said:
Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
Click to expand...
Click to collapse
I think using Exynos Abuse apk will do the work
http://forum.xda-developers.com/showthread.php?t=2050297
Thanks for the heads up, I'll look into it. But to be clear, that answers question 1, correct?
Sent from my GT-N7105 using xda app-developers app
frankieGom said:
Thanks for the heads up, I'll look into it. But to be clear, that answers question 1, correct?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Yes that's a way to root the device.
Regarding encryption, very few people on xda seem to use it. So for that reason you'll have trouble finding out what works... I do use it though through choice so I can help you a bit.
When you encrypt the device, just consider /data to be off limits to anything not booted fully. That's why it asks you for your key in swedish - it can't see what language is in use until you unlock /data.
You will have issues using recovery with the device, since they can't read /data. You can use an external sd to perhaps load data to the device though.
I believe that TWRP might soon support the Samsung encryption on the device, meaning you could use it as recovery. Once you have a recovery that supports Samsung encryption, you should be able to consider it a fairly normal device.
Just be more cautious to backup your data as it is hard to recover if something goes wrong...
If your using stock rom 4.1.2, exynos abuse method of root will not work. It's been patched
Sent from my GT-N7100 using xda app-developers app
pulser_g2 said:
Yes that's a way to root the device.
Regarding encryption, very few people on xda seem to use it. So for that reason you'll have trouble finding out what works... I do use it though through choice so I can help you a bit.
When you encrypt the device, just consider /data to be off limits to anything not booted fully. That's why it asks you for your key in swedish - it can't see what language is in use until you unlock /data.
You will have issues using recovery with the device, since they can't read /data. You can use an external sd to perhaps load data to the device though.
I believe that TWRP might soon support the Samsung encryption on the device, meaning you could use it as recovery. Once you have a recovery that supports Samsung encryption, you should be able to consider it a fairly normal device.
Just be more cautious to backup your data as it is hard to recover if something goes wrong...
Click to expand...
Click to collapse
Fine, I understand. As long as I have a way to recover my data if I need to wipe I'm okay... I just have to hope Titanium backup gives me that until TWRP can manage encruption on the Note 2.
I'm really waiting for a stock rom that boots in English or French now.
Sent from my GT-N7105 using xda app-developers app
vash_h said:
If your using stock rom 4.1.2, exynos abuse method of root will not work. It's been patched
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Not the case with xxdll1. When was it patched, xxdll4 or xxdll7?
Sent from my GT-N7105 using xda app-developers app
frankieGom said:
Not the case with xxdll1. When was it patched, xxdll4 or xxdll7?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
I am on Stock 4.1.2 and Exynos Abuse did work on my device, it's successfully rooted using the Exynos AbuseAPK on 4.1.2 :good:
OK, now I have been experimenting a bit with backups and upgrade and have trouble restoring my device fully. Let me explain...
I got hold of a TWRP build that seems to handle Samsung encryption fine through one of the TWRP devs (thanks!), so I decided to go back and try to update my device.
Current ROM: N7105XXDLL1_N7105TLADLL1_N7105XXDLK7_HOME.tar (obtained from Samsung Updates)
New ROM: N7105XXDLL7_N7105OLBDLL2_N7105DXDLL1_HOME.tar (obtained from Samsung Updates)
First I performed a complete Titanium Backup on the device and pulled the files to my laptop using ADB.
Then I restarted into TWRP 2.4.0.0 (got a prompt for my password), performed a full backup and pulled the files to the laptop using ADB.
(for some reason, I could not install the new ROM from TWRP (unable to open ZIP), but the ZIP looked OK, as well as after a second download which TWRP since did not like, so I had to use Odin instead).
Next, I flashed DLL7 with Odin. It worked, asked for the password at boot, but the device was unrooted at this point (I expected that).
Then, I flashed CF-Auto-Root-t0lte-t0ltexx-gtn7105.tar from Odin, but the boot up password would not be accepted anymore as I already knew.
Tried to flash DLL7 again from Odin, same thing
Flashed TWRP back on recovery partition, but on startup it would not ask for password anymore and the external sdcard looked empty to it.
I then copied my backup to a different, non encrypted sdcard and could restore from TWRP but the password would still not work after reboot.
I did a factory reset, restored backup, same result.
At this point I decided to factory reset, wipe Dalvik and format /data. The format did the trick and after TWRP restore of my original back up the device booted up, did not ask for password and all my data was there. Except the Exchange account I use for Corporate email wants me to restore encryption in order to work (I expected that too).
Back at DLL1, so I flashed DLL7 again with Odin (OK), rooted the phone, triangled away the flash counter and reflashed TWRP to recovery.
I was where I wanted to be except for one thing: I need to restore Corporate access. But when I let it encryp the phone it does nothing. I let it through the night and nothing). And if I reboot the phone no password is needed at boot time, yet the phone seems to behave as if it thought the device was still encrypted...
I reflashed my original, full, backup (i.e DLL1) succesfully but Exchange still wants to encrypt my device. Isn't restore supposed to restore the encrypted /data I backed up?
At this point I'm left with possibly tryinjg to go back to full factory settings, not use the backup at all, encrypt the device then restore my data from the Titanium backup I made.
Is there a better option?
[edited jan 18 - TWRP/TB behaviour]
My comments apply to encrypted devices only! I am not trying to talk down TWRP or TB here, as they provide splendid performance on non encrypted devices. I have come upon hard time trying to upgrade/restore an encrypted device using thoise tools, that's all
For those considering upgrading & re-rooting encrypted devices, don't!
I am finding the hard way that this is a one way street. At this point, my TWRP made full backup does not restore the device to the expected status. Each time I apply it, subsequent bootup takes several minutes and I end up going through the initial setup procedure. It seems the device for some reasoin goes through a complete reset procedure.
[edit]
Clarification: The TWRP build I use, 2.4.0.0 is an alpha build and I was not current when I restored my backup. I so happens that it was overwriting the encryption header on the partition, which messed things up bad, and had issues writing back the data partition, ending up in a factory reset status!
Using the latest drop as of today (jan 27) I was able to restore my original backup and am now back to my original state. All is well.
[/edit]
Titanium Backup is none better. It keeps telling me that my Android ID has changed, a host of system applications start to fail when I try to restore and generally speaking I have now spent between a good 20 hours trying to simply restore my data.
[edit]
this behaviour is probably linked to encryption. I know for a fact that TB works very well on non encrypted phones. The 20h figure is overall, not just with TB.
[/edit]
The end story is: root before you encrypt, and either don't upgrade or don't re-root if you do! If you do, be prepared for some rough times...
Unless someone has a cleat idea of how to do this properly without losing all your data, that is.
François
frankieGom said:
For those considering upgrading & re-rooting encrypted devices, don't!
I am finding the hard way that this is a one way street. At this point, my TWRP made full backup does not restore the device to the expected status. Each time I apply it, subsequent bootup takes several minutes and I end up going through the initial setup procedure. It seems the device for some reasoin goes through a complete reset procedure.
Titanium Backup is none better. It keeps telling me that my Android ID has changed, a host of system applications start to fail when I try to restore and generally speaking I have now spent between a good 20 hours trying to simply restore my data.
The end story is: root before you encrypt, and either don't upgrade or don't re-root if you do!
Unless someone has a cleat idea of how to do this properly without losing all your data, that is.
François
Click to expand...
Click to collapse
I have had no issues despite doing upgrades, with and without wipes.
Titanium is fine, just stop restoring system app data. Seriously, what data do you have in a system app that you want to restore.
Restore your user apps, their data, and the xml based call, sms, Wifi backups. It will work fine.
Device ID isn't a problem - it's just trying to help you.
pulser_g2 said:
I have had no issues despite doing upgrades, with and without wipes.
Titanium is fine, just stop restoring system app data. Seriously, what data do you have in a system app that you want to restore.
Restore your user apps, their data, and the xml based call, sms, Wifi backups. It will work fine.
Device ID isn't a problem - it's just trying to help you.
Click to expand...
Click to collapse
Sorry if I came across dissing Titanium Backup and/or TWRP. This was not the intent... I am sure both tools work real nice in general cases (and I have had success restoring data on a Jetstream before).
My main issue here is _full device encryption_ enforced by my company's corporate IT to allow me on the corporate exchange server. Do you have full device encryption on?
On my device, even after a full wipe and flashing a fresh stock rom Titanium Backup just did not work as I hoped. When I had to confirm individual popups of apps closing unexpectedly while it was proceeding and got nothing back in the end, what was I supposed to think? It could be that I don't understand how TB works... I was neither able to restore missing apps after the flash (missing apps: 0) nor installed apps data (they would close unexpectedly when started after restoring the back up). So I say: until full operation of TB on encrypted devices is documented, I will stay away from it, even though I am a registered user (and I do not plan to seek reimbursment)!
Anyway, I got to a belated happy ending (previous post edited).
frankieGom said:
Sorry if I came across dissing Titanium Backup and/or TWRP. This was not the intent... I am sure both tools work real nice in general cases (and I have had success restoring data on a Jetstream before).
My main issue here is _full device encryption_ enforced by my company's corporate IT to allow me on the corporate exchange server. Do you have full device encryption on?
On my device, even after a full wipe and flashing a fresh stock rom Titanium Backup just did not work as I hoped. When I had to confirm individual popups of apps closing unexpectedly while it was proceeding and got nothing back in the end, what was I supposed to think? It could be that I don't understand how TB works... I was neither able to restore missing apps after the flash (missing apps: 0) nor installed apps data (they would close unexpectedly when started after restoring the back up). So I say: until full operation of TB on encrypted devices is documented, I will stay away from it, even though I am a registered user (and I do not plan to seek reimbursment)!
Anyway, I got to a belated happy ending (previous post edited).
Click to expand...
Click to collapse
Yup I use device encryption Enabled manually, but it's the same encryption.
You should find that titanium shouldn't even be aware of it - the encryption is transparent!
I wonder... I'm sure lenny had that issue on a recent 4.1.2 "stock" ROM... And he doesn't use encryption...
I personally have had no issues with titanium on an encrypted device anyway
I notice you were using the newest rom - that's the one lenny had issues on.
pulser_g2 said:
Yup I use device encryption Enabled manually, but it's the same encryption.
You should find that titanium shouldn't even be aware of it - the encryption is transparent!
I wonder... I'm sure lenny had that issue on a recent 4.1.2 "stock" ROM... And he doesn't use encryption...
I personally have had no issues with titanium on an encrypted device anyway
I notice you were using the newest rom - that's the one lenny had issues on.
Click to expand...
Click to collapse
Exactly like I thought, encryption should be transparent to Titanium Backup since it runs within the OS.
I have had problems restoring into 4.1.2 DLL1 (the build I came from) and DLL7 (the one I was trying to go to)
The point is moot anyway since the DLL7 I tried was actually branded (Singtel stuff all around the launcher) and did not include French, which is why restoring my TWRP backup was a tempting proposition.
Good to know TB runs fine with encryption as well. What ROM are you running?
François
frankieGom said:
Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
Click to expand...
Click to collapse
About a backup : have you tried Online Nandroid (Playstore) (or similar, based on Onandroid) ? This makes a CWM or TWRP compatible backup while the device is running (everything should be unencrypted at this moment).
See http://forum.xda-developers.com/showthread.php?t=1620255
About rooting : you can try the same trick as above, by using ADB-shell and pushing the needed files to root to the device while it is running.
For my S3 there is a Toolkit that automates all this (http://forum.xda-developers.com/showthread.php?t=1703488), maybe there is something similar for your device ?
If not, you should still be able to do it using manual ADB-pushing.
I'm sorry I can't give you detailed instructions about the rooting as I'm not familiar with your device. Search here on XDA and you'll find more details.
pat357 said:
About a backup : have you tried Online Nandroid (Playstore) (or similar, based on Onandroid) ? This makes a CWM or TWRP compatible backup while the device is running (everything should be unencrypted at this moment).
See http://forum.xda-developers.com/showthread.php?t=1620255
About rooting : you can try the same trick as above, by using ADB-shell and pushing the needed files to root to the device while it is running.
For my S3 there is a Toolkit that automates all this (http://forum.xda-developers.com/showthread.php?t=1703488), maybe there is something similar for your device ?
If not, you should still be able to do it using manual ADB-pushing.
I'm sorry I can't give you detailed instructions about the rooting as I'm not familiar with your device. Search here on XDA and you'll find more details.
Click to expand...
Click to collapse
Thanks for the suggestions, and no I had not tried Online Nandroid as I was not aware of it. Anyway, my main issue is now resolved since TWRP has include support for Samsung TouchWiz based encryption in 2.4 and that works well.
For those interested, the only remaining issues I have with TWRP regarding encryption are that if you want to format /data from TWRP (say, to remove encryption) it will fail unless you _do not_ enter the password at boot, and the TWRP formated /data cannot be re-encrypted (you must use stock recovery to factory reset/wipe the device or else the encryption step will sit deat in the water doing nothing). I suppose the second one is a bug that will be fixed in a later version.
I will check Online Nandroid out anyway, being able to make a backup from a live system sounds good!
François
frankieGom said:
Thanks for the suggestions, and no I had not tried Online Nandroid as I was not aware of it. Anyway, my main issue is now resolved since TWRP has include support for Samsung TouchWiz based encryption in 2.4 and that works well.
For those interested, the only remaining issues I have with TWRP regarding encryption are that if you want to format /data from TWRP (say, to remove encryption) it will fail unless you _do not_ enter the password at boot, and the TWRP formated /data cannot be re-encrypted (you must use stock recovery to factory reset/wipe the device or else the encryption step will sit deat in the water doing nothing). I suppose the second one is a bug that will be fixed in a later version.
I will check Online Nandroid out anyway, being able to make a backup from a live system sounds good!
François
Click to expand...
Click to collapse
I have a similar issue. I had the device encrypted and decided to ROOT (using CF-AutoRoot). Unfortunately I cannot bypass the password screen now, although I know that I'm entering the right password. You are saying that if I flash TWRP everything will be fine?
ludovicianul said:
I have a similar issue. I had the device encrypted and decided to ROOT (using CF-AutoRoot). Unfortunately I cannot bypass the password screen now, although I know that I'm entering the right password. You are saying that if I flash TWRP everything will be fine?
Click to expand...
Click to collapse
Two separate things:
Root messing up encrypted touchwiz devices and twrp not handling touchwiz encrypted partitions properly.
The 2nd one, as much as I can tell, is fixed since before 2.5 so if youwork with the latest (2.6) you should be fine.
The first one I haven't played with in a while, but my finding is that you don't want to root a device once it's been encrypted. I've tried several different methods including rooting as you flag as is possible with twrp and all end up the same:the password is not recognised anymore!
The only thing that works for me is rooting before encrypting or only flashing pre-rooted ROMs.
frankieGom said:
Two separate things:
Root messing up encrypted touchwiz devices and twrp not handling touchwiz encrypted partitions properly.
The 2nd one, as much as I can tell, is fixed since before 2.5 so if youwork with the latest (2.6) you should be fine.
The first one I haven't played with in a while, but my finding is that you don't want to root a device once it's been encrypted. I've tried several different methods including rooting as you flag as is possible with twrp and all end up the same:the password is not recognised anymore!
The only thing that works for me is rooting before encrypting or only flashing pre-rooted ROMs.
Click to expand...
Click to collapse
Yes - I had to factory reset the phone and format the SD Card. Never root AFTER encryption :silly:
Hello,
my Samsung Galaxy S4 mini stutters / lags when scrolling. This appears in every app, systems setting, when scrolling in a browser or a menu or just going through the home screens (original TouchWiz). But games are running smoothly and also videos / youtube are free from stuttering.
So this is not a very big problem, but its making the use of the device not as enjoyable as before. To be honest: Its really annoying.
Some information about the devices / firmwares history:
- Bought the device originally from a market (not branded by a service provider) with stock ROM and Android 4.2.2.
- Used the phone for some months in its original condition. Not rooted, not removed TouchWiz, no custom kernels, etc. Everything was fine.
- Some weeks before the phone offers me the update to Android 4.4.2. Update was executed without any problem. Still no stuttering.
- Because of the new permissions for SD-cards in 4.4.2 I rooted the phone with towelroot and used "NextApp SDFix". No stuttering, SD-card ok.
- For backup purposes I installed Titanium backup (after SuperSU and BusyBox). Everythings fine.
- But some days later, without a clear reason, the stuttering / lags occurs and is there since then. Rebooting does not help.
What I have tried:
- Removed all newly installed apps.
- Temporarily unrooted, temporarily removed SuperSU, temporarily removed BusyBox.
Nothing helped.
Then I had done a factory reset. The phone started up like a newly bought device with Android 4.4.2. But still with lags / stuttering when scrolling!
A question to all the Pro's here:
- Which information can I tell you about the phone to give you a better view of the problem?
- May it be a problem in the kernel - so that changing the kernel would help?
I am also thinking about installing CyanogenMod, but if not necessary I would like to avoid it. I am happy with the look and feel of the stock ROM (I am simply used to it) - apart from the stuttering.
Model: GT-I9195
Android version: 4.4.2
Kernel version: 3.4.0-1646188 / [email protected] #1 / Fri May 23 19:52:02 KST 2014
Build: KOT49H.I9195XXUCNE6
SE for Android Status: Enforcing / SEPF_GT-I9195_4.4.2_0016 / Fri May 23 19:52:40 2014
Secure boot status: Type: Samsung
Thank you for any help!
Have you tried to flash your currently installed firmware again with Odin so far?
Sent from my black pearl using Tapatalk
nunein said:
Have you tried to flash your currently installed firmware again with Odin so far?
Click to expand...
Click to collapse
No, I have not tried that. So you would suggest the following (just to be sure to understand you correctly):
- Do a full backup with Titanium backup (for example).
- Get the stock ROM containing the Samsung flavour of Android 4.4.2 for Galaxy S4 mini.
- Flashing the device with Odin.
- Rooting again with towelroot, installing SuperSU and BusyBox.
- Install Titanium backup and restore my apps and settings.
Is this right?
ontheair said:
No, I have not tried that. So you would suggest the following (just to be sure to understand you correctly):
- Do a full backup with Titanium backup (for example).
- Get the stock ROM containing the Samsung flavour of Android 4.4.2 for Galaxy S4 mini.
- Flashing the device with Odin.
- Rooting again with towelroot, installing SuperSU and BusyBox.
- Install Titanium backup and restore my apps and settings.
Is this right?
Click to expand...
Click to collapse
Don't know if it will help, but it's not much effort and at least it will not hurt.
Full backup should not be necessary (data partition will not get wiped - if you do no factory reset), but is always recommended before flashing firmware.
Very important is that you will be flashing exactly the same stock firmware (with same CSC) as currently installed. In that case no data should get lost, no Knox tripped and so forth.
But as you mentioned, you will have to re-root (Towelroot + SuperSU) and run SDFix.
Thank you very much for your help and all these informations!
nunein said:
Very important is that you will be flashing exactly the same stock firmware (with same CSC) as currently installed.
Click to expand...
Click to collapse
On sammobile.com is just one ROM for Galaxy s4 mini containing Android 4.4.2, for my language, without carrier branding. So I suggest this is the right one...
Or are there any other ways how to additionally check if its the right stock firmware? Sorry for these questions, but I dont want to run into problems just because I picked the wrong firmware...
ontheair said:
Thank you very much for your help and all these informations!
On sammobile.com is just one ROM for Galaxy s4 mini containing Android 4.4.2, for my language, without carrier branding. So I suggest this is the right one...
Or are there any other ways how to additionally check if its the right stock firmware? Sorry for these questions, but I dont want to run into problems just because I picked the wrong firmware...
Click to expand...
Click to collapse
"Phone INFO ★Samsung★" is a nice app to check the phone status, it will show for instance CSC and firmware details.
From your information in the OP you run the same firmware as I do (the file name of my download was 'I9195XXUCNE6_I9195OXACNE6_I9195XXUCNE6_HOME.tar.md5').
nunein said:
"Phone INFO ★Samsung★" is a nice app to check the phone status, it will show for instance CSC and firmware details.
Click to expand...
Click to collapse
Thats great, thank you! I compared the informations provided by this app with the firmware on sammobile.com and its identically. So I will download the firmware now and flash it to the device (after the backup is ready).
I will keep you updated if the stuttering is away then!
In the meantime: Thank you very much for your help!
Finally I flashed the current stock firmware via Odin again. After flashing, the phone booted up correctly (in a non-rooted condition, of course).
But the problem is still present: When scrolling through any apps, lists or even the home screens, the movement stutters.
Are there any other things to check in order to get rid of this? A factory reset (done before) also achieved no improvement. That's really weird...
ontheair said:
Finally I flashed the current stock firmware via Odin again. After flashing, the phone booted up correctly (in a non-rooted condition, of course).
But the problem is still present: When scrolling through any apps, lists or even the home screens, the movement stutters.
Are there any other things to check in order to get rid of this? A factory reset (done before) also achieved no improvement. That's really weird...
Click to expand...
Click to collapse
Sorry to read that.Since you did a factory reset before I don't think it makes sense to do another one.
This is clutching at straws, but: is the issue still present if you remove your SD card?
nunein said:
This is clutching at straws, but: is the issue still present if you remove your SD card?
Click to expand...
Click to collapse
I have tried this now:
- Removing the SD card
- Removing the SIM
- Used another battery without NFC
- Temporarily used a CPU tuner app and switched the CPU temporarily to highest level.
But the problem is still present.
Additionally I found another new problem beside of the stuttering:
- Two heavily used apps doesnt react anymore and needed to be started again (Threema Messenger and Viber messenger). Seems like the system was under high load / low RAM and stopped the apps. But RAM consumption of the device is moderate.
- In YouTube sometimes videos are shown in a damaged way and just in black/white. After restarting the video it is shown correctly.
Im thinking of two last chances:
- Is there a way to create log files of the system and is there somebody who is able to find the problem seeing these logs?
- Or the last way: Switching to another ROM. In this case I can not use the backups created by Titanium, right?
ontheair said:
I have tried this now:
- Removing the SD card
- Removing the SIM
- Used another battery without NFC
- Temporarily used a CPU tuner app and switched the CPU temporarily to highest level.
But the problem is still present.
Additionally I found another new problem beside of the stuttering:
- Two heavily used apps doesnt react anymore and needed to be started again (Threema Messenger and Viber messenger). Seems like the system was under high load / low RAM and stopped the apps. But RAM consumption of the device is moderate.
- In YouTube sometimes videos are shown in a damaged way and just in black/white. After restarting the video it is shown correctly.
Im thinking of two last chances:
- Is there a way to create log files of the system and is there somebody who is able to find the problem seeing these logs?
- Or the last way: Switching to another ROM. In this case I can not use the backups created by Titanium, right?
Click to expand...
Click to collapse
With regards to your second question:
Of course you can restore user apps and related data from one ROM to another. And for instance contacts, SMS and call logs can be saved and restored with MyPhoneExplorer. Restoring data of system apps may work but may cause issues.
Ok! Thank you very much for your help!