Hi all,
I'm far from an Android specialist so please excuse me if I don't fully understand you in a technical sense.
I'm trying to root my Note 4 and failing miserably, when comparing my rooting process to those of others who are successful I only see one difference.
When installing SuperSU I get this error:
******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/mmcblk0p17
- Extracting ramdisk
- Decompressing ramdisk
- Checking patch status
--- Already patched, attempting to find stock backup
--- Stock restore failed, attempting ramdisk restore
--- Ramdisk restore failed, aborting
When watching other install in the exact method I do, it just continues installing after "- Checking patch status"
Any advice/guidance would be greatly received
Cheers,
TRL1995
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?
I tried to update stock phone via Firmware Finder from B170 to B360. Downloaded fine and asked for restart. Phone said it was updating but froze at 5% and restarted by itself and bootlooping.
Holding Vol+ and power on leads to "EMUI installing update..." screen, then "Software install failed!" with only option to
Reboot system now
Rebooting takes phone to Huawei eRecovery with options
Download latest version and recovery
Reboot
Shutdown
Download and recovery ends with "Getting package info from server" which eventually fails
I can enter Fastboot & Rescue Mode, but phone is LOCKED (in green text) so cannot flash
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 532676608 bytes
sending 'recovery' (41787 KB)...
OKAY [ 1.471s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.487s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 532676608 bytes
sending 'boot' (33249 KB)...
OKAY [ 1.166s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 1.197s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 532676608 bytes
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
Also, the phone is not being recognized by HiSuite latest version (8.0.1.302), and not supported by HiSuite System Recovery!
I've been reading through these forums and Googling but nothing is helping! :crying: Phone is out of warranty as it's a hand-me-down. Are paid options like DC unlocker the only way?
Anyone? Or is this phone too outdated now?
I managed to get microSD card for phone but still having troubles. I put UPDATE.APP into dload folder on root of microSD and boot with three button press but installation gets stuck and fails at 42%. I've tried with all FullOTA-MF roms from Firmware Finder, no success.
if your bootloader is unlocked see this post: https://forum.xda-developers.com/showpost.php?p=74624117&postcount=2
zaabolla said:
if your bootloader is unlocked see this post: https://forum.xda-developers.com/showpost.php?p=74624117&postcount=2
Click to expand...
Click to collapse
It was locked (getting the 14 day message before) but I tried to unlock again through the EMUI website and it worked!
So I successfully flashed TWRP 3.0.3.0. but I cannot install zips, encountering this error for all versions B360, B358, B356, and B170.
Code:
Installing zip file '/external_sd/dload/update.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
mountencrypt: failed to mount /data: No such file or directory
Removing unneeded files...
Patching system files...
Removing empty directorys...
Unpacking new files...
add link type file...
write radio image...
error:oemsbl version write error!
check_write_data_to_partition,write data error
[COLOR="Red"]E:unknown command [errno][/COLOR]
update_huawei_pkg_from_ota_zip: update package from zip failed
[COLOR="red"]Updater process ended with ERROR: 7
Error installing zip file 'external_sd/dload/update.zip[/COLOR]
Updating partition details...
...done
I tried the steps in that post above but there are issues when copying the contents to the device as process hangs at file system.ext4.win000, saying 3 minutes remaining forever, eventually stopping the process itself.
Any further steps? I feel like I am one step closer to unbricking this device though.
i don't know what are you doing like that
flashing official rom is with original recovery not with TWRP recovery
with TWRP you can flash only custom roms like lineage, or restore backup rom
---------- Post added at 12:58 PM ---------- Previous post was at 12:56 PM ----------
and copy backup files to an sdcard with PC, and try the new TWRP
Oh, hmm, silly me then
Anyway, the restore worked fine when put on microSD card. Reboot failed stating an error in Chinese text (don't know what it says), and keeps rebooting into TWRP.
System not booting anyway so flashed LineageOS.zip but during the process, log showed "failed to mount /product (invalid argument)". Reboot phone and it's stuck on Lineage OS boot animation for over 30 minutes
Updated TWRP to latest 3.1.1-0
Changed the filesystem to f2fs and the TWRP backup in that post booted! Everything seems to be working except the phone is branded as CAN.
Flashing any version of stock MLA-TL10 firmware with stock recovery still fails at 42% just like before though. And flashing Lineage OS still hangs on boot animation like before as well.
I think I'll just leave the phone as is in stock Android 6.0, at least it's useable now
Flashed TWRP 3.1.1-0. The log says Failed to mount /product (invalid argument). Never had this error before but everything seems to be working fine.
Just got an idea, if anyone can kindly provide a TWRP backup I can try restoring to that.
i am trying to restore twrp backup but there's a problem
Failed to mount /product (invalid argument).
Failed to mount /cust (invalid argument).
and there's no file name cust and product in offical firmware update.app and any other i had try 3 or 4 firmware's but didnt find any file name in update.app using huawei firmware extractor can you guys please help me out? my phone is stuck on bootloader unlocked option power button for continue col up button for ercovery
my bootloaders are unlocked
---------- Post added at 05:32 PM ---------- Previous post was at 05:32 PM ----------
i am trying to restore twrp backup but there's a problem
Failed to mount /product (invalid argument).
Failed to mount /cust (invalid argument).
and there's no file name cust and product in offical firmware update.app and any other i had try 3 or 4 firmware's but didnt find any file name in update.app using huawei firmware extractor can you guys please help me out? my phone is stuck on bootloader unlocked option power button for continue col up button for ercovery
my bootloaders are unlocked
I bicked my P9 Lite and need some help with it. The main problem is, that I "accidentally" wiped my vendor and product partitions using TWRP and now I can't fix them anymore. Of course I created no recovery files before... I try to give you as much information as I can:
I have a european P9 Lite L31.
I think VNS-L31C432B130 but im not shure, because fastboot getvar returns just:
Code:
>fastboot oem gevar modelid
...
FAILED (remote: Command not allowed)
finished. total time: 0.008s
I also tried to flash the volumes from a Update.zip (I decompressed using HuaweiUpdateExtractor) via fastboot, but I get the following messages:
Code:
>fastboot flash product product.img
target reported max download size of 471859200 bytes
sending 'product' (112112 KB)...
OKAY [ 3.867s]
writing 'product'...
FAILED (remote: Command not allowed)
finished. total time: 3.889s
However flashing other images (like system or recovery) works.
I also tried to restore my phone by creating a ./dload directory on my sd-card containing the update.app (and other files from the zip) using the original recovery function. However this stops at 5% before my phone reboots.
Trying to repair the partitions by using TWRP > Wipe > Advanced Wipe > [Product/Vendor] > Repair or Change File System had also no success.
Clicking the repair-button gives the following output:
Code:
Updating parition details...
Failed to mount '/ventor' (Invalid argument)
Failed to mount '/product' (Invalid argument)
...done
Full SELinux support is present.
MTP Enabled
Repairing Product using e2fsck...
/sbin/e2fsck -fp process ended with ERROR: 16
Unable to repair Product
Trying to reformat a partition or installing a new OS also fails with the "Failed to mount /[vendor/product]" message.
I am using this Update.zip:
Huawei P9 Lite B382/B383 Nougat Update
(not allowed to post a link)
I really home you guys can help me...
Don't use B382/383 files if you have B130..
Same Problem
I have exactly the same Problem; exept my P9lite doesn't have the ability to "UPTAT.APP" anymore - caused of the stupid ish erecovery.
Did you find a solution?
I would be glad to hear a reply tnx
tmato12 said:
I have exactly the same Problem; exept my P9lite doesn't have the ability to "UPTAT.APP" anymore - caused of the stupid ish erecovery.
Did you find a solution?
I would be glad to hear a reply tnx
Click to expand...
Click to collapse
More info about your phone and FW version pls. Have you TWRP on board? What says bootloader about Phone/FRP ?
bozka1 said:
More info about your phone and FW version pls. Have you TWRP on board? What says bootloader about Phone/FRP ?
Click to expand...
Click to collapse
I have the Huawei p9 lite VNS-L31 with TWRP installed and accesable
it is in following state:
PHONE unlocked
FRP Unlock
but i cant fastboot anymore and this error appears:
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/product' (Invalid argument)
use the dload method via an external sdcard
Hi. I'm french. Have you resolved the problem ?
I'm atleast 51% sure that a flash of Service Repair ROM would fix that... But... Does such a ROM for MM exist?
Maybe the latest one (B381) will work...
Ofcourse flashing product and other partitions won't work. They get installed/updated through the UPDATE.APP (I think that also EliteROM is also doing that). They contain what model is the phone, how should everything be working and etc.
I am getting always the same error:
E1001: Failed to update system image.
Updater process ended with ERROR: 1
I wiped and formatted every partition, installed the most recent firmware.
I would appreciate any suggestion or advise. Thanks.
Then begin from new. First the right miui version with mi flashtool( don't look your bootloader) and then step by step