Galaxy J7 with A5 2017 V4 ROM giving random reboots - Samsung Galaxy J7 Questions & Answers

Hello everyone, I am here to ask you for help, I flash the ROM A5 2017 V4, I deleted some apps, and also includes, this did not interfere with the system, but when I changed the boot animation, it started ramdom reboots when the screen Is offline, I do not want to switch to another ROM, but I can change boot animation to Stock, help me if possible

Dirty flash the rom i.e. flash without wiping.
Sent from my SM-G935F using Tapatalk

I cleaned everything right
dodo2244 said:
Dirty flash the rom i.e. flash without wiping.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
No, I cleaned the Dalvik cache, cache, system, and internal storage

Related

[Q] custom ROM boot problem!

Hey everyone,
I'm a new-by to the tech world. I have a "google nexus s" running on ICS 4.0.4, I recently rooted my phone, flashed clockworkmod recovery and tried to install CM9 on my device. After the installation was completed through the clockworkmod, the boot image had showen up and continued to boot throughout the night and never showed up the home screen nor did the custom ROM open itself.
Can anyone give me a lil help as to about what this problem is or the reason why this is happening?
Any help would be really appreciated.
Thanx!
Did you do a full wipe and cache wipe? My suggestion is to do that and reinstall. You could also try a different ROM.
But wouldnt I loose my phone data if I do that?
Sent from my Nexus S using xda premium
i'm having the same problem for every ROM i try on my phone! what to do?
You have a bootloop, this appears because of kernel (boot.img) problems and/or inconsistent cache.
Please wipe/erase cache and Dalvik cache (this can be found in the Advanced menu). Wiping cache partition and Dalvik cache won't erase your personal data.
Make sure the previously flashed CM zip contained a boot.img file. If not, please flash a proper/recommended boot.img (kernel; which is in a zip file) or another rom (with boot.img).
When you flash a new rom over your stock.. first make a backup, then you need to wipe data, cache and dalvik cache..
Sent from my Nexus S using XDA app
Got a backup and mods are running cool! Thanx for the help!
Sent from my Nexus S using xda premium

[Q] After Flushing PA Jelly Bean Rom It Keep showing PA boot screen

