I got huawei G510-0200 from friend to try to fix it. The phone is allready rooted and has installed a custom ROM(SlimKat 4.4) and TWRP recovery. But when the software is booted up, all the time i get the pop up message of applications crashing(play store, messenger, nova launcher etc) and i didn't run any application. So here's the real problem... When i access recovery and try the full wipe, factory reset or installing new rom, twrp reports that actions are successful but nothing happened. Nothing has changed. The phone was not reseted, data and applications are still there and same rom is still running. Someone told me that issue could be partitions.
Anyone had this problem, any ideas how to solve it?
Thanks in advance...
Sent from my P5_Quad using XDA Free mobile app
Related
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:
I know there are many forums addressing this problem but mines is a bit different, I know the common solution is App Info > Clear Data but this doesn't help. Neither does a force stop, reset or a clearing of settings cache.
I resolved to needing to do a data wipe, however I received this message, "failed to stat /data/date/com.android.defcontainer/cache" and nothing wiped. I started the phone to the exact same home screen and apps, but I had lost wifi settings and such, and can't open settings to set up wifi yet again.
I contemplated reflashing CM through the installer but wasn't sure if the failed to stat problem would interfere and potentially brick.
Any help would be much appreciated, cheers.
Flash the latest stock firmware for your country with Odin, factory reset in recovery before first boot.
boomboomer said:
Flash the latest stock firmware for your country with Odin, factory reset in recovery before first boot.
Click to expand...
Click to collapse
I read online that downgrading from 4.4 (CM) to Stock 4.3 would hard brick the device, is there any merit to this?
No, if you use the right firmware and do it properly there is no more risk than with a normal flash.
Problems with all roms SM-T210
Hi!
This problem is driving me crazy!
I have a similar problem!
I have Samsung Galaxy Tab SM-T210
For a long time I used RocketTab rom. I decided to try out new Android 4.4.2 Rom.
I started to get an error "Unfortunately settings has stopped" when I tried to open settings. I also got another application errors.
Now, it does not matter what rom I install, i get application has stopped error.
Even the RocketTab rom.
I flashed original stock rom via Odin, same problem.
I tried CWM and TWRP recovery.
I wiped dalvik cache, system, cache, Data, internal storage.
After flashing a new rom via odin or recovery, same problem.
I don't understand how it's possible that after deleting everything, I still get the same error.
Sometimes when I open settings, instead of getting an error, tablet restarts.
Tablet was 100% working before flashing Android 4.2.2
Any ideas?
Thanks guys
Why are you asking in the i9300 forum?
boomboomer said:
Why are you asking in the i9300 forum?
Click to expand...
Click to collapse
Because the problem seems to be very similar.
Point taken!
Hey guys...
My WhatsApp was running normal and when I open it was like I had never opened it before. I put my number again, and when he appeared "Connecting ..." he just closed and went to the Apps screen. And when I opened again, same thing ...
I tried to uninstall and reinstall it with the play store, but it appeared the error 504, even thought it might be something with the beta, then deactivated and tried to install it, and it was the same error ...
I also tried to download the APK from the official website, but the application did not install "Could not install the application."
But I took this APK and tried using ADB and installed, but the app asked my number again and again ...
The last thing I tried was reset my device, and remains the same in the play store and manual installation ...
Thank you.
More information:
Stock ROM
.109
Locked bootloader
Non-rooted
Update
I solved the problem by Xperia Companion using software repair
Did you flash anything recently? I had the same problem after installing xposed. All I had to do is clear dalvik cache in recovery.
Morph' said:
Did you flash anything recently? I had the same problem after installing xposed. All I had to do is clear dalvik cache in recovery.
Click to expand...
Click to collapse
I've never done anything on that device, I've never seen anything like it, was the first app I tried to install after reset, and still the same thing, only with whatsapp, all the other apps work ... I'm thinking of doing a full wipe.
Thanks
I have been running various flavors of AOKP ROM's on SG3's for several years now. I recently obtained a refurb S3 and set it up to do the usual.
It came with stock TW 4.4.
Using ROM Manager I installed CWM and made an image of the stock phone. I then installed my AOKP variant and loaded my apps, blah blah. All is good.
I've since decided I want to revert back to TW for awhile. I restored my nandroid and I get the interminable GAPPS failure messages. I have on occasion been able to get it to calm down and have a working phone, usually be uninstalling play app and clearing framework services cache. This is extraordinarily painful and doesn't always work. I've done all the usual, reinstall GAPPS, etc., and basically it is a MAJOR headache just trying to get the image to function.
But....When it does work the phone does not see my SIM card, IMEI, nothing.. I have no mobile connectivity. Restoring the AOKP nandroid brings me back to a fully functioning phone.
So my questions are:
Can anyone explain to me why the TW nandroid is giving all these GAPPS issues and how to circumvent/fix it?
Why is the system seeming to lose my IMEI/SIM info? Is there a way to fix that? Should I have done something different in my setup/nandroid creation?
Lastly - I don't quite understand how CWM works. There is a recovery image. When I do factory reset, is it resetting to this recovery image as opposed to the factory TW? I seem to think so, when I do a reset I see the android version is not what my factory one is.
Thanks all.
Hi everybody,
I'm using a Redmi Note2 Prime with MIUI 8 7.4.27 Beta (weekly). The phone was running very smooth, fast and reliable - battery life was always several days.
Yesterday I tried to root it using method 4 from here using recovery.img from TWRP 3.0.2-2.zip and UPDATE-SuperSU-v2.79-20161211114519.zip (SuperSU app was already installed). After several attempts (installed MI PC Suite twice until it worked on Win10) it finally worked.
I rooted since I wanted to try dual boot patcher and a MM ROM as second.
But after phone booted again it was nearly unusable. No smooth reaction I had to wait several seconds until screens changes when just scroll through them. Also apps and settings now need lots of time more before they start. Wifi is always turned off after reboot (while it was on during shutdown) and Google sync starts automatically after reboot while it is deactivated in all settings. Also background image of lock screen was changed. Google Play Services are now constantly crashing (need to click away these message requesters all the time) and Play Store does not even start anymore. Meanwhile I removed SuperSU app again since it never asked for granting root access while it was set to do so.
Installing a second ROM using Dual Boot Patcher finally also did not work (patching worked - installing not). Details are provided here.
I am still puzzled what happened here and do not have any clue since I rooted already several devices without any problems so far. Even this one some time ago IIRC.
Does anybody have any idea how I can get the phone back into a stable, usable mode? Do I have to completely reflash the MIUI8 ROM? Or do I have to use another SuperSU zip?
Any help is highly appreciated!
Thanks guys!
You can try wiping data/factory reset.
To easily install TWRP, you can use the Fastboot Install Method described here:
https://twrp.me/devices/xiaomiredminote2.html
Thanks. But doesn't this wipe/reset delete all apps and data (which I try to avoid)?
Would reflashing complete MIUI8 (version which I already have installed - without any system/data wipe) cure the problem?
TWRP app is already installed - but either TWRP recovery or SuperSU.zip crashed the Google Services (Play Services or even more) for whatever reason.
Does anybody have some idea why this might have happened? Maybe due to dalvik cache wipe which was requested?
I think that the phone become unusable a Google Services/Play Services is crashing because of wrong settings or data corruption.
That's why I said to do a factory reset.
You can try deleting just cache and data for Google Play Services and Google Play Store apps. Data are on cloud and should be restored automatically when needed.
Seems I got it working again - thanks to post #2. Used TWRP app to install another TWRP, afterwards I got a reboot loop. Then I deleted cache and dalvik cache and now everything works fine again!
Thank you!
Well Dual Boot still does not work but progressed a little bit further - but this is a different topic.
Try do delete your Rom (Backup all with Titanium backup before) and try to install latest Dev from mi-globe ! Prerootet and very smooth and good ROMs!
Thanks. But as said - got it working again (see above). The only thing which is not working is flashing a secondary ROM using Dual Boot Patcher (already opened another thread and posted it into the PATHCER thread - but seems nobody knows about some solution...).