Hi people, my problem is that i erase all nexus one files form ClockworkMod Recovery and when i power on the nexus it's go directly to recovery mod.
when i try
adb shell
mount data
adb push C:\ROM.zip /data/
adb shell
recovery –update_package=DATA:ROM.zip
its return
sh: /sbin/postrecoveryboot.sh: not found
when i try apply a zip from sdcard return
E: can't mount /sdcard/
anyone know anything about this ?
You're saying you formatted your system? In that case your ROM is probably gone right? If you have a flashable custom rom in your SD card why don't you flash that from recovery?
Can't you just:
adb push [rom file path] /sdcard/
reboot
Flash that rom ( just any working rom)
???
If that doesn't work and still says can't mount sd have you tried formatting your sd card?
Do you have any recovery backups you can restore?
my problem is i put encryption on my htc one but could not get rid of it no matter what i did so i wipe every single thing from the recovery so now there notting on my phone what so ever, when i try to mount sd card now it just wont mount there no error message notting from recovery, is there any way in fixing this.... im using clockworkmod 6.0.3.0??
thanks
seanhtcone said:
my problem is i put encryption on my htc one but could not get rid of it no matter what i did so i wipe every single thing from the recovery so now there notting on my phone what so ever, when i try to mount sd card now it just wont mount there no error message notting from recovery, is there any way in fixing this.... im using clockworkmod 6.0.3.0??
thanks
Click to expand...
Click to collapse
you can try fastboot erase userdata
or fastboot -w
after that use adb push to get a ROM onto your sd card
or use adb sideload to push a rom and install.
gunnyman said:
you can try fastboot erase userdata
or fastboot -w
after that use adb push to get a ROM onto your sd card
or use adb sideload to push a rom and install.
Click to expand...
Click to collapse
it wont let me erase userdata, it says cant be done remotely and also when i try to side load it says failed to wirte data 'protocol fault<no status> ???
Thanks.. sideload worked it just failed like 6 times first for some reason, sideload is so handy
Phone: xt1060, verizon, Moto X Dev edition (2013)
ROM: Cm 12.1 (however, I was unable to encrypt with my last ROM as well)
My data directory is formatted with f2fs. When I attempt to encrypt the phone, it reboots without error and without any encryption action. I've used logcat to capture these messages:
I/Cryptfs ( 242): Check if PFE is activated on Boot
E/Cryptfs ( 242): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs ( 242): Error getting crypt footer and key
E/Cryptfs ( 242): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs ( 242): Not a valid ext4 superblock
E/Cryptfs ( 242): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
Click to expand...
Click to collapse
Because of the "Not a valid ext4 superblock" error, I tried changing the file system to ext4. When I boot after changing the data partition to ext4, the phone enters a boot loop. It boots up to an error that says "encryption unsuccessful" and the only choice is to reset the phone. I reset the phone and it boots back to the same error. I've formatted cache, system, data and sdcard, reinstalled both ROM and recovery and still I boot back up into this error message even though I am not presently trying to encrypt.
I read about a problem which requires the data partition to be reduced in size by at least 16KB, so I reduced it by about 4MB. The data partition was 27606912 blocks, and I reduced the partition to 27606000 blocks. However, this had no affect.
I have changed the partition back to f2fs because at least the phone boots using this file system without entering the "encryption unsuccessful" loop.
I have tried multiple recoveries in case that was the problem. I've tried CWM, the recovery for CM 12.1, and the most recent TWRP. I get the same problem in each of these.
I am most baffled about the boot loop after formatting the partitions in ext4 then installing a fresh ROM. Apparently my attempt to encrypt is remembered somewhere other than system, data, cache, or sdcard?
I considered flashing back to factory, however, I do not have the files, the links I've found on xda are broken, and I am waiting on Motorola to provide me access to the stock firmware - I requested it tonight though.
I appreciate any assistance that can be offered. Thank you.
I found the factory firmware and I attempted following the directions for a factory restore:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot erase userdata
$ fastboot erase cache
$ fastboot reboot
Click to expand...
Click to collapse
However, the system.img failed. So, I reflashed recovery to TWRP and found that I did not have a system, data, cache or sdcard partition. I reflashed recovery to CWM because it has a custom format option and I formatted data, cache, system and sdcard using ext4, then I reflashed recovery to TWRP and because I am able to transfer files using TWRP. I transferred the CM 12.1 and gapps images, flashed them both, then rebooted.
After all of that, I still booted up into an "encryption failed" screen!
I then went back into TWRP, changed the data partition to f2fs, then I was able to boot into the new CM 12.1. So, the exact same problem exists: using f2fs, I am unable to encrypt the phone. Using ext4, I am stuck in an "encryption failed" loop.
I'm giving this thread a bump in hopes someone can share a solution with me as I am still having the same problem.
I'm on Verizon Developer Edition, but I had a similar problem after the Lolipop update. I just got it working. I had to flash the moto recovery back and format data and cache through there. Then I could encrypt. I'm gonna try to restore a backup from TWRP onto my encrypted data partition now.
I used the recovery from 47-vzw_xt1060_444-kxa2112-l126_cfc_1ff (google the file I can't post links). I'm not sure if its totally perfect with lolipop, but it formatted my data to work with encryption (ext4).
Same issue here on Moto X (ghost) with cm-12.1-20151007-SNAPSHOT-YOG4PAO332 and cm-12.1-20151105-NIGHTLY.
I could get rid of the message
E/Cryptfs ( 242): Orig filesystem overlaps crypto footer region. Cannot encrypt in place
Click to expand...
Click to collapse
by applying the update from this thread, but the other error messages still remain and I cannot encrypt my device..
Hey friends.I have HTC One (m7) HBOOT(1.61.0000) (OS-7.19.401.30) with TWRP 2.6.3.3.
I did a backup and yesterday i tried to restore and my phone wont start.After that i wipe everything (no OS installed now) and try to flash a ROM(CarbonTEAM-LP5.1.1.C1-RELEASE-20150811-1840-m7.zip) and after unsuccesful flash i thy with (cm-Resurrection_Remix_LP_v5.3.4-20150216-m7.zip) and i get everytime this error
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system,
assuming ext4 mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system:No such file or directory unmount of /system failed; no such volume could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system,assuming ext4 mount:failed /dev/block/platform/msm_sdcc.1/by-name/system at /system:no such file or directory unmount of /system failed; no such volume script succeded:result was[0.2000000].
I get this error either i sideload the ROM.zip file either i put it at sdcard and flash it from recovery.
So how i'm supposed to make it work??To flash a ROM??(tried the above with the CWM too)
THANKS in advance sorry for bad English!!
All roms based on CM must be flashed using TWRP 2.7.1.1 or newer. Update your recovery and flash again.
Pretty simple problem that's screwing me over at the moment, I wiped my phone to install LOS, flashed it and GAPPS, no luck booting, tried rebooting multiple times, it kept going back to recovery. I flashed the latest TWRP, then went to copy over the ROM to flash again and now I can't copy files over when storage is mounted in TWRP. Further, I'm unable to push files using ADB, even though the phone is showing up under ADB devices. ADB push results in this...
Code:
adb push lineage-15.1-20180416-CHINEEL-shamu.zip /data
failed to copy 'lineage-15.1-20180416-CHINEEL-shamu.zip' to 'C:/Program Files/Git/data': No such file or directory
4464 KB/s (507170784 bytes in 110.939s)
Any help is greatly appreciated.
Reformatting the /system and /data partition as exfat and then again as ext4 solved the problem.