Okey fellow members of XDA, time to work your magic!
Been rooted and running CM ever since I gor my Nexus S, which was on the day of release. Everything has been working smoothly, until recently.
When I try to boot up my phone, I get stuck on the GOOGLE logo, and when I go into CW, it tells me that E:Can´t mount /sdcard/.
Been browsing the web and XDA, found some people with the same problem but no answers.
Help would be veeeeeery appreciated!
I had a similar Problem with a Nexus S i9020T.
But in my case i couldn't really write on the sdcard for good. I just shove some zip files onto the sdcard and the second i unmounted, everything was back to the way it was. Even formating the sdcard didn't really delete anything.
and when i did get some zip files onto the card, CWM told me they were bad..
I got the phone running again by flashing with fastboot but that didn't really make the problem go away. Dozens of FC's because the phone couldn't really access the sdcard..
So all i can suggest for you is to try to flash with fastboot
Try mounting /data/. If that didn't work, your NAND might be shot.
Sent at 88 miles per hour, powered by 1.21 jiggawatts of electricity.
litanyoffail said:
Try mounting /data/. If that didn't work, your NAND might be shot.
Sent at 88 miles per hour, powered by 1.21 jiggawatts of electricity.
Click to expand...
Click to collapse
The same happend with my phone. Where I can order memory chip for 9023 model?
Related
So I was running the may 5 nscollab for a few days and experienced a lot of reboots, then eventually boot loops or whatever we call the reboot leaving you with backlights on and black screen. I usually pulled the battery and things were fine for a while. I was not over clocking or using bln. The last time, about a week ago, my 9020t couldn't reboot. I was able to get in to recovery, but cwr was unable to mount any partitions but /cache. All wipes failed, and so did permission fix because of this.
Next, I fired up adb. No problem there. Started fastboot and locked then unlocked but the problem remained. So I tried flashing IMgs from a stock recovery. Recovery.img worked fine. System, boot failed after 30 seconds with write errors. I also got an error on the fastboot screen that two addresses were exceeded. I didn't write them down as I don't know that they are important, having googled these.
Next came Odin with a 2.3.1 set of tars for 9020. It hung trying to flash system.img. I tried a few times with the same results.
Last, I checked what was up with adb shell. I found out I can manually mount /dev/block/mmcblk1 as /sdcard and could read and write to it. I pushed a rom zip and flashed it using cwr with no errors, but on reboot I saw it was nothing but the recovery.
Any ideas. It seems the other partitions are not mounting. Can't I just wipe everything and repartition then flash with Odin? I don't know why Odin didn't work. Do I need a pic file for the nexus s? Bah! It is frustrating that a brick is not a brick.
Really, any ideas? Sucks to have a 600 dollar phone that spontaneously combusted like this.
it seems i am missing /dev/block/platform/s3c-sdhci.0/by-name/system
and /dev/block/platform/s3c-sdhci.0/by-name/userdata
so they wont mount. Also, the mtdblock files in /dev/block aren't even listed in fstab. is there any way i can wipe this base system? Odin won't do it. Nothing I have tried can overwrite whatever is royally messed up in the filesystem. It seems that even for any recovery to work properly, the mounts must be correct!!!!
Unfortunately, sometimes as a brick is a brick. I have similar symtoms as you - I cannot mount /system and cannot get past the google splash screen. I cannot write or read to storage.
http://forum.xda-developers.com/showthread.php?t=993403
I've already called Samsung to send the phone in, just lagging putting it in the mail. I've been using my g1 for past couple of weeks.
irishrally said:
Unfortunately, sometimes as a brick is a brick. I have similar symtoms as you - I cannot mount /system and cannot get past the google splash screen. I cannot write or read to storage.
http://forum.xda-developers.com/showthread.php?t=993403
I've already called Samsung to send the phone in, just lagging putting it in the mail. I've been using my g1 for past couple of weeks.
Click to expand...
Click to collapse
Thank goodness for my g1 also!
What did they say to you? I do not like the idea of having to pay. Bah!
PM's sent to both of you. I can fix this issue with JTAG...
Samsung didn't say much, just send it in. I'm hoping it won't cost anything but if it does I may consider the jtag services mentioned above.
connexion2005 said:
PM's sent to both of you. I can fix this issue with JTAG...
Click to expand...
Click to collapse
How much for the instructions to do this? We have a device at work that the EEs use to jtag TI micro-controllers. Not sure if that would work. If Samsung gets all crazy and tries to charge me ridiculous amounts of money I may go your route.
irishrally said:
Samsung didn't say much, just send it in. I'm hoping it won't cost anything but if it does I may consider the jtag services mentioned above.
How much for the instructions to do this? We have a device at work that the EEs use to jtag TI micro-controllers. Not sure if that would work. If Samsung gets all crazy and tries to charge me ridiculous amounts of money I may go your route.
Click to expand...
Click to collapse
I doubt it would work. Does it support ARM 8 architecture? YouTube search "nexus s jtag" and you can see my video.
Please let me know, either method. I can wait a little while. Thanks.
Hello:
I'm having a frustrating experience attempting my first root of my G2X.
I've had a previous thread from yesterday, attempting to do things from the Mac side:
http://forum.xda-developers.com/showthread.php?t=1172487&highlight=velanche
As of now, I've decided to revert to Windows 7 on my Mac to try and rectify things. I'm able to use One-Click Recovery Flasher, following the instructions, to flash the phone. I then downloaded an earlier nightly version of CM7, installed it on my flash drive, and did the install via ClockworkMod.
I had no errors from CWM, from the wipe to the install. I then choose the reboot open, and it powers off my phone.
Upon attempting to turn on my phone, I would get the LG screen, followed by a quick flash, followed by another LG screen with some horizontal blue background behind it. I'm taking it that it means that it's stuck, because I've waited 10 minutes before having to do a battery pull.
I did at one time attempted to flash back to the stock T-Mobile, but when the LG screen came it, it would just remain there without any progress.
At this stage, I don't know where else to go. I'm not sure if there's something amiss, because my phone, as far as I know, as been erased. If there's a way to progress to CM7, I'm game. But one thing I really need to do is to get my phone back.
I didn't backup my phone's contents initially because I was going to recreate everything anyway. Now I'm in a not-so-good place, save having to get a phone exchange.
Any assistance would be appreciated; thanks so much.
V.
Download one of the "Stock Rooted Nandroid Backups" from the development section, stick it on your SD card and do a Nandroid restore from CWM. That should get your phone working again...
On the CM7 installation problem, I have no idea what that could be. I've been flashing ROMs on Android devices since the G1 first came out a few years ago and the only reasons I had bootloops were from me trying to flash without wiping or flashing an unstable build.
Sorry to digress for a second here, but you DO have the T-Mobile branded G2x and NOT the Optimus2x, right?
Working on It
Hey thanks for the help.
I have a T-Mobile G2X, so I should have done everything the way I expected. Then again, things should have worked if I did.
So I installed the Nandroid recovery for my phone, and attempted recovery via CWM, but ended up with a MD5 mismatch error (whatever that means).
I even went so far as move select files from my SD card. I formatted it, then put in those select files i wanted to keep.
I tried again, and no change.
Any suggestions on how I should proceed? Thanks!
V.
I get the same kind of "just not going to happen" errors when I try to install EaglesBlood. I've found no solution, though CM7 works just fine. I don't know what to tell you, really...
Sent from my Nexus 5g using XDA Ultimate App
velanche said:
Hey thanks for the help.
I have a T-Mobile G2X, so I should have done everything the way I expected. Then again, things should have worked if I did.
So I installed the Nandroid recovery for my phone, and attempted recovery via CWM, but ended up with a MD5 mismatch error (whatever that means).
I even went so far as move select files from my SD card. I formatted it, then put in those select files i wanted to keep.
I tried again, and no change.
Any suggestions on how I should proceed? Thanks!
V.
Click to expand...
Click to collapse
The md5 mismatch will happen if you try to copy and past the files. Try it again but this time unzip it directly to the fold where it should be. Do not copy and past the unzipped folder. This is also someones backup so you must go through the restore option in cm
Sent from my LG-P999 using XDA Premium App
LordButtersI said:
I get the same kind of "just not going to happen" errors when I try to install EaglesBlood. I've found no solution, though CM7 works just fine. I don't know what to tell you, really...
I don't know if this might have anything to do with why I've had problems getting CM7 to work, but I've noticed that when I plug the phone either into Windows or OS X, I've somehow lost the internal drive. I know that it's there because I've found a whole bunch of files on it while in CWN, but I'm suspecting that there's some link between neither computer seeing the internal drive and the issue with getting the phone to boot.
Yes, I can mount the external drive, either from CWM's mount on both platforms or when I press both volumes on my phone and plug in to Windows 7 via USB.
Do you have any insight on this? I was watching a few of The Unlockr vids, and I noticed that even though the guy's phone was rooted and flashed, he still could boot into his phone until he was ready to put on the new ROM (CM7, in this case).
Thanks!
Click to expand...
Click to collapse
scooter247 said:
The md5 mismatch will happen if you try to copy and past the files. Try it again but this time unzip it directly to the fold where it should be. Do not copy and past the unzipped folder. This is also someones backup so you must go through the restore option in cm
I tried on the OS X side to do this, having to download an RAR app. I found the LG file, and told the app to extract it to the backup directory on my phone. I tried the restore again in CWM, but still a mismatch.
I will try it in Windows 7 tomorrow, and will let you know the outcome.
I'm beat; spent the whole weekend on this phone modding biz. I suspect I'll be really good by the time I finally am able to get things working.
V.
Click to expand...
Click to collapse
Is this an old SD card? Perhaps some bad sectors on it? Without holding the phone in my hands I can't think of anything else. Other than double check your steps, re-copy the files and try, try again.
The SD card is not old; about 2 months old. I tried formatting the card via Windows 7, but did it in FAT32. I take it that it's supposed to be formatted differently? The card is 16GB, but when I looked into CWM it's limit is 4GB.
I tried the steps again, and still get the same md5 mismatch. Is my guess correct that the card is supposed to be formatted a certain way? Unfortunately, I can access the previous OS via my phone, nor will the internal memory appear when the phone is plugged into the computer. However, I am able to mount the SD card within the computer's OS.
I almost feel like walking away from it for a week, but that means I'll be stuck without phone access for awhile. Tips or suggestions are most welcome.
BTW, there's apparently alternate instructions to deal with the md5 mismatch error. Though in Windows the NDIVIA driver is loaded for the phone, I tried the adb shell command but my device isn't detected by the software.
Thanks again,
V.
Hello all
I suspect that either my Nexus has a hardware fault (internal memory) or I bricked it somehow.
For the past few weeks the phone has been getting stuck on the google boot screen quite a lot - It takes several attempts
to start up each time so I've been trying to keep the battery from running down.
The other day while I was attempting to switch roms I put the stock img on my SD card but when I went to flash it CWM
couldnt mount my (internal) SD Card. Senior forum member Caliban2 suggested that it could be my recovery so I installed CWM 6.0.0.7 non-touch using fastboot and, like magic, the phone started up -though I suspect this may have been luck.
I rebooted the phone out of curiosity and it got stuck on the google boot screen - no amount of battery pulling and restarting could coax
it back to life, so I went into CWM again to discover that it could not mount the SD Card, I was getting the 'cannot mount' and 'E:Unable to open ums lunfile(no such file or directory)' error messages. My windows 7 PC could see the phone but said that their was non memory inserted. Out of curiosity I installed CWM 5.0.2.0 but that produced the same results.
So now my phone appears dead, is the internal memory or something related to it is broken? I have seen things on here about using an unbricking tool in Debian Linux or flashing stock using odin but I confess that I have not tried these solutions and don't fully understand them (yet).I wussed out and dropped the phone into a local repair workshop, I imagine they will be trying these same steps themselves and they say it will take them a few days to get back to me.
My problem is that I need a phone for work and I gave my backup phone (HTC Hero) to my dad recently. Should I just take the plunge
and go out today and buy a new phone? Or is there a reasonable chance that these guys can fix my nexus s, or that I might be able to?
I'm a relative 'noob' at this so I thank you all for your advice in advance, it's much appreciated.
Derek
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Thanks, will do. It's in the shop at the moment, I suspect this is probably what they're doing now.
Perhaps subconsciously I'm just looking for someone to tell me it's irreparable so I can rush out
and pick up a Galaxy Nexus.
Harbb said:
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Click to expand...
Click to collapse
Hey Harbb
Just wanted to give you an update on this, got it back from the shop who said they would need to send it to Samsung for a hardware repair, didn't expect it to work but fastbooted the stock bootloader, radio and image to the device and it's now working!
I've already moved onto a Galaxy Nexus on contract but at least now I can make a bit of money back off my old phone.
Thanks again for the advice
Derek
Harbb said:
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Click to expand...
Click to collapse
I am relatively new at ROMs and I installed CyanogenMod 10 on my AT&T HTC One X (US) a couple of months ago. Recently, I tried upgrading to the M2 release of CM10.1 using the evita package which I understand is the US version of the ROM. I followed the same instructions I used to install 10.0 for 10.1. However, the installation froze and did nothing for a few minutes and gave me the message "no MD5 file found". I shut the phone down and restarted, but the phone would no longer start. I did a "system wipe" to get ride of the OS so I could re-install it, but now, my computer won't recognize my phone when I connect them and I can't move the CM10.1 zip file from my desktop to my phone. I have nothing already on the phone I can flash besides Team Win Recovery Project which is what I use for Recovery. I have no recovery files.
Did I just paperweight my phone, or is there a way to salvage this situation.
sliceroo said:
I am relatively new at ROMs and I installed CyanogenMod 10 on my AT&T HTC One X (US) a couple of months ago. Recently, I tried upgrading to the M2 release of CM10.1 using the evita package which I understand is the US version of the ROM. I followed the same instructions I used to install 10.0 for 10.1. However, the installation froze and did nothing for a few minutes and gave me the message "no MD5 file found". I shut the phone down and restarted, but the phone would no longer start. I did a "system wipe" to get ride of the OS so I could re-install it, but now, my computer won't recognize my phone when I connect them and I can't move the CM10.1 zip file from my desktop to my phone. I have nothing already on the phone I can flash besides Team Win Recovery Project which is what I use for Recovery. I have no recovery files.
Did I just paperweight my phone, or is there a way to salvage this situation.
Click to expand...
Click to collapse
Are you able to get into recovery?
joelrwise said:
Are you able to get into recovery?
Click to expand...
Click to collapse
Yes. I can get into recovery and the screen that tells you the root status of the phone.
sliceroo said:
Yes. I can get into recovery and the screen that tells you the root status of the phone.
Click to expand...
Click to collapse
If you can get into recovery then you aren't bricked just yet! If you have an sd card reader on your computer or know somebody who does thats one way you could get a new rom on your phone to flash. Most recoveries have a way to let you connect your phone to your computer for file transfer while in recovery. I believe in TWRP the option is in the Mount are. I could be wrong though. You just need to figure out how to get a new Rom on your phone. If none of the above work, one trick that has always worked for me, would be to put your sd card into someone elses phone, and download a known working rom onto your sd card via theyre phone, and just put it back into your phone. Hope i helped. Let me know how it goes man. I've been here before haha
joelrwise said:
If you can get into recovery then you aren't bricked just yet! If you have an sd card reader on your computer or know somebody who does thats one way you could get a new rom on your phone to flash. Most recoveries have a way to let you connect your phone to your computer for file transfer while in recovery. I believe in TWRP the option is in the Mount are. I could be wrong though. You just need to figure out how to get a new Rom on your phone. If none of the above work, one trick that has always worked for me, would be to put your sd card into someone elses phone, and download a known working rom onto your sd card via theyre phone, and just put it back into your phone. Hope i helped. Let me know how it goes man. I've been here before haha
Click to expand...
Click to collapse
I went into TWRP Mount and it allowed me to mount the phone. I went ahead and did that, but Windows told me that I had to format the disk. I agreed and Windows formatted it. Afterwards, I successfully copied over the CM10.1 Evita M2 zip file and the lates Gapps zip file. I then went to TWRP's install section and flashed both zips. TWRP told me both happened succesfully. However, while flashing over the CM10.1 file, it told me that no MD5 file was found and that it was just going to skip that. Then, it formatted some mke5 partition and then went ahead and finished. I wiped the Dalvik cache and the system Cache and restarted the phone. It is currently stuck at the "HTC Quietly Beautiful" intro screen and won't boot past that. Is there something I missed?
If that 10.1 already failed because of an MD5 problem, I wouldn't have tried to flash it again - the file probably has some problems in itself and either needs to be re-downloaded or just won't work.
Just flash the stock firmware or something - and use an MD5 checking program.
Pennycake said:
If that 10.1 already failed because of an MD5 problem, I wouldn't have tried to flash it again - the file probably has some problems in itself and either needs to be re-downloaded or just won't work.
Just flash the stock firmware or something - and use an MD5 checking program.
Click to expand...
Click to collapse
The thing is TWRP returned the status as successful despite missing the MD5 file. I'll try flashing over another package and if that doesn't work, I'll try flashing over CM10. If that still doesn't work, I'll just do stock firmware if I can find it somewhere, I guess.
In the future, making a backup is really awesome. Not saying that like "I told ya so" - but I've used them so many times myself, it's really great to say, "oops, I overlooked something" and then be able to just go back to a perfect snapshot of how things were before.
Also, how long did you let the phone sit at the boot screen ? It can hang for quite a while on the first boot.
Pennycake said:
In the future, making a backup is really awesome. Not saying that like "I told ya so" - but I've used them so many times myself, it's really great to say, "oops, I overlooked something" and then be able to just go back to a perfect snapshot of how things were before.
Also, how long did you let the phone sit at the boot screen ? It can hang for quite a while on the first boot.
Click to expand...
Click to collapse
Yeah I would just reflash a ROM that you've used before and that you know works. Chances are if the cm10.1 didn't work the first time its probably not going to the second time. And he has a point. First boot always takes forever. I've flashed a couple ROMs and thought I was bootlooped but I let it sit for a good 5-10 minutes and the setup screen finally came up.
joelrwise said:
Yeah I would just reflash a ROM that you've used before and that you know works. Chances are if the cm10.1 didn't work the first time its probably not going to the second time. And he has a point. First boot always takes forever. I've flashed a couple ROMs and thought I was bootlooped but I let it sit for a good 5-10 minutes and the setup screen finally came up.
Click to expand...
Click to collapse
I had no idea that it could take that long. I guess I'll just turn my phone on and see if it wants to start. I'll leave it going for a good five to ten minutes this time. Shutting the phone down while its still in the intro screen doesn't damage the OS, does it? Thanks for the advice so far guys, I really appreciate it.
Hi
I bought some electronics at an auction and there was a Asus TF101 included in the lot. After reading about the unit I thought it would be great for personal use. I ordered a charger online an I tried it but it gets stuck at the boot screen. If I try switching it off it just switches back on. I think this is a botched root job but I don't know what the previous owner did. I doubt it is hardware related though. It has Clockworkmod Recovery v6.0.1.3 installed and can boot into the recovery but honestly I am a bit lost at what to do next.
Attempts to wipe the data etc to reset the device has all failed. It seems it needs to be flashed so any help will be appreciated. While I am at it I was thinking of going for one of the newer roms here on XDA available for the device.
Update: I wiped the user data and got the unit reset but now it boots straight into the clockworkmod app
Thanks!
Johandj73 said:
Hi
I bought some electronics at an auction and there was a Asus TF101 included in the lot. After reading about the unit I thought it would be great for personal use. I ordered a charger online an I tried it but it gets stuck at the boot screen. If I try switching it off it just switches back on. I think this is a botched root job but I don't know what the previous owner did. I doubt it is hardware related though. It has Clockworkmod Recovery v6.0.1.3 installed and can boot into the recovery but honestly I am a bit lost at what to do next.
Attempts to wipe the data etc to reset the device has all failed. It seems it needs to be flashed so any help will be appreciated. While I am at it I was thinking of going for one of the newer roms here on XDA available for the device.
Update: I wiped the user data and got the unit reset but now it boots straight into the clockworkmod app
Thanks!
Click to expand...
Click to collapse
Since you have Clockwork installed and recovery is booting, look here.
http://forum.xda-developers.com/eee-pad-transformer/development/rom-t2942560
See the install instructions, upgrading to TWRP and flashing rom and other components.
mb_guy said:
Since you have Clockwork installed and recovery is booting, look here.
http://forum.xda-developers.com/eee-pad-transformer/development/rom-t2942560
See the install instructions, upgrading to TWRP and flashing rom and other components.
Click to expand...
Click to collapse
I did see that and I have done some more reading since I posted here. Will I be able to upgrade from Clockwork to TWRP 2.8. if the unit doesn't boot?
Also I got an error saying that the sdcard cannot be mounted. I know this is the internal storage and not the actual sd card.
Johandj73 said:
I did see that and I have done some more reading since I posted here. Will I be able to upgrade from Clockwork to TWRP 2.8. if the unit doesn't boot?
Also I got an error saying that the sdcard cannot be mounted. I know this is the internal storage and not the actual sd card.
Click to expand...
Click to collapse
I believe I flashed mine that way. If you have just wiped storage that is the normal error. I would give it go
mb_guy said:
I believe I flashed mine that way. If you have just wiped storage that is the normal error. I would give it go
Click to expand...
Click to collapse
That one worry less, was worried something hardware wise was faulty.
This may sound like a stupid question (definitely newbie question) but if I cant access the internal storage how am I going to copy TWRP onto the internal storage and run the install from clockwork?
Johandj73 said:
That one worry less, was worried something hardware wise was faulty.
This may sound like a stupid question (definitely newbie question) but if I cant access the internal storage how am I going to copy TWRP onto the internal storage and run the install from clockwork?
Click to expand...
Click to collapse
Sorry it has been a long time since I used Clockwork, but does it not see the external removable sd card? Or try the adb push method if the CM version will support.
https://wiki.cyanogenmod.org/w/Install_CM_for_tf101
No after some blood sweat and lots of foul language I got 4.4.4 loaded just to dicover the lcd has a nice shade of green ..... So LCD = another $30... lol I am so deep in...... Anyway started a new thread just to check if anybody else had the same problem and whether in fact it is the LCD that faulty
Oh just For info... I used EasyFlasher to get TWRP 2.6 onto the Unit with a very nice step by step guide for a newbie like me here
:http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
I then Used Kisskat 4.4.4 here at XDA forums to flash the Unit. Lollipop was not happy with the older version of TWRP