Kindle Fire 2nd Generation Recovery Isssues - General Questions and Answers

I currently have a bricked Kindle Fire 2nd Gen and I am having trouble recovering it.
I have used those unbrick tools and also the standard adb interface, but I always run into one issue. Whenever I try to flash the system, i get an error. This is from when I try to do it from the adb interface:
Code:
fastboot flash system system.img
target reported max download size of 486539264 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/2 (473434 KB)...
OKAY [ 14.739s]
writing 'system' 1/2...
FAILED (remote: : Sparsed Write)
finished. total time: 14.816s
And this is what I get when I do it from the unbrick tool:
Code:
sending 'system' (907264 KB)...
FAILED (remote: data too large)
finished. total time: 0.049s
I have tried seeing if the fastboot version was up to date (which it was).
Code:
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
At this point i have no idea what to do. I would post this to the Kindle Fire 2nd Gen Discussion, but I do not have a high enough post count. So I am stuck with the Q&A Discussion.

Related

[Q] [SOLVED] “Invalid image size for partition recovery”

I'm trying to flash a recovery image to a Razr Maxx HD, but I'm not entirely sure that I'm doing it correctly.
Code:
$ sudo fastboot flash recovery ~/recovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7340 KB)...
OKAY [ 0.589s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.734s
Afterwards, my phone says “invalid image size for partition recovery.” The image I'm using is at goo .im /devs /Hashcode /vanquish, and I've tried all three versions. Am I on the right track at all or no?
Edit: Never mind. Gotta unlock the phone first. Problem solved.
I also saw that error when it was the wrong carrier recovery image

XT1541 broken after attempt do factory reset

Dear all,
I own a XT1541 and updated to Marhsmallow via OTA few weeks ago. I encountered some troubles with the performance. I also had the issue that a single app was attempted to be optimized on every boot. Therefore, I decided to reset it to factory settings. However, it seemed that this process failed (waited nearly for an hour to complete but nothing happened).
After rebooting then manually, I am stuck in a fastboot message
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from charger boot mode
CID Read Failure
Invalid CID status 0x69
I can access the device via my Linux using fastboot command. What do you propose to recover from my problem.
Thanks
IK1981 said:
Dear all,
I own a XT1541 and updated to Marhsmallow via OTA few weeks ago. I encountered some troubles with the performance. I also had the issue that a single app was attempted to be optimized on every boot. Therefore, I decided to reset it to factory settings. However, it seemed that this process failed (waited nearly for an hour to complete but nothing happened).
After rebooting then manually, I am stuck in a fastboot message
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from charger boot mode
CID Read Failure
Invalid CID status 0x69
I can access the device via my Linux using fastboot command. What do you propose to recover from my problem.
Thanks
Click to expand...
Click to collapse
Try flashing the factory image here are the instructions
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
bobby0724 said:
Try flashing the factory image here are the instructions
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Click to expand...
Click to collapse
Already tried this. Already fails at first command... When doing this for the first time, it takes up to one minute to get a response. When retrying, it fails immediately
Code:
~/Downloads/XT1541_OSPREY_RETEU_6.0_MPI24.65-33.1_cid7_subsidy-DEFAULT_CFC__v2.xml# fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 55.425
Try usuing my Motorola downgrade tool , or Motorola utility , created by me , to try and fix problems like this. Links can be found in the general section of Moto g 3 forums , or in Moto g 3 devdb. Therealduff1 is the username you are looking for . I am happy to try and help you with this !
therealduff1 said:
Try usuing my Motorola downgrade tool , or Motorola utility , created by me , to try and fix problems like this. Links can be found in the general section of Moto g 3 forums , or in Moto g 3 devdb. Therealduff1 is the username you are looking for . I am happy to try and help you with this !
Click to expand...
Click to collapse
Thanks for your help. Tried it with your tool but as far as I could see I land in the same troubles.
Code:
OSPREY_RETEU_6.0_MPI24.65-33_cid7_subsidy
please move all of the firmware files into the moto toolkit directory (the same folder containing toolkit.py)
Please make sure usb debugging is turned on in developer settings, then type 'done' into this promptdone
error: device '(null)' not found
Has your device successfully loaded bootloader mode ? please type 'yes' if it has successfully loadedyes
Press enter to confirm you would like to upgrade to android marshmallow ;)
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 55.795s
Partition table has been flashed
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 1.438s
Bootloader has been flashed
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.062s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.172s
boot logo has been flashed
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.530s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.093s
boot.img has been flashed
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.094s
Stock marshmallow recovery has now been flashed
target reported max download size of 268435456 bytes
sending 'system' (238438 KB)...
OKAY [ 7.500s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 15.891s
System part 1 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (238552 KB)...
OKAY [ 7.492s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 9.608s
System part 2 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (256695 KB)...
One thing that confuses me is the fact that the tool tells me that I shall turn on the USB debug mode. However, since Android does not boot any longer, I have no chance to do this in the Settings. Is there any way to enable this debug mode in another way?

Problems with moto g3 downgrade marshmellow to lollipop

OK I HAVE A MOTO G3 , SKU=XT1541 , VER=P2B , BUILD MP.124.107.55 , SYS VERS=24.61.55OSPREY
It is an unlocked euro version with 1gb ram , i.e not locked to any carrier or ever has been.
I was able to unlock the bootloader , I then followed very carefully the instructions on this site to get the image , usb drivers and everthing required.
However once ono entering the commands at the dos window to start flashing a new rom it comes back with an error , I think I have the incorrect image or there is not one on this site.
I am a complete nuubie can anyone help me please.
D:\XT1541_OSPREY_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.417s
D:\XT1541_OSPREY_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml>
I get this after entering fastboot flash partition gpt.bin
some progress
robin red said:
D:\XT1541_OSPREY_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.417s
D:\XT1541_OSPREY_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml>
I get this after entering fastboot flash partition gpt.bin
Click to expand...
Click to collapse
ok I managed to get to the part when I load the sparse files 0-5 , it send them all but reports failure on them all every other command on the list executes correctly.
After this it locked for a while a rebooted in version 6 marshmellow.!!!!! well I guess I am learning.
Anyone any ideas , guess I am lucky I did not brick the thing.
here is what I am getting after entering the third command
C:\Users\Robin L\Desktop\roby>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.470s

Never seen a brick this hard to solve...

So I have an Honor 8 FRD-L04 that I was trying to root today. I flashed TWRP and all was good. Until I tried to install SuperSU using TWRP. It said my data partition wasn't able to be found or something, I can't remember. So I did some quick Googling and tried some fixes (changing the partition format to FAT and back to EXT4, etc). This just screwed it up even more. So here's the scenario:
*Can't access ADB anymore, doesn't show up in devices
*Can access fastboot, however:
I usually get "FAILED (remote: Command not allowed)" when I try to do any commands (bootloader is unlocked). Because of this, I can't flash extracted .IMG files.
*eRecovery tells me "Getting Package Info Failed"
*Don't have access to TWRP anymore
*Have tried multiple firmwares using the dload method, either they can't install or simply do nothing
*I've tried Huawei Multi Tool and got the following output:
Code:
RNV0216B29003646 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (15440 KB)...
OKAY [ 0.332s]
writing 'boot'...
OKAY [ 0.370s]
finished. total time: 0.710s
target reported max download size of 471859200 bytes
sending 'cust' (252389 KB)...
OKAY [ 5.407s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 5.418s
target reported max download size of 471859200 bytes
sending 'recovery' (36976 KB)...
OKAY [ 0.791s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.675s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (424496 KB)...
OKAY [ 9.894s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 9.945s
*I've tried using the dload method by first installing the rollback package (which actually installed), and then installing the actual firmware. But of course, the installation of the actual firmware failed.
I've probably tried a few other things, but I'm just so frustrated I can't remember. If anyone can suggest anything else, I'd greatly appreciate it.
This is really bad. The solution to your first problem was to simply remove encryption by formatting data.
Jdelacrix said:
So I have an Honor 8 FRD-L04 that I was trying to root today. I flashed TWRP and all was good. Until I tried to install SuperSU using TWRP. It said my data partition wasn't able to be found or something, I can't remember. So I did some quick Googling and tried some fixes (changing the partition format to FAT and back to EXT4, etc). This just screwed it up even more. So here's the scenario:
*Can't access ADB anymore, doesn't show up in devices
*Can access fastboot, however:
I usually get "FAILED (remote: Command not allowed)" when I try to do any commands (bootloader is unlocked). Because of this, I can't flash extracted .IMG files.
*eRecovery tells me "Getting Package Info Failed"
*Don't have access to TWRP anymore
*Have tried multiple firmwares using the dload method, either they can't install or simply do nothing
*I've tried Huawei Multi Tool and got the following output:
Code:
RNV0216B29003646 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (15440 KB)...
OKAY [ 0.332s]
writing 'boot'...
OKAY [ 0.370s]
finished. total time: 0.710s
target reported max download size of 471859200 bytes
sending 'cust' (252389 KB)...
OKAY [ 5.407s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 5.418s
target reported max download size of 471859200 bytes
sending 'recovery' (36976 KB)...
OKAY [ 0.791s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.675s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (424496 KB)...
OKAY [ 9.894s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 9.945s
*I've tried using the dload method by first installing the rollback package (which actually installed), and then installing the actual firmware. But of course, the installation of the actual firmware failed.
I've probably tried a few other things, but I'm just so frustrated I can't remember. If anyone can suggest anything else, I'd greatly appreciate it.
Click to expand...
Click to collapse
I'm going to cover the basis here, as I've seriously screwed over my phone before but recovered.
If you managed to get the phone responsive with the rollback package try flashing the EMUI 4 package.
If that doesn't work, plug into the computer and press and hold the power and volume down buttons to get into fastboot: unlock oem if possible
let me know if that gets you started.
sonicscrewup said:
I'm going to cover the basis here, as I've seriously screwed over my phone before but recovered.
If you managed to get the phone responsive with the rollback package try flashing the EMUI 4 package.
If that doesn't work, plug into the computer and press and hold the power and volume down buttons to get into fastboot: unlock oem if possible
let me know if that gets you started.
Click to expand...
Click to collapse
i was in a similar situation and this method worked! connect the phone to pc in switched off condition, press power+vol down and get into fastboot and then oem unlock, install twrp and tried to installed the zips.. worked and phone booted!!

Stuck in bootloader nothing loads

Update: Of course... bad abd files quick update and everything went smooth.
Tried to root with magisk and got stuck in bootloop so I tried to install factory image and just be done with it and now its stuck in bootloader. trying to boot recovery just reboots into bootloader trying to use deuces script doesnt work and the flash-all script just fails its bootloader .0059 and its in boot-slot B and wont change to slot a. Havent had the phone long so im desperate to try and fix it if at all possible.
example of the flash-all
Code:
< waiting for any device >
target didn't report max-download-size
sending 'bootloader' (38728 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: -0.000s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.003s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.153s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
tried flashing twrp and got
Code:
C:\Users\coolp\Downloads>fastboot flash recovery twrp-3.2.1-0-walleye.img
target reported max download size of 536870912 bytes
sending 'recovery' (32768 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
Coolpente said:
Update: Of course... bad abd files quick update and everything went smooth.
Tried to root with magisk and got stuck in bootloop so I tried to install factory image and just be done with it and now its stuck in bootloader. trying to boot recovery just reboots into bootloader trying to use deuces script doesnt work and the flash-all script just fails its bootloader .0059 and its in boot-slot B and wont change to slot a. Havent had the phone long so im desperate to try and fix it if at all possible.
example of the flash-all
Code:
< waiting for any device >
target didn't report max-download-size
sending 'bootloader' (38728 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: -0.000s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.003s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.153s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
tried flashing twrp and got
Code:
C:\Users\coolp\Downloads>fastboot flash recovery twrp-3.2.1-0-walleye.img
target reported max download size of 536870912 bytes
sending 'recovery' (32768 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
Click to expand...
Click to collapse
Try new platform tools. Then try different computer and usb cable. Preferably the usb c to c cable.
enzyne said:
Try new platform tools. Then try different computer and usb cable. Preferably the usb c to c cable.
Click to expand...
Click to collapse
I did the new platform tools and it worked. I was not capable of using another cable since I dont have an adapter for the c to c.
How odd. Latest platform tools from google. Two computers. Two pixel2 phones. Yes, TWO phones! Four cables. All the exact same result. The deuces script wiped twrp and I'm beginning to believe it installed a borked bootloader:
fastboot flash recovery twrp-3.2.1-0-walleye.img
target reported max download size of 536870912 bytes
sending 'recovery' (32768 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
fastboot --version
fastboot version 0.0.1-4500957
Installed as /usr/bin/fastboot
dattaway said:
How odd. Latest platform tools from google. Two computers. Two pixel2 phones. Yes, TWO phones! Four cables. All the exact same result. The deuces script wiped twrp and I'm beginning to believe it installed a borked bootloader:
fastboot flash recovery twrp-3.2.1-0-walleye.img
target reported max download size of 536870912 bytes
sending 'recovery' (32768 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
fastboot --version
fastboot version 0.0.1-4500957
Installed as /usr/bin/fastboot
Click to expand...
Click to collapse
Are you flashing the proper factory image? Have you tried re downloading?
enzyne said:
Are you flashing the proper factory image? Have you tried re downloading?
Click to expand...
Click to collapse
How do I tell which is the proper factory image? There are 15 listed for the Pixel 2. Since I bought my two Pixel phones directly from Google, there appears to be 5 that might work, so I tried each one with identical results. SHA-256 Checksums match.
dattaway said:
How do I tell which is the proper factory image? There are 15 listed for the Pixel 2. Since I bought my two Pixel phones directly from Google, there appears to be 5 that might work, so I tried each one with identical results. SHA-256 Checksums match.
Click to expand...
Click to collapse
I just wanted to make sure there wasn't any data corruption. The most recent one which was .19 should do the trick if that's not working and you've tried everything else it may be time to do an RMA.
Sorry to piggyback on a thread, but I seem to be having the same problem (I think). All I did was update Magisk to 16.0, then reboot my phone now I'm stuck in bootloader, none of the options do anything except make the screen go black for a minute then go back to the bootloader screen (assuming the bootloader screen is the one with the Android laying on it's back).
Is the main fix to re-flash a google factory image? OP said something about bad abd files, but I haven't even tried to push anything with adb since I rooted my phone last month. Or should i use the fix bootloop script in the other thread?
Rookx said:
Sorry to piggyback on a thread, but I seem to be having the same problem (I think). All I did was update Magisk to 16.0, then reboot my phone now I'm stuck in bootloader, none of the options do anything except make the screen go black for a minute then go back to the bootloader screen (assuming the bootloader screen is the one with the Android laying on it's back).
Is the main fix to re-flash a google factory image? OP said something about bad abd files, but I haven't even tried to push anything with adb since I rooted my phone last month. Or should i use the fix bootloop script in the other thread?
Click to expand...
Click to collapse
What your talking about is the android stock recovery not the bootloader.

Categories

Resources