I tried flashing the official TWRP 3.2.1-0 which I downloaded from their website through shreps TWRP 3.1.1. After flashing, I got a recovery error. Even command from powershell can't flash it. Any fixes?
I'm running stock ROM Feb 2018 security patch version
CMKdaGreatest said:
I tried flashing the official TWRP 3.2.1-0 which I downloaded from their website through shreps TWRP 3.1.1. After flashing, I got a recovery error. Even command from powershell can't flash it. Any fixes?
I'm running stock ROM Feb 2018 security patch version
Click to expand...
Click to collapse
try this way of flashing
in command type without quote
"fastboot boot (twrpname).img"
u will get booted to twrp recovery their transfer the twrp img from pc to internal
and thn while still in twrp booted mode select install, select flash img, choose the the twrp img on the internal.
and select recovery partition. DONE :silly::good:
Tanha_Dil said:
try this way of flashing
in command type without quote
"fastboot boot (twrpname).img"
u will get booted to twrp recovery their transfer the twrp img from pc to internal
and thn while still in twrp booted mode select install, select flash img, choose the the twrp img on the internal.
and select recovery partition. DONE :silly::good:
Click to expand...
Click to collapse
I'll surely try. Thanks
Related
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
You need to run the phone in Qualcomm mode on a PC and run the recovery tool to fix you bootloader.
I did the same and it was a royal ball ache trying to find out how to fix it
Don't do what rosswaa said
Why not?
What you should do is boot your phone into fastboot mode, connect it to your pc. Flash this modified TWRP recovery img to your phone https://www.androidfilehost.com/?fid=24459283995297945. After that you have to flash this modified SuperSU (through the new recovery) https://www.androidfilehost.com/?fid=24459283995297946.
The normal recovery doesn't work in OOS 3.0 (just like in HOS) and it's the SuperSU that gives you the soft brick. A dirty flash of the modified SuperSU should fix it.
I also had your problem and I did what rosswaa said which shouldn't be necessary (I lost all my data and backups).
I didn't lose anything, but I tried doing what you said and my bootloader was screwed so wouldn't take a flashed recovery or anything (yes the modified one)
Wish I hadnt been so excited and just flashed but all sorted now
Hmm okay, if it doesn't work with flashing the new recovery img then do what rosswaa said and after that follow this post https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/
Obviously try what green says first, if it works then happy days
first i am really glad that someone give some advices on me. But since i am a noob, how can i flash twrp in fastboot mode? using command? "fastboot flash recovery xxx.img"? thx
SPiCa39's said:
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
Click to expand...
Click to collapse
1 Install official TWRP 3.x via fastboot twrp.me/devices/oneplustwo.html
Reboot to recovery
2 install this modified version of TWRP
forum.xda-developers.com/oneplus-2/development/recovery-teamwin-recovery-project-3-0-0-t3310713
Reboot to recovery
3 install oos3 (And supersu)
Sorry i can't post link
Hi guys. I have a problem with my ze500KL. I can install only the twrp 2.8.7.7 version. But when i try to install img or zip of roms /original firmware, the twrp fails the operation , saying " error data", "unable to mount"... i have problems with wipe too. any solution?
nik91thebest said:
Hi guys. I have a problem with my ze500KL. I can install only the twrp 2.8.7.7 version. But when i try to install img or zip of roms /original firmware, the twrp fails the operation , saying " error data", "unable to mount"... i have problems with wipe too. any solution?
Click to expand...
Click to collapse
I can't understand what you mean. If you want to install stock rom from TWRP recovery, you have to modify updater-skript.
Why do you can install only the twrp recovery 2.8.7.7, when we have the twrp recovery 3.0.0.2
File img you can flash from fastboot mode. Commands:
fastboot flash system file.img
fastboot flash recovery file.img
fastboot flash boot file.img
or
fastboot boot file.img for example twrp recovery img or stock recovery img. This is command for once booting.
I want to return to original firmware , i download it from the site of asus. So, i booted twrp in fastboot mode (i tried different version of twrp, but the only that starts is the 2.8.7.7 version) using adb.
Now i am in recovery with twrp 2.8.7.7. I can push using .zip files or img files on internal storage.
But i have different problems with this recovery:
IF i use wipe function: error opening sys, could not mount, enabe to mount, ... (failed)
If i install rom or firmware with zip files: error unable to mount, unable to find partition for path.... (failed)
Adb sideload goes failed too.
What should i do???
I think that the problem is in the internal partition... I have to install using a min usb ext storage? or what????? thanks :fingers-crossed:
nik91thebest said:
I want to return to original firmware , i download it from the site of asus. So, i booted twrp in fastboot mode (i tried different version of twrp, but the only that starts is the 2.8.7.7 version) using adb.
Now i am in recovery with twrp 2.8.7.7. I can push using .zip files or img files on internal storage.
But i have different problems with this recovery:
IF i use wipe function: error opening sys, could not mount, enabe to mount, ... (failed)
If i install rom or firmware with zip files: error unable to mount, unable to find partition for path.... (failed)
Adb sideload goes failed too.
What should i do???
I think that the problem is in the internal partition... I have to install using a min usb ext storage? or what????? thanks :fingers-crossed:
Click to expand...
Click to collapse
Easiest way to fix your phone is flash stock rom from stock recovery. Stock rom put to sd card. Reboot to stock recovery and choose flash rom from sd card. New version number system must be the same or higher than installed in the phone.
Do you want to return to the lower version of Android.
http://forum.xda-developers.com/zenfone-2-laser/general/guide-downgrade-zenfone-2-laser-to-t3382172
Do you want to flash stock rom from twrp recovery.
http://forum.xda-developers.com/zen...uide-how-to-flash-stock-rom-via-twrp-t3409768
Muminek111 said:
Easiest way to fix your phone is flash stock rom from stock recovery. Stock rom put to sd card. Reboot to stock recovery and choose flash rom from sd card. New version number system must be the same or higher than installed in the phone.
Do you want to return to the lower version of Android.
http://forum.xda-developers.com/zenfone-2-laser/general/guide-downgrade-zenfone-2-laser-to-t3382172
Do you want to flash stock rom from twrp recovery.
http://forum.xda-developers.com/zen...uide-how-to-flash-stock-rom-via-twrp-t3409768
Click to expand...
Click to collapse
Stock recovery doesn't work man. The only recovery that works is the twrp 2.8.7.7. But it has problems.
nik91thebest said:
Stock recovery doesn't work man. The only recovery that works is the twrp 2.8.7.7. But it has problems.
Click to expand...
Click to collapse
Do you have Lollipop or Marshmallow and what is your version number.
For Marshmallow you need to this working twrp recovery.
https://drive.google.com/file/d/0B7F3ZXr565GkY28yUjhfRkd5MUk/view?usp=drivesdk
For Lollipop you need to this working twrp recovery.
https://drive.google.com/file/d/0B7F3ZXr565GkY1NQbUtoVzdwWEU/view?usp=drivesdk
If you haven't installed stock recovery, it's not no problem. You can it flash from fastboot mode.
i had mawshmallow. i tried but failed...
nik91thebest said:
i had mawshmallow. i tried but failed...
Click to expand...
Click to collapse
How did you flash the file twrp.img.
OK guys I've solved the problem. I moved in this way:
1) Volume up + power to go in fastboot mode
2) after installing adb and the other drivers, i've insered these commands:
fastboot erase cache
fastboot erase userdata
fastboot erase system
3) after downloading twrp version 3.0.0 (for the zenfone 2 laser), I load it using the command "fastboot boot (name file twrp).zip"
4) the recovery starts automatically. Now i downloaded the file "back2stock.zip" and the original firmware (WW, worldwide) form the official site of the Asus
5) this passage is the most important:using 7zip I've extracted the file zip of the firmware and the backtostock, then i created a new file using 7zip : in this new zip i've loaded the files inside back2stock and the files file_contentexts, system.new.dat, system.patch.dat, boot.img e system.trasfer.list inside the zip of the official firmware
6) I've loaded this new file on the phone using the command "adb push (new file name).zip /"
7) at last i have installed this file on the phone ENJOY it
This works both ways on Sailfish & Marlin
TWRP 3.5.1_9-0 as Recovery Ramdisk can now co-exist with Magisk! Yey!
The twrp-installer-3.5.1_9-0-marlin.zip is still unable to boot back to recovery after flashing. But as long as you flash twrp-3.5.1_9-0-marlin.img as Recovery Ramdisk, then you're okay.
Note: Download first twrp-3.5.1_9-0-marlin.img from twrp.me and save it to your preferred download location.
You need to boot TWRP from bootloader by typing "fastboot boot twrp.img". After TWRP loads up, go to "Advanced>Install TWRP Image as Recovery Ramdisk>Find twrp-3.5.1_9-0-marlin.img location>Install Recovery Ramdisk".
After that reboot back to recovery then flash Magisk-v22.0.apk & viola!
edwaine said:
This works both ways on Sailfish & Marlin
TWRP 3.5.1_9-0 as Recovery Ramdisk can now co-exist with Magisk! Yey!
The twrp-installer-3.5.1_9-0-marlin.zip is still unable to boot back to recovery after flashing. But as long as you flash twrp-3.5.1_9-0-marlin.img as Recovery Ramdisk, then you're okay.
Note: Download first twrp-3.5.1_9-0-marlin.img from twrp.me and save it to your preferred download location.
You need to boot TWRP from bootloader by typing "fastboot boot twrp.img". After TWRP loads up, go to "Advanced>Install TWRP Image as Recovery Ramdisk>Find twrp-3.5.1_9-0-marlin.img location>Install Recovery Ramdisk".
After that reboot back to recovery then flash Magisk-v22.0.apk & viola!
Click to expand...
Click to collapse
The title says Android 11; will this work with Android 10? I tried on LineageOS 17.1 (Android 10) and TWRP said the image was too large but I already had Magisk 22 installed.
Perhaps: 1) Install LineageOS 17.1 weekly update with Options/Update/Updater
2) Boot into Lineage recovery to change slots
3) Reboot into bootloader
4) fastboot boot twrp-3.5.1_9-0-marlin.img
5) As OP said, "Advanced>Install TWRP Image as Recovery Ramdisk>Find twrp-3.5.1_9-0-marlin.img location>Install Recovery Ramdisk"
6) Reboot into recovery (may not be needed?)
7) Flash Magisk-v22.0.apk (renamed to Magisk-v22.0.zip)
8) Reboot system & violin!
I've been trying to get TWRP and Magisk installed without having to use another computer to go into fastboot and flash the image. There may be a way to use the Magisk TWRP A/B retention script. This at least tells me why using TWRP 3.5.2_9-0-marlin.img to install the TWRP zip file would never reboot into recovery. Thanks.
lichan said:
The title says Android 11; will this work with Android 10? I tried on LineageOS 17.1 (Android 10) and TWRP said the image was too large but I already had Magisk 22 installed.
Perhaps: 1) Install LineageOS 17.1 weekly update with Options/Update/Updater
2) Boot into Lineage recovery to change slots
3) Reboot into bootloader
4) fastboot boot twrp-3.5.1_9-0-marlin.img
5) As OP said, "Advanced>Install TWRP Image as Recovery Ramdisk>Find twrp-3.5.1_9-0-marlin.img location>Install Recovery Ramdisk"
6) Reboot into recovery (may not be needed?)
7) Flash Magisk-v22.0.apk (renamed to Magisk-v22.0.zip)
8) Reboot system & violin!
I've been trying to get TWRP and Magisk installed without having to use another computer to go into fastboot and flash the image. There may be a way to use the Magisk TWRP A/B retention script. This at least tells me why using TWRP 3.5.2_9-0-marlin.img to install the TWRP zip file would never reboot into recovery. Thanks.
Click to expand...
Click to collapse
Youre free to try the steps. I only confirmed it on Android 11 because I'm already using Pixel Experience 11 Plus. You really need to repartition before TWRP can fit to your Phone.
edwaine said:
Youre free to try the steps. I only confirmed it on Android 11 because I'm already using Pixel Experience 11 Plus. You really need to repartition before TWRP can fit to your Phone.
Click to expand...
Click to collapse
Thanks, I'll check into the repartitioning.
edwaine said:
Youre free to try the steps. I only confirmed it on Android 11 because I'm already using Pixel Experience 11 Plus. You really need to repartition before TWRP can fit to your Phone.
Click to expand...
Click to collapse
What's the difference between PE and stock pixel rom? aren't they the same?
X4c3 said:
What's the difference between PE and stock pixel rom? aren't they the same?
Click to expand...
Click to collapse
Same. But with added features on Pixel Experience 11 Plus
edwaine said:
Same. But with added features on Pixel Experience 11 Plus
Click to expand...
Click to collapse
You own Cherry Mobile G1(seed/crackling), are you from Philippines? where did you buy your Pixel XL with unlocked boot loader?
edwaine said:
This works both ways on Sailfish & Marlin
TWRP 3.5.1_9-0 as Recovery Ramdisk can now co-exist with Magisk! Yey!
The twrp-installer-3.5.1_9-0-marlin.zip is still unable to boot back to recovery after flashing. But as long as you flash twrp-3.5.1_9-0-marlin.img as Recovery Ramdisk, then you're okay.
Note: Download first twrp-3.5.1_9-0-marlin.img from twrp.me and save it to your preferred download location.
You need to boot TWRP from bootloader by typing "fastboot boot twrp.img". After TWRP loads up, go to "Advanced>Install TWRP Image as Recovery Ramdisk>Find twrp-3.5.1_9-0-marlin.img location>Install Recovery Ramdisk".
After that reboot back to recovery then flash Magisk-v22.0.apk & viola!
Click to expand...
Click to collapse
I can confirm that this works on the Pixel 2 XL (taimen). I just tested it with twrp-3.5.2_9-0-taimen.img and Magisk-v23.0 with Havoc-OS v4.6 (Android 11).
No go for me. Not sure why my pixel xl gen 1 refusing to boot to any twrp when flashed but 3.3.0.0. I can command line boot fastboot to the latest fine though.
Attempted to update from the latest stable 10.3.12 to 11 by flashing the full OTA zip in TWRP.
Install failed and phone locked up.
Attempting to boot to recovery or system results in Qualcomm Crashdump Mode.
I can get to Fastboot, but I'm not sure if I should try flashing twrp.img or pull boot.img from the OTA or what.
Anyone have any suggestions?
SMcC2 said:
Attempted to update from the latest stable 10.3.12 to 11 by flashing the full OTA zip in TWRP.
Install failed and phone locked up.
Attempting to boot to recovery or system results in Qualcomm Crashdump Mode.
I can get to Fastboot, but I'm not sure if I should try flashing twrp.img or pull boot.img from the OTA or what.
Anyone have any suggestions?
Click to expand...
Click to collapse
An attempt to flash TWRP and reflashing should go.
Hi,
I'm having kinda same issue.
I'm on stable A11 oneplus 6t,
i'm trying to boot into twrp in order to install new recovery and root with magisk.
when fasboot boot twrp.img i'm getting a qualcomm crashdump.
tried different twrp img's with no success..
maybe someone figure it out?
thanks
BenoMosko said:
Hi,
I'm having kinda same issue.
I'm on stable A11 oneplus 6t,
i'm trying to boot into twrp in order to install new recovery and root with magisk.
when fasboot boot twrp.img i'm getting a qualcomm crashdump.
tried different twrp img's with no success..
maybe someone figure it out?
thanks
Click to expand...
Click to collapse
I did not have time to wait so before bed I just reset everything.
I ended up using the MSM tool located here:
The Complete Guide to Unbrick OnePlus 6/6T from a Hard-Brick using MSMDownload Tool
Unlocked bootloader, installed TWRP & Magisk, installed A11 zip, everything is working again now.
Good luck!
BenoMosko said:
Hi,
I'm having kinda same issue.
I'm on stable A11 oneplus 6t,
i'm trying to boot into twrp in order to install new recovery and root with magisk.
when fasboot boot twrp.img i'm getting a qualcomm crashdump.
tried different twrp img's with no success..
maybe someone figure it out?
thanks
Click to expand...
Click to collapse
Hey, I'm having the same issue. Did you end up figuring out how to solve this?
Artificial_Intelligence said:
Hey, I'm having the same issue. Did you end up figuring out how to solve this?
Click to expand...
Click to collapse
Flash temporary recovery first ( lineage recovery ) then from fastboot.. boot into recovery.
You will see lineage recovery.
Select apply update - > update from adb ....
Then "adb sideload <twrp image>.img...
(probably it ask to verify choose yes)
Go back select advanced restart ( not sure the right word ) -> reboot to recovery.
Then you will have twrp installed.
If you only want to root why not flash magiskpatched image there no need TWRP just to root.
s.seila said:
Flash temporary recovery first ( lineage recovery ) then from fastboot.. boot into recovery.
You will see lineage recovery.
Select apply update - > update from adb ....
Then "adb sideload <twrp image>.img...
(probably it ask to verify choose yes)
Go back select advanced restart ( not sure the right word ) -> reboot to recovery.
Then you will have twrp installed.
If you only want to root why not flash magiskpatched image there no need TWRP just to root.
Click to expand...
Click to collapse
Hm but how would I install lineage recovery? Flashing recovery through fastboot doesn't work on the new devices anymore right?
I also tried booting lineage recovery without flashing but that also didn't work (although it didn't get stuck on crashdump but booted into the regular OS instead).
I did notice that it seems to be related to OOS 11 firmware. On 10 booting into TWRP works just fine and as soon as I upgrade to 11 it stops working (maybe this means it's fixable?). What I used as a workaround for now is to have 10 firmware in one slot, upgrade other slot to 11 and flash TWRP to both slots from the 10 slot. Seems to work so far but is not ideal IMO. I'm not a developer sadly but maybe someone smarter than me will come up with a solution.
What do you mean by "new device"?? New OOS version right??
I use this method all the time with oos 11.x.x.x.x to install TWRP so i can install Custom ROM later.
no need to go to oos 10 you can flash it from newest oos11.
---------------------------------------------------------------------------------------------------------------
First boot into fastboot mode.
to install lineage recovery
fastboot flash boot <lineage recovery image>.img
download from here https://download.lineageos.org/fajita
menualy select and boot to recovery. It will boot to lineage recovery.
lmao it appear in two posts. deleted 1.
I am trying to get a custon ROM to work on my Oneplus 8 Pro (instantnoodlep)
ROMs I tried installing:
Cherish OS 3.9.5
Nameless-AOSP_instantnoodlep-12.1-20220708-0935-Official
What I do:
1. Download recovery provided with the ROM
2. Reboot to bootloader and flash recovery
'fastboot flash recovery recovery.img'
'fastboot reboot recovery'
3. Select apply update/apply from ADB
4. Connect device to PC
5. Sideload rom.zip
'adb sideload rom.zip'
6 Do Factory reset/format data from recovery
7. Restart to system
What happens:
Phone goes to fastboot and stays there.
When I try
fastboot reboot system
or
fastboot reboot recovery
I also land in fastboot again.
The only way to get out of fastboot again is fastboot boot recovery.img, which boots into recovery. When I then reboot into system, my old OOS11 boots up.
Because this is independent of the Custon ROM, there might be another issue. But which one?
You made sure you have latest OOS11 on BOTH slots?
xtcislove said:
You made sure you have latest OOS11 on BOTH slots?
Click to expand...
Click to collapse
Thanks for the response! How do i check that? Both slots of what?
Infraviored said:
Thanks for the response! How do i check that? Both slots of what?
Click to expand...
Click to collapse
When you're booted in OOS 11 just do a local install of the same OOS version that you're on. That will install OOS to the other slot, meaning you'll have the same OOS version on both slots and "should" be able to flash a custom rom.
Infraviored said:
I am trying to get a custon ROM to work on my Oneplus 8 Pro (instantnoodlep)
ROMs I tried installing:
Cherish OS 3.9.5
Nameless-AOSP_instantnoodlep-12.1-20220708-0935-Official
What I do:
1. Download recovery provided with the ROM
2. Reboot to bootloader and flash recovery
'fastboot flash recovery recovery.img'
'fastboot reboot recovery'
3. Select apply update/apply from ADB
4. Connect device to PC
5. Sideload rom.zip
'adb sideload rom.zip'
6 Do Factory reset/format data from recovery
7. Restart to system
What happens:
Phone goes to fastboot and stays there.
When I try
fastboot reboot system
or
fastboot reboot recovery
I also land in fastboot again.
The only way to get out of fastboot again is fastboot boot recovery.img, which boots into recovery. When I then reboot into system, my old OOS11 boots up.
Because this is independent of the Custon ROM, there might be another issue. But which one?
Click to expand...
Click to collapse
U don't need the command fastboot reboot recovery. U can just use the volume buttons to select recovery and press power button to boot to recovery
Nimueh said:
When you're booted in OOS 11 just do a local install of the same OOS version that you're on. That will install OOS to the other slot, meaning you'll have the same OOS version on both slots and "should" be able to flash a custom rom.
Click to expand...
Click to collapse
Another way to set your phone up for a custom rom can be found here. https://wiki.lineageos.org/devices/instantnoodlep/install
Just make sure your booting from a good 00S11 install when you do this.
I had a heck of a time with this two days ago. OP pushed c33, A12 on my phone. It took forever to corrupt both a and b enough to get twrp recovery installed and working to install A11 again. I had to load the recovery on both slots, a and b and I used twrp install to install the OTA to slot a. Right now I have nothing on slot b other that twrp recovery.
king_xerxes said:
I had a heck of a time with this two days ago. OP pushed c33, A12 on my phone. It took forever to corrupt both a and b enough to get twrp recovery installed and working to install A11 again. I had to load the recovery on both slots, a and b and I used twrp install to install the OTA to slot a. Right now I have nothing on slot b other that twrp recovery.
Click to expand...
Click to collapse
Sorted it out by this. Thank you!