Hardware problem? - Nexus 10 Q&A, Help & Troubleshooting

Hi there
I've got an old Nexus 10 that recently got stuck in a bootloop, so I booted into recovery and did a factory reset. After a few boots and updates everything seemed ok, but then it just died and went into a bootloop again.
I've flashed TWRP recovery, but no partitions are mounted or mountable and attempts to repair file system make the screen go squiggly (corrupted/interference) and then the tablet reboots into bootloader.
Is this likely to be a hardware issue or is there more I can try?
Slainte
mmidders
P.S. also tried flashing the stock ROM using flash-all.sh, output appended:
erasing 'boot'...
OKAY [ 0.022s]
finished. total time: 0.023s
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.097s]
finished. total time: 0.097s
erasing 'recovery'...
OKAY [ 0.029s]
finished. total time: 0.029s
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.150s]
finished. total time: 0.150s
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 0.373s]
finished. total time: 0.373s
target didn't report max-download-size
sending 'bootloader' (1280 KB)...
OKAY [ 0.192s]
writing 'bootloader'...
OKAY [ 0.115s]
finished. total time: 0.307s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.454s
< waiting for any device >
extracting android-info.txt (0 MB)...
extracting boot.img (4 MB)...
target didn't report max-download-size
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (5 MB)...
archive does not contain 'recovery.sig'
extracting system.img (641 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
archive does not contain 'vendor.img'
wiping userdata...
mke2fs 1.44.1 (24-Mar-2018)
/tmp/TemporaryFile-poiJRI: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata

Update:
I updated adb and fastboot and ran the flash-all.sh script again with the following output (now waiting for first boot):
Erasing 'boot' OKAY [ 0.022s]
Finished. Total time: 0.025s
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.093s]
Finished. Total time: 0.095s
Erasing 'recovery' OKAY [ 0.025s]
Finished. Total time: 0.027s
******** Did you mean to fastboot format this ext4 partition?
Erasing 'system' OKAY [ 0.150s]
Finished. Total time: 0.153s
******** Did you mean to fastboot format this ext4 partition?
Erasing 'userdata' OKAY [ 0.372s]
Finished. Total time: 0.375s
Sending 'bootloader' (1280 KB) OKAY [ 0.194s]
Writing 'bootloader' OKAY [ 0.132s]
Finished. Total time: 0.330s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.453s
< waiting for any device >
--------------------------------------------
Bootloader Version...: MANTAMF01
Baseband Version.....: no modem
Serial Number........: R32F200S5XR
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.001s]
extracting boot.img (4 MB) to disk... took 0.018s
archive does not contain 'boot.sig'
Sending 'boot' (4966 KB) OKAY [ 0.745s]
Writing 'boot' OKAY [ 0.118s]
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (5 MB) to disk... took 0.028s
archive does not contain 'recovery.sig'
Sending 'recovery' (5532 KB) OKAY [ 0.851s]
Writing 'recovery' OKAY [ 0.121s]
archive does not contain 'vbmeta.img'
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'super_empty.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting system.img (641 MB) to disk... took 6.544s
archive does not contain 'system.sig'
Sending 'system' (657130 KB) OKAY [ 96.291s]
Writing 'system' OKAY [ 15.845s]
archive does not contain 'system_ext.img'
archive does not contain 'vendor.img'
Erasing 'userdata' OKAY [ 0.371s]
mke2fs 1.44.1 (24-Mar-2018)
/tmp/TemporaryFile-3eTxBH: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata

Related

samsung I9020A writing 'system'...FAILED (remote: Write Fail)

