I have a Nexus 7 LTE tablet, I recently did a Paranoid android update and everything went smooth. I performed my nandroid backup as I normally would. At some point during the day, my screen went black. I tried rebooting the tablet, but the screen was still black. The device appears to boot fine. I have no boot screen, I cannot enter TWRP or any other boot loader. The notification indicator light blinks and I was able to access the device via adb.
I decided to flash the default nexus 7 firmware using the official google files - 4.4.2 (KOT49H) assuming this would work as per the directions I read in similar threads.
My issue continunes. I still have a black screen. I can no longer access ADB. Fastboot on the other hand works just fine.
Here is the output of my last flash attempt.
Code:
./flash-all.sh
sending 'bootloader' (3911 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 1.355s]
finished. total time: 1.484s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
sending 'radio' (76038 KB)...
OKAY [ 2.388s]
writing 'radio'...
OKAY [ 2.995s]
finished. total time: 5.383s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: DEB-Z00_2.42.0_1204
Serial Number........: 0*******
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.004s]
sending 'boot' (7018 KB)...
OKAY [ 0.268s]
writing 'boot'...
OKAY [ 0.348s]
sending 'recovery' (7566 KB)...
OKAY [ 0.283s]
writing 'recovery'...
OKAY [ 0.290s]
erasing 'system'...
OKAY [ 1.296s]
sending 'system' (730592 KB)...
OKAY [ 24.929s]
writing 'system'...
OKAY [ 32.060s]
erasing 'userdata'...
OKAY [ 25.211s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 28856791040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7045115
Block groups: 215
Reserved block group size: 1024
Created filesystem with 11/1761280 inodes and 154578/7045115 blocks
sending 'userdata' (139085 KB)...
writing 'userdata'...
OKAY [ 12.329s]
erasing 'cache'...
OKAY [ 0.445s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
sending 'cache' (10984 KB)...
writing 'cache'...
OKAY [ 0.874s]
rebooting...
finished. total time: 98.361s
Even after a clean flash I still get a black screen and only fastboot is accessible.
What can I do to get rid of this black screen and get my tablet back in working condition?
Any help is appreciated.
I have the same issue, but I am stuck on google boot loop. I have tried going back to old factory roms, but still no good.
Have you tried using old factory roms? And were you able to go to recovery from bootloader? I can't even flashing stock recovery.
0wangj4 said:
Have you tried using old factory roms? And were you able to go to recovery from bootloader? I can't even flashing stock recovery.
Click to expand...
Click to collapse
I have no bootloader available as the screen is black. I can only access fastboot. I tried flashing the original google supplied firmware as well with no luck.
micemicerabies said:
I have no bootloader available as the screen is black. I can only access fastboot. I tried flashing the original google supplied firmware as well with no luck.
Click to expand...
Click to collapse
As I look at the script it looks like that was a very fast flash. Did you check the MD5 to make sure the file was not corrupted? Because it does not even look like anything flashed.
Edit: At best, maybe, the system flashed but boot and recovery were done in a couple seconds. I'd check the MD5 or reflash the images.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
As I look at the script it looks like that was a very fast flash. Did you check the MD5 to make sure the file was not corrupted? Because it does not even look like anything flashed.
Edit: At best, maybe, the system flashed but boot and recovery were done in a couple seconds. I'd check the MD5 or reflash the images
Click to expand...
Click to collapse
Code:
root[email protected]:/root/# md5sum razorg-kot49h-factory-49789b24.tgz && sha1sum razorg-kot49h-factory-49789b24.tgz
8e42ffe324a9109031dd4f9dd53fdc9a razorg-kot49h-factory-49789b24.tgz
49789b240cab9a8e91c1f5a3eb0b6be0b07b5732 razorg-kot49h-factory-49789b24.tgz
Correctly hashes against
MD5SUM = 8e42ffe324a9109031dd4f9dd53fdc9a
SHA1SUM = 49789b240cab9a8e91c1f5a3eb0b6be0b07b5732
For the 4.4.2 (KOT49H) Image (NOTE: The original flash that I showed the output for was for the later image 4.4.2_r2 (Verizon) (KVT49L)) In the past I have had more success with the KOT49H image and will continue testing using this image.
Here is the latest attempt at flashing using the flash-all.sh script
Code:
[email protected]:/root/razorg-kot49h-factory-49789b24/razorg-kot49h# ./flash-all.sh
sending 'bootloader' (3911 KB)...
OKAY [ 0.244s]
writing 'bootloader'...
OKAY [ 1.383s]
finished. total time: 1.627s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
sending 'radio' (43830 KB)...
OKAY [ 2.666s]
writing 'radio'...
OKAY [ 1.748s]
finished. total time: 4.415s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: DEB-G00_2.37.0_1024
Serial Number........: 0*******
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.004s]
sending 'boot' (7018 KB)...
OKAY [ 0.424s]
writing 'boot'...
OKAY [ 0.369s]
sending 'recovery' (7566 KB)...
OKAY [ 0.456s]
writing 'recovery'...
OKAY [ 0.281s]
erasing 'system'...
OKAY [ 1.304s]
sending 'system' (721408 KB)...
OKAY [ 43.544s]
writing 'system'...
OKAY [ 30.515s]
erasing 'userdata'...
OKAY [ 22.401s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 28856791040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7045115
Block groups: 215
Reserved block group size: 1024
Created filesystem with 11/1761280 inodes and 154578/7045115 blocks
sending 'userdata' (139085 KB)...
writing 'userdata'...
OKAY [ 14.458s]
erasing 'cache'...
OKAY [ 0.484s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
sending 'cache' (10984 KB)...
writing 'cache'...
OKAY [ 1.179s]
rebooting...
finished. total time: 115.443s
I agree that these write speeds seem a little too quick
Sidenote: Before I tried this last flash I was able to confirm that the digitizer is functional. The devices appeared to boot into the factory image (screen was still black) I was some how able to get the accessibility options enabled so that the devices would speak out my actions. I did not complete this tutorial. This leads me to believe there is some more bizarre underlying screen issue. Possibly a loose cable?
Hopefully something here can help.
Code:
fastboot getvar all
(bootloader) version-bootloader: FLO-04.02
(bootloader) version-baseband: DEB-G00_2.25.1_0802
(bootloader) version-hardware: rev_e
(bootloader) version-cdma: N/A
(bootloader) variant: deb 32G
(bootloader) serialno: 0*******
(bootloader) product: deb
(bootloader) secure_boot: enabled
(bootloader) lock_state: unlocked
(bootloader) project: deb
(bootloader) off-mode-charge: yes
(bootloader) uart-on: no
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:bootloader: 0x0000000000aee000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:recovery: 0x0000000000a00000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x0000000034800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000023000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x00000006b7ffbe00
all:
finished. total time: 0.026s
Asus RMA was not horrible
I want to close out this thread with some answers about my experience.
I requested an RMA from Asus and sent my device to get checked out or repaired by them. I was fearful that they would notice that I had tampered with the device. I removed the backing to check the battery, unlocking the bootloader and flashing 3rd party ROMs etc.
I ended up re-locking the bootloader since I had fastboot access and tested my luck. I bubble wrapped the devices as Asus said they do not supply padding or any packing material for return of the product.
I was able to check the RMA status page and saw that my tablet arrived in TX at the repair site. They did not update the status page for 3 days with no indication of what caused the issue. Finally the status was changed from < Received > to < Repair Complete >. I had to contact support as they did not supply me with a tracking number. They gave me the tracking details and I got my tablet back yesterday. Asus did not use any of my bubble wrap and the tablet was free floating in a barely reinforced cardboard box.
No explanation was given as to the cause of the failure, I got back the exact same back cover as well as the screen. So either they changed some internal part or flashed some part of the device that I am unaware of.
Anyone else who has a similar issue and needs to get an RMA I would recommend the following.
1. If you still have access to fastboot relock the bootloader. You can check using
Code:
fastboot getvar all
1. Take photos of the device and all physical imperfections so you have some recourse if someone breaks the screen
2. Bubble wrap the device tightly to ensure no damage occurs on the way to the repair site.
3. Tracking & Insurance is a must. If you can prove the screen broke due to USPS or whoever then at least you can get a new tablet with the insurance money. Don't cheap out, get the $250 or $350 worth. The whole cost of shipping should be less than $10 and is worth the piece of mind.
Finally I just updated my tablet to 4.4.3 as it was returned with 4.4.2. Here is what a successful flash looks like, as well as how long each part takes to flash. Compared to the previous flash times one can see the difference.
Code:
[email protected]:/Android/razorg-ktu84l-factory-9f9b9ef2/razorg-ktu84l# ./flash-all.sh
sending 'bootloader' (3911 KB)...
OKAY [ 0.227s]
writing 'bootloader'...
OKAY [ 1.285s]
finished. total time: 1.512s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
sending 'radio' (76038 KB)...
OKAY [ 4.231s]
writing 'radio'...
OKAY [ 2.986s]
finished. total time: 7.217s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: DEB-Z00_2.42.0_1204
Serial Number........: 0*******
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.004s]
sending 'boot' (7050 KB)...
OKAY [ 0.408s]
writing 'boot'...
OKAY [ 0.335s]
sending 'recovery' (7600 KB)...
OKAY [ 0.432s]
writing 'recovery'...
OKAY [ 0.290s]
erasing 'system'...
OKAY [ 1.297s]
sending 'system' (740284 KB)...
OKAY [ 42.003s]
writing 'system'...
OKAY [ 32.278s]
erasing 'userdata'...
OKAY [ 21.615s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 28856791040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7045115
Block groups: 215
Reserved block group size: 1024
Created filesystem with 11/1761280 inodes and 154578/7045115 blocks
sending 'userdata' (139085 KB)...
writing 'userdata'...
OKAY [ 13.308s]
erasing 'cache'...
OKAY [ 0.368s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
sending 'cache' (10984 KB)...
writing 'cache'...
OKAY [ 1.145s]
rebooting...
finished. total time: 113.509s
My overall experience with the RMA process was great I did not have any of the nightmare problems that I read about on other forums.
Good luck to anyone going through this headache.
micemicerabies said:
I want to close out this thread with some answers about my experience.
I requested an RMA from Asus and sent my device to get checked out or repaired by them. I was fearful that they would notice that I had tampered with the device. I removed the backing to check the battery, unlocking the bootloader and flashing 3rd party ROMs etc.
I ended up re-locking the bootloader since I had fastboot access and tested my luck. I bubble wrapped the devices as Asus said they do not supply padding or any packing material for return of the product.
I was able to check the RMA status page and saw that my tablet arrived in TX at the repair site. They did not update the status page for 3 days with no indication of what caused the issue. Finally the status was changed from < Received > to < Repair Complete >. I had to contact support as they did not supply me with a tracking number. They gave me the tracking details and I got my tablet back yesterday. Asus did not use any of my bubble wrap and the tablet was free floating in a barely reinforced cardboard box.
No explanation was given as to the cause of the failure, I got back the exact same back cover as well as the screen. So either they changed some internal part or flashed some part of the device that I am unaware of.
Anyone else who has a similar issue and needs to get an RMA I would recommend the following.
1. If you still have access to fastboot relock the bootloader. You can check using
Code:
fastboot getvar all
1. Take photos of the device and all physical imperfections so you have some recourse if someone breaks the screen
2. Bubble wrap the device tightly to ensure no damage occurs on the way to the repair site.
3. Tracking & Insurance is a must. If you can prove the screen broke due to USPS or whoever then at least you can get a new tablet with the insurance money. Don't cheap out, get the $250 or $350 worth. The whole cost of shipping should be less than $10 and is worth the piece of mind.
Finally I just updated my tablet to 4.4.3 as it was returned with 4.4.2. Here is what a successful flash looks like, as well as how long each part takes to flash. Compared to the previous flash times one can see the difference.
Code:
[email protected]:/Android/razorg-ktu84l-factory-9f9b9ef2/razorg-ktu84l# ./flash-all.sh
sending 'bootloader' (3911 KB)...
OKAY [ 0.227s]
writing 'bootloader'...
OKAY [ 1.285s]
finished. total time: 1.512s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
sending 'radio' (76038 KB)...
OKAY [ 4.231s]
writing 'radio'...
OKAY [ 2.986s]
finished. total time: 7.217s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: DEB-Z00_2.42.0_1204
Serial Number........: 0*******
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.004s]
sending 'boot' (7050 KB)...
OKAY [ 0.408s]
writing 'boot'...
OKAY [ 0.335s]
sending 'recovery' (7600 KB)...
OKAY [ 0.432s]
writing 'recovery'...
OKAY [ 0.290s]
erasing 'system'...
OKAY [ 1.297s]
sending 'system' (740284 KB)...
OKAY [ 42.003s]
writing 'system'...
OKAY [ 32.278s]
erasing 'userdata'...
OKAY [ 21.615s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 28856791040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7045115
Block groups: 215
Reserved block group size: 1024
Created filesystem with 11/1761280 inodes and 154578/7045115 blocks
sending 'userdata' (139085 KB)...
writing 'userdata'...
OKAY [ 13.308s]
erasing 'cache'...
OKAY [ 0.368s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
sending 'cache' (10984 KB)...
writing 'cache'...
OKAY [ 1.145s]
rebooting...
finished. total time: 113.509s
My overall experience with the RMA process was great I did not have any of the nightmare problems that I read about on other forums.
Good luck to anyone going through this headache.
Click to expand...
Click to collapse
Thanks for taking the time to update!
Related
I have a problem with my Galaxy Nexus maguro. I have successful flash ASOP rom but after few days i was no able to boot my device, it always do a bootloop.
I decide to come back to factory and i'm following this insctruction: https:/developers.google.com/android/nexus/images
Process goes fine without errors, but after reboot I continue to see ASOP... I try to flash other roms (Paranoid, FML) but no result... I try to format /system from recovery, but always ASOP (with bootloop).
Please help me!
This is my flashing log:
Code:
C:\yakju-jwr66y-factory-09207065\yakju-jwr66y>flash-all.bat
sending 'bootloader' (2308 KB)...
OKAY [ 0.309s]
writing 'bootloader'...
OKAY [ 7.938s]
finished. total time: 8.253s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.575s]
writing 'radio'...
OKAY [ 4.387s]
finished. total time: 5.966s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'tos.img'
Creating filesystem with parameters:
Size: 14539534336
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3549691
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/887696 inodes and 97200/3549691 blocks
Creating filesystem with parameters:
Size: 452984832
Block size: 4096
Blocks per group: 32768
Inodes per group: 6912
Inode size: 256
Journal blocks: 1728
Label:
Blocks: 110592
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27648 inodes and 3566/110592 blocks
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: 014E281201010006
--------------------------------------------
checking product...
OKAY [ 0.006s]
checking version-bootloader...
OKAY [ 0.008s]
checking version-baseband...
OKAY [ 0.008s]
sending 'boot' (4376 KB)...
OKAY [ 0.570s]
writing 'boot'...
OKAY [ 2.537s]
sending 'recovery' (4924 KB)...
OKAY [ 0.645s]
writing 'recovery'...
OKAY [ 4.508s]
erasing 'system'...
OKAY [ 0.008s]
sending 'system' (474180 KB)...
OKAY [ 60.222s]
writing 'system'...
OKAY [1610.786s]
erasing 'userdata'...
OKAY [ 0.034s]
sending 'userdata' (137559 KB)...
OKAY [ 17.768s]
writing 'userdata'...
OKAY [243.699s]
erasing 'cache'...
OKAY [ 0.009s]
sending 'cache' (8832 KB)...
OKAY [ 1.134s]
writing 'cache'...
OKAY [ 14.461s]
rebooting...
finished. total time: 1956.473s
Press any key to exit...
Have you tried using "Nexus Root Toolkit"? http://www.wugfresh.com/nrt/
Tried flashing this just now:
https://developers.google.com/android/nexus/images#razor
6.0.1 (MOB30D)
via https://dl.google.com/dl/android/aosp/razor-mob30d-factory-15169856.tgz
Terminal result:
Code:
MBP:android-platform-tools $ ./flash-all.sh
sending 'bootloader' (3911 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 1.764s]
finished. total time: 1.893s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'tos.img'
Creating filesystem with parameters:
Size: 13052653568
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3186683
Block groups: 98
Reserved block group size: 783
Created filesystem with 11/798112 inodes and 90699/3186683 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: FLO-04.05
Baseband Version.....: none
Serial Number........: 091aafd9
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7440 KB)...
OKAY [ 0.242s]
writing 'boot'...
OKAY [ 0.707s]
sending 'recovery' (8184 KB)...
OKAY [ 0.268s]
writing 'recovery'...
OKAY [ 0.338s]
erasing 'system'...
OKAY [ 0.175s]
sending 'system' (843529 KB)...
OKAY [ 26.422s]
writing 'system'...
FAILED (remote: Unknown chunk type)
finished. total time: 63.936s
I also verified MD5:
MBP:android-platform-tools $ md5 /Volumes/Data/Downloads/Android/razor-mob30d-factory-15169856.tgz
MD5 (/Volumes/Data/Downloads/Android/razor-mob30d-factory-15169856.tgz) = 701bc5f47b4919294968995a52ab5c76
Click to expand...
Click to collapse
I had previously tried this with a few others such as MOB30D, MMB29V, MMB29Q, MMB29O with same results. Thoughts?
You are using an obsolete version of 'fastboot'. Get another one or try fastboot on Windows.
k23m said:
You are using an obsolete version of 'fastboot'. Get another one or try fastboot on Windows.
Click to expand...
Click to collapse
How can I check fastboot version? I just went through and downloaded what I thought was the latest version. Afterwords, I tried flashall again. I did 2 seconds further down into the install:
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 1.522s]
finished. total time: 1.652s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'tos.img'
Creating filesystem with parameters:
Size: 13052653568
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3186683
Block groups: 98
Reserved block group size: 783
Created filesystem with 11/798112 inodes and 90699/3186683 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: FLO-04.05
Baseband Version.....: none
Serial Number........: 091bbfd9
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7440 KB)...
OKAY [ 0.244s]
writing 'boot'...
OKAY [ 0.468s]
sending 'recovery' (8184 KB)...
OKAY [ 0.268s]
writing 'recovery'...
OKAY [ 0.338s]
erasing 'system'...
OKAY [ 0.175s]
sending 'system' (843529 KB)...
OKAY [ 26.570s]
writing 'system'...
FAILED (remote: Unknown chunk type)
finished. total time: 65.996s
My Nexus 5X was on 7.1.2 and rooted. But I wanted to go to 7.1.1 (for some compatibility).
So, I went on Google APIs and downloaded the 7.1.1 N4F26T, Mar 2017 build and together with Platform Tools I used "flash-all".
But... at a certain point, I get an error and it stopped.
Logs:
C:\Users\*\Desktop\android img\bullhead-n4f26t>flash-all
target reported max download size of 536870912 bytes
sending 'bootloader' (4603 KB)...
OKAY [ 0.173s]
writing 'bootloader'...
OKAY [ 0.135s]
finished. total time: 0.317s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.022s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.359s]
writing 'radio'...
OKAY [ 0.494s]
finished. total time: 1.859s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 27283927040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6661115
Block groups: 204
Reserved block group size: 1024
Created filesystem with 11/1667904 inodes and 148720/6661115 blocks
wiping cache...
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
--------------------------------------------
Bootloader Version...: BHZ11h
Baseband Version.....: M8994F-2.6.36.2.20
Serial Number........: 014702846496c259
--------------------------------------------
checking product...
OKAY [ 0.021s]
checking version-bootloader...
OKAY [ 0.017s]
checking version-baseband...
OKAY [ 0.018s]
sending 'boot' (12013 KB)...
OKAY [ 0.345s]
writing 'boot'...
OKAY [ 0.105s]
sending 'recovery' (16141 KB)...
OKAY [ 0.464s]
writing 'recovery'...
OKAY [ 0.163s]
erasing 'system'...
OKAY [ 0.575s]
sending sparse 'system' 1/6 (520438 KB)...
OKAY [ 13.092s]
writing 'system' 1/6...
OKAY [ 5.904s]
sending sparse 'system' 2/6 (515462 KB)...
OKAY [ 13.286s]
writing 'system' 2/6...
OKAY [ 5.574s]
sending sparse 'system' 3/6 (479562 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 53.984s
Press any key to exit...
Ok... the phone is in bootloop (for more than 20 min). I tried again, the same thing. I installed Nexus Root Toolkit 2.1.6 and I tried with "Flash Stock + Unroot" with the same build N4F26T but I get the same thing.
So, I tried an older build, N4F26O.
This one worked, kind of, some errors in the process but it managed to finish the flashing.
Logs:
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target reported max download size of 536870912 bytes
sending 'bootloader' (4603 KB)...
OKAY [ 0.182s]
writing 'bootloader'...
OKAY [ 0.133s]
finished. total time: 0.320s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.013s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.404s]
writing 'radio'...
OKAY [ 0.491s]
finished. total time: 1.902s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
target reported max download size of 536870912 bytes
erasing 'vendor'...
OKAY [ 0.076s]
sending 'vendor' (25792 KB)...
OKAY [ 0.676s]
writing 'vendor'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 0.958s
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.568s]
sending sparse 'system' 1/6 (520382 KB)...
OKAY [ 12.999s]
writing 'system' 1/6...
OKAY [ 5.097s]
sending sparse 'system' 2/6 (515518 KB)...
OKAY [ 12.752s]
writing 'system' 2/6...
OKAY [ 5.570s]
sending sparse 'system' 3/6 (479542 KB)...
OKAY [ 11.994s]
writing 'system' 3/6...
OKAY [ 4.906s]
sending sparse 'system' 4/6 (514681 KB)...
OKAY [ 13.001s]
writing 'system' 4/6...
OKAY [ 5.170s]
sending sparse 'system' 5/6 (524285 KB)...
OKAY [ 13.645s]
writing 'system' 5/6...
OKAY [ 5.062s]
sending sparse 'system' 6/6 (182573 KB)...
OKAY [ 4.856s]
writing 'system' 6/6...
OKAY [ 1.688s]
finished. total time: 97.350s
Creating filesystem with parameters:
Size: 27283927040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6661115
Block groups: 204
Reserved block group size: 1024
Created filesystem with 11/1667904 inodes and 148720/6661115 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.611s]
sending 'userdata' (138993 KB)...
OKAY [ 3.435s]
writing 'userdata'...
OKAY [ 1.534s]
finished. total time: 5.581s
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.073s]
sending 'cache' (5688 KB)...
OKAY [ 0.231s]
writing 'cache'...
OKAY [ 0.068s]
finished. total time: 0.371s
rebooting...
finished. total time: 0.012s
Still in bootloop after 20 min, so I tried what the NRT said, went into recovery and did a factory reset from there, but same ****. After 20 minutes still in bootloop.
Tried the Soft-Bricked/Bootloop in NRT but it didn't help.
I don't really know what to do....
Send help
Omseik said:
My Nexus 5X was on 7.1.2 and rooted. But I wanted to go to 7.1.1 (for some compatibility).
So, I went on Google APIs and downloaded the 7.1.1 N4F26T, Mar 2017 build and together with Platform Tools I used "flash-all".
But... at a certain point, I get an error and it stopped.
Logs:
C:\Users\*\Desktop\android img\bullhead-n4f26t>flash-all
target reported max download size of 536870912 bytes
sending 'bootloader' (4603 KB)...
OKAY [ 0.173s]
writing 'bootloader'...
OKAY [ 0.135s]
finished. total time: 0.317s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.022s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.359s]
writing 'radio'...
OKAY [ 0.494s]
finished. total time: 1.859s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 27283927040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6661115
Block groups: 204
Reserved block group size: 1024
Created filesystem with 11/1667904 inodes and 148720/6661115 blocks
wiping cache...
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
--------------------------------------------
Bootloader Version...: BHZ11h
Baseband Version.....: M8994F-2.6.36.2.20
Serial Number........: 014702846496c259
--------------------------------------------
checking product...
OKAY [ 0.021s]
checking version-bootloader...
OKAY [ 0.017s]
checking version-baseband...
OKAY [ 0.018s]
sending 'boot' (12013 KB)...
OKAY [ 0.345s]
writing 'boot'...
OKAY [ 0.105s]
sending 'recovery' (16141 KB)...
OKAY [ 0.464s]
writing 'recovery'...
OKAY [ 0.163s]
erasing 'system'...
OKAY [ 0.575s]
sending sparse 'system' 1/6 (520438 KB)...
OKAY [ 13.092s]
writing 'system' 1/6...
OKAY [ 5.904s]
sending sparse 'system' 2/6 (515462 KB)...
OKAY [ 13.286s]
writing 'system' 2/6...
OKAY [ 5.574s]
sending sparse 'system' 3/6 (479562 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 53.984s
Press any key to exit...
Ok... the phone is in bootloop (for more than 20 min). I tried again, the same thing. I installed Nexus Root Toolkit 2.1.6 and I tried with "Flash Stock + Unroot" with the same build N4F26T but I get the same thing.
So, I tried an older build, N4F26O.
This one worked, kind of, some errors in the process but it managed to finish the flashing.
Logs:
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target reported max download size of 536870912 bytes
sending 'bootloader' (4603 KB)...
OKAY [ 0.182s]
writing 'bootloader'...
OKAY [ 0.133s]
finished. total time: 0.320s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.013s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.404s]
writing 'radio'...
OKAY [ 0.491s]
finished. total time: 1.902s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
target reported max download size of 536870912 bytes
erasing 'vendor'...
OKAY [ 0.076s]
sending 'vendor' (25792 KB)...
OKAY [ 0.676s]
writing 'vendor'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 0.958s
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.568s]
sending sparse 'system' 1/6 (520382 KB)...
OKAY [ 12.999s]
writing 'system' 1/6...
OKAY [ 5.097s]
sending sparse 'system' 2/6 (515518 KB)...
OKAY [ 12.752s]
writing 'system' 2/6...
OKAY [ 5.570s]
sending sparse 'system' 3/6 (479542 KB)...
OKAY [ 11.994s]
writing 'system' 3/6...
OKAY [ 4.906s]
sending sparse 'system' 4/6 (514681 KB)...
OKAY [ 13.001s]
writing 'system' 4/6...
OKAY [ 5.170s]
sending sparse 'system' 5/6 (524285 KB)...
OKAY [ 13.645s]
writing 'system' 5/6...
OKAY [ 5.062s]
sending sparse 'system' 6/6 (182573 KB)...
OKAY [ 4.856s]
writing 'system' 6/6...
OKAY [ 1.688s]
finished. total time: 97.350s
Creating filesystem with parameters:
Size: 27283927040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6661115
Block groups: 204
Reserved block group size: 1024
Created filesystem with 11/1667904 inodes and 148720/6661115 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.611s]
sending 'userdata' (138993 KB)...
OKAY [ 3.435s]
writing 'userdata'...
OKAY [ 1.534s]
finished. total time: 5.581s
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.073s]
sending 'cache' (5688 KB)...
OKAY [ 0.231s]
writing 'cache'...
OKAY [ 0.068s]
finished. total time: 0.371s
rebooting...
finished. total time: 0.012s
Still in bootloop after 20 min, so I tried what the NRT said, went into recovery and did a factory reset from there, but same ****. After 20 minutes still in bootloop.
Tried the Soft-Bricked/Bootloop in NRT but it didn't help.
I don't really know what to do....
Send help
Click to expand...
Click to collapse
what happend to you happend to me as weel,
my phone was rooted and bootloader unlocked, so i unroot and lock the bootloader and send the phone do the warranty, after 2 days my phone was already ready to pick up and seems like the motherboard(tranlation from my language, sorry if is not the correct word) was changed to a new one, now the phone is tottaly fine :good:
I think you should send the phone to warranty.
HugoSilva said:
what happend to you happend to me as weel,
my phone was rooted and bootloader unlocked, so i unroot and lock the bootloader and send the phone do the warranty, after 2 days my phone was already ready to pick up and seems like the motherboard(tranlation from my language, sorry if is not the correct word) was changed to a new one, now the phone is tottaly fine :good:
I think you should send the phone to warranty.
Click to expand...
Click to collapse
That's not a solution for me.... I need to make it boot somehow
Omseik said:
That's not a solution for me.... I need to make it boot somehow
Click to expand...
Click to collapse
If this is not a solution for you, sorry cant help you :crying:
Fixed the problem
So... until today, I always used the USB-C cable provided by Google/LG. I used it on the Thunderbolt 3 port on my laptop.
I ordered a new cable, a cheap one, USB-C to USB-A 2.0 and I tried again to flash the device from Soft Bricked with Nexus Root Toolkit and it worked!
This reply is for future people who may have this problem. Looks like Thunderbolt is not always the best move.
I'm trying to flash a factory image. I'm using the guide here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 . I really have no idea what I'm doing wrong... the procedure is so simple, download the factory image and run flash-all.bat It goes, but I get errors. I searched but all I could find was a guy flashing the wrong image. I am using "taimen-opd1.170816.025-factory-907c4030" from https://developers.google.com/android/images. I was on 8.1.1 and want to go back due to multi-touch issues. Below is my log:
target reported max download size of 536870912 bytes
sending 'bootloader' (55680 KB)...
OKAY [ 1.252s]
writing 'bootloader'...
OKAY [ 0.564s]
finished. total time: 104.574s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.358s]
writing 'radio'...
OKAY [ 0.563s]
finished. total time: 1.931s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 56946044928
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13902843
Block groups: 425
Reserved block group size: 1024
Created filesystem with 11/3481600 inodes and 264598/13902843 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: TMZ10n
Baseband Version.....: g8998-00122-1708311414
Serial Number........: 712KPHG1155193
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.004s]
sending 'boot' (40960 KB)...
OKAY [ 0.940s]
writing 'boot'...
OKAY [ 0.376s]
sending sparse 'system' (524284 KB)...
OKAY [ 13.421s]
writing 'system'...
OKAY [ 2.436s]
sending sparse 'system' (524284 KB)...
OKAY [ 13.139s]
writing 'system'...
OKAY [ 2.408s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.975s]
writing 'system'...
OKAY [ 2.416s]
sending sparse 'system' (338968 KB)...
OKAY [ 8.364s]
writing 'system'...
OKAY [ 1.568s]
sending 'vendor' (349428 KB)...
OKAY [ 7.941s]
writing 'vendor'...
OKAY [ 1.607s]
erasing 'userdata'...
OKAY [ 0.591s]
sending 'userdata' (140898 KB)...
OKAY [ 3.031s]
writing 'userdata'...
OKAY [ 1.496s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 72.790s
Press any key to exit...
Well, it always happens this way - I create the thread and the issue is instantly fixed. I was using a usb2 hub hearing it was more stable. Remove the hub and flash and it works... FYI if anyone runs into the same issue.
machx1111 said:
Well, it always happens this way - I create the thread and the issue is instantly fixed. I was using a usb2 hub hearing it was more stable. Remove the hub and flash and it works... FYI if anyone runs into the same issue.
Click to expand...
Click to collapse
Glad you got it fixed.
Adb & flashing rules:
1. Connect phone directly to computer. Don't use USB hub
2. Use the USB cable that came with phone, if possible
3. If it still fails, try a different cable or USB port
If adb recognizes the device, that means your adb environment is setup correctly and adb is working. If flashing still fails at this point, that means your cable or port is bad.
Hey all,
I recently got a Pixel 2 XL, and decided to unlock bootloader, and install Resurrection Remix. All went ok, until I got back a message stating, the stock images were incorrect. So, I decided to just go back to stock, and go back to it later. Well, I got the factory images from Google.
Im using Ubuntu 18.04. Within terminal I used ./flash-all.sh It kept coming back as, "Fastboot too old".
if ! grep -q dtbo.sig $(which fastboot); then
echo "fastboot too old"
exit 1
fi
fastboot flash bootloader bootloader-taimen-tmz12bb.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-taimen-g8998-00202-1802061358.img
fastboot reboot-bootloader
sleep 5
So, I removed the first bit of script, and it starts to download. But, it doesnt appear to download correctly. Still on RR when I restart? Heres the script that comes back:
target reported max download size of 536870912 bytes
sending 'bootloaderb' (36344 KB)...
OKAY [ 1.025s]
writing 'bootloaderb'...
OKAY [ 0.374s]
finished. total time: 1.399s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.201s
target reported max download size of 536870912 bytes
sending 'radiob' (60412 KB)...
OKAY [ 1.768s]
writing 'radiob'...
OKAY [ 0.588s]
finished. total time: 2.356s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.201s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 56946044928
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13902843
Block groups: 425
Reserved block group size: 1024
Created filesystem with 11/3481600 inodes and 264598/13902843 blocks
--------------------------------------------
Bootloader Version...: TMZ12bb
Baseband Version.....: g8998-00202-1802061358
Serial Number........: 712KPAE1212112
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.000s]
sending 'bootb' (40960 KB)...
OKAY [ 1.315s]
writing 'bootb'...
FAILED (remote: No such partition.)
finished. total time: 1.320s
I have never really run into this on a Google device. If anyone out there has any insight for me, id really appreciate it. Ill buy a beer to anyone who can help me out.
You could've just ignored that. It doesn't interfere with the device. Just reflash how you normally do then if you get that message again just flash the vendor image.
Sent from my SM-G965U using Tapatalk
Well, after much research, and experimenting, I found that using the oldest image, from Sept 2017, fixed my issue. This whole time I was using the newest April image. Defiantly different with the a & b partition. That threw me off. But, all is well in Pixel land now.