Related
I updated TWRP today to 2.3.0.0 from within GooManager then rebooted into recovery and fixed my permission. It was done unusually fast and when I rebooted, it would get stuck on the booting screen. When I tried to boot into recovery by pressing power and both volume buttons, it would get stuck on the google logo.
Please advise.
Any other way I can fix this or somehow restore from a backup?
A lot of users are having issues with cwm and twrp not booting with new boot loader. You can revert back to old version or some have had success by deleting "recovery-from-boot." file. You can look at http://forum.xda-developers.com/showthread.php?t=1779092 I'm going to wait patiently for a twrp update that should resolve the issue.
Sent from my Nexus 7 using xda premium
Gigabitex2 said:
A lot of users are having issues with cwm and twrp not booting with new boot loader. You can revert back to old version or some have had success by deleting "recovery-from-boot." file. You can look at http://forum.xda-developers.com/showthread.php?t=1779092 I'm going to wait patiently for a twrp update that should resolve the issue.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you very much!
I'm sorry but I'm not too much of an expert on Android. AFAIK Recovery mode is the only way I know to do some low system stuff. If I can't boot into recovery, how else can I do anything to fix this?
How can I revert back to old version?
I know you linked the other thread but there are 33 pages I was hoping you would have a short answer hehe thanks.
Is it constantly rebooting at the google screen or just stuck?
goofball2k said:
Is it constantly rebooting at the google screen or just stuck?
Click to expand...
Click to collapse
If I try to boot into system, it's stuck on boot animation.
If I try to boot into recovery manually (power + volume buttons then select recovery) it would get stuck on Google. It doesn't loop.
I see that you posted over on the twrp thread, hopefully those guys can help you. I am assuming that you have updated to 4.1.2? If you're really stuck maybe try a tool kit like wugs or n7 toolkit? Sorry but SDK isn't one of my strong points either
Sent from my Nexus 7 using xda premium
woshiweili said:
If I try to boot into system, it's stuck on boot animation.
If I try to boot into recovery manually (power + volume buttons then select recovery) it would get stuck on Google. It doesn't loop.
Click to expand...
Click to collapse
You can reflash recovery from fastboot. If you've updated to 4.1.2 you might be experiencing same issue as many of us - being unable to boot to recovery. If that is the case, flash bootloader 3.34 from the JRO03D factory image as well.
Sent from my Nexus 7 using Tapatalk 2
comminus said:
You can reflash recovery from fastboot. If you've updated to 4.1.2 you might be experiencing same issue as many of us - being unable to boot to recovery. If that is the case, flash bootloader 3.34 from the JRO03D factory image as well.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
From what I understand, in order to reflash recovery from fastboot would require me to get the file to the device. However, right now I can't seem to get access at all as it never boots up whether into system or recovery. Are there any other ways to get files onto there?
---
OK this is weird. I tried rebooting into recovery again and it worked! I then rebooted into system and that worked too! This is so strange because I didn't do anything different. I guess it just took 20+ tries... I am not rebooting in a while... lol
woshiweili said:
From what I understand, in order to reflash recovery from fastboot would require me to get the file to the device. However, right now I can't seem to get access at all as it never boots up whether into system or recovery. Are there any other ways to get files onto there?
---
OK this is weird. I tried rebooting into recovery again and it worked! I then rebooted into system and that worked too! This is so strange because I didn't do anything different. I guess it just took 20+ tries... I am not rebooting in a while... lol
Click to expand...
Click to collapse
Hey, glad to hear you're in. In an earlier post you described
woshiweili said:
If I try to boot into recovery manually (power + volume buttons then select recovery) it would get stuck on Google. It doesn't loop.
Click to expand...
Click to collapse
which sounds like you were able to get to fastboot mode (power + vol buttons) - your N7 should look like this. From there you can issue fastboot commands to the device to flash recovery. kerne, and bootloader to name a few.
Actually I spoke too soon.
I can boot into recovery TWRP 2.3 with USB plugged in, but still can't boot into system.
Is it possible for me to downgrade to TWRP 2.2 from within TWRP? I kind of doubt it but am pretty desperate at the moment lol.
Yes, I can get into fastboot, but I'm not sure how to do anything besides pressing volume up or down to start, recovery, fastboot or shut down.
woshiweili said:
Actually I spoke too soon.
I can boot into recovery TWRP 2.3 with USB plugged in, but still can't boot into system.
Is it possible for me to downgrade to TWRP 2.2 from within TWRP? I kind of doubt it but am pretty desperate at the moment lol.
Yes, I can get into fastboot, but I'm not sure how to do anything besides pressing volume up or down to start, recovery, fastboot or shut down.
Click to expand...
Click to collapse
If you can get in to fastboot you are in good shape. :good:
You'll need the fastboot program (and the driver if on Windows) on your computer in order to issue commands. This guide can direct you on how to get that set up.
comminus said:
If you can get in to fastboot you are in good shape. :good:
You'll need the fastboot program (and the driver if on Windows) on your computer in order to issue commands. This guide can direct you on how to get that set up.
Click to expand...
Click to collapse
Thanks for all your help comminus!
Fortunately I was able to wipe everything while I was in recovery and restore from my most recent backup and now it's working fine. At the very least it's allowing me to boot into system
OK I'm really not rebooting for a while lol
I installed twrp a few weeks ago through GooManager and made a backup. When the 4.1.2 update came out, I downloaded it manually with the intent on flashing it via cu custom recovery, but low and behold twrp wasn't working at all. Even with my device plugged into my Win 7 pc... nothing but the exclamation point droid.
I was able to install an updated version of twrp and get everything sorted out, but now I don't have a lot of faith in it, and am booting into recovery at least once a day to make sure it's still working. I never had any problems with cwm.
Twrp has been updated if you're still having issues.
Sent from my Nexus 7 using xda premium
I'm using twrp version 2.3.0.0, and have no plans on updating it because it's stable and working great now
Gigabitex2 said:
Twrp has been updated if you're still having issues.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Updated to 2.3.1.0 but still having booting issues
I followed http://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 this guide in order to root my new p8lite (ale-l21). And it now starts only in recovery as adb shows but im not sure cuz its black screen for me.
So i got unlocked bootloader and updated it to android 6.0 and it all worked fine untill i installed twrp recovery and tried to enter fastboot. It started to boot only in recovery after trying to get in fastboot.
Any Help?
Im Panicing!!!!~
What to do????!!1
asdfqwerty33 said:
I followed http://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 this guide in order to root my new p8lite (ale-l21). And it now starts only in recovery as adb shows but im not sure cuz its black screen for me.
So i got unlocked bootloader and updated it to android 6.0 and it all worked fine untill i installed twrp recovery and tried to enter fastboot. It started to boot only in recovery after trying to get in fastboot.
Any Help?
Im Panicing!!!!~
What to do????!!1
Click to expand...
Click to collapse
Did you try unbricking method? Chapter 4
I also rooted the phone using this method not sure why your phone got into bootloop. What twrp did you flash? 3.0.2? Because that one is for marshmallow.
Suleiman01 said:
Did you try unbricking method? Chapter 4
I also rooted the phone using this method not sure why your phone got into bootloop. What twrp did you flash? 3.0.2? Because that one is for marshmallow.
Click to expand...
Click to collapse
I tried but my phone isnt booting in fastboot it boots only in recovery wich is black screen
I used twrp 3.0.2
asdfqwerty33 said:
I tried but my phone isnt booting in fastboot it boots only in recovery wich is black screen
I used twrp 3.0.2
Click to expand...
Click to collapse
Flash the original recovery and then put firmware(dload folder) in your sdcard and turn on your phone by pressing all buttons. The update should start automatically. Just wait 10~15 mins(even if the screen is black).
Suleiman01 said:
Flash the original recovery and then put firmware(dload folder) in your sdcard and turn on your phone by pressing all buttons. The update should start automatically. Just wait 10~15 mins(even if the screen is black).
Click to expand...
Click to collapse
When i try to flash it to orginal recovery it shows waiting for device and nothing happens
asdfqwerty33 said:
When i try to flash it to orginal recovery it shows waiting for device and nothing happens
Click to expand...
Click to collapse
What happens if you type fastboot devices while phone is in fastboot mode?
Suleiman01 said:
What happens if you type fastboot devices while phone is in fastboot mode?
Click to expand...
Click to collapse
I dont think that i can even enter fastboot. When i try to enter fastboot it enters automaticly recovery mode atleast thats what adb shows
Suleiman01 said:
What happens if you type fastboot devices while phone is in fastboot mode?
Click to expand...
Click to collapse
Holy sh1t i got android back up running . I did like u said pressed all buttons together and waited. Thanks alot man
asdfqwerty33 said:
Holy sh1t i got android back up running . I did like u said pressed all buttons together and waited. Thanks alot man
Click to expand...
Click to collapse
Congratulations. Can you type solved in the title.
Suleiman01 said:
Congratulations. Can you type solved in the title.
Click to expand...
Click to collapse
I dont know how to do that
asdfqwerty33 said:
I dont know how to do that
Click to expand...
Click to collapse
You need to edit first post. Title should be there.
asdfqwerty33 said:
I dont know how to do that
Click to expand...
Click to collapse
SOLVED
I was flashing the MM zip file that was provided with TWRP but when the phone restarted it just got stuck on the logo (not the lg one). Can anyone help me?
RazorMKD said:
I was flashing the MM zip file that was provided with TWRP but when the phone restarted it just got stuck on the logo (not the lg one). Can anyone help me?
Click to expand...
Click to collapse
Did you wipe data before that ?
mayankjet said:
Did you wipe data before that ?
Click to expand...
Click to collapse
I made a mistake by flashing the SuperSU zip without booting into the system first. Can you tell me how to boot into recovery with the hardware buttons ?
Turn off your device then hold down power off + volume down button when you see lg logo release the power button for a second while keeping the volume down button pressed then press and hold down power button again with the volume down pressed. Your phone should boot up into factory reset menu click yes to factory reset. Don't worry click yes to factory reset. It will boot into twrp.
NOTE:- It will only work if you have latest twrp build installed, won't work, if you have first build installed.
mayankjet said:
Turn off your device then hold down power off + volume down button when you see lg logo release the power button for a second while keeping the volume down button pressed then press and hold down power button again with the volume down pressed. Your phone should boot up into factory reset menu click yes to factory reset. Don't worry click yes to factory reset. It will boot into twrp.
NOTE:- It will only work if you have latest twrp build installed, won't work, if you have first build installed.
Click to expand...
Click to collapse
If you still have the first build, you can still enter the recovery by adb with "adb reboot recovery" while the factory reset scrip of the twrp runs. It won't be immediate, you'll probably lose your data but it will work
---------- Post added at 07:18 PM ---------- Previous post was at 07:15 PM ----------
RazorMKD said:
I made a mistake by flashing the SuperSU zip without booting into the system first. Can you tell me how to boot into recovery with the hardware buttons ?
Click to expand...
Click to collapse
You need to use at least SuperSU 2.79, previous versions won't boot and will get stuck al LG logo.:good:
[Happened to me >.<' ]
The problem is I can't start my phone at all. Can't get adb because I can't boot up the system. When I go to recovery TWRP just does something and reboots to the system where it gets stuck again.
RazorMKD said:
The problem is I can't start my phone at all. Can't get adb because I can't boot up the system. When I go to recovery TWRP just does something and reboots to the system where it gets stuck again.
Click to expand...
Click to collapse
Similar thing happened to @MadjijaHacker
https://forum.xda-developers.com/lg...e-poland-v20b-stock-rom-t3565676/post71338313
but, then, he managed to get solved it:
https://forum.xda-developers.com/lg...e-poland-v20b-stock-rom-t3565676/post71339075
You can ask him how did it.
walterfuster said:
Similar thing happened to @MadjijaHacker
https://forum.xda-developers.com/lg...e-poland-v20b-stock-rom-t3565676/post71338313
but, then, he managed to get solved it:
https://forum.xda-developers.com/lg...e-poland-v20b-stock-rom-t3565676/post71339075
You can ask him how did it.
Click to expand...
Click to collapse
I just falshed wrong zip, i flashed rom template, not actual rom
Sent from my LG-H440 using Tapatalk
RazorMKD said:
The problem is I can't start my phone at all. Can't get adb because I can't boot up the system. When I go to recovery TWRP just does something and reboots to the system where it gets stuck again.
Click to expand...
Click to collapse
That "something" that twrp does is probably the factory reset scrip, so you have to keep the phone plug and adb running so while it's doing "that something" use "adb reboot recovery" command
69PerTTu69 said:
That "something" that twrp does is probably the factory reset scrip, so you have to keep the phone plug and adb running so while it's doing "that something" use "adb reboot recovery" command
Click to expand...
Click to collapse
Just tried that and still no success, adb doesn't even register the device while the script is running.
RazorMKD said:
Just tried that and still no success, adb doesn't even register the device while the script is running.
Click to expand...
Click to collapse
Only option left is Download Mode and flash .kdz again.
Take out batery, plug the phone and put the battery on while pressing vol+
By the way, which SuperSu version did you use?
69PerTTu69 said:
Only option left is Download Mode and flash .kdz again.
Take out batery, plug the phone and put the battery on while pressing vol+
By the way, which SuperSu version did you use?
Click to expand...
Click to collapse
I used SuperSU v2.79
[Edit] By the way which tool do I use to flash the old kdz ?
RazorMKD said:
I used SuperSU v2.79
Click to expand...
Click to collapse
I really don't know what happened then. I flashed SuperSU and MM altogether several times (Trying to fix another problem) and I never had a problem.
But well, as long as you have Download Mode you can always start from scratch
69PerTTu69 said:
I really don't know what happened then. I flashed SuperSU and MM altogether several times (Trying to fix another problem) and I never had a problem.
But well, as long as you have Download Mode you can always start from scratch
Click to expand...
Click to collapse
I did that trice trying to fix my problem, 3rd time i figured my mistake
Sent from my LG-H440 using Tapatalk
RazorMKD said:
I used SuperSU v2.79
[Edit] By the way which tool do I use to flash the old kdz ?
Click to expand...
Click to collapse
LG Flash Tool 2014
Remember, without battery plug it to the computer, press Vol+ and then put the battery. It'll show you a message telling you to keep de Vol+ until the "Download Mode" screen appears
Goodluck!:good:
Ok so I got everything back to normal thanks to you guys. But I have a question. I found that there are 2 aboot.bin files in the system. One is in dev/block/bootdevice and one is in dev/block/platform. So do I run the command twice for both or do I do just one ?
RazorMKD said:
Ok so I got everything back to normal thanks to you guys. But I have a question. I found that there are 2 aboot.bin files in the system. One is in dev/block/bootdevice and one is in dev/block/platform. So do I run the command twice for both or do I do just one ?
Click to expand...
Click to collapse
These are the same. Just do
Code:
dd if=/sdcard/aboot_v10f.bin of=/dev/block/mmcblk0p5
assuming aboot_v10f.bin (the patched aboot) is on the root of internal storage.
Thank you very much to everyone that helped. Everything worked perfectly. Had some problems with the official TWRP app so I used Flashify to flash the recovery. For now I am going to use the v10f rom until there is a custom one ( hope we get LineageOS soon ).
Add [SOLVED ]the post title too!
Glad we were useful!
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
Hi everyone, i have an Oneplus 8 pro BA european one.
I was in 10.5.6 rooted and with xXx rom 11.0
I did this to install 10.5.8 update:
Before all Disable all magisk modules
- Update the Rom: settings> System> System upgrade. WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
After reboot magisk seems to be unnistalled:
https://ibb.co/55hJjwH
And also i cant enter into bootloader, i tried first selecting bootloader mode after pressing power buttom,
but in enters in recovery mode not bootloader mode. Then i tried to use ADB commands, adb reboot bootloder. It goes
into recovery again. Finally i tried to select bootloader mode in the recovery, but nothing...
Any idea?
https://youtu.be/mWpstCqT5gw
jumpet said:
Click to expand...
Click to collapse
Isn't that the bootloader itself???
Nandan.R.D said:
Isn't that the bootloader itself???
Click to expand...
Click to collapse
The category of the video is comedy .....
mohammed510 said:
The category of the video is comedy .....
Click to expand...
Click to collapse
:silly::silly::silly:
Nandan.R.D said:
Isn't that the bootloader itself???
Click to expand...
Click to collapse
It is
Lol? comical vid...
Why this thread exists?
Nandan.R.D said:
Isn't that the bootloader itself???
Click to expand...
Click to collapse
didnt knew it was, cause i did fasboot list devices command and nothing happens.
People use to laught at you instead help you btw. Very sad life they have.
[/QUOTE]And also i cant enter into bootloader, i tried first selecting bootloader mode after pressing power buttom,
but in enters in recovery mode not bootloader mode. Then i tried to use ADB commands, adb reboot bootloder. It goes
into recovery again. Finally i tried to select bootloader mode in the recovery, but nothing...
Any idea?[/QUOTE]
Hm...I'm in a similar constellation, after update to 10.5.8 I lost magisk and so root. Somehow the extraction of 10.5.8's boot.img and conversion into magisk_patched.img didn't help me regain boot, but ends in crashdump. But from here, I always can get back to bootloader with long pressing vol+ and power, when screen turns black let go both buttons and immediately press vol- and power which brings me back to recovery, from here into bootloader. reflash stock boot.img and I'm fine, but still no root, of course.
ok now, did you try to simply reflash 10.5.8 from settings/system/systemupdate/local upgrade? :fingers-crossed::fingers-crossed::fingers-crossed:
jumpet said:
didnt knew it was, cause i did fasboot list devices command and nothing happens.
People use to laught at you instead help you btw. Very sad life they have.
Click to expand...
Click to collapse
You are getting in to bootloader , I saw some discussion on the how to root without twrp thread , go check there people are having same issue and I think it works for a dude there and mentioned how he did so :good:
I'm having the same problem. After trying this I get into the CrashDump Mode and can't get out no matter what. Tried to get into the recovery to get fastboot or something but it brings me back to CrashDump Mode. Anybody know how to fix this? kind of don't want a brick here with me... Thanks in advance!
RobotPanda0961 said:
I'm having the same problem. After trying this I get into the CrashDump Mode and can't get out no matter what. Tried to get into the recovery to get fastboot or something but it brings me back to CrashDump Mode. Anybody know how to fix this? kind of don't want a brick here with me... Thanks in advance!
Click to expand...
Click to collapse
you saw my above post? I can always get back to stock recovery like this :fingers-crossed:
jomansch said:
you saw my above post? I can always get back to stock recovery like this :fingers-crossed:
Click to expand...
Click to collapse
I can get into fastboot actually by holding both volume buttons but as soon as I try to get into recovery the screen stays black and my PC says USB device not recognized. I flashed the stock boot image from 10.5.6 but it didn't work as it just goes back to CrashDump Mode...
RobotPanda0961 said:
I can get into fastboot actually by holding both volume buttons but as soon as I try to get into recovery the screen stays black and my PC says USB device not recognized. I flashed the stock boot image from 10.5.6 but it didn't work as it just goes back to CrashDump Mode...
Click to expand...
Click to collapse
try flashing the stock boot.img to both slots ... fastboot set_active (slot), do this for each slot. then fastboot flash boot boot.img (in my case it doesn't matter which slot is set active, my OP8pro does boot anyway). then fastboot boot boot.img. good luck:fingers-crossed:
jomansch said:
try flashing the stock boot.img to both slots ... fastboot set_active (slot), do this for each slot. then fastboot flash boot boot.img (in my case it doesn't matter which slot is set active, my OP8pro does boot anyway). then fastboot boot boot.img. good luck:fingers-crossed:
Click to expand...
Click to collapse
Thank You SO MUCH. I had to set the active slot to slot b in my case and like you said flash the stock boot.img and booted right up! Again, Thank you so much!