So, I wanted to upgrade my rezound the 8-12 stuff. Log story short, I unlocked with HTCdev again and everything seems to have gone Ok, but obviously it didn't.
My phone will not boot. It just sits and spins on the cyanogenmod bootscreen.
Current specs:
S-OFF
JB HBOOT 2.25
Radios: 421/424r
I've tried re-flashing my rom, and kernel to no avail. Same problem as before.
HELP!
If you are s on did you flash the boot.img file
xkjonathanxk said:
If you are s on did you flash the boot.img file
Click to expand...
Click to collapse
I'm s-off
Wait what exactly where you doing ?
Ok, here's a bit more info.
Just reflashed the kernel again. When I wipe dalvic-cache it says:
E:Can't mount /dev/block/mmcblk0p35
(File exists)
Error mounting /data/dalvic-cache!
Try
luis86dr said:
Try the following in adb:
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p35 /data
Samsung Galaxy S3
Click to expand...
Click to collapse
/sbin/sh: su: not found
/ # mount -o remount,rw -t ext4 /dev/block/mmcblk0p35 /data
mount -o remount,rw -t ext4 /dev/block/mmcblk0p35 /data
mount: mounting /dev/block/mmcblk0p35 on /data failed: Invalid argument
what recovery are you using because the error you are getting is most common in cwm
Amon RA 3.06
Hmm researching and the only thing found was to lock bootloader and flash the ruu and root again
try this thread seemed to have the same problem as you
http://forum.xda-developers.com/showthread.php?t=1907758
Well, I tried the stuff at the end of that post and it booted! BUT, I lost everything. I think I might have a backup to restore so hopefully it's not too bad.
Thank you for the help.
kkozma said:
Well, I tried the stuff at the end of that post and it booted! BUT, I lost everything. I think I might have a backup to restore so hopefully it's not too bad.
Thank you for the help.
Click to expand...
Click to collapse
You're also running a very old version of Amon Ra. You should upgrade to v3.16.
Related
I've searched all over google and these forums and found lots instructions for different phones that don't seem to work for the vibrant.
I've been trying to modify some of the icons and such in the framework-res.apk. I'm trying to boot into recovery, mount the /system partition and push the modified file back.
Can anyone provide me with the adb command to mount the /system partition on the vibrant or a link to a thread that has the information.
Thanks...
you can't do it in stock recovery, you must be in clockworkmod recovery. IF you're in clockworkmod recovery, got the the mounts section and there you can mount /system, /data/, /sdcard and a few others with a graphical interface.
But incase you want it for some future reference:
Code:
su
mount -o rw,remount /dev/block/stl9 /system
and for this to work, su must be granted root permission (which it can't from stock recovery)
geoffcorey said:
you can't do it in stock recovery, you must be in clockworkmod recovery. IF you're in clockworkmod recovery, got the the mounts section and there you can mount /system, /data/, /sdcard and a few others with a graphical interface.
But incase you want it for some future reference:
Code:
su
mount -o rw,remount /dev/block/stl9 /system
and for this to work, su must be granted root permission (which it can't from stock recovery)
Click to expand...
Click to collapse
Thanks for the response. When I go into clockwork recovery I can't connect via adb? When I adb devices it doesn't list anything. When I'm in the stock recovery it lists my device.
Am I missing a step?
Thanks in advance for the help.
Hello,
I just unlocked my rooted prime and flashed the newest CWM via Rom Manager.
Now I can't backup my existing rom. Also I can't install any custom rom.
When I hit backup in CWM, it sais "Can't mount backup path"
When I hit install zip from SD, there is another error "Can't mount /sdcard/
I also tried TWRP Recovery, with no success.
Code:
E:failed to mount /data (Invalid argument)
-- Could not mount: /sdcard.
-- Aborting
Screenshots:
ttp://img37.imageshack.us/img37/561/img20120616114555.jpg
ttp://img801.imageshack.us/img801/2844/img20120616112128.jpg
Just for info: My device is still running stock rom and is encrypted.
Has anyone a solution for this?
Thank you for your help.
With best regards,
B-Paul
Restore is borked in the latest version of CWM. Push 5.8.2.0 and everything will be OK.
Just tried, still the same error message
Brausepaul said:
Code:
E:failed to mount /data (Invalid argument)
-- Could not mount: /sdcard.
-- Aborting
Click to expand...
Click to collapse
You can't mount /sdcard/ (which is a symlink to /data/media/) when device is encrypted, cwm/twrp do not know how to handle this.
edit: Looking at my Nexus, only way to step out of encryption is to use fastboot. It should work like this for the Prime as well.
I have a ZOPO C2 (http://www.zopomobileshop.com/en/18...tk6589t-5-inch-fhdg-screen-android-phone.html) and it's stuck at the boot image.
I know what went wrong: I tried to move some of the memory of my internal sdcard memory(32GB) to my internal memory(2GB) using this apk: http://forum.xda-developers.com/showthread.php?t=2240954
After rebooting it just got stuck at the boot image, and the button combination to get into recovery doesn't work (it never did work so no change there)
Through adb I managed to get into TWRP recovery. I cannot wipe anything (except the external sd-card):
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
E:Unable to mount '/emmc'
E:Unable to mount '/emmc'
E:Unable to mount '/system'
E:Unable to mount '/emmc'
Formatting emmc using mkdosf's...
E:Unable to mount '/cache'
E:Unable to mount '/data'
E:Unable to mount '/emmc'
E:Unable to mount '/emmc'
E:Unable to mount '/system'
E:Unable to mount '/emmc'
Click to expand...
Click to collapse
I tried installing a custom ROM, which doesn't fail, but I do get a screen full of the same error message:
E:A render request has failed.
Click to expand...
Click to collapse
It also gives 1 line of this error message every second while the screen locks due to timeout.
After installing the custom ROM, I try to reboot, but the TWRP warns me "No OS installed, reboot?". After reboot again stuck at boot image.
I tried 2 custom ROM's, both of which worked earlier.
I also cannot use adb shell:
- exec '/system/bin/sh' failed: No such file or directory (2) nRet(-1) -
Click to expand...
Click to collapse
However, I can use the Terminal Command within recovery
Within TWRP recovery I can also use the file manager, where the /system/bin/ folder is empty.
My guess is my filesystem is corrupted. Any idea on how to fix this without adb shell?
Edit: Nevermind, flashed the device using latest stock ROM with manufacturer flasher:
http://www.zopomobileshop.com/content/9-download-zopo-mobile-latest-rom
Fixed
same problem
I have the same problem for the same reason, have tried flashing with the latest stock rom, but does not connect to my phone, how was you able to connect thought adb
thanks
henkienl said:
I have a ZOPO C2 (http://www.zopomobileshop.com/en/18...tk6589t-5-inch-fhdg-screen-android-phone.html) and it's stuck at the boot image.
I know what went wrong: I tried to move some of the memory of my internal sdcard memory(32GB) to my internal memory(2GB) using this apk: http://forum.xda-developers.com/showthread.php?t=2240954
After rebooting it just got stuck at the boot image, and the button combination to get into recovery doesn't work (it never did work so no change there)
Through adb I managed to get into TWRP recovery. I cannot wipe anything (except the external sd-card):
I tried installing a custom ROM, which doesn't fail, but I do get a screen full of the same error message:
It also gives 1 line of this error message every second while the screen locks due to timeout.
After installing the custom ROM, I try to reboot, but the TWRP warns me "No OS installed, reboot?". After reboot again stuck at boot image.
I tried 2 custom ROM's, both of which worked earlier.
I also cannot use adb shell:
However, I can use the Terminal Command within recovery
Within TWRP recovery I can also use the file manager, where the /system/bin/ folder is empty.
My guess is my filesystem is corrupted. Any idea on how to fix this without adb shell?
Edit: Nevermind, flashed the device using latest stock ROM with manufacturer flasher:
http://www.zopomobileshop.com/content/9-download-zopo-mobile-latest-rom
Fixed
Click to expand...
Click to collapse
degogar said:
I have the same problem for the same reason, have tried flashing with the latest stock rom, but does not connect to my phone, how was you able to connect thought adb
thanks
Click to expand...
Click to collapse
With the flasher I used all I had to do was remove the battery, plug in the usb and let the flasher do its work.
Hello, I have a Nabi sitting around and decide to get it out, update it and put it to use. My flashing skills are novice, I do a phone or tablet once in a blue moon and it it usually been with a AIO or relatively trouble free.
I have TWRP 2.3.3.0 and the Kernel is 1.9.3.7 from last year I install custom recovery
I attempted to install Monarch UI Removed/SuperSU & SU Binaries Installed including BusyBox 3.0.13( Fuhu/Nabi/Keenhi Stuff Removed ) - n3wt when that failed I attempted Stock Rom 3.0.13 via TWRP - aicjofs
I did a full Wipe, attempted to install with TWRP and ADB sideload.
The ADB sideload reaches 100% on PC and is marked failed on the Tablet in TWRP sideload UI.
Installing in TWRP I get the following errors in the Terminal
Code:
Updating Partitions details...
E:/Unable to mount '/data'
E:/Unable to mount '/data'
E:/Unable to mount '/system'
E:/Unable to mount '/cache'
E:/Unable to mount '/data'
E:/Unable to mount '/addon'
I also tried installing Stock Version 1.9.37 with similar results.
In the mount menu I can't selec "Using internal storage" or any of the mount options.
Also all wiping options for cash and system fail.
Next I re-installed TWRP 2.3.3.0 through fastboot to make sure everything was clean and it appeared to all take, and I still get the same results trying to flash.
So I am at a loss as what to try next and would appreciate any help.
While posted I've been trying NabiLab here is the error I received on a stock recovery.
*********** Restore Nabi to Factory 1.9.37 from ANDROID ****************
Install recovery to Internal or External SD card?
-If external make sure your card is installed-
1. Internal SD
2. External SD
Choose an option:1
Files are prepared. Press any key to begin restore.
Press any key to continue . . .
rebooting...
When TWRP is done booting press enter
Press any key to continue . . .
Pushing stock recovery to your device
Ignore external SD card error if you have none installed
This files are 1.2GB this will take many minutes. Please wait.
mount: mounting /system on ext4 failed: No such file or directory
mount: mounting /cache on ext4 failed: No such file or directory
mount: mounting /data on ext4 failed: No such file or directory
mount: mounting /addon on ext4 failed: No such file or directory
mkdir: can't create directory '//data/media/TWRP/BACKUPS/0123456789ABCDEF/abcdst
ock123': No such file or directory
1332 KB/s (8388608 bytes in 6.149s)
9 KB/s (48 bytes in 0.005s)
Click to expand...
Click to collapse
jumbojimx said:
Hello, I have a Nabi sitting around and decide to get it out, update it and put it to use. My flashing skills are novice, I do a phone or tablet once in a blue moon and it it usually been with a AIO or relatively trouble free.
I have TWRP 2.3.3.0 and the Kernel is 1.9.3.7 from last year I install custom recovery
I attempted to install Monarch UI Removed/SuperSU & SU Binaries Installed including BusyBox 3.0.13( Fuhu/Nabi/Keenhi Stuff Removed ) - n3wt when that failed I attempted Stock Rom 3.0.13 via TWRP - aicjofs
I did a full Wipe, attempted to install with TWRP and ADB sideload.
The ADB sideload reaches 100% on PC and is marked failed on the Tablet in TWRP sideload UI.
Installing in TWRP I get the following errors in the Terminal
Code:
Updating Partitions details...
E:/Unable to mount '/data'
E:/Unable to mount '/data'
E:/Unable to mount '/system'
E:/Unable to mount '/cache'
E:/Unable to mount '/data'
E:/Unable to mount '/addon'
I also tried installing Stock Version 1.9.37 with similar results.
In the mount menu I can't selec "Using internal storage" or any of the mount options.
Also all wiping options for cash and system fail.
Next I re-installed TWRP 2.3.3.0 through fastboot to make sure everything was clean and it appeared to all take, and I still get the same results trying to flash.
So I am at a loss as what to try next and would appreciate any help.
While posted I've been trying NabiLab here is the error I received on a stock recovery.
Click to expand...
Click to collapse
Wrong TWRP version is my guess. http://forum.xda-developers.com/showpost.php?p=62391871&postcount=2635 There are the 3 versions you need to try.
Thanks, got it fixed.
It was the wrong TWRP. Then I wasn't seeing any recovery files. ADB was giving me an odd generic serial number, I did a back up and then dumped the files in the TWRP created folder and they appeared.
Original Post.
aicjofs said:
Wrong TWRP version is my guess. http://forum.xda-developers.com/showpost.php?p=62391871&postcount=2635 There are the 3 versions you need to try.
Click to expand...
Click to collapse
Thanks for the reply.
I tried all 3 versions of TWRP in your post . TWRPv263 for ICS Nothing (cache,data,system, extsdcard etc) will mount. TWRPv285 for JB&KK Everything but /system will mount.
Using all 3 versions of TWRP I tried to install 3013stock.zip and 3013bootloader. No files from the extracted zip show up in TWRP recovery tab.
So I assume the issue I am aiming at is getting /system to mount in either KK or JB version of TWRP. v285?
Click to expand...
Click to collapse
i have big problem !!, i own galaxy s3 (i9300) and i use android 4.3 , everytime i try to flash custom rom like cyanogenmod or other rooms im lost network and connection of sim , i do backup to efs file and restore it in the custom rom but this does not work ,I notice that /efs unable to mount in twrp recovery mode i tray to mount it using this command mount -w -t ext4 /dev/block/mmcblk0p3 , but this give message sayes mount: mounting /dev/block/mmcblk0p3 on /efs failed: Operation not supported on transport endpoint
PLEASE I NEED HELP !!!
Fail to mount us 9/10 times a borked recovery (twrp). Flash another recovery or flash a stock rom via odin and start over.
Sent from my HTC One M9 using Tapatalk