So I'm fairly new to rooted android, custom ROMs and the like but I did a bit of research and decided to root my phone and install a pacman 4.3 build on it. While i was able to succesfully root the phone and have had some success with flashing roms I have run into what seems to be a recurring bootloop issue.
Phone: Samsung Captivate Glide I927
Current OS: Stock Android 4.0.4 ICS
I'll start by describing what I have done so far:
Starting with a factory Android 2.3 phone I rooted my device using the following guide
Next I used odin 3.04 to flash CWM 6.0.2.1 to my phone
I then backed up using CWM, wiped data/factory reset, wiped cache, and flashed kick buttowski's PAC 4.3 build and gapps
Upon rebooting I received a samsung logo and then a black screen with no boot (over 15 min)
After some forum investigation I decided my best bet was to try and flash from a stock ICS build
I restored and attempted to flash a stock ICS zip; phone rebooted with a black screen and a pull down menu only
I restored and flashed a stock ICS tar through odin from here
This worked nearly perfectly as I was finally able to fully boot up, although the wifi will not turn on at all - even after some troubleshooting
I backed up the mostly working stock ICS and pressed forward.
First I had to re-flash CWM through odin as my native recovery mode had returned.
I then flashed the PAC 4.3 build with the same black screen error.
I then flashed bubor's PAC 4.3 build and gapps and was able to boot into the PACMAN startup screen at last....short lived as it displayed a pacman, game over, insert coin startup animation indefinitely (over 15 min)
I tried flashing bubor's CM 10.2 Cyanogen 4.3 and gapps instead and was met with a similar issue - indefinite cyanogen startup circle (over 15 min)
I tried flashing Omni 4.4 as well but was not able to even properly flash this one for a reboot.
I have run into this problem trying to flash a number of ROM's where I get stuck in an infinite bootloop. I have restored, wiped data and wiped caches in between each flash attempt and started from a stock ICS build and at this point don't know what to troubleshoot anymore. Can anyone help me?
Ok, I have a Nexus 5. I have been trying to port (Zip style, not Source) the CM11S build for the OnePlus One. I used the 20140615 CM11 nightly build as the base, but it keeps getting stuck at the boot animation. My issues are that I need to know how to activate ADB Debugging through the build.prop so I can get a logcat on first boot (while it's stuck on the boot animation). Also, once I can get a logcat, I would love some help debugging my port. I will upload a copy of my Zip in it's current form, if anyone has any advice, feel free to pass along some advice.
My CM11S Port (AndroidFileHost)
SO......
The title says most of this. I am installing kali linux nethunter with the latest software.
I have tried twice with Cyanogen OS 12.1. I do a clean (factory image) installation, then install the nethunter zip directly after.
POOF! My device will not boot into the bootloader, system, or recovery. it gets stuck on both the recovery and system splash screens and i must use the Color.zip method to retrieve the device from a hard brick.
I have tried installing it over the COS 12.1 xxx2K1 version and i am currently trying to install it over the current release of CyanogenMod 13 (Not cyanogen OS 13)
Has anyone been able to successfully install nethunter on the most recent versions of software?
any help is appreciated. thank you!
Update:
Device still bricks with CyanogenMod 13 as well
Hello, I don't know if I did something wrong, but every time I flash MoKee rom or CM 13 and I reboot my device it turn into Bootloader and when I flash the stock rom it say "Failed to load driver error (19)" after the optimizing aps finish and neither Wifi, sound or signal is working so any solution would be appreciated.
My software status is Modified and my bootloader is unlocked and it's still S-On
I'm also running twrp-3.0.3-5_CPTB-TEST2-hiae as my recovery.
My phone has an unlocked bootloader. Rooted. Custom ROM (lineage OS Android 10). I want to underclock and undervolt it for increased battery but the current kernel is not capable of that. I am thinking of flashing a custom kernel but it appears most custom kernels for my phone were developed a long time before Android 10. Would it be safe to attempt to flash a kernel for an older Android version? If it were to not work, would it result in the possibility of a completely bricked device or would I be able to boot into TWRP and load a backup (do TWRP backups store the original kernel?)?
Thank you.
it would Hard-Brick or Soft-Brick.
Softbrick would happen because mismatching android versions will cause it to not boot.
Hardbrick would (unlikely) happen because custom kernels contain a device tree blob which if corrupted/incompatible would completely hardbrick the device. Not even fastboot would work because the little kernel (the kernel that handles fastboot/recovery/normal boot) for some reason stops working if the device tree blob is not working.
@Ali_Shaikh744
Android doesn't have an own kernel: In the world of Android its kernel is a modified Linux kernel matching a device's hardware. Using a wrong kernel makes the phone unuseable.
As said the Android kernel per se does not exist, but every manufacturer maintains a different Linux kernel for every device. This is partly due to the fact that every manufacturer cooks its own soup and wants to stand out from the competition with a special feature. Sometimes it's the driver of the camera module, which is not freely available, but usually the graphics drivers and many other modules remain closed source.
The Anroid recovery has it's own kernel and you can boot an Android independently of the boot partition ( i.e., booting up/from the recovery partition - that's what you do when you boot in recovery mode ).
xXx yYy said:
@Ali_Shaikh744
Android doesn't have an own kernel: In the world of Android its kernel is a modified Linux kernel matching a device's hardware. Using a wrong kernel makes the phone unuseable.
As said the Android kernel per se does not exist, but every manufacturer maintains a different Linux kernel for every device. This is partly due to the fact that every manufacturer cooks its own soup and wants to stand out from the competition with a special feature. Sometimes it's the driver of the camera module, which is not freely available, but usually the graphics drivers and many other modules remain closed source.
The Anroid recovery has it's own kernel and you can boot an Android independently of the boot partition ( i.e., booting up/from the recovery partition - that's what you do when you boot in recovery mode ).
Click to expand...
Click to collapse
So what you are saying is that boot has its own kernel and recovery also has its own kernel therefore only the boot kernel will be changed if I were to flash, meaning recovery will still be accessible?
Once you install TWRP device's Stock Recovery gets removed. So before flashing a new Linux kernel you might have to flash the full stock firmware to your device to get the Stock Recovery along and remove TWRP thereby.
Why don't you just boot your custom kernel over Fastboot? The bonus is that if it doesn't work, you can just reboot into the working kernel on storage.
xXx yYy said:
Why don't you just boot your custom kernel over Fastboot? The bonus is that if it doesn't work, you can just reboot into the working kernel on storage.
Click to expand...
Click to collapse
I thought old Samsung devices don't support Fastboot? I tried for multiple hours to get my device to reboot into fastboot mode even when I was using the stock kernel, stock OS and stock recovery. If I attempted "adb reboot bootloader" it would restart but go to the OS rather than fastboot. Even trying to get it into fastboot with the new OS doesn't work. I tried rebooting through 1.PC, 2. LineageOS settings, 3. wifi ADB shells through another Android device but nothing worked. Finally I came across information that old Samsung devices don't support fastboot
xXx yYy said:
Once you install TWRP device's Stock Recovery gets removed. So before flashing a new Linux kernel you might have to flash the full stock firmware to your device to get the Stock Recovery along and remove TWRP thereby.
Click to expand...
Click to collapse
But what is the problem if I were to flash using TWRP rather than stock recovery?
Ali_Shaikh744 said:
I thought old Samsung devices don't support Fastboot? I tried for multiple hours to get my device to reboot into fastboot mode even when I was using the stock kernel, stock OS and stock recovery. If I attempted "adb reboot bootloader" it would restart but go to the OS rather than fastboot. Even trying to get it into fastboot with the new OS doesn't work. I tried rebooting through 1.PC, 2. LineageOS settings, 3. wifi ADB shells through another Android device but nothing worked. Finally I came across information that old Samsung devices don't support fastboot
Click to expand...
Click to collapse
That's the 1st time here you say a Samsung phone is involved. Yes, Samsung devices doesn't know of Fastboot mode , the Koreans use the ODIN / Download mode instead.
Ali_Shaikh744 said:
But what is the problem if I were to flash using TWRP rather than stock recovery?
Click to expand...
Click to collapse
As I can see you understood nothing. Sorry to say this.
xXx yYy said:
As I can see you understood nothing. Sorry to say this.
Click to expand...
Click to collapse
Yeah I don't understand. I tried rereading. I still don't understand. Can you please elaborate as my comprehension skills are poor.