Hi everyone, recently I flashed Pixeldust rom with the twrp recovery (I did all the wipe: sistem, all both cache and data before flash). Everything seems worked fine but when I tried to reboot the system, my cell stuck on bootloop. It loads the half first animation of the rom, with the flying dots by google and after it goes in bootloop. I tried everything, I don't know if depends from rom. I tried to flash other roms and it happens the same things. Please help me.
EDIT: after pixeldust I also flashed Pixelrom but the result was the same.
Related
I flashed a rom and then this problem started happening since. My phone tries to go to the samsung boot animation screen but never goes through it, it vibrates and then reboot, i tried installing stock rom, etc, i can now go to recovery and download mode.
You might need a jtag
But if i can go through recovery and download mode, maybe there is something i could do to fix this issue?
errusdan said:
But if i can go through recovery and download mode, maybe there is something i could do to fix this issue?
Click to expand...
Click to collapse
I Can install firmware through download mode.!""
Me too, i tried installing stock firmware and all that. Even i am able to use the aroma filemanager from recovery, to see all my files, and when i delete system, preload, data, cache, etc i can see that in fact the device deletes them correctly.
Sorry I miss understand, you can go in download and recovery, my bad.
Have you tried factory reset, Flash original firmware, factory reset, let it boot
What was your original firmware which file(s) did you use?
When the thing you said happened i went on the store and Luckly they replaced my phone. Your phone probably ruined thats what happens when you play with it:cyclops:
Yeah i know that there are risks when you install another roms and such. I've read that it can corrupt your internal sd card, maybe that is what happened to me? because i tried installing different firmwares, kernels, recoveries, wipe data, wipe cache, wipe dalvik cache, wipe system, wipe preload, etc, even i tried installing boot animations, and it stucks at the boot animation screen samsung galaxy, it tries to load but then it vibrates and restart like a loop.
I am now with the russian 4.4.2 rom, and yes i know that i cannot downgrade because of the bootloader version. But i tried installing modified roms with zip (like cm 11) in recovery, and it installs correctly without errors, the problem is with the bootloop.
Hey. So, my dad had a n5120 and it randomly just fell into an infinite bootloop. It had a version of Cyanogen Mod on it. No big deal, I thought. I flashed another ROM from the forums here and same thing. Bootloop. I've been flashing ROMs and messing around with Android for a little while now so I did the basic troubleshooting, wiped cache partition, dalvik cache and factory reset. Still boot looped. I tried installing several ROMs, to no avail (all flashed successfully, but bootlooped). I flashed the stock firmware (recovery, system etc.) with Odin, but still no luck!
I am now stumped. Can anyone help?
nanokiwi said:
Hey. So, my dad had a n5120 and it randomly just fell into an infinite bootloop. It had a version of Cyanogen Mod on it. No big deal, I thought. I flashed another ROM from the forums here and same thing. Bootloop. I've been flashing ROMs and messing around with Android for a little while now so I did the basic troubleshooting, wiped cache partition, dalvik cache and factory reset. Still boot looped. I tried installing several ROMs, to no avail (all flashed successfully, but bootlooped). I flashed the stock firmware (recovery, system etc.) with Odin, but still no luck!
I am now stumped. Can anyone help?
Click to expand...
Click to collapse
You are simply having wrong bootloader issue if I make a quess...I would check it out civato's ROM and follow the instruction.
basically, flash n5120 with odin, and then flash civato's n5120 flexburst room and see if it resolves your issue...
I have tried the roms below:
Pac-rom
LiquidSmooth
CyanogenMod 12.1
CyanogenMod 11
And the result is it always gets stuck at boot where the boot animation continues infinitely. I have gave it about 30 minutes to boot.
With LiquidSmooth I was able to run logcat, but CM12.1 I am not able to.
I have tried resetting system, data, caches in twrp and using the reset for new rom in philz.
I have tried flashing with both TWRP and Philz.
I am using the latest Philz and TWRP.
The only thing that has worked for me is samsung stock ROM, but I do not like the stock ROM.
Are there SPH-L900 phones you have to do something different?
Is there a way to get boot logs from CM12?
Am I doing something wrong?
See attachment from LiquidSmooth.
After flashing http://forum.xda-developers.com/showthread.php?t=2086769 everything worked.
GRMrGecko said:
After flashing http://forum.xda-developers.com/showthread.php?t=2086769 everything worked.
Click to expand...
Click to collapse
Hi,
I see that you got it working by using that thread, but what exactly did you flash from it? I had it working with CM12.1 but decided to flash the recovery from CM for my phone and it ruined the installation. Tried re-flashing with the latest nightly to get stuck in the CM infinite boot, returned to stock (that worked fine) flashed TWRP and CWM 6.0.4.3 Touch, re-did everything again with both, but cant go past the infinite boot. This happened the last time too, but it started working out of nowhere so I continued patching until I flashed "cm-12.1-20150828-NIGHTLY-l900-recovery.img". Now it doesn't boot again and redoing what I did the last time is not working (Wiping Cache, Dalvik...)
Thanks
Raziel10000 said:
Hi,
I see that you got it working by using that thread, but what exactly did you flash from it? I had it working with CM12.1 but decided to flash the recovery from CM for my phone and it ruined the installation. Tried re-flashing with the latest nightly to get stuck in the CM infinite boot, returned to stock (that worked fine) flashed TWRP and CWM 6.0.4.3 Touch, re-did everything again with both, but cant go past the infinite boot. This happened the last time too, but it started working out of nowhere so I continued patching until I flashed "cm-12.1-20150828-NIGHTLY-l900-recovery.img". Now it doesn't boot again and redoing what I did the last time is not working (Wiping Cache, Dalvik...)
Thanks
Click to expand...
Click to collapse
Followed this guide from some post I found after reading for 8 hours, LOL. Don't remember who it is from... It's for the Cyanide ROM but worked perfect for CM12.1 latest nightly with the latest GAPPs
1.) revert everything to stock
Using Odin3 v3.09 I first flashed this: L900VPUCNE2_L900SPTCNE2_SPR.zip
2.) Reboot and verify it's not bricked, then use ODIN to flash Philz philz_touch_6.15.4-l900.tar.md5
3.) Reboot into Philz recovery and follow these steps exactly
1. Mounts and Storage
Format / system
Format / cache
Format / data
Format / data and /data /media (/sdcard)
(note this isn't the EXTERNAL sdcard, on to which I had loaded the ROM, Shift and gapps)
2. Power Options > reboot recovery
3. Wipe cache partition
4. Advanced > Wipe dalvik cache
5. Wipe data / factory reset > Wipe data / factory reset
6. Wipe data / factory reset > clean and install new ROM
At one point Philz asked me if I wanted to root and I said yes.
3.) Flash (from the external sdcard) the ROM (Tablet style ROM found in OP "5.0.2-RC-7.1-tablet"), Then flash Shift (Shift-LP-4.3 other versions DID NOT WORK), then flash gapps (GApps-5.0.2-20150315-signed NO OTHER VERSION WOULD FLASH, got Error 20 every time) Here's the
After everything was flashed I rebooted and got stuck at boot animation AGAIN, so I rebooted into recovery and wiped cache. Just cache, not dalvik or user data, rebooted, and it worked.
Installed Netflix from appstore, when I logged in to netflix it asked me to update google play services (I've seen it do this on other devices as well). Updated google play services and went back to Netflix, chose a random show and tapped on it, stuck at "loading" screen. Rebooted phone, tried netflix again and it works.
This was a tough one! But it's working now and I've saved all these files in one place incase it bricks again. Now to install the Note 3/4 style faux-stitched-leather back cover I got off Amazon.
Thanks all!
Hi,
I had been using Resurrection Remix Lollipop rom for over a year when last week, on manually rebooting, it would not get past the RR boot animation.
Using CWM recovery I tried factory reset/wipe cache/wipe Dalvik cache to no avail.
I then tried flashing a new rom CM13
http://forum.xda-developers.com/galaxy-note-2/orig-development/rom-t3342449
I discovered that CM13 boots fine if I do not flash gapps. However, as soon as I flash gapps, the phone gets stuck on the CM boot animation. I have tried the following gapps packages, downloaded from opengapps:
open_gapps-arm-6.0-stock-20160916.zip
open_gapps-arm-6.0-nano-20160919.zip
open_gapps-arm-6.0-pico-20160919.zip
Thanks for any ideas how to resolve this
Maybe flash back to stock with Odin, factory wipe, and start over?
I have since had success by replacing CWM with the latest TWRP and then re-flashing CM13 and gapps.
(Had to flash CM13 and gapps twice, though, to get rid of a "unfortunately play services has stopped" error during first set up!)
Crossing fingers it will all be ok now, otherwise will try as you suggest audit13, many thanks
Hello ,
I downloaded required files: Lineage OS 14.1(serrano3gxx) , GApps etc. I wiped dalvik cache, data, factory, cache, system and boot. Then, I flashed firstly Lineage OS zip file. Secondly, before rebooting I flashed GApps. I did not take any error. Finally, I did reboot system but phone stuck at loading screen. I have not passed loading screen, yet. Actually, I followed every steps true. Where did I make mistake ? What do you think ? Do you know any solution ?
Also, I did try MIUI Rom and other versions of Lineage Rom. Situations were same.
I did back up my device. But, it is giving error when restoring /data partition. So, I cannot pass loading sreen in any way. This causes that I cannot do anything right now.
Note: I am using CWM Recovery. My phone was rooted. I am using Custom Kernel.
If you want more information, please report
Important Edit: I tried Lineage Rom 15 and it worked. First, I waited several minutes but i worked without any problem. I guess there is no problem for me.