Hello, I wanted to ask that I flashed new rom with clean flash (data,system,caache,artcache) and then flashed the new rom. Now the rom gets stuck at bootanimation and stays there . Since rom hasn't booted once enabling usb debugging goes out of the question and when it was booting after the bootlogo i tried to take logcat while boot animation was going on but all I was getting was waiting for device message . I even tried kmesg,and dmesg and It says device/emulator not found. What should i do now ??
I know that i can flash the other rom but i really wanted to help the developer and try the rom . And in the process learn new things . Flashing another rom is always an option but currently i don't want that i want to have a solution . I want to learn that . @Stryke_the_Orc can you help me dear.
DUE TO REAL LIFE TIME CONSTRAINTS I AM UNABLE TO CONTINUE READING AND DIAGNOSING LOGS FOR MEMBERS. PLEASE USE THIS THREAD AS INTENDED, AS A STARTING POINT IN LEARNING TO READ THESE LOGS AND DIAGNOSE PROBLEMS YOURSELF. THANK YOU!
From the first post:
I'd have thought you grasped the concept that if your not getting far enough in the boot process to be recognized by adb, then your not going to get a log "to help the developer". The issue with capturing a logcat during a bootloop is that the boot process has to be far enough along to have started the adb daemon.
Have you saved a copy of the log made during flashing? You should be able to pull that off your device in recovery, right after flashing. At this stage, it's most likely that log will give a clue.
It sounds like there is something more fundamental going on. Go back to the ROM thread and make sure things like flash order, bootloader and recovery versions, additional packages that are/not required are all being followed. Make sure you check md5 (if available) for all downloads packages or that zip verification is turned on prior to flashing. I'm not saying that this is the problem, but it happens to people (more often than you'd think) that the ROM they downloaded wasn't actually for the device they're putting it on. You'll have to figure out what fundamental thing is stopping the boot process.
@ktmom double checked every thing . With all due respect whatever you said i do check that every single time with every single device i have . I am just asking if is there a way to get logs when it is stuck at bootanimation . Recovery logs yes i have but it shows nothing wrong. And if i download wrong file for wrong device i should get twrp error 7 or else , don't you think ??
@tdunham that is the thing . That is why i said since rom is not booted once . Jab debugging and RSA keys goes out of the question .
Edit - found two threads where i can get logs at bootanimation gonna try that.
|how-to, logcat, troubleshooting|