Hi guys, a friend gave me this phone because it has boot loop. It has no root and no strange flashes have been attempted. I'm trying to flash custom firmware with UpgradeDownload but as soon as it turns on, it restarts right after logo shows up. Any idea on how I can flash through adb/fastboot? Or maybe with SD?
You can flash phone's Stock ROM by means of ADB.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM.ZIP>
adb reboot
jwoegerbauer said:
You can flash phone's Stock ROM by means of ADB.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM.ZIP>
adb reboot
Click to expand...
Click to collapse
Will this work if debug mode is not enabled? And I don't know if bootloader is unlocked
ADB only works if USB debug got enabled: should be obvious.
BTW: FastBoot only works if OEM unlock got enabled.
jwoegerbauer said:
ADB only works if USB debug got enabled: should be obvious.
Click to expand...
Click to collapse
I don't know if it's enabled, as I said this isn't mine. Any way to check?
Run
Code:
adb devices
If nothing is listed then it isn't enabled.
jwoegerbauer said:
Run
Code:
adb devices
If nothing is listed then it isn't enabled.
Click to expand...
Click to collapse
I get this result:
List of devices attached
JAD82015000614 sideload
but if I try to use the second line of code I get:
error: closed
Phone is configured to operate in Sideload mode. When ADB returns "error:closed" then it's not really specific, can have many reasons.
Try
Code:
adb devices
adb usb
adb reboot
jwoegerbauer said:
Phone is configured to operate in Sideload mode. When ADB returns "error:closed" then it's not really specific, can have many reasons.
Try
Code:
adb devices
adb usb
adb reboot
Click to expand...
Click to collapse
it gives me back the same error when trying "adb usb"
My recommendation: Take phone to authorized service center and let them try to fix it.
jwoegerbauer said:
My recommendation: Take phone to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
It's not worth for this phone, thanks for your time, if you have other ideas let me know
TunguskaMed said:
Hi guys, a friend gave me this phone because it has boot loop. It has no root and no strange flashes have been attempted. I'm trying to flash custom firmware with UpgradeDownload but as soon as it turns on, it restarts right after logo shows up. Any idea on how I can flash through adb/fastboot? Or maybe with SD?
Click to expand...
Click to collapse
That's how I solved the issue. I called the Wiko assistance and I asked for the stock firmware because of boot looop. They sent me an exe wich did all by itself and now the phone is fully working. That was easy after all!
Related
Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.
looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.
Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......
Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.
You need the drivers.
albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.
the same issue for me. is there any working solution for that?
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing
I'm on a Mac and my N5 appears in fastboot, but fails to in adb. When I type the command ./adb devices it says attached devices, but no number appears. Any idea why?
Try a different USB port, and also try a different cable on the same port
Also try toggling USB storage mode from MTP to Camera - has worked for me
If device is on/using fastboot mode… you won't be be able to use adb.
adb only works in android or recovery. Which are you in?
I've tried both in recovery and android. I've turned USB debugging on and off, killed the server and restarted it to no avail.
Stock recovery doesn't have adb enabled, afaik.
It should, how else do you sideload an OTA?
beekay201 said:
Stock recovery doesn't have adb enabled, afaik.
Click to expand...
Click to collapse
it didnt used to, but since they now allow adb sideload, I think it does.
@ the OP, Will be a driver issue. There are threads about this.
ebtek220 said:
It should, how else do you sideload an OTA?
Click to expand...
Click to collapse
rootSU said:
it didnt used to, but since they now allow adb sideload, I think it does.
@ the OP, Will be a driver issue. There are threads about this.
Click to expand...
Click to collapse
Afaik, sideload is a diff "mode" of adb. I.e. if on sideload mode.. You can't push files to /sdcard/.
beekay201 said:
Afaik, sideload is a diff "mode" of adb. I.e. if on sideload mode.. You can't push files to /sdcard/.
Click to expand...
Click to collapse
True, but I would still expect adb devices to work. Though I've never tested it.
If you run 'adb devices' when in stock recovery it'll come up with 'sideload' as the status as opposed to 'device'
I've tried everything I can think of to solve this issue. I even tried a different, mac, computer to no avail. For kicks I tried to access adb on my 2012 N7. It connected right away without issue. This tells me the problem has to do with my N5 which cannot get out of offline mode.
Found a version of adb 1.0.31 for mac, I was on 1.0.29, and this solved my problem of my device being offline. When I went to sideload the 5.01 OTA, I'm told I need adb 1.0.32. Can anybody share with me version 1.0.32 of adb and fastboot for mac? I greatly appreciate it!
ebtek220 said:
Found a version of adb 1.0.31 for mac, I was on 1.0.29, and this solved my problem of my device being offline. When I went to sideload the 5.01 OTA, I'm told I need adb 1.0.32. Can anybody share with me version 1.0.32 of adb and fastboot for mac? I greatly appreciate it!
Click to expand...
Click to collapse
Grab android-sdk-tools for mac from Google. Install it.
All is good. I did install SDK, but at first didn't realize that you can actually have two versions of adb on your CPU at the same time and 1.0.31 was always being used. All is now fixed. Thanks for the help!
I need to restore to stock firmware to get Lollipop, but adb won't recognise my phone in cmd, thus I can't follow this guide: http://forum.xda-developers.com/showthread.php?t=2542219 . I installed the Motorola Drivers from here: http://forum.xda-developers.com/showthread.php?t=2550635 , and I have the Motorola Device Manager installed. MotoTool picks up my device and is able to boot it into fastboot and install CWM or TWRP, but when I try to flash stock recovery using MotoTool it either gives me a 'no command' screen or doesn't work at all. Anyone having the same problem/know how to fix this? I'm on the Moto G 2013 XT1032 British retail.
EDIT: I fixed it! I replaced Moto Tool's stock recovery with the one that was included in here: http://forum.xda-developers.com/show...3#post54872143 then used Moto Tool to flash it, as that recognised my phone. I could then download the OTA as normal and installed it like a regular update. Enjoying Lollipop!
If the phone is in fastboot mode, try using fastboot commands on your computer. At the command prompt, type fastboot devices to see of your phone's serial # appears.
Do you have USB debugging enabled in settings?
Are you opening cmd in the directory where fastboot and adb were installed?
Are you sure you installed adb and fastboot correctly?
audit13 said:
If the phone is in fastboot mode, try using fastboot commands on your computer. At the command prompt, type fastboot devices to see of your phone's serial # appears.
Click to expand...
Click to collapse
SammyP6 said:
Do you have USB debugging enabled in settings?
Are you opening cmd in the directory where fastboot and adb were installed?
Are you sure you installed adb and fastboot correctly?
Click to expand...
Click to collapse
Yes to both of these, I was in fastboot and 'adb devices' came back with nothing even though I was in the directory where adb and fastboot were installed and the phone had USB debugging enabled. I fixed it a different way though, I replaced Moto Tool's stock recovery with the one that was included in here: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143 then used Moto Tool to flash it as that recognised my phone. I could then download the OTA as normal and installed it like a regular update.
Adb commands won't work when the phone is in fastboot mode from what I have seen.
audit13 said:
Adb commands won't work when the phone is in fastboot mode from what I have seen.
Click to expand...
Click to collapse
They didn't work at all, no matter what mode I was in. All sorted now though.
Fithboy said:
They didn't work at all, no matter what mode I was in. All sorted now though.
Click to expand...
Click to collapse
It's great you that got the issue sorted out.
Post your solution in case it may help other users down the road. Thanks.
Hi guys,
I have a rooted Device with CM and TWRP installed, but someting happenend using the device and my Moto G got stuck on startup logo and Recovery TWRP logo, with adb I have acess to adb shell but everything else like adb reboot bootloader etc doesn't seems to work, with adb shell I have realized that the TWRP wasn't running 'cause when I use the interface on shell I get this message
$twrp wipe cache
"TWRP does not appear to be running. Waiting for TWRP to start"
Is there any way to install a new recovery via adb shell or reinstall a new rom, factory reset or something like that to make my cellphone work again?
Thanks,
If you are okay to wipe internal storage, the following fastboot command will probably make TWRP load again:
fastboot erase userdata
fastboot flash recovery newrecovery.img - is a way to reflash recovery, however the above command may still be required.
The problem is that with fastboot the device is not recognized, only when I open the recovery mode...
The logo freezes but the device is reconigzed with adb devices...
gconsentini said:
The problem is that with fastboot the device is not recognized, only when I open the recovery mode...
The logo freezes but the device is reconigzed with adb devices...
Click to expand...
Click to collapse
What OS are you using? Maybe try the ADB commands:
adb shell
wipe data
lost101 said:
What OS are you using? Maybe try the ADB commands:
adb shell
wipe data
Click to expand...
Click to collapse
It's the latest CM
I'll try, but the last time I got this message.
"TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit."
EDIT
using
adb shell
twrp wipe data
happened the same above
gconsentini said:
It's the latest CM
I'll try, but the last time I got this message.
"TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit."
EDIT
using
adb shell
twrp wipe data
happened the same above
Click to expand...
Click to collapse
I meant what OS on PC are you using. Stop adding the phrase 'twrp' - type the command as I wrote it.
lost101 said:
I meant what OS on PC are you using. Stop adding the phrase 'twrp' - type the command as I wrote it.
Click to expand...
Click to collapse
Sorry, I'm using Windows 10, if I use only wipe data, the command wipe is not reconigzed.
Can you enter fastboot mode by holding vol down and powering phone on?
lost101 said:
Can you enter fastboot mode by holding vol down and powering phone on?
Click to expand...
Click to collapse
yes, but when I connect the phone usb and use fastboot devices
it has no devices on the list
gconsentini said:
yes, but when I connect the phone usb and use fastboot devices
it has no devices on the list
Click to expand...
Click to collapse
There are many threads on Win10 and usb driver issues. If you don't want to try to fix fastboot on Windows, you could boot into a Ubuntu Linux LiveCD and install fastboot there.
lost101 said:
There are many threads on Win10 and usb driver issues. If you don't want to try to fix fastboot on Windows, you could boot into a Ubuntu Linux LiveCD and install fastboot there.
Click to expand...
Click to collapse
Yes, I thought about that too =x
SOLVED
Guys the problem was that I've not installed the drivers before, after doing this, I just installed the stock rom from motorola.
Thanks
gconsentini said:
SOLVED
Guys the problem was that I've not installed the drivers before, after doing this, I just installed the stock rom from motorola.
Thanks
Click to expand...
Click to collapse
Hey i'm having the same issue, would you mind telling me how you re-flashed the Motorola rom, Thanks
thomasswan5547 said:
Hey i'm having the same issue, would you mind telling me how you re-flashed the Motorola rom, Thanks
Click to expand...
Click to collapse
Install the Minimal Fastboot & ADB package and the Motorola USB drivers, use the mfastboot package and install the stock ROM as per the instructions provided, but ignore the disassembly part, unless you have your phone does not respond to keypresses.
https://forum.xda-developers.com/showpost.php?p=71328823&postcount=915
After entering recovery I realized that it has a "Reboot to bootloader" on my Samsung phone. And it doesn't reboot to Download mode, instead, it reboots to a "Fastboot mode". Does this Fastboot really work or it's better do not modify anything there?
ferreraiury05 said:
After entering recovery I realized that it has a "Reboot to bootloader" on my Samsung phone. And it doesn't reboot to Download mode, instead, it reboots to a "Fastboot mode". Does this Fastboot really work or it's better do not modify anything there?
Click to expand...
Click to collapse
It seems the A10? Which model is? At least type fastboot devices to see if it is listed in CMD, anyway locked as it is you couldn't do much.
ferreraiury05 said:
After entering recovery I realized that it has a "Reboot to bootloader" on my Samsung phone. And it doesn't reboot to Download mode, instead, it reboots to a "Fastboot mode". Does this Fastboot really work or it's better do not modify anything there?
Click to expand...
Click to collapse
As I has knew since I used HTC M7. ''Locked'' status , it means the phone can't flash any custom ROM. my phone is Samsung M20 . it don't show as your picture
SubwayChamp said:
It seems the A10? Which model is? At least type fastboot devices to see if it is listed in CMD, anyway locked as it is you couldn't do much.
Click to expand...
Click to collapse
No, it's a A015M. After looking for some help, I realized that it really doesn't work.
fellpanda said:
Using Samsung Android 11 default ROM - nothing modified. I'm trying to boot custom recovery (twrp) temporarily from PC console.
What I did to set up adb and fastboot:
OEM unlocked, usb debugging active, not rooted.
I installed latest ADB and Fastboot. Also installed Samsung USB drivers. Samsung doesn't provide fastboot drivers, and I've read on some thread that AOSP drivers are used for that. So, I'm using Google's Bootloader Interface installed via Device Manager, because plenty of guides suggest that online.
Problem:
I can use adb when phone's on. But when it comes to fastboot, I can get into it by 'adb reboot bootloader' and, i can see the device is listed using 'fastboot devices', but i can't really do anything at all other than that command.
I tried 'fastboot oem device-info', 'fastboot boot twrp.img'. I don't get any error messages. When I execute a command, the command just stays there on the terminal like it is busy executing. Waiting for over 15 minutes and there's no change.
Ex: When I executed the boot command, the console output was stuck at 'Sending boot.img', without any progress.
Click to expand...
Click to collapse
crownvn said:
As I has knew since I used HTC M7. ''Locked'' status , it means the phone can't flash any custom ROM. my phone is Samsung M20 . it don't show as your picture
Click to expand...
Click to collapse
That's not my device, it's from a YouTube video, because I couldn't take any picture until now. My device is listed as unlocked.
Samsung devices don't know of Fastboot mode but of Download ( aka ODIN ) mode, hence not any fastbbot command works.
xXx yYy said:
Samsung devices don't know of Fastboot mode but of Download ( aka ODIN ) mode, hence not any fastbbot command works.
Click to expand...
Click to collapse
ferreraiury05 said:
No, it's a A015M. After looking for some help, I realized that it really doesn't work.
Click to expand...
Click to collapse
I think fastboot is only there because it is a MTK device.
If it's a Samsung SM-A015M then it's not MTK, but Qualcomm based.
I have j7 2015 and i have twrp and i want to do "fastboot boot <magisk patched image>" but i can't do it because i can't get inside fastboot mode
Any soulotions please?
Sorry for bad English.
As said earlier here Samsung devices don't have a FASTBOOT mode
xXx yYy said:
As said earlier here Samsung devices don't have a FASTBOOT mode
Click to expand...
Click to collapse
Thanks so the only way to flash images only with modded TWRP or flashify
Abdullrahman_Dawaliby said:
Thanks so the only way to flash images only with modded TWRP or flashify
Click to expand...
Click to collapse
or odin
With fastboot it is possible to enable the UART serial interface for viewing kernel messages. Is it even possible to do that on Samsung devices, since fastboot is not available?