Anyone can upload TWRP backup the XT1069 , I realized Wipe System and have no backup
tks
sidneyft said:
Anyone can upload TWRP backup the XT1069 , I realized Wipe System and have no backup
tks
Click to expand...
Click to collapse
I don't think that someone else's backup will work on your phone lol, go here http://sbf.droid-developers.org/phone.php?device=36 and download your stock ROM, then flash it via fastboot
Thank you, I managed recovery my "Moto G" through the fastboot
Brick my phone again, after changing to ART.
The phone goes into bootloader mode, tried to flash via fastboot, but of the following errors:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 5.059s]
writing 'partition'...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.474s
Every command I do the fastboot appears the following error:
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition (comando que eu escrevi)
FAILED (remote failure)
Does anyone know what might be going on?
And you can not I use the recovery , any option I choose in cell itself appears: "boot up failed".
I also tried the RSD Lite, did not work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sidneyft said:
I also tried the RSD Lite, did not work
Click to expand...
Click to collapse
can you go into custom recovery or can you flash a custom recovery
Related
I had KK 4.4.4 running on my KF2 and now on the process of restoring the stock Amazon OS I'm facing an issue
where my device IS is fastboot, fastboot detects it but when I try to push something it stays on "waiting for device",
any ideas?
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is kind of ridiculous but after hours trying different drivers nothing worked so I tried to run a different fastboot command to see if it would work, I entered this:
Code:
C:\Restore>fastboot -i 0x1949 flash boot boot.img
target reported max download size of 486539264 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.469s]
writing 'boot'...
OKAY [ 0.891s]
finished. total time: 1.359s
And it worked, how come?
Then I thought, well, let me run the first command again, which would always hang on "waiting for device":
Code:
C:\Restore>fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
target reported max download size of 486539264 bytes
sending 'bootloader' (227 KB)...
OKAY [ 0.250s]
writing 'bootloader'...
OKAY [ 0.047s]
finished. total time: 0.297s
Bazinga!
Then I ran these commands:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img
fastboot -i 0x1949 reboot
And now the Kindle booted up.
Warning: This will most likely not work with the older cm11 bootloader please make sure you are using the latest bootloader!!
Hello!
Just figured out that the one can take bigger fastboot logo images than 446x56 so I made a Samsung download mode logo that shows when you enter fastboot mode!
Image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On actual device:
I am in no way responsible for any bricks caused by this, the guide and bin file both work 100% and were flashed numerous times by me! Always make sure the downloaded file is not corrupted (size for my logo.bin should be ~1361KB)
How to install:
1: Download this logo.bin file: Download (MD5: 9f3a4250452b8453f83d199db6a962ed)
2: Reboot into fastboot by holding power up and power until "fastboot mode" appears
3: Connect phone to computer
4: Flash the downloaded logo.bin file by typing: Fastboot flash LOGO logo.bin
5: If everything went well and no errors occured, type: fastboot reboot
6: Boot into fastboot again to see the result
Something wrong with the image? Want me to change/add something? Tell me via PM or reply to this post!
Reckon you could post the MD5? I really don't wanna accidentally get a corrupted download and flash it
TheLemonyOrange said:
Reckon you could post the MD5? I really don't wanna accidentally get a corrupted download and flash it
Click to expand...
Click to collapse
The MD5 should be 9f3a4250452b8453f83d199db6a962ed
Thank you! Will flash this once I get home or if I can get flashify functioning again
Hi there i have new problem when flashing the persist I get an error message
Sending 'persist' (32768 KB) OKAY [ 0.703s]
Writing 'persist' FAILED (remote: 'Flashing is not allowed for Controlled Partitions')
which one the solution? :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You gotta unlock flashing for critical partitions too.
Type *fastboot flashing unlock* then *fastboot flashing unlock_critical* on fastboot. After that, try to flash again.
Good luck.
Sent from my Mi A2 using XDA Labs
Cuesta4 said:
You gotta unlock flashing for critical partitions too.
Type *fastboot flashing unlock* then *fastboot flashing unlock_critical* on fastboot. After that, try to flash again.
Good luck.
Sent from my Mi A2 using XDA Labs
Click to expand...
Click to collapse
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.009s]
Finished. Total time: 0.010s
It's probably due to treble. 8.1 and 9.0 don't have a /persist partition, if I'm not mistaken.
Try goin back to 8.0 or Nougat and then flashing.
Sent from my Mi A2 using XDA Labs
EDIT: I believe I have deleted the recovery partition!? (not sure how that happened) I have verified this by trying to boot to recovery and it just cycles one time and then the next cycle it comes to the home screen. How do I fix this?
I have an Xperia XZ2 Dual SIM
I was able to unlock my phone, however when I try to either boot or flash TWRP I get these errors
I flashed stock rom using newflasher, I unlocked the Bootloader. Xperia says the bootloader is unlocked...
I cant proceed any further until i fix this. And YES I HAVE GOOGLED TO FIND THE ANSWERS ( I cant find one)
C:\ADB>fastboot flash recovery recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (4548 KB)...
OKAY [ 0.145s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 0.151s
C:\ADB>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.154s]
booting...
FAILED (remote: Invalid Boot image Header: Bad Buffer Size)
finished. total time: 0.166s
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm starting to think that this phone doesn't have a recovery partition. It does it some other way.
Someone will have to recomfirm that as that's what a absolute noob thinks after hours of searching.
A/B partitioned device does not have recovery partition, recovery is in ramdisk inside boot partition
Hi guys, something is wrong with my bootloader i assume. I cant get in recovery or the system. Only in fastboot. The only way to get into PixelExperience is by giving the phone the command: fastboot continue. How can I reflash the bootloader? fastboot flashing unlock_critical is an unknown command btw
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Larsos099 said:
Hi guys, something is wrong with my bootloader i assume. I cant get in recovery or the system. Only in fastboot. The only way to get into PixelExperience is by giving the phone the command: fastboot continue. How can I reflash the bootloader? fastboot flashing unlock_critical is an unknown command btw
View attachment 5883583
Click to expand...
Click to collapse
Try to flash stock ROM via miflash
Or if unlocked, in fastboot flash recovery and reboot to recovery. Then flash custom rom
Reinstall latest Xiaomi USB drivers into your Windows. That simple thing fixed an annoying blank response with "fastboot devices."
Larsos099 said:
Hi guys, something is wrong with my bootloader i assume. I cant get in recovery or the system. Only in fastboot. The only way to get into PixelExperience is by giving the phone the command: fastboot continue. How can I reflash the bootloader? fastboot flashing unlock_critical is an unknown command btw
View attachment 5883583
Click to expand...
Click to collapse
only possible with EDL