Related
I'm having a strange problem when I flash kernels (tried for Xcelerate and Beast kernels on both CM11, CM12.1), TWRP 2.8.6 gives the "e:Zip signature verification failed: 1" error message . The zip files for the kernels are perfectly fine - tested fine using archiver app and I don't face the same problem when flashing roms (MIUI/CM11/12/etc).
Turning zip verification off in TWRP allows the flashing process to complete normally but checking the kernel version under settings shows that it hasn't changed (still shows kratos/jsevi for CM11/12.1).
Any ideas?
barrack1 said:
I'm having a strange problem when I flash kernels (tried for Xcelerate and Beast kernels on both CM11, CM12.1), TWRP 2.8.6 gives the "e:Zip signature verification failed: 1" error message . The zip files for the kernels are perfectly fine - tested fine using archiver app and I don't face the same problem when flashing roms (MIUI/CM11/12/etc).
Turning zip verification off in TWRP allows the flashing process to complete normally but checking the kernel version under settings shows that it hasn't changed (still shows kratos/jsevi for CM11/12.1).
Any ideas?
Click to expand...
Click to collapse
FYI, i never ticked/marked the zip signature while flashing beast or xcelerate kernel, and all of them works fine with the rom.
after clean install, i reboot to rexovery and i flash the kernel and reboot, never wipe anything
presetz said:
FYI, i never ticked/marked the zip signature while flashing beast or xcelerate kernel, and all of them works fine with the rom.
after clean install, i reboot to rexovery and i flash the kernel and reboot, never wipe anything
Click to expand...
Click to collapse
I did a clean install several times with different rom-kernel combinations and I keep running into the same problem. I think its related my other problem of looping in recovery (twrp) after performing a factory reset in cm11/12.1.
barrack1 said:
I did a clean install several times with different rom-kernel combinations and I keep running into the same problem. I think its related my other problem of looping in recovery (twrp) after performing a factory reset in cm11/12.1.
Click to expand...
Click to collapse
did you flashed twrp recovery.img to boot option, instead of recovery option?
if that case, youll get looping to twrp, instead of system. IMO
presetz said:
did you flashed twrp recovery.img to boot option, instead of recovery option?
if that case, youll get looping to twrp, instead of system. IMO
Click to expand...
Click to collapse
I don't know what you mean there. I flashed twrp using fastboot.
I have no problems with using TWRP to flash customs roms multiple times (except for flashing kernels).
edit-
Steps I took to flash kernel-
- start twrp recovery and wipe everything except for external sdcard and usb otg
- flash rom cm11/12.1/etc
- wipe cache/dalvik
- reboot to system and check that everything is fine etc
- power off and start in twrp to flash kernel
- get error msg as stated in my OP
barrack1 said:
I don't know what you mean there. I flashed twrp using fastboot.
I have no problems with using TWRP to flash customs roms multiple times (except for flashing kernels).
edit-
Steps I took to flash kernel-
- start twrp recovery and wipe everything except for external sdcard and usb otg
- flash rom cm11/12.1/etc
- wipe cache/dalvik
- reboot to system and check that everything is fine etc
- power off and start in twrp to flash kernel
- get error msg as stated in my OP
Click to expand...
Click to collapse
sorry, just my experienced with twrp looping that i encountered once.
i dont know if it help, but i moved the kernel.zip in the internal storage before i flashed it.
edit: just curious, before you flashed kernel, had you double checked, if the zip verification was unmarked in twrp>setting ?
presetz said:
sorry, just my experienced with twrp looping that i encountered once.
i dont know if it help, but i moved the kernel.zip in the internal storage before i flashed it.
edit: just curious, before you flashed kernel, had you double checked, if the zip verification was unmarked in twrp>setting ?
Click to expand...
Click to collapse
I think so but I make sure zip verification is always toggled on in the install menu. There is no reason to turn it off since verification is very quick and doesn't cost anything.
But even when I turn it off, the kernel doesn't seem to have changed from what I see in the kernel version info under settings after I reboot the phone - as stated in the OP.
barrack1 said:
I think so but I make sure zip verification is always toggled on in the install menu. There is no reason to turn it off since verification is very quick and doesn't cost anything.
But even when I turn it off, the kernel doesn't seem to have changed from what I see in the kernel version info under settings after I reboot the phone - as stated in the OP.
Click to expand...
Click to collapse
okay, last i remembered,i once encountered no changed on kernel, but i saw some posting at xcelerate thread, that it had to flashed on top of stock boot.img, the file extracted from the rom.zip,
flashed the boot.img first then straight to flash the kernel.zip.
if you already tried that and still had the issued, then im wondering why too...
presetz said:
okay, last i remembered,i once encountered no changed on kernel, but i saw some posting at xcelerate thread, that it had to flashed on top of stock boot.img, the file extracted from the rom.zip,
flashed the boot.img first then straight to flash the kernel.zip.
if you already tried that and still had the issued, then im wondering why too...
Click to expand...
Click to collapse
Is the boot.img from CM11/12.1 or miui rom? From what I understand, the boot.img flash is only if the kernel is other than cm11/12.1 like Beast/Xcelerate/Carbon. Since I'm only on on CM11 or 12.1 on a clean flash without any other modifications theres no point in flashing boot.img (from CM11/12.1).
barrack1 said:
Is the boot.img from CM11/12.1 or miui rom? From what I understand, the boot.img flash is only if the kernel is other than cm11/12.1 like Beast/Xcelerate/Carbon. Since I'm only on on CM11 or 12.1 on a clean flash without any other modifications theres no point in flashing boot.img (from CM11/12.1).
Click to expand...
Click to collapse
yup, thats true, i have encountered that after clean install while still on cm12 and the procedure was worked for me.
presetz said:
yup, thats true, i have encountered that after clean install while still on cm12 and the procedure was worked for me.
Click to expand...
Click to collapse
Err what do you mean? Encountered what? Did you still have to flash boot.img from cm11/12.1 or miui?
barrack1 said:
Err what do you mean? Encountered what? Did you still have to flash boot.img from cm11/12.1 or miui?
Click to expand...
Click to collapse
sorry my mistaken, thought that my problem was the same with yours with no changed kernel after flashin custom kernel while back at cm12
and no, i didnt need to flashed boot.img first before custom kernel ever since cm12.1 clean install
Dear XDA Members,
I currently run stock 5.1.1 (14.6.A.1.236) with no modifications whatsoever and a locked bootloader.
I would like to install a custom rom (PAC-ROM LP-MR1 5.1.1) on my Z1C.
I did some research and these are the steps i came up with:
1. install sdk and drivers
2. unlock bootloader
3. fastboot flash recovery "fota.img" (shouldn't it specify somehow that i need it to be flashed on the fota partition?)
4. factory reset/wipe
5. install custom rom + gapps
Coming from a locked bootloader a fully stock phone is there anything else i need to do like a new bootloader or something?
Also I'll be doing it through Win 10 64bit, I hope that isn't a problem.
Any advice will be highly appreciated.
Thank you very much
ursidae1 said:
Dear XDA Members,
I currently run stock 5.1.1 (14.6.A.1.236) with no modifications whatsoever and a locked bootloader.
I would like to install a custom rom (PAC-ROM LP-MR1 5.1.1) on my Z1C.
I did some research and these are the steps i came up with:
1. install sdk and drivers
2. unlock bootloader
3. fastboot flash recovery "fota.img" (shouldn't it specify somehow that i need it to be flashed on the fota partition?)
4. factory reset/wipe
5. install custom rom + gapps
Coming from a locked bootloader a fully stock phone is there anything else i need to do like a new bootloader or something?
Also I'll be doing it through Win 10 64bit, I hope that isn't a problem.
Any advice will be highly appreciated.
Thank you very much
Click to expand...
Click to collapse
First things first... Root. If you already did that then you're on the right track.
1. If you're not doing major development stuff, don't install the whole sdk. See here - http://forum.xda-developers.com/showthread.php?p=48915118 There may be issues you'll have to work with on newer versions of Windows. I haven't done it on anything later than 7. Keep in mind, though, that you won't need the computer to flash your boot img or rom, but you will need it to unlock the bootloader.
2. -
3. You can do this with an app called Rashr on your phone with root. Just download a recovery img, then open Rashr and follow the instructions.
4-5. Boot into recovery, full wipe, (system data and caches), flash rom zip and gapps zip. Maybe best to not flash more than that at once to start, in case there's a problem and you have no way to figure out what it is.
BTW, PacMan is a great choice. I've been using it for months.
levone1 said:
First things first... Root. If you already did that then you're on the right track.
1. If you're not doing major development stuff, don't install the whole sdk. See here - http://forum.xda-developers.com/showthread.php?p=48915118 There may be issues you'll have to work with on newer versions of Windows. I haven't done it on anything later than 7. Keep in mind, though, that you won't need the computer to flash your boot img or rom, but you will need it to unlock the bootloader.
2. -
3. You can do this with an app called Rashr on your phone with root. Just download a recovery img, then open Rashr and follow the instructions.
4-5. Boot into recovery, full wipe, (system data and caches), flash rom zip and gapps zip. Maybe best to not flash more than that at once to start, in case there's a problem and you have no way to figure out what it is.
BTW, PacMan is a great choice. I've been using it for months.
Click to expand...
Click to collapse
Thanks a lot for your reply.
I was reading on the cyanogen mod wiki how-to for our phone and it doesn't require a prior root.
I did those steps on my xperia m and it worked and i had never rooted it, the only difference is that i flashed cyanogen recovery and install cm12 which basically roots the phone and then flashed fota recovery.
Should i go this way again to gain root or would you recommend an easier root method for my stock build which is the newest.
If you recommend another root method when should it occur? prior unlocking the bootloader or afterwards?
Thanks
If this is your first time unlocking your bootloader, make sure you backup your DRM-Keys! You need to be rooted for that.
They are lost when bootloader gets unlocked. Some features in regards of camera performance are lost for example.
ursidae1 said:
Thanks a lot for your reply.
I was reading on the cyanogen mod wiki how-to for our phone and it doesn't require a prior root.
I did those steps on my xperia m and it worked and i had never rooted it, the only difference is that i flashed cyanogen recovery and install cm12 which basically roots the phone and then flashed fota recovery.
Should i go this way again to gain root or would you recommend an easier root method for my stock build which is the newest.
If you recommend another root method when should it occur? prior unlocking the bootloader or afterwards?
Thanks
Click to expand...
Click to collapse
True, if bl is unlocked, then you can flash the kernel and recovery via fastboot, then flash your rom. You may need the boot.img from your rom zip file. Then use commands 'fastboot flash boot' for the boot img, and 'fastboot flash recovery' for recovery. If you're rooted already, you can just do it on the phone.
levone1 said:
True, if bl is unlocked, then you can flash the kernel and recovery via fastboot, then flash your rom. You may need the boot.img from your rom zip file. Then use commands 'fastboot flash boot' for the boot img, and 'fastboot flash recovery' for recovery. If you're rooted already, you can just do it on the phone.
Click to expand...
Click to collapse
This is fantastic.
Do you think itll be ok to fastboot flash boot boot.img from cm12.1 rom zip then fastboot flash recovery fota.img instead of the cyanogen recovery that comes with cm12.1?
Do you think that might cause an issue?
ursidae1 said:
This is fantastic.
Do you think itll be ok to fastboot flash boot boot.img from cm12.1 rom zip then fastboot flash recovery fota.img instead of the cyanogen recovery that comes with cm12.1?
Do you think that might cause an issue?
Click to expand...
Click to collapse
Should be fine. It's also a 1 second operation to extract boot.img from your rom zip, which you need already downloaded and on your SD card before you flash imgs. You might even be fine without flashing the boot img - can't hurt to try. Just flash the recovery and reboot and see if you get a purple light. Then, volume button changes purple to orange, and you're in recovery. Some recoveries don't work with some kernels, (been my experience).
levone1 said:
Should be fine. It's also a 1 second operation to extract boot.img from your rom zip, which you need already downloaded and on your SD card before you flash imgs. You might even be fine without flashing the boot img - can't hurt to try. Just flash the recovery and reboot and see if you get a purple light. Then, volume button changes purple to orange, and you're in recovery. Some recoveries don't work with some kernels, (been my experience).
Click to expand...
Click to collapse
I now have cm12.1 with cyanogen recovery.
Which recovery is best for our phone, which one do you use?
I can find 2 options:
FOTA TWRP 2.8.6.0 (http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719)
XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2647480)
Thanks a lot
ursidae1 said:
I now have cm12.1 with cyanogen recovery.
Which recovery is best for our phone, which one do you use?
I can find 2 options:
FOTA TWRP 2.8.6.0 (http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719)
XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2647480)
Thanks a lot
Click to expand...
Click to collapse
I have only used xzdr with stock rom. I think in the past I've had it not work for me on CM, so I just stick to straight twrp by default. I know NUT has always been hard at work and has made steady improvements, so maybe not an issue now. Personally I realized that I only need 1 recovery anyway. There's a newer Twrp here - http://forum.xda-developers.com/crossdevice-dev/sony/twrp-v2-8-6-0-f2fs-z1-z1c-z2-z3-z3c-t3098573
One important fact that has already been probably mentioned is that installing custom roms on your XPERIA will worsen your camera, esp the front one. Keep this in mind.
Hi all, got TWRP installed OK on my Pixel 2 XL, hit reboot and then it goes straight back into TWRP, but with no Touch. So, thought I could flash a new kernel (Flash?) but... no ADB! I guess the phone hasn't probably booted so ADB can't see the phone.
Any options at this point?!
rendez2k said:
Hi all, got TWRP installed OK on my Pixel 2 XL, hit reboot and then it goes straight back into TWRP, but with no Touch. So, thought I could flash a new kernel (Flash?) but... no ADB! I guess the phone hasn't probably booted so ADB can't see the phone.
Any options at this point?!
Click to expand...
Click to collapse
If your phone boots back to bootloader on reboot, you did something wrong. Reflash system imgs and start over.
Thanks! Is that a matter of following the guides on the official google download page and getting the factory images?
rendez2k said:
Thanks! Is that a matter of following the guides on the official google download page and getting the factory images?
Click to expand...
Click to collapse
Yes. If you don't want your data wiped, open the install.bat file and take off the -w.
Did you unlock your bootloader correctly? Unlock critical? I believe the pixel 2 xl is the only phone where that has to be done.
Boot into bootloader and fastboot flash recovery.img again, once your in recovery, flash the recovery.zip from your storage again, then reboot recovery.... its happened to me, usually when I switch slots, all I have to do is reflash recovery.
Also note, If I am trying to boot at that point (rather than flash a ROM), I usually just flash the kernel and magisk and I'm good to go.
Thanks all! I flashed the patched boot.img again and it seems to be working OK
OK, this whole thing is confusing me now! I get TWRP installed then I have to re-flash my boot.img before I quit TWRP (a magisk patched version of Flash) or the phone keeps booting to TWRP. Thats fine, but when I've flashed the boot.img I loose TWRP!
rendez2k said:
OK, this whole thing is confusing me now! I get TWRP installed then I have to re-flash my boot.img before I quit TWRP (a magisk patched version of Flash) or the phone keeps booting to TWRP. Thats fine, but when I've flashed the boot.img I loose TWRP!
Click to expand...
Click to collapse
Yes you do loose twrp after flashing the boot.img. the reason being that stock recovery resides in the boot.img. So when you flash it, bye..bye twrp! Why not just fastboot twrp, then once in twrp, flash the twrp installer zip, then flash your custom kernel(if used) then flash the magisk zip for root. :good:
Ok! So this is where I'm confused. The Flash Kernel is called boot.img? So I'm flashing it in twrp with the boot option?
rendez2k said:
Ok! So this is where I'm confused. The Flash Kernel is called boot.img? So I'm flashing it in twrp with the boot option?
Click to expand...
Click to collapse
No. Flash kernel is just the kernel, the boot.img is from the factory image. Flash the zip version of Flash kernel in twrp, then flash magisk.zip :good:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
rendez2k said:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
Click to expand...
Click to collapse
Download the 14mb FlashKernel-Taimen-v2.30.zip instead and put it in your phone to flash from within TWRP, followed by the magisk zip
http://nchancellor.net/downloads/kernels/taimen/8.1.0/stable/
rendez2k said:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
Click to expand...
Click to collapse
DON'T DO THAT! You'll bootloop for sure!! Do what the post below says, and what I told you earlier!
Pyr0x64 said:
Download the 14mb FlashKernel-Taimen-v2.30.zip instead and put it in your phone to flash from within TWRP, followed by the magisk zip
http://nchancellor.net/downloads/kernels/taimen/8.1.0/stable/
Click to expand...
Click to collapse
Thanks all! All sorted! Now, to Xposed or not to Xposed. That's the question. Seems to be tripping safetynet but that's another quandary
rendez2k said:
Thanks all! All sorted! Now, to Xposed or not to Xposed. That's the question. Seems to be tripping safetynet but that's another quandary
Click to expand...
Click to collapse
There is no solution for that. Xposed always fails SafetyNet.
Is Xposed worth having these days? Are people still actively developing useful mods?
rendez2k said:
Is Xposed worth having these days? Are people still actively developing useful mods?
Click to expand...
Click to collapse
I think it's worth it, for the following apps:
I've had so many problems with TWRP on this phone that I don't even flash it anymore. If I need to flash a zip file I just fastboot into TWRP and flash it that way. Kind of a pain in the ass but I don't flash many zip files anyway.
Fuse8499 said:
I've had so many problems with TWRP on this phone that I don't even flash it anymore. If I need to flash a zip file I just fastboot into TWRP and flash it that way. Kind of a pain in the ass but I don't flash many zip files anyway.
Click to expand...
Click to collapse
No problems with TWRP here. Maybe you are flashing to the wrong slot.
rendez2k said:
Is Xposed worth having these days? Are people still actively developing useful mods?
Click to expand...
Click to collapse
I keep hoping Xposed will go die in a fire. It causes more problems than it solves, to the point ROM developers will tell you not to bother reporting issues with it installed. Rovo knows his stuff, but his creation has caused more damage to custom ROM development than Cyanogenmod did in its last three years.
This has happened to me before, I think -- I restarted, and my phone unrooted itself. What's that about, again? How do I stop it?
My guess is when you flashed the magisk_patched boot.img you only used fastboot boot instead of fastboot flash so on reboot it reverted to stock.
ctfrommn said:
My guess is when you flashed the magisk_patched boot.img you only used fastboot boot instead of fastboot flash so on reboot it reverted to stock.
Click to expand...
Click to collapse
I feel like I did fastboot flash, but I'll try to fix that. I've done a lot of setup since then, though... Could I just go back into my bootloader and flash the patched boot.img, or do I need to do something fancy now? Do I need to clear my phone to reroot it?
DanHakimi said:
I feel like I did fastboot flash, but I'll try to fix that. I've done a lot of setup since then, though... Could I just go back into my bootloader and flash the patched boot.img, or do I need to do something fancy now? Do I need to clear my phone to reroot it?
Click to expand...
Click to collapse
You can just go flash the patched boot again.
ctfrommn said:
You can just go flash the patched boot again.
Click to expand...
Click to collapse
Welp... I did that, and now my phone is stuck booting, it won't go past the G screen.
I haven't tried this, but you can probably fastboot flash your stock boot.img file from wherever your stock img is stored on your PC/laptop. I'm not sure if you need to extract it first though, but still that's one possible option. You can also fastboot boot twrp-x.x.x.-x.img(boot command, not flash) to temporarily boot into twrp and flash a custom kernel...I think Dank kernel is still a 9.0 kernel that may work for you.
& All this is assuming the boot.img got f'd; if it's system that's f'd somehow - you may need to start fresh. If you need to start fresh and want to keep your data, alter the flash-all script file - eliminate " -w " and your data will not be wiped.
*Also, in the future for root, you can download the magisk zip file, temporarily fastboot boot twrp, and flash the zip file to gain root; imo it's an easier option than patching the boot.img through magisk, etc. It's just a temporary boot of twrp so it will not be stored on your device.
Bob nesta said:
I haven't tried this, but you can probably fastboot flash your stock boot.img file from wherever your stock img is stored on your PC/laptop. I'm not sure if you need to extract it first though, but still that's one possible option. You can also fastboot boot twrp-x.x.x.-x.img(boot command, not flash) to temporarily boot into twrp and flash a custom kernel...I think Dank kernel is still a 9.0 kernel that may work for you.
& All this is assuming the boot.img got f'd; if it's system that's f'd somehow - you may need to start fresh. If you need to start fresh and want to keep your data, alter the flash-all script file - eliminate " -w " and your data will not be wiped.
*Also, in the future for root, you can download the magisk zip file, temporarily fastboot boot twrp, and flash the zip file to gain root; imo it's an easier option than patching the boot.img through magisk, etc. It's just a temporary boot of twrp so it will not be stored on your device.
Click to expand...
Click to collapse
Aaaaaand... nope, it's still in a bootloop. I guess I'll try it with the wipe. Edit: yeah, the wipe worked, now let me root it again...
I don't need a custom kernel, I'm not flashing to min/max my battery life or anything, I just want to get this thing working, rooted, and, if possible, with the clock on the right side of the notification bar.
DanHakimi said:
Aaaaaand... nope, it's still in a bootloop. I guess I'll try it with the wipe. Edit: yeah, the wipe worked, now let me root it again...
I don't need a custom kernel, I'm not flashing to min/max my battery life or anything, I just want to get this thing working, rooted, and, if possible, with the clock on the right side of the notification bar.
Click to expand...
Click to collapse
I only mentioned flashing a custom kernel since your patched boot.img messed you up so I threw that out there because sometimes it's a way to get out of a boot problem. (I'm not trying to plug other peoples' kernels/work or anything like that.)
But you got things up and running, so...carry on
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me
Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.