Related
hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Snow201 said:
hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Click to expand...
Click to collapse
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
FatherD said:
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
Click to expand...
Click to collapse
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Snow201 said:
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Click to expand...
Click to collapse
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
osugsxr said:
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
Click to expand...
Click to collapse
NVM, there is no recovery for HTC at all, only Galaxy and some more. what i need to do?
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
k1llacanon said:
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Snow201 said:
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Click to expand...
Click to collapse
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
k1llacanon said:
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Snow201 said:
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Click to expand...
Click to collapse
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
frdd said:
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
Click to expand...
Click to collapse
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Snow201 said:
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Click to expand...
Click to collapse
If you have working ADB and fastboot working (there is a sticky by user fibsib that explains this) you can make sure your phone isnt really just trying to boot the OS and failing rather than trying to enter recovery with the command
Code:
adb reboot recovery
But anyways figure out which version you have before doing anything more, flash the wrong stuff and you could break stuff. There are good info here as to how to see if you have the Ville=Z520e=S4 processor model or the Ville C2/Z560e/S3 processor model.
Then download a recovery for your phone model and install it with this command from your computer
Code:
fastboot flash recovery nameofrecoveryyoudownloaded.img
Should work.
have you actually flashed a recovery yet?
which one and how did you do it?
Make sure you have your phone updated to the latest software version before you root. Download system update OTA and click update.
Otherwise you will have issues.
I am rooted T-Mobile phone with original software 1.54 and still can not do recovery or update, it is probably me but it is difficult.
If you are in the US, make sure you use the US version in the development section after you upgrade your phone. Update then try to root it might be easier.
Hello XDA members
i have a big problem, when i want to open SuperSU a box popup saying that you must update SU binary then it asks what kind of method do you want to update "Normal" or "TWRP/CWM", when i choose "Normal" it failed to update, when i choose "TWRP/CWM" it reboots into recovery, i don't know what to do. Any one can help please.
Thanks.
Superuser.apk
hbforce said:
Hello XDA members
i have a big problem, when i want to open SuperSU a box popup saying that you must update SU binary then it asks what kind of method do you want to update "Normal" or "TWRP/CWM", when i choose "Normal" it failed to update, when i choose "TWRP/CWM" it reboots into recovery, i don't know what to do. Any one can help please.
Thanks.
Click to expand...
Click to collapse
I think it's much better if you install Superuser.apk rather than SuperSU.apk, you can find it here http://androidsu.com/superuser/
Download its files (superuser and su-binary) that appropriate to your device and then flash it via Recovery (CWM/TWRP).
im having the same problem, i will install superuser but how do i uninstall SuperSU ?
You must install supersu by recovery. Search for supersu on xda and download de latest version in zip version. Install it with e recovery and enjoy it.
Sent from my HTC One S using XDA Premium 4 mobile app
hbforce said:
when i want to open SuperSU a box popup saying that you must update SU binary then it asks what kind of method do you want to update "Normal" or "TWRP/CWM", when i choose "Normal" it failed to update, when i choose "TWRP/CWM" it reboots into recovery, i don't know what to do.
Click to expand...
Click to collapse
Try to use the recovery method several times. It will probably work after some tries. Also, did you update superSU from the market? Do this first.
Try to install SuperUSER.zip via recovery.
It will root your phone and It will install Superuser apk.
I had the same issue and now, superuser works fine <3
Sent from my HTC One S using xda app-developers app
xQubee5o3 said:
Try to install SuperUSER.zip via recovery.
It will root your phone and It will install Superuser apk.
I had the same issue and now, superuser works fine <3
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I have SuperSU and I also have the problem with the binary update failing. Can you please tell me how to install supersu via recovery? How to install anything via recovery?
Thanks, I am good at administrating windows PCs, but android is a totally new field to me...
jantinak said:
I have SuperSU and I also have the problem with the binary update failing. Can you please tell me how to install supersu via recovery? How to install anything via recovery?
Thanks, I am good at administrating windows PCs, but android is a totally new field to me...
Click to expand...
Click to collapse
SuperSU flashable zip can be found here.
Hi - I didn't have a problem finding the zip - that is easy. I don't know how to flash these things "via recovery" or whatever that means...
I found some guides which say how to flash zips through recovery CWM / TWRP, but as I dug deeper, these things require root to function properly, but that is the thing - I don't have the root, since I cannot update the SU binary library, see?
Also - when I tried to get to the recovery mode by pressing the buttons as it was stated in the guide, I got into some mode, but I got only an image of phone and cable connected to it, which was crossed by red lines. And no menu, nothing... it seemed, that the phone should be connected to the PC, but the guide didn't say anything about connecting phone to PC before entering recovery mode.
Could you help me solve this issue with binary thing from ground up?
Thanks
jantinak said:
Hi - I didn't have a problem finding the zip - that is easy. I don't know how to flash these things "via recovery" or whatever that means...
I found some guides which say how to flash zips through recovery CWM / TWRP, but as I dug deeper, these things require root to function properly, but that is the thing - I don't have the root, since I cannot update the SU binary library, see?
Also - when I tried to get to the recovery mode by pressing the buttons as it was stated in the guide, I got into some mode, but I got only an image of phone and cable connected to it, which was crossed by red lines. And no menu, nothing... it seemed, that the phone should be connected to the PC, but the guide didn't say anything about connecting phone to PC before entering recovery mode.
Could you help me solve this issue with binary thing from ground up?
Thanks
Click to expand...
Click to collapse
1. Unlock your bootloader via HTCdev.com
2. flash a custom recovery via fastboot (This toolkit will help you --> LINK
3. flash superuser
LS.xD said:
1. Unlock your bootloader via HTCdev.com
2. flash a custom recovery via fastboot (This toolkit will help you --> LINK
3. flash superuser
Click to expand...
Click to collapse
I have LG P880, not HTC phone...
Just how do I go about flashing it? It seems the only way to boot into recovery mode is to have root access which I don't have because Supersu needs an update. It's all a tiring cycle.
Hi guys, a few day ago my One SV had some problems, rebooting itself and runs very slowly; so i tryed to do something like root it, but not knowing what i'm doing 'cause i don't have much time.
Probably installing a wrong rom, now I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags.
The phone stuck with htc logo, i only manage to go into bootloader, pdanet gives me sync error, twrp recovery doesn't work anymore.
Is there something I can do now?
VictorCic said:
Hi guys, a few day ago my One SV had some problems, rebooting itself and runs very slowly; so i tryed to do something like root it, but not knowing what i'm doing 'cause i don't have much time.
Probably installing a wrong rom, now I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags.
The phone stuck with htc logo, i only manage to go into bootloader, pdanet gives me sync error, twrp recovery doesn't work anymore.
Is there something I can do now?
Click to expand...
Click to collapse
As long as your device is Locked, you can't flash a custom recovery.
So unlock your device at htcdev.com, flash Twrp recovery and flash back a working rom.
Use a Android 4.1.2 rom, otherwise you will have problems with noisy sound.
old.splatterhand said:
As long as your device is Locked, you can't flash a custom recovery.
So unlock your device at htcdev.com, flash Twrp recovery and flash back a working rom.
Use a Android 4.1.2 rom, otherwise you will have problems with noisy sound.
Click to expand...
Click to collapse
Thanks, i've unlocked it and flashed Twrp recovery, but trying to using this last one always says unable to mount sd...
And could you help me to find the right rom or stock rom?
And trying to put it in s-off with revone, rumrunner, moonshine doensn't work
Thank you very much!
VictorCic said:
Thanks, i've unlocked it and flashed Twrp recovery, but trying to using this last one always says unable to mount sd...
And could you help me to find the right rom or stock rom?
And trying to put it in s-off with revone, rumrunner, moonshine doensn't work
Thank you very much!
Click to expand...
Click to collapse
How do you mount the sd?
At least pull it out of your device and put it into your PC and copy needed files in this way.
One thing i could not solve earlier (because of bad internet connection): did you already install the Android 4.2.2 update or what was your software running on your device before? Thats important to give you the right rom for your firmware!
I'll give you the links anyway:
4.1.2 -> http://forum.xda-developers.com/showthread.php?t=2254384
4.2.2 -> http://forum.xda-developers.com/showthread.php?t=2512742
Rumrunner & moonshine are confirmed working for your hboot, but which you should use at least also depends on your previous software.
old.splatterhand said:
How do you mount the sd?
At least pull it out of your device and put it into your PC and copy needed files in this way.
One thing i could not solve earlier (because of bad internet connection): did you already install the Android 4.2.2 update or what was your software running on your device before? Thats important to give you the right rom for your firmware!
I'll give you the links anyway:
4.1.2 -> http://forum.xda-developers.com/showthread.php?t=2254384
4.2.2 -> http://forum.xda-developers.com/showthread.php?t=2512742
Rumrunner & moonshine are confirmed working for your hboot, but which you should use at least also depends on your previous software.
Click to expand...
Click to collapse
Im sorry That error is from the twrp recovery when i try to install superuser.. It says unable to mount int sd.. I think internal memory
Ignore it. Only use the files, recommended in my index thread (use SuperSu, not Superuser), link in my signature.
And answer the other question.
old.splatterhand said:
Ignore it. Only use the files, recommended in my index thread (use SuperSu, not Superuser), link in my signature.
And answer the other question.
Click to expand...
Click to collapse
Sorry i had update it to 4.2.2
Ok, so you can use the second link for the stock rom. And rumrunner for S-off.
old.splatterhand said:
Ok, so you can use the second link for the stock rom. And rumrunner for S-off.
Click to expand...
Click to collapse
I installed the 4.2.2 versions, seems completed but phone remains with black screen showing only the top bar with the clock, then reboot itself; sometimes after reboot it shows the bottom clock and lock, you can also unlock it, but then it reboots;
One time it shows me the backgroud.
Maybe it's a motherboard problem, what do you think?
Thanks
VictorCic said:
I installed the 4.2.2 versions, seems completed but phone remains with black screen showing only the top bar with the clock, then reboot itself; sometimes after reboot it shows the bottom clock and lock, you can also unlock it, but then it reboots;
One time it shows me the backgroud.
Maybe it's a motherboard problem, what do you think?
Thanks
Click to expand...
Click to collapse
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
old.splatterhand said:
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
Click to expand...
Click to collapse
Yes, flashed boot.img and wipe data/cache/dalvik.
Later i'm gonna try the 4.1.2.. I hope that will work
VictorCic said:
Yes, flashed boot.img and wipe data/cache/dalvik.
Later i'm gonna try the 4.1.2.. I hope that will work
Click to expand...
Click to collapse
old.splatterhand said:
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
Click to expand...
Click to collapse
installed the 4.1.2 version..same as before (black screen, only the first time turned on it showed the background), apart it can show every time the ring to unlock the screen; unlocking it it reboot itself...
VictorCic said:
installed the 4.1.2 version..same as before (black screen, only the first time turned on it showed the background), apart it can show every time the ring to unlock the screen; unlocking it it reboot itself...
Click to expand...
Click to collapse
Stop. Did you only wipe data/cache/dalvik.
No system?
You need to wipe all, except internal & external sd!
old.splatterhand said:
Stop. Did you only wipe data/cache/dalvik.
No system?
You need to wipe all, except internal & external sd!
Click to expand...
Click to collapse
Also system yes. And if i wiped the internal sd?
anyway after installing the rom, from twrp internal storage is 0 MB
Then i'm running out of ideas
As the roms worked for other people, i also start thinking thats something bugged with your device.
You checked md5sum of the roms? Using latest TWRP recovery?
old.splatterhand said:
Then i'm running out of ideas
As the roms worked for other people, i also start thinking thats something bugged with your device.
You checked md5sum of the roms? Using latest TWRP recovery?
Click to expand...
Click to collapse
Yes, used the latest TWRP recovery.
the recovery say to me no md5 file, is this the problem?
How can I check the md5 now?
I don't know the name of the tool (i'm at work), but you will find it with google search, i think.
In recovery this is not a problem, its only to check on your pc, if the downloaded file is the same as the upload.
old.splatterhand said:
I don't know the name of the tool (i'm at work), but you will find it with google search, i think.
In recovery this is not a problem, its only to check on your pc, if the downloaded file is the same as the upload.
Click to expand...
Click to collapse
Checked, the codes matches..
Then i think your device has a defect
old.splatterhand said:
Then i think your device has a defect
Click to expand...
Click to collapse
Hi, i managed to change the motherboard, so trying to put a mod, the phone now stuck on the htc logo...
I unlocked it with htcdev, then installed the recovery but this one doesn't work, it says starting recovery but doesn't start..(trying to install a different recovery, it seems unable to rewrite it)
trying to do something i flashed with fastboot the stock boot.img and now the phone doesn't start anymore..
what can i do now? :crying:
Last night i decided it was finally time to root and put recovery onto my shield tablet. everything went smoothly that is untill i tried to boot into recovery (TWRP) everytime i try to enter recovery there's a picture of a dead android with a triangle on him with the words "no command" ...the only way i've been able to get back into recovery is to flash the image again. but once i leave twrp it's gone again. does anyone have any suggestions please. if you need more information, let me know
Thanks
Habbz said:
Last night i decided it was finally time to root and put recovery onto my shield tablet. everything went smoothly that is untill i tried to boot into recovery (TWRP) everytime i try to enter recovery there's a picture of a dead android with a triangle on him with the words "no command" ...the only way i've been able to get back into recovery is to flash the image again. but once i leave twrp it's gone again. does anyone have any suggestions please. if you need more information, let me know
Thanks
Click to expand...
Click to collapse
You unlocked your bootloader before, right?
seems the original recovery is working, and not twrp.
after boot loader unlock you flashed TWRP via fastboot?
Yeah first thing i did was unlock the bootloader , then proceeded to root. i've installed a custom rom too ( Lineage os)...but i just can't seem to get into TWRP when rebooting , even with the button combo. the files for TWRP are on my tablet but i just can't access it. i followed this guide
http://nvidiashieldzone.com/shield-...shmallow/root-shield-tablet-v1-marshmallow-2/
Habbz said:
Yeah first thing i did was unlock the bootloader , then proceeded to root. i've installed a custom rom too ( Lineage os)...but i just can't seem to get into TWRP when rebooting , even with the button combo. the files for TWRP are on my tablet but i just can't access it. i followed this guide
http://nvidiashieldzone.com/shield-...shmallow/root-shield-tablet-v1-marshmallow-2/
Click to expand...
Click to collapse
Don t know how old the twrp is? Can t try it now, cause our web protection blocked the site.
I use always the last recovery from official twrp site
https://twrp.me/devices/nvidiahshieldtablet.html
Steps.
-bootloader unlock.
-'fastboot flash recovery /place/of/your/recovery'
after that you can flash custom roms and/or root with supersu or magisk..
If you did not start TWRP, how could you flash linageos?
wiQbold said:
Don t know how old the twrp is? Can t try it now, cause our web protection blocked the site.
I use always the last recovery from official twrp site
https://twrp.me/devices/nvidiahshieldtablet.html
Steps.
-bootloader unlock.
-'fastboot flash recovery /place/of/your/recovery'
after that you can flash custom roms and/or root with supersu or magisk..
If you did not start TWRP, how could you flash linageos?
Click to expand...
Click to collapse
Once i flashed TWRP it automatically put me into it after a few seconds, but then when i rebooted or asked to be put into recovery it gave me the no command line, the version of TWRP was old and i just installed the latest one like you mentioned and now it's working again. thanks for replying though, it might help someone else out in the same position.
Just one last question, do i need Xposed for Magisk ? i'm on nougat and haven't seen much about it apart from an unnoficial release.
Habbz said:
Once i flashed TWRP it automatically put me into it after a few seconds, but then when i rebooted or asked to be put into recovery it gave me the no command line, the version of TWRP was old and i just installed the latest one like you mentioned and now it's working again. thanks for replying though, it might help someone else out in the same position.
Just one last question, do i need Xposed for Magisk ? i'm on nougat and haven't seen much about it apart from an unnoficial release.
Click to expand...
Click to collapse
maybe you wait for official xposed. what modules are you looking for?
there are many alternatives and/or magisk modules that can do some work ..
I only missed gravitybox cause of customisation of the statusbar and xprivacy..
don t tried the early xposed, cause there is no need for me.
but your problem was solved? good
wiQbold said:
maybe you wait for official xposed. what modules are you looking for?
there are many alternatives and/or magisk modules that can do some work ..
I only missed gravitybox cause of customisation of the statusbar and xprivacy..
don t tried the early xposed, cause there is no need for me.
but your problem was solved? good
Click to expand...
Click to collapse
I'm looking for one that can play remote play, heard it uses Magisk , i'm not too sure though, yeah it's been solved thanks.
Hi everyone!
Issue is pretty simple to explain - after upgrading via OTA from the latest open beta Pie (29) to open beta Android 10 (30), I can't boot into recovery.
System works normally, the only thing I'm having trouble with are the generic issues discussed on the OP community forum (autorotate and other sensors, Gboard gap...). It is recommended repeatedly that one should reboot to recovery and wipe the cache partition.
The problem is that I can only get into fastboot mode - tried the advanced boot menu, adb/fastboot and selecting recovery mode while in the fastboot mode but it always goes into fastboot.
TWRP doesn't support android 10 yet as far as I know and I've found no other reference of this issue anywhere else. Only thing that comes to mind is to wait for the next open beta and hope it will be resolved after another OTA.
Thanks for your help!
seems the open beta install was more bad for you than mine. Upgraded from op29 to op30 like you, but i had everything stock. No unlocked bootloader, no big customizations, etc. I just tried entering recovery mode via fastboot and it worked like normal for me, had to enter my pin to decrypt my data, and the rest like normal. I'd suggest to downgrade back to pie and reflash the open beta software to see if the issue is gone or not, but that's your call to do so.
HighOnLinux said:
seems the open beta install was more bad for you than mine. Upgraded from op29 to op30 like you, but i had everything stock. No unlocked bootloader, no big customizations, etc. I just tried entering recovery mode via fastboot and it worked like normal for me, had to enter my pin to decrypt my data, and the rest like normal. I'd suggest to downgrade back to pie and reflash the open beta software to see if the issue is gone or not, but that's your call to do so.
Click to expand...
Click to collapse
I think you stumbled across the answer everyone has been searching for. How did you upgrade? Did you download the whole zip and flash through updated?
This kinda makes sense. Do you remember how big the update file was? It could have been an incremental rather than a full if you weren't unlocked and thus (maybe) didn't change fastboot.
verbatim7 said:
Hi everyone!
Issue is pretty simple to explain - after upgrading via OTA from the latest open beta Pie (29) to open beta Android 10 (30), I can't boot into recovery.
System works normally, the only thing I'm having trouble with are the generic issues discussed on the OP community forum (autorotate and other sensors, Gboard gap...). It is recommended repeatedly that one should reboot to recovery and wipe the cache partition.
The problem is that I can only get into fastboot mode - tried the advanced boot menu, adb/fastboot and selecting recovery mode while in the fastboot mode but it always goes into fastboot.
TWRP doesn't support android 10 yet as far as I know and I've found no other reference of this issue anywhere else. Only thing that comes to mind is to wait for the next open beta and hope it will be resolved after another OTA.
Thanks for your help!
Click to expand...
Click to collapse
Had read somewhere that flashing stock boot.img will help restore stock recovery.. Have you tried doing that
brashmadcap said:
I think you stumbled across the answer everyone has been searching for. How did you upgrade? Did you download the whole zip and flash through updated?
This kinda makes sense. Do you remember how big the update file was? It could have been an incremental rather than a full if you weren't unlocked and thus (maybe) didn't change fastboot.
Click to expand...
Click to collapse
i grabbed the update file from this news article from xda itself: https://www.xda-developers.com/oneplus-android-10-oxygenos-beta-oneplus-6-6t/
the update zip was the full update and not incremental. i updated my device using the local device upgrader found under the system update settings to do the job for me.
Edit: this part down was meant for OP, sorry for confusion
so far when i updated last night, the auto rotate was tripping, until you mentioned that wiping the cache should do the trick (and it did do the trick thanks for that).
But back to your problem, you should try flashing the file under the link i put into this reply and if it doesn't work, just back up your data, downgrade back to pie, and flash the full update file that is present within that article and you should be back to normal
HighOnLinux said:
i grabbed the update file from this news article from xda itself: https://www.xda-developers.com/oneplus-android-10-oxygenos-beta-oneplus-6-6t/
the update zip was the full update and not incremental. i updated my device using the local device upgrader found under the system update settings to do the job for me. so far when i updated last night, the auto rotate was tripping, until you mentioned that wiping the cache should do the trick (and it did do the trick thanks for that).
But back to your problem, you should try flashing the file under the link i put into this reply and if it doesn't work, just back up your data, downgrade back to pie, and flash the full update file that is present within that article and you should be back to normal
Click to expand...
Click to collapse
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:
Use an older version of magisk and you won't lose twrp
verbatim7 said:
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:
Click to expand...
Click to collapse
how did u get back the recovery?
LazerH said:
how did u get back the recovery?
Click to expand...
Click to collapse
As stated above - just downloaded the OTA Android 10 update file for the right device, installed it and didn't install magisk to inactive slot and I had it back. If I tried to install magisk to keep root I didn't have the recovery mode. My guest guess is that magisk still isn't fully compatible with the new Android 10 boot changes.
verbatim7 said:
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:
Click to expand...
Click to collapse
To me having a stable phone is much more important than a heavily modified device that's unstable at any given time. I'd say use the msm tool, flash back to a fresh build of pie, download the full open beta 30 zip, after its done flashing, reboot twice to iron out any present issues, then unlock the bootloader, and then you should be good to go. If you want root, just fastboot boot into twrp and flash the latest magisk zip and you're good to go. At the end you should have root, an unlocked bootloader, all while on the open beta android 10 build, with access to the stock recovery
Can u guys help me please, i just flashed by mistake with " fastboot flash boot" a TWRP enchilada file and now i'm stuck in fastboot and i cant boot ...i dont know how to factory reset or flash firmware from fastboot (
terrorblade23 said:
Can u guys help me please, i just flashed by mistake with " fastboot flash boot" a TWRP enchilada file and now i'm stuck in fastboot and i cant boot ...i dont know how to factory reset or flash firmware from fastboot (
Click to expand...
Click to collapse
Had the same problem. Flash this one: https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
OOS 10 Open Beta 1 Stock Boot
Schnullifax said:
Had the same problem. Flash this one: https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
OOS 10 Open Beta 1 Stock Boot
Click to expand...
Click to collapse
thanks..this is what i was looking for ...the problem is that now i'm in a boot loop , the dots keep spinning 4ever...and i did factory reset it from recovery
up1: i managed to install on slot a (i guess) Twrp.. but the whole memory is empty and i cant place anything (firmware) with pc on phone
formated data from twrp (to some format ntfc4 or smth like that ) and installed back android q and is working .