Database Info

[Q] FUBAR'd (Status 7)

i seem to have fubar'ed my nexus s (uk version) i updated to ics, didnt like it so tried to restore to a backup i made earlier today...
at the moment when i turn on my phone it shows
fastboot mode- No Boot or Recovery img
lock state - unlocked
I can enter recovery. but cannot restore.
tried wiping cache,dalvik etc.
When hitting restore it returns with:
... system.img not found. skipping restore of /system/
also does the same with
data.img
cache.img
sd-ext.img
i have no idea what to do... if you could help it would be greatly appreciated.

Try flashing a rom. U can mount SD card within recovery.
Sent from my Nexus S 4G using xda premium

yeah tried flashing ...
gets stuck on google screen

Do you have a One Click return to stock available for your model? It wouldn't hurt to start fresh. I did that on my NS4G last week. Does your PC recognize the phone?
Sent from my SPH-D710 using Tapatalk

looking into the unbrickable mod atm... my phone seems to have no .img files.
tried restoring to stock and still the same issue... it says it cant find .img so skips them then when i try to re boot it sticks on the google screen

After trying to apply from zip (cm7, that i have used numerous times before)
i get this ---
Installing update...
assert failed: getprop("ro.product.device") =="crespo" ll getprop("ro.build.Product") == "crespo" ll getprop("ro.product.board") == "crespo"
E:Error in /sdcard/update-cm-7.0.3-NS-signed.zip
(Status 7)
Installation aborted.
i havent the faintest idea what to do...

Tried re-flashing CWM recovery?

yup tried re flash,
i think i need to replace the .img files... i just dont know how
it says that
system.img not found
data.img not found
cache.img not found
sd-ext.img not found.
it skips the restore of these say restore complete. yet there is obviously nothing to restore.
there must be a way of fixing this???

Do you have the latest version of CWM flashed? (5.0.2.0)

yeah re installed/reflashed (5.0.2.0)
it seems to be working
*~~~~~~*
Facepalm
*~~~~~~*
Such a noob
I have had a similar problem before, and even advised on that exact thing.
lesson learned.
KEEP RECOVERY.IMG UP TO DATE
Thank you for pointing out the obvious.
I'm such a ****

No problem flex59, best way to learn is the long and hard way . I had a similar status 7 problem on my move up to ICS. Figured the latest recovery will save me wasted hours down the track eventually, and hopefully someone elses.

To downgrade from ICS, you need to flash the full GB 2.3.6 ROM first...
I downgraded from OTA ICS 4.0.3 due to battery, Wifi & lag issues as well. A NANDroid backup does NOT contain the bootloader and radio AFAIK. Here's what I did.
Find the appropriate FULL ROM here and download and copy to your SD card.
Download this flashable Superuser here and copy to your SD card.
Make sure you are familiar with and set up for fastboot and have the latest CWM recovery img file. You will have to reinstall CWM. These instructions are assuming that CWM recovery is already installed on your device.
1. Make sure the full ROM and SU zip are on the root your SD card.
2. I did a full wipe of data, cache, dalvik.
3. Go into CWM recovery and flash the full ROM. Now flash the SU zip.
4. At this point, the full ROM flashed GB2.3.6, stock recovery, bootloader and radio back. But you should be rooted due to step 3.
5. Boot into Android. I installed ES File Explorer from the market. In ES File Explorer settings, select both root settings “Root Explorer” and “Mount File System” to navigate and modify root files. Allow permissions in SuperUser.
6. Navigate to /system/etc and rename (tap&hold on file) install-recovery.sh to install-recovery.sh.bak (this file reinstalls the stock recovery at every boot)
7. Using fastboot on your computer, flash CWM recovery again.
8. NOW using CWM, restore your GB 2.3.6 NANDroid backup.
Like nothing ever changed.

[mod][tool]dual boot for zte blade/modify-tool

