Develop Bugs

[Q] Can't reset to factory details

Hi,
I have a bad situation with my device, which has gone low on battery and turned off and doesn't want to switch on again.
The situation is that the device can't neither mount nor format nor delete the "userdata" partition via ClockWorkMod Recovery, AmonRA recovery, fastboot, etc.
Now booted the device into HBoot and issued "ClearStorage" command - it hangs on "Clear emmc..." line.
fastboot -w goes forever until the battery dies and then it displays "too many links" error.
I was able to mount the contents of the internal storage to PC (obviously, not the userdata partition).
In attempt to use the parted mkfs command, got the input/output error.
I need a suggestion as to is it possible that the internal storage is damaged physically? Or - how to format the internal storage completely and erase all partitions if it is possible.
Also - I got another Droid Incredible device from which I have the backup - it fails to install when restoring userdata.
Please, help, I'm really stuck

Boot loop after sdcard repartition. URGENT!

Hi,
I have Cyanogenmod 7 on my Desire.
And I'm running Ubuntu 11.04 on my PC.
I copied the contents of my SD Card and the Apps2SD Partition (including hidden files), erased my SD Card and formatted it again (ext3 and FAT32), copied everything back (including hidden files) and now I get a boot loop.
-I used MicroSD>SD Card Adapter>PC
-I can access recovery
-I reduced the size of the ext partition from 1GB to 700MB
-I didn't make a nandroid backup before I did this.
-I changed the label of the ext partition.
-I'm using this for Apps2SD
Is there possibly some sort of temporary files/cache I can delete to make it work?
Thanks

