Im sorry for shouting guys but i really need help with this.
I just got my G2 a Few Days ago and i Rooted it and i was running Cyanogen 7 (nightly). I was using it normally and then it just started to freeze.. so i yanked out the battery and it would just stay frozen in the HTC screen. i can still access the recovery through Fastboot but when i go into recovery it tells me
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
I'm Pretty sure this has something to do with it.
If anyone can help me PLEASE do! I'm Willing to pay
Did you make a nandroid backup before flashing cyanogenmod 7?
My G2 running GingerVillin 1.5
Mine has said that too, dont mind it unless it actually throws an error while your doing something. And try reflashing cm7, make sure you have cwm 3.x
murdah204 said:
Im sorry for shouting guys but i really need help with this.
I just got my G2 a Few Days ago and i Rooted it and i was running Cyanogen 7 (nightly). I was using it normally and then it just started to freeze.. so i yanked out the battery and it would just stay frozen in the HTC screen. i can still access the recovery through Fastboot but when i go into recovery it tells me
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
I'm Pretty sure this has something to do with it.
If anyone can help me PLEASE do! I'm Willing to pay
Click to expand...
Click to collapse
I think that you have a problem with your sd card. See if it is seated correctly.
Utorrent76 said:
Did you make a nandroid backup before flashing cyanogenmod 7?
My G2 running GingerVillin 1.5
Click to expand...
Click to collapse
Yes i did but its a CM 6.1.1 Backup
EdKeys said:
I think that you have a problem with your sd card. See if it is seated correctly.
Click to expand...
Click to collapse
I've already checked it multiple times and nothing
Powers88 said:
Mine has said that too, dont mind it unless it actually throws an error while your doing something. And try reflashing cm7, make sure you have cwm 3.x
Click to expand...
Click to collapse
It has thrown errors at me
its wont mount the System,boot,or cache
did you try reflashing recovery???
fastboot flash recovery recovery.img
flash a 2.x clockwork recovery and flash a froyo rom....
I just stared this thread http://forum.xda-developers.com/showthread.php?t=1023657 before finding this one. My problem sounds identical. Same symptoms - the freeze, the lack of booting, the errors - all the same.
Did you make any progress?
One last desperate bump
can't you access the phone's shell by using ADB?
SnowOokami said:
can't you access the phone's shell by using ADB?
Click to expand...
Click to collapse
I'm having the same issue as bonstio and murdah.
I don't think you can access adb shell because you can't accept superuser requests without access to the ROM.
I'm having the same symptons here. And when I try to flash another rom it aborts it. I recently redownload ROM manager, I don't know if that's the cause or not
Same problem mt4g here. Recovery doesn't work, it gives a fail error. I've tried fastboot commands they work, but don't fix the problem. adb commands do not work.
Well... whenever I got stuck in a bootloop (stuck at HTC screen) when I messed something up in the system, I could still use adb to enter the phone's shell. Pull out the battery, put it back in, hook the phone to the computer and power it on, adb should (not sure it will..) recognize it. If you can't modify the system, remount it.
Maybe another solution is to flash PC10IMG.zip again using fastboot?
SnowOokami said:
Well... whenever I got stuck in a bootloop (stuck at HTC screen) when I messed something up in the system, I could still use adb to enter the phone's shell. Pull out the battery, put it back in, hook the phone to the computer and power it on, adb should (not sure it will..) recognize it. If you can't modify the system, remount it.
Maybe another solution is to flash PC10IMG.zip again using fastboot?
Click to expand...
Click to collapse
I think he should be able to use the PC10IMG way if he used the gfree method I believe.( could be wrong) and if you used unforgivens method you would have to hex edit something to be able to return to stock or you will get a simi brick.
Sent from my Vision using XDA Premium App
Hi Last weekend i had the same issues used a tool i used a lot with my desire and it worked to get recovery installed on the desire z you need to be S-Off to use it so check this first it saved my new desire Z !!!!!
http://forum.xda-developers.com/showthread.php?t=794638
ClockworkMod still works (3.0.0.5) and I can still adb to the phone. Confirmed S-OFF. HBOOT -0.85.0005
Even though CMW is still OK I tried to reflash since it is moaning about recovery From adb shell:
/sdcard # flash_image recovery recovery-clockwork-3.0.0.5-passion.img
flash_image recovery recovery-clockwork-3.0.0.5-passion.img
Can't read device: "/dev/block/mmcblk0"
Error in reading mbr!
failed with error: -1
I'd be happy to try the PC10IMG.zip approach if you can be more specific.
Contents of /proc/mounts in case it helps:
/sdcard # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p27 /cache ext3 rw,nodev,noatime,nodiratime,errors=continue,da
ta=writeback 0 0
/dev/block/mmcblk1p1 /sdcard vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=
0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
It gets more sinister.
Following this thread http://forum.cyanogenmod.com/topic/15623-how-to-fix-a-semi-bricked-g2/ I tried to reflash PC10IMG.zip.
Blah blah continue with update? YES.
Then I see:
Parsing... [SD ZIP]
[1] BOOTLADER - Fail-PU
...
Partition update fail!
Update fail!
//cries
That's.... ouch at least you can still access the phone from the outside, not sure how to fix that issue though, you can't simply enter rm -r *
Check the development forums? maybe there's a solution there or someone who could help you.
Yay I fixed it. I returned to stock firmware using PC10IMG and reflashed recovery
Related
http://psfreedom.com/wiki/index.php?title=OpenDesire4.0.4
http://www.ps3hax.net/showthread.php?p=123003
Im trying to install this recovery so i can jailbreak my PS3, but when i try to use unrEVOked, it hangs while pushing the recovery
When i try to use adb on both my phone and my computer it says i have no space!
what should i do?
EDIT:
fastboot erase recovery
fastboot flash recovery recovery.img
sounds like it would work, bu t i dont want to risk that lol
The no space error will happen if you don't mount system as writable. By default it is set as read only.
Read around to lookup the command to remount system as writable. The command varies depending on your device.
For the motorola droid I used the following:
mount -o remount,rw -t yaffs2 /dev/blockmtdblock4 /system
I think the G1 and other HTC phones use mtdblock3 instead of mtdblock4, but I'm not sure.
SwordOfWar said:
The no space error will happen if you don't mount system as writable. By default it is set as read only.
Read around to lookup the command to remount system as writable. The command varies depending on your device.
For the motorola droid I used the following:
mount -o remount,rw -t yaffs2 /dev/blockmtdblock4 /system
I think the G1 and other HTC phones use mtdblock3 instead of mtdblock4, but I'm not sure.
Click to expand...
Click to collapse
Alright, thats good to know. Ill look around
http://forum.xda-developers.com/showthread.php?t=770663
"You can only write to system on the desire via adb from recovery."
So i do what? boot into recovery, plug in my phone and adb it again?
flash_image recovery image.img?
Hmm, guess not.
I booted into recovery. Plugged my phone in and did an adb devices. It said one device called recovery
i did mount /sdcard (apparently i dont have to mount it to a location)
i cd'd into thte sdcard and did a flash_image recovery psfMod.img and it said i had no space
I was also looking at this
http://forum.xda-developers.com/showthread.php?t=770663
but i still cant get it to work.
do i have to have s-off?
ok this is anoying know
keep getting this error
E: cant mount /dev/block/mmcblk0p1 ( or /dev/block/mmcblk0) (no such file or directory) E:cant mount /sdcard
i flashed coolexe sense 3.0 before that i made a back up of rcmix 2.0
had a play with coolexe sense 3.0 went into ra recovery and went to wipe everythink before restoring my backup
and got this error
E: cant mount /dev/block/mmcblk0p1 ( or /dev/block/mmcblk0) (no such file or directory) E:cant mount /sdcard
ive tryed looking for a answer but not getting any where
any one with some knowlegde i not sure but i think its a fastboot command but i cant find it any where
daddyspud said:
ok this is anoying know
keep getting this error
E: cant mount /dev/block/mmcblk0p1 ( or /dev/block/mmcblk0) (no such file or directory) E:cant mount /sdcard
i flashed coolexe sense 3.0 before that i made a back up of rcmix 2.0
had a play with coolexe sense 3.0 went into ra recovery and went to wipe everythink before restoring my backup
and got this error
E: cant mount /dev/block/mmcblk0p1 ( or /dev/block/mmcblk0) (no such file or directory) E:cant mount /sdcard
ive tryed looking for a answer but not getting any where
any one with some knowlegde i not sure but i think its a fastboot command but i cant find it any where
Click to expand...
Click to collapse
maybe this thread could help you, click here, as i think that is what's happened.
nope i seen that but that not wat im looking for ziggy a buddy mentioned somethink about a command threw fastboot but he not online and was hoping some one else of might known it
Is there a video that says "I'm a noob @ XDA"?!
hope you fix it soon.
The commands you're looking for are:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
Should fix the USB brick. If it doesn't, PM me.
jordan.harris01 said:
The commands you're looking for are:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
Should fix the USB brick. If it doesn't, PM me.
Click to expand...
Click to collapse
thanks sorted ur a star all done thank **** lol
jordan.harris01 said:
The commands you're looking for are:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
Should fix the USB brick. If it doesn't, PM me.
Click to expand...
Click to collapse
I would like to thank you so much my friend for these commands. I just fixed my desire also.
jordan.harris01 said:
The commands you're looking for are:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
Should fix the USB brick. If it doesn't, PM me.
Click to expand...
Click to collapse
gonna tattoo this commands in my fore-arm
lifesaver!
seriously thought i bricked my desire
I've got the same problem on motorola dext..what commands to use there ?
Try to enable bluetooth
Sent from my HTC Desire using XDA App
already tryed all this small tricks i need something serious to solve my problem.
Hi all,
Help needed,
I ran into a problem with my Droid Incredible after power up it hangs at the HTC Incredible splash screen. This started after accepting updates for 4 apps and installing Google+. I thought everything finished ok afterwards but found it powered down an hour later.
I tried a number of suggestions that matched what others have seen that looked identical to this but still no joy.
Current status
**** LOCKED (OOW) ****
INCREDIBLEC XD SHIP S-off
HBOOT-1.02.0000
MICROP-0417
Touch Panel-almelc03_16ac
Radio-2.15.10.07.07
Dec 21 2011,23:37:16
When I go to recovery I get the ClockworkMod Recovery v5.0.2.0 Blue menu.
After this menu I get the following errors:
ClockworkMod Recovery v5.0.2.0
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
When I go to mounts and storage and try and mount /cache I get:
Error mounting /cache!
The only file system I can mount is /system
When I go to command prompt using adb shell
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mtdblock3 on /system type yaffs2 (rw,nodev,noatime,nodiratime)
cat fstab
/dev/block/mmcblk0p2 /cache auto rw
/dev/block/mmcblk0p1 /data auto rw
/dev/block/mmcblk0p1 /datadata yaffs2 rw
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mmcblk1p1 /sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext auto rw
I feel something is not right with the file system that is keeping the system from booting up correctly.
I need some guidance from someone that has experience with these kinds of systems. I did load some updates to Radio & HBOOT as others have done when they reported these errors, The only difference being my attempt did not result in a fix. I really miss my phone running cyanogenmod 7. Is there a way to start from scratch to get CM7 running again?
freddymac said:
Hi all,
Help needed,
I ran into a problem with my Droid Incredible after power up it hangs at the HTC Incredible splash screen. This started after accepting updates for 4 apps and installing Google+. I thought everything finished ok afterwards but found it powered down an hour later.
I tried a number of suggestions that matched what others have seen that looked identical to this but still no joy.
Current status
**** LOCKED (OOW) ****
INCREDIBLEC XD SHIP S-off
HBOOT-1.02.0000
MICROP-0417
Touch Panel-almelc03_16ac
Radio-2.15.10.07.07
Dec 21 2011,23:37:16
When I go to recovery I get the ClockworkMod Recovery v5.0.2.0 Blue menu.
After this menu I get the following errors:
ClockworkMod Recovery v5.0.2.0
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
When I go to mounts and storage and try and mount /cache I get:
Error mounting /cache!
The only file system I can mount is /system
When I go to command prompt using adb shell
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mtdblock3 on /system type yaffs2 (rw,nodev,noatime,nodiratime)
cat fstab
/dev/block/mmcblk0p2 /cache auto rw
/dev/block/mmcblk0p1 /data auto rw
/dev/block/mmcblk0p1 /datadata yaffs2 rw
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mmcblk1p1 /sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext auto rw
I feel something is not right with the file system that is keeping the system from booting up correctly.
I need some guidance from someone that has experience with these kinds of systems. I did load some updates to Radio & HBOOT as others have done when they reported these errors, The only difference being my attempt did not result in a fix. I really miss my phone running cyanogenmod 7. Is there a way to start from scratch to get CM7 running again?
Click to expand...
Click to collapse
Have you tried reflashing cwm? Also i noticed your info says locked oow but s-off, im not sure but mabey the bootloader being locked is causing the issue, but it shouldnt since your true s-off.
same issue
So I am also getting the
E:Can't mount /cache/recovery/command
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
Chain of events: I dropped the phone from standing, phone was on clip. It worked until i decided to download an app from Amazon App Store. I started getting Bootloops....then I couldn't do anything except open the recovery via CWM Recovery 5.0.2.0....
I have tried multiple things to recover back to normal....but its not working ....
CDSmythe said:
So I am also getting the
E:Can't mount /cache/recovery/command
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
Chain of events: I dropped the phone from standing, phone was on clip. It worked until i decided to download an app from Amazon App Store. I started getting Bootloops....then I couldn't do anything except open the recovery via CWM Recovery 5.0.2.0....
I have tried multiple things to recover back to normal....but its not working ....
Click to expand...
Click to collapse
Are you also on hboot 1.02 and is it locked oow? If so go to htcdev site and unlock your bootloader.
Im enjoying similar issues. Have tried everything. Every ruu i could find, countless pb31imgs, every different recovery, nandroid restores from anothe inc i own. (shocked when ics booted, though it was shut down quick) even tried parted recovery. Led to mmcblk0 doesnt exist(?). Any help with this would be great. Starting to think this a lost cause.
Sent from my SPH-D710 using xda premium
did any one figure out how to solve this issue yet. been stuck for 3 wks.
Mine turned out to be a lost cause
Followed this guide:
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
when trying to use parted command
mmcblk0 did not exist, used fdisk command and it returned with I/O error which appears to be a hardware failure.
So last night i finally decided to install JetiX20. Installation ran smoothly until reboot.
hmm ... stuck on Samsung galaxy note 2 logo for over 45 mins.
Reboot into clockworkMod recovery v6.0.4.3
Code:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Cant open /cache/recovery/last_log
So.. i tried to wipe data/factory reset and cache partition....
Code:
--wiping data--
formatting /data...
error mounting /data!
skipping format...
formatting /cache...
E: format_volume:make_extf4fs failed on /dev/block/mmcblk0p12
formatting /sd-ext...
formatting /sdcard/.android_secure...
E: unknown volume "/sdcard/.android_secure"
data wipe complete
So, now i move to adb:
[email protected]:~$ adb devices
List of devices attached
42f7410e7bc79f3f recovery
Code:
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 67.1 GB, 67108864000 bytes
4 heads, 16 sectors/track, 2048000 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 2048000 65535992 83 Linux
~ #
Code:
# mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
Some how i manage to corrupt my mobile's partition?
I tried Odin, Heimdall, fastboot and adb as per recommended on the forum.
Is there anything else i could try?
Thanks for any advices.
You should re-flash the stock ROM of Samsung Galaxy Note 2 through ODIN.
I did, still getting the very same error.
May need to fix partitions by flashing a PIT file...
Zen Arcade has a pit thread in the development section...
Read EVERYTHING before flashing a PIT....g
gregsarg said:
May need to fix partitions by flashing a PIT file...
Zen Arcade has a pit thread in the development section...
Read EVERYTHING before flashing a PIT....g
Click to expand...
Click to collapse
I sure will read up on it. thanks
http://forum.xda-developers.com/showthread.php?t=2609871
There they are...
Again....I cannot stress enough the importance of reading every word Zen posted on the subject...
And remember....the PIT may not be your issue....so evaluate carefully...
I bid you good luck....g
Hello again
So sadly I'm still having the same issue, looks like everything install/runs ok but at reboot the phone still at bootloop when I try to pull the logs from the device all I get is can't mount mmcblk0p12.
Are you getting a "cannot mount sd card " in that error message ??
That error would indicate a failed partition on the emmc..
This is not looking good.....g
No just can't mount/open /cache/recovery.
But on wipe data/factory reset one of the lines say "E: unknown volume "/sdcard/.android_secure".
I can't find anything else that will give me that error.
Okay ...please post the link to the stock rom you are trying to flash....and also tell us what bootloader version you have..g
gregsarg said:
Okay ...please post the link to the stock rom you are trying to flash....and also tell us what bootloader version you have..g
Click to expand...
Click to collapse
Hi greg, this is the link http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189 and i am pretty sure NE5.
at first i though it was the actual external sd card, but then after some more careful reading, mmcblk0p12 is a partition of my internal storage correct?
Yep....emmc
And if those permanent partitions are whacked ....then it's bye bye phone....
No PIT will fix the emmc...it would be a chip replacement or new phone..
The emmc is essentially the boot sector of the device...g
gregsarg said:
Yep....emmc
And if those permanent partitions are whacked ....then it's bye bye phone....
No PIT will fix the emmc...it would be a chip replacement or new phone..
The emmc is essentially the boot sector of the device...g
Click to expand...
Click to collapse
Well thats a shame is there another way to verify the status of the emmc or this is pretty much it?is just strange how i try to install the JediX20 rom before and installed ok still boot, i would figure it will give errors installing and hang.
Oh well... ill try a few more times before i decide to move onto hardware
thanks greg.
Hello again everyone
So doing some more reading last night about my issue and found this:
****@****:~$ adb shell cat /sys/block/mmcblk0/device/manfid
0x000000
Will this confirm the issue to be with the chip?
thanks. \m/
One last attempt here...
Format your external SD CARD to FAT32 on a PC....then reload it into the device and reflash your rom....g
Omg Greg I was just about to do that lmao. Thanks working on it
While this is formatting I have a question. I just noticed that I can only see mmcblk0 when the external card is in. Why would that be?
Thanks.
I hope this doesn't come up twice. External SD formatted to fat32... Try installing ucune5.. Odin said it pass but still stuck on logo after reboot
Chamo709 said:
While this is formatting I have a question. I just noticed that I can only see mmcblk0 when the external card is in. Why would that be?
Thanks.
Click to expand...
Click to collapse
Because your device is trying to mount the storage block....and the mmcblk0 is the address...
I'm hoping it's an external error and not internal...because the emmc will give similar errors....g
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
Chamo709 said:
I hope this doesn't come up twice. External SD formatted to fat32... Try installing ucune5.. Odin said it pass but still stuck on logo after reboot
Click to expand...
Click to collapse
Wipe data....factory reset in recovery...g
Ok... So no bueno still getting the same exact error ... What a shame really. I guess next step is getting a new board?
I have a family member's phone (N7100) that was stuck on a bootloop. This phone was never rooted or had any custom recoveries or roms installed on it. When I go into recovery I see that I'm getting the common "e:failed to mount /efs(invalid argument)". When trying to google the problem I found that common fix for it:
Code:
adb shell
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3 /efs
So I go ahead and do this but I notice that even though the phone is out of a bootloop and goes into factory mode (I already know how to get out of it), it doesn't connect to the phone network. Going back to recovery I see that EFI is still not able to be mounted but the error is different "failed to mount /efs Operation not supported on transport endpoint".
I can tell that if I ADB into the phone and do "mount -w -t ext4 /dev/block/mmcblk0p3 /efs" it will mount just fine. Anybody knows what is happening? To make everything worse he doesn't have a EFI backup so at this point I'm thinking the phone is dead no matter what. Suggestions?
Thanks
Try flashing stock ROM.
Skull97 said:
Try flashing stock ROM.
Click to expand...
Click to collapse
I already did and it didn't help. Googling the problem doesn't seem to give me any results for that particular error line.
Bump! I hate to do this but I think this is my last chance to fix it. Google is not giving me any good leads for me to latch on.