I have a serious problem with my Elephone P6000 (MTK6732). Following a freeze, it seems my internal storage got corrupted. After a few attempts at fixing the issue by wiping and formatting in recovery, I resorted to a clean flash through SPFT. SPFT looks like it's working, but I suspect it's not actually writing anything, because:
- the format part of the operation is way too quick
- I am not injecting a custom recovery in the scatter file, but my custom recovery remains functional on the phone
- nothing changes in terms of normally booting the phone (i.e. it doesn't)
I have some I/O errors in dmesg, and I very well understand this could simply be a case of hardware failure that no amount of hacking can fix, but I read this is not always the case so I am still giving it a shot.
I also tried using parted via adb, but the changes I make don't seem to persist. I can still mount and unmount /cache and /system and their contents don't appear to be damaged. I wanted to give SP Multiport Flash a shot, but it complains about the COM port and I can't figure out how to set it properly.
Is there anything left to try or should I assume it's indeed a hardware problem? SPFT not working really concerns me. Would a nandroid backup help? I think I made one a few months ago and I am looking for it on my PC but I haven't found it yet. For clarity, I can still boot into Fastboot and CWM, I can still use a shell via ADB and SP Flash Tool still talks to the phone.
Forgive me fot bumping this but it would be great to get some help.
Hi,
You've asked in the correct section: http://forum.xda-developers.com/android/general/p6000-thread-bug-fixes-faq-info-t3028845
so I'll close this thread.
Related
Hi.
First of all I have to say that I found similar threads in this forum such as this and this and this but the problem is, they either provide use SEUS as a solution (which is only for sony ericson) or Flashing the entire phone.
I have a Motorola Charm phone with Android 2.1 firmware, and like everyone else tried rooting my android (using SuperOneClick, which went well) and installing apps2sd, but failed to do so due to lack of memory, and now I've lost the shell access, Wi-Fi, Bluetooth, and what not.
The command "adb shell" gives me this error:
exec '/system/bin/sh' failed: Exec format error (8)
I can't flash the phone due to the contacts, notes, and other important info I have on the phone. If there's a way to backup these info and then flash, please let me know. If there is a solution for this without the need to flash the phone, I'll appreciate it. Any help would be appreciated!
Again thanks a lot for your help. This problem is frustrating and I need my phone back asap!
I don't want to spam but can somebody PLEASE help me out??
This problem is frustrating and I've almost lost half of my entire phone functionality, all I can do is texting and calling. It's no different from an old Nokia phone running Symbian!
I searched everywhere and I found NO acceptable solution for this problem, although it seems to be very common. SEUS only works for Sony Ericson, and I've got a Motorola...
:crying::crying::crying:
There are no other forums better than xda-developers.
Please somebody help me out!
Try to wipe data and cache from stock recovery and let us know what happen
Is there any way to backup those info before wiping the data?
I have a whole lot of notes, contacts, etc which are essential.
Please, I need an answer. I can't just wipe the data, there are info I need to keep. I have to backup the data before flashing the phone...
I've tried several tools such as Wodershare MobileGO, but none of them work because they usually need shell access, and that doesn't work.
Does anyone know about a tool that can backup the internal phone memory without using ADB?
OK I did it but it still didn't work!
I master reset the phone, which wipes all the data and resets the phone back to the factory settings, but the WiFi is still not fixed and now I can't even call since the phone requires me to login and to do that it needs an internet connection...
Nothing was fixed. I'm brain-dead.
Anyone has a solution for this??
So what state is your phone in right now?
Even without shell access, you may be able to explore the filesystem with adb, using the pull subcommand. Finding a usable version of sh (perhaps in somebody's nandroid backup), and pushing it to /system/bin/sh may help you get shell access back.
-Snags
Fixed!!
Snags697 said:
So what state is your phone in right now?
Even without shell access, you may be able to explore the filesystem with adb, using the pull subcommand. Finding a usable version of sh (perhaps in somebody's nandroid backup), and pushing it to /system/bin/sh may help you get shell access back.
-Snags
Click to expand...
Click to collapse
It's good that someone at least is trying to help me...
Good thing I somehow managed to get it fixed!
After talking to the customer service and hearing them telling me that "I've got no choice but to exchange my phone,"; I came up with the idea of erasing the entire internal memory of the phone. I googled, learned that such thing is called Flashing, watched the tutorial, found the right SBF, Flashed my phone, and now everything is back to normal!
Also I found out about Link2SD app, and used this one instead of the script which worked perfect, and now, although I didn't find any custom ROMs for my phone, I have the apps moved to the SD card and the phone functions properly!
However, I'm kinda disappointed with XDA-Developers, based on their reputation. I expected some help. Maybe if someone had told me what to do this would've taken much less time for me. Doesn't matter now tho...
TL;DR:
The solution was Flashing the Phone (instead of Resetting it back to Factory Settings).
Dear all,
I have flashed my MZ605 (32GB) using EOS 3.0 for MZ601 with TWRP and that has worked quite well for some time, but last week I was fiddling with the navigation app and the tablet suddenly froze. The only way to get it back to life was doing a volume-up+power. Now the system still boots: i get to the lock screen, but as soon as I unlock (no password, just swiping to the right), I receive a shower of f/c messages and no icons apear. The settings screen still seems to work, but since the stream of f/c messages doesn't stop, it's very hard to do anything at all. I tried all the standard stuff first: Flashing EOS 3.0 using TWRP and Factory Reset: It seems to do nothing at all. Everything stays the same! When trying to delete cache, userdata, etc. Right after displaying the message "updating partition details", it complains that it is not able to access certain files in /data/media (a bunch of mp3 files)
Figuring that something must be wrong with the filesystem, I fired up the console of TWRP and did an e2fsck (e2fsck -vfcp) on partition 8,9 and 10, resulting simply in "unable to set superblock flags". I tried formatting the thing by hand but when doing mke2fs, it acts like it it's creating the fs (you see the numbers fly by), but when mounting the fs again, nothing changed at all!
About the partition table: Accessing the kernel messages (dmesg) with ADB says that the primary gpt table is corrupt and will try to use the backup table. It then merrily continues booting. However, when checking the partition table with gdisk (using ADB): it says nothing is present. Using the recovery options show that the primary table contains garbage and the backup partition table doesn't seem to contain anything. :S This contrasts with the fact that kernel still sees the partitions and that they are mountable both when booting normally as well as with TWRP
As a last resort I downloaded RSDLite 5.7 and the most recent SBF image. It flashes the whole thing without any errors, but when booting the system: nothing changed at all???
For the tl;dr people: Sorry! In a nutshell: fs seems to be frozen: mke2fs does nothing, fastboot flash does nothing and even sbf flash doesn't do anything at all. However the device still boots, albeit with a shower of f/c on unlock screen.
Any suggestions what to? I have been googling for many days now and reading this forum. Nothing has helped so far...
My next try would be to redefine the gpt partition table using gdisk and then hope that'll fix the frozen that. After that I would of course do a wipe all and flash a new ROM. The problem is, I can't find the standard partition layout details for the Xoom anywhere, nor do I have any other ideas what to do in case this does not work
If anyone has any hint or idea, please let me know. Thanks!
Nobody?
If anyone could please tell me their partition layout, like start - end - type for each partition. It'd really appreciate it!
Thanks!
No one?
Hello,
have you fixed it ?
Nope
jkd said:
Hello,
have you fixed it ?
Click to expand...
Click to collapse
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.
ioish said:
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.
Click to expand...
Click to collapse
Actually I have the same problem, I have read several forums and I have not found an answer
jkd said:
Actually I have the same problem, I have read several forums and I have not found an answer
Click to expand...
Click to collapse
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?
ioish said:
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?
Click to expand...
Click to collapse
my xoom caracteristic:
- Recovery: TWRP v2.6.3.0 (RunAndHide05 Edition), I can not tell if it's a bigpart or no recovery. Also I am unable to change recovery is cwm or another version of TWRP. I always find my TWRP recovery v2.6.3.0.
- ROM omni: 4.4.2-20140102-1218 + 0100-wingray-HOMEMADE (I don't know if is bigpart rom)
- kernel:2.6.39.4-ElementalX-Xoom-2.1+
Hi all, I have completely screwed my surface rt last night.
I was trying to do a reset and it wasn't working then I tried a bunch of other things ive read on the forum and my surface wont even boot up. its just in a constant loop ive trying to do an automatic repair and diagnosing and keeps bringing me to the boot menu.
I made a recovery usb but it doesn't seem to be working so im assuming the OS was already corrupt hence the reason the reset option in "change pc settings" wasn't working.
I would really love if someone could upload a recovery image of their surface rt. I cannot find one any where and the ones I have found they have pulled the links down.
hope someone can help me out here.
cheers.
adam_4049 said:
Hi all, I have completely screwed my surface rt last night.
I was trying to do a reset and it wasn't working then I tried a bunch of other things ive read on the forum and my surface wont even boot up. its just in a constant loop ive trying to do an automatic repair and diagnosing and keeps bringing me to the boot menu.
I made a recovery usb but it doesn't seem to be working so im assuming the OS was already corrupt hence the reason the reset option in "change pc settings" wasn't working.
I would really love if someone could upload a recovery image of their surface rt. I cannot find one any where and the ones I have found they have pulled the links down.
hope someone can help me out here.
cheers.
Click to expand...
Click to collapse
Next time do a search. You would have found a thread on this. And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you. Take it to Microsoft and have them replace it.
C-Lang said:
Next time do a search. You would have found a thread on this. And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you. Take it to Microsoft and have them replace it.
Click to expand...
Click to collapse
i did do a search and nothing has been able to help me so far. i also did read that it is device specific but have also read it has worked for some people. unfortunatley in australia we do no have any microsoft stores so its not that easy to just take it somewhere.
I feel like there are files missing from c drive. Almost like it started to do a restore then stopped halfway. In which I have never been able to get it to that stage for that to be the case.
I did some reading and was able to find the recover partition and tried to run the install.wim file from which I understand to basically be the “OS”. When I try to run it it says “no such interface supported”
From what I understand there is just no way to do a fresh install on these things regardless of what the problem is which is disappointing on Microsoft’s behalf.
C-Lang said:
And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you.
Click to expand...
Click to collapse
No. Those recovery images are device-type specific. Not device-specific. You can safely take one WIM file from the recovery partition of your device and use it to recover a different device of the identical model.
adam_4049
I see that you were able to start a restore process and it fails in the middle.
You may try the following: boot into the command line mode and format the boot partition (probably drive C: ). This would fix the disk errors if they are present, but you'll lose everything. Use diskpart tool to find the disk letter. Be careful with diskpart - do not delete partitions or issue "clean" command.
Then assign the letter to recovery partition with diskpart (say, R: ), then expand WIM file from the recovery partition with the command like this:
Code:
Dism /apply-image /imagefile:R:\RecoveryImage\install.wim /index:1 /ApplyDir:c:\
R:\RecoveryImage\install.wim - a path to install.wim on the recovery partition.
More info: http://technet.microsoft.com/en-us/library/hh824910.aspx - you need only "Dism /apply-image" part, bcdboot is unnecessary. Lets hope that "apply-image" option is present on RT.
This would forcibly expand the WIM file to your disk C:. Or at least you'll be able to see why it fails.
This may help. Or may completely brick the device and you'll need to go to service. So use it on your own risk. And you should be familiar with the command line - so don't ask how to use diskpart.
I had a problem with the recovery process when I've played with BCD and added a boot from VHD option. Had to delete that extra boot setting - and then recovery went fine. But I assume that you have not played with BCD.
Yeah, looks like people dont use search, what you want is a nice useful soul that creates a USB recovery from his EN-UK Surface_RT and puts it up on Copy, or Dropbox or something like that...
Hello there.
My phone is in a state which is widely being reffered to as "bricked". After hours of reading through hundreds of forums and trying out everything possible/impossible, I came to this - I'm posting here, and desperately asking you guys for help.
I have Moto G XT1032. I converted it to GPE, to install a 5.0.1 ROM few months ago. I used it without any problems. However, today I decided to try out the stock 5.0.2 ROM. But I read that I'll have to change my Data partition to F2FS (from EXT4). I did that (using TWRP v2.8.5.0), and then I did this terrible mistake: I decided to do a clean install, so I wiped everything. I wiped System, and Internal storage as well. Yes, I know that I'm stupid.
Now my phone is stuck at my custom recovery (TWRP) or at bootloader. I can switch between these two, but I can't boot to the system, because I don't have any system installed (because I wiped the /system partition - what an Einstein I am -_-). I thought that it would be easy - I just have to somehow push the zip file of the new ROM to my phone, and then install it from TWRP. The thing is - I can't transfer any files to the phone. I'm probably missing some drivers, but the problem is, that the phone doesn't have any operating system installed (besides bootloader, I guess) - so I can't get any drivers working. My PC is running Windows 7 64bit.
I tried installing Motorola Device Manager, I tried using the drivers from android-sdk, but nothing helped. When I type a command "adb devices" to a command line, it says: "List of devices attached >emtpy line<". When I connect the phone to the PC, it doesn't even try to look for drivers anymore. I tried deleting them (drivers), placing there some new, but again - nothing helped. If anyone can provide any help, I'd be very, very, very glad.
Thanks in advance.
//edit: Nevermind, I made my phone alive again. I just had to use mfastboot tools. Moderators can close or delete this thread, please. I'm sorry for creating it, since it was kinda useless.
temme how to recover the system folder. i have a system folder on my desktop. help me. my phone isnt turing on
If you can get into fastboot and recover you can restore your phone. You just need a complete ROM, and restore it with mfastboot method.
It doesn't matter if you wiped system, you can do that in TWRP, if you reboot it won't boot into the OS (obviously) but go into fastboot mode.
Download mfastboot, a ROM image, and go through the command lines. There is a FAQ on how to restore.
felmaster said:
Hello there.
My phone is in a state which is widely being reffered to as "bricked". After hours of reading through hundreds of forums and trying out everything possible/impossible, I came to this - I'm posting here, and desperately asking you guys for help.
I have Moto G XT1032. I converted it to GPE, to install a 5.0.1 ROM few months ago. I used it without any problems. However, today I decided to try out the stock 5.0.2 ROM. But I read that I'll have to change my Data partition to F2FS (from EXT4). I did that (using TWRP v2.8.5.0), and then I did this terrible mistake: I decided to do a clean install, so I wiped everything. I wiped System, and Internal storage as well. Yes, I know that I'm stupid.
Now my phone is stuck at my custom recovery (TWRP) or at bootloader. I can switch between these two, but I can't boot to the system, because I don't have any system installed (because I wiped the /system partition - what an Einstein I am -_-). I thought that it would be easy - I just have to somehow push the zip file of the new ROM to my phone, and then install it from TWRP. The thing is - I can't transfer any files to the phone. I'm probably missing some drivers, but the problem is, that the phone doesn't have any operating system installed (besides bootloader, I guess) - so I can't get any drivers working. My PC is running Windows 7 64bit.
I tried installing Motorola Device Manager, I tried using the drivers from android-sdk, but nothing helped. When I type a command "adb devices" to a command line, it says: "List of devices attached >emtpy line<". When I connect the phone to the PC, it doesn't even try to look for drivers anymore. I tried deleting them (drivers), placing there some new, but again - nothing helped. If anyone can provide any help, I'd be very, very, very glad.
Thanks in advance.
//edit: Nevermind, I made my phone alive again. I just had to use mfastboot tools. Moderators can close or delete this thread, please. I'm sorry for creating it, since it was kinda useless.
Click to expand...
Click to collapse
Also TWRP/CWM has support for adb, u just need to install the drivers manually. Then you can push whatever you want.
Of course you can try restoring stock as suggested above.
How did u fixed it? :/
As a last resort there is always OTG (this thing has OTG support right?). Life was so much simpler when you could just put your sd card into a card reader and put your zip on there. A quick google search makes me think its got support, but who knows
Persistent bricking of a Moto G XT1040 LTE
I'm happy to PayPal $20 to anyone who figures this one out...
One day it was working, and then - it froze and went to the loading screen and stayed there. I've unlocked and rooted and used for months with no issue. I've tried everything I can find to fix my Moto G LTE gen-1 XT1040, and I'm at my wits end.
It works, in the sense that I can load fastboot, and I can load CWM (I cannot load any version of TWRP), but I can't get into an operating system. I've tried flashing the stock OEM, I've tried flashing lolipop, slimkat, cyanogenmod - no luck with anything. It does not load into recovery (stock, CWM or TWRP) but can load CWM with "fastboot boot cwm.img" (fastboot flash boot cwm.img then booting into recovery fails).
It looks like some parts of the cyanogenmod flashing stuck, but since then nothing else seems to do anything. Also, the system partition seems to be "raw" when I try to use it - I can't delete my user data (things have persisted despite wiping commands from fastboot and in adb and in CWM). It looks as though anything I'm trying isn't "sticking". I've tried to be as detailed as possible with screenshots.
Maybe: corrupted system partition? somehow things are "locked"? should be hardbricked and then reinstalled as device driver? hardware issue?
All images / screenshots / logs with details are here: imgur.com/a/dQQGD
Any suggestions, tips, advice on this one? Your help would be very appreciated.
Sounds like the emmc corruption (making phone read-only) that possibly affects many phones. There are certainly numerous cases of this happening with Moto G - so many infact that I have looked into getting ROMs to boot via OTG-USB drives. There appears to be many 'solutions' if you search around, but I know of no single case where someone has fixed the problem. Replacing Motherboard is of course an option.
lost101 said:
Sounds like the emmc corruption (making phone read-only) that possibly affects many phones. There are certainly numerous cases of this happening with Moto G - so many infact that I have looked into getting ROMs to boot via OTG-USB drives. There appears to be many 'solutions' if you search around, but I know of no single case where someone has fixed the problem. Replacing Motherboard is of course an option.
Click to expand...
Click to collapse
Hmm.. Thanks for your reply. In another thread user liveroy posted "The eMMC is not corrupted or defunct, you just got the fs on those positions destroyed, therefore they are not formatted now, thus being RAW. If you still have custom recovery installed, try formatting /system, /data and flash CM12."
Any way to follow-up on that? Is there a way to do the formatting from adb?
I'm OK with replacing the motherboard, if that's needed. No idea where to find this particular part though.
Tried "mount -o rw,remount -t yaffs2 /system" got "mount: can't find /system in /proc/mounts"
canwond said:
Hmm.. Thanks for your reply. In another thread user liveroy posted "The eMMC is not corrupted or defunct, you just got the fs on those positions destroyed, therefore they are not formatted now, thus being RAW. If you still have custom recovery installed, try formatting /system, /data and flash CM12."
Any way to follow-up on that? Is there a way to do the formatting from adb?
I'm OK with replacing the motherboard, if that's needed. No idea where to find this particular part though.
Tried "mount -o rw,remount -t yaffs2 /system" got "mount: can't find /system in /proc/mounts"
Click to expand...
Click to collapse
I was under the impression the appearance of partitions being 'raw' was just another symptom of corruption. I gave some ideas to try regarding formatting in the later posts of this thread.
Look for an XT1040 with broken screen, but still functional; as a cheap way to get a motherboard.