Related
Hi all,
My nexus 7 has flashed with PA 3.65.
Now, I want to back to stock 4.2.2 ROM. I use the two tool kits-- Nexus 7 Toolkit and Nexus Root Toolkit
But my device is like locked, I use all kinds of commands to erase/flash it, my device is still run as PA version.
Go into TWRP and factory reset, the PA system still exist...
Use the Toolkit to flash, the PA system still exist...
Use adb/fastboot command to flash recovery image from TWRP 2.5.0.0 to 2.6, it always run as TWRP 2.5.0.0.
I feel my nexus 7's partition is locked, I can NOT add/delete anything. For example, if I delete a file in internal storage, the file will appear at the next reboot. If I add a file in internal storage, it will disappear at the next reboot time.
Anyone can help me? I have no idea to solve it.:crying:
Download the Nexus 7 4.2.2 factory package and unzip the contents to your ADB/Fastboot directory then reboot your device into Bootloader. Start > Run > CMD > cd (your directory) e.g. "cd c:/platform-tools" > "flash-all.bat" will your erase all current partitions and replace them with the factory images including the recovery, system, boot, data, etc.
Username invalid said:
Download the Nexus 7 4.2.2 factory package and unzip the contents to your ADB/Fastboot directory then reboot your device into Bootloader. Start > Run > CMD > cd (your directory) e.g. "cd c:/platform-tools" > "flash-all.bat" will your erase all current partitions and replace them with the factory images including the recovery, system, boot, data, etc.
Click to expand...
Click to collapse
thanks.
This way I has used and failed to recovery my nexus 7 to stock ROM. No error messages, all fastboot commands run successfully.
But the PA system is still exist...
Here are my logs, everything in fine...no error message.
But, reboot into the system, it still PA ROM, not stock ROM...
LMlatform-tools liming1$ ./fastboot oem unlock
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
LMlatform-tools liming1$ ./fastboot erase boot
erasing 'boot'...
OKAY [ 0.022s]
finished. total time: 0.022s
LMlatform-tools liming1$ ./fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.022s]
finished. total time: 0.022s
LMlatform-tools liming1$ ./fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.022s]
finished. total time: 0.022s
LMlatform-tools liming1$ ./fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.022s]
finished. total time: 0.022s
LMlatform-tools liming1$ ./fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.033s]
finished. total time: 0.033s
LMlatform-tools liming1$ ./fastboot flash bootloader ~/Downloads/bootloader-grouper-4.18.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.300s]
writing 'bootloader'...
OKAY [ 0.594s]
finished. total time: 0.894s
LMlatform-tools liming1$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
LMlatform-tools liming1$ ./fastboot -w update ~/Downloads/nakasi-jdq39/image-nakasi-jdq39.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.18
Baseband Version.....: N/A
Serial Number........: 015d2994xxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.040s]
checking version-bootloader...
OKAY [ 0.023s]
sending 'boot' (4944 KB)...
OKAY [ 0.612s]
writing 'boot'...
OKAY [ 0.171s]
sending 'recovery' (5446 KB)...
OKAY [ 0.668s]
writing 'recovery'...
OKAY [ 0.188s]
erasing 'system'...
OKAY [ 0.024s]
sending 'system' (471804 KB)...
OKAY [ 56.425s]
writing 'system'...
OKAY [ 20.828s]
erasing 'userdata'...
OKAY [ 0.027s]
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 [ 23.105s]
erasing 'cache'...
OKAY [ 0.003s]
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 [ 1.584s]
rebooting...
finished. total time: 103.851s
LMlatform-tools liming1$
Click to expand...
Click to collapse
The package includes the stock recovery, not a custom one. You can also flash stock images individually such as the system and data, which will restore the stock OS.
Username invalid said:
Download the Nexus 7 4.2.2 factory package and unzip the contents to your ADB/Fastboot directory then reboot your device into Bootloader. Start > Run > CMD > cd (your directory) e.g. "cd c:/platform-tools" > "flash-all.bat" will your erase all current partitions and replace them with the factory images including the recovery, system, boot, data, etc.
Click to expand...
Click to collapse
Username invalid said:
The package includes the stock recovery, not a custom one. You can also flash stock images individually such as the system and data, which will restore the stock OS.
Click to expand...
Click to collapse
Yes, I know the package included the stock recovery. I flashed it, but it didn't restore my nexus 7 to stock OS. My nexus 7 always running in PA ROM even I flashed all stock images.
thanks!
limingg said:
Yes, I know the package included the stock recovery. I flashed it, but it didn't restore my nexus 7 to stock OS. My nexus 7 always running in PA ROM even I flashed all stock images.
thanks!
Click to expand...
Click to collapse
Did you notice the problem immediately after install the new ROM or did it happen suddenly?
Username invalid said:
Did you notice the problem immediately after install the new ROM or did it happen suddenly?
Click to expand...
Click to collapse
I am not sure, I upgrade PA to 3.65 from 3.6 and flash franco r65 kernel yesterday.
Today I found some app FC and I delete my google account in setting, the magic happen, I reboot system and the google account come back...I try many times, even I delete a file and it will restore after reboot system.
So I feel my partition locked, I ca't flash anything or modify system. It is like that my nexus 7 freeze at a time. The PA ROM always exist, I can't flash( destory ) it.:crying::crying::crying:
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 can someone please help me. i am unrooted but unlocked i am trying desperately but when i try to run flash-all.sh it says it is not found. somewhere on the internet it said i should open that file in a text editor and place a ./ in front of every fastboot command. i tried that but still no luck
Feedback
robe5pierre said:
hi can someone please help me. i am unrooted but unlocked i am trying desperately but when i try to run flash-all.sh it says it is not found. somewhere on the internet it said i should open that file in a text editor and place a ./ in front of every fastboot command. i tried that but still no luck
Click to expand...
Click to collapse
make sure the file is executable try this open terminal at the directory the flash-all.sh is located and type
Code:
chmod +x flash-all.sh
this should make it executable than try to run the command
Code:
flash-all.sh
let me know if this helps.....Thx lj
lj50036 said:
What is the OS of your PC??
Click to expand...
Click to collapse
Osx 10.6.8
fastboot
robe5pierre said:
Osx 10.6.8
Click to expand...
Click to collapse
How did you install fastboot??
lj50036 said:
How did you install fastboot??
Click to expand...
Click to collapse
im trying to do everything all over again from scratch. can you recommend a thorough walkthrough? I had followed instructions from here: http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/ and picked up some other pointers elsewhere (like including not only ./ but ./fastboot-mac before any command)
fastboot/adb
robe5pierre said:
im trying to do everything all over again from scratch. can you recommend a thorough walkthrough? I had followed instructions from here: http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/ and picked up some other pointers elsewhere (like including not only ./ but ./fastboot-mac before any command)
Click to expand...
Click to collapse
Check this out for a very easy way to install fastboot/adb correctly
http://forum.xda-developers.com/showthread.php?t=2638673
lj50036 said:
Check this out for a very easy way to install fastboot/adb correctly
http://forum.xda-developers.com/showthread.php?t=2638673
Click to expand...
Click to collapse
thanks, when i run the script it asks me for the sudo password. what is this?
sudo
robe5pierre said:
thanks, when i run the script it asks me for the sudo password. what is this?
Click to expand...
Click to collapse
It means super user do... Take a look here http://support.apple.com/kb/ht4103
lj50036 said:
Check this out for a very easy way to install fastboot/adb correctly
http://forum.xda-developers.com/showthread.php?t=2638673
Click to expand...
Click to collapse
thanks! i installed fastboot your way, but when i tried to run ./flash-all.sh this is what was returned:
erasing 'boot'...
OKAY [ 0.032s]
finished. total time: 0.032s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.104s]
finished. total time: 0.104s
erasing 'recovery'...
OKAY [ 0.028s]
finished. total time: 0.028s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.445s]
finished. total time: 0.446s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.369s]
finished. total time: 0.369s
error: cannot open 'bootloader-manta-mantamf01.img'
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
ERROR: could not get pipe properties
< waiting for device >
error: failed to load 'image-mantaray-kot49h.zip': No such file or directory
any ideas?
robe5pierre said:
thanks! i installed fastboot your way, but when i tried to run ./flash-all.sh this is what was returned:
erasing 'boot'...
OKAY [ 0.032s]
finished. total time: 0.032s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.104s]
finished. total time: 0.104s
erasing 'recovery'...
OKAY [ 0.028s]
finished. total time: 0.028s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.445s]
finished. total time: 0.446s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.369s]
finished. total time: 0.369s
error: cannot open 'bootloader-manta-mantamf01.img'
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
ERROR: could not get pipe properties
< waiting for device >
error: failed to load 'image-mantaray-kot49h.zip': No such file or directory
any ideas?
Click to expand...
Click to collapse
Did you get the file from here???
https://developers.google.com/android/nexus/images
lj50036 said:
Did you get the file form here???
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
yes i did. i will try again fresh. i unpack it into a folder on my desktop and run the flash-all.sh like this: Users/myname/Desktop/myfolder/./flash-all.sh is that correct?
feedback
robe5pierre said:
yes i did. i will try again fresh. i unpack it into a folder on my desktop and run the flash-all.sh like this: Users/myname/Desktop/myfolder/./flash-all.sh is that correct?
Click to expand...
Click to collapse
Yes run all the command from the directory that contains flash-all.sh
It should aslo contain the bootloader and the zip folder
lj50036 said:
Yes run all the command from the directory that contains flash-all.sh
It should aslo contain the bootloader and the zip folder
Click to expand...
Click to collapse
i did it again and got the same result
paste
robe5pierre said:
i did it again and got the same result
Click to expand...
Click to collapse
Paste the input command include the command prompt line and the command you ran
Your bootloader is unlocked yes??
Im going to do the process on my nexus 10.. Give me a minute im downloader the factory image now....
lj50036 said:
Paste the input command include the command prompt line and the command you ran
Your bootloader is unlocked yes??
Click to expand...
Click to collapse
i think you are saying to paste it here so you can see... so here it is: /Users/myname/Desktop/new/./flash-all.sh
'myname' is my gf's name whose mac i am using. 'new' is the folder i made on the desktop with the kot49h files in it
yes i am unlocked
when i ran the script you gave me to install fastboot. the last thing it says is 'type adb or fastboot to run' it is at this point that i typed the above command. should i instead first type adb or fastboot?
after uninstalling and reinstalling fastboot with the link you provided me, then deleting and redownloading kot49h, unpacking it, unpacking the subsequent zip file that was produced and putting all the files in the same folder called 'new' on my desktop, then running the command i showed you, this is what i am getting:
error: cannot open 'bootloader-deb-flo-04.02.img'
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
error: cannot open 'radio-deb-deb-g00_2.37.0_1024.img'
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
error: failed to load 'image-razorg-kot49h.zip': No such file or directory
and now it appears i am stuck in bootloader mode. this is a new development
Feedback
robe5pierre said:
i think you are saying to paste it here so you can see... so here it is: /Users/myname/Desktop/new/./flash-all.sh
'myname' is my gf's name whose mac i am using. 'new' is the folder i made on the desktop with the kot49h files in it
yes i am unlocked
Click to expand...
Click to collapse
so open a new terminal window and instead of telling where the file is let move to that directory.....Here is what it would look like on my PC it is Linux but it will be almost the same
when i open my termail this is what I see without any input from me
Code:
[email protected] ~ $
Now lets move to the directory that contains the flash-all.sh.... we will just say that it is in Downloads/mantaray-kot49h thats the path to my sh file
we will type in the terminal
Code:
cd Downloads/mantaray-kot49h
Than my command line will change to this
Code:
[email protected] ~/Downloads/mantaray-kot49h $
Than to verify all the files that are needed to be used in the process are there we can run a
Code:
ls
Code:
[email protected] ~/Downloads/mantaray-kot49h $ ls
bootloader-manta-mantamf01.img flash-all.bat flash-all.sh flash-base.sh image-mantaray-kot49h.zip
There are all the files I need to flash the stock image
let go ahead and I will do that to show you the whole thing...
Code:
./flash-all.sh
Code:
[email protected] ~/Downloads/mantaray-kot49h $ ./flash-all.sh
erasing 'boot'...
OKAY [ 0.029s]
finished. total time: 0.029s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.103s]
finished. total time: 0.103s
erasing 'recovery'...
OKAY [ 0.029s]
finished. total time: 0.029s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.378s]
finished. total time: 0.378s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.435s]
finished. total time: 0.435s
sending 'bootloader' (1280 KB)...
OKAY [ 0.161s]
writing 'bootloader'...
OKAY [ 0.193s]
finished. total time: 0.354s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTAMF01
Baseband Version.....: no modem
Serial Number........: R32D1040PSW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
sending 'boot' (4784 KB)...
OKAY [ 0.606s]
writing 'boot'...
OKAY [ 0.120s]
sending 'recovery' (5334 KB)...
OKAY [ 0.678s]
writing 'recovery'...
OKAY [ 0.123s]
erasing 'system'...
OKAY [ 0.152s]
sending 'system' (647286 KB)...
OKAY [ 81.942s]
writing 'system'...
OKAY [ 16.038s]
erasing 'userdata'...
OKAY [ 0.374s]
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 [ 29.138s]
erasing 'cache'...
OKAY [ 0.094s]
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.603s]
rebooting...
finished. total time: 130.879s
---------- Post added at 10:56 AM ---------- Previous post was at 10:48 AM ----------
If that still will not work for you I would get a new image from the nexus site.....
---------- Post added at 10:59 AM ---------- Previous post was at 10:56 AM ----------
robe5pierre said:
after uninstalling and reinstalling fastboot with the link you provided me, then deleting and redownloading kot49h, unpacking it, unpacking the subsequent zip file that was produced and putting all the files in the same folder called 'new' on my desktop, then running the command i showed you, this is what i am getting:
error: cannot open 'bootloader-deb-flo-04.02.img'
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
error: cannot open 'radio-deb-deb-g00_2.37.0_1024.img'
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
error: failed to load 'image-razorg-kot49h.zip': No such file or directory
Click to expand...
Click to collapse
It looks like you don't have the right file for the nexus 10?? Make sure you get the mantaray!! If thas what your working with
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
robe5pierre said:
and now it appears i am stuck in bootloader mode. this is a new development
Click to expand...
Click to collapse
For sure you dont have a ROM installed now you started the process and it erased all your data.....
lj50036 said:
so open a new terminal window and instead of telling where the file is let move to that directory.....Here is what it would look like on my PC it is Linux but it will be almost the same
when i open my termail this is what I see without any input from me
Code:
[email protected] ~ $
Now lets move to the directory that contains the flash-all.sh.... we will just say that it is in Downloads/mantaray-kot49h thats the path to my sh file
we will type in the terminal
Code:
cd Downloads/mantaray-kot49h
Than my command line will change to this
Code:
[email protected] ~/Downloads/mantaray-kot49h $
Than to verify all the files that are needed to be used in the process are there we can run a
Code:
ls
Code:
[email protected] ~/Downloads/mantaray-kot49h $ ls
bootloader-manta-mantamf01.img flash-all.bat flash-all.sh flash-base.sh image-mantaray-kot49h.zip
There are all the files I need to flash the stock image
let go ahead and I will do that to show you the whole thing...
Code:
./flash-all.sh
Code:
[email protected] ~/Downloads/mantaray-kot49h $ ./flash-all.sh
erasing 'boot'...
OKAY [ 0.029s]
finished. total time: 0.029s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.103s]
finished. total time: 0.103s
erasing 'recovery'...
OKAY [ 0.029s]
finished. total time: 0.029s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.378s]
finished. total time: 0.378s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.435s]
finished. total time: 0.435s
sending 'bootloader' (1280 KB)...
OKAY [ 0.161s]
writing 'bootloader'...
OKAY [ 0.193s]
finished. total time: 0.354s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTAMF01
Baseband Version.....: no modem
Serial Number........: R32D1040PSW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
sending 'boot' (4784 KB)...
OKAY [ 0.606s]
writing 'boot'...
OKAY [ 0.120s]
sending 'recovery' (5334 KB)...
OKAY [ 0.678s]
writing 'recovery'...
OKAY [ 0.123s]
erasing 'system'...
OKAY [ 0.152s]
sending 'system' (647286 KB)...
OKAY [ 81.942s]
writing 'system'...
OKAY [ 16.038s]
erasing 'userdata'...
OKAY [ 0.374s]
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 [ 29.138s]
erasing 'cache'...
OKAY [ 0.094s]
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.603s]
rebooting...
finished. total time: 130.879s
---------- Post added at 10:56 AM ---------- Previous post was at 10:48 AM ----------
If that still will not work for you I would get a new image from the nexus site.....
---------- Post added at 10:59 AM ---------- Previous post was at 10:56 AM ----------
It looks like you don't have the right file for the nexus 10?? Make sure you get the mantaray!! If thas what your working with
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
For sure you dont have a ROM installed now you started the process and it erased all your data.....
Click to expand...
Click to collapse
Seriously, thank you thank you thank you. Even though the 4.4.2 kot49h is listed under 'mantaray' and it is the file i was told by another administrator to use and he assured me there would be no problem going from 4.3 jwr66v directly to kot49h since it is a factory image, alas the problem was that i needed to use 4.4 krt16s. Doing this, and following everything else you told me, it worked like a charm. As soon as i booted up, i got the ota for 4.4.2 and installed that smoothly. Thank you sooo much @lj50036!
Now i guess i am going to root again just so i can have usb functionality with stickmount. Do you have any suggestions for a really good set of instructions for this? also, do i need to save this folder i created on my mac desktop??
I have a problem with my nexus 2012 WiFi version
I put twrp recovery 2.7.0.0 and omini ROM 4.4.2. Since then I have been unable to wipe anything on the device. I wipe or format in twrp when reboot every thing is same. Even with fastboot I format internal SD or wipe everything. It says it is OK but when u boot nothing is wiped. I can install apps but when I reboot they are erased and only apps which were there earlier stay. Please help. Another guy in the forum has same problem.
Default Can't wipe or factory reset Nexus 7 (2102) using multiple methods
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/show....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
Thanks[/QUOTE][/QUOTE]
Seems your firmware files are missing things, as noted in your logs.
Try getting the proper firmware from another source.
---------- Post added at 04:40 PM ---------- Previous post was at 04:39 PM ----------
Did you use this guide?
http://forum.xda-developers.com/showthread.php?t=1907796
Hey I did flash and updated my boot loader from right image posted on XDA. What firmware are you referring to
Hey can you help me please
Androgoo said:
Hey can you help me please
Click to expand...
Click to collapse
Follow the guide I linked... Exactly as it says and you should be fine.
Hey when I click the link I can't see any guide or steps to follow.
Also is the guide simple to use. I am very new to all this
The guide starts on first page with post number 1.
Hey I tried the guide. Every thing goes through fine but when tab reboots it still has old omni ROM on it. 4.4.2. I also tried to update twrp to v. 2.8 from 2.7 in fastboot but no joy. It stays on 2.7 on reboot even though fastboot flashes it and says OK done. Also I cannot relock the boot loader. I give the command in fastboot OEM lock its says OK button reboot its still unlocked. But I can boot into a new version of twrp or cwm touch temporarily using wgh tool and click boot custom recovery temporarily and it does it. But can't flash it permanently. What shall I do. Feel like smashing the tablet with a hammer. I am pissed because my son has no tablet any more. I was the one who put omni ROM on it. So I take the blame for ruining it. It was working fine but suddenly it rebooted on it'd own after few weeks and since then nothing works on it. Just the stuff that was on it. Can't install anything new. I wonder why I can't even change custom recovery from twrp permanently to a new version. Please give me your guidance.
Cant Restore / format / recovery
I had rooted the device, loaded dirty unicorns and then decided to try out Liquid. Got liquid flashed and let google restore apps and such. Came back and my girlfriend mentioned there was an update to 4.4.3 and she downloaded the "update" while I was making dinner. I came back in and she said the tablet had rebooted and now wouldn't boot. So I tried to get into TWRP which was working just fine. NO Luck.... So I tried the stock restore. it just hangs at the formatting data.
So i then tried the Nexus tool kit to reflash the stock system and unroot and I figured i would just start over. Well Im now Stuck.
I have tried everything i can.....
Included is a couple screenshots.
TIA
Nick
momule said:
I had rooted the device, loaded dirty unicorns and then decided to try out Liquid. Got liquid flashed and let google restore apps and such. Came back and my girlfriend mentioned there was an update to 4.4.3 and she downloaded the "update" while I was making dinner. I came back in and she said the tablet had rebooted and now wouldn't boot. So I tried to get into TWRP which was working just fine. NO Luck.... So I tried the stock restore. it just hangs at the formatting data.
So i then tried the Nexus tool kit to reflash the stock system and unroot and I figured i would just start over. Well Im now Stuck.
I have tried everything i can.....
Included is a couple screenshots.
TIA
Nick
Click to expand...
Click to collapse
Did you try fastboot?
KJ said:
Did you try fastboot?
Click to expand...
Click to collapse
I assume you mean via CMD
Yes, this guide here....
http://forum.xda-developers.com/showthread.php?t=1907796
KJ said:
Yes, this guide here....
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
Yup. I'll go back through everything again. Uninstall and re install the drivers and SDK,
Thanks
Nick
momule said:
Yup. I'll go back through everything again. Uninstall and re install the drivers and SDK,
Thanks
Nick
Click to expand...
Click to collapse
Im confused. My device is not able to boot and therefore I cant enable debugging and use ADB. I have installed all the drivers and all the pkgs with SDK. and The toolkit finds myt fastboot device. hjowever CMD window does not.
Im not a cmd wiz and none of the cmds seem to be recognizable.
Use the guide linked. You'll be using fastboot from bootloader mode... Shouldn't need adb.
Read the guide carefully.
KJ said:
Use the guide linked. You'll be using fastboot from bootloader mode... Shouldn't need adb.
Read the guide carefully.
Click to expand...
Click to collapse
went through everything but writing the bootloader. Anytime it reboots into bootloader it just goes to black screen and get no response.
momule said:
went through everything but writing the bootloader. Anytime it reboots into bootloader it just goes to black screen and get no response.
Click to expand...
Click to collapse
I'm confused.. If you can't get into bootloader, then how are you using fastboot?
And, what exactly is your device (n7 2012..not 2013 right... And WiFi or 3g model) , and what exactly are you trying to flash? What firmware file?
KJ said:
I'm confused.. If you can't get into bootloader, then how are you using fastboot?
And, what exactly is your device (n7 2012..not 2013 right... And WiFi or 3g model) , and what exactly are you trying to flash? What firmware file?
Click to expand...
Click to collapse
N7 2012 - Wifi - The Tablet shows the current bootloader to be 4.18. What I mean is when the tab is manually put into bootloader its fine but when given a cmd prompt to reboot to booloader it goes to a black screen and no response from the PC connection or on the tab
I have tried flashing the following Stock images from
https://developers.google.com/android/nexus/images
4.2.2 (JDQ39)
4.3 (JWR66Y)
4.4.3 (KTU84L)
I extracted the files to SDK platform tools folder and like i said everything erases fine via fastboot cmd's. However when I get to the flash bootloader cmd its gives an error. (seen in pics posted above) I even tried the older version of the 4.23 img link in the guide you suggested.
anyone? Anyone offer a service to restore stock image for me. Thanks
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.