I've picked up a Nexus 7 cheap because it was stuck on the Google logo, apparently it wanted to do an update and it seems it wasn't successful and is now stuck at the Google screen
I got it to try and attempt to repair it but don't seem to be having much luck with it.
When I try flashing factory images using the flash-all.bat file I get
Code:
c:\adb>flash-all.bat
sending 'bootloader' (3915 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: -0.000s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 28521246720
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6963195
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1741488 inodes and 153337/6963195 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.04
Baseband Version.....: none
Serial Number........: 07be4417
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
FAILED
Device version-bootloader is 'FLO-04.04'.
Update requires 'FLO-04.08'.
finished. total time: 0.039s
Press any key to exit...
#
Trying to unlock the bootloader I get
Code:
PS C:\adb> fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
And it just sits there for ages and doesn't do anything.
I'm a bit stumped as to what more I can do?
Did you check the SHA-256 checksum?
No, not directly but I know when wugfresh downloads an image it does a hash check so I'm pretty sure the files are fine.
It is by the looks of it having troubles handling the erase commands so I'm guessing it's a problem with the emmc.
I've tried 2 different computers with different usb ports also.
Try sideload ota from recovery if this is working
I'd love to but I can't boot to recovery, just sits there doing nothing.
Related
Hi i don't know if this board is correct but i have serious problem to flash official factory image.
Problem: reboot galaxy nexus. when lockscreen is loaded phone reboot alone.
1) download Factory Images "yakju" for Galaxy Nexus "maguro"
2) reboot device in download
3) ./fastboot oem unlock and select YES
2) sudo su, i use Ubuntu
3) -/flash-all.sh
sending 'bootloader' (3911 KB)...
OKAY [ 0.496s]
writing 'bootloader'...
FAILED (remote: Write Fail)
finished. total time: 0.527s
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...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: 014E1EC50300D006
--------------------------------------------
checking product...
FAILED
Device product is 'tuna'.
Update requires 'flo'.
finished. total time: 0.035s
I trie line for line..
1) ./fastboot flash bootloader bootloader-flo-flo-04.04.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.495s]
writing 'bootloader'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.502s
I don't understand beacuse bootloader is locked again
I tryed in recovery and i want delete all user data.
1) wipe data/factory reset ----YES delete all user data.....Data wipe complete
reboot
I see old my lockscreen again... it's strange.
Reboot in fastboot mode.
1) ./fastboot oem unlock. Select Yes and i see Loct State- Unlocked
copy flash-all.sh command line
2) ./fastboot flash bootloader bootloader-flo-flo-04.04.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.495s]
writing 'bootloader'...
FAILED (remote: Write Fail)
finished. total time: 0.527s
3) try only update rom ./fastboot -w update image-razor-lrx21p.zip
./fastboot -w update image-razor-lrx21p.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.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........: 014E1EC50300D006
--------------------------------------------
checking product...
FAILED
Device product is 'tuna'.
Update requires 'flo'.
I don't understand... I have a European Galaxy Nexus... yakju.
is it hardware problem?
gsources75 said:
Hi i don't know if this board is correct but i have serious problem to flash official factory image.
Problem: reboot galaxy nexus. when lockscreen is loaded phone reboot alone.
1) download Factory Images "yakju" for Galaxy Nexus "maguro"
2) reboot device in download
3) ./fastboot oem unlock and select YES
2) sudo su, i use Ubuntu
3) -/flash-all.sh
sending 'bootloader' (3911 KB)...
OKAY [ 0.496s]
writing 'bootloader'...
FAILED (remote: Write Fail)
finished. total time: 0.527s
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...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: 014E1EC50300D006
--------------------------------------------
checking product...
FAILED
Device product is 'tuna'.
Update requires 'flo'.
finished. total time: 0.035s
I trie line for line..
1) ./fastboot flash bootloader bootloader-flo-flo-04.04.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.495s]
writing 'bootloader'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.502s
I don't understand beacuse bootloader is locked again
I tryed in recovery and i want delete all user data.
1) wipe data/factory reset ----YES delete all user data.....Data wipe complete
reboot
I see old my lockscreen again... it's strange.
Reboot in fastboot mode.
1) ./fastboot oem unlock. Select Yes and i see Loct State- Unlocked
copy flash-all.sh command line
2) ./fastboot flash bootloader bootloader-flo-flo-04.04.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.495s]
writing 'bootloader'...
FAILED (remote: Write Fail)
finished. total time: 0.527s
3) try only update rom ./fastboot -w update image-razor-lrx21p.zip
./fastboot -w update image-razor-lrx21p.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.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........: 014E1EC50300D006
--------------------------------------------
checking product...
FAILED
Device product is 'tuna'.
Update requires 'flo'.
I don't understand... I have a European Galaxy Nexus... yakju.
is it hardware problem?
Click to expand...
Click to collapse
Your flashing the wrong images man , flo is nexus 7 tablet , as is razor . you must have downloaded the wrong files .
I tryed:
fastboot format system
fastboot format userdata
fastboot fomat cache
and.. i see old lockscreen, smartphone reboot and reboot again
Dude
Device product is 'tuna'.
Update requires 'flo'.
Click to expand...
Click to collapse
Do you have a Tuna or do you have a Flo?
As Bsmitty said: download the proper image.
Yeah, download "Nexus Root Toolkit" - http://www.wugfresh.com/nrt/ it will automatically download and flash the correct image.
Hi there
I got the same problem in my old gnex, there is no fix for this, its a hardware damage.
Yea you just flashed wrong img... You need Tuna not Flo
jhonnyx said:
Dude
Do you have a Tuna or do you have a Flo?
As Bsmitty said: download the proper image.
Click to expand...
Click to collapse
He said he has a European galaxy nexus. Last words from his op.
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
Hello,
I have a HTC 10 with stock rom and locked bootloader, S-On. I stuck in a boot loop, no recovery nor download mode. Just bootloader mode...
I tried the commands. You can find the results below.
C:\adb>fastboot devices
FA69LBN01701 fastboot
C:\adb>fastboot format cache
Creating filesystem with parameters:
Size: 234881024
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 57344
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/14336 inodes and 1961/57344 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: Not allow when s-on)
finished. total time: 0.046s
C:\adb>fastboot format userdata
Creating filesystem with parameters:
Size: 26273120256
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6414336
Block groups: 196
Reserved block group size: 1024
Created filesystem with 11/1605632 inodes and 144812/6414336 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: Not allow when s-on)
finished. total time: 0.014s
C:\adb>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.012s
C:\adb>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.027s
C:\adb>fastboot flashing unlock
...
FAILED (remote: unknown command)
finished. total time: 0.044s
C:\adb>fastboot flash unlock
unknown partition 'unlock'
error: cannot determine image filename for 'unlock'
C:\adb>fastboot oem unlocking
...
FAILED (remote: unknown command)
finished. total time: 0.039s
Obviously, I need the S-OFF.
Anyone can help with me?
Thanks in advance.
Tried the solutions in this thread??
https://forum.xda-developers.com/htc-10/help/enter-download-mode-t3406529/page2
JohnSoong said:
Tried the solutions in this thread??
https://forum.xda-developers.com/htc-10/help/enter-download-mode-t3406529/page2
Click to expand...
Click to collapse
Yes and unfortunately, still in the boot loop when I select "boot to download&recovery" mode
Edit: fastboot rebootRUU also results in boot lopp
Hello,
I made a backup of my RR ROM by followmsi in my usb stick, after give a short try to AOSP OREO I decide go back to my old rom. So I reboot into TWRP (latest version) in order to restore my backup that it´s on my usb stick. After the restore I reboot to system but I never go into system, it get stuck on RR logo, so I go back to TWRP and now it asks for a password to decrypt data and I NEVER USE A PASSWORD/PATRON
I try to format every partition but TWRP is always unable to mount those partitions. Now I try to make a new install of the rom with no results.
So now my Pixel C is like a rock and I can´t get it boot. Anyone can help me bringing it back to life? Doesn´t matter if I must restore it to fully stock, this is the very last time that I try roms or similar in Pixel, I´m done and probably I sell it, I´m just tired and it´s insanely messy for me.
I never never have this kind of problems that I´m facing with Pixel C with any of my android phones/tablets, this is my fault probably at 100% just I can´t understand anything.....
Thanks in advance.
I try to flash latest Oreo factory image and latest Nougat factory image with no good results. Here is the log:
target reported max download size of 268435456 bytes
sending 'bootloader' (16384 KB)...
OKAY [ 0.420s]
writing 'bootloader'...
FAILED (remote: unsupported command)
finished. total time: 0.424s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
target reported max download size of 268435456 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'
Creating filesystem with parameters:
Size: 26557284352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6483712
Block groups: 198
Reserved block group size: 1024
Created filesystem with 11/1622016 inodes and 145840/6483712 blocks
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
--------------------------------------------
Bootloader Version...: Google_Smaug.7132.295.0
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'Google_Smaug.7132.295.0'.
Update requires 'Google_Smaug.7900.67.0'.
finished. total time: 0.018s
Press any key to exit...
I also try to flash manually the bootloader with no results. In adition I try to lock and unlock the device to get it wiped also with no results.
Any ideas?? I´m totally desperated.
Thanks in advance.
I think you need to find the original firmware with the bootloader version the same as you have now(Device version-bootloader is 'Google_Smaug.7132.295.0'.) and install it. After that, I think it will be possible to update on OTA for a newer one.
Istvan_86 said:
I try to flash latest Oreo factory image and latest Nougat factory image with no good results. Here is the log:
target reported max download size of 268435456 bytes
sending 'bootloader' (16384 KB)...
OKAY [ 0.420s]
writing 'bootloader'...
FAILED (remote: unsupported command)
finished. total time: 0.424s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
target reported max download size of 268435456 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'
Creating filesystem with parameters:
Size: 26557284352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6483712
Block groups: 198
Reserved block group size: 1024
Created filesystem with 11/1622016 inodes and 145840/6483712 blocks
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
--------------------------------------------
Bootloader Version...: Google_Smaug.7132.295.0
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'Google_Smaug.7132.295.0'.
Update requires 'Google_Smaug.7900.67.0'.
finished. total time: 0.018s
Press any key to exit...
I also try to flash manually the bootloader with no results. In adition I try to lock and unlock the device to get it wiped also with no results.
Any ideas?? I´m totally desperated.
Thanks in advance.
Click to expand...
Click to collapse
My problem is that my Nexus 7 will not start anymore. It will still display a startup screen, but then it will not continue. Also, I'm still in the boot loader, but can not flash the Recovery TWRP, because apparently the device is not recognized. Also in the Recovery TWRP I can not start, it will then hang synonymous.
Had actually installed CyanogenMod 14.1 and ran for some time with it
What options do I have left?
JuergenRaab said:
My problem is that my Nexus 7 will not start anymore. It will still display a startup screen, but then it will not continue. Also, I'm still in the boot loader, but can not flash the Recovery TWRP, because apparently the device is not recognized. Also in the Recovery TWRP I can not start, it will then hang synonymous.
Had actually installed CyanogenMod 14.1 and ran for some time with it
What options do I have left?
Click to expand...
Click to collapse
I dont know if it work for you. I'm stuck in bootloader menu when i try to resize the partition... it still does not work for me
but try Nexus Root Toolkit 2.1.9
it work for me. whenever i screw up, i put stock back
flash write failure
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target didn't report max-download-size
sending 'bootloader' (3915 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.780s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
target didn't report max-download-size
sending 'boot' (7422 KB)...
OKAY [ 0.239s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.059s
target didn't report max-download-size
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.017s
target didn't report max-download-size
sending 'recovery' (8166 KB)...
OKAY [ 0.264s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.278s
target didn't report max-download-size
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.017s
Creating filesystem with parameters:
Size: 28521246720
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6963195
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1741488 inodes and 153337/6963195 blocks
target didn't report max-download-size
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.015s
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
target didn't report max-download-size
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.014s
rebooting...
finished. total time: 0.006s