getting bootanimation logo after installing any custom rom.
tried aosp, velidus and flashed all with twrp recovery but still getting the same issue.
delvik, cache wiped but no changes .. please help
starpareek said:
getting bootanimation logo after installing any custom rom.
tried aosp, velidus and flashed all with twrp recovery but still getting the same issue.
delvik, cache wiped but no changes .. please help
Click to expand...
Click to collapse
You should reflash your phone using QPST, unlock bootloader and try again. And make sure to wipe your data before installing any other ROM.
Related
Help me Im stuck in boot loop.. Before this I flashed Merruk kernel 2.0 and creeds 3.2. It works well but after I flashed back to stock rom (DXLA1) I got endless boot loops. Can someone help me T_T
If you have a backup of your creed's fusion with merruk kernel, then restore it via CWM. Or else you'll have to flash back to stock rom via Odin. But first try flashing back to stock kernel.
Sent from my Galaxy Young
wipe data and dalvik
godofping1111 said:
Help me Im stuck in boot loop.. Before this I flashed Merruk kernel 2.0 and creeds 3.2. It works well but after I flashed back to stock rom (DXLA1) I got endless boot loops. Can someone help me T_T
Click to expand...
Click to collapse
go to recovery mode
wike data n cache
all solved.
i have a suggestion for you to do any romming or modding work
firstly, make a backup of your system by CWM,
it is useful;;;;
Remove battery wipe cache factory reset wipe dalvik install new from e.g. creeds 3.2 .
experienced
in my experience i just reflash ROM
tnx
thanks guys
I've tried most of the 4.3 ROMs available. Installed 100% clean with a factory reset and/or wipe system, data, cache & dalvik. After the initial boot if I try to reboot, the phone gets stuck on the first "note2" screen. 4.2.2 ROMs flash boot and reboot fine. I've tried a factory reset after flashing a 4.3 but it still gets stuck. I tried devil kernel... Stuck. I'm using the latest twerp recovery. Please tell me where I fail! Thanks
mrtoast said:
I've tried most of the 4.3 ROMs available. Installed 100% clean with a factory reset and/or wipe system, data, cache & dalvik. After the initial boot if I try to reboot, the phone gets stuck on the first "note2" screen. 4.2.2 ROMs flash boot and reboot fine. I've tried a factory reset after flashing a 4.3 but it still gets stuck. I tried devil kernel... Stuck. I'm using the latest twerp recovery. Please tell me where I fail! Thanks
Click to expand...
Click to collapse
Sorry I made a duplicate thread. I think I've tried more trouble shooting than the other thread. Its your call moderator.
mrtoast said:
Sorry I made a duplicate thread. I think I've tried more trouble shooting than the other thread. Its your call moderator.
Click to expand...
Click to collapse
Maybe try flashing just the rom without any gapps. see if it'll boot for you after a couple reboots. also when u download the files check them again their MD5's so you can confirm that you have a good download.
Clockwordmod superuser app was the key! After the first boot, I ran the app and even though it always wanted to be updated (even after it went through its process) 4.3 ROMs would reboot! I tried probam and pacrom. Each time I flashed new, I had to re update the su or else no reboot. Thanks for your help!
Hello,
I have a unique issue. I'm having a problem installing any custom rom on my t999 (tmobile). I have been using a custom rom for over a year. Always used TWRP. Started with Paranoid Android and for the last few months I've been using PAC-Man (nightly) roms. I was having gps lock issues, I decided to upgrade the modem to a leaked UVUEMJC, this fixed the gps lock issue. But after the reboot, I was stuck on bootloader screen. The only way I could get the rom to work was to backup the rom, flash the system and data, and after that, the rom would work until reboot. I did this a few times until it stopped working. My efs was corrupted, IMEI missing, To recover it, I went into download mode, and noticed in red Warranty bit =1. I used odin to flashed a rooted cf 4.3 samsung touchwiz rom (root66_TMO_T999UVUEMJC). All imei/efs issues were fixed. I decided to try installing a custom rom again, PAC-Man rom, it installed just fine, all EFS/IMEI info was intact, but at reboot, I got stuck on the CM bootlogo. This happens everytime. IF I recover a backup, it gets stuck on the boot logo. I'm using TWRP v2.6.3.
Anybody have any suggestions on how to fix this issue?
Thanks!
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.
Perseus71 said:
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.
Click to expand...
Click to collapse
Thanks for the reply Perseus71. I'll give it a shot!
acedik said:
Thanks for the reply Perseus71. I'll give it a shot!
Click to expand...
Click to collapse
Upgrading to the newest TWRP did the trick! Everything is working fine now. :good:
Thanks for the help!
I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D
Donny Orbit said:
I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D
Click to expand...
Click to collapse
You need to post info about the error
Sent from my SGH-M919 using Tapatalk
It says
E: Error executing updater binary in zip '/external
Error flashing zip '/external_sd/pac_d2tmo-night
I tried flashing the Rom that doc fixed specifically for the T999LTE for the CM10.1.2 also with no avail.
Same problem.
D
wipe Dalvik and Cache before trying the rom again. If
I tried:
different recoveries ( 2 versions of TWRP and 1 other ) , flashing different kernels, wiping cache/dalvik cache/factory reset like 100 times, 3 ROMS that used to work in the past
I didn't try flashing a rom with adb because I can't get it to work, but I don't know if it would help.
The only thing that works is stock ROM with stock kernel and stock recovery. ( ROM from EN MIUI forum )
Everything else just gets stuck on the boot animation ( the cyanogenmod/mokee/... logo )
btw: already tried googling, but all I found is how to fix the problem by installing stock everything but the problem is I hate the stock rom/recovery and If I flash a custom recovery and ROM after fixing it, it just gets stuck again.
Thanks in advance
As you already tried TWRP and not working, here is something u can try...
1)Flash Original miui for redmi 1s
2)then flash philz touch through stock recovery
3)then try to install CM 11 or other ROM
Not sure if it will work for you but you can try
BANG that THANKS button
lanadekat said:
I tried:
different recoveries ( 2 versions of TWRP and 1 other ) , flashing different kernels, wiping cache/dalvik cache/factory reset like 100 times, 3 ROMS that used to work in the past
I didn't try flashing a rom with adb because I can't get it to work, but I don't know if it would help.
The only thing that works is stock ROM with stock kernel and stock recovery. ( ROM from EN MIUI forum )
Everything else just gets stuck on the boot animation ( the cyanogenmod/mokee/... logo )
btw: already tried googling, but all I found is how to fix the problem by installing stock everything but the problem is I hate the stock rom/recovery and If I flash a custom recovery and ROM after fixing it, it just gets stuck again.
Thanks in advance
Click to expand...
Click to collapse
Had you tried to wipe cache, dalvik, data, and system before? I had my problem solved with custom rom
See here, focus what written at Edit section, ignore else. Just curios thou.. Need to be confirmed by others. Thanks
presetz said:
Had you tried to wipe cache, dalvik, data, and system before? I had my problem solved with custom rom
See here, focus what written at Edit section, ignore else. Just curios thou.. Need to be confirmed by others. Thanks
Click to expand...
Click to collapse
Could be the problem I asked the guy/girl who posted it how he fixed the problem. I'll also look for another non-CM based ROM and see if it works.
lanadekat said:
Could be the problem I asked the guy/girl who posted it how he fixed the problem. I'll also look for another non-CM based ROM and see if it works.
Click to expand...
Click to collapse
Just try what i said, wipe cache, dalvik, data, system,
As i recalled (i used twrp) reflash twrp. Leave it without OS
After reboot update twrp to 2.8.6.0 allow to install root, reboot.
And after you enter twrp recovery once again, do clean install as custom rom "how to install" instructed. Hope that help, might have to try other than cm, just for testing it.
Hit thanks if it work, else dont curse on me
presetz said:
Just try what i said, wipe cache, dalvik, data, system,
As i recalled (i used twrp) reflash twrp. Leave it without OS
After reboot update twrp to 2.8.6.0 allow to install root, reboot.
And after you enter twrp recovery once again, do clean install as custom rom "how to install" instructed. Hope that help, might have to try other than cm, just for testing it.
Hit thanks if it work, else dont curse on me
Click to expand...
Click to collapse
oh haha I didn't notice you were the same guyI thought you linked me to someone else's post xD I'll try it, I hope it works!
edit: thanks! reflashing the kernel, wiping everything, then fixing the permissions ( but not the SElinux permissions ) fixed the problem for me I'm back to android 12.1
I'll see if I can close the thread.
Hi,
I flashed the latest AICP 5.0 build...I did this because I don't want 5.1 as yet. The ROM boots up fine after I flashed it. The problem is whenever I try to reboot my phone it is stuck in a bootloop. However I fixed the problem by booting into recover and wiping cache and dalvik cache...So every time I want to reboot my phone, I have to wipe the caches. Can someone please explain why this is happening or suggest a fix. Thanks in advance
Sent from my LG-VS985 using Tapatalk