Hello guys. This my dual booting project for our amazing ZTE BLADE!
What is this?
>This mod works on the basis of two scripts which are to be executed in the terminal emulator or script manager and a modified boot.img to boot the rom from sdcard instead of NAND.
FOR ADVANCED USERS ONLY!!!
I WILL NOT BE RESPONSIBLE FOR ANY BRICKED DEVICES, DAMAGED SDCARDS ETC.
DO IT AT YOUR OWN RISK!!!
It is in alpha stage, so lot of work is still needed to make it more safer and convenient.
I will add this mod for more ROMS like CM10, Paranoidandroid etc.
Downloads:
Cyanogenmod9(KonstaKang)
Boot.img - Download
Updater-script - Download
Cyanogenmod10
Boot.img - Download
Updater-script - Download
Gapps::
Jelly Bean Gapps Updater-script - Download
Tool:
Modify-Boot - Download
Now no need to wait for me to mod your boot.img.Mod your boot image for dual boot with this tool!!!
Guide for the tools is on the second post.
Thanks go to:
Sulthekk for guiding me towards right way.
SNAP.iT for giving me some mounting ideas.
All the people who have helped me(can't remember all names ).
And the big community to test it for me.
SCROLL DOWN to 2nd POST FOR THE WHOLE GUIDE...

GUIDE
So here is the full guide:
PARTITIONING SD CARD TO MOUNT /SYSTEM AND /DATA
Take the backup of your sd card data first
Make sure you have partitioned your sdcard before.
Connect your phone to your computer and mount usb storage.
Download the EASEUS partition manager from here.
Open partition manager and delete all partitions of your sdcard.
Right click on the 'unallocated' and click create partition.Don't label it select partition type as primary and filesystem as FAT32 and enter the partition size bot remember this will hold your photos,media etc,you should leave about 600 mb space free click OK.
right click again and create partition as primary and filesystem as EXT3 and size of 250 mb click OK.
Repeat above step again.
Apply all the changes by cliking on apply tap and you have succesfully partitioned your sdcard for dual booting.
​
GUIDE FOR THE TOOL
Extract the downloaded zip file extract to any concinient directory.Here I will explain the guide as a cygwin user.
Extract the zip to directory say c:\
The extracted folder will look like 'Modify-boot".Now open the terminal or cygwin bash and mount the directory by typing
cd c:\modify-boot
Click to expand...
Click to collapse
Now drop your boot.img in the WORKING_313 folder and execute the script by typing
./modify-boot.txt
Click to expand...
Click to collapse
It will mod your boot.img for dual booting.Output boot.img will be in the WORKING_313 folder as boot.img.
MODDING THE ROM FOR DUAL BOOTING
Open the ROM.zip.
Get the modded boot.img from the tool and replace with the original one.
Now download the attached updater-script from 1st post and replace the orignal one with this modded one(path to udater-script META-INF/com/google/android).
Zip up the rom.
ADAPTING A ROM TO INSTALL IN THE SD CARD
If you want to mod your own rom other than the posted here,then you have to mod the updater-script in the rom
For that open your rom zip go to /META-INF/com/google/android and open the updater script
Now replace every line looking like following as;
From
mount("yaffs2", "MTD", "system", "/system");
Click to expand...
Click to collapse
TO
run_program("/sbin/mount", "dev/block/mmcblk0p3", "/system");
Click to expand...
Click to collapse
and this one
From
format("yaffs2", "MTD", "system", "0");
Click to expand...
Click to collapse
TO
run_program("/sbin/mkfs.ext2", "dev/block/mmcblk0p3");
Click to expand...
Click to collapse
and add the following line next to the line written above
run_program("/sbin/mkfs.ext2", "dev/block/mmcblk0p2");
Click to expand...
Click to collapse
Save the file and zip up the rom.Your rom is ready to install to SD CARD!!!!
FLASHING GUIDE
Remember, before partitioning the sd card you should wipe data and cache in the recovery during NAND rom installation or it will erase the partitions created before.
First flash the rom you want to install in the NAND,do not wipe data or anything do it before partitioning.
Then install the rom without wiping data or anything.
reboot the system. You will be in your sd card rom!!!
Now create folder in the sd card as /sdcard/multiboot.
Take both boot.img from NAND rom and cm9 rom rename the cm9 boot.img to bootsd.img and keep the NAND boot.img as it is.
Copy both imgs to multiboot folder.
Now download attached(or use above link for unregistered users) bootnand.sh and bootsd.sh and place at the root of the sdcard.
Open terminal emulator,type su and execute bootsd.sh to boot into sd card rom or execute bootnand.sh to boot into NAND rom.
THAT'S IT . ENJOY DUAL BOOT ON YOUR ZTE BLADE!!!!

[email protected] said:
So here is the full guide:
PARTITIONING SD CARD TO MOUNT /SYSTEM AND /DATA
Take the backup of your sd card data first
Make sure you have partitioned your sdcard before.
Connect your phone to your computer and mount usb storage.
Download the EASEUS partition manager from here.
Open partition manager and delete all partitions of your sdcard.
Right click on the 'unallocated' and click create partition.Don't label it select partition type as primary and filesystem as FAT32 and enter the partition size bot remember this will hold your photos,media etc,you should leave about 600 mb space free click OK.
right click again and create partition as primary and filesystem as EXT3 and size of 250 mb click OK.
Repeat above step again.
Apply all the changes by cliking on apply tap and you have succesfully partitioned your sdcard for dual booting.
​
MODDING THE CM9 ROM FOR DUAL BOOTING
Open the konstakang.zip (currently only supported rom, will add more soon).
Download modded boot.img from here extract it and rename the .img file to boot.img.
Delete the boot.img from the cm9 rom and put the downloaded one.
Now download the attached updater-script (remove .txt) or from here (for unregistered users)and replace the orignal one with this modded one(path to udater-script META-INF/com/google/android).
Zip up the rom.
FLASHING GUIDE
Remember, before partitioning the sd card you should wipe data and cache in the recovery during NAND rom installation or it will erase the partitions created before.
First flash the rom you want to install in the NAND,do not wipe data or anything do it before partitioning.
Then install the cm9 rom without wiping data or anything.
reboot the system. You will be in your sd card rom!!!
Now create folder in the sd card as /sdcard/multiboot.
Take both boot.img from NAND rom and cm9 rom rename the cm9 boot.img to bootsd.img and keep the NAND boot.img as it is.
Copy both imgs to multiboot folder.
Now download attached(or use above link for unregistered users) bootnand.sh and bootsd.sh and place at the root of the sdcard.
Open terminal emulator,type su and execute bootsd.sh to boot into sd card rom or execute bootnand.sh to boot into NAND rom.
THAT'S IT . ENJOY DUAL BOOT ON YOUR ZTE BLADE!!!!
Click to expand...
Click to collapse
hi, thank u ....... the link for 'boot.img' is not working. Pls fix it

Can't thank you enough for this,if it works.. Great stuff btw.. At least,you were the first one that tried and got it working..
Sent from my LT26i using xda premium

karthiknr said:
Can't thank you enough for this,if it works.. Great stuff btw.. At least,you were the first one that tried and got it working..
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
+1
We've been waiting on this ever since karthik and wbaws discussion made it sound impossible

Just reported as a news tip for the portal

Thanks!!

New update coming for tool soon!!!

Its a great achievement .. future updates will be easy to go on for basic user. Btw thanks man. .
Sent from my Blade using Tapatalk 2

I've found that making four partitions and installing /data to mmcblk0p4 and /system to mmcblk0p3 helps with certain roms that have S2E configured.
I'm also trying to get it to boot two mounted loop filesystems instead, i installed SSRLS7 and GB-Gapps as per your instructions in the OP (just changed the partitions for installation and the updater-script and init.rc so that it would work) did a dd of the entire partitions to files on the sdcard and edited the init.rc like this:
Code:
on fs
# mount mtd partitions
chmod 777 /sbin/busybox
symlink /sbin/busybox /sbin/losetup
mount vfat /dev/block/mmcblk0p1 /mnt/sdcard
losetup /dev/block/loop0 /mnt/sdcard/multiboot/snow/system.img
losetup /dev/block/loop1 /mnt/sdcard/multiboot/snow/data.img
mount ext2 /dev/block/loop0 /system
mount ext2 /dev/block/loop1 /data
mount yaffs2 [email protected] /cache nosuid nodev
on post-fs
# ZTE_JCD_CTSCONFIG, 2011.05.03, BEGIN
mkdir /system/lost+found 0770
chmod 0770 /system/lost+found
# ZTE_JCD_CTSCONFIG 2011.05.03, END
# once system is setup, no need to modify /system , ZTE_BOOT_LIWEI_20110331
mount ext2 /dev/block/loop0 /system ro remount
I also copied busybox to /sbin in the ramdisk before letting the process finish and make bootsd.img
It doesn't work though and i have no idea why not. I've mounted the system.img and data.img files on the phone via the terminal to test if the procedure works and it does mount them just fine.
If anyone has any clue why this doesn't work then please tell me.

Dual boot on ideos x6
[email protected] said:
hello guys. This my dual booting project for our amazing zte blade!
What is this?
>this mod works on the basis of two scripts which are to be executed in the terminal emulator or script manager and a modified boot.img to boot the rom from sdcard instead of nand.
For advanced users only!!!
I will not be responsible for any bricked devices, damaged sdcards etc.
Do it at your own risk!!!
It is in alpha stage, so lot of work is still needed to make it more safer and convenient.
I will add this mod for more roms like cm10, paranoidandroid etc.
Downloads:
cyanogenmod9(konstakang)
boot.img - download
updater-script - download
cyanogenmod10
boot.img - download
updater-script - download
gapps::
Jelly bean gapps updater-script - download
tool:
Modify-boot - download
now no need to wait for me to mod your boot.img.mod your boot image for dual boot with this tool!!!
Guide for the tools is on the second post.
Thanks go to:
Sulthekk for guiding me towards right way.
Snap.it for giving me some mounting ideas.
All the people who have helped me(can't remember all names ).
And the big community to test it for me.
Scroll down to 2nd post for the whole guide...
Click to expand...
Click to collapse
dear friends is it possible on huawei ideos x6?
Plz reply

vimi93 said:
dear friends is it possible on huawei ideos x6?
Plz reply
Click to expand...
Click to collapse
Seriously? Dude can't u see this is the Blade forum. It will not work on any other phones

QuantumFoam said:
Seriously? Dude can't u see this is the Blade forum. It will not work on any other phones
Click to expand...
Click to collapse
Actually, it'll work on any phone that runs android and has a working recovery that can be used to install boot.img and system files via an updater script.
It works fine on my Mini and Huawai G300.

Jinxxed said:
Actually, it'll work on any phone that runs android and has a working recovery that can be used to install boot.img and system files via an updater script.
It works fine on my Mini and Huawai G300.
Click to expand...
Click to collapse
I stand corrected.
---------- Post added at 01:42 AM ---------- Previous post was at 01:37 AM ----------
Oh and btw, [email protected], check the xda portal. You're on the front page.
Congratulations

Jinxxed said:
Actually, it'll work on any phone that runs android and has a working recovery that can be used to install boot.img and system files via an updater script.
It works fine on my Mini and Huawai G300.
Click to expand...
Click to collapse
Will try it out on my LG P500 then!

thanks
Jinxxed said:
Actually, it'll work on any phone that runs android and has a working recovery that can be used to install boot.img and system files via an updater script.
It works fine on my Mini and Huawai G300.
Click to expand...
Click to collapse
thank you for the reply

[MOD][SCRIPT] Super WIPE Script HTC One | Aroma GUI (upd.18/03/2015)

This tool will allow you to easily WIPE system, data (except /data/media), boot (kernel) and cache partitions directly from custom recovery.
Before using this tool you need to be sure you are using latest version of custom recovery (TWRP or CWM). The current downloads for both CWM and TWRP can found below:
The latest M7 U/UL TWRP can be downloaded HERE. I recommend to use TWRP 2.6.3.0 (for v1.0.2d) and TWRP 2.8.5.* (for v2.0.2) .
v1.0.2d will work for Intarnational version, GE, T_Mobile, AT&T but NOT for SPRINT DEVICE
and v.2.0.2 - for all version!!!
To use this tool please copy zip file to your phone and then boot into custom recovery and choose Install. Then browse to where you copied zip file and select it. Aroma installer will begin. Choose options you want to run.
What script does:
1. Wipe /cache partition (select in Aroma);
2. Wipe delvik-cache (select in Aroma);
3. Wipe /system partition (select in Aroma);
4. Wipe /data partition except /data/media (select in Aroma);
5. Format boot partition (kernel) and removes /system/lib/modules (select in Aroma);
/system/lib/modules
/system/etc/init.d/01-h2w
/system/etc/init.d/01-pwp
/system/etc/init.d/01-therm
/system/etc/init.d/01-blinkbuttons
/system/etc/init.d/01-f2s
/system/etc/init.d/01-f2w
/system/etc/init.d/01-f2ws
/system/etc/init.d/01-f2wt
/system/etc/init.d/01-p2w
/system/etc/init.d/thoravukk
system/etc/init.d/89elementalx
/system/etc/init.d/99elementalx
/system/etc/init.d/99elementalx~
/system/etc/init.d/99bulletproof
/system/etc/init.d/56zram
/system/etc/init.d/30sweep2wake
/system/etc/elementalx.conf
/system/bin/fstrim
/system/usr/keylayout/synaptics-rmi-touchscreen.kl
/sys/android_touch/sweep2wake
/sys/android_touch/doubletap2wake
/sys/android_touch/logo2wake
/sys/android_touch/pocket_detect
/sys/android_touch/logo2menu
5. Removes some system files from /data/media;
/sdcard/.android_secure
/sdcard/.bookmark_thumb1
/sdcard/LazyList
/sdcard/LOST.DIR
/sdcard/.data/footprints
/sdcard/.data/mail
sdcard/Android/data/com.android.providers.media
/sdcard/Android/data/com.google.android.apps.genie.geniewidget.news-content-cache
/sdcard/Android/data/com.google.android.apps.maps
/sdcard/.data/navigator/Data/Temporary
6. Check partitions for errors;
7. Create a log of work on internal memory card.
This operation will remove all your data except for /data/media.
If you wipe ONLY BOOT, then you must to flash new kernel and kernel modules too (/system/lib/modules)!
Make sure that you have nandroid backup and Titanium backup before a full wipe!!!
You must have new ROM on /data/media to flash after full wipe!!!
If AROMA Installer stops at 0%, then you must to press Power button and hold 15-17 seconds to reboot. Then go to recovery and start installation again. This will help you.
***Credits***
amarullz for his AROMA Installer Script.
mike1986 for his SUPER WIPE script for Android Revolution HD.
Venom Team for updater-script for ViperOne.
LlabTooFeR for his updater-script for Maximus.
***Download***
Super_Wipe_HTC_One_FULL_v2.0.2.zip - some updates from 18/03/15
Arhive:
Super_Wipe_HTC_One_FULL_v1.0.2d.zip - 2.66 MB - some updates from 24/11/13
md5: 60cff28e4f5ec11e11c15e7d37c54d35
Enjoy!

Version for HTC ONE M9 (ONLY!!!!)
(Russian interface)
Download:
Super_Wipe_HTC_One_M9_FULL_v3.0.1_RUS.zip

Thank you! :good:

Excellent, i miss this scripts since DHD days Thanks mate...

@Golv - good job

i want to wipe everything except the contents on my sdcard download folder > eg. downloaded roms for flashing in TWRP
what should i choose.
what is this script do is the same as wiping in TWRP recovery?

Magpir said:
i want to wipe everything except the contents on my sdcard download folder > eg. downloaded roms for flashing in TWRP
what should i choose.
what is this script do is the same as wiping in TWRP recovery?
Click to expand...
Click to collapse
You must select all of items then will be deleted data, system, cache the boot partitions, after that you can return back into recovery, choose Install and select rom to flash.
This script makes a wipe as well as in TWRP recovery. It's more convenient to use script for somebody ...

Golv said:
You must select all of items then will be deleted data, system, cache the boot partitions, after that you can return back into recovery, choose Install and select rom to flash.
This script makes a wipe as well as in TWRP recovery. It's more convenient to use script for somebody ...
Click to expand...
Click to collapse
i dont understand what this script does is wipe more stuff than the standard TWRP recovery or what?
isnt wiping the boot partitions dangerous?

Magpir said:
i dont understand what this script does is wipe more stuff than the standard TWRP recovery or what?
isnt wiping the boot partitions dangerous?
Click to expand...
Click to collapse
In TWRP all the same, except wipe of boot partition. And there is no partition format /data/media in this script.
Boot partition can be flashed into bootloader (fastboot usb) through:
Code:
fastboot flash boot boot.img
or through:
Code:
fastboot oem rebootRUU
fastboot flash zip boot.zip
(If you S-OFF you can put into zip 2 files: boot.img and android-info.txt, if s-on - signed firmware.zip)
or into custom recovery (zip).
It's dangerous to delete HBOOT partition! In this case - bricks. If you erased boot partition then you can enter into bootloader and recovery and restore all things! ...

so are u telling me that yr script is different from wiping in TWRP ?
So yr script dont delete Hboot partition?

Do not worry! :laugh:
This script don't delete Hboot partition!

so its safe to use?

I checked all items of script on myself. All safe. And if someone does not think before to do something, it is always dangerous!

Awesome, been using a wipe script for the galaxy nexus, great to have one for the One, thanks OP!

when i use this script.
checked all options and wipe.. no rom and no kernel on my phone?
flash now a rom without choose fullwipe in aroma..
why all my apps on phone, my own homescreen?
sent from my HTC One powered by ViperOne

Hopie, thank you! Try this version. Super_Wipe_HTC_One_FULL_v1.0.2d.zip - 2.66 MB An updated version in OP.

Молодец, @Golv. Так держать.
Great work! Thanks.

forgot to answer
with new version all ok..
ium think u know it ^^
sent from my HTC One powered by IronByte

works this script on android 5?

Hopie said:
works this scriot on androud 5?
Click to expand...
Click to collapse
Yes.

How to fix 'E: Can't Mount Cache' in CWM

This happens when you wipe the cache, but it does not mean anything is wrong with your phone.
E: Can't mount /cache/recovery/log and the other five errors are similar to this.
PERFORM A BACKUP PRIOR TO THIS
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE.
Start by going into your recovery..
If you want to keep the ROM you have, then follow these directions. When flashing a new ROM follow the next set of directions.
KEEPING YOUR CURRENT ROM
1) Go into your recovery
2) Go to mounts and storage
3) Format /cache x3
4) Go to advanced in the main menu
5) Reboot recovery
If it is not working, repeat the steps.
FLASHING A NEW ROM
1) Go into your recovery
2) Format /system /data /cache x3 (Like any normal flashing of a ROM)
3) Install the ROM you want to use
4) Go to mounts and storage
5) Format /cache
6) Go to advanced in the main menu
7) Reboot recovery
8) Boot into your newly flashed ROM
I made this thread because some people still have this error show up even though it doesn't affect the way you flash a ROM.. It's just annoying to see that come up every time you hit the back button in CWM.

