[Q] Device not recognized in custom recovery - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

I'm attempting to flash a ROM to my Galaxy S4 using the adb sideload method. However, my computer doesn't recognize my phone unless I use the default recovery mode. I can't use the default recovery mode because the signature verification fails. I've tried CWM and TWRP, and in both cases adb returns "error: device not found". Are there extra drivers I need to install?
Using an AT&T Galaxy S4 I337 on stock 4.2.2 rooted.

Motu88 said:
I'm attempting to flash a ROM to my Galaxy S4 using the adb sideload method. However, my computer doesn't recognize my phone unless I use the default recovery mode. I can't use the default recovery mode because the signature verification fails. I've tried CWM and TWRP, and in both cases adb returns "error: device not found". Are there extra drivers I need to install?
Using an AT&T Galaxy S4 I337 on stock 4.2.2 rooted.
Click to expand...
Click to collapse
If your rooted just do a straight flash in recovery.. Please wipe 1st no dirty flashes then flash the kernel

sloanster said:
If your rooted just do a straight flash in recovery.. Please wipe 1st no dirty flashes then flash the kernel
Click to expand...
Click to collapse
Thanks for your reply. I have been flashing straight from the phone's memory, but I would still like to know what I can do to get the adb method working for future reference. If I accidentally get to a point where I can't boot properly and I don't have an available backup on the phone, I want to be able to flash from my desktop.

Motu88 said:
I'm attempting to flash a ROM to my Galaxy S4 using the adb sideload method. However, my computer doesn't recognize my phone unless I use the default recovery mode. I can't use the default recovery mode because the signature verification fails. I've tried CWM and TWRP, and in both cases adb returns "error: device not found". Are there extra drivers I need to install?
Using an AT&T Galaxy S4 I337 on stock 4.2.2 rooted.
Click to expand...
Click to collapse
I had similar problems with TWRP. I ended up searching around Google and found some drivers that worked. Some keywords I used were the Hardware ID(s) that the unknown device gave to Windows, and "twrp". It's just using a different version of ADB or something, and Windows doesn't like it. I'm out of time for today, but I'm sure you'll find it. Look for google results that take you either to XDA or over to TWRP's website.

Related

[Q] Failed Root? Stock Sideload Help!

Hello all,
I initally used the Wugz root toolkit to unlock, install drivers and root my device. I flashed CWM and a ROM. Once I flashed the ROM, it wouldn't boot, but would flash the google logo, go black, then go to the google logo and open up CWM again.
I searched for backups, they were gone. So I tried a few things and now I can't even get to CWM.
All I can get to is the Recovery menu and Stock Recovery. My computer won't recognize the device in adb fastboot but will recognize it when I put it into sideload from the stock recovery.
I've tried to flash the 4.1.2 and 4.2.2 images from the Google developer website but when it verifies the installation package it says installation aborted.
Is there any way I can fix this just from the Stock Recovery sideload? Is this hopelesss?
Take a look at this THREAD
Nico_60 said:
Take a look at this THREAD
Click to expand...
Click to collapse
Thanks. I did try this first, I must have messed it up somewhere. I'll try it again. Not sure if it'll work without the device being recognized under fastboot.
To know if it's recognized type "fastboot devices" but if the driver were already installed it must be ok
Whew got it to work. Thanks.

Soft brick (Already searched up and down)

