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?
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
So i'm a noobie. I mean i have some experience (rooted and installed many ROMS like my Nexus One device, i know, ancient) but i got all that information and knowledge on here! So my mom is using this HTC ONE X that she just received and i want to be nice and root it and remove all the bloatware on it and what not. After so many struggles of unlocking the bootloader and all things that fall under rooting the device i was able to FINALLY gain root permission but for some reason i couldn't permanently delete the apps on there like i have in the past with other phones. So, i decided to try flashing a ROM. So i Google'd, YouTube'd and tried to come across the best one i could find. Found a Lollipop Rom somewhere (probably made a mistake on which phone it was for), followed the instructions but didn't backup anything (i know, i know, noob move #1) but it would get stuck on then HTC Quietly Briliant screen (oh and before that, i had a HUGE amount of trouble with the phone using ADB and it being recognized, flashing recoveries and booting into them, it was just a hassle!). I also flashed Clockworkmod at one poit to try and fix things but i was able to get back on TWRP V2.5.0 (tried a higher version but it did not work) so now my phone connects easily to my pc and i pretty much know how to use adb fastboot commands and get into recovery and sideload ROMs but, after many, many attempts at trying to install different ROMs, none work. It'll either stay on the HTC Quietly Briliant screen or won't install and i'll get a message in ADB Sideload:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: No file_contexts
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
script succeeded: result was [0.200000]
Updating partitio details...
E:Unable to mount '/cache'
Formatting Cache using mke2fs...
Done .
Updating partition details...
Wiping Dalvik and Cache Directories....
--Dalvik Cache Directories Wipe Complete!
Also, came across this on a different site:
Here's the solution.
The problem was that I managed to screw up the partitions on my internal storage card, so basically nothing would work properly. I could still get into recovery, though. That's key.
Here's what you'll need:
1 Working recovery, basic knowledge of adb & the shell
2 Parted (download here)
3 stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Click to expand...
Click to collapse
So i thought this may be my problem but then as i get to the parted /dev/block/mmcblk0 mkfs ext2 part of the steps I get stuck because it says something like i can't overlap partitions?
So here i am, desperate for help, trying to fix my mothers phone. Sorry, if i'm not clear enough, i tried my best to recall everything i did (kind of hard after hours and hours of trying multiple things for multiple problems) and all that i've come across without being too specific on things that may not matter (hopefully?). So can anyone help? Please, guide me!
babymatrix said:
So i'm a noobie. I mean i have some experience (rooted and installed many ROMS like my Nexus One device, i know, ancient) but i got all that information and knowledge on here! So my mom is using this HTC ONE X that she just received and i want to be nice and root it and remove all the bloatware on it and what not. After so many struggles of unlocking the bootloader and all things that fall under rooting the device i was able to FINALLY gain root permission but for some reason i couldn't permanently delete the apps on there like i have in the past with other phones. So, i decided to try flashing a ROM. So i Google'd, YouTube'd and tried to come across the best one i could find. Found a Lollipop Rom somewhere (probably made a mistake on which phone it was for), followed the instructions but didn't backup anything (i know, i know, noob move #1) but it would get stuck on then HTC Quietly Briliant screen (oh and before that, i had a HUGE amount of trouble with the phone using ADB and it being recognized, flashing recoveries and booting into them, it was just a hassle!). I also flashed Clockworkmod at one poit to try and fix things but i was able to get back on TWRP V2.5.0 (tried a higher version but it did not work) so now my phone connects easily to my pc and i pretty much know how to use adb fastboot commands and get into recovery and sideload ROMs but, after many, many attempts at trying to install different ROMs, none work. It'll either stay on the HTC Quietly Briliant screen or won't install and i'll get a message in ADB Sideload:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: No file_contexts
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
script succeeded: result was [0.200000]
Updating partitio details...
E:Unable to mount '/cache'
Formatting Cache using mke2fs...
Done .
Updating partition details...
Wiping Dalvik and Cache Directories....
--Dalvik Cache Directories Wipe Complete!
Also, came across this on a different site:
So i thought this may be my problem but then as i get to the parted /dev/block/mmcblk0 mkfs ext2 part of the steps I get stuck because it says something like i can't overlap partitions?
So here i am, desperate for help, trying to fix my mothers phone. Sorry, if i'm not clear enough, i tried my best to recall everything i did (kind of hard after hours and hours of trying multiple things for multiple problems) and all that i've come across without being too specific on things that may not matter (hopefully?). So can anyone help? Please, guide me!
Click to expand...
Click to collapse
When you install some rom are you flash the boot.img with the command fastboot flash boot boot.img where the boot.img is taken from rom archive where you install and puted in your fastboot folder
Thant said:
When you install some rom are you flash the boot.img with the command fastboot flash boot boot.img where the boot.img is taken from rom archive where you install and puted in your fastboot folder
Click to expand...
Click to collapse
Initially on the first rom i remember doing so (still didn't work), but after that i did fail to do it for the other roms.
babymatrix said:
So i'm a noobie. I mean i have some experience (rooted and installed many ROMS like my Nexus One device, i know, ancient) but i got all that information and knowledge on here! So my mom is using this HTC ONE X that she just received and i want to be nice and root it and remove all the bloatware on it and what not. After so many struggles of unlocking the bootloader and all things that fall under rooting the device i was able to FINALLY gain root permission but for some reason i couldn't permanently delete the apps on there like i have in the past with other phones. So, i decided to try flashing a ROM. So i Google'd, YouTube'd and tried to come across the best one i could find. Found a Lollipop Rom somewhere (probably made a mistake on which phone it was for), followed the instructions but didn't backup anything (i know, i know, noob move #1) but it would get stuck on then HTC Quietly Briliant screen (oh and before that, i had a HUGE amount of trouble with the phone using ADB and it being recognized, flashing recoveries and booting into them, it was just a hassle!). I also flashed Clockworkmod at one poit to try and fix things but i was able to get back on TWRP V2.5.0 (tried a higher version but it did not work) so now my phone connects easily to my pc and i pretty much know how to use adb fastboot commands and get into recovery and sideload ROMs but, after many, many attempts at trying to install different ROMs, none work. It'll either stay on the HTC Quietly Briliant screen or won't install and i'll get a message in ADB Sideload:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: No file_contexts
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
script succeeded: result was [0.200000]
Updating partitio details...
E:Unable to mount '/cache'
Formatting Cache using mke2fs...
Done .
Updating partition details...
Wiping Dalvik and Cache Directories....
--Dalvik Cache Directories Wipe Complete!
Also, came across this on a different site:
So i thought this may be my problem but then as i get to the parted /dev/block/mmcblk0 mkfs ext2 part of the steps I get stuck because it says something like i can't overlap partitions?
So here i am, desperate for help, trying to fix my mothers phone. Sorry, if i'm not clear enough, i tried my best to recall everything i did (kind of hard after hours and hours of trying multiple things for multiple problems) and all that i've come across without being too specific on things that may not matter (hopefully?). So can anyone help? Please, guide me!
Click to expand...
Click to collapse
hello babymatrix, i'm wondering if you were able to solve or find a solution to your issue. The reason i'm asking is because i'm on the same boat right now and looking for way to fix a similar issue as yours.
basically, i got a phone with a broken partition like yours. I can still go to recovery but you'll see this message and cannot mount system. I also cannot go into fastboot mode (it hangs when i do a power+vol down)
E: failed to mount block devices /dev/block/mmcblk1p1
E: remount block devices /dev/block/mmcblk1
E: failed to mount /sdcard (No such file or directory)
From searching the net, i figured there's something wrong with the partitioning of the phone. I managed to do adb shell and i could see there's a folder sdcard.
nway, if you've managed to find a solution for your issues, i hope if you could share. thanks.
So last night, my kindle was working normally with my self-compiled CM13 build (7/1/16 version), 7/16/16 opengapps, and other miscellaneous tweaks I use to refine my experience. Anyway, I was using my device normally and set it down to charge earlier. When I came back to it, I noticed it was booting CM. A few minutes later, I see that it's rebuilding cache for all the (system?) apps. I check back in a little bit later, and it reboots again. Suspecting an issue, I typed fastboot -i 0x1949 erase cache to try to erase the cache, and it doesn't work. The terminal window just hangs until I unplug the device. I tried rebooting into TWRP before doing the cache wipe, and it ends up not fully booting into TWRP. After that /cache wipe command fails, I suspect that my /sdcard or /data partitions are full somehow, so I kick the device into TWRP via fastboot -i 0x1949 oem recovery. TWRP boots that time, but asks if it can remount /system as R/W, so something's amiss. I plug the kindle into my Ubuntu machine, and I don't see any files or anything. I don't even see the "Internal storage" icon that usually shows up. I find it really baffling. I try to browse /sdcard from TWRP's file manager, and nothing shows up there either. I check the TWRP log, and it says "Failed to mount '/data' (Invalid argument)" and "Unable to recreate /data/media folder." For /cache, it says "Failed to mount '/cache' (Invalid argument)". Note that I didn't flash anything or otherwise modify the device leading up to this. I checked the battery via TWRP, and I have a decent level of around 48%. The kindle's 3 years old (got it in 2013 as a birthday present, so I know it's at least 3). Any ideas, or is this the last leg for my 8.9"?
I just wanted to post a couple updates. First off, I wiped /cache in TWRP by switching it over to ext4 from f2fs (both /data and /cache were f2fs-formatted), and that resolved the "failed to mount /cache" issue. I later did a raw backup of the data partition, tried to mount it, and couldn't. I ran fsck.f2fs on it, and it said it couldn't find a valid F2FS superblock at 0x0 or 0x1. I figured the partitions both corrupted, which makes sense considering that cache and data were both formatted under f2fs, and they were the only partitions affected. I did some research, and I discovered that f2fs can indeed go ballistic. I reformatted the data partition as ext4 as well, and now CM's working again.
The moral of the story: backup early and often.
When I boot my phone I get the message "Device storage corrupt" and it prompts me to reboot into recovery. However TWRP doesnt automatically fix the problem. In TWRP most operations terminate with the message "Unable to mount /data". I cannot wipe /data because it gives me that error.
Is it a problem with the partition table? Should I be trying to flash a PIT file using Heimdal? (I am new to Samsung sorry.) If it is a problem which can be sorted out by manually partitioning, I'm a pretty deft hand with the linux shell and maybe the adb shell isnt too different.
TIA
Oh no ! You have updated your phone to an locked bootloader ! You can't flash now something.
Word to the wise: I was able to fix this problem by reformatting the /data partition. For some reason twrp was not able to do this.
0. Reboot into twrp and if necessary disable MTP in the mount menu.
1. Then I found out the name of the partition block device which holds the /data partition. I found this out by trying to wipe the data partition using TWRP and noting the error message. For me that was mmcblk0p24.
2. Run adb shell mke2fs -T ext4 /dev/block/mmcblk0p24
Problem solved!