syedwaseem said:
This happens when you wipe the cache, but it does not mean anything is wrong with your phone.
E: Can't mount /cache/recovery/log and the other five errors are similar to this.
PERFORM A BACKUP PRIOR TO THIS
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE.
Start by going into your recovery..
If you want to keep the ROM you have, then follow these directions. When flashing a new ROM follow the next set of directions.
KEEPING YOUR CURRENT ROM
1) Go into your recovery
2) Go to mounts and storage
3) Format /cache x3
4) Go to advanced in the main menu
5) Reboot recovery
If it is not working, repeat the steps.
FLASHING A NEW ROM
1) Go into your recovery
2) Format /system /data /cache x3 (Like any normal flashing of a ROM)
3) Install the ROM you want to use
4) Go to mounts and storage
5) Format /cache
6) Go to advanced in the main menu
7) Reboot recovery
8) Boot into your newly flashed ROM
I made this thread because some people still have this error show up even though it doesn't affect the way you flash a ROM.. It's just annoying to see that come up every time you hit the back button in CWM.
Click to expand...
Click to collapse
I have tried this but this does not work. I am Using PhilZ CWM 6.49.2. I cant even Flash A Custom ROM Because of this problem it would just show me these error messages and say "Installation Aborted" and restart phone.
I have also Flashed back the Stock ROM and repeated all of the procedures: 1.Framaroot 2:CWM
Still no success it just keeps giving me these stupid errors, Please Find a FIX.
THANKS

