Related
Regardless of what recovery I used, (yash28, regalstreak, official twrp) or even starting from the scratch( flashing stock OxygenOS using the Oneplus tools) and then reflashing the recovery, my attempts to succesfully load into a ROM has been futile. As of now, I am pretty much unable to boot into any recovery, and I am stuck using the stock OxygenOS. I tried flashing modem, first attempt was clean flashing the new modem, then flashing it dirty after flashing my rom, I tried doing the same thing with the old modem, my attempts have been futile. If anyone could shed light in this situation, it would be great, I would hate to be stuck using the stock OxygenOS rom, and not try out the great roms that are developed. I can however flash oxygenOS stock rom.
i have the same problem and i cant find any solution i thought of starting fromt he scratch as it didnt help u it might not help me too
Have the same, I've done everything. I've made the phone full stock again and still won't boot.
I have finally found the solution to my own problem
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
So now youre able to flash CM13 without bootloops?
yousuf.shareef said:
So now youre able to flash CM13 without bootloops?
Click to expand...
Click to collapse
Yep! Also make sure you are using official TWRP (https://dl.twrp.me/oneplus2/) Good luck.
abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
FINALLY! Thank you!! Ive been stuck all day without getting ANY MM ROM to boot,. and this ...thing...fixed it! Thanks again
Finally someone found the answer! Unfortunately I wiped whole internal memory and forgot to take backup of whatsapp backup so i lost that. Oh well, all works good now, thank you!
JudderArts said:
Finally someone found the answer! Unfortunately I wiped whole internal memory and forgot to take backup of whatsapp backup so i lost that. Oh well, all works good now, thank you!
Click to expand...
Click to collapse
Dont forget to thank people.
abhisek1994 said:
Dont forget to thank people.
Click to expand...
Click to collapse
JudderArts said:
thank you!
Click to expand...
Click to collapse
That's exactly what I did.
I think i faced the same problem, im using h2os 6.0.1 close beta, with twrp 3.0, but without rooting. I can restore my rom tru twrp without problem. But my try to flash grarak cm13 and new mokee os 6.0 ended up with bootloops, both stuck at oneplus logo
abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
Do you have to go back to the stock rom before flashing persist and then install cm13? or can i do it while i am on the boot logo screen...i tried going into fastboot while stuck on the boot logo (which i was able to) and flashed persist and rebooted but it is still stuck on the boot logo screen
muthukumarc said:
Do you have to go back to the stock rom before flashing persist and then install cm13? or can i do it while i am on the boot logo screen...i tried going into fastboot while stuck on the boot logo (which i was able to) and flashed persist and rebooted but it is still stuck on the boot logo screen
Click to expand...
Click to collapse
You have to downgrade fastboot/bootloader to the Lollipop one (just flash the usual revert_to_lollipop.zip found in these forums as usual).
Please help, I've made the mistake of applying the marshmallow update file, while using the TWRP recovery. It was stuck on writing splashscreen, for around 2hrs. I thought about restarting the device to restore a previous backup image. That is when the screen turned off for good. No matter what i tried, I could not boot into recovery, or even fastboot. I've tried the key combinations, adb, but nothing seems to bring this up to life. Please tell me how to flash the stock zip, I don't care about the data in the phone at this point.
You probably have the same problem I have. Fixed it with this http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
dcduartee said:
You probably have the same problem I have. Fixed it with this http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
I did have the same issue,Thank you. But in the later steps, when the phone boots into fastboot, I cannot use any flash commands. It always shows FAILED (remote: flash_cmds error!). Any ideas?
Can you boot into recovery now? after doing those steps I still had twrp installed and used the recovery.img from the stock rom and then booted back to stock recovery and applied update via adb
dcduartee said:
Can you boot into recovery now? after doing those steps I still had twrp installed and used the recovery.img from the stock rom and then booted back to stock recovery and applied update via adb
Click to expand...
Click to collapse
It did work after another xFSTK download, don't know why the error was caused in the first place. Flashed TWRP and restored a previous backup.
KuntalBiswas said:
It did work after another xFSTK download, don't know why the error was caused in the first place. Flashed TWRP and restored a previous backup.
Click to expand...
Click to collapse
Happened the same to me. Still don't know why it happened xD
Hello everyone,
i just flashed the newest Pure Nexus Rom and everything went fine.
I forgot to flash the SuperSU Zip so i tried to got back into TWRP, but now it stuck.
The System boots normally, only TWRP wont boot.
Anyone had that problem too?
if anyone else has the same issue, here is the answer:
I forgot to erase the userdata or cache.
If you have the same problem use fastboot!
fastboot format cache
fastboot format userdata
Then it should work again.
(Everything on your own risk)
If you dont flah SuperSU asap, TWRP will not stick on reboot (w nougat). That was the issue.
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
kaufikauf said:
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
Click to expand...
Click to collapse
Exactly. It happened before you flashed SuperSU zip. Not flashing SuperSU caused your problem. It needs to be flashed the first time you go into TWRP or you won't be able to boot back into TWRP. The previous poster is correct.
Maybe we talk about different problems
Ive formatted cache and userdata yesterday,
now i can go back into twrp.
(SuperSU is not flashed now).
Just tried it, works perfectly!
kaufikauf said:
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
Click to expand...
Click to collapse
I never, ever flash userdata, and never had an issue.
We can agree to disagree. Either the other poster and I arent understanding your question, or you arent understanding our reply. It's cool, it happens.
But TWRP not sticking is due to not running SuperSU at the end of the install process. It wont stick.
And now i know the misunderstanding!
My sentence was a little bit silly formulated:
It didnt stuck by flashing SuperSU. I just forgot to do that and when i recognized this, i want to boot into recovery. Then i recognized the bootloop.
So SuperSU as itself was not involved. By the way BeansTown wrote in the Thread for PureNexus Rom that you have to format your userdata (normally over TWRP).
Shame on me that i didnt read before start flashing
kaufikauf said:
And now i know the misunderstanding!
My sentence was a little bit silly formulated:
It didnt stuck by flashing SuperSU. I just forgot to do that and when i recognized this, i want to boot into recovery. Then i recognized the bootloop.
So SuperSU as itself was not involved. By the way BeansTown wrote in the Thread for PureNexus Rom that you have to format your userdata (normally over TWRP).
Shame on me that i didnt read before start flashing
Click to expand...
Click to collapse
You should take a look at this post in the official TWRP thread for a clearer reason why.
SlimSnoopOS said:
You should take a look at this post in the official TWRP thread for a clearer reason why.
Click to expand...
Click to collapse
So I followed the guide and updated to 7.1.1 and did the normal "fastboot flash recovery xxx" then "fastboot reboot bootlader" then rebooted it via phone I go to "Recovery" from my phone and I get a screen saying "No Command" I tried to flash twrp-3.0.3-0-angler.img
Did I miss something?
USFguy said:
So I followed the guide and updated to 7.1.1 and did the normal "fastboot flash recovery xxx" then "fastboot reboot bootlader" then rebooted it via phone I go to "Recovery" from my phone and I get a screen saying "No Command" I tried to flash twrp-3.0.3-0-angler.img
Did I miss something?
Click to expand...
Click to collapse
After flashing TWRP from the bootloader, go directly into recovery and flash SuperSU 2.78 or newer to make it stick permanently.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
After flashing TWRP from the bootloader, go directly into recovery and flash SuperSU 2.78 or newer to make it stick permanently.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
It won't boot into recovery, I flash recovery, unplug device hit recovery boot and it boot loops once then boots normally....
USFguy said:
It won't boot into recovery, I flash recovery, unplug device hit recovery boot and it boot loops once then boots normally....
Click to expand...
Click to collapse
Hmm. If you are on stock, reflash the boot, system, recovery, and vendor from the factory image that matches your stock, security update. Restart the phone and boot into Android. Restart into the bootloader then fastboot flash recovery TWRP-angler.img. See if it lets you boot into TWRP then. If not, try an older version of TWRP and see if that will flash and allow you to boot into it.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Hmm. If you are on stock, reflash the boot, system, recovery, and vendor from the factory image that matches your stock, security update. Restart the phone and boot into Android. Restart into the bootloader then fastboot flash recovery TWRP-angler.img. See if it lets you boot into TWRP then. If not, try an older version of TWRP and see if that will flash and allow you to boot into it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Tried that, ended up going down an update in TWRP and it worked, weird....
I had a similar issue and I had to go back in and reflash Recovery image to recovery partition and all was well
Hi, I have a essential phone running Oreo 8.1, just recently I have rooted the phone with magisk v16 an twrp 3.2.1, I successfully flashed it with twrp but after the flash whenever I want to get into twrp it just freezes up on the mount data screen and I have to force reboot it, does anyone know a solution to this problem
Make sure you're following the exact steps from this post. Every step is crucial (except #3, because you have to disable your screen lock before booting twrp.
You shouldn't have to manually mount anything in TWRP either. The magisk installer might give you an error about mounting system but it doesn't seem to make any difference.
[QRCODE][/QRCODE]
yellk20 said:
Hi, I have a essential phone running Oreo 8.1, just recently I have rooted the phone with magisk v16 an twrp 3.2.1, I successfully flashed it with twrp but after the flash whenever I want to get into twrp it just freezes up on the mount data screen and I have to force reboot it, does anyone know a solution to this problem
Click to expand...
Click to collapse
You cannot have TWRP installed with 8.x.
TWRP is not compatible.
You must flash the original boot image, then install magisk.
TWRP cannot remain.
You will boot loop.
Please read the instructions on rooting carefully.
Ok thank you
Why can't TWRP replace recovery instead of boot?
RawSlugs said:
Why can't TWRP replace recovery instead of boot?
Click to expand...
Click to collapse
No one has created a bit image with TWRP as the recovery.
Sent from my PH-1 using XDA Labs
RawSlugs said:
Why can't TWRP replace recovery instead of boot?
Click to expand...
Click to collapse
Because the partition layout of the Essential does not have a recovery partition.
Recovery is contained in the boot image.
So to have TWRP resident/permanent, the boot image must be patched.
It has been done for 7.x, but sense 8.x is still beta, there is no official TWRP for Oreo.
Once Oreo is final, I expect we will get a TWRP that works.
The current limitation, means you can't flash without a computer handy.
So after a long battle with flashing magisk that resulted in a bootloop everytime I was only able to boot again after flashing the magiskuninstaller. I decided to flash magisk again, flash dmverityencryption disabler and format data as some users suggested.
Now i'm stuck in a full on bootlop.
I decided to wipe everything and just flash the latest miui11 (11.0.4.0) cause that fixed my problems last time. But this time i'm still stuck in a bootloop after flashing the rom. I also noticed that the persist partition is missing for some reason, not sure if it's supposed to be like this. Luckily the phone still boots to orangefox recovery so hopefully I can fix this.
Any advice guys?
beybus said:
So after a long battle with flashing magisk that resulted in a bootloop everytime I was only able to boot again after flashing the magiskuninstaller. I decided to flash magisk again, flash dmverityencryption disabler and format data as some users suggested.
Now i'm stuck in a full on bootlop.
I decided to wipe everything and just flash the latest miui11 (11.0.4.0) cause that fixed my problems last time. But this time i'm still stuck in a bootloop after flashing the rom. I also noticed that the persist partition is missing for some reason, not sure if it's supposed to be like this. Luckily the phone still boots to orangefox recovery so hopefully I can fix this.
Any advice guys?
Click to expand...
Click to collapse
U flash the 11.0.4.0 fastboot rom or over twrp?
joke19 said:
U flash the 11.0.4.0 fastboot rom or over twrp?
Click to expand...
Click to collapse
Thanks for the answer. So far I only tried flashing over twrp, should I download the fastboot version and try with miflash?
Yes but look that u don't lock ur bootloader
joke19 said:
Yes but look that u don't lock ur bootloader
Click to expand...
Click to collapse
Okay, after using the miflash tool the phone boots up again. Now i'll fastboot the orangefox recovery. How do I got about flashing magisk after that so I avoid bootloop again?
beybus said:
Okay, after using the miflash tool the phone boots up again. Now i'll fastboot the orangefox recovery. How do I got about flashing magisk after that so I avoid bootloop again?
Click to expand...
Click to collapse
Backup and test. Normally no problem, only by updates with old modules