So i hard bricked my at&t Note 3 when i was in Odin. Looked like Odin froze so i unplugged it half way thru and tried to get back into download mode and NOTHING! Black screen ... can't get into download mode, power device on or nothing. Never bricked a device in all the years i've been rooting and tried everything. Unfortuantly, i still can't get this to work on Linux system and just want to know im doing things right. I placed the img on sd card and inserted it with thumb usb and that's fine. When i type in dmesg | tail i get this ...
[email protected] ~ $ dmesg | tail
[ 1548.786072] sd 10:0:0:0: [sdb] No Caching mode page found
[ 1548.786079] sd 10:0:0:0: [sdb] Assuming drive cache: write through
[ 1548.790452] sd 10:0:0:0: [sdb] No Caching mode page found
[ 1548.790461] sd 10:0:0:0: [sdb] Assuming drive cache: write through
[ 1548.791624] sdb: sdb1
[ 1548.794337] sd 10:0:0:0: [sdb] No Caching mode page found
[ 1548.794347] sd 10:0:0:0: [sdb] Assuming drive cache: write through
[ 1548.794355] sd 10:0:0:0: [sdb] Attached SCSI removable disk
[ 1549.170010] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 1956.468460] perf samples too long (2506 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
I know my card is sdb1 and tried typing in the rest of the commands. When i type in second command sudo dd if=/<path_to_debrick.img> of=/dev/sdX i get this ...
[email protected] ~ $ sudo dd if=/<path_to_debrick.img> of=/dev/sdb1
bash: path_to_debrick.img: No such file or directory
Really no idea what im doing to not get this work but i'm sure it's something simple. I just want to get back into download mode and then i'll be straight and can Odin my files to recover. Unfortuantely i can't get back in download mode!
Do i need MJ5 img since i was on MJ5 then did UNOFFICIAL KK update and was running DynamicKat when this happened?
Also i am using a SanDisk Elevate 32GB sdhc card on my 32 Note 3 so i know the cards not the problem. It's brand new and reads fine otherwise.
Please let me know if i'm doing anything wrong as i've been working on this for 48 hours and just need my phone back! lol
Thanks ... I really appreciate it!
I'm just going to bite my tongue on this one and help you.
"<path_to_debrick.img>" is just a place holder, you have to actually put the path of the debrick.img file you loaded onto your device, not <path_to_debrick.img>
SpikeyPsyche said:
I'm just going to bite my tongue on this one and help you.
"<path_to_debrick.img>" is just a place holder, you have to actually put the path of the debrick.img file you loaded onto your device, not <path_to_debrick.img>
Click to expand...
Click to collapse
Wow. That's all i have to say ... just wow! Atleast someone was able to "Bite their tongue" and let me know. Appreciate it. Will try again now. Thanks lol ... no words
SpikeyPsyche said:
I'm just going to bite my tongue on this one and help you.
"<path_to_debrick.img>" is just a place holder, you have to actually put the path of the debrick.img file you loaded onto your device, not <path_to_debrick.img>
Click to expand...
Click to collapse
Sent you a PM. Thanks again.
So i got the img to write onto sd card but still can't get into download mode when i hold the buttons. No signs of life still. This is what i got after i wrote the image
PaulMichael paul # dd if=/home/paul/Desktop/debrick/Unbrick_SM-N900A.img of=/dev/sdb1
400000+0 records in
400000+0 records out
204800000 bytes (205 MB) copied, 72.2845 s, 2.8 MB/s
PaulMichael paul # fdisk -l /dev/sdb1
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb1'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb1: 31.9 GB, 31910789120 bytes
1 heads, 32 sectors/track, 1947680 cylinders, total 62325760 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1p1 1 61071359 30535679+ ee GPT
Any help would be appreciated. I even tried it twice with no luck. Also my new 32gb sd card won't read now when i put it reader into usb. No pop up or anything? Thanks guys.
***Edited*** also i was on MJ5 then did the Unofficial "Jump from Jellybean to kk" ... which image would i need then? And if someone has it can they send it to me please!
Something didn't go right with the debrick image writing. That fdisk command should have listed all the partitions on that disk, with should be 20+, and you are only seeing one.
Re-run writing the debrick image. Sometimes it fails on the first few tries.
SpikeyPsyche said:
Something didn't go right with the debrick image writing. That fdisk command should have listed all the partitions on that disk, with should be 20+, and you are only seeing one.
Re-run writing the debrick image. Sometimes it fails on the first few tries.
Click to expand...
Click to collapse
Tried writing it a few times but will keep trying. Atleast now i know where to look for the partitions to see. Thanks again.
Yeag3r24 said:
Tried writing it a few times but will keep trying. Atleast now i know where to look for the partitions to see. Thanks again.
Click to expand...
Click to collapse
You're not inputting the command to write the image correctly.
The last part should be of=/dev/sdb NOT of=/dev/sdb1. Lose the 1
You really didn't read the hard debrick OPs instructions closely. he explicitly says to ignore the partition number, being the 1, because you are overwriting the current partitions.
Correcting that issue with the command should write the image correctly, and you should be good to go from there
SpikeyPsyche said:
You're not inputting the command to write the image correctly.
The last part should be of=/dev/sdb NOT of=/dev/sdb1. Lose the 1
You really didn't read the hard debrick OPs instructions closely. he explicitly says to ignore the partition number, being the 1, because you are overwriting the current partitions.
Correcting that issue with the command should write the image correctly, and you should be good to go from there.
Click to expand...
Click to collapse
Funny you said that because i did just rewrite it twice without the 1 just as sdb and when i unplugged it and plugged it back into usb i did recieve about 6 pop ups but were all sd card readers showing on my desktop like i had 6 different usb readers with different size sd cards some
Here's the correct screenshot of whole desktop. Also battery was 65% when this all happened but hasn't been used since in last 2 days of trying to fix it so see no need why the battery would be dead, correct? I could have phone on for 2 days and not touch it and wouldn't be dead. Would still be at about 40-50% i would assume if left on untouched for a few days. I just know i could do this and see no reason why this shouldn't work. Do i need the MJ5 img or something since i was on that with unofficial KK on dynamickat?
SS
Yeag3r24 said:
SS
Click to expand...
Click to collapse
It looks like one of the partitions isn't being written correctly on the SD card for some reason.
How many partitions is the fdisk command showing?
SpikeyPsyche said:
It looks like one of the partitions isn't being written correctly on the SD card for some reason.
How many partitions is the fdisk command showing?
Click to expand...
Click to collapse
PaulMichael paul # dd if=/home/paul/Desktop/debrick/Unbrick_SM-N900A.img of=/dev/sdb
400000+0 records in
400000+0 records out
204800000 bytes (205 MB) copied, 74.1923 s, 2.8 MB/s
PaulMichael paul # fdisk -l /dev/sdb
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb1: 31.9 GB, 31910789120 bytes
1 heads, 32 sectors/track, 1947680 cylinders, total 62325760 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1p1 1 61071359 30535679+ ee GPT
Yeag3r24 said:
PaulMichael paul # dd if=/home/paul/Desktop/debrick/Unbrick_SM-N900A.img of=/dev/sdb
400000+0 records in
400000+0 records out
204800000 bytes (205 MB) copied, 74.1923 s, 2.8 MB/s
PaulMichael paul # fdisk -l /dev/sdb
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb1: 31.9 GB, 31910789120 bytes
1 heads, 32 sectors/track, 1947680 cylinders, total 62325760 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1p1 1 61071359 30535679+ ee GPT
Click to expand...
Click to collapse
Now it's back to one partition again. Very strange.
SpikeyPsyche said:
Now it's back to one partition again. Very strange.
Click to expand...
Click to collapse
Well today must be my day. I called to get replacement phone and girl was real cool and said I could just pick one up here locally at the support center. Luckily dude at support center was just as cool and just pretty much swapped it right out without even trying another battery or doing tests. However when he put my battery in replacement Note i stilll had 65% so who knows wtf i did. Lesson learned ... never pull out early when Odin looks like it freezes for a few mins. Just in time for the official KK root now that I'm actually on Official KK stock rom. Thanks again for all your help. Much appreciated!
Yeag3r24 said:
Well today must be my day. I called to get replacement phone and girl was real cool and said I could just pick one up here locally at the support center. Luckily dude at support center was just as cool and just pretty much swapped it right out without even trying another battery or doing tests. However when he put my battery in replacement Note i stilll had 65% so who knows wtf i did. Lesson learned ... never pull out early when Odin looks like it freezes for a few mins. Just in time for the official KK root now that I'm actually on Official KK stock rom. Thanks again for all your help. Much appreciated!
Click to expand...
Click to collapse
No prob. I hope you have better luck in the future.
Please delete.
Sent from my SM-N900A using XDA Free mobile app
N900A 4.4.2, 32GB Unbrick HELP!!!
Yeag3r24 said:
Well today must be my day. I called to get replacement phone and girl was real cool and said I could just pick one up here locally at the support center. Luckily dude at support center was just as cool and just pretty much swapped it right out without even trying another battery or doing tests. However when he put my battery in replacement Note i stilll had 65% so who knows wtf i did. Lesson learned ... never pull out early when Odin looks like it freezes for a few mins. Just in time for the official KK root now that I'm actually on Official KK stock rom. Thanks again for all your help. Much appreciated!
Click to expand...
Click to collapse
Help !!!
I have a N900A, tried to unlock the phone and now is dead.
I would like to know how you solve your problem?
please i cant restore my device, i was using quantum rom with ak kernel, all was ok, i let my device run out of battery, when i put it to charge i was stuck in a bootloop. i go to twrp to restore my nandroid backups, i always get error "failed" on restoring data... these backups always worked fine!! then i wipe all the usual things (dãlvik, data, cache, system, even internal storage and format data) try to flash any rom and give me error:
***formatting system***
assert failed: format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system")
E:Error executing updater binary in zip ' /sdcard1/ROM NAME.zip
i really need to resolve this, its my work and personal phone. i have external sd card with roms and backups and access to bootloader screen and twrp, but cant flash anything!!
already tried stock recovering with adb fastboot but its not recognizing phone.. (i think usb debbuging was off if that matters). also tried fix permisions, and partition sd card in twrp, it gives me error: E:Unable to locate device to partition.
anyone?
i can flash small zips, but flashing roms always get me same error. fix permissions get me E:Unable to chmod error. partition sd card give me E:Unable to locate device to partition. restoring backups gives error also. help please
CPMAGMPC said:
i can flash small zips, but flashing roms always get me same error. fix permissions get me E:Unable to chmod error. partition sd card give me E:Unable to locate device to partition. restoring backups gives error also. help please
Click to expand...
Click to collapse
I think the partitions on your phone somehow got screwed.
Reinstall Stock, either KK or Lollipop via fastboot, that will reset the partitions to their proper state.
But keep in mind, by doing so, Internal Memory is going to be erased, but no the External SD Card.
i already tried that but i cant access with fast boot, it keeps me getting device not found.. so im stuck with twrp...also wiping data is not a problem because i already wiped all internal storage
SirRhor said:
I think the partitions on your phone somehow got screwed.
Reinstall Stock, either KK or Lollipop via fastboot, that will reset the partitions to their proper state.
But keep in mind, by doing so, Internal Memory is going to be erased, but no the External SD Card.
Click to expand...
Click to collapse
CPMAGMPC said:
i already tried that but i cant access with fast boot, it keeps me getting device not found.. so im stuck with twrp...also wiping data is not a problem because i already wiped all internal storage
Click to expand...
Click to collapse
If the device is not found is most likely because the Motorola drivers are not installed correctly, or not installed at all. So check that.
Reinstall the drivers, get into the bootloader and see if the device is recognized by Windows.
EDIT: Give me 10 minutes and I will send you the links of both installers for ABD that I use.
EDIT 2: Install both of these files:
https://www.dropbox.com/s/8dvpquv805r2rxi/Motorola%20Device%20Manager.exe?dl=0
https://www.dropbox.com/s/miyw2cu21ldyuwo/UniversalADBdriver.msi?dl=0
{
"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"
}
Uninstaled all driver from windows and installed yours. problem persists,device is not found maybe usb debbuging not active on the device? i searched google and cant find an option to enable it outside the rom settings, since i cannot boot...
SirRhor said:
If the device is not found is most likely because the Motorola drivers are not installed correctly, or not installed at all. So check that.
Reinstall the drivers, get into the bootloader and see if the device is recognized by Windows.
EDIT: Give me 10 minutes and I will send you the links of both installers for ABD that I use.
EDIT 2: Install both of these files:
https://www.dropbox.com/s/8dvpquv805r2rxi/Motorola%20Device%20Manager.exe?dl=0
https://www.dropbox.com/s/miyw2cu21ldyuwo/UniversalADBdriver.msi?dl=0
Click to expand...
Click to collapse
anyone as a solution? had this amazing device for 2 months only.. it was all good, tried all sort of amazing roms on this forum and now its dead... at least for now i hope.. i dont know if it helps but everytime i boot the phone or get in bootloader mode it keeps showing me quantum LP logo, even after i flashed titan prime or hyperdrive, but that was ok for a week or so till my device went out of juice.
also when i try to flash a cm 12.1 based rom phone reboots almost at finish not give me any error, when i flash other roms i get the error. when i flash addons or kernels i get success. wierd stuff
CPMAGMPC said:
anyone as a solution? had this amazing device for 2 months only.. it was all good, tried all sort of amazing roms on this forum and now its dead... at least for now i hope.. i dont know if it helps but everytime i boot the phone or get in bootloader mode it keeps showing me quantum LP logo, even after i flashed titan prime or hyperdrive, but that was ok for a week or so till my device went out of juice.
Click to expand...
Click to collapse
So you also have this problem, the same happened here. I am experiencing the same, but it seems impossible to solve :-\
Battery drained, device shutdown and afterwards partitions messed, no write operations possible.
Is your device encrypted, too?
Did you have an app pinned when the battery drained?
Here is another one on Reddit:
https://www.reddit.com/r/MotoG/comments/331wfs/moto_g_2014_bootloop/
I suspect this user has the same problem:
http://forum.xda-developers.com/moto-g-2014/help/factory-reset-t3075587
And I described the same here:
http://forum.xda-developers.com/moto-g-2014/help/factory-reset-t3075587
BTW: I need more than 10 minutes to solve those reCAPTCHAs here - this is ridiculous, did technology already surpass us?
mine wasnt encrypted. no apps pinned. i was taking shots in camera app when device shutdown at 0%. it seems that data partition is messed up, when i try to restore backups on other partitions i get success, not if i restore data. maybe there are some commands we can insert in twrp command line to solve this mess?
cxxxx said:
So you also have this problem, the same happened here. I am experiencing the same, but it seems impossible to solve :-\
Battery drained, device shutdown and afterwards partitions messed, no write operations possible.
Is your device encrypted, too?
Did you have an app pinned when the battery drained?
Here is another one on Reddit:
https://www.reddit.com/r/MotoG/comments/331wfs/moto_g_2014_bootloop/
I suspect this user has the same problem:
http://forum.xda-developers.com/moto-g-2014/help/factory-reset-t3075587
And I described the same here:
http://forum.xda-developers.com/moto-g-2014/help/factory-reset-t3075587
BTW: I need more than 10 minutes to solve those reCAPTCHAs here - this is ridiculous, did technology already surpass us?
Click to expand...
Click to collapse
Whatever you try dont try fastboot erase all
This would destroy your phone my first gen and second gen are died out of this command :crying:
I just found a twrp I could boot directly using fastboot... I am now in TWRP... to be continued. I'll keep you informed, I want to backup now first.
For now, this is the one I finally was able to boot:
http://techerrata.com/file/twrp2/titan/openrecovery-twrp-2.8.5.0-titan.img
Some more findings:
Code:
# fastboot oem fb_mode_set
...
FAILED (remote failure)
In the flashfile.xml form stock firmware-package, this command is listed before all the flash-commands.
Another irregularity is that the device cannot be locked again:
Code:
[[email protected] ~]# fastboot oem lock
...
(bootloader) Phone is locked successfully!
(bootloader) Please flash valid signed system image now!
OKAY [ 1.020s]
finished. total time: 1.020s
[[email protected] ~]# fastboot getvar securestate
securestate: locked
finished. total time: 0.001s
[[email protected] ~]# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.251s
[[email protected] ~]# fastboot getvar securestate
securestate: unlocked
finished. total time: 0.034s
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
J0SH1X said:
This would destroy your phone my first gen and second gen are died out of this command :crying:
Click to expand...
Click to collapse
I already heard of it.
The symptoms we are facing seem to be very similar to what you experience after issuing this command, but it has not been run.
---------- Post added at 11:04 AM ---------- Previous post was at 10:49 AM ----------
Backup is not possible.
Mounting /data fails all the time, no valid filesystem is recognized.
When using TWRP for "advanced format" it claims to create an ext2-filesystem, but it still cannot be accessed or overwritten.
I am able to open a shell using adb, but I'm unsure how to proceed.
---------- Post added at 11:19 AM ---------- Previous post was at 11:04 AM ----------
Could someone with a working device show me the output of
Code:
parted /dev/block/mmcblk0 print
?
I'd like to compare with my partitioning:
Code:
/system # parted /dev/block/mmcblk0 print
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 67.2MB 67.1MB ext4 modem
2 67.2MB 67.8MB 524kB sbl1
3 67.8MB 67.8MB 32.8kB DDR
4 67.9MB 68.9MB 1036kB aboot
5 69.4MB 69.6MB 205kB rpm
6 69.9MB 70.4MB 410kB tz
7 70.5MB 70.5MB 32.8kB sdi
8 70.5MB 71.0MB 524kB utags
9 71.0MB 73.1MB 2097kB logs
10 73.1MB 75.5MB 2388kB padA
11 75.5MB 76.5MB 1036kB abootBackup
12 77.0MB 77.2MB 205kB rpmBackup
13 77.5MB 78.0MB 410kB tzBackup
14 78.1MB 78.1MB 32.8kB sdiBackup
15 78.1MB 78.6MB 524kB utagsBackup
16 78.6MB 79.7MB 1077kB padB
17 79.7MB 81.3MB 1573kB modemst1
18 81.3MB 82.8MB 1573kB modemst2
19 82.8MB 83.3MB 500kB hob
20 83.3MB 83.4MB 32.8kB dhob
21 83.5MB 85.1MB 1573kB ext2 fsg
22 85.1MB 85.1MB 1024B fsc
23 85.1MB 85.1MB 8192B ssd
24 85.1MB 86.1MB 1049kB sp
25 86.1MB 86.3MB 131kB cid
26 86.3MB 89.4MB 3146kB ext3 pds
27 89.4MB 93.6MB 4194kB logo
28 93.6MB 97.8MB 4194kB clogo
29 97.9MB 106MB 8389kB ext4 persist
30 106MB 107MB 524kB misc
31 107MB 117MB 10.4MB boot
32 117MB 128MB 10.5MB recovery
33 128MB 129MB 1049kB deviceinfo
34 129MB 146MB 16.8MB ext4 ftmlog
35 146MB 706MB 560MB ext4 cache
36 706MB 1863MB 1158MB ext4 system
37 1863MB 1872MB 8389kB kpan
38 1872MB 7784MB 5913MB userdata
Partitions are there, but something is wrong with userdata, there is no filesystem and I cannot create one:
Code:
/system # mkfs.ext2 /dev/block/mmcblk0p38
mkfs.ext2: lseek: Value too large for defined data type
---------- Post added at 11:24 AM ---------- Previous post was at 11:19 AM ----------
parted crashes when trying to format:
Code:
(parted) mkfs
mkfs
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
Yes/No? Yes
Yes
Partition number? 38
38
File system type? [ext2]?
Error: Invalid superblock. Are you sure this is an ext2 file system?
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
http://ftp.gnu.org/gnu/parted/
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
http://www.gnu.org/software/parted
for further information.
Your report should contain the version of this release (1.8.8.1.179-aef3)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Error: SEGV_MAPERR (Address not mapped to object)
Aborted
/system #
---------- Post added at 12:13 PM ---------- Previous post was at 11:24 AM ----------
is /cache/kernel_last_log from recovery or from system-boot?
This is interesting:
Code:
<6>[ 627.767910,2] F2FS-fs (mmcblk0p38): mounting..
<3>[ 627.903098,2] F2FS-fs (mmcblk0p38): recovery did not fully complete
<6>[ 627.903235,1] F2FS-fs (mmcblk0p38): mounted filesystem
<7>[ 627.903687,1] SELinux: initialized (dev mmcblk0p38, type f2fs), uses xattr
<6>[ 629.503418,0] EXT4-fs (mmcblk0p36): mounted filesystem with ordered data mode. Opts:
<7>[ 629.503560,0] SELinux: initialized (dev mmcblk0p36, type ext4), uses xattr
<6>[ 629.505612,0] F2FS-fs (mmcblk0p38): mounting..
<3>[ 629.638769,0] F2FS-fs (mmcblk0p38): recovery did not fully complete
<6>[ 629.638999,0] F2FS-fs (mmcblk0p38): mounted filesystem
<7>[ 629.639667,0] SELinux: initialized (dev mmcblk0p38, type f2fs), uses xattr
I also am able to write data on the partition using dd, so it is no hardware-problem. //edit: Bull****? When I dd'd the filesystem, nothing should be able to mount.
It is strange, that I can use /cache on adb shell, while fastboot says there would be an invalid partition type "raw" for /cache and /data.
---------- Post added at 12:43 PM ---------- Previous post was at 12:13 PM ----------
Code:
~ # dd if=/dev/zero of=/dev/block/mmcblk0p38 bs=8192 conv=fsync
dd: writing '/dev/block/mmcblk0p38': No space left on device
721777+0 records in
721776+0 records out
5912788992 bytes (5.5GB) copied, 501.042553 seconds, 11.3MB/s
This is so weird. This command usually destroys any single bit on a partition. "conv=fsync" makes sure that the data is actually written to the device.
The command finishes, but still kernel claims to have mounted something here when system boots:
Code:
<6>[ 629.505612,0] F2FS-fs (mmcblk0p38): mounting..
<3>[ 629.638769,0] F2FS-fs (mmcblk0p38): recovery did not fully complete
<6>[ 629.638999,0] F2FS-fs (mmcblk0p38): mounted filesystem
<7>[ 629.639667,0] SELinux: initialized (dev mmcblk0p38, type f2fs), uses xattr
---------- Post added at 01:26 PM ---------- Previous post was at 12:43 PM ----------
during formatting, dmesg is full of messages like:
Code:
<3>[ 1289.062754,0] Buffer I/O error on device mmcblk0p38, logical block 262
<4>[ 1289.062838,0] lost page write due to I/O error on mmcblk0p38
<3>[ 1289.062991,0] Buffer I/O error on device mmcblk0p38, logical block 263
<4>[ 1289.063075,0] lost page write due to I/O error on mmcblk0p38
<3>[ 1289.063233,0] end_request: I/O error, dev mmcblk0, sector 3661824
<3>[ 1289.063328,0] end_request: I/O error, dev mmcblk0, sector 3661880
Not sure if this TWRP is broken or my internal storage.
I think I give up on this. Glad to live in EU where I still should have warranty as the device is not older than 6 months
So you saying that if we leave in eu and phone purchased before 6 mo ago, we can still send phone to warranty even if we unlocked bootloader and did all the s* with it? I leave in portugal so i would think im in.
CPMAGMPC said:
So you saying that if we leave in eu and phone purchased before 6 mo ago, we can still send phone to warranty even if we unlocked bootloader and did all the s* with it? I leave in portugal so i would think im in.
Click to expand...
Click to collapse
if you have bought it after 6 month ago, see here:
http://piana.eu/root
You might need to convince the shop were you bought it, but generally in EU rooting/unlocking does not taint warranty. Note that it's the warranty the seller gives you, not the warranty from Motorola.
Just for interest, when you format your /data-partition, do you also get I/O-errors when entering dmesg?
I did not even unlock my device before the problem occured, so I assume that this problem is not caused by your custom rom.
when i format data partition in twrp i get success, but i check data after and all apps, photos etc still there and i can copy that data to my pc with usb and windows explorer.
cxxxx said:
if you have bought it after 6 month ago, see here:
http://piana.eu/root
You might need to convince the shop were you bought it, but generally in EU rooting/unlocking does not taint warranty. Note that it's the warranty the seller gives you, not the warranty from Motorola.
Just for interest, when you format your /data-partition, do you also get I/O-errors when entering dmesg?
I did not even unlock my device before the problem occured, so I assume that this problem is not caused by your custom rom.
Click to expand...
Click to collapse
My wife's XT1064 (Canadian Single SIM) is doing this exact same thing. Boot loops after the battery drained to 0%. All the options in the fastboot menu do nothing other than show the Motorola android logo.
Can someone link me to the proper firmware for the XT1064 factory image? This forum is pretty haphazardly laid out...
jippers said:
My wife's XT1064 (Canadian Single SIM) is doing this exact same thing. Boot loops after the battery drained to 0%. All the options in the fastboot menu do nothing other than show the Motorola android logo.
Can someone link me to the proper firmware for the XT1064 factory image? This forum is pretty haphazardly laid out...
Click to expand...
Click to collapse
Unfortunately they can be found only in a share on filefactory: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1
See here: http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
Are you sure you did not confuse power-button with volume-up-button in fastboot menu? I did nearly a whole day
But even after I found out, I was not able to start recovery until I tried to flash with a custom recovery - what did not succeed, but at least stock recovery started then and I am able to boot TWRP directly using "fastboot boot recovery.img".
Would be nice to hear whether your storage is messed up, too.
I have faced the same prblm . Just boot into boot loader mode and download stock Firmware from http://forum.xda-developers.com/moto-g-2014/general/moto-g-2014-factory-firmware-images-t2869485 and then flash everything Cheers u have fixed ur moto G.
Source: Experienced it. lol I have a lot of sad experiences.
already tried that.. the problem is adb fastboòt never recognizes my device, only if im twrp it gets recognized, but then when i try to send commands with fastboot, device returns to boòtloader mode, and then it stops being detected again. i really think my device as no return.. hope im wrong :crying:
Mohandass said:
I have faced the same prblm . Just boot into boot loader mode and download stock Firmware from http://forum.xda-developers.com/moto-g-2014/general/moto-g-2014-factory-firmware-images-t2869485 and then flash everything Cheers u have fixed ur moto G.
Source: Experienced it. lol I have a lot of sad experiences.
Click to expand...
Click to collapse
CPMAGMPC said:
already tried that.. the problem is adb fastboòt never recognizes my device, only if im twrp it gets recognized, but then when i try to send commands with fastboot, device returns to boòtloader mode, and then it stops being detected again. i really think my device as no return.. hope im wrong :crying:
Click to expand...
Click to collapse
What PC OS are u using? I use Windows 7... I think Motorola's Drivers aren't Compatible with Windows 8 Yet As when i tried on my Friends PC with Windows 8, My phone wasn't recognised in bootloader mode even with Drivers installed...
Hello,
I've been trying to encrypt my device for a while now. It always just goes to the encrypting icon, then waits a second and boots into CM12.1 again. Now I've tried to use adb logcat, where I was able to find this when starting encryption, just after all the SIGKILLs:
E/Cryptfs ( 229): Cannot open real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs ( 229): Unable to get crypt_ftr_info
E/Cryptfs ( 229): Cannot get size of block device /dev/block/platform/msm_sdcc.1/by-name/userdata
Click to expand...
Click to collapse
I'm using CM12.1 titan linked here. However, I'm fairly certain that this is not a ROM issue, I've had it on all ROMs. Any help would be greatly appriciated.
~ Robin
maybe it really is the encryption footer?
Robin.S said:
I've been trying to encrypt my device for a while now. It always just goes to the encrypting icon, then waits a second and boots into CM12.1 again. Now I've tried to use adb logcat
Click to expand...
Click to collapse
(I'm sorry but it won't let me post links yet, you'll have to fix them below to use, I stripped the schemes, put them between LINK uppercase, and italicized the link text)
I'm getting the same thing, I just tried with 20150505 nightly cm12.1, this seems to a be a known issue, but with very little real information as to the problem. I found LINK forum.cyanogenmod.org/topic/88973-moto-g-cm11-encryption-failed/ LINK this forum post going back to mid 2014, and LINK jira.cyanogenmod.org/browse/CYAN-4532 LINK the linked JIRA bug which seems to indicate that all the Moto G devices (falcon, peregrine, titan), possibly Moto X as well are affected, but nobody seems to know what causes this bug, only vague hints that it may be a "timing related issue" but no other clarifying information in the now more than a year since this bug was posted.
The obvious conclusion is that nobody is encrypting their devices, which I find bizarre. Once Motorola releases a 5.1 factory ROM for this device (which is supposedly imminent -- they've already released for G-2013 and X-2014 I believe), I'll flash it and test that one.
I used logcat -v long and saw the times, the process kills definitely come after the attempts to open the block device fails. I did a logcat -c in one shell and then a vdc cryptfs enablecrypto inplace <password> in another (this is what the encrypt UI initiates), and the after the resulting softboot (it keeps the adb shell alive, and system uptime continues, so this isn't a hard boot), a logcat shows the same sequence:
Code:
[ 05-06 20:06:03.897 230: 287 E/Cryptfs ]
Cannot open real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
[ 05-06 20:06:03.897 230: 287 E/Cryptfs ]
Unable to get crypt_ftr_info
[ 05-06 20:06:03.898 230: 287 E/Cryptfs ]
Cannot get size of block device /dev/block/platform/msm_sdcc.1/by-name/userdata
and then the kills start.
At first, because of the apparent inability to get crypt footer (in the error message), I thought this was lack of the 16k footer mentioned in the aforementioned bug, but LINK review.cyanogenmod.org/#/c/86684/ LINK the patch to include it appears to be long incorporated in LINK github.com/CyanogenMod/android_device_motorola_titan/blob/cm-12.1/BoardConfig.mk LINK our board's version of this file.
However, as I write this, I notice that the size in BoardConfig.mk does not correspond to the one on the device:
Code:
$ readlink /dev/block/platform/*/*/userdata
/dev/block/mmcblk0p38
$ grep mmcblk0p38 /proc/partitions
259 6 5774208 mmcblk0p38
$ bc
((5930598400 / 1024) - 5774208) / 1024
16.9843750000
they appear to differ by slightly more than 16k (the size of the encryption footer). But yet /system corresponds exactly with the line from BoardConfig.mk:
Code:
$ readlink /dev/block/platform/*/*/system
/dev/block/mmcblk0p36
$ grep mmcblk0p36 /proc/partitions
259 4 1130496 mmcblk0p36
$ bc
1157627904 / 1024
1130496.0000000000
so now I'm thinking that really is the problem (the userdata partition needs to have its size extended by 16k). But then there is LINK forum.cyanogenmod.org/topic/104204-xt1039-cm12-nightly-20150123-encryption-of-data-partition-not-working-simply-warm-reboots/ LINK this forum post which claims that the same partition encrypts fine with the stock image.
I didn't factory reset when flashing cm12.1 (from a stock 5.x ROM), which I think recreates the partition (?) So, maybe the partition didn't get resized to the correct value. However if the stock ROM handles this case, I should think CM would too.
What about you? Did you factory reset (including /data) when you installed CM on your Titan? I saw no need to get rid of /data (although I did have to delete some things in /data/misc to get rotation working) when coming from stock ROM and wanted to avoid having to redo everything. Which worked fine... except for this
SO, i have a 1st gen Moto X, the 2013 model. Verizon if that matters.
I havent used it in a while, and it was working when i replaced it. I decided to tinker with it a bit a few months ago, and was trying an unlock method i found online, and appear to have bricked it in the process. I figured, no big deal, and tossed it in a cabinet and figured i'd come back to it later. Well now is later. I'd like to get the thing working so my daughter might be able to play with it.
It wont power on, if you connect it to power, either USB or a wall plug, it does nothing, no charging indicator, nothing. I cant power it on, cant fastboot, cant get to recovery, nothing.
In my attempts to restore it, i've got the moto drivers and whatnot installed, and my Windows laptop will recognise it and add it to device manager, as "Qualcomm HS-USB QDLoader 9008 (COMx)". Which makes be believe there is hope.
I tried the procedure here: https://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057, with no success, i get an error while it's trying to get an handshake from the device.
Code:
C:\Users\war\Desktop\MotoX Recovery\blankflash\blankflash>qflash -com7 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloader_singleimage.bin -v -o
Motorola qflash Utility version 1.3
COMPORT :COM7
RAMLOADER :MPRG8960.hex
type is 0x21
7 mbn file name MSM8960_bootloader_singleimage.bin type 33
verbose mode on
Motorola qflash dll version 1.6
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
EOF_REC
Sleeping for 3s
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
Still no data, giving up!
sdl_hello() - Failed to receive ACK
sdl_hello() - Invalid response: 7e030003331b7e
sdl_hello() - This is a NAK response from ROM code, which means the device has been reset back to blank flash mode. Usually this is caused by power supply issues. Please try again with battery eliminator if it persists
I've had no luck finding a way around that.
If i hold the power button for 10 seconds, while plugged into my PC's usb port, the green indicator light behind the speaker lights up for a second, and then goes out. Same deal if I try to do power+vol-up or vol-down.
Any suggestion that might help me move this along? If i can get it to fastboot, or a recovery image, I think I can get it from there.
Thanks!
That's obsolete, and won't work for your lastest bootloader. See next thread. And don't flash Moto at random next time)
Thanks for the response. I'll give that thread a look!