[Q] Help Needed installing Stock base Roms - Galaxy S II Q&A, Help & Troubleshooting

Help Needed !!
Recently I unrooted my alerady rooted I9100 and installed stock ROM,after few days again I rooted it and installed
custom ROM but now whenever I go to install stock base ROM like S4 for I9100 , NoteII mini etc...
it gets stuck on the samsung logo (earlier they were working ok), but this doesnt happen with other ROM's like CM,Carbon etc...
Can anyone suggest any solution or what I must have done wrong.
Thanks in Advance

abhiwildfire said:
Help Needed !!
Recently I unrooted my alerady rooted I9100 and installed stock ROM,after few days again I rooted it and installed
custom ROM but now whenever I go to install stock base ROM like S4 for I9100 , NoteII mini etc...
it gets stuck on the samsung logo (earlier they were working ok), but this doesnt happen with other ROM's like CM,Carbon etc...
Can anyone suggest any solution or what I must have done wrong.
Thanks in Advance
Click to expand...
Click to collapse
Always do Wipe data Factory restore and wipe cache before going to Stock rom to Cm10 or any custom rom.

Jeetu said:
Always do Wipe data Factory restore and wipe cache before going to Stock rom to Cm10 or any custom rom.
Click to expand...
Click to collapse
Yep I also did format/system along with the wipes but no luck is it due to recent changes to cwm's like when I was on stock I had rooted with Philz (touch) and then when I tried to install other stock base I was on other CWM (non touch)
basically I am very new in this flashing world...

abhiwildfire said:
Yep I also did format/system along with the wipes but no luck is it due to recent changes to cwm's like when I was on stock I had rooted with Philz (touch) and then when I tried to install other stock base I was on other CWM (non touch)
basically I am very new in this flashing world...
Click to expand...
Click to collapse
have the latest cwm installed and wipe data, cache and dalvik cache before flashing an entirely new rom
No certainly cwm has nothin to do with it
Check for corupt file

Related

Cyanogenmod 7 Very Annoying Bootloop

