everything was working fine for almost a year. twrp, magisk, everything was working as intended. decided to update to the july stable build (walleye-pq3a.190705.001) and decided id like a fresh start. ok cool, easy enough, just boot into the bootloader/fastboot mode and use the flash-all script, done. flash TWRP 3.3.0 using "TOOL ALL IN ONE". installs fine, reboots fine, cool. reboot to recovery to install the magisk 19.3 zip. wait what? password not accepted? it works in system, and is the same password i always use for the phone (i just use one to prevent butt dialing). ok fine whatever lets just reboot and completely remove all security for now, and figure that one out later. reboot into twrp, no password this time. excellent. lets flash this zip (same zip that i downloaded directly from magisk manager before starting any of this, also tried an old copy that i used to root the first time). everything looked like it was fine, so i rebooted to system. waited about 3 - 5 minutes, and it rebooted to recovery. hmm, odd, maybe just a bad cache or something. rebooted again. same thing, kicked back to recovery. ok, lets do dalvik/cache. nope, same problem. redid flash-all, and manually installed TWRP using fastboot to boot an img, push the twrp installer zip, flash that. same problems. changed slots, flash-, manual twrp flash, same problem. factory reset, repeat flashing, same problem. format system and data partition to get rid of everything, reflash, same problem. theres other stuff that ive tried that i dont remember too.
EDIT: also tried restoring an old TWRP backup from feb. and got the yellow auth error on the bootloader
where i currently sit is i can get a factory image on there and can get twrp on there, and even flashed lineage just for ****s and giggles, and that even worked (esim manager kept crashing, didnt test much else, but it booted and was functional for what little i tested).
TLDR: twrp wont accept pin, and when i disable the pin and flash magisk i can no longer boot even though these are the same files that have been on my E drive since the day i got it, which worked fine back then. it almost feels like theres some kind of corruption somewhere.
Related
Ok, so I'm coming from the Nexus 6P which has a different file system, I get that. But, this is so confusing to me.
I have gotten TWRP to work and SuperSU, however, they both do not work at the same time.
If SuperSU is working correctly and I want to go to TWRP, TWRP is all encrypted it looks like. It is not until I boot to bootloader and manually use fastboot boot that I can get TWRP to work right. Doing this causes me to lose root and vice versa...
I guess I am wondering what steps people usually take to install a rom and kernel correctly while keeping twrp and root at the same time.
I realize this probably makes no sense, but it doesn't to me either and I'm trying to explain it as best I can.
GohanBurner said:
Ok, so I'm coming from the Nexus 6P which has a different file system, I get that. But, this is so confusing to me.
I have gotten TWRP to work and SuperSU, however, they both do not work at the same time.
If SuperSU is working correctly and I want to go to TWRP, TWRP is all encrypted it looks like. It is not until I boot to bootloader and manually use fastboot boot that I can get TWRP to work right. Doing this causes me to lose root and vice versa...
I guess I am wondering what steps people usually take to install a rom and kernel correctly while keeping twrp and root at the same time.
I realize this probably makes no sense, but it doesn't to me either and I'm trying to explain it as best I can.
Click to expand...
Click to collapse
Your problem with TWRP isn't related to root. When you boot TWRP you have to enter your pin or pattern lock (whatever you use to unlock the phone when it's booted up) before it can decrypt the data. If you don't get offered the chance to unlock, reboot recovery until the lockscreen appears. It's a bug in TWRP. I don't have much trouble with it myself but once in a while I have the same thing happen. It might take one reboot, it might take several. Eventually it'll work for you though.
robocuff said:
Your problem with TWRP isn't related to root. When you boot TWRP you have to enter your pin or pattern lock (whatever you use to unlock the phone when it's booted up) before it can decrypt the data. If you don't get offered the chance to unlock, reboot recovery until the lockscreen appears. It's a bug in TWRP. I don't have much trouble with it myself but once in a while I have the same thing happen. It might take one reboot, it might take several. Eventually it'll work for you though.
Click to expand...
Click to collapse
I fastboot booted TWRP and installed the zip so I would keep TWRP, then I flashed the SR4 SuperSU zip. I rebooted and tried going back into TWRP though my ROM and all my folders looked like this:
a9239xwhg802348
8208dncbjs8d0s99
3n9c8bnd8s0s93n3
8db0xndne8s8n3n
nz0sd8fn2308df0n
etc...
I used fastboot boot twrp again and everything went back to normal, but then I lost root. I did the exact same thing again and now it seems I have both working at the same time. You can see how this is so confusing lol. I have no idea why it didn't work the first time when I did the exact same thing.
GohanBurner said:
I fastboot booted TWRP and installed the zip so I would keep TWRP, then I flashed the SR4 SuperSU zip...
Click to expand...
Click to collapse
It could be that you didn't use the latest SuperSU. 2.78SR4 is not the newest. Flash 2.79SR3 and see is that works.
I installed the latest SuperSU and all is working correctly, yet there are still some issues I am having...
-Randomly, TWRP will reboot into some kind of encrypted state. Where all the folders listed are like "asd8a0b93eea9dnb9" instead of what's actually in there like the Download folder. Rebooting a few times sometimes fixes it.
-Sometimes phone will just boot into stock recovery even though I have flashed the TWRP installer.
-Need confirmation on what exactly Slot A and Slot B are. Are those just states? Like installing one rom on Slot A and installing one rom on Slot B allows the ability to switch between the two?
-Do I basically need to have a computer handy any time I want to install a ROM because of the fact TWRP sometimes doesn't stick? Or can I run fastboot boot (terminal) commands from inside the system?
-Is there any specific order I need to flash things? Vendor, SuperSU, TWRP, etc?
Stuck on the 4 colored dots that animate before it' supposed to be displaying the text "android".
Flashed TWRP and everything seemed to be going well. Pushed SuperSU to /sdcard/ and flashed it. Pressed to reboot after flashing and it asked me again to flash SuperSU. I pressed yes and now my phone won't boot.
Did I install SuperSU twice or something? Not entirely sure what that hiccup was.
Edit: Followed this guide (method 2) to try and flash all the stock stuff for my phone, but the cache was a corrupted image file and the recovery doesn't have any menu options so I can't wipe my phone anymore and I still have the bootloop issue. Is my phone done for?
Edit 2: I got a little over dramatic there. Upon trying method 1 in the same guide, it worked flawlessly. I'll be sure to flash TWRP and see if it bootloops again, though.
Going to try to give as much information as possible so it will help me figure this out.
I have been working with Renovate module and rom/ Different magisk etc.
The display within the settings has been always messed up and crashes upon using.
So someone suggested a factory reset.
Pre-reset. I did a nandroid backup as well as Titanium backup , and google sync just in case.
Then everything was fine. But had some issues with Magisk installer. Basicly it was not correct and root didn't work correctly.
Flashing some module updates and newest Renovate update.
Then going back to reboot, all of a sudden it goes into fastboot mode.
Tried restarting in recovery , and it would not. It always wants to go to fastboot mode.
Posting and getting some advice (Thanks) they said I bricked my phone.
I tried everything I could to get data that I did a backup of off my phone (This is where I with it was micro SD)
Finally got into TWRP VIA fastboot boot ( had to change active slot) and it was encrypted.....
Booted again using Bluespark via fastboot (Think it was slot b this time) and was able to get a full SD backup onto PC.
Thinking this is going good, I flashed bluespark into slot b?.
Well it never took, and just showed a white light on top , the notification light.
Tried a few flashing VIA fastboot, and last thing I did was fastboot boot an official TWRP, to a slot that worked.
Tried Msmdownloadtool, and various other ways to get stuff going.
Tried Fastboot flashall and fails as well
Can anyone help me get the phone back so recovery works or help in any way?
eracet said:
Going to try to give as much information as possible so it will help me figure this out.
I have been working with Renovate module and rom/ Different magisk etc.
The display within the settings has been always messed up and crashes upon using.
So someone suggested a factory reset.
Pre-reset. I did a nandroid backup as well as Titanium backup , and google sync just in case.
Then everything was fine. But had some issues with Magisk installer. Basicly it was not correct and root didn't work correctly.
Flashing some module updates and newest Renovate update.
Then going back to reboot, all of a sudden it goes into fastboot mode.
Tried restarting in recovery , and it would not. It always wants to go to fastboot mode.
Posting and getting some advice (Thanks) they said I bricked my phone.
I tried everything I could to get data that I did a backup of off my phone (This is where I with it was micro SD)
Finally got into TWRP VIA fastboot boot ( had to change active slot) and it was encrypted.....
Booted again using Bluespark via fastboot (Think it was slot b this time) and was able to get a full SD backup onto PC.
Thinking this is going good, I flashed bluespark into slot b?.
Well it never took, and just showed a white light on top , the notification light.
Tried a few flashing VIA fastboot, and last thing I did was fastboot boot an official TWRP, to a slot that worked.
Tried Msmdownloadtool, and various other ways to get stuff going.
Tried Fastboot flashall and fails as well
Can anyone help me get the phone back so recovery works or help in any way?
Click to expand...
Click to collapse
UPDATE: When booting into TWRP 3.2.2.0 it gives me encrypted files. When booting into TWRP 3.2.3.0 it gives me non-encyrpted files and asks for password.
Booting anything to slot A gives me a load error. failed to authenticate.
Update2: Now I cannot get Bluspark TWRP or stock recovery to load VIA Fastboot. Only TWRP 3.2.3.0 works and loads correctly
Update 3: Keep having to do different versions of TWRP to get anything going, even tried OTA and did not work.
Update 4: Phone wants to boot into Qualcomm HS-USB Diagnostics mode when light is on.
Found you
Next time tag me
I'm the same guy on the oneplus forums
Send me a private message here or on the oneplus forums and I'll take it from there
Update: I have resolved the issue. Please do not post any further comments on this because
The issue is already resolved, duh
Hi, as the title explains I can flash and boot into lineage os but when I try to flash a stock OxygenOS signed flashable zip from this thread (https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244)
and when I boot to system, the screen doesn't show a boot logo, it just goes black for a few seconds before rebooting back to twrp (also if it helps, when it goes to twrp all the files are gibberish, I have to shut off the phone and boot into it from fastboot or I can't see any files).
This all started because I misunderstood the instructions and tried to flash an ota package which then broke the system, it's working now but I'd much rather use OOS as Lineage is missing a lot of the features I'm used to on Oxygen.
I've also tried the "flash-all-partitins-fastboot" from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 but unfortunately that gave the same issue, it just went back to recovery and wouldn't load OOS.
If anyone has any ideas on how to get back to oxygen that'd be super helpful! I'm considering using the MSM tool but I'd rather not have to start from scratch and lose all my files.
I'm just guessing, but there might be something wrong with your TWRP, did you try re-flashing it?
mati11233 said:
I'm just guessing, but there might be something wrong with your TWRP, did you try re-flashing it?
Click to expand...
Click to collapse
I should've clarified in the post, I mean all the files are gibberish (as in not decrypted I think?) but when I
Code:
fastboot boot twrp.img
it works fine and I can see all the files.
I've probably tried flashing it 4 times through twrp but every time it just does the same thing, boot to system just shows a black screen for a few seconds then reboots to twrp.
I'd love to use blu_spark like everyone recommends but I can't find the blu_spark recovery for the op6, only their kernel.
The reason why it's gibberish is because your device is encrypted and you need to input the password in the twrp to be able to access it. Seems the twrp doesn't detect the encryption correctly so there might be something wrong with it.
Here is the bluespark twrp https://github.com/engstk/android_device_oneplus_enchilada/releases
mati11233 said:
The reason why it's gibberish is because your device is encrypted and you need to input the password in the twrp to be able to access it. Seems the twrp doesn't detect the encryption correctly so there might be something wrong with it.
Here is the bluespark twrp https://github.com/engstk/android_device_oneplus_enchilada/releases
Click to expand...
Click to collapse
I just tried with blu_spark and the same thing happens but I realised something else, twrp only doesn't work on slot A.
If I see that it didn't decrypt the files, I can set B to active, reboot to recovery, and it works perfectly.
I noticed after one of the failed boots it switched the active slot to B even though I had set it to A before flashing. So every time it doesn't show the logo or anything, it sets the active slot from A to B and reboots to recovery.
Also I just looked and from the Backup page, it shows 2.7 GB for system on slot A and 1.7GB on slot B so I'm going to try wiping both and reflashing the flashable signed zip on each then twrp.
UPDATE: Just did that and the twrp installer was giving an error saying unsupported android version so I looked and system is only 4MB after flashing that package (OnePlus6Oxgygen_22_OTA_034_all_...zip), I'm trying an older one (...OTA_026...zip) to see if that actually works.
So I tried with the older one and lineage and they both still left the system partition at 4MB and the blu_spark twrp installer isn't detecting an android version. The system image partition is at 2.6GB if that means anything.
Oh wait more update, I'm dumb and shut off the phone while taking the case off (got stuck and it was pushing the power button) and even though the twrp installer couldn't detect anything and twrp said No OS installed when trying to boot to system, lineage just started up, no problem. I am very confused I miss when there was one system partition.
How are you flashing the OS?
mati11233 said:
How are you flashing the OS?
Click to expand...
Click to collapse
I'm using twrp, blu_spark and normal, and both have the same result. They can flash lineage and it runs fine, but oxygen refuses to boot and just switches the active slot and goes to recovery instead.
I also tried the fastboot rom flashing thing from the thread I linked to in the OP and it's the same thing, just goes back to recovery and wont boot.
P.S. I'm currently copying over /sdcard to an external drive and if I can't figure out how to fix this by the time that's done, I'll just use MsmDownloadTool and start over.
And you are wiping each time before flashing it, right? If it is the case then the download tool is probably the easiest way to go about it, rather than spending days troubleshooting it.
mati11233 said:
And you are wiping each time before flashing it, right? If it is the case then the download tool is probably the easiest way to go about it, rather than spending days troubleshooting it.
Click to expand...
Click to collapse
I've tried it with and without wiping and it always seems to do the same thing either way, works with LOS not with OOS. Thanks for the help! but yeah I think I'm just going to end up using the download tool once everything's over.
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
kozaqu said:
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
Click to expand...
Click to collapse
That got me in the right direction and I can at least get back into recovery now. Thanks! :good:
Also in the same boat
mkhopper said:
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Click to expand...
Click to collapse
I'm also sort of in the same boat i had a custom rom installed and decided to go back to stock os and now i'm stuck at either the Nvidia Logo or the Fastboot menu there's nothing else it let's me do i'd take any advice at this point. I can use Fastboot commands and I've tried Flashing Twrp.img and also flashing all the stock os which goes through with no problems i reboot the device and it's just stuck at the Nvidia logo
Ps: how did you manage to get back into recovery
Hello.
I think i had the same Problem.
I Flashed a Custom Rom, MiniGapps and the tegra...Battery file and since then i had boot loop an the NVidia Logo.
The Problem was: i flashed the tegra-Battery.ZIP file!!!
I noticed that i have to unzip it and flash teh tegra-..battery.DTP file.
since then it booted up again.
the OpenGappMini was buggy. it worked with the Nano!
Hope this helps for you as well!
OMG you guys. I did the exact same damn thing. Flashed the ZIP instead of the DTP file. 100 million thanks to you. I'm going to give it a shot now.
It worked! I wonder how many other folks didn't realize it wasn't a zip to flash to dtb and bricked their devices.