sending 'bootloader' (1536 KB)...
OKAY [ 0.188s]
writing 'bootloader'...
OKAY [ 0.391s]
finished. total time: 0.578s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.531s]
writing 'radio'...
OKAY [ 1.969s]
finished. total time: 3.500s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 3831EC3B76D900EC
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (3964 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.609s]
sending 'recovery' (4308 KB)...
OKAY [ 0.547s]
writing 'recovery'...
OKAY [ 0.656s]
sending 'system' (333431 KB)...
OKAY [ 41.797s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 44.156s
Press any key to exit...
harry_01 said:
sending 'bootloader' (1536 KB)...
OKAY [ 0.188s]
writing 'bootloader'...
OKAY [ 0.391s]
finished. total time: 0.578s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.531s]
writing 'radio'...
OKAY [ 1.969s]
finished. total time: 3.500s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 3831EC3B76D900EC
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (3964 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.609s]
sending 'recovery' (4308 KB)...
OKAY [ 0.547s]
writing 'recovery'...
OKAY [ 0.656s]
sending 'system' (333431 KB)...
OKAY [ 41.797s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 44.156s
Press any key to exit...
Click to expand...
Click to collapse
did you encrypt your phone? if yes, boot to factory recovery and format the phone from there. then try again.
Nexus HAL said:
did you encrypt your phone? if yes, boot to factory recovery and format the phone from there. then try again.
Click to expand...
Click to collapse
i try but same also i repair my bootloader Jtag
then try to flash when come write system file wait long time but not finish
then try odin also same problem
show write system file 3 green line show then nothing 30 min same no error not complete
now tell me what i do

Error flashing stock ROM

Hi, I used WUG's toolkit to flash the rom and came up with this error:
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.034s]
finished. total time: 0.035s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.134s]
finished. total time: 0.135s
erasing 'recovery'...
OKAY [ 0.035s]
finished. total time: 0.036s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.180s]
finished. total time: 0.181s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 14.477s]
finished. total time: 14.478s
sending 'bootloader' (2100 KB)...
OKAY [ 0.273s]
writing 'bootloader'...
OKAY [ 1.217s]
finished. total time: 1.492s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No such device or address))
error: out of memory
Need advice as my tablet is inoperable.:/
Try running the toolkit as administrator or use flash-all script of the factory image by running it through Administrator Command Prompt.

[Q] Problem in downgrade to 4.4.4

dear
i have Lg Nexus4 want to downgrade from lollipop to kitkat
i did download 4.4.4 file occam-ktu84p
after i connected my phone in fastboot and run the flash-all.bat
after loading some files it failed
for me i dont want to keep backup so i need flash-W so i keep bootloader locked
sending 'bootloader' (2203 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
FAILED (remote: not supported in locked device)
finished. total time: 0.109s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.605s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 1.621s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 748585716 bytes
error: update package missing system.img
Press any key to exit...
i show also image of file i used
almoudamer said:
dear
i have Lg Nexus4 want to downgrade from lollipop to kitkat
i did download 4.4.4 file occam-ktu84p
after i connected my phone in fastboot and run the flash-all.bat
after loading some files it failed
for me i dont want to keep backup so i need flash-W so i keep bootloader locked
sending 'bootloader' (2203 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
FAILED (remote: not supported in locked device)
finished. total time: 0.109s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.605s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 1.621s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 748585716 bytes
error: update package missing system.img
Press any key to exit...
i show also image of file i used
Click to expand...
Click to collapse
You need unlocked bootloader to flash image.
Sent from my Nexus 4 using XDA Free mobile app
Hello
thxfor ur quick reply
i did unlock bootloader and tested again ,but still facing this same problem as update package missing system.img even it is available in zip file if we open as i showed in before picture
sending 'bootloader' (2203 KB)...
OKAY [ 0.078s]
writing 'bootloader'...
OKAY [ 0.296s]
finished. total time: 0.374s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.641s]
writing 'radio'...
OKAY [ 2.605s]
finished. total time: 4.262s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 748585716 bytes
error: update package missing system.img
Press any key to exit...
br

[Help] Bootloop when trying to flash stock 5.1.1

Hello everyone
I've downloaded the factory image of Android 5.1.1 for nexus 4 (latest build) here : https://developers.google.com/android/nexus/images
I tried to flash it using
Code:
./flash-all.sh
in fastboot mode but then I only have the Lollipop loop going around again and again....
Here is the whole return in the Shell
Code:
./flash-all.sh
sending 'bootloader' (2264 KB)...
OKAY [ 0.074s]
writing 'bootloader'...
OKAY [ 0.296s]
finished. total time: 0.370s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 1.437s]
writing 'radio'...
OKAY [ 2.409s]
finished. total time: 3.846s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30f
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.04
Serial Number........: 016d97ae92486357
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6348 KB)...
OKAY [ 0.216s]
writing 'boot'...
OKAY [ 0.340s]
sending 'recovery' (6892 KB)...
OKAY [ 0.223s]
writing 'recovery'...
OKAY [ 0.381s]
sending 'system' (809641 KB)...
OKAY [ 26.279s]
writing 'system'...
OKAY [ 46.357s]
erasing 'userdata'...
OKAY [ 0.478s]
erasing 'cache'...
OKAY [ 0.023s]
rebooting...
finished. total time: 74.312s
I also tried to flash boot, recovery and system manually after seing the three lines
Code:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
But everything was the same...
Thank you in advance for your help and advice !
It seemed to wake up after 15 minutes... Never had to wait so long though

