I hope this is the right place to post this. I have been trying to 2 hours now to get my phone to either work with Odin so I can factory reset but stuck on file analysis, so I decide to skip that and use some of the adb methods (Ultimate goal is to update to one of these new roms.) On ADB, my device manager shows ADB, but as soon as the script in CMD shows it rebooting ADB service, ADB disappears from device manager and my phone locks up. I have tried everything that I can think of and am pulling my hair out.
-On the Odin, I did verify that only those 2 items were checks and device shows. Please help and let me know if this posting is acceptable. Thanks in advance.
I am dying here and want to throw this m*fer against the wall. LOL... I really am tired and about to go to sleep I think. If anyone has any ideas, please let me know.
I forgot to mention that Odin sees my device. It always shows 0:[COM4] or some random number.
That's really odd. Do normal adb commands work for you (i.e. can you get into adb shell or can you do an adb push)?
richse said:
That's really odd. Do normal adb commands work for you (i.e. can you get into adb shell or can you do an adb push)?
Click to expand...
Click to collapse
Yeah, I can do initial ADB commands, but any script that says "reboot ADB shell" freezes my phone and then no ADB in dev manager and my phone is mostly frozen. I have already factory reset it to see if it was something I put on it, but no luck. I'm still messing with Odin and I can't get that to work either...... sucky.
billecorgan said:
Yeah, I can do initial ADB commands, but any script that says "reboot ADB shell" freezes my phone and then no ADB in dev manager and my phone is mostly frozen. I have already factory reset it to see if it was something I put on it, but no luck. I'm still messing with Odin and I can't get that to work either...... sucky.
Click to expand...
Click to collapse
how long did you give the script to reboot adb shell? One time it took like 10 minutes for no reason. I just let it sit and finally it worked.
Start from scratch. Load up adb (using the developer sdk) and type adb kill-server. Then adb devices (server should restart) and then try your adb commands again. Report back with success/problems.
Sent from my SPH-D700 using XDA App
Related
I'm on the stock JF6
and i have a build 1008 phone..
I can't seem to access download or recovery mode using the 3 buttons
anything I can do? My friend had flashed this random chinese I9000 ROM onto my captivate, so I flashed it back to stock using ODIN
recoverymode/download mode was fine on his ROM though
thoughts? cheers
and I can't return the phone as I live overseas!
Use ADB to get into download/recovery modes
And read the q&a sticky for more info and links.
Sent from my SAMSUNG-SGH-I897 using XDA App
avgjoegeek said:
Use ADB to get into download/recovery modes
And read the q&a sticky for more info and links.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
i'm using droid explorer
it has the same adb commands, but when I tell it to either reboot into recovery/download mode
it popups up on my PC screen and says are you sure, click "yes"
then nothing happens
or
it says "reboot operation not permitted"
bump
need urgent help pleaes
Do a search in the Development section for designgears' 3 button fix.
Hope that helps.
------
Axura 2.5CE
Samsung Galaxy S w/ AT&T
Mr.Pie[OCN] said:
i'm using droid explorer
it has the same adb commands, but when I tell it to either reboot into recovery/download mode
it popups up on my PC screen and says are you sure, click "yes"
then nothing happens
or
it says "reboot operation not permitted"
Click to expand...
Click to collapse
Learn to use the real ADB from the SDK.
Also, if your phone is not rooted, the reboot command does not work.
http://forum.xda-developers.com/showthread.php?t=812434
fixed
nvm
thanks all
do u know what i did was use a different usb cable dont use the one that comes with the phone. i used a different cable and download/recovery mode comes up. hope this helped
For those who need to know....
If you have a 1008 build (like me). Most of the time the buttons on the phone will not work. (Most meaning if your running certain custom ROMs the functionality returns until you go back to stock.)
I end up having to use ADB to reboot my phone into download or recovery in between flashing back to stock and going onto the new ROM because the buttons never work when I want them too, and it's become almost second nature to me
In order for ADB commands to work - you do NOT need your phone Rooted (otherwise I'd have been fubard a long time ago). You do need USB Debugging turned on or the commands won't work.
Also.. you only need Root/SU if you plan on using ADB shell commands and wish to play within the phone itself. Def not suggested for those who never have played with a shell before.
If you're going to be flashing different roms then next time you go back to stock use this one:
http://forum.xda-developers.com/showthread.php?t=818439
I've used it on my 1008 captivate probably 100 times so I know it works
avgjoegeek said:
In order for ADB commands to work - you do NOT need your phone Rooted (otherwise I'd have been fubard a long time ago). You do need USB Debugging turned on or the commands won't work.
Also.. you only need Root/SU if you plan on using ADB shell commands and wish to play within the phone itself. Def not suggested for those who never have played with a shell before.
Click to expand...
Click to collapse
Oops. I had totally forgotten that was for the shell on the phone cause thats how Ive been doing it lately when I flash. Thanks for correcting everyone
Sent from my Captivate
abhele said:
do u know what i did was use a different usb cable dont use the one that comes with the phone. i used a different cable and download/recovery mode comes up. hope this helped
Click to expand...
Click to collapse
Wrong the one that came with the phone will work for download mode everytime. it is the other 3rd party usb cords that do not work sometimes.
I have a 1008 batch phone and have never had a single problem flashing ROMs.
New that would get attention. Is there anyone out there that is dedicated to helping for a lil cabbage? I have this tf101 transformer that i cant seem to get rooted. Why is it so gosh dern hard to root one? I have followed all methods and tryed diff methods. The emulator runs but root is still not acheived. I have not bricked it. Its running ics. Ive rooted phones and tablets since the evo 4g..... this garbage a$$ tablet is without a doubt one of the worst i have ever had the displeasure of owning. Nexus 7,,,samsung note 1,,,note 2,,,,,,note 10.1,,,,,htc first,,,,evo 4g,,,,blackberry tour....AND NONE HAVE EVER BEEN THIS HARD TO ROOT. I wont buy another asus anything.
So,if som1 could explain what im doing wrong thatwould be great...also 20 buck in the paypal acct.....if you can think of it. Ive done it. Next is taking it apart to see what makes it tick
First thing - Does your tablet get seen by your PC in either APX or ADB mode? And did you update the driver using the Naked Drivers?
Last time I rooted I used Wolf's Method 3. Here is what I did:
Plugged in my tablet to my PC via USB (win 7 PC).
After the device was detected, I went to Settings - Developer Options - Debugging (tick the box).
It should install new hardware and show 2 devices, an MTP and an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: http://forum.xda-developers.com/showthread.php?t=1998650
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite recovery. I strongly recommend TWRP. The latest official release is here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save this at c:\adb\TWRP.blob. You can use a different recovery method if you have the blob file (such as CWM) but TWRP is far superior unless you are looking to install Android Revolution HD.
Next, run the following commands (from Wolf's Exploit, Method 3)
Code:
adb push TWRP.blob /sdcard/
adb shell
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p4 /data/local/tmp
adb reboot
exit
It will reboot. Once you see the ASUS loading screen, you can continue:
Code:
adb shell
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
Wait until you see it succesfully transfer data.
Then:
Code:
adb reboot
exit
Once it reboots, you should see a progress bar at the ASUS screen. Once this completes you will have TWRP (or some other custom recovery installed)
Now you can install your favorite SuperUser app.
Download a zip flashable SuperUser
ChainsDD SuperUser: http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
ClockWorkMod SuperUser: http://download.clockworkmod.com/superuser/superuser.zip
Chainfire SuperSU: http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip
I like the CWM SuperUser at the moment, but all three will work.
Put these where you can see them from the recovery you flashed. If using TWRP, it needs to be in the /sdcard/ directory or on the microSD card.
Next, reboot to recovery. Hold VOL DOWN and POWER for 12-15 seconds until you see some white text in the upper left of the screen. Release both buttons and tap VOL UP to enter RCK (Recovery).
Once in recovery, tap Install and choose the SuperUser.zip file to install. Once installed, you are rooted.
Another time I rooted, I used EasyFlasher and here is the thread on my rooting guide for that if you are interested: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
Once again, if you cannot get your tablet detected by ADB or APX, chances are it is a bad USB cable.
harley1rocker said:
-snip-
Click to expand...
Click to collapse
If you've 'tried everything', then it's likely Bad drivers or a bad USB cable, I'll assume you've tried my tool, the idcrisis tool, Easyflasher and wolf's method (Described by Fred) above.
If you'd like me to remote desktop you with Teamviewer to make sure your drivers are good I can do that, but if you've really tried everything then it's likely a bad cable.
ToD
To test the cable, simply transfer a file through USB with a known md5 signature, then verify it again after it's been transferred. You can use something like AFV to check the md5 once on the device. The bigger the file the better; the more chances it has to fail.
I GOT IT! holy crap! Ive gotta windows 7 comp. It turns out, it was the computer!. I completely wiped my laptop and started over. Still failed to flash recovery. I borrowed a friends computer and wah lah. Went into apx mode, got the new device found notification and installed the naked driver from device maneger. They finally took! This tablet is pretty old so I figure SBK1, nope, command wudnt run. No harm done. Went back and did SBK2 and FINALLY! Anyway, the first thing I do on any rooted device ready for a custom rom is do a nand back up. I kept gettin the "error path not known" or sumthin. This was on rogue. No offense to them, I never liked the lay out from the epic 4g touch days. So I loaded twrp. And now im able to do a back up.
And if I could not of gotten it, yes I would have let u remotely access my comp. It was the computer though. I trashed it and got me another this morning.
HUGE FREAKIN THANX TO ALL WHO RESPONDED. I still say this tablet is the toughest ive encountered by far. THANX FELLAS
harley1rocker said:
I GOT IT! holy crap! Ive gotta windows 7 comp. It turns out, it was the computer!. I completely wiped my laptop and started over. Still failed to flash recovery. I borrowed a friends computer and wah lah. Went into apx mode, got the new device found notification and installed the naked driver from device maneger. They finally took! This tablet is pretty old so I figure SBK1, nope, command wudnt run. No harm done. Went back and did SBK2 and FINALLY! Anyway, the first thing I do on any rooted device ready for a custom rom is do a nand back up. I kept gettin the "error path not known" or sumthin. This was on rogue. No offense to them, I never liked the lay out from the epic 4g touch days. So I loaded twrp. And now im able to do a back up.
And if I could not of gotten it, yes I would have let u remotely access my comp. It was the computer though. I trashed it and got me another this morning.
HUGE FREAKIN THANX TO ALL WHO RESPONDED. I still say this tablet is the toughest ive encountered by far. THANX FELLAS
Click to expand...
Click to collapse
Glad you got it sorted.
who got the 20 dollars
Sent from my Transformer TF101 using xda premium
stesteste said:
who got the 20 dollars
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Wasn't me. But I did not respond for the $20, I am just a good guy.
No one....yet. right after i posted that i got another comp. Installed naked drivers and wah lah. APX mode was recognized . But,if any1....fredreco. thanx for the info u posted.
harley1rocker said:
No one....yet. right after i posted that i got another comp. Installed naked drivers and wah lah. APX mode was recognized . But,if any1....fredreco. thanx for the info u posted.
Click to expand...
Click to collapse
We're all here to help, it really isn't about $, for me really it's just seeing that someone cares to donate that makes my day.. It's all about the passion of android though As fred will probably tell you.
I used ROM manager to add Cyanagenmod 9.1 to my tf101 - I had scoured the forums on how to but somehow missed the warning to not use ROM manager. Cold Booting to OS works but I have no wifi access and turning it on only results in an endless "turning on wifi" message.
Anyway like others I am getting the CWM bootloop but when I try to use the shell commands:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
I'm getting an access denied error from superuser...so no access there from terminal emulator
I've tried easyflasher, viperMOD, oneclick, naked drivers, ASUS, etc...nothing works. I can Cold boot to OS and view the tablet as a storage device and load .zip files to the internal memory but the current CWM does not see the SDcard.
One issue which someone said might be complicating things is that I don't have an OEM cord so that may be hampering my laptop (Win7 64b) seeing it in APK mode...
assistance por favor!
I bought a 5$ chinese cable and it works fine, but that doesn't mean yours doesn't.
What are the symptoms when you try to enter APX?
Can you access ADB through a computer?
Are you sure you su'ed to root in your terminal emulator?
Lethe6 said:
I bought a 5$ chinese cable and it works fine, but that doesn't mean yours doesn't.
What are the symptoms when you try to enter APX?
Can you access ADB through a computer?
Are you sure you su'ed to root in your terminal emulator?
Click to expand...
Click to collapse
I have a new cable coming. No recognition on the computer trying ADB.
Yes I tried su command on terminal emulator dozens of times and definitely got the "superuser has denied access to terminal emulator" message every time.
I'm hoping the brain trust here will clue me in on what I'm missing.
Sent from my SGH-I897 using xda app-developers app
The CWM version on my tf101 is 5.8.3.4
My tablet is a B70
Anything else that might help? I'm really bummed about this since cold booting to OS is rather useless since wifi is not working, superuser is denying access to any and all apps.
I think I have read nearly all the threads on this CWM bootloop and so far nothing seems to be working to flash and new recovery, stock ROM, new ROM etc...
Updated SDK and Java dev to try and run ADB but SDK only flashes a command screen for nanoseconds and closes. I've run in the past for other devices and it's worked fine but not this time.
gt_bike said:
The CWM version on my tf101 is 5.8.3.4
My tablet is a B70
Anything else that might help? I'm really bummed about this since cold booting to OS is rather useless since wifi is not working, superuser is denying access to any and all apps.
I think I have read nearly all the threads on this CWM bootloop and so far nothing seems to be working to flash and new recovery, stock ROM, new ROM etc...
Updated SDK and Java dev to try and run ADB but SDK only flashes a command screen for nanoseconds and closes. I've run in the past for other devices and it's worked fine but not this time.
Click to expand...
Click to collapse
Try to enter APX mode on another PC and plug it in check device manager for anything with yellow next to it and let me know.
So last night I tried to install CM11 and unfortunately forgot to make sure it was a clean install. Got stuck on boot animation and after remembering what I did wrong, tried to get back into recovery, however this is my first time trying to install CM on this device so was confused when the power button wasn't the "select" button to get me into recovery...so I ended up messing around for a bit and now I'm screwed.
My phone doesn't show up as a storage device on my computer and only recognises it as an "Android" device or "Fastboot Falcon S". I have tried reinstalling the Motorola drivers and I'm just at a loss. :crying:
I can access recovery on my phone but when I attempt to install a zip from sdcard it says "E: Can't mount /sdcard". Which means I can't install any Roms. I did some research and apparently I can push a stock rom to my phone, but this leads me to my next problem.
I can't seem to get adb to recognise my phone. I feel like I have tried everything but I have reached the extent of my knowledge on this matter and It's starting to hurt my brain. I saw mention of using "Eclipse" but when I try to run it I get an error message about Java.
Edit: When I say adb doesn't recognise my phone, it doesn't show up when I type the command "adb devices" and whenever I attempt an adb command such as "adb push" or "adb shell" I get an error message. I can however use all fastboot commands, which were a big help.
I honestly am completely and totally baffled on how to recover from this total f*ck up, so if any of you geniuses could help me save my device I would be forever grateful. I'm not sure what information I should supply you with as this is my first post. So please tell me what you need and I'll try me best to get you the info.
Thank you!
If you can boot into fastboot mode, just flash stock firmware of your region. There are many guides in the general and q/a sections. Just read them properly and remember to use mfastboot.
Sent from my Moto G using Tapatalk
You don't need adb, but mfastboot, which are two different things.
Let your brain rest few hours and then read the guides how to flash stock firmware.
You are fantastic. Thank you so much!
I can finally use it again.....and attempt to flash CM11 again, hopefully this time without screwing it up.
I owe you!
Hello Xda community, I open this thread after two days of reading and trying different ways to solve my problem.
My Nexus 5 runs Android 5.1.1 which I got OTA, I've never Rooted, installed any ROMS or done anything that might violate the system or the warranty.:angel:
Few days ago I downloaded some crappy program to my PC called Wondershare Dr.Fone (BURN IN HELL !!!) that was suppose to recover my deleted photoes from the Nexus, during the process of syncing etc.. it asked me to open developer settings and turn ON debugging mode.. which I did... and after about 30-40 minutes of "working" I realized it FROZE
The program didn't have any "Abort" button, and it was already late, so I just disconnected my Nexus, and after a moment it restarted and went into Bootloop
First I waited about an hour to realize it was infinite, then I tried going into Recovery Mode and deleting Cache Partition then restarting... it also didn't help, whenever I tried to turn it off, it was just turning on again, showing the Google Logo and then bashing those infinite Spinning Google Ballz in my face (I can turn off the phone using the Bootloader which works just fine, but it doesn't helps with the bootloop)...
The next whole day I was trying to at least recover my photos and videos, hoping that I can use the ADB to Pull the Camera folder out... I tried to install maaaany Google USB drivers following the steps of dozen tutorials, downloaded the SDK Manager and tried to install them thru Google server, and even Installed Naked Drivers with Windows 8.1 Signature Check Disabled... and tried it on 3 different PCs (win 8.1 and 7) the result was the same: Nexus 5 remained invisible until I Clicked in recovery mode "ADB Sideload.." in which case my Nexus 5 appeared in Device manager under Other Devices section (which let me install the drivers) otherwise it was invisible for my PCs...
The problem: whenever I was lunching the ADB from it's folder and typing "adb devices" I saw some sort of serial number, and "Sideload" next to it (while in other tutorials people have the word "Device" instead) and every command such as "adb usb" or "adb pull /sdcard/" or "adb pull /Camera/" result in "Error: closed" :crying:
In despair I tried to Factory reset my Nexus, and after about an hour of wiping, it allowed me to reboot which ended up in another infinite Bootloop....
I don't know what to do now, I don't live in the States and don't have warranty, I feel it's really unfair how after preserving my Nexus and it's Stock OS for so long... some Dr.fone bull**** broke it...
Please help me save my Nexus
Yea well... I knew nobody would give a crap in here... >.>
iJutsu said:
Yea well... I knew nobody would give a crap in here... >.>
Click to expand...
Click to collapse
[sarcasm]Way to stay positive.[/sarcasm]
You said you've tried doing a factory reset and that your system detects your device while in sideload mode on the stock recovery, correct? If so, have you at least tried sideloading the stock system update? Could be worth a shot at least.
Or with the driver issues, have you looked into opening device manager and see if it reads any kind of connection when hooked up not under sideload?
When adb is in sideload mode, you cant use any of the normal adb operations, like pull or push.
davehasninjas said:
You said you've tried doing a factory reset and that your system detects your device while in sideload mode on the stock recovery, correct? If so, have you at least tried sideloading the stock system update? Could be worth a shot at least.
Or with the driver issues, have you looked into opening device manager and see if it reads any kind of connection when hooked up not under sideload?
Click to expand...
Click to collapse
Factory reset didn't give any results, just destroyed any hope of recovering the photos I had onboard...
The system did detect my device for some time only when I activated the "ADB Sideload.." in the Recovery mode, but it wasn't same as in most guides and tutorials I've seen... When I typed the command "adb devices" it showed "4bd...serial.. Sideload", while according to tutorials it should be detected as "4bd.... Device"... Also I think the phone should get detected even without pushing the "Adb Sideload"... but the main problem is that every command results in "Error: Closed" so I can Pull or Push or Sideload anything since it's always same error"... which made me think perhaps the drivers aren't Okey, but I tried every Nexus 5/Google driver I could find, and I really doubt it's the drivers fault.
As I said the device remains invisible both in Device Manager and in Devices and Printers, until I click the Adb Sideload on the Nexus...
Factory Reset didn't work even tho I've never did any root or install Stock ROM or Kernel or anything of that sort, makes me wonder if that Dr.Fone crap app actually bricked my phone...
Thanks for trying to help
beekay201 said:
When adb is in sideload mode, you cant use any of the normal adb operations, like pull or push.
Click to expand...
Click to collapse
Aw... that's what I suspected... But activating the ADB sideload is the only way to make my Nexus 5 visible when I type "adb devices".... Does the fact that my PC can see it during ADB Sideload means that the Drivers are installed correctly? what may be the problem then? uff..
Have u tried this
Since you dont mind losing your data, I guess u already did a factory reset, I seriously suggest trying this guide. Read carefully. It worked perfectly for me which was in bootloop after 5.1.1 update.
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632