So I bought my new galaxy s2 (i9100 int'l version) and i flashed a stock rom that matches my carrier and country (israel) and then i rooted it
by using CF-Root kernel, now i have it for over a month and i flashed many roms with success and then when i tried to flash cm 7 from stock i got into an endless bootloop.
now if you need to know how i flashed it so here you go:
flash stock rom (2.3.5) with ODIN
flash CF-Root kernel that matches my rom (KJ1)
move the official cm 7 (cm-7.2.0-galaxys2.zip) install file onto my internal memory
reboot into cwm recovery with 3 button combo
wipe data/factory reset
wipe cache partition
wipe delvik cache
install zip from internal SD TWICE just to be sure
and then when i reboot with the "reboot device" option i get stuck on the galaxy sii screen
note: after i flashed the zip twice i also tried to reboot straight into cwm from the advanced tab and it still got stuck in the bootloop.
also when im in the bootloop i cant get into cwm with 3 button combo but i can get into download mode and i have been reading that when a thing like this happens it means its a NAND rw corruption
so does it mean i can never acomplish successfull installation of cm 7 on my device?
If you would have corrupted nand rw, you couldn't flash stock firmware with success.
Why don't you try CM9/10?
LSGio said:
So I bought my new galaxy s2 (i9100 int'l version) and i flashed a stock rom that matches my carrier and country (israel) and then i rooted it
by using CF-Root kernel, now i have it for over a month and i flashed many roms with success and then when i tried to flash cm 7 from stock i got into an endless bootloop.
now if you need to know how i flashed it so here you go:
flash stock rom (2.3.5) with ODIN
flash CF-Root kernel that matches my rom (KJ1)
move the official cm 7 (cm-7.2.0-galaxys2.zip) install file onto my internal memory
reboot into cwm recovery with 3 button combo
wipe data/factory reset
wipe cache partition
wipe delvik cache
install zip from internal SD TWICE just to be sure
and then when i reboot with the "reboot device" option i get stuck on the galaxy sii screen
note: after i flashed the zip twice i also tried to reboot straight into cwm from the advanced tab and it still got stuck in the bootloop.
also when im in the bootloop i cant get into cwm with 3 button combo but i can get into download mode and i have been reading that when a thing like this happens it means its a NAND rw corruption
so does it mean i can never acomplish successfull installation of cm 7 on my device?
Click to expand...
Click to collapse
hey ma8, try wiping data/factory reset after installing CM7 not before, then reboot phone and see
przemcio510 said:
If you would have corrupted nand rw, you couldn't flash stock firmware with success.
Why don't you try CM9/10?
Click to expand...
Click to collapse
i tried cm9 and 10 but i just mis the old day you know!
cause i haad sgs1 and i flashed any rom with no problam but i dont wanna go back to my sgs1 i just want to have cm7 on my sgs2.
Sun90 said:
hey ma8, try wiping data/factory reset after installing CM7 not before, then reboot phone and see
Click to expand...
Click to collapse
i tried to wipe after and it didn't work but i appriciate the advice
przemcio510 said:
If you would have corrupted nand rw, you couldn't flash stock firmware with success.
Why don't you try CM9/10?
Click to expand...
Click to collapse
can the problem be envolved with that fact that im flashing the rom from the internal sd card?
cause i saw some videos that people were installing cm 7 onto thier devices from the external sd and it worked for them.
LSGio said:
So I bought my new galaxy s2 (i9100 int'l version) and i flashed a stock rom that matches my carrier and country (israel) and then i rooted it
by using CF-Root kernel, now i have it for over a month and i flashed many roms with success and then when i tried to flash cm 7 from stock i got into an endless bootloop.
now if you need to know how i flashed it so here you go:
flash stock rom (2.3.5) with ODIN
flash CF-Root kernel that matches my rom (KJ1)
move the official cm 7 (cm-7.2.0-galaxys2.zip) install file onto my internal memory
reboot into cwm recovery with 3 button combo
wipe data/factory reset
wipe cache partition
wipe delvik cache
install zip from internal SD TWICE just to be sure
and then when i reboot with the "reboot device" option i get stuck on the galaxy sii screen
note: after i flashed the zip twice i also tried to reboot straight into cwm from the advanced tab and it still got stuck in the bootloop.
also when im in the bootloop i cant get into cwm with 3 button combo but i can get into download mode and i have been reading that when a thing like this happens it means its a NAND rw corruption
so does it mean i can never acomplish successfull installation of cm 7 on my device?
Click to expand...
Click to collapse
Are you sure you have I9100 or do you have I9100G? Try flashing CM9 or CM10 and report if you face similar issues.
atulalvenkar said:
Are you sure you have I9100 or do you have I9100G? Try flashing CM9 or CM10 and report if you face similar issues.
Click to expand...
Click to collapse
i flashed cm9 and 10 with no problem and i know for sure i have i9100 cause all the roms i flash are for i9100 and i flash them successfully.

Boot loop not resolved after flashing stock

Hey guyz
I flashed siyah kernel
Then I tried dual boot wid sammy jb (1st ROM) and cm10.1 as second.
However I wasnt able to boot to second ROM and I had just black screen
Then I removed 2nd ROM
And tried to boot into primary
But got a bootloop.
Then i wiped cache dalvik cache and partition cache.. Still no luck
Then I restored nandroid.
No luck
Then I flashed stock ROM wid odin
Still no luck
What am I missing.. M new to Samsung..
doctor_droid said:
Hey guyz
I flashed siyah kernel
Then I tried dual boot wid sammy jb (1st ROM) and cm10.1 as second.
However I wasnt able to boot to second ROM and I had just black screen
Then I removed 2nd ROM
And tried to boot into primary
But got a bootloop.
Then i wiped cache dalvik cache and partition cache.. Still no luck
Then I restored nandroid.
No luck
Then I flashed stock ROM wid odin
Still no luck
What am I missing.. M new to Samsung..
Click to expand...
Click to collapse
What ur missing for now is a little commonsense to Read before doing anything silly
1)U should be aware (if not get it now), that u cannot Dual boot Stock Samsung JB4.1.2 or Roms based on it, unless they are modified.
2) Siyah doesn't support Rom's like CM10.1 which is based on Android 4.2.2 properly.
3) Dual boot not wrk'ng with JB 4.1.2 (stock samsung/and roms based on it) is due to the reason that they use 'Preload partition' which is required as 'Secondary rom-partition' for Dual boot .
4) which is the reason why u werent able to boot CM10.1 in the firsrt place and could'nt restore/boot back the stock JB (reason being the data in the preload/secondary rom partition being deleted)
5) now start afresh by installing/flashing a stock JB rom via ODIN.
He he he I read siyah doesn't support jb dual boot still was stupid enough to try :/ ...
And as I mentioned...flash stock still doesn't let it boot... I see Samsung and then boot loop
Sent from my GT-I9100 using Tapatalk 2
doctor_droid said:
He he he I read siyah doesn't support jb dual boot still was stupid enough to try :/ ...
And as I mentioned...flash stock still doesn't let it boot... I see Samsung and then boot loop
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
try flashing a custom kernel like 'Philz' from Odin, then enter its recovery and do full wipe including 'Preload',after that try flashing either a stock rom from odin or a Stock based custom rom like 'Neat rom' or 'Alliance Rom' from philz recovery and see
Sun90 said:
try flashing a custom kernel like 'Philz' from Odin, then enter its recovery and do full wipe including 'Preload',after that try flashing either a stock rom from odin or a Stock based custom rom like 'Neat rom' or 'Alliance Rom' from philz recovery and see
Click to expand...
Click to collapse
Sure will try and let u knw...currently m able to boot official cm and enjoying it... bt having poor battery
Sent from my GT-I9100 using Tapatalk 2
Sun90 said:
try flashing a custom kernel like 'Philz' from Odin, then enter its recovery and do full wipe including 'Preload',after that try flashing either a stock rom from odin or a Stock based custom rom like 'Neat rom' or 'Alliance Rom' from philz recovery and see
Click to expand...
Click to collapse
okay i flashed philz kernel ... formated /wiped data ,dalvik,system,cache preload, ... flashed neat rom.. success... then i tried flashing stock rom.. got a bootloop after seeing samsung logo...
i can restore nandroid of cm10.1
bt restoring nandroid of pure stock gives bootloop.
Sounds like your problem is to do with the /preload folder. To restore a stock nandroid, you also have to restore the preload folder associated with that backup. Search on xda for hawkerpaul's backup and restore scripts for preload, and read his OP on how to use them. That should get you sorted. As you wouldn't have already backed it up from the sound of things, you might not have any luck restoring that exact stock backup, and may have to reflash. If you need to extract data from the nandroid, titanium backup can extract data from a nandroid.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox

