[[DEV][WIP]ClockWorkMod Recovery 6.0.3.7[ALPHA-1] - HTC Desire C

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ClockWorkMod Recovery​
Finally No more the Golfu users have to be with the TWRP ... Here I present with my evening work of a stable ClockWorkMod 6.0.3.7
Working List
EveryThing
How to Get it
Code:
[LIST="1"]
[*]Download the Zip Package
[*]Put it on your SD card
[*]Boot To ClockWorkMod
[*]Select Install from SD card and select the RecoveryZip Package
*]Then yes and it will get install
[*]Go to Advanced option and Reboot Recovery
[*]Check your recovery
[/LIST]

Download Links
Code:
[CENTER][SIZE="5"]Link--> [URL="http://www.mediafire.com/?jne56maeb5lk5ut"][COLOR="Blue"]Alpha-1[/COLOR][/URL][/SIZE][/CENTER]

yajnab said:
Download Links
Code:
[CENTER][SIZE="5"]Link--> [URL="http://www.mediafire.com/?jne56maeb5lk5ut"][COLOR="Blue"]Alpha-1[/COLOR][/URL][/SIZE][/CENTER]
Click to expand...
Click to collapse
Release just as recovery. IMG as we don't have s-off
Sent from my HTC Desire C using XDA Premium 4 mobile app

Shad0wPanda said:
Release just as recovery. IMG as we don't have s-off
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I dont get you! Can you please elaborate

yajnab said:
I dont get you! Can you please elaborate
Click to expand...
Click to collapse
You don't need to put in zip just release as recovery.img and is there a touch version? And it works fine
Sent from my HTC Desire C using XDA Premium 4 mobile app

Shad0wPanda said:
You don't need to put in zip just release as recovery.img and is there a touch version? And it works fine
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ohh!! Ya thanks. I will be happy of you can take some screenshots of the CWM with a tool called ddms present in the sdk/tools present in the android-sdk..

yajnab said:
Ohh!! Ya thanks. I will be happy of you can take some screenshots of the CWM with a tool called ddms present in the sdk/tools present in the android-sdk..
Click to expand...
Click to collapse
Ok and could you make a touch version please. Thanks
Sent from my HTC Desire C using XDA Premium 4 mobile app

Great work!!
I haven't seen any bugs.

Is it working properly???Thinking to change the recovery...
Please if any one used it, can report bugs...

good work, tried it , It Works Fine... it has smaller text so it looks quite nice like that.
but instructions are not noob friendly and incorrect as far as i know
it says boot to clockwork mod, if comming from stock you wont have clockwork mod
and cannot be flashed via cwm anyway,
also ths needs to be flashed via fastboot
like so
open up cmd windows on pc, plug phone into usb
hold the volume down key and hold power button till you boot to bootloader
type this from the command window on your pc
fastboot flash recovery recovery.img
good job though bro.
notes:, theres options in backup for internal sd card and we have no internal sd on this phone, so im assuming you can remove these
and upon boot into cwm recovery, it came up with "Warning: no such file" or something like that, but appers to work fine, baybe related to the internal sd I just mentioned.

There is a partition named and used as Internal Storage ...just take your SDCard out and you'll still have storage space
Bashing away at my HTC Desire C

that is true it does have a small storage
but just wanted to report that this recovery is giving a warning on first start
no file_contexts
and the cwm log is giving info
like
I: checking for extended command...
I: skipping execution of extended command, file not found...
I: can't format unknown volume: /external_sd
what is this about does anyone know, this cwm works great though
got no problems with it so far, quite like it, it seems a little faster to backup and restore
maybe just placebo, but gonna stay with it on phone see how it runs.
edit: also if select choose zip from internal sdcard
E: can't mount /emmc/
and key test, works but unable to go back

i just now tried it on my phone
hi i just flashed it on my phone .
i previously had Mujeni V5 as recomended i tried install zip from sd card but it did not work so i did adb thing with
fastboot flash recovery recovery.img and it worked .
i did not try or notice insternal storaged cards thing but when i come across it then ill post regarding it.

Thanks yajnab, it works perfectly on my phone! Now backup is completed correctly.

