i hope someone really can help - General Questions and Answers

i have a htc clone which looks like the real thing i have attached pics to show you guys it runs 4.4.2 and since monday it wont let me boot up it will only let me go into the cwm recovery in the bottom left hand corner it says
cwm auto mode 27.12.2014 19:57:37
e: can't mount/cache/recovery/command
e: can't mount/cache/recovery/log
e: can't open/cache/recovry/log
e: can't mount/cache/recovery/last_log
e: can't open/cache/recovery/last_log
i hope someone can help me with this i can also tryed restoreing it and it wont
its on mt 6589 chipset and i dont know where to get the stock rom from

Related

[Recovery] CWM for Infuse 4G (untested)

I do not have a infuse 4G and that is why this is untested. I just built this recovery after setting up the configurations. It is quite possible that this doesn't work but I shall be active throughout the day to work on it.
Initial CWM (test)
http://www.mediafire.com/?ha2iu5mq8l51mnq
Flash it after installing this 3e recovery w/o signature checks: http://forum.xda-developers.com/showthread.php?t=1091465
I shall hopefully be on freenode irc #infuse4g but if not just send me a twitter at
twitter.com/razor950
just downloaded will be trying in a moment
ok had a working cwm recovery on my phone it was a older 2. something version with green writing i flashed this and the color changed to orange writing and it says clockwork mod recovery v3.1.0.1 follwed by the orange clockwork options follwed by
E:missing bitmap icon_clockwork
(code _10
clockworkmod recovery v3.1.0.1
E:failed to open /etc/recovery.ftsab (no such file or directory)
E:unknown volume for path [/cache/recovery/command]
E: cant mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:cant mount /cache/recovery/log
E:cant open cache/recovery/log
E:unknown volume for path {/cache/recovery/last_log]
E:cant mount cache /recovery/last_log
E:cant open ?cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
old version was 2.5.1.2 i rebooted into recovery after the install and it went back to 2.5.1.2 i dont know if it isnt working due to me having already put in cwm ?
Yep, I get the same exact behavior. Using the posted CWM gives orange screen, using CWM from Rom Manager gives green, and functions correctly (does nandroid backup at least)
yep clockwork from rom manager takes nandroid backups and allows me to flash cwm zips made in the uot kitchen
Hows the development on this?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

Please Help me Tablet problem

hi everyone i have an dicra tab 720 and i have a big problem since i have installed rom manger the cwm v5.5.0.4 then the tablet have a bootloop to recovery and i can't do anything in this recovery because of :
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 every time i reboot it reboot to this recovery can anyone tell me how to fix it plzzz? it didn't show on my computer help me please :crying: :crying: :crying:
Galaxy pop Plus said:
hi everyone i have an dicra tab 720 and i have a big problem since i have installed rom manger the cwm v5.5.0.4 then the tablet have a bootloop to recovery and i can't do anything in this recovery because of :
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 every time i reboot it reboot to this recovery can anyone tell me how to fix it plzzz? it didn't show on my computer help me please :crying: :crying: :crying:
Click to expand...
Click to collapse
hi i am new so i cannot specify the problem,but i can suggest you to view this link:
h t t p : / / x d a - u n i v e r s i t y. co m / a s - a- u s e r/ h o w- t o -r e c o v er - f r o m -a - b o o t l o o p
please remove the spaces...pardon me i cannot post direct link yet...
1+
Galaxy pop Plus said:
1+
Click to expand...
Click to collapse
has your problem been resolved via the link?
Try Reflashing Stock Recovery Via ADB....
Mr..X said:
has your problem been resolved via the link?
Click to expand...
Click to collapse
no it isn't resolved yet this a screenshoot for my problem
N'ayam Amarsh'e said:
Try Reflashing Stock Recovery Via ADB....
Click to expand...
Click to collapse
how can i do it plzz?
No answers :crying::crying:
Galaxy pop Plus said:
No answers :crying::crying:
Click to expand...
Click to collapse
sorry i didn't reply.....
here's how you can do it...
first take a same tab as yours or take a new cwm img file which you think it will work....
if you take a new device dump its rom.... see how to
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
when the dumping is done take its recovery.img file....
if you have a new cwm and if you have the recovery.img file you extracted go here
http://theblogoftechnology.wordpres...ll-clockworkmod-recovery-without-rom-manager/

[Completed] Problems with tablet x-tab pheonix easy touch 4gb 2g

Hello i have a tablet X-tab phoenix easy touch environmont 4gb
the tablet dosen't start (only in boot mod i can enter)
i have the rom for inet 86ve rev01
zeng gc 2012-12-06
the problem is when i try to rom i get an error
(e: Short write of /tmp/sideload/package.zip (No space left on device)
i tryed to instal an recovery mod img but i cannot instal cuz of Signature Verification Failed
+ i get some errors when i enter in boot
e: Error in /cache/recovery/last_log
(Read-only file system)
e:Can't open /cache/recovery/last_install
it seems that is not other recovery for my tablet so i have the own recovery (android system recovery 3e)
i dont know what to do more :| plz help
Hi,
There's no section for your device on XDA, so you'd want to ask for help here....
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!

[Q] E: failed to mount /efs (invalid argument)

Hello everyone. I'm a new member here so if I forget to mention crucial information needed to get technical support, please let me know.
Surprisingly it all started when my Galaxy Note Pro 12.2 (SM-P900) was low on battery yesterday. I had to go to college so I took my external battery with me and charged it in my backpack. I didn't need my tablet so I left it in there (was working fine before) and I came back to it this morning to find that it had restarted. It was on the glowing blue Samsung logo, but it wouldn't load past that. I tried restarting it and it wouldn't boot past the logo no matter what. So I tried booting into Android System Recovery (Power + Volume UP) to wipe the cache and still, same results. This is where I can see the error "E: failed to mount /efs (Invalid argument)".
I also did the following:
*Download Samsung Kies (both version 3 and the other since each one says it's not supported and to download the other) and try to resolve the issue. Tablet could not be recognized by either version. No fix.
*Download ADB and the official firmware and flash it (adb gives various errors, ex: can't connect. I may be doing the commands wrong as I'm no expert at this). No fix.
*Download Odin in an attempt to flash it, but the first search result in google was a professional-looking website that actually had a trojan-horse for download; had to shut down my PC and run MalwareBytes, Avast! and McAffee to ensure that nothing remained.
I've been at this since morning. I've also looked at other topics and websites about this problem but I can't seem to find a straight-forward solution. Can anyone please help? I desperately need my tablet for work as soon as possible.
Thanks in advance, and please be precise and clear with your answers (because I'm not so good at Android/Linux commands, or rooting or anything that isn't spoon-fed).
Update: Still not working after I tried to apply TWRP 2.8.6.0 (zip) through System Recovery. After finding, opening and verifying the package it gives the following error message:
E: failed to seek in /tmp/sideload/package.zip (Value too large for defined data type), E: signature verification failed, E: failed to mount /efs (Invalid argument).
I should also note that throughout the entire time I used the official firmware, I haven't used any custom ROMs but I'm now open to it since I have to do all this.
Update 2: Downloaded Cyanogenmod Installer and while it was about to install, it detected the device needed to be repaired. My device was in Android System Recovery under the "apply update from ADB" selection, and these errors came up when Cyanogenmod tried to fix it: "E: footer is wrong, E: signature verification failed".
BIG Update (3): I managed to find the legit Odin application and flashed TWRP v2.8.6.0. However, I'm not sure what to do from this point on out. Help?
Hi.
I am in the same situation. Have you found a solution ?
Thanks in advance.

[Completed] OT popc3 4033 bricked

Hello ... I tried to flash a custom rom to my OT popc3 but i think << HUSTON WE HAVE PROBLEM>> So i decided to ask your help... I have 2 days now searching for a backup because i didn t backup before flash custom rom! Anyway ! I have find something but i think i have a lot of work yet ! I find a stock rom with scatter file... I flash it and i am on recovery mode... But i got error E:cant mount /cache/recovery/command
cant mount /cache/recovery/log
cant open /cache/recovery/log
cant mount /cache/recovery/Last_log
cant open /cache/recovery/Last_log
Although ... IMEI don t appear ! If someone gonna help me .. Pls start from first step ! I hate MTK chipsets!
Thanks A lot
PS. I have access only in CWM !
ikerakos said:
Hello ... I tried to flash a custom rom to my OT popc3 but i think << HUSTON WE HAVE PROBLEM>> So i decided to ask your help... I have 2 days now searching for a backup because i didn t backup before flash custom rom! Anyway ! I have find something but i think i have a lot of work yet ! I find a stock rom with scatter file... I flash it and i am on recovery mode... But i got error E:cant mount /cache/recovery/command
cant mount /cache/recovery/log
cant open /cache/recovery/log
cant mount /cache/recovery/Last_log
cant open /cache/recovery/Last_log
Although ... IMEI don t appear ! If someone gonna help me .. Pls start from first step ! I hate MTK chipsets!
Thanks A lot
PS. I have access only in CWM !
Click to expand...
Click to collapse
SOLVED ! IF someone have the same problem can pm me because i can t post urls yet
ikerakos said:
SOLVED !
Click to expand...
Click to collapse
Thread closed.

Categories

Resources