Oneplus 7T - TWRP no OS installed and unable to install OS - OnePlus 7T Questions & Answers

Hi all,
I tried rooting my Oneplus 7T (Android 11) but it failed horribly. I started by unlocking my bootloader, then "fastboot boot twrp.img" and it worked. I was in TWRP when I tried flashing Magisk and TWRP, and somehow my OS is gone.
Now, whenever I reboot, it says "No OS installed" and boots back to TWRP. I tried to sideload a stock ROM but failed as well. I did adb push stock rom and tried to install it but it gave the same error. As of now I am clueless on what to do. I already wiped my system and formatted my phone (I already backup everything).
Error code when trying to sideload ROM (both stock and custom):
Failed to mount '/system_root' (permission denied)
Failed to mount '/vendor' (permission denied)
Devices on super may not mount until rebooting recovery.
To flash additional zips, please reboot recovery to switch to the updated slot.
As you can see, I am an idiot.
Please help.

Msmtool to unbrick

[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com

U must flash twrp and not boot twrp:
fastboot flash recovery twrp.img (rename img file to twrp.img and put in same adb folder)

HOLY COW IT WORKED, I managed to reinstall the OS.
Thank you very much HueyT, you certainly saved my day.
So...if I want to root my Oneplus 7T, I need to flash instead of boot TWRP?

Yes, op7t won't like boot TWRP as it has a dedicated recovery partition (both a and b slots-but when u don't specify TWRP goes into both slots)

twrp-3-5-1_11-hotdog-20210821-oos11-test.img | by lossyx for OnePlus 7T Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Is best TWRP for oos11 as allow data backup in twrp

im having a similar issue as OP... with device super message. I flashed the OOS firmware, then TWRP and then the custom rom whichever that may be.
However i have a feeling i am doing something wrong here. The only rom i can boot into is Syberia Android 12. However, after that i cant enter recovery again, and get stuck on the TWRP splash screen.
is there any reason why i cant boot into any custom android 11 roms?

Related

root problem after update to beta 19

hi,
my oneplus 3 has been rote since i got it (i bought it on launch day) but since i updated it to the beta 19, my phone is no longer rooted : when i put the phone in fastboot it says that my bootloader it unlocked but all the apps who requier root are saying that the phne is not rooted and i cant get twrp to work. i tryied with the official app on my phone and with a program called "tool all in one" (https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993) and when i flash twrp from the program, i can boot into twrp but then i can't access my files and after i boot the phone, i can no longer boot to twrp
does anyone have a solution that doesn't involve me wiping the phone?
You loose root after updating. Try installing twrp again and then rooting it. Use the toolkit for oneplus 3. Simplifies the process
what do you mean by "then rooting it" ?
the program i use does the same thing as the toolkit and when i install twrp, as i said, it can boot on twrp one time and in twrp i can't access my files and after i boot the phone i can't get back to twrp ,i get the stock recovery
Unless your ROM has built-in root, after flashing TWRP, you have to flash SuperSU or Magisk to obtain root. Mere flashing of TWRP will not give you root.
I know but i can't get to the folder when the magisk file is : when in boot into twrp i cant see my files
Few details... it's quite difficult to help you.
What's the root method? Magisk, SuperSU or Kingroot? Which version?
Ps TWRP recovery is not depending by root, you just need to unlock bootloader (surely it's already unlocked) and flash the same recovery, from PC, via the command "fastboot flash recovery filename.img".
Now enter in TWRP:
1) Wipe /system and /cache;
2) Flash another time Open Beta 19;
3) Flash Magisk or SuperSU (be sure to have latest release);
4) Move TWRP img file from computer to device, then flash it another time (because firmware provides the OOS stock recovery);
5) Reboot and wait 5-10 minutes, because of cache rebuilding.
Tell me if you solve
I am using magisk
Yes my bootloader is unlocked
My problem is that when i flash twrp i cant access my files so i don't want to wipe system if i cant reflash something after
I think that I'll wait for the next update, maybe then it will work
But thank you for your help
Which version of TWRP do you have? Try eng.stk's latest version.
I tryied 3.1.1-2
The eng.stk is not available anymore
Your phone is encrypted, so you have to format data ( but your internal storage wiped by formating data, so back it up ,then only twrp read files in your storage)and flash custom kernel then boot restore backup .
how do you know that my phone is encrypted? i never encrypted it
i use titanium backup so i can't back my phone up until i get rot back
Whenever you flash stock ROM it encrypt if you boot into system directly . So twrp could not read internal storage. Whenever you flash stock ROM you must flash custom kernel or any other method to avoid encryption. This is happened to me and what I'd done is flash custom kernel before boot into rom
To save your data try this
https://forum.xda-developers.com/oneplus-3/how-to/unencrypt-oxygenos-loosing-data-t3412228
Who said that? Check this: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Edit: If you want to save items in internal storage, you can use ADB commands instead of TWRP. You can also simply copy and paste if your PC recognises the internal storage of your phone.
I succeeded but i had to clean everything and use the last backup i made a week ago
Thank you all for your help

