Related
Hi guys.
My phone is a international i9300
I've been searching for a problem like mine in the forum for three weeks now and I couldn't find a proper solution.
I just can't flash any rom via CWM anymore...
I can flash roms via ODIN, but when it comes to CWM, it gets stucked at Samsung logo after the install.
I tried:
Wipe cache / Dalvik / factory reset.
before the installation, after the installation, every combination possible.
Tried megawipe and no help.
Changed the kernel, Siyah, Googy, stock...
Changed versions of CWM, touch.
I have now the Phil'z 5.0.15.
I like very much the XXELK4 version from roalex with its MOD, for the call recording and full multiwindow support, but can't flash it anymore, nor any other custom or stock via CWM.
By now I can only have a full stock flashed via odin, or my Omega 46.1, wich I have a full backup.
Another solution could be find a .tar rooted and with the MODS flashable via Odin, but I really wanted to understand what's happening with my recovery.
Thank you all and congrats for the great work with the forum.
In cwm format..
Data
System
Cache
Then go to advanced and wipe dalvik cache
Then flash the rom.
Your cwm is upto date?
andrewwright said:
In cwm format..
Data
System
Cache
Then go to advanced and wipe dalvik cache
Then flash the rom.
Your cwm is upto date?
Click to expand...
Click to collapse
Sorry.
Forgot to include in the original post... I tried that too. Formatted everything
Got the 6.0.6.3
I also tried with the last Philz recovery.
And with previous versions of both too.
Have you tried to go bk to stock,root that firmware then install cwm then flash custom rom? Clean slate start.
Your problem may be a bad file download .
andrewwright said:
Have you tried to go bk to stock,root that firmware then install cwm then flash custom rom? Clean slate start.
Click to expand...
Click to collapse
Yes... didn't work...
JJEgan said:
Your problem may be a bad file download .
Click to expand...
Click to collapse
I'll try to download again, although it's not likely that several files are bad. I tried with so many different roms...
I bought another micro sd of 64gb. Maybe the one I'm using is ruining the files...
There can't be a so huge bug in philz recovery
Try install from internal sdcard, a simple 'Factory Reset before New Rom' no need to mega wipe anything.
Striatum_bdr said:
There can't be a so huge bug in philz recovery
Try install from internal sdcard, a simple 'Factory Reset before New Rom' no need to mega wipe anything.
Click to expand...
Click to collapse
Of course. And I tried with different versions of Philz' and also CWM. It can't be a bug in recovery.
Re-downloaded the revolution 29.0 and the Roalex XXELK4 rooted, copyed directly to internal and flashed... Same problem. Stuck at Samsung logo in boot. I'm begining to think my phone is screwed up. But this is so strange. I can restore my backup with no problems, and also can flash with Odin.
Is there a way to flash a .ZIP ROM in Odin?
Does not make any sense .
What model phone do you have ???
What model firmware are you flashing .
What about basic stock custom roms flashed via CWM ??
Have you booted to Philz recovery mounts and storage format sd card cache system and data then flash rom ??
Agree it is strange Deviating a little from your problem but have you tried flashing anything with TWRP recovery see if the problem persists with that.
JJEgan said:
Does not make any sense .
What model phone do you have ???
What model firmware are you flashing .
What about basic stock custom roms flashed via CWM ??
Have you booted to Philz recovery mounts and storage format sd card cache system and data then flash rom ??
Click to expand...
Click to collapse
I know it doesn't. That's why I'm going crazy.
I uploaded the screenshots with my system specs.
The model is correct, international i9300. Tried to download from the site and also directly from rommanager.
The firmwares I'm trying to flash are stock, but rooted by Roalex. I couldn't find a pure stock .zip for testing with CWM. The firmware I'm using is UBEMH5 from sammobile, wich I flashed via Odin.
Yes... Tried and formatted everything, several times, mounted, unmounted, every possible order...
Almost giving up. :crying:
tallman43 said:
Agree it is strange Deviating a little from your problem but have you tried flashing anything with TWRP recovery see if the problem persists with that.
Click to expand...
Click to collapse
I never used TWRP. Can I flash the same ROM file .zip with it or it requires it's own rom file type?
I'm gonna be out of the country for two days. When I come back I'll give it a try.
Thank you all so far.
ivansaab said:
I never used TWRP. Can I flash the same ROM file .zip with it or it requires it's own rom file type?
I'm gonna be out of the country for two days. When I come back I'll give it a try.
Thank you all so far.
Click to expand...
Click to collapse
It's been a while since i used it last time was when I had a S2 and I used it all the time:good: You can flash any rom with it that cwm can flash (as far as I know) but it had a little trouble restoring backups made with cwm but I think that got fixed.But you can make backups and loads of other things with it I recommend people to try it at least once This won't fix your cwm problem but would be interesting to see if it works
If twrp doesn't work on stock Flash googy Max dualboot kernel and keep stock as primary rom and custom as second rom. Then you have best of both world's :thumbup: also take the pic down with your emei showing :banghead: never ever show this!
What i would do in this situation is .
In recovery format cache system sd card preload .
Flash stock rom via Odin.
Check phone works ok .
Then root / flash philz recovery .
Put custom rom on sd card boot to recovery factory reset .
Then install custom rom watching setup to spot a failure point .
Wait for rom to load 10 mins fails then remove batter replace and factory reset .
Problem solved
Hi folks.
Think I figured out what's going on.
Via TWRP it says the files were corrupted, although the file sizes were identical.
I MD5 checked the files in my computer and they're ok, but when checked already inside my phone or SD they're not.
Instead of copying the files via USB cable I removed the SD card and inserted directly in my laptop slot and copyed the files. MD5 checked and they're ok...
After I tryed again copy via USB and the files were corrupted again.
I think my desktop USB or maybe the Samsung drivers are doing that.
Well, problem solved. I hope this helps other people in future problems.
Thank you all for your help and support. Keep on with the great work.
Mark solved then for other users .
Hi, all!
I have that annoying problem with all the 4.3 ROM I've tried with no exception. Everything is fine until the first reboot. Then it's stuck on the first Galaxy SIII boot logo. I'm using TWRP - the latest version if it matters.
I always wipe everything first.
Please give more details on how you flash it.
Enviado do meu GT-I9305 utilizando o Tapatalk now Free
nikolav75 said:
Hi, all!
I have that annoying problem with all the 4.3 ROM I've tried with no exception. Everything is fine until the first reboot. Then it's stuck on the first Galaxy SIII boot logo. I'm using TWRP - the latest version if it matters.
I always wipe everything first.
Click to expand...
Click to collapse
!!ALL QUESTIONS GO IN THE Q&A FORUM!! OR THEY MAY BE DELETED!!
nikolav75 said:
Hi, all!
I have that annoying problem with all the 4.3 ROM I've tried with no exception. Everything is fine until the first reboot. Then it's stuck on the first Galaxy SIII boot logo. I'm using TWRP - the latest version if it matters.
I always wipe everything first.
Click to expand...
Click to collapse
If you did all required wipes and followed the instructions did you try a different recovery? I read in the SB thread for example of people having issues with TWRP
Sent from my Nexus 7 (2013)
I am sorry for the wrong section. May I ask some to move it to Q&A?
I always wipe data, cash, dalvik cash, system. Then install the ROM and gapps...
After the restart I set up the google account and etc. And after the first restart the phone freezes. That's all.
I'll try with different recovery.
PS. I've just tried CWM recovery 6.0.3.3. and Omega AOSP v9. Still the same.
Try cwm 6.0.3.6 and after you install the rom and after its set up go to recovery and factory reset
nikolav75 said:
I am sorry for the wrong section. May I ask some to move it to Q&A?
I always wipe data, cash, dalvik cash, system. Then install the ROM and gapps...
After the restart I set up the google account and etc. And after the first restart the phone freezes. That's all.
I'll try with different recovery.
PS. I've just tried CWM recovery 6.0.3.3. and Omega AOSP v9. Still the same.
Click to expand...
Click to collapse
That's strange, I run Philz recovery and every 4.3 flash till now went through without issue.
Sent from my GT-I9300 using xda app-developers app
I tried all the recoveries I could find. Including Philz. Still the same.
And something else strange. I installed CWM, CWM, touch and Philz and with them I made backups. After restoration of the backup the phone freezes. I also tried to install Omega 49 and the installation goes OK, but freezes before the first start-up.
The only solution was to install manually TWRP (Odin) to restore some of my old backups. I'm beginning to think that there is something wrong with my phone. It's black if it is important.
Suggest total wipe of phone install your stock rom and test
Hi,
I just want to say I'm also having the same problem.
Started using TWRP with full wipe, same issue on 4.3 and no issues on 4.2.
On latest CWM same problem and 4.2 wont even pass the first boot on Samsung logo.
Also had to use Odin to get back on TWRP and flash a 4.2 rom again.
Anyway there is one more thing I would like to try but haven't had the chance to do so, is installing the latest modem and ril. But I'm kind skeptic about that currently because there is also some risks and my S3 is my daily driver.
Don't change the ril on any custom as you stand a big chance of breaking the calls and Tex's. Modem yes but not ril. Do change to cwm and retry.
andrewwright said:
Don't change the ril on any custom as you stand a big chance of breaking the calls and Tex's. Modem yes but not ril. Do change to cwm and retry.
Click to expand...
Click to collapse
Thanks for the info, I was planning to read more about it before I would make an attempt. BTW already tried CWM that only made things worse, couldn't flash any rom without getting stuck on samsung screen.
bla166 said:
Thanks for the info, I was planning to read more about it before I would make an attempt. BTW already tried CWM that only made things worse, couldn't flash any rom without getting stuck on samsung screen.
Click to expand...
Click to collapse
You are doing a full wipe?. System and data is the main thing to wipe not just factory reset. So go into mounts and storage and format data,system and cache there then flash the rom /gapps.
andrewwright said:
You are doing a full wipe?. System and data is the main thing to wipe not just factory reset. So go into mounts and storage and format data,system and cache there then flash the rom /gapps.
Click to expand...
Click to collapse
yes tried that, also used the mega wipe zip thing
Start fresh and flash stock with Odin then try again after you root and install cwm.
andrewwright said:
Start fresh and flash stock with Odin then try again after you root and install cwm.
Click to expand...
Click to collapse
Tried to go stock and flashed a 4.3 rom again that fixed my problem. =)
Thanks! :good:
I'll try it too. And one stupid question. Where do I find a stock ROM? I never did it before
nikolav75 said:
I'll try it too. And one stupid question. Where do I find a stock ROM? I never did it before
Click to expand...
Click to collapse
http://www.sammobile.com/
Thank you!
But nothing helped. I flashed a stock ROM, with Odin. First I tried with TWRP, and the second time (again after flashing stock) with CWM recovery. I tried two 4.3 ROMs. They both can't boot after the first reboot.
nikolav75 said:
Thank you!
But nothing helped. I flashed a stock ROM, with Odin. First I tried with TWRP, and the second time (again after flashing stock) with CWM recovery. I tried two 4.3 ROMs. They both can't boot after the first reboot.
Click to expand...
Click to collapse
Hi, I think I did the following steps to get it working on my device.
1. Flash stock with odin
2. Hard reset
3. Boot up and finish first run menus
4. Flash twrp with odin
5. Format data with twrp
6. Flash 4.3 rom
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
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")
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.