Database Develop

[Q] Fastboot will not see my device, Recovery does. Unable to push files.

I had the SD card issue where it wasn't seeing all my files. Recovery mode would see files I could not locate within the os.
What I did:
Backed up my contents. Always have a nandroid backup!
Downloaded and md5sum checked Trickdroid 8.0.0
Booted into recovery, wiped phone. Formatted all partitions.
My next plan of action was to adb push trickdroid. This failed, its not seeing my sdcard partion. I have attempted to format /sdcard. It returns no errors. I got to mount /sdcard, It fails to find the directory.
When I boot into fastboot (Thinking at the very worst I could relock my device nad flash an RUU)
It does not see any devices. I have verified multiple times that I am using the correct driver. I have removed all drivers from the system, attempted to use htc sync, uninstalled that, used the Naked Drivers, uninstalled those (still no device in fastboot), installed the ADB Driver installer (found using the search button). Still, no devices in fastboot.
If someone could point me in the right direction I would greatly appreciate it. I have been using adb and flashing devices for a number of years and have not yet encountered a problem like this.
-Erik

voltage88 said:
I had the SD card issue where it wasn't seeing all my files. Recovery mode would see files I could not locate within the os.
What I did:
Backed up my contents. Always have a nandroid backup!
Downloaded and md5sum checked Trickdroid 8.0.0
Booted into recovery, wiped phone. Formatted all partitions.
My next plan of action was to adb push trickdroid. This failed, its not seeing my sdcard partion. I have attempted to format /sdcard. It returns no errors. I got to mount /sdcard, It fails to find the directory.
When I boot into fastboot (Thinking at the very worst I could relock my device nad flash an RUU)
It does not see any devices. I have verified multiple times that I am using the correct driver. I have removed all drivers from the system, attempted to use htc sync, uninstalled that, used the Naked Drivers, uninstalled those (still no device in fastboot), installed the ADB Driver installer (found using the search button). Still, no devices in fastboot.
If someone could point me in the right direction I would greatly appreciate it. I have been using adb and flashing devices for a number of years and have not yet encountered a problem like this.
-Erik
Click to expand...
Click to collapse
I fixed it!!! Anyone that has a similiar issue. This is what I did.
In a previous thread, I saw that 4.2 will redo the sd card structure. After some research, it was recommended to change the path to /data/media/0. I was then attempting to do the command as follows 'adb push Trickdroid_8.0.0.zip /data/media/0' (without tick marks)
The file was pushing as it should (no progress bar) however, it would fail at the very end saying it was unable to locate the directory.
After seeing adb fail in that manner, I knew my sdcard was not mapped to the above path. What I did was boot into recovery, go to mounts and storage, mount my sdcard. Go back to the first menu now.....From here, select advance, and view log. It will tell you where your sdcard is being mapped to. Simply push your zip file to this directory and success! I have a working phone again.
Fastboot still doesn't recognize my device however. I'd be more then happy to be educated as to what I may have done wrong.

SOLVED Need help w/4.01 OTA ("Move installation package into SD card root directory")

SOLVED Need help w/4.01 OTA ("Move installation package into SD card root directory")
Just got my 3T. It's currently running 3.5.4. (Check for updates shows "OnePlus A3000_28_161213")
So new, I haven't even rooted it yet.
I've downloaded the 4.01 OTA from Google Drive (OnePlus3TOxygen_28_OTA_035-037_patch_1701041831_c9652aee6cc.zip) onto myPC, and moved the file to my phone.
But every time I try to select Local Upgrade, I get the message:
Move installation package into SD card root directory​I've tried:
adb push to /sdcard
adb push to /storage/emulated/0
copying the file using Windows Explorer
Same result every time.
What do I have to do so it recognizes the file?
____________________________________________________________
Update: I ended up downloading the Full Zip (OnePlus3TOxygen_28_OTA_037_all_1701041831_a2ba632ce9.zip) instead of the OTA file.
Copied that to the SDcard, and Local Upgrade worked.

