Related
Hi there, I need your help and advice please.
Here’s my problem. My phone is the SGS2 running KI3 rooted with CF-root KI3 flashed the secure kernel and then flashed the zImage so I still have root CWM and to get rid of the yellow triangle. I have downloaded CM nightly 88 to my laptop and transferred it to my S2 via usb cable into the download folder.
Here’s where the problem comes into play when I run CF’s CWM and choose reboot into recovery I do a wipe/factory reset / wipe cache and update via sdcard, I pick the cm88 from the download folder and it starts to update and then stops. I reboot and it’s stuck on the Samsung S2 page (boot loop). I then have to get into the recovery and restore my phone to the previous state. Can someone help me I would like to try the CM’s custom rom but don’t know what I’m doing wrong? Thanks.
i have the exact same problem!
InFa_ReD_1 said:
Hi there, I need your help and advice please.
Here’s my problem. My phone is the SGS2 running KI3 rooted with CF-root KI3 flashed the secure kernel and then flashed the zImage so I still have root CWM and to get rid of the yellow triangle. I have downloaded CM nightly 88 to my laptop and transferred it to my S2 via usb cable into the download folder.
Here’s where the problem comes into play when I run CF’s CWM and choose reboot into recovery I do a wipe/factory reset / wipe cache and update via sdcard, I pick the cm88 from the download folder and it starts to update and then stops. I reboot and it’s stuck on the Samsung S2 page (boot loop). I then have to get into the recovery and restore my phone to the previous state. Can someone help me I would like to try the CM’s custom rom but don’t know what I’m doing wrong? Thanks.
Click to expand...
Click to collapse
try download it again. Sound like a corrupted package
Sent from my GT-I9100 using Tapatalk
rembrandtlnx said:
try download it again. Sound like a corrupted package
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I tried and got the samething. I also tried a different cm nightly and got the same results.
InFa_ReD_1 said:
I tried and got the samething. I also tried a different cm nightly and got the same results.
Click to expand...
Click to collapse
me2 only stock roms work for me =(
I think there was an issue with the version of CWM used on the CF-roots since it's been modified by CF and because it's an older version.
After you've rooted with CF, try flashing a kernel on there with a newer version of CWM on there (I used codeworkx's kernel from the Cyanogenmod wiki I've attached below with CWM 4.0.1.4).
Once this kernel is on there, then try flashing the CM7 ROM as per this thread. I prefer flashing from recovery myself, but it's your call.
Make sure you flash it twice in a row if you're having issues.
The problem, as stated above is that cf root kernel installs a modified version of CWM that won't work with CM7. Another thing is you have to flash a stock KH3 because KI3 has the new bootloader (unless you flashed KI3 with the old bootloaders). Then, you have to flash the codeworkx kernel so you get a compatible version of CWM. Once in CWM clear data factory reset + clear cache partition + clear dalvik cache (from advanced).
THIS IS IMPORTANT: Flash the ROM from sd card and when finish do not reboot device, just flash it again without wiping anything in between, just 2 consecutives "install from sd card". When this is done you can reboot the system and then enter again to CWM to flash the google apps .zip file that you can download from the CM7 thread.
Hope this helped. When I flashed CM7 i had exactly the same problem and went back to stock cause it was a pain in the ass to flash it fr the first time. But once you get in CM7, everything becomes great and easy, and you can update the nighlies directly from ROM manager without doing any wiping. You just can't use ROM manager when getting to CM7 for the first time.
InFa_ReD_1 said:
Hi there, I need your help and advice please.
Here’s my problem. My phone is the SGS2 running KI3 rooted with CF-root KI3 flashed the secure kernel and then flashed the zImage so I still have root CWM and to get rid of the yellow triangle. I have downloaded CM nightly 88 to my laptop and transferred it to my S2 via usb cable into the download folder.
Here’s where the problem comes into play when I run CF’s CWM and choose reboot into recovery I do a wipe/factory reset / wipe cache and update via sdcard, I pick the cm88 from the download folder and it starts to update and then stops. I reboot and it’s stuck on the Samsung S2 page (boot loop). I then have to get into the recovery and restore my phone to the previous state. Can someone help me I would like to try the CM’s custom rom but don’t know what I’m doing wrong? Thanks.
Click to expand...
Click to collapse
DO NOT use cf-root to install CM7. It's stated by Codeworkx a lot of times in CM Q&A thread. Just flash his kernel to get cwm.
http://forum.xda-developers.com/showthread.php?t=1118693
Now you have the original cwm recovery (from Koush). Boot into recovery, Wipe data, cache, dalvik.
Install CM7 twice in a row without rebooting.
Then flash gapps (without rebooting) http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip.
Now reboot. Wait for a few mins since system has to build dalvik cache. And you're all good to go
Worried about yellow triangle? Get a usb jig.
Siyah kernel 2.0 supports CM7 and miui. So....have fun.....!!
droidphile said:
DO NOT use cf-root to install CM7. It's stated by Codeworkx a lot of times in CM Q&A thread. Just flash his kernel to get cwm.
http://forum.xda-developers.com/showthread.php?t=1118693
Now you have the original cwm recovery (from Koush). Boot into recovery, Wipe data, cache, dalvik.
Install CM7 twice in a row without rebooting.
Then flash gapps (without rebooting) http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip.
Now reboot. Wait for a few mins since system has to build dalvik cache. And you're all good to go
Worried about yellow triangle? Get a usb jig.
Siyah kernel 2.0 supports CM7 and miui. So....have fun.....!!
Click to expand...
Click to collapse
Thanks. Can i flash the orginal CWM over top the CF CWM?
InFa_ReD_1 said:
Thanks. Can i flash the orginal CWM over top the CF CWM?
Click to expand...
Click to collapse
I did it and didn't have any problems, just follow the steps as I posted above.
tomascunill said:
I did it and didn't have any problems, just follow the steps as I posted above.
Click to expand...
Click to collapse
Great thanks for the help it worked I'm now running CM7. One thing though I can make calls but have lost my network connection. Can someone help me with this? Sorry for all the questions I'm new to the whole smartphone business. Thanks.
Ok all fixed up thanks for all your help.
Hello, I hope this is the right group.
I have spent the last 2 days trying to get JB working on my SGS2. I previously had ICS Hydra h2o 1.4.1 ROM on my device.
The troubles started when I tried booting into CWM recovery. The phone wouldn't go past the yellow triangle so I had to use ODIN to flash stock Samsung ICS ROM on the phone to get it working again. I have since tried multiple JB ROMs with different kernels but most of them get past the yellow triangle but then stop on logos varying between kernels. I am also unable to boot into CWM recovery and must flash a CF-Root kernel using ODIN to get into recovery.
It is strange that this happens only with JB ROMs and I have no trouble installing Hydra h2o again through recovery.
I always use the same method of installing ROMs through CWM:
- wipe data/factory reset
- wipe cache
- wipe dalvik
- install .zip from sdcard
I have also tried fixing permissions before and after flashing ROMs, nothing seems to get me into the OS.
One ROM, Vanilla RootBox, I have found to sometimes boot all the way into the OS but the system frequently freezes and is unstable. Looks amazing tho.
Do you have any ideas on how I could get JB ROMs working with my SGS2? Is there anything I am missing?
SynGates said:
Hello, I hope this is the right group.
I have spent the last 2 days trying to get JB working on my SGS2. I previously had ICS Hydra h2o 1.4.1 ROM on my device.
The troubles started when I tried booting into CWM recovery. The phone wouldn't go past the yellow triangle so I had to use ODIN to flash stock Samsung ICS ROM on the phone to get it working again. I have since tried multiple JB ROMs with different kernels but most of them get past the yellow triangle but then stop on logos varying between kernels. I am also unable to boot into CWM recovery and must flash a CF-Root kernel using ODIN to get into recovery.
It is strange that this happens only with JB ROMs and I have no trouble installing Hydra h2o again through recovery.
I always use the same method of installing ROMs through CWM:
- wipe data/factory reset
- wipe cache
- wipe dalvik
- install .zip from sdcard
I have also tried fixing permissions before and after flashing ROMs, nothing seems to get me into the OS.
One ROM, Vanilla RootBox, I have found to sometimes boot all the way into the OS but the system frequently freezes and is unstable. Looks amazing tho.
Do you have any ideas on how I could get JB ROMs working with my SGS2? Is there anything I am missing?
Click to expand...
Click to collapse
Follow this:
-boot to CWM recovery
-wipe data /factory reset
-wipe dalvik cache (under advanced)
-format /system (under mount and storage)
-flash ROM
-flash Gapps (for jelly bean)
-fix permissions
-reboot phone
Done
Swyped from my Samsung Galaxy SII
Thank you for the reply, but that method does not seem to work either.
One thing I have noticed though is when I select wipe data/factory reset it reports an error formatting /sdcard/.android_secure.
Is this something that could be causing my problems?
SynGates said:
Thank you for the reply, but that method does not seem to work either.
One thing I have noticed though is when I select wipe data/factory reset it reports an error formatting /sdcard/.android_secure.
Is this something that could be causing my problems?
Click to expand...
Click to collapse
Nope
Swyped from my Samsung Galaxy SII
SynGates said:
Thank you for the reply, but that method does not seem to work either.
One thing I have noticed though is when I select wipe data/factory reset it reports an error formatting /sdcard/.android_secure.
Is this something that could be causing my problems?
Click to expand...
Click to collapse
which kernel u were into while flashing the JB rom?
Use siyah or dorimanx kernel it works fine for me must be your kernel
Sun90 said:
which kernel u were into while flashing the JB rom?
Click to expand...
Click to collapse
When I'm flashing I'm using XLPB kernel with CF-root. That's the kernel I flash to get into CWM when the ROMs misbehave.
SynGates said:
When I'm flashing I'm using XLPB kernel with CF-root. That's the kernel I flash to get into CWM when the ROMs misbehave.
Click to expand...
Click to collapse
try this.
after flashing Cf-root kernel from ODIN.
1) flash the .zip file of siyah kernel v3.5.2 for S2, dwnld the same Here.
2)after that reboot into siyah kernel recovery.
3) wipe data/factory reset, then wipe cache and dalvik.
4) flash the JB rom zip file(Vanilla root box).
5)reboot ur phone and see.
ps- before doing wipes and rom flash do please backup ur exsisting rom once ur into siyah kernel recovery first
Sun90 said:
try this.
after flashing Cf-root kernel from ODIN.
1) flash the .zip file of siyah kernel v3.5.2 for S2, dwnld the same Here.
2)after that reboot into siyah kernel recovery.
3) wipe data/factory reset, then wipe cache and dalvik.
4) flash the JB rom zip file(Vanilla root box).
5)reboot ur phone and see.
ps- before doing wipes and rom flash do please backup ur exsisting rom once ur into siyah kernel recovery first
Click to expand...
Click to collapse
Gives me Kernel panic or stops at the triangle loading screen. Seems the only way to get into CWM is through CF-root.
SynGates said:
Gives me Kernel panic or stops at the triangle loading screen. Seems the only way to get into CWM is through CF-root.
Click to expand...
Click to collapse
Use a newer version of siyah or dorimanx, they should work fine
Sent from my GT-I9100 using xda app-developers app
I have tried three versions of syiah, including 4.1.4 but I will try dorimanx and report with the results.
edit: dorimax kernel is the same.
One thing I noticed tough is whenever I wipe dalvik cache the system reports "unknown volume for /ext-sd blablabla" - maybe this is connected to my problem?
I am at a complete stop...
No JB kernels seem to work whatsoever. Is there any wit to flash the bootloader? Or is that even possible?
I really would like to get JB working on my device.
There must be something about the previous state of my phone, some files or folders that are in the way or are missing or somewhat. Is there any way to completely reset the phone? Not just factory resetting it since that is not working.
edit: Progress! These are my steps:
- Downloaded fresh stock Samsung ROM and another version of CF-root.
- Flashed stock ROM and then CF-root kernel.
- Booted into recovery and did the whole wipe.
- Flashed .zip twice (don't know if that did the trick or what)
- Wipe dalvik cache and fix permissions.
After that the phone booted normally and I'm now running ResurrectionRemix with Android 4.1.1, hoping it wil be awesome as ****.
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
hi! first of all im sorry for posting a thread here instead of posting on the rom thread. im a noob and have posted less than 10 times so im not allowed to post in the rom thread. let me explain what my problem is.
i hv a rooted i9300 and was happily using wanamlite v7.3 with stock kernel. but since it became quite slow n laggy i thought of changing my rom n opted for neatrom v7.5 (touchwiz). this is what i did
1 forgot to take a backup. but i had previous backups from not so long ago so i didnt freak out too much
2 wipe data
3 wipe cache
4 dalvik cache
5 wipe battery stats
6 install rom ( i went through all the steps of the rom installation i.e terms n conditions, selecting which apps i want etc)
after the installation the phone started rebooting....only to be booted into recovery mode. i tried rebooting several times, and even reflashing the rom several times, but the phone would only boot into recovery mode.
so i googled my problem n found this solution http://checkrom.com/threads/resurrection-odin-checkrom-evohd™-v4.896/
i used odin n flashed this rom, n thankfully the phone booted normally. BUT i had no signal. the phone wouldnt catch any signal.
after panicking for 10 min i decided to gv one last try n reflashed wanamlite v7.3. thankfully it worked. i hv signal n the phone is running normally
why does it crash when flashing neatrom? i would really like to try this rom. did i do something wrong while flashing?
thanks in advace for ur help
Usually due to not having a current recovery, update to the latest Philz, or not clearing your previous installation, use Philz to wipe for new rom and format mount/storage/emulated.
The no signal issue might be due to efs problems, which has nothing to do with firmware. Older firmwares are less picky about efs, newer ones won't even boot.
Sent from my GT-I9300 using Tapatalk
Get cmw 6.0.4.4 and flash with that. Just to be safe bk up you're efs with ktool from playstore. Get mg4 modem zip. Check md5 don't waste you're time wiping battery stats. And format system,data,cache before you flash. Reason why I say 6.0.4.4 is I have used this on many many roms and it works very well. Same with twrp 2.7
Edit: thinking about it modem's are in aroma installer so you don't need that too much. Get it for another day as it may come in handy.
Sent from my GT-I9300 using xda premium
andrewwright said:
Get cmw 6.0.4.4 and flash with that. Just to be safe bk up you're efs with ktool from playstore. Get mg4 modem zip. Check md5 don't waste you're time wiping battery stats. And format system,data,cache before you flash. Reason why I say 6.0.4.4 is I have used this on many many roms and it works very well. Same with twrp 2.7
Edit: thinking about it modem's are in aroma installer so you don't need that too much. Get it for another day as it may come in handy.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
cwm 6.0.4.4 did the trick! thanks a lot
No problem. Please add solved to thread title to help others. :thumbup:
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.