Hi guys, Im having a little trouble, hoping somebody could tell me what Im missing or should be doing differently. I am currently on 2.2 OTA. i just rooted using RoOoLeR's Guide to ROOT / BACKUP / ROMS for 2.2 OTA (sticky under hacks). I then downloaded Bootstrap. Opened the app and hit "bootstrap recovery", got the pop-up saying "Success". Then i rebooted into recovery and started a nandroid backup. about a minute into it, it failed and gave me the following message.
E: Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)
(Device or resource busy)
Can't mount /sdcard/.android_secure!
I have yet to install rom manager and load any custom roms beacuse i want to make sure i have a good backup before doing anything.
Suggestions? Thank you so much in advance.
--
Garret
It sounds like you have an issue with the SD card. I would backup the data on the card to a PC, format it blank, and the let the X reinitialize it.
Hello!
I'm trying to find out where to see a list of parameters I can use in there.
I'm using the ClockworkMod recovery (even if I think it's just universal that part), but if I write in that cache file "boot-recovery --nandroid" nothing happens when I reboot into recovery, if I set just "--nandroid" it says "E: invalid arguments"...
What I want to achieve is to execute a nandroid backup and then one or more update zip files. Is it possible?
Thanks!
no one has any idea?
Greetings.
I am trying to install Cyanogenmod 7.0.2 on my HTC Tattoo (still has 1.6). This is the first time I've done this.
I am following the Cyanogenmod wiki page that shows you the whole process of rooting+flashing a new rom (since this is my first post I am unable to post outside links in this thread).
In the "Installing Clockworkmod Recovery" section, I get the following error when trying to flash the image:
flash_image: not found
I listed the files in /sdcard and saw that it was completely empty.
Can anyone tell me what I missed?
I copied the Clockworkmod image file to the root directory by connecting my phone to my PC through USB (USB Debugging was on) and copying the file there.
Please let me know how to solve this.
Thank you.
I was able to solve my problem and proceed with the attempt to flash Clockworkmod. Now I'm getting another error though:
error writing recovery: No space left on device
I have plenty of space in the SD Card (~2GB), but I'm assuming the problem is with the phone's internal memory. I don't know what I can delete.
Any thoughts?
Thank you.
Hi
Ok so i see you have that kind of problems...
I done it this way.
Downloaded Rom Manager->Downloaded Superuser
Then in ROM MANAGER i clicked an option "Flash Clockwork Mod Recovery"..
After that my phone had Clockwork and i completed the procedure to Flash CM7...
Hope this will help you..
CROpipe said:
Hi
Ok so i see you have that kind of problems...
I done it this way.
Downloaded Rom Manager->Downloaded Superuser
Then in ROM MANAGER i clicked an option "Flash Clockwork Mod Recovery"..
After that my phone had Clockwork and i completed the procedure to Flash CM7...
Hope this will help you..
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
I tried to do as you said and installed both Rom Manager and Superuser. But now I have other issues...
1. On Superuser, it says there is a newer version of su and to update. I accept and get the following error:
An error occurred and su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your binary.
2. So, I decided to ignore the update of su and just move on to Rom Manager. Here, I get an error like "su was not found in /system/bin". Well, su is in "/data/local/bin", as per the cyanogen wiki to root the phone. After this, any attempt to flash Clockworkmod fails.
3. To try to make it so Rom Manager has everything it needs, I followed the wiki again, but this time I tried to move the su file to /system/bin. I got the following error:
failed on './su' - Cross-device link
Any ideas?
Thanks in advance!
Hmm, i had the same problem when i was trying to Flash CM7...
Your phone is not rooted...
I know its very frustrating but no worries!
1.Download program from this thread ->http://forum.xda-developers.com/showthread.php?t=761507... you'll see the program in attachemnts and dl the first one.
2.Paste it in your's SD card , install it (use ASTRO MANAGER, to find the program)
3.Open the program and root the phone with 1 click
4. Then Superuser will ask you to allow it and click yes, and go to ROM MANAGER.
5.You will have to allow the Superuser here too.. Do it.
6.Flash Clockwork Mod recovery, and reboot into recoverymod.
7.Flash your Rom , flash Gapps(Google applications)
8.Enjoy
Thank you CROpipe!
Your instructions worked! I now have CM7 installed on my HTC Tattoo!
Here are the issues I found though:
1. When I was trying to download the ROM using ROM Manager, the list of ROMs was empty. Maybe it's because I was not using the Premium version...? I ended up downloading the ROM from the forum, copying it to the SD card and installing it that way.
2. I tried also to install GApps through Rom Manager. I was afterwards able to set up my google account, but I still had to manually download GMail, Google Maps, ... I'm not sure if this is actually how it's supposed to go... :-/
Anyway, thanks again for the help.
Yap that is quite allright Congrats on your new ROM ))
I have tried searching forums here and google and am just running in circles with same solutions to every problem except mine, the few times I HAVE seen a problem similar to mine, it has been added to an existing fix and no answer posted.
I have an old NC (stock 1.0.1) and quite a while ago i put a new honeycomb rom on it that worked great for a few days, then black screen. following various guides here I have seen the "need to update CWM" and all the like, but here is what I have and the problem:
I have CWM 3.2.0.1, I have tried a variety of restore to stock and custom roms, but it doesn't seem to matter what i add to the sdcard after writing the CWM image because no matter what I do (tried TWRP and got same results) I always get the following errors:
Turn on while plugged in with sdcard in --
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
When I try to follow directions found in one thread to format data and system --
Formatting /data...
Error formatting /data!
Formatting /system...
Error formatting /system!
When I try to mount sdcard --
Error mounting /sdcard!
When I try to mount USB --
E:Unable to write to ums lunfile (No such file or directory)
I am able to see the device with cmd adb devices...it gives me a bunch of 0's instead of the actual s/n and says "recovery" at the end of that line.
Have i managed to completely brick a NC or is there a way to fix this? I have learned quite a bit since I decided to try and fix the black screen, but nothing I have found has given me a solution to this.
I appreciate you guys being here and thanks in advance for any help you may have!
**UPDATE** 06/18/2012
by following this ( http://forum.xda-developers.com/showthread.php?t=919353 ) guide, i am able to get some result with sudo:
Code:
[email protected]:~$ sudo android-sdk-linux/platform-tools/adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
0000000000000000 recovery
Then I try entering the quoted commands and even attempt to edit them, but the result sucks:
Code:
[email protected]:~$ dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd: opening `/sdcard/boot.img': No such file or directory
[email protected]:~$ sudo android-sdk-linux/platform-tools/adb shell
~ # dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd: can't open '/sdcard/boot.img': No such file or directory
~ # dd if=/boot.img of=/dev/block/mmcblk0p1
dd: can't open '/boot.img': No such file or directory
~ # dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
dd: can't open '/sdcard/system.img': No such file or directory
the reason for this is that I can't mount the sdcard. if i could mount the sdcard, then this would be an easy fix and i never would have posted in the first place. using CWM 3.2.0.1 in place of nookie froyo since EVERY link for nookie froyo i have found has been a dead link or the instructions require mounting the sdcard which is the problem i am having. Also, CWM 3.2.0.1 and TWRP 3.2.0.1 or older are the ONLY things that actually allows the NC to turn on.
XSmoky said:
I have tried searching forums here and google and am just running in circles with same solutions to every problem except mine, the few times I HAVE seen a problem similar to mine, it has been added to an existing fix and no answer posted.
I have an old NC (stock 1.0.1) and quite a while ago i put a new honeycomb rom on it that worked great for a few days, then black screen. following various guides here I have seen the "need to update CWM" and all the like, but here is what I have and the problem:
I have CWM 3.2.0.1, I have tried a variety of restore to stock and custom roms, but it doesn't seem to matter what i add to the sdcard after writing the CWM image because no matter what I do (tried TWRP and got same results) I always get the following errors:
Turn on while plugged in with sdcard in --
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
When I try to follow directions found in one thread to format data and system --
Formatting /data...
Error formatting /data!
Formatting /system...
Error formatting /system!
When I try to mount sdcard --
Error mounting /sdcard!
When I try to mount USB --
E:Unable to write to ums lunfile (No such file or directory)
I am able to see the device with cmd adb devices...it gives me a bunch of 0's instead of the actual s/n and says "recovery" at the end of that line.
Have i managed to completely brick a NC or is there a way to fix this? I have learned quite a bit since I decided to try and fix the black screen, but nothing I have found has given me a solution to this.
I appreciate you guys being here and thanks in advance for any help you may have!
Click to expand...
Click to collapse
Look in my tips thread linked in my signature. There is an updated CWM SD listed there. Try using that. Read items A8 and A10.
Edit: I suspect your internal partitions are somehow corrupted. Search the threads for references to restoring stock partitions.
leapinlar said:
Look in my tips thread linked in my signature. There is an updated CWM SD listed there. Try using that. Read items A8 and A10.
Edit: I suspect your internal partitions are somehow corrupted. Search the threads for references to restoring stock partitions.
Click to expand...
Click to collapse
Ok, first of all, thanks for the fast reply. Second, with CWM 3.2.0.1, I can see the CWM menus and navigate them, however, with the 5.5.0.4 I am left with the black screen. I have so far attempted including restore zips and nothing but the 5.5.0.4 with no success.
I believe that somehow, with all my attempts to fix, the internal may be completely wiped, but I still find it strange that from a NC I can only use the 3.2.0.1 or older CWM or TWRP to get anything besides a black screen.
XSmoky said:
Ok, first of all, thanks for the fast reply. Second, with CWM 3.2.0.1, I can see the CWM menus and navigate them, however, with the 5.5.0.4 I am left with the black screen. I have so far attempted including restore zips and nothing but the 5.5.0.4 with no success.
I believe that somehow, with all my attempts to fix, the internal may be completely wiped, but I still find it strange that from a NC I can only use the 3.2.0.1 or older CWM or TWRP to get anything besides a black screen.
Click to expand...
Click to collapse
I suspect the 5.5.0.4 did not get burned properly and it is not trying to boot from it. It just is still trying to boot emmc which is corrupt. But I'm not sure that it would have done you any good anyway. Like I said in my edit above, I think you need to somehow rebuild your partitions. And that means more than just trying to flash a stock ROM. You have to find a thread that tells you how to use adb to rebuild the partitions.
leapinlar said:
I suspect the 5.5.0.4 did not get burned properly and it is not trying to boot from it. It just is still trying to boot emmc which is corrupt. But I'm not sure that it would have done you any good anyway. Like I said in my edit above, I think you need to somehow rebuild your partitions. And that means more than just trying to flash a stock ROM. You have to find a thread that tells you how to use adb to rebuild the partitions.
Click to expand...
Click to collapse
I used win32diskimager and received no error messages, so i guess it was the long shot.
I have been digging through all kinds of recover partitions threads but have thus far been plagued by dead links. My searches for adb partitioning keeps showing me recovery zips that I have already tried multiple times. Atm I am working on IOMonster's method, but have my doubts.
I will post results and if I manage to find an ADB guide, I will link it or repost it with citations and keywords to make it easier to find
XSmoky said:
I used win32diskimager and received no error messages, so i guess it was the long shot.
I have been digging through all kinds of recover partitions threads but have thus far been plagued by dead links. My searches for adb partitioning keeps showing me recovery zips that I have already tried multiple times. Atm I am working on IOMonster's method, but have my doubts.
I will post results and if I manage to find an ADB guide, I will link it or repost it with citations and keywords to make it easier to find
Click to expand...
Click to collapse
No error messages and being able to read in your PC does not necessarily mean it will boot from it.
But like I said, I'm not sure it would have helped you anyway. Did you look at this thread?
http://forum.xda-developers.com/showthread.php?p=25433167
Your problem is that your partitions have gotten corrupted.... you will need to dd some img's back to the nook... I have all of them available... but for /dev/block/mmcblk0p2 and 0p3 you will need to do some editing... since they are device specific.
If you're lucky... /dev/block/mmcblk0p3 is still "normal" and the device can recover 0p2 from the rombackup.zip on there... if not... editing is in your future.
Anyway... if you need the img files... I can make them available... have helped a few out with this problem.
Thanks guys, I'm gonna dual boot linux and get to work on the harder to do things now, but with my kids running around it'll take me some time to do.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
lufc said:
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Click to expand...
Click to collapse
Thought i was in the right place given other similar issues posted in same area, thanks for putting me in the right place.
****Moderator please delete this extra post****
Hi,
i'm pretty new to this and i have kinda big problem. I had MIUI 7 rom installed on my S4 I9505, but yesterday after the update phone wont boot. I downloaded new .zip file, put it on SD card, boot into recovery, wipe everything and tried to install new rom. With no succes. I tried 3 differrent roms, i even tried with diffirent recovery, still nothing.
This is what it says:
Installing: /storage/sdcar1/cm-12.1-20151106-NIGHTLY-jfltexx.zip
Finding update package
Opening update package
Installing update
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid argument
unmount of /system failed: no such volume
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by_name/userdata
Patching system image unconditionally...
And that's it. Previosly i was getting errors, status 0 and status 7 if i remmember correctly, but now not even that
Now what to do? Please be noob friendly At this point i don't even care any more what rom to install, stock or custom, but i think i would prefer stock.
Thanks for your help!
Edit: I found this guide, will it do it? forums.androidcentral.com/ambassador-guides-tips-how-s/499009-guide-samsung-how-flash-stock-rom-via-odin-new-interface.html
It worked. Admin, you can close/delete this thread.