Ereptor

Phone near bricked, help needed

76 posts in this topic

i take it this is clockwork working but giving you problems?

you need a working backup

Edited by wrtease
0

Share this post


Link to post
Share on other sites

Adb shell command "ls cache" What happens?

0

Share this post


Link to post
Share on other sites

@wrtease : More or less yes, I can get into CWM, but it lists the errors after almost every operation. Not to mention that for some reason the system itself doesn't boot, wether we tried to boot in the old system or the new, freshly installed Infusion one. I'd thought that the problem was with CWM itself, but since I can't even reflash any recovery via fastboot/adb, it doesn't seem to be the case.

@Hogweed : Nothing, the cache is empty. At least the directory is, since I can't mount it, so I don't really know what's going on in the cache. But if anything is working even remotely as it's supposed to, it should be empty anyway, since the first thing I tried was wiping the cache, to see if that solves the problem.

Edited by Ereptor
0

Share this post


Link to post
Share on other sites

well you need a working nandroid backup .at least to eliminate any problem ,what was the clockwork version you have.

0

Share this post


Link to post
Share on other sites

So you don't get the error "no such file or directory"?

Also did you check the partition table and did it appear to be intact?

Edited by Hogweed
0

Share this post


Link to post
Share on other sites

The CWM version I use is v4.0.1.5. Not the latest and greatest, but it was the one listed in the guide, and we didn't feel the need to flash a newer one. At least until that dreadful day, when my friend called me that his phone is dead.

@Hogweed : Nope, the directory is there, but as I said, it's only the directory where cache would be mounted itself, since it can't be mounted. Or that's what I believe anyway, because when I try it writes "umount: can't umount cache: Invalid argument". Actually that's the exact same error as the one that I get when I want to mount it. Weird.

Edit:

I'm not sure how the partition table should look. It definitely doesn't look like a healthy one to me, but I might be wrong. If you haven't seen it, I posted it in one of my previous posts by the way.

Edited by Ereptor
0

Share this post


Link to post
Share on other sites

Someone may have fiddled with the default mounts or some related fiddling - at least that's what I'm starting to think.

Edited by Hogweed
0

Share this post


Link to post
Share on other sites

have you tried another sdcard and load it with a couple of roms and a clockwork zip and see what happens.try installing any?

Edited by wrtease
0

Share this post


Link to post
Share on other sites

I tried it with another sdcard. I haven't actually flashed the rom that's on it yet, I'll check back when I'm done. One thing is sure: the roms and the recovery did look like they were flashed with the previous sd card, but the rom didn't boot, and the recovery didn't get updated at all. Not to mention, that I guess if the problem was with the card, then flashing with fastboot should work, but it doesn't.

Done, and the same: It installs successfully, but nothing really changes. (At least with the rom, I don't really think that it would be any different with a recovery)

Edited by Ereptor
0

Share this post


Link to post
Share on other sites

Ok partition table looks ok at first glance. Could you now post the output of the shell command "mount"

0

Share this post


Link to post
Share on other sites

Sure, here's the output of mount:

rootfs on / type rootfs (rw)

tmpfs on /dev type tmpfs (rw,relatime,mode=755)

devpts on /dev/pts type devpts (rw,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,relatime)

tmpfs on /tmp type tmpfs (rw,relatime)

/dev/block/mmcblk1 on /sdcard type vfat (rw,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)

0

Share this post


Link to post
Share on other sites

i thought the sdcard should have been fat or fat32 ?

0

Share this post


Link to post
Share on other sites

It's the card of my dad, the previous one was partitioned as fat32. But since I did that the recovery doesn't recognize it. Actually, it really is weird, I thought that it had to be fat/fat32, but it seems to be working okay, all the contents are there, and the flash seemed to be working either.

0

Share this post


Link to post
Share on other sites

you could copy all the contents to your pc and then reformat your card , then copy back .

0

Share this post


Link to post
Share on other sites

If you want me to I can do that, but I'm afraid that it might not recognize this card anymore either. But then again, the phone is a bit more important than the chore of copying 200 Mb twice, so, give your command and I shall follow you to death, sir! ... God, I'd need some sleep.

0

Share this post


Link to post
Share on other sites

use a card reader if you can.

0

Share this post


Link to post
Share on other sites

I have one somewhere, but I can't find it. Now I'm trying to use my sister's phone as an adapter, but Windows can be so annoying when it's trying to interact with a Samsung device. I mean c'mon, why can any Unix based OS just mount that freaking SD card, and why can't Windows do the same...?

0

Share this post


Link to post
Share on other sites

nothing is straight forward now adays.

0

Share this post


Link to post
Share on other sites

Okay, I tried again with a fat32 sd card, and to not that much of a surprise, it's the same results. I guess I'll just give it a day and see if Dazzozo could have spared some of his time on my problem, maybe he could come up with a solution. And if he can't, then I guess I'll just give the phone back to my friend, and see if he goes back to the costumer service and says that out of the blue it just broke, wether they give a new phone to him or not.

0

Share this post


Link to post
Share on other sites

well you could try to put ics back on or use the downgrade option ,and see if that works ,nothing to loose now.

0

Share this post


Link to post
Share on other sites

so, what exactly happens when you try to boot the phone after installing a rom?

if its because of the cache, i could give you a script that converts the cache to the sdcard or RAM at boot.

we used this on the zte skate so we could resize the cache and get more internal storage,

this could get the phone to boot up at least

0

Share this post


Link to post
Share on other sites

Well, when I try to boot the rom, it stops at the splash screen (the orange logo with the 3G and chinese mark). And that's it, it doesn't even begin the boot animation, it's just there, as if there wasn't even a rom installed.

0

Share this post


Link to post
Share on other sites

you need to run the ics dload folder and the downgrade dload .good luck.

0

Share this post


Link to post
Share on other sites

I tried to install the official ICS rom with the UPDATE.app, but at around 30% it stops. Or do I have to start with the downgrade? The 4kb looked too little, so I didn't risk running it and loosing the recovery and maybe even the bootloader for nothing.

0

Share this post


Link to post
Share on other sites

one of those dload folders should work. even the b927 version.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.