[Q] The story of my Flash : A noob's journey - The Pros & Cons - Galaxy 3 General

This is my journey from Eclair to Froyo - read only if you have ample time. You have been warned !
I had never tried even rooting my Galaxy I5801 so I was a bit hesitant to upgrade my DDJG6 Eclair to DDJP2 FROYO even via Kies. After some days of the official release I finally plugged my phone to update. But alas, Kies constantly showed "operation timed out" (poor connectivity ?) and I was left with no other choice but Odin
DAY 1:
Downloaded the flashing package and the relevant firmware, connected and fired up Odin as per the tutorial. Loaded the packages and started the process with a prayer on my lips. The first boot nearly gave me a panic attack but the tutorial did calm me down and voila ! I had successfully flashed Froyo. Thereafter I also loaded my backed up contacts & memo data through Kies sync.
DAY 2:
I was happy with my effort and started explorin the possibilities of FROYO including app2sd. All fine until I decided to install a flashlite plugin later that day. The system starting freezin so I rebooted. The problem recurred and I again rebooted. This my boot screen got stuck on the "GTI5801 - Samsung" screen. I knew I was screwed but since I could access download / recovery mode (even though wipe data or cache didnt work) I knew it was only a "soft brick"
Day 3:
Geared up to reflash my phone through Odin. This time I took some unusual steps - removed bootloader & sbl and extracted dats.rfs from DDJG6 & added it to DDJP2 tar package. Flashing was succesful and I had started to sort of like the entire process.
Day 4:
Was disappointed with the improper implementation of swype so I decided to install swype beta. Root, delete, register and install - simple ? That's what everybody says.... Downloaded superoneclick, enabled USB debugging and rooted (Z4root didnt work). Now the delete process was tricky. Couldnt make sense of titanium backup so tried another method. Since root explored is paid app and terminal emulator is beyond my scope, installed super manager from market. Gave superuser permission and started deleting relevant swype files - I think it was 2 from /system/app, 1 from /system/lib and 1 from /data/data. Registered for swype beta and downloaded it as advised on the website. I write this post with swype beta.
Everything is working fine now - almost !
PROS - learnt flashing, knew the benefits of rooting, now can manage my apps and memory a bit better
CONS - My music player is screwed. For that matter, any music player I have downloaded and tried is having the same problem. The player doesnt play some music files, skips it or even if forced to play remains mute although the music play status bar moves. I checked the file properties and played them on PC. They are either Mp3 or M4a. Do I need to reinstall the music player coz it sounds like its become corrupted ? But then it plays some tracks flawlessly
I am in debt to XDA Galaxy 3 forum members and rudolf in particular for helping me out at crucial junctures. Now if only I could solve this problem !

jg6 is an eclair rom right? That could be causing problems, mizing eclair and froyo.
Did you do a factory reset after flashing (I suspect you did if you followed a tutorial).
Also, removing boot and spl is not unusal, it is HIGHLY RECOMMENDED, always do it! (this is mostly for other people reading this thread)

Nice story... Waiting for day 5+

@stubborn - yup, i did a reset but the music player problem persists. I included the data.rfs file from eclair to froyo coz I was somehow convinced that its absence in the DDJP2 had causes my system to freeze the first time
@kyrillos - Day 5+ testing isnt exactly detailed. The only thing I noticed is that the battery drain was more than DDJG6 eclair or maybe its the battery bug acting whimsically (as it usually does). Havn't modified or tested the GPS so no comments. Installed Gingerbread keyboard but not exactly to my taste. Still using a combo of swype and regular tap.
BTW - ur ROMS are damn good judging by the features, performance feedbacks and screenshots. However, It will take me another leap of faith to flash one of those since the complexity involved is beyond my current level of expertise (or rather the lack of it !)
Any ideas / tutorials on deleting the stock music player app and reinstalling it (with apk files, if possible) ?

Related

gapps/google talk/market/acore crashing/not working

