I'm going to post here to see if i can get any feedback.
mpgrimm2 said:
Well as I always say, I am not a developer or play one on TV...
My N5 locked up on me the other day after a call. I was on 5.1.1. LMY48B, basic stock with root going on a month or so since the 5.1.1 update which I did via full flash Method 2 originally (as all my updates).
- Phone stops at the "Google" screen.
- I can get to Fastboot, and I can get to factory recovery.
- I am lucky if I can get it to turn on at all so I can get to Fastboot screen; and when it locks, it takes a bit of a miracle to get it to turn off.
- I have been able to reflash the factory images from Post 1 with LMY48B 2x and went back and tried LMY47D for giggles. Same results.
It seems like something is corrupt with my /boot perhaps. Not sure if I should try a fastboot erase on all the partitions (EDIT: Tried that from post 2, no change) or if anyone has any other suggestions.
Click to expand...
Click to collapse
Edit:
As a last ditch i even tried WugFresh's N5 Toolkit just to see if it would somehow do something different on a stock reload. (LMY48B now)
Nope. No change.
Comes to a dead stop at the Google logo and just gets hot if i leave it there.
Really hoping someone knows something else to try so i can tuck the LG G4 away as a spare and get my N5 back.
Sent from my LG G4 on Tapatalk.
Bump.
Sent from my LG G4 on Tapatalk.
You have wiped data haven't you while trying this?
Sent from my Nexus 5 using Tapatalk
Ben36 said:
You have wiped data haven't you while trying this?
Click to expand...
Click to collapse
Yes. (I left out some of the details for C:/ .... boot.img etc below)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ...
fastboot reboot-bootloader ...
fastboot flash radio ...
fastboot reboot-bootloader ...
fastboot flash system ...
fastboot flash userdata ...
fastboot flash boot ...
fastboot flash recovery ...
Do you have a working nandroid backup to restore?
Did you try to format /cache instead of erasing it?
Primokorn said:
Do you have a working nandroid backup to restore?
Did you try to format /cache instead of erasing it?
Click to expand...
Click to collapse
I do have a backup on my pc. I can get to the bootloader, and run fastboot, load twrp but the backup still doesn't boot.
Tried flashing a zip of M preview2 someone put together with TWRP 2.8.7.1 . It hangs during install and phone shuts off.
* I don't think a format command has been done unless it was part of the factory image's script during during install.
I'm going to have to look up the syntax for a "fastboot format" after work unless you know it off hand? I assume its similar to the erase command.
Sent from my LG G4 on Tapatalk.
mpgrimm2 said:
I do have a backup on my pc. I can get to the bootloader, and run fastboot, load twrp but the backup still doesn't boot.
Tried flashing a zip of M preview2 someone put together with TWRP 2.8.7.1 . It hangs during install and phone shuts off.
* I don't think a format command has been done unless it was part of the factory image's script during during install.
I'm going to have to look up the syntax for a "fastboot format" after work unless you know it off hand? I assume its similar to the erase command.
Sent from my LG G4 on Tapatalk.
Click to expand...
Click to collapse
Yes, the same: fastboot format cache
Maybe you should add fastboot format userdata.
Primokorn said:
Yes, the same: fastboot format cache
Maybe you should add fastboot format userdata.
Click to expand...
Click to collapse
Well I did a format of: System, Userdata, & cache ... and an erase on the eMMC partitions (boot & recovery).
Code:
C:\Android\WorkingFlashFolder>fastboot format boot
Formatting is not supported for filesystem with type 'emmc'.
C:\Android\WorkingFlashFolder>fastboot format system
Creating filesystem with parameters:
Size: 1073741824
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 4096
Label:
Blocks: 262144
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/65536 inodes and 8536/262144 blocks
error: file_write: write: Bad file descriptor
Cannot read image.
erasing 'system'...
OKAY [ 1.320s]
finished. total time: 1.320s
C:\Android\WorkingFlashFolder>fastboot format cache
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
error: file_write: write: Bad file descriptor
Cannot read image.
erasing 'cache'...
OKAY [ 0.800s]
finished. total time: 0.800s
C:\Android\WorkingFlashFolder>fastboot format userdata
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
error: file_write: write: Bad file descriptor
Cannot read image.
erasing 'userdata'...
OKAY [ 7.970s]
finished. total time: 7.970s
C:\Android\WorkingFlashFolder>fastboot erase boot
erasing 'boot'...
OKAY [ 0.220s]
finished. total time: 0.230s
C:\Android\WorkingFlashFolder>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.230s]
finished. total time: 0.230s
Followed by a full load of the google factory images for LMY48B. Still hangs at the "Google" logo like something is corrupted in /boot or /aboot somehow? I'm not sure if there is anyway to actually delete/recreate the partitions on the N5 to get it to work. Still open to ideas.
Here is my "getvar" command output if its needed...
Code:
C:\Android\WorkingFlashFolder>fastboot getvar all
(bootloader) max-download-size: 0x40000000
(bootloader) version-hardware: rev_11
(bootloader) version-baseband: M8974A-2.0.50.2.26
(bootloader) version-bootloader: HHZ12h
(bootloader) version-cdma: N/A
(bootloader) variant: hammerhead D820(H) 16GB
(bootloader) serialno: EDITED
(bootloader) carrier: None
(bootloader) secure-boot: yes
(bootloader) unlocked: yes
(bootloader) product: hammerhead
(bootloader) partition-size:aboot: 80000
(bootloader) partition-type:aboot: emmc
(bootloader) partition-size:boot: 1600000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:recovery: 1600000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:system: 40000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:userdata: 3321fa800
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 2bc00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:persist: 1000000
(bootloader) partition-type:persist: ext4
I ran out of ideas mate... Almost everyone in a similar situation had to send their device to Google.
I keep searching and come back to you if I find something useful.
Best of luck!
Bump. Tried latest LMY48i, still mostly dead.
It's clear to me that something is missing B/w the bootloader and the OS loader.
Open to ideas from some more knowledgeable folks, especially since I have had a few PM's from others in the same situation.
Sent from my LG G4 on Tapatalk.
Look here http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632 you might have a corrupt persist partition.
Do you have usb debugging on?
Can you reach the phone with adb? (try "adb devices" command and see if it recognizes your phone).
Are you rooted?
I have the same problem, i have tried the persist solution but it does not work. it keep rebooting and its not the power button. thx for your help in adavnce.
eross said:
Look here http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632 you might have a corrupt persist partition.
Do you have usb debugging on?
Can you reach the phone with adb? (try "adb devices" command and see if it recognizes your phone).
Are you rooted?
Click to expand...
Click to collapse
Thanks for taking a look and sorry for the delay, my PC died Friday.
Yes I have taken a look at that thread hoping it would help. Unfortunately, no version of android back to the original release for my Nexus 5 will boot properly (req'd for the Persist T/S) to get past the Google logo which also prevents the use of ADB commands.
Fastboot/bootloader can be accessed (with difficulty) to reload the OS from the factory images, but always with the same result. No Go.
Related
Update 11/19/13: I contacted Google and as they sent me a new n5, my old one is now on it's way "home".
I'll update again in case they don't accept it bc of my unlocked bootloader and custom recovery.
Thanks for everyone who tried to help!
What I know so far:
- Flashing Google's factory image does not change anything
- I have access to ADB and fastboot
- fastboot oem lock will be reverted after reboot
- fastboot flash recovery recovery.img succeeds, but as I boot to recovery there will always be twrp 2.6.3.0
- twrp keeps asking me for a password
- I can pull and push files, however all changes made seem to revert as I reboot
- I can't flash zip or factory reset through recovery
- I can't mount internal storage, cache, persist (only system)
- My phone will somehow boot to the welcome screen, but give me permanent fc's, I reached the settings once
- The guides on going back to stock etc succeed (in cmd), but actually it feels like no changes are beeing made
I will provide you any information you need, as long as you tell me how to get it.
Hey, when I woke up this morning, my nexus was stuck on a boot loop.
I followed this guide: http://forum.xda-developers.com/showthread.php?t=2513701 but it didn't fix my issue. Also, my device would still have TWRP instead of stock recovery (even tried to flash cwm). TWRP can't mount data or cache, can't factory reset and keeps asking me for a password.
When I boot my device (to the welcome, choose language screen) it will only show me all kinds of force closes.
As I set it up, it will tell me my storage is full (at 0mb).
Edit: SuperSU was running after setting up.
I hope that someone has an idea on how to fix my issue..
Click to expand...
Click to collapse
here is my dmesg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If at least I could get rid of TWRP in order to RMA..
fastboot flash recovery recovery.img succeeds, but as I start recovery, it still is twrp
George_Mn said:
If at least I could get rid of TWRP in order to RMA..
fastboot flash recovery recovery.img succeeds, but as I start recovery, it still is twrp
Click to expand...
Click to collapse
Is the recovery.img the stock recovery or it's It twrp?
jd1639 said:
Is the recovery.img the stock recovery or it's It twrp?
Click to expand...
Click to collapse
it is the stock recovery.
I really don't like it when ppl push their own threads, but as mine went to page 3 without any attempt to help me, I feel like pushing.
Something messed up my partitions and i have no clue how to solve it. Could it be twrp? When I try to decrypt data it asks me for a password I dont have!
Try cwm twrp has done that to the nexus 7 a few times since 2.5 or so
Sent from my Nexus 5 using Tapatalk
George_Mn said:
Hey, when I woke up this morning, my nexus was stuck on a boot loop.
I followed this guide: http://forum.xda-developers.com/showthread.php?t=2513701 but it didn't fix my issue. Also, my device would still have TWRP instead of stock recovery (even tried to flash cwm). TWRP can't mount data or cache, can't factory reset and keeps asking me for a password.
When I boot my device (to the welcome, choose language screen) it will only show me all kinds of force closes.
As I set it up, it will tell me my storage is full (at 0mb).
Edit: SuperSU was running after setting up.
I hope that someone has an idea on how to fix my issue..
Click to expand...
Click to collapse
I had the same issue.
I fixed it by booting into fastboot, doing a bootloader lock and then a bootloader unlock. All your data gets wiped and the storage gets formated.
But it worked for me and was worth the data loss
Harry GT-S5830 said:
Try cwm twrp has done that to the nexus 7 a few times since 2.5 or so
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I can't. When flashing any other then twrp, upon booting recovery it still shows twrp.
maaximal said:
I had the same issue.
I fixed it by booting into fastboot, doing a bootloader lock and then a bootloader unlock. All your data gets wiped and the storage gets formated.
But it worked for me and was worth the data loss
Click to expand...
Click to collapse
I already locked and unlocked once, but I will try again.
George_Mn said:
I already locked and unlocked once, but I will try again.
Click to expand...
Click to collapse
After that use the stock image flash-all.bat/.sh from the google factory tgz (https://developers.google.com/android/nexus/images?hl=us#hammerhead)
bump
Try this. Download the factory image if you haven't done so already: https://developers.google.com/android/nexus/images#hammerhead and extract it down to the images.
Boot into the bootloader and use these commands:
Code:
fastboot format boot
fastboot format cache
fastboot format recovery
fastboot format system
fastboot format userdata
Then run the flash-all.bat
Report back.
El Daddy said:
Try this. Download the factory image if you haven't done so already: https://developers.google.com/android/nexus/images#hammerhead and extract it down to the images.
Boot into the bootloader and use these commands:
Code:
fastboot format boot
fastboot format cache
fastboot format recovery
fastboot format system
fastboot format userdata
Then run the flash-all.bat
Report back.
Click to expand...
Click to collapse
Unfortunately this didn't change anything, also still on twrp. edit: internal storage also still at 0mb.
Code:
E:\Users\George_Mn\Desktop\tools>fastboot format boot
formatting 'boot' partition...
Formatting is not supported for filesystem with type 'emmc'.
FAILED ()
finished. total time: 0.101s
E:\Users\George_Mn\Desktop\tools>fastboot format cache
erasing 'cache'...
OKAY [ 0.217s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 1.883s]
finished. total time: 2.103s
E:\Users\George_Mn\Desktop\tools>fastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'emmc'.
FAILED ()
finished. total time: 0.105s
E:\Users\George_Mn\Desktop\tools>fastboot format system
erasing 'system'...
OKAY [ 0.213s]
formatting 'system' partition...
Creating filesystem with parameters:
Size: 1073741824
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 4096
Label:
Blocks: 262144
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/65536 inodes and 8536/262144 blocks
sending 'system' (18800 KB)...
writing 'system'...
OKAY [ 2.400s]
finished. total time: 2.616s
E:\Users\George_Mn\Desktop\tools>fastboot format userdata
erasing 'userdata'...
OKAY [ 0.491s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
sending 'userdata' (137318 KB)...
writing 'userdata'...
OKAY [ 14.469s]
finished. total time: 14.964s
Code:
sending 'bootloader' (2506 KB)...
OKAY [ 0.283s]
writing 'bootloader'...
OKAY [ 0.401s]
finished. total time: 0.688s
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.096s
sending 'radio' (42033 KB)...
OKAY [ 1.467s]
writing 'radio'...
OKAY [ 2.847s]
finished. total time: 4.317s
rebooting into bootloader...
OKAY [ 0.089s]
finished. total time: 0.090s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11d
Baseband Version.....: M8974A-1.0.25.0.17
Serial Number........: 032ac31c08e6b033
--------------------------------------------
checking product...
OKAY [ 0.101s]
checking version-bootloader...
OKAY [ 0.098s]
checking version-baseband...
OKAY [ 0.098s]
sending 'boot' (8620 KB)...
OKAY [ 0.488s]
writing 'boot'...
OKAY [ 0.726s]
sending 'recovery' (9202 KB)...
OKAY [ 0.541s]
writing 'recovery'...
OKAY [ 0.763s]
erasing 'system'...
OKAY [ 0.254s]
sending 'system' (692940 KB)...
OKAY [ 22.651s]
writing 'system'...
OKAY [ 44.442s]
erasing 'userdata'...
OKAY [ 0.509s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
sending 'userdata' (137318 KB)...
writing 'userdata'...
OKAY [ 14.418s]
erasing 'cache'...
OKAY [ 0.241s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 1.871s]
rebooting...
finished. total time: 87.765s
Press any key to exit...
Hmmmm. Alright try 'fastboot erase recovery' instead.
Then just flash the recovery.img.
'fastboot flash recovery recovery.img'
Sent from my Nexus 5 using Tapatalk
El Daddy said:
Hmmmm. Alright try 'fastboot erase recovery' instead.
Then just flash the recovery.img.
'fastboot flash recovery recovery.img'
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
actually tried that right after the first attempt. no luck.
I've found some similar cases around xda. Specifically with the N7. When twrp asks for a password can you hit "back" to get to the menu where you are able to factory reset?
Maybe @efrant has an idea. He's pretty good with this stuff.
Sent from my Nexus 5 using Tapatalk
El Daddy said:
I've found some similar cases around xda. Specifically with the N7. When twrp asks for a password can you hit "back" to get to the menu where you are able to factory reset?
Maybe @efrant has an idea. He's pretty good with this stuff.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I can hit cancel but factory reset fails.
Code:
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/persist'
E:Unable to mount storage.
E:Unable to mount '/cache'
E:Unable to mount '/cache'
Formatting Cache using make_ext4fs function.
E:Unable to mount '/cache'
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/persist'
E:Unable to mount storage.
also, on the mount menu, there is an option to decrypt data which asks me for the password.
You didn't happen to flash a recovery or boot image that was for a device other than the N5 did you? I think that would be one cause of what you are seeing.
There is still a way to recover the device by flash the stock TOT file in download mode.
Let me see if I can find the right DLL for the N5, and I'll post in this thread.
George_Mn said:
I can hit cancel but factory reset fails.
Code:
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/persist'
E:Unable to mount storage.
E:Unable to mount '/cache'
E:Unable to mount '/cache'
Formatting Cache using make_ext4fs function.
E:Unable to mount '/cache'
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/persist'
E:Unable to mount storage.
also, on the mount menu, there is an option to decrypt data which asks me for the password.
Click to expand...
Click to collapse
It's asking you for a password because you didn't boot into android after flashing TWRP. For some reason, you cannot boot directly into TWRP right after any wipe (of userdata) without booting into Android first. It causes issues.
Hello,
I recently got my hands on a bricked TF700 and I'm trying to unbrick it, with no luck.
Onto the details:
- bootloader version 10.6.1.14.10
- bought in France
- the tablet is stuck on a bootloop, splash screen, loading animation (the spinner) and reboot after 2 or 3 seconds of spinning
- I can access the bootloader, but I when I try to update the firmware via recovery, the operation show a progress bar for about 10 seconds, then reboot, and bootloop again.
Regarding the firmware update, I tried with "WW_epaduser10_6_1_14_10_UpdateLauncher.zip" then with "TF700T_WW_epaduser_V1061144UpdateLauncher.zip", unzipping the content, renaming the contained file to "EP201_768_SDUPDATE.zip", moved it to a formatted-for-the-occasion-using-fat32 microsd card
Any ideas how to investigate this further ?
More details:
Code:
#> fastboot getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 015d3fb62730160a
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: yes
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006c6e80000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.094s
Output regarding the microSD partition:
Code:
#> file -s /dev/sdb1
/dev/sdb1: DOS/MBR boot sector, code offset 0x58+2, OEM-ID "mkfs.fat", sectors/cluster 16, Media descriptor 0xf8, sectors/track 32, heads 64, hidden sectors 2048, sectors 31289344 (volumes > 32 MB) , FAT (32 bit), sectors/FAT 15264, reserved 0x1, serial number 0x62a7d02b, unlabeled
papylhomme said:
Hello,
I recently got my hands on a bricked TF700 and I'm trying to unbrick it, with no luck.
Onto the details:
- bootloader version 10.6.1.14.10
- bought in France
- the tablet is stuck on a bootloop, splash screen, loading animation (the spinner) and reboot after 2 or 3 seconds of spinning
- I can access the bootloader, but I when I try to update the firmware via recovery, the operation show a progress bar for about 10 seconds, then reboot, and bootloop again.
Regarding the firmware update, I tried with "WW_epaduser10_6_1_14_10_UpdateLauncher.zip" then with "TF700T_WW_epaduser_V1061144UpdateLauncher.zip", unzipping the content, renaming the contained file to "EP201_768_SDUPDATE.zip", moved it to a formatted-for-the-occasion-using-fat32 microsd card
Any ideas how to investigate this further ?
More details:
Code:
#> fastboot getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 015d3fb62730160a
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: yes
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006c6e80000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.094s
Output regarding the microSD partition:
Code:
#> file -s /dev/sdb1
/dev/sdb1: DOS/MBR boot sector, code offset 0x58+2, OEM-ID "mkfs.fat", sectors/cluster 16, Media descriptor 0xf8, sectors/track 32, heads 64, hidden sectors 2048, sectors 31289344 (volumes > 32 MB) , FAT (32 bit), sectors/FAT 15264, reserved 0x1, serial number 0x62a7d02b, unlabeled
Click to expand...
Click to collapse
Most likely that your device has a /data corruption. If you don't have anything to save for your personal stuffs. Then you can erase your /data partition and it should be up and running. I don't know enough to fix the issue that you described above. Otherwise, you can wait for some experts here to give some suggestions without erasing your data, good luck....:fingers-crossed:
Thanks for the feedback !
So I tried various things related to the idea I was experiencing data corruption:
Wipe Data command from the bootloader: it doesn't changed anything.
Erasing the data partition using fastboot erase userdata: the command doesn't return (see below), bootloop on reboot
Erasing the cache and system partition using fastboot erase cache|system: the command doesn't return (see below), bootloop on reboot
Formatting the partitions using fastboot format userdata|cache|system: formatting "seems" to succed, then stuck on erasing the partition
Formatting the system partition gave slightly different results: erasing was ok, then the command sent an image (I don't know where it came from), and the command get stuck on writing 'system'....
After that one, I'm still able to enter the bootloader, but no more bootloop, the tablet is stuck at the first splash screen, no more loading spinner.
Code:
#> fastboot format cache
Creating filesystem with parameters:
Size: 448790528
Block size: 4096
Blocks per group: 32768
Inodes per group: 6848
Inode size: 256
Journal blocks: 1712
Label:
Blocks: 109568
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27392 inodes and 3534/109568 blocks
erasing 'cache'...
Code:
#> fastboot format userdata
Creating filesystem with parameters:
Size: 29106896896
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7106176
Block groups: 217
Reserved block group size: 1024
Created filesystem with 11/1777664 inodes and 155606/7106176 blocks
erasing 'userdata'...
Code:
#> fastboot format system
Creating filesystem with parameters:
Size: 805306368
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 3072
Label:
Blocks: 196608
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/49152 inodes and 6355/196608 blocks
erasing 'system'...
OKAY [ 0.175s]
sending 'system' (14616 KB)...
OKAY [ 10.972s]
writing 'system'...
papylhomme said:
Thanks for the feedback !
So I tried various things related to the idea I was experiencing data corruption:
Wipe Data command from the bootloader: it doesn't changed anything.
Erasing the data partition using fastboot erase userdata: the command doesn't return (see below), bootloop on reboot
Erasing the cache and system partition using fastboot erase cache|system: the command doesn't return (see below), bootloop on reboot
Formatting the partitions using fastboot format userdata|cache|system: formatting "seems" to succed, then stuck on erasing the partition
Formatting the system partition gave slightly different results: erasing was ok, then the command sent an image (I don't know where it came from), and the command get stuck on writing 'system'....
After that one, I'm still able to enter the bootloader, but no more bootloop, the tablet is stuck at the first splash screen, no more loading spinner.
Code:
#> fastboot format cache
Creating filesystem with parameters:
Size: 448790528
Block size: 4096
Blocks per group: 32768
Inodes per group: 6848
Inode size: 256
Journal blocks: 1712
Label:
Blocks: 109568
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27392 inodes and 3534/109568 blocks
erasing 'cache'...
Code:
#> fastboot format userdata
Creating filesystem with parameters:
Size: 29106896896
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7106176
Block groups: 217
Reserved block group size: 1024
Created filesystem with 11/1777664 inodes and 155606/7106176 blocks
erasing 'userdata'...
Code:
#> fastboot format system
Creating filesystem with parameters:
Size: 805306368
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 3072
Label:
Blocks: 196608
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/49152 inodes and 6355/196608 blocks
erasing 'system'...
OKAY [ 0.175s]
sending 'system' (14616 KB)...
OKAY [ 10.972s]
writing 'system'...
Click to expand...
Click to collapse
You should have just erased your /data and /cache only, Not your /system... Is your device still stock or a locked bootloader? Do you have a stock firmware available? Do you still have adb? Try this cmd: "adb devices" while your system is trying to boot. Do you see any respond with this cmd? Please don't do anything else until someone give you some good instructions, good luck? :fingers-crossed:
hello dear members.
i force restarted my tf700 in the middle of twrp formatting internal memory.after reboot twrp showed 0mb memory so i rebooted again and twrp just started to loop.i erased recovery, boot,misc,cach,system,user with fastboot.
i have no twrp to use adb command for getting partition blob file.
my device can go to bootloader but when ever i try to flash twrp recovery.img or stock blob file i get these errors:
most of all this one comes:
FAILED (command write failed (No such device or address))
other errors:time out or data transfer error(unknown error)
fastboot devices shows my device in the list but i get the errors.
i also had to rewire my data cable to a new usb2 connector head because i can't find new cable for my tablet in my country.as i have seen in the diagram tf700 only uses usb2 for data connection.
is my device hard broken or can it be repaired?
is it the cable?
please help me.
thank you
sx57 said:
hello dear members.
i force restarted my tf700 in the middle of twrp formatting internal memory.after reboot twrp showed 0mb memory so i rebooted again and twrp just started to loop.i erased recovery, boot,misc,cach,system,user with fastboot.
i have no twrp to use adb command for getting partition blob file.
my device can go to bootloader but when ever i try to flash twrp recovery.img or stock blob file i get these errors:
most of all this one comes:
FAILED (command write failed (No such device or address))
other errors:time out or data transfer error(unknown error)
fastboot devices shows my device in the list but i get the errors.
i also had to rewire my data cable to a new usb2 connector head because i can't find new cable for my tablet in my country.as i have seen in the diagram tf700 only uses usb2 for data connection.
is my device hard broken or can it be repaired?
is it the cable?
please help me.
thank you
Click to expand...
Click to collapse
I don't think that your device is hardbrick?
Maybe not the cable either.
Do you know the difference between "erase" and "format"? The answer may fix your device. Good lucks.......:fingers-crossed:
The tablet us not hard bricked, but the cable could be a problem. Do all fastboot commands fail? Including: fastboot reboot, fastboot format userdata?
If yes either the cable is bad or you hot wrong drivers....
If you can fix the fastboot problem you can get the tablet back.
berndblb said:
The tablet us not hard bricked, but the cable could be a problem. Do all fastboot commands fail? Including: fastboot reboot, fastboot format userdata?
If yes either the cable is bad or you hot wrong drivers....
If you can fix the fastboot problem you can get the tablet back.
Click to expand...
Click to collapse
If you interrupted the format process, your partition tables are screwed so you need to fix the partitions before trying to flash new blobs.... It is just my guesses for this issue. I hope that the user above has the latest bootloader so he can use the format cmd in fastboot. I believed that some older bootloader did not support the format cmd in fastboot and forgot started fromm what version that it added the format cmd...
Cheers,
LMK
Thank you all for kindly helping me.
Not all fastboot command fail.for example it cheerfully erased my recovery! And other partitions.
Take a look at this log when I tried to format system:
Creating filesystem with parameters:
Size: 805306368
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 3072
Label:
Blocks: 196608
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/49152 inodes and 6355/196608 b
erasing 'system'...
OKAY [ 2.317s]
sending 'system' (14616 KB)...
OKAY [ 4.666s]
writing 'system'...
OKAY [ 1.373s]
finished. total time: 8.379s
C:\Program Files (x86)\Android\android-sdk\platform-tools
sh system blob
sending 'system' (800927 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.007s
C:\Program Files (x86)\Android\android-sdk\platform-tools
As you see after system format I still can’t flash stock blob or recovery.if format user data fails at sending user data (second step after erase)but formar system completes successfully.
Any ideas what to do or how repartition the my tablet.
update: i also noticed that after every successful format system my device hangs at bootloader an d becomes unknown device so i have to reboot into bootloader again.every try at system blob flash comes with the mentioned errors in my original post.
C:\Program Files (x86)\Android\an
ta
Creating filesystem with paramete
Size: 61415620608
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14994048
Block groups: 458
Reserved block group size: 10
Created filesystem with 11/375193
erasing 'userdata'...
OKAY [ 38.151s]
sending 'userdata' (141163 KB)...
FAILED (data transfer failure (Un
finished. total time: 43.192s
C:\Program Files (x86)\Android\an
ta
Creating filesystem with paramete
Size: 61415620608
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14994048
Block groups: 458
Reserved block group size: 10
Created filesystem with 11/375193
erasing 'userdata'...
OKAY [ 38.392s]
sending 'userdata' (141163 KB)...
FAILED (data transfer failure (Un
finished. total time: 43.436s
every format userdata fails but format system succeeds.cache partition can be formatted too.
fastboot getvar all reports my bootloader locked! it's wiered.
ootloader) version-bootloader: 1.0
ootloader) version-baseband: 2.0
ootloader) version: 0.4
ootloader) serialno: 015d29955b43f613
ootloader) mid: 001
ootloader) product: Cardhu
ootloader) secure: yes
ootloader) unlocked: no
ootloader) uart-on: yes
ootloader) partition-size:bootloader: 0x0000
ootloader) partition-type:bootloader: basic
ootloader) partition-size:recovery: 0x000000
ootloader) partition-type:recovery: basic
ootloader) partition-size:boot: 0x0000000000
ootloader) partition-type:boot: basic
ootloader) partition-size:system: 0x00000000
ootloader) partition-type:system: ext4
ootloader) partition-size:cache: 0x000000001
ootloader) partition-type:cache: ext4
ootloader) partition-size:userdata: 0x000000
ootloader) partition-type:userdata: ext4
l:
nished. total time: 0.237s
sx57 said:
fastboot getvar all reports my bootloader locked! it's wiered.
ootloader) version-bootloader: 1.0
ootloader) version-baseband: 2.0
ootloader) version: 0.4
ootloader) serialno: 015d29955b43f613
ootloader) mid: 001
ootloader) product: Cardhu
ootloader) secure: yes
ootloader) unlocked: no
ootloader) uart-on: yes
ootloader) partition-size:bootloader: 0x0000
ootloader) partition-type:bootloader: basic
ootloader) partition-size:recovery: 0x000000
ootloader) partition-type:recovery: basic
ootloader) partition-size:boot: 0x0000000000
ootloader) partition-type:boot: basic
ootloader) partition-size:system: 0x00000000
ootloader) partition-type:system: ext4
ootloader) partition-size:cache: 0x000000001
ootloader) partition-type:cache: ext4
ootloader) partition-size:userdata: 0x000000
ootloader) partition-type:userdata: ext4
l:
nished. total time: 0.237s
Click to expand...
Click to collapse
It is the first time that I hear that the bootloader is relocked.... Obviously, it is reported that your bootloader is still locked.
You are using the "erase" and "format" interchangeable in your posts above so I am confused which cmd that you used in the fastboot mode. Did you use this cmd in fastboot?
Code:
fastboot format userdata
If not, then you can give it a try to see what is going on after that, good luck....:fingers-crossed:
LetMeKnow said:
It is the first time that I hear that the bootloader is relocked.... Obviously, it is reported that your bootloader is still locked.
You are using the "erase" and "format" interchangeable in your posts above so I am confused which cmd that you used in the fastboot mode. Did you use this cmd in fastboot?
Code:
fastboot format userdata
If not, then you can give it a try to see what is going on after that, good luck....:fingers-crossed:
Click to expand...
Click to collapse
thanks for answering.yes i used format userdata and i sent the log for it.it always finished in these 3 errors
1-no such device or address.
2-data transfer error
3-timeout
format system works well
top left of my tf700screen us written key driver not found..booting os and the some version information.
if i select rck or android i get unrecoverable bootloader error (0x0000000)in red color.i have no system or recover so the error is related to that i believe.before erasing recover it worked go into twrp which started looping.
i use erase when i use erase command and i use format when i use format command.sorry for causing confusion mate.
LetMeKnow said:
It is the first time that I hear that the bootloader is relocked.... Obviously, it is reported that your bootloader is still locked.
Click to expand...
Click to collapse
No, I get the same return with getvar all. And I guarantee you - my bootloader is unlocked
We have to remember that fastboot is a very generic Android tool... doesn't work the same on all platforms..
Probably
Code:
(bootloader) uart-on: yes
is the more relevant entry here. "Unlocking the bootloader" on this device is nothing more than gaining the ability to flash partitions with files not signed by Asus. The BL is still encrypted and proprietary....
sx57 said:
thanks for answering.yes i used format userdata and i sent the log for it.it always finished in these 3 errors
1-no such device or address.
2-data transfer error
3-timeout
format system works well
top left of my tf700screen us written key driver not found..booting os and the some version information.
if i select rck or android i get unrecoverable bootloader error (0x0000000)in red color.i have no system or recover so the error is related to that i believe.before erasing recover it worked go into twrp which started looping.
i use erase when i use erase command and i use format when i use format command.sorry for causing confusion mate.
Click to expand...
Click to collapse
Sigh...
Unfortunately you cannot really rely on fastboot return messages. Especially if you're trying this on Win10!!!!!!!
I'm getting totally frustrated with this OS. I get a positive return for "fastboot devices" and then it does nothing for any subsequent command. Gives me a "finished" for "fastboot reboot" but the tablet never reboots. Basically it does not respond to any fastboot commands.
Until I boot the tablet into recovery. Try a few adb commands - everything works. Go "adb reboot-bootloader" to get into fastboot mode and all the sudden all fastboot commands work???????????????
So that together with your patched cable introduces enough ????? that it's almost impossible to isolate the cause.
But the only way I have seen people (many, many people) recover from an "unrecoverable bootloader error" is by flashing the stock blob in fastboot. You gotta get that working.....
If you've tried this on a USB 3.0 port, try a USB 2.0. Reboot the PC, reboot the tablet when switching ports.
If you can get your hands on Linux machine, try that. Or try this live CD: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Good luck!
berndblb said:
No, I get the same return with getvar all. And I guarantee you - my bootloader is unlocked
We have to remember that fastboot is a very generic Android tool... doesn't work the same on all platforms..
Probably
Code:
(bootloader) uart-on: yes
is the more relevant entry here. "Unlocking the bootloader" on this device is nothing more than gaining the ability to flash partitions with files not signed by Asus. The BL is still encrypted and proprietary....
Sigh...
Unfortunately you cannot really rely on fastboot return messages. Especially if you're trying this on Win10!!!!!!!
I'm getting totally frustrated with this OS. I get a positive return for "fastboot devices" and then it does nothing for any subsequent command. Gives me a "finished" for "fastboot reboot" but the tablet never reboots. Basically it does not respond to any fastboot commands.
Until I boot the tablet into recovery. Try a few adb commands - everything works. Go "adb reboot-bootloader" to get into fastboot mode and all the sudden all fastboot commands work???????????????
So that together with your patched cable introduces enough ????? that it's almost impossible to isolate the cause.
But the only way I have seen people (many, many people) recover from an "unrecoverable bootloader error" is by flashing the stock blob in fastboot. You gotta get that working.....
If you've tried this on a USB 3.0 port, try a USB 2.0. Reboot the PC, reboot the tablet when switching ports.
If you can get your hands on Linux machine, try that. Or try this live CD: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Good luck!
Click to expand...
Click to collapse
thank you very much for helping me.i am using win7 my frirnd.
I am gonna do what you kindly suggested to see if i get it working.i will try to get another cable from someone if any of my friends have one by chance.is there a command to see if bootloader is really still unlocked?
I will post the results but getting a cable is gonna take a few days if possible at all.in the meantime i will try other solutions.thank you all my friends.please post if any othetr solution comes to your mind.
Don't worry. There's no way to lock the tablet again unless through Asus.
Watch the screen when you turn it on. Even in this state it should say: The device is unlocked
hellooooooooooooooooo.my tablet is alive and the problem is finally solved.thank you all my friends specially berndblb. i finlally found and bought a new cable and after some problems with different PCs(errors same as i mentioned in my original post) i succeeded.
here are some points that i think need to be emphasized upon:
a direct usb port was necessary for me.it worked when the device was connected directly to my Iconia (windows pc tablet) w700's only usb 3 port.(usb 2 works but a direct port is needed,hubs make more problems.)
in windows XP fastboot was completely useless and didn't work and would just stuck on commands.(most probably needed another driver)
look here please :http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Buster99's excellent solution needed to be done step by step.i had to erase the mentioned partitions and only after that,blob file was flashed successfully.
thank you all for your help.
I was trying to install a custom recovery in moto e first gen. After the flashing of recovery it said that the recovery size mismatched and booting into recovery always showed "No Commands". Then i tried many threads from different forums and somehow have my recovery partition erased. Now When i try to flash a recovery it was not successful. Then i found that the recovery partition is missing in the memory. How do i add a recovery partition and add a custom recovery.
The device is unlocked and shows status code 3
When i try flashing this is the output
fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 299892736 bytes
sending 'recovery' (10280 KB)...
OKAY [ 0.385s]
writing 'recovery'...
OKAY [ 1.623s]
finished. total time: 2.010s
fastboot getvar recovery returns this
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) recovery: not found
getvar:recovery FAILED (remote failure)
finished. total time: 0.053s
This is the output from the shell when i checked for the partitions
[email protected]_umtsds:/ $ df
Filesystem Size Used Free Blksize
/dev 455.5M 292.0K 455.2M 4096
/sys/fs/cgroup 455.5M 12.0K 455.5M 4096
/mnt/asec 455.5M 0.0K 455.5M 4096
/mnt/obb 455.5M 0.0K 455.5M 4096
/system 881.9M 713.2M 168.7M 4096
/data 2.2G 1.1G 1.0G 4096
/cache 447.0M 7.5M 439.4M 4096
/persist 4.9M 4.1M 828.0K 4096
/firmware 62.4M 43.4M 19.1M 4096
/pds 1.9M 1.0M 920.0K 1024
/fsg 635.0K 634.0K 1.0K 1024
/mnt/shell/emulated 2.2G 1.1G 1.0G 4096
/storage/emulated/legacy 2.2G 1.1G 1.0G 4096
. Can anyone guide me to have my recovery back.
vijvin57 said:
I was trying to install a custom recovery in moto e first gen. After the flashing of recovery it said that the recovery size mismatched and booting into recovery always showed "No Commands". Then i tried many threads from different forums and somehow have my recovery partition erased. Now When i try to flash a recovery it was not successful. Then i found that the recovery partition is missing in the memory. How do i add a recovery partition and add a custom recovery.
The device is unlocked and shows status code 3
When i try flashing this is the output
fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 299892736 bytes
sending 'recovery' (10280 KB)...
OKAY [ 0.385s]
writing 'recovery'...
OKAY [ 1.623s]
finished. total time: 2.010s
fastboot getvar recovery returns this
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) recovery: not found
getvar:recovery FAILED (remote failure)
finished. total time: 0.053s
This is the output from the shell when i checked for the partitions
[email protected]_umtsds:/ $ df
Filesystem Size Used Free Blksize
/dev 455.5M 292.0K 455.2M 4096
/sys/fs/cgroup 455.5M 12.0K 455.5M 4096
/mnt/asec 455.5M 0.0K 455.5M 4096
/mnt/obb 455.5M 0.0K 455.5M 4096
/system 881.9M 713.2M 168.7M 4096
/data 2.2G 1.1G 1.0G 4096
/cache 447.0M 7.5M 439.4M 4096
/persist 4.9M 4.1M 828.0K 4096
/firmware 62.4M 43.4M 19.1M 4096
/pds 1.9M 1.0M 920.0K 1024
/fsg 635.0K 634.0K 1.0K 1024
/mnt/shell/emulated 2.2G 1.1G 1.0G 4096
/storage/emulated/legacy 2.2G 1.1G 1.0G 4096
. Can anyone guide me to have my recovery back.
Click to expand...
Click to collapse
Hello,
This
recovery size mismatched
Click to expand...
Click to collapse
is a known warning in Motorola devices.
Did you try to boot to recovery ?
Regards
Vatsal,
Forum Moderator.
Vatsal said:
Hello,
This is a known warning in Motorola devices.
Did you try to boot to recovery ?
Regards
Vatsal,
Forum Moderator.
Click to expand...
Click to collapse
Yes I did try to boot into recovery, but initially it was showing No Commands, then at some point it was showing the android dead icon. Now there is no recovery boot at all.
vijvin57 said:
Yes I did try to boot into recovery, but initially it was showing No Commands, then at some point it was showing the android dead icon. Now there is no recovery boot at all.
Click to expand...
Click to collapse
Hello,
Are you able to boot your device to fastboot?
Regards
Vatsal,
Forum Moderator.
Vatsal said:
Hello,
Are you able to boot your device to fastboot?
Regards
Vatsal,
Forum Moderator.
Click to expand...
Click to collapse
Sorry for the late reply, Yes, I am able to boot into the fastboot from adb as well as using the power and volume down buttons.
vijvin57 said:
Sorry for the late reply, Yes, I am able to boot into the fastboot from adb as well as using the power and volume down buttons.
Click to expand...
Click to collapse
Hello,
You may try reflashing stock firmware via fastboot.
Regards
Vatsal,
Forum Moderator.
Vatsal said:
Hello,
You may try reflashing stock firmware via fastboot.
Regards
Vatsal,
Forum Moderator.
Click to expand...
Click to collapse
I have re-flashed the stock firmware for moto e, But still the recovery partition doesn't exist, posting the phone info in attachment, Could you please confirm whether this is Stock firmware. If I have flashed the right firmware, what other option do i have
vijvin57 said:
I have re-flashed the stock firmware for moto e, But still the recovery partition doesn't exist, posting the phone info in attachment, Could you please confirm whether this is Stock firmware. If I have flashed the right firmware, what other option do i have
Click to expand...
Click to collapse
Hello,
It is correct firmware.
Why are you so curious about Recovery partition?
Regards
Vatsal,
Forum Moderator.
Vatsal said:
Hello,
It is correct firmware.
Why are you so curious about Recovery partition?
Regards
Vatsal,
Forum Moderator.
Click to expand...
Click to collapse
Hi Vatsal,
Nothing curious, I need to the recovery partition for installing some custom roms. I have seen that some Android N roms are available for moto e.Want to test it on my phone. If you can guide me to do that without the recovery that would be great.
vijvin57 said:
Hi Vatsal,
Nothing curious, I need to the recovery partition for installing some custom roms. I have seen that some Android N roms are available for moto e.Want to test it on my phone. If you can guide me to do that without the recovery that would be great.
Click to expand...
Click to collapse
Hello,
Please download the latest TWRP from here dl.twrp.me/condor
and fastboot it with this command
Code:
fastboot flash recovery <filename>.img
Regards
Vatsal,
Forum Moderator.
Vatsal said:
Hello,
Please download the latest TWRP from here dl.twrp.me/condor
and fastboot it with this command
Code:
fastboot flash recovery <filename>.img
Regards
Vatsal,
Forum Moderator.
Click to expand...
Click to collapse
Hi Vatsal,
Yes, I have already done the following steps and the result is in the first post where it says the recovery partition is missing. Any ways I tried again with the TWRP you have pointed to and the results are the same. My device now dont have a recovery partition to flash, That was and is my problem
Thanks
Vinod
Vatsal said:
Hello,
Please download the latest TWRP from here dl.twrp.me/condor
and fastboot it with this command
Code:
fastboot flash recovery <filename>.img
Regards
Vatsal,
Forum Moderator.
Click to expand...
Click to collapse
Hi Vatsal,
I had already done this, But I have tried it again with the twrp that you have pointed to. But the device shows the same screen as before, Not able to boot into recovery, When recovery is selected the device goes into a black screen and nothing comes up. Still the recovery partition is missing. Do we have any other option
Thanks
Vinod
Hi,
my Nexus 5 was plugged on my laptop.
After a while I saw, that my phone rebooted. I saw the google logo.
I pressed and hold the "Power Button".
My phone booted again and stuck in the booting animation.
This happened three days ago.
I tried so many things. It's not working.
Maybe I messed up the partition.
The first thing I tried was to flash the android factory image like this (Flashing instructions - don't forget to press the button "ACKNOWLEDGE"):
https://developers.google.com/android/images
I first thought, that maybe the eMMC is fried.
I checked this like this ( https://forum.xda-developers.com/showthread.php?t=1284196 ):
Code:
adb shell
dmesg | grep mmc0
I didn't get a message like this:
Code:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
I read, that I should change to usb 2.0 port and the usb cable.
I've also a Galaxy nexus. I've tried to flash a new stock with WugFresh. Everything worked with the usb 2.0 port and the usb cable.
When I tried to do that with my nexus 5 nothing works. I get this failure messages:
FAILED (remote: flash write failure)
I used TWRP (twrp-3.0.3-0-hammerhead.img) and clockwork mod (recovery-clockwork-touch-6.0.4.4-hammerhead.img).
The main errors I get:
Can't mount /data
...
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovers/log
E: Can't open /cache/recovers/log
...
I really don't know what to do.
Is there a method to build the partition new? Or what else can I do?
Thank you for any help.
Does the bootloader relock when rebooted after being unlocked? Have you tried flashing the stock KK ROM?
Yes. It relocks when rebooted.
Do you mean Kit Kat? No, I didn't. I've tried only the new versions like 6.0.1 (MOB31E), 6.0.1 (M4B30Z, Dec 2016).
I will try KK Rom later.
I've downloaded this factory image:
"hammerhead" for Nexus 5 (GSM/LTE)
4.4.4 (KTU84P)
from here: https://developers.google.com/android/images
This is the original "flash-all.bat" file:
Code:
@ECHO OFF
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-hammerhead-ktu84p.zip
echo Press any key to exit...
pause >nul
exit
I've changed the "flash-all.bat" a little bit. I added this line "fastboot oem unlock". When I not add "fastboot oem unlock", I get a message like "not unlocked":
Code:
@ECHO OFF
PATH=%PATH%;"%SYSTEMROOT%\System32"
[B]fastboot oem unlock[/B]
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
[B]fastboot oem unlock[/B]
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
fastboot reboot-bootloader
[B]fastboot oem unlock[/B]
ping -n 5 127.0.0.1 >nul
fastboot -w update image-hammerhead-ktu84p.zip
echo Press any key to exit...
pause >nul
exit
I've started the "flash-all.bat". This is the output:
Code:
target reported max download size of 1073741824 bytes
sending 'bootloader' (2508 KB)...
OKAY [ 0.203s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.406s
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
< waiting for any device >
...
OKAY [ 4.109s]
finished. total time: 4.109s
target reported max download size of 1073741824 bytes
sending 'radio' (45409 KB)...
OKAY [ 1.625s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.844s
rebooting into bootloader...
OKAY [ 0.109s]
finished. total time: 0.109s
< waiting for any device >
...
OKAY [ 6.250s]
finished. total time: 6.250s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
wiping userdata...
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
wiping cache...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
--------------------------------------------
Bootloader Version...: HHZ20f
Baseband Version.....: M8974A-2.0.50.2.29
Serial Number........: 04ae306b2524b05b
--------------------------------------------
checking product...
OKAY [ 0.109s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ20f'.
Update requires 'HHZ11k'.
finished. total time: 0.594s
Press any key to exit...
Before flashing again, unlock the bootloader and immediately reboot the phone into fastboot. Does the bootloader relock when the phone is rebooted? If yes, the memory chip is damaged.
audit13 said:
Before flashing again, unlock the bootloader and immediately reboot the phone into fastboot. Does the bootloader relock when the phone is rebooted? If yes, the memory chip is damaged.
Click to expand...
Click to collapse
I have the same problem and after doing that I can see that my eMMC is in fact fried since the bootloader relocks. I was wondering, where is the bootloader/fastboot stored on the device? On the CPU/GPU/RAM stack or on the eMMC. If I swap out the eMMC chip, will I still be able to access it (the bootloader) with a blank eMMC or is it on the eMMC as well? I'm trying to find out what are the steps to format and partition the eMMC after a new one is installed...
I don't know where the bootloader is located. When I determine that there is a problem with the memory chip, I just replace the motherboard.
audit13 said:
I don't know where the bootloader is located. When I determine that there is a problem with the memory chip, I just replace the motherboard.
Click to expand...
Click to collapse
Thank you very much for sharing your experience!
I would assume that the bootloader is located on the eMMC since I can't write to the bootloader (or any other) partition from fastboot. I'll have to look into solutions during the weekend since I don't have much time until then, but replacing the MB is a no go for me because of the price.
I'm not sure where you are located but I live in a big city in Canada where I can find deals for people selling Nexus 5 phones with smashed screens and working internal components.
Good luck and please share your results. Thanks.
@audit13: When I unlock the bootloader and then reboot the phone into fastboot. The bootloader relocks.
Is the memory chip now really damaged? Can't I do nothing? My N5 is three years old. I don't want to pay a lot of money for a main board.
The cheapest solution for a damaged emmc chip may be to buy a used Nexus 5 with a smashed screen and working motherboard. This is what I had to do for 2 phones with self re-locking bootloaders.
I bought a display damaged nexus 5. It arrived today. Changed the main board. And Voila! It's working.
The other guy has installed this build:
"hammerhead" for Nexus 5 (GSM/LTE)
6.0.1 (MOB30H)
No my question: Which factory image should I install?
https://developers.google.com/android/images
"hammerhead" for Nexus 5 (GSM/LTE)
...
6.0.1 (MOB30H)
6.0.1 (MOB30M)
6.0.1 (MOB30P)
6.0.1 (MOB30Y)
6.0.1 (MOB31E)
6.0.1 (M4B30X, Oct 2016)
6.0.1 (M4B30Z, Dec 2016)
I'm not sure, because the last two has dates. Are they meaning something (I mean, are they special builds), because the other factory images don't have dates.
Or should I do this:
https://developers.google.com/android/ota
OTA binary image files that allow you to manually update your Nexus or Pixel device. This has the same effect of flashing the corresponding factory images, but without the need of wiping the device.
"hammerhead" for Nexus 5 (GSM/LTE)
6.0.1 (M4B30Z)
Is OTA better than factory images?
OK. I've installed this version 6.0.1 (M4B30Z, Dec 2016). Everything works.