dima234 said:
I have tried this but this does not work. I am Using PhilZ CWM 6.49.2. I cant even Flash A Custom ROM Because of this problem it would just show me these error messages and say "Installation Aborted" and restart phone.
I have also Flashed back the Stock ROM and repeated all of the procedures: 1.Framaroot 2:CWM
Still no success it just keeps giving me these stupid errors, Please Find a FIX.
THANKS
Click to expand...
Click to collapse
I have the same problem.
I tried methods:
$ su
#dd if = / sdcard / recovery.img of = / dev / block / mmcblk0p13
It does not work.
I installed the stock rom and checked the partition mmcblk0p13 with "Partition Table" and the partition is not mounted.
Maybe this is the problem?

meriox said:
I have the same problem.
I tried methods:
$ su
#dd if = / sdcard / recovery.img of = / dev / block / mmcblk0p13
It does not work.
I installed the stock rom and checked the partition mmcblk0p13 with "Partition Table" and the partition is not mounted.
Maybe this is the problem?
Click to expand...
Click to collapse
Yea even i have tried the same but it does not work, guess we have to stick to the stock ROM till someone finds a fix.

dima234 said:
Yea even i have tried the same but it does not work, guess we have to stick to the stock ROM till someone finds a fix.
Click to expand...
Click to collapse
Do you think that someone will be looking to solve the problem?
It seems to me that the problem occurs only in the new models that have been bought recently.
I tried to install the older stock firmware but it did not help.
None of the methods that have been on the forum does not work.
The problem occurs only when WIPE DATA / FACTORY RESET.