fankool said:
Thanks yajnab, it works perfectly on my phone! Now backup is completed correctly.
Click to expand...
Click to collapse
... but today I tried to cancel dalvik cache and it wasn't possible (error mounting file system, and something more like this). I tried to mount manually and still nothing. Am I alone?

fankool said:
... but today I tried to cancel dalvik cache and it wasn't possible (error mounting file system, and something more like this). I tried to mount manually and still nothing. Am I alone?
Click to expand...
Click to collapse
Get a log from the recovery and do it a pastebin.org

yajnab said:
Get a log from the recovery and do it a pastebin.org
Click to expand...
Click to collapse
However, on the last line of the main screen of CWM it's written: "Warning: No file_contexts". How can I save a log on memory card? If you mean recovery.log you can see it here: http://pastebin.com/BgCzWerx
Selecting "show log" on cwm I can read:
-----
init.svc.choice_fn=stopped
init.svc.dmesg=stopped
init.svc.detect_key=running
init.svc.rmt_storage=running
init.svc.adbd=restarting
service.adb.root=1
ro.9kramdump=0
init.svc.recovery=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't format unknown volume: /external_sd/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM manager to report the issue
-----
Is it normal I can change the option on the screen only by keys and not touching the screen?
thanks

fankool said:
However, on the last line of the main screen of CWM it's written: "Warning: No file_contexts". How can I save a log on memory card? If you mean recovery.log you can see it here: http://pastebin.com/BgCzWerx
Selecting "show log" on cwm I can read:
-----
init.svc.choice_fn=stopped
init.svc.dmesg=stopped
init.svc.detect_key=running
init.svc.rmt_storage=running
init.svc.adbd=restarting
service.adb.root=1
ro.9kramdump=0
init.svc.recovery=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't format unknown volume: /external_sd/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM manager to report the issue
-----
Is it normal I can change the option on the screen only by keys and not touching the screen?
thanks
Click to expand...
Click to collapse
I dunnno why this problem is arising . You cant use ROM manager and its not touch

Nice. Works fine, no bugs or anything. But I think no one would use it as we already have TWRP with full-touch and more features But still, GREAT WORK DUDE!

Related

[INFO] ClockworkMod 5.0.2.0 [09-05-11]

