Database Develop

[Q] Custom roms won't boot.

Hi guys,
First of all, i made a new thread after looking for a solution for days and pretty much everywhere.
• My issue : i can't get any custom rom to boot. Everytime i flash one, i get stuck with endless bootanim
• so you know :
- flashing original firmwares from sammobile or stock based roms (i.e N4elite) with odin or recovery works perfectly. roms boot and everything work flawlessly.
- i tried almost every lollipop roms (RR, Nameless 2.0 and 2.1, cm12.1, asop, aicp)
- i tried different recoveries (CWM, TWRP, PSN_TWRP)
- i tried different gapps packages
- all downloaded files were good
- i tried wiping everything, even tried changing file system to f2fs (and reverted back to ext4)
- i guess flash memory is ok since Sammy roms work
- my battery is almost new, i changed it not so long ago
- i was running an early cm12.1 build and everything was ok, the issue occured when i tried to flash cm12.1 stable 3 build
As i'm now out of idea, any suggestion would be appreciated.
Thanks !

fraydz said:
Hi guys,
First of all, i made a new thread after looking for a solution for days and pretty much everywhere.
• My issue : i can't get any custom rom to boot. Everytime i flash one, i get stuck with endless bootanim
• so you know :
- flashing original firmwares from sammobile or stock based roms (i.e N4elite) with odin or recovery works perfectly. roms boot and everything work flawlessly.
- i tried almost every lollipop roms (RR, Nameless 2.0 and 2.1, cm12.1, asop, aicp)
- i tried different recoveries (CWM, TWRP, PSN_TWRP)
- i tried different gapps packages
- all downloaded files were good
- i tried wiping everything, even tried changing file system to f2fs (and reverted back to ext4)
- i guess flash memory is ok since Sammy roms work
- my battery is almost new, i changed it not so long ago
- i was running an early cm12.1 build and everything was ok, the issue occured when i tried to flash cm12.1 stable 3 build
As i'm now out of idea, any suggestion would be appreciated.
Thanks !
Click to expand...
Click to collapse
Hello,
I got the same issues ...
Trying to root the Stockrom results in the disappearance of baseband. Maybe this could help? I need to get some sleep first.
Regards
Heiko
EDIT: I thought maybe I fill in a bit more detail. I had CM 11 running which also flashed my recovery to cwm. So I used the TWRP Manager to install new Recovery, but I didn't check the Partition! So it didn't work as planned. Phone was in a boot loop and restartet every 5s. But TWRP via Odin worked. I wiped every partition available in Odin and installed Stock. Which seems to work without root.
CM 11 results in a boot loop.
CM 10.3 boots up, bud doesn't find the modem (same as Stock with root)
I hope there is some help. I like this phone a lot.

I did reinstall Samsung Stock via Kies.
And thank god that solved the Problem.
Restored my backup and everything is working again.

Heikoles said:
I did reinstall Samsung Stock via Kies.
And thank god that solved the Problem.
Restored my backup and everything is working again.
Click to expand...
Click to collapse
thanks for your feedback and ideas.
i tried to flash stock with kies, it ended with an error, but flashing stock firmware with odin worked, and everything was ok (including modem)...
for now i'm stuck with stock firmware flashed with odin
EDIT :
i finally succeeded.
- flashed old 4.3 firmware with odin without auto reboot
- the flash failed at the end
BUT
- manual reboot in download
- flashed TWRP tar
- reboot in recovery
- flashed 4.3 modem zip
let system boot
reboot in recovery
flash any rom and gapps !

Custom roms and stuck on splash/boot animation (SOLVED)

