Ok, so I have a question that either does not exist on Google or that I just don't know how to explain.
My Kindle Fire 2 was flashed a while back with a stock version of Android Jellybean 4.2.2, until today. I made a complete backup of everything inside TWRP and transferred all of those backup files to my laptop. I then flashed a newer version of TWRP, version 2.6.3.1. After that, i flashed the newest version of Cyanogenmod 11, Android 4.4.4.
Anyways, I got to adjusting the settings and told it to allow me to pick between rebooting into recovery or normal mode when i pressed the reboot button on the power menu.
Here is my problem though. At one point, I told Cyanogenmod to reboot me into recovery, and ever since, my Kindle will only let me boot into the TWRP recovery area, regardless of what I tell it to load in the bootloader.
How can I just get it to boot to the normal OS? I've tried reflashing the recovery and reflashing Cyanogenmod onto it. I just don't know what to do because I don't know exactly why this is happening.
I've tried wiping the /data partition too, but to no use. I still am able to wipe internal data partition, however I don't know how it will respond to that. I mean... Isn't that where TWRP is stored? I don't want to lose my recovery partition where I have no way to get back.
If it comes to it, could I replace my recovery partition with Cyanogenmod?
I am still able to use ADB and I'm able to push files. (So far)
Possible solution
mayuri1 said:
Ok, so I have a question that either does not exist on Google or that I just don't know how to explain.
My Kindle Fire 2 was flashed a while back with a stock version of Android Jellybean 4.2.2, until today. I made a complete backup of everything inside TWRP and transferred all of those backup files to my laptop. I then flashed a newer version of TWRP, version 2.6.3.1. After that, i flashed the newest version of Cyanogenmod 11, Android 4.4.4.
Anyways, I got to adjusting the settings and told it to allow me to pick between rebooting into recovery or normal mode when i pressed the reboot button on the power menu.
Here is my problem though. At one point, I told Cyanogenmod to reboot me into recovery, and ever since, my Kindle will only let me boot into the TWRP recovery area, regardless of what I tell it to load in the bootloader.
How can I just get it to boot to the normal OS? I've tried reflashing the recovery and reflashing Cyanogenmod onto it. I just don't know what to do because I don't know exactly why this is happening.
I've tried wiping the /data partition too, but to no use. I still am able to wipe internal data partition, however I don't know how it will respond to that. I mean... Isn't that where TWRP is stored? I don't want to lose my recovery partition where I have no way to get back.
If it comes to it, could I replace my recovery partition with Cyanogenmod?
I am still able to use ADB and I'm able to push files. (So far)
Click to expand...
Click to collapse
I assuming you have a TWRP bootloop problem? Like everytime you reboot it, it shows you the kindel fire logo (organge/white), then to the blue/white logo, and then instead of the normal android ui, it boots into TWRP? If this is the case, have you tried selecting the 'bootmode' option during the kindle fire blue/white logo screen? That was my solution when I had the recovery bootloop problem recently.
rocketfans14 said:
I assuming you have a TWRP bootloop problem? Like everytime you reboot it, it shows you the kindel fire logo (organge/white), then to the blue/white logo, and then instead of the normal android ui, it boots into TWRP? If this is the case, have you tried selecting the 'bootmode' option during the kindle fire blue/white logo screen? That was my solution when I had the recovery bootloop problem recently.
Click to expand...
Click to collapse
I tried telling it to boot normal during that screen. Still goes to TWRP.
Sent from my PantechP8010 using XDA Free mobile app
I've recently flashed the latest twrp on my oneplus3 a3003 through fastboot. All fine, I flashed the cyanogenmod 14.1 and the gapps 7.1 over the oxygen os. Now I tried to boot into recovery to flash the pixelfy zip file, but I found out that I can't access recovery mode. All I get is boot logo and the capacitive buttons illuminated for a while, then the screen goes off and I have to press the power button for 6/7 seconds. I tried reflashing the recovery.img through the terminal and no result, I tried through TWRP manager, it says successful but the result is still the same. Ah, before installing the twrp I hard bricked the device and I unbricked it, so to me it's like a corrupted partition. Is there a way to restore twrp (or to restore the recovery partition, still being able to flash twrp) without losing data? If no, is there a way to restore it to a funcional state without having to use qualcomm drivers? If no, is there a way to restore it to a funcional state AND keep it that way?
I solved it. Basically the cm14.1 version was blocking twrp or any other recovery aside from the cm recovery. I found a fixed version of the twrp somewhere.
Vas0sky said:
I solved it. Basically the cm14.1 version was blocking twrp or any other recovery aside from the cm recovery. I found a fixed version of the twrp somewhere.
Click to expand...
Click to collapse
Is it possible that you gave me this recovery? I'm looking for one too same problem as you
Thanks
http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Here you go.
Hello, I flashed CM14 Nougat 7.1.1 and everything worked fine until I tried to boot into recovery to get access to TWRP. If I try and boot into recovery I get the 1+ logo and then just a black screen and i have to hard reboot the phone to use it again. After the hard reboot it just goes back to nougat. I downloaded the TWRP APK to try and restore my previous save but it just does the same thing.
Can anyone help?
Thank you.
I get the same problem. This is WHY we should BACKUP it first. but I didd't, and so are you. I was having lots of works and did not check much news about CM for a long time. but yes, I get the rumors about CM getting shut down. and I check the news. Today I found out CM is shutting down, and my phone is not working.
But, hey, who am I. OnePlus 3 User with lots of experience.
So I tried CM recovery, the newest version works, but there is no backup option, I tried old CM13 recovery. it also black screen. This confirm my theory, this is due to Android 7.1 or CM14.1 upgrade
How to solve this problem?
I found this
https://forum.xda-developers.com/oneplus-3/development/rom-hydrogenos-h2os-beta-edition-oct-t3482259
go to this thread, and download modified TWRP.
BACKUP.
Install your new ROM via any XDA rom. not the CM14.1 build on Dec 25.
Note: If you want Android 7.xx, you could flash the Official Beta ROM(above), or download modem from
https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Happy New Year.
YungKremer said:
Hello, I flashed CM14 Nougat 7.1.1 and everything worked fine until I tried to boot into recovery to get access to TWRP. If I try and boot into recovery I get the 1+ logo and then just a black screen and i have to hard reboot the phone to use it again. After the hard reboot it just goes back to nougat. I downloaded the TWRP APK to try and restore my previous save but it just does the same thing.
Can anyone help?
Thank you.
Click to expand...
Click to collapse
boot into fastboot mode and give following commands
fastboot erase recovery
fastboot flash recovery twrp-xxxx.img
now reboot to recovery...
Please confirm if this works
Used the search, used google, couldn't find any concrete answers
I am on Android N - unlocked bootloader - rooted via magisk, One Plus 3.
Could I do the following?
use TWRP to make a Nandroid Backup (System+Data+Boot) of my current set-up
then, manually flash (using twrp) Android O
find out I don't particularly like it
Go back to TWRP and Nandroid Restore back to Android N, as if no update ever happened
Or will there be issues?
Thanks
I do that with freedomos. 2.17(N)>3.1(O)>2.17. I restore nandroid and reflash rom
xGOGI said:
I do that with freedomos. 2.17(N)>3.1(O)>2.17. I restore nandroid and reflash rom
Click to expand...
Click to collapse
Should have mentioned I'm using stock rom.
So I'd restore the nandroid via twrp, and I should be good to go?
arthritis said:
Used the search, used google, couldn't find any concrete answers
I am on Android N - unlocked bootloader - rooted via magisk, One Plus 3.
Could I do the following?
use TWRP to make a Nandroid Backup (System+Data+Boot) of my current set-up
then, manually flash (using twrp) Android O
find out I don't particularly like it
Go back to TWRP and Nandroid Restore back to Android N, as if no update ever happened
Or will there be issues?
Thanks
Click to expand...
Click to collapse
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
maxs8007 said:
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
Click to expand...
Click to collapse
Thank you for the detailed procedure.
maxs8007 said:
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
Click to expand...
Click to collapse
Thank you
Hi @maxs8007
thanks for the instructions. I did all that to get back to my nougat rom (PureFusion) and all seem good and phone booted fine. But i am stuck on login screen after booted up. I tried my correct password several times but to no avail. anyway reset my password without factory resetting again?
Thanks for the advise.
sqlpro said:
Hi @maxs8007
thanks for the instructions. I did all that to get back to my nougat rom (PureFusion) and all seem good and phone booted fine. But i am stuck on login screen after booted up. I tried my correct password several times but to no avail. anyway reset my password without factory resetting again?
Thanks for the advise.
Click to expand...
Click to collapse
Go to twrp - advanced - file manager - go to root folder - data - system - and delete files with .key extension. There will be 2 files delete both and reboot.
maxs8007 said:
Go to twrp - advanced - file manager - go to root folder - data - system - and delete files with .key extension. There will be 2 files delete both and reboot.
Click to expand...
Click to collapse
Thank you very much and that worked. I am back in the system.
BTW in your original instructions I had to re flash rom after restoring twrp backup otherwise it didn't boot and stuck at rom animation.
sqlpro said:
Thank you very much and that worked. I am back in the system.
BTW in your original instructions I had to re flash rom after restoring twrp backup otherwise it didn't boot and stuck at rom animation.
Click to expand...
Click to collapse
Thanks for pointing out, I must have forgot to add it. I'll update again.
Hi @maxs8007
I ran into this issue again today! after unlocking as per instructions yesterday and am back into phone and re-set the pin and all good. But today i had to reboot the phone and same issue again , cant login on the lock screen!! i tried deleting those files again but to no avail!!
any ideas before factory reset and loose my data ? Thanks.
sqlpro said:
Hi @maxs8007
I ran into this issue again today! after unlocking as per instructions yesterday and am back into phone and re-set the pin and all good. But today i had to reboot the phone and same issue again , cant login on the lock screen!! i tried deleting those files again but to no avail!
any ideas before factory reset and loose my data ? Thanks.
Click to expand...
Click to collapse
This should not have happened, anyways delete all those files which I've highlighted in the image below. This will reset the lock settings.
Oh sorry I forgot to attach the file. Here it is.
maxs8007 said:
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
Click to expand...
Click to collapse
Hi, OP here. Thanks for this guide.
Unfortunately, it did not work out for me.
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Done
Do factory reset(wipe everything except internal storage)
Wiped fine although I got an error of not being able to wipe 'USB-OTG' or whatever it's called. I ignored it and moved on.
then flash oreo twrp image.
I googled oreo twrp image and got an img file with filename "TWRP-Oreo-OnePlus-3-3T". When I installed the img, it asked the options to choose Boot, System, or Recovery - so I chose System.
Then I rebooted and went back to recovery.
Flash oreo stock zip
flash oreo twrp image
Done
reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu.
This is where it ends. I get stuck at the OnePlus loading screen and forced reboot into twrp and flashed magisk. Once I boot up the OS, I get stuck at the OnePlus logo and that's it.
I actually re-did ALL of the steps again (in case I made a mistake) and still, the same issue. No progression.
Once I gave up on Oreo, I decided to go restore my nandroid
Reboot to recovery. Perform factory reset as mentioned above.
Wiped
Restore everything except bootloader, cache and dalvik cache
Here's the issue:
I press Restore (I uncheck both bootloader and cache, but there's no option for a specific dalvik cache- unless I'm not looking hard enough?) and I get the 255 Error.
Flash nougat twrp recovery. Reboot to system.
I tried to ignore that error and flash the twrp recovery.
Rebooted and it took me to fastboot. Regardless of I keep trying to reboot system it won't work.
I actually made two separate nandroid backups (the same 'everything except system image' as you've described) in case one of the backups was corrupted. Both backups ended up with the same error.
I got too tired of all these errors and just found a stock recovery and ROM and flashed it back. Now, all my apps and settings are gone. To be honest, I just want my phone back to where it was with Nougat.
Can anyone assist me?
@maxs8007, Like I said I did that already but nope still same issue. It wouldn't let me do matter what I did.
---------- Post added at 04:59 AM ---------- Previous post was at 04:54 AM ----------
arthritis said:
Hi, OP here. Thanks for this guide.
Unfortunately, it did not work out for me.
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Done
Do factory reset(wipe everything except internal storage)
Wiped fine although I got an error of not being able to wipe 'USB-OTG' or whatever it's called. I ignored it and moved on.
then flash oreo twrp image.
I googled oreo twrp image and got an img file with filename "TWRP-Oreo-OnePlus-3-3T". When I installed the img, it asked the options to choose Boot, System, or Recovery - so I chose System.
Then I rebooted and went back to recovery.
Flash oreo stock zip
flash oreo twrp image
Done
reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu.
This is where it ends. I get stuck at the OnePlus loading screen and forced reboot into twrp and flashed magisk. Once I boot up the OS, I get stuck at the OnePlus logo and that's it.
I actually re-did ALL of the steps again (in case I made a mistake) and still, the same issue. No progression.
Once I gave up on Oreo, I decided to go restore my nandroid
Reboot to recovery. Perform factory reset as mentioned above.
Wiped
Restore everything except bootloader, cache and dalvik cache
Here's the issue:
I press Restore (I uncheck both bootloader and cache, but there's no option for a specific dalvik cache- unless I'm not looking hard enough?) and I get the 255 Error.
Flash nougat twrp recovery. Reboot to system.
I tried to ignore that error and flash the twrp recovery.
Rebooted and it took me to fastboot. Regardless of I keep trying to reboot system it won't work.
I actually made two separate nandroid backups (the same 'everything except system image' as you've described) in case one of the backups was corrupted. Both backups ended up with the same error.
I got too tired of all these errors and just found a stock recovery and ROM and flashed it back. Now, all my apps and settings are gone. To be honest, I just want my phone back to where it was with Nougat.
Can anyone assist me?
Click to expand...
Click to collapse
Buddy from my experience the whole thing too finicky and am thinking just factory reset and stick with stock rom. I wasted so much time already. Everytime I get different error, probably recoveries still not fully compatible with Oreo.
sqlpro said:
@maxs8007, Like I said I did that already but nope still same issue. It wouldn't let me do matter what I did.
---------- Post added at 04:59 AM ---------- Previous post was at 04:54 AM ----------
Buddy from my experience the whole thing too finicky and am thinking just factory reset and stick with stock rom. I wasted so much time already. Everytime I get different error, probably recoveries still not fully compatible with Oreo.
Click to expand...
Click to collapse
Could you please tell me what error you get on the lock screen? Could you post an image so that I can get a better idea of what's happening with your device? Also could you please confirm which files have you deleted? This time you need to delete 5 files which are related to lock screen setting and those are the only files responsible for lock settings on the device. I'm somewhat confused because I never ran into such issue while I did the oreo thing
If you have decided to flash stock then just make a backup of data partition so that you won't loose your data and you can easily restore it via twrp.
---------- Post added at 01:06 AM ---------- Previous post was at 12:42 AM ----------
arthritis said:
I googled oreo twrp image and got an img file with filename "TWRP-Oreo-OnePlus-3-3T". When I installed the img, it asked the options to choose Boot, System, or Recovery - so I chose System.
Click to expand...
Click to collapse
I read the entire post and here what I've to say. The above quoted steps is where you went wrong. The recovery needs to to be flashed as a recovery and not as system.
In your case the nougat recovery was never replaced with the oreo recovery because you flashed it as a system. This is where it went wrong. Sorry for the dalvik cache and USB - otg, I didn't mentioned about them. Those are the least important points in flashing though I should have mentioned that already
The next thing you mentioned is you went back to recovery which at that moment was nougat recovery and not oreo recovery. I'll link the modded recovery I used for oreo below
The next thing you did is you flashed oreo zip and again flashed the oreo recovery but as you flashed the recovery as system, the oreo stock rom was automatically replaced with recovery because you flashed it as system and the device didn't boot because there was no android OS to boot up
You got stuck on oneplus boot up screen. (this was going to happen because of the same flashing error at your end).
You were unable to boot back to nougat as well because of the same issue.. Never flash the recovery as system. This won't let you boot the device.
To restore your nandroid backup just follow the steps below
As you confirmed you booted to stock rom with a stock recovery.
Flash nougat twrp via fastboot
Boot back to the twrp recovery and restore the nandroid backup and you are good to go
---------- Post added at 01:18 AM ---------- Previous post was at 01:06 AM ----------
I'll make a video in my free time to help you guys with the steps that I've followed to flash oreo rom and how i came back to nougat successfully.
Hello @maxs8007
Sorry I didn't have any screen shots of the prompt and finally I was fed up with the whole process and had to switch back to oreo stock rom.
Login prompt I was referring to was standard pin required load android. Black background with only pin entry.
BTW I tried blu twrp recovery oreo version and nougat version.
What's interesting is, after several failed attempts it said I got 10 more tries before phone wiped out but after 10 attempts it started counting backwards from zero, - 1,-2 etc., finally I had to flash stock recovery via fastboot and selected forgot password option which reset my phone.
BTW I have deleted all those files from data/system I found another thread but no dice.
Thank you for trying to help us all.
@maxs8007 followed your steps. Booted to oreo, didn't felt as stable as nougat then booted back to nougat. You saved me. Thanks.
sqlpro said:
Hello @maxs8007
Sorry I didn't have any screen shots of the prompt and finally I was fed up with the whole process and had to switch back to oreo stock rom.
Login prompt I was referring to was standard pin required load android. Black background with only pin entry.
BTW I tried blu twrp recovery oreo version and nougat version.
What's interesting is, after several failed attempts it said I got 10 more tries before phone wiped out but after 10 attempts it started counting backwards from zero, - 1,-2 etc., finally I had to flash stock recovery via fastboot and selected forgot password option which reset my phone.
BTW I have deleted all those files from data/system I found another thread but no dice.
Thank you for trying to help us all.
Click to expand...
Click to collapse
I'm sorry that I was unable to help you. The thing is I never used the pin prompt to load android because I reboot too often to flash things via recovery and its too much of a hassle to enter the pin everytime the device is booted and I think it's too much to a security for a android device when there's already a lock screen present once booted to secure the device.
Please don't put the pin entry to load android next time if you flash stuff regularly. It will save you the hassle of going back to stock rom and recovery when something like this ever happens again. The files which I told you to delete in the image I posted above remove the lock screen protection completely
The login pin at the boot to load android was implemented to avoid unauthorized access to the device in case it gets stolen or lost.
maxs8007 said:
I'm sorry that I was unable to help you. The thing is I never used the pin prompt to load android because I reboot too often to flash things via recovery and its too much of a hassle to enter the pin everytime the device is booted and I think it's too much to a security for a android device when there's already a lock screen present once booted to secure the device.
Please don't put the pin entry to load android next time if you flash stuff regularly. It will save you the hassle of going back to stock rom and recovery when something like this ever happens again. The files which I told you to delete in the image I posted above remove the lock screen protection completely
The login pin at the boot to load android was implemented to avoid unauthorized access to the device in case it gets stolen or lost.
Click to expand...
Click to collapse
Frankly no clue why deleting those files didn't reset my pins and I even deleted gatekeeper files too.
Maybe these are lock screen key files and android boot prompt stored somewhere else. Not sure though.
I just got my 5t a couple of days back. Unlocked the bootloader and used Blu spark twrp and magisk beta for root.
On restart phone would boot up to one plus logo, and then just go black. The notification light goes on. But nothing else.
Help please?
Edit FIXED(No data loss)
1. Boot into TWRP, clear cache. Hard reset(Volume up + Power from a switched off state).
2. Boot back into twrp.
3. Adb push full zip(Found here - Signed Flashable Zip)(Adb push follows this syntax - adb push /(filename).zip /storage/
4. On twrp goto the install menu, navigate to storage and install the file.
5. Optionally you may clear the cache and then install magisk. I couldn't get it to work without magisk but YMMW
Do a hard reset if you still can...
Manish54 said:
Do a hard reset if you still can...
Click to expand...
Click to collapse
Already did that, multiple times. No success.
Same happened to me. It eventually forced into a fastboot bootloop. I had to flash and boot twrp from fastboot again, and then flash the full ota zip and essentially start over.
Decided to skip the root though, until there is a solid ROM release or a stable magisk.
imatts said:
Same happened to me. It eventually forced into a fastboot bootloop. I had to flash and boot twrp from fastboot again, and then flash the full ota zip and essentially start over.
Decided to skip the root though, until there is a solid ROM release or a stable magisk.
Click to expand...
Click to collapse
I tried a similar approach. Cleared dalvik, hard reset then booted into Blu twrp. Flashed Full zip and then magisk again. Booted right up.
therock12123 said:
I tried a similar approach. Cleared dalvik, hard reset then booted into Blu twrp. Flashed Full zip and then magisk again. Booted right up.
Click to expand...
Click to collapse
Yes that was one of my many troubleshooting steps as well, didn't work for me.
Can you help me with this, having a similar issue when I tried to unroot and screwed everything up.
Can anyone help me with this? I'm trying to push via adb the stock os and it looks successful but I don't see it in TWRP.
It's not a big issue, you just flashed the wrong magisk, just boot into recovery and re flash the stock OS
With this type of brick, if u r able to access recovery just go amd reflash, this is not a major brick