This has been mentioned elsewhere, even by me but I think it has fallen through the cracks. It may be an unrelated problem but when trying to use CWM to do a backup it fails saying that /system cannot be mounted.
The issue it may be related to is that CWM on boot installed via either method fails to stick past the initial reboot. It looks to me that it is restoring an image on start up each time undoing any changes. It must not be changing everything because the root sticks. I have made sure init.d support has been installed. The phone is an AT&T branded MB865, has been rooted and is running stock 2.3.6 firmware.
Any pointers will be appreciated and I come from an embedded Linux background so I'm willing to help out, but why re-invent the wheel if this has already been solved.
cdlees said:
This has been mentioned elsewhere, even by me but I think it has fallen through the cracks. It may be an unrelated problem but when trying to use CWM to do a backup it fails saying that /system cannot be mounted.
The issue it may be related to is that CWM on boot installed via either method fails to stick past the initial reboot. It looks to me that it is restoring an image on start up each time undoing any changes. It must not be changing everything because the root sticks. I have made sure init.d support has been installed. The phone is an AT&T branded MB865, has been rooted and is running stock 2.3.6 firmware.
Any pointers will be appreciated and I come from an embedded Linux background so I'm willing to help out, but why re-invent the wheel if this has already been solved.
Click to expand...
Click to collapse
Update your busybox .
I had thought of that, running BusyBox 1.20, 1.20.1 fails to install. As 1.20 is fairly recent I doubt this is the problem. The initial install of CWM via Power Boost works, so busybox is installed correctly. An old version of busy box wouldn't explain the not being able to mount /system as as far as I know it isn't used by CWM for this purpose, but I could be wrong. But it could explain the CWM not sticking problem.
Further investigation shows that the system partition does not change between doing a PowerBoost CWM install and after a reboot meaning that there is nothing screwy going on like the boot sequence over writing files in system so that CWM isn't persistent. Can anyone enlighten me on the boot sequence so I can take a look to see if anything is getting over written?
This of course gets me no closer on why CWM can't mount system but it is just one of two problems.
cdlees said:
Further investigation shows that the system partition does not change between doing a PowerBoost CWM install and after a reboot meaning that there is nothing screwy going on like the boot sequence over writing files in system so that CWM isn't persistent. Can anyone enlighten me on the boot sequence so I can take a look to see if anything is getting over written?
This of course gets me no closer on why CWM can't mount system but it is just one of two problems.
Click to expand...
Click to collapse
Have you tried "fix permissions" in cwm?.then reboot and see if it still gives you that error when you go back into cwm
Sent from my MB865 using xda premium
I'm pretty sure I had already tried all that, but just to be sure I did it all again, here is what happened
PowerBoost CWM install
Reboot into CWM
CWM Fix permissions
CWM recovery restart
CWM backup
Failed due to not being able to mount /system
Power cycled, didn't boot into CWM
Since permissions may have changed once CWM Fix permissions had been run
PowerBoost CWM install
Reboot
Enters CWM
Reboot
Didn't boot into CWM
Surely I'm not the only one seeing this problem?
cdlees said:
I'm pretty sure I had already tried all that, but just to be sure I did it all again, here is what happened
PowerBoost CWM install
Reboot into CWM
CWM Fix permissions
CWM recovery restart
CWM backup
Failed due to not being able to mount /system
Power cycled, didn't boot into CWM
Since permissions may have changed once CWM Fix permissions had been run
PowerBoost CWM install
Reboot
Enters CWM
Reboot
Didn't boot into CWM
Surely I'm not the only one seeing this problem?
Click to expand...
Click to collapse
Well once u reboot your phone it goes into cwm. When u reboot from cwm its suppose to go into rom not cwm again.
Sent from my MB865 using xda premium
Have u tried manually mounting system in cwm and see what happens?
Also what version of busybox do u have installed? . Should be 19.4. Nothing higher.
Sent from my MB865 using xda premium
rdavisct said:
Well once u reboot your phone it goes into cwm. When u reboot from cwm its suppose to go into rom not cwm again.
Click to expand...
Click to collapse
I realise this but I was under the impression that if the phone is power cycled or reboot from Android then it will go into CWM on restart.
Still doesn't explain the inability to mount /system
rdavisct said:
Have u tried manually mounting system in cwm and see what happens?
Also what version of busybox do u have installed? . Should be 19.4. Nothing higher.
Click to expand...
Click to collapse
I'm running BusyBox 1.19.4. I just tried to manually mount /system from CWM, same problem. Just to make sure that mounting works I mounted a few other things that were not already mounted.
cdlees said:
I'm running BusyBox 1.19.4. I just tried to manually mount /system from CWM, same problem. Just to make sure that mounting works I mounted a few other things that were not already mounted.
Click to expand...
Click to collapse
Id say rsd flash 2.3.5 . Root. Install atrix bootstrapper. And see if problem persists.
Sent from my MB865 using xda premium
Ok, reflashed back to 2.3.5, rooted, Bootstraped, tried to mount /system from CWM, no luck, same error. Tried to install CWM on boot using the zip from CWM, didn't seem to work. Tried the fix permissions script from CWM, still doesn't work.
There is something up with this phone, is it possible that Motorola has decided to be extra evil.
I till haven't gotten very far with this but I have some more information on what may be the issue. I can get it to update the system partition by flashing a zip. I decided to give it a go with SCV6 as I was sure I'd be able to recover if it failed. It flashed just fine but on reboot it dropped out to the fastboot screen. This is where I decided to get creative, I mounted the system.img file from from the stock fimware, deleted its contents and replaced it with what is in the SCV6 zip system directory, after all this is what CWM will be doing as far as I could tell. I then flashed this file using moto-fastboot. It failed on boot dropping out at fastboot again.
Running out of time for the day I decide to just restore it back to stock, I have a Linux script to automate the process, on completion, same failure. What had happened is I had mounted the system.img file to look inside and then unmounted it, and this may have changed a signature or checksum in the filesystem so it failed to boot. Re-extracting the system.img file and flashing again worked fine.
Are there different versions of the bootloader that do different things? Mine just being a total pain and not allowing much at all.
Just realised the install script puts in a whole pile of symlinks, not having them would cause a boot failure on creating the image the way I did. It will be possible to create an image with said symlinks.
This though fails to explain while mounting and then unmounting the system.img makes it fail.
I may just be talking to myself here but I have some relevant information relating to the original problem of not being able to mount /system which is why flashing doesn't work as well as the flashing scripts don't actually check to see if the system partition is mounted, they just assume it is.
In CWM if you try to mount /system then look at the log it says
mount: mounting /dev/block/mmcblk1p20 on /system failed: Invalid argument
Now the question is, what is the mount line it is trying to execute and which argument is invalid? Can someone with a working phone go into CWM, unmount /system if its mounted by default and then mount it, look at the log and tell me what it says regarding the mounting of system.
Here is the really interesting part, once the phone has booted and checking what is actually mounted on /system its /dev/block/mmcblk1p21, so CWM is trying to mount the wrong partition
I worked out the problem, I was using the Razr bootstrap which obviously mounts a different partition as system, I had followed some instructions that I read somewhere that the Razr version worked and gave a link to said package. Once I swapped to the atrix 2 version it all works, I'll attempt to install SCV6 tomorrow night when I have some time.
can't mount /system!
[/COLOR]
cdlees said:
I till haven't gotten very far with this but I have some more information on what may be the issue. I can get it to update the system partition by flashing a zip. I decided to give it a go with SCV6 as I was sure I'd be able to recover if it failed. It flashed just fine but on reboot it dropped out to the fastboot screen. This is where I decided to get creative, I mounted the system.img file from from the stock fimware, deleted its contents and replaced it with what is in the SCV6 zip system directory, after all this is what CWM will be doing as far as I could tell. I then flashed this file using moto-fastboot. It failed on boot dropping out at fastboot again.
Running out of time for the day I decide to just restore it back to stock, I have a Linux script to automate the process, on completion, same failure. What had happened is I had mounted the system.img file to look inside and then unmounted it, and this may have changed a signature or checksum in the filesystem so it failed to boot. Re-extracting the system.img file and flashing again worked fine.
Are there different versions of the bootloader that do different things? Mine just being a total pain and not allowing much at all.
Click to expand...
Click to collapse
Can you please post the link/s, i have the same problem as you
Related
im not sure what im missing- i have smooth maximus x, rom manager, and it has the recovery or whatev- but when i boot into recovery it boots the stock one- wtf! the menu for rom manager is not flashing the img. it says it is. just erased everything for nothing!problem?
If its going to the stock recovery, its working fine! when you are on stock recovery menu, choose install packages (or whatever it is) and that will get you into clockwork recovery.
But its not loading to clockworks revovery. It just goes to standard start up when that option is selected.
correction
Sorry correction- I try that, and it says "signature verififaction failed- installation aborted." Why?
cpkfolief2 said:
im not sure what im missing- i have smooth maximus x, rom manager, and it has the recovery or whatev- but when i boot into recovery it boots the stock one- wtf! the menu for rom manager is not flashing the img. it says it is. just erased everything for nothing!problem?
Click to expand...
Click to collapse
why are you using ROM manager to flash the recovery if your on SMX ? SMX has bali 2.2 in it wich has CWM built into the kernel so your recovery should be the RED voodoo CWM recovery by default. and if stock blue recovery is coming up for some reason yu should be able to reinstall packages cause SMX has the modded stock recovery already
No no no, I'm not on smx- I'm trying to install the darn thing. I'm still on the stock rom. When I boot into recovery there are 4 options-
Reboot now
Wipe data
Wipe cache
Install packages
When selecting install packages, it fails via signature verification. There are no cwm recovery options available, either.
ooh .. your problem is you have to be rooted which im sure you already are ..
then go to the CWM thread in the DEV section and apply the modded recovery to system/bin . this will make the recovery ignore the signature check so you can flash CWM then SMX
use root explorer or adb push this file
http://dl.dropbox.com/u/2993191/recovery
to /system/bin
then put this file on the root of ur sd
http://dl.dropbox.com/u/2993191/update.zip
and put maximus x rom on ur sd
reboot recovery
reinstall packages
now ur in cwm
- Wipe Data/Factory Reset
- Wipe Cache Partition
Go to mounts and storage
UNMOUNT CACHE
MOUNT DATA
MOUNT SDCARD
UNMOUNT SYSTEM
install zip from sd
choose zip from sd
look for maximus x rom install and u should be good
after you flash, go back to mounts and storage (before rebooting) and make sure your mounts look like this
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
this is as easy as i can put it
Thank you very muych for your persistence to help! I am a noob and cannot find the ty button. I'm a newb, I know.HOWEVER....…I am not a newb to this in general, and I have tried that already. I read that forum . Duh!this is what happens when trying to move the file to sys.bin:
Root explorer says:
Paste operation failed-
Does not say why. I found a solution! Another forum says to downgrade to stock recovery e2, then cwm will work. But I have to get odin and crap. So if there is something I'm STILL missing, and can't move the file there for that reason, don't hesitate to enlighten me.
you need to move the modded recovery to /system/bin/recovery, anything that tells you to downgrade is not correct, as we do not have anything to 'downgrade' to. The modded recovery from Krylon does the same thing. you should be following this:
1. download the recovery.zip from krylon
2. extract the .zip and copy the recovery file to your sdcard
3. use root explorer to copy the recovery from the sdcard to /system/bin/recovery
if it fails, make sure that /system is mounted as read write, rather than read only, there should be a button in root recovery to mount read/write.
Thank you sir! I was comitting a syntax error... maybe by attempting to copy the file from the wrong directory. No, the downgrade works... I was reffering to e2 recovery for samsung rather than e3 which requires signature ver. But that takes waaaaaay longer. So thank you. I was trying to copy the whole zip, rather than the actual file because I thought I had extracted it(stupid). But yeah. Ty! Will see if cwm works now.
Glad to hear that it worked for you, let me know how cwm works out for you, as well as whatever parts come after that for you. Don't forget the Thanks button if someone helps you
The files are in their proper places, all is right.
But when I boot into recovery, I am startled with fright!
For its still normal, its still stock-
So help me ill throw this phone like a rock!
Haha. But seriously. Still same issue.
FAILS TO INSTALL ANYTHING
"Signature verification failed- installation aborted."
It seems I will have to do it the hard way by installing e2. This was this issue for the galaxy s.
Why does no one else with a sidekick have to do this!!!!? Why is it not giving y'all signature verification errors! Why is there no video yet?
Sig verification issues relate to the recovery. it should still look like stock, as the original CWM is a fake flash. Make sure you have the cwm update.zip from Krylon's thread in your sdcard.
It is!!!!!! I think I'm going to cry.
Recovery is saved (overwrite) as instructed.
Update is on sd card as instructed.
Can't be corrupted, deleted files and tried again.
Boot into recovery and stock shows (as it should.)
Re-install from package (only option other than data wipe and reboot)
Whole signature failure
Signature verification failure
Installation aborted. :'(
i'll make you a script and a zip of everything to do this for you later, but that won't be until a bit later, still have to drive my girl home. in the meantime, can you try redownloading the cwm from ayo's original post? also, have you tried the rom manager version of cwm?
Roger that.
And it would be greatly appreciated. If it is, however, just another list of the instructions as mentione previously in this thread, or in the original rom post, forget it. But if there's something new then sure. Heck, a video would be great. I'm sure I wouldn't be the only one watching it either. And I will redownload all of it again(non-existant jesus christ) and try again in the meantime. Thank you again for your effort and supporth surely it must be that I am the only on with this issue. So I am unique on xda! Silly video...
i could even go so far as to skype someone to SHOW them ive got it right or what i have done, in which case i would hope for an "ah ha!now that thurz ya problem right thur neow."
Ok, I have a script for you, it's semi-tested? I already have root in my adb, so I can't test it as well, but it should work. let me know what happens. just unzip this, and run the run.bat.
this will reboot you into recovery after it's done, so make sure you're not doing anything on your phone when you run it.
https://sites.google.com/a/stephenduvick.com/www/files/sk4gtestoneclickroot.zip?attredirects=0&d=1
Credit to Noobnl for the original script, and krylon for the fake flash.
So how exactly do I run the run.bat? Its not an exe or script file... is there a command list I need to put in? (Gawd, the last custom rom I installed(cliq xt) was so much easier, before there even was a clockwork mod. It was easier, and that was when it was the hard way!) And my phone is already rooted, sure that doesn't matter though.
I've been running CM7 for a month or so and I started having some stability problems. So I decided to try DarkyRom.
I did everything like normal (used heimdall).
Upon boot it had an error.
Failed to mount /efs while applying multi-csc.
I'm dead in the water. I tried to flash back to stock. I get an error and thrown into samsung recovery. I can reboot from that and I boot to the gui with no radio. Phone info says "Unknown" Hardware and Baseband Version.
No. I did not backup any EFS (news to me). I do have access to the same model phone, my son has one he just uses as a fancy MP3 player (no phone/data plan).
Is there anything I can do? I did use the ADB Shell and ran "mount" to see if the EFS was mounted. It was a negative...
-MT
Could this have something to do with the file system?
I don't have CWM working. I'm going to work on that. Right now I juast have Samsung Rec. Utils. The error that is in there is:
E:Can't mount /dev/block/mmcblk0p1 (Invalid argument)
mainethoughts said:
Could this have something to do with the file system?
I don't have CWM working. I'm going to work on that. Right now I juast have Samsung Rec. Utils. The error that is in there is:
E:Can't mount /dev/block/mmcblk0p1 (Invalid argument)
Click to expand...
Click to collapse
First off,are you even on the right forum? Darky rom isn't built for this phone so it's not going to work.
Sent from my SCH-I500 using XDA App
Ugh...an unfortunate response. Yes...I'm on the right forum.
I did make a CWM backup from a couple weeks ago. Not sure if that helps.
mainethoughts said:
Ugh...an unfortunate response. Yes...I'm on the right forum.
Click to expand...
Click to collapse
Them why are you flashing roms from other forums/phones? Use odin and check repartition.
Sent from my SCH-I500 using XDA App
*hangs head* Admonishment accepted. I really don't know what I was thinking.
Here is my progress. I tried using Odin to just Re-partition. No go.
<ID:0/003> Can't open the specified file. (Line: 1455)
So then I downloaded stock EC10 (That was factory on my phone). I flashed that via Odin with "Success".
The same error as initially posted was on the phone. I rebooted from the stock recovery console and I was able to boot. 3g works. The hardware and baseband are now accurate. I'm getting a lot of force closes however. The twlauncher is constantly crashing.
So now the phone is semi-functional but there are still errors. (I was getting more forces than normal in CM7 that caused me to dive into this process in the first place).
I could be way off base but I'm thinking that possibly there is corruption (or wrong file system?) problems with the internal SD (I did format the External SD at the start of this).
I appreciate your help. Any suggestions from here?
-MT
Additional Note: Settings are not saved between reboots.
-Rooted
-Installed ROM Manager
-Installed CWM 3
-Reboot into Recovery Mode
No go. Same /dev/block/mmcblk0p1 error (installation aborted)
The 3e recovery also says:
"your storage not prepared yet, please use UI menu for format and reboot actions."
I tried both wipes. Errors.
mainethoughts said:
-Rooted
-Installed ROM Manager
-Installed CWM 3
-Reboot into Recovery Mode
No go. Same /dev/block/mmcblk0p1 error (installation aborted)
The 3e recovery also says:
"your storage not prepared yet, please use UI menu for format and reboot actions."
I tried both wipes. Errors.
Click to expand...
Click to collapse
Use the full odin restore package and make sure you use pit and pda files. Repartition must be checked. Wiping data might be a good idea as well.
Sent from my SCH-I500 using XDA App
I would odin the full mesmerize package EE19. http://forum.xda-developers.com/showthread.php?t=881064
That is what I have already done I believe. Followed instructions from:
http://forum.xda-developers.com/showthread.php?t=881064
-MT
If you've done that, then i'm at a loss. That usually is my solve-all solution... Sorry man.
Thank you much. Is it possible that I could have a faulty internal SD? I had suddenly started getting a lot of force closes in CM7. I guess I'm just wondering if I'm fighting two separate issues here. (My bonehead move vs. a real problem)
-MT
I think I'm FIXED!
I was finally (I don't know how) able to get Odin to Flash CWM 4 (The Blue one needed to install CM7).
I got ZERO errors in CWM. So I took the opportunity to clear caches, format data...I got destructive.
I then installed the CM7 Rom. -SUCCESS
Installed GAPPS - SUCCESS
I hope everything is OK at this point. I know CM7 is booting in about 20 seconds opposed to 5 minutes like it was before I decided to try to morph my phone into an I9000.
I actually saw the black screen with the little phone to PC icons at one point tonight. I think I came real close....
Thanks for your help!
PS: CONFIRMED mmcblk0p1 is mounted! (EFS, etc) PHEW!
I had this happen to me right after a Odin even did the rfs formatter tool exact same problems not saving settings upon reboot and it saying something along the lines of process.android.blah blah blah and double vibrate when booting before the fc anyhow I just reflashed miui to get cwm4 wiped everything reflashed cm7 no probs since
Sent from my SCH-I500 using XDA App
Hi,
I checked through many threads to see if anyone had a similar problem but couldn't find anything unfortunately.
Background :
I was running a Lite'ning ROM on my Samsung Galaxy S2. You're probably familiar with this ROM, but for those who aren't it gets flashed with ODIN and comes rooted and pre-installed with CWM.
I forget which version of Lite'ning ROM it was, but I am fairly certain it was pre-1.5 as the bundled CWM was definitely version 3.x.x.x (later versions I found had 4.x.x.x and 5.x.x.x).
I wanted to try a version of GalnetMIUI for something a bit different and hadn't changed ROMs in quite some time, so I booted into CWM 3.x.x.x (maybe 3.0.0.2?) and did a backup to the internal SD. This came in at around 1.4 GB and comprised of 4 files :
cache.img
data.img
nandroid.md5
system.img
I copied these to my PC too, just in case they somehow got erased from my phone.
Once I'd done this, I then copied the new ROM .zip file (latest version of GalnetMIUI) to the root of the internal SD, booted the phone into CWM, wiped user data and Dalvik cache, then proceeded to install it.
The problem :
I can't get my apps or data back. I was under the false impression that my Google account was automatically backing this up for me, and would restore everything once logged in as it had in the past (factory resets etc.). So once this didn't happen, I tried using CWM to revert back to how things were before installing the new ROM but although the restore appears to work I end up with issues.
I've tried a number of different ROMs and they either get stuck in 'boot loops' or a black screen after running through the restore procedure. I've tried restoring just data via the 'Advanced' option but this doesn't help.
I was under the impression that I'd be able to fully restore the ROM backup if I needed to, and have the phone running exactly how it was prior to messing around. It would seem this is not the case.
In desperation I tried flashing every Lite'ning ROM from version 1.0 to 4.2, restoring my backup each time but as mentioned I always get boot issues.
Have I lost my data? I hope not, as I had 'To Do' lists and all sorts of things that would cause problems if they were not retrievable. I realise this is a lack of knowledge and foresight on my part. I'm thinking now that I should have run Titanium Backup prior to this, and not assumed that CWM was going to provide a complete solution.
Hope all this makes sense and if any of you have the time to read through and offer advice it would be greatly appreciated. I am currently running a very pretty and slick GalnetMIUI without any of my data!
Thanks in advance.
download cwm 2.5.x.x its better
[email protected] said:
download cwm 2.5.x.x its better
Click to expand...
Click to collapse
Thanks for that, I'll give it a go tonight after work. Am I right in thinking that if it doesn't work I can extract the individual files and insert them manually to get my app data back?
OK, so after hours of searching I'm still no wiser as to how to install CWM 2.5.1.2
I found a zip file that was apparently version 2.5.1.2 but when I tried to install it from inside CWM 5.0.2.6 (included with GalnetMIUI) it sometimes gives an error, sometimes it reboots CWM and sometimes it simply says it has successfully installed (it lies). No matter what it says or does, it doesn't seem to actually replace version 5.0.2.6 with the older one and every time I do the three-finger boot it loads up the latest version like nothing changed.
I'm just so lost. All I want to do is restore my old backup, get my data back and move on. Please someone help me before I go insane from all this research!
[EDIT] In case any more information is needed, my exact procedure for installing version 2.5.1.2 of CWM went like this :
Download 2.5.1.2 zip file
Copy zip file to root folder on internal SD
Boot into CWM 5.0.2.6
Select "install zip from sdcard"
Select "choose zip from sdcard"
Navigate to 2.5.1.2 zip file, select and confirm
Can anyone help me at all?
In particular I'd like to know how I can downgrade to CWM 2.5.1.2 or similar in order to give [email protected]'s suggestion a go.
Failing that, if anyone has any suggestions whatsoever about how I can get my backup data restored it would be greatly appreciated. After spending some time with MIUI - in particular the Galnet ICS build - I have nothing but praise, but I really have to get my data back!
You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.
Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App
Sorry for the delayed reply, for some reason I didn't get an email notification that my thread had been updated.
lowandbehold said:
You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.
Click to expand...
Click to collapse
For some reason, when I select "All ClockworkMod Recoveries" the only two options are 4.0.1.4 and v4.0.1.4. I'll have to look into "fastboot" flashing as I've never heard of that.
By the way, if I boot into CWM via ROM Manager the version that loads is 4.0.1.5, but if I perform the three-button combo when switching my device on I get version 5.0.2.6.
EmoBoiix3 said:
Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I didn't, is that something I should try?
Edit - Just tried this and at first it rebooted CWM and the version number hadn't changed. Doing this again yielded me the following error with no change in version number :
Code:
E:Error in /sdcard/CM V 2.5.1.2_update.zip
(Status 0)
Installation aborted.
I found out that I can extract the contents of my backed up .img files using unyaffs.exe.
Unless I'm doing something wrong, it would appear that my backup is corrupt somehow. When trying to extract data.img, it processes for a while and does bring back a lot of files but I also get the following :
Code:
read image file
: Bad file descriptor
read image file
: Bad file descriptor
data.img is around 1.2GB but the files I extract only amount to around 190MB.
It would appear that I don't have my contacts database in there which is annoying as for some reason there were quite a few that didn't get synced to Google's servers.
EDIT: I solved my own problem. Scroll down to post #8 for the solution.
My problem was that my phone (T-Mobile USA HTC One S) would not boot into ICS anymore, but I was still able to get into recovery (CWM), yet I had no access to the sdcard ("unable to mount /sdcard").
Post #8 below tells you how you can restore access to the sdcard in CWM so that you can push a ROM zip file to the sdcard via adb.
-J
Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium
archie53 said:
Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Unfortunately I didn't have the foresight to make a nandroid backup. My previous phone was a Samsung Galaxy S 4G, which, like most Android phones, has a removable SD-Card that stuff can be copied onto (and then flashed). Not so here obviously.
Is it even possible to push files to the sdcard using the method I tried when in CWM?
When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?
joshnichols189 said:
When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?
Click to expand...
Click to collapse
It just got worse. I got the idea to format all partitions (data, system, cache, sdcard) through CWM, and now CWM can't even mount /sdcard/ anymore...
I had to do the same thing:
adb push "NameOfFile.zip /sdcard
then go to install from zip.
Look on sd card and it will be there.
I always rename the zip files to there can be less errors.
you can also do
adb shell pull "nameOfFile.zip /sdcard
make sure the zip file is where your adb and fastboot is
My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?
LuckyMethod said:
My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?
Click to expand...
Click to collapse
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J
If that doesn't work an easy fix is boot into bootloader, goto fastboot and use "fastboot flash boot boot.img" and so fouth. In the dev section I seen a stock tmobile naindroid. Download it and you'll have your data.img and boot.img. You should be able to flash them without needing to push to /sdcard. letme know how it works
I know you fixed this already just thought this still might help
cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
...cut...
-J
Click to expand...
Click to collapse
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.
LuckyMethod said:
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.
Click to expand...
Click to collapse
Happy it worked for you. Took me several days to figure this out
Sent from my HTC One S using xda premium
I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium
j3.cole said:
I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Thank you. I changed the title and original post to make it easier for people to find this thread.
I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...
mrmoretti said:
I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...
Click to expand...
Click to collapse
IT WORKED! This thread should be made sticky! I'm sure a lot of users who have HTC One S with built-in SD will have the same issue when mucking about with their phone. Thank you!
Bump, as too many people are having this problem.
Sent from my HTC One S using Tapatalk 2
cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J
Click to expand...
Click to collapse
THANK YOU SO MUCH! THIS WORKED PERFECTLY!
This should definitely be included in a stickied guide for people like me who have managed to corrupt their recoveries.
Got it after several tries
hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.
yasir_jan87 said:
hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.
Click to expand...
Click to collapse
Try to shorten the filename, i.e. "rom.zip".
And try this slightly modified command instead:
adb push rom.zip /sdcard/rom.zip
Sent from my aokp_tenderloin using Tapatalk 2
I recently acquired a Photon Q LTE after being an Epic 4G user for years. I've flashed and rooted and beat that Epic 4G to bits over the years, but I can't seem to get CWM installed on this device for the life of me.
I've verified I've unlocked the bootloader and followed the directions in shabby's thread (http://forum.xda-developers.com/showthread.php?t=1856480) and on a couple other sites (http://www.andromods.com/basic-how-...r-user-install-cwm-recovery-photon-q-lte.html and http://www.androidegis.com/how-to/root-and-install-clockworkmod-recovery-on-motorola-photon-q-4g/), but it never seems like CWM wants to stick. Fastboot sends the file fine and says it writes it, but whenever I try to boot into recovery, I get the old school factory recovery with the Red Triangle and the Android System Recovery (3e) header, which is the factory bootloader (right?). Obviously SU isn't going to load in there.
My wife was playing with my new phone before I had a chance to do so (it was a gift), and I think she ran the latest OTA updates before I had a chance to even touch it. Looks like I'm running SW Version 77.8.10.XT897.Sprint.en.US and Android Version 4.0.4, so I don't know if this has been tested with that or if I'll need to revert to a lower version, root, and then upgrade.
Any help would be greatly appreciated.
Thanks!
sometimes stock ROMs have a file in the system folder called recovery-from-boot, which reinstalls stock recovery on boot. if you have flashed SU, try looking in /system, and if that file is there, you can rename it to recovery-from-boot-bak, and that should disable it.
yogi2010 said:
sometimes stock ROMs have a file in the system folder called recovery-from-boot, which reinstalls stock recovery on boot. if you have flashed SU, try looking in /system, and if that file is there, you can rename it to recovery-from-boot-bak, and that should disable it.
Click to expand...
Click to collapse
I haven't been able to get SU installed as I can't get CWM installed. Is there another way to push SU to the phone without CWM?
Running terminal emulator, I can see there's a recovery-from-boot.p file /system, which is probably my issue. So basically, I need to get SU on there somehow to kill it, unless there's a way to kill that file with desktop adb or something.
orty said:
I haven't been able to get SU installed as I can't get CWM installed. Is there another way to push SU to the phone without CWM?
Running terminal emulator, I can see there's a recovery-from-boot.p file /system, which is probably my issue. So basically, I need to get SU on there somehow to kill it, unless there's a way to kill that file with desktop adb or something.
Click to expand...
Click to collapse
ok, i see. damn that's odd, because i haven't seen anyone run into this. i'm trying to think if there
is a way to boot straight into recovery from the bootloader, without booting up the system. i don't think you will be able to modify the file in /system without SU.
---------- Post added at 09:15 PM ---------- Previous post was at 09:11 PM ----------
come to think of it, i think there is a rootkit somewhere here that will install SU without flashing recovery. can't find it atm tho... but i believe it is said to still work on your software version..
actually if i remember correctly, i think it might be Dan Rosenberg's Motofail2Go exploit:
http://forum.xda-developers.com/showthread.php?t=1940594
the other thing you might try is flashing TWRP recovery instead of CWM. i am not sure but maybe TWRP automatically disables the recovery-from-boot file. i used TWRP and i see my file is already renamed and i never consciously did that!
I'll try to get a few minutes tonight and give that a whirl. Will report back as soon as I can.
Thanks!
orty said:
I'll try to get a few minutes tonight and give that a whirl. Will report back as soon as I can.
Thanks!
Click to expand...
Click to collapse
i just posted at the same time as you, so if you didn't see it, perhaps TWRP recovery is worth trying too!
Motofail2go got SU installed, which allowed me to rename that file. Then was able to follow the procedure to install CWM just fine.
Thanks much for the help!
Great, glad you got it working!
Did CWM not stick on my Photon Q ?
What is the key sequence to boot into CWM on a motorola photon Q ? I did an motorola upgrade before I tried any of this so my version nmbers are the same as orty.
SW Version 77.8.10.XT897.Sprint.en.US and Android Version 4.0.4
Here's how it went. - The bootloader unlock seemed to work fine. Things were a little hairy with the CMW install. I am doing this on ubuntu and much like orty I had to make the best guess from various posts. Since I'm not sure of the key sequence to boot for CWM - you can bet I was not holding any buttons when the thing rebooted after downloading CWM. I looked around for a while before I found anything about the key sequence and now if I try a boot holding power & volume up I get an dead android with an red triangle ! in his tummy. I gather this means failure. I did however manage to install Superuser from ChainsDD. Does having Superuser installed mean anything about whether I have CWM installed or not? I am confused! From this post I gather I should try the CMW install again and hold the buttons when it reboots? What do you see to indicate you are in CWM? Some sort of menu?
If I knew how I would try and use the installed SU to look in /system to see if there are any of the mentioned files.
Can somebody give me some clues on next steps I can try at home tonight. Much appreciated!!
penguinpal said:
What is the key sequence to boot into CWM on a motorola photon Q ? I did an motorola upgrade before I tried any of this so my version nmbers are the same as orty.
SW Version 77.8.10.XT897.Sprint.en.US and Android Version 4.0.4
Here's how it went. - The bootloader unlock seemed to work fine. Things were a little hairy with the CMW install. I am doing this on ubuntu and much like orty I had to make the best guess from various posts. Since I'm not sure of the key sequence to boot for CWM - you can bet I was not holding any buttons when the thing rebooted after downloading CWM. I looked around for a while before I found anything about the key sequence and now if I try a boot holding power & volume up I get an dead android with an red triangle ! in his tummy. I gather this means failure. I did however manage to install Superuser from ChainsDD. Does having Superuser installed mean anything about whether I have CWM installed or not? I am confused! From this post I gather I should try the CMW install again and hold the buttons when it reboots? What do you see to indicate you are in CWM? Some sort of menu?
If I knew how I would try and use the installed SU to look in /system to see if there are any of the mentioned files.
Can somebody give me some clues on next steps I can try at home tonight. Much appreciated!!
Click to expand...
Click to collapse
Yeah, sounds like you got into recovery properly by holding volume up while powering on. But it also sounds like your CWM might have gotten overwritten. If you did get SU installed, you can use a file program like Root Explorer or ES File Explorer to look for recovery-from-boot.p in your /system directory, and rename it to recovery-from-boot.bak. then reflash CWM.
smorealt rorer
Ok so a little program to browse for files. I'll load that because I'll blow it away when I redo CWM anyway.
---------- Post added at 11:01 AM ---------- Previous post was at 10:48 AM ----------
Yip there is it - recovery-from-boot.p in /system - so just so I understand - If I rename it now -does this mean it will not be drop-dead necessary to boot straight into CWM after I download CWM onto the phone and it reboots - because the phone won't be setup to undo the CMW anymore.
Also - am I correct that you can make backups using CWM?
penguinpal said:
Ok so a little program to browse for files. I'll load that because I'll blow it away when I redo CWM anyway.
---------- Post added at 11:01 AM ---------- Previous post was at 10:48 AM ----------
Yip there is it - recovery-from-boot.p in /system - so just so I understand - If I rename it now -does this mean it will not be drop-dead necessary to boot straight into CWM after I download CWM onto the phone and it reboots - because the phone won't be setup to undo the CMW anymore.
Also - am I correct that you can make backups using CWM?
Click to expand...
Click to collapse
Yep, correct on both counts you'll see the option 'backup and restore' in CWM.
Well no go on the rename - recovery-from-boot.p cannot be renamed because the file system is read-only.
I installed Total Commander and when I try and remount / as r/w with it I get re-mount error su called failed. Seems my su is not the real thing.
Will it work if I install CWM and boot straight from the download into the CWM - can I rename the file from there somehow?
If you can get adb access in CWM, there should be a command to rename that file, i'm not sure if it would be from adb shell or not... perhaps Google it or someone else will chime in here. You would probably need to flash SU first, then try adb and type su first and see if you get # prompt.
Otherwise you can go thru the full cycle- flash CWM, boot straight into recovery, flash SU, reboot and rename the recovery file, reflash CWM. Using adb in CWM would be the more elegant way, haha.
I am OK with full cycle - just explain this to me --> boot straight into recovery, flash SU,
I think I know how to boot straight into recovery -> but how do I flash SU from there?
Do I have to get the su.zip onto the phone before I boot into recovery? How do I do that?
Which reminds me of another question the http://forum.xda-developers.com/showthread.php?t=2017748 thread says
Bugs:
Usb mass storage isnt working,
Is this still true? Does this mean if you install CWM you can't mount your phone as mass storage in anyway ?
Yeah, load the SU zip onto your phone before going into CWM, since usb storage might not mount. Easiest way might be just to DL the zip on the phone by going to the thread on the phone, then navigate to your downloads folder in CWM to flash it. Otherwise if you have a more recent version of Ubuntu, you might be able to access device storage thru usb to transfer the zip... or else you can do that in Windows(or Mac maybe?).
Edit: flashing CWM won't break usb storage in general, it just doesn't seem to mount in CWM.
Great - so I downloaded the SU.zip from my phone and it is in /sdcard/Download for later. So I assume loading CWM does not erase what is in the download folder ?
And thanks for explaining that CWM just break usb mount in CWM not generally.
Much Much appreciated.
CWM shouldn't erase whats in the download folder. If it does, there's an issue there.
And why not just use MotoFail2Go to push in SU and then use RomManager from the appstore to flash CWM from the OS itself, because that fixes the rewrite issue as well and is a much simpler process?
CMNDR
since I am using ubuntu the word "windows" in the link did not draw me in .... am I missing something?
http://vulnfactory.org/public/motofail2go_windows.zip
penguinpal said:
since I am using ubuntu the word "windows" in the link did not draw me in .... am I missing something?
http://vulnfactory.org/public/motofail2go_windows.zip
Click to expand...
Click to collapse
i always keep a Windows installation around, just for certain programs. but, by doing this the manual way, at least you get to see what is being done, instead of programs doing it for you