Hello,
hopefully someone could help me solve my issue.
i've installed the latest nightly of cm 12.1 today overwriting my previous installation of cm11 with a build from january.
the recovery i used so far was twrp.
after upgrading cm to 12.1 i can no longer access the recovery. the phone shows a black screen and reboots when i press the power button.
i've tried reflashing current and older (2.7) versions of twrp with odin but with no success.
NiteFlame1003 said:
Hello,
hopefully someone could help me solve my issue.
i've installed the latest nightly of cm 12.1 today overwriting my previous installation of cm11 with a build from january.
the recovery i used so far was twrp.
after upgrading cm to 12.1 i can no longer access the recovery. the phone shows a black screen and reboots when i press the power button.
i've tried reflashing current and older (2.7) versions of twrp with odin but with no success.
Click to expand...
Click to collapse
You should have flashed official lollipop first, to get the latest bootloader. And you should begin there. And then flash twrp for your rom and cm12.1 using twrp.
Use a cm12.1 rom from development forums instead. E.g temaseks.
so just to make it clear for the dummy kind of user which i seem to be the necessary steps are:
1. getting a stock lp rom and flash this
2. flashing a custom recovery
3. flashing custom rom (e.g. temaseks or standard cm12.1)
Does the Phone have to be rooted for these steps? It looks like it has lost its root status with the update to 12.1 or when i tried to re-flash the broken recovery partition.
thanks for your patience.
Heya guys, I've been rocking my OnePlus 2 for a while. I was wanting to install a newer ROM on it but I seem to run into some problems and I just can't figure it out.
I tried to install several roms (which are all based on 7.1 android) and I seem to be getting the same error on all of them: E:Error executing updater binary in zip '/sdcard/crDroidAndroid-7.1-20161128-oneplus2.zip' This was when I tried the crDroid mod, of course. The only ones that seem to work are CM13 and OxygenOS 2.2.
Couldn't really find a good solution for this when I google'd. I tried carefully wiping what I had to but that didn't seem to help.
I also tried updating my recovery, but when I try to update my recovery it just freezes when I boot. I tried this using fastboot and or via TWRP. I'm currently using version 2.8.7.0 of TWRP because the lastest version of TWRP bricks my recovery. I've also tried the blue spark TWRP and TWRP-hybrid, they don't seem to work either, my phone just stays on the 1+ logo. I have to flash the old version of TWRP back onto it using fastboot to get a working recovery.
Anyone have a solution for me?
EDIT: I have a Chinese OnePlus2, the A2001.
EDIT2: Forgot to mention something that might be critical to the problem: I did update from OxygenOS 2.2.1 to the latest as of now, 3.1. This removed my TWRP recovery and I couldn't get the new one to work, which made me install 2.2.1 again. I've seen people mention some problems with 3.1 so this might be the cause of it?
Hello. a little while ago I restored my Huawei p9 lite nougat L31C440B380 rom from a bootloop thanks to tw1st3d83's P9 Lite Toolkit but since then i haven't been able root it again properly using magisk and other supersu apps because when i boot up music and sound don't play on my apps and videos on apps don't work at all, yet when i unroot my phone works normally, which is strange as i've rooted many times before with no problems. I'd been having some issues with magisk then due to installing and then deleting the viper4arise mod as apps didn't show in my drawer and magisk modules as well as the manager started to malfunction frequently. I looked around for anything that might help me fix this and came across HassanMirza01's P9 Lite elite kernel (All Variants CxxB3xx Phh Superuser v9 version and MagiskSU v10 version based on the b380 Rom) and decided to try it out. I used a special modded version of oldroid's twrp (TeamElite) https://www.androidfilehost.com/?fid=889764386195914200 to flash the kernels, the phh Superuser 9 version, https://www.androidfilehost.com/?fid=529152257862726224 , and the magiskSU 10 version, https://www.androidfilehost.com/?fid...0096634768996. Because they were pre-rooted, I assumed at the time i'd be able to solve my root problem.
When i was using the kernel I noticed everything ran more smoothly than usual but sound and video still weren't working. Because the kernels were pre-rooted before i installed, i think they may have modified the boot image in such a way that even when i completely format data with twrp and do an advanced wipe, then restore the factory images including the stock boot image i extracted from the B380 rom it starts up normally but gets stuck on the loading screen. At first I thought it needed time to load so I left it to charge overnight as the battery was pretty low but i when i woke up the next morning it was still on the Huawei logo. i don't think the kernel has an uninstaller or if there's one i can flash that doesn't have root. If i flash the boot image that I patched earlier with magisk, everything loads fine but i'm still faced with the same problems with no video or sound. I've been thinking of just reflashing the stock images and then relock the bootloader so i can do three button "dload" method for a clean install of my B380 rom as i've tried to use it before and failed as i get this error message before it finishes:
write radio image...
32K crc checked failure
E:unknown command [errno]
update_huawei_pkg_from_ota_zip: update from zip failed
Updater process ended with ERROR: 7
But seeing as how the kernel has altered the boot image I can only use the boot image that I patched with magisk or supersu.
I'm definitely sure that the method won't be able to work on a phone that's rooted but what i'm more worried about is that something goes wrong and i end up in a bootloop with no way to use adb to unlock the bootloader or use recovery, pretty much bricking the device. I've looked around for other kernels i might be able to flash and restore my device like Smoky Kernel and Rusty Kernel but they didn't work at all as opposed to the Elite Kernel. Can I lock the bootloader with a rooted phone and my reinstall my stock rom with the three button method or is there another way i could go about this? I'm asking this way because every time i unroot with either magisksu elite kernel or my magisk boot image the phone will always bootloop. The TWRP version I'm on, 3.1.1-0 isn't very useful at the moment compared to when I was on MM because when I had a problem I just flash and forget, but as the stock rom has two files it's a bit harder for me to get the hang of it so i would be very grateful for where to go from here.
This may sound dumb but I have noverity and twrp already installed and cannot get it back to stock by installing P852A12V1.2.0B12_RM_data.zip. Usually I can get this done in the recovery and update the zip file but it doesn't show me an option anymore. Is this possible with TWRP?
Currently on LOS 14.1 since that is the only thing I can load up (sure other roms work too but more interested on stock for Wi-Fi calling). I have tried tdm B14 boot stack and stocksystem files but I get hung on ZTE startup.
Anyone have any insights?
Update:
Got it working. Crucial step was to make system read-only in TWRP.
Hey, so I wanted to install a custom ROM (LineageOS 14.1) anyway, I found this site that was showing me how to but first i needed to unlock bootloader and install TWRP, i clicked on the steps for that and it brought me here:
https://devsjournal.com/how-to-root...to_unlock_Bootloader_of_Motorola_Moto_G4_Plus
I followed all the steps on that page, even installing the SuperSU, but this is where the problem began. After rebooting from installing SuperSU i was stuck on a black screen (not even backlight) and a white blinking LED light next to the fingerprint scanner. I began to look around for a fix and i found this site:
https://forum.xda-developers.com/2015-moto-g/help/problem-boot-flashing-supersu-t3507127
I followed the steps but nothing worked. Then i tried this:
https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
but that still didn't work. Flashing a new ROM does not fix the problem, and it seems nothing will. I am able to get into the bootloader and I am also still able to get into TWRP but i can't boot into ROM. I need help.
I should have attached this before but here is a picture of the bootloader. After typing in all those command the only thing that changed was the yellow text that says Software status: Modified
1) What ROM are you trying to flash onto your device?
2)The issue here appears to be that you've rooted on the stock ROM - what those pages don't mention is that those steps only work for Marshmallow stock ROMs - attempting to root on the stock Motorola Nougat ROM may cause you to bootloop and you need a custom kernel to root on stock Nougat ROMs. One way around this may be to flash a custom kernel such as ElementalX 2.0.1 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 then attempt to boot. You can boot to TWRP, connect your device to your computer, which should show up as internal storage. There, you should be able to copy a download of the custom kernel to your device and flash through TWRP. If you made a backup before rooting, you could re-flash just the boot (kernel) partition to restore a clean stock kernel then attempt to flash the custom kernel and then root.
3)You could alternatively boot to TWRP and flash Lineage. You do not need root at all to flash custom ROMs - just an unlocked bootloader. Root for installing custom ROMs is unnecessary. Be aware to flash the Lineage build matching your TWRP (i.e. 32 bit Lineage if you're running the official TWRP or any other 32 bit TWRP recovery for athene, 64 bit Lineage only is flashable with the 64 bit TWRP, else you'll get an error 255 on flashing). As always, flashing a new custom ROM requires a /system, /data and /cache wipe at least - possibly an internal storage wipe, so back up to your computer or the cloud as necessary.
4)As for the modified status, that may have been from rooting on the stock kernel. That can disappear if you were to flash a stock OTA onto your device, but that would mean flashing the NPJ25.93-14.7 Sept 2017 security patch stock ROM (latest leak we have for XT1644 devices as far as I recall), and then taking OTA updates up to April 2018 which may be risky.
echo92 said:
1) What ROM are you trying to flash onto your device?
2)The issue here appears to be that you've rooted on the stock ROM - what those pages don't mention is that those steps only work for Marshmallow stock ROMs - attempting to root on the stock Motorola Nougat ROM may cause you to bootloop and you need a custom kernel to root on stock Nougat ROMs. One way around this may be to flash a custom kernel such as ElementalX 2.0.1 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 then attempt to boot. You can boot to TWRP, connect your device to your computer, which should show up as internal storage. There, you should be able to copy a download of the custom kernel to your device and flash through TWRP. If you made a backup before rooting, you could re-flash just the boot (kernel) partition to restore a clean stock kernel then attempt to flash the custom kernel and then root.
3)You could alternatively boot to TWRP and flash Lineage. You do not need root at all to flash custom ROMs - just an unlocked bootloader. Root for installing custom ROMs is unnecessary. Be aware to flash the Lineage build matching your TWRP (i.e. 32 bit Lineage if you're running the official TWRP or any other 32 bit TWRP recovery for athene, 64 bit Lineage only is flashable with the 64 bit TWRP, else you'll get an error 255 on flashing). As always, flashing a new custom ROM requires a /system, /data and /cache wipe at least - possibly an internal storage wipe, so back up to your computer or the cloud as necessary.
4)As for the modified status, that may have been from rooting on the stock kernel. That can disappear if you were to flash a stock OTA onto your device, but that would mean flashing the NPJ25.93-14.7 Sept 2017 security patch stock ROM (latest leak we have for XT1644 devices as far as I recall), and then taking OTA updates up to April 2018 which may be risky.
Click to expand...
Click to collapse
Yea i should have been more clear on what ROM i was trying to flash, i wanted to flash LineageOS but when i try to flash it and boot i still get the same problem, the led light just blinks over and over until i unplug the phone or go into the bootloader. Maybe i have the wrong version of something? All i know is that the phone was working perfectly fine before and it is the XT1644 model. It had all its updates up to date but i just wanted to install LineageOS, i do now realize that you don't need root to flash a custom ROM but also i don't know where to find files for the kernel you are talking about, I also did not make a backup (lets just say im pretty stupid and i know i should have). If you have any info or need any more to further assist me, let me know. Thank you for responding!
So i tried flashing the custom kernel and it looked like everything was working, but the phone still won't boot, it just flashes the LED light, also i reinstalled LineageOS after wiping all the cache and internal storage and stuff but it still hasn't worked.
Hey, i got good news, i was able to get the phone to boot by downloading and following these steps here: https://forum.xda-developers.com/mo...e-npj25-93-t3549369/post70843323#post70843323
The phone now is working and i will attempt to install LineageOS once more. Thank you for you help!