[HELP!] in VERY hot water... - Galaxy S II Q&A, Help & Troubleshooting

this is a long story, so bear with me, please:
i used to be on JPKH1 (this was the rom that came out of the box)
i was on XXKI3 when i decided to flash nightly #116 of CM7. i followed the instructions, got it working and had no real issues. however, i felt like CM7 made my phone old-ish (loved it otherwise), so i decided to return to a custom rom. prior to all this, i was on VillainROM 3.0
i flashed XWKJ3, business as usual, and then Batista70 rom. when i did that, something...strange, happened. none of the system functions worked (SNS sync, android system ringtones, etc.). i was overall dissatisfied with it, so i switched to Omega rom 6 XT.
i did that, and installed the relevant version of ICS domination theme by vertumus, and that's when it first happened - both the camera AND android system ringtones were force closing. also, when a system notification came on the unfortunate moment my phone was asleep, there would be a moving pixel on the screen and nothing else until i woke the phone up. nothing i did would fix it, and believe me, i tried EVERYTHING (restore nandroid, fix permissions, reflash rom). at last, i factory reset it, which did the trick but took some of the 'omega' out of 'omega rom'
i flashed stock XWKJ3, factory reset, flashed Omega 7 XT, and the problem persisted. it starts whenever i reboot the phone, for any reason, even if it doesn't change anything on the phone (just a simple power on/power off)
now i was pissed, and went back KI3 and VillainRom 3 and all SEEMED good. there were VRTweaks i wanted to use, but the above DID happen, after all. i rebooted into CWM recovery, took a nandroid, booted up again and sure enough, 'it' happened AGAIN!!!
this has me driving myself crazy, and no one on the Omega thread seems to believe in the existence of my post there (that's how well they're ignoring it). WHAT SHOULD I DO?!!!
by the way, i have NEVER flashed a .PIT file (since i've read in so many places not to touch that thing on the S2) and my binary counter is at a service-center-scaring 7. and for the love of god, don't just read this and go away (that's happened to me before), GIVE ME A HAND!!!

Stock rom via odin, and reroot.
Sent from HydrOG3N MOD S2.
Technology Evolves, Android Evolves.
HydrOG3N is THE Revolution.

tried that already
flashed KJ3, then omega 6
flashed KJ3, then omega 6
flashed KJ3, then omega 7
flashed KI3, then villainrom 3.0
or were you implying something else?

Try wiping dalvik/partition/cache before and after installing the custom ROM

I do that out of habit when installing custom roms, as in the above cases
Sent from my GT-I9100 using Tapatalk

Have you tried fixing permissions? Might be worth a try
Sent from my GT-I9100 using Tapatalk

the pixel on the screen is because of app called noLED or something like that just uninstall it like any other apk and your that problem will be solved it automatically installs when you flash OMEGA ROM

@thefaixy: well, solved i guess
@macdam: nope
Sent from my GT-I9100 using Tapatalk

Random but I had an issue on my phone that followed me through different ROMs and kernels like some sort of ghost.
Turned out to be a corrupted video file in my ext SD card which was basically crashing the phone constantly and causing all sorts of strange issues.
Sent from my Optimus 2X using Tapatalk

thanks for the suggestion, mungulz, but i suppose we don't have the same problem. i went through all my internal AND external data and saw nothing out of the ordinary
on that note, introducing another twist in this ridiculous predicament, NO app (and with the exception of root explorer, NO app) can see my songs (external sd). if i use root explorer to force an app to use it, the app force closes

and just a thought, but i keep fixating on the .PIT file. your thoughts?

Have you done a full wipe including user data? Might be something left over that us causing issues, take a titanium backup first though
Sent from my GT-I9100 using xda premium

if you mean the CWM one, then yes, plenty of times. basically, each time i flashed something on the phone in this period, i factory reset. if i do it now, that will temporarily solve the problem and i'm pretty sure of it. one reboot later, i'll be back in hot water
i'm aware, of course, that there are other ways of factory resetting...

1) Flash Stock KI3, with pit file and re-partition
2) Back up everything including the int. SD to my PC.
3) press *2767*3855# it will completely wipe your device.
4) Once phone reboots, place custom rom and pictures + titanium backup onto the int. SD
5) Flash a custom Kernel
6) Reboot recovery, wipe data, wipe system, Flash Rom.
7) Reboot and restore the DATA only
or without pit file and uncheck re-partition

