custom rom for sm-g360h\Ds>>>plz - Samsung Galaxy Core Prime Questions & Answers

i need custom rom for SM-360H\DS
i have tried [ROM][6.0.1][BETA-1][SM-G360H/HU] RESURRECTION REMIX 5.7.4 for SamsungGalaxyCorePrime by [email protected]
but it's freezing on the starting boot image
plz help

Ahmed.se said:
i need custom rom for SM-360H\DS
i have tried [ROM][6.0.1][BETA-1][SM-G360H/HU] RESURRECTION REMIX 5.7.4 for SamsungGalaxyCorePrime by [email protected]
but it's freezing on the starting boot image
plz help
Click to expand...
Click to collapse
Clean your phone with WIPE of TWRP, and flash rom again. I'm using BETA-4 and CORE™ KERNEL, very good but don't suitable to use daily. After 4 month use, today I have to reset my phone by TWRP and i lost my data, because it hang on logo boot screen But it still good custom rom, i will use RR to explorer

Try CM13

Related

Problem with Custom Roms with Samsung S5

Hello Every One
I Have A Problem With my Phone Samsung Galaxy S5 (SM-G900F) I was Having a resurrection remix Rom on my phone then i have booted an Official Marshmallow Rom Then it have been slow so i have flashed Rom resurrection remix Again and here is the Problem when i flashed it it flash normally when it goes to the resurrection remix Logo it doesn't open and stay showing the logo
i have restarted several times and it doesn't open so I Have tried to flash cyanogenmod Rom then it goes on the logo of the cyanogenmod Rom then the Phone Restart .
Please Help .
SOS !!
statiicz said:
Hello Every One
I Have A Problem With my Phone Samsung Galaxy S5 (SM-G900F) I was Having a resurrection remix Rom on my phone then i have booted an Official Marshmallow Rom Then it have been slow so i have flashed Rom resurrection remix Again and here is the Problem when i flashed it it flash normally when it goes to the resurrection remix Logo it doesn't open and stay showing the logo
i have restarted several times and it doesn't open so I Have tried to flash cyanogenmod Rom then it goes on the logo of the cyanogenmod Rom then the Phone Restart .
Please Help .
SOS !!
Click to expand...
Click to collapse
I am having EXACTLY the same problem here!!! It happened after I flashed stock BTU (UK unbranded) and then trying to revert back to BlissPop/CM13. Maybe the new stock boot/modem is not supported by custom ROM makers yet?
Could anyone confirm/solve this? Thanks a lot!
statiicz said:
Hello Every One
I Have A Problem With my Phone Samsung Galaxy S5 (SM-G900F) I was Having a resurrection remix Rom on my phone then i have booted an Official Marshmallow Rom Then it have been slow so i have flashed Rom resurrection remix Again and here is the Problem when i flashed it it flash normally when it goes to the resurrection remix Logo it doesn't open and stay showing the logo
i have restarted several times and it doesn't open so I Have tried to flash cyanogenmod Rom then it goes on the logo of the cyanogenmod Rom then the Phone Restart .
Please Help .
SOS !!
Click to expand...
Click to collapse
Just verifing. When flashing a new rom, you are clearing the old one out first, right?
Like wiping the cache, system, boot,ect.
Shadow Assassin said:
Just verifing. When flashing a new rom, you are clearing the old one out first, right?
Like wiping the cache, system, boot,ect.
Click to expand...
Click to collapse
(I'm #2) Did all the usual wipes. No problem with stock rom, but cannot boot after flashing any custom ROMs like CM13.
Shadow Assassin said:
Just verifing. When flashing a new rom, you are clearing the old one out first, right?
Like wiping the cache, system, boot,ect.
Click to expand...
Click to collapse
Yes I Wipe All The Data With TWRP Recovery And i Have tried with CWm Recovery And Philz touch recovery either
And the is no changes it stuck !!
spolarbear said:
(I'm #2) Did all the usual wipes. No problem with stock rom, but cannot boot after flashing any custom ROMs like CM13.
Click to expand...
Click to collapse
statiicz said:
Yes I Wipe All The Data With TWRP Recovery And i Have tried with CWm Recovery And Philz touch recovery either
And the is no changes it stuck !!
Click to expand...
Click to collapse
Sorry its taken me so long to reply back, had stuff going on. Anyways, after doing some studying and playing with my sisters G5. They seem to be very finicky with modifications, even after root and a custom recovery installed. One thing to try (because it happened on my skyrocket), is to reinstall your recoveries and do it with a computer, that how to get a stable install, if your already using a computer, then it sounds like a something from the old firmware may still be their. You may need to install the earliest stock firmware for your G5 out of the box, and root it from their, you may even need a complete stock restore then re-root and install your custom recovery. Also. I have had some roms take 20 minutes to boot, but thats the rom stabilising.
Sent from my LG-H900 using XDA-Developers mobile app

Error 7 while flashing new rom

I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9
shahark86 said:
I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9
Click to expand...
Click to collapse
Hi, If you already have twrp recovery and you can boot into twrp recovery, then you need to download stock oxygen os 2.2.1 ota.
when you download oxygen os 2.2.1 ota, flash it via twrp recovery, after that wipe factory data reset, then you flash your custom roms later. this will bypass the error 7 and you will have to resume enjoying your custom roms.
Here's what happens, when u totally erases the system, data, and formats everything with twrp recovery, custom roms don't run again, i think they kinda need some basic files from the stock rom to enable them to run. i experienced this myself with aicp and this is how i fixed it. so go on, look for the oxygen 2.2.1 ota.zip, download, flash, then wipe data fastory reset, then you can now have your custom roms flashed and working. again.
Right!! but oos 3.0 official is also working
shahark86 said:
I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9
Click to expand...
Click to collapse
It's there to protect you from flashing a ROM incompatible with your current bootloader (there's two of them, pre oos3 and oos3 bootloader/fastboot).
So if you want to flash a ROM which is Lollipop (or using Lollipop bootloader like easier versions of Graraks and Seraph08s builds) you will have to restore your phone to oos2.x.x first. Same goes the other way around, and also your recovery system must be compatible with respective bootloader.
This info should be force-feeded to every noob checking in on this forum hoping for an easy swapping of ROMs on this phone, which is not gonna happen because of this.

LEX727: custom ROM's won't boot

Hello. After I flash any custom ROM based on Android 7.1 my phone won't boot to OS. Screen is constantly showing LeEco logo and nothing happens. I use TWRP 3.1.1-0.
try just wiping, flashing rom, and gapps and see if it boots
Azgort said:
Hello. After I flash any custom ROM based on Android 7.1 my phone won't boot to OS. Screen is constantly showing LeEco logo and nothing happens. I use TWRP 3.1.1-0.
Click to expand...
Click to collapse
Go back into TWRP, wipe, by swiping should be all that you need to do. Afterwards reinstall your custom ROM and Gaps nano. Shut off phone, and then start. Sometimes it can take a few minutes to load after the initial install. BTW, I use Paranoid 7.3.1, it works great!
Sent from my LEX727 using XDA Labs
Thank you for you replies. Now my phone works as supposed. I successfully flashed Paranoid Android ROM.

sm-g7102

Hi guys. I just want to ask how to fix bootloop. I think its bootloop. I flash stock ROM from Samsung. Then I tried to flash custom ROM( already done this numerous times in the same phone(cm13, RR, aokp) before I flash stock rom) but when the flashing completed and the phone reboots, its stuck in boot animation. Right now I'm trying to flash this aokp 7.1 for sm-g7102 but stuck in boot animation like other custom ROM. I've already installed aokp 7.1 , cm13, and RR on this phone before I flash custom ROM. Pls help me flash at least aokp. I'm stuck at 4.4.2 KitKat. Help me guys.
kiritokazuto332 said:
Hi guys. I just want to ask how to fix bootloop. I think its bootloop. I flash stock ROM from Samsung. Then I tried to flash custom ROM( already done this numerous times in the same phone(cm13, RR, aokp) before I flash stock rom) but when the flashing completed and the phone reboots, its stuck in boot animation. Right now I'm trying to flash this aokp 7.1 for sm-g7102 but stuck in boot animation like other custom ROM. I've already installed aokp 7.1 , cm13, and RR on this phone before I flash custom ROM. Pls help me flash at least aokp. I'm stuck at 4.4.2 KitKat. Help me guys.
Click to expand...
Click to collapse
Do clean install, wipe all except internal & external sdcard. Then flash the rom

2 boot logos and random reboot

I'm currently running Resurrection remix 7.0. I used to be on superman ROM. My phone will randomly reboot into the superman boot logo. Then will load up resurrection remix. I performed a full wipe in TWRP before installing RR ROM. I have no idea how to solve this issue. If someone knows how to fix, thank you in advance.
elusiveguy said:
I'm currently running Resurrection remix 7.0. I used to be on superman ROM. My phone will randomly reboot into the superman boot logo. Then will load up resurrection remix. I performed a full wipe in TWRP before installing RR ROM. I have no idea how to solve this issue. If someone knows how to fix, thank you in advance.
Click to expand...
Click to collapse
Try flashing the latest oreo build via odin or you can update the bootloader through twrp and reflash resurrection remix. It should work fine after that

Categories

Resources