I have a sudden and strange problem with my Nexus 10 bought about two months ago. The ROM is stock Android 4.4.2 (automatic OTA update from original 4.2), not rooted. It seems that its internal storage became read-only. First, the tablet started to reboot every 10 minutes or so and tried to update some of the installed applications after every restart. I have tried to uninstall them and found that after reboot they are back and that writing to internal storage does not work. Installing, uninstalling and updating applications, saving application settings, deleting and copying files, both using a file manager on the tablet and through MTP - nothing works. After restart everything is back to the state before writing. Resetting to factory defaults from the Settings menu and from recovery (factory reset/data wipe) also does not work (in the latter case the tablet freezes on a screen showing that formatting /data is in progress). Any ideas? At least, I would like to delete some personal documents from the tablet before sending it for repair or replacement.
I'm in the same position. Was running CM 11 nightlies... running fine for weeks. Starting last week it's stuck in this mode i.e. every time I do a reload, it's as if it doesn't remember anything that was previously done (like app updates). Any attempt to do a factory reset, copy a new image etc. just gets ignored - device just reboots and goes back to it's previous state.
I would suggest using fastboot to wipe all partitions, this would involve unlocking bootloader. Then I would flash the factory image through fastboot as well
(Just Google : android factory images)
Sent from my Nexus 4 using XDA Premium 4 mobile app
Thanks for the suggestion. So I tried following:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system -w
> fastboot erase userdata
> fastboot flash bootloader bootloader-manta-mantalj12.img
> fastboot reboot-bootloader
> fastboot -w update image-mantaray-jdq39.zip
Had to use 4.2.2 factory image since that's the version of bootloader I had. All the commands seems to complete OK.. at the end, device reboots... but CM 11 loads again as if nothing had been changed! It's as if the erase commands have no affect.
So the output in cmd/terminal says successful for each command but at the end nothing happened? This is very strange to me... Can you try again and post the input/output from terminal?
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So the output in cmd/terminal says successful for each command but at the end nothing happened? This is very strange to me... Can you try again and post the input/output from terminal?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried with "fastboot flash" steps too... but same issue. After reboot, goes right back to CM.
S:\android\wugs\data>fastboot devices
R32CB03R8KW fastboot
S:\android\wugs\data>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.095s]
finished. total time: 0.259s
S:\android\wugs\data>fastboot erase system -w
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.020s]
erasing 'userdata'...
OKAY [ 0.019s]
formatting 'userdata' partition...
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
sending 'userdata' (137478 KB)...
writing 'userdata'...
OKAY [ 19.662s]
erasing 'cache'...
OKAY [ 0.018s]
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.465s]
finished. total time: 21.186s
S:\android\wugs\data>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.019s]
finished. total time: 0.020s
S:\android\wugs\data>fastboot erase boot
erasing 'boot'...
OKAY [ 0.019s]
finished. total time: 0.019s
S:\android\wugs\data>fastboot flash system system.img
erasing 'system'...
OKAY [ 0.019s]
sending 'system' (522703 KB)...
OKAY [ 65.509s]
writing 'system'...
OKAY [ 4.250s]
finished. total time: 69.778s
S:\android\wugs\data>fastboot flash boot boot.img
sending 'boot' (4608 KB)...
OKAY [ 0.580s]
writing 'boot'...
OKAY [ 0.018s]
finished. total time: 0.598s
S:\android\wugs\data>fastboot flash cache cache.img
erasing 'cache'...
OKAY [ 0.018s]
sending 'cache' (10372 KB)...
OKAY [ 1.301s]
writing 'cache'...
OKAY [ 0.088s]
finished. total time: 1.411s
S:\android\wugs\data>fastboot flash userdata userdata.img
erasing 'userdata'...
OKAY [ 0.019s]
sending 'userdata' (137478 KB)...
OKAY [ 17.234s]
writing 'userdata'...
OKAY [ 0.588s]
finished. total time: 17.842s
S:\android\wugs\data>fastboot flash recovery recovery-clockwork-touch-6.0.2.3-ma
nta.img
sending 'recovery' (6296 KB)...
OKAY [ 0.792s]
writing 'recovery'...
OKAY [ 0.019s]
finished. total time: 0.812s
S:\android\wugs\data>fastboot reboot
rebooting...
finished. total time: 0.001s
S:\android\wugs\data>
...this I have never encountered. I assume these are all manually entered commands and the wugs is just the name of the folder the factory images are in correct? As in you aren't using a toolkit to do this? If not then it appears you are doing everything correct and I can not see why it isn't erasing or flashing the new images
The only other suggestions I have would be try a different PC, maybe a Linux live disc or something, or try another USB cable. But its unlikely to help but nonetheless worth a shot.
Or if you can find the proper images to be used in Odin or hiemdal you could try going into download mode and see if a factory flash this way will help. Note I haven't used download mode on my n10 before but many times on other Sammy devices
Try any of the above and if I can think of more I'll post back
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Yep.. indeed it is very strange. The wugs directory is just where adb/fastboot are located (I'm using the adb/fastboot that wugs creates vs. downloading the sdk)... and the factory image is unzipped in the same dir. All commands are being manually entered. Using a windows 8 laptop with OEM USB cable.
I haven't used odin or hiemdal before... but will search and see how.
I've had this N10 since it launched... and it's had some sort of custom rom ever since... never had a problem. I switched to CM11 back in december, and it has been fine... even doing updates. But now it's stuck in this state. I can copy a new rom to the device, but when I reboot and go into recovery and try to install it, the rom file has been removed. Every time it reboots it goes and re-downloads app updates that came in the past week or two... installs them without issue.. and functions fairly normally. But if a reboot is triggered, it goes back to its old state. I also have to re-enable Developer mode and USB debugging every time after reboot.
Anyway, I'll keep digging.
well being this stroked my curiosity i figured i would spend a few minuets looking into this, and it appears others have indeed had this issue. most commonly with samsung devices.
I feel there must be a fix of sorts out there, but i dont have time to dig more, but i thought i would through up a few links that summarize what i found
http://forum.xda-developers.com/showthread.php?t=2627703&page=4
http://forum.xda-developers.com/showthread.php?t=1704646
http://androidforums.com/incredible...internal-phone-storage-becomes-read-only.html
http://forum.xda-developers.com/showthread.php?t=2193499
there were many more i looked at but these were just the tabs i have opened.
Ill dig some more tonight but it what is being said is true, your internal sd is failing you. if you still have a warranty im not sure if they will except it as there is a custom rom/recovery on there but many have said RMA works fine even with this on a nexus. otherwise it may be possible to do a full brick with dd commands if you want to send it back completely bricked... any way hope you find some way of getting working again!
Useful links... I'll go through them. Hopefully something there will work.
My warranty is out though.. it's over a year since I bought it
Maybe of interest for you with root
http://www.chainfire.eu/articles/113/Is_Google_blocking_apps_writing_to_SD_cards_/
ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
This is also an issue on some galaxy nexus'. It is a fried EMMC chip im afraid. The internal storage is ruined and needs to be replaced. I didnt know this was possible on the Nexus 10 and maybe im wrong but it has all the signs..
Sent from my Galaxy Nexus using XDA Premium HD app
Thanks for all the links guys... I think this appears to be some sort of hardware issue. I'm reluctant to tinker further in case I make it worse. Right now it is usable as long as I don't try to update the rom or run certain apps. I'll keep stumbling along until the N10 replacement (N11?) comes out... gives me an excuse to buy it
Hi,
For more it looks like a dead end (even fastboot didn't work!), I think you should try one more thing, I'm highly skeptical that it will work, but now I guess every little bit will be something.
First reboot to your recovery. Then plug it to your PC and go to your and folder, now type:
Code:
adb shell
su
touch /sdcard/null
cd /dev/block/platform/dw_mmc.0/by-name/
dd if=/sdcard/null of=system
dd if=/sdcard/null of=userdata
dd if=/sdcard/null of=boot
If the command went trough rightly, it will format your system, kernel (boot) and data. If this doesn't work I'm out of ideas, I was going to suggest things that were already suggested here, so it only left me with this. I just want to tell you that if something goes wrong and it stops working, I'm not responsible for it. If the command works, then it's all about flashing a new ROM.
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10
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:
Okay, so I'm having what I believe to be a strange issue and was hoping someone here might be able to help.
One day my Nexus 7 (2012/wifi/grouper) started to reboot while sitting on my desk. It then would go into a boot-loop. I turned if off for a bit and every time since it does the same thing. Loads up correctly but after any amount of time it will do the same thing.
So I tried a Factory Wipe & Erase. It went through the whole deal and I rebooted it; but the device didn't wipe or erase, everything was still on the device. >.>
So I decided to flash back to stock. (device was/is unlocked/rooted). Updated the SDK and made sure adb and fastboot both work correctly and that I had the most recent updates to anything available. USB drivers are current and working correctly. Fantastic I say to myself as I go through the fastboot process of returning to stock.
Code:
C:\android-sdk\platform-tools>fastboot devices
015d2d42201c1213 fastboot
I hit fastboot devices and it shows me my device, so I go through the normal bits. This is what I get:
Code:
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.283s]
writing 'bootloader'...
OKAY [ 0.596s]
finished. total time: 0.879s
Awesome! It appears everything is working fine, so I figure I might as well continue.
Code:
C:\android-sdk\platform-tools>fastboot -w update image-nakasi-krt16s.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........: 015d2d42201c1213
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.019s]
sending 'boot' (4990 KB)...
OKAY [ 0.652s]
writing 'boot'...
OKAY [ 0.177s]
sending 'recovery' (5530 KB)...
OKAY [ 0.722s]
writing 'recovery'...
OKAY [ 0.184s]
erasing 'system'...
OKAY [ 0.021s]
sending 'system' (611886 KB)...
OKAY [ 78.120s]
writing 'system'...
OKAY [ 27.180s]
erasing 'userdata'...
OKAY [ 0.030s]
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 [ 25.415s]
erasing 'cache'...
OKAY [ 0.012s]
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.655s]
rebooting...
finished. total time: 134.326s
Alright, we're booting back into the device and it appears to have gone fine! But then I notice I'm still seeing the Jellybean "X" boot screen and think to myself well, that's kind of strange...The Nexus 7 loads up and...nothing changed. The device still has everything on it that it had previously, nothing has been changed or deleted.
I've tried deleting (user data such as music or videos) using Windows Explorer. I've tried File Manager and ES File Explorer via the tablet. But every, single time I turn the device back on...everything is still there!
So I guess what I'm trying to figure out is...am I high? Did I die in my sleep and I'm just not aware of it yet? Has my Nexus 7 been cast for a sequel of Groundhog's Day?
What am I missing here? I've done this time and time again but I don't think I've ever seen something like on any of my previous devices (or with this N7 in question as well...)
Hopefully I'm missing something very minor here and someone will make me feel stupid for it. I don't mind feeling stupid if it means I learn something new! (Any and all help would be greatly appreciated.)
limbonik said:
Okay, so I'm having what I believe to be a strange issue and was hoping someone here might be able to help.
One day my Nexus 7 (2012/wifi/grouper) started to reboot while sitting on my desk. It then would go into a boot-loop. I turned if off for a bit and every time since it does the same thing. Loads up correctly but after any amount of time it will do the same thing.
So I tried a Factory Wipe & Erase. It went through the whole deal and I rebooted it; but the device didn't wipe or erase, everything was still on the device. >.>
So I decided to flash back to stock. (device was/is unlocked/rooted). Updated the SDK and made sure adb and fastboot both work correctly and that I had the most recent updates to anything available. USB drivers are current and working correctly. Fantastic I say to myself as I go through the fastboot process of returning to stock.
Code:
C:\android-sdk\platform-tools>fastboot devices
015d2d42201c1213 fastboot
I hit fastboot devices and it shows me my device, so I go through the normal bits. This is what I get:
Code:
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.283s]
writing 'bootloader'...
OKAY [ 0.596s]
finished. total time: 0.879s
Awesome! It appears everything is working fine, so I figure I might as well continue.
Code:
C:\android-sdk\platform-tools>fastboot -w update image-nakasi-krt16s.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........: 015d2d42201c1213
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.019s]
sending 'boot' (4990 KB)...
OKAY [ 0.652s]
writing 'boot'...
OKAY [ 0.177s]
sending 'recovery' (5530 KB)...
OKAY [ 0.722s]
writing 'recovery'...
OKAY [ 0.184s]
erasing 'system'...
OKAY [ 0.021s]
sending 'system' (611886 KB)...
OKAY [ 78.120s]
writing 'system'...
OKAY [ 27.180s]
erasing 'userdata'...
OKAY [ 0.030s]
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 [ 25.415s]
erasing 'cache'...
OKAY [ 0.012s]
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.655s]
rebooting...
finished. total time: 134.326s
Alright, we're booting back into the device and it appears to have gone fine! But then I notice I'm still seeing the Jellybean "X" boot screen and think to myself well, that's kind of strange...The Nexus 7 loads up and...nothing changed. The device still has everything on it that it had previously, nothing has been changed or deleted.
I've tried deleting (user data such as music or videos) using Windows Explorer. I've tried File Manager and ES File Explorer via the tablet. But every, single time I turn the device back on...everything is still there!
So I guess what I'm trying to figure out is...am I high? Did I die in my sleep and I'm just not aware of it yet? Has my Nexus 7 been cast for a sequel of Groundhog's Day?
What am I missing here? I've done this time and time again but I don't think I've ever seen something like on any of my previous devices (or with this N7 in question as well...)
Hopefully I'm missing something very minor here and someone will make me feel stupid for it. I don't mind feeling stupid if it means I learn something new! (Any and all help would be greatly appreciated.)
Click to expand...
Click to collapse
I'm not an expert on these things but I basically have a question for you. If you're willing to wipe out the whole thing, have you tried doing the factory reset via settings?
Sent from my Nexus 7 (2013)
Thanks for the suggestion. I have tried Factory wipe from inside the device and it says it completes and I reboot to everything on the device.
I've also tried wiping everything out using TWRP and it to gives me a completion message, but after start up everything is still on the device.
I've also went into TWRP under advanced options, used the built in file explorer and deferred everything from the "sd card". But once again the device reboots, loads up...And everything is there once more!
That's why I wasn't sure if I might be high or dead. I am completely dumbfounded by what's occurring here. -.-
Sent from my Nexus 7 (2013) running 4.4
limbonik said:
Thanks for the suggestion. I have tried Factory wipe from inside the device and it says it completes and I reboot to everything on the device.
I've also tried wiping everything out using TWRP and it to gives me a completion message, but after start up everything is still on the device.
I've also went into TWRP under advanced options, used the built in file explorer and deferred everything from the "sd card". But once again the device reboots, loads up...And everything is there once more!
That's why I wasn't sure if I might be high or dead. I am completely dumbfounded by what's occurring here. -.-
Sent from my Nexus 7 (2013) running 4.4
Click to expand...
Click to collapse
Wow! Are you there's no cameras outside your window, shooting for the next Twilight Zone movie?
The only thing I can think of is using a Toolkit like WugFresh and see if that works, other than that, I'm at a total loss.
Sent from my Nexus 7 (2013)
Oh~ ho! I have also tried Wugfresh and ADB Sideload from within TWRP; same thing occurs.
I've also moved the zip to the device from Windows Explorer to the root directory, but when I reboot to recovery to install from TWRP the file is no longer there! >_<
Sent from my Nexus 7 (2013) running 4.4
limbonik said:
Oh~ ho! I have also tried Wugfresh and ADB Sideload from within TWRP; same thing occurs.
I've also moved the zip to the device from Windows Explorer to the root directory, but when I reboot to recovery to install from TWRP the file is no longer there! >_<
Sent from my Nexus 7 (2013) running 4.4
Click to expand...
Click to collapse
I've got exactly the same problem. N7 (2012) which is constantly booting into the same state. The same apps try to update themselves from the play store, the same screen etc etc.
I've tried the basic factory reset from the menus - when it reboots nothing has changed. I've removed the other user account from the N7 that I keep locked for work use. It seems to disappear, but when I reboot its there again. I've tried booting into recovery mode, selecting "wipe data/format" (or whatever it says), it says that has gone OK, then it reboots and nothing has been changed / deleted - its still in the same state.
I've rebooted into fastboot mode and used WUGS toolkit to flash stock + unroot in the soft-brick / bootloop mode (both with the force flash option on and off), they both report it is working fine, reboots and there are absolutely no changes at all made to the device.
I turn wifi off, reboot and wifi is back on again. I enable developer options / usb debugging, reboot and they are gone again. Its as if some part of the flash storage has gone completely unwritable, but what is really odd is that whilst the device is on, it behaves as if things are changing - apps appear to update, and be installed, options get changed etc. But nothing at all "sticks" after a reboot! Plus I am lucky if the device stays booted for more than a couple of minutes, it is constantly self--rebooting.
Did you ever find a fix for this, its driving me mad!!
Matt
(Edit - placed a call to google support, and they are sending me a replacement - despite it being 18 months since purchase! Impressed!!)
larkim said:
I've got exactly the same problem. N7 (2012) which is constantly booting into the same state. The same apps try to update themselves from the play store, the same screen etc etc.
I've tried the basic factory reset from the menus - when it reboots nothing has changed. I've removed the other user account from the N7 that I keep locked for work use. It seems to disappear, but when I reboot its there again. I've tried booting into recovery mode, selecting "wipe data/format" (or whatever it says), it says that has gone OK, then it reboots and nothing has been changed / deleted - its still in the same state.
I've rebooted into fastboot mode and used WUGS toolkit to flash stock + unroot in the soft-brick / bootloop mode (both with the force flash option on and off), they both report it is working fine, reboots and there are absolutely no changes at all made to the device.
I turn wifi off, reboot and wifi is back on again. I enable developer options / usb debugging, reboot and they are gone again. Its as if some part of the flash storage has gone completely unwritable, but what is really odd is that whilst the device is on, it behaves as if things are changing - apps appear to update, and be installed, options get changed etc. But nothing at all "sticks" after a reboot! Plus I am lucky if the device stays booted for more than a couple of minutes, it is constantly self--rebooting.
Did you ever find a fix for this, its driving me mad!!
Matt
(Edit - placed a call to google support, and they are sending me a replacement - despite it being 18 months since purchase! Impressed!!)
Click to expand...
Click to collapse
Now THAT'S support! :thumbup::thumbup:
Sent from my Nexus 7 (2013)
Free Beer* for anyone who can help!
I have a serious problem with my nexus 7 (2012) which I have been researching and working on for many months now to no avail. For this reason I am offering a free beer to anyone who can help (t's&c's apply)!
Background:
The device has stock 4.2.2 rooted installed along with Multirom which has CM10, paranoid android and Ubuntu (desktop).
All this ran fine for a while. I then noticed that if I made any change to the stock rom, update an app, download an app, change the wallpaper, download a file to any part of the filesystem... that when I rebooted the tablet that change would not be there... The wallpaper would be back as it was or the file simply didn't exist! It was as if the filesystem was mounted as non - persistent.
So I tried the other rooms on the tablet and realised they would not boot. All except Ubuntu which was working fine however doesn't mount the internal storage so I couldn't test any further.
I attempted to re flash back to stock. Using flashboot I cleared the cache, system, user data etc and had no errors and then flashed the stock rom. After rebooting my old system appeared to my surprise.
I have tried since then to re flash everything. Recovery won't update (currently TWRP) and the only time I get any error message is when trying to re flash the bootloader which is currently 4.18, everything seems to go well and then "signature match" appears on the tablet screen and it hangs leaving an error in the fastboot terminal reading "Remote: ()"
If anyone can help me fix this issue then the beer is yours... The only stipulation is you have to be in Ireland to claim it but what better excuse for a holiday
Thanks in advance.
Kieran
I have just used Wug's Toolkit to "Flash Stock + Unroot"
Below is th terminal output:
Code:
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.020s]
finished. total time: 0.020s
erasing 'recovery'...
OKAY [ 0.020s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.020s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.030s]
finished. total time: 0.030s
sending 'bootloader' (2096 KB)...
OKAY [ 0.270s]
writing 'bootloader'...
OKAY [ 0.590s]
finished. total time: 0.860s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
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........: 015d21d914481613
--------------------------------------------
checking product...
OKAY [ 0.040s]
checking version-bootloader...
OKAY [ 0.020s]
sending 'boot' (4944 KB)...
OKAY [ 0.610s]
writing 'boot'...
OKAY [ 0.160s]
sending 'recovery' (5446 KB)...
OKAY [ 0.670s]
writing 'recovery'...
OKAY [ 0.180s]
erasing 'system'...
OKAY [ 0.020s]
sending 'system' (471804 KB)...
OKAY [ 55.586s]
writing 'system'...
OKAY [ 20.822s]
erasing 'userdata'...
OKAY [ 0.030s]
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 bloc
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 24.063s]
erasing 'cache'...
OKAY [ 0.010s]
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.580s]
rebooting...
finished. total time: 103.951s
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...
I used the same stock rom I am using so I ddn't have to flash the bootloader which is an issue (see above).
I can't see any errors in that terminal, everything looks fine but when the tablet reboots it has not changed a single thing!! Multirom is still there as it was and my old rom and userdata and everything down to the crappy wallpaper I put on 8 months ago is still there!!
Can anyone PLEASE HELP!!!
So what do you want to do? Get rid of the multirom and get back to stock? If so do you care about your data?
kilometers4 said:
So what do you want to do? Get rid of the multirom and get back to stock? If so do you care about your data?
Click to expand...
Click to collapse
Exactly that! Don't care about data, just want a stock working image.
I'm having the exact same issue. Tablet reboots after 5 seconds after the lock screen loads so I thought I'd erase user data and re flash the rom. Except that it doesn't actually flash, or erase anything. I've tried toolkits and fastboot. And the log always says the flash has performed successfully but it always reboots to the same old rom, wallpaper, all data still intact.
It's almost like the partitions are write protected and won't allow any data changes.
If anyone can help with this issue, I'll double the free beer offer!
Sent from my iPhone using Tapatalk
mattsolberg said:
I'm having the exact same issue. Tablet reboots after 5 seconds after the lock screen loads so I thought I'd erase user data and re flash the rom. Except that it doesn't actually flash, or erase anything. I've tried toolkits and fastboot. And the log always says the flash has performed successfully but it always reboots to the same old rom, wallpaper, all data still intact.
It's almost like the partitions are write protected and won't allow any data changes.
If anyone can help with this issue, I'll double the free beer offer!
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Can I just ask, are you using multirom aswell? Your the only other person I've heard of with the problem, we should go more notes and try and narrow this down.
No multi-rom. I've found about a half dozen other threads with people experiencing the same thing. It's rare, but it's not just me. Being completely unable to wipe data has me thinking there might be a hardware issue at play.
I'll post links to some of the other threads. Thanks for offering to help. I'm willing to try anything at this point.
Sent from my iPhone using Tapatalk
---------- Post added at 01:00 PM ---------- Previous post was at 12:57 PM ----------
Four other threads describing the exact same problem:
http://forum.xda-developers.com/showthread.php?t=2588911
http://forum.xda-developers.com/showthread.php?t=2585440
http://forum.xda-developers.com/showthread.php?t=2514148
http://forum.xda-developers.com/showthread.php?t=1781250
Sent from my iPhone using Tapatalk
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
Infinite reboot problem
I need help, my nexus has been continously rebooting by itself. It starts, goes to my homescreen for a few seconds and reboots. I can boot in the bootloader and have tried to do a factory reset, but it just stays a long time in formatting data. After waiting a complete day I decided to stop the process and start again my tablet. It just went to my home screen and again it kept rebooting. It didn't wipe anything.
Next I tried to fastboot flash a stock image, it never gave me any kind of error. My tablet rebooted, but it just went to my home screen, and clearly the image wasn't installed. And again it started the rebooting process.
C:\Users\Username\Downloads\fastboot>fastboot flash bootloader bootloader-manta-mantamf01.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.156s]
writing 'bootloader'...
OKAY [ 0.203s]
finished. total time: 0.359s
C:\Users\Username\Downloads\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Username\Downloads\fastboot>fastboot -w update image-mantaray-lmy48x.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 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...: MANTAMF01
Baseband Version.....: no modem
Serial Number........: R32CB03FJ1P
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ -0.000s]
sending 'boot' (4982 KB)...
OKAY [ 0.626s]
writing 'boot'...
OKAY [ 0.016s]
sending 'recovery' (5548 KB)...
OKAY [ 0.688s]
writing 'recovery'...
OKAY [ 0.016s]
erasing 'system'...
OKAY [ 0.016s]
sending 'system' (656930 KB)...
OKAY [ 80.289s]
writing 'system'...
OKAY [ 5.318s]
erasing 'userdata'...
OKAY [ 0.020s]
sending 'userdata' (139141 KB)...
OKAY [ 16.687s]
writing 'userdata'...
OKAY [ 1.162s]
erasing 'cache'...
OKAY [ 0.016s]
sending 'cache' (10372 KB)...
OKAY [ 1.266s]
writing 'cache'...
OKAY [ 0.094s]
rebooting...
finished. total time: 106.464s
Click to expand...
Click to collapse
Also, I tried to re-lock the bootloader with fastboot oem lock, it said Ok, but the status didn't change (I have a warranty and I think is time to use it, but I need to lock the bootloader). Thanks in advance for your help.
C:\Users\Username\Downloads\fastboot>fastboot oem lock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Click to expand...
Click to collapse
Uldar said:
I need help, my nexus has been continously rebooting by itself. It starts, goes to my homescreen for a few seconds and reboots. I can boot in the bootloader and have tried to do a factory reset, but it just stays a long time in formatting data. After waiting a complete day I decided to stop the process and start again my tablet. It just went to my home screen and again it kept rebooting. It didn't wipe anything.
Next I tried to fastboot flash a stock image, it never gave me any kind of error. My tablet rebooted, but it just went to my home screen, and clearly the image wasn't installed. And again it started the rebooting process.
Also, I tried to re-lock the bootloader with fastboot oem lock, it said Ok, but the status didn't change (I have a 3 year warranty that will expire this december, and I think is time to use it, but I need to lock the bootloader). Thanks in advance for your help.
Click to expand...
Click to collapse
Hello, did you try to boot on a custom recovery ?
fastboot boot recovery x.img will work.
From there you might try formatting / installing a custom rom.
Khaon said:
Hello, did you try to boot on a custom recovery ?
fastboot boot recovery x.img will work.
From there you might try formatting / installing a custom rom.
Click to expand...
Click to collapse
Yeah, I tried to do a factory reset with twrp, but it didn't work. It stays a long time in formatting cache using make_ext4fs function and doesn't make any progress. I left it like that for 6 hours after I decided to finish the process. It started again, went to my homescreen and kept rebooting.
Uldar said:
[/HIDE]
Yeah, I tried to do a factory reset with twrp, but it didn't work. It stays a long time in formatting cache using make_ext4fs function and doesn't make any progress. I left it like that for 6 hours after I decided to finish the process. It started again, went to my homescreen and kept rebooting.
Click to expand...
Click to collapse
What is the output of " adb shell dmesg" when you are inside the recovery mode ?
Seems that most likey your eMMC is dead.
timed out sending SET_BLOCK_COUNT command, card status 0x400d00
Click to expand...
Click to collapse
You could try formatting with f2fs but fi you already tried unlock/lock I don't think it will helpas it erase the whole storage.
Khaon said:
Seems that most likey your eMMC is dead.
You could try formatting with f2fs but fi you already tried unlock/lock I don't think it will helpas it erase the whole storage.
Click to expand...
Click to collapse
Thanks a lot for your help, I'm going to send it under warranty and see if they can fix it. I hope they don't reject it because the bootloader is unlocked.
PIT files
My nexus 10 has the boot loop problem and I think I have been left with the only option of Re-Partition but I need the PIT file. Can anybody help or provide this file?
I have tried everything else (fastboot, adb, temporary custom recoveries, Nexus Root Toolkit) with no success.