Related
Disclaimer: I am not responsible for bricked devices, dead SD cards, thermonuclear war, or anything else. YOU doing this at your own risk.
This guide is taken from 4pda.ru forums and tested on my own device.
I strongly recommend you to make Nandroid backup with CWM Recovery v6.0.3.0 so after repartitioning ALL DATA (/system, /system1, /data, /cache) WILL BE ERASED.
1. Connect you phone to PC via USB. (USB debugging must be turned on)
2. Install MiFlash. Remember installation path. It will install drivers for "Android Composite ADB Device". If there's still one "Android" device without drivers - just ignore.
3. Run Command Prompt (cmd) and go to the %FOLDER_WHERE_YOU_INSTALLED_MIFLASH%\Google\Android (For me it was C:\Program Files (x86)\Xiaomi\MiPhone\Google\Android)
4. Type adb devices and press enter. It should start adb daemon and show your device with status offline. Check phone for dialog and allow USB debug from your computer.
5. Type adb devices again. Now it should show your phone with status device. Close Command Prompt.
6. Download and unpack to any folder attached archive tadb.zip
7. Run tadb shell.bat. If everything fine it will show something like "[email protected]:/ $"
9. Type su and press enter. If requested allow root access on phone.
10. Now enter busybox fdisk /dev/block/mmcblk0 to start repartiotioning program (All changes are virtual until written)
11. Delete all partitions from 20 to 15 inclusive. For this enter d, enter 20, enter d, enter 19 till 15th partition.
After this enter p. Your partition table must be like this
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 12801 102400 c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 12801 12863 500 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 12863 13051 1500 51 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 13051 488448 3803183+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 13052 13114 500 47 Unknown
/dev/block/mmcblk0p6 13114 13370 2048 45 Unknown
/dev/block/mmcblk0p7 13370 13683 2500 4c Unknown
/dev/block/mmcblk0p8 13683 14963 10240 48 Unknown
/dev/block/mmcblk0p9 14963 16243 10240 64 Unknown
/dev/block/mmcblk0p10 16243 16305 500 46 Unknown
/dev/block/mmcblk0p11 16305 16368 500 65 Unknown
/dev/block/mmcblk0p12 16385 16768 3072 4a Unknown
/dev/block/mmcblk0p13 16769 17152 3072 4b Unknown
/dev/block/mmcblk0p14 20481 20864 3072 58 Unknown
12. Recreate needed partitions table. Press n, enter start block, end block. You can use attached partitions.xls to calculate needed values. Also You can change size of system partitions in this file as you wish (Make them 384Mb for example). Values will be recalculated.
13. Now we must return System type for 17th block (recovery). Enter t, enter 17, enter 60. After this operation your partiotion table will be like this (If you left 256Mb):
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 12801 102400 c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 12801 12863 500 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 12863 13051 1500 51 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 13051 488448 3803183+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 13052 13114 500 47 Unknown
/dev/block/mmcblk0p6 13114 13370 2048 45 Unknown
/dev/block/mmcblk0p7 13370 13683 2500 4c Unknown
/dev/block/mmcblk0p8 13683 14963 10240 48 Unknown
/dev/block/mmcblk0p9 14963 16243 10240 64 Unknown
/dev/block/mmcblk0p10 16243 16305 500 46 Unknown
/dev/block/mmcblk0p11 16305 16368 500 65 Unknown
/dev/block/mmcblk0p12 16385 16768 3072 4a Unknown
/dev/block/mmcblk0p13 16769 17152 3072 4b Unknown
/dev/block/mmcblk0p14 20481 20864 3072 58 Unknown
/dev/block/mmcblk0p15 20866 53633 262144 83 Linux
/dev/block/mmcblk0p16 53635 86402 262144 83 Linux
/dev/block/mmcblk0p17 86404 87683 10240 60 Unknown
/dev/block/mmcblk0p18 87685 88708 8192 83 Linux
/dev/block/mmcblk0p19 88710 111749 184320 83 Linux
/dev/block/mmcblk0p20 111751 488448 3013584 83 Linux
14. Time to save changes. If you not sure, you can just enter q to leave without saving changes. Enter w to write new partition table. Program will show error about using old partition table - that's normal. After you reboot phone - changes will be applied, so it will not load anything except fastboot.
15. Load phone in fastboot mode (Power + Volume Down + Mi-Button), go to folder with tadb and run flash_recovery.bat. It will flash CWM 6.0.3.0 to your device.
16. Go to mounts & storage menu and format /cache, /system, /system1 and /data
17. Now you can restore your nandroid backup.
NOTE: All operations been made on Windows 7 32-bit and Xiaomi Mi-One Plus with MIUIv5 3.7.19
Waiting for move to right forum section. Report sent.
What is the point to do all these? Are some benefits from this change?
dancer_69 said:
What is the point to do all these? Are some benefits from this change?
Click to expand...
Click to collapse
Some custom ROMS (MoKee OS for example) have very few free space in /system after installation. Not enough even to flash GApps.
Yes, I know about that but there is already a tool for repartition. I thought that this was more than that. It' s nice that you can customise the size though. But isn't dangerous? I'm saying this because I've hard break my device twice using gparted. I had a full linux backup of device though so I recovered it but was the only way to do it. I succeed once though.
What's the name of the repartition tool? I'm caught in a wicked cloning loop that duplicates my partitions periodically and I haven't tracked down the cause. Ota JB Feb. 1st is the day it started. Thanks
A Charge of $17.99 Was Applied To Your Mobile Account For Browbeating The Author's Questions. Albeit, Most Likely a Foolish, Ignorant, Uneducated Compilation of Useless Quibble. But He Is Less Than 1 Year With Me and Is Bashing Adb, Scripting, Rooting, Romming Like a Red Headed Stepchild With No Thumbs, Herpes Type 4.2.2. Flashaholicism! Give My Poor TTS Owner A Hand Would ya? Sent From His Overclocked Porn Providing ClapaTalk Razr Maxx Xt-912.
I mean Genocolar' s and Forumber' s update zips for repartition.
dancer_69 said:
I mean Genocolar' s and Forumber' s update zips for repartition.
Click to expand...
Click to collapse
Can you give links to them?
Here is the topic:
http://forum.xda-developers.com/showthread.php?t=1112857&highlight=partition
As for Forumber' s modified way to larger /system, search on U8800 developing section, it' s in a lot roms threads.
just a note:
On M1S phones the last END block is 477184 and not 488448 like M1+ and M1 C1
all is equal except that
So M1S users take in mind when repartitioning your phones.
ehrans said:
just a note:
On M1S phones the last END block is 477184 and not 488448 like M1+ and M1 C1
all is equal except that
So M1S users take in mind when repartitioning your phones.
Click to expand...
Click to collapse
Well, when creating last partition (/data) you can just hit Enter when prompted for last END block to use Default value. I think tadb automatically will use 477184 instead of 488448 for M1S. Not sure.
i dont know if this its related but here it seems that there are a easier method to change the size
the author have it set on 280mb but it could be increased
link: miui.es/index.php/topic,7965.0.html
eilegz said:
i dont know if this its related but here it seems that there are a easier method to change the size
the author have it set on 280mb but it could be increased
link: miui.es/index.php/topic,7965.0.html
Click to expand...
Click to collapse
yes, is my tutorial for an automated way to do the changes from a recovery instalable .zip
just download, flash a compatible recovery (any cwm with busybox for M1/S should work) then install the zip for ur phone model.
eilegz said:
i dont know if this its related but here it seems that there are a easier method to change the size
the author have it set on 280mb but it could be increased
link: miui.es/index.php/topic,7965.0.html
Click to expand...
Click to collapse
You can restore a broken link?
r.dave said:
You can restore a broken link?
Click to expand...
Click to collapse
check your pm
Could somebody refresh link for instalable.zip ?
thx
thankyou
All important information/ links will be moved to an INFO thread, since this is a question thread, we do not need it anymore.
Still looking.
Bump, can anyone help?
Saw this page:
forum.xda-developers .com/showthread.php?t=1959445
Was wondering if it's worth a shot.
Kernel released by Huawei.
For kernel/Rom Developers, Huawei has released the kernel for the Huawei Prism II online.
Attached is a notepad document with the links in them, since I am not allowed to post links. I apologize for the inconvenience.
ALSO
For anyone else with a Huawei device that has not released their kernel, I used the email format below:
Emal 1:
I would like the source code for my phone that is available to me. I am an android developer, and it would be useful to me if I have the
source code(that is offerred by Huawei).
The reply you will get:
Dear Customer,
Thank you for contacting Huawei device. The open source is under our technical department to make. Since the procedure is a little more complex, so please kindly be a little patient. We will keep you informed once available.Once again thank you for contacting Huawei device.
Best Regards.
Huawei Device Customer Care Team.
Give them 2-3 days, then E-mail once again! Be persistent!
2nd email:
Any new information about the source code?
The reply I got:
Dear Customer,
Thank you for contacting Huawei device. Please kindly check the source code link for your reference:
(link given above)
Once again thank you for contacting Huawei device.
Best Regards.
Huawei Device Customer Care Team.
Parted/FDisk Output on /dev/block/mmcblk0
streetdev22 said:
Bump, can anyone help?
Saw this page:
forum.xda-developers .com/showthread.php?t=1959445
Was wondering if it's worth a shot.
Click to expand...
Click to collapse
Tried the guide on my Prism II. Parted gave me an error. Possible reason for parted error is explained here: http://forum.xda-developers.com/showthread.php?t=2169709.
However, fdisk worked, but it doesn't clearly identify the partitons:
Edited to include gdisk output
parted:
Code:
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: Unable to satisfy all constraints on the partition.
fdisk:
Code:
[email protected]:/ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes
1 heads, 16 sectors/track, 477184 cylinders
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 477184 3684031+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 16897 18432 12288 6a Unknown
/dev/block/mmcblk0p6 18433 18944 4096 46 Unknown
/dev/block/mmcblk0p7 18945 19456 4096 63 GNU HURD or SysV
/dev/block/mmcblk0p8 19457 19840 3072 58 Unknown
/dev/block/mmcblk0p9 19969 20352 3072 4a Unknown
/dev/block/mmcblk0p10 20481 20864 3072 4b Unknown
/dev/block/mmcblk0p11 20993 21504 4096 47 Unknown
/dev/block/mmcblk0p12 21505 22528 8192 48 Unknown
/dev/block/mmcblk0p13 22529 25088 20480 60 Unknown
/dev/block/mmcblk0p14 25089 25600 4096 6c Unknown
/dev/block/mmcblk0p15 25601 50176 196608 83 Linux
/dev/block/mmcblk0p16 50177 60416 81920 83 Linux
/dev/block/mmcblk0p17 60417 191488 1048576 83 Linux
/dev/block/mmcblk0p18 191489 338944 1179648 83 Linux
/dev/block/mmcblk0p19 338945 477184 1105920 6b Unknown
gdisk:
Code:
[email protected]:/ # gdisk -l /dev/block/mmcblk0
gdisk -l /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************
Exact type match not found for type code 4D00; assigning type code for
'Linux filesystem'
Exact type match not found for type code 4500; assigning type code for
'Linux filesystem'
Exact type match not found for type code 6A00; assigning type code for
'Linux filesystem'
Exact type match not found for type code 4600; assigning type code for
'Linux filesystem'
Exact type match not found for type code 6300; assigning type code for
'Linux filesystem'
Exact type match not found for type code 5800; assigning type code for
'Linux filesystem'
Exact type match not found for type code 4A00; assigning type code for
'Linux filesystem'
Exact type match not found for type code 4B00; assigning type code for
'Linux filesystem'
Exact type match not found for type code 4700; assigning type code for
'Linux filesystem'
Exact type match not found for type code 4800; assigning type code for
'Linux filesystem'
Exact type match not found for type code 6000; assigning type code for
'Linux filesystem'
Exact type match not found for type code 6C00; assigning type code for
'Linux filesystem'
Exact type match not found for type code 6B00; assigning type code for
'Linux filesystem'
Warning! Main partition table overlaps the first partition by 33 blocks!
You will need to delete this partition or resize it in another utility.
Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/block/mmcblk0: 7634944 sectors, 3.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): E271C8D6-2001-435D-A466-BEFE7ED158CD
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 7634910
Partitions will be aligned on 1-sector boundaries
Total free space is 9599 sectors (4.7 MiB)
Number Start (sector) End (sector) Size Code Name
1 1 40 20.0 KiB 8300 Linux filesystem
2 41 640 300.0 KiB 8300 Linux filesystem
3 641 266880 130.0 MiB 0700 Microsoft basic data
5 270336 294911 12.0 MiB 8300 Linux filesystem
6 294912 303103 4.0 MiB 8300 Linux filesystem
7 303104 311295 4.0 MiB 8300 Linux filesystem
8 311296 317439 3.0 MiB 8300 Linux filesystem
9 319488 325631 3.0 MiB 8300 Linux filesystem
10 327680 333823 3.0 MiB 8300 Linux filesystem
11 335872 344063 4.0 MiB 8300 Linux filesystem
12 344064 360447 8.0 MiB 8300 Linux filesystem
13 360448 401407 20.0 MiB 8300 Linux filesystem
14 401408 409599 4.0 MiB 8300 Linux filesystem
15 409600 802815 192.0 MiB 8300 Linux filesystem
16 802816 966655 80.0 MiB 8300 Linux filesystem
17 966656 3063807 1024.0 MiB 8300 Linux filesystem
18 3063808 5423103 1.1 GiB 8300 Linux filesystem
19 5423104 7634943 1.1 GiB 8300 Linux filesystem
[email protected]:/ #
Partition Layout
streetdev22 said:
Recently rooted and unlocked the bootloader on my Huawei Prism II, but there is no custom recovery nor custom roms for this phone. I have tried determing the partition layout in order to dump the recovery, but I am unable to do so.
Tried earlier versions of romdump, but they returned with a segmentation failure.
Click to expand...
Click to collapse
I believe I've found the partition layout based on the /etc/recovery_mmc.fstab extracted from mmcblk0p13, but am not sure. The excerpt of my /etc/recovery_mmc.fstab file from mmcblk0p13 shows some partition names correlated to device names. Could someone verify this is a legitimate way to determine the partition layout? I've also attached the whole recovery_mmc.fstab file.
recovery_mmc.fstab excerpt:
Code:
/boot emmc /dev/block/mmcblk0p12
/cache ext4 /dev/block/mmcblk0p15
# /* < DTS2012062603367 lizhigang 20120626 begin */
/data ext4 /dev/block/mmcblk0p18 length=-16384
#/* < DTS2012062603367 lizhigang 20120626 end */
/recovery emmc /dev/block/mmcblk0p13
/misc emmc /dev/block/mmcblk0p7
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p17
/sys_boot vfat /dev/block/mmcblk0p3
/fat vfat /dev/block/mmcblk0p3
/HWUserData vfat /dev/block/mmcblk0p19
#/*< DTS2012020804291 weizhonghui 20120208 begin */
/cust ext4 /dev/block/mmcblk0p16
#/* DTS2012020804291 weizhonghui 20120208 end >*/
#/* DTS2012011906026 chendeng 20120120 end > */
# /* DTS2012031506621 lishubin 20120321 end > */
Easier to read (joined fdisk and the recovery_mmc.fstab)
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 3 20 4d Unknown /sdcard
/dev/block/mmcblk0p2 3 41 300 45 Unknown
/dev/block/mmcblk0p3 41 16681 133120 c Win95 FAT32 (LBA) /sys_boot and /fat
/dev/block/mmcblk0p4 16681 477184 3684031+ 5 Extended
/dev/block/mmcblk0p5 16897 18432 12288 6a Unknown
/dev/block/mmcblk0p6 18433 18944 4096 46 Unknown
/dev/block/mmcblk0p7 18945 19456 4096 63 GNU HURD or SysV /misc
/dev/block/mmcblk0p8 19457 19840 3072 58 Unknown
/dev/block/mmcblk0p9 19969 20352 3072 4a Unknown
/dev/block/mmcblk0p10 20481 20864 3072 4b Unknown
/dev/block/mmcblk0p11 20993 21504 4096 47 Unknown
/dev/block/mmcblk0p12 21505 22528 8192 48 Unknown /boot
/dev/block/mmcblk0p13 22529 25088 20480 60 Unknown /recovery
/dev/block/mmcblk0p14 25089 25600 4096 6c Unknown
/dev/block/mmcblk0p15 25601 50176 196608 83 Linux /cache
/dev/block/mmcblk0p16 50177 60416 81920 83 Linux /cust
/dev/block/mmcblk0p17 60417 191488 1048576 83 Linux /system
/dev/block/mmcblk0p18 191489 338944 1179648 83 Linux /data
/dev/block/mmcblk0p19 338945 477184 1105920 6b Unknown /HWUserData
Very nice!
Correlates with the hints found in other files as seen above, so I think we have successfully found the partition layout! I will take a look when my device gets here(originally was working on my relative's phone, but now I purchased it for myself). If this method is confirmed,we can to port CWM, thank you all!! After CWM, we should be able to make custom ROMs freely.
streetdev22 said:
Correlates with the hints found in other files as seen above, so I think we have successfully found the partition layout! I will take a look when my device gets here(originally was working on my relative's phone, but now I purchased it for myself). If this method is confirmed,we can to port CWM, thank you all!! After CWM, we should be able to make custom ROMs freely.
Click to expand...
Click to collapse
Great. I'm glad that someone can verify part of the partition layout. Hopefully, this means that the new information is credible too.
Prism 2 said:
Great. I'm glad that someone can verify part of the partition layout. Hopefully, this means that the new information is credible too.
Click to expand...
Click to collapse
How exactly did you extract the file? Did you extract it from mmcblk0p13? Have the device on hand, so I am trying to verify the findings.
Thanks.
Unpacking Recovery Image
streetdev22 said:
How exactly did you extract the file? Did you extract it from mmcblk0p13? Have the device on hand, so I am trying to verify the findings.
Thanks.
Click to expand...
Click to collapse
First, I made a selective backup using a google store app called Online Nandroid Backup https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup&hl=en to make a backup on the "recovery" partition. Even though the app does not specify which block it copies, I believe the app makes a backup of /dev/block/mmcblk0p13 because it uses /system/partlayout4nandroid to determine the partition layout. If you look at the "cat /system/partlayout4nandroid" output below, you'll see that mmcblk0p13 corresponds to recovery.
Then I transferred the recovery.img from the sdcard to my computer.
From there, I followed the directions in Step 1 and Step 2 of http://www.imajeenyus.com/computer/20130301_android_tablet/android/unpack_repack_recovery_image.html to unpack and extract recovery.img.
Online Nandroid Backup Partition Layout:
Code:
[email protected]:/ # cat /system/partlayout4nandroid
cat /system/partlayout4nandroid
dev: size erasesize name
mmcblk0p1: 010000 000000 "modem"
mmcblk0p2: 000008 000000 "ssd"
mmcblk0p3: 000080 000000 "sbl1"
mmcblk0p4: 000100 000000 "sbl2"
mmcblk0p5: 000200 000000 "sbl3"
mmcblk0p6: 000200 000000 "aboot"
mmcblk0p7: 000200 000000 "rpm"
mmcblk0p8: 000200 000000 "tz"
mmcblk0p9: 002800 000000 "pad"
mmcblk0p10: 000c00 000000 "fsg"
mmcblk0p11: 002000 000000 "persist"
mmcblk0p12: 002800 000000 "boot"
[B]mmcblk0p13: 002800 000000 "recovery"[/B]
mmcblk0p14: 0b8000 000000 "system"
mmcblk0p15: 0d0000 000000 "cache"
mmcblk0p16: 000c00 000000 "modemst1"
mmcblk0p17: 000c00 000000 "modemst2"
mmcblk0p18: 040000 000000 "tombstones"
mmcblk0p19: 000400 000000 "misc"
mmcblk0p20: 001000 000000 "logo"
mmcblk0p21: 001000 000000 "logo2"
mmcblk0p22: 54c000 000000 "userdata"
mmcblk0p23: 00ffef 000000 "grow"
[email protected]:/ #
Probably correct.
My father(the owner of the phone) has once again left on a trip, so I will have to wait until Monday/Tuesday, when I receive my phone, to confirm these results.
My only issue with this is is why nandroid shows a different partition layout then what is shown in other files.
If partition 13 is recovery, there is no coincidence that you would find that fstab file in the extracted recovery.
Do you mind dumping all the extracted files from the recovery and uploading them to 4shared, mediafire, or any other cloud service as a compressed file(zip, tar)? I think the file is not coincidental, and that we have indeed found the partition layout(or at least the important partitions for our purposes).
Also, try dumping the boot partition that is currently identified (block 12) without using online nandroid backup(I think via dd should still work) and see if you can find similar files to that explained in the guide(.png, ramdisk directory, etc). If these files match up to what would be typically found in a boot.img or recovery.img, then the layout is most likely correct.
If these files match up to typical boot.img or recovery.img files, we can test the layout by changing something simple like a background before working on serious stuff.
Also, thanks for helping! Once we conclusively identify that this partition layout is correct, we can start to port clockworkmod.
streetdev22 said:
My father(the owner of the phone) has once again left on a trip, so I will have to wait until Monday/Tuesday, when I receive my phone, to confirm these results.
My only issue with this is is why nandroid shows a different partition layout then what is shown in other files.
If partition 13 is recovery, there is no coincidence that you would find that fstab file in the extracted recovery.
Do you mind dumping all the extracted files from the recovery and uploading them to 4shared, mediafire, or any other cloud service as a compressed file(zip, tar)? I think the file is not coincidental, and that we have indeed found the partition layout(or at least the important partitions for our purposes).
Also, try dumping the boot partition that is currently identified (block 12) without using online nandroid backup(I think via dd should still work) and see if you can find similar files to that explained in the guide(.png, ramdisk directory, etc). If these files match up to what would be typically found in a boot.img or recovery.img, then the layout is most likely correct.
If these files match up to typical boot.img or recovery.img files, we can test the layout by changing something simple like a background before working on serious stuff.
Also, thanks for helping! Once we conclusively identify that this partition layout is correct, we can start to port clockworkmod.
Click to expand...
Click to collapse
The extracted files in partition 13 can be found in post #44 of http://forum.xda-developers.com/showthread.php?t=2546455&page=5 labeled as "ramdisk.tar.bz2". I will make a dump of the boot partition using dd and run the tests tomorrow.
Looks validated, Also more tools
There are other guides on the matter of porting cyanogenmod..for example
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
which even mentions a recovery.fstab file in recovery.img! So, that means the partition layout in the fstab file you found is most likely correct.
Another guide:
http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
Also, there is an automated tool to porting cyanogenmod for new devices..
http://builder.clockworkmod.com/ (I would recommend avoiding the touch recovery for now, simple is all we need and we don't need more complications)
I am really feeling pretty confident about the partition layout found in the recovery.fstab, because one guide mentions it to be found in the recovery.img!
I would recommend making the changes to a recovery.img instead, because boot.img is still kinda scary (possible bricking )
Also, I think there is a command to try booting from a recovery.img without flashing the .img to the actual partition.
I think the command is mentioned here: http://forum.xda-developers.com/showthread.php?t=2233477
fastboot boot recovery.img is the command and it will not overwrite your existing recovery.
By using this command, you can try booting the stock recovery you extracted(to validate that we have a stock recovery available if we need it), and then boot the recovery.img you make with small edits, and then boot the recovery.img made from the automated CWM porter.
Thank you for replying so fast! We have made real progress in the last few days.
Edit:In the ramdisk that was extracted, another fstab exists on the root of the directory that is named fstab.msm7627, which is the same name from the file I located in post 1! They are the same file! I think this is validated.
Testing Recovery Partition
streetdev22 said:
I would recommend making the changes to a recovery.img instead, because boot.img is still kinda scary (possible bricking )
Also, I think there is a command to try booting from a recovery.img without flashing the .img to the actual partition.
I think the command is mentioned here: http://forum.xda-developers.com/showthread.php?t=2233477
fastboot boot recovery.img is the command and it will not overwrite your existing recovery.
By using this command, you can try booting the stock recovery you extracted(to validate that we have a stock recovery available if we need it), and then boot the recovery.img you make with small edits, and then boot the recovery.img made from the automated CWM porter.
Click to expand...
Click to collapse
I've made
a regular recovery.img using "dd if=/dev/block/mmcblk0p13 of=/sdcard/recovery.img" to make a copy of the recovery partition
a test recovery.img that is the same in every way to the original recovery.img except that all the images under /res/images is rotated 90 degrees. You can see the difference yourself by looking in res.rar attached below.
a clockworkmod recovery image from the clockworkmod recovery builder website
These images can be found attached below:
recovery.rar = original Huawei recovery image
recovery-test.rar = edited recovery image
recovery.img = clockworkmod recovery automatic builder image from http://jenkins.cyanogenmod.com/job/recovery/52069/
Unfortunately, I cannot test this image myself, because I do not want to unlock my bootloader yet.
If anyone with a rooted, unlocked Huawei Prism 2 is interested in helping to further the development of recovery roms for the Prism 2, I have made 3 tests to see if
the recovery partition is located in /dev/block/mmcblk0p13
the command "fastboot boot recovery.img", which we will be using extensively, can be used to boot the specified image file
the Clockworkmod Recovery image made from automated CWM porter successfully boots
The files you will need are provided below. I've also given instructions to the best of my ability without actually having done this.
To test if the recovery partition is located in /dev/block/mmcblk0p13:
Go into fastboot mode (step 2f in post #1 of http://forum.xda-developers.com/showthread.php?t=2546455)
Download the recovery.rar file below and extract it to get recovery.img.
Open up terminal
change directory to where you extracted recovery.img
type
Code:
fastboot boot recovery.img
See if phone boot into recovery
Next we test an edited recovery.img to see if "fastboot boot recovery.img" is truly letting us boot the image we've specified.
To find out, we're going to use the edited recovery.img and do pretty much the same thing except now with recovery-test.img:
Go into fastboot mode (step 2f in post #1 of http://forum.xda-developers.com/showthread.php?t=2546455)
Download the recovery-test.rar file below and extract it to get recovery-test.img.
Open up terminal
change directory to where you extracted recovery-test.img
type
Code:
fastboot boot recovery-test.img
See if any pictures are upside down (the battery symbol, numbers, or the android robot)
After completing the 2 tasks above, and verifying that we have a valid original recovery.img and that we can use
Code:
fastboot boot recovery.img
to boot a specific image file, we can start testing a very, very, very EXPERIMENTAL Clockworkmod Recovery image using fastboot. I would not rely on this image to make backups and I honestly do not know what kind of damage it might inflict on the phone so make a backup of everything before starting.
output from CWM automatic recovery builder: http://jenkins.cyanogenmod.com/job/recovery/52069/
To test if this CWM recovery image will boot and have the right partition layout:
Go into fastboot mode (step 2f in post #1 of http://forum.xda-developers.com/showthread.php?t=2546455)
Download the recovery.img.
Open up terminal
change directory to where you downloaded recovery.img
type
Code:
fastboot boot recovery.img
If the cwm recovery image boots, type
Code:
mount
See if /sdcard is mounted to the right partition)
If you're feeling lucky, make a backup to /sdcard **this step can cause damage to phone if /sdcard is mounted to the wrong partition**
Thanks for volunteering and bringing the Huawei Prism 2 one step closer to custom roms.
Will test as soon as I get the phone.
I should be getting my phone in the mail Tuesday-Wednesday, but I will test as soon as I get it in the mail and I get my bootloader unlocked. I shouldn't have an issue booting it, since it will boot without effecting my current recovery partition. Hopefully the cwm recovery boots as well.
streetdev22 said:
I should be getting my phone in the mail Tuesday-Wednesday, but I will test as soon as I get it in the mail and I get my bootloader unlocked. I shouldn't have an issue booting it, since it will boot without effecting my current recovery partition. Hopefully the cwm recovery boots as well.
Click to expand...
Click to collapse
Great! I really hope it works. Let me know if I can help with anything in the meantime.
Getting my phone today
My phone is coming today! I will let you know the results either later today or tomorrow. Also, could you pull a build.prop using ADB from your phone? This guy needs it: http://forum.xda-developers.com/showthread.php?p=49494728
niceeeee
Prism 2 said:
Great! I really hope it works. Let me know if I can help with anything in the meantime.
Click to expand...
Click to collapse
I tried them today and they work fine siiiiir. both booted while i was stuck in a boot loop from deleting my settins apk
Cjantolak said:
I tried them today and they work fine siiiiir. both booted while i was stuck in a boot loop from deleting my settins apk
Click to expand...
Click to collapse
Thats good news! Could you state specifically which 2 of the 3 images booted though? I'm assuming the original (recovery.rar file) and the edited (recovery-test.rar file) recovery.images, but want to make sure
In other words, did you test the clockworkmod recovery image?
first two
Prism 2 said:
Thats good news! Could you state specifically which 2 of the 3 images booted though? I'm assuming the original (recovery.rar file) and the edited (recovery-test.rar file) recovery.images, but want to make sure
In other words, did you test the clockworkmod recovery image?
Click to expand...
Click to collapse
I did just boot the clockworkmod recovery and i just booted up fine. os is running as it should other than the whole missing settings app. im stuck without root, without wifi, and usb debugging.
adb not installing the app either so idk.
Thanks for straightening out the confusion. Can you check the mounted partitions are correct? Afterwards you can use update.zip to install your settings.apk
---------- Post added at 01:11 AM ---------- Previous post was at 01:04 AM ----------
Never mind about checking the partition layout. I just remembered you don't have adb. I will try to make a better recovery image.
Read before continue:
http://forum.xda-developers.com/showthread.php?t=1914359
http://forum.xda-developers.com/showthread.php?t=2136738
http://forum.xda-developers.com/showthread.php?t=2345860
http://forum.xda-developers.com/showthread.php?t=3303112
DrGit said:
As I understand it, this only works because the Snapdragon boot ROM (NOT the bootloader, which resides on the eMMC - this is part of the CPU) has a fallback mode which reads the bootloader from an SD card if the eMMC fails.
Click to expand...
Click to collapse
ᴿℓᴚ said:
Check the references below about MSM8960 boot architecture. PBL (Primary Bootloader) Error Handler sequence:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Requirements:
A hardbricked Yuphoria/lettuce (YU5010/YU5010A) - when connected with a PC, it should expose itself as QHUSB_BULK (when no driver is installed)/Qualcomm HS-USB QDLoader 9008 (when appropriate driver is installed).
(Optional) A working Yuphoria/lettuce, if you want to create the recovery image yourself.
A microSD card - contrary to the popular belief, you don't need a 16 GB or bigger one. 1 GB is sufficient.
Win32 Disk Imager (Windows) / dd (*nix).
Information regarding the recovery image:
The partition structure of Yuphoria is as follows:
Code:
Number Start (sector) End (sector) Size Code Name
1 131072 262143 64.0 MiB 0700 modem
2 262144 262145 1024 bytes FFFF fsc
3 262146 262161 8.0 KiB FFFF ssd
4 262162 263185 512.0 KiB FFFF sbl1
5 263186 264209 512.0 KiB 0700 sbl1bak
6 264210 265233 512.0 KiB FFFF rpm
7 265234 266257 512.0 KiB 0700 rpmbak
8 266258 267281 512.0 KiB FFFF tz
9 267282 268305 512.0 KiB 0700 tzbak
10 268306 269329 512.0 KiB FFFF hyp
11 269330 270353 512.0 KiB 0700 hypbak
12 270354 273425 1.5 MiB FFFF modemst1
13 273426 276497 1.5 MiB FFFF modemst2
14 276498 296977 10.0 MiB FFFF splash
15 393216 393279 32.0 KiB FFFF DDR
16 393280 396351 1.5 MiB FFFF fsg
17 396352 396383 16.0 KiB FFFF sec
18 396384 398431 1024.0 KiB FFFF aboot
19 398432 400479 1024.0 KiB 0700 abootbak
20 400480 466015 32.0 MiB FFFF boot
21 466016 531551 32.0 MiB FFFF recovery
22 531552 4725855 2.0 GiB FFFF system
23 4849664 4980735 64.0 MiB FFFF cache
24 4980736 5046271 32.0 MiB FFFF persist
25 5046272 5048319 1024.0 KiB FFFF misc
26 5048320 5049343 512.0 KiB FFFF keystore
27 5049344 5050367 512.0 KiB FFFF config
28 5050368 30785502 12.3 GiB FFFF userdata
From the above table, its evident that dumping the first 200 MB should be enough to include all required partitions, but you can opt for a full dump as well.
To dump, we can use any of the following methods:
Directly to the PC using ADB.
Be rooted, connect to adb shell with root privilege & call dd to dump it in external sdcard.
Without being rooted but on unlocked bootloader, boot to (tethered booted/permanently flashed) TWRP, get shell access in TWRP or via adb shell, call dd to dump it in external sdcard.
For dumping the whole eMMC, use:
Code:
dd if=/dev/block/mmcblk0 of=/external_sd/backup.img bs=512 count=30535646
For dumping first 200 MB, use:
Code:
dd if=/dev/block/mmcblk0 of=/external_sd/backup.img bs=512 count=409600
You can directly write to the external sdcard as well:
Code:
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1
Be very careful working with dd! mmcblk0 is the eMMC and mmcblk1 is the external SD card.
Pre-created eMMC dump:
eMMC backup - Google Drive
drive.google.com
It is created from a bootloader unlocked Yuphoria running cm-12.1-YOG4PAS47N build.
The size of the whole dump is ~14.5 GB.
After compression, the size is ~998 MB. Its compressed using 7-Zip & split into 10 parts.
File hashes (SHA-1) are as follows:
Code:
9ce4d504395e1c64fbb6960c781fc537eb6b04a2 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.001
523287e0c3fb85c5c2ca1004a1b8219585845462 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.002
ad88026b7b723adf2591b622ebdb3051220c69d8 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.003
b0c6396ddae119d85c9135a6ff4e3cf122e5823e *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.004
c88b13065babcb7792fd66b877af5f2f4811f710 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.005
bbf88b156bd67d79bd3da64a1b9273d92c1487ee *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.006
99c2be608f8c359caabcd13889828ea1777dde73 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.007
e60acbafd6326d4d000a81128f8195ad0c14342e *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.008
895d7db6e961e56ce5c9e541adddfb72815f44c5 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.009
6267aac32bedcff93f4b873a5bce749b85d0ba09 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.010
0c7639808db3480dd06246e952f1f0d363edf6ba *cm-12.1-YOG4PAS47N-lettuce-eMMC.img
Usage:
Download the eMMC dump created by me or make it yourself.
Use Win32 Disk Imager (Windows) / dd (*nix) to write in a microSD card. I've used a 16 GB Class 10 one.
Insert the sdcard into the hardbricked Yuphoria, insert the battery, press Volume Up key & connect it with PC. It should expose itself as a bootloader/fastboot interface.
Flash official Cyanogen OS - you may need to omit the bootloader unlock/re-lock part.
Profit!
Note:
Try at your own risk! If you've any doubt, please contact with the nearest YU service center & ask them for a replacement.
Credit goes to the countless number of people, who risked their devices to find a working method to unbrick it (especially the girlfriend of my friend, who was forced to lend her device for the experiment).
The process is known to many persons out there - earlier I advised some of the Yureka users to try it out, but didn't get any further feedback. Credit goes to @Jimmyz0r for testing the hypothesis on Yureka on his own.
Please provide detailed feedback regarding your success/failure story, so that this tutorial can be enhanced more.
Reserved for future v1.
Reserved for future v2.
@Titokhan,
I tried using first 100MB dump before using full eMMC dump from Yureka but unfortunately I was unable to boot into fastboot, didn't tried 200MB though. I might make one 200MB dump and try it when I get enough time to brick and unbrick my device again.
PS: thanks for the credit m8
Thank You man For the nice Post I just got my phone back , I sucessfully restore my phone from Hell. It was complete Dead , Showing only qualcomm 9008 mode . I followed ur steps And My mobile is working again ... WAITED 4 mOnths for this Post I though i have to put my phone is trash , But it is working now
After Flashing Phone Nothing Boot Up
After follow your steps and download your EMMC data in 16GB 10class SD Card phone is able to connect with pc in fastboot mode and after i download the firmware and flash this with fastboot on my phone it is not booting up ..when i connect my phone to my it nothing show up any..please send me instrucations what can i do for my phone :crying::crying::crying::crying:
@lakhwinderlucky
1. How did you brick the device?
2. Which was original OS - Cyanogen OS or stock Android?
3. Is there any error while flashing via fastboot?
first my phone start restarting automattically and i thought that
there is any problem in firmware and i download the YU Yuphoria firmware and when i flash the downloaded package the phone become completely dead....now i put my phone in trash and crack it with aa big hammer..now i never purchase aa Yu Phone its all bull ****...without any major reason the phone was unexpetdly dead ...and service center is very poor and they refuse for the replacement in the warranty..anyway now i am free to that phone...:laugh::laugh:
Just one question. Does it matters if bootloader is locked or unlocked ? I have a dead Yuphoria with locked bootloader so just want to make sure before trying this revival guide.
Ruvy said:
Just one question. Does it matters if bootloader is locked or unlocked ? I have a dead Yuphoria with locked bootloader so just want to make sure before trying this revival guide.
Click to expand...
Click to collapse
Shouldn't be a problem - please post your feedback.
I have my friend's Yuphoria, due to some problem, I was asked to re-flash the stock rom, I tried to do the same. At that time it was in working condition, successfully entered the fastboot mode, flashed he file, while flashig I saw some message asking me "" volume up to Continue"" or
"" volume down to Cancel"" .. I don't remember the HEAD of the message, and also I don't remember which button I pressed (vol up or vol down). But the phone got bricked and it was never ON back. Now I nneed to try out your procedure.
My doubt is, are all the 3 procedures required to be done to dump the emmc ? If I have a 16GB memory card with class 4, is it OK ?
Rajatmohod said:
Thank You man For the nice Post I just got my phone back , I sucessfully restore my phone from Hell. It was complete Dead , Showing only qualcomm 9008 mode . I followed ur steps And My mobile is working again ... WAITED 4 mOnths for this Post I though i have to put my phone is trash , But it is working now , If anybody has difficulty to restore this phone , Pls Dont bother to call me .. I will help you to Get back your Phone My cell no. is +919975235086
Click to expand...
Click to collapse
Hi bro,
I am trying to reach you on your mobile but you are not picking up the phone. I have downloaded all the 10 zip filrs, made an image file and tried to write to the micro SD card of 16 GB class 10. But I saw about 67 files in my 16gb memory card and can't find the 25+ files as mentioned in the original post. Please guide me...
Sent from my YU5010 using XDA-Developers mobile app
Titokhan said:
Read before continue:
http://forum.xda-developers.com/showthread.php?t=1914359
http://forum.xda-developers.com/showthread.php?t=2136738
http://forum.xda-developers.com/showthread.php?t=2345860
http://forum.xda-developers.com/showthread.php?t=3303112
Requirements:
A hardbricked Yuphoria/lettuce (YU5010/YU5010A) - when connected with a PC, it should expose itself as QHUSB_BULK (when no driver is installed)/Qualcomm HS-USB QDLoader 9008 (when appropriate driver is installed).
(Optional) A working Yuphoria/lettuce, if you want to create the recovery image yourself.
A microSD card - contrary to the popular belief, you don't need a 16 GB or bigger one. 1 GB is sufficient.
Win32 Disk Imager (Windows) / dd (*nix).
Information regarding the recovery image:
The partition structure of Yuphoria is as follows:
Code:
Number Start (sector) End (sector) Size Code Name
1 131072 262143 64.0 MiB 0700 modem
2 262144 262145 1024 bytes FFFF fsc
3 262146 262161 8.0 KiB FFFF ssd
4 262162 263185 512.0 KiB FFFF sbl1
5 263186 264209 512.0 KiB 0700 sbl1bak
6 264210 265233 512.0 KiB FFFF rpm
7 265234 266257 512.0 KiB 0700 rpmbak
8 266258 267281 512.0 KiB FFFF tz
9 267282 268305 512.0 KiB 0700 tzbak
10 268306 269329 512.0 KiB FFFF hyp
11 269330 270353 512.0 KiB 0700 hypbak
12 270354 273425 1.5 MiB FFFF modemst1
13 273426 276497 1.5 MiB FFFF modemst2
14 276498 296977 10.0 MiB FFFF splash
15 393216 393279 32.0 KiB FFFF DDR
16 393280 396351 1.5 MiB FFFF fsg
17 396352 396383 16.0 KiB FFFF sec
18 396384 398431 1024.0 KiB FFFF aboot
19 398432 400479 1024.0 KiB 0700 abootbak
20 400480 466015 32.0 MiB FFFF boot
21 466016 531551 32.0 MiB FFFF recovery
22 531552 4725855 2.0 GiB FFFF system
23 4849664 4980735 64.0 MiB FFFF cache
24 4980736 5046271 32.0 MiB FFFF persist
25 5046272 5048319 1024.0 KiB FFFF misc
26 5048320 5049343 512.0 KiB FFFF keystore
27 5049344 5050367 512.0 KiB FFFF config
28 5050368 30785502 12.3 GiB FFFF userdata
From the above table, its evident that dumping the first 200 MB should be enough to include all required partitions, but you can opt for a full dump as well.
To dump, we can use any of the following methods:
Directly to the PC using ADB.
Be rooted, connect to adb shell with root privilege & call dd to dump it in external sdcard.
Without being rooted but on unlocked bootloader, boot to (tethered booted/permanently flashed) TWRP, get shell access in TWRP or via adb shell, call dd to dump it in external sdcard.
For dumping the whole eMMC, use:
Code:
dd if=/dev/block/mmcblk0 of=/external_sd/backup.img bs=512 count=30535646
For dumping first 200 MB, use:
Code:
dd if=/dev/block/mmcblk0 of=/external_sd/backup.img bs=1M count=200
You can directly write to the external sdcard as well:
Code:
dd if=/dev/block/mmcblk0 of=of=/dev/block/mmcblk1 bs=1M count=200
Be very careful working with dd! mmcblk0 is the eMMC and mmcblk1 is the external SD card.
Pre-created eMMC dump:
https://drive.google.com/folderview?id=0B9zZIJPXbMsuaGg2SXFHcW5mbzQ&usp=sharing
It is created from a bootloader unlocked Yuphoria running cm-12.1-YOG4PAS47N build.
The size of the whole dump is ~14.5 GB.
After compression, the size is ~998 MB. Its compressed using 7-Zip & split into 10 parts.
File hashes (SHA-1) are as follows:
Code:
9ce4d504395e1c64fbb6960c781fc537eb6b04a2 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.001
523287e0c3fb85c5c2ca1004a1b8219585845462 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.002
ad88026b7b723adf2591b622ebdb3051220c69d8 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.003
b0c6396ddae119d85c9135a6ff4e3cf122e5823e *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.004
c88b13065babcb7792fd66b877af5f2f4811f710 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.005
bbf88b156bd67d79bd3da64a1b9273d92c1487ee *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.006
99c2be608f8c359caabcd13889828ea1777dde73 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.007
e60acbafd6326d4d000a81128f8195ad0c14342e *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.008
895d7db6e961e56ce5c9e541adddfb72815f44c5 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.009
6267aac32bedcff93f4b873a5bce749b85d0ba09 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.010
0c7639808db3480dd06246e952f1f0d363edf6ba *cm-12.1-YOG4PAS47N-lettuce-eMMC.img
Usage:
Download the eMMC dump created by me or make it yourself.
Use Win32 Disk Imager (Windows) / dd (*nix) to write in a microSD card. I've used a 16 GB Class 10 one.
Insert the sdcard into the hardbricked Yuphoria, insert the battery, press Volume Up key & connect it with PC. It should expose itself as a bootloader/fastboot interface.
Flash official Cyanogen OS - you may need to omit the bootloader unlock/re-lock part.
Profit!
Note:
Try at your own risk! If you've any doubt, please contact with the nearest YU service center & ask them for a replacement.
Credit goes to the countless number of people, who risked their devices to find a working method to unbrick it (especially the girlfriend of my friend, who was forced to lend her device for the experiment).
The process is known to many persons out there - earlier I advised some of the Yureka users to try it out, but didn't get any further feedback. Credit goes to @Jimmyz0r for testing the hypothesis on Yureka on his own.
Please provide detailed feedback regarding your success/failure story, so that this tutorial can be ehanced more.
Click to expand...
Click to collapse
Dear Mr Titokhan,
I have done the same exercise as was mentioned in post #1 of thsi thread, but nothing has happened. Let me come with my exercise..
* I have downloaded all the 10 files from google drive and made it 1 image file with 7Z
* I have downloaded win32 disk imager and wrote the image to a Samsung 16 GB Class 10 with 48/mbps Memory card
* Inserted this card into the bricked device and pressed volume up and connected the cable to PC for flashing. But nothing came up.
* Tried vol+ and Power button retaining the MC in the device - no use.
* When tried to see the contents of memory card that was written the image file, I could not see anything except 63 mb of free data. (
* When entered the Disk Management I could see number of partitions without any names.
* I have tried with the ROM files, cm-12.1-YOG4PAS47N-lettuce-signed-fastboot-5d674b9b61 and cm-12.0-YNG1TBS2P2-lettuce-signed-fastboot but no use.
I have my friend's Yuphoria, due to some problem, I was asked to re-flash the stock rom, I tried to do the same. At that time it was in working condition, successfully entered the fastboot mode, flashed he file, while flashig I saw some message asking me "" volume up to Continue"" or
"" volume down to Cancel"" .. I don't remember the HEAD of the message, and also I don't remember which button I pressed (vol up or vol down). But the phone got bricked and it was never ON back. Now I need your help.
Note: I have 1 more YU5010 with me and presently using that. Since if it is useful for any type of backup of stock rom, I am just telling you in advance. Please help me with step by step procedure.
@vsrkmurthy
1. Please don't quote the whole first post.
2. Have you matched the hash of the eMMC image after extracting?
3. Windows can't see multi-partitioned removable media; it only shows the first readable partition.
4. After inserting the sdcard, pressing volume up & connecting the device with PC please send me the screenshot of Device Manger.
Titokhan said:
@vsrkmurthy
1. Please don't quote the whole first post.
2. Have you matched the hash of the eMMC image after extracting?
3. Windows can't see multi-partitioned removable media; it only shows the first readable partition.
4. After inserting the sdcard, pressing volume up & connecting the device with PC please send me the screenshot of Device Manger.
Click to expand...
Click to collapse
Thanks for the reply, If you can give me your whatsapp number, I want to send you the screenshots thro' that. Infact, yesterday, Rajat (refer post #5 of this thread) and myself tried a lot by connecting Team Viewer also. But no use. Please give me your contact number so that we can discuss and finalise. else, my number is +919059927728 (whatsapp also).
Bro ; you are a god. Seriously bro ; i went to All shops of NEHRU PLACE; NEW Delhi. They all said ; we can't do it. we(Service centre guys) have to change the motherboard of your YUpHORIA YU5010. and they were asking for ₹3k ;. I literally ordered a new smart phone ; but after reading your post and following each step i got my Yuphoria back. Thank You bro. Hats off to u. Thank You so much bro.
Please give me your contact number
Sent from my 2013023 using XDA-Developers mobile app
eMMc Dump not extracting
Titokhan said:
Shouldn't be a problem - please post your feedback.
Click to expand...
Click to collapse
Hello @Titokhan I have downloaded all the files but they are not extracting i have 16 Gb class 10 samsung card so can you please tell how to only dump necessary files.
Thanks in advance
How did you dump only 100mb?
YuganshT7 said:
Hello @Titokhan I have downloaded all the files but they are not extracting i have 16 Gb class 10 samsung card so can you please tell how to only dump necessary files.
Thanks in advance
Click to expand...
Click to collapse
Jimmyz0r said:
@Titokhan,
I tried using first 100MB dump before using full eMMC dump from Yureka but unfortunately I was unable to boot into fastboot, didn't tried 200MB though. I might make one 200MB dump and try it when I get enough time to brick and unbrick my device again.
PS: thanks for the credit m8
Click to expand...
Click to collapse
Can you tell me how can i Dump only 200mb of eMMc on My SD card . I am on windows
@YuganshT7
Can you please elaborate more? What was the exact error message you got?
Hello,
I need some help. At the moment I am connected with the eMMC flash of my SOHO 3rd GEN tablet.
I used the exploitee.rs emmc adapter.
The problem:
-The tablet want not booting anymore. Stuck fw was on it (no idea wich fw).
-I try to bring it back with a fastboot cable but something burned on the mainboard (If you had a 3rd gen device and a microscope pls help)
What I want to try:
-I want to reflash the bootloader (are there two on this device???) and the recovery with my emmc adapter to be able to flash the stock fw again. I want to give him just manually 3.7V with a power adapter, at the battery connector.
The problem now:
I really dont know how to extract the right img-files from the stock-bin file. There are some different img files: (md5 sum at begining)
Code:
f82a8c5518a76b96b95dc0448b772d81 /media/galliumos/MULTIBOOT/Amazon_Kindle_Fire_HD_3rd_gen_SOHO/images/boot.img
Code:
a5224737ba83a65d40e3049ba6d71582 /media/galliumos/MULTIBOOT/Amazon_Kindle_Fire_HD_3rd_gen_SOHO/images/boot-prod.img
Code:
4e6181ea47c7868c2104147dc0b2fce6 /media/galliumos/MULTIBOOT/Amazon_Kindle_Fire_HD_3rd_gen_SOHO/images/u-boot.bin
Code:
38cfffa45008955f2887f7998dbd1c4e /media/galliumos/MULTIBOOT/Amazon_Kindle_Fire_HD_3rd_gen_SOHO/images/u-boot-prod.bin
Code:
aa4b135a185e5486656893f4c7101271 /media/galliumos/MULTIBOOT/Amazon_Kindle_Fire_HD_3rd_gen_SOHO/recovery_images/recovery-eng.img
Code:
5cba5636109eec7c7e5faa35104d65c0 /media/galliumos/MULTIBOOT/Amazon_Kindle_Fire_HD_3rd_gen_SOHO/recovery_images/recovery-prod.img
Code:
Here is recovery from the old system:
7e781998261c22852f6bae53e02335c6 /media/galliumos/MULTIBOOT/Amazon_Kindle_Fire_HD_3rd_gen_SOHO/recovery.img
I really think the bootloader was broken and that was the reason why the device was still black.
So I really would like to flash with
Code:
sudo dd if=/sdcard/bin-extract-stock/images/the-right.img of=/dev/sda2
the needed partitions. Like when I let the device making an update.
Can you help me to get the 100% right image files for the right partitions.
Here are some informations about the current partitions:
Code:
Disk /dev/sda: 14.6 GiB, 15634268160 bytes, 30535680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: F9F21FFF-A8D4-5F0E-9746-594869AEC34E
Device Start End Sectors Size Type
/dev/sda1 256 511 256 128K Microsoft basic data
/dev/sda2 512 1023 512 256K Microsoft basic data
/dev/sda3 1024 1151 128 64K Microsoft basic data
/dev/sda4 1152 1183 32 16K Microsoft basic data
/dev/sda5 1184 1187 4 2K Microsoft basic data
/dev/sda6 2048 34815 32768 16M Microsoft basic data
/dev/sda7 34816 51199 16384 8M Microsoft basic data
/dev/sda8 51200 67583 16384 8M Microsoft basic data
/dev/sda9 67584 2623487 2555904 1.2G Microsoft basic data
/dev/sda10 2623488 4466687 1843200 900M Microsoft basic data
/dev/sda11 4466688 30535679 26068992 12.4G Microsoft basic data
Code:
Command (? for help): ?
b back up GPT data to a file
c change a partition's name
d delete a partition
i show detailed information on a partition
l list known partition types
n add a new partition
o create a new empty GUID partition table (GPT)
p print the partition table
q quit without saving changes
r recovery and transformation options (experts only)
s sort partitions
t change a partition's type code
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu
Command (? for help): i
Partition number (1-11): 1
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F00-A8D4-5F0E-9746-594869AEC34E
First sector: 256 (at 128.0 KiB)
Last sector: 511 (at 255.5 KiB)
Partition size: 256 sectors (128.0 KiB)
Attribute flags: 0000000000000000
Partition name: 'xloader'
Command (? for help): i
Partition number (1-11): 2
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F01-A8D4-5F0E-9746-594869AEC34E
First sector: 512 (at 256.0 KiB)
Last sector: 1023 (at 511.5 KiB)
Partition size: 512 sectors (256.0 KiB)
Attribute flags: 0000000000000000
Partition name: 'bootloader'
Command (? for help): i
Partition number (1-11): 3
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F02-A8D4-5F0E-9746-594869AEC34E
First sector: 1024 (at 512.0 KiB)
Last sector: 1151 (at 575.5 KiB)
Partition size: 128 sectors (64.0 KiB)
Attribute flags: 0000000000000000
Partition name: 'idme'
Command (? for help): i4
Partition number (1-11): 4
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F03-A8D4-5F0E-9746-594869AEC34E
First sector: 1152 (at 576.0 KiB)
Last sector: 1183 (at 591.5 KiB)
Partition size: 32 sectors (16.0 KiB)
Attribute flags: 0000000000000000
Partition name: 'crypto'
Command (? for help): i
Partition number (1-11): 5
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F04-A8D4-5F0E-9746-594869AEC34E
First sector: 1184 (at 592.0 KiB)
Last sector: 1187 (at 593.5 KiB)
Partition size: 4 sectors (2.0 KiB)
Attribute flags: 0000000000000000
Partition name: 'misc'
Command (? for help): i
Partition number (1-11): 6
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F05-A8D4-5F0E-9746-594869AEC34E
First sector: 2048 (at 1024.0 KiB)
Last sector: 34815 (at 17.0 MiB)
Partition size: 32768 sectors (16.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'efs'
Command (? for help): i
Partition number (1-11): 7
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F06-A8D4-5F0E-9746-594869AEC34E
First sector: 34816 (at 17.0 MiB)
Last sector: 51199 (at 25.0 MiB)
Partition size: 16384 sectors (8.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'recovery'
Command (? for help): i
Partition number (1-11): 8
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F07-A8D4-5F0E-9746-594869AEC34E
First sector: 51200 (at 25.0 MiB)
Last sector: 67583 (at 33.0 MiB)
Partition size: 16384 sectors (8.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'boot'
Command (? for help): i
Partition number (1-11): 9
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F08-A8D4-5F0E-9746-594869AEC34E
First sector: 67584 (at 33.0 MiB)
Last sector: 2623487 (at 1.3 GiB)
Partition size: 2555904 sectors (1.2 GiB)
Attribute flags: 0000000000000000
Partition name: 'system'
Command (? for help): i
Partition number (1-11): 10
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F09-A8D4-5F0E-9746-594869AEC34E
First sector: 2623488 (at 1.3 GiB)
Last sector: 4466687 (at 2.1 GiB)
Partition size: 1843200 sectors (900.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'cache'
Command (? for help): i
Partition number (1-11): 11
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F0A-A8D4-5F0E-9746-594869AEC34E
First sector: 4466688 (at 2.1 GiB)
Last sector: 30535679 (at 14.6 GiB)
Partition size: 26068992 sectors (12.4 GiB)
Attribute flags: 0000000000000000
Partition name: 'userdata'
gparted
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Greetings by I_did_it_just_tmrrow
overlode said:
Edit - SUCCESS!!! It seems I may have had one wire touching another so I tidied up the soldering and the eMMC was recognised straight away
I have successfully accessed the Soho eMMC and can see all partitions as in the attached image!!!
Now if only I could find the commands to backup the entire eMMC...
Click to expand...
Click to collapse
overlode said:
Ok, files uploaded -
Bootloader - https://drive.google.com/file/d/0BwMwdZJ36fBoVTNRVmNjX2FmZTQ/edit?usp=sharing
eMMC Dump - https://drive.google.com/file/d/0BwMwdZJ36fBoNTQyUENvbmVGY1E/edit?usp=sharing
Enjoy
Click to expand...
Click to collapse
I found this post here.
So now I had a 100% bootloader partition and my recovery partition.
What is about 'xloader' partition name?
And the partition 8: "boot". It that "u-boot.bin" from my source?
Pls, I need some answers.
Greetings by Idijt
its been awhile since i got mine revived! soo all this is like something new to me! howeveer ill provide what little that i have
abatoir said:
its been awhile since i got mine revived! soo all this is like something new to me! howeveer ill provide what little that i have
Click to expand...
Click to collapse
Did you still own your device? Can dump your partitions with dd?
Greetings by Idijt
No I don't own it anymore. But mine was an 8gb version, seems like yours is a 15gb version or something like that. I do have photos of my complete partitions.
Sent from my Redmi Note 2 using XDA Free mobile app
---------- Post added at 05:07 AM ---------- Previous post was at 04:48 AM ----------
this is my partiton table after succesfully uploading to emmc
Hello, I'm soho everything is normal, but then teardown accidentally short after the motherboard usb boot don't boot, but the computer have a reaction, but did not show for help how to solve the screen is black, from youdao translation
Hope this helps...
I did something similar. I was using a cheap cable so I swapped them out. I got a LG cable and plugged it in, well it borked my tablet. Black Screen, I took cable apart and found a resistor soldered to a pin! Tested it and it was sending odd pulses, whatever it broke mine. Here is a list of what I backed up before testing.
KF3_p1-xloader.img
-rwxrwxrwx 1 root vboxusers 35002 Sep 3 17:35 KF3_p1-xloader.rar
-rwxrwxrwx 1 root vboxusers 262144 Sep 3 17:27 KF3_p2-BootLoader-Orig.img
-rwxrwxrwx 1 root vboxusers 65536 Sep 3 17:35 KF3_p3-idme.img
-rwxrwxrwx 1 root vboxusers 16384 Sep 3 17:35 KF3_p4-crypto.img
-rwxrwxrwx 1 root vboxusers 2048 Sep 3 17:35 KF3_p5-misc.img
-rwxrwxrwx 1 root vboxusers 16777216 Sep 3 17:35 KF3_p6-efs.img
I assume you need to dd a original image to xloader &or bootloader.
I can only get mine in usb boot mode, which shows as omap4470 windows and Linux as:
Bus 002 Device 005: ID 0451:d012 Texas Instruments, Inc. I suspect I may need to mod & recompile the usbboot source. I think its hardcoded for 4430 or 4460.
*Your Method is even more promising.
I will upload the files if you need them. All except idme & efs as it contains my serials, etc. I *assume* those 2 files will work as they are stock and should have signatures intact.
Would You Post a Pic of the rs device connected to your Kindle?
I would love to find the serial and JTAG pinouts...?
any try this and did can repier of this problem
can you help me please
unimatrix725 said:
I did something similar. I was using a cheap cable so I swapped them out. I got a LG cable and plugged it in, well it borked my tablet. Black Screen, I took cable apart and found a resistor soldered to a pin! Tested it and it was sending odd pulses, whatever it broke mine. Here is a list of what I backed up before testing.
KF3_p1-xloader.img
-rwxrwxrwx 1 root vboxusers 35002 Sep 3 17:35 KF3_p1-xloader.rar
-rwxrwxrwx 1 root vboxusers 262144 Sep 3 17:27 KF3_p2-BootLoader-Orig.img
-rwxrwxrwx 1 root vboxusers 65536 Sep 3 17:35 KF3_p3-idme.img
-rwxrwxrwx 1 root vboxusers 16384 Sep 3 17:35 KF3_p4-crypto.img
-rwxrwxrwx 1 root vboxusers 2048 Sep 3 17:35 KF3_p5-misc.img
-rwxrwxrwx 1 root vboxusers 16777216 Sep 3 17:35 KF3_p6-efs.img
I assume you need to dd a original image to xloader &or bootloader.
I can only get mine in usb boot mode, which shows as omap4470 windows and Linux as:
Bus 002 Device 005: ID 0451:d012 Texas Instruments, Inc. I suspect I may need to mod & recompile the usbboot source. I think its hardcoded for 4430 or 4460.
*Your Method is even more promising.
I will upload the files if you need them. All except idme & efs as it contains my serials, etc. I *assume* those 2 files will work as they are stock and should have signatures intact.
Would You Post a Pic of the rs device connected to your Kindle?
I would love to find the serial and JTAG pinouts...?
View attachment 3866692
Click to expand...
Click to collapse
can you help me please
Nit an expert, mine is still bricked sitting on shelf.
arikurdi said:
can you help me please
Click to expand...
Click to collapse
I would suggest reading from first post. I don't know allot about the kindle. I spent many hours reading the threads to try and fix mine. I would suggest googling for an identification guide, since kindles are hard to tell apart. To make sure you are in the correct place. The second thing when needing help is to provide a detailed description of your problem. You increase chances of more than one person helping.
kindle fire soho
unimatrix725 said:
I would suggest reading from first post. I don't know allot about the kindle. I spent many hours reading the threads to try and fix mine. I would suggest googling for an identification guide, since kindles are hard to tell apart. To make sure you are in the correct place. The second thing when needing help is to provide a detailed description of your problem. You increase chances of more than one person helping.
Click to expand...
Click to collapse
my problem is my kindel fire soho is just read on pc omap4470 and idont know how to make short
and install driver on linux ihave linux but idont how is work iflashed wrong bootloader file
Hi, I also have Kindle Fire HD 7 Soho (2013). I was attempting to unlock the bootloader and install TWRP, following this thread:
https://forum.xda-developers.com/ki...ment/unlock-kfsowi-bootloader-unlock-t3262770
I was able to get into fastboot mode, then proceeded to flash boot with the hijack image, but in the next line, where the system partition is flashed with a system image, I mistakenly flashed system image to the boot partition. I then did continue, before I realized my mistake. It doesn't boot anymore, but I believe the card reader emmc access would be able to get me back in business again.
I've read this thread, and the thread for the HD 7 2012 Tate emmc, I don't see anything pointing to the connections for the card reader to the 2013 soho motherboard. If there is something that has been posted, could someone put a link in this thread? I think it will be very helpful for those of us that want to try that method to unbrick our Kindles (2013, 3rd generation). Thank you.
EDIT: After more reading, I came across a thread which shows the points to connect an sd card reader to the motherboard of a Kindle Fire HD 7 Soho (2013, 3rd gen) in order to access the emmc of the kindle, it will show up as a usb drive when the card reader is connected to the usb port.
https://forum.xda-developers.com/showthread.php?t=2674737&page=3
Here is another related link, it shows the connections using the pins of a micro-sdcard adapter, you should read the entire article because it mentions a 50k-ohm pull up resistor that is required between pins 2 & 4. This was used on a Kindle Fire HD 7 Tate (2012)
https://forum.xda-developers.com/kindle-fire-hd/7-inch-help/kindle-fire-hd-7-emmc-access-t2828906
I am waiting on a fastboot cable first, and it should arrive soon. If I can't get into fastboot mode with the new cable, then I will try the card reader method.
@crackitopen any news?
I found a pin decription for the SOHO and I got a image.
Currently I had still the broken SOHO-8GB from the first post. But I got a second SOHO-16GB version. I could imagine that the bootloader ist the same but I am not sure how to read it and flash it in the right way. Could anybody help with that?
Greetings by Idijt
I_did_it_just_tmrrow said:
@crackitopen any news?
Click to expand...
Click to collapse
Hi Sorry for the late reply, but yes - I waited for the fastboot cable to arrive, and when it did, I was able to get into fastboot mode, so I had only to reflash those 2 partitions. I was very careful this time around, and I was successful in updating the Soho to CyanogenMod 12 unofficial Soho, Android 5.0.2 as described in that other post that I referenced.
crackitopen said:
Hi Sorry for the late reply, but yes - I waited for the fastboot cable to arrive, and when it did, I was able to get into fastboot mode, so I had only to reflash those 2 partitions. I was very careful this time around, and I was successful in updating the Soho to CyanogenMod 12 unofficial Soho, Android 5.0.2 as described in that other post that I referenced.
Click to expand...
Click to collapse
Did you have some tipps for me?
I own 2 SOHO devices and grab from the first one the following partitions:
Code:
=========================================
soho:/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 470440 480 469960 1% /dev
tmpfs 470440 0 470440 0% /mnt
/dev/block/mmcblk0p10 1251544 707172 544372 57% /system
/dev/block/mmcblk0p12 5316696 2888156 2428540 55% /data
/dev/block/mmcblk0p11 907096 15708 891388 2% /cache
/dev/fuse 5316696 2888156 2428540 55% /mnt/runtime/default/emulated
/dev/fuse 5316696 2888156 2428540 55% /mnt/runtime/read/emulated
/dev/fuse 5316696 2888156 2428540 55% /mnt/runtime/write/emulated
=========================================
soho:/ # ls -la /dev/block/platform/omap_hsmmc.1/by-name
total 0
drwxr-xr-x 2 root root 280 2017-10-22 01:35 .
drwxr-xr-x 4 root root 380 2017-10-22 01:35 ..
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 boot -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 bootloader -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2017-10-22 01:35 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 crypto -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 efs -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 exploit -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 idme -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 recovery -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2017-10-22 01:35 system -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 xloader -> /dev/block/mmcblk0p1
The following partition was to big ofr internal memory:
Code:
lrwxrwxrwx 1 root root 21 2017-10-22 01:35 userdata -> /dev/block/mmcblk0p12
What would I like to do next:
I wanna solder my gtv-Hacker emmc adapter to my SOHO mainboard to fix it. Then I would like to flash "bootloader -> /dev/block/mmcblk0p2" & "recovery -> /dev/block/mmcblk0p7" & "exploit -> /dev/block/mmcblk0p9".
Commands to flash the 3 partitions?
Greetings by Idijt
Jesus christ you fixed it? You are a god to me OP.
Galaxyninja66 said:
Jesus christ you fixed it? You are a god to me OP.
Click to expand...
Click to collapse
If you mean me, no I dont fix it yet. I was on the right way but then my noob-Linux knowledge or any other reason seems to destroy the one mainboard. I had SOHO mainboard, one with hardware error and one with software-Brick error.
But I think you have another kindle, I had 2 SOHO boards and you seems to have a TATE:
Code:
>KFHD 7 2012 (tate) - CyanogenMod 13 (Considering an SFOS port)
Greetings by Idijt
I_did_it_just_tmrrow said:
If you mean me, no I dont fix it yet. I was on the right way but then my noob-Linux knowledge or any other reason seems to destroy the one mainboard. I had SOHO mainboard, one with hardware error and one with software-Brick error.
But I think you have another kindle, I had 2 SOHO boards and you seems to have a TATE:
Code:
>KFHD 7 2012 (tate) - CyanogenMod 13 (Considering an SFOS port)
Greetings by Idijt
Click to expand...
Click to collapse
I know we have different kindles, but raising a messed up board from the dead is an accomplishment no less
On a side note, and SFOS port might not be possible due to the nature of the Kindle fire bootloader. Each build just goes straight to fastboot which is un heard of on any other device.
Just wanted to say thank you to @overlode and @unimatrix725. Thanks to you I was able to bring my hard bricked Fire HD 3rd gen (soho) back to the land of living. I've made a mistake of flashing a wrong bootloader.
After a bit of googling I came across a thread on xda where @overlode shared an immensely helpful photo with eMMC pins mapped out - you rock! Using this mapping I was able to solder an usb sdcard reader to the eMMC and access it from gparted. Then I've found this thread where @unimatrix725 shared his original bootloader.img which I then subsequently flashed to my device. Now my Fire HD is happy again - thank you!
Glad you were able to sort it @pfoltyn, I haven't looked at this for a couple of years and have since moved on to other projects but glad it's still helping people
Sorry for the noob question but how do I do "While on Slot_A Flash copypartitions.zip"
I cant find the copypartitions.zip
please help thanks
same here
I have the same problem, new in phone customizing; not computer noob but android; well how unlock bootloader - described, no problem; done; how install twrp or magisk, all infos and links are available;
but copypartitions.zip? what is it, where is it explained or described; when exactly do this thing? when i'm flashing custom rom the first time? after or before it? and where is partitions zip file? flash from PC to phone using fastboot or what? I'm stuck;
if theres forum topic about it , thats all what i'm asking for; just like its for twrp or magisk;
and Yes, i'm aware of this topic https://www.xda-developers.com/how-a-b-partitions-and-seamless-updates-affect-custom-development-on-xda/, understand idea of A/B partitions but don't understand the meaning of copy A/B partitions zip; what zip? where it is? make backup of A and B partitions using TWRP?
There is nothing to copy and make a backup of
Download the copy A/B partitions zip from here
https://androidfilehost.com/?fid=4349826312261636295
Just flash that zip file in custom recovery directly coming from stock or recently restoring stock firmware.
From wiki.lineageos.org:
In some cases slot b can be unpopulated(*) or contain much older firmware than slot a(**), leading to various issues including a potential hard-brick. We can work around that by copying the contents of slot a to slot b.
(*) new devices which have never done an update before
(**) e.g. an older version of Android
@darko454
You must have an unlocked bootloader to install this or any rom on any Android device.. https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Magisk isn't mandatory. If you don't want root just don't flash magisk during your installation. While on "slot a" be sure and flash the copy partitions ab zip from the original post here and make sure it installs correctly with no errors on your screen then flash rom and reboot as it says in the op. If it takes you to recovery and prompts for factory reset then factory reset and afterwards you will boot up and be up and running. You can always return to stock by fastboot flashing your stock firmware for your device model. There have been MANY hard bricks on this device because people didn't flash that copy ab zip while on slot a. Also unlike many devices instead of installing custom recovery I recommend booting recovery instead: fastboot boot recovery.img You won't have any freezes on your recovery touch screen when you boot recovery -vs- if you install it.
I use a USB thumb drive and a micro sdcard and keep everything on them and not on my internal storage because when you install a rom on this device you have to format data. That being said ..
How I flash: Move anything and everything I want to keep to either my external sdcard or thumb drive storage. Check mark developer options and USB debugging and take any screen lock is off in security settings, plug up to computer, look on phone for a pop up. If nothing pops up scroll down in developer options to "default USB configuration" and change that to " file transfer" and watch phone for pop up. As soon as it pops up checkmark the box allowing computer to communicate with your phone .. On phone push power and reboot then hold down volume down button until you're in bootloader mode and has a black screen with "start" run fastboot command: fastboot getvar all , That will tell you what slot you're activly on. You want to be on slot a. If you're on slot b then: fastboot set_active a ,Once it goes to slot a then: fastboot reboot bootloader ,then boot recovery: fastboot boot recovery (where "recovery" is replace that word with whatever you renamed your recovery image that you're flashing.)
Wipe data, system, cache, internal storage, format data, flash copy partitions ab zip, flash rom , reboot system. Then it will take you to recovery, select factory reset and confirm and it will then boot system and you'll be up and running.
*I wrote this over on pixel experience rom thread in the Moto g7 power roms section of our forum. Hope it helps someone. I knew nothing about this device when I first came here and I owe what I have learned to xda and everyone who shared about what to do , what not to do....etc but going on telegram group for moto g7 power and reading up has been a great learning experience. Thanks Gabi and Electimon and everyone else on there who helped me. I bricked quite a few times when I first got my device. I got it too early the same day metro pcs at the time was getting them is when I ended up grabbing mine. There was nowhere near the information here there is now. :good:
***Copy partition ab zip is also located in the original post of pixel experience rom here on xda.
Here: https://forum.xda-developers.com/g7-power/development/rom-pixel-experience-plus-t4072061
heres my question. so in slot a, boot twrp and do i install twpermanently before wiping data, system, cache and internal and format datta before installing copy partitions zip an hten the rom an then gapps. I am new at a b flashing and iwant to be sure beforei amke any mistakes that may end up bricking the device.
mrk2815 said:
heres my question. so in slot a, boot twrp and do i install twpermanently before wiping data, system, cache and internal and format datta before installing copy partitions zip an hten the rom an then gapps. I am new at a b flashing and iwant to be sure beforei amke any mistakes that may end up bricking the device.
Click to expand...
Click to collapse
Ok, your current active slot is _a. I give you a step by step guide:
1. boot TWRP with
Code:
fastboot boot twrp-XXX.img
2. do a complete backup of all you can select and store it on your PC or external SD
3. select 'Wipe' > 'Format Data' > type 'yes' > swipe to confirm
4. select 'Reboot' > reboot into bootloader > boot TWRP again
5. now flash:
a) copy-partitions.zip
b) your ROM => will be installed on slot _b
c) TWRP-installer.zip => installs TWRP on both slots6. select 'Reboot' > reboot into recovery => boot slot changes automatically, no need to change it!
7. now you are on slot _b > flash GApps
8. You don't need to wipe /cache, /data or internal storage because you already formatted /data which stores all these directories. You don't need to wipe /system as well because it was flashed by your ROM.
9. reboot into system and enjoy your ROM!
---------- Post added at 11:32 PM ---------- Previous post was at 11:24 PM ----------
I forgot that your new ROM on slot _b will install a new boot.img also. So it would be better to flash the TWRP-installer.zip after you installed your new ROM. !!Edited steps above to bring them in the right order!!
these steps you explained to me.did they work for you and did your new rom boot after the entire process was complete . hopefully there were no issues after the reboot correct
mrk2815 said:
these steps you explained to me.did they work for you and did your new rom boot after the entire process was complete . hopefully there were no issues after the reboot correct
Click to expand...
Click to collapse
This is a common guide for a A/B device, nothing special
thanks to all the info on the matter. I will b attempting this soon.we will se if i am successful in the new venture of a/b flashing.i have flashed a only devices in the past and i would always have success when flashing.but with the new scheme, its a bit confusing at first.but i will gradually grasp it hopefully.
mrk2815 said:
thanks to all the info on the matter. I will b attempting this soon.we will se if i am successful in the new venture of a/b flashing.i have flashed a only devices in the past and i would always have success when flashing.but with the new scheme, its a bit confusing at first.but i will gradually grasp it hopefully.
Click to expand...
Click to collapse
I "remastered" the guide and now you can follow it steb by step.
WoKoschekk said:
I "remastered" the guide and now you can follow it steb by step.
Click to expand...
Click to collapse
wait so if flash to stock do I need to do this?
Malfrosty said:
wait so if flash to stock do I need to do this?
Click to expand...
Click to collapse
u gonna use a flash script for the stock rom?
WoKoschekk said:
u gonna use a flash script for the stock rom?
Click to expand...
Click to collapse
yeah its what I normally do, but I am confused on if I need to use copypartitions.zip when going to stock
Malfrosty said:
yeah its what I normally do, but I am confused on if I need to use copypartitions.zip when going to stock
Click to expand...
Click to collapse
No
Malfrosty said:
yeah its what I normally do, but I am confused on if I need to use copypartitions.zip when going to stock
Click to expand...
Click to collapse
What's described here in my guide has nothing to do with how a stock rom is being flashed. Use your flash script and you should be fine with that. Use the copy-partition.zip only for custom ROMs.
if one does flash copy partitions at first then rom then gaps then twrp installer then install copy partitions zip again, then reboots recovery an then install rom and gapps and then twrp installer and then reboot system.will that brick the device or not.just wondering.
No, you will only brick your brain, but not your device! Although it does not make any sense to do this, I will try to explain it:
Regarding to this copy-partions.zip from LineageOS, I'll take my Moto G6+ as an example.
Here is the complete partition layout (mmcblk0):
Number Start (sector) End (sector) Size Code Name
1 256 7423 3.5 MiB A012 xbl_a
2 7424 14591 3.5 MiB FFFF xbl_b
3 14592 18687 2.0 MiB A016 tz_a
4 18688 22783 2.0 MiB FFFF tz_b
5 22784 23807 512.0 KiB A018 rpm_a
6 23808 24831 512.0 KiB FFFF rpm_b
7 24832 25855 512.0 KiB A017 hyp_a
8 25856 26879 512.0 KiB FFFF hyp_b
9 26880 27135 128.0 KiB FFFF devcfg_a
10 27136 27391 128.0 KiB FFFF devcfg_b
11 27392 28415 512.0 KiB A01E pmic_a
12 28416 29439 512.0 KiB FFFF pmic_b
13 29440 31487 1024.0 KiB FFFF abl_a
14 31488 33535 1024.0 KiB FFFF abl_b
15 33536 34559 512.0 KiB FFFF cmnlib_a
16 34560 35583 512.0 KiB FFFF cmnlib64_a
17 35584 36607 512.0 KiB FFFF cmnlib_b
18 36608 37631 512.0 KiB FFFF cmnlib64_b
19 37632 38655 512.0 KiB FFFF keymaster_a
20 38656 39679 512.0 KiB FFFF keymaster_b
21 39680 39935 128.0 KiB FFFF storsec_a
22 39936 40191 128.0 KiB FFFF storsec_b
23 40192 40703 256.0 KiB FFFF prov_a
24 40704 41215 256.0 KiB FFFF prov_b
25 41216 266495 110.0 MiB 0700 modem_a
26 266496 491775 110.0 MiB FFFF modem_b
27 491776 491777 1024 bytes A029 fsc
28 491784 491799 8.0 KiB A02C ssd
29 492032 524799 16.0 MiB FFFF dsp_a
30 524800 557567 16.0 MiB FFFF dsp_b
31 557568 559615 1024.0 KiB A01A ddr
32 559616 560639 512.0 KiB FFFF utags
33 560640 561663 512.0 KiB FFFF utagsBackup
34 561664 565759 2.0 MiB A027 modemst1
35 565760 569855 2.0 MiB A028 modemst2
36 569856 590335 10.0 MiB A02A fsg_a
37 590336 610815 10.0 MiB FFFF fsg_b
38 610816 676351 32.0 MiB A026 persist
39 676352 677375 512.0 KiB FFFF frp
40 677376 677631 128.0 KiB FFFF cid
41 677632 710399 16.0 MiB FFFF carrier
42 710400 711423 512.0 KiB FFFF metadata
43 711424 727807 8.0 MiB FFFF kpan
44 727808 858879 64.0 MiB A036 boot_a
45 858880 989951 64.0 MiB FFFF boot_b
46 989952 1022719 16.0 MiB FFFF dto_a
47 1022720 1055487 16.0 MiB FFFF dto_b
48 1055488 1057535 1024.0 KiB A01F misc
49 1057536 1073919 8.0 MiB FFFF logfs
50 1073920 1074431 256.0 KiB A022 apdp
51 1074432 1074943 256.0 KiB A023 msadp
52 1074944 1074945 1024 bytes A024 dpo
53 1074952 1074959 4.0 KiB A021 devinfo
54 1074960 1084175 4.5 MiB FFFF bluetooth_a
55 1084176 1093391 4.5 MiB FFFF bluetooth_b
56 1093392 1160239 32.6 MiB FFFF logo_a
57 1160240 1227087 32.6 MiB FFFF logo_b
58 1227088 1227215 64.0 KiB FFFF vbmeta_a
59 1227216 1227343 64.0 KiB FFFF vbmeta_b
60 1227344 1261567 16.7 MiB FFFF padA
61 1261568 1277951 8.0 MiB FFFF hw
62 1277952 1294335 8.0 MiB FFFF sp
63 1294336 1785855 240.0 MiB FFFF oem_a
64 1785856 2277375 240.0 MiB FFFF oem_b
65 2277376 4145151 912.0 MiB FFFF vendor_a
66 4145152 6012927 912.0 MiB FFFF vendor_b
67 6012928 11649023 2.7 GiB A038 system_a
68 11649024 17285119 2.7 GiB FFFF system_b
69 17285120 122142686 50.0 GiB A03A userdata
Assuming we start on slot A and slot B is empty.
mrk2815 said:
if one does flash copy partitions at first...
Click to expand...
Click to collapse
First of all we should know which partitions are being copied and flashed by the script. Every partition whose name contains a slot will be copied except those:
Code:
# Partitions ignored
IGNORED=" dtbo_a dtbo_b system_a system_b boot_a boot_b vbmeta_a vbmeta_b "
Flashing the script will still leave those ones blank, because you will flash them with your ROM. Always.
=> Result of this step: All parts, especially your bootloader, are now copied to slot B. Except the above mentioned "ignored parts"
mrk2815 said:
...then rom then gaps then twrp installer....
Click to expand...
Click to collapse
Now the ignored parts were flashed by the ROM and slot B is completely written (GApps are only single files and not an image for an entire partition, you could ignore them). TWRP installer patches both boot partitions - slot A+B.
=> Result of this step: Slot A is completely written with your old ROM and TWRP. Slot B is completely written with your new ROM and TWRP.
mrk2815 said:
...then install copy partitions zip again,...
Click to expand...
Click to collapse
=> Slot A is still the same and Slot B is still the same. Remember the ignored parts!
mrk2815 said:
...then reboots recovery an then install rom and gapps and then twrp installer....
Click to expand...
Click to collapse
Reboot sets the active slot to B. So, the ROM will be installed on slot A. TWRP installer patches both slots again.
=> New ROM is installed on both slots now. TWRP was installed a second time = no changes
mrk2815 said:
...and then reboot system.will that brick the device or not.just wondering.
Click to expand...
Click to collapse
=> Reboot sets active slot to A and you will boot into your new ROM on slot A.
Any questions?
thanks for all the explanations .its now more clear on what's going on with a b device flashing. Thanks to your step by step instructions, i was was able to successfully flash my first custom rom to an a b device without any fear of bricking it . Again thanks for the best step by step explanation of hte entire proces of flashing a B devices.
mrk2815 said:
thanks for all the explanations .its now more clear on what's going on with a b device flashing. Thanks to your step by step instructions, i was was able to successfully flash my first custom rom to an a b device without any fear of bricking it . Again thanks for the best step by step explanation of hte entire proces of flashing a B devices.
Click to expand...
Click to collapse
A kind of brain teaser. :laugh:
But you will only hard brick your device if bootloader is blank or corrupted. That's all.