Hello!, my device is GT-i9305 and i seem to have a problem of some sort. (I have had three devices before this and installed lots of custom roms, but never have i encountered something like this)
Whenever i try to install a custom rom (omnirom/pacrom/cyanegenmod) i get stuck in the splash/boot screen animation, but when i flash back to stock rom (4.4.4) using odin it loads up and everything works like its supposed to.
I have tried using TWRP and CWM-recovery. (With CWM i can get omnirom to boot, but i wont be able to dial or use mobile-data etc. (Seems like my efs files or something are missing) and i also get some error message about androidcore or somethinglikethat.
Most common fixes for this in the forums are to wipe dalvic and cache after installing. Which i have done + some other odd "fixes" i found.
I am really baffled. Whats wrong?

Did you flash TWRP 2.8.7.0? That recovery is buggy and does not work. You have to stay on 2.8.5.0 for the moment. There are people already trying to fix the faulty recovery. CWM won't get any updates anymore. It does still work but you might come across some ROMs which won't work with CWM.
To start all over again with no issues: flash 4.4.4 Stock, install TWRP 2.8.5.0 and you're good to go

Thankyouthankyouthankyou
That totaly fixed it! Thank you sooooo much, no more sleepless nights because of this.

Problems with TWRP/CyanogenMod 12.1 - Motorola MotoG 2nd Gen XT1068

Hello guys! How are you?
I'm having some bugs with CyanogenMod 12.1 in my MotoG and haven't found nothing that could help me with my problem.
Well, here's the story:
My device had Android KitKat 4.4 as the stock rom and I updated it to Lollipop 5.0 before rooting.
Well, I unlocked the bootloader and used TWRP as a custom recovery and installed SuperSU.
I've been using the phone about almost 8 months after rooting and then, Motorola released an update, I tried to update it via OTA and, of course, it didn't worked since TWRP can't OTA. Nothing changed in my phone, I simply rebooted it and it worked but since a few days some apps started to suddenly close and/or stop.
I decided to install CyanogenMod 12.1, downloaded the latest nightly and a stock package of GApps and flashed them via TWRP.
Wiped Dalvik Cache, Data, Cache and System
At the first attempt, TWRP rebooted after flashing CM12.1 and I wiped the caches via WIPE menu before flashing GApps wich couldn't be installed because there was "no space in storage". Well, I booted my phone normally (running cm12) and downloaded a Micro GApps package and flashed it sucessfully.
Problem is: Clock stops working (it has stopped for now), I can't install some apps from PlayStore such as Facebook, etc and my phone appears to be unrooted.
I think my TWRP is bugged or something cause it does not works as tutorials, etc tells...It shows some errors and sometimes reboots itself after flashing some file.
Do you guys think I should reset everything and then redo all the steps to use CyanogenMod properly? I really liked this custom rom but I'm afraid there will be more bugs in the future....

Anyone?

my solution..
1. (JUST SAYING)You can install ota through fastboot. Use the ota file found in root.( There is a thread for this)
2. Try installing Lucas 2.8.7.0 build. Find it in his thread. Its posted there. It's somewhere in the sea of posts just find it.
3. Then try to clean flash cm 11 build. Then install cm 12.1 build.
4. See if it works.
I don't understand why you face this problem cause well TWRP is very stable.
Well see if it works and get back to me.
Edit :
Saved you some trouble here's the link for TWRP
Link : https://drive.google.com/file/d/0B0WGdtNWubBJVlctNE5PZ1oyQ00/view?pli=1
Its labelled as 2.8.7.0 but its actually 6.0 features of 7.0.

sagar846 said:
1. (JUST SAYING)You can install ota through fastboot. Use the ota file found in root.( There is a thread for this)
2. Try installing Lucas 2.8.7.0 build. Find it in his thread. Its posted there. It's somewhere in the sea of posts just find it.
3. Then try to clean flash cm 11 build. Then install cm 12.1 build.
4. See if it works.
I don't understand why you face this problem cause well TWRP is very stable.
Well see if it works and get back to me.
Edit :
Saved you some trouble here's the link for TWRP
Link : https://drive.google.com/file/d/0B0WGdtNWubBJVlctNE5PZ1oyQ00/view?pli=1
Its labelled as 2.8.7.0 but its actually 6.0 features of 7.0.
Click to expand...
Click to collapse
This is exactly what you should do.
There are several things that don't work as they supposed to do, so follow the steps @sagar846 mentioned.
Sent from somewhere

Oniganon said:
Anyone?
Click to expand...
Click to collapse
cm 12 and 12.1 have some little bugs still but it is useable for daily use

S3 LTE won't go past bootscreen no matter what

So last time my phone was stuck on the device name and model number screen. I solved that issue by flashing TWRP using Odin.
but now the phone would not go past the boot screen no matter what I do. I re-flashed CM11 4 times now, factory reseted and wipe cache and dalvik cache. What should I do?

1. change your thread title please. Need help is not really helpful or directs to your issue.
2. what version of TWRP are you using? The official TWRP 2.8.7.0 does not work. Too long to explain why's that. To fix this issue there are some solutions if you flashed the faulty recovery:
- flash Stock ROM again and stay on TWRP 2.8.5.0
- some users fixed this issue by just flashing another recovery or just flashing a stock based custom rom to get their phone working. You still need to change recovery.
In my case I had to flash stock again and flash my preferred recovery again to get my phone working.

maultasche said:
1. change your thread title please. Need help is not really helpful or directs to your issue.
2. what version of TWRP are you using? The official TWRP 2.8.7.0 does not work. Too long to explain why's that. To fix this issue there are some solutions if you flashed the faulty recovery:
- flash Stock ROM again and stay on TWRP 2.8.5.0
- some users fixed this issue by just flashing another recovery or just flashing a stock based custom rom to get their phone working. You still need to change recovery.
In my case I had to flash stock again and flash my preferred recovery again to get my phone working.
Click to expand...
Click to collapse
So I should flash TWRP 2.8.5.0 and flash CM11 again? (because I don't have stock rom for S3 LTE)
Where can I get stock rom fro S3 LTE I can't seem to find it all, I find is firmwares.
Also, a few questions
1) If I give it into my phone carrier (Optus) would they know that it is rooted?
2) If they know it is rooted and with a custom rom and don't fix it for free is it possible to get it fixed by paying money??