Hi all, i have been having a very bazaar problem lately...When my phone boots up i get a pop-up message indicating that the gapps process shutdown unexpectedly...and sometimes i may even get a acore crash too. Applications from the market do not download...when i select my download i will end up getting a gapps crash and then the supposed download just sits there saying "starting...". Google talk doesn't even open! It will just say that the process quit unexpectedly. Even after a fresh install with factory data reset all these problems will continue. The initial boot up screen/tutorial will even show a gapps crash. I have tried with 3 different versions of cyanogenmod all with the exact same problem..Each version i've tried with a2sd enabled and disabled, formatting the partition each time before a new install to ensure no data carry-over issues. I don't know what to do. To me it seems like it make be something on googles side...but i can't for the life of me figure out whats causing these wild problems. Help would be very much appreciated.
ANDROID Market problems
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
six6star said:
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
Click to expand...
Click to collapse
I have searched and it seems many people have the Market/Gtalk problem.
I have the same problem (with an Eclair 2.1 Cyanogenmod rom) and I've not been able to find a solution. Wiping the cache makes nothing.
Anyone knows how to solve it?
Huh. I had a problem with the market at first with cyan 5.0.8 . I went in the terminal and ran fix_permissions after su and haven't had any problems since. Might try that
Sent from my HTC Magic using XDA App

Too many issues so few roms