So I messed up my Nexus somehow. I was trying to install MIUI coming from Carbon ROM but something went wrong as it got stuck on the miui logo. So I rebooted to TWRP and restored my backup. So then I tried to install PA and then it just got stuck on the google logo. So i restored my backup again and tried again to no avail. Then after that I couldn't restore my backup ( I keep getting FAILED as soon as the data restore starts). I can boot to Recovery but I dunno what to do. I tried sideloading but that's not working. I tried the toolkit but everytime it tries to download the factory image it says 404. The phone charges and whatnot but I don't know what to do. I only have the PA rom on my phone and reinstalling it doesn't do anything. The only weird thing is that when I try to install the PA gapps I get a FAILED message. Any help would be appreciated
varem said:
So I messed up my Nexus somehow. I was trying to install MIUI coming from Carbon ROM but something went wrong as it got stuck on the miui logo. So I rebooted to TWRP and restored my backup. So then I tried to install PA and then it just got stuck on the google logo. So i restored my backup again and tried again to no avail. Then after that I couldn't restore my backup ( I keep getting FAILED as soon as the data restore starts). I can boot to Recovery but I dunno what to do. I tried sideloading but that's not working. I tried the toolkit but everytime it tries to download the factory image it says 404. The phone charges and whatnot but I don't know what to do. I only have the PA rom on my phone and reinstalling it doesn't do anything. The only weird thing is that when I try to install the PA gapps I get a FAILED message. Any help would be appreciated
Click to expand...
Click to collapse
Have you tried to install another rom on your nexus?
you can put it on with adb push command from recovery though a pc, and then wipe everything and try to install it.
Or you can download stock 4.2.2 rom here: http://forum.xda-developers.com/showthread.php?t=2147281
Here you can find your factory image directly from google: https://developers.google.com/android/nexus/images#occamjdq39
How do I adb push?
varem said:
How do I adb push?
Click to expand...
Click to collapse
you must enter into recovery, connect your phone to your pc with usb cable and then you should be able to see your device,
try
Code:
adb devices
on CMD and it can see your phone type
Code:
adb push **your-rom-from-computer** /sdcard/
then just install it from the recovery
When you say recovery do you mean the main menu? I'm using TWRP and when I'm on the main menu my PC doesnt read the device
http://forum.xda-developers.com/showthread.php?p=34674471
My bad I should have read.....you tried a tool kit already
Sent from my Nexus 4 using xda app-developers app
mmh i don't have twrp so i don't know, do you have the option to mount sdcard to usb?
varem said:
When you say recovery do you mean the main menu? I'm using TWRP and when I'm on the main menu my PC doesnt read the device
Click to expand...
Click to collapse
Ok, wait. I need some clarification. I'm going to try to be as simple as possible, to make sure we are on the same page. When you say your PC doesn't read the device, do you mean through adb or on Windows Explorer?
If you mean through Windows Explorer, then that is not where you need to be. You must get adb working as a bridge to your device. Use this sticky guide to get it set up. I would recommend reading that guide top to bottom anyway, it's extremely informative and new-user friendly. Anyway, the info you need is in the 'Setting up ADB for our device:' section.
If you have adb installed, you need to check to see if it recognizes your device. Do this by opening up cmd and navigating to the folder that adb.exe is located. After that, use 'adb devices' to see if adb recognizes your device. If so, move to the next paragraph. If not, your drivers aren't set up properly for recovery mode. Go into Device Manager on your computer and find your device (under something like 'Other devices', or 'Android device'). If you find it, then get these drivers and install them for the device. Do this by right-clicking, and selecting 'Update Driver Software...', 'Browse my computer for driver software', and browse to that folder. I may have missed a few steps on installing the drivers, it's been a while. If so, just search on how to do it, or post back here. I'm sure I can walk through it and get a more precise guide.
Assuming you have adb installed and it recognizes your device, you need to open up cmd and navigate to the folder that adb.exe is located. Then, use the adb push command as outlined above.
Download stock images from Google's website and flash it via fastboot. If you don't know how to do it then use a toolkit like WuguFresh to do it for you.
Sent from my Nexus 4
You can also use the toolkit for pushing a ROM in your SDcard, or backup your SD in your pc.
Envoyé depuis mon Nexus 4 en utilisant Tapatalk 4 Beta
The PC reads the device as it detects it but when I type in adb devices it doesnt show up. It only ever shows up when I enter the sideload menu in TWRP
atulalvenkar said:
Download stock images from Google's website and flash it via fastboot. If you don't know how to do it then use a toolkit like WuguFresh to do it for you.
Sent from my Nexus 4
Click to expand...
Click to collapse
Thanks man. This toolkit saved my nexus!
Sent from my Nexus 4 using xda premium

[Q] GAPPS failed to flash/install, what are my options?