Android 8 update with FlashFire breaks TWRP or TWRP boot-loop

Hi everyone,
I tried to update my rooted Pixel C with Android 8 and TWRP 3.1.0.0 from August build to September build with FlashFire.
All of the following have I done on my Nexus 5x as well and it worked as a charm there.
Therefore i dl'd the corresponding zip-file from google dev page and started the update with FF. It said to me it can update the boot, system, recovery and vendor partition so I unchecked the recovery partition only to keep TWRP. I also told FF it should include SuperSU again to root the new Android.
After the update the device was unrooted, so i tried to start into recovery to install superSU manually. But TWRP was gone and i get everytime the android on the back with the text "no command".
Therefore I tried to flash TWRP with NRT again. But after the flash the device always starts into TWRP and Android isn't starting anymore.
I can use NRT again to flash Android without loosing my data but than TWRP is gone again.
So either the device always starts into TWRP or I have no recovery installed.
Anyone an idea what i can do to flash TWRP again and to fix the boot order or whats broken than?
Regards,
flattervieh
I don't have the C but here's what I would try. First, have your device booting normally with the stock recovery. Then use fastboot to boot into TWRP, not flash it. When it boots into TWRP then flash supersu. From TWRP then boot back into the bootloader and then flash TWRP with fastboot.
Flash the latest (beta?) TWRP. It allows reading the encrypted data folder.
Short notice, i'm still struggling with the problem.
In the meantime I tried the following:
1. I temporarely booted TWRP 3.1.0.0, with this version I was not able to encrypt the data partion (always invalid key) but I was able to see the system partition and I installed SuperSU. After that i restarted into the bootloader and flashed TWRP 3.1.0.0.
This led to the same phenomenon, that my pixel always boots into TWRP and not into Android itself.
2. Same thing as before but with TWRP 3.1.1.1.
With this version I was able to see the size of the data partition, but I was also not able to read or write onto it. (Again invalid code) I installed SuperSU and made a device restart without flashing TWRP 3.1.1.1.
This led to a totally softbricked device with a boot into "no command" screen.
After flashing Android again via fastboot Android starts correctly and I can use the device but root is still not working.
Regards
I'm not sure why twrp isn't sticking. But the android on its back with "no command"is the stock recovery. To get into it simultaneously press and release the power and vol up keys. You might have to try it a few times as the timing can be very finicky. From there you can boot into the system, you don't need to flash the factory image and start all over.

Honor 7x bricked

