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)
Related
I wanted to get a secondary ROM on my rooted Nexus 5 so I decided to get MultiROM. I had Cyanogenmod 11 (Stable) and Elementalx Kernel with ClockWordMod recovery when I installed MultiROM. I used the MultiROM Manager app and installed it from there. I checked the three boxes that installed MultiROM, the MultiROM recovery and the CM 11 kernel (or else it wouldn't install). It installed and booted my device into MultiROM. It worked! So I booted back into Cyanogenmod. It was stuck at the black screen for a long time, and I did some research and found out that CM had gotten deleted off my phone. I was going to get a new ROM so I plugged my Nexus 5 into my PC and I couldn't access the files for the Nexus 5 on my computer to get a new ROM. I had no ROM's on my phone, so it is basically unusable now. Could someone please tell me if there is a way to fix this?
Boot into recovery and adb push a rom to the sdcard, or side load a rom
Sent from my Nexus 5
Use ADB sideload
If I try to re flash TWRP again my phone gets stuck in a boot loop, I then can only boot into TWRP recovery, then flashing CM 12.1 again fixes my OS not booting, but I'm back to square one again. I have never enabled it in Developer settings before nor is it enabled now.
The only reason this bothers me is because I can't flash updates without modifying a Update file because I keep getting this dumb message "This build is for D6603, etc." even though my device is on that list but keeps saying it's the wrong one, and the "fix" going around disables Micro SD card support which I NEED.
JOSE89178 said:
If I try to re flash TWRP again my phone gets stuck in a boot loop, I then can only boot into TWRP recovery, then flashing CM 12.1 again fixes my OS not booting, but I'm back to square one again. I have never enabled it in Developer settings before nor is it enabled now.
The only reason this bothers me is because I can't flash updates without modifying a Update file because I keep getting this dumb message "This build is for D6603, etc." even though my device is on that list but keeps saying it's the wrong one, and the "fix" going around disables Micro SD card support which I NEED.
Click to expand...
Click to collapse
You need one of the FOTAKernel versions of TWRP.
Sony devices have a unified kernel/recovery in one image, so changing the recovery will change the kernel. However MOST recovery repacks (including the one built-in to CM) have some extra code that checks the FOTAKernel partition for an alternate ramdisk. If you flash one of the FOTAKernel TWRP versions, this will replace whatever recovery is included in MOST kernels out there.
Hello guys,
I've been trying to get MultiROM to work properly for some time now and I've come here as my last resort. I need a kexec-hardboot patch but I can't get it to work without getting in a bootloop (mostly).
What I've already done:
-Unlocked bootloader
-Root
-Installed TWRP
-Installed MultiROM
TWRP works, MultiROM works, booting into CM11s works (stock since purchase). Any other ROM does not because I need a custom kernel.
The MultiROM has cm11.zip (AK kernel I think) with it. Installing cm11.zip causes a bootloop (cannot get into MultiROM at all).
The cm12.zip does more, I CAN get into MultiROM with that, but loading a ROM either freezes upon entering the lock screen and reboots, or freezes during the boot animation.
I've tried AK kernel separately, does get to multiROM, not any other ROM.
Needless to say, I am clueless. I am new to the Android community but am somewhat tech savvy (have used linux before, IT is main course at school, ...).
Any assistance or help is greatly appreciated. TWRP works and so does ADB, so I'm not close to bricking anything anytime soon.
EvoSteven said:
Hello guys,
I've been trying to get MultiROM to work properly for some time now and I've come here as my last resort. I need a kexec-hardboot patch but I can't get it to work without getting in a bootloop (mostly).
What I've already done:
-Unlocked bootloader
-Root
-Installed TWRP
-Installed MultiROM
TWRP works, MultiROM works, booting into CM11s works (stock since purchase). Any other ROM does not because I need a custom kernel.
The MultiROM has cm11.zip (AK kernel I think) with it. Installing cm11.zip causes a bootloop (cannot get into MultiROM at all).
The cm12.zip does more, I CAN get into MultiROM with that, but loading a ROM either freezes upon entering the lock screen and reboots, or freezes during the boot animation.
I've tried AK kernel separately, does get to multiROM, not any other ROM.
Needless to say, I am clueless. I am new to the Android community but am somewhat tech savvy (have used linux before, IT is main course at school, ...).
Any assistance or help is greatly appreciated. TWRP works and so does ADB, so I'm not close to bricking anything anytime soon.
Click to expand...
Click to collapse
Check this thread
http://forum.xda-developers.com/oneplus-one/general/guides-mmwolverines-opo-mods-tips-tricks-t3027926
The issue:
Phone is boot looping regardless of ROM. Additionally, if I use the torch, I have to reboot the phone to turn it off, and the camera is unable to load. -- The boot looping isn't always during the boot cycle, but sometimes a few minutes after the phone starts.
Backstory:
A few days ago my phone started to randomly boot loop. I was running one of the OTA of cm 12.x with TWRP at the time. After the issue started, I originally thought it was due to the upgrade to cm 12 and tried reverting to cm 11. This did not correct the issue, so I've tried a few other things since.
First I tried the method in this thread: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 however, while the batch job was running, the device became unresponsive. After an hour of waiting I unplugged the device which sort of hard bricked it.
To recover from this brick, I tried the method in this forum: https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
This allowed me to boot my phone into color OS with no apparent issues (I didn't test extensively). Following this, I tried using fastboot to put XNPH22R on it by flashing the files individually following the first guide.
I am currently left with XNPH22R, and the phone appeared to be working fine - the flashlight bug was fixed, and it wasn't boot looping. Unfortunately, while I was setting it up (I didn't do it at first because I wanted to test first), it began to boot loop again.
Does anyone have any advice? Additionally, while flashing the individual image files, I erased and formatted them first to give myself a clean install. Are there any other ones I may have missed that could be cleaned to fix this issue?
Thanks.
EDIT: Now my phone is freezing up in twrp as well. Additionally, the bootloader is locked and fastboot oem unlock is not unlocking it, and there is no OS because it froze during the flash from twrp.
Naturally the first I would ask you to do is:
1. Flash a Custom Recovery
2. Update firmwares to the latest ones (I guess May)
3. Update your ROM to latest Stock ROM or a Stable Custom ROM.
I have a strong feeling that mismatched firmware version could be causing this problem. I had a bootloop problem due to that.
Sent from my A0001 using XDA Free mobile app
tr.supradeep said:
Naturally the first I would ask you to do is:
1. Flash a Custom Recovery
2. Update firmwares to the latest ones (I guess May)
3. Update your ROM to latest Stock ROM or a Stable Custom ROM.
I have a strong feeling that mismatched firmware version could be causing this problem. I had a bootloop problem due to that.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I agree that it is likely a mismatched firmware given the issues I have seen with the torch and camera. However, I think I may have a misunderstanding of what the firmware is on Android. I thought it was the underlying linux kernel, which from what I'm seeing is the boot sector. If this is the case, wouldn't the fastboot flash boot boot.img replace the firmware with the appropriate version for the ROM? If not, can you please explain this further? Usually my experience with custom roms stops at loading a custom recovery and then simply flashing zip files from that.
Additionally, I have twrp as my recovery.
I decided it was finally time to upgrade to the newer LineageOS 17.1 branch nightlies from my previous installation of 16, rebooted to recovery and sideloaded lineage-17.1-20201013-nightly-enchilada-signed.zip onto it from https://download.lineageos.org/enchilada .
After doing so it appears the recovery successfully updated, it has a new purple skin it didn't have before, however the actual ROM won't start. Instead it goes to fastboot mode and asks whether I want to Start/Restart/Recovery/etc, but I can only get into fastboot or recovery mode.
I've tried flashing older nightlies, but even with 20200922 the issue was still there. I did notice there was a ton of updates in that specific release so I wonder if anything is broken in there.. unfortunately that's also the oldest available nightly so without compiling my own there's no way I can test whether older ones are functional, unless someone here has an older version available perhaps.
I did notice doing adb sideload only makes it go to 47% before the phone goes to installing it, however maybe that's normal, I haven't used it in a while so I don't know for sure. I tried using ADB to push an image onto /tmp, however the new recovery only seems to have 'Apply from ADB' as option so I can't actually install it from there.
Does anyone have any ideas I could try, or perhaps an older LineageOS nightly from before 09-22 laying around somewhere? Any help or suggestions much appreciated!
PPS: Of course I forgot to mention but I also did a factory reset, but that did not help. unsure what else to try besides compiling a rom myself or trying other roms from the forums here, though I'd very much prefer having LineageOS..
I found the reason. I had to install the official Oneplus 6 ROM first, probably to get the right vendor binaries/kernel modules/drivers.
This is what I did:
- fastboot boot TWRP ( TWRP can be found here https://twrp.me/oneplus/oneplus6.html )
- wipe -> advanced wipe -> all the things (technically optional but if you want to get rid of GApps etc this is needed)
- adb sideload official OnePlus 6 'Oxygen' ROM ( https://www.oneplus.com/global/support/softwareupgrade/details?code=PM1574156173727 )
- reboot, fastboot boot TWRP
- run the 'copy partitions' zip from https://androidfilehost.com/?fid=8889791610682929240 to copy Oxygen to the other A/B partition
- Install latest build from https://download.lineageos.org/enchilada
- reboot, optionally boot TWRP again and install GApps, also optionally install TWRP, reboot, enjoy.
PS: Please note that after this you shouldn't switch A/B partition without first flashing another nightly or something over it, i.e fastboot boot twrp and install latest lineageos again, otherwise you'll end up booting the vanilla Oxygen rom