I flashed a custom kernel for my custom rom(unofficial lineage os 16).I've checked that it's for android 9 like the rom and the flash went fine. After flash and reboot it has been stuck on the battery charging indicator. Even after I disconnected the charger it's completely frozen. What do I do now?
Related
I'm currently downgraded my phone back to Jellybean (98.30.1) because the Kitkat firmware was a huge battery hog. I then decided to flash TWRP 2.6.3.0. Everything goes well, and then I flashed the pacman msm8960jbbl rom. After that, the phone no longer goes beyond the splash screen. I can still go to recovery and ap fastboot but no matter how many times i wipe my phone, the results always stay the same. The rom worked the first time, but the next few flashes were a trainwreck. Any idea how to fix this problem?
Try returning to stock ROM with RSD lite after that repeat the process to install the custom ROM
Sent From My Razr M (Bliss Stalk ROM) xt907
Got brand new F320,tried installing two different ROMs (both 5.1.1) and both did not boot,stuck at LG logo and I couldn't even access recovery and when I tried to reflash second time update is stuck at 49% percent. I'm so lost,what do I do?
EDIT: Got it working,it just magically booted into recovery mode and from there I managed to flash CM13.
Hey guys,
I have a little problem with my new OP2.
I unlocked the bootloader and rooted etc.
I installed Paranoid Android and I wanst sure which kernel works on it.
So I tried flashing one for CM13 and one for OOS3, but both of them wouldnt work.
Now Im trying to get back to stock or atleast flash the boot.img from the Paranoid ROM.
I can boot, access the recovery and bootloader. I flashed different boot.imgs (Stock and Paranoid) and recoverys. But none of them helped.
The touchscreen wont react at all. If I boot, if I am in the recovery. It just wont work. Hardware button seems to be fine though.
Any ideas how to fix that?
Try wiping system partition and flash the PA ROM again (and Gapps of course) and it will restore system and kernel back to PA default.
If touch still doesn't work, then you'll probably have to wipe userdata partition as something you installed with the kernels not supporting other than official latest CM13 sources is messing with your system.
You need to flash full stock using fastboot from unbrick guide.
Sent from my ONE A2005 using Tapatalk
google megaunbrick guide oneplus2 and follow that!
didn't got your logic behind flashing custom kernel that too on paranoid android, I can understand that for cm13 as the battery life sucks there but pa easily gives 6+ hrs of sot which any other rom or even a custom kernel can't even come closer to it in my personal experience.
meaning you can try to flash the whole rom through fast boot or use unbrick guide to go full stock.
Hello. After I flash any custom ROM based on Android 7.1 my phone won't boot to OS. Screen is constantly showing LeEco logo and nothing happens. I use TWRP 3.1.1-0.
try just wiping, flashing rom, and gapps and see if it boots
Azgort said:
Hello. After I flash any custom ROM based on Android 7.1 my phone won't boot to OS. Screen is constantly showing LeEco logo and nothing happens. I use TWRP 3.1.1-0.
Click to expand...
Click to collapse
Go back into TWRP, wipe, by swiping should be all that you need to do. Afterwards reinstall your custom ROM and Gaps nano. Shut off phone, and then start. Sometimes it can take a few minutes to load after the initial install. BTW, I use Paranoid 7.3.1, it works great!
Sent from my LEX727 using XDA Labs
Thank you for you replies. Now my phone works as supposed. I successfully flashed Paranoid Android ROM.
Hello,
I have an i9505 LTE International version (jflte) for about 4,5 years, working perfectly with the latest LineageOS until yesterday when my phone suddenly shut off itself (as like as I removed the battery). I tried then to turn it on again but restarted itself after the LineageOS logo appeared. I thought there was something wrong with the OS, so I've booted to recovery TWRP to flash the same OS again. The strange thing is that TWRP stopped flashing at +/- 20% freezing itself. After that I was not able to boot to recovery anymore.
I removed the battery, SIM card and microSD for about three hours. Tried again only with the battery and was able to install LineageOS again. After booting with the fresh installed LineageOS (I formatted the /system /data /cache partitions) the system was very unstable and slow. After 10 seconds the screen went completely pink and it shut off again and never came up (showing me the boot logo and rebooting - bootloop).
I removed the battery again and tried to flash, after one day, with odin the stock firmware. I had no issues while flashing but the OS won't boot. Therefore I flashed the TWRP to the recovery partition and it doesn't work. After 10 minutes without the battery I am able to boot TWRP but when I try to, for example, copy the logs to /data TWRP freezes and I cannot do anything else but hard reboot.
Someone knows what's going on here? Could the eMMC be seriously damaged/corrupted?
The strange thing is that, without the battery for 10 minutes plugged in, I am able to boot to TWRP and navigate through the menu - although after trying to format the /data and /cache partitions TWRP freezes. After a reboot I cannot boot to recovery anymore (it remains stuck on the samsung logo screen with the RECOVERY BOOTING and Set Warranty Bit: recovery headings.
My fathers old S4 has a similar issue, https://forum.xda-developers.com/galaxy-s4/help/s4-i9505-wont-past-screen-boots-t3810088
It seems so strange, I'm currently trying to get the files left on the phone safely of but it crashed when trying to do so and now I can't enter recovery.
But I'm trying to troubleshoot it as good as possible without risking loosing the files, and the strange this is that many S4s seems to have problems with the fact that it is a random restart and then goes into bootloop. But the thing that worries me the most is the fact that you were running Lineage while my father was running stock TouchWiz based on 5.0.1. That leads me to believe that this is a hardware issue, I'm considering unscrewing it and try to troubleshoot it. Going to get my hands on my fathers old extra batteries for his S4 tommorow, will see if that makes a difference.
Did you wipe the /data partition after flashing the stock rom? I had the same issue... After flashing LOS, my phone is bootlooping randomly and i tried to flash stock rom. ODIN does not wipe the data partition after flashing the original stock samsung firmware so the OS can`t boot due incompatible data( The lineage os data with android 7.1.2 is not compatible with lollipop). Try to flash the stock rom again, wait until your device restarts to the robot and hold the vol up+home+on/off to get into stock recovery. Perform a factory reset and then restart. You have to wait a bit (maybe 10 min)