Hi everyone. So, I wanted to install a KitKat custom ROM to my device (which has a unlocked bootloader), and so, I dug through some old ROMs, I tried Cyanogenmod, AOKP and AOSB, since the mayority of other ROMs were gone.
Now, I tried each one, and after some use and installing a lot of apps: BAM! It crashed, the bootanimation appeared, without even rebooting and then it rebooted, but stayed on a bootloop.
(Also, I tried M5 kernel to see if it helps, but it did not.)
What is going on?
Best regards.
Related
Hi XDA,
For the past several days I've tried to Safestrap a custom ROM to my phone. I'm running a rooted Samsung Galaxy S4 with ME7 (Verizon), Android 4.2.2. It's worth noting that the phone has not received an official Verizon update since August; I tried using Loki back then before knowing about the locked bootloader, and it has not affected anything except that the phone softbricks into the ODIN screen whenever it tries to install a Verizon update. (I hope this is not the cause of the problem, but let me know if you think it is.) It's also worth noting that I deleted the stock messaging app (SecMMS.apk and SecMMS.odex.) I am using Safestrap 3.65.
So far, I've tried three different ROMs (Hyperdrive RLS10.2, Jelly Beans Build 7, Google Play Edition for 4.2.2.) Each install produced the same results: it installs just fine in the ROM slot (along with the ME7 modules afterwards), but when I reboot the system, it shows the Samsung logo, the Safestrap splash screen, and then the screen goes black indefinitely. A battery removal is required.
I've tried every trick I could find to get the ROMs working. I've done a full factory reset each time (data + both caches), tried downloading each mod several times on both my phone and my computer (verified MD5 each time) and same with the modules, waited at least 20 minutes during each boot attempt, tried installing each ROM with default settings and minimal apps, used Stock kernels each time, made sure the modules are installed before rebooting (I also tried without the modules to make sure they weren't the problem--same result.) Each time I try an install, I delete the ROM slot and format it again (usually a 1GB-2GB-300MB split.) I've searched and searched and can't seem to find anyone with this problem that hasn't solved it through one of the fixes I've unsuccessfully tried.
I'm plum out of ideas now, and am hoping someone may have more wisdom to share. Please help!
Hello,
I have been googling and reading all threads about this issue for over a month now, so it's problably something quite special. Every time I try to use an app using a camera or flashlight, it reports with "Can't connect to camera" message. This first happened while trying to flash a Kitkat rom (Artas's CM11) with wrong recovery. So it was not working, I got back to system, flashed the correct recovery via flashify, got back to it and finally flashed the rom. Ever since that the camera has not been working, with one exception - now this is the interesting thing that makes me think it's not a hw problem - while trying to do all kinds of unbricks and resets I know of (flashing all kinds of different roms, CM based, AOSP, of course all kinds of original roms) I decided to go for KDZ - so I got the original bin I found on this forum and got back to v10i and the camera worked! So I was happy that it's solved and decided to stick with stock rom. It updated to JB (the official way) and ever since, it has not been working. I have tried to flash persist images, to mess with permisions and I can't really think of any other way. (Of course I have tried to flash KDZ again the same way, but it did not work, not even on ICS).
Thanks for every idea!
Hello all...
First of all, I'm not very experienced at flashing roms.. HOWEVER, I've flashed several roms across multiple phones over the years and have yet to brick a phone.. so I am fairly familiar with recoveries, etc... But I've run into a "wall" and don't know what to do.... hopefully someone can shine some light to my issue.
My TMobile S5 is currently running Twisted Lollipop (v7?).. but I want to switch now to a CM based rom. I had PREVIOUSLY used a CM based rom (a nightly) dated back from June before I switched to Twisted. My phone is rooted.. and I am using TWRP recovery. However, NOW if I do a full on wipe... and try to flash a rom (so far only the latest nightlies).. it seems to do some partitioning stuff.. and then stops saying COMPLETE... I never get the typical "install" text you see when installing a rom in recovery.. If when it's finished.. when I click REBOOT.. TWRP asks me if I want to.. and warns NO OS is installed..
I was able to load a backup of a CM 12.1 based build from a June nightly I had.... but I get the same thing if I go thru the CM updater. I honestly haven't tried to flash anything else..
Am I missing or overlooking something.. I'm on the DOB1 firmware.
Thanks
aenielida
Hi,
I have quite a serious problem with my phone.
I used stable CM11 as my ROM lately, worked nice, seemed to be ok. Now, if I want to boot my phone, it suddenly crashes as soon as I want to enter unlock code. "Funny" thing is, performing a full backup via TWRP didn't help.
So I decided to wipe everything (even sdcard) and do everything from scratch, including flashing boot.img. After flashing the ROM zip, it's still the same.
After that, I flashed boot.img from AOSP 5.1 Unstable, installed this new, different ROM (which I had successfully tested on my device before) and STILL THE SAME?!
What's going on here? It sounds a bit like defective hardware, but I never experienced a crash when I was in Recovery mode, so that's quite unplausible.
My last idea is to flash stock ftf. Perhaps this will help...
So for various reasons, many problems with cm13, candy and lineage ROMs, I decided to go back to cm12 (carbon ROM)
Wasn't simple but eventually I got there and everything was good for a week. Then for some reason the wifi stopped working, getting stuck at 'turning on wifi'.
At this point I couldn't do much of anything except restore my old backup of carbon ROM.. couldn't install cm13 (hang at first boot) couldn't install candy 6 or 7 (boot loops) or lineage (boot loops). Couldn't even restore backups I'd made of those others.
So, several hours of effort got me back to rooted stock 5.1. Everything works right now, including wifi, but I'm stuck at stock which of course is less than ideal. I figured I could try a clean install of carbon ROM but this is now my problem. When I try to install via TWRP, I get an error saying that it requires bootloader .....b322 but my bootloader is 'unknown'.
A week of fiddling and flashing and I'm stumped. Anyone know what's wrong and how to fix it?
Sent from my MT2L03 using XDA-Developers Legacy app