Hello,
I've installed a twrp recovery file on my oneplus 6t recently, and for some reason after trying to boot up the OS this frozen "bootloader is unlocked" screen appears. It won't go away! The screen turns black for a second after holding down the volume up+power button, but then goes back to the "bootloader is unlocked" screen again. Draining the battery doesn't help either.
Any ideas on how to fix this?
You probably have to MSMTool it but you could try activating your other partition.
Code:
fastboot --set-active=a
Or
Code:
fastboot --set-active=b
You didn't give much info on what happened exactly. We dig the technical details on here!
Wrapped with delicious Fajita [emoji896]
FiWe20 said:
Hello,
I've installed a twrp recovery file on my oneplus 6t recently, and for some reason after trying to boot up the OS this frozen "bootloader is unlocked" screen appears. It won't go away! The screen turns black for a second after holding down the volume up+power button, but then goes back to the "bootloader is unlocked" screen again. Draining the battery doesn't help either.
Any ideas on how to fix this?
Click to expand...
Click to collapse
Is your phone the T-Mobile or International version?
If International, have a look at this thread and see if the issue you are facing is similar to mine. The solution posted by Mannan Qamar further down the thread is what solved the issue for me, and I've detailed the solution step by step in the latest post in that thread.
Timmmmaaahh said:
You probably have to MSMTool it but you could try activating your other partition.
Code:
fastboot --set-active=a
Or
Code:
fastboot --set-active=b
You didn't give much info on what happened exactly. We dig the technical details on here!
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Thanks for replying!
For some reason after days of desperately trying to fix it, the 6t it suddenly booted into fastboot after being battery-drained. I am not experienced in rooting at all but I think this stuck "bootloader is unlocked" issue happened when I installed the twrp file via the "flash boot_a" instead of the "flash recovery".
FAILED (remote: '(recovery_a) No such partition')
comes up when using the normal "flash recovery".
So the flashing is the main problem I guess. Is there any other way to install twrp?
FiWe20 said:
Thanks for replying!
For some reason after days of desperately trying to fix it, the 6t it suddenly booted into fastboot after being battery-drained. I am not experienced in rooting at all but I think this stuck "bootloader is unlocked" issue happened when I installed the twrp file via the "flash boot_a" instead of the "flash recovery".
FAILED (remote: '(recovery_a) No such partition')
comes up when using the normal "flash recovery".
So the flashing is the main problem I guess. Is there any other way to install twrp?
Click to expand...
Click to collapse
You need to boot TWRP first as there is no recovery partition to flash to (hence the error). From there, you can flash a TWRP installer as explained in the TWRP thread. If you're not knowledgeable or have doubts about the topic then I strongly recommend in reading thoroughly before taking any actions.
Alternatively, you can flash from within Magisk Manager when you get the boot image right as explained in my previous post here. That can be a bumpy ride though! You've been warned
Just note that, with Android 10 (if that is your goal), the safest option is having root without TWRP recovery. If you're sticking with Android Pie, just ignore these last two paragraphs.
Timmmmaaahh said:
You need to boot TWRP first as there is no recovery partition to flash to (hence the error). From there, you can flash a TWRP installer as explained in the TWRP thread. If you're not knowledgeable or have doubts about the topic then I strongly recommend in reading thoroughly before taking any actions.
Alternatively, you can flash from within Magisk Manager when you get the boot image right as explained in my previous post here. That can be a bumpy ride though! You've been warned
Just note that, with Android 10 (if that is your goal), the safest option is having root without TWRP recovery. If you're sticking with Android Pie, just ignore these last two paragraphs.
Click to expand...
Click to collapse
I tried "fastboot boot twrp.img" before but then the next issue comes up...
Sending 'boot.img' (31136 KB) OKAY [ 0.667s]
Booting FAILED (remote: 'unknown command')
FiWe20 said:
I tried "fastboot boot twrp.img" before but then the next issue comes up...
Sending 'boot.img' (31136 KB) OKAY [ 0.667s]
Booting FAILED (remote: 'unknown command')
Click to expand...
Click to collapse
Are you on Android 10? Because in that case this is expected behaviour or in sweet dev terms: by design. OOS Android 10 Beta 1 doesn't allow TWRP for some reason. You can only get it by fastboot flashing a patched boot image or via a Magisk flash. You also need some luck because in both cases it can fail miserably. On top of that, you need some old keymaster to be able to access any files. It's all a true joyride for now, lol...
---------- Post added at 02:18 PM ---------- Previous post was at 02:14 PM ----------
Wait, "fastboot boot twrp.img" gives you "Sending 'boot.img'"? That can't be. Enlighten us on version numbers first please.
Timmmmaaahh said:
Are you on Android 10? Because in that case this is expected behaviour or in sweet dev terms: by design. OOS Android 10 Beta 1 doesn't allow TWRP for some reason. You can only get it by fastboot flashing a patched boot image or via a Magisk flash. You also need some luck because in both cases it can fail miserably. On top of that, you need some old keymaster to be able to access any files. It's all a true joyride for now, lol...
---------- Post added at 02:18 PM ---------- Previous post was at 02:14 PM ----------
Wait, "fastboot boot twrp.img" gives you "Sending 'boot.img'"? That can't be. Enlighten us on version numbers first please.
Click to expand...
Click to collapse
Its interesting because I managed to get TWRP working the first time and if I remember correctly it was via the "flash boot_a" command. And yes it was through the Open Beta version of Android 10. I think this whole "bootloader is unlocked" problem was caused after rebooting from twrp.
How do you fastboot flash a patched boot image if flashing a normal boot image cause errors? I really appreciate you taking your time on this.
---------
Fastboot version 29.0.4-587166
FiWe20 said:
Its interesting because I managed to get TWRP working the first time and if I remember correctly it was via the "flash boot_a" command. And yes it was through the Open Beta version of Android 10. I think this whole "bootloader is unlocked" problem was caused after rebooting from twrp.
How do you fastboot flash a patched boot image if flashing a normal boot image cause errors? I really appreciate you taking your time on this.
Click to expand...
Click to collapse
There could be many reasons; Android works in mysterious ways. The "bootloader is unlocked" screen shows the minute you.. well, unlock your bootloader (fastboot oem unlock)
The fact that it freezes is simply because it finds something to boot but it fails to do so, which could be either an OS or a recovery. I've been there as well but forcing a restart with power+volume buttons did fix it for me (different situation of course, it was months ago).
Trust me, experiencing these annoying situations is the best way to learn more about your device. Before you know it you'll be playing around with fastboot, adb, recoveries, ROMs, kernels and mods like a pro.
Timmmmaaahh said:
There could be many reasons; Android works in mysterious ways. The "bootloader is unlocked" screen shows the minute you.. well, unlock your bootloader (fastboot oem unlock)
The fact that it freezes is simply because it finds something to boot but it fails to do so, which could be either an OS or a recovery. I've been there as well but forcing a restart with power+volume buttons did fix it for me (different situation of course, it was months ago).
Trust me, experiencing these annoying situations is the best way to learn more about your device. Before you know it you'll be playing around with fastboot, adb, recoveries, ROMs, kernels and mods like a pro.
Click to expand...
Click to collapse
Booting OS doesn't work(-> "freeze screen"), recovery mode doesn't work(-> also freeze) and installing new recovery files won't work either because it's in the beta version of android 10. So my 6t is completely broken unless twrp releases an open beta android 10 version of their recovery file?
FiWe20 said:
Booting OS doesn't work(-> "freeze screen"), recovery mode doesn't work(-> also freeze) and installing new recovery files won't work either because it's in the beta version of android 10. So my 6t is completely broken unless twrp releases an open beta android 10 version of their recovery file?
Click to expand...
Click to collapse
Great. What did you do this time? lol. I thought you had it working. Not to worry, you can always resort to the MSMtool (found here). But before you do, there's a few 'softer' methods you can try. I advise reading the first post of this thread.
One piece of advice: if at all possible, try avoiding locking the bootloader again. It serves no purpose and can only create more problems. I have to admit that I haven't used MSMtool myself (been quite lucky so far) but I'm guessing it locks the bootloader in its automated process. If there's a switch to prevent that, use it! If not, ah well...
Timmmmaaahh said:
Great. What did you do this time? lol. I thought you had it working. Not to worry, you can always resort to the MSMtool (found here). But before you do, there's a few 'softer' methods you can try. I advise reading the first post of this thread.
One piece of advice: if at all possible, try avoiding locking the bootloader again. It serves no purpose and can only create more problems. I have to admit that I haven't used MSMtool myself (been quite lucky so far) but I'm guessing it locks the bootloader in its automated process. If there's a switch to prevent that, use it! If not, ah well...
Click to expand...
Click to collapse
Nah. It locks the Bootloader. Meaning if something went wrong you can't do anything. Happened to one guy here but I guess that was cause he erased persist. Another thing about MSM is that it only flashes One Slot.
Mannan Qamar said:
Nah. It locks the Bootloader. Meaning if something went wrong you can't do anything. Happened to one guy here but I guess that was cause he erased persist. Another thing about MSM is that it only flashes One Slot.
Click to expand...
Click to collapse
That's why I referred to the 'softer' methods, sometimes just switching partition slots can solve all your problems.
FiWe20 said:
Booting OS doesn't work(-> "freeze screen"), recovery mode doesn't work(-> also freeze) and installing new recovery files won't work either because it's in the beta version of android 10. So my 6t is completely broken unless twrp releases an open beta android 10 version of their recovery file?
Click to expand...
Click to collapse
MSM tool and stop suffering
FiWe20 said:
Booting OS doesn't work(-> "freeze screen"), recovery mode doesn't work(-> also freeze) and installing new recovery files won't work either because it's in the beta version of android 10. So my 6t is completely broken unless twrp releases an open beta android 10 version of their recovery file?
Click to expand...
Click to collapse
Msm tool dude
Related
First of all i want to say thankyou to the xda community who help people like us and build rooting and other flashing softwares.
So, this is probably my first post on xda, first for sure when i'm stuck and asking for help
Background of the Problem:
I was on OS 2.1.2 rooted with twrp recovery. (was really happy with my phone)
MM 3.0.2 upgrade comes and i decide to upgrade my phone manually (since ota was disabled due to root)
All goes well in first try..(did a dirty flash) OP2 3.0.2 runs smoothly
However, i found out i had lost root and couldn't boot into recovery.
I ignored for a month when i decided it was too hard to go on without root now..
So i searched through a few forums, went into fastboot tried oem unlocking.. failed.. Stuck hard in the bootloop..
Searched for about 3hours and used the MSM tool to finally unlock bootloader.. but still stuck at bootloop and no luck with recovery.. I couldn't boot into my installed rom(3.0.2)
I flashed recovery from OOS 2.1.2 or 2.0.1 and booted into recovery and flashed 2.1.2 again..
So now, 2.1.2 runs fine on my phone
I have refered to these guides/files while trying to install 3.0.2 or trying to recover my phone
http://forum.xda-developers.com/onep...s-3-x-t3392826
https://www.androidfilehost.com/?w=f...f4a13afecc347f
https://www.androidfilehost.com/?w=f...9e2340a15d9033
https://forums.oneplus.net/threads/u...plus-2.347607/
http://forum.xda-developers.com/oneplus-2/general/zip-oxygenos-3-x-t3392826
PROBLEM:
Whenever i update my phone to 3.0.2, it stucks at the bootloop (showing oneplus logo and cmd showing it in fastboot mode)
i lose recovery and rom
i have tried flashing grarak recovery and hybrid recovery (both of which i believe are modded recovery for OOS MM)
In cmd, fastboot flash command completes without any problem but the phone doesnt boot to recovery and both give an error while giving the fastboot boot command
" downloading boot.img
OKAY
booting...
FAILED (remote: dtb not found)"
finished. "
Please suggest me something so that i can boot into 3.0.2 without bootloop problem.. 3.0.2 runs really smooth..
and additionally if possible, i would like to root but thats secondary.
Thankyou guys in advance. Please help a brother out
Sahaj4 said:
First of all i want to say thankyou to the xda community who help people like us and build rooting and other flashing softwares.
So, this is probably my first post on xda, first for sure when i'm stuck and asking for help
Background of the Problem:
I was on OS 2.1.2 rooted with twrp recovery. (was really happy with my phone)
MM 3.0.2 upgrade comes and i decide to upgrade my phone manually (since ota was disabled due to root)
All goes well in first try..(did a dirty flash) OP2 3.0.2 runs smoothly
However, i found out i had lost root and couldn't boot into recovery.
I ignored for a month when i decided it was too hard to go on without root now..
So i searched through a few forums, went into fastboot tried oem unlocking.. failed.. Stuck hard in the bootloop..
Searched for about 3hours and used the MSM tool to finally unlock bootloader.. but still stuck at bootloop and no luck with recovery.. I couldn't boot into my installed rom(3.0.2)
I flashed recovery from OOS 2.1.2 or 2.0.1 and booted into recovery and flashed 2.1.2 again..
So now, 2.1.2 runs fine on my phone
I have refered to these guides/files while trying to install 3.0.2 or trying to recover my phone
http://forum.xda-developers.com/onep...s-3-x-t3392826
https://www.androidfilehost.com/?w=f...f4a13afecc347f
https://www.androidfilehost.com/?w=f...9e2340a15d9033
https://forums.oneplus.net/threads/u...plus-2.347607/
http://forum.xda-developers.com/oneplus-2/general/zip-oxygenos-3-x-t3392826
PROBLEM:
Whenever i update my phone to 3.0.2, it stucks at the bootloop (showing oneplus logo and cmd showing it in fastboot mode)
i lose recovery and rom
i have tried flashing grarak recovery and hybrid recovery (both of which i believe are modded recovery for OOS MM)
In cmd, fastboot flash command completes without any problem but the phone doesnt boot to recovery and both give an error while giving the fastboot boot command
" downloading boot.img
OKAY
booting...
FAILED (remote: dtb not found)"
finished. "
Please suggest me something so that i can boot into 3.0.2 without bootloop problem.. 3.0.2 runs really smooth..
and additionally if possible, i would like to root but thats secondary.
Thankyou guys in advance. Please help a brother out
Click to expand...
Click to collapse
Follow this step one by one ..
1. Flash this recovery via firstboot
https://drive.google.com/file/d/0B0OiN2evbEPuNk5KejhvLWsyeDg/view?usp=drivesdk
2. Now boot into recovery and flash this zip firmware .
https://drive.google.com/file/d/0B0OiN2evbEPucnBkUGZIdlZCSnM/view?usp=drivesdk
3. Now boot into new recovery and flash oxygen os 3.x.x .
That's it.
4. If camera or other sensor not work flash this persist.img file via firstboot.
https://drive.google.com/file/d/0B0OiN2evbEPueVNEQTdUSHJYTHM/view?usp=drivesdk
Jyoti_re said:
Follow this step one by one ..
1. Flash this recovery via firstboot
https://drive.google.com/file/d/0B0OiN2evbEPuNk5KejhvLWsyeDg/view?usp=drivesdk
2. Now boot into recovery and flash this zip firmware .
https://drive.google.com/file/d/0B0OiN2evbEPucnBkUGZIdlZCSnM/view?usp=drivesdk
3. Now boot into new recovery and flash oxygen os 3.x.x .
That's it.
4. If camera or other sensor not work flash this persist.img file via firstboot.
https://drive.google.com/file/d/0B0OiN2evbEPueVNEQTdUSHJYTHM/view?usp=drivesdk
Click to expand...
Click to collapse
Heyy.. Thanks a lot Jyoti_re! It worked out perfectly..
I have done till step 3.. The phone booted into 3.0.2
The sensors are not working. I will flash the presist.img as you said in step 4
However, i have encountered a problem. My OP2 is a 64 GB version. But now the internal storage shows 7gb free out of 9.66 GB.. Earlier it used to show 54GB instead of 9.66..
What should i do?
Thanks again
Yes u must have to flash persist.img via firstboot mode by typing [ fastboot flash persist ] for sensor correctly working.
Install es file explorar from play store and check which folder taking More space
don't forget to press thanks if I helped u.
Thanks a lot Jyoti! /
Yeah i got it.. Flashed the persist img.
i searched through the forums.. somehow my device got the 16gb version img.. i dont know how..
i had to flash userdata64G.img as well
Now it all works perfectly.. sensors are working.. data storage is back at 54gb..
Thanks a lot! I had been stuck on this bootloop since 3 days..
and i pressed the thanks button.. i will press it 100 times over if possible Thanks again! Cheers!
Just to confirm.. Can i flash supersu via recovery now to get root? i hope it wont lead me to bootloops.. If there is some specific supersu file to flash for OOS 3.0.2 please guide me to it.. Thanks!
Sahaj4 said:
Just to confirm.. Can i flash supersu via recovery now to get root? i hope it wont lead me to bootloops.. If there is some specific supersu file to flash for OOS 3.0.2 please guide me to it.. Thanks!
Click to expand...
Click to collapse
Flash this SuperSU
https://drive.google.com/file/d/0B0OiN2evbEPuZk1KSk1hYUpEazA/view?usp=drivesdk
don't forget to press thanks if I helped u.
OP2 stuck in bootloop on upgrading from 2.0.2 to 3.0.2
Hi guys and thanks to all xda developers community for helping us. I'm trying to root my op2 via fastboot,using the comand fastboot oem unlock,but always having this message: <remote oem unlock is disabled>. And when i try to use volume down+power to get in recovery mode the op2 vibrate and flashes the screen and do nothing. I'm not having access to do anything with the op2. Please help...
ciroportugues said:
Hi guys and thanks to all xda developers community for helping us. I'm trying to root my op2 via fastboot,using the comand fastboot oem unlock,but always having this message: <remote oem unlock is disabled>. And when i try to use volume down+power to get in recovery mode the op2 vibrate and flashes the screen and do nothing. I'm not having access to do anything with the op2. Please help...
Click to expand...
Click to collapse
Have u enabled OEM unlocking in developer option ??
No i forgot to enable...
No i forgot to enable... What can i do now?
---------- Post added at 06:44 AM ---------- Previous post was at 06:39 AM ----------
Jyoti_re said:
Have u enabled OEM unlocking in developer option ??
Click to expand...
Click to collapse
No iforgot to enable...
What can i do now?
ciroportugues said:
No i forgot to enable... What can i do now?
---------- Post added at 06:44 AM ---------- Previous post was at 06:39 AM ----------
No iforgot to enable...
What can i do now?
Click to expand...
Click to collapse
Go thru "METHOD 1" of this post and fill free to contact if u face any problem.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Jyoti_re said:
Go thru "METHOD 1" of this post and fill free to contact if u face any problem.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
Hi. I tried to do every steps in method 1,but when i try to enter to recovery mode my op2 vibrate and flash the screen till i stop pressing the power button,and never get into recovery mode.
ciroportugues said:
Hi. I tried to do every steps in method 1,but when i try to enter to recovery mode my op2 vibrate and flash the screen till i stop pressing the power button,and never get into recovery mode.
Click to expand...
Click to collapse
After use the recovery tool the op2 restarts and stuck into powered by android nothing more happens.
ciroportugues said:
After use the recovery tool the op2 restarts and stuck into powered by android nothing more happens.
Click to expand...
Click to collapse
What does the Device Manager show when you connect your phone? By what name is it identified?
Thanks for reply. When i put press volume+and- shows qualcomm hs-usb qdloader9008 (com29),and when i put into fastboot shows android bootloader interface,and when stucks into start shows the same(android bootloader interface).
---------- Post added at 10:06 PM ---------- Previous post was at 09:37 PM ----------
Sahaj4 said:
What does the Device Manager show when you connect your phone? By what name is it identified?
Click to expand...
Click to collapse
Thanks for reply. When i put press volume+and- shows qualcomm hs-usb qdloader9008 (com29),and when i put into fastboot shows android bootloader interface,and when stucks into start shows the same(android bootloader interface).
When you are in fastboot mode..
Try giving the command
"fastboot continue"
or
"fastboot reboot-bootloader"
"fastboot continue"
(without quotes) if your system files are not corrupt, it will boot you into your rom.. and then enable oem unlocking from settings
Tried this commands and the system reboots and stucks on the screen powered by android.
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
Sahaj4 said:
When you are in fastboot mode..
Try giving the command
"fastboot continue"
or
"fastboot reboot-bootloader"
"fastboot continue"
(without quotes) if your system files are not corrupt, it will boot you into your rom.. and then enable oem unlocking from settings
Click to expand...
Click to collapse
Tried this commands but the sistem reboots and stucka on powered by android
ciroportugues said:
Tried this commands and the system reboots and stucks on the screen powered by android.
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
Tried this commands but the sistem reboots and stucks on powered by android
Click to expand...
Click to collapse
Hi. want to know if you anymore command to help me? thanks for help
ciroportugues said:
Hi. want to know if you anymore command to help me? thanks for help
Click to expand...
Click to collapse
I don't know much.. only as much as i have tried..
try running the command
fastboot oem device-info
if your device is unlocked, you are lucky! then there are many options
but if your device is locked.. then as far as i know, msm tool is your only saviour
try using this guide to unbrick your phone
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
EDIT: Fixed! Big thanks to @S0wL , @bkores , @tamahouse02 and @tron1 for the help. I made a guide to help other people with the same problem:
Guide to get TWRP again HERE
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Try the menu on the boot screen.
Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Sounds like the issue is with the ROM like it is somehow blocking you from accessing bootloader mode. It's definitely not my toolkit.
Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system
@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.
Choose an username... said:
@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.
Click to expand...
Click to collapse
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery
tamahouse02 said:
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery
Click to expand...
Click to collapse
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd
Choose an username... said:
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd
Click to expand...
Click to collapse
Not same my axon7tool. I use this https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.
DrakenFX said:
Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.
Click to expand...
Click to collapse
I was thinking about that, but does mifavor let you roll back from an SD update? I'll try later, but i doubt it.
Besides from that is there any way to flash stuff from the stock recovery? It tells me that ZIPs have to be signed only
tamahouse02 said:
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system
Click to expand...
Click to collapse
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?
dnlilas said:
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?
Click to expand...
Click to collapse
Official 3.0.4.1
@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).
dnlilas said:
@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).
Click to expand...
Click to collapse
I use 3.0.4.1 because I flash plenty things before without any issue, so I keep using it.
After write recovery by axon7tool, it's reboot automatically and override the recovery, that why I have to unplug to stop the reboot, and also flash all I can - fortunaeally it also stop recovery be overrided
@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?
I've been in the same situation like you @Choose an username... Updated to nougat on G model and I had not bootloader. This is what I did :
1. Downloaded the tool from here https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
2. Installed the driver using the install driver option that you can choose once you connect you phone to your computer
3. Use the tool to perform the unlock bootloader command again even though you have unlocked it before
4. Use the tool to install twrp, it will boot the phone in twrp
5. Flash Supersu before you boot the system first time after flashing twrp
5. Install whatever version of android want after
@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx
Choose an username... said:
@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx
Click to expand...
Click to collapse
Use Zadig then and let me know if it worked
@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??
Choose an username... said:
@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?
Click to expand...
Click to collapse
I try your version once, but it seems not work for me, so I keep using the old one.
---------- Post added at 03:42 AM ---------- Previous post was at 03:39 AM ----------
Choose an username... said:
@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??
Click to expand...
Click to collapse
I thought you had already unlocked bootloader? Why have you done it twice?
Hi guys, I have kinda big problem.
Yesterday I was messing around with my device just to understand how the a/b partitions work. Then I decided to install a custom rom but TWRP was throwing me errors at the end of the installation (cannot mount /system (access denied) or something like that). After this problem I thought the best solution was to erase every partition (yes, I'm an idiot) throught fastboot and then reflash the phone with msmdownloadtool. I did exactly that and when the unbrick tool finished the phone rebooted and got stuck on the boot screen (the big red circle and the two smaller ones around it). I don't know what to do, I tried almost every version of msmdownloadtool (even the h2os one), I tried unlocking the bootloader, but the phone rejects it and I'm still stuck in a bootloop.
Please help me, I'm running out of ideas and I don't want to have a 570€ paperweight.
Sorry if my english is bad, this is not my native language.
amt911 said:
Hi guys, I have kinda big problem.
Yesterday I was messing around with my device just to understand how the a/b partitions work. Then I decided to install a custom rom but TWRP was throwing me errors at the end of the installation (cannot mount /system (access denied) or something like that). After this problem I thought the best solution was to erase every partition (yes, I'm an idiot) throught fastboot and then reflash the phone with msmdownloadtool. I did exactly that and when the unbrick tool finished the phone rebooted and got stuck on the boot screen (the big red circle and the two smaller ones around it). I don't know what to do, I tried almost every version of msmdownloadtool (even the h2os one), I tried unlocking the bootloader, but the phone rejects it and I'm still stuck in a bootloop.
Please help me, I'm running out of ideas and I don't want to have a 570€ paperweight.
Sorry if my english is bad, this is not my native language.
Click to expand...
Click to collapse
Try only MSMTool again. It is the ultimate solution for bricks.
If that doesn't help, then contact OnePlus and behave dumb. Just say your device stopped working
amt911 said:
Hi guys, I have kinda big problem.
Yesterday I was messing around with my device just to understand how the a/b partitions work. Then I decided to install a custom rom but TWRP was throwing me errors at the end of the installation (cannot mount /system (access denied) or something like that). After this problem I thought the best solution was to erase every partition (yes, I'm an idiot) throught fastboot and then reflash the phone with msmdownloadtool. I did exactly that and when the unbrick tool finished the phone rebooted and got stuck on the boot screen (the big red circle and the two smaller ones around it). I don't know what to do, I tried almost every version of msmdownloadtool (even the h2os one), I tried unlocking the bootloader, but the phone rejects it and I'm still stuck in a bootloop.
Please help me, I'm running out of ideas and I don't want to have a 570€ paperweight.
Sorry if my english is bad, this is not my native language.
Click to expand...
Click to collapse
Lo siento por mi ingles. Tuve el mismo problema y lo resolví con comandos ADB. No recuerdo cómo. Estoy seguro de que tuve suerte ... Tal vez puedas intentarlo. Al menos, la PC debería leer el modo fastboot y comenzar a hacer algo.
I'm sorry for my English. I had the same problem and I solved it with ADB commands. I do not remember how. I'm sure I was lucky ... Maybe you can try it. At least, the PC should read fastboot mode and start doing something.
indian84 said:
Try only MSMTool again. It is the ultimate solution for bricks.
If that doesn't help, then contact OnePlus and behave dumb. Just say your device stopped working
Click to expand...
Click to collapse
I think I'll have to send it to OnePlus. But before that I would like to try to revive it. I can access fastboot, but the bootloader is locked, can I do something in fastboot or with the locked bootloader I'm out of luck?
Thanks.
Don't worry I understood you.
The problem is I can't access to adb because the stock recovery doesn't allow and I can't boot any custom recovery because my bootloader I locked.
Thanks.
I have the same issue with oneplus x, and I followed this method, https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
So try to get stock recovery mode on you phone, then try to flash stock rom. Later you can go for the TWRP and Magisk Installation for Root access.
ACB369 said:
I have the same issue with oneplus x, and I followed this method, https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
So try to get stock recovery mode on you phone, then try to flash stock rom. Later you can go for the TWRP and Magisk Installation for Root access.
Click to expand...
Click to collapse
The problem is the OnePlus 6T doesn't have an adb sideload option in the stock recovery so I can't sideload anything and the msmdownloadtool left me with the bootloader locked, so I can't flash anything in fastboot nor boot a custom recovery.
Thanks.
amt911 said:
The problem is the OnePlus 6T doesn't have an adb sideload option in the stock recovery so I can't sideload anything and the msmdownloadtool left me with the bootloader locked, so I can't flash anything in fastboot nor boot a custom recovery.
Thanks.
Click to expand...
Click to collapse
Try fastbooting the stock boot.img, follow the instructions below...
Reboot to Bootloader
Open up a command prompt in the folder with the boot.img
Enter the command
Code:
fastboot boot *insert boot.img name here*
Nothing, just wait for your phone to boot
1. Download full OTA to your pc and unzip https://androidfilehost.com/?fid=1395089523397891265
2. Edit flash-all-partitions.bat and put this line on the top "fastboot -w" and save
3. double click flash-all-partitions.bat
4. If step 3 still showing error. Edit flash-all-partitions.bat and add "fastboot set_active other" on the top and save then repeat step 3 again.
Sent from my ONEPLUS A6013 using Tapatalk
vichao.s said:
1. Download full OTA to your pc and unzip https://androidfilehost.com/?fid=1395089523397891265
2. Edit flash-all-partitions.bat and put this line on the top "fastboot -w" and save
3. double click flash-all-partitions.bat
4. If step 3 still showing error. Edit flash-all-partitions.bat and add "fastboot set_active other" on the top and save then repeat step 3 again.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I tried entering in fastboot mode and writing "fastboot -w" but it says "FAILED (remote: 'Erase is not allowed in Lock State')". I think it's because the bootloader is locked, I don't know what can I do next.
Thanks.
Is there any way that I could wipe everything in EDL mode? Is the only thing I think it could fix the phone.
Please could you give me more suggestions. I don't know what to do, I flashed the phone with MSMDownloadTool at least ten times and still nothing, it only shows the boot animation and gets stuck there and fastboot doesn't accept any command because of the locked bootloader.
Thanks.
amt911 said:
Please could you give me more suggestions. I don't know what to do, I flashed the phone with MSMDownloadTool at least ten times and still nothing, it only shows the boot animation and gets stuck there and fastboot doesn't accept any command because of the locked bootloader.
Thanks.
Click to expand...
Click to collapse
Which version of the MSM tool are you using?
Is the phone fully charged?
How long are you waiting for the phone to boot? When you say stuck do you just leave the phone alone?
After MSM the first boot is a long time.
tech_head said:
Which version of the MSM tool are you using?
Is the phone fully charged?
How long are you waiting for the phone to boot? When you say stuck do you just leave the phone alone?
After MSM the first boot is a long time.
Click to expand...
Click to collapse
I'm using the v4.0.58 one with OOS 9.0.11, yes the phone is at 75%.
I wait around an hour to see if it boots, but nothing.
When I said that my phone got stuck I meant that it got stuck in the boot animation and nothing else happens.
Yeah, I know, but I don't think it needs an hour to boot.
Thanks.
amt911 said:
I tried entering in fastboot mode and writing "fastboot -w" but it says "FAILED (remote: 'Erase is not allowed in Lock State')". I think it's because the bootloader is locked, I don't know what can I do next.
Thanks.
Click to expand...
Click to collapse
have you try "fastboot set_active other"
Sent from my ONEPLUS A6013 using Tapatalk
---------- Post added at 09:20 PM ---------- Previous post was at 09:17 PM ----------
amt911 said:
I'm using the v4.0.58 one with OOS 9.0.11, yes the phone is at 75%.
I wait around an hour to see if it boots, but nothing.
When I said that my phone got stuck I meant that it got stuck in the boot animation and nothing else happens.
Yeah, I know, but I don't think it needs an hour to boot.
Thanks.
Click to expand...
Click to collapse
sometime flushing cache can solves this kind of issue.
Sent from my ONEPLUS A6013 using Tapatalk
vichao.s said:
have you try "fastboot set_active other"
Click to expand...
Click to collapse
Yes, the same, because the bootloader is locked I can't do anything except "fastboot OEM unlock" which I can't use because I can't access os and I can't turn on oem unlocking.
Thanks.
vichao.s said:
have you try "fastboot set_active other"
Sent from my ONEPLUS A6013 using Tapatalk
---------- Post added at 09:20 PM ---------- Previous post was at 09:17 PM ----------
sometime flushing cache can solves this kind of issue.
Click to expand...
Click to collapse
How can I do that? I tried wiping cache and factory resetting in recovery but nothing. Still in bootloop.
amt911 said:
How can I do that? I tried wiping cache and factory resetting in recovery but nothing. Still in bootloop.
Click to expand...
Click to collapse
Dunno if this will work but after reflashing another time. Boot to stock recovery and factory reset. I dunno the exact procedure but I assume you boot to bootloader and from there boot to recovery and do a factory reset. I had something similar. I flashed OOS via TWRP after soft bricking my phone. And factory reset fixed it. Tho in my case it didn't even load the bootanimation. Just the Unlock Warning and reboot.
Mannan Qamar said:
Dunno if this will work but after reflashing another time. Boot to stock recovery and factory reset. I dunno the exact procedure but I assume you boot to bootloader and from there boot to recovery and do a factory reset. I had something similar. I flashed OOS via TWRP after soft bricking my phone. And factory reset fixed it. Tho in my case it didn't even load the bootanimation. Just the Unlock Warning and reboot.
Click to expand...
Click to collapse
I tried that and it's still stuck on the boot animation, I think it's just a hardware problem because back then with my OnePlus 3T I did the same and it worked just fine. I contacted OnePlus and they accepted sending the phone to them. I'll see when they examine it what is their answer.
Thanks.
What I did to brick it was using this guide: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
And inside the manual flash section there are a lot of fastboot commands.
What I did was using only the fastboot ones and replacing "flash" to "erase" to delete every partition. After that I flashed the phone using msmdownloadtool right away. My question is: Could this be the cause that my phone is in bootloop?
Thanks.
Once I installed the stable version of android Q on my OP6T, I tried to install TWRP on it, however it said "FAILED! Unknown remote command". I then saw a thread saying that they have successfully installed TWRP on android Q on their oneplus6 using 'fastboot flash boot boot.img'. I instead typed 'fastboot flash boot twrp.img' and rebooted the phone. From there my phone is just stuck on the bootloader is unlocked warning screen. The device is unable to be detected by my PC as well. so anything through ADB is not possible. What do I do?
I tried pressing the vol up and power button to get it to fastboot mode, but it just turns off for a second and goes back to the bootloader is unlocked warning screen.
Please help me out
Thank you
AdlietMeyer said:
Once I installed the stable version of android Q on my OP6T, I tried to install TWRP on it, however it said "FAILED! Unknown remote command". I then saw a thread saying that they have successfully installed TWRP on android Q on their oneplus6 using 'fastboot flash boot boot.img'. I instead typed 'fastboot flash boot twrp.img' and rebooted the phone. From there my phone is just stuck on the bootloader is unlocked warning screen. The device is unable to be detected by my PC as well. so anything through ADB is not possible. What do I do?
I tried pressing the vol up and power button to get it to fastboot mode, but it just turns off for a second and goes back to the bootloader is unlocked warning screen.
Please help me out
Thank you
Click to expand...
Click to collapse
First of all: breathe. You'll fix this. Don't worry. And if you really can't (rarely happens), OnePlus has your back.
Did you know you can press power + both volume buttons for about 10 seconds to force the device to go off? Try that, leave it for a couple of seconds and try booting again (normally), try that a few times and if unsuccessful, let us know if booting to fastboot works.
You can go nuclear instantly with MSMTool, that'll be your quickest and easiest way to salvation (if normal booting doesn't work). Don't use this tool just yet, we have another trick to try first (if fastboot works).
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
First of all: breathe. You'll fix this. Don't worry. And if you really can't (rarely happens), OnePlus has your back.
Did you know you can press power + both volume buttons for about 10 seconds to force the device to go off? Try that, leave it for a couple of seconds and try booting again (normally), try that a few times and if unsuccessful, let us know if booting to fastboot works.
You can go nuclear instantly with MSMTool, that'll be your quickest and easiest way to salvation (if normal booting doesn't work). Don't use this tool just yet, we have another trick to try first (if fastboot works).
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Booting into fastboot works, but then what should I do after? Im thinking I should get the stock boot.img since I patched it with that command
AdlietMeyer said:
Booting into fastboot works, but then what should I do after? Im thinking I should get the stock boot.img since I patched it with that command
Click to expand...
Click to collapse
Of course it works, Android is awesome like that. Try:
Code:
fastboot --set-active=a
and reboot (fastboot reboot). If that doesn't work, try
Code:
fastboot --set-active=b
and reboot again. There's a good chance one of the partitions will still boot.
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
Of course it works, Android is awesome like that. Try:
Code:
fastboot --set-active=a
and reboot (fastboot reboot). If that doesn't work, try
Code:
fastboot --set-active=b
and reboot again. There's a good chance one of the partitions will still boot.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
I am able to boot into partition B, it leads me to stock OOS Recovery
Flashing another patched boot image is another option. I used this one. Make sure to flash it to both partitions with these commands:
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
If that fails, you should indeed try a stock img. If you're on a T-Mobile (converted or not) device, go straight to MSMTool.
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
Flashing another patched boot image is another option. I used this one. Make sure to flash it to both partitions with these commands:
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
If that fails, you should indeed try a stock img. If you're on a T-Mobile (converted or not) device, go straight to MSMTool.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
I am able to boot into Partition B, and it leads me to the stock OOS Recovery
AdlietMeyer said:
I am able to boot into Partition B, and it leads me to the stock OOS Recovery
Click to expand...
Click to collapse
I know but if you don't get an OS to boot in, it doesn't have much use. Proceed with the boot image flashing in fastboot. You may need to switch partition to A again when regular reboot doesn't work after flashing.
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
I know but if you don't get an OS to boot in, it doesn't have much use. Proceed with the boot image flashing in fastboot. You may need to switch partition to A again when regular reboot doesn't work after flashing.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
I have flashed the boot image on both partitions, switched to partition A and it booted! THANK YOU SO MUCH!
May I know how do I install TWRP on OOS 10.0.
Do I need to use blu spark twrp?
Timmmmaaahh said:
I know but if you don't get an OS to boot in, it doesn't have much use. Proceed with the boot image flashing in fastboot. You may need to switch partition to A again when regular reboot doesn't work after flashing.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Is there a way to boot into twrp without flashing it? I tried fastboot boot twrp.img but it doesn't work. As I've read this post, if i do fastboot flash boot twrp.img would that brick my device?
I'd recommend to stay away from TWRP until OnePlus supports it as it's a recipe for disaster for the time being.
Glad I could help, don't forget to press those thank you buttons [emoji6]
Wrapped with delicious Fajita [emoji896]
---------- Post added at 12:33 PM ---------- Previous post was at 12:30 PM ----------
AmonRatMC said:
Is there a way to boot into twrp without flashing it? I tried fastboot boot twrp.img but it doesn't work. As I've read this post, if i do fastboot flash boot twrp.img would that brick my device?
Click to expand...
Click to collapse
It just won't work, would be my guess. There are patched images that include TWRP and it could be flashed via Magisk but in both situations the result is unpredictable: a working TWRP, TWRP without decryption or total brick. It's device gambling, lol
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
I'd recommend to stay away from TWRP until OnePlus supports it as it's a recipe for disaster for the time being.
Glad I could help, don't forget to press those thank you buttons [emoji6]
Wrapped with delicious Fajita [emoji896]
---------- Post added at 12:33 PM ---------- Previous post was at 12:30 PM ----------
It just won't work, would be my guess. There are patched images that include TWRP and it could be flashed via Magisk but in both situations the result is unpredictable: a working TWRP, TWRP without decryption or total brick. It's device gambling, lol
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Yeah I guess it's best to just wait until something works for sure instead of taking shots in the dark haha. thank you
Found solution - please delete this post.
ROFL, you know if you read a few threads you could have avoided this.
Also, if you need your phone so urgently always, maybe you should just run stable and not run Betas which are always prone to problems.
Anyway, easy fix to get back to stable.
STUCK
I tried to uninstall magisk module and it didn't boot and I messed something else up with the boot partition and ofc now I have same situation, only that I can't get even into fastboot... And I don't wan't to use msmtool, coz I would lose all the data, but if it's the only choise then I'll do it. If someone can help me with this II would be superrrr happy )
Thevili03 said:
I tried to uninstall magisk module and it didn't boot and I messed something else up with the boot partition and ofc now I have same situation, only that I can't get even into fastboot... And I don't wan't to use msmtool, coz I would lose all the data, but if it's the only choise then I'll do it. If someone can help me with this II would be superrrr happy )
Click to expand...
Click to collapse
What do you mean, "can't get even into fastboot"? What exactly are you trying to do and what results is it getting you? Try pressing all buttons (Power + VolUp + VolDown) for about 10 seconds, then try booting again.
Timmmmaaahh said:
What do you mean, "can't get even into fastboot"? What exactly are you trying to do and what results is it getting you? Try pressing all buttons (Power + VolUp + VolDown) for about 10 seconds, then try booting again.
Click to expand...
Click to collapse
Yeah, my english isn't very great, but I solved my problem. But I tried to press all the buttons like for a minute or so, but no results. But thanks still!
Thevili03 said:
Yeah, my english isn't very great, but I solved my problem. But I tried to press all the buttons like for a minute or so, but no results. But thanks still!
Click to expand...
Click to collapse
How did you get it solved? Sharing is caring =)
Timmmmaaahh said:
How did you get it solved? Sharing is caring =)
Click to expand...
Click to collapse
I actually don't remember excatly anymore but I somehow got in to fastboot and flashed stock boot.img and got it working. Tho I have still problem uninstalling the magisk module, because twrp don't wan't to decrypt my storage, and I tried to build magisk core only mode, but I couldn't do that and I believe that's my only chance to get root again to work. If some one could build me a magisk with only core mode enable I would appreciate it so much(flashable zip or just boot.img which is patched). But yeah, still trying to get everything working...:cyclops: (ps. I hope that my english is understandable XD)
hey guys, i just UNINSTALLED magisk from app within and it reboots to bootloop only at just bootloader unlocked yellow page only. But i not able to boot into either recovery or fastboot. Both are not working. What should i do now? Please help me fast.
---------- Post added at 09:47 PM ---------- Previous post was at 09:41 PM ----------
hey hey hey...i pressed POWER+VOL_UP+VOL_DOWN all at same time and now i can see the official bootloader option where i can select recovery/fastbbot/reload bootloader option by using vol up/down key and power to select. BUT as soon as i select either recovery/fastboot mode, device again turns off and on at the same BL unlocked yellow page and stays there. What should i do?
Was on Rooted device (Magisk), phone got OTA updated, lost root and TWRP, I tried flashing via cmd "twrp-3.2.3-x_blu_spark_v9.86_op6.img" in fastboot mode. Now the phone is forever stuck on the fastboot screen. It won't even switch off. Please tell me how to get out of this situation.
Literally had this happen to me today. Hold volume up and power button worked for me eventually
anthonyg45157 said:
Literally had this happen to me today. Hold volume up and power button worked for me eventually
Click to expand...
Click to collapse
I tried this, the screen goes off for 0.5 seconds and the same Fastboot screen shows up again.
Edit: Never mind, it finally worked after few tries, thanks.
jokerooney said:
I tried this, the screen goes off for 0.5 seconds and the same Fastboot screen shows up again.
Edit: Never mind, it finally worked after few tries, thanks.
Click to expand...
Click to collapse
The device is finally booting, please tell me how do I get my TWRP back now?
jokerooney said:
The device is finally booting, please tell me how do I get my TWRP back now?
Click to expand...
Click to collapse
I used my computer to boot twrp.img then flash twrp.zip
I still don't understand why so many people are using blue spark TWRP..... Nearly all posts in the last few days talking about issues related with twrp were with this one out with outdated versions of mauronaufrio's.
The TWRP to use is latest mauronaufrio's one there is a whole thread about it.
You don't 'flash' twrp in fastboot mode. You temporarily boot the phone with TWRP: 'fastboot boot twrp.img'
And THEN only you flash twrp installer from within this booted twrp.
Striatum_bdr said:
I still don't understand why so many people are using blue spark TWRP..... Nearly all posts in the last few days talking about issues related with twrp were with this one out with outdated versions of mauronaufrio's.
The TWRP to use is latest mauronaufrio's one there is a whole thread about it.
You don't 'flash' twrp in fastboot mode. You temporarily boot the phone with TWRP: 'fastboot boot twrp.img'
And THEN only you flash twrp installer from within this booted twrp.
Click to expand...
Click to collapse
Can you please share mauronaufrio's thread link here? Thanks
jokerooney said:
Can you please share mauronaufrio's thread link here? Thanks
Click to expand...
Click to collapse
Man, there is a whole thread in ROM section.... It's called TWRP