i had to go for tuition, so i couldn't do all the things gasmias said; just factory reset with *2767*3855# and then restored the apps ONLY with TB. and...my phone is back!
huge thanks to all of you for trying to help (lol, too many thanks buttons to press) . i guess it was just corrupt left overs. but dammit, now i'm scared of putting VRTweaks back in . eh, i'll take a nandroid back up
in light of these events, anything i should keep in mind for my future flashing endeavors?

Related

Phone randomly rebooting, no mounting/formatting sdcard

Hey guys,
need some help here. Some time ago (about 4 weeks), my phone started to crash randomly. Example: I was listening to some music, suddenly the music stopped. I thought I accidentially unplugged my earphones, but instead, my phone rebooted, without any further notice. Since then I got those reboots several times a day, not only while listening to music, but surfing the web, doing literally nothing (during work, I suddenly hear my phone reboot while idling in my pocket) or accessing any app installed on my device.
I am rooted and use a custom kernel and a custom rom. At first I thought, maybe there's something wrong with your kernel/rom, so I updated those. (Was on LeoMar75's Revolution Rom 2.5 -> installed 2.7.1; updated to latest Siyah kernel, I think it was 2.0.1 or something) Of course, I did a full wipe, but it didn't help at all. The first day everything looked fine, but then the phone started crashing again. After some more time, I changed to CheckROM RevoHD 2.0 and then 3.1.1. and changed kernel to Siyah. 2.1.1. then DK-kernel 2.1. Always the same results, always random reboots.
In the end, I thought to myself, that custom rom/kernel might not work properly on my device, so I went into cwm, wiped everything, installed stock kernel and flashed original rom via Kies. But, I STILL got those reboots.
Just for the record, when I say "wipe", i mean going into CWM and wiping cache and dalvik chache, batterystats, doing a factory reset and formatting /system, /data, /sdcard and /emmc. But the last time I did this, I noticed that i could not format /sdcard, I could'nt even mount it. I'm on CWM 5.0.2.7. now.
After that much of annoying text, my question is: Am I doing something wrong or is my phone broken? And if I'm doing something wrong, please tell me what, 'cause I'm kinda desperate here...^^
Looking forward to your help
Check to see if any apps are installed to external SD. If so, move them to internal storage. Also, in my experience, uninstall Dolphin HD if you have it on your device.
Sent from my GT-I9100 using XDA App
Hi SaneinOne,
I have no apps installed to my external_sd. I only store some music there. Additionally, I delete all android related folders from my external_sd before inserting it into a freshly flashed phone.
About Dolphin HD, already heared of that, tried it, didn't help.
But thanks for your help
No clues? C'mon guys, please, I'm desperate.
Maybe it a hardware problem ...
Try using warranty.
Dont know what your rom is but .
I would clean phone and start over .
Boot recovery
Mounts and storage FORMAT cache sd card data system
Remove battery
Boot to download mode flash stock rom via Odin .
Clear Custom rom counter with USB jig if needed .
Return to service centre .
jje
tEsT_MaStEr, JJEgan,
thanks for your replies.
I flashed everything back to stock and reset the flash counter with my friends' jig. I returned the phone to my store, they said they'll send it to Samsung to check it up. Let's see what happens...
Yay, 6 weeks without smartphone...

My Note is very unstable - can't tell if it's a lemon or something I did

