So I desperately need help here! Using a GT-i9300 here.
Been at this for like 7 hours or so.
Was running a 4.1.2 rom for quite a while, thought I'd bump it up to 4.4.2 today.
Was thinking about flashing Resurrection Remix rom, so did the usual downloaded the files but noticed somewhere you need a 4.2.2 or above rom already in use to be flashing a 4.4.2. So went to S4 revolution rom (4.2.2). Then decided to flash the 4.4.2 rom.
Did the usual, data wipe, cache wipe, dalvik cache wipe. Flashed the rom. Then Gapps.
Now here's the messed up part, after flashing the phone would boot to the Rom logo. And it hasn't moved since. Thought something was up, flashed it again, did the take battery out thing also.
Thought it would be a ROM problem, so flashed 2 other roms. Neat rom and Gummy rom. Same result.
The 4.2.2 rom is working btw. So any ideas?!
Please! Reallly want the 4.4.2
Thank you!
Prosilicus said:
So I desperately need help here! Using a GT-i9300 here.
Been at this for like 7 hours or so.
Was running a 4.1.2 rom for quite a while, thought I'd bump it up to 4.4.2 today.
Was thinking about flashing Resurrection Remix rom, so did the usual downloaded the files but noticed somewhere you need a 4.2.2 or above rom already in use to be flashing a 4.4.2. So went to S4 revolution rom (4.2.2). Then decided to flash the 4.4.2 rom.
Did the usual, data wipe, cache wipe, dalvik cache wipe. Flashed the rom. Then Gapps.
Now here's the messed up part, after flashing the phone would boot to the Rom logo. And it hasn't moved since. Thought something was up, flashed it again, did the take battery out thing also.
Thought it would be a ROM problem, so flashed 2 other roms. Neat rom and Gummy rom. Same result.
The 4.2.2 rom is working btw. So any ideas?!
Please! Reallly want the 4.4.2
Thank you!
Click to expand...
Click to collapse
Please read the RR thread again. You need a full wipe for it to work. Try a 4.3-based Rom like Omega and then search XDA on how to do a FULL wipe. Then proceed with RR.
~ RazorMC
RazorMC said:
Please read the RR thread again. You need a full wipe for it to work. Try a 4.3-based Rom like Omega and then search XDA on how to do a FULL wipe. Then proceed with RR.
~ RazorMC
Click to expand...
Click to collapse
Thanks for the reply. But could you please elaborate on how to do a full wipe? Kind of a newbie to all this. Thanks!
Prosilicus said:
Thanks for the reply. But could you please elaborate on how to do a full wipe? Kind of a newbie to all this. Thanks!
Click to expand...
Click to collapse
Sorry, I've forgotten the link to the method. Maybe someone else can also shed light on this matter.
But if I remember:
- Wipe Cache,
- Wipe dalvik,
- format /system,
- format /data,
- format /cache.
- Then install the Rom.zip.
PS: Don't do "format /data and /data/media" section or it will delete everything on the internal SD. If you do this, make sure you have an external SD with a ROM placed in it (don't wipe this too) otherwise you will end up in a very difficult situation like i did
~ RazorMC
RazorMC said:
Sorry, I've forgotten the link to the method. Maybe someone else can also shed light on this matter.
But if I remember:
- Wipe Cache,
- Wipe dalvik,
- format /system,
- format /data,
- format /cache.
- Then install the Rom.zip.
PS: Don't do "format /data and /data/media" section or it will delete everything on the internal SD. If you do this, make sure you have an external SD with a ROM placed in it (don't wipe this too) otherwise you will end up in a very difficult situation like i did
~ RazorMC
Click to expand...
Click to collapse
If I am not wrong, formatting data will not erase the root directory. Where u put the rom zip. But just have an ext sd card just for safety.
Sent from my GT-I9300 using xda app-developers app
JellyYogurt said:
If I am not wrong, formatting data will not erase the root directory. Where u put the rom zip. But just have an ext sd card just for safety.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
You're right. "format /data" does not erase the root directoy. But I found "format /data and /data/media and /sdcard" option deleted everything on my S3 and even adb sideload failed for me after selecting it. After that I had to reflash stock via Odin.
+1 to ext SD
~ RazorMC
Usually I would just flash the mega wipe zip to get the device clean (only leaves ext. sd) and then start reflashing from scratch. I find it easier than doing it manually in recovery.
@RazorMC @JellyYogurt
Hey! Sorry got a bit busy but just got around to what you all recommened today and it's still no use.
Did everything this time.
First, I tried flashing the RR rom with the full wipe as you said. Oh and I'm using CWM 6.0.4.7
- Moved the zip file to ext SD
- wipe data
- wipe cache
-wipe dalvik cache
- format /system,
- format /data,
- format /cache.
During this got a status 6 error with the RR rom and I had put a Gummy Rom (4.4.2) just in case so tried the same process with this also but got a status 7 error with this one.
Left both, downloaded CM 11. Did the same process while on the 4.2.2 rom with it. This got stuck on the boot screen. Like the CM logo was going around for 30 minutes.
Finally when I couldnt tolerate it, removed battery, moved to 4.2.2 again and downloaded a 4.3 rom. Again, CM.
You wouldnt believe this but this also didnt work! This got stuck on the same thing. CM logo is still flashing around. Been watching this for 20 minutes now.
So, you guys got any ideas? Really pissing off.
Btw, thanks for the previous replies )
Oh and btw, would it matter if I didnt flash gapps after flashing the rom?
Those are just for the Google services and not related to whether the rom is booting up to home screen right?
Prosilicus said:
Oh and btw, would it matter if I didnt flash gapps after flashing the rom?
Those are just for the Google services and not related to whether the rom is booting up to home screen right?
Click to expand...
Click to collapse
Try other recoveries to see if problem still there try latest PhilZ recovery (this as a setting for wiping and installing new roms)..if that does not work try twrp recovery..
No you don't have to flash gapps after flashing you can do that later..
Prosilicus said:
@RazorMC @JellyYogurt
Hey! Sorry got a bit busy but just got around to what you all recommened today and it's still no use.
Did everything this time.
First, I tried flashing the RR rom with the full wipe as you said. Oh and I'm using CWM 6.0.4.7
- Moved the zip file to ext SD
- wipe data
- wipe cache
-wipe dalvik cache
- format /system,
- format /data,
- format /cache.
During this got a status 6 error with the RR rom and I had put a Gummy Rom (4.4.2) just in case so tried the same process with this also but got a status 7 error with this one.
Left both, downloaded CM 11. Did the same process while on the 4.2.2 rom with it. This got stuck on the boot screen. Like the CM logo was going around for 30 minutes.
Finally when I couldnt tolerate it, removed battery, moved to 4.2.2 again and downloaded a 4.3 rom. Again, CM.
You wouldnt believe this but this also didnt work! This got stuck on the same thing. CM logo is still flashing around. Been watching this for 20 minutes now.
So, you guys got any ideas? Really pissing off.
Btw, thanks for the previous replies )
Click to expand...
Click to collapse
Try a stock-based 4.3 like omega rom after flashing stock 4.1.2
Use Philz Recovery like tallman43 said. I prefer that over others.
If it doesn't work then maybe there's some compatibility issues.
~ RazorMC
Related
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.
tetakpatak said:
Please quote my post and copy&paste whole text into some help thread for your phone, it is better idea as we are now getting off topic here. I'll try to help you there.
Format /system is done in recovery mode under "mount and storage" then after that you can restore your nandroid if it is done with the same recovery you use now. If you're on PhilZ 6, it usually can restore also CWM 6 backups.
Click to expand...
Click to collapse
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Click to expand...
Click to collapse
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
tetakpatak said:
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
Click to expand...
Click to collapse
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it? .
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it?
Click to expand...
Click to collapse
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
tetakpatak said:
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
Click to expand...
Click to collapse
Thanks for helping, but I ended up downloading the stock rom and flashing it. Everything was normal. Then I installed cm10.2 so everything's great now. Thanks!
Sent from my Nexus 4 using xda app-developers app
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
tetakpatak said:
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
Click to expand...
Click to collapse
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Sent from my Nexus 4 using xda app-developers app
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
keithross39 said:
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
Click to expand...
Click to collapse
6.0.4.5 is compatible? I think so ......
Sent from my Nexus 4 using xda app-developers app
I've always read....not.....
In any case, probably best not to risk it......
6.0.4.7 is DEFINITELY KK compatible.... and it'd take a couple of seconds to flash.........
Sent from my Infected KitKat bar.....
AndroidReborn said:
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Click to expand...
Click to collapse
Yes, mate, CWM 6.0.4.5 is capable of flashing KitKat.
It is usually always the same:
download your ROM zip and compatible Gapps
check in the phone (or PC) if the zips are corrupted through download (if they open after clicking them, they are fine)
move the zips to the folder you will flash it from (if you use PC to flash zips with ADB sideload, put them in the sdk/platform-tools folder)
make nandroid backup of your presently used ROM
wipe data/factory reset
wipe cache
wipe dalvik cache (advanced)
format /system (under mount and storage)
flash ROM.zip
flash Gapps
reboot
It is in general always good to read in the development thread of the ROM you attend to flash in the opening post which Gapps are recommended, or if there is some unusual order of flashing (sometimes, developers recommend reboot system after flashing ROM, and after that going to recovery and flash Gapps zip.
Some KitKat ROMs struggle with root access by using Superuser, so SuperSU should be flashed. If SuperSU app from Play Store gives errors by updating binary, you should uninstall SuperSU app then, find in the Chainfire's thread the compatible UPDATE-SuperSu.zip (version for your phone), flash its zip in the recovery, install SuperSU app, update binary (either "normal" or "through CWM/TWRP")
HI.
I've changed roms before countless times, but now I'm trying to install a 4.4.2 rom on my Galaxy S3, and I have some problems. The installation (flash) passes with no problems, but after that, the phone won't boot. It sticks on whatever the rom's boot animation is. I've tried to wipe data, cache, wipe dalvik after this but it's still not working. Before I flash every rom, I do a factory reset, wipe the dalvik cache, and format system. I've tried with 15+ 4.4.X roms, and these are some of them: CyanogenMod, OmniROM, SlimKat, AOKP, Pacman and so on. As I said, I've flashed roms before a lot of times, without any problem. Only 4.4+ roms wont work. I tried to change the recovery, still the same result. I flash gapps with every rom too. Any idea what can be causing the problem? I'm using the latest Clockwork recovery, Sorry for my bad english and thanks.
divoom12 said:
HI.
I've changed roms before countless times, but now I'm trying to install a 4.4.2 rom on my Galaxy S3, and I have some problems. The installation (flash) passes with no problems, but after that, the phone won't boot. It sticks on whatever the rom's boot animation is. I've tried to wipe data, cache, wipe dalvik after this but it's still not working. Before I flash every rom, I do a factory reset, wipe the dalvik cache, and format system. I've tried with 15+ 4.4.X roms, and these are some of them: CyanogenMod, OmniROM, SlimKat, AOKP, Pacman and so on. As I said, I've flashed roms before a lot of times, without any problem. Only 4.4+ roms wont work. I tried to change the recovery, still the same result. I flash gapps with every rom too. Any idea what can be causing the problem? I'm using the latest Clockwork recovery, Sorry for my bad english and thanks.
Click to expand...
Click to collapse
Format data and system and cache (full wipe) also intstall the rom then boot it then flash gapps after see if that helps.
tallman43 said:
Format data and system and cache (full wipe) also intstall the rom then boot it then flash gapps after see if that helps.
Click to expand...
Click to collapse
I've already done that every time. As I said - Its not my first time flashing roms on my device. I know how to fix the general errors. This is something unusual tho.
Hey
When it bootloops, have you tried to goto recovery and see what us the cwm version??
Also try re-flashing the ROM without wipes..
Sent from my GT-I9300 using xda app-developers app
I just flashed EHNDROIX V (based on CynogenMod 4.4.2 KitKat) last night and it worked just fine.
Rooted the device with Odin, install TWRP from playstore, install TWRP recovery from TWRP, clean dalvik, clean data, clean cache, flash ROM and then flash Gapps (spesific Gapps for the ROM) and voila it worked right away.
Note:
You see, I am not using CWM but TWRP. I dunno if CWM is the one causing the problem.
Most of the weird flashing issues are due to the recovery used, you could also try the latest version of Philz recovery which has an option to wipe for new firmware.
Sent from my GT-I9300 using Tapatalk
divoom12 said:
I've already done that every time. As I said - Its not my first time flashing roms on my device. I know how to fix the general errors. This is something unusual tho.
Click to expand...
Click to collapse
Quote " Before I flash every rom, I do a factory reset, wipe the dalvik cache, and format system" You said nothing about formatting data that is why i suggested it! Next time please include all details on how you flashed the rom then It cuts down on useless post's like mine
Like everybody suggested try a different recovery ( latest one) which if you have flashed roms many times before you should have done anyway
Thanks guys, but I've already tried these things. CWM, TWRP and three other recoveries (not famous ones) haven't been able to help.
divoom12 said:
Thanks guys, but I've already tried these things. CWM, TWRP and three other recoveries (not famous ones) haven't been able to help.
Click to expand...
Click to collapse
If a rom is stuck in a loop, I would go to recovery and wipe dalvik and wipe data then reboot into same rom. This has worked for me when I've been stuck after a flash.
~ RazorMC
RazorMC said:
If a rom is stuck in a loop, I would go to recovery and wipe dalvik and wipe data then reboot into same rom. This has worked for me when I've been stuck after a flash.
~ RazorMC
Click to expand...
Click to collapse
I said that I've already done that in my First post.
divoom12 said:
HI.
I've changed roms before countless times, but now I'm trying to install a 4.4.2 rom on my Galaxy S3, and I have some problems. The installation (flash) passes with no problems, but after that, the phone won't boot. It sticks on whatever the rom's boot animation is. I've tried to wipe data, cache, wipe dalvik after this but it's still not working. Before I flash every rom, I do a factory reset, wipe the dalvik cache, and format system. I've tried with 15+ 4.4.X roms, and these are some of them: CyanogenMod, OmniROM, SlimKat, AOKP, Pacman and so on. As I said, I've flashed roms before a lot of times, without any problem. Only 4.4+ roms wont work. I tried to change the recovery, still the same result. I flash gapps with every rom too. Any idea what can be causing the problem? I'm using the latest Clockwork recovery, Sorry for my bad english and thanks.
Click to expand...
Click to collapse
Did you update your bootloader? When I flashed 4.4.2 from 4.4.1 on my s3, I had to update mine to get it to work. http://forum.xda-developers.com/showthread.php?t=2321310 hope this helps.
Sent from my unknown using XDA Premium 4 mobile app
I searched the internet and threads on XDA for this problem but couldn't really find one!
The problem is- My Galaxy S3 (GT-I9300) doesn't boot any AOSP/AOKP/CM ROMs! It's just the bootanimation and DONE! For hours and hours the bootanimation only! But I can flash any Sammy 4.3 / 4.4 ROMs! They boot! They work properly!
I used to change to AOSP to Sammy and vice versa so many times with no issues. One day I downloaded the UltimaAOSP Valhalla ROM and flashed it. This was the first time my S3 didn't boot. I flashed custom Kernels like boeffla on it but all in vain. It was stuck on the bootanimation. I flashed NeatROM AOSP on top of it, which worked properly. Then it was with the fusion sp ROM that it didn't boot again. Again I flashed NeatROM AOSP on top of it (it's my favorite ROM), which I used just to copy some other ROM from my PC to my phone.
Now, I'm on my Stock ROM which came with my phone since so long! I'm shocked to see now NO AOSP ROMs are booting! I've used C-ROM, NeatROM, Resurrection Remix and SOKP Milestone. I have the ROMs' ZIP files and also a Nandroid Backup which I made when I changed to other ROMs. Not the ZIP files neither the Nandroid Backups are helping! ZIP files get flashed succesfully (I wipe the data & cache & dalvik-cache every time) and the Nandroid Backups get restored successfully! But always the phone gets stuck on the bootanimation!
I always moved to AOSP from Sammy (never Sammy to Sammy) but this time I gave it a shot.
Result : All the Samsung ROMs are flashing, working properly, even the Nandroid restores boot. I flashed my newly downloaded FlashingDroid Sammy 4.4 ROM which also works.
BUT I CAN'T GET THE AOSP ROMs onto my phone!
My thought (it could be wrong) : Is it to do something with the data in a partition other than system, data, and cache? Some partition which has stored files needed to boot Sammy ROMs and is preventing AOSP ROMs to start?
HELP!
:crying:
MORE UPDATED INFO ON POST #6
::ROBLEM SOLVED:::
Wipe system, data, cache and preload partitions manually in mounts and storage in CWM Recovery.
DONE! AOSP Working!
Suggests something is being left behind that aosp objects to. Try the rescue firmware in general forum, wipe internal sd and preload.
boomboomer said:
Suggests something is being left behind that aosp objects to. Try the rescue firmware in general forum, wipe internal sd and preload.
Click to expand...
Click to collapse
Have lots of data on my internal memory! Still I deleted lots of unwanted files. Any other way to wipe the hidden preload partition other than using Philz Recovery? I remember I flashed Philz after which I couldn't restore any of my Nandroid Backups backed up with CWM Recovery..
Sent from my GT-I9300 using XDA Premium 4 mobile app
In cwm mounts and storage wipe preload
Press thanx if i helped you in anyway...
Update - Got More Info
Update : Just noticed that when it's the bootanimation on the screen after flashing an AOSP ROM, pressing any of the buttons on the phone vibrates the phone vigorously 2 times.. why??
Also, I want to ask about the connection between a kernel and a bootanimation without starting a new thread 'cause I think it's the solution to my problem here.. The data which I probably suspect that prevents AOSP ROMs from booting is some different bootanimation file? I mean when I'm on a Sammy ROM, I started to flash different bootanimations after flashing some CWM Custom Bootanimation ZIP file. The bootanimation changes on all Kernels on Sammy ROMs -except 1 that is the boeffla kernel. The strange thing is that the first custom bootanimation I had flashed (after flashing Boeffla's Sammy Kernel) when I switched to Sammy from my last AOSP was the hTC One Bootanimation which worked fine (the bootanimation successfully changed). After that, it never changed. My phone always booted up showing the hTC One Bootanimation no matter how many times I flashed another bootanimation ZIP or the CWM ZIPs which enable/disable Custom bootanimations. But! When I changed to any other kernel (the stock that came with the ROM/GoogyMax 2/AGNi), the bootanimation was the last one flashed by me before changing the kernel. I could change the bootanimations successfuly every time after that. Now, I flashed Android Revolution HD ROM and was on Stock Kernel. As soon as I changed to boeffla kernel (without flashing any other ZIP), the bootanimation changed! (automatically!) And it was again the same old hTC One Bootanimation.
Can someone please tell me WHERE is this bootanimation data and the data that prevents AOSP ROMs to boot is stored? Certainly not in the data or system or cache partition...
Update 2 : Just figured out where the automatic htc bootanimation magic happened. The hTC bootanimation.zip file was found in data/local . However, I always knew the bootanimation directory as system/media.. So now, is it safe for me to delete all files in data/local 'cause it seems it is the problem for AOSP ROMs?
Sent from my GT-I9300 using XDA Premium 4 mobile app
the main thing i can think of is your trying to go back to jb roms which you cant do as far as i know try flashing kitkat based roms
jimbobpro87 said:
the main thing i can think of is your trying to go back to jb roms which you cant do as far as i know try flashing kitkat based roms
Click to expand...
Click to collapse
I'm not trying to go back to Jelly Bean! I'm flashing AOSP based ROMs of KitKat 4.4.2 which don't boot!
SOLVED!
Yayy!
I guess I got a solution!
Wiped system, data, cache and preload partitions manually in mounts and storage in my CWM Recovery.
DONE! AOSP Working!
:victory:
THANKS TO ALL WHO HELPED! :angel:
Thank you for your post.
I am having the same problem, phone not booting past boot animations using aosp ROMs. Haven't tried Sammy ROM to test the theory yet but will try soon.
How do you wipe preload? In mounts and storage, I get an error when trying to mount or format preload using CWM 6.0.4.7
I don't see an option to wipe anything other than data, cache, or dalvic.
alaska_ryder said:
How do you wipe preload? In mounts and storage, I get an error when trying to mount or format preload using CWM 6.0.4.7
I don't see an option to wipe anything other than data, cache, or dalvic.
Click to expand...
Click to collapse
Strange- it happened that day but not now. Even I get an error formatting preload. But! I guess the problem is the system partition! There IS an option to format /system in mounts and storage option on the first screen.
Sent from my GT-I9300 using XDA Premium 4 mobile app
This is really an old post i think.
But, can someone answer me please, ive been searching for This maybe for more than a year. Can someone please help me? @Paresh Kalinani
I have the exact same issue.
My device: Grand Prime (G530FXXU1AOJI baseband)
Stock android: 5.0.2
Recovery: TWRP 3.1.0.0
I have booted many Samsung roms and also ported many of them like J5's 5.1.1 , On7's 5.1.1 rom and many other 5.1.1 and 5.0.2 roms and all of them work perfectly. But when it comes to AOSP ROMS each of them keeps loading at the booting animation screen. Ive tried many roms like RR, AOSP Extended, Cyanogenmod, LINEAGEOS, All of these 5.1.1 , 7.1.1.
It booted for others with the exact Same variant as mine too.
Please help me?
Id been really grateful.
Thanks,
Eden532
Eden532 said:
This is really an old post i think.
But, can someone answer me please, ive been searching for This maybe for more than a year. Can someone please help me? @Paresh Kalinani
I have the exact same issue.
My device: Grand Prime (G530FXXU1AOJI baseband)
Stock android: 5.0.2
Recovery: TWRP 3.1.0.0
I have booted many Samsung roms and also ported many of them like J5's 5.1.1 , On7's 5.1.1 rom and many other 5.1.1 and 5.0.2 roms and all of them work perfectly. But when it comes to AOSP ROMS each of them keeps loading at the booting animation screen. Ive tried many roms like RR, AOSP Extended, Cyanogenmod, LINEAGEOS, All of these 5.1.1 , 7.1.1.
It booted for others with the exact Same variant as mine too.
Please help me?
Id been really grateful.
Thanks,
Eden532
Click to expand...
Click to collapse
Have you flashed the rom then factory reset?
Beamed in by telepathy.
shivadow said:
Have you flashed the rom then factory reset?
Beamed in by telepathy.
Click to expand...
Click to collapse
Nope.
I wiped system, data, cache and dalvik cache the flashed the rom and the rebooted?
Do I have to do a factory reset then?
Thanks a lot for the immediate response.
Eden532 said:
Nope.
I wiped system, data, cache and dalvik cache the flashed the rom and the rebooted?
Do I have to do a factory reset then?
Thanks a lot for the immediate response.
Click to expand...
Click to collapse
Well, what you did was butter than a factory reset.
Factory reset means wiping data, cache and dalvik cache.
I would like you to do something first, try downloading the latest stock firmware for your phone from sammobile, and then flash it with Odin, then try flash AOSP roms again, maybe you have an old bootloader.
MigoMujahid said:
Well, what you did was butter than a factory reset.
Factory reset means wiping data, cache and dalvik cache.
I would like you to do something first, try downloading the latest stock firmware for your phone from sammobile, and then flash it with Odin, then try flash AOSP roms again, maybe you have an old bootloader.
Click to expand...
Click to collapse
Im running the latest firmware which id flashed through odin.
AOSP roms still not booting.
I had wiped those partitions before i flashed the rom. I did not wipe after i flashed them.
Eden532 said:
Im running the latest firmware which id flashed through odin.
AOSP roms still not booting.
I had wiped those partitions before i flashed the rom. I did not wipe after i flashed them.
Click to expand...
Click to collapse
Are you sure it's the latest one?
Did you check Sammobile.com?
The latest one was released in 1st Feb 2017.
Also please check the IMEI of your phone by typing *#06#, because if you've a problem with efs partition you may not be able to flash any AOSP Rom (happened to a friend before..he had sim working without IMEI!!)
Also what is your country code?
As stated above, check your imei is still OK then from a working stock state:
Root it.
Flash custom recovery.
Flash the custom rom twice and then wipe data/cache. Do not wipe system!.
If that doesn't work then try the above but instead of wipe data/cache do a factory reset.
Beamed in by telepathy.
MigoMujahid said:
Are you sure it's the latest one?
Did you check Sammobile.com?
The latest one was released in 1st Feb 2017.
Also please check the IMEI of your phone by typing *#06#, because if you've a problem with efs partition you may not be able to flash any AOSP Rom (happened to a friend before..he had sim working without IMEI!!)
Also what is your country code?
Click to expand...
Click to collapse
My country code is XSG but ill try flashing the THL latest version and again report.
I was trying to check my IMEI number it shows UNKNOWN APPLICATION but sim and other modem related stuff works really fine.
Is it something to do with this?
shivadow said:
As stated above, check your imei is still OK then from a working stock state:
Root it.
Flash custom recovery.
Flash the custom rom twice and then wipe data/cache. Do not wipe system!.
If that doesn't work then try the above but instead of wipe data/cache do a factory reset.
Beamed in by telepathy.
Click to expand...
Click to collapse
I did flash the custom rom twice but still no good.
(And also i checked the IMEI via a custom Sammy rom)
Eden532 said:
My country code is XSG but ill try flashing the THL latest version and again report.
I was trying to check my IMEI number it shows UNKNOWN APPLICATION but sim and other modem related stuff works really fine.
Is it something to do with this?
Click to expand...
Click to collapse
This is the latest firmware for United Arab Emirates:
https://androidfilehost.com/?fid=385035244224412750
Flash it and see if the problem solved :good:
MigoMujahid said:
This is the latest firmware for United Arab Emirates:
https://androidfilehost.com/?fid=385035244224412750
Flash it and see if the problem solved :good:
Click to expand...
Click to collapse
Thank you so much for sending the link, Its really difficult to download from sammobile.com . Ill check it right away and report. Thanks.
Self-explanatory really.
I updated my phone a few weeks ago to Omnirom 4.4.4, one of the nightly builds and everything was going well.
Today I installed a couple of apps, and tonight the screen started flickering and the phone reset, however when it started again, it went into a bootloop.
How do I get it working again without losing the files that are on the internal memory? (I don't know which resets in CWM delete personal data)
Thanks
septimoose said:
Self-explanatory really.
I updated my phone a few weeks ago to Omnirom 4.4.4, one of the nightly builds and everything was going well.
Today I installed a couple of apps, and tonight the screen started flickering and the phone reset, however when it started again, it went into a bootloop.
How do I get it working again without losing the files that are on the internal memory? (I don't know which resets in CWM delete personal data)
Thanks
Click to expand...
Click to collapse
Flash latest (6.0.4.7) CWM or latest TWRP (2.7.1.0 if Im not wrong) and reflash the rom.
Wiping data, and formatting partitions doesnt get you wiped internal memory files; but apps and things installed.
NaminatoR1254jaime.sier said:
Flash latest (6.0.4.7) CWM or latest TWRP (2.7.1.0 if Im not wrong) and reflash the rom.
Wiping data, and formatting partitions doesnt get you wiped internal memory files; but apps and things installed.
Click to expand...
Click to collapse
I did this, and I'm still stuck in a bootloop, it gets as far as the "Omni" animation, and then reboots
Any advice?
septimoose said:
I did this, and I'm still stuck in a bootloop, it gets as far as the "Omni" animation, and then reboots
Any advice?
Click to expand...
Click to collapse
Flash stock ROM via Odin
verny94 said:
Flash stock ROM via Odin
Click to expand...
Click to collapse
I'm sorry for my ignorance, but would you happen to know of a guide for flashing the stock ROM?
Would it fix by flashing a different ROM, such as Cyanogenmod which I have in the download folder on the phone?
If like you said you don't want to lose data don't flash stock rom this will wipe your data fist thing you need to do is install PhilZ recovery then look here >> http://forum.xda-developers.com/galaxy-s3/orig-development/i93xx-philz-touch-t2002953 << then look at the special features section here >> http://forum.xda-developers.com/showthread.php?p=39433728#post39433728 << look for the aroma file manager and how to use.
You will then be able to boot into recovery browse your internal files with aroma and move and copy/backup what you need,once you have done all that you will then be able to return to stock with odin.
Edit
Guide for flashing stock rom here >> http://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125 <<
---------- Post added at 11:21 AM ---------- Previous post was at 11:10 AM ----------
septimoose said:
I'm sorry for my ignorance, but would you happen to know of a guide for flashing the stock ROM?
Would it fix by flashing a different ROM, such as Cyanogenmod which I have in the download folder on the phone?
Click to expand...
Click to collapse
If you don't want to lose your data then no because you need to wipe your data....Did you reboot into recovery and wipe cache advanced delvik cache? Also read my suggestions above