Forgot fastboot set_active a command, (and other errors) now phone is bricked.amidun?

Here is the sequence of commands:
C:\Users\blah\Desktop\platform-tools>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
PM1LHMA7blahblah unauthorized
C:\Users\blah\Desktop\platform-tools>adb devices
List of devices attached
PM1LHMA7blahblah device
C:\Users\blah\Desktop\platform-tools>adb reboot bootloader
C:\Users\blah\Desktop\platform-tools>fastboot devices
PM1LHMA7blahblah fastboot
C:\Users\blah\Desktop\platform-tools>fastboot getvar current-slot
current-slot: _a
Finished. Total time: 0.001s
C:\Users\blah\Desktop\platform-tools>fastboot flash vendor_a vendor-QQ1A.200105.088.img # OOPS i should have put b so i try to fix it in the next command
Sending 'vendor_a' (392296 KB) OKAY [ 9.211s]
Writing 'vendor_a' OKAY [ 2.446s]
Finished. Total time: 11.667s
C:\Users\blah\Desktop\platform-tools>fastboot flash vendor_b vendor-QQ1A.200105.088.img
Sending 'vendor_b' (392296 KB) OKAY [ 9.215s]
Writing 'vendor_b' OKAY [ 2.439s]
Finished. Total time: 11.661s
C:\Users\blah\Desktop\platform-tools>fastboot erase system_b
Erasing 'system_b' OKAY [104.577s]
Finished. Total time: 104.580s
C:\Users\blah\Desktop\platform-tools>fastboot flash system_b system.img
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/6 (523151 KB) OKAY [ 12.365s]
Writing 'system_b' OKAY [ 3.943s]
Sending sparse 'system_b' 2/6 (520769 KB) OKAY [ 12.262s]
Writing 'system_b' OKAY [ 3.271s]
Sending sparse 'system_b' 3/6 (523599 KB) OKAY [ 12.327s]
Writing 'system_b' OKAY [ 3.311s]
Sending sparse 'system_b' 4/6 (522306 KB) OKAY [ 12.262s]
Writing 'system_b' OKAY [ 3.563s]
Sending sparse 'system_b' 5/6 (503327 KB) OKAY [ 11.967s]
Writing 'system_b' OKAY [ 8.774s]
Sending sparse 'system_b' 6/6 (42300 KB) OKAY [ 1.068s]
Writing 'system_b' OKAY [ 0.311s]
Finished. Total time: 87.248s
C:\Users\blah\Desktop\platform-tools>fastboot flash boot_b unsigned-new.img
fastboot: error: Couldn't parse partition size '0x'.
C:\Users\blah\Desktop\platform-tools>fastboot flash boot_a unsigned-new.img
fastboot: error: Couldn't parse partition size '0x'.
C:\Users\blah\Desktop\platform-tools>fastboot flash:raw boot_b unsigned-new.img
Sending 'boot_b' (23864 KB) OKAY [ 0.634s]
Writing 'boot_b' OKAY [ 0.298s]
Finished. Total time: 0.958s
##FORGET TO USE COMMAND fastboot set_active a
C:\Users\blah\Desktop\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 54.443s]
mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 26768215 4k blocks and 6692864 inodes
Filesystem UUID: blah
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (544 KB) OKAY [ 0.100s]
Writing 'userdata' OKAY [ 0.018s]
Finished. Total time: 54.827s
Now when i restart the phone it just stays on the screen with the essential logo and powered by android at the bottom; never gets to spinning circles. When I restart i can pause it from booting because the bootloader is unlocked, but adb cant find it because to do that i have to give it debug permissions, but no OS to boot to so i cant do that. Did i brick my phone?
If you can still get into the bootloader, its fixable. Just reflash stock
vsn4 said:
If you can still get into the bootloader, its fixable. Just reflash stock
Click to expand...
Click to collapse
When I reboot, it says press power to pause (the screen where it says g.co/ABH), but then eventually proceeds to boot by itself after a few seconds.
noideawtf said:
When I reboot, it says press power to pause (the screen where it says g.co/ABH), but then eventually proceeds to boot by itself after a few seconds.
Click to expand...
Click to collapse
It boots back into the screen with the logo and phrase powered by android and sits there. After it dissipated its power all night doing that, I was able to get the bootloader screen to appear (The word start in big green letters) this morning, but i selected start and now that screen refuses to show up again, so ill try draining it again i guess?
I drained it of power and as soon as i plugged it into a charger it turned on by itself and went into the bootloader unlike it was doing before. Was able to issue the command I missed earlier and now it loads right up.

Categories

Resources