meriox said:
Do you think that someone will be looking to solve the problem?
It seems to me that the problem occurs only in the new models that have been bought recently.
I tried to install the older stock firmware but it did not help.
None of the methods that have been on the forum does not work.
The problem occurs only when WIPE DATA / FACTORY RESET.
Click to expand...
Click to collapse
yea getting the same problem here.
cant mount system
cant mount cache
and most of all when install custom ROM. cannot continue since non of those partitions cannot mount properly.
and other errors are flooding the recovery, we have tried Philz, CWM, TWRP. same annoying problems.

Hello,
On another website I found this:
"All worked fine but that like of command in terminal you put there isn't right, i did this
$ su [and then enter]
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p32 [and then enter]
# reboot recovery [and then enter]
PS: the $ comes automatically when you start the terminal emulator app; the # comes automatically after you allow the super user [in $ su]
Do consider all the "Spaces" between symbols and paths!"
Has anyone used this method?

syedwaseem said:
This happens when you wipe the cache, but it does not mean anything is wrong with your phone.
E: Can't mount /cache/recovery/log and the other five errors are similar to this.
PERFORM A BACKUP PRIOR TO THIS
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE.
Start by going into your recovery..
If you want to keep the ROM you have, then follow these directions. When flashing a new ROM follow the next set of directions.
KEEPING YOUR CURRENT ROM
1) Go into your recovery
2) Go to mounts and storage
3) Format /cache x3
4) Go to advanced in the main menu
5) Reboot recovery
If it is not working, repeat the steps.
FLASHING A NEW ROM
1) Go into your recovery
2) Format /system /data /cache x3 (Like any normal flashing of a ROM)
3) Install the ROM you want to use
4) Go to mounts and storage
5) Format /cache
6) Go to advanced in the main menu
7) Reboot recovery
8) Boot into your newly flashed ROM
I made this thread because some people still have this error show up even though it doesn't affect the way you flash a ROM.. It's just annoying to see that come up every time you hit the back button in CWM.
Click to expand...
Click to collapse
Thanks worked for me :good:

bricked
I've got these errors on my htc desire x, I made a backup, after that, I try to flash a new rom, with the steps written in the first post. The result was: after the htc logo, it showed a black screen! I try to restore the backup, but I cant restore!!!!! I've got soft brick, so I take it a service. I hope, they can fix it

Recovering from /data mount issues

Guys,
I have had an device impacted by TWRP 2.7.X build that created the problem of not being able to mount /data and sometimes(/cache & /system) partitions.
I have managed to make it run a ROM by using information from
http://forum.xda-developers.com/showthread.php?t=1869673 & http://forum.xda-developers.com/showthread.php?t=1843062.
the problem is that the mounts are not remaining permanent and my modified boot.img does not boot the devices. So i have to mount the partition manually during the boot process over a shell and then the device boots.
Need help from experts to do a kernel which can mount sdext partition and an updated recovery image which also mounts the sdext partition as /data so that roms can be flashed easily.
I will try and do a writeup of how i made it run.

Resurrecting Pyramid
As mentioned in the earlier thread, my sensation got into trouble with TWRP 2.7 version and i was having trouble mounting /data, /system and /cache partitions.
I eventually got the /cache partition mounted by using mkfs.ext4 utility but could not get other and hence started working on a way to move both /data and /system partitions completly off SD card. Lot of people have already attempted that for other devices, feel free to go and check the threads linked in the post 1. Lets get started:
Assumptions: You have a sensation on which /data and /system partitions are an issue - not getting mounted / formatted etc. /cache is expected to be ok/working.
Requirements:
1) Your phone is booting and can go into recovery. Please get 4EXT recovery installed. You can download an img file from here
2) You have basic adb and fastboot setup on your machine(Win/Linux). Just google them out, if you dont have , there are plenty of tools out there.
3) Download Revelation 1.0.3 from here. you can choose any other ROM but i worked on this and have the boot image patched to look at /system from sd-ext.
4) download the two files attached with this thread.
Steps to recover:
1) Boot your phone in recovery. We will first get the SD Card set up. A Class 10 card is preferred, you will have a good feel on the phone.
2) Using 4EXT partition tool for sd card, create 2 sd ext partition in addition to your sdcard. I suggest first partition(which we will use as /system) to be more than 800 MB and second partition( which we will use as /data) to be more than 1024 MB.
3) Verify using the 'info' option of 4ext recovery that you can see sd-ext, sd-ext2 and sdcard partitions.
4) Extract the ROM you have downloaded using 7z/Winzip /winrar and replace the following files you have downloaded from this thread.
a) updater-script in /META-INF/com/google/android/ folder.
b) boot.img in /KERNEL folder.
5) Zip the file again and copy to your sdcard. Choose install from sdcard from the 4ext recovery menu. Choose default options in AROMA installer.
6) Reboot.
Hope your phone boots. If not, this is how you debug
Android will create a /proc/kmsg file when the kernel boots. So open two terminal(linux) windowds, in one, type this
Code:
adb pull /proc/kmsg
and in the second terminal(make sure the directory is same), type this:
Code:
cat kmsg | less
and then go through the error messages to see what is going wrong. If you can share your kmsg file created, I can try and help you debug.
Good luck !!!!!