Hi,
I have AT&T Motorola Atrix 2 MB-865 , i was on official ICS after root unlock I flushed pa_edison-3.69-20130729-nokex.zip rom to my atrix 2, using http://forum.xda-developers.com/showthread.php?t=2050705
i did factory reset, data format system, format cache and etc before flushing that ROM after successful flush , I rebooted , after reboot it keep stuck (does't not hang just stuck) on paranoid boot screen, i tried to flush again but same result in addition i want to say i flushed only rom , no gapps, , now i am again on ics_edison using RDS Lite ,Please any one tell me where i am wrong
Thanks in advance.
cheeta123 said:
Hi,
I have AT&T Motorola Atrix 2 MB-865 , i was on official ICS after root unlock I flushed pa_edison-3.69-20130729-nokex.zip rom to my atrix 2, using http://forum.xda-developers.com/showthread.php?t=2050705
i did factory reset, data format system, format cache and etc before flushing that ROM after successful flush , I rebooted , after reboot it keep stuck (does't not hang just stuck) on paranoid boot screen, i tried to flush again but same result in addition i want to say i flushed only rom , no gapps, , now i am again on ics_edison using RDS Lite ,Please any one tell me where i am wrong
Thanks in advance.
Click to expand...
Click to collapse
Firstly its FLASH not FLUSH.!! On which system did you flash the ROM.. If you have flashed on 2nd system you should not wipe data... It will wipe out your other partitions... And did you flash via bmm or cwm??
Sent from my MB865 using XDA Premium HD app
nikhJ said:
Firstly its FLASH not FLUSH.!! On which system did you flash the ROM.. If you have flashed on 2nd system you should not wipe data... It will wipe out your other partitions... And did you flash via bmm or cwm??
Sent from my MB865 using XDA Premium HD app
Click to expand...
Click to collapse
he's is in a habit of writing 'flush' in place of 'flash' (see his other posts)
sent from my A2 running ÑÜMÅ3.0
$ÇÏÊÑÇÈ is the only TRUTH
Re
nikhJ said:
Firstly its FLASH not FLUSH.!! On which system did you flash the ROM.. If you have flashed on 2nd system you should not wipe data... It will wipe out your other partitions... And did you flash via bmm or cwm??
Sent from my MB865 using XDA Premium HD app
Click to expand...
Click to collapse
I used Atrix2BootStrap.apk which seem like CWM based, there was no option 1st system or second system, it was like standard flashing(means normally we flash using Clock world recovery so no 1s or seccond system option appeared).
cheeta123 said:
I used Atrix2BootStrap.apk which seem like CWM based, there was no option 1st system or second system, it was like standard flashing(means normally we flash using Clock world recovery so no 1s or seccond system option appeared).
Click to expand...
Click to collapse
i think this rom can be install via BMM only... my friend has do like what you do before..... the only you can do is FXZ to stock,root,and then go to play store, install BMM 0.3..... dont install bootstrap.apk again after installing BMM and you will be fine...
I seem to have a similar issue.
First of all although this is my first post on XDA I'm not new to flashing and using Custom Roms infact I have been using CM 10.1 versions switching back and forth between 4.1.2 when I run into trouble.
I decided to give PA a shot and seem to have run into a wall. I flashed PA nokex on system 3 (which previously had CM10.1 - JBX 0.8.1(kernel)).
Before flashing PA on it I destroyed and recreated system, data and cache partitions so I didn't see the need to do wipes on them again. Nevertheless I did dod wipes. Flashed PA nokex, Gapps, wiped dlavik cache and rebooted. (Using BMM ofcourse)
I am stuck at a black screen with the red LED. I would really like to sample PA so any help would be really appreciated.
blazebud350 said:
I seem to have a similar issue.
First of all although this is my first post on XDA I'm not new to flashing and using Custom Roms infact I have been using CM 10.1 versions switching back and forth between 4.1.2 when I run into trouble.
I decided to give PA a shot and seem to have run into a wall. I flashed PA nokex on system 3 (which previously had CM10.1 - JBX 0.8.1(kernel)).
Before flashing PA on it I destroyed and recreated system, data and cache partitions so I didn't see the need to do wipes on them again. Nevertheless I did dod wipes. Flashed PA nokex, Gapps, wiped dlavik cache and rebooted. (Using BMM ofcourse)
I am stuck at a black screen with the red LED. I would really like to sample PA so any help would be really appreciated.
Click to expand...
Click to collapse
i think PA non kexec is for ICS base only!
¢@®bøÑ///JBX
Super_Commando said:
i think PA non kexec is for ICS base only!
¢@®bøÑ///JBX
Click to expand...
Click to collapse
Yeah. I flashed the kexec version and it booted up fine... Thank you.

[Q] Fixing A Messed Up Flash

So I flashed a custom ROM and did the usual steps. Install, wipe caches, etc., and the ROM itself loads. It's a custom 4.4.2 ROM for GT-P31XX and I used CWM 6.0.4.5 recovery to flash it. Problem is that when I boot, I get to the lock screen but System UI, Settings, and AOSP Keyboard always fail. I can't seem to boot into recovery any more but I want to install a different ROM or reinstall stock JB and start over. How would I go about fixing this situation?
Okay, I can boot into recovery actually.
KingMotion said:
Okay, I can boot into recovery actually.
Click to expand...
Click to collapse
Did you wipe everything first then install? Because you want to wipe, install, boot. Cache, dalvik, data, system are the main ones, always wipe these when flashing a new ROM.
Sent from my GT-P5110 using XDA Premium 4 mobile app

[Q] Nexus 5 enters bootloop everytime I reboot

Hi,
My Nexus 5 enters bootloop on Euphoria logo everytime I reboot. Wiping cache and dalvik solves the problem but I have to wait for apps to "update" after doing this.
It also happens when I flash another ROM by MultiROM and try to boot into it but I haven't tried to wipe cache and dalvik so I don't know if it solves the problem. I uninstall the ROM when I get a bootloop.
I want to know what causes the problem and how to solve this.
Recovery: TWRP MultiROM (latest)
ROM: Euphoria OS 1.0
Kernel: ElementalX 2.10 (SELinux: permissive)
GApps: PA Google Stock Package
Other: MultiROM v31 and Xposed installed.
Thanks in advance.
When you instated the rom did you wipe data and the caches first?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
When you instated the rom did you wipe data and the caches first?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, when I installed my internal ROM (Euphoria). In fact, I installed it after accidentally wiping everything on phone, that's another story.
But I don't wipe anything when I install secondary ROMs. Should I?

Weird issue

So, the problem started after i flash slimsaber rom after wiping system, data, cache and dalvik on my oxygen os...
The boot was fine, but it can't detect my sim card, and it reboot after i enable the wifi
Does anybody knows how to fix it?
Sent from my iPhone using Tapatalk
AndreIrawan97 said:
So, the problem started after i flash slimsaber rom after wiping system, data, cache and dalvik on my oxygen os...
The boot was fine, but it can't detect my sim card, and it reboot after i enable the wifi
Does anybody knows how to fix it?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
You have to flash the latest CM firmware in order to switch from Oxygen to AOSP roms since they are based on CM device trees.

Categories

Resources