For some reason, anytime I attempt to copy/cut whatever app im in crashes. When I long press to copy, I never get the context to complete the action. This only started happening after rooting my phone yesterday Anything I can do to fix this?
via Galaxy S III
Well, was unable to figure out the problem so this is what I ended up doing:
First of all, I rooted via mrRobinsons method and installed cwm as he instructed as well. I'm running CWM 5.5.0.4 IIRC
I did a nandroid and then did a factory reset, wiped cache, wiped dalvik cache and then I flashed Jirv311's stock/rooted/deodexed AT&T rom.
After rebooting I went into the browser to confirm it was working right, and it was. So I rebooted into recovery and went to advanced restore and restored data. After rebooting I went into the browser to confirm it was still working...it wasn't So I flashed the rom from above again, tested it, working right. This time I just installed the apps I wanted one by one from the market via my pc. After they all installed I checked to make sure it was working right, it was, and it's been working right ever since.
Related
I've tried it all folks. New kernels, factory reset, different radios, different ROMs. Every-thing. The WiFi will turn on for a quick second and I will get an error message "Unable to scan for networks" and then the Wifi will just turn on and off on and off over and over again. I've even deleted the files in the data/dhcp and data/wifi folders. Rebooted, still same issue. I've deleted the files and flashed a kernel and rebooted, still same issue.
Of course I am still in contract and will have to purchase a new phone outright from Verizon if I can't get this issue resolved......
I don't know what else to do here.....
Did you try formatting data and system before installing a new rom from recovery? If that doesn't work i would say its a hardware issue. You're not restoring system data with any backup programs are you?
Sent from my ADR6400L using Tapatalk
I've wiped pretty much everything known to man on the phone. The ROM installs are all "fresh" I haven't tried to install any APPS on the phone. Just wipe everything, factory reset / Dalvik Cache, all of it... install fresh ROM. Try to turn on Wifi, phone boot loops. No matter what ROM I install, still same issue with Wifi / boot looping.
Well guess we can close this out. I went out and paid full boat for a Samsung Nexus since I couldn't fix this issue.
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
@ajoesq I had the same problem when i installed thunderstick thru boot manager. My wifi stopped and I could get it going on my phone rom. So i booted back into thunderstick and wifi was working. Booted back to hte phone rom then into recovery and then i flashed my phone rom again without wiping or anything (Thunbershed V1.2) and it worked fine. wifi started agian.
ajoesq said:
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
Click to expand...
Click to collapse
Run a logcat when you try to turn wifi on. Put the output on pastebin.com and post the link. This might tell us what the problem is.
I'd make sure that the radio(s) were at least at the minimum of what the ROM called for.
Sent from my HTC ThunderBolt using XDA Premium App
after i flashed the latest cm7 weekly-29-jan,something weird occurred.
first when i unplugged the usb from pc as i restore all apps,the phone can't boot anymore.
second thing,when i pull out the battery and it did reboot,but some apps disappered suddenly and it switched back to the original theme(i used to install a ics theme).
all the weird things never happened in the version weekly-22-jan.and i assume it has something to do with USB.i just don't know why.
any ideas frome devs?? thanks.
I just installed the zip
cleared cache and dalvik cache
and rebooted
Everything worked fine and then I flashed another kernel and all.I didnt clear data or anything like that and it's working fine for me.I bet you had a bad flash try clearing everything and flashing again and dont restore your backed up apps just download them again that might be your prblem.
Also fix permissions
Ok I just got my S3, straight out of the box I booted into odin and successfully followed these instructions to get root http://forum.xda-developers.com/showthread.php?t=1756885 rebooted and started setting up my phone. It automatically started restoring all my apps then I went on and used titanium to restore my k9 mail and a few other apps (no system data or sms app data or anything like that). After I rebooted a messaged appeared " Unfortunately, Messaging has stopped" cleared the cache, fixed permissions, cleared cache and data of the messaging app. Nothing worked. Reset factory. As soon as the phone booted to the setup screen the messaging app error was already there. Back to Odin and reloaded the rooted tar file (I'm using the full stock, rooted version) and I still get the error when I turn the phone on! How can that be?
Exact same problem
jasondhsd said:
Ok I just got my S3, straight out of the box I booted into odin and successfully followed these instructions to get root http://forum.xda-developers.com/showthread.php?t=1756885 rebooted and started setting up my phone. It automatically started restoring all my apps then I went on and used titanium to restore my k9 mail and a few other apps (no system data or sms app data or anything like that). After I rebooted a messaged appeared " Unfortunately, Messaging has stopped" cleared the cache, fixed permissions, cleared cache and data of the messaging app. Nothing worked. Reset factory. As soon as the phone booted to the setup screen the messaging app error was already there. Back to Odin and reloaded the rooted tar file (I'm using the full stock, rooted version) and I still get the error when I turn the phone on! How can that be?
Click to expand...
Click to collapse
My SIII is doing the exact same thing. Verizon 32 gb rooted stock I am returning and they are shipping me a new one on the 14 day no worry guarantee.
Mine SIII also get a busy signal when trying to make a call an phone wont call out or receive calls I am reading where this is happening to a lot of them.
TheSurgeon said:
My SIII is doing the exact same thing. Verizon 32 gb rooted stock I am returning and they are shipping me a new one on the 14 day no worry guarantee.
Mine SIII also get a busy signal when trying to make a call an phone wont call out or receive calls I am reading where this is happening to a lot of them.
Click to expand...
Click to collapse
Hi I found another thread that had a solution, didn't think it would work but it did. I can't find the thread or I'd give him credit.
Basically, boot into odin and flash this (verizon stock unrooted) h**p://samsung-updates.com/get/2114/Samsung_Firmware_SCH-I535_VZW_I535VRALF2_Android_4_0_4.html after its done let it boot and then restart and go back into odin and reflash the rooted image. It's odd but it worked and all my apps and data remained(but backup just in case).
Factory reset guys. You are writing system files over existing system files. Factory reset. Factory reset. Factory reset
Sent from my SCH-I535 using xda app-developers app
das7982 said:
Factory reset guys. You are writing system files over existing system files. Factory reset. Factory reset. Factory reset
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Factory reset didn't work, first thing I tried...did it twice, nor did reflashing the rooted image, fixing permissions, clearing caches, etc. After the factory reset and reloading the rooted image, the error would appear on the language selection screen when first being setup. Reloading the stock non-rooted image and then reflashing the rooted image was the only thing that fixed it.
jasondhsd said:
Hi I found another thread that had a solution, didn't think it would work but it did. I can't find the thread or I'd give him credit.
Basically, boot into odin and flash this (verizon stock unrooted) h**p://samsung-updates.com/get/2114/Samsung_Firmware_SCH-I535_VZW_I535VRALF2_Android_4_0_4.html after its done let it boot and then restart and go back into odin and reflash the rooted image. It's odd but it worked and all my apps and data remained(but backup just in case).
Click to expand...
Click to collapse
Your my hero! This worked perfect. Now everything is as I want it. Once you validate you should make a new topic in development with the subject being the error message and Samsung Galaxy SIII this way all the people with this problem can easily impliment the solution.
Also you were correct. None of my data was lost.
:good::good:
Hi guys,
I wonder if someone can help me with this... really annoying problem!
I was checking out various roms i downloaded here, started with 4.0 aokp which was great, then gave cyanogen 4.2 a try, but then i wanted to go back to Aokp 4.0 cause it seemed to run faster
Now first thing, i couldnt get rid of cyanogen (no offense intended) cause when i wiped all data, cache and dalvik it just took aokp a few seconds to install from CWM recov, that doesnt seem right, right?
Then installed GAPPS, but still it ran on Cyanogen
So, i did a NANDROID backup, which made my phone like before i started with all this..
THIS IS WHERE IT WENT WRONG?
now it just wont read my simcard
i tried my sim in my old phone and that works fine, so the problem is in my phone somehow
is it something about the radio settings specific to my phone and network?
how can i change these settings and are they specific for my provider?
you guys always helped me out so i hope you know what i mean..
kipdeontdekker said:
Hi guys,
I wonder if someone can help me with this... really annoying problem!
I was checking out various roms i downloaded here, started with 4.0 aokp which was great, then gave cyanogen 4.2 a try, but then i wanted to go back to Aokp 4.0 cause it seemed to run faster
Now first thing, i couldnt get rid of cyanogen (no offense intended) cause when i wiped all data, cache and dalvik it just took aokp a few seconds to install from CWM recov, that doesnt seem right, right?
Then installed GAPPS, but still it ran on Cyanogen
So, i did a NANDROID backup, which made my phone like before i started with all this..
THIS IS WHERE IT WENT WRONG?
now it just wont read my simcard
i tried my sim in my old phone and that works fine, so the problem is in my phone somehow
is it something about the radio settings specific to my phone and network?
how can i change these settings and are they specific for my provider?
you guys always helped me out so i hope you know what i mean..
Click to expand...
Click to collapse
I've exactly the same problem.
Are your wifi and BT still OK ?
Is your IMEI (*#06#) still the same as under the battery ?
Was your phone locked ? Did you buy it with a SIM ?
My problem appeared after flashing several different modems/RILS : I got no error warning anywhere, but after reboot, I completely lost my netwerk connection. (no voice calls , no mobile data)
At first I thought a bad RIL driver, so I restored my Nandroid backup from the day before (after wipe cache/wipe dalvik/format system), but still no connection with the netwerk. and can't even make voice calls.
Then I was in panic !
After this I did a complete factory reset, and wiped/formatted cache/dalvik/system/data/SD-card and went in to download mode. After loading a stock ELLA for my region using Odin, still no connection. I was also never asked to enter the PIN-code for my SIM to unlock it.
Damned, this is an embarrassing situation : I can't think of loosing my SG3 for several weeks if I have to send it to Samsung !!
Mu phone is bought without SIM, so it's not SIM-locked.
My Wifi and BT are still OK, my IMEI is also still OK.
Any other ideas, please ?
How do I come in the service mode for the Radio ?
This is the way my netwerk is indicated : a circle with a stripe, much like the famous traffic sign.
Its fixed
So i have no idea how it eventually got fixed but if someone else has this problem, heres what i did:
Full wipe/factory reset blablabla all that
Did Nandroid restore again, put the AOKP ROM and GAPPS back on my phone
Installed ROM which was I9300CEDLI1
Used Odin to install latest CWM, which was already on there, but still
Then booted into CWM and installed .zip of course
This still went suspiciously fast since the very first time it took way longer, that worried me but,
Installed GAPPS again,
Rebooted... IT ASKED FOR MY PIN NUMBER!! hell yes that was what i wanted!
So now it again sees my simcard in there, so now i can make calls end use intnet again!
Still i think it started after the nandroid backup for some reason, or it may have been because of wiping Dalvik Cache?
I have no idea if that even makes sense
kipdeontdekker said:
Its fixed
So i have no idea how it eventually got fixed but if someone else has this problem, heres what i did:
Full wipe/factory reset blablabla all that
Did Nandroid restore again, put the AOKP ROM and GAPPS back on my phone
Installed ROM which was I9300CEDLI1
Used Odin to install latest CWM, which was already on there, but still
Then booted into CWM and installed .zip of course
This still went suspiciously fast since the very first time it took way longer, that worried me but,
Installed GAPPS again,
Rebooted... IT ASKED FOR MY PIN NUMBER!! hell yes that was what i wanted!
So now it again sees my simcard in there, so now i can make calls end use intnet again!
Still i think it started after the nandroid backup for some reason, or it may have been because of wiping Dalvik Cache?
I have no idea if that even makes sense
Click to expand...
Click to collapse
Good to hear your problem is fixed !
I'm still not able to make voice calls or enable mobile data : "insert SIM card" is the message I get.
I did already twice a full reset/factory restore and flash a stock ROM using PC Odin, but no avail.
Today I did a restore from my EFS folder using a backup that a had made before the problem appeared, but no avail.
BTW, did you also have the same indication from network status as on my screen-shot ?
Any idea what else I can try ?
I'm getting desperate .....
I'm having the same trouble after doing backup in TWRP when boot up it doesn't recognize the sim card.
I've flash CM10.1 and it only work after i remove the card e put it back on.
Try to see if it something about the simcard.
Regards,
Rui
Hi,
Last night I installed the new stock lollipop. Initially I had a problem with rooting it but eventually everything was working fine. I've used Philz recovery and cf-auto-root. All seemed fine, and I've got all my apps, accounts, etc. back.
This morning I woke up and it looks as if at 6:02am the phone just froze. The strange things are (1) I could turn on and off the display so it was not completely frozen, just the UI (displaying new screens and receiving a response from the keys or the touch screen). (2) I thought to reboot into recovery and when I did - it was the stock recovery! not sure what happened to Philz that was there before?
In any case, I did clear cache and restarted. The logo came up but after 20 sec I've got "unfortunately, media storage has stopped". Of course - it did not receive any response from keys or the touch screen so I could not release this message - only on-off worked. After a minute or so, I saw that other services are crashing...
Of course I can do yet another "wipe to factory" but I was wondering if anyone experience the same. If I will make it work after clear to factory - I'm afraid it will behave the same after a day or so... Any suggestions?
Thanks!
gilbnx said:
Hi,
Last night I installed the new stock lollipop. Initially I had a problem with rooting it but eventually everything was working fine. I've used Philz recovery and cf-auto-root. All seemed fine, and I've got all my apps, accounts, etc. back.
This morning I woke up and it looks as if at 6:02am the phone just froze. The strange things are (1) I could turn on and off the display so it was not completely frozen, just the UI (displaying new screens and receiving a response from the keys or the touch screen). (2) I thought to reboot into recovery and when I did - it was the stock recovery! not sure what happened to Philz that was there before?
In any case, I did clear cache and restarted. The logo came up but after 20 sec I've got "unfortunately, media storage has stopped". Of course - it did not receive any response from keys or the touch screen so I could not release this message - only on-off worked. After a minute or so, I saw that other services are crashing...
Of course I can do yet another "wipe to factory" but I was wondering if anyone experience the same. If I will make it work after clear to factory - I'm afraid it will behave the same after a day or so... Any suggestions?
Thanks!
Click to expand...
Click to collapse
This happened to me. I had to do a factory reset.
I seriously do not recommend cf auto root(because its not designed for this firmware). Use chainfire's update SU zip that you flash through a recovery. That update SU zip will prevent the stock recovery from being re-flashed. In addition, I always do a factory reset (wipe entire internal storage) before updating the ROM since I root. If I didn't root or anything, I wouldn't wipe my data. But when we root and mess with stuff, plus all the tries to prevent root, it conflicts sometimes. So a factory reset is always best. I was able to use Titanium Backup to restore everything. Just forgot to backup my Internal SD card.. xD
elesbb said:
I seriously do not recommend cf auto root(because its not designed for this firmware). Use chainfire's update SU zip that you flash through a recovery. That update SU zip will prevent the stock recovery from being re-flashed. In addition, I always do a factory reset (wipe entire internal storage) before updating the ROM since I root. If I didn't root or anything, I wouldn't wipe my data. But when we root and mess with stuff, plus all the tries to prevent root, it conflicts sometimes. So a factory reset is always best. I was able to use Titanium Backup to restore everything. Just forgot to backup my Internal SD card.. xD
Click to expand...
Click to collapse
Thanks elesbb, I saw your message just now but I have my phone working already since few hours ago after a 2nd stock reflashing. If I have the same issues as before - I will use chainfire's update SU.
What I did find is that once I enable accessibility (to apps like Tasker, and an LG bluetooth headphone I have (so it could announce notifications) the phone becomes unstable; it just went through 2 boot loops but eventually recovered... Hopefully it will stay stable.
Gil.