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
Related
Hi Everyone,
I keep getting a boot-loop after installing ANY custom ROM. I factory wipe, clear cache and dalvik cache, THEN i install the zip and gapps, then I factotry wipe, clear cache and dalvik cache AGAIN. It loads the boot screen, whether its CM10 or ParanoidAndroid, and then at the "welcome" screen, it reboots after 2 seconds. It just keeps looping.....any ideas?
try formatting system before flashing
just format system or cache and data as well? and do I do that before I wipe or after i wipe everything?
format system/data/cache, then flash
ok, I only did system and cache, and it still is rebooting constantly, i'll try it with formatting data.
which Rom are you trying to install?
slaphead20 said:
which Rom are you trying to install?
Click to expand...
Click to collapse
Paranoid Android.
Wrong gapps version??
I tried doing it without gapps, I'm still getting a restart after everytime I get the lock screen on EVERY ROM i try to install....don't know what the problem is with my phone, it's happening with EVERY ROM. Is it because my baseband/firmware stuff isn't uniform?
Product Code: GT-I9300RWD(INU) (India i think)
PDA: I9300XXBLH1
Phone: I9300XXLFB
CSC: I9300ODDBLG2
Download the ROM AGAIN and this time download the OLDER version and keep your eyes on the download especially you are downloading from chrome. sometimes the problem is in the downloaded rom its self. and than make a factory Reset and then install the rom and than factory reset again than reboot the phone. Hope it works. I just did it yesterday. I also had boot loop. I tried to restore backup, install the newer ROM nothing worked. than I tried that and it worked....
what do you mean download again and download the older version? I've tried every combination of factory reset/wipe/dalvik cache/reset/install/reset/cache/dalvik, etc....
melemed said:
what do you mean download again and download the older version? I've tried every combination of factory reset/wipe/dalvik cache/reset/install/reset/cache/dalvik, etc....
Click to expand...
Click to collapse
Download the ROM from internet again. this time try the older version of the ROM that you want to install.
EXAMPLE: I wanted to install Omega v26.1 and I went to boot loop. I tried everything to flash the newer version, I also tried to restore the nandroid backup. nothing worked. so I downloaded Omega V13 and than I did factory reset than I installed omega v13. Worked like charm.
I hope it will work for you too...
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
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.
Hi;
So i recently installed CyanogenMod 13.0 on to my Samsung S4 GT-I9505 using the first download link on:
https://download.cyanogenmod.org/?device=jfltexx --> cm-13.0-20160102-NIGHTLY-jfltexx.zip
That all installed fine, but i wanted to get the Google apps installed aswell, which is where i am having some issues.
I have been trying to install the following package:
http://opengapps.org/?api=6.0&variant=nano
but have also tried to install quite a few others as well, and all have exactly the same issue. Basically after the apps have been installed and i boot the device up, i get various error messages like:
unfortunately, Setup Wizard has stopped
unfortunately, google play services has stopped
Any help on fixing this would be much appreciated, as nothing seems to download from the play store thats included in Cyanogen, they just say "your download will begin shortly" but never does.
Thanks in advance
I am a total noob, but I had exactly this problem. The issue appears to be that you have to flash gapps *before* rebooting after flashing CM. In my case since I had already flashed CM before I flashed gapps I had to put the gapps file on the phone (I did this by push with adb, you might find an easier way), re-flash CM, wipe cache/dalvik, flash gapps, wipe cache/dalvik, reboot. It worked.
The easiest guide I found was on androiding.how, called "how to install cm13 (cyanogenmod13)." (The forum won't let me post a link, just google it, it should come up).
Hope that helps. I'm on a galaxy s5 and used twrp recovery if that matters.
audacityandrouge said:
I am a total noob, but I had exactly this problem. The issue appears to be that you have to flash gapps *before* rebooting after flashing CM. In my case since I had already flashed CM before I flashed gapps I had to put the gapps file on the phone (I did this by push with adb, you might find an easier way), re-flash CM, wipe cache/dalvik, flash gapps, wipe cache/dalvik, reboot. It worked.
The easiest guide I found was on androiding.how, called "how to install cm13 (cyanogenmod13)." (The forum won't let me post a link, just google it, it should come up).
Hope that helps. I'm on a galaxy s5 and used twrp recovery if that matters.
Click to expand...
Click to collapse
Thanks for the reply, i gave that a try and it seems to be stuck on a loop now with "installing app # of 22" . it completes the installation and then reboots, after about 5 minutes on the Cyanogen boot screen, it goes back to installing apps again.
Hm, did you do a factory reset in your recovery before re-flashing CM and gapps? If not, that might be necessary.
audacityandrouge said:
Hm, did you do a factory reset in your recovery before re-flashing CM and gapps? If not, that might be necessary.
Click to expand...
Click to collapse
Yeah, i did. Tried it multiple times now
That's about the limit of my ability right there, hopefully someone with more experience than me can point you in the right direction. Good luck.
Boot to recovery (preferably TWRP)
Wipe cache / dalvik cache / data / system
Flash CM13 and the gapps you were trying first
Reboot
Profit!
Since you keep flashing different gapps on top of the system, this is probably causing some issues. Once you fully wipe and reflash everything, it should work.
es0tericcha0s said:
Boot to recovery (preferably TWRP)
Wipe cache / dalvik cache / data / system
Flash CM13 and the gapps you were trying first
Reboot
Profit!
Since you keep flashing different gapps on top of the system, this is probably causing some issues. Once you fully wipe and reflash everything, it should work.
Click to expand...
Click to collapse
Ive tried that multiple times using twrp (i always wipe everything before i flash CM13 and gapps), i still get the exact same issue. The second the phone boots, i get all these "unfortunately ******** has stopped".
Perhaps try installing 12.1 with gapps, get it all updated then upgrade to 13. I did the accidental upgrade to 13 but have had no issues whatsoever.