So I decided to install PA 4.6 BETA4 on my Nexus 4, 4.3 JWR66Y Phone which is unlocked and rooted. I used the Nexus Root Toolkit to install the latest TWRP recovery, put the pa_mako-4.6-BETA4-20141007.zip and pa_gapps-stock-4.4.4-20141011-signed.zip onto my phone. Went into recovery to flash the two. The PA ROM went successful, tried flashing the gapps and it just says failed. I tried redoing the ROM flash then gapps again but that doesn't work.
I had the dumb idea of moving my nandroid backup to my computer and now I can't transfer it back to my phone using adb sideload. I go into ADB sideload in TWRP, and it just says no devices found when trying to transfer maually. When I try using NRToolkit, it fails as well.
Any advice? I feel like I've searched everywhere. I don't know what the next step to take is. Maybe Flash Stock + Unroot option on the NRToolkit? Have I somehow flashed incompatible zip files?
sirmot said:
So I decided to install PA 4.6 BETA4 on my Nexus 4, 4.3 JWR66Y Phone which is unlocked and rooted. I used the Nexus Root Toolkit to install the latest TWRP recovery, put the pa_mako-4.6-BETA4-20141007.zip and pa_gapps-stock-4.4.4-20141011-signed.zip onto my phone. Went into recovery to flash the two. The PA ROM went successful, tried flashing the gapps and it just says failed. I tried redoing the ROM flash then gapps again but that doesn't work.
I had the dumb idea of moving my nandroid backup to my computer and now I can't transfer it back to my phone using adb sideload. I go into ADB sideload in TWRP, and it just says no devices found when trying to transfer maually. When I try using NRToolkit, it fails as well.
Any advice? I feel like I've searched everywhere. I don't know what the next step to take is. Maybe Flash Stock + Unroot option on the NRToolkit? Have I somehow flashed incompatible zip files?
Click to expand...
Click to collapse
UPDATE: I got the gapps to install successfully. I installed Wifi File Explorer through NRToolkit in order to transfer files to my phone. And transferred the same exact file to my phone. I tried flashing the file and it worked... I'm guessing the wired transfer corrupted the file somehow. Thank you NRT for that option to install apks.
Hi,
Good to know that you managed to get it working . Could you add a [SOLVED] tag on the title of your thread?
Also, I'd like to point out that when you tried to copy the backup file via adb sideload it had a reason to not work! Adb sideload was born to flash zips which are transfered via adb to the device. Loading then as soon as they are loaded. To copy the files back to your device using adb you should have used the "adb push" command, which is like a "copy/paste" on the shell . Hope this helps in the future.
~Lord
XxLordxX said:
Hi,
Good to know that you managed to get it working . Could you add a [SOLVED] tag on the title of your thread?
Also, I'd like to point out that when you tried to copy the backup file via adb sideload it had a reason to not work! Adb sideload was born to flash zips which are transfered via adb to the device. Loading then as soon as they are loaded. To copy the files back to your device using adb you should have used the "adb push" command, which is like a "copy/paste" on the shell . Hope this helps in the future.
~Lord
Click to expand...
Click to collapse
Ah of course that makes sense. I think I tried just pushing the file when I was in the bootloader as well, but it also gave me devices not found. Not sure why, but anyways thanks for the reply. Hopefully this might help out someone.
sirmot said:
Ah of course that makes sense. I think I tried just pushing the file when I was in the bootloader as well, but it also gave me devices not found. Not sure why, but anyways thanks for the reply. Hopefully this might help out someone.
Click to expand...
Click to collapse
Hi,
In bootloader you mean fastboot right? If so, you can't use adb on this mode. To push a file via fastboot is only the stock image using "fastboot install" or "fastboot boot".
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
XxLordxX said:
Hi,
In bootloader you mean fastboot right? If so, you can't use adb on this mode. To push a file via fastboot is only the stock image using "fastboot install" or "fastboot boot".
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
Click to expand...
Click to collapse
Oh I see. So the adb push can only be used when the phone is on normally and connected via adb? Is there a way to transfer files to a phone if it were stuck in fastboot?
sirmot said:
Oh I see. So the adb push can only be used when the phone is on normally and connected via adb? Is there a way to transfer files to a phone if it were stuck in fastboot?
Click to expand...
Click to collapse
Hi,
If you're stuck in fastboot you can flash a recovery or use the "fastboot boot" to boot in recovery and then use adb push from there .
~Lord