Hi,
I followed your instructions but the Aroma installer always stops and the log shows this:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:00:31 1970
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
line 44 col 70: syntax error, unexpected BAD
2 parse errors
Installer Error (Status 6)

Jack Daniel's said:
Hi,
I followed your instructions but the Aroma installer always stops and the log shows this:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:00:31 1970
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
line 44 col 70: syntax error, unexpected BAD
2 parse errors
Installer Error (Status 6)
Click to expand...
Click to collapse
Pick the files from here and then try...
http://forum.xda-developers.com/htc-sensation/help/bricked-htc-corrupted-partitions-t2804222/page3

rmann said:
Pick the files from here and then try...
http://forum.xda-developers.com/htc-sensation/help/bricked-htc-corrupted-partitions-t2804222/page3
Click to expand...
Click to collapse
I tried that before.
Same result but it shows one error less.
Code:
...
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
Installer Error (Status 6)

Jack Daniel's said:
I tried that before.
Same result but it shows one error less.
Code:
...
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
Installer Error (Status 6)
Click to expand...
Click to collapse
Which recovery are you using... I have re-tested the script and it works ok for me.

rmann said:
Which recovery are you using... I have re-tested the script and it works ok for me.
Click to expand...
Click to collapse
I get the same exact error as Jack Daniel's.
I am using as recovery 4EXT Recovery Touch v1.0.0.5 RC5.

antiziclon said:
I get the same exact error as Jack Daniel's.
I am using as recovery 4EXT Recovery Touch v1.0.0.5 RC5.
Click to expand...
Click to collapse
did you try to update the recovery to the latest version?

rzr86 said:
did you try to update the recovery to the latest version?
Click to expand...
Click to collapse
Just tested with v1.0.0.6 RC3 build 8, same error

antiziclon said:
Just tested with v1.0.0.6 RC3 build 8, same error
Click to expand...
Click to collapse
redownload the zip file
after that i am out of ideas

ok, I found out the issue.
The issue is on the encoding of the "updater-script" file.
It needs to be in Unix encoding. If you use Windows (as I do) when unzipping the Zip file or when creating a new file with a text editor, the encoding gets changed and it is not Unix encoding.
To solve it:
- Open the file in Notepad++.
- Go to Edit --> EOL Conversion --> UNIX
It will change the enf of lines to comply with Unix encoding. Then add the file to the Rom zip file and you are ready to go
Enjoy!

