Related
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
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?
Due to instability issues in the latest nightlies, I clean flashed and reverted back to CM11 milestone 5. After doing this, I haven't been able to get mobile data. Voice and sms work fine, just "mobile network state disconnected" and no data connectivity. Also after flashing back to M5, "Phone" seems to prevent the device from sleeping. In battery stats, the device is always awake, with "Phone" using the majority of the batter.
I've tried re-flashing CM11 M5 multiple times, I've also flashed different modems, and I've also called AT&T to reset my internet connectivity. Nothing has worked thus far. Any suggestions? :good:
UPDATE/SOLUTION:
I got mobile data back by going back to stock, clean flashing AOKP (which works with mobile data), then dirty flash to CM11. Quite unorthodox, probably not the best solution, but it's the only 'fix' that has worked!!
I've tried many other suggestions, such as the "patched" modems & kernels, to no avail. Finally this works, dreams do come true
UPDATE: I tried ODINing back to stop 4.3 ROM, on which data was working again. However, upon flashing back to CM11, data stopped working once again. I tried flashing AOKP, which *did* get data back, so I'm assuming this is a CM11-exclusive problem.
I really don't know how the CM11 data problem persisted even after flashing back to stock and then re-flashing CM11. What could've gone wrong? Anyways, I guess I'm sticking to AOKP for the time being.
n0stalgia said:
UPDATE: I tried ODINing back to stop 4.3 ROM, on which data was working again. However, upon flashing back to CM11, data stopped working once again. I tried flashing AOKP, which *did* get data back, so I'm assuming this is a CM11-exclusive problem.
I really don't know how the CM11 data problem persisted even after flashing back to stock and then re-flashing CM11. What could've gone wrong? Anyways, I guess I'm sticking to AOKP for the time being.
Click to expand...
Click to collapse
Which AOKP rom you using? Is it for Kit Kat 4.4.2?
LAD2012 said:
Which AOKP rom you using? Is it for Kit Kat 4.4.2?
Click to expand...
Click to collapse
yep, latest AOKP nightly
check out this thread
http://forum.xda-developers.com/galaxy-s3/help/major-problem-s3-network-t2748246/page2
and this one too
http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289
n0stalgia said:
yep, latest AOKP nightly
Click to expand...
Click to collapse
Have you got a link to the rom - any issues with Wi-Fi or 3G/Mobile Data? This CM 11 rom I have is awesome but it's a pain that the 3G/Mobile data just doesn't work at all.
LAD2012 said:
Have you got a link to the rom - any issues with Wi-Fi or 3G/Mobile Data? This CM 11 rom I have is awesome but it's a pain that the 3G/Mobile data just doesn't work at all.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s3/orig-development/rom-aokp-kitkat-i9300-t2597838
I had a problem connecting to the network with all ROMs
http://forum.xda-developers.com/galaxy-s3/help/emergency-calls-t2748393
If you look on that thread, try installing the specified modem and kernel. Hope this helps.
lukeg26 said:
I had a problem connecting to the network with all ROMs
http://forum.xda-developers.com/galaxy-s3/help/emergency-calls-t2748393
If you look on that thread, try installing the specified modem and kernel. Hope this helps.
Click to expand...
Click to collapse
Did you install the patched kernel/modem while on stock ROM or on a custom ROM?
n0stalgia said:
Did you install the patched kernel/modem while on stock ROM or on a custom ROM?
Click to expand...
Click to collapse
Got the 4.3 stock ROM from sammobile then installed the kernel and modem from TWRP recovery - haven't tried a custom ROM yet but I presume it'd work in the same way
UPDATE:
I got mobile data back by going back to stock, clean flashing AOKP (which works with mobile data), then dirty flash to CM11. Quite unorthodox, probably not the best solution, but it works!
I've tried many other suggestions, such as the "patched" modems & kernels, to no avail. Finally this works, dreams do come true
I was using slimkat 4.4.2 and restored the official samsung rom 4.3 to try a mhl cable. The result as you may know is that I couldn't install any custom rom that wasn't based on samsung's after that.
Searching here in the forums I found some people saying that it was because of a layout change on partitions, others because of knox, or the update in bootloader...
I installed the twrp-2.7.1.0 recovery and tried to install omni rom with pa_gapps, cm11 etc and I always get an error for gapps (couldn't find build.prop or something...). Tried Omega v58 (based on sam) and it worked, then I tried slimkat 4.4.3 weekly and slim_AIO_gapps (advanced wipe, everything but extsd, format data) and it installed everything fine.
It's almost perfect but now I have only a small problem... when I plug the headset the audio is really bad and sometimes I can't hear anything ... I tried another kernel with the same result. Tried slimkat 4.4.2 stable, same.
Does it make any sense to anyone here? any sugestions on how to fix? flash something somewhere maybe :x
and what is the real problem after the 4.3 official update? if slimkat is working maybe we can make other roms work too.
Thank you in advance
Do a full wipe, all your previous issues were due to files left over from other firmware.
On the headset, go back to stock firmware after a full wipe. If still the same then it is hardware.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Do a full wipe, all your previous issues were due to files left over from other firmware.
Click to expand...
Click to collapse
I still can't install most roms even with full wipe (gapps error) after the 4.3 official update but I'm happy with slimkat. I think maybe it works because it just copies the gapps files to android without doing other checks, maybe editing the scripts we can "force" the install of other roms too. If anyone have any info, please tell me.
boomboomer said:
On the headset, go back to stock firmware after a full wipe. If still the same then it is hardware.
Click to expand...
Click to collapse
Oh, I think it was just a series of bad coincidences. Tried the stock firmware and the headset did not work. Seems like my headset broke the same day all that stuff happened, and I tried the one I use on PC but it didn't connect firmly on s3 so the sound was bad too... just tried a new phone headset and it's working fine.. thank you
Guys,
i'm using cm14.1 i want to revert back to miui ....please help
when i tried flash fastboot rom (kenzo_global_images_V7.3.6.0.LHOMIDD_20160523.0000.23_5.1_global_aef179560d) my wifi not worked. then i came back to cm14.1 now everthing work fine but i need miui.....please help
(sorry for bad english)
Same happened to me, I guess because we try downgrade to lollypop which has different radios. First I tried with twrp and with fastboot, but no wifi on 5.1. MM works fine for me... If anyone know how to downgrade to 5.1 I want answer too
redminote3 said:
Same happened to me, I guess because we try downgrade to lollypop which has different radios. First I tried with twrp and with fastboot, but no wifi on 5.1. MM works fine for me... If anyone know how to downgrade to 5.1 I want answer too
Click to expand...
Click to collapse
Bro did miui dev 6.0 fastboot rom work ?
Yeah, wifi and all will work no doubt on 6.0
use xiaomi.eu rom...flash from twrp...everything work properly for me.
site: xiaomi.eu
I use EU ROM currently too and it is the best one for me to date, also freezed some system apps with Titanium Backup.
But still dont know, if theres a way to downgrade to 5.1 if I dont have backup from 5.1, because my Kenzo came to me with 6.0... It boots fine, but wifi dont work, so also other radios, so its not usable
P.S. Can I flash with TWRP(zcx) old EU ROM recovery with 5.1 and radios will work?
I guess ill try that now
redminote3 said:
I use EU ROM currently too and it is the best one for me to date, also freezed some system apps with Titanium Backup.
But still dont know, if theres a way to downgrade to 5.1 if I dont have backup from 5.1, because my Kenzo came to me with 6.0... It boots fine, but wifi dont work, so also other radios, so its not usable
P.S. Can I flash with TWRP(zcx) old EU ROM recovery with 5.1 and radios will work?
I guess ill try that now
Click to expand...
Click to collapse
yes...you can directly flash 5.1 rom from zcx.
backup your data then do factory reset in twrp before flashing LP rom to remove any MM encryption.
hope you can downgrade without any problem..happy flashing.
anyway, probably your bootloader will relocked. but i am not really sure about this, just check it first after flashing LP rom.
abihary said:
use xiaomi.eu rom...flash from twrp...everything work properly for me.
site: xiaomi.eu
Click to expand...
Click to collapse
how to download recovery rom xiaomi.eu ...i didn't get any download button over there
abihary said:
yes...you can directly flash 5.1 rom from zcx.
backup your data then do factory reset in twrp before flashing LP rom to remove any MM encryption.
hope you can downgrade without any problem..happy flashing.
anyway, probably your bootloader will relocked. but i am not really sure about this, just check it first after flashing LP rom.
Click to expand...
Click to collapse
I tried that yesterday, except I wiped all except cust/microsd , flashed 5.1 eu rom and then I flashed also SuperSU, it was a disaster, phone only shows Mi logo and turn off...I cant go to twrp, only to fastboot. Im going to get computer in two hours where I have everything set up And will try to go to EDL mode and then flash With MiFlash... I doubt that flashing 5.1 will work with wifi
Denis:) said:
I tried that yesterday, except I wiped all except cust/microsd , flashed 5.1 eu rom and then I flashed also SuperSU, it was a disaster, phone only shows Mi logo and turn off...I cant go to twrp, only to fastboot. Im going to get computer in two hours where I have everything set up And will try to go to EDL mode and then flash With MiFlash... I doubt that flashing 5.1 will work with wifi
Click to expand...
Click to collapse
from fastboot, are you check your bootloader? it seems your bootloader relocked, thats why you can't pass mi logo
if your bootloader relocked, you can easily unlock it using miunlock.
for wifi, you can easily flash any miui mm firmware from twrp.
Thank you for the tip, didnt thought about that...
im gonna borrow computer now, I have all drivers installed etc on it...
If its only relocked and I will be able to boot and wifi will not work, where can I get firmware (and you must be thinking LP firmware not MM, right?
btw I flashed older EU ROM MIUI7, 5.1 then flashed through zcx supersu and reboot, now Mi logo only flashss and turn off. Only fastboot I can enter.
I will then first check if BL is locked, and unlock it if it is...
thank you for help
Ok so you were right, BL was locked so I unlocked it and got enryption problem after booting up, I had to reflash ZCX TWRP, because EU ROM replaced it with official 3.2.0. So now I am finally booted up on EU rom MIUI 7.3 by xiaomi.eu/Beta, Android 5.1.1, but Wifi as expected dont work, also SIM is not recognised.
What and where to get radios I have to flash to get it working? Because it says unknown under system info about version of radios
Also it says unknown device ID (IMEI,..).
I have backed up all partitions before on MIUI 8 EU,6.0, so do I need to flash those radios or firmware or do I need it from 5.1? And where to get it if so
Nice I got it to work, restored EFS,MODEM,FIRMWARE ROM,FIRMWARE EMMC and wifi works and SIM is working )
Nice I had backup of that...still not sure if all works as needed, gotta test a bit
Denis:) said:
Thank you for the tip, didnt thought about that...
im gonna borrow computer now, I have all drivers installed etc on it...
If its only relocked and I will be able to boot and wifi will not work, where can I get firmware (and you must be thinking LP firmware not MM, right?
btw I flashed older EU ROM MIUI7, 5.1 then flashed through zcx supersu and reboot, now Mi logo only flashss and turn off. Only fastboot I can enter.
I will then first check if BL is locked, and unlock it if it is...
thank you for help
Click to expand...
Click to collapse
for me, it's positive thats your bootloader relocked. unlock it, and you can boot into rom. for firmware, you can download from below
link firmware:
miui LP firmware
miui 6.7.21 firmware
miui 7.3.2.0 firmware
miui MM firmware
miui 6.9.29 firmware
miui 6.10.13 firmware
redminote3 said:
Ok so you were right, BL was locked so I unlocked it and got enryption problem after booting up, I had to reflash ZCX TWRP, because EU ROM replaced it with official 3.2.0. So now I am finally booted up on EU rom MIUI 7.3 by xiaomi.eu/Beta, Android 5.1.1, but Wifi as expected dont work, also SIM is not recognised.
What and where to get radios I have to flash to get it working? Because it says unknown under system info about version of radios
Also it says unknown device ID (IMEI,..).
I have backed up all partitions before on MIUI 8 EU,6.0, so do I need to flash those radios or firmware or do I need it from 5.1? And where to get it if so
Nice I got it to work, restored EFS,MODEM,FIRMWARE ROM,FIRMWARE EMMC and wifi works and SIM is working )
Nice I had backup of that...still not sure if all works as needed, gotta test a bit
Click to expand...
Click to collapse
good, seems your problem already solved. :good:
Yeah, now a problem is I cant access fingerprint or password lock, I think because I cant connect to Mi account, cant find my device, also cant manually log in, because it cannot verify "find device", also cannot access to "Privacy" to install 3d party apps it is a must to enable this... Also settings freeze occasionally. I think I still didnt do something right... Any tip?
Thank you for helping me!
redminote3 said:
Yeah, now a problem is I cant access fingerprint or password lock, I think because I cant connect to Mi account, cant find my device, also cant manually log in, because it cannot verify "find device", also cannot access to "Privacy" to install 3d party apps it is a must to enable this... Also settings freeze occasionally. I think I still didnt do something right... Any tip?
Thank you for helping me!
Click to expand...
Click to collapse
sound like firmware problem, you can try to flash firmware from above link which suitable with your current android version. if you're in LP, flash 6.7.21/7.3.2.0 and see if it work. or, you can flash one of MM firmware above.
to avoid from getting relocked, you can delete emmc_appsboot.mbn from zip package using winrar/7zip without extract it and let the apps repack it again.
abihary said:
sound like firmware problem, you can try to flash firmware from above link which suitable with your current android version. if you're in LP, flash 6.7.21/7.3.2.0 and see if it work. or, you can flash one of MM firmware above.
to avoid from getting relocked, you can delete emmc_appsboot.mbn from zip package using winrar/7zip without extract it and let the apps repack it again.
Click to expand...
Click to collapse
I tried flashing your firmware 7.3.2.0 and had to restore EFS,MODEM(maybe only modem) to get wifi,SIM working also your firmware fixed only I could log in to Mi account and find device, but still couldnt set PIN,FP, also tried calling and couldnt hear anything also on the other side no voice.
Im losing confidence that I can get everything work on 5.1 MIUI7
Then I wiped everything expect microSD and wanted to restore backup I made on EU ROM,MM6, but it said read only. Then I flashed 6.10.13 EU ROM and it works everything perfectly here...
Still want to downgrade to MIUI7,5.1 if theres a way to get it all working, because I heard battery is lil better...
redminote3 said:
I tried flashing your firmware 7.3.2.0 and had to restore EFS,MODEM(maybe only modem) to get wifi,SIM working also your firmware fixed only I could log in to Mi account and find device, but still couldnt set PIN,FP, also tried calling and couldnt hear anything also on the other side no voice.
Im losing confidence that I can get everything work on 5.1 MIUI7
Then I wiped everything expect microSD and wanted to restore backup I made on EU ROM,MM6, but it said read only. Then I flashed 6.10.13 EU ROM and it works everything perfectly here...
Still want to downgrade to MIUI7,5.1 if theres a way to get it all working, because I heard battery is lil better...
Click to expand...
Click to collapse
ah...this is only for battery life?
miui 8 a lot better on battery backup comparing with miui 7. also you got android M with bunch of feature & security update.
if you want better battery, flash xposed & amplify (you can limits nlp wakelock), flash kernel & use darkness/zzmove gov, use adaway or minminguard to remove ads.
still want more? flash stable aosp rom & keep using above way. pure stock android will give you better battery comparing with miui.
Thanks for all this great info!
I used few CM roms for this device, but none of them were working flawless...Which one are you talking about? I tried almost all Nougat based and had a lot of problems, only CM13 from thestrix were the closest, but I like MIUI though... Thank you for your time to help me!
redminote3 said:
Thanks for all this great info!
I used few CM roms for this device, but none of them were working flawless...Which one are you talking about? I tried almost all Nougat based and had a lot of problems, only CM13 from thestrix were the closest, but I like MIUI though... Thank you for your time to help me!
Click to expand...
Click to collapse
give a try for nx rom or aicp, both mm base. i really like both rom stability & feature. almost all my friend using both rom
for N, its still in progress & you won't get stability using N for now. give more time to let dev work & you'll get stable N which better than MM.
you're welcome, enjoy your device & dont bricked it
Thanks man, I flashed NX ROM and its stable and fast so far, also 400MHz unlocked by default ,..Flashed it with pico gapps and kenzo radios.
I want to flash xposed and amplify now, hope xposed doesnt do contra effect.
Thank you again!