OK, so first, My padfone S automatically reboot and stuck on asus logo for a while, then after exhaustively waited , i manually hit power button for 30 second and it reboot but, still stuck on the asus logo. At this time i try to enter the recovery mode and try to wipe cache wipe /cache partition. It gives a bunch of can't mount error line. But still there's one line saying wipe completed. Then i try to wipe everything, and same error can't mount but still wipe completed was shown. At this time i was so stressed i try to follow the recommendation which posted http://forum.xda-developers.com/padfone-x/help/guide-restoring-stock-rom-recovery-t3179818 ..
I skipped to the part where i enter fastboot and open up adb tools to flash TWRP_2.8.7.0 to unlock bootloader. Before this, I try using adb devices command line but, my devices was not shown. So after i flashing TWRP as mentioned, it show exactly what Ninekaw has said, [ It will show that flashing FAILED (remote: can't flash unsigned image), it fact, it was succeeded, ] .. Then when i try to enter the recovery mode as for the next step, It stuck on the Asus logo. Now i can't even enter to recovery mode, my adb tools can't detected my devices. I don't know what to do. Please oh please merciful android race. HELP ME. I'm a noob to this kind of technology.
Oh.. the error command line in recovery mode
and the error command line was,
E: can't mount, change path -dev/lock/emmcblk1
E: can't mount /cache partition
E: can't mount /cache/recovery/log
E: can't mount /cache/recovery/log1
E: can't mount /cache/bootloader
E: can't mount /cache/bootloader1
Seriously?
Seriously guys? no help at all? man, i'm disappointed after all the website i go through mention to go consult in this website.. maybe the community here wasn't as good others pictured it would..
Related
Hi guys,
I'm afraid my emmc is fried. After occasional crashes/freezes/FC's in different apps/Android modules in CM7 over a few months, one day I opened this site in the browser, and the browser FC'ed and then kept FC'ing when opened. When rebooting, the phone gets stuck looping in the CM7 animated start-up logo. When I boot in Clockworkmod (v4.0.1.0) , I get this error:
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
and I can't use Clockworkmod. Cannot mount/wipe cache, cannot install anything. I tried checking the eMMC with ADB and FASTBOOT, but they can't see the device, though Heimdall does see it as I was able to flash recovery.bin again in d/l mode (but without fixing the problem). Please help, I've run out of ideas and have no phone...
bollorr said:
Hi guys,
I'm afraid my emmc is fried. After occasional crashes/freezes/FC's in different apps/Android modules in CM7 over a few months, one day I opened this site in the browser, and the browser FC'ed and then kept FC'ing when opened. When rebooting, the phone gets stuck looping in the CM7 animated start-up logo. When I boot in Clockworkmod (v4.0.1.0) , I get this error:
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
and I can't use Clockworkmod. Cannot mount/wipe cache, cannot install anything. I tried checking the eMMC with ADB and FASTBOOT, but they can't see the device, though Heimdall does see it as I was able to flash recovery.bin again in d/l mode (but without fixing the problem). Please help, I've run out of ideas and have no phone...
Click to expand...
Click to collapse
you need to get into recovery via the power menu...depending on what kernel version your running, three fingering into recovery will cause a bootloop. the same thing applies to all ICS roms. If you can no longer get the phone to boot up then simply odin cwm4 fixed for cm7, three finger into recovery, wipe data, then reflash the rom. Make sure everything is backed up first. More information can be found in section 3 here:
http://forum.xda-developers.com/showthread.php?t=1238070
Thanks for your reply. I explained that the phone doesn't boot up anymore (gets stuck in a loop), and while booting into ClockworkMod works (3 fingers), I get these errors, so even though the up/down/power buttons work (I can scroll through the recovery menus/options), certain things don't work, like wiping the cache (it cannot mount or open the cache) or re-flashing CM7 from SD-card... I get errors.
I've had problems with Odin before (it said it flashed stuff, but stuff didn't work), so I've been using Heimdall for a while instead. Like I said, I was able to successfully re-upload ClockworkMod to the phone (in d/l mode) with Heimdall, but it doesn't fix the problem. The problem seems to be that the cache partition is corrupted, and I can't do much from within ClockworkMod (though it worked without problems in the past).
I've found tips on here (http://forum.xda-developers.com/showthread.php?t=1284196) that the errors I get are sometimes (though not always) because of physical corruption of eMMC. Is it possible to flash CM7 or CM9 using Heimdall or (Heimdall-frontend), are there instructions on this, though I doubt it will work...I'm new to this lol. I want to at least have a working phone, until I can figure out how to fix the cache problem and make Clockworkmod work again. Thanks.
Is it possible to just fix the cache partition or re-partition using a program like Heimdall?
bollorr said:
Hi guys,
I'm afraid my emmc is fried. After occasional crashes/freezes/FC's in different apps/Android modules in CM7 over a few months, one day I opened this site in the browser, and the browser FC'ed and then kept FC'ing when opened. When rebooting, the phone gets stuck looping in the CM7 animated start-up logo. When I boot in Clockworkmod (v4.0.1.0) , I get this error:
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
and I can't use Clockworkmod. Cannot mount/wipe cache, cannot install anything. I tried checking the eMMC with ADB and FASTBOOT, but they can't see the device, though Heimdall does see it as I was able to flash recovery.bin again in d/l mode (but without fixing the problem). Please help, I've run out of ideas and have no phone...
Click to expand...
Click to collapse
i have the exact same problem with my fascinate i would think that if i could get odin to flash a new rom to it it would boot but im not intirely sure
I've found others who have the same problem... in my opinion it's clear that the cache partition got corrupted for some reason, either software (fixable) or hardware (the internal memory/eMMC which then it would need replacement or a new phone lol).
bollorr said:
I've found others who have the same problem... in my opinion it's clear that the cache partition got corrupted for some reason, either software (fixable) or hardware (the internal memory/eMMC which then it would need replacement or a new phone lol).
Click to expand...
Click to collapse
you need to flash back to a stock rom via odin, heimdall, or adb...thats the only way to fix it at this point. if you can get odin to recognize the device try section 5 of my guide.
Thanks. I'll give it a try. Odin doesn't see my device, so I'm using Heimdall Frontend which is a little bit different. Do you have instructions for it? I load atlas.pit, but then in order to load the GB rom (which is .tar.md5), it asks for a BIN file, and I also have to add a partition and it's got a lot of options there. Why doesn't Odin see my device, but Heimdall does?
I got Odin to recognize my device (stupid USB ports), I followed the instructions, phone says downloading, do not turn off target, Odin says the same... it's been more than 5 minutes, the same...does it mean I have a bricked device now?
and I forgot, Odin says in top left corner, SET PARTITION...it's been 15 minutes now, maybe it cannot set the partition
Update...I rebooted the phone into Recovery after 20 mins or so of Odin not being able to flash (set partition)... of course Odin detected it and a big red FAIL appeared in the top left corner, and the bottom log said Re-partition operation failed, so, is there anything else I can try or the memory chip fried?
http://rootzwiki.com/topic/8867-romsch-i500-vzw-ed05-froyo-heimdall-linux-friendly/
Thanks, I tried what you said, and just like I thought, Heimdall (like Odin) gave this error:
Uploading PIT
ERROR: Failed to send file part packet!
PIT upload failed!
Ending session...
ERROR: Failed to send end session packet!
please help, I have no phone
Is Re-Partition checked in Odin? If it is, try unchecking it. If it isn't, try checking it. If it's unchecked, it won't fix the corrupted cache partition, but it should at least let you flash the OS
yes, I tried that in odin, doesn't work
Yikes. You seem to be stuck between a rock and a hard place. Honestly, it seems that the only possible option here is to get a new phone. It seems as though there must be physical damage to the chip, otherwise Odin/Heimdall would have worked.
bollorr said:
Thanks, I tried what you said, and just like I thought, Heimdall (like Odin) gave this error:
Uploading PIT
ERROR: Failed to send file part packet!
PIT upload failed!
Ending session...
ERROR: Failed to send end session packet!
please help, I have no phone
Click to expand...
Click to collapse
your last option is to try adb.
MultipleMonomials said:
Yikes. You seem to be stuck between a rock and a hard place. Honestly, it seems that the only possible option here is to get a new phone. It seems as though there must be physical damage to the chip, otherwise Odin/Heimdall would have worked.
Click to expand...
Click to collapse
that's usually the diagnostic (fried eMMC chip) for these error messages (though not always) and that's what I thought, and I was looking for ways to determine for sure whether the chip is fried or not, as to know what to do and not waste my time and the time of the people on this board...for some reason adb doesn't work, or I don't know how to use it (first time using it)...I type adb devices, I get error, no devices, adb shell, error again
droidstyle,
do you have instructions anywhere on how to use adb, it was one of the first things I tried, but it doesn't see the devices, I cannot start shell (adb shell)...thanks
I made an ADB for Noobs guide about a year ago. It never gained much traction but it should still be current. Anywhere it says CM7, the same goes for CM9.
Was installing the hairybean bootloader, it was on the blue bar loading page, it stopped half way and restarted. It will only boot into TWRP, and it asks for a password. I press the log button and it says:
* Verifying filesystems...
* Verifying partition sizes...
E:Unable to mount '/cache' (tw_mount)
E:Can't open /dev/block/mmcblk0p3
(No such file or directory)
etc...
It will not read my micro sd card, I press install, there are folders but none that I recognize or any that would be of any help
I was planning to sell this tonight -.-
Am I doomed?
I'm sorry for posting this. This was my last resort, I searched everywhere for 4+ hours, and nothing.
Thanks
Edit: I can now boot in apx mode, could I do anything with this?
I also tried the Option 1 on the unbricking thread, in the cmd prompt it says it works but it is the same deal when you turn it back on.
Edit: I can now get into fastboot by typing adb reboot-bootloader fastboot.
Help would be much appreciated!!! Im selling this tomorrow!!!
[email protected]#[email protected][email protected]@[email protected]@@[email protected]!
Followed this - http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Omg.....
I’m using this HTC One from AT&T for almost a year, unlocked and rooted and flashed with the google edition room from day I bought it, and currently on Kitkat 4.4 provided by bigxie on this forum: http://forum.xda-developers.com/showthread.php?t=2341395, using recovery TWRP 2.6.3.3. With the RevOne method, I also get S-OFF (prerequisite for using kitkat 4.4 rom). Yesterday out of blue my phone died with 90% battery. I could get into the bootloader menu and that seems to be the furthest point I could reach. Here is the print out from bootloader:
-------------------------------------------------
*** TAMPERED ***
*** UNLOCKED ***
M7_ul PUT SHIP S-OFF RH
CID-CWS_001
HBOOT-1.44.0000
RADIO-4T.21.3218.21
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 18 2013, 18:29:18:-1
The only working part now is fastboot devices, when I boot the phone and connect it to my pc via usb cable
C:\ minisdk>fastboot devices
HT35MW905396 fastboot
Interestingly, adb command doesn’t work, returning an empty list
C: \minisdk>adb devices
List of devices attached
The following is some failed attempt:
1. Flash the identical TWRP that I have before the crash: openrecovery-twrp-2.6.3.3-m7, downloaded from TWRP site and md5 checked.
C:\ minisdk>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.178s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.327s
2. Erase Cache
C:\minisdk>fastboot oem lock
(bootloader) SD: write failed in CMD25.
(bootloader) [PG_ERROR] htc_pg_part_update(982):
(bootloader) sd_write_sector failed
(bootloader) [PG_ERROR] htc_pg_part_traverse(930):
(bootloader) fn return error
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 2.569s
3. After that, still could list device by fastboot devices, but erase cache returned same error message
C:\minisdk>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 1.412s
4. Reboot OEM RUU
C:\minisdk>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
(bootloader) SD: write failed in CMD25.
OKAY [ 1.069s]
finished. total time: 1.070s
Running out of energy and I might just contact HTC or ATT as the last resort. Any suggestion and comments are very appreciated. Thank you!
When you tried locking the boot loader, did it ever work? You could also try another usb cable, sometimes my fastboot fails with certain ones.
no the relock failed. I tried two different cables, both of which works fine with other devices.
Sent from my Nexus 10 using XDA Free mobile app
xxk said:
no the relock failed. I tried two different cables, both of which works fine with other devices.
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
contact AT&T it sounds like your Motherboard went out
and adb only works in recovery or when the phone is booted to the os
with your old hboot you could try fastboot boot openrecovery-twrp-2.6.3.3-m7.img
and see if you can do a factory reset from their
Thanks a lot! doing: fastboot boot openrecovery-twrp-2.6.3.3-m7.img does bring me to the TWRP screen.
However, from there, when I try to do "Restore", my internal storage is 0 MB. Nothing there.
When I tried "Advanced -> HTC Dumblock -> Restore Original Boot", it seems again the internal disk is totally wiped.
E: unable to find partition size for '/data'
E: unable to find partition size for '/recovery'
E: unable to find partition size for '/data'
Updating partition details...
E: unable to mount '/system'
E: unable to mount '/cache'
E: unable to mount '/cache'
E: unable to mount '/cache'
E: unable to mount '/system'
E: unable to mount '/system'
E: unable to mount '/system'
E: unable to mount '/cache'
E: unable to mount '/cache'
E: unable to mount '/system'
E: unable to mount '/system'
E: unable to mount '/system'
What to do next?
clsA said:
contact AT&T it sounds like your Motherboard went out
and adb only works in recovery or when the phone is booted to the os
with your old hboot you could try fastboot boot openrecovery-twrp-2.6.3.3-m7.img
and see if you can do a factory reset from their
Click to expand...
Click to collapse
xxk said:
Thanks a lot! doing: fastboot boot openrecovery-twrp-2.6.3.3-m7.img does bring me to the TWRP screen.
However, from there, when I try to do "Restore", my internal storage is 0 MB. Nothing there.
When I tried "Advanced -> HTC Dumblock -> Restore Original Boot", it seems again the internal disk is totally wiped.
E: unable to find partition size for '/data'
E: unable to find partition size for '/recovery'
E: unable to find partition size for '/data'
Updating partition details...
E: unable to mount '/system'
E: unable to mount '/cache'
E: unable to mount '/cache'
E: unable to mount '/cache'
E: unable to mount '/system'
E: unable to mount '/system'
E: unable to mount '/system'
E: unable to mount '/cache'
E: unable to mount '/cache'
E: unable to mount '/system'
E: unable to mount '/system'
E: unable to mount '/system'
What to do next?
Click to expand...
Click to collapse
well if you can get into TWRP go to wipe / format data / and Factory Reset
then go to Advanced / ADB Sideload / check the 2 boxes /swipe to sideload
then from your PC sideload your Rom back to the phone and hope it works
put your rom in the same folder as adb / fastboot and from a command prompt
shift+right click / command prompt here
adb sideload name-of-rom.zip
Well, both step failed.
When I do wipe -> format data -> confirm by typing YES, twrp restarted, then I do Factory Reset, the following error occured. Basically, it can't mount internal storage.
E: unable to find partition size for '/boot'
E: unable to find partition size for '/recovery'
E: Primary block device '/dev/block/mmcblk0p37' for mount point '/data/ is not present!
E: unable to mount '/data'
E: unable to create /data/media folder
.....
E: unable to mount internal storage.
When I went to Advance->ADB Sideload, with the two box checked and started sideload, "adb devices" on my PC terminal still returned a empty device list, therefore, sideload a backup room is not possible either.
The whole things looks like the partition table for the internal disk is corrupted. I'll go to AT&T and see if they could fix it.
Thank you so much clsA for the inputs!
clsA said:
well if you can get into TWRP go to wipe / format data / and Factory Reset
then go to Advanced / ADB Sideload / check the 2 boxes /swipe to sideload
then from your PC sideload your Rom back to the phone and hope it works
put your rom in the same folder as adb / fastboot and from a command prompt
shift+right click / command prompt here
adb sideload name-of-rom.zip
Click to expand...
Click to collapse
How did you get on with this in the end? I have recently had the same problem and can't find any posts that are similar to the situation or and solutions! I get the exact same messages on adb, I can't flash recovery and can't lock the bootloader or erase the cache! Unlike you though the adb boot "recovery".img doesn't load twrp for me. It says that it is a success but then the phone freezes, and I have to reboot with power and vol down.
I have to give up and took it to AT&T. Since I'm still in the first year warranty period, I got a replacement, with a 90 days warranty.
Believe it or not, the same problem occurred after about 80 days of normal use! This time I did not even bothered to fix it, just took it back again to AT&T, and got yet another replacement, with the new Sense UI on it. Don't know how long this one will last.
brownie69 said:
How did you get on with this in the end? I have recently had the same problem and can't find any posts that are similar to the situation or and solutions! I get the exact same messages on adb, I can't flash recovery and can't lock the bootloader or erase the cache! Unlike you though the adb boot "recovery".img doesn't load twrp for me. It says that it is a success but then the phone freezes, and I have to reboot with power and vol down.
Click to expand...
Click to collapse
xxk said:
I have to give up and took it to AT&T. Since I'm still in the first year warranty period, I got a replacement, with a 90 days warranty.
Believe it or not, the same problem occurred after about 80 days of normal use! This time I did not even bothered to fix it, just took it back again to AT&T, and got yet another replacement, with the new Sense UI on it. Don't know how long this one will last.
Click to expand...
Click to collapse
Yeah I have been trying for days now and havent had any luck! Unfortunately not all providers are as forgiving as AT&T and I have had to buy a replacement nexus 4 until I get my upgrade! Thanks for getting back to me.
stuck in the same probelm did it got solved
I am having same problem
phone starts and reboots freezes hang and restarts every 5-10 min
any solutions?
or change hardware?
brownie69 said:
Yeah I have been trying for days now and havent had any luck! Unfortunately not all providers are as forgiving as AT&T and I have had to buy a replacement nexus 4 until I get my upgrade! Thanks for getting back to me.
Click to expand...
Click to collapse
jhakjhuk1853 said:
I am having same problem
phone starts and reboots freezes hang and restarts every 5-10 min
any solutions?
or change hardware?
Click to expand...
Click to collapse
Could'nt find any way to solve the problem, had to send it back to HTC where I am made to believe that it is a hardware fault but they still are charging me for the repair!
i have solved it
i have solved it by changing cache partion to extfat and formating
brownie69 said:
Could'nt find any way to solve the problem, had to send it back to HTC where I am made to believe that it is a hardware fault but they still are charging me for the repair!
Click to expand...
Click to collapse
jhakjhuk1853 said:
i have solved it by changing cache partion to extfat and formating
Click to expand...
Click to collapse
kindly please explain step by step how did you change the partition to extfat and how to get into recovery my htc one freeze when ever i try to get into recovery i can only get into boot loader nothing else can be access on the phone.
salman.saloo said:
kindly please explain step by step how did you change the partition to extfat and how to get into recovery my htc one freeze when ever i try to get into recovery i can only get into boot loader nothing else can be access on the phone.
Click to expand...
Click to collapse
I have a sprint htc one but I was in the same boat. Unable to mount data and internal storage. What I just did was while in boot loader I clicked on the factory reset option and it took me into twrp. It wiped everything and it seem to be working after I flashed a rom. Right now I'm trying to nandroid back with a otg cable.
jhakjhuk1853 said:
i have solved it by changing cache partion to extfat and formating
Click to expand...
Click to collapse
thx that did the trick for me also!!!!
I had this issue after flashing sense firmare over the GPE 5.1 firmare.
With your solution in TWRP i have reformated it to exFat first and than back to ext4 -> now it works!
My wife has a stock, unrooted, developer options off Asus MemoPad FHD 10 (ME302C) that is stuck on the Asus logo. I am able to get into the bootloader which says:
IFWI VERSION: 51.33
SERIAL_NUM: 1111111111111111
DROIDBOOT VERSION: Local Build or ENG version
PRODUCT: US_EPAD
At the bottom it has:
E:failed to mount /cache (Invalid argument)
E: Unable to mount /cache! we skip check debricking
E:failed to mount /cache (Invalid argument)
E: Unable to mount /cache! we skip check debricking
FASTBOOT INIT...
FASTBOOT CMD WAITING...
I have attempted to do the Factory Reset and it says:
E:failed to mount /cache (Invalid argument)
E: Unable to mount /cache! we reformat now!
At this point the green progress bar pops up but stops moving and it will stay like this until the battery dies.
I have attempted "Fastboot -w" which results in it beginning to erase the user data with the progress bar moving properly but again it will stay like this until the battery dies and fastboot reports that it fails due to too many links.
I have attempted to flash recovery, and boot both ending in send ok write failed. Hopefully someone here may know what to do next.
Same problem, a next step to solve 31122014
Hello, I have the same Problem with this ASUS tablet. There is a different product type, instead of US_EPAD it shows me WW_EPAD.
One next step I found to solve the problem is, that the tablet need a connection to the Internet. In the middle of the screen there are read "No USB cable connected!. Link the tablet to the net and it is changing to "Ready for download".
I am not further which download is it, but maybe someone can tell here? Please!
Problem solved, but it takes to replace motherboard
Pierre again.
I sent tablet to ASUS-Repair in Europe. They checked functions and tried different Software updates. At the end there are no success by repairing or trying things. They changed Motherboard and the issue was solved.
Bye, Pierre
My tablet is the same IFMI VERSION: 51.33 US_EPAD the only way I fixed it was download newest firmware off ASUS support and used fastboot.exe to flash it to my tablet. Good as new. 1. fastboot -w 2.fastboot flash update <update.zip> The second on on my machine looked like this.
fastboot flash update US_ME302C-V5.0.21-0-ota-user.zip The tablet won't work if you try to flash an image older than what you had.
Hi, I was running leedroid m9 rooted s-off with twrp and it was working great until I had some bizarre out of nowhere system app crashes earlier tonight (I guess yesterday by now). Commence boot loop. At first I was unable to access recovery and was just met with another shorter boot loop. I was eventually able to get into recovery through the bootloader menu but with a glaring fault. It gave me the prompt as if it was the first time booting into twrp, asking if I wanted to leave the partitions in read only mode. I thought "well kinda weird but ok". Then I try to restore my last post install image. It starts out with something about being unable to mount data or find the crypto header, and then it's nothing but "failed to mount x (invalid argument)". Same result for everything. Wipe, failed, adb sideload, failed, even manually attempting to mount in terminal failed (invalid argument). We even tried just completely opening up permissions (I know, very bad move for security but we were at our wits end). Unable to detect the phone via RUU or ADB in any state I can get it to boot to. I imagine something going on with encryption is to blame here? But I don't recall opting for or setting up any encryption?
Basically, is this phone beyond hope? Is there anything magical I can do through the bootloader (also not detected by adb)?
Also, looking in terminal in twrp, I'm still a root user? Don't know if that helps shed a light on this.