• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

Phone near bricked, help needed

76 posts in this topic

Posted (edited) · Report post

Hi guys,

As you could have read it, my friend's g300 is sort of ... bricked. I did everything that the guides told us to get Infusion's ICS rom on his phone, we downloaded and installed the stock ICS from Huawei, rooted it, etc.

For some time, it was great. After a week or two though, he found that his phone shut down and when he powered it on, it only showed the splash screen. When I get into the recovery, it writes:

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

It shows everytime when I do any function call in the recovery.

I thought that reflashing a recovery would help. Unfortunately it didn't, it said that the installation was successful, but the recovery didn't get flashed itself, when I restart the phone the old (and corrupted) recovery comes back. The recovery version that I used is "CWM-based Recovery" v4.0.1.5 .

I tried to TPT the stock ROMs from Huawei's website (via the volume up-down and power on method), but at around 30% the installation stops.

My last idea was trying to flash a recovery via fastboot, but when I do it closes with a warning:

sending 'recovery' (5898 KB)...

OKAY [ 0.565s]

writing 'recovery'...

FAILED (remote: flash write failure)

finished. total time: 87.952s

And I'm pretty much out of ideas. As far as I know as long as the phone can be turned on it's not literally bricked, but I just can't get it back to life. Any ideas? It would help a lot.

Thanks!

Edit:

One more thing. He mentioned that whenever he shut the phone down and then powered it on in the morning, it went straight to the recovery without holding the volume up button. I don't know why he didn't mention it when things were still working, but I can't go back in time, I guess...

Edited by Ereptor
0

Share this post


Link to post
Share on other sites

Posted · Report post

Boy, the suspense is killing me... ;)

Anyways, it's been a long day, I'll check back tomorrow if there was a good advice. If not, I guess I'll just have to tell him that his phone is a brick. Lesson learned: *never* tweak someone else's phone, because out of the blue things can get ugly.

And sorry about the double post, I'd just like to have the information separated from the hidden bump.

0

Share this post


Link to post
Share on other sites

Posted · Report post

just try a different sdcard and start again.

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Hmm. Try booting first with no SD card. Probably won't help but worth a try as it is simple. Next try to manually mount cache in CWM recovery. If that doesn't work try wipe cache and/or format and attempt to remount. You could also try mounting system partition in CWM to check that it can do it. Hopefully you just have a corrupt cache partition. Do not try more general wipes/formats/resets just yet but they may be needed depending on what's actually wrong.

At the moment it seems you still have CWM and an intact recovery partition at the least. Don't lose it! No more attempts to flash CWM. It is not a problem with CWM.

It might also be possible to use fastboot and/or adb commands from a PC to sort this out. "Fastboot erase cache" possibly might do the trick but I've not tried this myself

Edited by Hogweed
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Okay, just a little feedback:

- Mounting cache is a no go. I tried to wipe it, format it, and in the end even erase it via fastboot, but it's still unmountable.

- The system partition can be mounted in CWM though. As a matter of fact, every other partition can be, except for the dreadful cache.

- adb doesn't recognize the phone. I'm on a mac though, so I'll try to install the sdk and tools on my windows machine and see it it's only the drivers or something else.

- And in the end, I doubt that it's something related to the sd card. Sorry that I didn't mention it in my first post, but the guy doesn't even have an sd card, when we installed stuff, we used mine. Still, I tried to format mine and start with a fresh one, but now it's unmountable, yet another reason to try with Windows.

That's it so far, thanks for the suggestions, and keep them coming, I could really use them.

By the way, I'm starting to wonder if it's a bad block that causes the problems, what do you think?

Edit:

I tried the adb from Windows too, it's not working. I guess the ADB-debugging was turned off on his device, and it still remembers it. I understand that adb can't be used from the bootloader, but then how can I tinker with it?

Edit2:

Elementary Watson, from the recovery...

Edited by Ereptor
0

Share this post


Link to post
Share on other sites

Posted · Report post

What we need here is someone with more low level knowledge. Hopefully someone can drop in on the thread. I could offer suggestions but I would be taking a stab in the dark as I have never tried to repartition the phone.

0

Share this post


Link to post
Share on other sites

Posted · Report post

you should check if the eMMC is fried :wacko:

follow this guide to find out (if so, send it back under warranty)

http://forum.xda-dev...d.php?t=1284196

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Thanks for the posts guys. The eMMC doesn't seem to be fried, I get a long log, but none of the lines contains any of the strings that imply a corrupted eMMC. At least now I know that it's not a hardware failure, so it should be "resurrectable".

And don't worry about it Hogweed, your advices were helpful so far, while I didn't exactly bring her back to life, I still hold some hope for it at least.

Okay, someone (with a different phone) resolved a similar problem with flashing the stock recovery. Since I really have no better idea, I think I'll try the same with the superrecovery from the adb shell, and pray that it works. I'll update the post when I'm done saving/bricking the phone. Wish me luck!

Edited by Ereptor
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

It is possible a forced update might work (don't know how official updates behave with a corrupted cache partition though) using a pre-update package first known as the "middle package" (or upgrade/downgrade tool) but I am still hopeful someone will pop along with the adb commands to recreate the filesystem in linux. I could have a stab at it but I'm not willing to scrub my internal partitions to check it works :-) Hopefully someone who knows for certain will comment.

Edited by Hogweed
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

If it is any help /dev/block/mmcblk0p6 is mounted (ext4) as /cache on my G300 so that's where you need to recreate a filesystem.

