Sup,
So, I flashed mutliple custom ROM's when I got this device like any other crack-flasher would but I then realised I much prefer it to be running stock with root access until an AOSP ROM comes along.
So I came from Omega 4.0 to stock LE8 in the UK, ever since I've flashed this stock ROM (Which is odexed) I keep getting the message "Sorry, messaging has unfortunately stopped" every time I open the app. I've tried wiping data/cache/dalvik and flashing in Odin again, same issues. I then went back to another custom ROM (HyperGalaxy) then went back to stock to test, still the same.
I have also tested an inverted AOSP 4.0.4 Mms app which worked on Omega, but didn't work on stock (Got the same message)
Data of the Messaging app has been wiped, i've disabled the app, rebooted, enabled again, still the same issues.
I've searched and I found 2 other threads with the same thing, but noone has been helpful enough yet.
It seems like the phone still thinks its running a Deodexed ROM but I need to get it back to full working order since I need to text something.
Any help is appreciated.
Try a factory reset...
Mopral said:
Try a factory reset...
Click to expand...
Click to collapse
Probably didn't make it clear enough, I did that already. 3 times to be exact.
i have the same issue. Need help.
i get this message with multiple apps.
all of them are standard run of the mill things like browser, messages, video player. My phone is only a week old and completely stock
some real bugs in this phone still that need sorting asap. poor effort by samsung really
Same issue here, has anyone found a fix for it yet?
I only encounter this in hyper x rom. So far so good in omega
Ok,I had this issue when I tried to install different firmware and modems using Mobile Odin. It fully resolved when I flashed back the official UK firmware and modem (le8) using normal desktop Odin. No force closes whatsoever since. Incidently, I'm now using LE9 firmware with UK CSC, rooted, with no issues at all. I used chainfires recovery, then flashed superuser to root.
Hope this helps.
nbhadusia said:
Ok,I had this issue when I tried to install different firmware and modems using Mobile Odin. It fully resolved when I flashed back the official UK firmware and modem (le8) using normal desktop Odin. No force closes whatsoever since. Incidently, I'm now using LE9 firmware with UK CSC, rooted, with no issues at all. I used chainfires recovery, then flashed superuser to root.
Hope this helps.
Click to expand...
Click to collapse
i got this everytime i clear cache and or wipe data from recovery before flashing new fw's.
so never wipe anything before flashing. if u already wiped, then flash it all over again and it will be all ok
Related
Hello
I did not want to wait for the ICS upgrade for my region. so I decided to flash another ICS stock rom. I downloaded one it was a tra.md5 file, I just flash it with Odin, after phone rebooted ICS was there but for my surprise all my applications and settings are there as well.
I was thinking that flashing another stock rom will delete all my apps as it usually happens when I was previously testing ICS before official release. Can you please explain this ?
Every ROM is different if there is some function that an other already installed app uses it will forceclose it is *Recommended* to wipe everything so there will not be so many bugs.
Sounds like you flash a "No Wipe" rom, this will upgrade your android while preserving existing data etc.
If the ROM is a no wipe Rom, then your apps and data will remain. There is nothing unusual.
Btw. Wrong thread.
Sent from my GT-I9100 using XDA
harise100 said:
Btw. Wrong thread
Click to expand...
Click to collapse
Reported to moderators. They will move it.
well this is a stock ROM from samfirmware XXLPS. I wanted to have the last one. Right now my phone keeps restarting. but I am not getting any FC.
Actually I have 300 Apps I did not want to reinstall them, does upgrading to ICS works fine without wipe?
the_desperado said:
well this is a stock ROM from samfirmware XXLPS. I wanted to have the last one. Right now my phone keeps restarting. but I am not getting any FC.
Actually I have 300 Apps I did not want to reinstall them, does upgrading to ICS works fine without wipe?
Click to expand...
Click to collapse
No some apps may not be compatible its your choice really stock roms are no wipe .
You can install the stock firmware posted on XDA .
jje
ok guys.now it is more stable. but market (play) is not working, I can open it I cam see my apps (not all of them) but I can not download or update. no errors just it is taking forever
I did a fall back. it keeps closing and restarting.
What is the best way then to upgrade without reinstalling all apps and resetting system settings? I mean something similar to KIES?
Until yesterday I used several different ROMs, without having any sound problem.
The problem started when I flashed Syiah kernel 1.2.6 (which might be a coincidence), while being on OMEGA-ROM. Thereafter I couldn't hear anything in phone calls any more (but others can hear me) on any ROOTED firmware or ROMs.
Reverting back to Syiah 1.1 (or switching to any other kernel) didn't help, neither did flashing any other rom.
Full wipe (including all storage space) solved the problem temporarlily. But after reboot no sound in phone calls again. Also changing the modem first helped, but the problem re-appeared after the first reboot.
Finally I flashed stock rom (LF2) via ODIN. Now the problem was solved - I believed. I could hear people in phone calls even after several reboots. But as soon as I rooted the phone with CF-Root AND changed some files on /system/media/ui the call sound was gone again after the following re-boot.
I reflashed again to stoch firmware via ODIN and now I have to live with an unrooted phone, which is not the worst thing in the world. But I really would like to be able to use custom ROMs again...
Anyone with similar experiences or with any idea about possible causes and/or solutions???
*** via Tapatalk ***
citronbitare said:
Until yesterday I used several different ROMs, without having any sound problem.
The problem started when I flashed Syiah kernel 1.2.6 (which might be a coincidence), while being on OMEGA-ROM. Thereafter I couldn't hear anything in phone calls any more (but others can hear me) on any ROOTED firmware or ROMs.
Reverting back to Syiah 1.1 (or switching to any other kernel) didn't help, neither did flashing any other rom.
Full wipe (including all storage space) solved the problem temporarlily. But after reboot no sound in phone calls again. Also changing the modem first helped, but the problem re-appeared after the first reboot.
Finally I flashed stock rom (LF2) via ODIN. Now the problem was solved - I believed. I could hear people in phone calls even after several reboots. But as soon as I rooted the phone with CF-Root AND changed some files on /system/media/ui the call sound was gone again after the following re-boot.
I reflashed again to stoch firmware via ODIN and now I have to live with an unrooted phone, which is not the worst thing in the world. But I really would like to be able to use custom ROMs again...
Anyone with similar experiences or with any idea about possible causes and/or solutions???
*** via Tapatalk ***
Click to expand...
Click to collapse
Really nobody who could help???
Can you record sound with other apps?
That should see if its a problem with just the phone apk or a more native problem.
Sent from my GT-I9300 using xda premium
Well, others can hear me but I can't hear them in phone calls. There is no problem with the phone speaker, because I can use viber without problems.
*** via Tapatalk ***
BUMP! I'm having the same problem!
I'm hoping it's not a hardware problem.
I wonder if any dev can chime in.
Well, it shouldn't be hardware related, because there is no problem on unmodified stock firmware.
*** via Tapatalk ***
Zabalba said:
BUMP! I'm having the same problem!
I'm hoping it's not a hardware problem.
I wonder if any dev can chime in.
Click to expand...
Click to collapse
You have the same problem, but after flashing syiah?
If yes it is not coincidence i think.
Kernel has sound modifications for last version 1.26
Sent from my GT-I9300 using xda premium
I noticed I had the problem intermittently when I first started using Foxhound on Saturday. Foxhound comes bundled with Syiah.
I thought it was something else all together. I asked in the Foxhound thread and only one other person +1'd my post. Today I switched to Omega hoping it the problem would go away and it was actually worse.
I was testing just now and every time I called my phone I could hear nothing on my handset or through headphones. Just in case I did't accidentally flubbed anything else up I unfroze all the TB apps I had frozen to see if it was working. Interestingly after defrosting and rebooting I can hear again. Attached are the apps I had frozen.
But this has not been the first time it was working correctly and then go back to not hearing calls.
JJEgan said:
Kernel has sound modifications for last version 1.26
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I strive for that. What I would do:
Flash stock rom
Factory reset via stock recovery
flash stock
cfroot
and then check if it is still a problem.
That is why the topic OMEGA asked that the next versions were the stock kernel.
That is why in order to avoid such problems.
marcinrek21 said:
You have the same problem, but after flashing syiah?
If yes it is not coincidence i think.
Click to expand...
Click to collapse
Yes, it all started after flashing syiah 1.2.6. So maybe it's not a coincidence after all.
*** via Tapatalk ***
Zabalba said:
I noticed I had the problem intermittently when I first started using Foxhound on Saturday. Foxhound comes bundled with Syiah.
I thought it was something else all together. I asked in the Foxhound thread and only one other person +1'd my post. Today I switched to Omega hoping it the problem would go away and it was actually worse.
I was testing just now and every time I called my phone I could hear nothing on my handset or through headphones. Just in case I did't accidentally flubbed anything else up I unfroze all the TB apps I had frozen to see if it was working. Interestingly after defrosting and rebooting I can hear again. Attached are the apps I had frozen.
But this has not been the first time it was working correctly and then go back to not hearing calls.
Click to expand...
Click to collapse
For me it has also been an intermittent problem. Kernel changes, modem changes, wipes, etc often temporarily helped - but only for one boot cycle. A reboot always brought the problem back. Only on stock firmware I can always hear.
*** via Tapatalk ***
marcinrek21 said:
I strive for that. What I would do:
Flash stock rom
Factory reset via stock recovery
flash stock
cfroot
and then check if it is still a problem.
That is why the topic OMEGA asked that the next versions were the stock kernel.
That is why in order to avoid such problems.
Click to expand...
Click to collapse
I have done exactly that - and the problem is gone as long as you only do these steps. But modifying the system partition in any way (changing, deleting or adding files or flashing custom rom) brings you back to square one.
*** via Tapatalk ***
citronbitare said:
I have done exactly that - and the problem is gone as long as you only do these steps. But modifying the system partition in any way (changing, deleting or adding files or flashing custom rom) brings you back to square one.
*** via Tapatalk ***
Click to expand...
Click to collapse
And may you have an earlier backup? Stock with cfroot or similar?
marcinrek21 said:
And may you have an earlier backup? Stock with cfroot or similar?
Click to expand...
Click to collapse
The sound problem is there even when I restore earlier backups. Now I am on stock firmware and everything is okay.
But I would like to use custom ROMs again with working phone call function, which is not possible for now.
*** via Tapatalk ***
This is the weirdest problem that I have seen here.
Just a status update. I have done some more testing and obviously what makes call sounds not to work is certain changes to the system partition (as compared to stock firmware).
In my case call sound works as long as I am on stock firmware (no matter what stock firmware; I have tested three or four different ones). If I root stock firmware with CF-root I still have call sound. I also can change kernels and it is possible to modify host files with ad-free.
However, as soon as I manually change or modify anything on the system-partition with root explorer or when I install custom ROMs the call sound disappears after the next reboot - no matter what radio I use. I also have tested the radio from the newest malaysian firmware which has surfaced today.
citronbitare said:
Just a status update. I have done some more testing and obviously what makes call sounds not to work is certain changes to the system partition (as compared to stock firmware).
In my case call sound works as long as I am on stock firmware (no matter what stock firmware; I have tested three or four different ones). If I root stock firmware with CF-root I still have call sound. I also can change kernels and it is possible to modify host files with ad-free.
However, as soon as I manually change or modify anything on the system-partition with root explorer or when I install custom ROMs the call sound disappears after the next reboot - no matter what radio I use. I also have tested the radio from the newest malaysian firmware which has surfaced today.
Click to expand...
Click to collapse
Thanks for your testing!
Like I mentioned in my earlier post I unfroze all of the apps and I have not run into the issue. My phone is running Omega 5.2 with Siyah 1.2.6. I'm totally expecting the problem to return but it has not so far. I wish it was consistent and reproducible.
Zabalba said:
Thanks for your testing!
Like I mentioned in my earlier post I unfroze all of the apps and I have not run into the issue. My phone is running Omega 5.2 with Siyah 1.2.6. I'm totally expecting the problem to return but it has not so far. I wish it was consistent and reproducible.
Click to expand...
Click to collapse
I'll keep my fingers crossed and hope that you have finally gotten rid of this problem. And thanks btw for asking Chainfire and Indie too look at this thread!
*** via Tapatalk ***
I got that problem myself, the only thing that really helped for me is to
flash my Stock Rom that where on the Phone out of the Box... since 2 Days
the Bug is gone. But havent tried any other Stock Rom.
I want to try Omega 6.0 Rom...(now)
I was thinking about flashing CF-Root and do those steps before custom:
1. Wipe Data/Factory Reset
2. Wipe Cache Partition
3. In Advanced ---> Format System/Cache/Data (someone tried this before?)
4. Flash the Rom.
My Question is for those guys like me where the only solution is to stay on
non rooted stock rom, have you tried flashing a custom rom with step 3. from above and still encounter the call issue?
I read somewhere that with step 3. the Phone is really FULL WIPE.
Sorry for my bad english :silly:
Hi,
I've updated the phone to the newer firmware from KIES, and the phone was connected to the WIFI network but signal connection keeps switching on and off, is there anyway to fix this issue so I can have a stable connection?
Have test with my iPhone and Ipad, both connectect to the same WIFI and only my samsung S3 having this problem.
PS: WIFI power saver mode is already <<off >>, keep Wifi on during Sleep mode is set to <<always>>, Network notification is <<un-tick>>
This is my current ROM (Rooted)
AP: I9300BUBLG3
CP: I9300BULG2
CSC: I9300VFGBLG3
settting > wireless & network > more > mobile network > automatic connections > sprint connection optimizer.. unchecked?
This is the international version is Samsung S3, I can't find such settings.
Sent from my GT-I9300 using xda app-developers app
I had the same issue when I reverted to stock. I thought it was this and that but really, all I did was
Backed up everything
Well mine was rooted and stuff so I triangled away the flash counter, probally dont need that if your on stock anyways
I wiped everything from the phones settings, back and restore, reset
I then booted up in recovery, doesnt matter if you are cwm or stock recovery, wipe again plus cache
Now I loaded up Odin and flash the original stock rom for my phone, I waited till it was complete, I then updated it through settings till I got to the latest update and then started reinstalling my apps from google play store or whenever else I had apps. So far all is well and no wifi issues.
Other advise would be instead of all the above, wait for another update or flash a new modem. That also worked for me when I was running another countries stock rom, Bad wifi, so I flashed my countries modem and it was fine! so good luck!
go to dialler
*#0011# will take you into Service Mode
click on menu
click on wifi
you will see a button that says "on" click on it
it will say off this stops the wifif connect/dis-connect problem.
If you shut down your phone you have to reset it to off.
jetbruceli said:
I had the same issue when I reverted to stock. I thought it was this and that but really, all I did was
Backed up everything
Well mine was rooted and stuff so I triangled away the flash counter, probally dont need that if your on stock anyways
I wiped everything from the phones settings, back and restore, reset
I then booted up in recovery, doesnt matter if you are cwm or stock recovery, wipe again plus cache
Now I loaded up Odin and flash the original stock rom for my phone, I waited till it was complete, I then updated it through settings till I got to the latest update and then started reinstalling my apps from google play store or whenever else I had apps. So far all is well and no wifi issues.
Other advise would be instead of all the above, wait for another update or flash a new modem. That also worked for me when I was running another countries stock rom, Bad wifi, so I flashed my countries modem and it was fine! so good luck!
Click to expand...
Click to collapse
This was the latest stock rom from KIES update (also rooted). But thanks for the reply, I'll try to flash different ROM and see what will happen.
colint3 said:
go to dialler
*#0011# will take you into Service Mode
click on menu
click on wifi
you will see a button that says "on" click on it
it will say off this stops the wifif connect/dis-connect problem.
If you shut down your phone you have to reset it to off.
Click to expand...
Click to collapse
I already set it <<off>>, still having issue with the wifi.
superfilm968 said:
I already set it <<off>>, still having issue with the wifi.
Click to expand...
Click to collapse
I've got the exact same problem. Do you have a BT Home Hub 3 by any chance?
I've just rooted mine so am going to try and flash a new modem and see if this fixes the issue
jonjuk said:
I've got the exact same problem. Do you have a BT Home Hub 3 by any chance?
I've just rooted mine so am going to try and flash a new modem and see if this fixes the issue
Click to expand...
Click to collapse
Sorry I don't have BT Home HUB 3, my connection is very simple, just connecting the S3 to a DrayTek Vigor2710Vn Router via Wifi. Please let me know the result after you flash with a new modem. If is working, please provide the link and file name where you got your file so I can flash it too.
Thanks!!!!
***By the way, what ROM version are you using at the moment? Please provide your AP, CP and CSC details if is different to my S3. ***
Repeat Modem has nothing to do with WiFi.
jje
I had the exact same issue, but ONLY after rooting the device (which I did just a day or two after I got it). I tried every possible fix, flashed new roms 3 or 4 times, wiped data and everything else in recovery, but no luck.
However, my final solution was to simply follow a guide to unroot the device, which I did today - and it did indeed work, I guess this issue is mainly happening to rooted phones, for unknown reason. Until I know this is fixed with an update (maybe in 4.1 JB), I won't be rooting this device again.
Link to guide on how to unroot
Are there actually people who can't fix it like me?
Also done everything I possible could but never got wifi working again.
Returned it to Samsung. I unrooted it and flashed the firmware again with KIES.
The day after there was also an official update for the BENELUX I guess. Also updated this with KIES.
So is it still possible they see that the modem was changed?
haenraets said:
Are there actually people who can't fix it like me?
Also done everything I possible could but never got wifi working again.
Returned it to Samsung. I unrooted it and flashed the firmware again with KIES.
The day after there was also an official update for the BENELUX I guess. Also updated this with KIES.
So is it still possible they see that the modem was changed?
Click to expand...
Click to collapse
did you reset the flash counter?
haenraets said:
Are there actually people who can't fix it like me?
Also done everything I possible could but never got wifi working again.
Returned it to Samsung. I unrooted it and flashed the firmware again with KIES.
The day after there was also an official update for the BENELUX I guess. Also updated this with KIES.
So is it still possible they see that the modem was changed?
Click to expand...
Click to collapse
Yeah as the guy above me said, you always have to reset the flash counter before unrooting (as this requires superuser access).
If you don't do this, it's easy to see the phone has been modified in either download mode or by checking status in settings.
After successfully unrooting you'll also have to re-enter CWM recovery and wipe data+cache.
After doing this you'll see the device being "normal" and it should show "stock" in download mode.
ph10m said:
Yeah as the guy above me said, you always have to reset the flash counter before unrooting (as this requires superuser access).
If you don't do this, it's easy to see the phone has been modified in either download mode or by checking status in settings.
After successfully unrooting you'll also have to re-enter CWM recovery and wipe data+cache.
After doing this you'll see the device being "normal" and it should show "stock" in download mode.
Click to expand...
Click to collapse
Forgot to mention it but I did this yes.
I also think KIES would not update when this is not a zero.
I believe the Vodafone UK 4.1.2 update has only become available this week, updated mine last night OTA - previous update was OTA and worked fine. I constantly get the 'Unfortunately android.process.media has stopped working error' and it's also not keen to load the keyboard, and the battery life is now hopeless.
I've googled the error message and I can see that it's a common problem, and the poor battery life is linked to the error message I'm constantly getting. I've tried to raise a thread on the Vodafone Eforum, but there seems to be some problem trying to login at the moment (the forum software has always been hopelessly slow and glitchy).
After all my googling, despite it being a common issue, I can't seen any real solution - can anyone help?
Re-flash the 4.1.2 firmware via Odin. But this time go inte Recovery and wipe data/cache and Dalvik cache if necessary before flashing.
You're right it's a common problem, and wiping usually fix it. Try it.
Cheers.
Thanks, I presume Odin requires the phone to be rooted?
This is the first android phone I've had where I've been happy with the standard rom. I've connected to Kies and it seems to think there's a further update available, I'm backing up and I'll try this first.
If that doesn't work I'll be looking to root and try some of the custom roms.
Ok try Kies update.
And NO, Odin does not require your phone too be rooted. You can although root your phone via Odin.
Cheers.
scoobydoo99 said:
Thanks, I presume Odin requires the phone to be rooted?
This is the first android phone I've had where I've been happy with the standard rom. I've connected to Kies and it seems to think there's a further update available, I'm backing up and I'll try this first.
If that doesn't work I'll be looking to root and try some of the custom roms.
Click to expand...
Click to collapse
I installed that very rom using mobile odin had no problems at all. After which you can keep it as stock but you able to remove all the bloatware, bock adds etc as you always have root privileges.
Sent from my GT-I9100 using xda premium
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?