Database Info

NANDROID RESTORE WITHOUT FASTBOOT?? - does it really work?

ok so im confused. I was reading the "how to flash cupcake" thread and came across this post by ridli. i tried following the instructions below but they failed, it seems like it works for him. if this truly works then there is no need for fastboot to reflash a nandroid back up. please help. thnx. BTW dudes .8 G build is awesome. (posted from my G1-modded w/root and gloss suite theme)
I tried the below on my G1 using recovery mode from JF-RC33 and i get:
error opening /sdcard/bu/system.img: no such file or directory.
I have checked the sdcard and its there, please help.
ridli said:
You can do the same without linux or any other SO.
1) Download cupcake
2) copy IMG files to a DIR in your SDCARD
3) reboot the phone in recovery mode
4) press ALT+X for go to console
5) #mount -a (for mount all partitions, without this you dont have flash_image becouse it is in /system/bin/)
6) use flash_image for flash the partitions
Code:
#flash_image system /sdcard/<dir>/system.img
#flash_image boot /sdcard/<dir>/boot.img
#flash_image userdata /sdcard/<dir>/data.img
7) #reboot
Optional: Do a backup of the phone with nandroid from the recovery mode, this do a img of system, data and boot partitions of your phone and copy to your sdcard. If you have any problem you can reflash your phone with you img.
Click to expand...
Click to collapse

It didn't work for me either, but it said I could not remount system as r/w because it was busy.
Anyway, I find instructions on how to do it via PC a lot easier. And if your phone would not boot, and you are stuck without backup, you can always pull it with adb.

Karolis:
System shouldn't be busy in recovery mode... also, it shouldn't be mounted if you're trying to write a fs image
And... no, if your phone can't boot, it can't boot. That includes starting adbd.
If you can enter recovery/spl, it's booting just fine.
flak0:
Have you checked the sdcard from the shell in android, or from your computer?
If it's the latter, you should make sure you can access the file from android.
I would recommend that you copy the flash_image binary out of /system (and /data), because you're rewriting that partition

Okay, don't use the forums when on a bad connection... my browser thought it lost connection, and decided to refresh, and send my post again... *Looks for a delete button*

this does not work
just so everyone is clear
DOES NOT WORK!
Note To Self, do not follow tutorials from junior members

arteshiftedscreen said:
this does not work
just so everyone is clear
DOES NOT WORK!
Note To Self, do not follow tutorials from junior members
Click to expand...
Click to collapse
Ummmm actually this does work if you do itcorrectly. Note to self no bashing people that are just trying to help.

so how is it done?
korndub said:
Ummmm actually this does work if you do itcorrectly. Note to self no bashing people that are just trying to help.
Click to expand...
Click to collapse
And could a Gscript or similar be written to do something like this? I'd be psyched to have the option to restore my phone on the fly. And of course, if you could do that, what would stop you from having a Nandroid restore point saved for a number of different builds? I would love that.

Out of curiosity, and I've never tried this method myself, are you just entering the following exactly?
#flash_image system /sdcard/<dir>/system.img
#flash_image boot /sdcard/<dir>/boot.img
#flash_image userdata /sdcard/<dir>/data.img
Click to expand...
Click to collapse
Or are you changing <dir> to the directory of your nandroid backup? Because if you aren't it certainly won't work.

ei8htohms said:
And could a Gscript or similar be written to do something like this? I'd be psyched to have the option to restore my phone on the fly. And of course, if you could do that, what would stop you from having a Nandroid restore point saved for a number of different builds? I would love that.
Click to expand...
Click to collapse
But it would be very unsafe to flash a fs image when the partition is actually mounted and your gscript is probably in it.
the only way is to do it in recovery mode.
one little problem though: i copied flash_image to /cache and chmod, but the shell kept telling me no such file. why is that?

billc.cn said:
But it would be very unsafe to flash a fs image when the partition is actually mounted and your gscript is probably in it.
the only way is to do it in recovery mode.
one little problem though: i copied flash_image to /cache and chmod, but the shell kept telling me no such file. why is that?
Click to expand...
Click to collapse
flash_image is a binary, should not be moved. why did you move it to cache? of course it wont work...

Unfortunately, flash_image does not support writing yaffs2 images. Look in the code, there's no support for writing the OOB data to the NAND. If it was possible I would've integrated backup AND restore in nandroid 2.0, and JesusFrekes recovery image would then also have a restore option. But alas, it's not to be.
Perhaps in a future release I can find a C coder who can add the code to the flash_image source, so that this becomes possible. But I'm not even sure if that can be done (because you need kernel driver support as well).