i had this 2 and there's 2 things you can try:
make sure you move all or any files you want to see or use in the root directory not in any folder, if that doesn't work reboot & check
lastly & oddly enough i used opera VPN so i could see the ota update BUT didn't do it but then i could see my local updates even after I turned off the von pretending to be in Canada
i hope that helps it worked for me
I still don't have the update in the USA but instead of doing the update manually im going to change location to Canada and do it over VPN using Opera im sooooo anxious waited from last Friday but I'm dying now hahahaha

cheshyre said:
Just got my 3T. It's currently running 3.5.4. (Check for updates shows "OnePlus A3000_28_161213")
So new, I haven't even rooted it yet.
I've downloaded the 4.01 OTA from Google Drive (OnePlus3TOxygen_28_OTA_035-037_patch_1701041831_c9652aee6cc.zip) onto myPC, and moved the file to my phone.
But every time I try to select Local Upgrade, I get the message:
Move installation package into SD card root directory​I've tried:
adb push to /sdcard
adb push to /storage/emulated/0
copying the file using Windows Explorer
Same result every time.
What do I have to do so it recognizes the file?
Click to expand...
Click to collapse
Reboot to recovery mode and try a local install, you'll have to browse to it. This worked for me.

Or try adb sideload

Solved it!
I ended up downloading the Full Zip (OnePlus3TOxygen_28_OTA_037_all_1701041831_a2ba632ce9.zip) instead of the OTA file.
Copied that to the SDcard, and Local Upgrade worked.

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?

Installing Custom Recovery, without download mode or USB Debugging.

Hi,
I would like to begin by stating I am new to posting on XDA, but I have used XDA for finding help in the past. The help is always accurate and exceptional. I am hoping that someone will be able to help me with a new problem that I can't get my head around. I will try my best to give all information I can.
OK Here Goes..........
My Father has a samsung A8, model A530F (Jackpotltexx/Jackpotlte8.0.0/R16nw/A530Fxxu3brl8 (this info obtained from stock recovery mode))
Now the problem is he has somehow activated, what I believe is called an MDM Lock.
I Believe because of this the phone will not go into download mode via button presses or any other means. Also USB debugging was not turned on nor OEM Unlocking.
What I wish to Achieve is to somehow install A custom recovery preferably TWRP to his device so that I can install a custom ROM or Even the default Firmware Via SDcard or Via ADB Sideload. I have already tried installing TWRP via SDCARD and ADB but I keep getting verification errors.
The Only thing I believe I have to use is the stock recovery, which won't let me factory reset, go into download mode or fastboot because of this stupid mdm lock. The only thing that seems to work is Update via ADB Sideload or SDcard but they require to be officially signed and verified.
Is there a way to install twrp or verify it?
Can I simply find verified Updates to downgrade / upgrade so that I can get usb debugging or download back?
Is there a way to format the phone using a verified zip?
Can The SDCard be used as a Boot device and install TWRP to it?
Any help or suggestions will be greatly appreciated.
Thanks In Advance.

Extra Info
Just updating my original post with some extra info,
When starting up phone in recovery the following is displayed at the bottom of the terminal.
#Reboot Recovery Cause is [BL:Recovery Mode Set by Key]# Support Single-SKU
File-Based OTA supported API: 3
#Manual Mode V1.0.0# remove failed dir '/system/carrier/ATT/Priv-app/AttIqi_ATT '(No such file or directorty)
Successfully verified dmverity hash tree.
Also when selecting Update via ADB It seems to activate the USB connection. Is there a way I can use this?
When I type adb devices it comes up with
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
52004f7ac028259d sideload
I was also wondering if anyone knows of anything that the stock recovery mode can update / flash. I have gotten a lot of "official firmware updates" from trusted sites and none of them want to update via adb or SDK card due to verification / signing issues.
Once again Thanks to everyone.

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?