Related
Hi.
I have not yet noticed anyone with similar problem, so i will appreciate any useful answer.
I would love to have Illusion Rom http://forum.xda-developers.com/showthread.php?t=1403044 on my SG S2. Everyone says it's a great ROM and sure looks great to. But here's my problem. After flashing and rebooting, phone is stuck at boot screen (some kind moving blue aurora keeps replaying).
I rooted my phone correctly, I saved ROM file in SD card, then I flashed it (like it says in instalation manual) in recovery mode. Everything goes great until reboot. Phone seems to stuck at boot screen.
Supposedly sometimes doubble flash might help, so i tried doing that too. Same issue.
Problem accures only with this rom.
Thanks for any help.
Full wipe and try again.. mine works like a charm.. let me know if still got issues
As squidkhaw says above, you need to do a full wipe as it doesnt say you did in your post above.
Wipe data, cache, and dalvik, then flash rom. Also next time make sure to create a nandroid backup before you wipe or flash anything.
Ok then. What about things like titanium backup?: its not getting activated when u have a root access..
Try to instal super su and check titanium backup whether its ask permission or not.
Sent from my GT-I9100 using XDA
Alright So I am new to this forum but Im not new to the scene. I cant figure this problem out after days of searching and restoring. So I just got my note last week been loving it coming from my old 4s. Anyways My problem is I did a fresh factory restore rooted with dags kernel (tried both stock root and Oc kernel). I have clockwork recovery installed btw. So usually everything goes smooth. I clear all caches phone boots up runs smooth, I install root then my basic apps. Now I was doing them one by one and restarting.
Well long story short. At random any one of these times I reboot the device I come back into the lock screen Ill unlock and it force closes everything and just keeps rerunning media scanner looping. (force close twlauncher calenders google sync etc like really anything usually its twlauncher thats first I click ok it goes back to lock screen freezes for a second then reboots media scanner. It doesnt find service or even attempt it. The only thing I can do is restore and try again. I have done this over 10 times just this past week. I have fixed permissions in both rom manager and clockwork. Though it was good until last night it just completely restarted on its own and when I booted back up it was force closing.
I even did a fresh format wiped everything reinstalled stock att unrooted Rom then rooted and I have to be afraid of my phone dying or just randomly crashing and that when I restart its not gonna make it back into gingerbread without a restore. Now this will happen whether I have no apps or some apps. I can seem to find anything triggering it. Is this a defect in the phone maybe? Should I restore to stock and exchange at at&t or am I missing something? Please help guys. Ive only been able to get about a day before everything force closes. And that is unacceptable for an 700 dollar phone when all these others are running smooth.
Did you happen to mess with any overclock values? I had the problem you explain only after I overclocked to much and it was unstable
Solution: put into download mode and flash back to total stock with odin and start over. It worked for me. Restoring backup did not work
Sent from my SGH-I717R using Tapatalk
It is a problem with CWM. You should look for and download darkside super wipe. If I were you I would probably flash the stock Odin tar and start fresh. Make sure you install the latest CWM.. I believe beta4. You should not have to reboot your phone after every new app install.
Use the super wipe from in CWM (install from zip) and then use Odin to get back to stock.
You most likely have an older version of the CWM, I don't think anyone has reported any problems with beta 4 and force closing issues.
I have CWM 5.0.2.7 on here. I dont have to restart everytime I install. I was doing it to see if there was a certain app triggering it thats all. Cuz if the phone goes off and reboots to lockscreen thats when the FC happens. It never happens while Im actually in use. First time this happened it was stock clock speed and its happened whether its 1.83 or 1.56 or stock rooted rom. And I had tried both restarting stock att rom with bloat and from my first backup after odin root.
Where do i find beta 4? I originally got this cwm from rootgalaxynote.com
Nevermind I found it I pulled a n00b. Ok Imma give that a try right now I see this is older version so HOPEFULLY thats it. Thanks a bunch Ill check back in after to let you know. Pretty crazy in the back of my mind I felt like CWM was the only thing I didnt check out.
Stuck in firmware upgrade encountered an issue. I cant do anything Odin wont write the stock firmware back on after wipe. What do I do? No cwm or anything phone just boots to telling me to restore with kies?
h3r3tic said:
I have CWM 5.0.2.7 on here. I dont have to restart everytime I install. I was doing it to see if there was a certain app triggering it thats all. Cuz if the phone goes off and reboots to lockscreen thats when the FC happens. It never happens while Im actually in use. First time this happened it was stock clock speed and its happened whether its 1.83 or 1.56 or stock rooted rom. And I had tried both restarting stock att rom with bloat and from my first backup after odin root.
Where do i find beta 4? I originally got this cwm from rootgalaxynote.com
Nevermind I found it I pulled a n00b. Ok Imma give that a try right now I see this is older version so HOPEFULLY thats it. Thanks a bunch Ill check back in after to let you know. Pretty crazy in the back of my mind I felt like CWM was the only thing I didnt check out.
Click to expand...
Click to collapse
The version of CWM you were using was most likely for the international Note and therefore incompatible with the Note you have.
---------- Post added at 09:03 PM ---------- Previous post was at 09:00 PM ----------
h3r3tic said:
Stuck in firmware upgrade encountered an issue. I cant do anything Odin wont write the stock firmware back on after wipe. What do I do? No cwm or anything phone just boots to telling me to restore with kies?
Click to expand...
Click to collapse
You may want to join the IRC channel and see if anyone there can offer you a solution.
irc.irondust.net
#attgalaxynote
Just for Clarification
I too had the TwLauncher issue and tried clearing the Dalvik cache, cache, etc. This then sent me into a boot loop into recovery. (My CWM is the 5.0...version too). Tried the restore, no luck, wipe, no luck etc.
My PC doesn't see the phone, so I need to basically start the root process over again and install the Beta4 CWM. Am I understanding correctly?
I have the same problem and its driving me crazy. Can some one please help me out step by step Im new to this any help would be gratefully appreciated
Hi all,
Had my SGS3 for a few weeks now and it's been good for the most part, but as of a few days ago things started to go wrong.
Had a message from Orange saying that i've been using my phone out of the EU and i've used 2MB (even though i haven't) this issue hasn't raised it's head again, i also had four apps install themselves, "slots", "cab app", "droid apps" and "new message", i've since wiped and had no issues.
Then this morning i had an icon show up saying car mode enabled, click here to disable, theres nothing i can do to remove it besides reboot the phone and then it promptly comes back again
The other one is since installing villain rom, which has been a solid rom and the dev's there are top notch so i don't even think it's the rom, but i've been getting a strange error too.
Also getting rebooting of the phone randomly also happens and again theres nothing i can do about that either.
I've attached screengrabs of both the car mode issue after i click on the notification and the error i'm getting when using villainrom.
Any help at all with any of these issues would be great.
Many thanks.
PS: Things i've tried:
Rebooting.
Full wipe, data, cache and dalvic.
Re downloaded the rom and full wiped again.
Cleared the internal and external memory.
Tried different kernels
The car mode issue was also present on Omega rom and i imagine it would follow me onto any other rom, i'm actually suspecting that it's some malware which has been left behind and has installed itself, so even after wiping it's just installing itself again.
I don't use apk's too much but i do use titanium after every flash although i am careful as to what i install.
Might i need to go back to stock and start over?
Thanks.
~EDIT: Just used the toolkit to go back to a stock rom and i'm still receiving errors "Unfortunately the process android.process.acore has stopped ?? wtf? It's supposed to be clean?
Anyone?
EDIT 2: Re rooted the phone and everything went perfect, flashed a custom rom and still good, then signed into google and as it was loading up my numbers and changing my wallpaper, attempting to download my apps, it crashes, i reboot and as soon as it's connected and trying to finish off what it was doing, it reboots again? This lump of **** is going back.
Baad.
Bump.
Yeah.bump. don't know what is causing this. But try this
Full wipe, go to mount/storage and format system, then flash new rom
Do have full access to all your apps,if not then your phone is on "safe mode/car mode" and i never use that feature, so i don't know how to turn it off.
Hope this can help
dladz said:
Bump.
Click to expand...
Click to collapse
Maybe if you "tick-off" the sync_with_google option before finishing the first time gmail setup??
And you could try Settings --> Back up and reset --> and untick Automatic Restore??
Good luck
zodiaxe66 said:
Yeah.bump. don't know what is causing this. But try this
Full wipe, go to mount/storage and format system, then flash new rom
Do have full access to all your apps,if not then your phone is on "safe mode/car mode" and i never use that feature, so i don't know how to turn it off.
Hope this can help
Click to expand...
Click to collapse
Completely unrooted, flashed a stock rom, still having issues.
Called orange, getting a new phone tomorrow, courier to my door Now that's service.
Don't know how to fix the issue but i had 6 reboots on the train on the way to work, couldnt' even send a text.
System was clean, i'd already wiped anything that could be wiped.
Hardware issue.
QuaQuaRaQuaQua said:
Maybe if you "tick-off" the sync_with_google option before finishing the first time gmail setup??
And you could try Settings --> Back up and reset --> and untick Automatic Restore??
Good luck
Click to expand...
Click to collapse
Sign in or don't sign in, the problem persists.
Car mode has stayed away but the reboots are still present, for a 20 day old phone i think it's utter bull****.
Must have been tested by a bunch of corpses, either that or the testers were high and thought it'd be funny to send out some dud unit's.
Even in my place of work, i sometimes set up client's phones, up til now i've done hundreds, about 10 of them have been dead from the box, some have had issues with the touchscreen, lalalalallalalaaaaaa, not good enough samsung, i understand that some bad eggs can slip through the net but for me the ratio is just too high.
Like i said, i'll be getting a spanking new phone delivered tomorrow morning, hopefully this one isn't on it's arse.
zodiaxe66 said:
Yeah.bump. don't know what is causing this. But try this
Full wipe, go to mount/storage and format system, then flash new rom
Do have full access to all your apps,if not then your phone is on "safe mode/car mode" and i never use that feature, so i don't know how to turn it off.
Hope this can help
Click to expand...
Click to collapse
If this issue is happening to you, send it back, mine went from being on it's knees to being on it's back in a coffin in one day.
I would suggest you do a full wipe as suggested and try to use a different GMAIL account initially to see if your issues return.
burmo said:
I would suggest you do a full wipe as suggested and try to use a different GMAIL account initially to see if your issues return.
Click to expand...
Click to collapse
M8, i HAVE done a full wipe, i've also signed in AND not signed in as i've previously said.
Both yielded the same results.
....................................
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 for your phone .
Still problems Triangle Away to set rom counter to zero flash stock rom .
Return to service centre .
jje
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 for your phone .
WHoa
-------------------------------------------------------------------------------------------
I'm not sure what your addressing here?
Balls'ed up the firmware? Not likely sunshine, not me
NO i think you'll find that this ***** has hardware issues, at least since it still reboots at stock.
Either way if someone does want to go back to stock then there is only one place they need to go to.
There is no script or anything else needed for it.
Just the tool kit.
Congrats, u neither helped me nor, did anything else, u just gave some unwanted info. Kudos i think????
-------------------------------------------------------------------------------------------------------------------------------------------
I DO NOT UNDERSTAND THE POINT OF YOUR POST, AT ALLLLLL.]
/I'm not sure what your thanks meter represents??
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....
Hello everyone, I hope I'm posting in the good section.
I usually can find solutions to my problems by searching and reading, but this time, I can't, and I have a huge problem.
As the title says, every new application that I install since a few days ago will crash when I try to use it. When I do, the phone will hang for a few seconds, then a message saying "unfortunately, <appname> has stopped", with two choices given: OK and report.
Every other app that was installed before still works. I uninstalled an app that worked and reinstalled it, it doesn't work anymore.
I have a galaxy S3 i9300, with jelly bean 4.1.1 (official rom from my carrier SFR), rooted with SuperSU through exynos abuse.
I don't know exactly when the problem actually happened (realized by trying to install and run new apps), but here is what I did before realizing the problem and that may be the source:
I tried to replace the android.policy.jar file to activate long press volume buttons to change songs. Didn't work, put the original back in place (with total commander).
I tried to installed Xposed after that to activate it, but it crashed too, so I uninstalled it.
Now that I think about it, it may have been with the same error message, but I can't say for sure. I dismissed it, thinking it was not compatible with JB and forgot it.
I uninstalled AdService through the task manager, and reinstalled it after realizing the problem, by using the apk backuped by rootuninstaller. But I can't force stop it from the task manager, so I guess it's not even running.
I also softbricked (stuck on boot logo) it by installing Chainfire3D on JB (I know, stupid of me. I did read the description though, but missed the "doesn't work on JB" somehow). I was able to unbrick it by using "adb -d shell su -c "/system/lib/cf3d_uninstall.sh"" (would that command work if the phone is not rooted by the way? I'd guess yes but I'm not sure) from my computer while the phone was in recovery mode (thanks to a user of this forum for the tip), but it was before all that and I'm sure I installed apps after that that would work.
Now when an app crash, the report is always the same:
Exception class name: java.lang.ClassNotFoundException
Source file: BaseDexClassLoader.java
Source class: dalvik.system.BaseDexClassLoader
Source method: findClass
Line number: 61
The stacktrace is also always the same, and is basically what's above.
I fear that I may have lost some system files (even though I don't remember modifying any beside android.policy.jar nor granting root access to apps that would. I didn't tinker a lot with my phone).
The strange thing though is that old apps still works, which leads me to think that maybe it is thanks to the dalvik cache and odex files that I read about (but don't know much) but that newly installed apps don't have.
I'd really appreciate any kind of help. Otherwise I guess I'll have to reset to factory settings, but I'd like to avoid that if I can.
Thanks in advance.
You're not, General is not for questions. Q&A is
Glebun said:
You're not, General is not for questions. Q&A is
Click to expand...
Click to collapse
Aw, such a fail... So would a kind moderator move the thread there or should I repost it and let this one drown to the abyss of this section?
If no one else comes up with any answers, I'd say that your best option would be to wipe everything and install a stock ROM again. That should sort it out.
DeadSOL said:
If no one else comes up with any answers, I'd say that your best option would be to wipe everything and install a stock ROM again. That should sort it out.
Click to expand...
Click to collapse
That's what I'm thinking about, but I have a question about that: would the reset to factory option from the recovery menu work? I see a lot of people advising to flash a stock rom, is there a difference between both (I do not have CWM)?
And is there a difference between "factory settings" and "store settings"? I mean, if I reset it to factory, will I have my phone in the same state I did when I bought it (with my carriers modifications and apps) or not?
hey01 said:
Aw, such a fail... So would a kind moderator move the thread there or should I repost it and let this one drown to the abyss of this section?
Click to expand...
Click to collapse
You ask via the report button on your post .
Wipe phone factory reset .
jje
hey01 said:
That's what I'm thinking about, but I have a question about that: would the reset to factory option from the recovery menu work? I see a lot of people advising to flash a stock rom, is there a difference between both (I do not have CWM)?
And is there a difference between "factory settings" and "store settings"? I mean, if I reset it to factory, will I have my phone in the same state I did when I bought it (with my carriers modifications and apps) or not?
Click to expand...
Click to collapse
Yes, I always factory reset via Recovery. This will give you a clean ROM with no extra apps installed.
Buuuuuut you need to repair your ROM since you messed with it. Just flash a stock ROM and you're good to go!
DeadSOL said:
Yes, I always factory reset via Recovery. This will give you a clean ROM with no extra apps installed.
Buuuuuut you need to repair your ROM since you messed with it. Just flash a stock ROM and you're good to go!
Click to expand...
Click to collapse
Ok, so I seemed to have mistaken a few things, I thought the factory reset did reinstall the rom, but apparently it just wipes user data and settings. And it also seems that flashing a new rom doesn't erase everything, such as CWM or similar things, right? So I wonder if it would solve my problem or not.
Also, I just realized, when in recovery mode, I have the classic 6 options in blue at the top, but then in the middle, I have this in yellow:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : SFR
Successfully applied multi-CSC.
And in the background, the android robot lies open with a red warning sign above.
The typo in "Applying Multi-CSC" and the warning sign make me think that this is not as it should be and there is a problem.
Would flashing also solve that problem, if it is one?
I'm sorry for the noob questions, but even though I'm reading a lot of guides and tutorials, I'm still quite confused.
The problem got worse: I did the wipe data/factory reset, and things got worse: when booting, I get dozens of "application stopped". Literally all of them, it's hard to even turn off the phone (need to press ok on all the popup to reach the shutdown button).
So I then tried to flash my phone, but problem again. I followed this guide exactly, but when I press start, Odin 3.04 hangs for a bit and crashes, be it on a windows XP or 7. It writes:
"checking md5... do not unplug the cable
please wait"
and crashes
I then tried to download another version, 3.07, but when I put the firmware in Odin, it does the md5 check at that moment and crashes again, on both computers, so it seems the problem isn't even related to the phone.
My phone is totally unusable now if I can't flash it, I'd really need some help.
hey01 said:
Ok, so I seemed to have mistaken a few things, I thought the factory reset did reinstall the rom, but apparently it just wipes user data and settings.
WRONG it reinstall the rom .
And it also seems that flashing a new rom doesn't erase everything, such as CWM or similar things, right?
Correct unless its a wipe rom .
The problem got worse: I did the wipe data/factory reset, and things got worse: when booting, I get dozens of "application stopped". Literally all of them, it's hard to even turn off the phone (need to press ok on all the popup to reach the shutdown button).
Sounds like the firmware stored in recovery is damaged .
Download a stock rom and flash via Odin and report failure point if it does not work .
jje
Click to expand...
Click to collapse
JJEgan said:
hey01 said:
Ok, so I seemed to have mistaken a few things, I thought the factory reset did reinstall the rom, but apparently it just wipes user data and settings.
WRONG it reinstall the rom .
And it also seems that flashing a new rom doesn't erase everything, such as CWM or similar things, right?
Correct unless its a wipe rom .
The problem got worse: I did the wipe data/factory reset, and things got worse: when booting, I get dozens of "application stopped". Literally all of them, it's hard to even turn off the phone (need to press ok on all the popup to reach the shutdown button).
Sounds like the firmware stored in recovery is damaged .
Download a stock rom and flash via Odin and report failure point if it does not work .
jje
Click to expand...
Click to collapse
Ok, I downloaded another rom from another forum, specific from my carrier, and Odin didn't crash. I flashed my phone, and it's working again. Only thing still worrying is that warning sign over the open android robot if I boot in recovery mode. It is still there and I can't find anywhere what it means.
Click to expand...
Click to collapse
Update, if any case someone has the same problem and ends here:
I tried once again to activate that long press, replace the .jar with another, it didn't work (I guess it does only on deodexed ones). Replaced the new jar by the original one, and the crashing new apps problem arised again.
Being less panicked than last time, I realized the permissions changed. The android.policy.jar should be rw-r--r--, as every other file there, but they were rw-------. So yes, bound to make problems.
So adb -d shell su -c "mount -o remount rw /system"
and then used total commander to change the permissions back to original. Rebooted, it works.