anyone know if this has got fastboot mode? I will try booting to ODIN screen and connecting to PC later, will report if I find anything.
chrisrotolo said:
anyone know if this has got fastboot mode? I will try booting to ODIN screen and connecting to PC later, will report if I find anything.
Click to expand...
Click to collapse
Almost no Samsungs do - Download mode (Odin/Heimdall) is Samsung's equivalent.
There's not really any need for fastboot with download mode.
thats what I figured, thanks.
What are you a nexus s noob like me? We better learn the adb codes now
Sent from my GT-P6210 using xda premium
I know adb but every other device I had also had fastboot. I knew about samsung Odin as well.
Related
Hi All,
i rooted my phone using what i thought was the right img file, but i can only assume it was the wrong file as i can now do nothing, i can boot into the Moto symbol, i can get to the droid with the warning triangle and into the fastboot section but i can no longer detect it when connected to the usb...
can anyone suggest a fix or am i screwed ??
thanks for any help
Try reflashing it with my tool, using unbrick feature, maybe you need fastboot drivers, just download it from sdk
Sent from my awesome ICS Xoom with xda Premium HD
cheers xxlordxx
ill give that a go, which drivers do i need to install for the fastboot ?
i downloaded the google usb driver package via the SDK last time, but it seems they are not firing up when i connect the tab.
TheWhiteDragon said:
cheers xxlordxx
ill give that a go, which drivers do i need to install for the fastboot ?
i downloaded the google usb driver package via the SDK last time, but it seems they are not firing up when i connect the tab.
Click to expand...
Click to collapse
If you can boot, you are not bricked - just start over with the root process using the correct image.
hey guys,
i have downloaded LAIOT but im not sure its detecting the pad, currently im getting
Searching For Device
List Of Devices
(Nothing listed)
on the pad
Starting Fastboot Protocol Support
tried doing the same using the different modes.
on Pad
Starting RSD Protocol Support
Same result on LAIOT
Recovery -
Same result.
this has all been done on a windows 7 laptop,
i have a linux laptop, will i get any more success using that with the google driver ?
just had a brain wave, checked device manager - i have an unknown device detected.. thats where the sodding thing has been hiding...
any ideas what drivers i need to get the dam thing detected correectly ?
just going to try using the default google ones from the SDK.
TheWhiteDragon said:
just had a brain wave, checked device manager - i have an unknown device detected.. thats where the sodding thing has been hiding...
any ideas what drivers i need to get the dam thing detected correectly ?
just going to try using the default google ones from the SDK.
Click to expand...
Click to collapse
Try a diff USB cable - download drivers from MOTOROLA website get this file - MotoHelper_2.1.32_Driver_5.4.0.exe
Okay here we go....
first thing let your xoom stuck on M logo.
Then hold power+volume up.
while power up press volume down to get firstboot.(make sure your PC and xoom know each other.)
You will see some text firstboot bla bla bla on left, top of screen.
Second thing open window cmd.exe
then type ...
cd /AndroidSDK/tools (where ever your adb.exe is located)
fastboot flash boot boot.img (the right boot image)
fastboot flash system system.img
fastboot erase cache
fastboot reboot
wait for reboot. You should see splash screen and you smile on your face.
TheWhiteDragon said:
hey guys,
i have downloaded LAIOT but im not sure its detecting the pad, currently im getting
Searching For Device
List Of Devices
(Nothing listed)
on the pad
Starting Fastboot Protocol Support
Click to expand...
Click to collapse
I need to fix it then...
Sent from my awesome ICS Xoom with xda Premium HD
thanks Mjamocha
ill give it ago tomorrow, sorry been flat out at work.
ill also try xxlords again on another machine just incase its the drivers on the laptop which are the problem.
XxLordxX said:
I need to fix it then...
Sent from my awesome ICS Xoom with xda Premium HD
Click to expand...
Click to collapse
sorry guys i have been flat out at work, SCCM deployment is taking a while to learn & play with.
but im back now and hopefully unbuggering my phone
i am going to redo all the bits you guys suggested on my PC rather than Craptop.
hopefully ill have more joy, ill let ya know how i get on 8)
What about using RDS?
woot im back
Thanks guys, just needed a fresh machine to do it on, think the craptop was a bit confused with the drivers.
TheWhiteDragon said:
woot im back
Thanks guys, just needed a fresh machine to do it on, think the craptop was a bit confused with the drivers.
Click to expand...
Click to collapse
Glad you got it going!
Had a similar problem where I had a boot loop and adb didn't recognise my device, but I could still put it into fastboot or recovery with power + vol down.
What I did was boot the Xoom so that it was stuck at the Moto logo, connected to the PC and queued up the fastboot command (fastboot flash boot boot.img) so the command window said "Waiting for device...", then reset the Xoom and manually put it into fastboot again at which point it picked up the queued command and started flashing.
I was flashing back to the stock Asus US 4.1 Rom from asus.com and that worked fine, but in the process I lost root. Now the operating system runs just fine, but when I power on into bootloader that works, but if I try recovery I get the android with the red ! (eclimation point), and if it try fastboot it says its starting fastboot, but just sits there.... Can someone please help me. Anything will help, and I mean anything. if there is a way to get root back or recovery through apx or anything. Any help will be much appreciated! thanks
If you are referring to what it says on the tablet saying fastboot is enable or something like that doesn't say any thing mire than that has long has you type fastboot devices in terminal under sdk/platform-tools and comes up with a serial number your good to go? If that helps?
Sent from my Galaxy Nexus using xda premium
larryv1979 said:
If you are referring to what it says on the tablet saying fastboot is enable or something like that doesn't say any thing mire than that has long has you type fastboot devices in terminal under sdk/platform-tools and comes up with a serial number your good to go? If that helps?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Sorry I should have been specific but I was at work. After I press vol and power and then go to the usb symbol; on the tablet it says "starting fastboot USB download protocol". On the computer it loads the driver for the "ASUS Android Bootloader Interface". I can't get the computer to comunicate with the tablet at all like this..."Fastboot devices" in cmd prompt does nothing. any advice?
Hello everyone,
I have done something utterly stupid with my Nexus 5, I wiped the internal storage and lost my roms, I really wasnt thinking.
I have tried looking at options like adb sideload but cant find a decent tutorial
Could I just get a micro usb to usb adapter and install a rom off that?
Would anyone be able to point me in the right direction with adb sideload?
Other problems are I can't get on the android SDK because the CMD box only flashes up.
Does the adb sideload option in TWRP actually do anything if you wait for it? Its been waiting for about 1 hour now and nothings happening.
Please guys any help is appreciated
osamarchie2000 said:
Hello everyone,
I have done something utterly stupid with my Nexus 5, I wiped the internal storage and lost my roms, I really wasnt thinking.
I have tried looking at options like adb sideload but cant find a decent tutorial
Could I just get a micro usb to usb adapter and install a rom off that?
Would anyone be able to point me in the right direction with adb sideload?
Other problems are I can't get on the android SDK because the CMD box only flashes up.
Does the adb sideload option in TWRP actually do anything if you wait for it? Its been waiting for about 1 hour now and nothings happening.
Please guys any help is appreciated
Click to expand...
Click to collapse
Why don't you flash the factory image using fastboot?
The Cmd box you are referring to happens because you need to navigate to that directory using Cmd and run it from there. You cannot just click it.
Thanks but I cant get the SDK to work at all. Im still looking into it but at the moment it wont work
Please somebody help me with the SDK, I dont know what else to do.
I cant open the SDK manager and I cant open it through eclipse either.
Someone else must have had this problem before
Click the link in my signature and then "adb and fastboot. What is it?"
This will help you configure adb properly. It also helps you learn commands. Like adb push.
adb sideload is the same as push but you type sideload instead.
FYI as much as people round here say it, there is no such thing as a soft brick. Its brick or not brick.
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
osamarchie2000 said:
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
Click to expand...
Click to collapse
Show down and don't panic. Your device is easily fixed. Hold the power button for 20 seconds. This will shut down the phone. Then press and hold the vol down then press the power button. That'll bring your into the bootloader.
Sent from my Nexus 5 using XDA Free mobile app
osamarchie2000 said:
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
Click to expand...
Click to collapse
Power + volume down button brings you in the bootloader, from there go into recovery (navigate with volume buttons and select with power button)
In recovery follow this guide: http://forum.xda-developers.com/showthread.php?t=2559200.
Or flash the factory image in the bootloader. (that should work because you need to unlock your bootloader in fastboot)
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
osamarchie2000 said:
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
Click to expand...
Click to collapse
Yeah that will work too. Water damage is never good for a phone even if it stil works after that. But that's another story
osamarchie2000 said:
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
Click to expand...
Click to collapse
Yes you can. You'll have to "tell" twrp where to find the rom zip.
Sent from my Nexus 5 using XDA Free mobile app
Only problem now is I cant get the SDK to work for my life. Ive spent 5 hours trying to fix my phone already today, I have the JDK installed. I open the eclipse thingy and when i try to open the SDK with eclipse it wont work either. Please somebody help with this
osamarchie2000 said:
Only problem now is I cant get the SDK to work for my life. Ive spent 5 hours trying to fix my phone already today, I have the JDK installed. I open the eclipse thingy and when i try to open the SDK with eclipse it wont work either. Please somebody help with this
Click to expand...
Click to collapse
You don't need the SDK. You're not developing here
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
TWRP cant find any of the files on my USB-OTG
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
osamarchie2000 said:
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
Click to expand...
Click to collapse
Did you read my thread that I told you to read?
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
osamarchie2000 said:
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
Click to expand...
Click to collapse
Here's a hint, read rootSU's sticky rollup and look for the 15 second fastboot adb installer.
Sent from my Nexus 5 using XDA Free mobile app
Very sorry, Ive just re-read what Im looking for
Appologies
thankyou all, phone is well and good and im on CM11.
Thanks guys, anyone who helped is the best
I'm working on un-bricking my SPH-l710 S3. I am trying to use Odin in the process. I am wondering if odin is recognizing my phone. I included an attachment showing Odin and my device mgr. If the zero is before the port # does that mean the computer isn't recognizing the phone? I downloaded and installed the newest samsung drivers. If anyone know how I can fix this I sure would appreciate it!
congaman59 said:
I'm working on un-bricking my SPH-l710 S3. I am trying to use Odin in the process. I am wondering if odin is recognizing my phone. I included an attachment showing Odin and my device mgr. If the zero is before the port # does that mean the computer isn't recognizing the phone? I downloaded and installed the newest samsung drivers. If anyone know how I can fix this I sure would appreciate it!
Click to expand...
Click to collapse
i think it recognized it ...but anyway reinstall the phone drivers to make sure .....here you can find what you need
congaman59 said:
I'm working on un-bricking my SPH-l710 S3. I am trying to use Odin in the process. I am wondering if odin is recognizing my phone. I included an attachment showing Odin and my device mgr. If the zero is before the port # does that mean the computer isn't recognizing the phone? I downloaded and installed the newest samsung drivers. If anyone know how I can fix this I sure would appreciate it!
Click to expand...
Click to collapse
Are your Samsung device is in download mode? Because its only recognize when you are on download mode.
Sent from my Sparkle V using XDA Premium 4 mobile app
Make sure you have the newest drivers installed on your pc..
1st make your phone go to download mode/odin mode then only your pc will recognize it...
(Press vol button+power button+home key simultaneously for going into download/odin mode...
You can find the full guide here http://andysolution.blogspot.in
Sent from my MI 3W using XDA Free mobile app
Devil Rocky said:
Make sure you have the newest drivers installed on your pc..
1st make your phone go to download mode/odin mode then only your pc will recognize it...
(Press vol button+power button+home key simultaneously for going into download/odin mode...
You can find the full guide here http://andysolution.blogspot.in
Sent from my MI 3W using XDA Free mobile app
Click to expand...
Click to collapse
I can't get the bootlaoders to download to the phone It fails every time. I'm going to try this: http://forum.xda-developers.com/showthread.php?t=2369125&page=1 I guess and see if I can get my phone back working again.
I think you should try universal adb drivers for your pc or u can download kingoroot app for your device in pc because when you install kingoroot app to your pc during installation process it will automatically install your phone drivers to your pc
Or you have to update your odin to latest version
Sent from my Magicon Mnote using Tapatalk
I got the drivers to work now in Odin but when I try to load the boot loader I keep getting a fail. I originally tried to fix my phone, not booting in to recovery, by using Kies. Kies tried to download something to the phone when it booted to download mode the phone boots directly to download mode and still won't boot to recovery. Now I'm going to try this: http://forum.xda-developers.com/showthread.php?t=2369125&page=1 to fix it. Unless someone can tell me a better solution.
Hi all,
I own a Samsung Galaxy Tab 2 10.1 SGH-I497 (don't forget, its that specific model) that I recently tried to flash a Kernel through CWM recovery. Unfortunately, by the time I realized I shouldn't do such a thing, it was too late and I pressed the wrong button to select "go back". Now my device is stuck in what I would assume is a boot loop, without any screen output. However, I can turn the tab off and my computer will make the "disconnect" noise, alike when a flash drive/USB is unplugged. It also makes a "connect" noise when the tab turns itself back on less than 5 seconds later. Since I need an IMEI number for the KIES firmware reset, I cannot fix this with KIES, as I have no access to my android OS and it is not written on the back plate (for some ungodly reason, thanks Samsung!) I do have an SD card and a cable, and also have ODIN installed, so any suggestions would be great Honestly I don't think it can get any more F*cked right now, so if you guys have a clue on what to start with, shoot!
Also, if ANYONE has a way to find the IMEI number, It would be VERY, VERY appreciated!~
Thanks!
-Tekk
Anyone? I have found out it is connecting/disconnecting to my PC as a "Qualcomm HS-USB QDLoader 9008 (COM3)", so I am going to attempt to use a qualcomm flash tool.
BUMP!
TheTekkitBoss said:
Anyone? I have found out it is connecting/disconnecting to my PC as a "Qualcomm HS-USB QDLoader 9008 (COM3)", so I am going to attempt to use a qualcomm flash tool.
Click to expand...
Click to collapse
I'm having this exact issue. Did you figure it out? Anyone? :silly:
I don't have this specific model but have you tried flashing the factory image using odin? Boot into download mode and connect it to your PC then odin should display "Added!" Then locate your firmware package and flash it
Sent from my espresso3g using XDA Labs
erasmosis said:
I'm having this exact issue. Did you figure it out? Anyone? :silly:
Click to expand...
Click to collapse
flashing a custom kernel that is not meant for the same device, is fatal in most of the cases. still if your device can get into either recovery or download mode. praise the lord.
there is a detailed guide in my signature below, where I had tried explaining most of the parts.
billysam said:
flashing a custom kernel that is not meant for the same device, is fatal in most of the cases. still if your device can get into either recovery or download mode. praise the lord.
there is a detailed guide in my signature below, where I had tried explaining most of the parts.
Click to expand...
Click to collapse
Thats exactly it... no download mode, no recovery mode.
erasmosis said:
Thats exactly it... no download mode, no recovery mode.
Click to expand...
Click to collapse
If none of those two modes work, then I'm sorry because now you have a pretty expensive paperweight now Only a JTAG can save it now
Sent from my espresso3g using XDA Labs
Do you have adb installed? You could try spamming adb reboot recovery when it connects for that brief moment.
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app