Okay, I'm getting saddened by my continuous fails in ROM porting... I had it down before, but now it seems that nothing is going right.. after wiping /system, and using the wipe data and cache option from the main menu in Clockwork, and flashed to test. here's what happened in recovery.
http://pastebin.com/0gyXJACG
it looka all sucessful and cool, until this happens (when looked at via logcat in adb )
exec '/system/bin/sh' failed: No such file or directory (2)
Yet, I check there and the file is present, and busybox is in so why could it be happening?
Related
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
"Turning wifi on..." is all my Wi-Fi settings says after flashing CM10.2. I probably did something wrong. Initially I flashed CM with twrp 2.4, which didn't boot. So I updated to the current twrp 2.6, wiped caches & system, and reflashed CM and rebooted. It seems fine aside from no wireless, so I've attached logcat here in hopes someone can point out my mistake. Apologies and appreciation in advance.
binaries:
cm-10.2-20131007-NIGHTLY-tf700t.zip
gapps-jb-20130813-signed.zip
briankb said:
"Turning wifi on..." is all my Wi-Fi settings says after flashing CM10.2. I probably did something wrong. Initially I flashed CM with twrp 2.4, which didn't boot. So I updated to the current twrp 2.6, wiped caches & system, and reflashed CM and rebooted. It seems fine aside from no wireless, so I've attached logcat here in hopes someone can point out my mistake. Apologies and appreciation in advance.
binaries:
cm-10.2-20131007-NIGHTLY-tf700t.zip
gapps-jb-20130813-signed.zip
Click to expand...
Click to collapse
Have you updated to the bootloader required for CM 10.2?
sbdags said:
Have you updated to the bootloader required for CM 10.2?
Click to expand...
Click to collapse
No I didn't, thanks for pointing me in the right direction. I was at 10.4.4.20.
Update: same problem after wiping system/caches and reinstalling. My only guess at this point is twrp 2.5, going to try again with cwmod
Well I didn't get far with that. After installing ClockworkMod 6.0.3.9 on my tf700t and it shows an error 'E: Can't mount /sdcard' when selecting 'choose zip from /sdcard'
show log produces several messages including:
e: Can't mount /sdcard
I: Skipping execution of extendedcommand, file not found..
I: using /data/media for /sdcard
mount: mounting /dev/block/mmcblk0p8 (file exists)
E: Can't mount /sdcard
[solved]
I solved the issue by formatting /data.
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!
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
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