Earlier today I decided I'd give a non-stock ROM a try, and ended up deciding on slimrom. I followed the instructions provided (factory reset, wipe cache, wipe dalvik cache) with no issues, but now when I try to flash Base_Samsung_4.0.zip it says
-- Installing: /emmc/Base_Samsung_4.0.zip
Finding update package...
OPening update package...
Installing update...
Slim ICS
Click to expand...
Click to collapse
and has been like this for over half an hour now. I'm starting to get worried that something is broken, and as my phone is my main form of communications I'd really like to be able to reply to people. I'd have asked in the slimrom thread, but I'm yet to hit 10 posts and here was my best bet.
You could try to wait some more, or take a little risk by pulling out the battery. I dont think there are any other options
Sent from my GT-I9100 using XDA
Dammit. It's only a 44MB file, which is why I find 30 minutes a very long time to need to flash. Might leave it for another 30 mins or so and then just pull the battery and hope for the best.
Emp_M said:
Earlier today I decided I'd give a non-stock ROM a try, and ended up deciding on slimrom. I followed the instructions provided (factory reset, wipe cache, wipe dalvik cache) with no issues, but now when I try to flash Base_Samsung_4.0.zip it says
and has been like this for over half an hour now. I'm starting to get worried that something is broken, and as my phone is my main form of communications I'd really like to be able to reply to people. I'd have asked in the slimrom thread, but I'm yet to hit 10 posts and here was my best bet.
Click to expand...
Click to collapse
Quickly tap the volume buttons and power button
Sent from my GT-P7510 using xda premium
slimrom probs
Hi
I installed slimrom once it took five-ten mins id pull the battry and follow the steps again except after youve done those wipe wipe wipe etc go in advanced (i think) and fix permissions then install rom again, also i cannot remember now but if it swapps your external sdcard to another folder emmc dont worry its done that for everyone i reccommend just leaving it and changing download folder in apps rather than installing sdcard fix (not app name)
Anyhow enjoy
Finally got it working fine. I just didn't try flashing Base_Samsung_4.0.zip and I'm now running Slimrom 4.
Related
Now my head i about to explode
Anyhow, I have an annoying problem.
Before the upgrade to XXALF6 I noticed no problem other than the known drainage of the battery in idle mode.
I rooted and flashed a ROM and it was ok.
But I got sick of the ROM and I hard reset the phone.
No problems.
Then I upgraded to XXALF6 - still unrooted and all.
First thing I notice is that the phone is lagging a bit now and then. Then when I sent and recieved an SMS or two the phone hung and rebooted.
I seems that happend because when vibration was active.
Also there was a new message saying "com.google.process.gapps" stopped working. And that came up again and again.
As far as I could find online that had to do with syncing the calendar and it should help to clear calendar cache in the phone. It did not.
Then I rooted the phone, just "CF-Root-SGS3-v6.4", no other ROM.
Now the problem was even worse and also the sound stops working on and off all the time.
I tried to find the "com.google.process.gapps" with a file explorer with no luck.
I do find it in ROM Toolbox but its not possible to see the where on the phone the file is even there. Also its not possible to uninstall or even kill the process.
I did notice there seem to be doubles of some apps that I didnt notice previously to flashing CF-Root this time.
And I recall the new guide never mentions to wipe any phone data whatsoever during rooting the phone, and now I am thinking that maybe that should have been in the guide?
Anyhow.. appreciate ANY tips at all, Im so sick of this for the moment ^^
Go to cwm recovery, wipe cash, wipe dalvik cash, wipe data/factory reset, then go to mounts&storage, format system. Then put your phone into the download mode and flash ROM again with odin. This should give you a nice and clean install,without any force closes..
Sent from my GT-I9300 using xda app-developers app
pedja381 said:
Go to cwm recovery, wipe cash, wipe dalvik cash, wipe data/factory reset, then go to mounts&storage, format system. Then put your phone into the download mode and flash ROM again with odin. This should give you a nice and clean install,without any force closes..
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I did wipe all things, cache, Dalvik, battery and user data with CWM.
At the moment it seems the phone is quite okay actually! The only thing left is SU.
U think I have to format system as well? What else would really be "cleaned" out that wasn't allready with the wipes?
Trust me,some of the devs insisted on formating system before flashing their custom roms,and I did have a bunch of force closes,until I decided to go their way and fully format the phone. It then installs everything from the scratch,so there's no way anything to go wrong.. give it a try,and report back... btw. make sure that you DO NOT restore any of the system data,if you use TB
Sent from my GT-I9300 using xda app-developers app
Yeah I pretty much learnt same way as predja it is always better to do full system wipe, it is not always necessary with some roms but if you do it you won't come across the problems you have as often.
sent from my SGS3 Using XDA app
I've seen a post about this one in the EVO area, but not here amongst us SGS3 owners:
When I reboot my phone, it always goes through an "Android is updating, application xxx of 3xx" counting up - and takes two or three minutes every reboot.
Is this normal under ICS?
Hmm, I'd say this is Not normal. One of the big "selling points" of the gs3 and ICS is the quick boot time. For me it is very quick. Maybe u should try doing a factory reset and see if it stops this behavior??
Sent str8 from my half eaten Banilla Ice Cream Samich
ratledge said:
I've seen a post about this one in the EVO area, but not here amongst us SGS3 owners:
When I reboot my phone, it always goes through an "Android is updating, application xxx of 3xx" counting up - and takes two or three minutes every reboot.
Is this normal under ICS?
Click to expand...
Click to collapse
If you're rebooting your phone after you wipe your dalvik cache, than that is normal. Reason being is that it stores applications for optimization so that the OS can run more smoothly. When you wipe your dalvik, it clears them out, and then when you reboot, it rebuilds the cache for all applications. Just do a normal reboot without wiping anything and see if it still does it.
That is not normal if it is happening on every boot, only if you wipe your dalvik cache then yes it will update.
id_twin said:
If you're rebooting your phone after you wipe your dalvik cache, than that is normal. Reason being is that it stores applications for optimization so that the OS can run more smoothly. When you wipe your dalvik, it clears them out, and then when you reboot, it rebuilds the cache for all applications. Just do a normal reboot without wiping anything and see if it still does it.
Click to expand...
Click to collapse
Yep, just a simple reboot or even a fault / reboot does the same thing. I'm not wiping the Dalvik cache or anything. Happens every time I boot my phone, and I've noticed over the past few days that I never seem to go into 4G/LTE mode any more. Curious - I guess I've laid the hammer on it a bit too much.
Are you using a custom rom or rooted? Or are you completely stock?
Sent from my SCH-I535 using Tapatalk 2
ratledge said:
Yep, just a simple reboot or even a fault / reboot does the same thing. I'm not wiping the Dalvik cache or anything. Happens every time I boot my phone, and I've noticed over the past few days that I never seem to go into 4G/LTE mode any more. Curious - I guess I've laid the hammer on it a bit too much.
Click to expand...
Click to collapse
what rom r u using ????
with aokp there are setting to which the user can wipe cache and dalvik on every reboot
I read on another forum that a TitaniumBackup odex file may cause this on certain phones. Try uninstalling the apk and then re-install it.
krackerjac said:
what rom r u using ????
with aokp there are setting to which the user can wipe cache and dalvik on every reboot
Click to expand...
Click to collapse
Sure sounds like it. I'm using the "Route66" rooted ROM with the Invisiblek overclocking kernel in place of the recovery.
Most likely the overclock. i ran the stock rooted 66 with no issue. I also have titanium backup installed without that issue.
id_twin said:
I read on another forum that a TitaniumBackup odex file may cause this on certain phones. Try uninstalling the apk and then re-install it.
Click to expand...
Click to collapse
Worth a shot. I'll give it a rip and report back... Thanks!
hmmm... Uninstalled and replaced Titanium Backup, reflashed the stock recovery: no joy there. I'm still getting the rebuild every time I boot. I suppose when I have more time (read next weekend, I'm working 12 hours every day this weekend, then my niece is in town for a week), I'll blow it to hades and start over.
ratledge said:
hmmm... Uninstalled and replaced Titanium Backup, reflashed the stock recovery: no joy there. I'm still getting the rebuild every time I boot. I suppose when I have more time (read next weekend, I'm working 12 hours every day this weekend, then my niece is in town for a week), I'll blow it to hades and start over.
Click to expand...
Click to collapse
Oh, well - factory reset, re-route66, invisiblek's v2 overclocked kernel. I'm good, no "Android is updating..." every time, and no mo unlocked icon on the main screen.
I dunno what I did, but the Sammy din't like it!
Thanks, guys!
Solved
Hello everyone
Since a few days ago my S2's Wifi is not working
h.ttp://i.imgur.com/ojDOm.png
The icon stays like this, pressing it does nothing. it happened 3 - 4 times before, usually, I'd just reboot it and that would do the trick (I google'd a bit and saw this is a common glitch when trying to turn wifi on), but not anymore, it refuses to turn on no matter what I do, rebooting, shutting down and restarting, it's stuck.
h.ttp://i.imgur.com/KeMxb.png
I can't Scan, add a network nor switch the toggle on/off because pressing them does nothing, So... I thought I should do backup and factory reset it, nope. still stuck.
What's wrong with it? Any ideas? The phone is a year old, running 4.0.3 Stock
Sorry about the dots in the URL's, can't post links yet.
Edit: Forgot to mention it started doing this since I got ICS, maybe I should try flashing it to see if that fixes it, I'm kinda reluctant though, since the factory reset didn't seem to do anything and I haven't done it before.
Cathari said:
Hello everyone
Since a few days ago my S2's Wifi is not working
h.ttp://i.imgur.com/ojDOm.png
The icon stays like this, pressing it does nothing. it happened 3 - 4 times before, usually, I'd just reboot it and that would do the trick (I google'd a bit and saw this is a common glitch when trying to turn wifi on), but not anymore, it refuses to turn on no matter what I do, rebooting, shutting down and restarting, it's stuck.
h.ttp://i.imgur.com/KeMxb.png
I can't Scan, add a network nor switch the toggle on/off because pressing them does nothing, So... I thought I should do backup and factory reset it, nope. still stuck.
What's wrong with it? Any ideas? The phone is a year old, running 4.0.3 Stock
Sorry about the dots in the URL's, can't post links yet.
Edit: Forgot to mention it started doing this since I got ICS, maybe I should try flashing it to see if that fixes it, I'm kinda reluctant though, since the factory reset didn't seem to do anything and I haven't done it before.
Click to expand...
Click to collapse
Do the steps below
- Boot to CWM recovery
- wipe cache partition
- wipe dalvik cache (under advanced)
- fix permissions (under advanced)
- reboot system now
The above steps will not make you lose some files and data
If that does not help, then flash another kernel
Since putting a custom kernel on my phone my bluetooth does exactly the same as what your wife is doing. Only way to turn it on is to reboot the phone whilst it is trying to turn on (ie whilst it is a shade of green)
saywhatt said:
Do the steps below
- Boot to CWM recovery
- wipe cache partition
- wipe dalvik cache (under advanced)
- fix permissions (under advanced)
- reboot system now
The above steps will not make you lose some files and data
If that does not help, then flash another kernel
Click to expand...
Click to collapse
Gonna try that and flash CM9 while I'm at it, never done this before... Lets see how it goes following the steps on CM's wiki
Cathari said:
Gonna try that and flash CM9 while I'm at it, never done this before... Lets see how it goes following the steps on CM's wiki
Click to expand...
Click to collapse
you should be Ok its relativley straight forward
Well, Flashed in CWM Recovery and CM9, wiped cache, Dalvik cache and fixed permissions but the wifi is still not working... it's still stuck at "Turning Wi-Fi on"
I really have no idea about kernels and that stuff, I don't know how to flash 'em (unless it's the same as flashing CWM) or which one to get at all, since theres too many and I don't know what they do/know if they're compatible.
Flashing kernels are the same as flashing ROMs and modems..
There are 2 ways to flash kernels.. 1 is via odin (.tar file) and 2 is via CWM (.zip file)
Now, if your ROM is on JB then use a JB Kernel
If ICS = ICS Kernel
AOKP = AOKP Kernel
AOSP = AOSP Kernel
The thing with kernel is that you have to match it with the ROM's base..
Sent from my GT-I9300 using xda premium
Hm...Checked my phone 7 hours after flashing CM9 on it and suddenly the Wifi's back on
Any explanation for this? It doesn't make any sense, I didn't even touch the phone during that time and it fixed itself?
Edit: Thanks for clarifying that up saywhatt, since I already flashed if and thus, voided the warranty I might as well go ahead and try flashing a kernel to improve battery life and get into the scene.
Cathari said:
Hm...Checked my phone 7 hours after flashing CM9 on it and suddenly the Wifi's back on
Any explanation for this? It doesn't make any sense, I didn't even touch the phone during that time and it fixed itself?
Edit: Thanks for clarifying that up saywhatt, since I already flashed if and thus, voided the warranty I might as well go ahead and try flashing a kernel to improve battery life and get into the scene.
Click to expand...
Click to collapse
No problem.
Perhaps the ROM was "settling"? Lol i dunno.. but i'm glad to hear you got it sorted out. You can revert back to complete stock if you have some serious problems and it is needed to be sent to the service center..
1 download triangle away to clear the binary count
2 flash stock firmware
Voila! U no longer have a void warranty
Sent from my GT-I9300 using xda premium
Several users swear by wiping or flashing multiple times. However, the explanations often seem like superstitions.
I would think if a single wipe didn't completely clear a partition, that would be a bug of the recovery software.
I would think if a ROM didn't install right with a single flash, that would be a bug of the ROM.
Thoughts?
I agree with your thoughts. I've never had a problem with just wiping once and/or flashing once. Not sure what wiping and/or flashing more than once would do if it didn't work the first time lol.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app.
I wipe atleast twice and flash once. Just check the md5 of the zip before flashing and there shouldn't be errors
Idk why someone would need to flash more than one time, and there's scripts to wipe 5 to 10 times automatically
But I wipe twice just to feel I got everything but I know one time is enough lol
Sent from my ADR6425LVW using xda app-developers app
I figured as such. Just wanted to make sure.
sdz2 said:
Several users swear by wiping or flashing multiple times. However, the explanations often seem like superstitions.
I would think if a single wipe didn't completely clear a partition, that would be a bug of the recovery software.
I would think if a ROM didn't install right with a single flash, that would be a bug of the ROM.
Thoughts?
Click to expand...
Click to collapse
There was a problem a long time ago involving clockwork recovery where wiping wasn't working all the time. At that time it was suggested to perform multiple wipes on that recovery. I think this all started and sort of stuck since then.
A developer friend of mine once said about wiping and changing ROMs...
"I treat wiping for a ROM change like taking a crap, you wipe and wipe until it's clean, then wipe one more time just to make sure I got everything."
Doesn't really answer the OPs question, just comes to mind every time someone says wipe more than once.
I wipe once because I like to live dangerously ... ohh we are talking about phones
but in honesty I never had a problem wiping once.
Whenever I use ANY rom that isn't based on stock I get random reboots. I'm currently on stock ics and really want to be able to run later versions of android. I can run padawan rom and blackstar perfectly fine without any random reboots but for other roms I somehow get random reboots. Am I flashing roms the wrong way or is something wrong with my phone?
Any help is appreciated!
shaftgobbler said:
Whenever I use ANY rom that isn't based on stock I get random reboots. I'm currently on stock ics and really want to be able to run later versions of android. I can run padawan rom and blackstar perfectly fine without any random reboots but for other roms I somehow get random reboots. Am I flashing roms the wrong way or is something wrong with my phone?
Any help is appreciated!
Click to expand...
Click to collapse
After flashing new ROM, did you wiped cache+dalvic cache and factory resetted your phone?
If not then do so, it'll be helpful for you.
Also try to clean flash your ROM, after wiping system and data.
PS: Also check the ROM your flashing is stable enough and don't have major bugs.
Regards,
hitman-xda
hitman-xda said:
After flashing new ROM, did you wiped cache+dalvic cache and factory resetted your phone?
If not then do so, it'll be helpful for you.
Also try to clean flash your ROM, after wiping system and data.
PS: Also check the ROM your flashing is stable enough and don't have major bugs.
Regards,
hitman-xda
Click to expand...
Click to collapse
I tried that many times lol but it still didn't help though. Might try again though.
shaftgobbler said:
I tried that many times lol but it still didn't help though. Might try again though.
Click to expand...
Click to collapse
Clean flash ROM > wipe cache+dalvic cache > reboot > flash gapps > wipe cache+dalvic cache > reboot > factory reset > reboot
Hope the above thing works
Regards,
hitman-xda
hitman-xda said:
Clean flash ROM > wipe cache+dalvic cache > reboot > flash gapps > wipe cache+dalvic cache > reboot > factory reset > reboot
Hope the above thing works
Regards,
hitman-xda
Click to expand...
Click to collapse
k will try when I have the chance I appreciate the help:good:
hitman-xda said:
Clean flash ROM > wipe cache+dalvic cache > reboot > flash gapps > wipe cache+dalvic cache > reboot > factory reset > reboot
Hope the above thing works
Regards,
hitman-xda
Click to expand...
Click to collapse
Order is incorrect. Factory reset, wipe cache and dalvic cache, flash ROM, flash a compatible gapps package, wipe cache and dalvic cache again, reboot system. Let rom fully boot. Only enter your wi-fi and google account info at this time (If asked) .Let settle for at least 10 minutes after boot before playing with your newly installed ROM. Best to use gimmeitorilltell's TWRP version 2.8.0.0 or possibly newer or most recent CWM. Use of incorrect gapps, or fiddling with a roms settings before letting it settle in will result in problems. Follow instructions/tips in the OP of the forum thread dedicated to your your chosen ROM.
Sent from my SAMSUNG-SGH-I717
developweb said:
Order is incorrect. Factory reset, wipe cache and dalvic cache, flash ROM, flash a compatible gapps package, wipe cache and dalvic cache again, reboot system. Let rom fully boot. Only enter your wi-fi and google account info at this time (If asked) .Let settle for at least 10 minutes after boot before playing with your newly installed ROM. Best to use gimmeitorilltell's TWRP version 2.8.0.0 or possibly newer or most recent CWM. Use of incorrect gapps, or fiddling with a roms settings before letting it settle in will result in problems. Follow instructions/tips in the OP of the forum thread dedicated to your your chosen ROM.
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
k will try that thanks guys for the help
Well I followed the steps exactly as told and I'm still getting random reboots. What shud I do next? I'm using beanstalk 4.3 since some of the kitkat Roma I use seem buggy and I can't get gaps to work on lollipop
shaftgobbler said:
Well I followed the steps exactly as told and I'm still getting random reboots. What shud I do next? I'm using beanstalk 4.3 since some of the kitkat Roma I use seem buggy and I can't get gaps to work on lollipop
Click to expand...
Click to collapse
Ok, I'll bite again....
Many who have had ongoing, unexplainable things going on with their phone recommend 1)a new or different battery (a fresh battery does wonders) or 2)wiping everything and going back to full stock....whatever shipped with your phone. Like a reset. Start over.
Edit: and lollipop gapps come in 5.0 and 5.1 and like I said earlier make sure you've got the right ones.
Sent from my SAMSUNG-SGH-I717
developweb said:
Ok, I'll bite again....
Many who have had ongoing, unexplainable things going on with their phone recommend 1)a new or different battery (a fresh battery does wonders) or 2)wiping everything and going back to full stock....whatever shipped with your phone. Like a reset. Start over.
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
I did both of those already. I'm currently using a new battery and went back to stock multiple times then returning to a rom. Nothing seemed to work.
developweb said:
Ok, I'll bite again....
Many who have had ongoing, unexplainable things going on with their phone recommend 1)a new or different battery (a fresh battery does wonders) or 2)wiping everything and going back to full stock....whatever shipped with your phone. Like a reset. Start over.
Edit: and lollipop gapps come in 5.0 and 5.1 and like I said earlier make sure you've got the right ones.
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
Well im not having random reboots now thanks for the help though I hope it stays this way. But I get reboots when changing cup speed and governor or stay in camera app for too long. Probably just the rom itself. Thanks all for the help! I'll tell if anything goes wrong:good: