As I know, unlocking bootloader will erase the DRM data in my phone.
If fastboot.exe can write something to that hidden partition in fastboot mode, why can't we back it up?
Related
The backup I make of the 9 partition is like 7.5gigs. When I flash it is only 300megs. Does the dd command erase the entire partition and start from scratch. Does it just write over stuff? If it just writes over stuff what is the stuff that stays the same?
Hi guys I just recently encountered this issue where fastboot cannot flash anything (boot.img, system.img) on my device if its data and cache partitions are on F2FS. It shows the device serial number if I key in "fastboot devices", however.
Are there any modifications that I need to make to make fastboot work with a F2FS-enabled device?
Side Question: Does flashing a ROM via TWRP revert the F2FS partition back to EXT4? Or would it cause some problems with the ROM/flashing process?
No, only when you format that partition, then it go back to EXT4. Some roms work in EXT4 only, some work both
Hi all. My wife has a Moto Z Droid that has started bootlooping. I can get into the bootloader and recovery mode just fine, but every time I try to boot (normal or safe mode) I get to the lock screen and then the phone freezes. The status bar disappears and the phone reboots. I have tried wiping cache. I want to try to do a full factory reset, but my wife wants me to make sure all of her photos and videos are backed up. Is there any way to get her data off of the phone from bootloader/recovery, or does anybody have any other suggestions for correcting the issue without factory reset? Thanks!
unlock bootloader (voids warranty!)
[*] boot/flash TWRP recovery, mount data (..) partition(s)
[*] make a backup of everything (just to be safe), and/or..
[*] use TWRP's built-in file browser to selectively backup the fotos etc..
/EDIT:
without an already unlocked bootloader, you'd wipe all userdata by unlocking it, so that'd be no good for you.
Thanks to PiousInquisitor for pointing this out, I totally missed that...
Second, I have no idea what differences there are between a MOTO-Z (XT1650-03, "griffin") and MOTO-Z droid (XT????-??). There's no TWRP available for this device and I have no clue if the one made for XT1650-03 is compatible. However, we don't need to answer that, because it would need an unlocked bootloader that you probably don't have.
Other approach: find out, which exact software version your system runs. Fastboot dumps may help, but I'm not sure if all the OTA updates also update those information as well..
Code:
fastboot oem config
fastboot getvar all
fastboot oem hw
Copy & paste the output dump for later use.
Somwhere in the getvar dump you will find entries like this:
Code:
(bootloader) sku: XT1650-03
...
(bootloader) ro.build.version.full[0]: Blur_Version.24.21.46.griffin.ret
(bootloader) ro.build.version.full[1]: ail.en.US
The Moto-Z with SKU "XT1650-03" comes with the codename "griffin". According to the Log it runs on MM version 24.21.46. Based on this, I'd look for a ROM image of this version and carefully flash e.g. the system partition...
benzinerwin said:
unlock bootloader (voids warranty!)
boot/flash TWRP recovery, mount data (..) partition(s)
make a backup of everything (just to be safe), and/or..
use TWRP's built-in file browser to selectively backup the fotos etc..
Click to expand...
Click to collapse
The key word in the title is "Droid".
Unlocking the bootloader wipes the phone anyway.
Sent from my XT1650 using Tapatalk
I was attempting to unlock my bootloader and managed to fat finger one of the critical pieces. When typing fastboot -i 0x1949 erase aboot, I typed in fastboot -i 0x1949 erase boot. Which erased by boot partition. Now my device dutifully sits at the grey Kindle Fire logo, but never boots. I haven't otherwise done anything to this device, and it was running on a fresh installation of 4.5.5.3.
I can still access fastboot via a fastboot cable. I attempted to fix the issue by loading the boot partition with the boot.img found in the latest Amazon update files, but it didn't seem to have any effect.
I also attempted to boot into bulk mode, but issuing the command to erase the aboot partition returns a message that there is no aboot partition?
Is this a recoverable situation?
leeharrison1984 said:
I was attempting to unlock my bootloader and managed to fat finger one of the critical pieces. When typing fastboot -i 0x1949 erase aboot, I typed in fastboot -i 0x1949 erase boot. Which erased by boot partition. Now my device dutifully sits at the grey Kindle Fire logo, but never boots. I haven't otherwise done anything to this device, and it was running on a fresh installation of 4.5.5.3.
I can still access fastboot via a fastboot cable. I attempted to fix the issue by loading the boot partition with the boot.img found in the latest Amazon update files, but it didn't seem to have any effect.
I also attempted to boot into bulk mode, but issuing the command to erase the aboot partition returns a message that there is no aboot partition?
Is this a recoverable situation?
Click to expand...
Click to collapse
@draxie - thoughts?
I managed to get back in to TWRP by manually installing it via fastboot.
dl.twrp.me/soho/
However, my real problem was I was using my Soho KF, not a Thor/Apollo variant.
I managed to get things sorted and unbricked the Soho, thanks for showing up though!
I used fastboot to delete all partitions (boot, recovery, userdata, system) using the command fastboot erase 'partion' . (Sent the phone for repair to a shady dealer (Screen Replacement) and wanted to ensure that they could not install any software on it without me noticing.)
My plan to recover the phone is to flash TWRP, boot to TWRP and restore the boot partition from a previous backup. Then I'll be able to flash a ROM and use the phone normally.
The only thing that bothers me is the possibility that I might not be able to boot into the recovery due to the missing boot partition. Can someone clear it up? I've looked on XDA for someone with the same problem and the only thread that was close was someone who deleted the boot partition and could no longer see their device on adb. (I can see the device listed when I run fastboot devices)
Can I download the boot partition and flash it through fastboot? If so, where can I find the boot partition. (Keep in mind that I have a TWRP backup which has the boot partition but would require me to boot into the recovery in the first place) Also, is there any specific command that I can use to flash the boot partition?
Also, I do not currently have the phone in hand so that I can try the method I listed above. If someone could clarify whether or not the method is working and if not provide an alternative method would be a great help.
Bootloader is unlocked. (IDK if that matters anymore.) I have ADB, TWRP img file and a backup.
Cheers.
you can flash using 9008 mode which doesn't require any partition
chetan180 said:
you can flash using 9008 mode which doesn't require any partition
Click to expand...
Click to collapse
Thanks.
But you didn't answer my question. Will I be able to boot into TWRP and restore the boot partitions using a backup?
I am talking about the commands
Code:
fastboot boot twrp-x-x-x.img
or
Code:
fastboot flash recovery twrp-x-x.img
Also, can you link to a post explaining how to use 'Qualcomm 9008' mode?
SohrabHamza said:
Thanks.
But you didn't answer my question. Will I be able to boot into TWRP and restore the boot partitions using a backup?
I am talking about the commands
Code:
fastboot boot twrp-x-x-x.img
Also, can you link to a post explaining how to use 'Qualcomm 9008' mode?
Click to expand...
Click to collapse
i think fastboot boot twrp.img you'll be able to boot into twrp n restore
some 9008 guides
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/