infernix said:
Unfortunately, flash_image does not support writing yaffs2 images. Look in the code, there's no support for writing the OOB data to the NAND. If it was possible I would've integrated backup AND restore in nandroid 2.0, and JesusFrekes recovery image would then also have a restore option. But alas, it's not to be.
Perhaps in a future release I can find a C coder who can add the code to the flash_image source, so that this becomes possible. But I'm not even sure if that can be done (because you need kernel driver support as well).
Click to expand...
Click to collapse
Can't we just use nandwrite from mtd-utils to do this? I haven't tried it yet (I'll build it for ARM when I get home from work), but it appears to be the right tool for the job. I'm really interested in getting a menu-driven restore in my recovery image.

cyanogen said:
Can't we just use nandwrite from mtd-utils to do this? I haven't tried it yet (I'll build it for ARM when I get home from work), but it appears to be the right tool for the job. I'm really interested in getting a menu-driven restore in my recovery image.
Click to expand...
Click to collapse
Oh that would be sooooooooo sweet!

[Q] Bricked Note. No Samsung Logo

hi all,
So, I've been a bit of a idiot.
In a nut shell I was trying to manually remove the flash count and followed the wrong tut.
I did dd if=/dev/zero of=/dev/block/mmcblk0 bs=1 count=1 seek=3145732 and now when i try to boot the note I dont get the Samsung logo splash screen, I get a screen full of static.
I can access the recovery partition, I can also access in download mode with odin.
If I try to flash the stock rom, it completes ok but doesn't auto restart and stays on the odin mode screen.
I do get E:\ unable to mount /efs when i wipe the cache's.
I have a 2nd note 10.1 (both n8010) so I'm hoping I can fix/copy/image from the 2nd working device.
Any ideas on how to fix? or is it now an expensive paper weight?
I have flashed the stock firmware and rom from samsung-mobile but no joy.
thanks,

http://forum.xda-developers.com/showthread.php?t=2087567
blastman said:
hi all,
So, I've been a bit of a idiot.
In a nut shell I was trying to manually remove the flash count and followed the wrong tut.
I did dd if=/dev/zero of=/dev/block/mmcblk0 bs=1 count=1 seek=3145732 and now when i try to boot the note I dont get the Samsung logo splash screen, I get a screen full of static.
I can access the recovery partition, I can also access in download mode with odin.
If I try to flash the stock rom, it completes ok but doesn't auto restart and stays on the odin mode screen.
I do get E:\ unable to mount /efs when i wipe the cache's.
I have a 2nd note 10.1 (both n8010) so I'm hoping I can fix/copy/image from the 2nd working device.
Any ideas on how to fix? or is it now an expensive paper weight?
I have flashed the stock firmware and rom from samsung-mobile but no joy.
thanks,
Click to expand...
Click to collapse
You are in a tough situation my friend

I think as long as the recovery and odin work there is a chance...
can you give me the link to that tutorial .. I think i may help
Or do you remember where that sector was??
Anyways you may try to backup both devices EFS (backup that of the non working device in case you need it for anything) .... (But i think the EFSPro wont work) (you may do that using EFSpro or i think it may be done through the shell by "dd if=dev/block/mmcblk0p? of=/sdcard/efs.img" where "?" is the number of EFS partition you can know that from shell command mount "i think its mmcblk0p3") .... then restore the EFS of the working device to the non-working one (EFS pro or using "dd if=/sdcard/efs.img of=/dev/block/mmcblk0p?" "i think its mmcblk0p3")
I hope this would succeed although i red that it contains MAC address data which may prevent both devices connecting to same network
(N8010 has no connection to cellular networks so i think no problem)

Scorpion_Ibm said:
I think as long as the recovery and odin work there is a chance...
can you give me the link to that tutorial .. I think i may help
Or do you remember where that sector was??
Anyways you may try to backup both devices EFS (backup that of the non working device in case you need it for anything) .... (But i think the EFSPro wont work) (you may do that using EFSpro or i think it may be done through the shell by "dd if=dev/block/mmcblk0p? of=/sdcard/efs.img" where "?" is the number of EFS partition you can know that from shell command mount "i think its mmcblk0p3") .... then restore the EFS of the working device to the non-working one (EFS pro or using "dd if=/sdcard/efs.img of=/dev/block/mmcblk0p?" "i think its mmcblk0p3")
I hope this would succeed although i red that it contains MAC address data which may prevent both devices connecting to same network
(N8010 has no connection to cellular networks so i think no problem)
Click to expand...
Click to collapse
this?
http://forum.xda-developers.com/showthread.php?p=37465299

jaydubbbbs said:
this?
http://forum.xda-developers.com/showthread.php?p=37465299
Click to expand...
Click to collapse
But before all these go to shell and try "dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img" and "tar -cvf /sdcard/EFS.tar /dev/block/mmcblk0p3"
if these commands succeed you would have a backup of old efs before changing any thing (keep it in a safe place)
Look you may try just backing up and then restoring the same EFS of the device
Try this first: use the tar command to copy the files of EFS "tar -cvf /sdcard/EFS.tar /dev/block/mmcblk0p3"
then do " mke2fs /dev/block/mmcblk0p3" the last thing is to restore the tar with "tar -xvzf /sdcard/EFS.tar -C /dev/block/mmcblk0p3"
I prefer you try what i said first as it's shorter and makes nearly the same thing except that it takes all files not just the nv_data.bin
You can then try that tutorial in the link i think it works and you can get the that file nv_data.bin from your other device or from the non-functioning one if you can extract it from the tar backup in the first step

Cheers for the replies guys.
I'll find the tut I followed and post a link.
I'll also look into the link and suggestions you've mentioned.
My main issue seems to be that I can't get a adb connection to the device as it won't boot.
Even with cwm 6.1 installed, I still can't connect. Bear in mind, I've flashed back to stock but not been able to boot it to put it into usb debugging mode. does this mean I'll never be able to get a shell open?
I have managed to create a efs.img from the working device but have no way to push to the broken one.
Any suggestions?
Thanks

blastman said:
Cheers for the replies guys.
I'll find the tut I followed and post a link.
I'll also look into the link and suggestions you've mentioned.
My main issue seems to be that I can't get a adb connection to the device as it won't boot.
Even with cwm 6.1 installed, I still can't connect. Bear in mind, I've flashed back to stock but not been able to boot it to put it into usb debugging mode. does this mean I'll never be able to get a shell open?
I have managed to create a efs.img from the working device but have no way to push to the broken one.
Any suggestions?
Thanks
Click to expand...
Click to collapse
You say that adb wont work even from CWM??
Try this and see if it works http://www.dominantwire.com/2012/11/how-to-solve-adb-device-not-found-error.html

yep, even when booted into cwm recovery i still can;t connect to adb
just downloading a custom rom now to see if it's the stock rom causing the issue.
although I am able to access adb in cmw recovery from the other working device, even with USB debugging turned off.

sadly that link is no good.
I'm able to connect to the working device on the same cwm recovery version, using the same cable, so setup and PC are ok.
I dont know if the roms are the same (maybe not) but I'll flash the broken one with a custom 'pre rooted' rom in case it helps.

blastman said:
yep, even when booted into cwm recovery i still can;t connect to adb
just downloading a custom rom now to see if it's the stock rom causing the issue.
although I am able to access adb in cmw recovery from the other working device, even with USB debugging turned off.
Click to expand...
Click to collapse
Ok try another rom as i think roms have diferences in adb !!
if not working also and If you know you can safely flash a new recovery .. try TWRP it has an inbuilt shell .. the keyboard is not that good but you can try it better than nothing

ok so....
I've flashed an different custom rom via cwm install from ext_sdcard. After a reboot I now have the samsung logo back!!!!
It's hung on the samsung logo for a wile now, 5 minutes or so, but I'll let it sit there for a good 30 minutes to be sure.
I'll see what happens from this rom flash, but failing this I'll stick TRWP on and have a go with the inbuilt shell. even if i can mount ext sd I should be able to restore the block i over wrote.
getting closer!!!
thanks so far,

blastman said:
ok so....
I've flashed an different custom rom via cwm install from ext_sdcard. After a reboot I now have the samsung logo back!!!!
It's hung on the samsung logo for a wile now, 5 minutes or so, but I'll let it sit there for a good 30 minutes to be sure.
I'll see what happens from this rom flash, but failing this I'll stick TRWP on and have a go with the inbuilt shell. even if i can mount ext sd I should be able to restore the block i over wrote.
getting closer!!!
thanks so far,
Click to expand...
Click to collapse
Good to hear .. i hope it finishes the problem .. but in case it fails before flashing TWRP try from adb .. adb kill-server then adb start-server and adb usb and see if it works

will do, thanks.
I've just noticed that the command i ran I outputted to mmcblk0 and your commands refer to mmcblk0p3.
Am i right in guessing the the 0 part lists the disk and the px part is referring to the partition on that disk (so to speak)?
so my original command which broke it basically wiped the internal storage? this would explain a lot about failed connections as well.

blastman said:
will do, thanks.
I've just noticed that the command i ran I outputted to mmcblk0 and your commands refer to mmcblk0p3.
Am i right in guessing the the 0 part lists the disk and the px part is referring to the partition on that disk (so to speak)?
so my original command which broke it basically wiped the internal storage? this would explain a lot about failed connections as well.
Click to expand...
Click to collapse
Did the device work or did you manage to get adb connection??
Anyways ... from what i read during searching is that if=/dev/zero and bs=1 count=1 seek=3145732 parts of your command writes zeros only to one byte, one time after seeking 3145732 blocks of the storage which seems to be in EFS partition which says cant mount ... So the commands i wrote are to take a backup of whatever files in there then format the drive and restore the files back to it ... after formating using mke2fs reboot the device before restore and see if it shows the cant mount message again

arh ok, that makes sense.
I've managed to tar the efs files form the working device.
I then opened the shell in twrp and did a mke2fs /dev/block/mmcblk0p3 which completed ok.
But when i try to tar -xvzf EFS.tar -C /dev/block/mmcblk0p3 (from the external sd dir, it tells me that the mmcblk0p3 isn;t a directory.
any ideas?
thanks again

how about doing a dd if=efs.img of=/dev/block/mmcblk0p3??
I got a efs.img from efs pro on the working device..

blastman said:
arh ok, that makes sense.
I've managed to tar the efs files form the working device.
I then opened the shell in twrp and did a mke2fs /dev/block/mmcblk0p3 which completed ok.
But when i try to tar -xvzf EFS.tar -C /dev/block/mmcblk0p3 (from the external sd dir, it tells me that the mmcblk0p3 isn;t a directory.
any ideas?
thanks again
Click to expand...
Click to collapse
try remove -C from the command it's for directory my mistake
and you can also try dd with (if=/"path of extsd"/EFS.img) but try the tar first .... after that see if it tells you cant't mount EFS by opening mount and select EFS and see if it becomes with an 'x' then going to the upper right corner of the screen and pressing the icon beside back and home and see if it shows cant mount EFS

sorry, before you replied i went and did a dd if=efs.img of=/dev/block/mmcblk0p3
I then flashed the stock ROM and BOOM!! im in!!
YEAH BABY!!!
only issue now is that the boot loader isn't quite right.
1 - it doesn't show the 'Samsung Galaxy Note 10.1" splash screen
2 - instead of above I get a screen showing the last thing i was doing, ie, download mode, but with static across it.
any ideas on how to correct this?

blastman said:
sorry, before you replied i went and did a dd if=efs.img of=/dev/block/mmcblk0p3
I then flashed the stock ROM and BOOM!! im in!!
YEAH BABY!!!
only issue now is that the boot loader isn't quite right.
1 - it doesn't show the 'Samsung Galaxy Note 10.1" splash screen
2 - instead of above I get a screen showing the last thing i was doing, ie, download mode, but with static across it.
any ideas on how to correct this?
Click to expand...
Click to collapse
Can you answer some questions??
what do you mean by you are in?? .. can you get to android or not yet?? ... what do you mean with getting download mode with static ??
would you try going to recovery and clear cache and dalvik cache to try??

sorry, by I'm in I mean that I can now boot to Android.
when i say download mode with static, image the download screen but fuzzy and punctuated with white nose.
I've done a cache format and a reset to factory but I still get the same issue.
Also, I'm still unable to get an adb connection to the device.
I have noticed that the serial number has now changed to the same as the working device but thats expected as we copied the efs contents from one to the other.
thanks for all your help. you saved my bacon

[Q] Accidentally Wiped /system, Can't Flash ROM

I was going to install a superuser.zip file to root my M4 but when I went to wipe the /cache the /system get wiped as well. I can boot into either CWM or TWRP and have full fastboot/adb, but when I try to boot into Android it just brings me back to the bootloader. When I try to install a stock ROM it just says it's flashing it but hangs at a certain point, I even had it run overnight and it still didn't install. When I try to flash a custom ROM suh as Cyanogenmod it either completes the flashing in about 2 seconds or greets me with an error. RUU and FUU don't seem to work. I'm 100% out of ideas now, and I'm open to anything to try.

legofan623 said:
I was going to install a superuser.zip file to root my M4 but when I went to wipe the /cache the /system get wiped as well. I can boot into either CWM or TWRP and have full fastboot/adb, but when I try to boot into Android it just brings me back to the bootloader. When I try to install a stock ROM it just says it's flashing it but hangs at a certain point, I even had it run overnight and it still didn't install. When I try to flash a custom ROM suh as Cyanogenmod it either completes the flashing in about 2 seconds or greets me with an error. RUU and FUU don't seem to work. I'm 100% out of ideas now, and I'm open to anything to try.
Click to expand...
Click to collapse
Andyt95 said:
Download Magio R4
reboot into recovery, type in cmd
Code:
adb devices
adb shell
mount data
exit
adb push /path/to/magioR4.zip /data/
[I](you should reboot here, in which case you'll
need to type[/I] "mount data" [I]again after adb shell,
but it's not really essential and should work anyway)[/I]
adb shell
mount /data /sdcard [I](creates a virtual sdcard)[/I]
flash your ROM in recovery just like you would normally (select .zip from sdcard) and boot up
run rumrunner, it should work, giving you S-OFF which will let you flash absolutely anything. If it doesn't, let me know and I'll come up with a workaround.
Click to expand...
Click to collapse
should work

Andyt95 said:
should work
Click to expand...
Click to collapse
Well first:
~ # ←[6nmount data
mount data
mount: mounting /dev/block/mmcblk0p37 on /data failed: Device or resource busy
But instead I just used a USB OTG and flash drive so no big deal
And then Magio popped up with its installer and I went through that and then hit "reboot" to be greeted with the bootloader, so I hit "reboot" in the bootloader, but it still brings me back to the bootloader immediately after a black screen, so I thought "Oops, needed to flash the boot.img", so boot.img was then flashed. Now the green HTC logo is sitting there and isn't doing anything, probably frozen.

Code:
mount: mounting /dev/block/mmcblk0p37 on /data failed: Device or resource busy
means /data is already mounted

I actually got it up and running from a nandroid restore, I tried it once before but the restore didnt finish so I thought it wouldnt work. Thanks for helping me out anyway though!

[Completed] [Q] Can't get into recovery; very strange flickering issue

Hey everyone, I have this very strange issue
The other day I made a nandroid backup because I wanted to mess around with some stuff I wasn't sure was going to work. I then restored the backup, and tada, bootloop. I was stuck on the boot animation. Tried a deleting data/dalvik/cache from recovery (CWM 6.0.4.7), installing rom again, but nothing worked.
Now, what I did may or may not have been smart. I wiped everything using "wipe userdata" in the adb shell. Everything gone. Now I want to put on a working rom again, but I can't. Two problems:
1. My CWM recovery is doing this . Not only when I boot into it trough bootloader, but, maybe this is because I don't have a working rom, it also seems to go into it after my bootloop attempts to boot twice, as seen here.
I have no idea what's happening and why and how. It just keeps flashing like this and I can't access the menu. I tried reflashing, flashing the touch version, flashing TWRP which doesn't have default adb access, and flashing it once again but same result. So I can't choose a rom to flash. How do I fix this?
2. I can still push files to /data/media/ and /sdcard/, but after that I have no way to install them. No tutorial I found seemed to work, e.g this one from xda says I have to mount /data/ but when I do that I get
> C:\sdk\platform-tools>adb shell
~ # mount data
mount data
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed:
Invalid argument
And I've also done this one which states the rom should install, but it doesn't. The cd and push are successful, but I can't do anything with it. I also think my /sdcard/ got unmounted at some point, but I was able to push a file to it so not sure here.
Does anyone know how to fix this. I have no idea what to do, pretty hopeless at this point. Thanks so so much if you have any tips
-Josh

Duplicate.
http://forum.xda-developers.com/general/xda-assist/bootloop-nandroid-restore-tried-t3153174

Htc sensation boot went to hell

Hi. This is my first post and I hope I didn't have to post in some other section just for present myself, since I'm doing it now.
Anyway, I tried to flash a new rom since my HTC Sensation (no 4g nor XE) was totally stucked. I even installed the minimum software that I needed, and the result was a phone that could barely make calls.
So I did a backup of all my datas, then proceeded to a factory reset.
After that I followed the procedure on the htcdev website to unlock the bootloader and everything went smooth.
The first problem happened when, following a video explanation of a french guy that didn't say that I needed a wire, I had to improvise with what I could find at a late time in the night, and it was some iron wire insulated with some paper. At first the phone reeboted but not like I needed, and the following tries were totally useless so I used that software called rumrunner that claims to do be able to turn S-OFF without the wire trick.
I don't really know if it worked or not: I have S-OFF but during the process in the cmd there was "WTF: what are you doing" and "process stopped" even if I didn't touch anything.
Anyway, let's assume that I have S-OFF:
I then tried to flash the recovery 4-EXT using a software called like "Sensation_All-In-One_Kit_v3.1". I didn't noticed any significant change, nor the other functions were working properly since everything said "phone not found". So I used cmd and flashed "recovery-clockwork-touch-5.8.0.9-pyramid" and it worked flawlessy.
Then I rooted the phone using the recovery and installing from the sdcard the file "su-2.3.6.3-efgh-signed".
Then I downloaded cm12.1 by ivanich and installed it, but I forgot to do a backup before that and when I turned on the phone, nothing was loading. It was a black screen with the superior bar. The touch was not working, the on/off button the same. So I reopened the recovery, wiped out the data and cache to factory reset, and did again the SU and custom SO install.
Now the phone boots but it's again the factory reset version, not the one that I installed. I see that from all the bloatware still there. Also, its version is wrong. It's android 4.0.3, while there wasn't that version when it was produced.
I need help.
edit: I found out that when I try to install the rom I get only errors saying :
[the first part is missing since I can't scroll up]
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
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: no such device
unmount of /data failed; no such volume
patching system image unconditionally...
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
script succeded: result was [0.200000]
Install from sdcard complete.
FINAL EDIT:
I searched in many places for help. I found the man in a IRC chat. Seems that I had to change the recovery app and install twrp. Then it worked flawlessy.

Ciome said:
Hi. This is my first post and I hope I didn't have to post in some other section just for present myself, since I'm doing it now.
Anyway, I tried to flash a new rom since my HTC Sensation (no 4g nor XE) was totally stucked. I even installed the minimum software that I needed, and the result was a phone that could barely make calls.
So I did a backup of all my datas, then proceeded to a factory reset.
After that I followed the procedure on the htcdev website to unlock the bootloader and everything went smooth.
The first problem happened when, following a video explanation of a french guy that didn't say that I needed a wire, I had to improvise with what I could find at a late time in the night, and it was some iron wire insulated with some paper. At first the phone reeboted but not like I needed, and the following tries were totally useless so I used that software called rumrunner that claims to do be able to turn S-OFF without the wire trick.
I don't really know if it worked or not: I have S-OFF but during the process in the cmd there was "WTF: what are you doing" and "process stopped" even if I didn't touch anything.
Anyway, let's assume that I have S-OFF:
I then tried to flash the recovery 4-EXT using a software called like "Sensation_All-In-One_Kit_v3.1". I didn't noticed any significant change, nor the other functions were working properly since everything said "phone not found". So I used cmd and flashed "recovery-clockwork-touch-5.8.0.9-pyramid" and it worked flawlessy.
Then I rooted the phone using the recovery and installing from the sdcard the file "su-2.3.6.3-efgh-signed".
Then I downloaded cm12.1 by ivanich and installed it, but I forgot to do a backup before that and when I turned on the phone, nothing was loading. It was a black screen with the superior bar. The touch was not working, the on/off button the same. So I reopened the recovery, wiped out the data and cache to factory reset, and did again the SU and custom SO install.
Now the phone boots but it's again the factory reset version, not the one that I installed. I see that from all the bloatware still there. Also, its version is wrong. It's android 4.0.3, while there wasn't that version when it was produced.
I need help.
edit: I found out that when I try to install the rom I get only errors saying :
[the first part is missing since I can't scroll up]
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
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: no such device
unmount of /data failed; no such volume
patching system image unconditionally...
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
script succeded: result was [0.200000]
Install from sdcard complete.
FINAL EDIT:
I searched in many places for help. I found the man in a IRC chat. Seems that I had to change the recovery app and install twrp. Then it worked flawlessy.
Click to expand...
Click to collapse
you just had a very old version of recovery
i assume that guy gave you the proper twrp because there is a false one which messes up with emmc after using wipe option

rzr86 said:
you just had a very old version of recovery
i assume that guy gave you the proper twrp because there is a false one which messes up with emmc after using wipe option
Click to expand...
Click to collapse
No he just told me to get the last version for my phone.

Ciome said:
No he just told me to get the last version for my phone.
Click to expand...
Click to collapse
actually i am saying the same thing