Related
How do I will erase the System and Data by mistake in twrp?
Backup does not take ....
Now it has come out warning the state OS is not.
I'm using ze552kl.
try flash the stock image.
BentotKulangot said:
try flash the stock image.
Click to expand...
Click to collapse
Thank you for your reply.
Because the way the writing of the ROM image is not know I was trying to write the system image "fastboot flash system system.img", but the error of the following did not go well occur.
Error description: "target reported max download size of 536870912 bytes
Invalid sparse file format at header magi "
Size of system.img is 4,026,286,080 byte.....
Try flashing a custom recovery like twrp then flashing the stock firmware
hello the ruu files for m9+ of various firmwares and regions have been uploaded recently ,so finally can get back to stock if we can flash and have the lastest android marshmello ota update
if anyone can donate their account on ir files
then we could download the files
or also u can upload the files from this link
http://ir-file.com/?p=Firmware/htc/htc_android/hiau_ml_tuhl
the currently needed lastest firmware in india is this:
0pk7img_hiau_ml_tuhl_l50_sense70_mr_htc_asia_wwe_1.90.707.3_radio_1.1506v24p22t34.2106.0727_ht[w.t]_release_464127_signed.zip
if anyone can please upload the file
yeah if someone can donate their login details or upload the firmware that would be a huge help.
I have the firmware if you still need it i'll try to upload it
mqum said:
I have the firmware if you still need it i'll try to upload it
Click to expand...
Click to collapse
it would be a huge huge help man if u upload this one
0pk7img_hiau_ml_tuhl_l50_sense70_mr_htc_asia_wwe_1 .90.707.3_radio_1.1506v24p22t34.2106.0727_ht[w.t]_release_464127_signed.zip
The upload is gonna take almost 2 days
Do not upload the gsm developers version ..It is not going back to stock even after several attempts
well i used that version and i got back to stock and now updated to 6.0
what error did you get?
No error I suppose but it did not get back to stock after flashing
Could you tell the exact process on how you do it ?
I relocked the bootloader
Renamed the firmware to 0PK7IMG.zip and placed it in my fastboot folder
Reboot to RUU OEM mode
Flashed the firmware with fastboot
after the phone started root was gone but bootloader still says software modified
then downloaded OTA update from phone and it worked now i have 6.0
please explain whats your problem i might be able to help solve it
C:\Users\Downloads\ruu htc m9+\New folder>fastboot flash zip Rom.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2311809023 is not a multiple of
the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2311809023 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 2311809023 is not a multiple of
the block size 4096
OKAY [ 1.121s]
writing 'zip' 1/1...
(bootloader) HOSD CL#670935
(bootloader) ERR preprocess_file : Cannot read header len bytes
(bootloader) ERR preprocess_file() failed
(bootloader) [email protected]
FAILED (remote: 3: fail to flash via downloadzip)
finished. total time: 2.171s
I'm having this issue while flashing it now .
Not understanding what's the real cause though
Could you explain how to solve ?
use this fastboot https://drive.google.com/open?id=0BzGqhf-ICYRYTUFDUnUtcF9NdDA
rename the firmware to 0PK7IMG.zip
open cmd from the fastboot folder i sent not the one you already have
fastboot oem rebootRUU
fastboot flash zip 0PK7IMG.zip
mqum said:
use this fastboot https://drive.google.com/open?id=0BzGqhf-ICYRYTUFDUnUtcF9NdDA
rename the firmware to 0PK7IMG.zip
open cmd from the fastboot folder i sent not the one you already have
fastboot oem rebootRUU
fastboot flash zip 0PK7IMG.zip
Click to expand...
Click to collapse
thank you so much i was able to flash mine
mine said that adb is out dated so replaced with the latest one and it worked fine
, now im downloading the update hope it will install
and yes my root has been unistalled i've not checked the bootloader though
In this thread u can find "HOW TO COMPLETLY RELOCK DEVICE" / UNBRICK VIDEO TUTORIAL
" ADB COMMAND METHOD":
In this method You can find how to unbrick device
If your device is only capable to access fastboot mode only
1.Find your stock firmware HERE
2.DOWNLOAD HuaweiUpdate extrator below in download section
3.open HuaweiUpdateExtractor select the update.app which was extracted from firmware zip
4.then extract the following files :::
-->boot .img
-->cust.img
-->recovery.img
-->system.img
Then boot your device into fastboot ,open adb command then type
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
device is now working but bootloader is still unlocked.
to lock the bootloader reboot your device into fastboot mode type :::
fastboot oem lock (your 16 digit bootloader code)
<<if it fails>>
then copy the update.app which was extrated earlier into sd card / dload
then force update by pow+volume +&volume-
THAT'S it UR DEVICE IS NOW FULLY LOCKED.
FOR VIDEO TUTORIAL :::
https://youtu.be/OMKDnBqbi3U
When flashing
fastboot flash cust cust.img
i get
target reported max download size of 471859200 bytes
sending 'cust' (433554 KB)...
OKAY [ 13.837s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 13.848s
In twrp i can see that the "cust" partition is 184MB, the cust.img il over 400MB, can be this the problem?
mandelbort said:
When flashing
fastboot flash cust cust.img
i get
target reported max download size of 471859200 bytes
sending 'cust' (433554 KB)...
OKAY [ 13.837s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 13.848s
In twrp i can see that the "cust" partition is 184MB, the cust.img il over 400MB, can be this the problem?
Click to expand...
Click to collapse
The bootloader is in unlock state or not??
VenuGopalu said:
The bootloader is in unlock state or not??
Click to expand...
Click to collapse
Unlock
are us using the last firmware? and also try all steps one more time respectively .. is your device working fine now
My tablet is Lenovo yoga tab 3 plus, I have rooted my tablet, and after downloading the update, an error occured, and here is the log:
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Source: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000691_161121_PRC:user/release-keys
Target: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000728_170211_PRC:user/release-keys
Verifying current system...
"EMMC:/dev/block/bootdevice/by-name/boot:31655208:db7b430aac30b324daddf17bcdb14201a6468700:31655208:4de06d70f69d35ffa0a0aa0c6975385a3c937030" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation abroated.
E:failed to mount /data (Invaild argument)
I think if we can bypass verification, we can install update while the device is rooted.
Any can help us?
zkn1021 said:
My tablet is Lenovo yoga tab 3 plus, I have rooted my tablet, and after downloading the update, an error occured, and here is the log:
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Source: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000691_161121_PRC:user/release-keys
Target: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000728_170211_PRC:user/release-keys
Verifying current system...
"EMMC:/dev/block/bootdevice/by-name/boot:31655208:db7b430aac30b324daddf17bcdb14201a6468700:31655208:4de06d70f69d35ffa0a0aa0c6975385a3c937030" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation abroated.
E:failed to mount /data (Invaild argument)
I think if we can bypass verification, we can install update while the device is rooted.
Any can help us?
Click to expand...
Click to collapse
So the easiest way is to restore the boot and system partition to the original S000725 version using fastboot and then install the update, but only if you are on S000725 now. If you are sure that you didn't modify the system partition (any root app installed system less) then the boot partition is sufficient. Flashing these two partitions will not delete your apps and settings.
Here is what to do:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
Extract it and get the boot.img and system.img files
restart into fastboot mode (e.g. via adb reboot bootloader, or restart the tablet with volume up key pressed)
Execute fastboot on your PC connected to the tablet with the following command:
Code:
fastboot flash boot boot.img
If the system partition was modified you will have to do the same for system
Code:
fastboot flash system system.img
If TWRP is flashed you also have to restore the recovery partition
Code:
fastboot flash recovery recovery.img
You can also install the factory image via the supplied flash tool. But we're not 100% sure it is safe wrt. DRM keys
Sometimes the flashing of such large partitions as the system partitions can fail in which case you have to do it again until it works. If you run into a bootloop after flashing the boot.img your system partition is not original and you have to flash the system.img again
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
matshias said:
So the easiest way is to restore the boot and system partition to the original S000725 version using fastboot and then install the update, but only if you are on S000725 now. If you are sure that you didn't modify the system partition (any root app installed system less) then the boot partition is sufficient. Flashing these two partitions will not delete your apps and settings.
Here is what to do:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
Extract it and get the boot.img and system.img files
restart into fastboot mode (e.g. via adb reboot bootloader, or restart the tablet with volume up key pressed)
Execute fastboot on your PC connected to the tablet with the following command:
Code:
fastboot flash boot boot.img
If the system partition was modified you will have to do the same for system
Code:
fastboot flash system system.img
You can also install the factory image via the supplied flash tool. But we're not 100% sure it is safe wrt. DRM keys
Sometimes the flashing of such large partitions as the system partitions can fail in which case you have to do it again until it works. If you run into a bootloop after flashing the boot.img your system partition is not original and you have to flash the system.img again
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
Click to expand...
Click to collapse
Thank you！
I'm wondering whether I have to root again after restoring the boot and system partitions.
I got the OTA update package, can I flash it directly via recovery? I have rooted my tablet.
zkn1021 said:
Thank you！
I'm wondering whether I have to root again after restoring the boot and system partitions.
Click to expand...
Click to collapse
zkn1021 said:
I got the OTA update package, can I flash it directly via recovery? I have rooted my tablet.
Click to expand...
Click to collapse
Well first unroot by flashing boot and system, then install update in Lenovo recovery. Yes it's possible to do that. Then when the update installed successfully you can root again with TWRP and SuperSU.
brothers, I skipped system verifying by editing updater-script, but the OTA still failed because signature verifying failed.
Anyone knows how to skip signature verifying?
If we can skip that, we may install ota update package manually while the device is rooted.
matshias said:
the easiest way is to restore the boot and system partition .
...
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
hi! how can i make a backup of my currently partitions (before rooting and so on) to make possible flash them back with "fastboot flash ..."?
is the command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
makes the image compatible with "fastboot flash ..." command? or i have to convert it somehow?
P.s. yes i know about restoring with command "dd if=/sdcard1/system.img of=/dev/block/bootdevice/by-name/system", but i want to have other ways to retreat
DGolovin said:
hi! how can i make a backup of my currently partitions (before rooting and so on) to make possible flash them back with "fastboot flash ..."?
is the command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
makes the image compatible with "fastboot flash ..." command? or i have to convert it somehow?
P.s. yes i know about restoring with command "dd if=/sdcard1/system.img of=/dev/block/bootdevice/by-name/system", but i want to have other ways to retreat
Click to expand...
Click to collapse
In TWRP (via adb or TWRP terminal) you can use the command that you listed to make backups of existing partitions. The system partition is a bit special though. The dd command will give you the raw partition image. Fastboot, however, expects the system partition in sparse format. To convert you need the tool "img2simg".
The other partitions are expected in raw format by fastboot.
Unless you have a special firmware version you don't have to create these backups since we have factory images which contain exactly these partition images. Boot, recovery and system partitions are the same for all devices with the same device variant and software version.
matshias said:
In TWRP (via adb or TWRP terminal) you can use the command that you listed to make backups of existing partitions. The system partition is a bit special though. The dd command will give you the raw partition image. Fastboot, however, expects the system partition in sparse format. To convert you need the tool "img2simg".
The other partitions are expected in raw format by fastboot.
Unless you have a special firmware version you don't have to create these backups since we have factory images which contain exactly these partition images. Boot, recovery and system partitions are the same for all devices with the same device variant and software version.
Click to expand...
Click to collapse
Thanks for eхplain. I have downloaded your backups of 734th firmware for Lenovo Yoga 3 Plus F already but new knowlege will not be redundant
Hello,
Tried "adb reboot bootloader" but it only stuck with Lenovo logo. So I tried to flash boot.img using app.
Now stuck with boot loop. Manage to go into Recovery Mode - Is there any way I could restore anything from Recovery? .zip
Thank you
Hi guys,
I got n OTA update. I only did the root process from https://forum.xda-developers.com/th...ta-twrp-root-disable-encryption-yoga-t3538017 before.
After doing the "fastboot flash boot boot.img" to allow the OTA update from this thread, I got a reboot loop (soft brick right?) when I try to go to recovery, i got this
https://photos.google.com/share/AF1QipMLfvQnTcKCr4lJ6ImnPHsb9_s5aR_ERj_k_oIuhhg_k6aGD2yNen8H9y7tdhPLOA?key=T2FYdmZSZ204OFczejB0dXpGOGlRdG1aNXBvckln
any help? sadly, I'm a noob u.u
thxs
NtahX said:
Hello,
Tried "adb reboot bootloader" but it only stuck with Lenovo logo. So I tried to flash boot.img using app.
Now stuck with boot loop. Manage to go into Recovery Mode - Is there any way I could restore anything from Recovery? .zip
Thank you
Click to expand...
Click to collapse
The fastboot mode (bootloader) only shows the Lenovo logo. So this is expected. If you get a bootloop you also have to flash system.img via fastboot. So do the adb reboot bootloader again and use fastboot tool on the PC to do the flashing
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
dasinflames said:
Hi guys,
I got n OTA update. I only did the root process from https://forum.xda-developers.com/th...ta-twrp-root-disable-encryption-yoga-t3538017 before.
After doing the "fastboot flash boot boot.img" to allow the OTA update from this thread, I got a reboot loop (soft brick right?) when I try to go to recovery, i got this
https://photos.google.com/share/AF1QipMLfvQnTcKCr4lJ6ImnPHsb9_s5aR_ERj_k_oIuhhg_k6aGD2yNen8H9y7tdhPLOA?key=T2FYdmZSZ204OFczejB0dXpGOGlRdG1aNXBvckln
any help? sadly, I'm a noob u.u
thxs
Click to expand...
Click to collapse
Same thing. Your system partition is not original that's why you have the boot loop. You have to flash the original version via fastboot.
matshias said:
The fastboot mode (bootloader) only shows the Lenovo logo. So this is expected. If you get a bootloop you also have to flash system.img via fastboot. So do the adb reboot bootloader again and use fastboot tool on the PC to do the flashing
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
Same thing. Your system partition is not original that's why you have the boot loop. You have to flash the original version via fastboot.
Click to expand...
Click to collapse
Code:
c:\adb>fastboot flash system system_yt_x703f_s000734.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.626s]
sending sparse 'system' (516880 KB)...
OKAY [ 18.443s]
writing 'system'...
OKAY [ 7.726s]
sending sparse 'system' (507198 KB)...
OKAY [ 18.163s]
writing 'system'...
OKAY [ 7.812s]
sending sparse 'system' (511833 KB)...
OKAY [ 18.332s]
writing 'system'...
OKAY [ 7.876s]
sending sparse 'system' (514911 KB)...
OKAY [ 18.410s]
writing 'system'...
OKAY [ 7.345s]
sending sparse 'system' (514937 KB)...
OKAY [ 18.282s]
writing 'system'...
OKAY [ 7.369s]
sending sparse 'system' (511997 KB)...
OKAY [ 18.328s]
writing 'system'...
OKAY [ 22.033s]
sending sparse 'system' (156572 KB)...
OKAY [ 5.703s]
writing 'system'...
OKAY [ 17.717s]
finished. total time: 194.195s
c:\adb>fastboot flash recovery recovery_yt_x703f_s000734.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.078s]
writing 'recovery'...
OKAY [ 0.829s]
finished. total time: 2.907s
Since I already flashed boot.img yesterday, continue with system & recovery. I didn't know that Download mode will only shows Lenovo logo. Normally it will shows what running on the background. Did as told and manage to recover. Sadly I've wiped cache & data in Recovery yesterday, now back to square 1. But at least better than bricked device. Thank you.
matshias said:
The fastboot mode (bootloader) only shows the Lenovo logo. So this is expected. If you get a bootloop you also have to flash system.img via fastboot. So do the adb reboot bootloader again and use fastboot tool on the PC to do the flashing
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
Same thing. Your system partition is not original that's why you have the boot loop. You have to flash the original version via fastboot.
Click to expand...
Click to collapse
the only way that my tablet can to be recognized in my computer is with sideload. I'll try with that method.
thxs!!
PS: I used at the end the Multiflashtool and now my tablet works perfectly
if someone has the parallel problem, here is the solution: http://www.mediafire.com/download/58upc51o93ux2f4/Archivo+StargetDawn.rar
just install and execute the multiflash program.
greetings
matshias said:
So the easiest way is to restore the boot and system partition to the original S000725 version using fastboot and then install the update, but only if you are on S000725 now. If you are sure that you didn't modify the system partition (any root app installed system less) then the boot partition is sufficient. Flashing these two partitions will not delete your apps and settings.
Here is what to do:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
Extract it and get the boot.img and system.img files
restart into fastboot mode (e.g. via adb reboot bootloader, or restart the tablet with volume up key pressed)
Execute fastboot on your PC connected to the tablet with the following command:
Code:
fastboot flash boot boot.img
If the system partition was modified you will have to do the same for system
Code:
fastboot flash system system.img
If TWRP is flashed you also have to restore the recovery partition
Code:
fastboot flash recovery recovery.img
You can also install the factory image via the supplied flash tool. But we're not 100% sure it is safe wrt. DRM keys
Sometimes the flashing of such large partitions as the system partitions can fail in which case you have to do it again until it works. If you run into a bootloop after flashing the boot.img your system partition is not original and you have to flash the system.img again
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
Click to expand...
Click to collapse
I'm sorry to bother you again.
Someone made a backup via twrp, and got these files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win000
system.ext4.win000.md5
system.ex4.win001
system.ext4.win001.md5
system.info
How to continue with these files?
Thank you!
zkn1021 said:
I'm sorry to bother you again.
Someone made a backup via twrp, and got these files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win000
system.ext4.win000.md5
system.ex4.win001
system.ext4.win001.md5
system.info
How to continue with these files?
Thank you!
Click to expand...
Click to collapse
Well it seems you have to request the backup again. system.ext4 is a file based backup. This will not restore to a 100% original system image. The person who provided this for you has to run it again and select "system image" instead of "system" when creating the backup. This will then be a binary copy of the system partition.
Once you have that you should create a backup using TWRP on your own device with boot and system image selected onto an external SD card. Don't forget to boot TWRP with system left read only. Then you replace the *.win* files (also the .md5 files) on you SD card with ones you get from this person files. Then reinsert the SD card into the tablet and select restore in TWRP. Then the two partitions should be original if the person you got them from didn't modify it somehow.
I am not sure which format TWRP uses to store these partition images but if the above doesn't work we'll figure out how to extract it.
matshias said:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
Click to expand...
Click to collapse
hello iam on s000689 and i have a hard time trying to find that recovery image... can i just you S000725 and then not have OTA updates?
After flashing some roms I came across the following situations:
1: mtp on recovery twrp no longer works. (Previously used normally)
2: I can not install any rom custon (even those based on rom stock)
3: I can not install rom 19S or larger via fastboot (bootloader)
4: I can not install any rom stock (even if I use official recovery)
* Fastboot flash system system.img
Target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Please help me!
Help please, I can not install any roms!
1: mtp on recovery twrp no longer works. (Previously used normally)
2: I can not install any rom custon (even those based on rom stock)
3: I can not install rom 19S or larger via fastboot (bootloader)
4: I can not install any rom stock (even if I use official recovery)
* Fastboot flash system system.img
Target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Please help me![/QUOTE]
Turn ON in dev options;
-OEM unlock
-Debugging
Turn on your phone in bootloader mode, turn on ADB and write;
- "fastboot oem unlock-go"
Download TWRP that should work with your model (x720 or x727, pick correct) and flash it through bootloader.
- "fastboot flash recovery twrp.img" (or another name that your TWRP image in adb folder have)
- "fastboot boot twrp.img" (as same)
After this, your phone should be in Recovery <TWRP> mode. It should ask about keep System Read only.
- Swipe to Allow Modification
If this steps won't help you, you should make wipe. But if you can't install OS now, it's riskable, so I won't to guide you there.
* or if your trouble is a upgrade from stock to stock OS, unlocked bootloader and TWRP can be a problem.
Rone3285 said:
After flashing some roms I came across the following situations:
1: mtp on recovery twrp no longer works. (Previously used normally)
2: I can not install any rom custon (even those based on rom stock)
3: I can not install rom 19S or larger via fastboot (bootloader)
4: I can not install any rom stock (even if I use official recovery)
* Fastboot flash system system.img
Target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Please help me!
Click to expand...
Click to collapse
marik1 said:
Turn ON in dev options;
-OEM unlock
-Debugging
Turn on your phone in bootloader mode, turn on ADB and write;
- "fastboot oem unlock-go"
Download TWRP that should work with your model (x720 or x727, pick correct) and flash it through bootloader.
- "fastboot flash recovery twrp.img" (or another name that your TWRP image in adb folder have)
- "fastboot boot twrp.img" (as same)
After this, your phone should be in Recovery <TWRP> mode. It should ask about keep System Read only.
- Swipe to Allow Modification
If this steps won't help you, you should make wipe. But if you can't install OS now, it's riskable, so I won't to guide you there.
* or if your trouble is a upgrade from stock to stock OS, unlocked bootloader and TWRP can be a problem.
Click to expand...
Click to collapse
I was with the rom "GROSSOSHOP 18S", then cleaned all data including system, and installed rom "MIUI 8 VillarLeg V2", after testing the rom I tried to go back to stock, I did the following:
1 - I cleaned all data including system
2 - put the rom rom in the internal memory and rename to update.zip
3 - I tried to install the rom, but got stuck in: patching system image unconditionally
After several attempts to install rons, only to achieve with "GROSSOSHOP 17S" via fastboot. It seemed that everything was solved, but I can not install any more roms except for fastboot, I already tried with stock recovery and twrp, but it does not work at all!
Check dev options and oem unlock...