Ano8 said:
Hi,
I have Cyanogenmod 7 on my Desire.
And I'm running Ubuntu 11.04 on my PC.
I copied the contents of my SD Card and the Apps2SD Partition (inclusing hidden files, erased my SD Card and formatted it again (ext3 and FAT32), copied everything back and now I get a boot loop.
-I used MicroSD>SD Card Adapter>PC
-I can access recovery
-I reduced the size of the ext partition from 1GB to 700MB
-I didn't make a nandroid backup before I did this.
-I changed the label of the ext partition.
Is there possibly some sort of temporary files/cache I can delete to make it work?
Thanks
Click to expand...
Click to collapse
The order of the partitions have to be FAT32 followed by the ext3 (and not viceversa)...Is it?

andQlimax said:
The order of the partitions have to be FAT32 followed by the ext3 (and not viceversa)...Is it?
Click to expand...
Click to collapse
They are in that order (unless you mean formatted first?)

The important thing is that the first partition is a fat32, and the second the ext
From the recovery menu try to see if it can mount the ext partition (try just a mount/unmount of the sd-ext to check if the recovery can access the ext) otherwise u can format it from the recovery and then copy back the files from ur pc car reader
U can also try wiping cache and dalvik cache, but don't think will have effects
Otherwise I have no other ideas

andQlimax said:
The important thing is that the first partition is a fat32, and the second the ext
From the recovery menu try to see if it can mount the ext partition (try just a mount/unmount of the sd-ext to check if the recovery can access the ext) otherwise u can format it from the recovery and then copy back the files from ur pc car reader
Click to expand...
Click to collapse
What is meant to happen when I do a mount/unmount in recovery?

Ano8 said:
What is meant to happen when I do a mount/unmount in recovery?
Click to expand...
Click to collapse
If the recovery can acces the ext, will just say u that is mounted (so everything is ok regarding that partition), otherwise u will get an error like "E:Can't mount dev/block/mmcblk0p2", in this last case u can try formatting the ext from the recovery menu, then restore the files in it (previously backupped) manually

andQlimax said:
If the recovery can acces the ext, will just say u that is mounted (so everything is ok regarding that partition), otherwise u will get an error like "E:Can't mount dev/block/mmcblk0p2", in this last case u can try formatting the ext from the recovery menu, then restore the files in it (previously backupped) manually
Click to expand...
Click to collapse
I went to the recovery menu and then I chose mounts and storage then I chose mount /sd-ext and then nothing happens. I can go and chose unmount /sd-ext, nothing changes except the text that says mount/unmount. No error messages.
What do I do now?

??????????

Bump.......

HELP!
I need to get my Phone working again!

Ano8 said:
HELP!
I need to get my Phone working again!
Click to expand...
Click to collapse
Why u didn't make a nandroid backup? A simple solution now will be to do a fresh install of ur rom again...
Anyway change the thread title.."Boot loop" is too generic, edit it as Boot loop after sdcard repartition URGENT, something like this...(To edit it just edit the first post title)
I hope someone else here can help u..I dont have other ideas, if the sdext is correclty read from the recovery, mean even ur rom should read it and should boot..How much time did u wait? are u sure the boot continue to loop? Go in recovery, wipe cache and dalvik, reboot and wait..U could also do "adb logcat" when ur phone is booting..Search for some guides for it..That will show u some possible errors during the boot that make ur phone bootlooping
Also try this: i read somewhere the ext partition label must be sd-ext (some a2sd script use the label to idenify the partition)(this label is automatically applied when u create/format the ext from the recovery, but as u created the partition ur self from the pc, put that label and see what happen)

andQlimax said:
Why u didn't make a nandroid backup? A simple solution now will be to do a fresh install of ur rom again...
Anyway change the thread title.."Boot loop" is too generic, edit it as Boot loop after sdcard repartition URGENT, something like this...(To edit it just edit the first post title)
I hope someone else here can help u..I dont have other ideas, if the sdext is correclty read from the recovery, mean even ur rom should read it and should boot..How much time did u wait? are u sure the boot continue to loop? Go in recovery, wipe cache and dalvik, reboot and wait..U could also do "adb logcat" when ur phone is booting..Search for some guides for it..That will show u some possible errors during the boot that make ur phone bootlooping
Also try this: i read somewhere the ext partition label must be sd-ext (some a2sd script use the label to idenify the partition)(this label is automatically applied when u create/format the ext from the recovery, but as u created the partition ur self from the pc, put that label and see what happen)
Click to expand...
Click to collapse
I've tried putting the label as sd-ext. Didn't work
I know I have waited long enough because the animation of the skateboarding blue android repeats (he comes in from the side again).
Can you link me a guide of how to do "adb logcat"?

???????????

bump.........

How do I do an "adb logcat"?
Can you show me a guide, please?

I'm using this for Apps2SD

you need to install android sdk. after that go to platform-tools folder and run adb.exe logcat
Ano8 said:
How do I do an "adb logcat"?
Can you show me a guide, please?
Click to expand...
Click to collapse

ranjii said:
you need to install android sdk. after that go to platform-tools folder and run adb.exe logcat
Click to expand...
Click to collapse
Ok, I'll do that now...

ranjii said:
you need to install android sdk. after that go to platform-tools folder and run adb.exe logcat
Click to expand...
Click to collapse
I'm getting this error:
/sbin/sh: logcat: not found

HELP!!!!!!!!

[Q] No /system /cache /sdcard partitions, can't flash kernel

Ok, here is the problem, i woke up today, my phone battery was empty, i connected the phone battery was loading, but i couldn't get to the system, after kernel load it stops, like there was no system installed. Everything worked fine day before,my configuration was: Doomkernel and Existenz_2.0.5 ROM.
So, i got to recovery (recovery works,CWM), and there i saw "can't mount cache" error. I got into shell with adb (this works too), and there is no way i can mount any system partition (/system, /cache, /data), what's more important /sdcard does not mount either. So, i'm in recovery, can't install or restore from sdcard,cause /sdcard does not mount.
I'v tried sideload, no go.
I've tried fastboot flash new kernel, and here's interesing thing, fastboot reported that flashing was ok, but i still have Doomkernel (i was trying to flash 6.0-TUX-Core-HD kernel. So seems like fastboot did not write anything at all.
I've tried flashtool with stock tft. It breaks with "final verification error", when i turn "final verification off" it goes all the way, says everything is installed, but when i restarted, still only Doomkernel.
Any ideas ? I take any advice.

Maybe you have already tried it, but format your phone's data, THEN the cache, and finally the internal storage (SD card). In XS's CWM, there's a bug, which causes sometimes an unformatable and unusable cache parition. But this method can be help on this. Maybe this problem causes those unformatable partitions.

Szatyor said:
Maybe you have already tried it, but format your phone's data, THEN the cache, and finally the internal storage (SD card). In XS's CWM, there's a bug, which causes sometimes an unformatable and unusable cache parition. But this method can be help on this. Maybe this problem causes those unformatable partitions.
Click to expand...
Click to collapse
Thank you for your reply. Haven't tried that but i have now and, unfortunately, no go. With /data and /cache seems like format was success but it didn't ( still can't Mount) and with /sdcard format fails (error mounting /sdcard).
Maybe my sdcard really died ?

qrto said:
Thank you for your reply. Haven't tried that but i have now and, unfortunately, no go. With /data and /cache seems like format was success but it didn't ( still can't Mount) and with /sdcard format fails (error mounting /sdcard).
Maybe my sdcard really died ?
Click to expand...
Click to collapse
Well, I don't think so. The "SD Card" is a part of the memory chip, which includes the system, the data and the cache partitions too. Because you cannot copy anything now to the internal storage, try to install a ROM from ADB Sideload if you can. Once it done, your phone can be boot maybe again. If it happens, try to format the internal storage by the Android. If it fails, connect the phone to your computer, and try to format with Windows or (it can be better) Linux to fat32 filesystem.

Szatyor said:
Well, I don't think so. The "SD Card" is a part of the memory chip, which includes the system, the data and the cache partitions too. Because you cannot copy anything now to the internal storage, try to install a ROM from ADB Sideload if you can. Once it done, your phone can be boot maybe again. If it happens, try to format the internal storage by the Android. If it fails, connect the phone to your computer, and try to format with Windows or (it can be better) Linux to fat32 filesystem.
Click to expand...
Click to collapse
Thank you for your ideas. Thing is, all i can start is cwm recovery. As i wrote, i can't install anything with sideload. And no partition is working. When i start parted /dev/block/mmcblk and try to list partitions, i get unrecognized disk label error, when i try to manually set disk label to msdos, there's I/O Error.
And i can't format sdcard, because when in recovery, phone is not detected by Linux nor Windows. But i tried formatting partitions internally, with mke2fs, and with fastboot command. No go.
I know that /sdcard is just a partition, but what i meant was that probably my phone memory chip died, like hardware died. but i'm still looking for new ideas i want to try everything before giving up.

qrto said:
Thank you for your ideas. Thing is, Alp i can start iż cwm recovery. As i wrote, i can't install anything with sideload. And no partition is working. When i start parted /dev/block/mmcblk and try to list partitions, i get unrecognized disk label error, when i try to manually set disk label to msdos, there's I/O Error.
And i can't format sdcard, because when in recovery, phone is not detected by Linux nor Windows. But i tried formatting partitions internally, with mke2fs, and with fastboot command. No go.
I know that /sdcard is just a partition, but what i meant was that probably my phone memory chip died, like hardware died. but i'm still looking for new ideas i want to try everything before giving up.
Click to expand...
Click to collapse
Then maybe it's a HW error really. But maybe just the partition table is corrupted. At this point, I don't know. I have only one suggestion left: Take the phone to the nearest SONY Center or GSM shop/service to investigation. But I think they will say you'll need to replace the phone's motherboard. Anyway, it's an too expensive solution I think, because this phone is a "retired" modell without any update, but with a "blacksheep (Snapdragon S3) SoC.

[Q] Bricked Ascend P6-U06

Hello there,
I made the mistake of wiping the internal storage using TWRP.
I am unable to enter recovery mode with the button hold options (tried all variations). The only way I was able to get into TWRP was adb reboot recovery. adb connection is now gone and the phone is stuck at the boot screen.
I can get a fastboot connection and the bootloader is unlocked. So I flashed the boot partition with a stock boot.img and the recovery partition with a stock recovery.img (even though I can't enter the recovery partition).
the phone never gets past the boot logo. Is there a way to directly flash a system.img vie fastboot, so that the device can be used? I am kind of stuck here.. read several threads for the past 2-3 hours, tried to reinstall TWRP as recovery but cant boot into it, etc.
I downloaded the B510.zip and was wondering if there is a way to burn an .img out of that and flash the system partition. But maybe that doesn't make sense at all.
Any help is greatly appreciated

update
Alright then, I managed to boot into TWRP!! a previous version worked.
it shows: Custom storage (498MB), Internal Storage (0MB), External Storage (0MB)
i am now proceding to install the zipped 510 rom from huawei. unfortunately i must have lost my microSD so i am lefti with sideload and otg.
sideload doesn't work because i can't find my device with adb. only fastboot seems to work, i dont know the reason but i understand its normal for my situation.
i only have an unpowered otg cable. from what i read that won't work, but I'm giving it a try and currently load the zip on a usb flashdrive.
do i understand correctly that the overall storage just appears to be 498MB? my partition table must be fairly messed up if that is the case. are there other partitions not shown by TWRP?
what do you recommend besides/instead of getting a microsd?
kind regards

update #2
I managed to mount the internal storage as mtp and copied the zip into the pictures folder, because i had no writing permission for the parent dir.
i tried to install, but the first time i got an error that cache could not be mounted. i cleared the dalvik cache and retried.
this time i had another error message as you can see in the screenshot.
adb still does not work, so sideload is not an option. i can also mount the custom partition but it is just under 500mb while the rom zip is 7xx mb
any help would be greatly appreciated

Resolved
I managed to solve it. Installed the paranoid android rom from the pictures dir. it was under 500mb and worked fine.

eyevector said:
I managed to mount the internal storage as mtp and copied the zip into the pictures folder, because i had no writing permission for the parent dir.
i tried to install, but the first time i got an error that cache could not be mounted. i cleared the dalvik cache and retried.
this time i had another error message as you can see in the screenshot.
adb still does not work, so sideload is not an option. i can also mount the custom partition but it is just under 500mb while the rom zip is 7xx mb
any help would be greatly appreciated
Click to expand...
Click to collapse
You cant install Huawei Firmware with TWRP! Only Repacked / Custom Roms.

thank you
RabbidZ said:
You cant install Huawei Firmware with TWRP! Only Repacked / Custom Roms.
Click to expand...
Click to collapse
so that is the reason why the paranoidandroid worked in the end.
cheers

Xperia M TWRP İnternal Storage 0 MB Problem!

Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.

didyou said:
Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.
Click to expand...
Click to collapse
Your device got ebola. There is no solution. Sorry mate.

Use internal storage 0 mb problem in TWRP Recovery. No flashing kernel and roms.

didyou said:
Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.
Click to expand...
Click to collapse
i am having same problem . but my internal storage is mounted as android os and my actual storage is not visible please help me.

fix for 0MB internal storage problem
Your device is still recoverable if you can boot into twrp successfully
Go to advanced --> terminal
Check your partition table with
fdisk -l /dev/block/mmcblk0
it will print out the partition table, last 3 should be system, cache and data
format system with ext4, for me that was /dev/mmcblk0p25 - YOURS MAY DIFFER
make_ext4fs /dev/block/mmcblk0p25
format data with ext4, for me that was /dev/mmcblk0p27
make_ext4fs /dev/block/mmcblk0p27
For me, this was met with errors, so format it with exfat first, mkfs.exfat /dev/mmcblk0p27, reboot into recovery, then format with make_ext4fs.
You cannot do this through advanced wipe, because twrp tries to guess your partitions AFTER mounting them, then reads /system is mounted on /dev/block/mmdblk0p25, but it's not mounted, so no repairing/formatting through that. Use the terminal instead, then reboot, twrp will find the partitions then.
afterwards reboot again into recovery. I didn't have to reformat cache, but you may have to. try mkfs.ext2 on that. You will always want to go with make_ext4fs though.
internal storage should show up again now, wiping and installing zips will work again.

rak-zero said:
Your device is still recoverable if you can boot into twrp successfully
Go to advanced --> terminal
Check your partition table with
fdisk -l /dev/block/mmcblk0
it will print out the partition table, last 3 should be system, cache and data
format system with ext4, for me that was /dev/mmcblk0p25 - YOURS MAY DIFFER
make_ext4fs /dev/block/mmcblk0p25
format data with ext4, for me that was /dev/mmcblk0p27
make_ext4fs /dev/block/mmcblk0p27
For me, this was met with errors, so format it with exfat first, mkfs.exfat /dev/mmcblk0p27, reboot into recovery, then format with make_ext4fs.
You cannot do this through advanced wipe, because twrp tries to guess your partitions AFTER mounting them, then reads /system is mounted on /dev/block/mmdblk0p25, but it's not mounted, so no repairing/formatting through that. Use the terminal instead, then reboot, twrp will find the partitions then.
afterwards reboot again into recovery. I didn't have to reformat cache, but you may have to. try mkfs.ext2 on that. You will always want to go with make_ext4fs though.
internal storage should show up again now, wiping and installing zips will work again.
Click to expand...
Click to collapse
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
https://imgyukle.com/i/Rk24Gt
https://imgyukle.com/i/Rk264c
https://imgyukle.com/i/Rk2fyR

didyou said:
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
Did you reboot after? You can try the advanced format in twrp, maybe you need to use exfat for your partition 27 (data) or ext3 not ext4 for system. Try some combinations.
Which twrp version is installed?
I checked mine and partitions 25 to 27 are formatted with ext4. I have latest twrp 3.0.2.0 and use lineage 14.1. from here.
Partition table looks fine, same sizes as me.
Click to expand...
Click to collapse

rak-zero said:
didyou said:
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
Did you reboot after? You can try the advanced format in twrp, maybe you need to use exfat for your partition 27 (data) or ext3 not ext4 for system. Try some combinations.
Which twrp version is installed?
I checked mine and partitions 25 to 27 are formatted with ext4. I have latest twrp 3.0.2.0 and use lineage 14.1. from here.
Partition table looks fine, same sizes as me.
Click to expand...
Click to collapse
I am using TWRP version 3.1.1.0. I tried to make Wipe after it restarted after operations but it still seems to be 0MB. I tried to change the file system, but not through the terminal.
Click to expand...
Click to collapse