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
Related
Hi,
I have successfully installed bootZ3monxtest01.img and CM12 nightlies for my Z3, and the android experience itself is fine and without issues...
however, I have several issues regarding my recovery:
- reboot to recovery feature from android never works, I have to boot cold (from power down first), and it only works when I enter a cable during boot and press the 'up' button.
- no matter whether I install TWRP, CWM or CM own's solution, the CM version seems to be installed after a normal reboot. The feature "Update Cyanogen recovery" in Developer options is disabled though
- attempts to update android OTA fail, and do not even begin. Updating from recovery is the only thing that works for now.
(and that's unrelated to having to changing the device name from 'z3' to 'D6653' in the updater script, which still appears to be necessary).
I imagine I've done something wrong regarding installation of recovery, or perhaps something in earlier stages... but I really don't know what (and didn't have any issues following installation howto's)
Anybody know what's wrong for me?
Kind regards,
Hi. I had the same problem with CM12. I think I read somewhere that it's a bug in cm recovery. It's just not working as it should.
I used flashtool to revert back to kitkat, rooted, flashed dual recovery, restored drm keys and then updated to rooted Lollipop. That was the only way.
Edit: don't forget to relock you're bootloader.
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.
Hi Guys,
I have an AT&T One X that I unlocked and flashed TWRP recovery on. I have been using this for quite some time with a stockish HTC Custom ROM. However I wanted to see what the latest Cyanogenmod was like. So I flashed the latest snapshot after first flashing the specific recovery software linked on the cyanogenmod page. So far so good. Device booted up and was ready for use.
I wanted to install Gapps afterwards so I went to OpenGapps to download the aroma installer. However the Cyanogenmod recovery software doesn't seem to support this. So I wanted to go back to TWRP. Instead of doing the usual flashing in the recovery I decided to use the TWRP Rommanager since it seemed like a quick fix. Ooh how wrong I was.
After installing the recovery through TWRP manager I accepted the request of TWRP manager to reboot to recovery. However my phone greeted me with a black screen afterwards. Up till now I haven't seen anything pop up onscreen anymore and I tried numerous things. The only strand of hope I still have left as that when connecting to my pc I'm still able to see the phone is in fastboot mode.
However when trying to execute a new flash of my recovery partition my phone keeps saying "fastboot error; remote not allowed". I've searched through numerous articles without a solution up till now. Is my phone too far gone to revive?
Doesn't seem like a straightforward fix as no responses are coming in. Maybe an indication if there would be a fix is appreciated as well.
Hello. I have had my phone rooted for some time now, and I have always used TWRP.
I am currently on CM13 (MM) and I also installed TWRP 3.0.2.0, but I have been having a problem ever since i let my phone die Completely (i had an xposed mod that prevented the auto-shutdown) and ever since then I have been unable to use my TWRP. When i use CM's recovery, it somewhat works, but its a huge pain in the ass to use. I have tried every TWRP iteration down to 2.8.7 and they all have the same symptom: I see the pink Entering recovery, and then the TWRP splash screen (of whatever version i flashed), then without notice it will reboot itself into the operating system.
Hi everyone,
I've been trying to get TWRP to stick for a while now, but still haven't been able to get it to install. A while ago I managed to flash Resurrection Remix using Lineage recovery which does work, but since Lineage recovery is quite limited, I really wanted to get TWRP to work. Since TWRP 3.5.0 released yesterday, I gave it another shot hoping that they fixed the issue, to no success.
I can get into TWRP just fine by temp booting it with fastboot, but after flashing the installer zip, any recovery that was previously installed gets wiped and the device will reboot when trying to get into recovery. I can still boot my phone otherwise.
The steps I took to get to this point:
Unlocked bootloader
fastboot boot twrp.img
Decrypt using screen pattern (successfully)
Flashed twrp installer zip (no error messages, process finishes successfully)
Reboot into recovery (both from twrp and bootloader at a later point)
Things I've tried:
Use a different TWRP version. Same problem as described above on both 3.4.x and 3.5.x, can't get it to decrypt on lower versions due to Android 10.
Install to recovery ramdisk, this just breaks things even more, probably because it's an A/B device?
Try a different recovery. Lineage recovery works just fine, but it's very very limited. Would really like to get TWRP working.
Trying to flash the zip results in no error messages, but any previously installed recovery gets wiped and magisk is uninstalled, which leads me to believe that it has done at least something to the boot img.
Thank you in advance.
EDIT 25.02.2021:
- Attached TWRP log
EDIT 12.03.2021:
- Log didn't want to attach, they can be found here: https://pastebin.com/awnhHDBU
Same question here. It seems that you can only boot from TWRP, not install it.
Tried installing again today, to no avail. However, I was smart enough to save the log this time. I have attached it to the main post, would be much appreciated if someone could check it out.