This phone was an insurance replacement from ATT, so alway a bit wary of these refurbished phones.
So for the longest time it has always been a bit glitchy, hanging, and unstable. I assumed it was a software problem, and something i had done wrong when flashing...but now I am wondering if maybe my phone is a lemon. Lately it has been rebooting randomly on its own,
I wanted to try flashing back to stock, just to start from scratch, and I did with Da G's stock rom . Then i just rooted it with Da G's root, and put on CWR. Then I flashed King Kang Rom. It's been still real buggy. Maybe I need to to stock ICS or JB then flash a ROM? OR maybe it's just this phone....either way not real happy with the stability i've been dealing with.
If youve tried multiple roms and stock roms and its still buggy then its probably the phone, I have got so many replacement phones that were duds
Are you doing a wipe between all those roms or just flashing one over the other? That could be a major problem that is easily fixed.
Yes, i do full wipes/factory reset in CWM every time.
I know i have seen some guys say you must flash like 3 times, so maybe i'm not flashing it enough times or something..? i also saw someone say don't touch your phone for 15 minutes after flashing. i have no idea if these tricks actually work or what. doesn't seem to be a definitive rule book on how to flash the right way
How are you restoring your apps? TB or letting Play reinstall them?
using TB. I usually do a just apps reinstall, then data
Was the TB backup from a different version of android, i.e. GB, ICS then installed on JB?
yes, i did create it on an ICS rom. you think that could be causing me problems?
Good possibility. I had the same issue. Moved from CM9 to CM10 and restored through TB. Lots of FC and reboots. Wiped and let Play reinstall everything, now its smooth.
great thought and worth a shot if that's what could be causing a problem. so did you lose all your data then with all apps? msgs, etc? sucks to start from complete scratch. i'll even miss call log
Lost data, but was able to d/l everything else. Messages and call logs were gone. It is worth it to have a working phone with out glitches. Let me know if it works.
Well a good test is to install a known solid ics problem free ROM like Padawan or Black ice? (exact name escapes me). If it works for u then over clock it to 1836 with setcpu and u will have a ROM VERY close to the JB rom smoothness but actually works.
If u still have problems then u may very well have a flaky phone.
(Oh yeah don't get to worried about stuff like wipe 3 times etc...old wifes tales. I haven't done that for over a year on 3 android phones. ). Also it is Safe to restore apps AND data with titaniumb (just not system data).
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
+1 on the old wives tale. Seems more like a placebo effect. I only wipe once, and I've flashed roms on tons of phones.
Sent from my Galaxy Nexus using xda premium
tried installing padawan...so far so good, have not overclocked yet....will report back
Some roms will format your system partition prior to flashing the rom while others do not.
Beyond the wipe of data, cache, dalvik and such, it is wise to go into " mounts and storage" and format the system partition while in CWM recovery.
This ensures that nothing remains on the device before the new rom image is pushed to the system partition.
I agree that wiping 3 times is a bit over the top, but wiping the entire image base before flashing a new one is almost always mandatory.....g
For future reference, you can back up call and sms logs and restore them without causing lags or fc. The logs are simple .xml files.

[Q] I777 shutdown & SOD issues with a twist

