Database Develop

Accidentally formatted sdcard prior to flashing

Hey guys, I need some help here
I accidentally formatted the sdcard when preparing a clean flash. I also formatted system ect. so now all I can do is boot into recovery but no files to flash.
Is there some way I can transfer files to the sdcard og another way to get the device working again?
Thanks in advance.

You are softbricked. Restore factory image using wugfresh
http://www.wugfresh.com/nrt/

Download the factory images, boot into bootloader (not recovery) by holding power+down, then flash the factory images.

I'm in exactly the same boat here, but every time I try to use fastboot commands, I get a write failed. I'm fairly certain the drivers are installed properly, as fastboot devices shows me the device. What else could be done?

codemonkey85 said:
I'm in exactly the same boat here, but every time I try to use fastboot commands, I get a write failed. I'm fairly certain the drivers are installed properly, as fastboot devices shows me the device. What else could be done?
Click to expand...
Click to collapse
Give the exact steps and exact messages, cut and paste is best, otherwise there is not enough info to go on.

I installed the drivers using Nexus Root Toolkit 1.5.5. (I used option #2, which is to install the signed drivers.)
I copied the extracted contents of the Nexus 7 4.2 factory image into my adb folder. I ran a command prompt in that folder.
I type: fastboot devices
I get: 015d25687443fe0f fastboot
I type: fastboot flash bootloader bootloader-grouper-4.13.img
I get: FAILED (command write failed (Unknown error))
I type: fastboot -w update image-nakasi-jop40c.zip
I get: FAILED (command write failed (Unknown error))

Well, I don't know how or why, but I just tried the same thing again using the Nexus Toolkit and it worked this time. I'm booting into a stock ROM right now.

Im unable to turn on USB debugging, cause i have no ROM. What to do?

codemonkey85 said:
I installed the drivers using Nexus Root Toolkit 1.5.5. (I used option #2, which is to install the signed drivers.)
I copied the extracted contents of the Nexus 7 4.2 factory image into my adb folder. I ran a command prompt in that folder.
I type: fastboot devices
I get: 015d25687443fe0f fastboot
I type: fastboot flash bootloader bootloader-grouper-4.13.img
I get: FAILED (command write failed (Unknown error))
I type: fastboot -w update image-nakasi-jop40c.zip
I get: FAILED (command write failed (Unknown error))
Click to expand...
Click to collapse
exactly the same error im getting.. how did you solve it?

Tried again on another USB port and now it worked.
Thanks for the help guys.

codemonkey85 said:
Well, I don't know how or why, but I just tried the same thing again using the Nexus Toolkit and it worked this time. I'm booting into a stock ROM right now.
Click to expand...
Click to collapse
Out of interest why didn't you just run the small script that comes with the factory image to wipe and reflash everything.
It's what I did to make sure I had a nice clean install.
Or were you trying to keep some data from /data for example.

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!

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?

Android Q update problems

Hello,
I'm struggling with my s10, SM-G973F, i was rooted and twrp etc, then i decided that i want the q beta, went to ASII signup for the members ap to get the beta and tried 3 way's to run the update by SD card - could not mount the sd card and adb way and this failed, and offcourse i tryed trough the phone Software update but this had failed as well, can anyone give me a hint hot get this done.
When i'm on ASII if i try by card i get:
Reboot recover Cause is [BL: Recovery Mode is set by key)#
Support SINGLE-SKU
#Manual Mode v1.0.0#
E: Failed to mount /sdcard: no such file or directory
-- Couldn't mount sdcard.
Installation Aborted
When i do it trough adb is say it successful but i get every time on botloop , and i have downloaded the update from different sources.
Updated firmware to BTU: ASJD trough smart switch and then followed the the steps and downloaded the update ZSK3 (it showed directly beta 3) trough the software update from settings, after all done i end up in bootloop again.
Can anyone help with this, i spent my Saturday on this silly thing.
Many Thanks

Did you relocked the bootloader?

Moto G7 plus TWRP installation issues/confusion

Hello. Newbie here trying to install TWRP onto my G7+ (xt1965-T, moto not Revlry). I've been following the twrp.me instructions, among others. I've got the bootloader unlocked, adb & fastboot devices both return what they should, I've copied the twrp-3.5.0_9-0-lake IMG & ZIP files to my platform-tools folder and am running powershell from there. I copied the zip file to the internal memory of the phone as well as the ASC file with basic copy/paste commands in windows.
I temporarily boot the TWRP image and try to install the zip file, only to have it fail signature verification. I tried it without sig verification but still failed on some error. I've searched, but I haven't been able to find anything to get me past this.
Confusion comes with conflicting instructions. I see here that there is a method that differs from the instructions linked above, AFIAK.
There is a note on the bottom of the 1st instructions stating " If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest firmware for your device and reflash the boot image." I did ignorantly initially type the command fastboot flash recovery TWRPxxx.img. Would this have anything to do with my issues?
Are there multiple ways to achieve installation of TWRP & something like LineageOS and I'm just getting confused between instructions for each?
Thanks

I just tried to install the zip file without signature verification, and it failed to unpack the image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/twrp-installer-3.5.0_9-0-lake.zip'
I've downloaded this a couple of times with the same result.

timsch75 said:
I just tried to install the zip file without signature verification, and it failed to unpack the image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/twrp-installer-3.5.0_9-0-lake.zip'
I've downloaded this a couple of times with the same result.
Click to expand...
Click to collapse
Did you go in to TWRP Advanced and try to sideload TWRP ?

timsch75 said:
Hello. Newbie here trying to install TWRP onto my G7+ (xt1965-T, moto not Revlry). I've been following the twrp.me instructions, among others. I've got the bootloader unlocked, adb & fastboot devices both return what they should, I've copied the twrp-3.5.0_9-0-lake IMG & ZIP files to my platform-tools folder and am running powershell from there. I copied the zip file to the internal memory of the phone as well as the ASC file with basic copy/paste commands in windows.
I temporarily boot the TWRP image and try to install the zip file, only to have it fail signature verification. I tried it without sig verification but still failed on some error. I've searched, but I haven't been able to find anything to get me past this.
Confusion comes with conflicting instructions. I see here that there is a method that differs from the instructions linked above, AFIAK.
There is a note on the bottom of the 1st instructions stating " If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest firmware for your device and reflash the boot image." I did ignorantly initially type the command fastboot flash recovery TWRPxxx.img. Would this have anything to do with my issues?
Are there multiple ways to achieve installation of TWRP & something like LineageOS and I'm just getting confused between instructions for each?
Thanks
Click to expand...
Click to collapse
I fought this same model G7+ (XT1965-T) for several days, trying to install LineageOS for microG. Here are the instructions I used here ....I used the same recovery image (twrp-3.5.0_9-0-lake .img) as you. Download the copy-partitions-20200903_1329.zip from here. To sideload copy-partitions zip in TWRP go to Advanced tab, ADB sideload tab, then I sideloaded lineage-17.1-20210202-microG-lake.zip here.

chuck8812 said:
I fought this same model G7+ (XT1965-T) for several days, trying to install LineageOS for microG. Here are the instructions I used here ....I used the same recovery image (twrp-3.5.0_9-0-lake .img) as you. Download the copy-partitions-20200903_1329.zip from here. To sideload copy-partitions zip in TWRP go to Advanced tab, ADB sideload tab, then I sideloaded lineage-17.1-20210202-microG-lake.zip here.
Click to expand...
Click to collapse

I've regressed. I had previously been ably to temporarily boot into TWRP with the fastboot boot x.img command, at least in windows, but for some reason now it hangs up and will not show the TWRP screen. I had this same issue in Linux, but it worked in Windows, but now it fails the same in both. I run the command above and it shows the typical splash screen that it would if booting the stock android system, but goes no further. Previously, it would flash this , but then go to the TWRP screen. I can't get any feedback from adding the verbose flag to the fastboot command. Any way to track down this problem?
effin 'ell I hate regressions, 'specially the ones that come out of nowhere.
p.s. I don't know what happened with the previous blank post. I was trying to reply in Windows, but it wouldn't let me enter text. I rebooted into Linux for this post, and I see that something got posted previously. I'd delete it if I could.... gremlins