Related
I was able to get my wife's phone unlocked over the weekend. I threw twrp 2.5.0.0 on there and tried to flash cleanrom. The phone was on the newest bootloader, so I tried flashing the boot.img in fastboot. It just stays on the boot screen forever. I found that there may be issues with newer twrp versions so I tried installing 3 different older version of twrp and all were unresponsive to touch. I could press power once and the twrp lock screen would come up, but that was it. I put 2.5.0.0 back on and it became usable again. Unfortunately I'm not S-Off yet because it says you have to be rooted and my plan was to put CleanRom on and then S-Off. I've verified the MD5 of the ROM zip on the phone. When I am going through the rom install though, and I go through all the options and it starts to install, it literally takes a tenth of a second and says successful. Then when I go to reboot to bootloader, it asks me if i'm sure since i don't have an OS installed. I figured that's just because I haven't flashed the boot img yet, but I am used to rom installs taking a couple seconds on my One XL. I've tried installing the boot.img with Hasoon's all-in-one and it says successful. I've tried installing the bulletproof kernel both via zip format and the boot img and still nothing boots up. What else can I try guys? The wife goes out of town tomorrow morning and needs a working phone. Thanks for your help.
edit: i found the log of the cleanrom install which appears to show the install failing.
utdps said:
I was able to get my wife's phone unlocked over the weekend. I threw twrp 2.5.0.0 on there and tried to flash cleanrom. The phone was on the newest bootloader, so I tried flashing the boot.img in fastboot. It just stays on the boot screen forever. I found that there may be issues with newer twrp versions so I tried installing 3 different older version of twrp and all were unresponsive to touch. I could press power once and the twrp lock screen would come up, but that was it. I put 2.5.0.0 back on and it became usable again. Unfortunately I'm not S-Off yet because it says you have to be rooted and my plan was to put CleanRom on and then S-Off. I've verified the MD5 of the ROM zip on the phone. When I am going through the rom install though, and I go through all the options and it starts to install, it literally takes a tenth of a second and says successful. Then when I go to reboot to bootloader, it asks me if i'm sure since i don't have an OS installed. I figured that's just because I haven't flashed the boot img yet, but I am used to rom installs taking a couple seconds on my One XL. I've tried installing the boot.img with Hasoon's all-in-one and it says successful. I've tried installing the bulletproof kernel both via zip format and the boot img and still nothing boots up. What else can I try guys? The wife goes out of town tomorrow morning and needs a working phone. Thanks for your help.
edit: i found the log of the cleanrom install which appears to show the install failing.
Click to expand...
Click to collapse
Did you flash boot boot.img?
Crypto66 said:
Did you flash boot boot.img?
Click to expand...
Click to collapse
I've narrowed down the issue to the install of CleanROM failing. This may be to twrp 2.5.0.0 but as I've said, earlier versions such as 2.3.3.0 aren't responding to touch for some reason. I don't think 2.5.0.0 is my problem though. I can see it if it didn't wipe properly, but the install is failing due to I/O errors.
But yes, I have tried flashing boot.img. twrp tells me I don't have an os when I try to reboot though, so that's the issue.
Try going to the advanced tab and fix permissions.
Sorry for slow responses, I've got to wait 5 minutes in between posts.
Crypto66 said:
Try going to the advanced tab and fix permissions.
Sorry for slow responses, I've got to wait 5 minutes in between posts.
Click to expand...
Click to collapse
Fix permissions won't work without a rom installed. It fails. And from what I understand anyways, fixing permissions is mostly for apps anyways.
Problem solved. Everyone make sure to use TWRP 2.3.3.1 and only that exact version. Older has touchscreen problems and newer has install issues. Man, this stuff can be frustrating at times.
That's not exactly true. Older versions work just fine, I'm using version 2.2 and it has never failed me.
Older versions aren't working for you because you have a newer touchscreen firmware, you would need to downgrade your touchscreen firmware in order to have touch response. For the same reason, you would not be able to run aosp roms until downgrading. Just thought I'd clear that up.
Sent from my One XL using XDA Premium
So here is my problem. I was rooted on JB,and getting propmts to update to KK. After some research I found out that is it now rootable/unlockable, so I downloaded the .183 update and used RSD Lite to get on the update. That went well. Used towelroot and motoapocalypse to get rooted and unlocked. Also went well. Used Flashify to install TWRP. Well again. Heres where things fell apart. I booted into recovery to backup my stock ROM. After I did that I moved the backup to my SD card like an idiot not knowing it couldn't be restored from there. So I downloaded Validus 5.2 and Gapps. When I flashed them I was stuck in a boot loop on start up. Power down and tried again, still looping. Fastbooted to Recovery to restore my backup, but it was not there cuz it was only reading from internal storage (oops). So I was screwed. Then I read that CM had updated the modem or something and that you had to update stuff to use it. Still not sure about all that, but anyway. I thought maybe that was the problem, so I downloaded an older version of CarbonROM from June that was before the CM changes thinking I would be good now, but when I flashed it the same thing happened. Boot loop. So I went back into fastboot and flashed the RSD Lite stuff again. Rooted with towelroot. Unlocked with motoapocalypse. Verified status code 3 in fastboot. Verified root with Root Checker. Installed Flashify, but I haven't installed a recovery yet. Was TWRP my problem? Why am I boot looping on custom ROMs? Can someone help me out, or point out something Ive missed here?
ilinimud said:
So here is my problem. I was rooted on JB,and getting propmts to update to KK. After some research I found out that is it now rootable/unlockable, so I downloaded the .183 update and used RSD Lite to get on the update. That went well. Used towelroot and motoapocalypse to get rooted and unlocked. Also went well. Used Flashify to install TWRP. Well again. Heres where things fell apart. I booted into recovery to backup my stock ROM. After I did that I moved the backup to my SD card like an idiot not knowing it couldn't be restored from there. So I downloaded Validus 5.2 and Gapps. When I flashed them I was stuck in a boot loop on start up. Power down and tried again, still looping. Fastbooted to Recovery to restore my backup, but it was not there cuz it was only reading from internal storage (oops). So I was screwed. Then I read that CM had updated the modem or something and that you had to update stuff to use it. Still not sure about all that, but anyway. I thought maybe that was the problem, so I downloaded an older version of CarbonROM from June that was before the CM changes thinking I would be good now, but when I flashed it the same thing happened. Boot loop. So I went back into fastboot and flashed the RSD Lite stuff again. Rooted with towelroot. Unlocked with motoapocalypse. Verified status code 3 in fastboot. Verified root with Root Checker. Installed Flashify, but I haven't installed a recovery yet. Was TWRP my problem? Why am I boot looping on custom ROMs? Can someone help me out, or point out something Ive missed here?
Click to expand...
Click to collapse
You have to ensure the ROM you are using is built for the KK kernel. Not all ROMs work with the KK kernel.
Here is a list of ROMs that work with KK:
http://www.droidrzr.com/index.php/topic/48909-kitkat-roms-list/
Anything else will result in what you are experiencing - bootloops.
I recently purchased a Verizon Pixel and successfully unlocked it, installed TWRP RC1, ROM and EX Kernel. I notice, however, that I cannot flash any other zips such as Viper4Android, WETA, etc. This makes no sense to me but after trying to flash these other zips (all of which say successful) nothing is ever installed after a reboot and files do not appear in the expected directory locations. Anyone have any idea what I am missing? I have never seen anything like this before.
Thanks!
bradld said:
I recently purchased a Verizon Pixel and successfully unlocked it, installed TWRP RC1, ROM and EX Kernel. I notice, however, that I cannot flash any other zips such as Viper4Android, WETA, etc. This makes no sense to me but after trying to flash these other zips (all of which say successful) nothing is ever installed after a reboot and files do not appear in the expected directory locations. Anyone have any idea what I am missing? I have never seen anything like this before.
Thanks!
Click to expand...
Click to collapse
After flashings the ROM; do you reboot to recovery before you flash the mods? You need to either reboot to recovery or boot to the system at least once before flashing any mods. When you flash a ROM, it gets flashed to the slot that is currently inactive. The mods will get flashed to slot the is currently the active slot. So, if you don't reboot before you flash the mods, they get flashed to the wrong slot. That's about the only thing I can think of that would cause this issue.
robocuff said:
After flashings the ROM; do you reboot to recovery before you flash the mods? You need to either reboot to recovery or boot to the system at least once before flashing any mods. When you flash a ROM, it gets flashed to the slot that is currently inactive. The mods will get flashed to slot the is currently the active slot. So, if you don't reboot before you flash the mods, they get flashed to the wrong slot. That's about the only thing I can think of that would cause this issue.
Click to expand...
Click to collapse
Yes, have rebooted to recovery numerous times. Zips appear to flash and on reboot to ROM, nothing! Zips with save log features return an error as if nothing is writing to memory.
I have returned to factory image and repeated everything, no change.
I have only booted to TWRP for installing zips, and I haven't installed TWRP on my phone. When booting TWRP RC1, I've had it fail to install zips multiple times. I think the times it failed I didn't get the initial opening information. Honestly I didn't look into it very much, because I just booted Alpha 2, and that installs zips just fine when RC1 doesn't work for me. If someone has rooted their phone, I think FlashFire can probably also install zips.
bradld said:
I recently purchased a Verizon Pixel and successfully unlocked it, installed TWRP RC1, ROM and EX Kernel. I notice, however, that I cannot flash any other zips such as Viper4Android, WETA, etc. This makes no sense to me but after trying to flash these other zips (all of which say successful) nothing is ever installed after a reboot and files do not appear in the expected directory locations. Anyone have any idea what I am missing? I have never seen anything like this before.
Thanks!
Click to expand...
Click to collapse
If you flash a mod from a flash made specially for Pixel, it should work. Other zips will not because the system files for the Pixel are in system/system, not just system.
I downloaded the Android 10 zip file from Oxygen Updater app. Went to settings app, selected local upgrade and installed the update. Since I already had root, and wanted to still have root, I went over to Magisk app, installed magisk (the way to do after installing an OTA) and I also flashed twrp and again installed magisk. After this is where everything went downhill. I rebooted the phone and I had Android 10 installed fine, but I didnt have root access. I wasnt able to use magisk, so to get back root access, I booted to twrp and there I had the problem where my internal memory was 0mb. So I followed a guide online and was able to fix it, but I lost all internal data, so I booted my phone and downloaded the magisk zip and went back to twrp, where again my internal memory was 0mb so I again followed the same steps and this time, I flashed the magisk zip using an otg pendrive. After all the android setup process, I couldnt find the magisk app anywhere. I assumed that my phone isnt rooted and since I was almost fed up at this moment, I thought, I'll manage a few days without root. After a while when I opened netflix it says that it isnt compatible with my device and on checking online, it seems that this problem occurs when the phone is rooted. I again tried to boot to the recovery to flash magisk but now the stock oneplus recovery comes. How do I get out of this situation? I want my phone either properly rooted or even if its totally unrooted its okay. I might have messed up on many things along the way, please help me fix it.
prathk said:
I downloaded the Android 10 zip file from Oxygen Updater app. Went to settings app, selected local upgrade and installed the update. Since I already had root, and wanted to still have root, I went over to Magisk app, installed magisk (the way to do after installing an OTA) and I also flashed twrp and again installed magisk. After this is where everything went downhill. I rebooted the phone and I had Android 10 installed fine, but I didnt have root access. I wasnt able to use magisk, so to get back root access, I booted to twrp and there I had the problem where my internal memory was 0mb. So I followed a guide online and was able to fix it, but I lost all internal data, so I booted my phone and downloaded the magisk zip and went back to twrp, where again my internal memory was 0mb so I again followed the same steps and this time, I flashed the magisk zip using an otg pendrive. After all the android setup process, I couldnt find the magisk app anywhere. I assumed that my phone isnt rooted and since I was almost fed up at this moment, I thought, I'll manage a few days without root. After a while when I opened netflix it says that it isnt compatible with my device and on checking online, it seems that this problem occurs when the phone is rooted. I again tried to boot to the recovery to flash magisk but now the stock oneplus recovery comes. How do I get out of this situation? I want my phone either properly rooted or even if its totally unrooted its okay. I might have messed up on many things along the way, please help me fix it.
Click to expand...
Click to collapse
Looks messy. I don't know the workarounds to get you through. If I was in your place, I would use MSM to reset it to factory settings, update to Android 10 as needed and then use a patched boot image to install magisk. I went that route this time as I really don't need twrp. Search xda for the exact steps to do this. Fairly easy.
life2018.jjn said:
Looks messy. I don't know the workarounds to get you through. If I was in your place, I would use MSM to reset it to factory settings, update to Android 10 as needed and then use a patched boot image to install magisk. I went that route this time as I really don't need twrp. Search xda for the exact steps to do this. Fairly easy.
Click to expand...
Click to collapse
I had alot of problems with the MSM tool the last time I tried to use it. Is there any other way that you could recommend me to start over with a clean slate? Meanwhile, I'll try to get things ready to try MSM tool once again.
prathk said:
I had alot of problems with the MSM tool the last time I tried to use it. Is there any other way that you could recommend me to start over with a clean slate?
Click to expand...
Click to collapse
You can try one of the fastboot stock ROMs: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Options for the fastboot ROMs, as I see it:
- Flash Android 9 fastboot stock ROM, root, and try to update and keep root (like you did before).
- Flash Android 10 fastboot stock ROM, and try to root by flashing patched boot image.
- Flash Android 10 fastboot stock ROM, and leave it unrooted.
prathk said:
I had alot of problems with the MSM tool the last time I tried to use it. Is there any other way that you could recommend me to start over with a clean slate? Meanwhile, I'll try to get things ready to try MSM tool once again.
Click to expand...
Click to collapse
I had similar issues and decided to fastboot oem lock my bootloader after upgrading to Android 10. This reset everything to stock on Android 10 and avoids the issue with Netflix for now. I may re-root at some point but the downsides of being rooted are a bit more glaring now with Android 10 (losing enterprise email for my work, worse version of Netflix, etc).
My assumption is you ran into the same encryption issue I had where the only way out was reformatting and wiping data in the process. Next time I do anything with TWRP/Root/OTA updates I'll be disabling my pin and fingerprints to see if that avoids the issue. I've had it happen 2-3 times now where internal storage is showing 0 and is encrypted with no way to enter my pin.
Just do it all over again, boot to OS install through local upgrade and open magisk, flash twrp first then install magisk OTA and reboot, that way it will go to the other partition.
I'm messing with my POCO X3 NFC a lot, reflashing new ROMs like a madman, messing with super partition trying to enable RW for /vendor, /product, /system... testing backup restore function, etc.
As a part of my flashing routine I always flash magisk (for root and required modules), since release of the version 22 I was using it without any problems on A11 ROMs, even latest A10 RR accepted it - until a point...
Not sure what went wrong in my device configuration, while reflashing it so many times (ROMs, super partition, data backups, encrypted, decrypted storage), but last week or two, suddenly any ROM cooperating with magisk 22 stopped behaved correctly (random freezes, navigation bar missing after reboot, flashed modules not working, loooong boot times).
I remember answering to someone asking if (at the time new) 22 version is working correctly on POCO X3 and my answer was - yes it's working ok. Well - that changed...
I was not able to restore my device to its original state where magisk v. 22 worked correctly, I tried to reflash MIUI base via recovery, or via fastboot, but nothing helped so far... the only thing I didn't try was to use Miflash ... I'm not that desperate, since I figured yesterday that magisk v 21.4 is working correctly (to be honest I looked for the problem anywhere, but in the magisk setup, so a lot of my time spend on finding what's wrong was wasted) ...
So, maybe you will find out that magisk v. 22 behave incorrectly on your phone too, simple try to use a lower version, that helped me...
Also any recommendations how to reenable magisk v. 22 functionality using fastboot or custom recovery?
Have you tried renaming the magisk.apk to magisk.zip and flashing it like in the old days (before magisk basically changed with v22)?
actually yes, I was flashing v.22 renamed magisk apk to zip...
This Magisk issue of longer boot times has been around since last January, see this issue tracker. Also a lot of people face segmentation faults patching their boot.img using version 2200 or higher, see this. I haven't tested this new version, since it is still a canary at this point. Just wait it out or patch your boot.img manually and report there if you get errors.
Hey jeryll, you replied to me in the ArrowOS thread
Did you try the v22 Magisk uninstaller? Maybe somewhere / something left a mark..
I also have a weird warning when flashing Magisk v22
'unable to detect magisk manager apk for bootsigner '
But installer completes successfully and none of the side effects that you are describing.
Beaster said:
Hey jeryll, you replied to me in the ArrowOS thread
Did you try the v22 Magisk uninstaller? Maybe somewhere / something left a mark..
I also have a weird warning when flashing Magisk v22
'unable to detect magisk manager apk for bootsigner '
But installer completes successfully and none of the side effects that you are describing.
Click to expand...
Click to collapse
thanks for the suggestion, can't believe that I overlooked this solution, but for now it seems that magisk uninstaller did its job, and I can use v22 again...
need to do more tests, but for now it seems working, thanks again