i have Slim's latest on my I777. i am having constant shutdowns & SOD's, like every few minutes. the twist is that i have had the same release of Slim on the phone before, several times in fact, and i had the occasional SOD, but not constantly like now. i have installed Slim a number of times because i like to try new ROMs, and i keep coming back to Slim cus i like JB.
this must be diagnosed, because i believe now that something was messed up a bit along the way of flashing ROMs, mods, and kernels, but our awesome ROM supporters in their threads have their limits they have told me, and i should ask here since this is a general question about the phone & system. i am seeking help here relating to the rest of the phone and system that may become damaged somehow, and i want to clean up my system to end this problem. logcat & last_kmssg linked below.
to be clear: i am rooted correctly, am running the right software for the I777, always check my MD5's from the phone before flashing, clear my caches when needed, wipe dalvik before flashing kernels, etc etc.
interestingly, i fully wiped/factory reset, formatted system, dalvik, wiped batt stats, and fixed permissions, then reinstalled stock Slim last night because i thought maybe my settings were trouble, so i decided to run an out-of-the-box Slim, changing only the dpi and launcher. no change.
i've tried Siyah's latest after running Jkay's kernel cleaner as well. no change. something is making my phone shutdown/SOD constantly, and it may not be the ROM. others don't seem to be having this issue. i have little running on the phone. just accuweather, Date in Tray Pro, and Apex Pro. no overclocking/voltage changes... nothing fancy at all. so i'm just perplexed.
here's the latest logcat: http://davidb.net/logcat_and_device_info(1).zip
here's the latest last_kmssg: http://davidb.net/last_kmsg
if any of you guys can help with this, then thank you in advance.
VR32 said:
i have Slim's latest on my I777. i am having constant shutdowns & SOD's, like every few minutes. the twist is that i have had the same release of Slim on the phone before, several times in fact, and i had the occasional SOD, but not constantly like now. i have installed Slim a number of times because i like to try new ROMs, and i keep coming back to Slim cus i like JB.
this must be diagnosed, because i believe now that something was messed up a bit along the way of flashing ROMs, mods, and kernels, but our awesome ROM supporters in their threads have their limits they have told me, and i should ask here since this is a general question about the phone & system. i am seeking help here relating to the rest of the phone and system that may become damaged somehow, and i want to clean up my system to end this problem. logcat & last_kmssg linked below.
to be clear: i am rooted correctly, am running the right software for the I777, always check my MD5's from the phone before flashing, clear my caches when needed, wipe dalvik before flashing kernels, etc etc.
interestingly, i fully wiped/factory reset, formatted system, dalvik, wiped batt stats, and fixed permissions, then reinstalled stock Slim last night because i thought maybe my settings were trouble, so i decided to run an out-of-the-box Slim, changing only the dpi and launcher. no change.
i've tried Siyah's latest after running Jkay's kernel cleaner as well. no change. something is making my phone shutdown/SOD constantly, and it may not be the ROM. others don't seem to be having this issue. i have little running on the phone. just accuweather, Date in Tray Pro, and Apex Pro. no overclocking/voltage changes... nothing fancy at all. so i'm just perplexed.
here's the latest logcat: http://davidb.net/logcat_and_device_info(1).zip
here's the latest last_kmssg: http://davidb.net/last_kmsg
if any of you guys can help with this, then thank you in advance.
Click to expand...
Click to collapse
Nothing jumps out at me but you need to backup your data and SDCARD to a PC, flash back to stock..... when stock boots up perform a factory reset and test with the stock firmware... if it work fine.... root and install the ROM fresh and clean and test without installing anything else. If it again is fine then install every app from the Market. if you want to restore your recent data afterwards that is up to you but There are so many variables that could be causing your issue and you need to step back and try to find the cause one step at a time.
shoman94 said:
Nothing jumps out at me but you need to backup your data and SDCARD to a PC, flash back to stock..... when stock boots up perform a factory reset and test with the stock firmware... if it work fine.... root and install the ROM fresh and clean and test without installing anything else. If it again is fine then install every app from the Market. if you want to restore your recent data afterwards that is up to you but There are so many variables that could be causing your issue and you need to step back and try to find the cause one step at a time.
Click to expand...
Click to collapse
thanks shoman. much appreciated for the tips.
You wouldn't happen to be using an aftermarket phone charger would you? I was working on a phone behaving like that and it was the charger. If you lifted up on the plug a little while plugged in, it would wake the phone from sleep and constantly restart it. It also did something to the ROM or possibly the Kernel cause it started restarting while not plugged in and the power button quit working. I used a known good Samsung charger and installed AOKP JB with the kernel that came with and it fixed everything. I replicated this problem with two different chargers. It is possible that the USB port on the phone was worn. However, no matter how I moved the cable with a Samsung charger, nothing bad would happen.
beaverslayer said:
You wouldn't happen to be using an aftermarket phone charger would you? I was working on a phone behaving like that and it was the charger. If you lifted up on the plug a little while plugged in, it would wake the phone from sleep and constantly restart it. It also did something to the ROM or possibly the Kernel cause it started restarting while not plugged in and the power button quit working. I used a known good Samsung charger and installed AOKP JB with the kernel that came with and it fixed everything. I replicated this problem with two different chargers. It is possible that the USB port on the phone was worn. However, no matter how I moved the cable with a Samsung charger, nothing bad would happen.
Click to expand...
Click to collapse
no I've never used one.
but it appears this was all caused by the app Screen Off And Lock by Katecca. I had the donate version. its always worked for me on every ROM up through ICS, but it seems to wonk out JB. I changed to Lock Screen App by Kenneth Cheng and have had zero problems in days now, which is a first.
Sent from my SGH-I777 using xda premium

[Q] I got a boot loop and almost bricked my phone and I don´t know why

Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
r1k1v1 said:
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
Click to expand...
Click to collapse
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
kunal1540 said:
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hmm, I don´t remember that the BlackBox 2.0.2 had any Framework...thats why I did a manual installation. But I will try the new version 2.1. Hopefully the problems may have been solved.
boomboomer said:
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Interesting. So I have to apply mods one by one? Or can I add multiple mods because corruption has already been solved?
On a side note, when I boot the phone the red exclamation mark that used to appear has disappeared. Does that means that I somewhat reseted the flash counter to 0?