Originally posted by Koushik Dutta on Google+:
I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes: update from 09.05.11
Fix the fact that some users were loosing root access with 5.0.1.0
Fix menu bug Even if you select no during wipe dalvik cache, it still says it wipes it (it is not actually wiping it, it is just a display bug)
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!
Click to expand...
Click to collapse
To flash recovery for Nexus S, download recovery and place it into your sdk tools folder. Reboot into bootloader and execute:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
ill try
Sent from my Google Nexus S using XDA Premium App
I'm on it!
Or you can directly flash it from Rom Manager
You can also just put it on SD and flash from terminal then reboot.
Edit- before someone asks
su(press enter)
flash_image recovery /sdcard/5014cw.img(press enter)
reboot recovery(press enter)
Obviously the sdcard/* is whatever you rename the file
sent from my nexus s on a kang from simms
zadnica said:
Originally posted by Koushik Dutta on Google+:
To flash recovery for Nexus S, download recovery and place it into your sdk tools folder. Reboot into bootloader and execute:
Code:
fastboot flash recovery recovery-clockwork-5.0.1.0-crespo.img
Click to expand...
Click to collapse
I wish I would have seen this BEFORE I updated. It kept taking me to bootloader screen!!!!! But I unistalled and installed and finally got it to work!
Sent from my Nexus S using Tapatalk
Hey guys,
Everytime I restore from a backup through Rom Manager with the new recovery, I lose root. Right now, I'm stuck at work and cannot flash a rom, theme, battery mod, etc. I'll go back to 4.0.1.4 as soon as I go home
Am I the only one?
Edit: Found a solution==> Reboot into Recovery, flash su.zip again, and it's all good now!
f.
suhas_sm said:
Or you can directly flash it from Rom Manager
Click to expand...
Click to collapse
doesn't work for me..
I always recommend not using rom manager for anything flashing related, most problems occur for people when they're using rom manager and get fixed when done through recovery or in this case terminal/adb
RevengeITA said:
doesn't work for me..
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms
sinik420 said:
I always recommend not using rom manager for anything flashing related, most problems occur for people when they're using rom manager and get fixed when done through recovery or in this case terminal/adb
Click to expand...
Click to collapse
Code:
fastboot flash recovery recovery-clockwork-5.0.1.0-crespo.img
I prefer my previous post using terminal
zadnica said:
Code:
fastboot flash recovery recovery-clockwork-5.0.1.0-crespo.img
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms
When i try to flash this through android terminal i get a whole bunch of errors saying that its out of memory. Any solutions? I also tried using rom manager and ended up with no recovery instead of a new version
It took me two or three tries through terminal
Robin_216 said:
When i try to flash this through android terminal i get a whole bunch of errors saying that its out of memory. Any solutions? I also tried using rom manager and ended up with no recovery instead of a new version
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms
Robin_216 said:
When i try to flash this through android terminal i get a whole bunch of errors saying that its out of memory. Any solutions? I also tried using rom manager and ended up with no recovery instead of a new version
Click to expand...
Click to collapse
What the errors?
Worked like a charm thanks
Backups are significantly faster, thanks. (Flashed using fastboot)
zadnica said:
What the errors?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These are the errors that appear. I however managed to flash it with rom manager after some tries so it works now.
Sent from my Nexus S using XDA App
Robin_216 said:
These are the errors that appear. I however managed to flash it with rom manager after some tries so it works now.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I had the same issue. What helped for me was (in Terminal) :
su
mount -o rw,remount /dev/block/mtdblock3 /system
chmod 755 /system/bin/flash_image (wait for a minute)
(Reboot if the next step didn't work)
flash_image recovery /sdcard/RECOVERY.img
Click to expand...
Click to collapse
If I use the latest one, can I boot into recovery by using Rom manager? Will Rom manager detect my latest clockworkmod?
Accidentally sent from my Nexus S using XDA Premium App
Strangely, *immediately* after flashing the new recovery, I have begun to experience the Nexus S Google Voice Search bug. In the two months I've had the phone, this never happened - not even once.
This was with a two week old CM nightly, and a Matrix kernel.
Regardless - I'm hoping we'll start to see 2.3.6 kernels/roms come out soon which will fix it permanently. I'm just shocked that this issue popped up immediately after flashing the updated Clockwork.

[GUIDE] Flash Clockworkmod recovery on Galaxy Mini/Pop

At first: Download the attachments to this post. warning: If you have Android Froyo, download CWM-Froyo.tar. If you have Gingerbread, download tass-recovery-cwm.tar
For the steps 4-9, there is a screenshot below.
After downloading, you can start using my little guide!
1. Power down your phone.
2. Enter download mode by pressing 'Volume down + Home button + power button. Wait a second. After some time the screen says download.
3. Connect through USB to your PC.
4. Launch ODIN v4.38.
5. Wait for Odin to recognize your phone. (At the left, there will be a yellow box that says COM "?", the number can be different.)
6. Select Tass_v1.0.ops by pressing the 'OPS-button'
7. Make sure 'One package' is marked at the left of the window.
8. Select tass-recovery-cwm.tar with the 'One Package-button' at the bottom of your window.
9. Press start, wait 'till your phone reboots. Now you'll have ClockWorkMod-recovery installed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does this work for Froyo as well?
If not maybe you should add it to your guide as a warning!
Nevertheless thank you very much for the guide!
Well, as far as my experience goes, it does.
But, found a version that's specially made for froyo, so I'll add it to the post.
Please add some screenshot for newbies
freddies said:
Please add some screenshot for newbies
Click to expand...
Click to collapse
Will do...
Tnx for your tip!
EDIT: added a screenshot...
Hi have the stock 2.3.5, I flashed clockworkmod and I tried to do a backup of my rom. Clockwork on opening says:
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
and then when I try to do a backup the same errors...
if I select "mounts and storage" I can't manually mount nothing (/system, /cache, /data).
I try to format the 32GB sdcard again and I changed it with another one (2GB). Same results :-(
anyway the problem it isn't the memory card, clockworkmod can see the contents of it. the problem is that can't mount system folders...
Had the same problem last time. Try to contact the developers over at Clockwork...
You might get some help over there. I've just made this guide, I am not the developer.
walker7373 said:
Hi have the stock 2.3.5, I flashed clockworkmod and I tried to do a backup of my rom. Clockwork on opening says:
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
and then when I try to do a backup the same errors...
if I select "mounts and storage" I can't manually mount nothing (/system, /cache, /data).
I try to format the 32GB sdcard again and I changed it with another one (2GB). Same results :-(
anyway the problem it isn't the memory card, clockworkmod can see the contents of it. the problem is that can't mount system folders...
Click to expand...
Click to collapse
You can't backup stock roms using this CWM recovery since it still doesn't supports backing up of rfs partitions. The developer left it so since we believed those who will be using CWM recovery will probably be using any custom rom which is supported for backup.
Agree with yagya.... Cwm fully function on ext 2/3/4 file system only. I've tried on stock rom xxkws2, backup sucseed..but failed to restore.
Sent from my GT-S5570 using xda premium
thanks for explanation
Is cwm 4.0.0.5 right?
KoperKiller said:
Is cwm 4.0.0.5 right?
Click to expand...
Click to collapse
Yes, read through this to flash it on our Galaxy Mini/Pop gts5570. http://yagyagaire.blogspot.com/2011/09/installing-clock-work-mod-recovery-in.html
You may also follow the link on my signature for grate Galaxy Mini stuffs and guides or tutorials.
Hi...you can backup stock rom...ho says that you cant ...i backup gingerbread with cwm v5...just trying to help
Sent from my GT-S5570 using XDA App
And by the way you can restore to...i had 2 backups one with stock and one with cyanogenmod and i restore them when i want
Sent from my GT-S5570 using XDA App
plesan said:
And by the way you can restore to...i had 2 backups one with stock and one with cyanogenmod and i restore them when i want
Sent from my GT-S5570 using XDA App
Click to expand...
Click to collapse
Yes, you can backup and restore stock roms with latest CWM recovery v5.0.2.6 however, there comes an issue when you try to restore GB backup over cm7 or other custom rom. So, it seems pretty useless.
Also, CWM recovery doesn't work fully with stock roms. Just yesterday someone complained recovery shows error when flashing gingerbread-2.3.6-root.zip file for rooting GB 2.3.6, later when I suggested him to flash it on stock recovery it worked.
So, it's pretty simple and clear custom recovery is good with custom roms only.
Unable to backup stock rom, seeking help.
Hello all and thanks Bunnybugs_007 for the tutorial.
I managed to install CWM v 4.0.0.5 but still I cannot backup my stock rom.
I can boot into recovery mode from CWM (4.0.0.5) But I can't backup stock rom.
I am getting mounting errors. (The only partition I can mount is the sdcard partition).
I would also like to ask you if I can update CWM through itself during recovery mode. Is this possible, I mean, CWM flashing itself?
Or do I have to use ODIN to update CWM 4.0.0.5 to CWM 5.0.2.6.?
This file is in a zip format but it does not have any img file inside...
I own a froyo but keep getting erros in mounting.
Thanks a lot.
P.s.: I been looking around for the answer but haven't figured it out yet. Although the question about CWM updating itself might by absurd i am forced to ask it. The info that I have gathered until now is confusing. I have also tried to update CWM through ROM MANAGER. but its GUI doesn't even recognize the CWM that is already installed. And RM doesn't recognize the phone model, when I try to get an appropriate version for it. So it's of no surprise that RM can't backup stock rom either...
thanks for the guide. going to check it out...
I managed to install CWM v 4.0.0.5 but still I cannot backup my stock rom.
I can boot into recovery mode from CWM (4.0.0.5) But I can't backup stock rom.
Click to expand...
Click to collapse
It simply means .. No, you can't backup Stock ROMs.
Hi Guys!
I flashed Clockworkmod recovery in my Galaxy Mini. I have Rom Manager, but when I try to partition my sd card, it says "You must have ClockworkMod Recovery installed before continuing! Install blah blah blah!"
The ClockworkMod is working in recovery mode too, but I don't know what exactly is the problem!
Help Guys! I desperately want to increase my internal memory
^^ You installed CWM via Odin or Rom Manager? If its through Rom Manager, then I guess something would have turned wrong.
Sent from SGM

[Touch recoveries] TWRP and CWM Touch (RC)

----- TWRP -----
What is TWRP:
Open source touch based recovery.
http://teamw.in/project/twrp2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
New version of TWRP v2.1.4 (31-05-2012):
Fixed weird colors
All function are working (including adb)
As fast as it gets
Theme I made is default (see 1st screen)
Please report bugs.
Known issues:
Theming works, but you gotta press the 'advanced->reload theme' button every boot.
Place ui.zip (do not extract) here: /sdcard/TWRP/theme/ui.zip. Reboot to recovery and press reload theme.
Ill try to fix theming on boot this week.
Install
Use fastboot to flash it (like normal recovery):
fastboot flash recovery recovery.img
Themes
ICS look
ICS look by XiproX
LG theme
----- CWM Touch -----
Single touch version under development by Napstar
About
Press thanks if you like this !!!
I don't like the slow downloadsites to make money, so a little donation would be nice
thomas1991_12 said:
Hi,
I'm new to android development but I have compiled twrp v2.1.4. for our lg gt540.
So we now have touch recovery
I haven't tested everything, so please report bugs.
Use fastboot to flash it (like normal recovery):
fastboot flash recovery recovery.img
Press thanks if you like this.
I don't like the slow downloadsites to make money, so a little donation would be nice
Click to expand...
Click to collapse
Thanks so much!!! Installing now and testing!
Thanks alot man !!! Can this recovery restore CWM backups ?? And why dont you try to make touch cwm recovery ?
smileydr0id said:
Thanks alot man !!! Can this recovery restore CWM backups ?? And why dont you try to make touch cwm recovery ?
Click to expand...
Click to collapse
Dont think so.. But you could try. I tried touch cwm but couldnt get touch input working. TWRP is good too
Sent from my GT540 using XDA
Confirmed. This recovery can't restore cwm backups because backups made with this recovery are in different format.
Good thing is that:
- backup's are faster (restore's too) than cwm
- can apply compression to backups so they will weigh less (207mb with TWRP vs 350mb of Cwm)
- can reboot into fastboot (in cwm don't)
- touch!!!!!!!
- can partition SD and set ext size and format.
- same features as Cwm recovery and more organized
Thanks for compile this recovery!!!
Sent from my GT540 using xda premium
You only have to make usb mount work and it will be perfect !!!!
so someone DID see the post i posted
Thanks for making this work!
great work i am waiting for this type of recovery bcz my volume butten is almost dead.sorry for my bad english
Sent from my GT540 using xda premium
maneshvinod said:
great work i am waiting for this type of recovery bcz my volume butten is almost dead.sorry for my bad english
Sent from my GT540 using xda premium
Click to expand...
Click to collapse
True story! Only difference is that my keyes are already dead
Anyone can try aroma installer on this recovery
Wysyłane z mojego GT-S5660 za pomocą Tapatalk 2
Fastboot is the only way to install this recovery.
I already try with android terminal and root toolbox.
The terminal returns error.
After both methods and reboot to recovery the phone goes to Fastboot mode.
I'll try fastboot later, because this is very interesting alternative recovery
10x
hmm? what error? is it to do with memory?
s-u-f-f-e-r said:
Fastboot is the only way to install this recovery.
I already try with android terminal and root toolbox.
The terminal returns error.
After both methods and reboot to recovery the phone goes to Fastboot mode.
I'll try fastboot later, because this is very interesting alternative recovery
10x
Click to expand...
Click to collapse
you CAN flash this with terminal emulator / adb shell (for example):
su
flash_image recovery /sdcard/recovery.img
If you want to interact with SDcard from your computer you can do this with ADB (instead of usb mount). There is a flag to disable USB mount for TWRP (TW_NO_USB_STORAGE) but i will leave it in for now.
Iam installed this recovery by using yaffsexpert.apk.try this apk works great for me
Sent from my GT540 using xda premium
Does it work with rom manager?
Sent by tT!
Check this out (cwm touch recovery for lg p500!!!):
http://forum.xda-developers.com/showthread.php?t=1633003
Maybe you can port it to our phone.
Anyone that has tested, how is this overall compared to CWM? I would like to try it, but I don't wanna keep flashing this, and rolling back to CWM.
Also could we get some screens up please.
delsus said:
Anyone that has tested, how is this overall compared to CWM? I would like to try it, but I don't wanna keep flashing this, and rolling back to CWM.
Also could we get some screens up please.
Click to expand...
Click to collapse
About the same functions as CWM, but faster backup/restore. And it is a bit faster because you have touch and don't have to scroll trough all the 'no's' in the CWM menu.
like thomas1991_12 said it has same options as cwm but with faster backup and restore,only thing that doesnt work is usb mount...
i took 2 pictures but im sry for bad quality cause i have only 5mpx camera
I'll check it out, always nice for new things

samsung galaxy S I897 restart E: failed to mount / data file(exists)

samsung galaxy S I897 restart after galaxy S logo
i try to flash this file
I897UCKH3_I897UCKH3_I897UCKH3_HOME.tar
or
I897UCJF6.tar
but same
show error
E: failed to mount / data file(exists)
Try i897ucKK4 here... http://forum.xda-developers.com/showthread.php?p=18370912
Sent from my SAMSUNG-SGH-I897 using xda premium
4-2ndtwin said:
Try i897ucKK4 here... http://forum.xda-developers.com/showthread.php?p=18370912
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
after flash this i897uckk4 Odin One Click CONTAINS Bootloaders, Re-partition, Full Wipe.exe file same condition show samsung Galaxy S then restart
reboot continues
now give error E:failed to mount invalid argument
Your internal sdcard (not the removable external sdcard) may be messed up.
Did u ever see on ur phone the "Encryption unsuccessful" warning/error ?? If so, then there are a couple of threads about a work around (not a fix) in the Development forum.
If not, then try Heindall instead of Odin, to flash Stock KK4 firmware.
Sent from my SAMSUNG-SGH-I897 using xda premium
4-2ndtwin said:
Your internal sdcard (not the removable external sdcard) may be messed up.
Did u ever see on ur phone the "Encryption unsuccessful" warning/error ?? If so, then there are a couple of threads about a work around (not a fix) in the Development forum.
If not, then try Heindall instead of Odin, to flash Stock KK4 firmware.
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
SystemsCorps Cwm-based recovery v5.1.0.7
Wiping data
Eraseing /data
updating device table..
Erasing /cache..
using erase (rm-rf)...
Eraseing /dbdate..
using erase (rm-rf)..
Erasing /sdcard/ .android-secure...
using format_unknow_device...
Error mounting /sdcard/ .android-secure!
Skipping format ...
Data wipe complete.
now brother you say try to flash Heindall kk4 stock firmware
brother please clear my set working again or not b'coz i'm tried to load files allready download 1.45 gb anyway final try kk4 stock firmware otherwise use jtag
brother i request you if possible so plz repaired my fone
Now that you have cwm recovery, download and copy CyanaogenMod9 rom to your external sd card. Get into cwm recovery and install CM9 zip from your external sd card.
uhm said:
Now that you have cwm recovery, download and copy CyanaogenMod9 rom to your external sd card. Get into cwm recovery and install CM9 zip from your external sd card.
Click to expand...
Click to collapse
brother CyanaogenMod9 4r ICS 4.0.4 or support all firmware ..? can u provide me link which 1 i download and flash
http://get.cm/get/jenkins/7073/cm-9.1.0-captivatemtd.zip
uhm said:
http://get.cm/get/jenkins/7073/cm-9.1.0-captivatemtd.zip
Click to expand...
Click to collapse
1st thanks brother
brother after download this file copy my sd card
i try to update apply update from sdcard
then
yes - Install /sdcard/update.zip
E:can't mount /sdcard/update.zip
there is no option update external sd card.
Code:
E: failed to mount / data file(exists)
E:failed to mount invalid argument
Error mounting /sdcard/ .android-secure!
E:can't mount /sdcard/update.zip
how to repaire this fone condition show Galaxy S then reboot continuous
try to flash these flash files
I897UCJF6
I897UCKH3_I897ATTKH3_I897UCKH3
I897UCKE3
I897UCJI6-OCD-REV02-Low-designgears.exe
I897UCKH3_withBL.exe
i897uckk4 Odin One Click CONTAINS Bootloaders, Re-partition, Full Wipe.exe
I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click
CornKernel_UCKK4_v706
dbdata.rfs
speedmod-kernel-i897-k13e-500hz_2
One more thing. Why did you flash speedmod-kernel-i897-k13e-500hz_2? Flash CornKernel_UCKK4_v706 via odin first and then get into recovery mode.
In cwm recovery menu, don't select apply update from sdcard option. Instead select install zip from internal sd card(it's misleading though but this options lets you select zip file from your external sd card) and navigate to CM9 zip file you copied to your sd card. Then flash that zip.
I have had this happen to my phone twice and nothing fixed it, had to rma it and they replaced the main board, even reflashing on their end didn't solve the problem. Both time I was using voodoo lag fix and when I disabled it to flash a new rom I got that error.
Sent from my Transformer Prime TF201 using xda premium
Vaanhoot said:
I have had this happen to my phone twice and nothing fixed it, had to rma it and they replaced the main board, even reflashing on their end didn't solve the problem. Both time I was using voodoo lag fix and when I disabled it to flash a new rom I got that error.
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
Do you know how much they charge for people without warranty?
there is no working solution this problem
E: failed to mount / data file(exists)
Aww, RIP captivate. Guess I should looks into a new phone.
darkpower05 said:
Aww, RIP captivate. Guess I should looks into a new phone.
Click to expand...
Click to collapse
darkpower05 said:
Do you know how much they charge for people without warranty?
Click to expand...
Click to collapse
if u know how to repair this problem so plz help us
Contact mobiletechvideos.com and chat with them and see if they can fix it. They are very reputable, fast and recommended by many here on xda.
Sent from my SGH-I897 using xda premium
4-2ndtwin said:
Contact mobiletechvideos.com and chat with them and see if they can fix it. They are very reputable, fast and recommended by many here on xda.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
okay brother i contact him
and i flash this rom
SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Uploading PIT
PIT upload successful
Uploading KERNEL
KERNEL upload successful
Uploading RECOVERY
RECOVERY upload successful
Uploading MODEM
MODEM upload successful
Uploading FACTORYFS
FACTORYFS upload successful
Uploading DBDATAFS
DBDATAFS upload successful
Uploading CACHE
CACHE upload successful
Uploading IBL+PBL
IBL+PBL upload successful
Uploading SBL
SBL upload successful
Uploading SBL2
SBL2 upload successful
Uploading PARAM
PARAM upload successful
Ending session...
Rebooting device...
Device not connected.
set on show Galaxy S logo then only touch keypad light on

Partitions not mounting @boot

Hey Guys,
first off i had this issue once before, but in that case i could restore a cwm backup from sd card and after sometime the problem fixed itself,
this time, i switched to bacon and i wanted to prepare the p880 for my sister to use, i downloaded zaiben, formatted my external sd card and put the rom on it, i rebooted to recovery wiped( i used the clean to install new rom in philz recovery if i remember correctly) everything and flashed the rom and exactly as last time, the flash seems to go way too fast and ofc i cant boot into android. now as i formatted my sd i have no backup to restore to. kdz flashing seems hopeless as well, as none of the tools recognize the phone when i put it in s/w upgrade mode,
for proof: i checked /system with aromafm and found it being empty after flashing a rom, i even tried extracting the rom zip on sd and moving the content from the zip to /system manually but after a recovery reboot, /system was empty again( only empty "bin" folder)
is somebody able to explain me why i have this issue and maybe how to fix it, or upload a clean cwm backup of whatever rom for me to use?
thx
Thanks for the help until now, really.......
In Further investigation i could find out that Roms ARE actually flashing properly, but /system and probably other partitions are not being mounted
At Boot or in recovery(manually mounting works Here) which is why aromafm reports an empty /system, after a manual Mount in either recovery itself of Aroma console i can See /system being filled with Rom files, now i will change the thread title accordingly, and now ASK: can i force /system to be mounted at Boot somehow? Someone pls answer this time
Okay this is ridicoulous.... why am i getting no help AT ALL?, thank you srsly.....
i investigated even further and suspected that something with fstab might be wrong, but fstab file looks fine to me:
Code:
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 rw
if someone bothers to answer: what do you think?
pls help........
bump
please help
What recovery are you using? Are you sure your partitions aren't formatted to F2FS? (which would explain why the (F2FS-) recovery can mount the partitions but the system cannot as it expects an ext4 formatted partition rather than a F2FS formatted one)
i'm using an older version of philz touch (i dont think it has f2fs functionality), as i had weird flickering issues with latest philz,
using cat /proc/mounts shows ext4 for /system and other partitions
~MaX~ said:
i'm using an older version of philz touch (i dont think it has f2fs functionality), as i had weird flickering issues with latest philz,
using cat /proc/mounts shows ext4 for /system and other partitions
Click to expand...
Click to collapse
Did you try to boot another ROM (Slim, nameless, whatever) or using another kernel?
laufersteppenwolf said:
Did you try to boot another ROM (Slim, nameless, whatever) or using another kernel?
Click to expand...
Click to collapse
i tried latest aospa,zaiben, pa 3.99 and iodak kernel (stock or cm according to the kind of rom i tried to boot)
thank you for helping btw, i appreciate it
EDIT: I attached an image of output of cat /proc/mounts (sorry for the size)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
~MaX~ said:
i tried latest aospa,zaiben, pa 3.99 and iodak kernel (stock or cm according to the kind of rom i tried to boot)
thank you for helping btw, i appreciate it
EDIT: I attached an image of output of cat /proc/mounts (sorry for the size)
Click to expand...
Click to collapse
hmm, can you please grab me a kmsg? (from when it is stuck)
laufersteppenwolf said:
hmm, can you please grab me a kmsg? (from when it is stuck)
Click to expand...
Click to collapse
could you give me a quick how to on using adb in recovery from pc? i put the phone in sideload mode and tried "adb shell dmesg" but the output just was "error close" and using the command in aromafm terminal gave me an endless stream of log
(Also currently need to charge the phone a bit)
EDIT: NVM kmesg incoming....
okay next question, how can i dump the output into a file and how do i know where it hangs? time in recovery is not correct anymore(i set it once but after reboot it was wrong again, also in kmesg the time again seems to be different)
does that part help? i think it has to do with boot
~MaX~ said:
does that part help? i think it has to do with boot
Click to expand...
Click to collapse
nah, I need the entire log
here's how you get it:
boot the system until it is stuck
hard reboot into recovery (don't enter sideload)
then run the following commands:
Code:
adb shell cat /proc/last_kmsg > /sdcard/last_kmsg
adb pull /sdcard/last_kmsg C:\whatever\path\you\like\last_kmsg
then post the file via pastie.com or any other online paste site
laufersteppenwolf said:
nah, I need the entire log
here's how you get it:
boot the system until it is stuck
hard reboot into recovery (don't enter sideload)
then run the following commands:
Code:
adb shell cat /proc/last_kmsg > /sdcard/last_kmsg
adb pull /sdcard/last_kmsg C:\whatever\path\you\like\last_kmsg
then post the file via pastie.com or any other online paste site
Click to expand...
Click to collapse
no such file or directory
by hard reboot you mean vol - and hold power without pulling battery after hang?
~MaX~ said:
no such file or directory
by hard reboot you mean vol - and hold power without pulling battery after hang?
Click to expand...
Click to collapse
Yes, I meant that. But no kernel log seems like your boot partition/kernel is messed up... I guess you'll have to find a way to restore your entire phone via LG tools, I can't see any other way around that..
laufersteppenwolf said:
Yes, I meant that. But no kernel log seems like your boot partition/kernel is messed up... I guess you'll have to find a way to restore your entire phone via LG tools, I can't see any other way around that..
Click to expand...
Click to collapse
two last things then: when i hold vol - and then hold power until i reboot, recovery does not start, it tries to boot android again (has always been like that)
and also: all roms except cm official show no bootanimation before hang, cm does
~MaX~ said:
two last things then: when i hold vol - and then hold power until i reboot, recovery does not start, it tries to boot android again (has always been like that)
and also: all roms except cm official show no bootanimation before hang, cm does
Click to expand...
Click to collapse
1) yeah, I know, easiest way to fix that is to simply pull the battery and then boot into recovery
2) if the bootanimation shows up, it means the kernel as well as the ramdisk have booted properly. So in this case, you should be able to grab a last_kmsg as well as a logcat
hi
today I installed that application " LG-Optimus-4XHD-Recovery-v1.0.apk "
I have selected ClockworkMod Custom Recovery.
It showed that Operation is successful.
than i clicked on "Boot Recovery" to restart my Phone in CloclworkMod Custom Recovery.
since then I am getting only Starting animation. (LG LOGO).
nothing happens.
My battery was full when i performed this procedure
any help please

Categories

Resources