Database Develop

Wipe & Flashing has no effect

Hi,
I have a problem with my Moto G 2014 XT1068 which is described in topic: forums.androidcentral.com/moto-g-2013/391289-something-seriously-wrong-my-moto-g.html#post3668518
I can't do these steps, because dialog window shows up all the time, and i cant go further.
I have disabled usb debugging option and can't disable ART runtime.
First of all "Factory" in bootloader doesn't work. Wipe and factory reset via stock recovery has no effect; old android remains, the same using TWRP:
"E:Unable to open 'cache/recovery/.version' but ends successfully
and PHilz.
I've tried to flash many roms using many recoveries( TWRP - few versions up to 2.8.5 because 2.8.6 has display flickering bug, few Philz, and few others that also flicker) and fastboot and msfastboot(both on linux).
When i flash via fastboot or mfastboot using xml.zip roms everything looks ok, there are no errors, but flashing has no effect - I have still old ROM with old issue.
When i flash via different recoveries always some errors appears. For example flashing latest CM 12.1 nightly
via TWRP i get:
"E:Error executing updater binary in zip '/sideload/package.zip'
or via stock recovery (ADB sideload) get:
"(...)
Verifying update package...
E:Failed to verify whole-file signature
E:signature verification failed
Installation aborted."
Partition erase in fastboot despite "OKAY" message in CLI has no effect. As i understand this should remove all files from partitions.
This problem showed up when i discharged battery to 0% and turned on the phone.
Have you any ideas what should i try more?
Thanks in advance.

Hi,
I've tried other things to back my phone to life, like turn on usb debugging or even delete files, all via adb shell in recovery, but it is impossible. In TWRP or PhilzTouch I remount partitions with rw privileges, it look like I'm able modifying files via vi and cat to check results but when remount one more time old files still exist, so it is like there is some buffer? (maybe some security lock?), when try rm -rf files it shows up that i can't delete because it read only... (but mount says rw). After remount partitions with rw privileges wipe /data in twrp ended successfully but has no effect.
Do you know why everything looks ok, but it is not? Of course android boots up but is useless and after few minutes phone turns off.

i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.

Sounds like you both have a failed eMMC. If that is the case, and I'm certain it is, there is nothing that can be done to "save" or "restore" your devices.
Sent from my XT1031

hi, maybe any1 has already found a solution?

dihcar said:
i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.
Click to expand...
Click to collapse
I have exactly the same issue with my XT1063. Reading a lot for a solution, traying all without success.
Hopping someone can help us!

Razr i cannot be flashed, doesn't load proper Recovery

