Related
Hi everyone i flashed kings marshmallow hydrogen os but i didnt like it so i reverted back to my blisspop via nandroid backup. Unfortunately I am know stuck at the oneplus boot screen with the oneplus logo in the middle and the powered by android logo at the bottom. I am unable to boot into twrp. I was able to boot into fastboot mode and managed to flash twrp recovery however the phone will not load into recovery and goes to the oneplus boot screen. I think i softbriked or hard bricked phone because i went from kings hydrogen os which is marshamllow based to my nandroid backup which is blisspop 5.1. IDK what to do know
Bottom line i can boot into fastboot mode. device manager on my pc recognizes phone as android device- marshall london bootlooder interface any suggestions?
If you can Boot to Fastboot you have a softbrick. Somewhere around here is a thread for the recovery tool with the qualcom drivers. Read carefully and maybe give it a try.
Scherzengel said:
If you can Boot to Fastboot you have a softbrick. Somewhere around here is a thread for the recovery tool with the qualcom drivers. Read carefully and maybe give it a try.
Click to expand...
Click to collapse
Ok i thought that was for hardbrick. I will give it a try anyway
neal425 said:
Ok i thought that was for hardbrick. I will give it a try anyway
Click to expand...
Click to collapse
I installed the qualcom drivers and recovery tool, but the recovery tool doesnt do anything
neal425 said:
Hi everyone i flashed kings marshmallow hydrogen os but i didnt like it so i reverted back to my blisspop via nandroid backup. Unfortunately I am know stuck at the oneplus boot screen with the oneplus logo in the middle and the powered by android logo at the bottom. I am unable to boot into twrp. I was able to boot into fastboot mode and managed to flash twrp recovery however the phone will not load into recovery and goes to the oneplus boot screen. I think i softbriked or hard bricked phone because i went from kings hydrogen os which is marshamllow based to my nandroid backup which is blisspop 5.1. IDK what to do know
Bottom line i can boot into fastboot mode. device manager on my pc recognizes phone as android device- marshall london bootlooder interface any suggestions?
Click to expand...
Click to collapse
Do restore again. Flash 5.1.1 patch youre ok
Do you read OP.. Once you go MM you cannot go back without flashing the patch
lummujaj said:
Do restore again. Flash 5.1.1 patch youre ok
Do you read OP.. Once you go MM you cannot go back without flashing the patch
Click to expand...
Click to collapse
can you please elaborate. I have no way of getting into recovery how am i suppose to flash the patch?
Download twrp 3.0.0.0 (since you were MM ) flash it via adb... Reboot to recovery and flash the patch.. After flashin it automaticlly reboot. Than restore backup
lummujaj said:
Download twrp 3.0.0.0 (since you were MM ) flash it via adb... Reboot to recovery and flash the patch.. After flashin it automaticlly reboot. Than restore backup
Click to expand...
Click to collapse
I have done this already... the recovery will not load
lummujaj said:
Download twrp 3.0.0.0 (since you were MM ) flash it via adb... Reboot to recovery and flash the patch.. After flashin it automaticlly reboot. Than restore backup
Click to expand...
Click to collapse
i flash twrp 3.0 using fastboot flash recovery command.....
just so u know
if i type in adb devices nothing is recognized
if i type in fastboot devices my device is recognized
You cant use adb in fastboot mode.. Wtf
fastboot flash recovery recoveryname.img
fastboot boot recoveryname.img
In recovery flash the patch.. Than restore backup.. So simple. Why you complicate
Post cmd comands and results
lummujaj said:
You cant use adb in fastboot mode.. Wtf
fastboot flash recovery recoveryname.img
fastboot boot recoveryname.img
In recovery flash the patch.. Than restore backup.. So simple. Why you complicate
Post cmd comands and results
Click to expand...
Click to collapse
i did flash via fasboot after i flash it says sending recovery (okay) writing recovery (okay) than i reboot but. but when i try to reboot into recovery it does not reboot into RECOVERY it justs stuck at one plust boot screen.
Stucking 1+ logo is because having unsupported recovery from system... After you did restore did you got any error...
Get both recoveries and try command
fastboot boot recoveryname.img
One of them has to boot. Youre doing something wrong
lummujaj said:
Stucking 1+ logo is because having unsupported recovery from system... After you did restore did you got any error...
Get both recoveries and try command
fastboot boot recoveryname.img
One of them has to boot. Youre doing something wrong
Click to expand...
Click to collapse
after i did restore i did not get an error
ive tried to flash twrp 2.87 and twrp 3.0. i promise u i am flashing the recoveries correctly. each time i flash the recovery it says ok. it just wont boot into recovery after it is flashed
Did you try the coomant to boot automaticlly .. Try both recoveries
fastboot boot recoveryname.img
lummujaj said:
Did you try the coomant to boot automaticlly .. Try both recoveries
fastboot boot recoveryname.img
Click to expand...
Click to collapse
just tried that for both recoverie says downloading boot img okay. than it next thing it says remote: dtb not found
lummujaj said:
Did you try the coomant to boot automaticlly .. Try both recoveries
fastboot boot recoveryname.img
Click to expand...
Click to collapse
hey man i really appreciate you taking the time to help me out but i dont think its gonna work, im just gonna use the hardbrick method to restore my phone
Hope you will find a solution... Try firstaid from general section. I still insist about having bad recovery. Or go to op supoort site and back all to stock
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
You need to run the phone in Qualcomm mode on a PC and run the recovery tool to fix you bootloader.
I did the same and it was a royal ball ache trying to find out how to fix it
Don't do what rosswaa said
Why not?
What you should do is boot your phone into fastboot mode, connect it to your pc. Flash this modified TWRP recovery img to your phone https://www.androidfilehost.com/?fid=24459283995297945. After that you have to flash this modified SuperSU (through the new recovery) https://www.androidfilehost.com/?fid=24459283995297946.
The normal recovery doesn't work in OOS 3.0 (just like in HOS) and it's the SuperSU that gives you the soft brick. A dirty flash of the modified SuperSU should fix it.
I also had your problem and I did what rosswaa said which shouldn't be necessary (I lost all my data and backups).
I didn't lose anything, but I tried doing what you said and my bootloader was screwed so wouldn't take a flashed recovery or anything (yes the modified one)
Wish I hadnt been so excited and just flashed but all sorted now
Hmm okay, if it doesn't work with flashing the new recovery img then do what rosswaa said and after that follow this post https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/
Obviously try what green says first, if it works then happy days
first i am really glad that someone give some advices on me. But since i am a noob, how can i flash twrp in fastboot mode? using command? "fastboot flash recovery xxx.img"? thx
SPiCa39's said:
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
Click to expand...
Click to collapse
1 Install official TWRP 3.x via fastboot twrp.me/devices/oneplustwo.html
Reboot to recovery
2 install this modified version of TWRP
forum.xda-developers.com/oneplus-2/development/recovery-teamwin-recovery-project-3-0-0-t3310713
Reboot to recovery
3 install oos3 (And supersu)
Sorry i can't post link
Hello guys,
I had my phone rooted with latest twrp. I flashed stock+ rom with Franco Kernel 25r and the A.R.I.S.E file for better sound. I've done the same set up minus the ARISE file and never had an issue.
well to my luck it kept bootlooping and I wasn't able to get back into my custom recovery. When I got home and got my hands on a pc I did a factory reset by manually flashing stock google img . I even used a couple tools since I ran out of ideas and still no luck.
I'm able to do anything through fastboot but I can't seem to get into my recovery at all.
Any ideas or tips of where I should go next?
Not a Hardbrick
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
leninmon said:
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
Click to expand...
Click to collapse
First of all thank you for the response.
I've tried flashing the most current twrp and it seems to go through fine on fast boot but when I actually try to get into recovery from the device it will boot loop and just keep doing that.
How can I get into the phones storage through fastboot?
Where can I get the factory zip?
it feels as if everything seems to go good through fastboot but when I actually try to boot the phone nothing seems to work.
Wiltron said:
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
Click to expand...
Click to collapse
Thanks for the reply.
I've done the manual flashing already and flashed everything single item the most current factory image. Everything seemed to have gone through okay but when I rebooted the phone it was back to 0.
I'm actually considering getting rid of the phone now since it is my daily =/
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
leninmon said:
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
Click to expand...
Click to collapse
I flashed the twrp.img and it went through successfully at least on the computer it did but when the phone actually tries to get into recovery (twrp) it will start to boot loop and keep on doing that. I tried both an encrypted and decrypted boot img but it still made no difference.
I'm really going crazy over this
Wiltron said:
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Click to expand...
Click to collapse
I just tried this and had no luck =/....the phone wont get past the google boot screen
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
leninmon said:
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
Click to expand...
Click to collapse
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
edgarted said:
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
Click to expand...
Click to collapse
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
i42o said:
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Click to expand...
Click to collapse
I was really really hoping this would help. I erase/formated everything before flashing anything. I then ran the flash-all file and it took a couple of minutes and it said finished on the command box and my phone restarted and went into the white google logo and rebooted again with a bootloop. I waited around 15 minutes hoping it would start but it didn't.
It honestly feels as if the phone is not processing the full commands but on the pc it seems to go through successfully
is there a way to force an install of a rom and see if maybe a dirty flash over the stock one will allow it to start up?
leninmon said:
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
Click to expand...
Click to collapse
i know how to flash the radio and bootloader but how do i do a fastboot update?
edgarted said:
i know how to flash the radio and bootloader but how do i do a fastboot update?
Click to expand...
Click to collapse
Just unzip the factory image and there U can see the flash shell script files too. Open them in a text editor & U could see the exact command. In a factory img, they also do the same thing via script files. Flashing the radio & bootloader & updating the rest archive
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
edgarted said:
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
Click to expand...
Click to collapse
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
blitzkriegger said:
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
Click to expand...
Click to collapse
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
edgarted said:
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Click to expand...
Click to collapse
This is weird. What version of the stock factory images did you flash? I've been using leviticus 1.3 since it came out and when i was still on stock rom. I switched over to cm builds and have been flashing every nightly since the 7/24th build, and in the process repeatesly reflashing the aound mod along, and i've had zero issues with the phone booting afterwards.
I'm trying to flash TWRP (twrp-3.2.1-0-taido.img) on my Moto E3 Power. I had successfully rooted this phone once, and that's why the phone is unlocked. So when I try to flash custom recovery using the command "sudo fastboot flash recovery twrp-3.2.1-0-taido.img", it says it completed successfully, but instead of booting into twrp, my phone is starting up completely. When I tried booting up custom recovery using "sudo fastboot boot twrp-3.2.1-0-taido.img", the same thing happened again.
The software on my phone is "23.0.XT1706_S151_180706_ROW". So far I've been unable to flash twrp on this phone, but I got it to work an year ago. Please, can anyone help me what's going wrong here? I'm following the tips on xda-forums using which other users were able to flash the same recovery on their phones.
you can try this
ajyotirmay said:
I'm trying to flash TWRP (twrp-3.2.1-0-taido.img) on my Moto E3 Power. I had successfully rooted this phone once, and that's why the phone is unlocked. So when I try to flash custom recovery using the command "sudo fastboot flash recovery twrp-3.2.1-0-taido.img", it says it completed successfully, but instead of booting into twrp, my phone is starting up completely. When I tried booting up custom recovery using "sudo fastboot boot twrp-3.2.1-0-taido.img", the same thing happened again.
The software on my phone is "23.0.XT1706_S151_180706_ROW". So far I've been unable to flash twrp on this phone, but I got it to work an year ago. Please, can anyone help me what's going wrong here? I'm following the tips on xda-forums using which other users were able to flash the same recovery on their phones.
Click to expand...
Click to collapse
Get into the fastboot mode try again unlock your oem
'fastboot oem unlock'(volume up on your phone and select yes ) --->'fastboot format userdata' now flash the twrp recovery the link is below try this it may work worked fine for me and dont know really why the updated twrp is not flashing
My Google Drive link for TWRP recovery:-https://drive.google.com/file/d/0BylQ6RZ2mIP_cElxMzFoRVEyRDg/view?usp=sharing
Hi I had LOS19.1 installed running quite well. I wanted Magisk, so I went to the TWRP website, selected my device, and downloaded latest
twrp-3.7.0_12-1-cheeseburger_dumpling.img
at https://dl.twrp.me/cheeseburger_dumpling/ ...
Booted into fastboot mode, renamed the img to twrp.img, then per the instructions I did...
$ fastboot flash recovery twrp.img this took a minute
$ fastboot reboot
Then when I tried to reboot into recovery it would show the TWRP loading screen for like 30 seconds and phone would shut off... Tried again and same...
Frustrated I thought I would try the oldfashion way and try to boot into the image...
$ fastboot flash boot twrp.img
Same thing happened again with the TWRP loading screen. But it wont boot into the OS now... I got to fastboot and selected START, starts the TWRP loading and powerdown again.
Oh **** did I just overwrite my ROM install? What do I do?
you know the difference between recovery and boot partition? restore the backup of boot.img
read the instructions for installing TWRP
https://forum.xda-developers.com/t/...-a12-cheeseburger-dumpling-25-12-2022.4351795
for rooting device with Magisk, read the instructions for installing Magisk
https://github.com/topjohnwu/Magisk
alecxs said:
you know the difference between recovery and boot partition? restore the backup of boot.img
read the instructions for installing TWRP
https://forum.xda-developers.com/t/...-a12-cheeseburger-dumpling-25-12-2022.4351795
for rooting device with Magisk, read the instructions for installing Magisk
https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
Im assuming boot has to do with booting the OS or bootloader... You mind commenting your thoughts on my mistake and what I should do?
on your second attempt, you flashed recovery into boot partition. you need to restore the boot.img now, otherwise you will boot into TWRP every time.
alecxs said:
on your second attempt, you flashed recovery into boot partition. you need to restore the boot.img now, otherwise you will boot into TWRP every time.
Click to expand...
Click to collapse
lol like in the other thread where would I get the boot.img? (yes I have these 2 devices with these 2 seperate problems). Appreciate your help so far..