[Q] Cannot Install new ROM, Status 7 error

So the other day my S3 gave up the ghost, and developed the hard-brick "QHSUSB_DLOAD" error. I have insurance so I was overnighted a new phone, and am sending the old one away. I believe this was related to a long-term power button issue I was having, perhaps a virus, or something. I had not changed anything to the ROM I was using since about October, and the issue just happened now in May.
At any rate, the new S3 I received is an MJB version, Android 4.3, Knox and all that other good stuff. After several failed attempts, I found a method to root this phone and disable Knox. The Warranty Bit is already tripped, so clearly I'm not sending this phone back until it hard bricks as well. I am trying to install the StockMOD ROM that is very popular, however I am being plagued by problem after problem.
I was able to flash a version of CWM Recovery onto my phone, but it was too old and couldn't mount any of the folders. Using ROM Manager, I was able to flash an update to my Recovery, and now it mounts and views all folders properly. However, when I go to install the StockMOD ROM, I continuously get a Status 7 error, something about "expects 5 args, got 3." I wiped the data, cache, and Dalvik, but kept getting this error. So, I had to recover my backup of stock, which didn't go well either. Once my backup was installed, all of my apps kept crashing. Gapps, ROM Manager, everything kept giving me constant FC errors. I had to wipe my data, cache, and Dalvik again and go back to factory default, and reinitialize the phone. Luckily I haven't installed anything of importance on here yet.
A quick search through here states that I need to use TWRP as my Recovery. I've flashed TWRP several times, first using the 2.6... version and then the most recent 2.7.0.0 version, and neither of these will mount any of my folders. It just gives me a litany of errors trying to mount the various locations. I've done Fix Permissions and everything else, TWRP will just NOT mount anything. Other folks say I need the latest PhilZ Recovery. I've downloaded the latest PhilZ Touch 6 and flashed it via Odin. It is giving me the same errors as regular CWM, Status 7, "expecting 5 args, got 3."
I don't know what else to do. My S3 that ran Android 4.0 was so much easier. I had that thing rooted and running a TW based ROM with Nova launcher in about 30 minutes. This phone has been a disaster since I turned it on. I'm just trying to get a 4.3 TW based ROM. I like the Samsung Camera, Calendar, Clock, Messaging, and Contacts apps far better than AOSP versions. But I also want much more customization to my notification drawer toggles. Stock TW doesn't have the toggles I use frequently like the data toggle as well as the torch toggle.
I don't know what I'm doing wrong, because unlike a lot of folks out there, once I find a ROM I like, I stick with it. I'm not constantly updating, changing, or searching for the newest version of Android. There's nothing wrong with that, it just isn't my cup of tea. So does anyone know what I need to do? At this point, I'm about to just give up and use Nova over top of rooted stock TW and call it a day.
Thanks!
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
nosphor said:
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
Click to expand...
Click to collapse
Everything is stock except the recovery. I'm using CWM 6.0.4.7 with PhilZ Touch 6. I'm still using the stock TW 4.3 ROM that shipped with the phone. The only exception is that I'm rooted now.
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
nosphor said:
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
Click to expand...
Click to collapse
Unfortunately, I've heard that it is not possible to revert to anything prior to 4.3 once a phone comes factory installed with 4.3, due to all of the security enhancements and etc. My kernel, modem, and baseband are all factory stock 4.3 MJB. Everyone else on the boards, under various other topics, warn of immediate and sudden death to the phone if you attempt to install a baseband prior to 4.3 MJB.
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
nosphor said:
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
Click to expand...
Click to collapse
I'm in the USA. The security features on the I747 US version are far different. I don't know how everyone else is succeeding. I am completely lost.
You are in the wrong forum, anything you try from here will hard brick your phone.
Sent from my GT-I9300 using Tapatalk
Sorry to tell you that, but what you say is not completely true.
Yes, there is a lot of people that rush to give an answer to the question, but there is also people that really like to help people that are in trouble :good:
Please, don't take most of the case for a generality
http://forum.xda-developers.com/showthread.php?t=1756338
Sent from my GT-I9300 using Tapatalk
Yes, i've read this, i know that, that's why i talk about the difference between country, different phone model
My apologies. Thought this was the 747 board. Go ahead and lock this, I'll repost in the correct forum.
Tried TWRP?

Categories

Resources