Hello,
I have a big problem with the I9300 from my mother-of-law.
Her Galaxy is neither modified, nor rooted or anything. So it's stilll stock.
Now her I9300 won't boot correctly anymore.
When she starts it, it lasts much longer than normal to boot. When unlocking, an error message pops up immediately "Application Installer stopped" (angehalten), when clicking ok, it comes another time then it reboots completely.
When going into "Android system recovery" and wiping data/factory reset, there still comes an error message when I reboot (error) and the same procedure appears.
> It lasts a long time to boot > after unlocking the error message appears (Application installer stopped and it reboots immediately).
Does anyone have an idea what the issue might be and what I could do?
Flash a new Rom?
(P.S. sometimes it doesn't start at all an just shuts down and the battery is empty - even though it was still 77%).
Edit:
Sorry, I made a data / f factory reset another time and now it finally seems to work, unfortunately with all datas erased..
You should flash newest firmware for your country via Odin and it should work correctly
Related
I just used Matt's utility to sbf and clean install .181 (same version I was on previously).
Once completed, the phone booted to the M logo, showed Andy with a cereal box, installed a package (status bar filled with orange), then rebooted and won't proceed past M logo.
I force shutdown and go into recovery, and select Wipe Cache - and the phone does nothing.
Any ideas?
I then thought it may be the download, so I downloaded the SBF and used RSD lite and tried again... no luck.
Any help is appreciated.. I'm really stumped here.
*Update*
So after re-flashing 8 times, I've been able to at least get to the "welcome" screen to begin android setup.. I am then greeted with the following errors:
"The application IMSCServer (process com.motorola.android.server.ims) has stopped unexpectedly. Please try again."
"The process com.motorola.service.main has stopped unexpectedly. Please try again."
"The application Smart Actions (process com.motorola.contextual.smartrules) has stopped unexpectedly. Please try again."
I'm sure there are more stacked underneath, but every time I hit force close, a new one pops up or repeats itself... It appears to be flashing incorrectly every time I fastboot which is causing the errors... I've been able to clear the cache and data/factory reset in recovery, but the errors won't go away.
After fiddling with the force closes for about 2 minutes after the phone boots, it freezes.
Anyone have any ideas on a an alternative way to ensure a clean flash?
Anyone have any ideas?? I dont think it's bricked as I can get to the set up screen - it just keeps freezing whenever I fastboot restore or use the utility.
Well, I've managed to install Bootstrap and get into it - now I'm just unclear what to do from here.. The ROM flash seems bad - while the phone was loading before freezing, it came up with a message box that said 'Storage is Full'. It definitely appears as if it's not wiping clean when SBF'ing.
I will continue to document my experiences if anyone could assist and jump in.
Hi guys,
little bit of background on the phone, had it since new close to 2 years away (2 year contract and im 7weeks from an upgrade) the phone is on orange (well EE now)
Basically when I turn my phone on it is stuck in a force close loop, with loads of different messages appearing, such as;
(process com.sec.android.provider.logsprovider)
calenders, messaging etc etc
So I have tried going into the boot mode, by pressing volume up, home screen and the power button.
Then when I try to reboot it comes up with the error messages;
e:error in /data/log/recovery_log.txt (read-only file system)
(read-only file system)
e:copy_kernel_file :: Can't Open /data/log/recovery_kernel_log.txt
Rebooting...
It then just continues onto the normal home screen, then when I enter my swipe code it comes up with the force close loop again.
Any solutions to this problem, Or will I have to factory restore, or is completly broken? Im not due an upgrade for about 7weeks either
Would rather not have to factory restore if possible as I have some files on there I dont want to loose, but if its unhelpable so be it
Thanks in advance guys!
Cheeky little bump, Anyone know a fix to this?
Have similar problem...
I believe a factory reset will fix it...sorry to hear you losing files though..
I have a similar problem. I should probably make a new thread for this though...
Background: Samsung Galaxy SII 1900 bought October 2011. Yesterday flashed a stock ROM for the phone and everything was working perfectly. This is probably not related but have been trying to install a working version of Android Keyboard which has gesture typing working for other languages than English, German, Spanish and French and so some hours before this happened I tried to flash a zip with that but it turned up "e: signature verification failed" so I pretty much gave it up and the phone was still working. Then I decided to install another recovery mode on the phone cause that should allow me to install without verification. So I downloaded the one for SGS2 at clockworkmod com rommanager and put it in on the SD card. Then I shut down the phone and this is the weird part: First I accidentally pressed the power button first so I realised the phone was gonna boot normall so I pressed the power button again to force shut it down. I pressed for quite a long time and then it just restarted and I'm at a boot loop where it says Samsung Galaxy S II with white text on black background.... Then suddenly after removing the battery and trying start several times it booted normally. So I just continued where I left off going to make a backup in Titanium Backup before flashing CWM and suddenly the phone just restarted and I got into the boot loop again. I am able to enter Download mode and Recovery mode but the phone no longer starts. Been trying like 30 times to restart it... Now when I entered Recovery mode just now I got the error message
"E:Error in /data/recovery_kernel_log.txt(Read-only file system)" in red letters... and that's where I'm at now.
Here's a sitty picture of it from my HP Chromebook webcam ******* (Google Drive) Edit: Not allowed to post links in first 10 posts
i recently flashed a new firmware on my sony xperia z2.
everthing went good.
i started up my phone and as i wanted to type in my sim code there was the error Unfortunately,android.process.acore has stopped for a millisecond and then my phone rebooted again and again and again.
pls i wanted also flash another firmware but the same thing happened.
Please Help.
Did a forum search and tried every solution I could but this is where I am at......D6503
Same problem as OP
Had working MM (niaboc79's found @ http://forum.xda-developers.com/xperia-z2/development/rom-official-6-0-1-23-5-0-486-beta-t3336770) but for some reason without the included recovery.
Decided I would install [NUT]'s Z2-lockeddualrecovery2.8.26-RELEASE.combined in preperation for future flashes.
This lead to a Bootloop.
Then I flashed D6503_Customized ES_1281-4644_23.4.A.1.264_R8C.ftf via Flashtool.
This helped me passed the initial Bootloop, all looked good, got the usual "program optimizing" load up.
System booted, albeit in Spanish, to language screen.
After that I got a few errors such as "unfortunately media...gmail...stopped" which allow me to press "OK"
then the "unfortunately,android.process.acore has stopped" message which is where the system freezes and reboots.
If I leave it alone and don't touch it, it just boots for 5/10 seconds before freezing and rebooting.
I tried flashing a different ftf however since flashing D6503_Customized ES_1281-4644_23.4.A.1.264_R8C.ftf all my settings have been reset, so USB Debugging etc is no longer checked which means it will not allow flashing.
I have access via Fastboot and Flashmode but I am unsure what I can do with these to restore a working system.
While phone is booting Flashtool reads my device correctly (model, firmware) and informs me I do not have root access, Busybox any longer.
It does give me the option at this stage, via now accessible tabs in Flashtool, to "root," "ask root permissions," and "install apk" but nothing I do works.
One one occasion, not sure what I did as I seem unable to repeat it, but it said I did infact HAVE root access. At that point I should have clicked on Flashtools "install recovery" or "root" tab but unfortunately didn't.
What are my options here? Is there a solution I can perform myself at this stage?
Thanks in advance
UPDATE:
Tried again for the 600th time, this time took my memory card out and it seems to have flashed the "...264" rom.
Select all wipes when flashing a new firmware.
so it goes like this .. I had a problem with my z90a40 as I was trying to fix a problem with network services(phone was able to recognize the sim but there was no service).. first I did a factory reset- didn't work, then I entered the boot menu again and wiped user data, then I choose "restore QCN backup" option , after that I rebooted, phone entered this initializing statues and after 2 seconds it rebooted(doesn't even finish the initializing, actually it only ticks at maybe less than 5% and then reboot) , and kept doing that, after this, I could no longer enter the boot menu ... I tried everything, ADB or cwm recovery won't work cause my device is not rooted nor the usb debugging is on .. so am stuck with this "initializing loop".. flashing didn't solve it for me, I tried every ROM I could find, rooted or not .. nothing .. what should I do now ?
thanks in advance & sorry for bad English
same problem
axiom913 said:
so it goes like this .. I had a problem with my z90a40 as I was trying to fix a problem with network services(phone was able to recognize the sim but there was no service).. first I did a factory reset- didn't work, then I entered the boot menu again and wiped user data, then I choose "restore QCN backup" option , after that I rebooted, phone entered this initializing statues and after 2 seconds it rebooted(doesn't even finish the initializing, actually it only ticks at maybe less than 5% and then reboot) , and kept doing that, after this, I could no longer enter the boot menu ... I tried everything, ADB or cwm recovery won't work cause my device is not rooted nor the usb debugging is on .. so am stuck with this "initializing loop".. flashing didn't solve it for me, I tried every ROM I could find, rooted or not .. nothing .. what should I do now ?
thanks in advance & sorry for bad English
Click to expand...
Click to collapse
1st was the network data, tried reset and then CQN restore on black menu. now just keep on rebooting with lenovo logo initializing at 2-5% then loop restart again...
now cannot access the black menu (vol down + power)
stuck on rebooting phone any fix?
Hi,
i'll try to explain the problem.
I use the Galaxy s6 SM-G925T and wanted to reset to factory defaults. The phone is in original state. So no custom rom, not rooted or any other modifications. The Battery has been replaced because the old battery had to be charged every 4 hours. Because the new battery does not lives much longer (maybe 6 hours) i wanted the factory reset.
First using the volume-up home and power button, i've choosen wipe cache / factory reset
Down the bottom of the screen was a text : No Support SINGLE-SKU - Supported API: 3 - dm-verify error
I continued and wiped the data
The system returned "Data wipe complete"
After the phone rebooted the system restarted, only to show the blinking SAMSUNG text.
I left the phone blinking for about 1 hour, nothing happened.
So i loaded the official systemfile : CF-Auto-Root-zerolte-zeroltexx-smg925f.tar
using Odin3_v3.14.1 i was able to flash it onto the phone.
After rebooting now the red android puppet showed up and the cf-auto-root program fnished without errors but the phone still wont start
Is the phone bricked or is it still possible to restore factory defaults and get the phone back to work ?
Thanx for all the helpfull answers !!
You may close this question.