Hello,
I attempted to root my Mi CC9 / 9 Lite and currently have a bootloop.
What I did:
-Flash TWRP from fastboot (success)
-Boot into TWRP (success)
-Wipe / Factory reset (success)
-Flashing Magisk v20 zip file (success)
-Then, reboot system sends me to TWRP again.
What I tried:
-The phone is not bricked. When I factory reset again from TWRP and boot to system, it boots up.
-Signing the boot image after flashing magisk using the zip file here (This did not work. Flashing the zip file returned a verification error)
Not quite sure how to root my phone at this point. Any help would be much appreciated. Thank you.
You need the Enable encryption zip...it will boot it up.. boot loop is cause from MIUI trying to encrypted and failing.
Flash the zip in this thread... go to the fstab zip that will help you
https://forum.xda-developers.com/mi-cc9/development/recovery-twrp-pyxis-unofficial-t3990493
[email protected] said:
You need the Enable encryption zip...it will boot it up.. boot loop is cause from MIUI trying to encrypted and failing.
Flash the zip in this thread... go to the fstab zip that will help you
https://forum.xda-developers.com/mi-cc9/development/recovery-twrp-pyxis-unofficial-t3990493
Click to expand...
Click to collapse
Where do I find it?
dupreme said:
Where do I find it?
Click to expand...
Click to collapse
Direct link from OP.
https://www.mediafire.com/folder/zqk7a9qj5ltyd/Mi 9 Lite (pyxis)
[email protected] said:
Direct link from OP.
https://www.mediafire.com/folder/zqk7a9qj5ltyd/Mi 9 Lite (pyxis)
Click to expand...
Click to collapse
Thank you. I tried flashing the fstab zip after flashing magisk and it did not change the situation. Shall I first flash the auto-decrypt TWRP img and then try again?
dupreme said:
Thank you. I tried flashing the fstab zip after flashing magisk and it did not change the situation. Shall I first flash the auto-decrypt TWRP img and then try again?
Click to expand...
Click to collapse
What I do is this: I Boot in recovery and format data then I go to advance wipe and select data and then repair and select ext4 and swipe and then reboot recovery and flash the MIUI rom and then I reboot the recovery and mount system and vendor and flash the zip and then reboot and wait for it... you know it will boot up because after it boots up the bootanimation increases it's light before the actual booting in the system and the rest you can figure out... hope this helps you out.
[email protected] said:
What I do is this: I Boot in recovery and format data then I go to advance wipe and select data and then repair and select ext4 and swipe and then reboot recovery and flash the MIUI rom and then I reboot the recovery and mount system and vendor and flash the zip and then reboot and wait for it... you know it will boot up because after it boots up the bootanimation increases it's light before the actual booting in the system and the rest you can figure out... hope this helps you out.
Click to expand...
Click to collapse
I'll try that. Thanks a lot. Do you use the auto-decrypt (the one you linked) TWRP in this, or just regular TWRP. I am using just the pyxis TWRP.
Can anyone elaborate on what needs to be done? The previous responses did not explain how to ROOT the phone.
What I have just tried:
-flashed the TWRP img here
-did a wipe
-sent Magisk and the fstab zips to storage and flashed them (fstab first)
still gives bootloop to recovery. How to root this phone?
Thank you
dupreme said:
Can anyone elaborate on what needs to be done? The previous responses did not explain how to ROOT the phone.
What I have just tried:
-flashed the TWRP img here
-did a wipe
-sent Magisk and the fstab zips to storage and flashed them (fstab first)
still gives bootloop to recovery. How to root this phone?
Thank you
Click to expand...
Click to collapse
After you unlock the bootloader I just put it in fastboot mode and fastboot boot "(whatever you have it called... I renamed it recovery) recovery.img and then press the volume up button and then I install the image through TWRP and reboot recovery and then follow the steps.
---------- Post added at 04:07 PM ---------- Previous post was at 04:06 PM ----------
dupreme said:
I'll try that. Thanks a lot. Do you use the auto-decrypt (the one you linked) TWRP in this, or just regular TWRP. I am using just the pyxis TWRP.
Click to expand...
Click to collapse
I used the TWRP for the team win recovery project website.
---------- Post added at 04:25 PM ---------- Previous post was at 04:07 PM ----------
dupreme said:
Can anyone elaborate on what needs to be done? The previous responses did not explain how to ROOT the phone.
What I have just tried:
-flashed the TWRP img here
-did a wipe
-sent Magisk and the fstab zips to storage and flashed them (fstab first)
still gives bootloop to recovery. How to root this phone?
Thank you
Click to expand...
Click to collapse
Fstab zip is last because it's the encryption fix
[email protected] said:
After you unlock the bootloader I just put it in fastboot mode and fastboot boot "(whatever you have it called... I renamed it recovery) recovery.img and then press the volume up button and then I install the image through TWRP and reboot recovery and then follow the steps.
---------- Post added at 04:07 PM ---------- Previous post was at 04:06 PM ----------
I used the TWRP for the team win recovery project website.
---------- Post added at 04:25 PM ---------- Previous post was at 04:07 PM ----------
Fstab zip is last because it's the encryption fix
Click to expand...
Click to collapse
I tried a combination of what you suggested and this guide and the phone booted up with root. However, opening the Magisk manager immediately says "your device needs additional setup" or something similar, and asks to flash a zip file. When I select flash, it says rebooting in 5 sec and stays in bootloop. Have you come across this?
use twrp by brigudav. It has also s built-in Magisk installer.
JimmyBondi said:
use twrp by brigudav. It has also s built-in Magisk installer.
Click to expand...
Click to collapse
Can you share a link? I could not find an XDA thread. Thank you.
dupreme said:
I tried a combination of what you suggested and this guide and the phone booted up with root. However, opening the Magisk manager immediately says "your device needs additional setup" or something similar, and asks to flash a zip file. When I select flash, it says rebooting in 5 sec and stays in bootloop. Have you come across this?
Click to expand...
Click to collapse
TBH no because as Soon as I got TWRP I flash another rom Mi Globe rom to be exact and use the method I posted.
Related
Close please.....
Boot into twrp and Flash twrp AGAIN (install-select img- Recovery).
Click to expand...
Click to collapse
I don't quite get what this means - please make it more thorough.
RJMacReady said:
I don't quite get what this means - please make it more thorough.
Click to expand...
Click to collapse
just flash twrp .img file with fastboot command
After I flashed the rom, mounted system normally and flashed magisk, etc. I booted into system, rebooted into FASTBOOT and re-flashed TWRP but it just leaves me at a black screen.
RJMacReady said:
After I flashed the rom, mounted system normally and flashed magisk, etc. I booted into system, rebooted into FASTBOOT and re-flashed TWRP but it just leaves me at a black screen.
Click to expand...
Click to collapse
hold power button for 15 sec boot the phone tryaguin
If that doesn't work, are you gonna recommend redoing the entire process over?
RJMacReady said:
If that doesn't work, are you gonna recommend redoing the entire process over?
Click to expand...
Click to collapse
i do it myself just let the os boot then reboot in fastboot and flash twrp
---------- Post added at 03:10 PM ---------- Previous post was at 02:30 PM ----------
RJMacReady said:
If that doesn't work, are you gonna recommend redoing the entire process over?
Click to expand...
Click to collapse
hi flash the new twrp the old one is not working
im tested is working
Twrp working on 3.5.2
RJMacReady said:
I don't quite get what this means - please make it more thorough.
Click to expand...
Click to collapse
i mean first install twpr vie fastboot.
then reboot into twrp.
then you can go to install (in twrp) and then you can select "select image" then you can choose your twrp.img and flash it on recovery partition
to go the safe way
Because i experienced that i flashed twrp via fastboot and when i boot the system, the stock recovery was flashed again.
RJMacReady said:
After I flashed the rom, mounted system normally and flashed magisk, etc. I booted into system, rebooted into FASTBOOT and re-flashed TWRP but it just leaves me at a black screen.
Click to expand...
Click to collapse
Can you boot into system?
or do you get the op3 logo and then black screen?
upps, sorry for posting two comments, my fault :c
Edit: if you have black Screen at Recovery Boot you must Flash twrp 3.0.2.19 from another thread
I think "how to dirty Flash........"
Phone Details:
Sony Xperia Z2 D6503 running Android 6.0.1
Boot loader unlocked
TWRP installed
Magisk v12.0
Had the phone rooted but un-rooted via SU and then re-flashed default os using Sony Companion and unlocked the boot loader
When i flash Magisk via TWRP it says its successful but when i go to reboot it won't boot up
Has anyone experienced this before or have successfully installed Magisk on Xperia Z2 that can help me out?
same problem here. can anyone recommend a solution ?
Same here.. Finally recovered my device flashing stock...
https://forum.xda-developers.com/lg-g5/development/stock-h850-20d-eu-rom-flashable-zips-t3592762
Before Magisk installs anything on your device, it will create a boot image backup in /data/stock_boot_<sha1>.img.gz
If anything goes wrong (e.g. bootloop), you can either use the uninstaller (recommended) or decompress the backup and manually restore your boot image
It should ALWAYS bring your device back to life (suppose you have a custom recovery that can decrypt your /data)
Click to expand...
Click to collapse
Source: Main Thread
TatesMan said:
Source: Main Thread
Click to expand...
Click to collapse
How to install the unistaller while the phone is in bootloop and i can't access recovery
deathlove70 said:
How to install the unistaller while the phone is in bootloop and i can't access recovery
Click to expand...
Click to collapse
If you can't access recovery you've got bigger issues than getting a bootloop from flashing Magisk. Can you access the bootloader to fastboot flash or boot a recovery image?
Didgeridoohan said:
If you can't access recovery you've got bigger issues than getting a bootloop from flashing Magisk. Can you access the bootloader to fastboot flash or boot a recovery image?
Click to expand...
Click to collapse
i can access flash mode and fast bootmode in flash tool. it says the phone is connected
deathlove70 said:
How to install the unistaller while the phone is in bootloop and i can't access recovery
Click to expand...
Click to collapse
try to boot using 'power+ volume down' to boot into recovery, if that didnt work then you have to boot into fastboot then flash the recovery from there
deathlove70 said:
i can access flash mode and fast bootmode in flash tool. it says the phone is connected
Click to expand...
Click to collapse
Cool. Then you should be good to go. If you don't know how to proceed from here, you should go to your device's forum for help.
can you make it simple and tell me what t do ?
what files should i flash ?
i have sony xperia Z2
---------- Post added at 11:16 PM ---------- Previous post was at 11:14 PM ----------
TatesMan said:
try to boot using 'power+ volume down' to boot into recovery, if that didnt work then you have to boot into fastboot then flash the recovery from there
Click to expand...
Click to collapse
boot via power+volume down didn't work. what's the file to flash ?
deathlove70 said:
can you make it simple and tell me what t do ?
what files should i flash ?
i have sony xperia Z2
---------- Post added at 11:16 PM ---------- Previous post was at 11:14 PM ----------
boot via power+volume down didn't work. what's the file to flash ?
Click to expand...
Click to collapse
best advice is to head to your device's forum and check for guides there on how to flash custom recovery (twrp) there.
Connect your phone with pc, go into fastboot mode and type on fastboot
Code:
fastboot boot recovery
Or try a simple ways with power button with volume -/+ or both just try it
i recovered the phone but lost the root and can't root my phone. i am on marshmallow stock firmware
Hi, today i saw a notification of magisk saying there's a new version aviable, i clicked and i selected the automatic update option, after done, i rebooted my phone, but now it is blocked in a loop witouth showing screen, what can i do?
Hi Guys
My brothers lenovo K3note was runing RR rom and he did factory reset the phone, but now it only goes to TWRP and not booting into the OS
I tried to reinstall the RR rom, it installs normally but after reboot from TWRP, it goes back to TWRP instead of android Os.
What can i do now, please help
any help guys,
skyh3ck said:
Hi Guys
My brothers lenovo K3note was runing RR rom and he did factory reset the phone, but now it only goes to TWRP and not booting into the OS
I tried to reinstall the RR rom, it installs normally but after reboot from TWRP, it goes back to TWRP instead of android Os.
What can i do now, please help
Click to expand...
Click to collapse
Hello mate
Don't worry.. Just wipe system, data and cache and re-install rr rom. The same thing happened to me when i did a factory reset on that ROM.
i did all, it shows as installing but after reboot goes back to TWRP recovery only
change ur twrp recovery, i mean update your twrp recovery and you will never face this problem....
skyh3ck said:
i did all, it shows as installing but after reboot goes back to TWRP recovery only
Click to expand...
Click to collapse
I had the same problem a few days back. I tried everything but at the end, I had to flash the stock ROM using SP Flash Tool. After that, I was able to boot into Stock Android and rooted the phone again and installed the Custom Rom later.
TheRootRiffs said:
I had the same problem a few days back. I tried everything but at the end, I had to flash the stock ROM using SP Flash Tool. After that, I was able to boot into Stock Android and rooted the phone again and installed the Custom Rom later.
Click to expand...
Click to collapse
And from where have you downloaded the stock ROM?
VinayakS said:
And from where have you downloaded the stock ROM?
Click to expand...
Click to collapse
youtube(dot)com/watch?v=TySRc_DkcFk&t=251s
Follow this
TheRootRiffs said:
youtube(dot)com/watch?v=TySRc_DkcFk&t=251s
Follow this
Click to expand...
Click to collapse
Thanks, I have already downloaded from some other URL.
@ skyh3ck and VinayakS
did it help?
My phone got a bootloop to twrp 3.0.2-7 after I wanted to restore to factory settings (from settings menu), I tried flashing 'new' RR-N-v5.8.5-20170926-aio_otfp-FINAL (during flashing I had 2 errors - logs available), tried to flash with some other roms, I tried to restore some old backups - same thing = bootloop to twrp.
I don't want to brick it like the guy from this thread https://forum.xda-developers.com/k3-note/help/help-unbricking-k3-note-k50a40-charging-t3699007
Krzykor said:
@ skyh3ck and VinayakS
did it help?
My phone got a bootloop to twrp 3.0.2-7 after I wanted to restore to factory settings (from settings menu), I tried flashing 'new' RR-N-v5.8.5-20170926-aio_otfp-FINAL (during flashing I had 2 errors - logs available), tried to flash with some other roms, I tried to restore some old backups - same thing = bootloop to twrp.
I don't want to brick it like the guy from this thread https://forum.xda-developers.com/k3-note/help/help-unbricking-k3-note-k50a40-charging-t3699007
Click to expand...
Click to collapse
I did not had time to revert rooting and remove custom recovery, so can't say much at this moment.
But your bootloop issue is most probably due to presence of TWRP, you need to completely remove root & TWRP, restore stock boot and recovery, then try.
VinayakS said:
But your bootloop issue is most probably due to presence of TWRP, you need to completely remove root & TWRP, restore stock boot and recovery, then try.
Click to expand...
Click to collapse
Fortunately I've made it working again.
What I did, I flashed phone with SP FLash Tool 5.1628 and K50a40_S433_160909_ROW https://forum.xda-developers.com/k3-note/development/official-build-lenovo-k3-note-k50a40-6-t3370537. But it was not success at that time. Phone acted weirdly couldn't boot, only vibration after power on could be felt. So I tried to flash only the recovery Lenovo K3 Note Stock Recovery.img 10,2MB (also in the package but not default recovery image for S433) with the scatter map from S433 stockrom but SPFL said that it didn't end successfully, so I flashed only rocovery from stock rom S433 target_bin folder recovery.img 12800kB and then voila, it started to boot, there was a Lenovo logo, took some time to start but eventually phone is working.
Now I want to root it and / or flash correct version because my phone is actually k50-t5 not k50a40.
So thanks and good luck to those with similar problems after restoring factory settings on AIMROM.
same prob happend to me
first time encountering with TWRP loop.
downloading the stock rom
if there is any improvements will update
the solution for this(FIX)
all we need to do is reinstall a stock recovery and the again reinstall the TWRP
https://forum.xda-developers.com/k3-...-note-t3102997
follow this link..my phone just got fixed
nidheeshv said:
all we need to do is reinstall a stock recovery and the again reinstall the TWRP
https://forum.xda-developers.com/k3-...-note-t3102997
follow this link..my phone just got fixed
Click to expand...
Click to collapse
That link is incorrect / not working.
updating
VinayakS said:
That link is incorrect / not working.
Click to expand...
Click to collapse
wait i will update the link now
---------- Post added at 12:05 PM ---------- Previous post was at 11:49 AM ----------
Before proceeding download a stock and TWRP recovery from the link below
https://drive.google.com/file/d/0B2I5z1mFfUpcTUtjWUtpUmFCRWM/view
this is the stock recovery,extract this recovery and paste the contents to a folder named STOCK
https://drive.google.com/file/d/0B2I5z1mFfUpcaE5sZTk3M2Vrc1E/view
this is the TWRP recovery,extract this recovery and paste the contents to a folder named TWRP
1.install adb and fastboot on ur laptop.(am using ububtu 16.04)
2.make the phone to go to TWRP
3.plug in the usb
4.open terminal and type adb devices
5.see if device is detected ,if detected do the following
go to the STOCK rfolder u created and open terminal there.and type the following
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery.img
fastboot reboot
6.Now ur device will have stock recovery.
7.again repeat the above steps instead of STOCK use TWRP recovery.
8.your device will boot up with TWRP recovery build in
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
nidheeshv said:
wait i will update the link now
---------- Post added at 12:05 PM ---------- Previous post was at 11:49 AM ----------
Before proceeding download a stock and TWRP recovery from the link below
https://drive.google.com/file/d/0B2I5z1mFfUpcTUtjWUtpUmFCRWM/view
this is the stock recovery,extract this recovery and paste the contents to a folder named STOCK
https://drive.google.com/file/d/0B2I5z1mFfUpcaE5sZTk3M2Vrc1E/view
this is the TWRP recovery,extract this recovery and paste the contents to a folder named TWRP
1.install adb and fastboot on ur laptop.(am using ububtu 16.04)
2.make the phone to go to TWRP
3.plug in the usb
4.open terminal and type adb devices
5.see if device is detected ,if detected do the following
go to the STOCK rfolder u created and open terminal there.and type the following
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery.img
fastboot reboot
6.Now ur device will have stock recovery.
7.again repeat the above steps instead of STOCK use TWRP recovery.
8.your device will boot up with TWRP recovery build in
Click to expand...
Click to collapse
dont download the files from the below link ,its for a different device ,its just a reference i used
the reference is
http://https://forum.xda-developers.com/oneplus-5/how-to/guide-fix-twrp-recovery-script-loop-t3649727
nidheeshv said:
wait i will update the link now
---------- Post added at 12:05 PM ---------- Previous post was at 11:49 AM ----------
Before proceeding download a stock and TWRP recovery from the link below
https://drive.google.com/file/d/0B2I5z1mFfUpcTUtjWUtpUmFCRWM/view
this is the stock recovery,extract this recovery and paste the contents to a folder named STOCK
https://drive.google.com/file/d/0B2I5z1mFfUpcaE5sZTk3M2Vrc1E/view
this is the TWRP recovery,extract this recovery and paste the contents to a folder named TWRP
1.install adb and fastboot on ur laptop.(am using ububtu 16.04)
2.make the phone to go to TWRP
3.plug in the usb
4.open terminal and type adb devices
5.see if device is detected ,if detected do the following
go to the STOCK rfolder u created and open terminal there.and type the following
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery.img
fastboot reboot
6.Now ur device will have stock recovery.
7.again repeat the above steps instead of STOCK use TWRP recovery.
8.your device will boot up with TWRP recovery build in
Click to expand...
Click to collapse
dont download the files from the below link ,its for a different device ,its just a reference i used
the reference is
http://https://forum.xda-developers.com/oneplus-5/how-to/guide-fix-twrp-recovery-script-loop-t3649727
sudip_55 said:
change ur twrp recovery, i mean update your twrp recovery and you will never face this problem....
Click to expand...
Click to collapse
Exactly the same thing happened to me.
So I tried your idea and updated my TWRP, going from 2.8 to 3.1..1
But exactly the same thing happens - it still bootloops, but to the new TWRP.
I've tried flashing several different ROMs that all worked in the past. But no change.
Salvadorfreeman said:
Exactly the same thing happened to me.
So I tried your idea and updated my TWRP, going from 2.8 to 3.1..1
But exactly the same thing happens - it still bootloops, but to the new TWRP.
I've tried flashing several different ROMs that all worked in the past. But no change.
Click to expand...
Click to collapse
do as what i have mentioned above,..and give update
It worked ! Thanks.
The reason I didn't try it straight away was all the comments about wrong links etc. And some of the links afterwards didn't work. So I was looking for a recovery.img file in other places.
I read your new message, so I used the first link in your post which gave me the recovery img. The TWRP link doesn't seem to work, but I already have an up to date TWRP on the phone.
October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds
chanh2018 said:
October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
Won't root for me.
you mean magisk not working with this build?
mcdull said:
you mean magisk not working with this build?
Click to expand...
Click to collapse
No, it's not working for ME.
Sent from my PH-1 using XDA Labs
avd said:
Won't root for me.
Click to expand...
Click to collapse
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.
kt-Froggy said:
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.
Click to expand...
Click to collapse
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:
JimmyCash030 said:
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:
Click to expand...
Click to collapse
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.
kt-Froggy said:
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.
Click to expand...
Click to collapse
yeah worked for me as well with the latest canary MM !!
Magisk 19.4 works just fine on latest 148 build if need be I can upload magisk rooted boot. Img
https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img
allenjthomsen said:
https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img
Click to expand...
Click to collapse
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
avd said:
getting back to the topic at hand, i flashed this, then twrp on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now i got to plug this in and swap slots to reinstall twrp.
Is possible that magisk and twrp are back to not playing nice to each other again?
(i'll test this out if i get a chance to swap slots)
Click to expand...
Click to collapse
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.
Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.
allenjthomsen said:
Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.
Click to expand...
Click to collapse
pretty much everything for this phone resides in t.me/ESSENTIALPH1DEV
avd said:
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.
Click to expand...
Click to collapse
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
Flashing the patched image provided just sits there looking at the boot animation.
I'll play with it tonight.
It's a Sprint phone. Could that be the issue?
Sent from my PH-1 using XDA Labs
I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?
I'm no expert but did this ans it worked:
1. In TWRP recovery (created nandroid and wiped cache)
2. Flashed full update zip from official download link, then TWRP, then wipe cache
3. Reboot system and let it settle
4. Reboot into TRWP and flashed Canary Channel zip file
5. Wipe cache
6. Reboot system
Hope this helps.
jionny said:
I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?
Click to expand...
Click to collapse
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
? I always have trouble remembering, not anymore it seems
gavinfernandes2012 said:
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
I always have trouble remembering, not anymore it seems
Click to expand...
Click to collapse
Are you able to give more precise instructions on fastboot instructions?
jionny said:
Are you able to give more precise instructions on fastboot instructions?
Click to expand...
Click to collapse
Nevermind, got the instructions from essentials site. flashed via fastboot which erased everything had to do a complete setup again
I tried to perform a factory reset from TWRP cause it wouldn't let me from Configuration>Reset and Restore (or something like that), and after a reboot system didn't launch, it said something about an encryption problem, so I decided to restore a system backup I did and now my phone is stuck in bootloop. Someone can point me in the right direction? Thanks in advance.
Yzakz said:
I tried to perform a factory reset from TWRP cause it wouldn't let me from Configuration>Reset and Restore (or something like that), and after a reboot system didn't launch, it said something about an encryption problem, so I decided to restore a system backup I did and now my phone is stuck in bootloop. Someone can point me in the right direction? Thanks in advance.
Click to expand...
Click to collapse
We're you on stock Orero, Pie? Or one of the custom Pie, Q ROMs?
Ainz_Ooal_Gown said:
We're you on stock Orero, Pie? Or one of the custom Pie, Q ROMs?
Click to expand...
Click to collapse
Stock Pie
Yzakz said:
Stock Pie
Click to expand...
Click to collapse
Yeah TWRP and Stock are at odds with each other.... You must fallow the guide to make TWRP and Stock compatible with each other when restoring.... alternatively you can try to flash one of the custom ROMs and see if it boots.
---------- Post added at 11:55 PM ---------- Previous post was at 11:51 PM ----------
This guide specifically https://forum.xda-developers.com/lg-v40/how-to/guide-twrp-data-access-stock-t3970149
Ainz_Ooal_Gown said:
Yeah TWRP and Stock are at odds with each other.... You must fallow the guide to make TWRP and Stock compatible with each other when restoring.... alternatively you can try to flash one of the custom ROMs and see if it boots.
---------- Post added at 11:55 PM ---------- Previous post was at 11:51 PM ----------
This guide specifically https://forum.xda-developers.com/lg-v40/how-to/guide-twrp-data-access-stock-t3970149
Click to expand...
Click to collapse
I tried with LineageOS but no luck. In fact, I tried to install LineageOS before I had this problem and even when TWRP said "Success", the phone booted into stock pie rom
Yzakz said:
I tried with LineageOS but no luck. In fact, I tried to install LineageOS before I had this problem and even when TWRP said "Success", the phone booted into stock pie rom
Click to expand...
Click to collapse
Did you switch slots?
Ainz_Ooal_Gown said:
Did you switch slots?
Click to expand...
Click to collapse
When? When installing LineageOS? To be honest right now I don't remember exactly what I did, but I'm 100% that I followed the write-up in the TWRP thread step by step.
Which slot should I select to install a custom rom?
Yzakz said:
Which slot should I select to install a custom rom?
Click to expand...
Click to collapse
When you install a ROM made for the V40 if your on Slot A when you boot into TWRP then the ROM installs in Slot B and if on B the it installs into A. But gapps and other flashable zips install into the current booted slot.
So flashing steps would be
1. Boot TWRP
2. Check which slot your on in the reboot menu
3. Flash ROM
4. Flash the TWRP recovery IMG. To ram disk
5. Go to reboot menu and select opposite Slot
6. Select reboot recovery and swipe to reboot
7.flash anything else gapps etc.
8. Reboot into your new working ROM.
Ainz_Ooal_Gown said:
When you install a ROM made for the V40 if your on Slot A when you boot into TWRP then the ROM installs in Slot B and if on B the it installs into A. But gapps and other flashable zips install into the current booted slot.
So flashing steps would be
1. Boot TWRP
2. Check which slot your on in the reboot menu
3. Flash ROM
4. Flash the TWRP recovery IMG. To ram disk
5. Go to reboot menu and select opposite Slot
6. Select reboot recovery and swipe to reboot
7.flash anything else gapps etc.
8. Reboot into your new working ROM.
Click to expand...
Click to collapse
I thought I did that, but when I rebooted the phone it booted to the stock Android rom
Yzakz said:
I thought I did that, but when I rebooted the phone it booted to the stock Android rom
Click to expand...
Click to collapse
My guess is you didn't select reboot recovery and instead hit reboot system...