3rd thread, about 4th rom flashed
constant issues with builds. have gone from stock to:
cm 6.1.3 -apps crashing, random crash notices i.e "phone book has crashed force close" - "the process com.android.phone has stopped unexpectedly"
cm 7 - random reboots, opening browser caused power cycle, wifi issues, lag (thread posted, no solutions at the forefront)
currently on tripnraver pre release. now another issue. no signal what so ever.
original baseband on this xperia x10a is .55. it is suggested to use with bands 52 or 49.
loading either of these basebands. which ive done. doesn't seem to fix the no signal problem. the description states should be backwards compatible even if appropriate bb is not installed on device. yet no luck.
attempting to flash either baseband fails to resolve this problem. currently trying to flash back to stock and try another full reinstall and baseband flash in flashtool.
any ideas would be a great help. having to flash x number of times between roms is getting quite time consuming
thanks everyone.
if you want to stay on the miui rom, you can flash the baseband patch located here and stay on whatever baseband works best for you (I'm on .55 and find it fantastic), then when you load the rom, go to dev tools>bad behaviour>crash the system server.
http://forum.xda-developers.com/showthread.php?t=1011608
Otherwise, I would recommend wolfbreaks cm 6.1.3, as it is the most stable. You must have done something wrong during installation as I never had an issue with his roms.
The only issue I have ever had with any rom is MiUi and thats because I used the wrong baseband. You must be doing something wrong for you to be having problems
if you want, try this flash, it's trips miui pre-final with the baseband patch implemented.
http://www.multiupload.com/KCKE9K2WKN
worked with my .54 baseband
thanks so much for the links to the baseband patches. i remember coming across a thread that posted it but unfortunately forgot to book mark. so im definitely going to go ahead and try with the patch installed. hopefully all works well
each rom ive flashed has been done properly according to instructions. cache wiped, dalvik, and full reset as per menu options in xrecovery.
one way or another i experienced lag for the most part, and as mentioned some random crashes. never had reset on wolfs rom just error messages at times. trips rom worked excellent, smooth and quick. hopefully with the patch implemented everything will work flawlessly
thanks you guys
*Updated
Flashed over rom with baseband patch. signal working. everything running smooth.
except for when using camera zoom. zoom default displays 0x. as soon as the option is selected it spawns an immediate force close
any patches? or similar outcome for anyone else?
i will outline my steps below so everyones up to speed on how i performed this flash.
- flashed back stock in SEUS
- root with one click (success)
- installed busy box (market)
- installed xrecovery apk
- booted into xrec
1. full factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
5. install custom zip from sd card
6. selected trips rom with bb patch implemented
5. reboot
Camera zoom doesn't work in most ROMs yet and the lag you were experiencing was likely just the FW "settling" it can take a little bit and a couple reboots sometimes for the phone to calibrate itself properly.
Sent from my X10i using XDA Premium App
thanks cmoney. maybe ill try my luck with cm7. give it a few reboots and hope for the best. great rom. im really loving trips iphonesque style
clean smooth and quick. everythings working great. hoping the zoom may get fixed soon enough. only other inquiry i have with regards to this rom is the apps2sd.
this feature is essential to myself personally. and it is not working as ive noticed on this rom. ive read a thread with regards to a fix for the last release. i checked the settings for an enable option in case the feature requires being manually set as active but nothing listed. within sd settings state reads as unavailable. if anyone has an answer as to whether this fix will function with the current pre release. ill be going ahead with completeling the flash and reporting what i find back on this thread.
thanks again everyone
Try Wolfbreaks rom. It's very very stable for me. It has cam and everything upto date.
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
thesoundofsilence said:
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
Click to expand...
Click to collapse
works for me on trips newest....
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
thesoundofsilence said:
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
Click to expand...
Click to collapse
I dunno man, it works fine for me, but I copied data from my 0.3.2 xrecovery image, so that might be why. try flashing that apps2sd fix for 0.3.2, should work fine
damn it. i just found that thread. found the links to the fixes. so far ive tried miui32_a2sd_fix.zip. and flashed that over with xrec prior to reboot. which did nothing.
there are two more links so im going to try those two flashes as well and hope that one of them will do the trick. if its working when utilizing .32 patches then ideally the bloody thing would have to work here. thanks for the input though dtox. much appreciated
I don't know what else to suggest man
From the feedback I see in the miui thread, everyone else is reporting it working!
Did you factory wipe, wipe cache partition, and wipe dalvik cache before install? then flash the miui 1.0.zip, and flash immediately the baseband patch then reboot into the rom.
Remember not all apps allow apps2sd so use something like android system info, go into the applications tab click on one, click manage and then see if the option "move to sd" is highlighted. Like I said check a few though, not all apps can be moved
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
thesoundofsilence said:
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
Click to expand...
Click to collapse
Try it again but without the fix...
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
thesoundofsilence said:
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
Click to expand...
Click to collapse
No idea man, like I said it is fine for everyone else so I'm so no big development will arise that will make it function with your phone....
maybe it has something to do with 10a. i dont know. but the point is it shouldn't even be doing this regardless. hypothetically if its froyo and it has apps2sd built in. it should work. its not the way ive flashed. the phone supports it. so my only conclusion the rom must not be as compatible as stated. and from reading different posts about the prev builds sometimes the patches worked at other times they didnt. and also the fact that the rom is claimed to work without the need for a bbpatch. yet without the patch instaled phone caught no single. i guess certain unexplainable glitches can be bound to happen at times but any how ill give it one last go.
if nothing comes out of that then im giving up on that build because it seems relatively hopeless.
lol I'm using an x10a...
Still man you're the only person reporting this. Don't you find that strange? What baseband are you using anyhow?

[Q] JVP really slow when booted with bluetooth on

I've flashed new JVP into my SGS using ramad's deodexed firmware with CF-root kernel and JKay skin. Then I restored my backup and used it for some time. After one reboot I noticed that it suddenly got much slower than it was - before I got quadrant score of 1900-2200, after it dropped to ~1300. After some investigation I found that there must be some problem with my settings - if I use some "clean" database (com.android.providers.settings) it works like it should but with my backed'up data it works fine only if I boot it with bluetooth turned off.
Can someone suggest what could have I done wrong?
Try to re-flash and use the stock Kernel, then see if you get the same problem. If not then only restore /data applications (Never restore /system applications) and see again if you get a problem, and so on..
You need to find out at which stage you get the problem, this could help isolating the problem so you can help finding a solution by finding out what cause it... in the way you are asking every member will give you a theory, try to find out by your self, devices are all different and so are the applications/settings/Kernels are all different on members devices.
Sorry for beeing so vague on the first post.
I did tried to isolate the problem - reflashed everything at least 10 times with different configurations. The result is I can show the exact moment when after restoring the backup phone starts to act weird.
Unfortunately the problem probably lies somewhere in my old settings as restoring only this one piece into the clean firmware (or - as my steps were - after flashing cf-root and installing theme) doesn't activate the slowdown. Unfortunately I also did a mostly clean restore - restoring only things I really need (contacts, bookmarks etc.) and only a few applications with data and for the rest of backup only applications. It didn't help.
Today I'll try another way - I'll reflash it and then restore only applications without any data and see what would happen.
Ok. So I did another round and for now I'm satisfied with the result.
What I did was:
1. reflash deodexed JVP
2. restored my user apps with data from backup
3. restored pieces of system data and configured missing settings
it worked fine up until this point
4. reflashed to CF-Root kernel - it seems this broke my setup. I'm certain that there must be something in my config/installation that when added to CF-Root and bluetooth introduces slowdowns.
5. as I needed my theme I just flashed it using CF-Root's CWM and after that I reflashed back to the stock kernel - everything returned to normal - quadrant score was back up at ~1300 (from around 700 with CF)
6. as I also wanted to convert to ext4 I flashed a Speedode kernel and I test the speed - it showed stable 1300
7. converted to ext4 using SpeedMod's CWM then rebooted and retested with quadrant - it holds fine at around 2200.
This closes the case for me for now
matofesi said:
Ok. So I did another round and for now I'm satisfied with the result.
What I did was:
1. reflash deodexed JVP
2. restored my user apps with data from backup
3. restored pieces of system data and configured missing settings
it worked fine up until this point
4. reflashed to CF-Root kernel - it seems this broke my setup. I'm certain that there must be something in my config/installation that when added to CF-Root and bluetooth introduces slowdowns.
5. as I needed my theme I just flashed it using CF-Root's CWM and after that I reflashed back to the stock kernel - everything returned to normal - quadrant score was back up at ~1300 (from around 700 with CF)
6. as I also wanted to convert to ext4 I flashed a Speedode kernel and I test the speed - it showed stable 1300
7. converted to ext4 using SpeedMod's CWM then rebooted and retested with quadrant - it holds fine at around 2200.
This closes the case for me for now
Click to expand...
Click to collapse
Good work, and you did it all on your own
Now you know what was the cause for your trouble and how to deal with such problem next time.
For others that find themselves in a similar predicament, but want an alternative method (or workaround), then keep reading.
I too am using Ramad's deodexed Rom's with CF-Root & have similar problems.
Ramad, I know it's not your Roms.
There is definitely something flaky after flashing CF-Root (no disrespect to Chainfire) , as I can replicate the faults again & again & again, with only the deodexed Rom & CF-Root, APN & WiFi setup. No user apps or anything else on the phone at this stage.
Certain problems then arise (lag is often noticed first) after the phone is restarted while ever WiFi & BT are both turned on prior to restarting the phone.
See my posts in the CF-Root thread here (Posts #2151 & #2152) which lists a few other problems which arise after flashing CF-Root, along with my workaround in post #2152.
It'd be great if Chainfire was able to get this issue fixed, as a workaround is never as good as a permanent fix.
If anyone found my workaround worked for them, feedback is definitely welcome.

!!!Stop SAMSUNG GALAXY S3 FREEZING Problems!!!

Well, here is my story...
My cell phone is a Samsung Galaxy S3 mod. GT-I9300. Locked for Digitel (Venezuela mobile carrier). Android Stock Rom version: 4.1.2.
Preamble:
I bought this cellular a year ago, and it worked flawlessly almost for 12 months straight. I haven't experienced any single freezing or rebooting problem. I downloaded KIES and the program detected that a new version of Android was available for downloading for my phone. Bump! Error. I should have backed up my EFS first before doing the upgrading. BACKUP YOURS, IMPORTANT!)
NOTE: Backup your personal data as well since any ROM installation will remove for sure your personal data and info.
After upgrading and a few days later, my cellphone started to act somewhat funny. I started to got some freezing. To be specifically, my phone started to freeze, the screen just froze and nothing happened when I touched the screen, pressed any button. The only thing worked was to restart the cell (by pressing and holding the POWER button or by removing the batteries). Anyway, the freaking freezing problems continue occurring.
By the way, the warranty expired just a few days ago...
Since I couldn't do anything to stop the freezing problems, I decided to root the cell and install a new version of Android not official for Samsung and test its performance. But before that, I factory reset my cellphone, but it didn't work at all.
I tested several Android version I could find on internet: cm-11-20140....-i9300.zip, specifically, the SNAPSHOT, STABLE, NIGHTLY version. None of that worked, I also tested the cm-10-20... without luck. In fact, the freezing problems with those versions got worse and worse.
Taking the above in consideration, I decided to re-install the stock rom version (ver. 4.1.0) the one that was shipped with my phone when I bought it. You can find these version for any carrier in the world at: sammobile
I flashed and I used it for almost a day or so. During that period of time, I could feel that the freezing issues were gone, not even a freezing event. But unfortunately, I couldn't connect to any Mobile Network!!, so I had just bricked my cell phone !!! I took it to the cell carrier company (DIGITEL) and they could not do anything since my warranty already expired. WTF ! I was alone with my own problem now to sort it out.
SOLUTION !!
By no means I mean this is a cure but I have just stopped getting the hellish freezing and rebooting problems, and I just wanna share my experience with you so maybe I could help you to get rid of this annoying issues for the time being.
Picking up where I was left off, all I had was my bricked phone and a working ROM: ver. 4.1.2, So I decided to to reinstall this version back on my phone and see if it connected to the mobile carrier.
I reinstalled it and of course, after erasing cache partitions and making a factory reset. The procedures to install any ROM on your cellphone you can find it on internet (for instance, youtube may help a lot).
After I installed the version 4.1.2. my cellphone could connect to the mobile carrier once again... phewww!! But the freezing problems continued to appear in the fuc# phone. Well, now the only option I had to test thoroughly my cell was to install any application one after another but testing if the application was the culprit for the freezing issue.
But right after installing the stock Rom, I got a error message when my phone run to the first screen (Home Screen): TOUCHWIZ stopped responding... it lit my LIGHT BULB! I searched the web for the TOUCHWIZ and found out reports regarding many problems with Touchwiz.
Holy craps! The TOUCHWIZ is a BUGGY APPLICATION that comes with the STOCK ROM developed by SAMSUNG.
My friends there is no way to UNINSTALL that application but to use another LAUNCHER. I fired up and decided to download KIT KAT Launcher. Well, I downloaded the launcher and when you first run this application a windows pops up so you can decide what launcher the cellphone may use and the time to use it. I select ALWAYS I press the HOME button, the launcher to use is KIT KAT.
In addition to that I disable various stuffs, follows (you have to go through the setting app):
Disable Touch wiz (delete CACHE, and FORCE STOP)
Disable GPS
Disable Multi Windows
Disable Swipe Lock ( I found my cellphone freezes a lot while this is on)
I don't use a lot of widgets... but only one: The Clock and Alarm widget.
So far (it has passed 5 days straight without freezing). My phone froze on me while I was downloading something (maybe the phone was updating an app) and at the same time I was texting someone. I am suspicious that there is something to do with the downloading system too and the phone that could trigger a freeze.
Anyway, if you have experienced the freezing issue on your Galaxy S3 just like me, then try what I just outlined and give it a test. But do not download a bunch of program at the same time, just pick one by one, and allow some time to test your application and check if your phone is stable before continue with the next app to download and so forth. I have downloaded so far: whatsapp, BBM, sudoku and other games.
Hope you can get rid of the freezing problems just the way I did, any question feel free to ask.
I will continue posting any advance with my phone.
FROYCARD
PS: excuse my standard English.
Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom
kariiim said:
Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom
Click to expand...
Click to collapse
Nope,, it didn't work with my cellphone. I already tested it. As a matter of fact, I can name you all the ROM I flashed to my cellphone:
cm-11-20131115-UNOFFICIAL-i9300-V2
cm-11-20140104-SNAPSHOT-M2-i9300
cm-11-20140117-UNOFFICIAL-temasek-i9300-V36
cm-11-20140125-NIGHTLY-i9300
cm-10.2.0-i9300
None of the above rom I used stopped the freezing issue, that's why I needed to return to stock rom, and since then I am using it without experiencing any laggy or freezing.
Thanks anyway. :good:
Isnt it possible to create a rom with all of Samsungs bloat ripped off (TouchWiz included) and replaced with stock apps?
The problem is that non stock kernel roms use up a lot more battery than the stock one...
what?
i havent got this
Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.
jinosong said:
Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.
Click to expand...
Click to collapse
Yeah,,, you may be right I am a newbie... but since I stopped using TOUCHWIZ, I have experienced fewer a fewer lock-ups. I dunno what it is happening with my phone, but that is a fact. I am using KITKAT launcher.
The current stock ROM I am using is: 4.1.2 .... (I9300UBEMH2)
I am not familiar with undervolting to lower my phone's temp... maybe you can guide me about using it, or I could search the web for it.
UPDATE: I installed TWITTER Apps yesterday and each time I used it, it froze my phone for 12 min approx. Any suggestion?
Read the freezing thread sticky .
Delete this non working fix as well .
JJEgan said:
Read the freezing thread sticky .
Delete this non working fix as well .
Click to expand...
Click to collapse
Why should I? Are you a moderator of this forum?
Well I just want to update my post.
Yesterday I just wanted to continue figuring this freezing problem out. Since I published my experiences about freezing until yesterday the problem appears to have reduced significantly. I was using stock ROM ver. 4.1.2 flashed with KIES.
But I wanted to continue testing other ROM's. I tried to install a ROM named SAMMY'S ROM developed by guy named JustArchi (that I found in this forum). However I could not install it on my phone (SGS3 - GT-I9300) since it gave me some errors when I tried to install: ERROR STATUS 7
A margin note: This techie or nerdie called JustArchi gave me the boot from his thread for trying to seek help on this error.. so I trashed this SAMMY'S ROM and move on with another solution.
Whatever, I downloaded another official stock Rom ver. 4.3, released by SAMSUNG, intended for IRELAND - I am not from Ireland, but Venezuela (I founded it at SAMMOBILE under the top 10 latest firmware just released). By using ODIN, I flashed my phone, and to tell the truth, my phone feels differently. I haven't experimented any sluggish or lagging, not even a freezing so far (knocking on wood).
For precaution, I am installing one app at the time, and giving it time to see if everything is stable.
Conclusion: to any guys who is getting the annoying freezing, I think you must stick with it until your mobile carrier makes ROM ver. 4.3 available. Otherwise, if you are like me, wanting to work things out for yourself, download any ROM (ver. 4.3 compatible with your phone model) and test it on your phone. Before doing that, you just have to search the Internet for directions to do so, I am not responsible for what you do with your phone. I'll keep updating if another problem arises.
Note: since I am getting some rude comments from senior members who think they are too techie to read newbie's comments, queries, etc. I am not interested in their replies since they are not helping at all, thus I just ignore your lame comments from now on. Just scram.
Dude, you're really not helping anybody here with your information here. I don't know what you think you're sharing. The error 7 pertains to recover error which can be eliminated by installing an alternate recovery version.
I don't care if you're a newbie or not but you are spreading false info.
I'll scram now.

Refresher on world of custom ROM's

Hi all
I have a Samsung Galaxy S5 G900F, which when I got it 18 months ago was very eager to get involved in rooting and getting a custom ROM on it.
Fast forward to present day and the novelty has worn off, I haven't kept up to date with anything, and I am probably very out of date.
As such I would like to either update to the latest ROM or just flash the latest stock - I am not sure I really use much nowadays that even requires anything other than stock (used to play a lot with Tasker, sysadmin apps)
What has prompted this is of late my phone has been very laggy, crashing, sys apps hanging, etc. I also dropped my phone ages ago and occasionally the screen stops working (although still responsive) and I have to take the battery out to get it back (sometimes it reboots to a full screen of coloured static, and I have to repeat this several times). Now I know this seems like a hardware issue but at times the phone will not have been touched or moved and it'll do this, which makes me hope that maybe updating it will help.
I have a paid version of Omega Files Pro but apparently there has been no update for a very long time.
Hopefully you guys can help me get back up to date and on a level
Android Version: 5.0
Baseband version: G900FXXU1ANCE
Kernel Version: 3.4.0-Omega-1.0
Build Number: Omega V17 - XXU1POCF
I have PhilZ Recovery iirc.
Thanks in advance, if you need anymore info please say.
Install the rom from alxndr thread. Its a stock rom slightly optimized. It is the best for stability, performance and battery. There is only great reviews about it, it has a great community, and he updates it very frequently.
He has roms for either android 5 or android 6, which could can find in the second post of the thread.
If you choose to install android 6, you will have to update the bootloader and modem. They, as well as instructions, can be found in his thread.
http://forum.xda-developers.com/galaxy-s5/development/rom-ane4-kitkat-4-4-2-multi-csc-t2813628
To correct the issues, you will probably need to perform a full factory reset before installing the rom. Before anything, I recommend you to do a full rom backup (using your recovery). That way, if you forgot to backup something (like your taskers profiles), you can always go back.
Before doing the factory reset, you should backup your SMS, calls and apps. The easiest way to do it is by using the integrated backup tools in your S5 options : in the backup&restore sections, you will find a Samsung section that can backup messages and phone calls. There will also be a Google section where you can choose to backup your apps. If everything is set up correctly, once you will boot the new rom, you will be asked sequentially if you want to restore the samsung (Messges, call logs) and google (apps) data.
Thank you I'll have a read.

Categories

Resources