Hi guys,
a couple days ago my Razr i stopped working. After a forced reboot it stucked at the intel logo an doesn't boot further (like http://forum.xda-developers.com/razr-i/help/wont-boot-stuck-intel-screen-t3162719). I tried several things I've read in this forum (and other sites) but with no success.
My original system was Android 4.4.2 build für RetailEU and I would love to have either this back or the CM11 from Hazou (http://forum.xda-developers.com/razr-i/development/rom-unofficial-cyanogenmod-11-t2966855). Unfortunately I don't get this far.
I unlocked (successfully) my phone tried to replace the Recovery with TWRP (as described in Hazou's thread) but after a reboot I get the following error:
Code:
E:fail to write to /tmp/kernel
E:fail to create kernel file /tmp/kernel
failed to enter recovery mode, error code -1
The only Recovery I was able to install was CWM 6.0.1.9 but unfortunately this version doesn't allow me to install the CM11 as I get the error:
Code:
set_metadata_recursive: some changes failed
A change in the updater script as suggested here http://android.stackexchange.com/qu...et-set-metadata-recursive-some-changes-failed doesn't work either.
Any suggestions how I can get my phone back to live?

Bootloop problem on my ze550kl after official marshmallow update

Hello everyone. My problem is bootloop. I searched this forum before I post my own problem. Im trying to solve bootloop problem for 2 days. So I learned couple things. I had no idea what was fastboot and adp before.
Let me tell you what caused bootloop. I was using 6.0.1 firmware and my phone started working slowly. So I thought maybe new update fix that. I updated my phone and it was still slow. Then I looked that up on the internet. Some people said wipe your cache that might fix slow working zenfone. I put my phone on recovery mode and wiped cache and it caused bootloop. I started to search for my new problem. Found one with cmd command flashall. It turned my phone firmware to 1.17.40.1234 from 21.40.1220.2179. And then I downloaded raw ze550kl rom for my current firmware which is 1.17.40.1234. Extracted recovery.img boot.img and system.img
and used following commands :
fastboot devices
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system.img
fastboot commands worked with no problem and then I switched to recovery mode again and used this command:
adb sideload ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip.If I tried to use raw rom as i mentioned before ,cmd says *cannot read. So I used this firmware from asus website.
last command causes this error on pc
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip
loading: 'ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip'adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
Total xfer: 0.00x
and on my phone this error shows up
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted.
Bootloop problem still exists so I tried to use different method which was flashtools. I got "Run flash image script failured" error. I tried to fix it but no luck.
Lastly I tried to apply update from sdcard but my phone cant read on sdcard for some reason and that sdcard is being used my little brother(it works).
What can I do to revive my phone ? Please help me.

Ankeroth said:
Hello everyone. My problem is bootloop. I searched this forum before I post my own problem. Im trying to solve bootloop problem for 2 days. So I learned couple things. I had no idea what was fastboot and adp before.
Let me tell you what caused bootloop. I was using 6.0.1 firmware and my phone started working slowly. So I thought maybe new update fix that. I updated my phone and it was still slow. Then I looked that up on the internet. Some people said wipe your cache that might fix slow working zenfone. I put my phone on recovery mode and wiped cache and it caused bootloop. I started to search for my new problem. Found one with cmd command flashall. It turned my phone firmware to 1.17.40.1234 from 21.40.1220.2179. And then I downloaded raw ze550kl rom for my current firmware which is 1.17.40.1234. Extracted recovery.img boot.img and system.img
and used following commands :
fastboot devices
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system.img
fastboot commands worked with no problem and then I switched to recovery mode again and used this command:
adb sideload ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip.If I tried to use raw rom as i mentioned before ,cmd says *cannot read. So I used this firmware from asus website.
last command causes this error on pc
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip
loading: 'ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip'adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
Total xfer: 0.00x
and on my phone this error shows up
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted.
Bootloop problem still exists so I tried to use different method which was flashtools. I got "Run flash image script failured" error. I tried to fix it but no luck.
Lastly I tried to apply update from sdcard but my phone cant read on sdcard for some reason and that sdcard is being used my little brother(it works).
What can I do to revive my phone ? Please help me.
Click to expand...
Click to collapse
First download latest official build and don't do any edit or repack of zip .. Copy that ROM in the SD card make sure SD card works or format SD card into fat32 file system and copy ROM in it .. Go to phone recovery .. Hit update from SD card choose the zip wait till it flash if u still fail comment here .. I will give u alternatives

P10 adb and HWOTA Flashing partition length get error (SOLVED)

I keep getting the same error while trying to flash anything to my p10 and I can't get round it. When I try flashing an update.zip from twrp I get error: 9. I can however flash a system.img for some reason. Ih vae tried force updating (vol+ vol- pwr) with an update.app in dload but that gets to 5% then fails. The device is originally VTR-L09. HWOTA gives the same partition length get error so I can't use that either. At this point I just want the stock firmware.
Any ideas anyone?

HWOTA is not for Oreo - on Oreo the partition scheme is different.
You can search for "HWOTA8", but I don't know if it supports P10.
Otherwise you can use my guide - it works with the same script commands as HWOTA, but modified for Oreo. You just need a sd card and you need to follow "Tutorial 2".

Jannomag said:
HWOTA is not for Oreo - on Oreo the partition scheme is different.
You can search for "HWOTA8", but I don't know if it supports P10.
Otherwise you can use my guide - it works with the same script commands as HWOTA, but modified for Oreo. You just need a sd card and you need to follow "Tutorial 2".
Click to expand...
Click to collapse
So i tried the method 2 and after installing oreoupdate.zip it rebooted into twrp. So i tried rebooting normally and it just went to huawei eRecovery. Should I do forced update? (vol+ vol- pwr)
Or maybe shoud i install the oreo twrp?
edit: I tried installing update.zip again with twrp 3.1.1-0 and it just booted back into twrp, what now?
edit2: I tried unpacking the update.app but got an error saying "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 38059 Got: 180" could it be a problem that it say ramdis instead if ramdisk?

Jyndon said:
So i tried the method 2 and after installing oreoupdate.zip it rebooted into twrp. So i tried rebooting normally and it just went to huawei eRecovery. Should I do forced update? (vol+ vol- pwr)
Or maybe shoud i install the oreo twrp?
edit: I tried installing update.zip again with twrp 3.1.1-0 and it just booted back into twrp, what now?
edit2: I tried unpacking the update.app but got an error saying "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 38059 Got: 180" could it be a problem that it say ramdis instead if ramdisk?
Click to expand...
Click to collapse
If you did everything exactly as I wrote it in my guide, it should boot into TWRP. TWRP shouldn't boot after you installed the oreoupdate.zip because the script should've overwrite it with a custom Huawei recovery.
Try it again and post the TWRP log please.

Jannomag said:
If you did everything exactly as I wrote it in my guide, it should boot into TWRP. TWRP shouldn't boot after you installed the oreoupdate.zip because the script should've overwrite it with a custom Huawei recovery.
Try it again and post the TWRP log please.
Click to expand...
Click to collapse
It is certainly having a problem because I think it might actually be crashing instead of rebooting twrp
I couldnt paste the log so i put it here: https://justpaste.it/1ijaz

The log tells me, that TWRP tries to install the three update zip files and you did not install oreoupgrade.zip - it's not in the log.
Can you please post a screenshot of /sdcard/oreoupdate?
The script should install the modified stock recovery, which is in /sdcard/oreoupdate/, then the script put three install commands in cache for this recovery. After thisthe script reboots into stock recovery.

Jannomag said:
The log tells me, that TWRP tries to install the three update zip files and you did not install oreoupgrade.zip - it's not in the log.
Can you please post a screenshot of /sdcard/oreoupdate?
The script should install the modified stock recovery, which is in /sdcard/oreoupdate/, then the script put three install commands in cache for this recovery. After thisthe script reboots into stock recovery.
Click to expand...
Click to collapse
I definitely isntalled oreoupdate.zip but I feel like twrp is crashing part way as it closes almost instantly then reboot and tries to install the rest. I did it again anyway:
https://imgur.com/gallery/VyoUK
https://justpaste.it/1ijtv
should I maybe try reinstalling twrp and all the files?

Okay. First you need to rename "update_full_VTR-L09_hw_eu.zip" to "update_full_hw.zip"
But this should produce the problem you have.
Somehow the script doesn't install the stock recovery.
Can you please install this TWRP version with following fastboot command:
Code:
fastboot flash recovery_ramdisk TWRP.IMG
Then try it again. If not, can you please test if adb is working with
Code:
adb devices
It should show you your device if it's working. Some P10 are having problem with TWRP and ADB.

Jannomag said:
Okay. First you need to rename "update_full_VTR-L09_hw_eu.zip" to "update_full_hw.zip"
But this should produce the problem you have.
Somehow the script doesn't install the stock recovery.
Can you please install this TWRP version with following fastboot command:
Code:
fastboot flash recovery_ramdisk TWRP.IMG
Then try it again. If not, can you please test if adb is working with
Code:
adb devices
It should show you your device if it's working. Some P10 are having problem with TWRP and ADB.
Click to expand...
Click to collapse
Nothing shows when I do adb devices...
edit: also VTR_RECOVERY_OREO_NoCheck.img was called VTR_RECOVERY_OREO-NoCheck.img with the dash for some reason. made no difference though

Jyndon said:
Nothing shows when I do adb devices...
Click to expand...
Click to collapse
Okay than there's a manual method:
In TWRP open the Terminal and enter following commands:
Code:
dd if=/external_sd/oreoupdate/VTR_RECOVERY_OREO-NoCheck.img of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk_a
dd if=/external_sd/oreoupdate/VTR_RECOVERY_OREO-NoCheck.img of=/dev/block/platform/ff3b0000.ufs/by-name/erecovery_ramdisk_a
This commands take a few seconds but the shouldn't give you any output.
If you get an output, post it here, please.
If not continue with following commands:
Code:
echo --update_package=/sdcard/oreoupdate/update.zip >> /cache/recovery/command
echo --update_package=/sdcard/oreoupdate/update_data_full_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/oreoupdate/update_full_hw.zip >> /cache/recovery/command
reboot recovery
Again, no output for each command. If there's any output, post it here.
eRecovery should start and install.

Jannomag said:
Okay than there's a manual method:
In TWRP open the Terminal and enter following commands:
Code:
dd if=/external_sd/oreoupdate/VTR_RECOVERY_OREO-NoCheck.img of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk_a
dd if=/external_sd/oreoupdate/VTR_RECOVERY_OREO-NoCheck.img of=/dev/block/platform/ff3b0000.ufs/by-name/erecovery_ramdisk_a
This commands take a few seconds but the shouldn't give you any output.
If you get an output, post it here, please.
If not continue with following commands:
Code:
echo --update_package=/sdcard/oreoupdate/update.zip >> /cache/recovery/command
echo --update_package=/sdcard/oreoupdate/update_data_full_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/oreoupdate/update_full_hw.zip >> /cache/recovery/command
reboot recovery
Again, no output for each command. If there's any output, post it here.
eRecovery should start and install.
Click to expand...
Click to collapse
I put those last commands in and nothing has happened its still in the terminal. what now?

No output in twrp terminal for each command? Reboot to recovery will start TWRP?

Jannomag said:
No output in twrp terminal for each command? Reboot to recovery will start TWRP?
Click to expand...
Click to collapse
I didnt get any outputs from the first two but the last three didn't show anything after. Did I need to exclude the echo?
and it reboots to twrp when rebooting to recovery
Edit: like the first two show and input thing an output with some stuff being copied after and it shows a time for execution but the last three that start with echo didnt do anything, just started a new line.

No OS Installed VTR-L29, EMUI 9.0 (Can't download stock)

I have the VTR-L29C605E2R1P8B119-log (9.0.1.119), EMUI 9 (android pie) of the P10 and I accidentally deleted my system, with only fastboot and twrp working. My EMUI erecovery is broken since there is no official global PIE update for the P10 (except the chinese) It will say "Failed to get package info"
I need help on how to fix this because I have tried downgrading and no avail.
Tried using funkyhuawei well, i'm getting "Failed to get package info" and i can assure you that the dns was working, and my oem isn't damaged.
Tried using DC-Pheonix but then it says phone not supported.
What a waste of 30$ but it's better than wasting 200$ for a new motherboard.
Tried using the Dload method. Software Install Failed (using the same rom)
Tried doing the HWOTA but it won't write to my recovery because it's set to "Recovery" not "recovery_ramdisk" I tried changing it's script to recovery_ramdisk, but when I tried to boot up to twrp and it gave me func 11 and 2 errors.
Tried flashing the images... Well, I couldn't flash system because of the "cannot load system.img" file.
Tried using oreo images, failed.
Tried using the Multi-Tool for huawei, well i thought it worked but it didn't because it flashed the system and everything else (the program doesn't know that the ramdisk is inside system) it gave me the error #1 at the end. Still didn't boot.
Tried flashing AOSP Roms and I bam it didn't work.
Do you guys have anymore solutions?

Did you try this?

Jannomag said:
Did you try this?
Click to expand...
Click to collapse
I did. But without adb working, I can't get it to work since it will look for devices/emulators which needed adb and it seems like my phone isn't responding to those.

If you flash the twrp image from the archive of the post I linked before, does it boot up and is adb then available?

Jannomag said:
If you flash the twrp image from the archive of the post I linked before, does it boot up and is adb then available?
Click to expand...
Click to collapse
Nope. It does not detect the adb.

Can you try this TWRP please, eventhough it's for Oreo.
If this isn't gonna work do something for me:
- Boot into your working TWRP and open the terminal (under Advanced).
- Type: "ls /dev/block/platform"
- You should get something like "FF3B0000.UFS" or other, please post in the next reply.
- Now type "ls /dev/block/platform/RESULT/by-name" - for RESULT enter the output of the first command.
- Please post the recovery and erecovery lines from the output in your reply.
With this output I should be able to write a small script, but I can't guarantee that this will work.
EDIT: I made a script based on my UFS device. Please do the commands above first.
If it shows "ff3b0000.ufs", then proceed with my script:
- create a new directory on your sdcard (it has to be sd, not internal!) called "downgrade" (without qoutes).
- Download my zip package and put it into /sdcard/downgrade
- Download your desired firmware - it has to be the same region C605! (Links for B374: update.zip, update_full_VTR-L29_hw_la.zip, update_data_full_public.zip)
- put all three zip files into /sdcard/downgrade and rename "update_full_VTR-L29_hw_la.zip" to "update_hw.zip".
- Boot into TWRP, tap in Install and navigate to the sdcard/downgrade directory.
- Install downgrade.zip. If there's any output, post it here.
The device will reboot itselfs and should start into Huawei's recovery, which should install the firmware.
Download my script here.

Jannomag said:
Can you try this TWRP please, eventhough it's for Oreo.
If this isn't gonna work do something for me:
- Boot into your working TWRP and open the terminal (under Advanced).
- Type: "ls /dev/block/platform"
- You should get something like "FF3B0000.UFS" or other, please post in the next reply.
- Now type "ls /dev/block/platform/RESULT/by-name" - for RESULT enter the output of the first command.
- Please post the recovery and erecovery lines from the output in your reply.
With this output I should be able to write a small script, but I can't guarantee that this will work.
EDIT: I made a script based on my UFS device. Please do the commands above first.
If it shows "ff3b0000.ufs", then proceed with my script:
- create a new directory on your sdcard (it has to be sd, not internal!) called "downgrade" (without qoutes).
- Download my zip package and put it into /sdcard/downgrade
- Download your desired firmware - it has to be the same region C605! (Links for B374: update.zip, update_full_VTR-L29_hw_la.zip, update_data_full_public.zip)
- put all three zip files into /sdcard/downgrade and rename "update_full_VTR-L29_hw_la.zip" to "update_hw.zip".
- Boot into TWRP, tap in Install and navigate to the sdcard/downgrade directory.
- Install downgrade.zip. If there's any output, post it here.
The device will reboot itselfs and should start into Huawei's recovery, which should install the firmware.
Download my script here.
Click to expand...
Click to collapse
Thanks for trying to help me, but I think this would work. I tried the ls /dev/block/platform command but it gave me the "sh ls /dev/block/platform: not found. " Is my device unrecoverable now? I tried to flash but gave me the error: 255 Maybe a backup twrp of kernel,cust,oeminfo,product,recovery,system,sys img, vendor, vendor img, version would work if i use the restore button in twrp but I don't have any backups because I forgot to. If you have any it might work I think?

[Solved]
Thanks for your help, I did a bit of changes though to your script.
Instead of of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk_a
I changed it to: of=/dev/block/sdd37
It installed the update well.

This explained that the other tools like HWOTA8 didn't work. sdd37 is only on eMMC device which are rare. I forgot that the eMMC devices have a different path tree under /dev than UFS devices.
I'm glad that this works now.
The script is based on HWOTA and I use this in my Update Guide, too.

have u tried to "reinstall" the FULL OTA (the version that u have installed) via HuRu updater?