Hi, i have been using XWLP9 stock rom + DXLP9 stock kernel for some days but i'm having weird lag issues with lock screen. I have had the same issues before with LP4 rom.
I use simple slide lock screen, but it also happens with pattern lock screen. Sometimes after pressing power or home buttons, after that screen turns on, screen is very unresponsive and i have to slide 3 times to unlock because it is laggy. Pressing home button again or waiting a bit before sliding reduce the problem, but it is irritating to do this every time i want to use my phone
I wiped everything before flashing and i'm not using external sdcard.
¿Is my phone faulty or is it a common problem on ICS roms? I never had this problems using stock GB rom.
Thanks for your help
Did you tried wiping?
I say backup your stuff, do a full wipe using cwm including format of system partition.
After that flash stock dxlp9 not xwlp9.
Wipe again using the dial code.
Don't think its your phone, might be bad flash.
atifsh said:
Did you tried wiping?
I say backup your stuff, do a full wipe using cwm including format of system partition.
After that flash stock dxlp9 not xwlp9.
Wipe again using the dial code.
Don't think its your phone, might be bad flash.
Click to expand...
Click to collapse
Hi, thanks for your answer.
My phone is not rooted so i have not used cwm, but i did the following wipes in recovery mode before flashing: Wipe Data/Factory reset. After that i wiped sd. I flashed my phone twice doing that, first LP4 and then XWLP9.
I use that rom instead of DXLP9 because it has Spanish language. However, I flashed DXLP9 kernel on top of XWLP9 to avoid SOD issues.
What are the differences between cwm wipes and the wipes i did?
as atifsh said ,follow tht an get it rooted to enjoy the benefits of android.....read few posts for ,begginers,rooting,flashing it will help u instead of asking minor issues.....
http://forum.xda-developers.com/showthread.php?t=1501719
get the cwm.zip, install it using the stock recovery, you will get touch version of cwm.
now goto mount and storage
format data, system, cache
goto advanced
wipe dalvik cache
reboot into download mode flash stock dxlp9 using odin
without signing let your phone start.
now see if you have those issues.
i think you will not have those issues anymore.
now you can flash any stock rom but please stay away from xwlp9. use xwlp7 instead.
Edit:
you never got rooted in the process above, if you dont want you are still as stock as you were before.
wiping the way i told will completly erase the OS from your phone thus you will have clean slate to start with.
if you want to stay on dxlp9, let me know ill tell you how to get spanish language for swype keyboard.
atifsh said:
http://forum.xda-developers.com/showthread.php?t=1501719
get the cwm.zip, install it using the stock recovery, you will get touch version of cwm.
now goto mount and storage
format data, system, cache
goto advanced
wipe dalvik cache
reboot into download mode flash stock dxlp9 using odin
without signing let your phone start.
now see if you have those issues.
i think you will not have those issues anymore.
now you can flash any stock rom but please stay away from xwlp9. use xwlp7 instead.
Edit:
you never got rooted in the process above, if you dont want you are still as stock as you were before.
wiping the way i told will completly erase the OS from your phone thus you will have clean slate to start with.
if you want to stay on dxlp9, let me know ill tell you how to get spanish language for swype keyboard.
Click to expand...
Click to collapse
Thanks again for your help, I'm going to do what you suggest and I'll let you know after that
Im having the same problem with rooted device running DXLP9, even with custom kernels, someone advice plz.
AbuS3ood said:
Im having the same problem with rooted device running DXLP9, even with custom kernels, someone advice plz.
Click to expand...
Click to collapse
What about flashing the latest XWLPD and see if the problem exists? The non-wipe from Intratech should do if you have already wipe/clear everything prior to updating from Gingerbread to ICS..
I'm having the same problem with the unlock screen. I have stock XXLPH, but rooted. I've been having this issue almost since day 1.
It is so annoying that I decided to disable the lockscreen at all for now
atifsh said:
http://forum.xda-developers.com/showthread.php?t=1501719
get the cwm.zip, install it using the stock recovery, you will get touch version of cwm.
now goto mount and storage
format data, system, cache
goto advanced
wipe dalvik cache
reboot into download mode flash stock dxlp9 using odin
without signing let your phone start.
now see if you have those issues.
i think you will not have those issues anymore.
now you can flash any stock rom but please stay away from xwlp9. use xwlp7 instead.
Edit:
you never got rooted in the process above, if you dont want you are still as stock as you were before.
wiping the way i told will completly erase the OS from your phone thus you will have clean slate to start with.
if you want to stay on dxlp9, let me know ill tell you how to get spanish language for swype keyboard.
Click to expand...
Click to collapse
I have just flashed my phone again (XWLPD Nordic Conuntries) following your steps but the problem persists. I formatted data, system, cache, wiped dalvik cache but the annoying issue is still there
Another idea?
It's called wake up lag or something like that. It's horrible, sometimes the screen is unresponsive 2 seconds after pressing the power button. Correct me if I'm wrong but i don't think GB had this problem, I've only noticed it on ICS. So no, it's not just you.
Guys, I got the damn issue solved, I flashed the leaked TW launcher(attached) from the SGSIII rom, then everything went fine and the device is soft and fast.
If flashing the new TW launcher didn't solve the problem flash the latest version of Siyah Kernel (im using 3.2.5.2)
http://www.gokhanmoral.com/gm/
I don't have that issue, yes if screen is of for some time waking it takes 2 3 secs, but it never lags to Swype, even if I hurry and unlock it right when screen shows.
Related
So i managed to solve the problem that i had.
When i said that i could flash only the stock one, i was flashing XXKI3 as one file after each failed attempt to flash a custom one.
So i tried and flashed another stock rom, again as 1 file. after the flash was done the phone again stucked at first screen wit the triangle.
After that i thought that something was really messed up in the phone and flashed again XXKI3 with PIT and multiple files and offcourse RE-Partition.
After that flash a stock rom with 1 file and modified bootloader from Intratech's thread, this way you can also reset the binary caunter with a jig (can find many on ebay).
After finish flashing and first boot
root with CF kernel and flash any custom rom. It worked as it should. Now i am on a custom rom and trying to see which one suits me best.
Thank Jiganet for some may be needed modified bootloader which is recommended so you can reset binary counter.
Everyone tha nk you for your suggestions and help.
any rom that i install is not getting beyond the bootlogo. i had xxki3 stock with cf-root xxki3 kernel.
every install i make full wipe on everything before(data, cache, dalvik).
any body any idea?
only stock rom working.
The first boot takes some time. Are you waiting that long?
mariosraptor said:
any rom that i install is not getting beyond the bootlogo. i had xxki3 stock with cf-root xxki3 kernel.
every install i make full wipe on everything before(data, cache, dalvik).
any body any idea?
only stock rom working.
Click to expand...
Click to collapse
1. Enter Clockworkmod recovery
1a. Do a Backup (not a must, but i suggest) from the cwm recovery of your current rom/settings.
2. Wipe Data/Cache Factory reset
3. Flash the new rom you want
4. Again (not needed but well..) Wipe Data/Cache Factory Reset
5. Wipe Cache
6. Advanced -> Wipe Dalvik Cache (this is why you get bootloops)
7. Reboot to system
Wait 4-5 minutes and you will have your new, shiny working rom.
Hope it helps, cheers
yes. more than 10 minutes.
kanefox said:
The first boot takes some time. Are you waiting that long?
Click to expand...
Click to collapse
i am not getting any bootloops. it just gets stucked at the first screen with the triangle.
i have no experience in samsung but i have done all that you mention.
still no luck. i will try once more and let you know in about 20 minutes.
thanks for your help.
rembrandtlnx said:
1. Enter Clockworkmod recovery
1a. Do a Backup (not a must, but i suggest) from the cwm recovery of your current rom/settings.
2. Wipe Data/Cache Factory reset
3. Flash the new rom you want
4. Again (not needed but well..) Wipe Data/Cache Factory Reset
5. Wipe Cache
6. Advanced -> Wipe Dalvik Cache (this is why you get bootloops)
7. Reboot to system
Wait 4-5 minutes and you will have your new, shiny working rom.
Hope it helps, cheers
Click to expand...
Click to collapse
Mh strange, the strange is.. with the stock rom is working.
Looks like your phone dosnt like the rom you are flashing so the quesion now is:
Are you sure, you are flashing a rom your phone can read? I know the i9100G and the AT&T versions cant be flashed with the standard (i9100) S2 roms (there is a specific thread i think here on xda for those versions)
mine is an unbranded i9100 from Greece. i am flashing the correct roms.
rembrandtlnx said:
Mh strange, the strange is.. with the stock rom is working.
Looks like your phone dosnt like the rom you are flashing so the quesion now is:
Are you sure, you are flashing a rom your phone can read? I know the i9100G and the AT&T versions cant be flashed with the standard (i9100) S2 roms (there is a specific thread i think here on xda for those versions)
Click to expand...
Click to collapse
the same. more than 15 minutes of waiting time. flashing stock again.
Im sorry cant rly help you then, let's wait for some more experienced user answer
thanks. no worries. stock is good. matter of speaking
rembrandtlnx said:
Im sorry cant rly help you then, let's wait for some more experienced user answer
Click to expand...
Click to collapse
next time when u flash try formatting system.
In CWM >mounts and storage> format system
Please state detailed steps you did when flashing a ROM and what kind of ROM.. That will help alot on trouble shooting your problem.
Sent from my GT-I9100 using xda premium
every body read first post managed to solve this.
Hi was there a solution to this problem as I seem to get it with EVERY rom I try to install from zip?
Hi to all, this is my first Post and this is my First Android I come from an iPhone 2G, iPhone 3g, iPhone 3GS and my last phone was an iPhone 4!!! now I'm extremely happy with my new SGS2!!!
I have been searching a lot!!! for a solution for this flash loop issue,
1 - I have flash to a stock 2.3.5 KI3 samfirmware,
2- then I have Odin>PDA>cf-root-KI3-4.2.tar to root my phone.
3 - After that I downloaded 3 custom roms, DarkyROM2_KI3, VillainROM-3.0.0-signed and Cyanogen cm_galaxys2_full-112. put them on my root internal sdcard.
4 - booted to ClockworkMod Recovery menu.
5 - Wipe Data/Factory Reset
6 - Wipe Partition Cache.
7 - Install Zip from sdcard.
and every thing seems ok, but when i restart, it stays on the boot loop, even if i manage to enter to CWM Recovery menu it says that E: Can't Mount ... bla bla bla
I had been trying to put a custom rom so much that my binary counter is now on 10
I'm going to try what you wrote on the first post!
Restore to stock KI3 firmware using pit file and repartition.
after that install the cf-root kernel. Restart and try to install any custom firmware.
Hope it works
Not it did not work, Maybe the problem was Wipe Partition cache after installing new rom, going to stock and repeating
I'm having this exact same problem, please post here if you find an answer to your problem.
I first installed checkrom with no problems, then i decided to wipe and try install dlevrom but after rebooting i'm left with the same problem as above.
It's only when i flash stock 2.3.5 KI3 through odin with pit, repartition, all checked that my phone works.
I then repeat the steps of flashing cf root through odin and then try flash a custom rom, either checkrom or dlevrom and neither work.
Another try another fail!
I have no idea on what else can I do!!! tried again and nothing! I tied cf-root 4.1 and nothing and cf-root 4.2 and nothing!.
I'm having this exact same problem, please post here if you find an answer to your problem.
I first installed checkrom with no problems, then i decided to wipe and try install dlevrom but after rebooting i'm left with the same problem as above.
It's only when i flash stock 2.3.5 KI3 through odin with pit, repartition, all checked that my phone works.
I then repeat the steps of flashing cf root through odin and then try flash a custom rom, either checkrom or dlevrom and neither work.
Click to expand...
Click to collapse
After i got the stuck on boot! I can restore to stock by only using the PDA, I don't need to set the pit file again!, but I'm usign all the files on Odin to see If that makes any difference but nothing!!!
I wonder how mariosraptor did it!!!! Can you throw us a light???
I have explained it on first post. Just follow step by step the first post directions.
Sent from my GT-I9100 using xda premium
Nope it didn't work
The steps I did:
1. Restore to stock using PIT, PDA, PHONE, CSC.
2. After it boots root the phone with cf root 4.1 for ki3
3. Use CWM Recovery to flash the new rom on internal sdcard.
I have been doing it with wipe data, wipe cache, wipe develk.
Nothing is there a step that im missing?
Thanks
SOLVED!!!!!! JAJAJA
The only problem, was one minor thing, a little thing called Bootloader!
I installed the old bootloader!
find it here: http://forum.xda-developers.com/showthread.php?t=1075278
And after that every thing worked perfectly, no boot loops!!!!
Hope it helps!!!
As the thread title states...I was on 7.1 and downloaded/updated it to 7.2 Now the phone doesn't boot up and all I get is the Kernel Panic Upload Mode.
Anyway I can fix this? And if so, is there a way of doing it without completely formatting my phone and losing all my apps?
Oh and if it makes any difference I had to install that Siyah Kernel or whatever it was called to get out of the bootloop issue that I had with CM7.1. I'm thinking that that may be causing the problem....? But then again what do I know
wipe cache only.
valentinrascu said:
wipe cache only.
Click to expand...
Click to collapse
How? I've been trying [Power+Volume Up+Home] and it hasn't been doing anything. Can I do it through download mode somehow?
Had this problem when i flashed Lite'ning rom. Had to go into download and flash stock with odin. Took me a few tries to actually get the rom to work. As far as I know, that'd be your only option, seeing as recovery doesn't work for you.
take a deep breath and read, there is a very small chance of bricking your phone just so you know. Flash back original with Odin and start everything again
thanks for the replies...looks like i'm gonna flash the stock firmware back and see what i can do about getting to CM7.2 to work. hopefully flashing stock firmware is enough. I can't imagine how this would completely brick my phone and render it unusable.
As an aside...wtf is the point of this "recovery mode" when the thing doesn't even work half the time?
Anywho...downloading the stock .exe file now from here: http://devsrom4android.blogspot.ca/2011/10/samsung-galaxy-s2-firmwares-bell-canada.html[/url
Ok so I flashed the stock rom and now I'm in Android system recovery: Should I just reboot system now or do I wipe data/factory reset or wipe cache partition??
nubreed000 said:
Ok so I flashed the stock rom and now I'm in Android system recovery: Should I just reboot system now or do I wipe data/factory reset or wipe cache partition??
Click to expand...
Click to collapse
If you flashed stock, you should be fine just rebooting.
Its stuck on the boot screen. I tried just rebooting, then wiping/factory reset, then both wipes...reinstalled stock a few times and nothing worked each time. I'm suck on the Samsung Galaxy SII GT-I9100 screen
:-\...when I go into recovery, I get a ton of red messages/errors
I'm gonna try somethig other than stock firmware see if that helps.
edit Ok so I rooted the phone and it got past the first boot screen and now appears to be stuck on the "animated S" boot screen...progress!!
nubreed000 said:
thanks for the replies...looks like i'm gonna flash the stock firmware back and see what i can do about getting to CM7.2 to work. hopefully flashing stock firmware is enough. I can't imagine how this would completely brick my phone and render it unusable.
As an aside...wtf is the point of this "recovery mode" when the thing doesn't even work half the time?
Anywho...downloading the stock .exe file now from here: http://devsrom4android.blogspot.ca/...msung and their changes to Android framework.
Click to expand...
Click to collapse
Ok everything back to somewhat normal. Stock ROM didn't work but 2.3.6 did, so I'm on that. Now do I wanna go back to CM is the question...
Either way, thanks again for all the replies and helping me out with this. Greatly appreciated!
I don't know exactly what caused the issue. Maybe some recent apps since that was all that I had installed. I was running the latest AOKP ICS 4-28-12 and Siyah 3.1x. I forget the exact kernal number but it wasn't the version that I read about phone bricking (R6?).
So I wake up this morning and unlock my screen and there are popups for everything force closing. Not just foreground running apps but everything including background running apps. Every time an app autorestarts in the background the force close error msg pops up again. It was running fine just 6 hours prior since I was using it before bed.
Reboot. Same issue. CMW Recovery. Wipe cache/dalvik. Reflash AOKP and GApps. Reboot. Same force closing issue. WTF. Attach USB to comp and try to move a different ROM to my Internal SD but no dice. Comp isnt recognizing phone now. [email protected]#K! Reboot into download mode. All the ROMS I downloaded are ZIP format instead of TAR format. So this time my dumb self uses Odin to reflash the TAR file I used to root my phone. After this I realize "that TAR doesn't have a ROM attached to it."
So now I can only boot into download mode. Can't load CMW. Sadly I had to leave for work and I'm without my phone until I get home at midnight. I FEEL SO DISCONNECTED! ='(
Will a simple file conversion program be sufficient to convert ZIP to TAR so I can use ODIN to flash them later? Or will I have to follow the unbrick instructions to return to stock and then start over? And after reading about that one version of Siyah bricking phones I think I'm going to leave the NEAK kernal that comes with AOKP.
Thanks for your assistance!
No, you can't build a tar from a zip.
I don't and have never used aokp or cm9 or miui, but in my experience, when you start getting massive force closes, and if a fix permissions in recovery doesn't fix it, then you're best off starting over from scratch. If you have a working nandroid backup, use that. Otherwise, flash back to stock, wipe data/factory reset, and reinstall your rom from scratch.
There are plenty of tar and one-click downloaders available. See links in my signature.
I found this on the i9100 forums, instructive. Instead of installing a stock samsung firmware and kernel, just download a rooted package (maybe go back to Gingerbread for i777) then go from there.
http://forum.xda-developers.com/showthread.php?t=1457458
I'm interested to know how this recovery works for you, keep us posted! Best luck!
Any idea what would randomly cause the issue of mass force closures so I can prevent this from occuring again?
Did you do a Full Wipe when you first installed AOKP? I have ran into issues before with Rom Control by just wiping cache and dalvik and under the OP of AOKP Task even states coming from aokp or cm9 you Should be good but more likely than not, I would do a complete wipe *Factory Reset under CWM*. And when you restore your data with TiBu just restore missing apps and their data. Do not restore system data as that will be a major cause of mass FC... So first things first, I would use Odin to go back to UCKH7 *hopefully with CWM and Root* and than go back to Aokp since in my opinion is the best rom for our phones now.
HTH,
Charlie
dmnall said:
Did you do a Full Wipe when you first installed AOKP? I have ran into issues before with Rom Control by just wiping cache and dalvik and under the OP of AOKP Task even states coming from aokp or cm9 you Should be good but more likely than not, I would do a complete wipe *Factory Reset under CWM*. And when you restore your data with TiBu just restore missing apps and their data. Do not restore system data as that will be a major cause of mass FC... So first things first, I would use Odin to go back to UCKH7 *hopefully with CWM and Root* and than go back to Aokp since in my opinion is the best rom for our phones now.
HTH,
Charlie
Click to expand...
Click to collapse
I didn't do a factory wipe. I'm thinking I'll just do a factory wipe for any new rom installs. It's a little more work but if it helps prevent this sort of error I'll do it. And after reading about the bricking with that one version of Siyah I'm going to wait a couple weeks before any new installs to make sure other people have tested it first.
creepyncrawly said:
No, you can't build a tar from a zip.
I don't and have never used aokp or cm9 or miui, but in my experience, when you start getting massive force closes, and if a fix permissions in recovery doesn't fix it, then you're best off starting over from scratch. If you have a working nandroid backup, use that. Otherwise, flash back to stock, wipe data/factory reset, and reinstall your rom from scratch.
There are plenty of tar and one-click downloaders available. See links in my signature.
Click to expand...
Click to collapse
Well the first attempt didnt work using kernel + rooted UCKH7. Odin did everything it was supposed to but the phone locks at the initial Galaxy S II I-9100 ! screen. =(
Second attempt using I777_UCKH7_OCD_Root_No_BL and I'm able to get past the Galaxy S II I-9100 screen and the original AT&T boot animation shows but after the boot animation it just continuously reboots. ='(
Third attempt I tried Kernel + cache + rooted UCKK6 and after the reboot it actually rebooted into recovery mode. I thought that was a good sign so I reboot the phone normally and same issue as above. I try to reboot into recovery mode (Vol + - and pwr) again but it doesn't come up now. ='(
Forth attempt I tried Kernel + cache + rooted UCKK6 again. It reboots into recovery mode and I select the Factory Wipe option and reboot. There's a long delay after the AT&T boot animation and finally my phone starts up as if it was stock.
What a freakin nightmare! I was so worried my phone was a goner. None of the other ROMs I tried gave the option of booting into recovery mode which would have saved me so much time. Only the stock one did. The factory wipe was the key. So I'm definitely saving that file for safe keeping.
Thank you all for your suggestions and assistance. It's much appreciated.
This entire thread could have been avoided. By wiping completely. What is a complete wipe? Well, its the /system , /cache, /data, and /dalvik partition. Each of which are easily wiped in cwm in under 30 seconds. Flashing the kernel cleaning script doesn't hurt. Keep in mind these are your phones people it wouldn't hurt to do some research.
Sent from my SGH-I777 using Tapatalk 2
Hey guys!!!
New galaxy S2 owner. I have done some searching in these forums and the threads answered many of my questions. However, I still have some newbie questions that I found unanswered. Please excuse me if my questions have been answered before but I got tired of searching
Here is the deal:
Yesterday, I flashed a CF Root with Odin3. Then used CWM to flash a wanamlite firmware. The firmware was great but I didn't like that it still had TW. So I dl'ed another firmware to the internal SD card and flashed again using CWM. I then flashed a couple of other ROMS and I noticed that after the first wanamlite flash, the new ROMs were unstable with many error messages that some OS processes have stopped etc.
I got back home, flashed to stock with Odin3 and the phone got stuck at the second samsung logo. I followed some community steps (thanks XDA) like disabling all kies processes from TM, wiping data/cache, then boot in DL mode and flash the stock ROM using Odin3 which worked.
I then Flashed a CF Root again and used CWM to flash a Spike Pure ICS ROM v5 which was great but I get occasional error messages like 'gallery stopped' or some other error message when I try to set contact photos. It just lags, blackscreen then comes back with the 'Unfortunately, the process had stopped'.
My questions: is this because of the previously flashed firmware that this is happening or is it that those ICS ROMs have these issues commonly? Did anyone have this experience before? What do you advice before flashing to a new ROM going back to stock or going straight from the current? Doesn't Odin3 technically wipe everything back to stock?
WIPE WIPE WIPE.
Go into recovery. Data/factory reset.
Advanced, Wipe dalvic cache. Mounts and storage, format system. Its a standard procedure going from one OS to another OS. You can then either flash a firmware zip from recovery or an .tar file from Odin.
Then to be on the safe side factory reset once again.
Sent from my GT-I9100 using Tapatalk 2
Wich fw do you have?
Make a deep clean with odin an flash on the latest ics version (lp9 is a good one)..then flash (if you want) a custom rom..
My experience with custom roms: one of the best rom samsung based (ics 4.0.3) is the foxhound greyfox v2..if you want a pure ics rom flash the omega aokp rom (ics 4.0.4)..
Try then to change kernel..siyah is the best for both roms..
P.s. sorry for my bad english
Sent from my GT-I9100 using Tapatalk 2
After LP7 should be staple enough for daily use .However you are using custom roms and you should read carefully each roms thread before flashing .
You are probably suffering from flashing multiple roms and leaving bits behind as well = clean wipe .
jje.
Can someone give me a clear full wipe procedure? I always wiped data/factory rest/wiuped chaceh and dalvik... but what else? a step by step procedure would be helpful!!
I currently have Spike Pure ICS v 5.
What do you mean by Odin3 'deep clean'?
OJ77 said:
Can someone give me a clear full wipe procedure? I always wiped data/factory rest/wiuped chaceh and dalvik... but what else? a step by step procedure would be helpful!!
Click to expand...
Click to collapse
Read my last post..
Sent from my GT-I9100 using Tapatalk 2
so:
1. Recovery mode > format user data > wipe cache > clear dalvik > format system (from moutns and storage)
2. Download mode > flash stock ROM using odin 3
Did I get it right? Was there something i didn't wipe?
Before you flash a new rom, make sure you answer the requirements.Some ICS roms need to be flashed in specific way.
The way of doing a full wipe is you go in Clockwork mode, wipe data/factory reset, you wipe cache partition, then go to advanced wipe Dalvik and Battery stats, then go in mounts and storage ( i think ) and you wipe the cache from there, but nothing else in mounts and storage.If you wipe anything else there's a high percent of bricking your phone.If this doesnt help you, I doubt that anyone could give you any clearer instructions.
Good luck.
DONT FORMAT SYSTEM.
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Followed by root and custom rom if you so wish .
jje
OK im confused now... do I format system directory in mounts and storage or no?
OJ77 said:
OK im confused now... do I format system directory in mounts and storage or no?
Click to expand...
Click to collapse
i always do personally.
I got tempted and formatted system/cache/data but now i cannot flash from my internal sd card.. I get errors and 'installation aborted' if i try to do it from CWM... does that mean formatting those 3 means Odin3 is the only way? Cus I'm not home and I don't have odin3 on me.... LOL!
OJ77 said:
I got tempted and formatted system/cache/data but now i cannot flash from my internal sd card..
Did you format sd card and totally wipe the lot = nothing on the phone .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
At this point you have no OS on the phone nor kernel rooted nor CWM .
Hence
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Click to expand...
Click to collapse
JJ, you really need to learn how to quote you know, makes your posts so confusing to read sometimes
skimminstones said:
JJ, you really need to learn how to quote you know, makes your posts so confusing to read sometimes
Click to expand...
Click to collapse
Agree must try better .
Habit from replying to emails i guess .
jje
Thanks...
I did a 'full wipe' by doing t his:
1. Boot into CWM: wipe data, wipe cache, wipe dalvik, wipe battery stats, wipe system/data/cache from mounts.
2. Reboot into DL mode, flash stock ROM using Odin3.
3. Repeat step 1
4. flashed spike ICS v 7.3 using CWM. Stable so far.
Thank you!
imho: the most stable ics release is the stock official, but with some.battery issues, my suggestion: stay on gingerbread, find a custom kernel to suits your need,
GT-I9100, official 2.3.6, hardcore's Speedmod
budi.hermawan said:
imho: the most stable ics release is the stock official, but with some.battery issues, my suggestion: stay on gingerbread, find a custom kernel to suits your need,
GT-I9100, official 2.3.6, hardcore's Speedmod
Click to expand...
Click to collapse
I agree! I don't like ICS because is still unstable! My battery lasts very short with ICS and the phone overheats.
Moreover I hate the browser! I mean, The Galax S2 with GB still has the smoother browser of all the smartphones out there, and Samsung with ICS update messed it up! Now is laggy with micro stutters! Don't understand why!
OJ77 said:
The firmware was great but I didn't like that it still had TW.
Click to expand...
Click to collapse
You didn't need to go through all that trouble just because you didn't want TW (which I also hate, btw).
You could simply have installed another launcher (such as Go Launcher EX, ADW, etc) from Play Store and, since you were already rooted, uninstalled TW using Titanium Backup afterwards. It has to be in that sequence (install new then uninstall old).
this way you can have whatever ROM + kernel combination you like, and still use whatever launcher you prefer.
Hi.
Met a problem with my GT-I9300. When I shut the phone off it just reboots. The phone was rooted and running a custom rom when this started. Now I have unrooted with mobile Odin and flashed a official firmware but the problem persists.
I have even tried a battery pull. When battery is inserted again the phone remains off til I push the powerbutton. But when I try to turn it off after this it just reboots again.
Anyone else had this? Tips on what to do?
I've never had any luck fixing this problem. I always had to wipe and flash. However, as a temporary fix, you can power off from recovery.
Sent from my GT-I9300 using Tapatalk
can I ask what you are doing when you turn it off?
Sent from the asylum
Just to clarify, even wipe the phone and restore it to stock completely by flashing official firmware doesnt solve it.
When I turn it off I hold powerbutton til i get the powermenu. From there I choose "turn off". Phone does what it should, screen goes off and everything, only a few seconds later the phone boots again.
basse10000 said:
Just to clarify, even wipe the phone and restore it to stock completely by flashing official firmware doesnt solve it.
When I turn it off I hold powerbutton til i get the powermenu. From there I choose "turn off". Phone does what it should, screen goes off and everything, only a few seconds later the phone boots again.
Click to expand...
Click to collapse
If the phone was totally cleaned formatted sd card and stock firmware installed then its a hardware problem .
But my guess is it as not totally clean .
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
jje
I have now tried to wipe and format sys/data/cach/sd in cwm. Flashed stock firmware via odin. Still same issue. Guess its hardware.
Thanks anyway.
This may sound strange, but is this the clock problem the Desire HD had.
In time settings, uncheck the auto update.
Change time & date to something random.
Power off and pull the battery before it reboots.
Give it a min, power up, reselect auto update and reboot.
Should be good to go. If its the same problem that is.
Sent from the App that Time Forgot.
It also happens to me yesterday, I wipe cache, system, data, reinstall roms (CM and AOKP) and is still happening
r0uzic said:
It also happens to me yesterday, I wipe cache, system, data, reinstall roms (CM and AOKP) and is still happening
Click to expand...
Click to collapse
It happened also to me once. I flashed my rom in the same order as you did. But what my problem solved was, I made a wipe AFTER I installed the ROM. After that, I didn't had this issue anymore.
These are the steps I did...
- Get into the CWM recovery
- Wipe Data/factory reset
- Wipe Cache
- Wipe Dalvik-Cache
Hope it works also to you...
Solved
I solved it by flashing a later official firmware - XXALF6.
Darkrider82 said:
It happened also to me once. I flashed my rom in the same order as you did. But what my problem solved was, I made a wipe AFTER I installed the ROM. After that, I didn't had this issue anymore.
These are the steps I did...
- Get into the CWM recovery
- Wipe Data/factory reset
- Wipe Cache
- Wipe Dalvik-Cache
Hope it works also to you...
Click to expand...
Click to collapse
basse10000 said:
I solved it by flashing a later official firmware - XXALF6.
Click to expand...
Click to collapse
Thanks, I'll try twice methods
Update: It's rare, but has returned to work normal and I doing nothing
Hello,
i found a solution for that problem. You will lose some sd card files.
go to settings-storage-others (or other) and mark all files. Then delete them an go to downloadmode to reflash you firmware. Reboot and the problem is missing.