Successful Pyramid rescue
I have a sensation with corrupted emmc caused by TWRP, /data cannot be mounted.
I followed your instructions and addition re script encoding and successfully installed Revelation to partitioned sdcard.
Phone boots and works.
That's great, thanks.
I have some questions:
1. Is 512 MB sufficient for swap partition? What would be the optimal size?
2. My sensation is s-on unlocked, and I had to flash boot via fastboot after install, 4ext did not flash it despite smartflash option turned on. Is that normal?
2. Superuser does not seem to work, I have no root. I checked with root validator and I have su binary, superuser and busybox, but no root is given to apps that require it, su binary update fails, and there are no logs left in superuser to check (or I simply don't know where to look).
Thank you.

rmann said:
As mentioned in the earlier thread, my sensation got into trouble with TWRP 2.7 version and i was having trouble mounting /data, /system and /cache partitions.
I eventually got the /cache partition mounted by using mkfs.ext4 utility but could not get other and hence started working on a way to move both /data and /system partitions completly off SD card. Lot of people have already attempted that for other devices, feel free to go and check the threads linked in the post 1. Lets get started:
Assumptions: You have a sensation on which /data and /system partitions are an issue - not getting mounted / formatted etc. /cache is expected to be ok/working.
Requirements:
1) Your phone is booting and can go into recovery. Please get 4EXT recovery installed. You can download an img file from here
2) You have basic adb and fastboot setup on your machine(Win/Linux). Just google them out, if you dont have , there are plenty of tools out there.
3) Download Revelation 1.0.3 from here. you can choose any other ROM but i worked on this and have the boot image patched to look at /system from sd-ext.
4) download the two files attached with this thread.
Steps to recover:
1) Boot your phone in recovery. We will first get the SD Card set up. A Class 10 card is preferred, you will have a good feel on the phone.
2) Using 4EXT partition tool for sd card, create 2 sd ext partition in addition to your sdcard. I suggest first partition(which we will use as /system) to be more than 800 MB and second partition( which we will use as /data) to be more than 1024 MB.
3) Verify using the 'info' option of 4ext recovery that you can see sd-ext, sd-ext2 and sdcard partitions.
4) Extract the ROM you have downloaded using 7z/Winzip /winrar and replace the following files you have downloaded from this thread.
a) updater-script in /META-INF/com/google/android/ folder.
b) boot.img in /KERNEL folder.
5) Zip the file again and copy to your sdcard. Choose install from sdcard from the 4ext recovery menu. Choose default options in AROMA installer.
6) Reboot.
Hope your phone boots. If not, this is how you debug
Android will create a /proc/kmsg file when the kernel boots. So open two terminal(linux) windowds, in one, type this
Code:
adb pull /proc/kmsg
and in the second terminal(make sure the directory is same), type this:
Code:
cat kmsg | less
and then go through the error messages to see what is going wrong. If you can share your kmsg file created, I can try and help you debug.
Good luck !!!!!
Click to expand...
Click to collapse
Ok try to make that in unix

Extreme lag
Hi there,
I followed all the staps, but when the rom was installed, it was very laggy and i experinced a lot of force closes. Is this because the partions are to small or because the sd is to slow EDIT: its a class 4 card?
Greetings,
Danil

Extreme unuseful slow
With my sensation XE i also followed all steps. Revelation 1.0.3 is booting, but not to use at all, it stucks in every step, cant even receive a call, can't go to any menu. Pls someone help me out of here. Do I need a swap partition? Or are the partitions to small? sd-ext has 1024Mib; sd-ext2 1537Mib.

danilandroid said:
Hi there,
I followed all the staps, but when the rom was installed, it was very laggy and i experinced a lot of force closes. Is this because the partions are to small or because the sd is to slow EDIT: its a class 4 card?
Greetings,
Danil
Click to expand...
Click to collapse
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner

dididoner said:
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
Click to expand...
Click to collapse
probably you need a sdcard with high speed of w/r but i am not sure

Lag
rzr86 said:
probably you need a sdcard with high speed of w/r but i am not sure
Click to expand...
Click to collapse
I'm going to buy a sd-card class 10 and than I will try the same thing agian. I will report later.
@ rmann Btw thanks for the amazing thread, I was completely stuck and now my phone is alive again kinda.
Danil

danilandroid said:
I'm going to buy a sd-card class 10 and than I will try the same thing agian. I will report later.
@ rmann Btw thanks for the amazing thread, I was completely stuck and now my phone is alive again kinda.
Danil
Click to expand...
Click to collapse
rzr86 said:
probably you need a sdcard with high speed of w/r but i am not sure
Click to expand...
Click to collapse
dididoner said:
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
Click to expand...
Click to collapse
So, I bought a class 10 card, revelation is running now!! At first start it was still very slowly an got stuck allover. But at second start it is running now! Thanks for that perfect thread!!:good:
I wonderd why vipers wont start the same way? When I try to boot it , 4ext recovery is starting rightaway with little delay!

Hi, when I got the same problem with /data, /cache and /system not mounting. I followed the steps from #2 post http://forum.xda-developers.com/showpost.php?p=55157092&postcount=2
and when I try to install from zip it says that the zip isn't meant to be flashed in recovery and it aborts the installation. First I tried renaming the new_boot.img you provided to boot.img but it's the same result.