Can ADB detect devices that's off? - Samsung Galaxy W I8150

I was just wondering, i got a One S and i think it got bricked. Some suggest me to use "adb reboot-bootloader" to get into Hboot to get into Recovery. It can't be switched at all. Ik its an irrelevant qn to our GWonder here but Im asking here cos the One S forum's devs all went away to another device..
CM11 Powered G-Wonder

Related

Fully Bricked Galaxy Nexus! HELP!

Okay so my friend bricked his galaxy nexus (Gave it to me because he said its bricked) of course i accepted it lol. But i tried to fix it i did everything i could from reading forums i swear i have worked forever looking for a fix. It is completely unresponsive no download mode. no ADB connection because when it plugs into a computer it shows up as OMAP 4440 or something like that. i have tried all kinds of different drivers and i have tried on multiple computers (Xp, Windows7, even a mac) he said he was flashing the sdcard or something and unplugged it by accident. So i could understand that being a issue since the phone only has a internal sd card. Anyone know how to get it back? i havent seen a Jtag yet for it and i have a Jig for my Galaxy Sii Skyrocket but it doesnt work on the nexus (FYI to anyone out there the jig works on my dads samsung windows phone) HELP!
You tried different drivers? You should just use the most current ones for the phone. Did you try the new toolkit mskip posted? Did you isntall the SDK?
paperhurts said:
You tried different drivers? You should just use the most current ones for the phone. Did you try the new toolkit mskip posted? Did you isntall the SDK?
Click to expand...
Click to collapse
Thanks for the response i didnt use mskips i dont think. i have tried the galaxy nexus toolkit 6.0 or whatever but i have tried all kinds of drivers including the google official galaxy nexus i515 or something like that. it shows up as omap 4440 in app manager and disconnects and connects constantly then says device didnt install properly. what do you mean by the sdk? i cant find any way to access my phone. i think i tried something with sdk but im not sure
Yes i read up i did do that GNex Toolkit v6.0 and it wouldnt find my phone (Because of the omap 4440 disconnect and reconnect thing i believe.
First off, on't use a toolkit.
Second, when you plug it in, go to device manager, right click the "OMAP 4460" and click install driver. Either install PDANet or find the driver online and your phone should be able to be used in fastboot.
Finally, if your (Or your friends) phone was "Fully Bricked" it wouldn't be recognized by the computer, it wouldn't turn on, it would literally not be able to do anything except sit there, the fact that the computer sees it means that it is "Soft Bricked" which is much less serious.
miketoasty said:
First off, on't use a toolkit.
Second, when you plug it in, go to device manager, right click the "OMAP 4460" and click install driver. Either install PDANet or find the driver online and your phone should be able to be used in fastboot.
Finally, if your (Or your friends) phone was "Fully Bricked" it wouldn't be recognized by the computer, it wouldn't turn on, it would literally not be able to do anything except sit there, the fact that the computer sees it means that it is "Soft Bricked" which is much less serious.
Click to expand...
Click to collapse
i appreciate it but when i install the driver which one should i select? it is the Verizon LTE one and i have tried manually choosing the driver but there is so many. What one should i choose?
When i try to install pdanet it always uninstalls at the end automaticaly? why is that?
IRusselldABear said:
When i try to install pdanet it always uninstalls at the end automaticaly? why is that?
Click to expand...
Click to collapse
I couldn't get PDAnet to work for me either. It asks you to enter Debugging mode and I can't get into android
I cant get into android neither thats the problem... it is unresponsive except for the fact that it says omap 4440 over and over. im gonna play with it more when i get home but im currently in school. LOL
is it possible to volume+power into recovery mode?
Jsweetser2 said:
is it possible to volume+power into recovery mode?
Click to expand...
Click to collapse
I can get mine into CWM, but whenever I'm flashing a ROM, it reboots itself.
Install PDANet and when it asks for your phone, go into Task Manager and force close the process. This will keep the driver/program installed without needing your phone and it should then be seen in recovery.
Not working still :/
Thanks for highjacking my post twinky lol. i have seen the answer to yours around... google a little more.
TwinkyOfHope said:
I can get mine into CWM, but whenever I'm flashing a ROM, it reboots itself.
Click to expand...
Click to collapse
Jsweetser2 said:
is it possible to volume+power into recovery mode?
Click to expand...
Click to collapse
Please Help!
My phone goes into boot loader and download mode however every time I flash Stock it finishes successfully and goes to the same google screen its always stuck on. I'm kinda a n00b so if anyone could help me with this (try to have a lot of detail) I would be grateful. Thanks
It sounds like what I did to my Galaxy Note before I bought my Nexus. When unrooting I overwrote my bootloader with a missed character through ADB. I tried everything, naked drivers, ODIN, all it would come up with was OMAP on the PC. I ended up having to return it to AT&T. Ask him if he was trying to root it the old way through ADB.
samiaziz said:
My phone goes into boot loader and download mode however every time I flash Stock it finishes successfully and goes to the same google screen its always stuck on. I'm kinda a n00b so if anyone could help me with this (try to have a lot of detail) I would be grateful. Thanks
Click to expand...
Click to collapse
samiaziz, make sure you're wiping everything before flashing a stock rom. It wouldn't hurt to wipe system, cache and dalvik and then restart recovery (in advanced menu) and wipe again before flashing the stock rom.
Ok, as long as it shows up, it's still working
OMAP440 is the processor, which means, that is is working, but the bootloader is corrupt, or missing. I'd say it's corrupt (Flash-error)
The best way I've found, check this website: http://www.mobiletechvideos.com and see if they have a JTAG solution... (My JTAG device will arrive in a few weeks )
Even if they don't, send it in, and they'll figure out a way to do that I think they do some special offer, if you send it in for testing purposes...
But, other than that, there's no way I can help you. The firmware is completely fu**ed...
Tried That
I have already tried getting into recovery but that dosnt work. it takes me to the google splash screen
2 words: fastboot, linux.
sent from my i9250
Instead of JTAG-ing it, you could always try this. The maker of the Riffbox JTAG has come out with a solution for unbricking by reflashing the OMAP processor.. Aptly named OMAPFlash.
I've used it with success several times, but also had it fail on me. It can't hurt though, if your phone is already bricked.
If it's coming up with OMAP4460 (even briefly) when the phone is plugged into your computer without a battery, you are able to run the program. You just need to install the drivers for it.
See http://forum.gsmhosting.com/vbb/f634/unbrick-dead-samsung-gt-i9250-galaxy-nexus-32gb-prime-via-usb-cable-freeeeeeeeeeee-1465412/ for download.
Lemme know if you need instructions.

[Q] adb says recovery when phone should be off?

Hey guys so I noticed this today when I was trying to charge my phone faster by turning it off that when I had it plugged into my computer after I turned my phone off, I typed in adb devices in terminal to see what it said and it showed my device and that it was in recover? But I thought the phone was off? I'm primoc htc one v running the rythmic rom 4.2.2. Is it always this way that when you plug in your phone it automatically turns on? I thought it stayed off while charging?
As a side question, do us primoc users have a kernel or way to "fast charge"?
Thanks!
If u r using cwm.... Change it.... Dats the problem.... Use twrp 2.4.1.0!!
Oh right I forgot to mention my recovery. I'm actually using TWRP 2.2.0 because I tried 2.4 and it wasn't working right, so I went back to what I had before

[Q] Ouya bricked? stuck in APX

Hi,
had my Ouya for two days, loaded some emulators had some fun, powered it off.
Powered it on after a day or so, no screen, no powerlight, just a fan sound.
Upon making a connection to my laptop the device gets recognized as the dreaded APX.
If you had a HTC one x this would mean a hard brick right?
does the same go for an Ouya? i already contacted Ouya support, but my guess is they will get back to me within several months (if they ever get back to me) and i'll have to pay TWICE the custom charge etc etc and wait for several months to receive the console again.
any of the tech minded Ouya people who have a solution?
to clarify:
ADB does not work
Device gets recognized as APX in windows
ADB does not work so no fastboot
i have no NAND backup or a CWM installed, it's bone-stock
No screen image
No powerlight
The only thing that works is the fan which goes on
hello,
luukneele said:
to clarify:
ADB does not work
Device gets recognized as APX in windows
ADB does not work so no fastboot
i have no NAND backup or a CWM installed, it's bone-stock
No screen image
No powerlight
The only thing that works is the fan which goes on
Click to expand...
Click to collapse
good luck... i think it's "game over".
luukneele said:
Hi,
had my Ouya for two days, loaded some emulators had some fun, powered it off.
Powered it on after a day or so, no screen, no powerlight, just a fan sound.
Upon making a connection to my laptop the device gets recognized as the dreaded APX.
If you had a HTC one x this would mean a hard brick right?
does the same go for an Ouya? i already contacted Ouya support, but my guess is they will get back to me within several months (if they ever get back to me) and i'll have to pay TWICE the custom charge etc etc and wait for several months to receive the console again.
any of the tech minded Ouya people who have a solution?
to clarify:
ADB does not work
Device gets recognized as APX in windows
ADB does not work so no fastboot
i have no NAND backup or a CWM installed, it's bone-stock
No screen image
No powerlight
The only thing that works is the fan which goes on
Click to expand...
Click to collapse
Yup your screwed the only way to fix it is to use NvFlash, BUT, the ouya has a Secure Boot Key(SBK), and unless ouya gives us that and the blobs you have a nice shiny paperweight.

can someone please help me????

yup im done messing with this tablet i never had so many problems in my life... so i thought my tablet was dead a lil while ago... then it came on.... so i just was watching wwjoshdo video on youtube.. about updating your N7 to 4.4.. so i followed the video and now im stuck with a tablet with NO os... i can get into bootloader and stock recovery.. my bootloader is unlocked still... i also just tried to restore it i ran that tool also and that wont work it just runs half way threw then freezes... i been going nuts... can someone that has teanviewer PLEASE help me out... ???im still new to nexus.. i havent been stuck like this in a very long time.. its called the oneclick factory restore dead or alive.. thats what i used also.. both will not finish... i have stock recovery now.. but no os..
This is why you don't use toolkits... If you can get into bootloader mode, you're fine. Boot into the bootloader and hook it up to your PC. In a command prompt/terminal window type "fastboot devices". If it returns a string of numbers and letters you're all set. Just download the factory image from the Android developers site (Google: Nexus factory images). Then follow this guide http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html you'll be back up and running in no time my friend. If you want to thank me, just promise to never use a toolkit for nexus devices again except maybe to install the drivers... :thumbup:
Sent from my Nexus 7 using Tapatalk 4
dimebagdan65 said:
This is why you don't use toolkits... If you can get into bootloader mode, you're fine. Boot into the bootloader and hook it up to your PC. In a command prompt/terminal window type "fastboot devices". If it returns a string of numbers and letters you're all set. Just download the factory image from the Android developers site (Google: Nexus factory images). Then follow this guide http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html you'll be back up and running in no time my friend. If you want to thank me, just promise to never use a toolkit for nexus devices again except maybe to install the drivers... :thumbup:
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
bro thats what i did that got me into this mess... i downloaded the factory image abd followed to a tee.. it got stuck half way threw... now i have no os.. that is why i used the restore tool kit to try and fix it.. well i used the tool kit i just used a diff pc and it worked!!!! IM BACK !! thanks!!
Just for future reference sometimes things like toolkits require a fair amount of available ram. If the computer can't supply it, then the response is usually to freeze. Sometimes just rebooting can clear up enough memory.
prshosting.org

[Q] Can my N7(2013) still be saved?

Hi, my N7 is bricked and I wanted to fix it.
I tried to flash ROM but couldn't do it since my computer wont recognize my N7 (except in Recovery Mode-> Sideload).
I think it has something to do with the "developer options -> need to check USB Debugging", however, I can't do that since my phone when turned on, Google Logo appears, then afterwards, BLACK SCREEN (and now in a loop, but there is no X logo just plain black).
My phone is rooted & unlocked. Out of curiousity (My fault), I bricked my N7.
I've read a lot of article on how to unbrick my N7 and I think I now know how to do it- through Android SDK/ADB Tool. I've also read the a guide on how to change drivers (and tried it in all possible ways I can think of), and it did install the driver. However searching my N7 through ADB Tool doesn't go through.
adb devices
List of devices attached
(**nothing follows**)
But if I turn my N7 to Recovery Mode->apply update from adb:
will show the result:
adb devices
List of devices attached
**serial number** sideload
I don't know what other ways in order to unbrick my N7.
I hope you can help me with it.
You can enter bootloader, right? Then try to use fastboot to flash a new rom.
Use wugs program but tick tablet is in bootloop.
Can you boot a brick in to recovery mode? No...so you aren't bricked...
Thanks for the info man!
AnarchoXen said:
Can you boot a brick in to recovery mode? No...so you aren't bricked...
Click to expand...
Click to collapse
Hi, thanks for the info... I already solved my problem.. If only I have read your post earlier I could've saved xx hours in my research!! LOL
donb1 said:
Use wugs program but tick tablet is in bootloop.
Click to expand...
Click to collapse
I tried, but N7 isn't recognized by PC. So the main problem is really how to make my N7 recognized by PC (ADB/bootloader).
But problem fixed now. Thanks!
Calvin Gross said:
You can enter bootloader, right? Then try to use fastboot to flash a new rom.
Click to expand...
Click to collapse
Before I fixed my N7, this is what I tried. But the problem is, PC wont recognize/find my N7 when I do:
adb devices nor fastboot devices
But, I already fixed my problem. Thanks for the response! Greatly appreciate it!

Categories

Resources