Sony E1 on release hasn't got recovery. If you flashed custom rom without support for recovery, or you have stock rom (you need to unlock bootloader) you have to flash or boot CWM. CWM have recovery inside boot partition.
sudo fastboot flash boot cwm.img
If you are on Windows, run command prompt with administrator priviliges, without "sudo" command.
To do backup of stock rom, run:
Spoiler: "for", linux syntax
for i in mmcblk0p1 mmcblk0p12 mmcblk0p15 mmcblk0p18 mmcblk0p20 mmcblk0p4 mmcblk0p7mmcblk0p10 mmcblk0p13 mmcblk0p16 mmcblk0p19 mmcblk0p21 mmcblk0p5 mmcblk0p8 mmcblk0p11 mmcblk0p14 mmcblk0p17 mmcblk0p2 mmcblk0p3 mmcblk0p6 mmcblk0p9; do adb pull /dev/block/$i $i.img; done
edit: you can use ROM manager
Windows have other syntax, you can backup the whole device
adb pull /dev/block/mmcblk0 mmcblk0.img
[CWM] Philz Touch Recovery for Xperia E1
You need an unlocked bootloader to flash this recovery Instructions- 1. Download the kernels, extract zip to somewhere on your computer & place img in the directory of fastboot.exe 2. Connect your phone in fastboot mode press vol + button while...
forum.xda-developers.com
With this custom kernel, camera works in stock rom
The stock ROM is the pre-installed operating system in your Android device. To backup your Stock ROM you have to install ROM Manager app on your Android mobile.
Related
like other people's can not mount anything ,
use TWRP boot , press install show internal storage 0mb
Is it means the storage over ?
ft7823 said:
like other people's can not mount anything ,
use TWRP boot , press install show internal storage 0mb
Is it means the storage over ?
Click to expand...
Click to collapse
hello anybody can help me ?
just after charging , the device can not open and use cwm boot in , showed can not mount anything ,
include the sdcard. I think the internal storage was damaged , is there any good ideas to get back ?
and I saw NT have a tool to unbrick ,is there also same tools for HD+?
What ROM were you using?
Are you booting from SD?
It seems that your emmc is bricked, unfortunately this seems not to be recoverable...
If you have adb access, try those commands mentioned here:
http://wiki.cyanogenmod.org/w/EMMC_Bugs#How_do_I_check_my_device.27s_eMMC_details.3F
CM10.2, I think you are right ,EMMC bricked.
but the strange thing is I use 3 sd card ,all can not boot from sdcard or emmc.
I want to flash noemmc version's cm, but also impossible now ...
so strange ..
wait, but you can boot into sd-recovery?
Jann F said:
wait, but you can boot into sd-recovery?
Click to expand...
Click to collapse
thank you , yesterday the devices can mount sdcard , so I install CM10.1 NOEMMC to sdcard
just one thing is not suit for me , the sdcard'format is not FAT32 and computer can only find the first part
so I can only download the file to my sdcard but cannot use usb or tf cardreader to put my files in.
but anyway , I can use it without emmc , the better thing than nothing to do.
1. My nook still bricked and cannot use any cwm except no-emmc version
2.I checked again, my nook is MGB4GA , I think should not be emmc bug
now
I use no-emmc version CWM flash EMMC recovery V6.0.3.2 ,
but without sdcard can only boot in the logo and stop there
e:can't mount /cache/revoery/command
and I use adb to check , show like below
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 398228 48 398180 0% /dev
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 15360 mmcblk0p3
179 4 16384 mmcblk0p4
179 5 49152 mmcblk0p5
179 6 49152 mmcblk0p6
179 7 458752 mmcblk0p7
259 0 688128 mmcblk0p8
259 1 475136 mmcblk0p9
259 2 28770304 mmcblk0p10
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 7761920 mmcblk1
179 25 7761888 mmcblk1p1
is this normal?
and is that able to restore from leapinlar's repari.zip?
Get yourself a 32gb class 4 sd card and you can boot into CWM recovery.
ft7823 said:
1. My nook still bricked and cannot use any cwm except no-emmc version
2.I checked again, my nook is MGB4GA , I think should not be emmc bug
now
I use no-emmc version CWM flash EMMC recovery V6.0.3.2 ,
but without sdcard can only boot in the logo and stop there
e:can't mount /cache/revoery/command
and I use adb to check , show like below
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 398228 48 398180 0% /dev
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 15360 mmcblk0p3
179 4 16384 mmcblk0p4
179 5 49152 mmcblk0p5
179 6 49152 mmcblk0p6
179 7 458752 mmcblk0p7
259 0 688128 mmcblk0p8
259 1 475136 mmcblk0p9
259 2 28770304 mmcblk0p10
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 7761920 mmcblk1
179 25 7761888 mmcblk1p1
is this normal?
and is that able to restore from leapinlar's repari.zip?
Click to expand...
Click to collapse
Your emmc looks ok. Do as the previous user suggested and get a SanDisk class 4 SD and make a bootable CWM SD per the instructions in item 1a in my HD/HD+ CWM thread linked in my signature. Then use that to flash a plain stock zip from item 6.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Your emmc looks ok. Do as the previous user suggested and get a SanDisk class 4 SD and make a bootable CWM SD per the instructions in item 1a in my HD/HD+ CWM thread linked in my signature. Then use that to flash a plain stock zip from item 6.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
So i need a sandisk card.... unfortunately i have no such card in my hand.
use old card with no-emmc version cwm flash nook 2.1 ,random offset 0x29,final abort , other models unable to be flashed to the system.
use 6028 flash 2.1 or 2.2 can run half but then black screen and shut off.
flash CM10.1 CM10.2 can not run just at the beginning and then black screen and shut off.
so is that possible to use your repair.zip?
ft7823 said:
So i need a sandisk card.... unfortunately i have no such card in my hand.
use old card with no-emmc version cwm flash nook 2.1 ,random offset 0x29,final abort , other models unable to be flashed to the system.
use 6028 flash 2.1 or 2.2 can run half but then black screen and shut off.
flash CM10.1 CM10.2 can not run just at the beginning and then black screen and shut off.
so is that possible to use your repair.zip?
Click to expand...
Click to collapse
You do not want to use the noemmc CWM if you are wanting to flash to emmc. If the 2.2 will not flash with 6028 then any repair zip I make will not work either.
Sent from my SCH-i705 using XDA Premium HD app
168599699669
leapinlar said:
You do not want to use the noemmc CWM if you are wanting to flash to emmc. If the 2.2 will not flash with 6028 then any repair zip I make will not work either.
Sent from my SCH-i705 using XDA Premium HD app
Click to expand...
Click to collapse
ok , understood , anyway ,thank you for your reply.
hello devs
From few days, im trying to figure out which is the recovery partition of my phone. But failed to do so. Whenever i type
Code:
cat proc/partitions
I get everything but not the recovery partition.
Plz help me to dump it.
Im not able to create a custom recovery bcoz of this.
My device is an asus zenfone 4 a400cg
X86 with android 4.4.2(stock)
Mmcblk0p3 is factory[WTH is that]
Mmcblk0p9 is system
Mmcblk0p6 is cache
Mmcblk0p5 is config
Mmcblk0p10 is data and
Mmcblk0p8 is ADF ext4
Now which is the recovery partition in these?????[emoji30] [emoji30] [emoji30] [emoji30] [emoji30] [emoji22]
Hello,
After a shutdown due to low battery, my tablet is soft bricked. :/ I suspect a corruption of the internal SD or the flash chip, I'm not really sure.
My tablet is unlocked, I have cwm 6.0.5.1 installed. If I remember correctly, I had some cromi-X rom.
I have access to the bootloader (11.4.1.29) and the recovery but the manipulations I'm doing aren't working.
When into recovery, I get the messages e: can't mount/open /cache/recovery/log (last_log, last_install).
I tried flashing all kind of roms, they all failed, the most successful install ended with an error creating symlinks.
Tried all the wipe/format/factory reset options in the recovery, most of the time, I get the "error mounting /data", "error mounting /sdcard/.android_secure".
I can mount /system but it doesn't work for /cache and /data.
I can fastboot boot other recoveries (other cwm, twrp) but somehow can't flash. I'm not getting any error, they're just not sticking.
I tried manually formatting with e2fsck commands but I get an error related with superblocks.
Here's my cat log /proc/partitions :
179 0 30535680 mmcblk0
179 1 8192 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 2097152 mmcblk0p4
179 5 897024 mmcblk0p5
179 6 512000 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 4096 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 4096 mmcblk0p13
179 14 26916864 mmcblk0p14
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
Here's what "df" is showing :
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 960124 128 959996 0% /dev
/dev/block/platform/sdhci-tegra.3/by-name/APP
2064208 1110432 953776 54% /system
I've done so many things to try fixing this with all I could find googling, I may have done some mistakes in the process but I didn't spot any change. The only thing I haven't tried yet is to install/boot a rom from the external SD. But I'm not experienced enough for that, I prefer to keep as a last resort.
I just ran a dmesg command, there's several error messages there, maybe that'll help. As I can't post URLs yet, here's a sample :
<4>[ 12.192838] lost page write due to I/O error on mmcblk0p5
<3>[ 19.972559] mmcblk0: mmc_blk_err_check: general error sending status command, card status 0x80900
<4>[ 19.981660] mmcblk0: retrying write for general error
<4>[ 19.986857] lost page write due to I/O error on mmcblk0p14
<3>[ 20.217027] mmcblk0: packed cmd failed, nr 20, sectors 280, failure index: 0
<4>[ 20.693382] JBD2: recovery failed
<3>[ 20.696941] EXT4-fs (mmcblk0p14): error loading journal
I'm not sure how it works, maybe it's possible to manually wipe everything, keeping the bare minimum to recreate the partitions and push the files.
I may have missed something, some help would be really appreciated. ^^
Thanks in advance !
I have same problem!! Any solutions?
Same Problem here as well!
I have the same problem. Seems like the /cache and /data partitions are corrupt.
I have full CWM and Bootloader access with ADB and fastboot. I cannot flash new recoveries. Cannot mount /data or /cache.
Repairing the partitions with e2fsck get me nowhere as well.
I can shell in and run parted on the /data (mmcblk0p14) and /cache (mmcblk0p5) blocks. I attempted to recreate the partitions using parted but keep getting input/output error during write on /dev/block/mmcblk...
Can't even delete the old partitions in /data (mmcblk0p14) and /cache (mmcblk0p5) with fdisk. get failure error.
Any ideas how to overcome the partition recreation errors? Are we screwed?
Same problem here as well.
had cromix up and running, then suddenly black screen. Recovery working good, but mount errors. Cannot restore nandroid or flash any kind of rom.
realmastah said:
Same problem here as well.
had cromix up and running, then suddenly black screen. Recovery working good, but mount errors. Cannot restore nandroid or flash any kind of rom.
Click to expand...
Click to collapse
If you use TWRP, first try to wipe dalvik cache only and then try again to flash a rom or to restore a nandroid backup. This problem is TWRP related...
I had this exact issue when i was moving to lollipop. I tried to flash to zombi-x and it caused this issue. every time i turned the device on it would boot direct to recovery. I was unable to restore backups, flash new roms... nothing worked. In the end, i formatted my data partition and put blisspop on my external sd. After the format it took the new rom and has been running amazingly well since then.
Jerry1996 said:
If you use TWRP, first try to wipe dalvik cache only and then try again to flash a rom or to restore a nandroid backup. This problem is TWRP related...
Click to expand...
Click to collapse
thanks for the suggestion, tried it without success.
meanwhile i sent the device back as it was still under warranty, got refund.
EDIT: I got an image courtesy of mp107
Hi,
can someone provide me with a dd image of mmcblk1p1?
I accedentaly formated mmcblk1p1 instead of mmcblk0p1, i assume this is where the bootloader is located.
Luckaly I realized before rebooting the phone. I now need a dd image of mmcblk1p1 to write back before the phone reboots for any reason.
When I was using Moto e2. I messed up with IMEI. And I downloaded the whole factory firmware and flashed it via fastboot using PC. But I lost my precious data.
This post is made for Noobs.
Now I am using Sanders XT1804 and would like to share a short and quick method to backup and understanding IMEI partitions. I am listing here the partition layout of XT1804 Indian variant with block no. And will tell you how to backup and restore the partitions easily by using DD command in terminal emulator app. Pls. read it carefully.
sbl1 mmcblk0p1
rpm mmcblk0p2
tz mmcblk0p3
devcfg mmcblk0p4
aboot mmcblk0p5
cmnlib mmcblk0p6
cmnlib64 mmcblk0p7
keymaster mmcblk0p8
prov mmcblk0p9
sbl1bak mmcblk0p10
rpmbak mmcblk0p11
tzbak mmcblk0p12
devcfgbak mmcblk0p13
abootbak mmcblk0p14
cmnlibbak mmcblk0p15
cmnlib64bak mmcblk0p16
keymasterbak mmcblk0p17
provbak mmcblk0p18
modem mmcblk0p19
fsc mmcblk0p10
ssd mmcblk0p21
dsp mmcblk0p22
DDR mmcblk0p23
sec mmcblk0p24
utags mmcblk0p25
utagsBackup mmcblk0p26
modemst1 mmcblk0p27
modemst2 mmcblk0p28
fsg mmcblk0p29
persist mmcblk0p30
frp mmcblk0p31
cid mmcblk0p32
logo mmcblk0p33
carrier mmcblk0p34
metadata mmcblk0p35
kpan mmcblk0p36
boot mmcblk0p37
recovery mmcblk0p38
misc mmcblk0p39
limits mmcblk0p40
mota mmcblk0p41
dip mmcblk0p42
syscfg mmcblk0p43
logs mmcblk0p44
apdp mmcblk0p45
msadp mmcblk0p46
dpo mmcblk0p47
padA mmcblk0p48
sp mmcblk0p49
hw mmcblk0p50
oem mmcblk0p51
cache mmcblk0p52
system mmcblk0p53
data mmcblk0p54
Requirements:-
1) Stock ROM or any custom ROM
2). ROOT
3) any Terminal Command app from Playstore.
For IMEI u must backup modem, modemst1 and modemst2.
Block no. are mmcblk0p19, mmcblk0p27, mmcblk0p28.
To backup modem partition:-
Open terminal emulator app first type "su" and then
dd if=/dev/block/mmcblk0p19 of=/sdcard/modem.img
To restore modem partition:-
dd if=/sdcard/modem.img of=/dev/block/mmcblk0p19
In the same way,
To backup modemst1 and modemst2 type:-
dd if=/dev/block/mmcblk0p27 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p28 of=/sdcard/modemst2.img
To restore modemst1 and modemst2:-
dd if=/sdcard/modemst1.img of=/dev/block/mmcblk0p27
dd if =/sdcard/modemst2.img of=/dev/block/mmcblk0p28
Make sure that in above commands I give the backup path to "sdcard" which is the internal storage of android device
Click to expand...
Click to collapse
You must copy that .IMG file to other storage or external device.
The partition block no. may vary with different variants of Sanders(G5S PLUS) above one is for XT1804 only.
Modemst1 is for SIM1 and modemst2 for SIM2 IMEI.
In the same way u can backup all the necessary partitions. Just replace the filename with "xxx.img" .IMG is necessary to make the image with IMG. format. I would recommend u do all the necessary partitions backup in your sdcard and than move this images to ur pc or pen drive.
Such as persist, carrier, modem, modemst1, modemst2 etc.
Once u do the backup and u bricked ur device in future. Don't worry, you can restore it anytime if u want.
Just install ADB in ur pc. Go to fastboot mode in ur mobile. Place the file in ADB folder on windows.
Type this command to restore/flash partitions.
For modem partition
Code:
fastboot flash modem modem.img
while doing backup/restore in terminal app using dd command. Keep the filename same as listed in partition layout according to block no.
Click to expand...
Click to collapse
Do enjoy and keep flashing custom roms. Cheers