The firmware provided by Samsung is the stock ROM I'm talking about
No, since you tried to flash a ROM through the faulty recovery you need to flash either official firmware from Samsung or a custom ROM based on Samsung stock like AMCHA or N4 Elite. I'd recommend to go with official Samsung firmware. After that go to stock recovery (it will come when you flash official firmware), do a factory reset and let the phone boot once. After that you can flash TWRP 2.8.5.0 and flash any ROM you want.
The new recovery from TWRP is too big for the S3. The S3 recovery is a little over 8MB, the new one needs more and messes up partitions etc. You won't be able to mount /system, /data and the recovery can't read your internal partitions as it should. Go with the way I provided. It seems like a lot of work but it's done in a few minutes.
For your two questions: yes and yes. But you can fix that on your own and don't need your operator or Samsung to get your phone fixed.

Thanks a lot for helping. I was scared to death cause if something happened I would've had to start using a old brick Nokia phones

Is it possible that after I flash the stock firmware, my phone still doesn't boot up?
I am basically a level above newbie, so I don't get what is happening. I see tutorials and do what they tell me to do. sometime I get what I am doing sometime I don't

as i said, after flashing stock, go into the recovery and do a factory reset. The phone will boot then

maultasche said:
as i said, after flashing stock, go into the recovery and do a factory reset. The phone will boot then
Click to expand...
Click to collapse
Ok sorry for doubting you! My phone is working now, thanks a lot for your help

Glad it's working now, you're welcome

I have rooted my s3 via odin and now i wont to flash twrp via flashify. Now i have a bootloop on my s3. How can i recover the phone. i am a noob on s3 and i don*t know how i could go into fastbootmode. Please help me.

what S3 do you have? Which recovery did you flash?

maultasche said:
2. what version of TWRP are you using? The official TWRP 2.8.7.0 does not work. Too long to explain why's that. To fix this issue there are some solutions if you flashed the faulty recovery:
- flash Stock ROM again and stay on TWRP 2.8.5.0
- some users fixed this issue by just flashing another recovery or just flashing a stock based custom rom to get their phone working. You still need to change recovery.
In my case I had to flash stock again and flash my preferred recovery again to get my phone working.
Click to expand...
Click to collapse
I had this problem too! Flashed stock rom, then flashed TWRP 2.8.5.0 (I was using 2.8.7.0) and then flashed cyanogenmod 12 and boom it booted and worked!
Thank you very much!

Stuck on boot animation screen (jumping balls/ waves) regardless of which ROM I use.

Whichever flashing method I use (TWRP, fastboot) Whichever rom I use (I tried clean stock, pre rooted, MM, LP, backups), I can't get past the animation screen. Even restoring a backup through TWRP gets stuck at the same spot. The only ROM that works is LineageOS (based on Android 7.1). I tried wiping various combinations of dalvik cache, data, cache, system, internal storage - still always stuck on boot animation. I tried leaving it for a long time always, the longest was over 2 hours. I feel like I'm missing wiping something since it seems like the issue is going from a 7.1 rom down maybe?
More info: I was using SLiM ROM (MM 6.0.1) for a while but it got extremely slow and poor battery life after a while. I flashed LineageOS for Z3C and it worked fine, but wasn't my cup of tea, so I wanted to go back to stock-based. I figured I'd try eXistenZ (MM 6.0.1). The instructions said to be on 23.5.A.1.291 first, then root it, and then flash the existenz zip. I didn't downgrade to .291 the first time and it didn't work. Second time I flashed a stock D5803_23.5.A.1.291 (which booted up normally). Went through the rooting process (as seen here), and that worked fine. But the next step of flashing eXistenz didn't work. I tried again from the start, but this time I couldn't boot into after flashing 23.5.A.1.291 again. This is where the problem started. I tried Slim and various roms using fastboot, various versions of twrp, and even a 6.0.1 backup through twrp. Always regardless of ROM, it gets stuck on boot animation. Except for LineageOS.

Hi, I'm in the exact same situation, I have Lineage OS 7.1 installed and I can't go back to any custom ROM based on Android 6.0 stock, all I get is always a bootloop. The only other ROM I can install is Sony stock via Flashtool. I really don't know what the problem is, please let me know if you manage to solve this weird problem.

Install old twrp, wipe /apps_log.
Or use emma to get a clean device again.

I solved the issue installing stock Android 6.0 with Flashtool, twrp 3.0.2 and then flashing ROM. :good: