I'm on Siyah Kernel which supports dual booting. My phone was running fine on ParanoidAndroid (Android version 4.1.2) as primary ROM, and my secondary was Revolution HD (a stock based ROM).
But then I decided I should try out LIQUIDSMOOTH [4.1.2] so I flashed it as my new secondary ROM. This wasn't my first time flashing a ROM, so yes, I know how to do it, wipe cache, wipe data, wipe Dalvik etc.
But here comes the issue: I can't boot into secondary ROM. I then force restart my phone by holding the power button and boot it into the primary Rom, but I now have no mobile connection. After unlock the lockscreen, the phone isn't asking for my SIM code as usual. I now can't make a call or receive one. Does any body know what happens?
PS: I've removed the secondary ROM and reflashed the primary one, but I still have no mobile connection.
I've even restored my phone under CWM Recovery with the back up I made 3 months ago to Samsung stock Rom but the phone still can't recognize the SIM card. I have no network data what so ever. My phone is not a phone right now cause I can't make or receive any phone call. I don't know what to do any more. Can somebody help me.
Try reflashing your modem or try another one
Never mind. I used Odin to flash Samsung official stock ROM and my phone recognizes the SIM card now.
Verizon S3 is rooted and running pac rom. Wanted to try cm10.1 with 4.2 gapps. Backed up, wiped and also WIPED CACHE PARTITION FOR THE FIRST TIME. then i installed the new rom and now i am without service even if i restore my backups. what did i do and how do i fix it?
No data service
goodknight001 said:
Verizon S3 is rooted and running pac rom. Wanted to try cm10.1 with 4.2 gapps. Backed up, wiped and also WIPED CACHE PARTITION FOR THE FIRST TIME. then i installed the new rom and now i am without service even if i restore my backups. what did i do and how do i fix it?
Click to expand...
Click to collapse
I am having same problem with neat rom. I have tried different modems and kernels but all still do not give me data service.
This is I9300 forum .
jje
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.
hello,
After installing NeatROM 6.4, I am not able to restore the CWM backup of Jelly Bean 4.1.2.
A CWM restore of the Cyanogenmod 10.1.3, works fine though.
When restoring the JB backup, I get a boot loop on the logo.
Even after doing a wipe data/factory reset and wipe Dalvik cache, still the bootloop.
It was possible to flash the stock ROM (both ICS and JB), so phone is back to normal.
Just want to know if anybody came across this issue and what might be the cause if it and how can one resolve it.
Many thanks for your help.
regards,
neptune3nl said:
hello,
After installing NeatROM 6.4, I am not able to restore the CWM backup of Jelly Bean 4.1.2.
A CWM restore of the Cyanogenmod 10.1.3, works fine though.
When restoring the JB backup, I get a boot loop on the logo.
Even after doing a wipe data/factory reset and wipe Dalvik cache, still the bootloop.
It was possible to flash the stock ROM (both ICS and JB), so phone is back to normal.
Just want to know if anybody came across this issue and what might be the cause if it and how can one resolve it.
Many thanks for your help.
regards,
Click to expand...
Click to collapse
Backups don't always work. The best way to restore stock is to download the stock rom for your region from sammobile.com or one of the other sites with stock firmware and flash it via odin.
noppy22 said:
Backups don't always work. The best way to restore stock is to download the stock rom for your region from sammobile.com or one of the other sites with stock firmware and flash it via odin.
Click to expand...
Click to collapse
OK. That could make sense. But I restored the JB Backup several times, before I installed NeatROM.
Could it be that a directory was changed / deleted / overwritten during the installation of NeatROM, thus giving me the bootloop?
neptune3nl said:
OK. That could make sense. But I restored the JB Backup several times, before I installed NeatROM.
Could it be that a directory was changed / deleted / overwritten during the installation of NeatROM, thus giving me the bootloop?
Click to expand...
Click to collapse
I'm not sure what could have happened, but I always have a copy of the stock rom in .tar.md5 format so if I get into trouble I can always go into download mode and rescue my phone with odin......
I found this out the hard way on my S2 as well......
It turns out that CWM doesn't backup the Preload partition.....so when you try to restore the nandroid it simply won't work.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Hey guys. So i tried flashing this rom but i couldnt get data or service to work so i restored my backup from Temasek's cm12.1 port. Everything was fine except that now I dont have any LTE and im stuck with 3G.
Ive tried a factory reset into clean flashing temasek's cm12.1 build but lte still doesnt work.
Any advice is appreciated
Edit: Now the screen won't even recognize the spen touches
itzkpanda said:
Hey guys. So i tried flashing this rom but i couldnt get data or service to work so i restored my backup from Temasek's cm12.1 port. Everything was fine except that now I dont have any LTE and im stuck with 3G.
Ive tried a factory reset into clean flashing temasek's cm12.1 build but lte still doesnt work.
Any advice is appreciated
Edit: Now the screen won't even recognize the spen touches
Click to expand...
Click to collapse
First I would go to settings/connections/more networks/mobile networks/network mode and make sure cdma/lte is checked. Then I would go to settings/general/system update/update PRL and make sure your PRL is updated to cm12.1 . If that doesn't work you make have corrupted something flashing back to cm12.1. While in recovery did you wipe system, cache, and delvik-cache before you flashed your backup of cm12.1 ? You could try going back into recovery wiping system, cache, and delvik-cache twice and restoring cm12.1 again and see if that corrects the problem.
If that doesn't work you will have to go and flash back to bone stock OS. If you have to go with the last option make sure to save all your data ( music, pics etc. ) to the desktop of your PC first, make sure your backup of cm12.1 is on your sd card. Then odin flash the stock OS TWICE !!! To make sure you are bone stock with your status in a stock recovery reading is Samsung Official and not custom !!! Then flash your custom recovery, and root the device. Now your ready to add back your personal data and flash your back up of cm12.1 which you should have moved to sd card. Click on rom flashing basics in my signature to get all the links and more info.