(I've searched around quite a bit in this forum and have not been able to answer the below question. Any assistance would be very appreciated.)
I am attempting to take a recovery/backup of a Pixel 3 using TWRP. I do not need to flash TWRP, just boot from it to perform the backup. Meaning, I don't care if TWRP is installed permanently.
The problem I am running into is that I need to unlock the bootloader before I can boot TWRP. And if I unlock the bootloader, the data on the device will be erased.
My question is: If I unlock the bootloader, will I be able to boot back into fastboot mode, and thus boot into TWRP, before the erasure occurs? And if to, how do I perform this? (I presume that if I hold the volume down button it will before rebooting it will go back into fastboot mode.)
I would rather not erase the phone. But if there is no other way I at least need the backup before the erasure occurs.
Thanks in advance for any assistance provided.
UPDATE: I found this thread, possibly it might work for a Pixel 3?
I am sorry I am of no help.... I only chimed in to say I could never get a working version of TWRP when I went to look for it on blueline. All I could get was Lineage Recovery so I have no idea if there is a way to backup before the wipe...
Related
My apologies if this post is not in the correct formatting or location.
A couple of days ago I flashed the Euroskank release of CM10 (10-20120816-UNOFFICIAL-crespo4g, to be exact) and after that, I have not been able to boot into recovery either from the power button's reboot menu or booting into the bootloader then recovery.
When I tried with both methods, I was presented with a completely blank screen and lit up, unresponsive capacitive keys. This state ususally persists for two minutes before shutting down and booting, normally, into the system where everything works as it should. Another forum post suggested using strong ambient lighting to see the standard onscreen options but my screen is completely blank.
I tried to reinstall the recovery with Rom Manager, which yielded the same result, and with fastboot, both flashing the recovery over the existing one and erasing the recovery partition and then flashing it.
I then thought to flash TWRP as it might have been a problem with CWM recovery. Once I flashed TWRP and booted into recovery, I was shown the standard TWRp splash screen for two minutes before the phone rebooted into the system.
I'm thinking there might be a problem with the unlocked state of my phone, even though it is OEM unlocked and there hasn't been any problems before.
I don't know how to fix this. Any help would be greatly appreciated!
[SOLVED]
It appears that the only way to fix this problem is to relock the device using fastboot and then to unlock it using the same method.
First of all backup everything you need.
1st method: try flashing a different rom, especially a stock one would be great, probably that does the trick.
If the first one doesnt help ypu can lock and unlock your phone again, since the unlocking procedure sets everything to default parameters.
Please report back, I'm curious.
miklosbard said:
First of all backup everything you need.
1st method: try flashing a different rom, especially a stock one would be great, probably that does the trick.
If the first one doesnt help ypu can lock and unlock your phone again, since the unlocking procedure sets everything to default parameters.
Please report back, I'm curious.
Click to expand...
Click to collapse
Thanks for the response!
Unfortunately, I'm unable to make a nandroid backup, as well as flashing any roms, since recovery is completely inaccessible. I am forced to rely entirely on Titanium backups and SMS backup. However I will relock and unlock in a bit once I'm sure no one is going to contact me.
Have you tried booting into recovery through ROM manager?
Sent from my Nexus S using Tapatalk 2
Hi guys, I'm normally the one who reads these forums, not starts them, so i'm in pretty desperate help.
I have a Samsung Nexus S phone that somehow got stuck in a bootloop after my dad attempted to fix the problem by wiping everything he could from the recovery; cache, system, data, factory reset. I am able to access fastboot (obviously). In fastboot mode, the only 4 options it gives are POWER OFF, REBOOT, RECOVERY, REBOOT BOOTLOADER. None of these options leads to any progress. Only one that makes sense is to click and run recovery. When recovery loads, i can:
Reboot system now
apply update from ADB
apply update from sd card
wipe/factory reset
wipe cache partition
I recently rooted and custom ROMed my Galaxy J7 Pro, and as you experts may know it wasn't too easy finding the correct files or even the support for it.
I know you have to have developer options enabled and OEM and USB Debugging as the prereqs for rooting, but this phone has nothing. I'm not sure what to do. The bootloader is locked and I obviously can't enable developer options. I guess where I'm stuck is how i can flash a custom recovery like twerp for a phone that has a locked bootloader that can't be unlocked through developer options.
As I'm writing this, i was thinking, can i prepare an SD card with the lollipop OS for the nexus to install and run on. Ive already wiped the internals and cache of the phone, meaning there is nothing on it?
Help would be appreciated, bringing back a phone that has the potential (working hardware) to run would be great.
Just do a manual restore using the google factory images (google them, first result usually and a VERY user friendly page, thanks google!).
Don't use the script, just reformat everything via fastboot, then manually flash the images to their respective partitions.
"cd [path to unzipped images]"
"fastboot format /[partition] ext4"
"fastboot flash /[partition] [path to image]"
and so on and so on. Then after, "fastboot reboot". I assume you've found a fix by now but maybe someone else will stumble on this. Keep in mind, I'm writing this from memory and with no drivers or way to test this on my mac, my Nexus S is coming in the mail soon so take what I say with a grain of salt and try to double check the commands. For the most part however, they should be correct. format, reflash, reboot. All you should have to do.
padhpataka said:
Hi guys, I'm normally the one who reads these forums, not starts them, so i'm in pretty desperate help.
I have a Samsung Nexus S phone that somehow got stuck in a bootloop after my dad attempted to fix the problem by wiping everything he could from the recovery; cache, system, data, factory reset. I am able to access fastboot (obviously). In fastboot mode, the only 4 options it gives are POWER OFF, REBOOT, RECOVERY, REBOOT BOOTLOADER. None of these options leads to any progress. Only one that makes sense is to click and run recovery. When recovery loads, i can:
Reboot system now
apply update from ADB
apply update from sd card
wipe/factory reset
wipe cache partition
I recently rooted and custom ROMed my Galaxy J7 Pro, and as you experts may know it wasn't too easy finding the correct files or even the support for it.
I know you have to have developer options enabled and OEM and USB Debugging as the prereqs for rooting, but this phone has nothing. I'm not sure what to do. The bootloader is locked and I obviously can't enable developer options. I guess where I'm stuck is how i can flash a custom recovery like twerp for a phone that has a locked bootloader that can't be unlocked through developer options.
As I'm writing this, i was thinking, can i prepare an SD card with the lollipop OS for the nexus to install and run on. Ive already wiped the internals and cache of the phone, meaning there is nothing on it?
Help would be appreciated, bringing back a phone that has the potential (working hardware) to run would be great.
Click to expand...
Click to collapse
I have the same problem.I know this was 4 years ago but as a noob I find that guides tend to assume greater levels of knowledge than I have. Trying to bypass FRP as I think this is what is causing the "system error" message when I try to access play store or Google plus. I haven't even been able to unlock bootloader or root phone . In fact I find "fastboot" and ADB downloads a mystery? How to get them to work?
Hi All,
I've been trying to install TWRP, Root etc on my XZP since yesterday. I've done something wrong at some point, and now my phone will not boot at all.
I had no troubles unlocking bootloader, installing TWRP etc initially. I then tried to install a custom rom from these forums and that's where things spiraled downwards for me.
As part of that procedure, I needed to flash the latest sony firmware first. That went fine.
However, now TWRP is not able to decrypt storage, so I'm not able to flash anything else. Perhaps this is because I booted into the new sony firmware and forgot change the pattern/fingerprint to pin/fingerprint.
So I'm not able to unlock the storage via TWRP by entering a password.
I tried to reflash the same firmware again using newflasher. But the phone won't boot at all. It turns off immediately after the Unlocked bootloader warning. It's not going into a boot loop. Just turns off.
I then tried to flash the TWRP recovery image using adb fastboot command, and the flash seemed to execute properly, but I still can not boot into recovery.
Is it possible the main storage is still encrypted, so nothing can flash to it? Bricked? If so, how do I proceed?
I read something about reformatting partitions? But I'm not able to get into TWRP recovery menu to do this.
*EDIT: I reflashed trwp recovery image, and am not able to boot into recovery. I still can not unlock (unencrypt) the main storage though.
*2nd EDIT: I followed the instructions here:https://forum.xda-developers.com/android/general/how-to-fix-unable-to-mount-data-t3830897
I was then able to flash the stock ROM back onto my device, and I'm able to boot my phone up. I'll look at installing a custom ROM at a later date.
Thread closed at OP request
Hey,
Quick rundown: Stuck in a bootloop to some sort of empty bootloader screen which has the readout:
"Start/Restart Bootloader/Recovery Mode/Power Off"
"Press volume key to select, and press power key to select"[Regarding above options]
"FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [Gonna leave this out for now]
SECURE BOOT - yes
DEVICE STATE - unlocked" [this line is in red]
Every choice besides Power Off returns me to the same window. What can I do to recover from this?
Background:
So I was trying to update my OP6 to the current OxygenOS while keeping my root using TWRP and Magisk, which I've done in the past without any issue(i.e. go in recovery flash OS, flash current TWRP, reboot back to recovery, flash current Magisk as I understand it). However this time I was running into an issue flashing the Oxygen update getting an error that said it "failed to map file" for the zip. My first instinct was to update TWRP to see if the newest version didn't run into this issue so I flashed that followed by the current Magisk(no reboot in between). After booting back to standard operations everything seemed fine. I went back into recovery and tried the OS update again, but hit the same issue.
I couldn't find anything specific to OP6 with this issue, but similar questions with other devices suggested clearing the dalvik cache, which I tried to no useful effect. Then I came across this thread (forums.oneplus.com/threads/oxygen-os3-i-have-a-problem-please-help.440587/page-2 too new to hyperlink) and did what I think really messed me up which was boldly follow this guy's advice to do an advanced wipe of everything but internal storage(I also left USB storage intact) from TWRP. This failed to fix the issue with the file mapping error when I subsequently tried to flash the update, though I was able to flash TWRP and Magisk successfully again before rebooting and ending up in this loop.
Any assistance in fixing this or general tips on how to not be foolish when messing around with this stuff is greatly appreciated.
Update:
So I followed the advice gleaned from the resourceful person here(https://forum.xda-developers.com/oneplus-6t/help/bootloader-baseband-versions-blank-t3927565) to try working with the device from my computer with fastboot. At first it would recognize the device as "Android" but be unable to find a driver for it and adb/fastboot both failed to recognize it as a device. After installing MiniTool(more as a way to backup what was on the SD card) the proper device driver also got installed and I was able to access it with fastboot; I ran into similar issues as the linked thread above, solved it by switching to b(still failed) then back to a.
Currently I've got it booted into TWRP and I'm working on getting the current Oxygen .zip copied onto the phone storage but the transfer keeps failing after moving a negligible amount.
Update 2:
Via TWRP was able to sideload the current up-to-date standard OS onto it, however my Google backup seems to have decided to disappear on me and the only OP backup I have is ages old. Anyone have recommendations on data recovery tools?
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
NickTheHuy said:
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
Click to expand...
Click to collapse
Good to know, thanks for the info!
I assume that happened when I messed around with advanced wipe, do you know which of the folders I selected that would have been under? And just for future awareness, would that have not occurred had I just used TWRP's standard wipe instead?
You can run a program that will install 9.0.6 from scratch, running a batch file...
Save my life before yesterday....
Your device is bricked
If able to access the TWRP recovery then boot into twrp and try to get all the data stored in your computer.
Then use the Qualcomm flash tool to completely recover from your hard bricked OP6.
from here https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Then its easy, again unlock boot-loader flash TWRP and magisk.
I have been trying to root my ASUS ROG Phone 1 for almost a month now. I already opened the bootloader, however, I am struggling in finding the right TWRP image. I tried too many images some of which locked the phone (the phone starts to ask for a password after rebooting and I had to reset factory). Other images do nothing, i.e., when I run fastboot boot twrp_Z01QD..img, the CMD shows that the boot was successful, but the phone does not reboot into TWRP. Lately, I used an image that indeed reboots the phone into the TWRP recovery, however, TWRP asks for a decryption password. I use no password for my phone. I tried the "default_password" password. None of them worked. After that, I removed the data encryption totally from my phone by running the following commands: fastboot format userdata; fastboot format cache; fastboot reboot. However, this did not solve the problem.
I think that the problem might be in the version of TWRP I am using. Any help in locating the right image to be used will be highly appreciated. Also, if you have any clue how to go around the password, please let me know.
If there is anything not clear in my request, please let me know.
Thank you in advance.
You should try porting twrp recovery
Just search on google how to port twrp recovery.
Hey Dreto, thank you for your help. I googled how to port TWRP recovery, and I felt that it is a time-consuming process so I decided to keep it as my last resort. So before trying it, I tried to flash the image without the help of TWRP and it worked out. The phone is now rooted.
Again, thank you for your help.
AliMazloum said:
Hey Dreto, thank you for your help. I googled how to port TWRP recovery, and I felt that it is a time-consuming process so I decided to keep it as my last resort. So before trying it, I tried to flash the image without the help of TWRP and it worked out. The phone is now rooted.
Again, thank you for your help.
Click to expand...
Click to collapse
No problem