The adb shell command hopefully is a simple as mke2fs command.

Edited by Hogweed
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

So, in theory, if I just repartition the /cache partition, I should be good to go?

If so, some Google search might actually solve the problem.

Update:

Flashing the superrecovery via adb quit with an error status -1, error scanning partitions.

Edited by Ereptor
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

I am hopeful that the partition table is intact and just recreating the filesystem with mke2fs command should work. Just getting the right arguments.

Might be worth just trying mke2fs /dev/block/mmcblk0p6

Edited by Hogweed
1

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Don't try to flash a new recovery as that is fine. Can you issue adb shell commands?

Edited by Hogweed
0

Share this post


Link to post
Share on other sites

Posted · Report post

Thanks for the tip, it didn't work. It was worth a shot though.

0

Share this post


Link to post
Share on other sites

Posted · Report post

Thanks for the tip, it didn't work. It was worth a shot though.

What did it say?

0

Share this post


Link to post
Share on other sites

Posted · Report post

Filesystem label=

OS type: Linux

Block size=1024 (log=0)

Fragment size=1024 (log=0)

49152 inodes, 196608 blocks

9830 blocks (5%) reserved for the super user

First data block=1

Maximum filesystem blocks=262144

24 block groups

8192 blocks per group, 8192 fragments per group

2048 inodes per group

Superblock backups stored on blocks:

8193, 24577, 40961, 57345, 73729

And yeah, I can at last, I did the mke2fs command from adb. I hope that's where I should have done it:)

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Now reboot recovery (or phone if feeling lucky)

Edited by Hogweed
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

I did, the problem persists. The same old E: can't mount ... errors.

I tried it again with adb's reboot. The same thing. I know repartitioning again and again (especially with an unstable phone which reboots from time to time, it totally crashed and rebooted on me the first time) isn't exactly safe, but I wanted to make sure it's the same this way. And I wanted to make sure that nothing changed either, and nope, the partition still has the same info as ever.

So, what I got from it that the problem isn't really the cache partition, or is it?

(If I'm feeling lucky? Boy, I'm kind of ambivalent on that one, I did things that should have made the phone explode and nothing happened, but it's still not working, so... :D )

Edit:

By the way, when I try to mount the cache partition in adb shell, I get an "invalid argument" error. I can mount all the other partitions except for this one (which makes sense, but I really don't get what's its problem with the arguments).

Edited by Ereptor
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Hmm, do you have an old nandroid backup? I wonder if you can "fastboot flash cache cache.img" from a backup.

I emailed Dazzozo to see if he can take a look at this thread but he may be busy or unavailable.

Edited by Hogweed
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Unfortunately not, as I said the sd card isn't his, so when the rom seemed to work all right, I deleted everything from the card.

Thank you, your help so far is much appreciated!

Edited by Ereptor
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

what you could do is make one .just wipe factory ,wipe cache, dalvick the usual as if your going to run a new rom . but backup and you have a clean nandriod.

that way you have no details of anyone .

Edited by wrtease
0

Share this post


Link to post
Share on other sites

Posted · Report post

How about the adb shell command "fdisk -l /dev/block/mmcblk0" that should list the partition table at least.

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Well, since the ROM has been reflashed since then it should be clean by default. Should I back that up and try to flash the cache anyway, just to see if it's possible at all?

Listed the partition table, here's the result:

Units = cylinders of 16 * 512 = 8192 bytes

Device Boot Start End Blocks Id System

/dev/block/mmcblk0p1 * 1 3 20 4d Unknown

Partition 1 does not end on cylinder boundary

/dev/block/mmcblk0p2 3 41 300 45 Unknown

Partition 2 does not end on cylinder boundary

/dev/block/mmcblk0p3 41 16681 133120 c Win95 FAT32 (LBA)

Partition 3 does not end on cylinder boundary

/dev/block/mmcblk0p4 16681 473088 3651263+ 5 Extended

Partition 4 does not end on cylinder boundary

/dev/block/mmcblk0p5 16897 18432 12288 6a Unknown

/dev/block/mmcblk0p6 18433 43008 196608 83 Linux

/dev/block/mmcblk0p7 43009 43520 4096 63 GNU HURD or SysV

/dev/block/mmcblk0p8 43521 43904 3072 58 Unknown

/dev/block/mmcblk0p9 44033 44544 4096 46 Unknown

/dev/block/mmcblk0p10 44545 44928 3072 4a Unknown

/dev/block/mmcblk0p11 45057 45440 3072 4b Unknown

/dev/block/mmcblk0p12 45569 94720 393216 83 Linux

/dev/block/mmcblk0p13 94721 193024 786432 83 Linux

/dev/block/mmcblk0p14 193025 193536 4096 47 Unknown

/dev/block/mmcblk0p15 193537 194560 8192 48 Unknown

/dev/block/mmcblk0p16 194561 197120 20480 60 Unknown

/dev/block/mmcblk0p17 197121 197632 4096 6c Unknown

/dev/block/mmcblk0p18 197633 207872 81920 83 Linux

/dev/block/mmcblk0p19 207873 473088 2121728 6b Unknown

Edited by Ereptor
0

Share this post


Link to post
Share on other sites

Posted · Report post

i have used to nandroid way before ,its still the way some devs use to give you the rom .

0

Share this post


Link to post
Share on other sites

Posted · Report post

I really don't see why backing up and restoring when you still have the problem would do any good myself. Does the partition table look ok?

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-2015. MoDaCo uses IntelliTxt technology.