Develop Bugs

[Q] emmc partion fix ......maybe?

I was doing some research on the emmc partion s on the g2 and desire z seems that some issues with the sd card not showing up and the usb bricks have a part in the emmc partion fies being corrupt if yu can still boot up into your phone while being s-on and un rooted or s-on and temp rooted with a factory recovery. Witch is my case...lol but I came a cross this tool that supports are emmc and cpu. At this site but I'm not to sure how to use it but supposidly it can copy or creat a new emmc partion if you have the correct files and flash them to correct your corupped emmc partions if you haven't completey fried it that is. But here's the link check it out and let me know what you think http://faq.riffbox.org/index.php?action=artikel&cat=10&id=53&artlang=en. And sorry if this has been posted/found be for but here it is if any body knows how to use it let me kno. As I want to give it a try to fix my sdcard brick...

This plugin may be useful, if somebody totally broken eMMC partition map (if it is possible) or if the device has a corruped HBOOT or radio and it is totally bricked (fails even start to boot).
If you device boots and you are not advanced hardware hacker, it is nothing for you.
The plugin is intended for JTAG manager. If you think you broken something mentioned above, then buy JTAG programmer hardware, disassemble your phone, connect JTAG cable and fix it.
Note: Repartitioning eMMC is a dangerous operation! Some operations are once-per-lifetime! And you will not be able to flash any of standard images.

Yes that is very true but if you read it very carfully it says you can use a jtag but it is also compatible for using it via usb cable....put I think there's apart of my emmc partion that is corrupted. But not really sure my phone boots up fine just I have access to my sdcard or access to my sdcard via usb to computer but I have access through adb and fastboot ...so not really sure if the emmc partion has any thing to. Do with how the phone mounts or reads the sdcard....but I had in my other post that wen I was on froyo in my storage settings I didn't have any access to select the mount sdcard or erase sdcard option but after I did the ota to ginger bread wich was a dumb idea to do but I was thinking it would fix that problem witch it kinda did as in my storage setting I can now select the erase sdcard option but the option to mount the sdcard is still greyed out unselectable....so I think it has a corrupted partion somwere if the emmc controls these settings

OK, they mention USB as well.
However I think, that your problem is not eMMC partitioning, but data in your partitions: bad system, kernel or so. If you want, you can probably flash using this utility. But if your system is not totally bricked, you can flash comfortably with standard tools - adb, bootloader, recovery.

Yea I thought so but I don't really know what I would need to flash to fix it unless its the misc.img or mtd0.img I have tryed and every time I do I get a failed error unless I try to just copy them to the proc directory and rewrite. Over the old ones yu think that mite help then just reboot the phone after I use adb to push to that directory so it would be like adb push misc to proc/misc/ then adb push mtd0.img /proc/mtd0

Also wen I go to rcovery through hboot select recovery hold vol up +power I get this error e:can't mount/ cache/command

ari3z said:
Also wen I go to rcovery through hboot select recovery hold vol up +power I get this error e:can't mount/ cache/command
Click to expand...
Click to collapse
Maybe you have corrupted cache partition. If you have a working system, please try Factory reset from the Android system menu.

Yea IV Trudy that its a no go...maybe it is a corrupted partion ....misc or mtd0 culd be any thing. Butvmy guess is what ever partion that controls the way the system scans. And controls the sdcard and usb storage controller is f3$k up....

[MOD] Alternative Partitioning Layout/Method for ODROID U2

