A month or so ago my Nexus 7 (2012) started rebooting itself after a minute or so of turning on - I think this may have been during OTA upgrade from JWR66Y to new release. I tried to fix this by clearing app data and booting into CWM recovery and deleting cache and dalvik cache but the problem persisted. So I decided to reset the Nexus 7 back to factory image and have tried every means of doing so but every time I keep getting back to my original data and the app crashes and reboot continues. I have never had any issues connecting to the device on USB and ADB so this is not a driver issue. Things I have tried:
* Hard reset on phone from recovery (plus endless deleting of cache and dalvik)
* Hard reset using Wugfresh toolkit (plus near every other tool on there)
* Hard refresh from recovery mode
* Hard refresh using ADB and deleting user data etc.
* Flash recovery from ADB (also using Wugfresh as per above)
* ADB sideload from recovery of factory images, bootloaders and other ROM's
* Lock/unlock/root/unroot - using ADB commands as well as Wugfresh and other toolkits
* Delete data, system, cache
It seems like the Nexus 7 going into read only mode? Erasing /data and everything else in recovery has no effect and also when trying to overwrite the bootloader I get "writing 'bootloader'... FAILED (remote: (InvalidState))" using Wugfresh toolkit as per below. The device is still running JWR66Y.
I'm totally stuck now as to how I get my Nexus 7 back again! I have seen other people having issues with the JWR66Y bootloader (http://forum.xda-developers.com/showthread.php?t=1907796) but have tried all the workarounds and can't seem to find a way to overwrite the bootloader...
*** Trying with ADB manually ***
C:\android-sdk\platform-tools>adb devices
List of devices attached
4df17c816ec76f25 device
C:\android-sdk\platform-tools>adb devices
List of devices attached
015d165c520bf80f device
C:\android-sdk\platform-tools>adb reboot-bootloader
C:\android-sdk\platform-tools>fastboot devices
015d165c520bf80f fastboot
C:\android-sdk\platform-tools>fastboot oem unlock
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.016s]
finished. total time: 0.031s
C:\android-sdk\platform-tools>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.
img
sending 'bootloader' (2100 KB)...
OKAY [ 0.344s]
writing 'bootloader'...
OKAY [ 0.594s]
finished. total time: 0.938s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot -w update image-nakasi-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d165c520bf80f
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.031s]
sending 'boot' (4992 KB)...
OKAY [ 0.781s]
writing 'boot'...
OKAY [ 0.172s]
sending 'recovery' (5532 KB)...
OKAY [ 0.844s]
writing 'recovery'...
OKAY [ 0.188s]
erasing 'system'...
OKAY [ 0.016s]
sending 'system' (625382 KB)...
OKAY [ 95.203s]
writing 'system'...
OKAY [ 27.500s]
erasing 'userdata'...
OKAY [ 0.031s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 38.453s]
erasing 'cache'...
OKAY [ 0.016s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 2.203s]
rebooting...
finished. total time: 165.625s
*** Now using Wugfresh tool ***
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.031s]
finished. total time: 0.031s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.031s]
finished. total time: 0.031s
sending 'bootloader' (3911 KB)...
OKAY [ 0.609s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.828s
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d165c520bf80f
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.031s]
sending 'boot' (4992 KB)...
OKAY [ 0.781s]
writing 'boot'...
OKAY [ 0.172s]
sending 'recovery' (5532 KB)...
OKAY [ 0.844s]
writing 'recovery'...
OKAY [ 0.188s]
erasing 'system'...
OKAY [ 0.016s]
sending 'system' (625382 KB)...
OKAY [ 96.078s]
writing 'system'...
OKAY [ 27.484s]
erasing 'userdata'...
OKAY [ 0.031s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [148.516s]
erasing 'cache'...
OKAY [ 0.016s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 3.266s]
rebooting...
finished. total time: 1197.719s
Groundhog Day
Hi there
I too have the same problem.
Whatever I do it is Groundhog Day... Seems to be Read-Only.
I have given up & consider it to be a hardware issue. Ordered another motherboard for mine.
barrymcsorley said:
A month or so ago my Nexus 7 (2012) started rebooting itself after a minute or so of turning on - I think this may have been during OTA upgrade from JWR66Y to new release. I tried to fix this by clearing app data and booting into CWM recovery and deleting cache and dalvik cache but the problem persisted. So I decided to reset the Nexus 7 back to factory image and have tried every means of doing so but every time I keep getting back to my original data and the app crashes and reboot continues. I have never had any issues connecting to the device on USB and ADB so this is not a driver issue. Things I have tried:
* Hard reset on phone from recovery (plus endless deleting of cache and dalvik)
* Hard reset using Wugfresh toolkit (plus near every other tool on there)
* Hard refresh from recovery mode
* Hard refresh using ADB and deleting user data etc.
* Flash recovery from ADB (also using Wugfresh as per above)
* ADB sideload from recovery of factory images, bootloaders and other ROM's
* Lock/unlock/root/unroot - using ADB commands as well as Wugfresh and other toolkits
* Delete data, system, cache
It seems like the Nexus 7 going into read only mode? Erasing /data and everything else in recovery has no effect and also when trying to overwrite the bootloader I get "writing 'bootloader'... FAILED (remote: (InvalidState))" using Wugfresh toolkit as per below. The device is still running JWR66Y.
I'm totally stuck now as to how I get my Nexus 7 back again! I have seen other people having issues with the JWR66Y bootloader (http://forum.xda-developers.com/showthread.php?t=1907796) but have tried all the workarounds and can't seem to find a way to overwrite the bootloader...
*** Trying with ADB manually ***
C:\android-sdk\platform-tools>adb devices
List of devices attached
4df17c816ec76f25 device
C:\android-sdk\platform-tools>adb devices
List of devices attached
015d165c520bf80f device
C:\android-sdk\platform-tools>adb reboot-bootloader
C:\android-sdk\platform-tools>fastboot devices
015d165c520bf80f fastboot
C:\android-sdk\platform-tools>fastboot oem unlock
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.016s]
finished. total time: 0.031s
C:\android-sdk\platform-tools>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.
img
sending 'bootloader' (2100 KB)...
OKAY [ 0.344s]
writing 'bootloader'...
OKAY [ 0.594s]
finished. total time: 0.938s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot -w update image-nakasi-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d165c520bf80f
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.031s]
sending 'boot' (4992 KB)...
OKAY [ 0.781s]
writing 'boot'...
OKAY [ 0.172s]
sending 'recovery' (5532 KB)...
OKAY [ 0.844s]
writing 'recovery'...
OKAY [ 0.188s]
erasing 'system'...
OKAY [ 0.016s]
sending 'system' (625382 KB)...
OKAY [ 95.203s]
writing 'system'...
OKAY [ 27.500s]
erasing 'userdata'...
OKAY [ 0.031s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 38.453s]
erasing 'cache'...
OKAY [ 0.016s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 2.203s]
rebooting...
finished. total time: 165.625s
*** Now using Wugfresh tool ***
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.031s]
finished. total time: 0.031s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.031s]
finished. total time: 0.031s
sending 'bootloader' (3911 KB)...
OKAY [ 0.609s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.828s
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d165c520bf80f
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.031s]
sending 'boot' (4992 KB)...
OKAY [ 0.781s]
writing 'boot'...
OKAY [ 0.172s]
sending 'recovery' (5532 KB)...
OKAY [ 0.844s]
writing 'recovery'...
OKAY [ 0.188s]
erasing 'system'...
OKAY [ 0.016s]
sending 'system' (625382 KB)...
OKAY [ 96.078s]
writing 'system'...
OKAY [ 27.484s]
erasing 'userdata'...
OKAY [ 0.031s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [148.516s]
erasing 'cache'...
OKAY [ 0.016s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 3.266s]
rebooting...
finished. total time: 1197.719s
Click to expand...
Click to collapse
Glad to hear I'm not the only one in this loop! I'll be gutted if it turns out to be hardware issue. Just been on ifixit.com to see how difficult it is to replace motherboard - maybe this will be opportunity to upgrade to the new Nexus 7 2013 version.....
pwllheli said:
Hi there
I too have the same problem.
Whatever I do it is Groundhog Day... Seems to be Read-Only.
I have given up & consider it to be a hardware issue. Ordered another motherboard for mine.
Click to expand...
Click to collapse
Any progress here? Same issue for me. Have searched everywhere for a fix and can't find one!
Sent from my iPhone using Tapatalk
No joy for me. Think I've read every forum and tried every single possible command or procedure and after all of them I end up rebooting back into the same login screen and crashing apps. The fact I can't wipe the data with any command makes me think it's pretty much a hardware issue. Now looking to see how feasible it is to swap out CPU/motherboard......
mattsolberg said:
Any progress here? Same issue for me. Have searched everywhere for a fix and can't find one!
Click to expand...
Click to collapse
Very frustrating. I'd even contacted Google support as a last ditch effort but as soon as they learned my 1 year warranty had expired they dropped me and sent me Asus' contact info.
I understand warranties but I'm still rather annoyed.
Sent from my iPhone using Tapatalk
Yeah I tried Google support too but no joy as warranty long gone. As you say can accept that but annoyed that I now have a £200 paperweight that I can spend another £50 on in the hope of fixing but no guarantee.....
Nexus 7 2012 help
It is not a hardware issue as I can use fastboot to write correct boot loader from jrrv version and it says success. I can't wipe system cache or data. It says its erasing or if I use format command it says its formatting but when I boot up the device nothing is wiped. I found another guy in the same boat woth his Alcatel phone. Its obviously is a software glitch. Any one can help me with this.
Hello,
Does any one know the answer to this issue. Please help
Sent from my Nexus 4 using XDA Free mobile app
---------- Post added at 02:53 PM ---------- Previous post was at 02:28 PM ----------
barrymcsorley said:
A month or so ago my Nexus 7 (2012) started rebooting itself after a minute or so of turning on - I think this may have been during OTA upgrade from JWR66Y to new release. I tried to fix this by clearing app data and booting into CWM recovery and deleting cache and dalvik cache but the problem persisted. So I decided to reset the Nexus 7 back to factory image and have tried every means of doing so but every time I keep getting back to my original data and the app crashes and reboot continues. I have never had any issues connecting to the device on USB and ADB so this is not a driver issue. Things I have tried:
* Hard reset on phone from recovery (plus endless deleting of cache and dalvik)
* Hard reset using Wugfresh toolkit (plus near every other tool on there)
* Hard refresh from recovery mode
* Hard refresh using ADB and deleting user data etc.
* Flash recovery from ADB (also using Wugfresh as per above)
* ADB sideload from recovery of factory images, bootloaders and other ROM's
* Lock/unlock/root/unroot - using ADB commands as well as Wugfresh and other toolkits
* Delete data, system, cache
It seems like the Nexus 7 going into read only mode? Erasing /data and everything else in recovery has no effect and also when trying to overwrite the bootloader I get "writing 'bootloader'... FAILED (remote: (InvalidState))" using Wugfresh toolkit as per below. The device is still running JWR66Y.
I'm totally stuck now as to how I get my Nexus 7 back again! I have seen other people having issues with the JWR66Y bootloader (http://forum.xda-developers.com/showthread.php?t=1907796) but have tried all the workarounds and can't seem to find a way to overwrite the bootloader...
*** Trying with ADB manually ***
C:\android-sdk\platform-tools>adb devices
List of devices attached
4df17c816ec76f25 device
C:\android-sdk\platform-tools>adb devices
List of devices attached
015d165c520bf80f device
C:\android-sdk\platform-tools>adb reboot-bootloader
C:\android-sdk\platform-tools>fastboot devices
015d165c520bf80f fastboot
C:\android-sdk\platform-tools>fastboot oem unlock
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.016s]
finished. total time: 0.031s
C:\android-sdk\platform-tools>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.
img
sending 'bootloader' (2100 KB)...
OKAY [ 0.344s]
writing 'bootloader'...
OKAY [ 0.594s]
finished. total time: 0.938s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot -w update image-nakasi-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d165c520bf80f
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.031s]
sending 'boot' (4992 KB)...
OKAY [ 0.781s]
writing 'boot'...
OKAY [ 0.172s]
sending 'recovery' (5532 KB)...
OKAY [ 0.844s]
writing 'recovery'...
OKAY [ 0.188s]
erasing 'system'...
OKAY [ 0.016s]
sending 'system' (625382 KB)...
OKAY [ 95.203s]
writing 'system'...
OKAY [ 27.500s]
erasing 'userdata'...
OKAY [ 0.031s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 38.453s]
erasing 'cache'...
OKAY [ 0.016s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 2.203s]
rebooting...
finished. total time: 165.625s
*** Now using Wugfresh tool ***
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.031s]
finished. total time: 0.031s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.031s]
finished. total time: 0.031s
sending 'bootloader' (3911 KB)...
OKAY [ 0.609s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.828s
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d165c520bf80f
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.031s]
sending 'boot' (4992 KB)...
OKAY [ 0.781s]
writing 'boot'...
OKAY [ 0.172s]
sending 'recovery' (5532 KB)...
OKAY [ 0.844s]
writing 'recovery'...
OKAY [ 0.188s]
erasing 'system'...
OKAY [ 0.016s]
sending 'system' (625382 KB)...
OKAY [ 96.078s]
writing 'system'...
OKAY [ 27.484s]
erasing 'userdata'...
OKAY [ 0.031s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [148.516s]
erasing 'cache'...
OKAY [ 0.016s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 3.266s]
rebooting...
finished. total time: 1197.719s
Click to expand...
Click to collapse
me. AtHey all I have same problem after installing omni ROM on my nexus 7 2012. Its version 4.4.2. Please help me
Add another soul to this helpless ship ... My nexus 7 became like this during the night... not erasing anything. Nobody find any help with this?!
Hi there
I too have the same problem.
Has become so during the night while in recharge.
Impossible ... delete ... restore ... wipe ... flash ... anything.
I am glad I am not the only one in this boat.
My N7 started acting up this weekend. Like the OP, I have just about tried everything under the sun in reflashing the kernel, the rom, etc but nothing works.
If anyone has any ideas, please share.
Thanks.
mchiass said:
I am glad I am not the only one in this boat.
My N7 started acting up this weekend. Like the OP, I have just about tried everything under the sun in reflashing the kernel, the rom, etc but nothing works.
If anyone has any ideas, please share.
Thanks.
Click to expand...
Click to collapse
Could you try relocking then unlocking the bootloader? This guarantees a data wipe.
EverDawn4 said:
Could you try relocking then unlocking the bootloader? This guarantees a data wipe.
Click to expand...
Click to collapse
I tried to relock the tablet last night, but it didn't work. I originally tried to do it manually via "fastboot oem lock", and it seemed to work. The "tablet is now locked" message appeared on screen. However, the command line on my desktop froze until I manually rebooted the tablet, which caused a failure message to appear in the DOS window.
I then tried WUG's toolkit. Again, everything on the surface appears to be a success until the tablet reboots. But, the Google screen continues to show the unlock symbol.
It is very weird that fastboot and adb seem to communicate properly and get the correct responses but the actual data on the tablet doesn't change. The only way I can alter any data is when I boot TWRP via WUG (I have CWM on the tablet) and delete folders in the \sdcard folder. Unfortunately, the virtual TWRP app won't connect for ADB sideload and I can't seem to get TWRP to replace CWM on the tablet either.
RIP Nexus 7
If anyone finds a fix for this , thanks in advance.
I've got the same problem - will buy new mobo
Can't unlock the bootloader the normal way (fastboot oem-unlock). Don't have the "blobs", so nvflash won't work. Can't believe there isn't a way to completely "nuke and pave" so to speak. I might hold out for the Nexus 9, or just get a new mobo from ebay.
Hey I am in the same boat with nexus 7 2012 WiFi. Can't even flash factory image back. Unable to install any new apps. When I reboot any new apps installed are wiped out and tablet returns to old state with same data
Crap, how did I miss this tread before I started a new one .
Add me to the list, I have the same issue:
jaysus145 said:
I am pretty sure this one is a doozy, or that I am missing something very simple... you know, one or the other
First the facts: 2012 Wifi Nexus 7 running 5.0, stock rom, unlocked bootloader - nothing fancy about it.
Some background: I've been having a constant reboot issue for a while now... not quite a bootloop, as it allows me to enter my screenlock and even open the settings menu before suddenly rebooting again (at random intervals). Any changes I make in that time are lost upon reboot and it takes me right back to my 5.0 lockscreen (even if I disabled it the last time it was booted) - Same thing happens if I uninstall any apps, they are there when I reboot again.
I am able to see my device in both fastboot and recovery.
I've tried a factory reset from the Settings menu - no go, right back to my 5.0 lockscreen.
I've tried to reset from recovery - no go, right back to my 5.0 lockscreen.
I reflashed the image from the bootloader - no go, right back to my 5.0 lockscreen.
I flashed 4.4.4 - no go, right back to my 5.0 lockscreen.
I flashed 4.4.2 - no go, right back to my 5.0 lockscreen.
I flashed 5.0.2 and the same thing happened - no go, right back to my 5.0 lockscreen. (I was able to check About Tablet... no changes there either)
same thing with Safe Mode- no go, right back to my 5.0 lockscreen.
Wug's toolkit failed on me when I tried that, after the bootloader and boot image failed I got an out of memory error. (tried a couple versions here, Jelly bean actually forced fastboot to close on me)
I did a Remote Erase Request from Android Device Manager, it did not work either.
This is sounding like a hardware issue, right? Anything I can do about that if so?
ETA: Booo, this is my issue isn't it? http://forum.xda-developers.com/showthread.php?t=2588911
How the heck did I miss that before posting this
Click to expand...
Click to collapse
I have the same problem.
Asus Service Support in Spain (cygitsolutions.com) considers it is a hardware issue. They want a motherboard replacement for 190€ (like a new one).
my google nexus can't wipe data/factory reset,,,is there any solution???it is restarting again and again,,,,
Hi There,
I've had a bricked Nexus 10 for 2 years now. Been trying WugFresh toolkit for a while & also tried manually flashing.
I realized in the code that it says that I have the wrong bootloader version:
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.020s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.024s]
finished. total time: 0.028s
erasing 'recovery'...
OKAY [ 0.024s]
finished. total time: 0.024s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.024s]
finished. total time: 0.024s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.024s]
finished. total time: 0.024s
sending 'bootloader' (1280 KB)...
OKAY [ 0.184s]
writing 'bootloader'...
OKAY [ 0.148s]
finished. total time: 0.340s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.008s
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: 29783752704
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7271424
Block groups: 222
Reserved block group size: 1024
Created filesystem with 11/1818624 inodes and 158176/7271424 blocks
Creating filesystem with parameters:
Size: 553648128
Block size: 4096
Blocks per group: 32768
Inodes per group: 6768
Inode size: 256
Journal blocks: 2112
Label:
Blocks: 135168
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/33840 inodes and 4363/135168 blocks
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB03G6VJ
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MANTALJ12'.
Update requires 'MANTAMF01'.
finished. total time: 0.024s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
---
"Device version-bootloader is 'MANTALJ12'.
Update requires 'MANTAMF01'."
Anyone what the next steps are? Some help would be greatly appreciated :good:
Thanks!!
Hi,
I'll suggest you flashing a stock ROM from zero here. It seems the version you're trying to install is incompatible with the bootloader version. To do as such, follow the instructions in the 3rd post of this thread: http://forum.xda-developers.com/showthread.php?t=2670400
Good luck,
~Lord
XxLordxX said:
Hi,
I'll suggest you flashing a stock ROM from zero here. It seems the version you're trying to install is incompatible with the bootloader version. To do as such, follow the instructions in the 3rd post of this thread: http://forum.xda-developers.com/showthread.php?t=2670400
Good luck,
~Lord
Click to expand...
Click to collapse
Hi Lord,
I appreciate the reply . As per your suggestion I tried the code in post 3:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Brian Wu>cd downloads
C:\Users\Brian Wu\Downloads>cd fastboot
C:\Users\Brian Wu\Downloads\fastboot>fastboot devices
R32CB03G6VJ fastboot
C:\Users\Brian Wu\Downloads\fastboot>fastboot oem unlock
...
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Users\Brian Wu\Downloads\fastboot>fastboot erase system -w
erasing 'system'...
OKAY [ 0.016s]
erasing 'userdata'...
OKAY [ 0.016s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29783752704
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7271424
Block groups: 222
Reserved block group size: 1024
Created filesystem with 11/1818624 inodes and 158176/7271424 blocks
sending 'userdata' (139141 KB)...
writing 'userdata'...
OKAY [ 19.061s]
erasing 'cache'...
OKAY [ 0.020s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 553648128
Block size: 4096
Blocks per group: 32768
Inodes per group: 6768
Inode size: 256
Journal blocks: 2112
Label:
Blocks: 135168
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/33840 inodes and 4363/135168 blocks
sending 'cache' (10372 KB)...
writing 'cache'...
OKAY [ 1.434s]
finished. total time: 20.548s
C:\Users\Brian Wu\Downloads\fastboot>fastboot erase boot
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Brian Wu\Downloads\fastboot>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Brian Wu\Downloads\fastboot>fastboot flash bootloader bootloader-manta-
mantamf01.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.163s]
writing 'bootloader'...
OKAY [ 0.140s]
finished. total time: 0.305s
C:\Users\Brian Wu\Downloads\fastboot>fastboot flash system system.img
sending 'system' (522703 KB)...
OKAY [ 65.681s]
writing 'system'...
OKAY [ 4.249s]
finished. total time: 69.931s
C:\Users\Brian Wu\Downloads\fastboot>fastboot flash userdata userdata.img
sending 'userdata' (137478 KB)...
OKAY [ 17.284s]
writing 'userdata'...
OKAY [ 0.588s]
finished. total time: 17.874s
C:\Users\Brian Wu\Downloads\fastboot>fastboot flash cache cache.img
sending 'cache' (10372 KB)...
OKAY [ 1.308s]
writing 'cache'...
OKAY [ 0.090s]
finished. total time: 1.399s
C:\Users\Brian Wu\Downloads\fastboot>fastboot flash boot boot.img
sending 'boot' (4608 KB)...
OKAY [ 0.584s]
writing 'boot'...
OKAY [ 0.019s]
finished. total time: 0.604s
C:\Users\Brian Wu\Downloads\fastboot>fastboot flash recovery recovery.ig
error: cannot load 'recovery.ig'
C:\Users\Brian Wu\Downloads\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (5108 KB)...
OKAY [ 0.645s]
writing 'recovery'...
OKAY [ 0.021s]
finished. total time: 0.666s
C:\Users\Brian Wu\Downloads\fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Users\Brian Wu\Downloads\fastboot>
---
However when it rebooted, I'm still bricked. Any ideas?
I was also able to flash the file with the correct bootloader version:
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.019s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.020s
erasing 'recovery'...
OKAY [ 0.020s]
finished. total time: 0.021s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.019s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.020s]
finished. total time: 0.021s
sending 'bootloader' (1280 KB)...
OKAY [ 0.168s]
writing 'bootloader'...
OKAY [ 0.100s]
finished. total time: 0.270s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
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: 29783752704
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7271424
Block groups: 222
Reserved block group size: 1024
Created filesystem with 11/1818624 inodes and 158176/7271424 blocks
Creating filesystem with parameters:
Size: 553648128
Block size: 4096
Blocks per group: 32768
Inodes per group: 6768
Inode size: 256
Journal blocks: 2112
Label:
Blocks: 135168
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/33840 inodes and 4363/135168 blocks
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB03G6VJ
--------------------------------------------
checking product...
OKAY [ 0.014s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4608 KB)...
OKAY [ 0.585s]
writing 'boot'...
OKAY [ 0.019s]
sending 'recovery' (5108 KB)...
OKAY [ 0.647s]
writing 'recovery'...
OKAY [ 0.021s]
erasing 'system'...
OKAY [ 0.020s]
sending 'system' (522703 KB)...
OKAY [ 66.031s]
writing 'system'...
OKAY [ 4.249s]
erasing 'userdata'...
OKAY [ 0.020s]
sending 'userdata' (139141 KB)...
OKAY [ 17.548s]
writing 'userdata'...
OKAY [ 1.086s]
erasing 'cache'...
OKAY [ 0.019s]
sending 'cache' (10372 KB)...
OKAY [ 1.313s]
writing 'cache'...
OKAY [ 0.089s]
rebooting...
finished. total time: 91.692s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
---
but still stuck on the Google logo with the lock symbol.
Hi,
Well, it is looking a problem far more complicated than I expected at first. You are clearly writing the partitions, but for some reason it is not booting in Android. Can you start recovery? If you can we can try issuing some commands via adb to your tablet.
~Lord
Hi Lord,
Really appreciate the follow up.
I can go to recovery or flashboot custom recovery via wugfresh. Do you happen to know which thread has the instructions for the sideload?
Thanks
I was able to get to stock recovery menu to do an adb sideload via wugfresh tools, but once it aborts installation everytime. Any ways around this?
Hi,
I've been trying to put Nethunter on my nexus and seems to have bricked the device.
My main issue is being unable to write to 'Bootloader' and' 'System'. See below for the problem I'm having.
I've tried a number of different images and variations on the steps but nothing seems to work. Any help would be great! Thanks
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.031s]
finished. total time: 0.031s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.062s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.031s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.062s]
finished. total time: 0.062s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 1.016s]
finished. total time: 1.031s
sending 'bootloader' (2100 KB)...
OKAY [ 0.469s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.625s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
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: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d24bc7d10080f
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.031s]
sending 'boot' (5184 KB)...
OKAY [ 1.062s]
writing 'boot'...
OKAY [ 0.188s]
sending 'recovery' (5738 KB)...
OKAY [ 1.188s]
writing 'recovery'...
OKAY [ 0.203s]
erasing 'system'...
OKAY [ 0.047s]
sending 'system' (649455 KB)...
OKAY [131.703s]
writing 'system'...
FAILED (remote: (BadParameter))
finished. total time: 144.578s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Hi, if you restart do you have the same apps and system there was before? Or is all erased as it should be according to your erase actions in fastboot?
If all works the same as it was it seems you have the same problem as us. There is unfortunately still no solution for this problem. If it is only a bootloader writing problem I also can't help you out, sorry.
See http://forum.xda-developers.com/showthread.php?t=2588911
There is nothing. It gets stuck on the google logo and never gets past that stage so I assume it's been completely wiped.
Hi all, I'm really a newbie and hope you can help me with my Nexus 7 2012 wi-fi.
I tried to downgrade to 4.4.4 ( becasuse from 5.0 the tablet was unusable) following the instructions I found on gottabemobile.
I unlocked the device and everything seemed ok but when I try to write the new image with flash-all.bat I get the following errors, like the computer can't communicate with the device.
Code:
...
OKAY [ 0.000s]
finished. total time: 0.000s
erasing 'boot'...
FAILED (remote: (Timeout))
finished. total time: 2.044s
erasing 'cache'...
FAILED (remote: (Timeout))
finished. total time: 2.028s
erasing 'recovery'...
FAILED (remote: (Timeout))
finished. total time: 2.028s
erasing 'system'...
FAILED (remote: (Timeout))
finished. total time: 2.028s
erasing 'userdata'...
FAILED (remote: (Timeout))
finished. total time: 2.028s
sending 'bootloader' (2100 KB)...
FAILED (remote: (Timeout))
finished. total time: 2.028s
rebooting into bootloader...
FAILED (remote: (Nv3pBadReceiveLength))
finished. total time: 1.014s
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: 14569963520
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3557120
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/889440 inodes and 97309/3557120 blocks
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d2856b1400802
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4994 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.179s
If I try a fastboot devices I can see the serial number of the tablet but it is stucked in fastboot mode.
The bootloader is v. 4.23, product name is grouper, the image I'm using is image-nakasi-ktu84p (nakasi-ktu84p-factory-2c6e4d6f.tgz)
In computer management I see Android Device > Android Bootloader Interface
What did I do wrong? Have I bricked the device or it can be saved? Thanks in advance for any help.
Did you try with a different USB cable / a different USB port? Because it looks really as a communication problem.
Nevertheless be sure not to flash one of the factory images which contain a defective bootloader! Normally I am unpacking the factory image and flash boot.img and system.img manually by fastboot, i.e.:
- fastboot flash boot boot.img
- fastboot flash system system.img
Thanks for your help AndDiSa: I changed cable and port and flashed the images one by one and it worked!
Just one question: is Android 4.3 faster that 4.4 on the Nexus 7? Will I miss something big if I downgrade to 4.3?
You should probably even try 6.x
Hey all,
My nexus 10 randomly started bootlooping a while back (i was on some custom firmware on something like 4.2, but never bothered to update because I rarely used it). Today I decided to take the plunge and try and restore this thing to stock firmware, so I tried to install the stock firmware on the google site for 5.1.1... and it didn't work. This was the log:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
erasing 'boot'...
OKAY [ 0.019s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.020s
erasing 'recovery'...
OKAY [ 0.019s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.019s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.021s]
finished. total time: 0.021s
sending 'bootloader' (1280 KB)...
OKAY [ 0.163s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.294s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
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: 14273216512
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3484672
Block groups: 107
Reserved block group size: 855
Created filesystem with 11/871408 inodes and 96018/3484672 blocks
Creating filesystem with parameters:
Size: 553648128
Block size: 4096
Blocks per group: 32768
Inodes per group: 6768
Inode size: 256
Journal blocks: 2112
Label:
Blocks: 135168
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/33840 inodes and 4363/135168 blocks
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB053T9E
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MANTALJ12'.
Update requires 'MANTAMF01'.
finished. total time: 0.018s
Press any key to exit...
Apparently, despite writing the MF01 bootloader to the tablet, it didn't take. I tried to do this manually with fastboot, but this also didn't hold - my tablet still defiantly displays its bootloader version as MANTALJ12.
Is there anything I can do to beat the new version into its head? Did I mess something up? Or am I just SOL?
Thanks in advance...