model: BND-L21(c432)
bootloader unlocked
FRP unlocked
My phone was running omnirom beta 5 for 2 months, was rooted with magisk (patched_boot flashed in ramdisk_recovery partition)
The bluetooth wasn't working so I wanted to install phhusson aosp 9
So I flashed emui 8 stock recovery then tried to flash phhusson aosp 9 as a system image in fastboot
Now, when the phone boot, it shut down instantly then boot into erecovery without the ability to factory reset or wipe cache (the only thing I can do is "reboot", "shutdown" and "download latest version and erecovery")
What's working and what's not:
access to erecovery (with ability to wipe cache and factory reset) when the phone is powered off then I press power & vol +
can't access twrp (even if the flash on recovery_ramdisk succeed with fastboot )
access to fastboot mode
access to erecovery (without the ability to wipe, only "download latest and erecovery) when the phone try to boot
access to dload installation
Here's my tries to fix the issue:
after installing emui 9 through fastboot: honor boot animation for 30-40s then bootloop
after installing emui 5 or 8 through fastboot: boot into error mode which displays this: (I can't flash ramdisk or boot (error: partition length get error))
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 10 (boot image)
Error NO : 2 (load failed)
Click to expand...
Click to collapse
dload installation don't work, even with service rom
tried installing phhusson aosp 9 and omnirom beta 5: boot into rescue mode error
huawei multi tool failed
hwoat failed (I can't reboot into twrp)
erecovery "download latest version and erecovery" failed
My thoughts are that my BOOT is broken, but since I can't flash a new one, I don't know what to do.
AlexLebul said:
model: BND-L21(c432)
bootloader unlocked
FRP unlocked
My phone was running omnirom beta 5 for 2 months, was rooted with magisk (patched_boot flashed in ramdisk_recovery partition)
The bluetooth wasn't working so I wanted to install phhusson aosp 9
So I flashed emui 8 stock recovery then tried to flash phhusson aosp 9 as a system image in fastboot
Now, when the phone boot, it shut down instantly then boot into erecovery without the ability to factory reset or wipe cache (the only thing I can do is "reboot", "shutdown" and "download latest version and erecovery")
What's working and what's not:
access to erecovery (with ability to wipe cache and factory reset) when the phone is powered off then I press power & vol +
can't access twrp (even if the flash on recovery_ramdisk succeed with fastboot )
access to fastboot mode
access to erecovery (without the ability to wipe, only "download latest and erecovery) when the phone try to boot
access to dload installation
Here's my tries to fix the issue:
after installing emui 9 through fastboot: honor boot animation for 30-40s then bootloop
after installing emui 5 or 8 through fastboot: boot into error mode which displays this: (I can't flash ramdisk or boot (error: partition length get error))
dload installation don't work, even with service rom
tried installing phhusson aosp 9 and omnirom beta 5: boot into rescue mode error
huawei multi tool failed
hwoat failed (I can't reboot into twrp)
erecovery "download latest version and erecovery" failed
My thoughts are that my BOOT is broken, but since I can't flash a new one, I don't know what to do.
Click to expand...
Click to collapse
I had the same error "error: partition length get error" with my BND-L24. What I did, I found the stock rom from the firmware finder application. Unloaded the boot.img and flashed it without any issues.
I used the guide in the OpenKirin webpage to find the correct rom (you can check the info of your phone using fastboot commands or download multitool and read the phone info there) and to extract the .img files (go to Openkirin webpage and press support for the guides).
Good luck!
i, I have an issue with my phone and would need your help in recovering it back to life.
I have rebranded mate SE to Indian version few months back. so far so good. I have unlocked bootloader and started playing with it by downgrading etc.
the current situation is the phone is bricked with a android pie erecovery and no boot. tried using all the roms visiting various threads here with no luck (including service rom, multi-tool flashing etc)
multi-tool says Orio version 8.0.0.375. I am not able to flash any Oreo images since multitool says partition mismatch (boot, recovery etc) but when I flash 9.0.XX versions or Nougat versions, system is flashed successfully, yet, boot loops and back to latest erecovery.
don't have twrp (despite multitool flashing is successful) all I get is phone boots only to erecovery (latest)
unable to flash any stock recovery or kernels - as multitools says, partition mismatch.
I tried above method of boot.img flashing but multitool says partition error. tried various boot.img (EMUI 5 / 8 / 9) with no luck.
any help? suggestions?
I had a similar issue the last two days. The only thing that worked was rebooting to fastboot. I tried to get back to Oreo but used a method, that bricked my phone since it flashed an older kernel.img. I got it back running by detecting the version of the bootloader with Multitool and fastboot-flashing recovery, kernel and system that have been aligned with that version.
Be aware: You will have two recovery partitions:
- Huawei has renamed the partitions from "recovery"/"recovery2" to "recovery_ramdisk"/""erecovery_ramdisk"
- unlocking the bootloader does only let you flash recovery_ramdisk
- if you boot into recovery (Pwr & Vol+), the image from erecovery_ramdisk gets loaded
- To boot into recovery you are able to flash, it requires three buttons to be pressed (Pwr & Vol+ & Vol-)
- To flash erecovery_ramdisk, you have to flash TWRP into recovery_ramdisk and from there you can install an image into erecovery_ramdisk.
After having flashed back everything to 9.1.0.162, it was possible to format damaged /data and to setup the device via erecovery and WIFI.

[SOLVED] TWRP does not decrypt /sdcard; 'fastboot boot recovery' doesn't work

Hi everyone. I hope this is the right forum for this question.
Edit: I found the thread for TWRP and it says there is a known issue with decryption for Android 10. I think that is the root of my problems. I'm going to try to downgrade to Android 9 since I hate Android 10 anyway. It was causing all sorts of problems with my phone...random reboots, etc.
I have a Pixel 3 XL running the latest version of Android (image-crosshatch-qp1a.191005.007). I want to root it, but am having problems with TWRP.
I have the google usb drivers and adb and fastboot. I downloaded them all through the latest version of Android Studio.
I then used the official guide from twrprecovery.me (slash) google-pixel-3-xl/ to try to install TWRP. When I follow that guide I have 2 issues.
First, the '.\fastboot boot recovery recovery.img' command does not work. I get this error:
Code:
fastboot: error: cannot load 'recovery': No such file or directory
I am able to use .\fastboot boot recovery.img. When I do that I encounter the second problem.
Second, if I boot into TWRP using the command .\fastboot boot recovery.img, the file system is encrypted. It shows no data in the /sdcard folder and it shows the available storage space in Internal Storage as 0MB.
I've seen a lot of threads about that, but none of the suggestions work (I.e., setting a pin, setting a password, disabling home screen security all together, setting the phone to require a password or pin on boot (that option isn't available on the Pixel 3 XL), etc).
What I have been able to do is use TWRP to chmod 755 the /sdcard folder and then use adb push to transfer the recovery.img file. This was more of a test since I didn't expect it to actually be able to flash it. To my surprise, that worked, even though it couldn't mount any of the partitions. Of course, doing it that way removed the OS because it was flashing it to System not Recovery (I think...this is the first Pixel I've installed TWRP on).
That wasn't an issue since unlocking the bootloader had already wiped all my data. I just reinstalled the stock OS. After reinstalling the stock OS I just see a dead Android when I boot to recovery. I think that's either because A) TWRP was never installed to the recovery partition, or B) the stock OS overwrote it.
To summarize, I need to 1) boot into recovery so I can install recovery.img without wiping the OS, and 2) decrypt the file system.
Can anyone help me out?
Thanks

Redmi Note 5 Pro Not Rooting

Hello There,
I have Redmi Note 5 Pro with unlocked bootloader. But unable to root it no matter what.
Let Me Explain The Situation.
1. After flashing TWRP, it asks for "decryption password" which is nowhere to be found on internet. But in order to decrypt it i had to format the phone. GOOD Now Storage is Detected in TWRP.
2. But if i boot phone in System and again boot it in Recovery then TWRP is replaced with Stock Recovery.
1 & 2 are in INFINITE LOOP now.
3. So OTG...... OTG is not even recognizing by TWRP, but OS is detecting it.
4. TWRP "Enable MTP" also not working.
So Let Me Know If I am Forgetting Something.
Please Help Me To Root IT.
PS : I have past experience of Rooting/ Flashing rom / Unlocking Bootloader etc.
I guess the main problem you're having is that your phone keeps replacing TWRP with the stock recovery once you boot into system. I've had same problem on different devices. To prevent this from happening you should not boot into system immediately after flashing twrp, rather you should boot directly into twrp recovery (try "fastboot boot recovery.img" command after flashing twrp - I'm assuming that your twrp img is saved as "recovery.img") and flash Magisk before booting into system. By flashing Magisk before booting into system your phone would no longer replace twrp, and then your phone would be rooted as well. At least that worked for me.
And also use orangefox rather than twrp on this phone

Categories

Resources