Installing Custom Recovery, without download mode or USB Debugging. - Samsung Galaxy A8+ (2018) Questions & Answers

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.

Related

[HELP] Android not booting [URGENT]

It's a bit urgent to get solved, I'm at college, and that's the only way to talk with my parents, being 1 or 2 days without answering them would be a problem, since they will start to get worried.
Phone: Motorola Moto G 2014, XT1063
Using Team Win Recovery Project v2.8.0.1
Basically I was trying to update to the Android 5.0, since I had my phone rooted, I decided to go with an customized ROM.
DIdn't understand why, but it f**ed up.
Basically I cleaned everything, and in an act of desperation I also lost my sdcard, I've been trying to install the ROM through sideload, but it's not working, I get the error *failed to write data protocol fault no status*, and the phone keeps rebooting, and stuck in the "WARNING BOOTLOADER UNLOCKED"
I appreciate any kind of help, as I said, it's really important to solve this ASAP.
Thanks in advance!
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
gouzzz said:
Basically I was trying to update to the Android 5.0, since I had my phone rooted, I decided to go with an customized ROM.
Click to expand...
Click to collapse
1) download TWRP 2.8.4.0 and install it through fastboot.
2) Since you have no sdcard we will use the mtp capability of twrp
-- Boot into your newly installed recovery. Check the version
-- Go to Mount and disable mtp and unmount everything. Now enable mtp. You should see that Data is mounting automatically and should appear on your Computer.
-- Transfer your ROM (I recommend The Titan Prime Rom for XT1063/64. It's based on stock and much more polished than CM12)
-- Download and transfer pa-gapps (MICRO MODULAR PACKAGE).
-- Download and transfer latest SuperSU (min version 2.45 is required by our device).
-- Wipe Dalvik, Cache, System and Data
-- Now Flash ROM, GApps and SuperSU. reboot and wait. it will take a couple of minutes.
Doppel u r right. follow doppel steps.
doppelhelix said:
1) download TWRP 2.8.4.0 and install it through fastboot.
2) Since you have no sdcard we will use the mtp capability of twrp
-- Boot into your newly installed recovery. Check the version
-- Go to Mount and disable mtp and unmount everything. Now enable mtp. You should see that Data is mounting automatically and should appear on your Computer.
-- Transfer your ROM (I recommend The Titan Prime Rom for XT1063/64. It's based on stock and much more polished than CM12)
-- Download and transfer pa-gapps (MICRO MODULAR PACKAGE).
-- Download and transfer latest SuperSU (min version 2.45 is required by our device).
-- Wipe Dalvik, Cache, System and Data
-- Now Flash ROM, GApps and SuperSU. reboot and wait. it will take a couple of minutes.
Click to expand...
Click to collapse
The device appear as offline in the fastboot, sometimes even doesn't appear, where can I get the drivers?
I searched for naked versions, and "universal" ones, but none seems to work.
gouzzz said:
The device appear as offline in the fastboot, sometimes even doesn't appear, where can I get the drivers?
I searched for naked versions, and "universal" ones, but none seems to work.
Click to expand...
Click to collapse
You can get Motorola drivers here. You probably also need a recent version of adb and fastboot. You can ge it here Minimal ADB and Fastboot. Install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installation or the desktop shortcut you choose to create and select "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ZX1D225X69 fastboot
now put your recovery.img into the directory where your command window is open and start flashing
Code:
fastboot flash recovery NAME_OF_RECOVERY.img
---------- Post added at 15:34 ---------- Previous post was at 15:31 ----------
gouzzz said:
EDIT: Now it doesn't charge, or something. I connected it to charge, but it keeps appearing 0% for more than 30 minutes, I can't even access the menu from "Volume Down + Power On"
Click to expand...
Click to collapse
You need a wall charger. USB from pc does not supply enough power. And you need at least 25% (ish) otherwise fastboot will refuse do do anything.
doppelhelix said:
You can get Motorola drivers here. You probably also need a recent version of adb and fastboot. You can ge it here Minimal ADB and Fastboot. Install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installation or the desktop shortcut you choose to create and select "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ZX1D225X69 fastboot
now put your recovery.img into the directory where your command window is open and start flashing
Code:
fastboot flash recovery NAME_OF_RECOVERY.img
---------- Post added at 15:34 ---------- Previous post was at 15:31 ----------
You need a wall charger. USB from pc does not supply enough power. And you need at least 25% (ish) otherwise fastboot will refuse do do anything.
Click to expand...
Click to collapse
On the MOUNT and UNMOUNT processing I don't see anything on my PC, I don't even know how to unmount it. It only appears Enable MTP and disable.
How am I supposed to load the ROMS?
Tried with sideload but got an errror : "Error executing updater binary in zip .."
Seems like the drivers aren't working properly, I have Windows 8.1, on the site it doesn't talk about it, this might be the problem? Cause I instaled motorola device manager, I scan for drivers but it doens't find anything, and the phone apperas with the yellow triangle on the Device Manager.
----------------------------------------------------------------------------
----------------------------------------------------------------------------
EDIT: I managed to boot the Titan 5.0.2, but now it's stuck in the 4 balls moving around, i waited for about 1hour.

[RECOVERY] Stock Recovery Image - v1.1.1.1929530

Here is a copy of the stock recovery.img from version 1.1.1.1929530 if anyone needs it:
Must enable ADB Debugging in developer menu! (About > tap build number to unlock developer options > developer options > Enable ADB Debugging) Make sure to grant access to your computer select ALWAYS.
Must have Unlocked bootloader: (which I assume you have if you are trying to go back to stock from TWRP)
Currently there is an unofficial build of TWRP that you can find here: http://forum.xda-developers.com/watch-urbane/general/twrp-2-8-6-0-test-build-t3122005 (thanks @Tasssadar)
Instructions:
ADB DEBUGGING ENABLED!
- adb reboot bootloader
- fastboot flash recovery <location of stock img file>
- reboot to recovery to make sure everything worked.
- adb reboot
I am not responsible for anything that happens to your device, please do not come to me if you brick your Android Wear, I am just providing the stock recovery for anyone who needs it.
I have tested this myself after flashing TWRP recovery. Works fine for me so you should have no issues.
Download Link:
http://1drv.ms/1FOVnNR
sharky481232 said:
Here is a copy of the stock recovery.img from version 1.1.1.1929530 if anyone needs it:
Must enable ADB Debugging in developer menu! (About > tap build number to unlock developer options > developer options > Enable ADB Debugging) Make sure to grant access to your computer select ALWAYS.
Must have Unlocked bootloader: (which I assume you have if you are trying to go back to stock from TWRP)
Currently there is an unofficial build of TWRP that you can find here: http://forum.xda-developers.com/watch-urbane/general/twrp-2-8-6-0-test-build-t3122005 (thanks @Tasssadar)
Instructions:
ADB DEBUGGING ENABLED!
- adb reboot bootloader
- fastboot flash recovery <location of stock img file>
- reboot to recovery to make sure everything worked.
- adb reboot
I am not responsible for anything that happens to your device, please do not come to me if you brick your Android Wear, I am just providing the stock recovery for anyone who needs it.
I have tested this myself after flashing TWRP recovery. Works fine for me so you should have no issues.
Download Link:
http://1drv.ms/1FOVnNR
Click to expand...
Click to collapse
Are backups and restores working? Or is there not enough memory? Anyone??
suzook said:
Are backups and restores working? Or is there not enough memory? Anyone??
Click to expand...
Click to collapse
I usually do a backup then once its done I use "adb pull" to my PC and delete the copy on the device. just safer that way. Anytime i need to restore I just "adb push" back to the same directory I pulled from.
sharky481232 said:
I usually do a backup then once its done I use "adb pull" to my PC and delete the copy on the device. just safer that way. Anytime i need to restore I just "adb push" back to the same directory I pulled from.
Click to expand...
Click to collapse
Thanks, gonna try and leave it on. I switch between my note4 and nexus 6...thinking I could just restore my backup when I switch. I wish wear was able to sync to multiple phones.
suzook said:
Thanks, gonna try and leave it on. I switch between my note4 and nexus 6...thinking I could just restore my backup when I switch. I wish wear was able to sync to multiple phones.
Click to expand...
Click to collapse
Havent tried this myself but seems like a faster process then restoring backups:
http://forum.xda-developers.com/and.../app-reset-wear-client-switch-phones-t3058962
sharky481232 said:
Havent tried this myself but seems like a faster process then restoring backups:
http://forum.xda-developers.com/and.../app-reset-wear-client-switch-phones-t3058962
Click to expand...
Click to collapse
Thanks, I'll give that a look. BTW, I'm trying to flash recovery, my adb sees my watch, but when I try fastboot OEM unlock, I get stuck at "waiting for device"..... Any ideas???
suzook said:
Thanks, I'll give that a look. BTW, I'm trying to flash recovery, my adb sees my watch, but when I try fastboot OEM unlock, I get stuck at "waiting for device"..... Any ideas???
Click to expand...
Click to collapse
If you are using Linux, make sure you are in SU mode, also sometimes - I have to wait til the watch is in bootloader mode then remove the watch from dock and put it back on then the computer will find it.
Any chance you could provide a system.img too? I semi-bricked my watch and I need a system.img dump to get it up and running again - I can't use adb to push and flash a .zip, so a .img is my only option right now.
BJSerpas said:
Any chance you could provide a system.img too? I semi-bricked my watch and I need a system.img dump to get it up and running again - I can't use adb to push and flash a .zip, so a .img is my only option right now.
Click to expand...
Click to collapse
Go here http://forum.xda-developers.com/watch-urbane/general/twrp-2-8-6-0-test-build-t3122005. There is a TWRP Urbane 5.1.1. image backup, including boot and system. Follow the instructions there and you'll be fined. I have just done so and recovered my urbane from a failed ROM.
Hello,
I have installed TWRP in order to root my Urbane (to increase the vibration intensity).
I need to reinstall the stock recovery to allow ROM to auto-install OTAs when available? or TWRP can be used by the system to install OTAs?
Thanks!

Stuck on Boot After installing SuperSU Binary [URGENT][Solved]

[Update]: Now it says no OS installed in TWRP. I think I have wiped the os by mistake. Just need to know how to install cm13 image using fastboot or ADB. Please help!
I wasn't aware if SuperSU works with CM13 and I installed the app, on request to update the binaries, I selected TWRP/CWM method because the normal mode didn't work. After the reboot the phone won't load into os, its stuck on the CM boot screen. I don't have a CM image on my sd therefore unable to flash again either. Is there a way to push files (cm img) to my phone? I have adb/adb over network enabled as well from developer options. I just need a way to put files into my sd card and flash using TWRP. Please help! this is urgent! :crying:
[SOLVED][HOW TO]
This is in a situation where you've messed up your system and don't have the image file stored in your sd card for quick flashing. Make sure you're using the latest USB drivers and ADB binaries 1.0.32+
- Get into TWRP
- Swipe to ADB Sideload and enable it
- On your desktop, open command and type "Adb sideload filename.zip" [Filename here is the filename of your flashable zip/rom]
- Once you the installation finishes, reboot twrp normally into system
dibyajyoti said:
I just need a way to put files into my sd card and flash using TWRP. Please help! this is urgent! :crying:
Click to expand...
Click to collapse
Have you tried enabling MTP in TWRP and using a computer to transfer the image over?
Contact me if you have any questions.
R55770 said:
Have you tried enabling MTP in TWRP and using a computer to transfer the image over?
Contact me if you have any questions.
Click to expand...
Click to collapse
MTP shows as enabled - But the device doesn't show up in my pc. I'm connected through USB in TWRP recovery. I have android debugging also enabled, when trying adb push command, it shows adb devices attached as empty.
[Update]: I am trying to push the file using ADB Sideload in TWRP, the error I get is my adb needs to be updated to 1.0.32. How do i get updated adb 1.0.32?
[Update 2]: So I managed to update by ADB on desktop, and push the zip file using adb sideload in twrp. The zip is being installed as I write this. Lets hope this works!
[Update 3]: Got the rom to install via ADB sideload, though all my apps and settings are gone Anyway, I got the phone back for immediate use. Phew!
dibyajyoti said:
MTP shows as enabled - But the device doesn't show up in my pc. I'm connected through USB in TWRP recovery. I have android debugging also enabled, when trying adb push command, it shows adb devices attached as empty.
[Update]: I am trying to push the file using ADB Sideload in TWRP, the error I get is my adb needs to be updated to 1.0.32. How do i get updated adb 1.0.32?
[Update 2]: So I managed to update by ADB on desktop, and push the zip file using adb sideload in twrp. The zip is being installed as I write this. Lets hope this works!
[Update 3]: Got the rom to install via ADB sideload, though all my apps and settings are gone Anyway, I got the phone back for immediate use. Phew!
Click to expand...
Click to collapse
Great. Thanks for letting us know.

sideload error no device

sorry if this is the wrong place...this is my problem
I got an old tablet off someone that i want to bring back to life, its an ares 8, model #NXA8QC116. unfortunately the sd card slot is broken so using it is out of the question..I have TWRP 3.0.2 on it and im trying to flash SU to it via "adb sideload."
when in system using "adb devices" it shows the device as well as in recovery mode, but when i try to use the sideload feature in TWRP i get a "ADB sideload failed no devices/emulators found error..if i try "adb devices here it does not show a device..im not sure if this is the problem. Also i cant FLASH SU BECAUSE IT IS NOT SHOWING UP IN twrp nor are any other zips which ive read is because of the encryption is still enabled? i have the disable encryption .zip but cant flash that eaither due to my same problem of .zips not showing up.
All the device drivers and adb+fastboot are setup properly as far as i can tell but i get the error no matter what i do.
my questions are..
1. is there and OTHER method i can use to flash SU.zip or the decryption.zip file without the use of an SD card?
2. does anyone have any ideas on how i can go about fixing the no devices/emulators found error while in sideload mode?
thank you very much for your anticipated reply!
1. is there any OTHER way to flash SU using

Pixel 5 Recovery questions

I recently bought an unlocked Pixel 5 from Amazon, only to discover it is (apparently) a VZW that was carrier unlocked, and so the OEM Unlock is not available. I am slowly making my peace with that fact, but am curious how much leeway I have to get at lease *some* more control.
When I boot into stock recovery, I have the option to mount /system. I am hoping this means I can pull, edit, and then push the build.prop and possibly other files as well. Perhaps also push the superuser binary. However, I am unable to detect my phone when I mount /system.
My system specs:
Windows 10 Pro
Version 21H2
OS Build 19044.2728
I have installed the latest drivers from Google.
I am able to detect and interact with my device in both ADB and Fastboot.
I was hoping being able to mount /system in the recovery menu meant I could use ADB shell and browse around the /system folder and tweak a few things. However, my computer behaves as though NOTHING is attached when I go into recovery. No "drivers not found" messages, no mysterious unidentified anything showing up in device manager.
Can anyone give me guidance as to how to get this working? Or am I not understanding how this is supposed to work?
Pixels do not have a recovery partition.; recovery lives in /boot alongside ramdisk and system kernel. Recovery is largely unnecessary from a modding perspective because of the ease of which we can directly flash device partitions.
Ok, but I can boot into stock recovery via "adb reboot recovery". From there I have the option to "Mount /system". I am hoping to be able to do that, then use adb to pull and then alter the build.prop file.
I can not flash device partitions because I cannot unlock the bootloader (I apparently have a Verizon phone.)

Categories

Resources