I've done quite a few searches and ended up here every time:
forum.xda-developers.com/showthread.php?t=502010
forum.xda-developers.com/showthread.php?t=517874
forum.xda-developers.com/showthread.php?t=543617
I'm starting to drive myself crazy here because I successfully did this once. Here's my issue, I've been playing around with Cyanogen Mod and I was doing some tweaking and for whatever reason I got stuck in a reboot loop. Well, since I couldn't get anything else to work, I wiped my SD:Ext using:
Code:
`mke2fs -j /dev/block/mmcblk0p2`
After that, I installed Enomther`s [ROM] TheOfficial Nexus1 - v1.8.1, Release 1.8.1 and everything seemed to be working fine. For some reason, I got in a reboot loop so I did a nand restore and went back to the stock 2.1 Android OS (ERE27). Unfortunately now I can't get anything to work again. Here's what I'm running into, when I open a shell, mke2fs is no longer a command nor does "mount -o rw /dev/block/mmcblk0p2 /system/sd" work as mount gives me a "usage" error. I don't know what all this talk is about /dev/block/mmcblk0p2" is but that doesn't exist. All I have in /dev/block is mmcblk0 and mmcblk0p1. When using the mount command, I do change mmcblk0p2 to an mmcblk* that exists in /dev/block/.
I'm really at a loss here because all I want to do is wipe my SD card like the guides tell me to so I can reflash my rom but I can't figure it out. These mount and mke2fs commands worked the last time I tried to do this but right now I'm stuck
No one can help? I've posted this up in two different forums and not one person can help?
Have you tried deleting all the partitions & recreating them from scratch? Parted seems to be reliable & is nice & simple to use. Try this guide. If your current ROM doesn't include parted, try doing this from Recovery as there's a fair chance it will. I suggest you stick to the instructions & don't improvise commands unless you're very sure you know what you're doing.
Friends,
Having issues with flashing a custom rom to just rooted HTC One X 2.20 (ATT). First Android phone for me, got it a week ago, and first run at any and all of these issues (just switched from iPhone, but still doing all of this using a Macbook Air). Here's the spread:
Unlock went fine, no issues.
Installed TWRP, DID NOT INSTALL SUPERUSER.
Managed to choke and wipe OS (along with caches, sdcard). Fastboot and adb work. I have full access to TWRP, however I cannot mount /sd to computer (Mac simply notes, when mounting, that the device is unreadable).
I managed to push both the rom I was hoping to install (aokp_evita_jb_build-4.zip), and gapps to sdcard with ADB, however neither file would show in TWRP's file manager (I placed them in the root dir of the phone). I attempted to run the ROM via fastboot to no avail. I did push the boot.img as directed.
As I did not install SuperUser when I was supposed to, I attempted to install the superuser.apk with ADB after the fact, with the resulting error stopping me in my tracks: /sbin/sh: pm: not found. The only resolution to this issue I could find did not seem to apply to my situation.
Are the lack of permissions granted by SuperUser the reason the rom and gapp .zip files do not appear in TWRP file manager? Can/should I continue to attempt installing the superuser.apk file? After digging through all of these godawful help requests (mine included), can/should I attempt to lock the bootloader and flash RUU? What am I missing that is painfully obvious to those with real experience in this mess?
emp1re07 said:
Friends,
Having issues with flashing a custom rom to just rooted HTC One X 2.20 (ATT). First Android phone for me, got it a week ago, and first run at any and all of these issues (just switched from iPhone, but still doing all of this using a Macbook Air). Here's the spread:
Unlock went fine, no issues.
Installed TWRP, DID NOT INSTALL SUPERUSER.
Managed to choke and wipe OS (along with caches, sdcard). Fastboot and adb work. I have full access to TWRP, however I cannot mount /sd to computer (Mac simply notes, when mounting, that the device is unreadable).
I managed to push both the rom I was hoping to install (aokp_evita_jb_build-4.zip), and gapps to sdcard with ADB, however neither file would show in TWRP's file manager (I placed them in the root dir of the phone). I attempted to run the ROM via fastboot to no avail. I did push the boot.img as directed.
As I did not install SuperUser when I was supposed to, I attempted to install the superuser.apk with ADB after the fact, with the resulting error stopping me in my tracks: /sbin/sh: pm: not found. The only resolution to this issue I could find did not seem to apply to my situation.
Are the lack of permissions granted by SuperUser the reason the rom and gapp .zip files do not appear in TWRP file manager? Can/should I continue to attempt installing the superuser.apk file? After digging through all of these godawful help requests (mine included), can/should I attempt to lock the bootloader and flash RUU? What am I missing that is painfully obvious to those with real experience in this mess?
Click to expand...
Click to collapse
Check the settings in TWRP. You should have everything mounted as writeable. Root files may not show up otherwise.
iElvis said:
Check the settings in TWRP. You should have everything mounted as writeable. Root files may not show up otherwise.
Click to expand...
Click to collapse
TWRP Settings does not appear to contain an options relating to this: Zip file sig. verification/Force MD5 check/Use rm -rf/ Skip MD5 generation/Enable MD5 verification/Ignore image size errors/Simulate actions for theme testing
Tried to use ADB sideload to load the ROM, didn't work.
I've continued searching through threads to find a situation similar to mine, no luck.
EDIT: Rebooted a couple of time, retried pushing gapps-jb-20120726-signed.zip and the aokp rom mentioned above. They now appear under /sdcard
Tried to install both .zip files, and was met with a FAIL for the following reasons: E: Unable to mount '/sdcard' and E: Unable to mount storege
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!
Hi, first of all sorry for my english.
I'm S-off, rooted, using TWRP touch and android 5.0 (from ivanich).
I went out of memory on my internal storage, so I had a pop-up that says lower your storage (my sd card couldn't be mounted). Then i went in recovery to wipe cache and data for it would free some space, but I got theses issue:
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
script succeeded: result was [0,200000]
updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
I also tried by advanced wipe> wipe Data and I went stuck on this :
"Formatting Data using make_ext4fs function"
If i try to reboot on the rom it's bootloop
I tried a few command in the terminal command that I've found here http://forum.xda-developers.com/showthread.php?t=2683787
mke2fs -T ext4 /dev/block/mmcblk0p8
I get this :
filesystem too small for a journal
writing superblocks and lifesystem accounting information : done
This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
So I have no idea how to fix this I never had this error before and I can't find anything about it, only Odin but correct me if I'm wrong but Odin doesn't work for Sensation ?
Thanks for any help I appreciate
you are facing probably the same issue with others that faced with twrp
those partitions corrupted after using the wipe options
the only thing i can suggest you is to use this solution
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
best wishes
So yeah, i've try so many things, and none of them is fixing my problem.
First i've installed 4ext recovery and i had still the same issue, not able to wipe cache or data or factory reset.
I've tried to install adb but it doesn't recognize my phone, even with SDK tools, i can't tell the program what my phone is.
now i've tried to install the RUU (dl the .exe, found the rom.zip, and put on my phone renamed it "PG58IMG.zip" now when i'm on the fastboot it loads the file and then it get stuck at the userdata part....
If i try to boot the normal way i get the black screen with the red triangle and exclamation mark ....
I'm going to keep looking but it's getting harder than expected
(still sorry for my english)
ni4rkx said:
So yeah, i've try so many things, and none of them is fixing my problem.
First i've installed 4ext recovery and i had still the same issue, not able to wipe cache or data or factory reset.
I've tried to install adb but it doesn't recognize my phone, even with SDK tools, i can't tell the program what my phone is.
now i've tried to install the RUU (dl the .exe, found the rom.zip, and put on my phone renamed it "PG58IMG.zip" now when i'm on the fastboot it loads the file and then it get stuck at the userdata part....
If i try to boot the normal way i get the black screen with the red triangle and exclamation mark ....
I'm going to keep looking but it's getting harder than expected
(still sorry for my english)
Click to expand...
Click to collapse
I can't help with issue but userdata is not mmcblk0p8, it's mmcblk0p23 on our device.
hinxnz said:
I can't help with issue but userdata is not mmcblk0p8, it's mmcblk0p23 on our device.
Click to expand...
Click to collapse
Hmm thanks for this info, I will try to do again all this but on an other computer tomorrow maybe it will work... I hope!
So after hours of trying to repair it, it still doesn't work.
But i've found something that might be intersting.
In recovery 4ext but now I'm twrp so I don't have the exact information again but when I went in storage information, it was written that the internal storage was --mb, and --mb free, so I guess it means that my partition doesn't exist anymore.. Anyway I've found that I'm not the only one with this but I still didn't find any solution to fix it..
ni4rkx said:
Hi, first of all sorry for my english.
I'm S-off, rooted, using TWRP touch and android 5.0 (from ivanich).
I went out of memory on my internal storage, so I had a pop-up that says lower your storage (my sd card couldn't be mounted). Then i went in recovery to wipe cache and data for it would free some space, but I got theses issue:
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
script succeeded: result was [0,200000]
updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
I also tried by advanced wipe> wipe Data and I went stuck on this :
"Formatting Data using make_ext4fs function"
If i try to reboot on the rom it's bootloop
I tried a few command in the terminal command that I've found here http://forum.xda-developers.com/showthread.php?t=2683787
mke2fs -T ext4 /dev/block/mmcblk0p8
I get this :
filesystem too small for a journal
writing superblocks and lifesystem accounting information : done
This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
So I have no idea how to fix this I never had this error before and I can't find anything about it, only Odin but correct me if I'm wrong but Odin doesn't work for Sensation ?
Thanks for any help I appreciate
Click to expand...
Click to collapse
I decided to try TWRP yesterday and Im having a similar issue. However when i flash roms I have no issues at all. However i get stuck at the HTC logo forever when i try and boot. I have manually flashed boot.img so that isnt the issue. I even tried doing some mkfs.ext4 executions and i still have the same issue. Im going back to my E63 to see if i can still repair this. However looks like another device is looking likely.
Can anyone tell me if you can run some error logs for when the device is in the boot stage, and by that i mean when the HTC logo so showing? I dont think ADB will work in that mode.
When you try to mount data from recovery does it fail?
Can you tell me which twrp your using? I mean which r stands at the end of the filename?
little_lerroyy said:
I decided to try TWRP yesterday and Im having a similar issue. However when i flash roms I have no issues at all. However i get stuck at the HTC logo forever when i try and boot. I have manually flashed boot.img so that isnt the issue. I even tried doing some mkfs.ext4 executions and i still have the same issue. Im going back to my E63 to see if i can still repair this. However looks like another device is looking likely.
Can anyone tell me if you can run some error logs for when the device is in the boot stage, and by that i mean when the HTC logo so showing? I dont think ADB will work in that mode.
Click to expand...
Click to collapse
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Sajito said:
When you try to mount data from recovery does it fail?
Can you tell me which twrp your using? I mean which r stands at the end of the filename?
Click to expand...
Click to collapse
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Where did you download that image?
That sounds like you just experienced the brick bug.
Sajito said:
Where did you download that image?
That sounds like you just experienced the brick bug.
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/pyramid from http://teamw.in/project/twrp2/66 the recovery img method.
Well I'm not sure because It booted the rom (cm12 from ivanich) but yeah bootloop on the CM logo
ni4rkx said:
http://techerrata.com/browse/twrp2/pyramid from http://teamw.in/project/twrp2/66 the recovery img method.
Well I'm not sure because It booted the rom (cm12 from ivanich) but yeah bootloop on the CM logo
Click to expand...
Click to collapse
I'm sorry to say, but that's definitely the brick bug. Only the link rzr86 posted might help you using your phone. Ivanich made twrp builds, which use his kernel and device trees, so we're pretty sure his twrp is not affected by that bug (that just as an info for anyone using the twrp from the official site. So if anyone reads this and is using twrp newer than 2.6 from official site, get ivanich's build).
The problem is that your data partition is corrupt, not the system partition. But you need the data partition, to use any rom, which is now not mountable anymore. So your able to flash roms and get until bootanimation, but without data partition working it won't boot.
@little_lerroyy did you use ivanich's twrp or the one from official site too?
Sajito said:
I'm sorry to say, but that's definitely the brick bug. Only the link rzr86 posted might help you using your phone. Ivanich made twrp builds, which use his kernel and device trees, so we're pretty sure his twrp is not affected by that bug (that just as an info for anyone using the twrp from the official site. So if anyone reads this and is using twrp newer than 2.6 from official site, get ivanich's build).
The problem is that your data partition is corrupt, not the system partition. But you need the data partition, to use any rom, which is now not mountable anymore. So your able to flash roms and get until bootanimation, but without data partition working it won't boot.
@little_lerroyy did you use ivanich's twrp or the one from official site too?
Click to expand...
Click to collapse
So you're saying that TWRP didn't do their job good enough and bricked my phone ? =/ that's pretty sad
thanks for the info tho but maybe there is a way to re create the data partition, since I think I'm not the only one who has this issue
ni4rkx said:
So you're saying that TWRP didn't do their job good enough and bricked my phone ? =/ that's pretty sad
thanks for the info tho but maybe there is a way to re create the data partition, since I think I'm not the only one who has this issue
Click to expand...
Click to collapse
The problem is not caused by twrp, but the faulty device/kernel trees which were used for that image. Unfortunately nobody knows who built these images, nor do we know which sources were used.
I had that too, I know that sucks.
Sajito said:
The problem is not caused by twrp, but the faulty device/kernel trees which were used for that image. Unfortunately nobody knows who built these images, nor do we know which sources were used.
I had that too, I know that sucks.
Click to expand...
Click to collapse
Alright then.... I have an old motorola defy yeahhhh :good:
ni4rkx said:
Alright then.... I have an old motorola defy yeahhhh :good:
Click to expand...
Click to collapse
You can still try to mount your sdcard as data partition, as explained in the link posted on page 1, it seems to work for some.
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Connect phone to pc, boot into recovery, open terminal and type 'adb devices', your device should show.
To try mount data enter 'adb shell mount /data'.
To check structure enter 'adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p23'.
Maybe this could help?
Sajito said:
You can still try to mount your sdcard as data partition, as explained in the link posted on page 1, it seems to work for some.
Click to expand...
Click to collapse
Hm I've take a look but it looks complicated :s
hinxnz said:
Connect phone to pc, boot into recovery, open terminal and type 'adb devices', your device should show.
To try mount data enter 'adb shell mount /data'.
To check structure enter 'adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p23'.
Maybe this could help?
Click to expand...
Click to collapse
Well I'll give it a try when I can work on an other computer because I also have an issue with windows 8.1, it doesn't recognize my phone, so I can't use adb to work with the phone. It worked on windows 7 on an other computer but I can't use it for now.. Thanks anyway I'll keep you in touch
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Follow this link, the process is done in ADB
http://android-revolution-hd.blogspot.com.au/2013/10/fix-data-htc-one.html
Just make sure where it says "mmcblk0p37" in step number 10, you put in "mmcblk0p23" which is your data partition, but i doubt you will have much access doing this.
little_lerroyy said:
Follow this link, the process is done in ADB
http://android-revolution-hd.blogspot.com.au/2013/10/fix-data-htc-one.html
Just make sure where it says "mmcblk0p37" in step number 10, you put in "mmcblk0p23" which is your data partition, but i doubt you will have much access doing this.
Click to expand...
Click to collapse
Thanks but as I said, I can't use ADB on my computer. I'll still try when I can use an other one !
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