I might have messed up the connector of the connector on the PCB for the microSD holder's bus while I replaced the LCD screen on my G2. Whenever I put in a card it gives the "unsupported filesystem please format" or " SD card removed or unmounted" error. I have tried with several SD cards and none has worked.
Is there a way to load up a rom without the microSD card?
Plus would it to possible to replace the connector?
Sent from my DoubleShot using xda app-developers app
It might be possible via fastboot in the main boot loader, but I wouldn't know how to go about that.
yes with fastboot, when in bootloader choose fastboot
open a cmd in the same folder fastboot.exe is along with the rom, type fastboot devices in cmd, if you see yours proceed -
all fastboot commands will show up by simply typing fastboot into cmd, you can flash radios, recoverys, spls, roms, etc here
all without sd cards
Sent from my HTC Vision using xda premium
Thanks a lot guys. Really appreciate the help.
Sent from my HTC DoubleShot using xda app-developers app
So my few attempts to flash left me with a semi brick . I tried flashing a zip through fastboot and didn't do it right unfortunately. I still have access to hboot and when I try wiping via recovery I get the following errors.
How do you unbrick a device when it say this in recovery?
E: cant mount /cache/recovery/command
E: cant mount /cache/recovery/log
E: cant open/cache/recovery/log
E: cant open/cache/recovery/last_log
E: cant mount /cache/recovery/last_log
during wipes it always gives me the
E: cant mount /cache/recovery/log
E: cant open/cache/recovery/log
E: cant open/cache/recovery/last_log
E: cant mount /cache/recovery/last_log
errors
Sent from my myTouch_4G_Slide using xda app-developers app
those errors either don't matter or are a sign of a fried emmc.
try to flash a new recovery via fastboot
you can also wipe via fastboot -w
Sent from my HTC Vision using xda premium
cybot_x1024 said:
So my few attempts to flash left me with a semi brick . I tried flashing a zip through fastboot and didn't do it right unfortunately. I still have access to hboot and when I try wiping via recovery I get the following errors.
How do you unbrick a device when it say this in recovery?
E: cant mount /cache/recovery/command
E: cant mount /cache/recovery/log
E: cant open/cache/recovery/log
E: cant open/cache/recovery/last_log
E: cant mount /cache/recovery/last_log
during wipes it always gives me the
E: cant mount /cache/recovery/log
E: cant open/cache/recovery/log
E: cant open/cache/recovery/last_log
E: cant mount /cache/recovery/last_log
errors
Sent from my myTouch_4G_Slide using xda app-developers app
Click to expand...
Click to collapse
Those are considered normal if you did a full wipe, brand new hboot etc, because /cache partition hasn't been formatted yet. You can always go into clockworkmod and select factory reset / wipe cache / wipe dalvik etc, and then reboot into recovery to see if it goes away.
Have you tried testing it with a new rom, to see if the partitions are formatted correctly after that?
EDIT: Well I guess you can't if you don't have a microSD card... cuz otherwise I was going to say grab the Superwipe zip file and place it on the card and apply it.
kbeezie said:
Those are considered normal if you did a full wipe, brand new hboot etc, because /cache partition hasn't been formatted yet. You can always go into clockworkmod and select factory reset / wipe cache / wipe dalvik etc, and then reboot into recovery to see if it goes away.
Have you tried testing it with a new rom, to see if the partitions are formatted correctly after that?
EDIT: Well I guess you can't if you don't have a microSD card... cuz otherwise I was going to say grab the Superwipe zip file and place it on the card and apply it.
Click to expand...
Click to collapse
I wouldn't go with superwipe in this cases. Today it has really scared me. I got my phone back from assistence, rooted it and the first thing I did, for an error, was a superwipe, I haven't been able to read from sd or boot the phone for about two hours. Then suddendly it started working again, but if it's an emmc problem I wouldn't superwipe...
virtualflyer said:
I wouldn't go with superwipe in this cases. Today it has really scared me. I got my phone back from assistence, rooted it and the first thing I did, for an error, was a superwipe, I haven't been able to read from sd or boot the phone for about two hours. Then suddendly it started working again, but if it's an emmc problem I wouldn't superwipe...
Click to expand...
Click to collapse
Yea that's a big if (emmc problem), though how would you be able to tell anyways?
I got those errors all the time with cwm recovery, switched to ext 4 and havent gotten them once.
Edit: I also had a problem on my HTC desire (original) where it wouldn't read the SD card. But it would read it in recovery. Have you tried getting into your SD card from recovery?
Sent from my HTC Desire Z using XDA Premium App
Thanks for all the ideas you are giving me but if I have to try out a rom I need figure out how to load that from adb, first. I don't want to risk bricking it any further.
How do I repartition it without an SD card?
I also tried accessing the SD card via recovery and wasn't successful.
Sent from my myTouch_4G_Slide using xda app-developers app
ptaylor09 said:
I got those errors all the time with cwm recovery, switched to ext 4 and havent gotten them once.
Edit: I also had a problem on my HTC desire (original) where it wouldn't read the SD card. But it would read it in recovery. Have you tried getting into your SD card from recovery?
Sent from my HTC Desire Z using XDA Premium App
Click to expand...
Click to collapse
How would I load up 4ext without an SDcard or a working rom?
Sent from my myTouch_4G_Slide using xda app-developers app
cybot_x1024 said:
How would I load up 4ext without an SDcard or a working rom?
Sent from my myTouch_4G_Slide using xda app-developers app
Click to expand...
Click to collapse
The recovery.img can be flashed via fastboot. (if you can find it, if not this copy I have here is specifically for G2/DZ http://xlu.be/g2/4EXT_Recovery_Touch_v1.0.0.5_RC5.zip can be used as a PC10IMG.zip or can be unpacked to fastboot flash the recovery.img )
Related
So I'm trying to install update.zip in recovery to get to clockwork. Problem is its not letting me install it, I'm getting the following error:
E:Can't mount /dev/block/vold/179:9
(no such file or directory)
E:Cant mount SDCARD:update.zip
Ive tried various downloads, and 2 different SD cards still no luck. Also tried various Odin's too.
Should I try to flash to stock then start over? I was running a Voodoo kernel and did a fixed lagfix(odd typing that) now I'm stuck. This really has me puzzled.
By the way i cant boot to android either
Thanks for all the help and awesome forum!
Well I'm back to stock now, but at least its not a brick
if anyones curious or has this problem i used the adrynalyne.us/files/kernels/DI01package3.tar.md5 to flash the stock rom.
WHAT I DID:
From stock ROM, albeit rooted -
opened ROM Manager
chose to download CM7rc2, also ticked Google bundle
allowed it to do its thing
Could not log into Google account, same as with CM6 - why does it hate me?
decided to flash back to previous backup
^^ that's where it gets stuck. I have 4 different nandroid backups, and none of them will restore. The best I can get is a boot loop. Right now I'm getting
Code:
Can't open /cache/recovery/log
can't open /cache/recovery/log
can't open /cache/recovery/last_log
can't open /cache/recovery/last_log
Checking MD5 sums...
Erasing boot before restore...
Error while erasing boot image!E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
futuremonkey said:
WHAT I DID:
From stock ROM, albeit rooted -
opened ROM Manager
chose to download CM7rc2, also ticked Google bundle
allowed it to do its thing
Could not log into Google account, same as with CM6 - why does it hate me?
decided to flash back to previous backup
^^ that's where it gets stuck. I have 4 different nandroid backups, and none of them will restore. The best I can get is a boot loop. Right now I'm getting
Code:
Can't open /cache/recovery/log
can't open /cache/recovery/log
can't open /cache/recovery/last_log
can't open /cache/recovery/last_log
Checking MD5 sums...
Erasing boot before restore...
Error while erasing boot image!E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
What version of clockwork recovery are you using and are you trying to restore a CM6 backup or CM7. Did you wipe before installing CM7? Also its been posted several places about using rom manager to update some have had issues and posted. Its probably best to use it to download the rom you want but for best results installing it manually usually avoids issues atleast for me anyways.
Sent from my CM7 powered G2
userfriendlyme said:
What version of clockwork recovery are you using and are you trying to restore a CM6 backup or CM7. Did you wipe before installing CM7? Also its been posted several places about using rom manager to update some have had issues and posted. Its probably best to use it to download the rom you want but for best results installing it manually usually avoids issues atleast for me anyways.
Sent from my CM7 powered G2
Click to expand...
Click to collapse
I am using the current version, 3.0.0.5 or something like that (I can't get into my phone to check). I am trying to restore a stock ROM. I have three backups made with ClockworkMod and none of them will restore. I try to start the restore, and after a few seconds I get "Error while erasing boot image: can't open /cache/recovery/log"
what method did you use to obtain root?
ruleftbehind said:
what method did you use to obtain root?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
The older versions of CWR 3.0.0.5 had some troubles retsoring their backups. Try to find a new one.
And regarding the boot problem.
Try to wipe cache
If it still does not boot, connect it to USB and run an adb logcat while it is booting. Ther should be some helpful information.
Sent from my HTC Vision using XDA App
guhl99 said:
The older versions of CWR 3.0.0.5 had some troubles retsoring their backups. Try to find a new one.
And regarding the boot problem.
Try to wipe cache
If it still does not boot, connect it to USB and run an adb logcat while it is booting. Ther should be some helpful information.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
adb logcat just says "waiting for device" forever.
You can't restore a stock rom with clockworkmod 3, as the stock rom is based on froyo (2.2)
Sent from my G2 running Cyanogenmod 7.
damn, that sucks!
You can use CWM 3.0.0.5 to flash between CM7, CM6, stock, etc and restore backups. I do it all the time. The newer versions (after 3.0.0.5) don't have that ability.
The output you provided most likely means you didn't wipe before flashing.
Reboot into recovery and wipe user data as well as cache. A nandroid restore from recovery should wipe automatically. I'm not sure Rom manager does it by default or you have to select the option. Perhaps that's why you got a boot loop.
If the restore fails Use ADB to push a rom. Sounds like it's not recognizing your device (perhaps a driver issue). If you can't use ADB, just mount usb in recovery and transfer a rom update. Remember to wipe cache and data, then flash. You will lose your apps and data, but you can restore them if you used Titanium Backup.
I do it all the time. The legit version of 3.0.0.5 that's offered through rom manager will allow you to reflash any rom
ibemad1 said:
You can't restore a stock rom with clockworkmod 3, as the stock rom is based on froyo (2.2)
Sent from my G2 running Cyanogenmod 7.
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App
Spastic909 said:
I do it all the time. The legit version of 3.0.0.5 that's offered through rom manager will allow you to reflash any rom
Click to expand...
Click to collapse
It was my understanding, unless koush put a fix in recently, that CWM3 only works using the ext4 file system which isn't compatible with CM6 or stock-they use ext3.
What I'd suggest doing is
-downloading the most recent version of CWM3,
-flash that through fastboot,
-try to boot in to recovery,
-wipe the phone, and
-try manually flashing CM7 and then the gapps.
That should resolve everything. If it doesn't, let us know and we'll try something else. Good luck.
QaeadarDAzeal said:
It was my understanding, unless koush put a fix in recently, that CWM3 only works using the ext4 file system which isn't compatible with CM6 or stock-they use ext3.
What I'd suggest doing is
-downloading the most recent version of CWM3,
-flash that through fastboot,
-try to boot in to recovery,
-wipe the phone, and
-try manually flashing CM7 and then the gapps.
That should resolve everything. If it doesn't, let us know and we'll try something else. Good luck.
Click to expand...
Click to collapse
He supposedly did but if that's true then why in the world didn't he fix the sd-ext aspect. Still doesn't see the ext partition *sigh*. Anyway, even if he did fix it doesn't mean it will work for everyone, especially when dealing with wildly different file systems. Especially with how different each phone can be. It just means it should work - no guarantee. If everyone else's suggestions don't work (which they should), then use rom manager to download and flash the most recent 2.x clockwork.
alright, I updated to 2.2 and I was going to make a backup.. but once I booted into stock recovery and tried to apply the update.zip I got this error
E:Can't mount /dev/block/vold179:9
(no such file in directory)
E:Can't mount SDCARD:bplib_delta_for_test.bin
then..
E:Can't mount /dev/block/vold179:9
(no such file in directory)
E:Can't mount SDCARD:update.zip
Installation aborted
any help would be appreciated. I couldn't find a fix anywhere I read.
thanks in advance!
I have the same issue...
Sent from my HTC Sensation 4G using XDA Premium App
I had this error when I was using imnuts recovery kernel (correct button mapping i.e. camera button selects) so instead I odin'd (haha) adryn's test_2 kernel from the "official" thread (the screwy button mapping i.e. press the menu softkey area) and it fixed the problem xP
I posted what happened in the ec04 stock thread too
Sent from my SCH-I400 using XDA Premium App
i had this problem when i first upgraded to froyo, but i started from scratch which probably wasn't necessary, well here's what i did:
-i odin'd stock dl17 full odin package
-rebooted phone, let it do its thing
-i put the blue(cyan) cwm update.zip file and rom/kernel for froyo on my sd card
-odin'd froyo modem
-odin'd cwm_recovery_test4_adryn.tar
-went to recovery mode and fakeflashed update.zip(cwm)
-wiped data/cache/dalvik cache
-flashed froyo rom/kernel zip file
-wiped data/cache/dalvik cache again
and out of nowhere it all worked again. hmm....again most of these steps weren't necessary but i like to start out from scratch sometimes(bad habit)
thanks guys, all I had to do was use adrynalynes .tar in stead of imnuts. and it worked fine.
Can someone post the dl17 Odin files? All of the links I've found so far are dead.
Sent from my HTC Sensation 4G using XDA Premium App
small warning
I just wanted to put out a small warning to those trying to update to ec03: Do NOT use the yellow version of CWM to attempt a data wipe/factory reset before OR after installing ec03. It will hang on formatting /data and cause all sorts of headaches.
If you ARE stuck at formatting /data already and just found this forum:
hold vol up+down+power for about 3-5 seconds to reboot
get back into yellow CWM
ensure the usb is plugged in and go to storage and mounts
mount the USB storage
copy the cyan CWM update.zip from your computer.
install the update.zip (replacing the yellow cwm's update.zip)
hold vol up+down+power for about 3-5 seconds to reboot
voila, cyan cwm!
continue to do a data wipe/factory reset from inside cwm, ignore the error msgs since the actual sucess messages get hidden by the cwm menu when format is complete.
then reboot & enjoy ec03 froyo
Hello to everyone, well i was new to the whole rooting and flashing roms thing, but i did it anyways and it seemed to work just fine , i will explain everything that i did:
i rooted my my touch 4g using the gfree method , and it worked then i flashed the rom royal ginger 3 and it booted just fine , then i just decided to turn off my phone and when i rebooted it it got stuck on the boot loop that i mention, i tried going back to recovery erase all data and re-installing royal ginger but it wont let me erase a thing not data not cache data, nor install the rom, its says the following:
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
and it goes on like that on the bottom of the recovery page
i would really appreciate the help as i am very frustrated
for all of your time and help thank you very much!!!
your phone might either be dead or you have on chance to save it. hapened to mine yesterday the same thing and now doesnt turn on and i already called tmobile for a replacement. Search on how to get the pd15img on there using hboot if you have it if not your phones dead and theres nothing you can do
Look at Glacier Wiki, section "Troubleshooting". Link in my signature.
You might have to use the driver and push the ROM threw command propt
Did you check your eMMC before rooting?
Sent from my HTC myTouch 4G using xda premium
sounds like eMMC failure
I agree, I have the bad one too but its worked fine for the past few months..
Sent from my HTC myTouch 4G using xda premium
Does it read your phone if you plug it in is your adb set up
Sent from my GT-I9000 using XDA App
sounds like its dead or a bad root. once you get it back running i would unroot and use the visionary method to root and flash using the clockwork.
if u made a stock backup like all threads strongly recommend before u flash a new rom, then just boot into recovery and install your stock backup. You do not need to wipe anything when u restore a backup. If u were attentive enough to make a stock backup then restore it and Then start over by unrooting and rerooting
pinguo777 said:
if u made a stock backup like all threads strongly recommend before u flash a new rom, then just boot into recovery and install your stock backup. You do not need to wipe anything when u restore a backup. If u were attentive enough to make a stock backup then restore it and Then start over by unrooting and rerooting
Click to expand...
Click to collapse
He said - "it (recovery) wont let me erase a thing not data not cache data, nor install the rom". It also won't let him restore any backups.
Please read the OP carefully before replying.
Your emmc chip fried,I had the same issue. Try to use adb to push the stock recovery, then go to Tmobile an get it replaced.
If I helped, give thanks, if you please.
........Death before dishonor........
Jack_R1 said:
He said - "it (recovery) wont let me erase a thing not data not cache data, nor install the rom". It also won't let him restore any backups.
Please read the OP carefully before replying.
Click to expand...
Click to collapse
The op says nothing about not being able to restore a backup. When it says ” I tried to reinstall the rom” it sounded like he was trying to reinstall the zip file that booted once and then went kaput. I was only offering an option to get the fone working again. I've rooted over 100 mt4g's and ran into this issue myself and was trying to help out with what worked for me.
pinguo777 said:
The op says nothing about not being able to restore a backup. When it says ” I tried to reinstall the rom” it sounded like he was trying to reinstall the zip file that booted once and then went kaput. I was only offering an option to get the fone working again. I've rooted over 100 mt4g's and ran into this issue myself and was trying to help out with what worked for me.
Click to expand...
Click to collapse
hey, i'm not sure if you just can't read or you're blind or something... but the OP clear states
i tried going back to recovery erase all data and re-installing royal ginger but it wont let me erase a thing not data not cache data, nor install the rom, its says the following:
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
and it goes on like that on the bottom of the recovery page
Click to expand...
Click to collapse
if he can't even erase anything, then he won't be able to install anything either.
Mr. Highway is right, your phone's eMMC chip probably died, like my old one did.
bord1er said:
Does it read your phone if you plug it in is your adb set up
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
no it does not and my emmc-samsung says 2151 mb 4407295sectors
I'm stuck in Recovery, because my device can't boot. I installed Chainfire (stupid me) and didn't read the description. I want to delete it, but when I'm trying to mount sdcard nothing is happening. I have Windows 7 64bit and ClockworkMod Recovey v.6.0.1.0.
Is it(sdcard mounting) possible in cwm recovery's current build? Haven't tried it myself.
Anyway, if you can't boot now and all else fails, just reinstall the JB stock image. Use a tool like the one in dev section(sticky).
Tapatalked from my N7
Sure, but I would like to save my data and apps cache files. That's the problem.
I already deleted the chainfire3d apk in data/data and data/app through adb. Still it's not turning on.
Mounting SDcard is not possible when I tried it on both version CWM 6 and 5
ben805 said:
Mounting SDcard is not possible when I tried it on both version CWM 6 and 5
Click to expand...
Click to collapse
Which is why I use TWRP
Sent from my Nexus 7 using XDA Premium HD app
---------- Post added at 04:35 PM ---------- Previous post was at 04:32 PM ----------
huiggi said:
I'm stuck in Recovery, because my device can't boot. I installed Chainfire (stupid me) and didn't read the description. I want to delete it, but when I'm trying to mount sdcard nothing is happening. I have Windows 7 64bit and ClockworkMod Recovey v.6.0.1.0.
Click to expand...
Click to collapse
Samething happen to me, fortunately for me I was able to bring mine back to Walmart for a new one. Next time use TWRP recovery, it allows mounting of SD cards.
Sent from my Nexus 7 using XDA Premium HD app
al you need to do is reflash your rom to boot up. you wont lose any data.
So I installed TWRP, but still when I'm mounting USB storage nothing is happening on PC, but I can click "unmount" on Nexus.
@UP: Reflash to boot up? What do you mean? Flash it just again?
huiggi said:
So I installed TWRP, but still when I'm mounting USB storage nothing is happening on PC, but I can click "unmount" on Nexus.
@UP: Reflash to boot up? What do you mean? Flash it just again?
Click to expand...
Click to collapse
flash whatever rom that you were using when this happened. itll overwrite the chainfire mod, and you wont lose any data.
But I can't mount USB Storage to copy that rom, the log in TWRP says:
E:Unable to locate volume information.
E:Unable to open ums lunfile '/sys/devices/platform/usb_mass_storage/lun0/file':
E:Unable to locate volume information.
E:Unable to open ums lunfile '/sys/devices/platform/usb_mass_storage/lun0/file':
E:Unable to locate volume information.
Click to expand...
Click to collapse