[Q] I need your help please

Hello,
I was trying to do a factory reset on my S2, and I noticed it doesn't delete my other files (Music, Photos, Etc.) but it does reset my apps installed. Because I want to totally erase my files, I went to recovery mode and did a wipe, and I think I may have wiped the data, system, dalvic, etc on the process. And now my phone wont boot up. It is stuck at the Siyah logo (Because I flashed siyah on it before and it was a success). After this, I tried to flash siyah again into my device and its still stuck. I dont know what to do anymore, I also tried factory resetting using recovery mode. I have flashed other kernels but it still doesn't work. BTW I am using a jelly bean device
Newbees said:
Hello,
I was trying to do a factory reset on my S2, and I noticed it doesn't delete my other files (Music, Photos, Etc.) but it does reset my apps installed. Because I want to totally erase my files, I went to recovery mode and did a wipe, and I think I may have wiped the data, system, dalvic, etc on the process. And now my phone wont boot up. It is stuck at the Siyah logo (Because I flashed siyah on it before and it was a success). After this, I tried to flash siyah again into my device and its still stuck. I dont know what to do anymore, I also tried factory resetting using recovery mode. I have flashed other kernels but it still doesn't work. BTW I am using a jelly bean device
Click to expand...
Click to collapse
did you fix permissions ?
slimlo said:
did you fix permissions ?
Click to expand...
Click to collapse
Sorry I'm nub, what is permissions? Can I find that on recovery mode?
Newbees said:
Sorry I'm nub, what is permissions? Can I find that on recovery mode?
Click to expand...
Click to collapse
yep in recovery mode
I found the fix permission Sir. Shall I flash again the kernel and do a fix permission?
Sir, it's still stuck at the Siyah logo
If you've formatted system as you say you will need to flash a rom, I'm running the latest neatrom lite, I'm confused by your post its 4am here
Sent from my GT-I9100 using Tapatalk 2
Hello sir, sorry if I disturbed your sleep XD no I did not flash a ROM. I just flashed a kernel using ODIN. Should I flash a ROM?
If I flash a new ROM, say the latest Snapdragon for S2 will the kernel be included in the package? I still cant pass the logo screen even though I have flashed different kernels
Newbees said:
If I flash a new ROM, say the latest Snapdragon for S2 will the kernel be included in the package? I still cant pass the logo screen even though I have flashed different kernels
Click to expand...
Click to collapse
the kernel is included most all roms doe and also make sure you follow all instructions on flashing properly... always make sure you do a backup )
gl
slimlo said:
the kernel is included most all roms doe and also make sure you follow all instructions on flashing properly... always make sure you do a backup )
gl
Click to expand...
Click to collapse
Thanks Sir Slim, I will try to flash the Snapdragon ROM as soon as after I finish downloading it. Because I believe I have cleared out the operating system and other important data on my device, that's why I need a new ROM.
Hi mate,
Do you run a stock ROM on your phone like you didnt flash any custom ROM on it....
Did you check if the SIYAH kernel you flashed on your device has STOCK ROM support, cause if the siya kernel you flashed has no support for stock rom it will just stay on the siyah logo the whole day until it drains out your battery.....
if you want to go to this website : http://dorimanx.shine.sk/ and dowload the v8.xxx those got stock rom support..... then do a wipe data factory reset....
if your phone booted up, and want to you wipe the phone completely, go to settings and do a factory reset there, your phone will prompt you if you want to wipe the memory card too.... put a check on it then follow the steps okay....
[email protected] said:
Hi mate,
Do you run a stock ROM on your phone like you didnt flash any custom ROM on it....
Did you check if the SIYAH kernel you flashed on your device has STOCK ROM support, cause if the siya kernel you flashed has no support for stock rom it will just stay on the siyah logo the whole day until it drains out your battery.....
if you want to go to this website : http://dorimanx.shine.sk/ and dowload the v8.xxx those got stock rom support..... then do a wipe data factory reset....
if your phone booted up, and want to you wipe the phone completely, go to settings and do a factory reset there, your phone will prompt you if you want to wipe the memory card too.... put a check on it then follow the steps okay....
Click to expand...
Click to collapse
Thank you sir! You are right that I did not have a custom ROM when I installed the Siyah kernel. Maybe that's the reason I was stuck
Newbees said:
Thank you sir! You are right that I did not have a custom ROM when I installed the Siyah kernel. Maybe that's the reason I was stuck
Click to expand...
Click to collapse
Nope it's not the right reasons may be you flashed a wrong siyah kernel.
Tell me your android version is it jellybean or ics
Sent from my GT-I9100 using xda premium

A problem with all JB 4.3 ROM I've tried

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

[SOLVED] Galaxy S3 not booting any AOSP/AOKP Custom ROMs. Stuck on Sammy?

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.

Categories

Resources