Related
Hi, I want to (re-)flash the stock 4.1.2 rom on my Photon Q, because I recently run into some problems of the phone sending messages to the number 8737 even after I had removed the stock sms app.
This should be the right rsd file:
Code:
asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip (MD5: 88f43a03d313bbcc262db78f15ac957c)
I'm on linux and I don't have any Windows system I could install and run RSDLite on. So I decided to take the fastboot way: I unzipped the above file and tried flashing the rom manually. But I always run in to the following error output:
Code:
# fastboot flash cdrom cdrom
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 22923264 is not a multiple of the block size 4096
fastboot: ../libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
Note that "fastboot devices" lists the Photon Q as "T069503UAP fastboot". The same or a similar error messages applies to "fastboot flash system system.img" etc. I use fastboot from the Fedora 20 "android-tools" package (version 20130123git98d0789-2).
Any ideas what's the problem here? Solution?
Thanks in advance!
It's dangerous to try and fastboot the items yourself. Would be better to borrow a Windows PC or something to use RSD (virtual machines are also NOT recommended for this).
But perhaps you should just try to fastboot the other partitions. Not sure 'cdrom' is needed. Either way, I strongly, STRONGLY advise against doing what you are doing.
Okay, thanks for your advice!
The same or similar error messages appear when flashing the other partitions (as already mentioned in the first post). Unfortunately, it's really hard to find somebody with a Windows system, at the moment. I thought RSDLite uses fastboot internally anyway.
I'm not sure if the FXZ images can be flashed as they are, via fastboot.
I believe they should be converted to the standard ext4 format via the simg2img.py pytoon script, before being usable.
I repeat I'm not sure, but I believe that hardly motorola's own format is handled correctly by the fastboot command.
Whatever, for your convenience, I attach the mentioned converter script.
Aside fastboot, can be used for a variety of other purposes, the ext4 images can be mounted straight in Linux via loopback device or extracted in windows with a bunch of tools, personally I use Ftk Imager.
Thanks, that tool is great! After conversion, I was indeed able to mount the system partition as follows:
Code:
# mount -o ro,loop system_converted.img /some/mnt/path
But it doesn't help with the other files (cdrom, boot.img, recovery.img), because they seem to have a different format. However, the system partition was all I wanted. Now, instead of reflashing, I'm going to compare the system partition's files (especially in the "app" folder) and see what might have caused my problem.
tuxor1337 said:
But it doesn't help with the other files (cdrom, boot.img, recovery.img),
Click to expand...
Click to collapse
The boot, recovery and similar partitions aren't written on top of a filesystem like /system or /data.
they are written as they are on top of the physical media.
you can safely flash them in any way: fastboot, restore by recovery and so on.
unlike the filesystem based partitions, they are always in the same format.
If you need to edit the boot or recovery content you need a special script to unpack and repack them, many android kitchens have it
I was just wondering whether flashing on Linux will work when using "moto fastboot" like this one: http://forum.xda-developers.com/showthread.php?t=1138092
I don't really need this functionality anymore. But out of curiosity: What do you think?
My photon has a broken USB connector, so I can't test it in first person.
Btw, I believe that testing is the only way to understand what is flashable and what not, obviously taking handy a good full nandroid backup.
After an unfortunate restart yesterday from a misbehaving app, my phone has decided that the whole of the userdata partition is going to be read-only. At the very least, it's stopping me, fastboot, adb, and even the home launcher (when it boots) from running anything. Here's a video of the crash: http://youtu.be/8orBg5ivxsQ?t=1m3s
Now I've spent hours trawling through the various threads, and the ones that has got me closest to anything useful has been this one:
XDA Nexus 5 - [HOWTO][GUIDE] Repairing corrupted /data partition
Now the commands work well, and I have a list of the Moto G (16gb version) superblocks here:
/dev/block/platform/msm_sdcc.1/by-name/system on /system type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/userdata on /data type f2fs (rw,seclabel,relatime,background_gc=on,discard,user_xattr,inline_xattr,acl,errors=recover,active_logs=6)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,seclabel,relatime,noauto_da_alloc,data=writeback)
/dev/block/platform/msm_sdcc.1/by-name/fsg on /fsg type ext4 (rw,seclabel,nodev,noatime,nodiratime)
/dev/block/platform/msm_sdcc.1/by-name/modem on /firmware type ext4 (rw,seclabel,nodev,noatime,nodiratime,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/persist on /persist type ext4 (rw,seclabel,nodev,noatime,nodiratime,data=ordered)
Running e2fsk works on all but the userdata superblock, which is the one I cannot write to. It fails with the message
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>
Clearly I can't e2fsck the f2fs partition (and I have no fsck), does anyone have any suggestions?
----
Tried and failed:
Nandroid restore (none found and can't write a new one to storage)
ADB Shell reading/deleting anythign from /data/media/0/
fasboot flash *anything*
mfastboot flash *anything*
Enter Bootloader screen (power on with vol down held)
Option (1) - Try flashing the gpt.bin included in the Motorola Firmware Image. Fastboot command:
fastboot flash partition gpt.bin
Option (2) - Flash the entire firmware image by following this tutorial:
http://forum.xda-developers.com/showthread.php?t=2542219
NB. fastboot erase userdata - will wipe all photos, music etc. Linux and some versions of windows will give you access to ADB in Custom Recovery. From there you can backup photos / internal storage by running the command: adb pull /sdcard/ C:/motog/
Tell me what model you have and I can link you to the Motorola Firmware Image.
Thanks.
Running Option (1) gives me the messages "(bootloader) Preflash verification failed" and "FAILED (remote failure)" in cmd, and the error version downgraded for primary_gpt on the phone screen. I have also attempted Option 2, but again that apparently has no effect. Even flashing a different recovery image (CWM, TWRP, Stock) does not change anything.
Even something simple like running a nandroid backup command fails through recovery- hence me thinking that the partition has gone read-only.
The model is a 16gb UK XT1032.
You need to use a 4.4.4 firmware image. See the FAQ regarding 'Preflash verification failed.'
Retail UK 4.4.4:
http://forum.xda-developers.com/showthread.php?p=54872143
I downloaded the firmware file (you're correct, I was probably previously using a 4.3 image) and tried to flash it using both fastboot and mfastboot.
Despite both methods giving no errors, it has absolutely no effect on the recovery, or once the phone boots (still the same wallpaper that I can see through the lockscreen before I unlock it and everything crashes).
Here's a video of it crashing, just for reference (note that xposed is clearly installed, but flashing the 'remove xposed' zip also does nothing): http://youtu.be/8orBg5ivxsQ
Are you using fastboot or mfastboot? What commands have you used? Do the 'flash system system.img' commands actually match the filenames of the firmware you have downloaded?
I have tried both actually. Here's the log from using mfastboot but it's the same for both. No errors reported in cmd or on the phone, but it doesn't make any actual changes to anything. Bizarre.
{
"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"
}
Fastboot is not user-friendly because it is meant for use by engineers. You will not be given helpful error messages. Please see this related post about the danger of misusing fastboot: http://forum.xda-developers.com/showpost.php?p=56123415&postcount=23
Try all three versions of fastboot in this zip: https://www.androidfilehost.com/?fid=23578570567719065
To be clear, here is the full list of required Fastboot commands:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
NB. Are system.img_sparsechunk.0 / .1 / .2 the actual file-names? Some firmware images include a forth sparsechunk.
I have not knowingly run fastboot erase all (I didn't know that was a command actually, perhaps for the best).
I can confirm that the commands I am running are exactly as you suggest, and with all the correct files. I have written three different .bat files not that I can run from from the command line, using fastboot, mfastboot and fastboot-moto-windows.
No luck unfortunately, despite the positive messages from cmd and the bootloader.
Have you tried converting 'userdata' to ext4 and back to f2fs in custom recovery?
TWRP > Wipe > Advanced > Repair > select 'data' - then choose repair
Afterwards reflash sparsechunks if necessary.
I'm using Philz custom recovery, but I have found a similar option.
I have tried turning on the f2fs <-> ext4 option in Custom Recovery Options and run it on /data and /data/media.
Selecting etx4 the first time, no effect.
Selecting f2fs the second time, no effect.
(despite both times it saying it had succeeded)
Silently said:
I'm using Philz custom recovery, but I have found a similar option.
I have tried turning on the f2fs <-> ext4 option in Custom Recovery Options and run it on /data and /data/media.
Selecting etx4 the first time, no effect.
Selecting f2fs the second time, no effect.
(despite both times it saying it had succeeded)
Click to expand...
Click to collapse
hi
I have my moto g doing the exact same thing as yours in your video I cant even flash a custom recovery to mine if I flash anything it says its completed but its done nothing completely read-only your the only person ive found on the net with the same problem as me.
Have you got any where with your G?
thanks
Skinpipe said:
hi
Have you got any where with your G?
thanks
Click to expand...
Click to collapse
No luck, I'm afraid.
Silently said:
No luck, I'm afraid.
Click to expand...
Click to collapse
I have same issue. Hard reset/ wiped many times but it goes back to same screen. Ask same password (I know password) but when I type password it keep on crashing on each and every program. Also when I do repair file system it just keep on repairing. Any help??
talkways said:
Also when I do repair file system it just keep on repairing. Any help??
Click to expand...
Click to collapse
From what I understand, the actual memory of the phone has become corrupted (a bit like when a memory stick formats itself as RAW) and there's no way to fix it.
If memory is corrupted, it should not load Android operating system at all. :S
Any more advices??
Silently said:
From what I understand, the actual memory of the phone has become corrupted (a bit like when a memory stick formats itself as RAW) and there's no way to fix it.
Click to expand...
Click to collapse
I've exactly the same problem with my XT1032 4.4.4. No solution yet
talkways said:
If memory is corrupted, it should not load Android operating system at all. :S
Click to expand...
Click to collapse
Well that's a damn good point. I assume it is something to do with the block structure of the underlying file system then, and it is something there which is preventing disk writes.
Good. We figured out the problem. Any solution??
I have tried many recoveries but it goes to standard recovery. Only way to go to custom recovery is boot via command fastboot boot recovery.img.
Device bootloader is unlocked.
Hi, anyone fixed the problem? This happened to my wife's phone few days ago.
Bootloader unlocked
Recovery TWRP
rom Paranoid (based on 4.4.4 android)
please help
Hi,
I got the terrible error "mounting cache failed" blabla and my Nexus 5 was dead. I tried with all ways I could find: fastbook flash cache cache.img; flashing factory image; LG Flashtool and TOT flashing, etc. All did not work.
But finally I found out the reason and made my Nexus 5 back to work.
The reason is simple: my cache partition should be EXT2 (or EXT4) but for some reason its type is unknown. That caused the mounting failed.
You could check your partition tables like:
adb shell parted -s /dev/block/mmcblk0 print
Keep an eye on your cache partition (27) type. Bingo, you can fix it if its type is blank!!
Fix the type (in the shell):
1) boot into recovery mode
1.1) adb shell
1.2) mkfs.ext2 /dev/block/mmcblk0p27
1.3) exit
2) boot into Fastboot
Flash the factory image (flash-all.sh) is the simplest way to make sure all works. Or simply flash the cache.img
fastboot flash cache cache.img
Reboot and you will see your Nexus 5 is back.
Good luck.
Yu
http: // clashin.com/
zhudachang said:
Hi,
I got the terrible error "mounting cache failed" blabla and my Nexus 5 was dead. I tried with all ways I could find: fastbook flash cache cache.img; flashing factory image; LG Flashtool and TOT flashing, etc. All did not work.
But finally I found out the reason and made my Nexus 5 back to work.
The reason is simple: my cache partition should be EXT2 (or EXT4) but for some reason its type is unknown. That caused the mounting failed.
You could check your partition tables like:
adb shell parted -s /dev/block/mmcblk0 print
Keep an eye on your cache partition (27) type. Bingo, you can fix it if its type is blank!!
Fix the type (in the shell):
1) boot into recovery mode
1.1) adb shell
1.2) mkfs.ext2 /dev/block/mmcblk0p27
1.3) exit
2) boot into Fastboot
Flash the factory image (flash-all.sh) is the simplest way to make sure all works. Or simply flash the cache.img
fastboot flash cache cache.img
Reboot and you will see your Nexus 5 is back.
Good luck.
Yu
http: / / justcoolthings.net
Click to expand...
Click to collapse
Just want to say thank you for these steps! It fixed my phone as well and saved my sanity! LOL
5.1 OTA Update Screwed My Nexus 5
zhudachang said:
Hi,
I got the terrible error "mounting cache failed" blabla and my Nexus 5 was dead. I tried with all ways I could find: fastbook flash cache cache.img; flashing factory image; LG Flashtool and TOT flashing, etc. All did not work.
But finally I found out the reason and made my Nexus 5 back to work.
The reason is simple: my cache partition should be EXT2 (or EXT4) but for some reason its type is unknown. That caused the mounting failed.
You could check your partition tables like:
adb shell parted -s /dev/block/mmcblk0 print
Keep an eye on your cache partition (27) type. Bingo, you can fix it if its type is blank!!
Fix the type (in the shell):
1) boot into recovery mode
1.1) adb shell
1.2) mkfs.ext2 /dev/block/mmcblk0p27
1.3) exit
2) boot into Fastboot
Flash the factory image (flash-all.sh) is the simplest way to make sure all works. Or simply flash the cache.img
fastboot flash cache cache.img
Reboot and you will see your Nexus 5 is back.
Good luck.
Yu
http: // clashin.com/
Click to expand...
Click to collapse
Hi Yu,
I have the same problem as you mention above, occured after i had the office 5.1 OTA update 3 days back.
After updating, i was able to play with my phone for a while.. The next day, it was in a boot loop state with the "Google" image on my device.
I am able to ADB into my phone, and adb devices returns me my deviceId and sideload.
But when i attempt this command "adb shell" i get "error: closed".. Been searching the net to find out how to open this so i can do the fix, but none so far....
Any idea how to sort this out? Many thanks in advance.
p/s: my device is stock STOCK... non-unlock and non-rooted.
Cheers,
Keith
I would suggest you do a "flash-all" to your device.
1) Download the factory image ("hammerhead-lmy47i") from https: // developers.google.com /android/nexus/images
2) Boot your device into bootloader mode and run "flash-all.sh" to flash the 5.1 factory rom. It should fix all your errors.
Good luck.
Yu
liquanize said:
Hi Yu,
I have the same problem as you mention above, occured after i had the office 5.1 OTA update 3 days back.
After updating, i was able to play with my phone for a while.. The next day, it was in a boot loop state with the "Google" image on my device.
I am able to ADB into my phone, and adb devices returns me my deviceId and sideload.
But when i attempt this command "adb shell" i get "error: closed".. Been searching the net to find out how to open this so i can do the fix, but none so far....
Any idea how to sort this out? Many thanks in advance.
p/s: my device is stock STOCK... non-unlock and non-rooted.
Cheers,
Keith
Click to expand...
Click to collapse
liquanize said:
Hi Yu,
I have the same problem as you mention above, occured after i had the office 5.1 OTA update 3 days back.
After updating, i was able to play with my phone for a while.. The next day, it was in a boot loop state with the "Google" image on my device.
I am able to ADB into my phone, and adb devices returns me my deviceId and sideload.
But when i attempt this command "adb shell" i get "error: closed".. Been searching the net to find out how to open this so i can do the fix, but none so far....
Any idea how to sort this out? Many thanks in advance.
p/s: my device is stock STOCK... non-unlock and non-rooted.
Cheers,
Keith
Click to expand...
Click to collapse
Keep in mind that STOCK recovery does NOT let you connect to normal ADB, a custom recovery does. Also, you need to be root to 'mkfs.ext2', and the target partition must not be mounted, I believe.
Before attempting the steps @zhudachang posted below, i.e. To flash a factory image, you need to unlock your bootloader.
zhudachang said:
I would suggest you do a "flash-all" to your device.
1) Download the factory image ("hammerhead-lmy47i") from https: // developers.google.com /android/nexus/images
2) Boot your device into bootloader mode and run "flash-all.sh" to flash the 5.1 factory rom. It should fix all your errors.
Good luck.
Yu
Click to expand...
Click to collapse
hi everyone! i need someone to help me create an image for my phone. to make the story short, my data/userdata partition (11.62 gb) has not been created using sp flash tool during flash using format all+ download. but luckily i did the partinfo before..
C:\Program Files\Minimal ADB and Fastboot>adb shell cat /proc/partinfo
Name
userdata
Start
0x00000000a4000000
Size
0x00000002fed80000
since i dont have the partition anymore, is it possible to create one?
if it is, can someone teach me? im currently using windows 7 x32 bit.
hi everyone! i couldn't sleep so i was messing around on my phone.. so heres the fix.
note: you must have a custom recovery like twrp to fix the prob.
boot to recovery..
tap on wipe, format data
type yes..
goback to wipe, advanced wipe
check all except for the external sd-card (if you have)
then swipe
done!
that's it!! you should be able to get back /data partition!
Greetings all.
Several weeks ago, I made this post seeking help with a self-created problem. I am happy to announce that the problem has been resolved with the immense help of sephstyler. He is literally my phone's messiah.
The afore-mentioned XDA member has a device identical to mine. I borrowed his and mirrored most of the data on his device by copying several partitions off his phone on to mine. I followed this guide about changing CID/MID.
I got a hold of a notepad document (you'll find it here) that lists partition information of the U11+. I wasn't sure which of my partitions were corrupt but I was certain the one containing the OS and IMEI information were messed up. My IMEI was blank. The OS version reported in fastboot was 9.99999 or something like that.
So I set out to copy these partitions and their corresponding img files in no particular order - boot, hosd, radio, modemst1, modemst2, cache, system, vendor, persist, and sdf1 (which carries CID info).
Please note that this method fixes the issue where your device is stuck on the bootloader screen with the message, "this phone has been flashed with unauthorised software and is locked....." And you will need a second device that is identical to yours (and functional too) for this process to work. I don't know if they both have to come from the same region (i.e have the same CID and MID). I guess there is no harm in trying. You couldn't possibly do more harm to your device by doing this. Or maybe you could. Either way, I will not be held responsible for any undesirable outcomes.
Steps taken:
- I installed HTC drivers on my computer, running Windows 10 64-bit. And 15-second ADB Installer. Get them both from here and here. I uninstalled HTC Sync Manager after the installation was done as I only needed the drivers.
- I flashed TWRP on the borrowed device so I could have access to adb from recovery.
- I then opened up a command prompt window on my computer, typed adb devices just to be sure that drivers were installed correctly.
The next few steps can be achieved right from within TWRP using the Terminal function. But I chose to use my computer as it'd be much quicker and I am less likely to make typos on a full-sized keyboard.
In a command prompt window, type adb shell. Hit enter.
To copy the system image, type dd if=/dev/block/sda5 of=/sdcard/system.img
For cache, type dd if=/dev/block/sdd21 of=/sdcard/cache.img
For boot, type dd if=/dev/block/sda3 of=/sdcard/boot.img
For radio, type dd if=/dev/block/sdd13 of=/sdcard/radio.img
For modemst1, type dd if=/dev/block/sde2 of=/sdcard/modemst1.img
For modemst2, type dd if=/dev/block/sde3 of=/sdcard/modemst2.img
For persist, type dd if=/dev/block/sde5 of=/sdcard/persist.img
For vendor, type dd if=/dev/block/sda6 of=/sdcard/vendor.img
For sdf1 (board_info), type dd if=/dev/block/sdf1 of=/sdcard/sdf1.img
For hosd, type dd if=/dev/block/sdd12 of=/sdcard/hosd.img
These img files would be saved to your internal storage. I then copied all files to the root folder of my faulty device's storage using Windows Explorer. System.img however refused to transfer. I got creative and used a microSD to make the transfer possible.
Now that these files were sitting comfortably on my phone, I booted to TWRP, connected it to my PC, then entered the following commands in Command Prompt via adb shell.
To copy these images to the appropriate partitions on your phone:
For board_info, type dd if=/sdcard/sdf1.img of=/dev/block/sdf1
For system, type dd if=/sdcard/system.img of=/dev/block/sda5
For cache, type dd if=/sdcard/cache.img of=/dev/block/sdd21
For boot, type dd if=/sdcard/boot.img of=/dev/block/sda3
For radio, type dd if=/sdcard/radio.img of=/dev/block/sdd13
For modemst1, type dd if=/sdcard/modemst1.img of=/dev/block/sde2
For modemst2, type dd if=/sdcard/modemst2.img of=/dev/block/sde3
For persist, type dd if=/sdcard/persist.img of=/dev/block/sde5
For vendor, type dd if=/sdcard/vendor.img of=/dev/block/sda6
For hosd, type dd if=/sdcard/hosd.img of=/dev/block/sdd12
Upon completion, press Ctrl+C or type exit to quit adb shell. Then type adb reboot to reboot your device.
If the above commands were entered correctly (and if the adb gods smile upon you), your device should be restored.
Now I know that copying all images fixed the issue. My guess is the system, boot, and radio images were the crucial ones. I am not entirely sure. But I was desperate for a positive result so I copied the ones that I deemed important.
I hope this helps someone. Cheers.
P.S: My apologies for the formatting. I am still fairly new to this. Also, I just realised I could upload these images for anyone who doesn't have access to a second device. I shall update the post with download links after the upload's completed. Sorry about the brain fart.
[EDIT] Images are up. You can find them here. These files are for the Taiwan-based HTC U11+ (CID - HTC_621)
Nice tutorial.
Hi, I'm having a similar problem with my U11+.... followed ur download link but a decryption key is needed. whats the decryption key?
ChuDust said:
Hi, I'm having a similar problem with my U11+.... followed ur download link but a decryption key is needed. whats the decryption key?
Click to expand...
Click to collapse
Here's the key. I had no idea the files were encrypted to begin with. Sorry about that.
-b087zdU9re0k3e3HHah1w
P.S: Since you're downloading the image files from the link provided, you don't have to go through the first half of the process - copying data from a working phone to an external location.
Best of luck.
Hello. I have an identical situation. My original CID is 622. I changed the CID to 001, but after RUU firmware I could not boot into the system. Now after flash RUU, the phone will reboot into the bootloader. Can anyone help me?
Do you have to be rooted or with unlocked bootloader to be able to backup the phone partitions using this method ?
Or does it just work on completely stock from an db connection to PC ?
Thank you.
The bootloader needs to be unlocked at the very least so you can gain access to the required partitions. Root isn't necessary.
Hope this helps.
Hello, I followed your instructions and made backups of my partitions from HTC U11+ dual-sim european version 401.12.
With unlocked bootloader and rooted with magisk by patched boot image.
Ran adb shell and su while phone was running normally in Android OS and connected to PC.
I'm curious about the sizes of the images created because they don't match with the sizes from partitions.txt.
For example "4210688 sda5 - system" is actually 4,311,744,512 bytes,
"65536 sda3 - boot" is actually 67,108,864 bytes in created image, but the actual boot.img from the OTA file is 38,163,762 bytes.
If these sizes are different can I actually trust the created images ? and use them in need.
Can these created images be flashed by fastboot, for example for system.img: "fastboot flash -S 1G system system.img" ?
Thanks.
andreipaval said:
I'm curious about the sizes of the images created because they don't match with the sizes from partitions.txt.
For example "4210688 sda5 - system" is actually 4,311,744,512 bytes,
"65536 sda3 - boot" is actually 67,108,864 bytes in created image, but the actual boot.img from the OTA file is 38,163,762 bytes.
Thanks.
Click to expand...
Click to collapse
If you divide the 4,311,744,512 bytes by the 1024, you get what you need - 4210688 - this is in Kb.
And so same for boot - 67,108,864 bytes / 1024 = 65536 Kb.
andreipaval said:
Hello, I followed your instructions and made backups of my partitions from HTC U11+ dual-sim european version 401.12.
With unlocked bootloader and rooted with magisk by patched boot image.
Ran adb shell and su while phone was running normally in Android OS and connected to PC.
I'm curious about the sizes of the images created because they don't match with the sizes from partitions.txt.
For example "4210688 sda5 - system" is actually 4,311,744,512 bytes,
"65536 sda3 - boot" is actually 67,108,864 bytes in created image, but the actual boot.img from the OTA file is 38,163,762 bytes.
If these sizes are different can I actually trust the created images ? and use them in need.
Can these created images be flashed by fastboot, for example for system.img: "fastboot flash -S 1G system system.img" ?
Thanks.
Click to expand...
Click to collapse
Hi. I hope your first question was answered. Regarding your second concern, I'm afraid I don't have an answer to that. At the time, flashing any image files onto my device didn't fix the issue even though each flash completed successfully. Copying them manually sure did.
Hope this helps.
Do you have the twrp backup of the stock rom?
andreipaval said:
Hello, I followed your instructions and made backups of my partitions from HTC U11+ dual-sim european version 401.12.
With unlocked bootloader and rooted with magisk by patched boot image.
Ran adb shell and su while phone was running normally in Android OS and connected to PC.
I'm curious about the sizes of the images created because they don't match with the sizes from partitions.txt.
For example "4210688 sda5 - system" is actually 4,311,744,512 bytes,
"65536 sda3 - boot" is actually 67,108,864 bytes in created image, but the actual boot.img from the OTA file is 38,163,762 bytes.
If these sizes are different can I actually trust the created images ? and use them in need.
Can these created images be flashed by fastboot, for example for system.img: "fastboot flash -S 1G system system.img" ?
Thanks.
Click to expand...
Click to collapse
Hello,
do you have the twrp backup of stock rom?
I did not make backups with twrp.