LG Stylo 2 unable to be recognized in recovery

New to XDA so sorry if i posted this in the wrong place
But recently i received a new phone, an LG Stylo 2 Boost Mobile. It recognized fine while it was on through adb, but when i turned it off and booted into recovery, it wouldn't be recognized by adb, nor fastboot, and when i tried to "reboot into bootloader" it only restarted the whole phone into its normal boot. Adb sideload worked but i had no idea what files to try due to a locked bootloader and no stock ROMs found anywhere. I tried kingroot and it didn't have any ways to get an instant root. Im running Ubuntu and the phone is on 6.0.1 Marshmallow. Any ideas out there? I'd be sure to give them a try
The phone would only be accessible in recovery via the adb sideload option with stock recovery.
What exactly are you trying to accomplish?
es0tericcha0s said:
The phone would only be accessible in recovery via the adb sideload option with stock recovery.
What exactly are you trying to accomplish?
Click to expand...
Click to collapse
I'm trying to unlock the bootloader so i can flash a new recovery then root won't be hard to achieve, but when i try to access the phone in recovery mode, it doesn't recognize whatsoever. I thought there would be something i could do with sideload to somewhat downgrade the system and gain some type of bootloader, but that didn't work. Is there someway i can flash a custom recovery?
Don't believe there are any options for unlocking the bootloader or a custom recovery for that phone. According to what I could find in a quick search, there is root available but only on the software update ending in ZV3.
https://forum.xda-developers.com/lg-g-stylo/help/boost-mobile-lg-stylo-2-lgls775-t3388675
Alright, thanks for the info, wasn't sure if there was a way around it or not

Problems installing a custom ROM on Grand Prime Duos (SM-G530H)

I have a Grand Prime Duos (SM-G530H), currently running an Android version 4.4.4 and I wanted to install a custom ROM to have a higher version of Android. (Tried installing LineageOS 17.1 from itexpert.120, but any custom ROM with a higher version of Android would do)
Problem 1: No custom recovery seems to work.
I installed the TWRP app and tried to flash 4 different versions of their recovery images (from twrp-3.7.0_9-0-fortuna3g.img to twrp-3.4.0-0-fortuna3g.img) and all of them resulted in a unless glitched gray recovery screen.
I also tried the CWM app but it fails to download a recovery image for the device, tried looking online for a image file but didn't find one either.
In the end I reverted the recovery to the default one that I had backed up.
Problem 2: ADB works but fastboot doesn't.
I downloaded the ADB tools to try and flash the ROM from my computer instead. The ADB commands work, but when the device enters recovery mode the fastboot commands don't work. ("fastboot devices" doesn't even list the device)
Went to check the drivers. Most tutorials say to open the device manager and look for the phone device with an exclamation mark and update the driver with ones downloaded from the official site. To my surprise the device doesn't show up at all in the device manager (not even with an exclamation mark). Trying to install the drivers anyway says it's already installed.
The Odin software showed the same problems, detects the device when it's on, but doesn't detect it when in recovery mode.
Problem 3: Error when installing directly through the recovery mode options.
This probably wouldn't work for technical reason I'm not aware of, but I went and tried anyway. On the default recovery mode there are 2 options, apply update from ADB and apply update from external storage. Tried both, the first using the command "adb sideload <lineage rom file>" and the second using the ROM file in a SD card. Both begin to unpack and install the file but after a while throw an error "E: failed to verify whole-file signature", then the device boots to the usual OS.
So, is there anything else I can try? any other recovery images or hacks that won't give me the glitched recovery that TWRP had? Or another method to install a ROM without fastboot? Maybe using another file format in problem 3?
OBS: the device is rooted and has no "OEM unlock" options in its settings
delete the samsung usb drivers and install an older version. only way you can flash custom recovery is with odin. only way to flash custom rom is with custom recovery. fastboot and sideload wont work, this isnt a nexus
You think the reason why the custom recovery was glitched is because it was flashed through the TWRP app and not Odin? Seems unlikely. Is there any non-TWRP recovery image for my model you can point me to?

Categories

Resources