I'm currently compiling Android (CM10.1 to be specific) for my ODROID to finish this mod, but it's 90% working and I'll give you details on what I have done.
Basically, the current partition layout on the ODROID is fine, but it's an old fashioned way of handling things, and it's awkward to update kernels (you have to use dd to a set position on the eMMC/SD card to flash it onto the eMMC). What I wanted to do was make the ODROID either have dedicated kernel/ramdisk partitions (similar to Android phones), or alternatively use a boot partition (similar to Linux desktops with /boot containing vmlinuz and initrd etc). It's really not that hard at all to pull this off with the ODROID being so easy to work with (eMMC removable, boot from SD, U-Boot, etc), but I'll run you through what I've had to do and try to go through it in further detail once I've finished the process, and probably upload some binaries so people can try it on their own device.
Note, I'm doing this on an SD card rather than my eMMC so I don't mess with my main Android system on it. I recommend you do this as well until you have it sorted. Also note I am doing this under Linux as Windows requires cygwin to do all this, and cygwin is a pain to tell people how to set it up. Basically, if you don't have Linux, then use Virtual Box and Ubuntu in it or something. It'll be way easier in the long run.
Delete all the partitions on the SD card. Use fdisk /dev/sdb (or whatever the device is for your SD card - I did this on my laptop which has an SD card reader and also a USB SD card reader and they both detect as sdb. Do cat /proc/partitions to see which is your SD card (obviously if you have a 4GB card, then it'll be the device that's 4GB in size).
Prepare your SD card with the ODROIDs bootloaders (BL1/2, U-Boot and Trustzone). I got this in the BSP that Hardkernel provides on their download page, but I'll put it in a smaller package when I make it.
The script flashes BL1, then BL2 at the end of it, then U-Boot, then Trustzone all appended after each other and it will do this with dd if=x.img of=/dev/sdb skip=x, etc.
Create your new partition table on the SD card. This part is awkward because we have the bootloaders at the start of the device, and I'm pretty sure U-Boot wants some space left at the end where it can save its environment settings/variables, so I left 5-10MB at the start of the card for U-Boot. The rest of the space is entirely up to you on how you want it to work, but I did a 50MB boot partition in FAT32 (you could do EXT2, U-Boot should support that too), 512MB for /system (that's about the size of it on my Galaxy S2 and my Nexus 7), 128MB for cache and the rest of the 4GB SD card for data, so 3ish GB for data and media. On a 16GB eMMC you'd effectively have 14-15GB of space for applications and media rather than having it split into 2GB and 12GB or something.
If you really want you can do an SD card partition and do it the old fashioned way, and it won't require a new version of Android, but I wanted to do more work.
When I made the partition table, I made the 50MB boot partition as a primary partition (sdb1) and then made a logical partition (sdb4) in which I made 3 logical partitions (sdb5/6/7) for system/cache/data. I did it that way so that I'm not at the limit of what the MBR partition table supports.
Make the filesystems on the partitions, so mkfs.vfat /dev/sdb1, mkfs.ext4 /dev/sdb5 etc.
Copy your kernel in its raw zImage format and ramdisk image to the boot partition, can call them kernel and ramdisk.img respectively (or whatever you like, I don't care)
Put the SD card in the device with your eMMC in there as well and boot the ODROID, or put the eMMC in your computer with your SD card
Mount the SD card and eMMC
Copy the system partition from the eMMC to the SD card (so if you do this on the ODROID, you will do cp -prf /system/* /mnt/tmp (assuming you mounted the SD card on /mnt/tmp)
Turn off the ODROID and remove the eMMC
Connect the ODROID to UART and turn it on. Provided you haven't mucked up the bootloader by not skipping the first 10MB of the card it should start to boot to U-Boot. You want to stop it and get to the prompt on U-Boot.
In the prompt, we need to change the default_bootcmd. This is the command that U-Boot falls back to if it can't find any boot scripts. You can edit bootcmd, but I don't recommend it. It's best to leave the bootscript functionality there for future endeavours. I changed it to this: "fatload mmc 0:1 40008000 kernel;fatload mmc 0:1 41000000 ramdisk.img;bootm 40008000 41000000". That will load the kernel from partition 1 (boot partition) on MMC 0 and then load ramdisk.img from it. You can change those filenames if you changed the filenames when putting them on the device.
Save the environment in U-Boot (saveenv) and reset the device (reset).
Provided all goes well, the device should load the two images and start booting Android.
You'll need to edit the ramdisk (the fstab specifically) to make it work with the new partitions, and if you went with a /data/media partition like I suggested, you will need to modify the storage_list.xml in the framework overlay in the Android source code and recompile it. As I said, I'll make binaries if you don't know how to do that.
Hopefully my information is clear enough for other people to understand what I'm doing here. If not then ask and I'll try to clarify it.
On a side note: will XDA ever have an ODROID U2 section? It has a Ras Pi section, so I feel that an ODROID U/U2 section is in order.

Would this work for creating a dedicated recovery partition also?

brando56894 said:
Would this work for creating a dedicated recovery partition also?
Click to expand...
Click to collapse
You can just put a recovery image on the boot partition, so yes.

[Instructions included] Need Internal Partitions (mmcblk0p1 to mmcblk0p5)

I've been trying to partition my External SD card so I can use it for Link2SD. I don't have an SD card reader so I tried using the adb + parted command. I was following this tutorial but then I realised that /dev/block/mmcblk0 was my Internal Storage and not my external SD. I deleted the first 5 partitions on there and my phone isn't charging nor turning on even though it's fully charged. Have I completely broken my phone?
Edit: phone shows up as QHSUSB_BULK in device manager.
Could someone please upload the first 5 partitions as imgs? I'm trying to use Ubuntu to try and replace the partitions I deleted. I'm running 4.16.1540.8 as my firmware and CM12 nightlies.
Use this command to save partitions as imgs on SD.
dd if=/dev/block/mmcblk0p5 of=/sdcard/dump/mfg.img
Just replace the mmc number with 1,2,3,4,5 and the image name to something that lets me know which partition it's on.
Thanks

bump

did you have any joy getting the mmcblk0 and if so can you upload it please

How to repair system partitions

Hi everyone, after trying to repair my phone without results (see http://forum.xda-developers.com/ascend-p6/help/flash-wipe-restore-t3096086) the conclusion is: 1 my emmc internal storage is broken/damaged or 2 my system partition is corrupted (because i can't write or flash anything via root explores, via twrp and via fastboot). I hope the second option. How can i repair the corrupted partitions? thank's everybody, and sorry for bad english

maicolboss said:
Hi everyone, after trying to repair my phone without results (see http://forum.xda-developers.com/ascend-p6/help/flash-wipe-restore-t3096086) the conclusion is: 1 my emmc internal storage is broken/damaged or 2 my system partition is corrupted (because i can't write or flash anything via root explores, via twrp and via fastboot). I hope the second option. How can i repair the corrupted partitions? thank's everybody, and sorry for bad english
Click to expand...
Click to collapse
please someone help me to know if my phone is hard bricked or not

*
Can someone answer this question so i can fix my old tablet, i completely destroyed my /system
Partition and i need to know if i will still be able to use recovery mode and if a factory reset will fix it or if i have to delete it and put a new one on from a backup of it on my flash drive.
I had root but the app for that was on the system partition so i might not have root anymore until it is fixed.
Tablet is a ematic egm 002 (old)

Boot from SD card *ONLY* (all partitions) ?

Hi,
My LG G3 d855 has fried, the flash chip looks dead (unable to flash new system partition, when I try the dmesg from the recovery kernel shows error from the flash chip).
So now I'd like to know if it's possible to install everything on the SD card and boot from there. I already made a copy of all the partitions (I can still read from the flash), the /system partition is unusable but all the other ones look good.
Has anyone tried that ? Or does anyone have an idea where I could stick some boot arguments to make it work ?