Every since the root method came out, I've been trying to root my phone for hours and hours and I haven't been able to. Since this is a problem for quite a few other users, I figured we should have a thread just for this problem since the rooting thread is over 30 pages long at this point.
My problem is that I see the device in offline mode for a few seconds, and after that it displays an empty list again.
What I'd like to know from people who managed to root their phones, if they had to try something different from the instructions to get passed the adb loop step where you have to catch the device in offline mode? What OS are you running (Win, Mac, Linux and x86 or x64)? How many times did you try?
I got past the loop by hitting ctrl c as soon as it detected the device it worked for me. it seems if you let the loop continue and you get device not connected you have to try again. I was able to get this to work consistently twice.
Getting the adb portion of this is what took me the longest in the rooting process.
Had your same problem on Ubuntu
Had same problem on windows 7 64 bit
UNTIL:
installed pda net - then htc sync, then removed android device driver, then installed the (r3) driver from android sdk... the update you can download through their program.
After that it worked like a charm first time.
my best advice is to start running the loop just before you click recovery from the boot loader screen.
Once you got it, theres no need to be quick with control C - it stays there.
- Faylix / local
the PDANET program seems to mess with the offline loop thing.
Once I closed it, it goes through just fine..
The only problem im having is that im getting a E:Failid to verify whole-file signature when i push the update.zip
And also I've used both Windows 7 64bit and XP 32bit to no avail...
My guess is its all about the drivers. I must have mine all mixed up. I am stuck in loop with no device found either. I will try one more time with pdanet off but Ive tried on a pc without it too anyways.
Someone really needs to write an indepth guide like the G1 because drivers arent even meantioned in the guide and I know its a big part of it especially if you have had other android devices before with sdk plus adb. One thing I do notice is all of us with the loop issue have touble with the device showing in device manager. It displays android 1.0 instead of mts or adb whatever it supposed to be. If your device isnt recognized from hboot it wont make the proper jump into recovery. Hence the loop issue. Can anyone with root ellaborate this a bit more?
@jnight
You're very close. I had this happen to me too. What's happening to you is the first try failed but the update.zip still got pushed to the SD Card. Here's what you do:
1) adb push ota.zip /sdcard/update.zip
2) Type in "push update.zip /sdcard/" on your computer but don't push enter yet
3) Choose "install update.zip" in the phone. AS SOON AS the green bar appears behind the letters, press enter on your computer.
If you miss the timing and don't see clockwork recovery, you NEED to go back to my step 1("adb push ota.zip /sdcard/update.zip") or it will continue to fail no matter how many times you try because you HAVE to start with ota.zip as the update.zip on the SD card. The trick is getting the phone to verify the signature from the ota.zip and replacing it with update.zip to enter the clockwork recovery. Once you're in clockwork recovery, it's a breeze- just follow the rest of the stickied root tutorial. Hope this helped
shinkinrui said:
@jnight
You're very close. I had this happen to me too. What's happening to you is the first try failed but the update.zip still got pushed to the SD Card. Here's what you do:
1) adb push ota.zip /sdcard/update.zip
2) Type in "push update.zip /sdcard/" on your computer but don't push enter yet
3) Choose "install update.zip" in the phone. AS SOON AS the green bar appears behind the letters, press enter on your computer.
If you miss the timing and don't see clockwork recovery, you NEED to go back to my step 1("adb push ota.zip /sdcard/update.zip") or it will continue to fail no matter how many times you try because you HAVE to start with ota.zip as the update.zip on the SD card. The trick is getting the phone to verify the signature from the ota.zip and replacing it with update.zip to enter the clockwork recovery. Once you're in clockwork recovery, it's a breeze- just follow the rest of the stickied root tutorial. Hope this helped
Click to expand...
Click to collapse
You are a godsend. Spent the last two hours trying to time this just right by doing Step 2 and 3 over and over and over. 5 minutes after reading this post - Hello, Clockwork.
Lol
shinkinrui said:
@jnight
You're very close. I had this happen to me too. What's happening to you is the first try failed but the update.zip still got pushed to the SD Card. Here's what you do:
1) adb push ota.zip /sdcard/update.zip
2) Type in "push update.zip /sdcard/" on your computer but don't push enter yet
3) Choose "install update.zip" in the phone. AS SOON AS the green bar appears behind the letters, press enter on your computer.
If you miss the timing and don't see clockwork recovery, you NEED to go back to my step 1("adb push ota.zip /sdcard/update.zip") or it will continue to fail no matter how many times you try because you HAVE to start with ota.zip as the update.zip on the SD card. The trick is getting the phone to verify the signature from the ota.zip and replacing it with update.zip to enter the clockwork recovery. Once you're in clockwork recovery, it's a breeze- just follow the rest of the stickied root tutorial. Hope this helped
Click to expand...
Click to collapse
I was having some trouble to, I found something else that I was gonna add but it was only on my end... I didn't have the same problem rooting my wifes. I will watch this thread and if I see any more posts I will drop my piece. Im glad someone else could post this before I could.
shinkinrui said:
@jnight
You're very close. I had this happen to me too. What's happening to you is the first try failed but the update.zip still got pushed to the SD Card. Here's what you do:
1) adb push ota.zip /sdcard/update.zip
2) Type in "push update.zip /sdcard/" on your computer but don't push enter yet
3) Choose "install update.zip" in the phone. AS SOON AS the green bar appears behind the letters, press enter on your computer.
If you miss the timing and don't see clockwork recovery, you NEED to go back to my step 1("adb push ota.zip /sdcard/update.zip") or it will continue to fail no matter how many times you try because you HAVE to start with ota.zip as the update.zip on the SD card. The trick is getting the phone to verify the signature from the ota.zip and replacing it with update.zip to enter the clockwork recovery. Once you're in clockwork recovery, it's a breeze- just follow the rest of the stickied root tutorial. Hope this helped
Click to expand...
Click to collapse
Thanks Man, I guess I was pressing the Enter button to fast...
Got past eveything except the "SU" it says "Permission Denied"
NM about this post for some reason it started working after I installed "Setcpu". Went in to Terminal emulator and it gives me the # just fine..
For some reason its just ADB that gives Permission Denied..
"Step 18.
adb install Superuser.apk (If this looks like it works, but says it cannot locate directories, make sure you can find your device using adb devices… If things still don't work, my best advice is to start over)
Step 19.
After Superuser is installed try to use adb to shell to your device.
adb shell
you will get a $
Then type su
Superuser should pop-up asking if you give permission, do so.
Your $ should turn into a #. If so, you have root."
Make sure you run this or you wont get SU rights, this programs needs to be installed to allow the SU rights.
AngelsShadow said:
"Step 18.
adb install Superuser.apk (If this looks like it works, but says it cannot locate directories, make sure you can find your device using adb devices… If things still don't work, my best advice is to start over)
Step 19.
After Superuser is installed try to use adb to shell to your device.
adb shell
you will get a $
Then type su
Superuser should pop-up asking if you give permission, do so.
Your $ should turn into a #. If so, you have root."
Make sure you run this or you wont get SU rights, this programs needs to be installed to allow the SU rights.
Click to expand...
Click to collapse
Thank you thank you....
I've been repeating myself over and over regarding this...
It's the Number 1 issue why people can't Root & Flash to the ENGINEER Build!!
Still a no go
Marvin,
I am still getting the two device OFFLINE showing after going into recovery from hboot. I deleted ALL of the HTC SYNC software and drivers and ONLY installed PDAnet. I now can see the MY TOUCH SLIDE device when connected in hboot, unfortunately I still am having the same stupid problem. So since it's not showing android 1.0 anymore and still having the same problems, we might have to explore some other avenues. FOR THE LOVE OF ROOT SOMEONE PLEASE HELP US!!!
If you run loop and go to recovery and only see the device offline a couple times then it goes away, I do not think it is a driver issue at that point. As someone in the root thread explained, the loop is simply trying to catch the device in ADB mode as it's going into recovery. And then, randomly, it will "stick" in ADB mode. Now, I am not sure if there is a difference between our devices for those of us having trouble getting the ADB mode to stick.
Ok, I'm giving up. I have tried this hundreds and hundreds of times. I know I've followed the instructions the correct way (I've seen the video and read countless forum posts). This simply cannot be done on my phone. I am going to take it to the store and try to exchange it, perhaps for a black one.
Does anyone else have any suggestions?
as i posted in the other thread i was having problems trying to get adb "stick" open when i went from the bootloader into recovery so i went into the file explorer and right clicked on my computer then went to manage devices then went to the driver tab then clicked on update driver right before i went into recovery and this is what finally worked for me. the purpose wasnt to change the driver the purpose was to trick my computer into keeping adb open
Re: Getting passed the adb loop step
I had to hit power on phone and enter on pc at almost the same time to get it working. Then I realized that after you reboot, it boots back to your normal phone not recovery and then adb devices it shows up.
-------------------------------------
Sent via the XDA Tapatalk App
Re: Getting passed the adb loop step
Ugh none of these tricks have worked for me.. Still Stuck .. Maybe it's a computer issue.. Guess ill try a friends computer..
-------------------------------------
Sent via the XDA Tapatalk App
Maybe/hopefully someone will find a different/easier way to root these for those of us stuck here. I've also tried, exhausting many many things, everything from timing of hitting loop/recovery, all the way to almost completely breaking the ADB driver on my PC. This is thoroughly frustrating the hell out of me.
By the way, add "ECHO OFF" (without the quotes) to the top of the batch file. It makes it easier to see when it reads out the offline devices.
Re: Getting passed the adb loop step
If you go to settings then pc connection . What seeting should it be? Drive , sync, or charge?
-------------------------------------
Sent via the XDA Tapatalk App
Hmm this thing with adb is very annoying. I have constantly 2 adb.exe running in my task manager and a third adb.exe going on and off every 5 seconds or so, i think this is the problem that forces my adb not to work in cmd, always server time out and it kills the server during the commands, so i can never ever finish any commands i need to do with adb to push, pull files . Now i'm sitting with a bricked phone not able to push any update.zip file to my sdcard so i can't restore it at the moment..
Anyone has any solutions for my adb or any idea of why i have 2 adb,exe up and running in my task manager and the third jumping in and out like crazy?
Hello i had a similar problems in the past and i resolved this by closing every background program that was running on my pc! Anti-virus included and then retried ADB.
Hope this helps and good luck
Moved to general as not development.
Nope that didn't help.. As now my phone is bricked i wish to change the topic of this thread? anyone knows where or how to do that?
After i tried to install the new sense hd rom on my phone with a faulty adb program i'm stuck with a bricked phone and no idea of how to get it back to normal.
I can't use adb commands since the return answer from every commande is "ADB server didn't ACK .. and timed out is also something i get when i try to use any adb command.
I tried to copy a rom file over to the sd card named "update.zip" , i can't get into recovery and when the screen with the red triangle appears i hold vol+ and power button, and at that menu i try to use command 2 which states "apply update.zip"
but at that point i get the reply " signature verification failed installation aborted.
So now i don't have a clue of what to do to restore my phone to a working condition ?
PLEASE HELP ME!
I am running Linux Mint 15 on my compute and want to use adb for rooting/reflashing purposes. I downloaded and ran the script from: https://code.google.com/p/adb-fastboot-install/
I used it several weeks ago without any issues. In the instructions it says to rename a file and put it in the Android-tools folder, then change to that directory and then use: adb push filename.zip /sdcard/.
I used adb several weeks ago and don't remember putting the file anywhere special, simply changing to the directory it is in (android-tools)
or specifying the path of the file I wan't to push to the Android SD card. I looked and can't find any folders named "android-tools."
If I run the command adb devices (with the phone connected via USB) I see that the command runs and it finds the device. However, if I then do the command adb push PC36.zip to /sdcard I get an error stating: "cannot stat 'PC36IMG.zip No such file or directory."
What am I doing wrong???
Never Mind
Never mind!
It was getting late so instead of typing the command "adb reboot bootloader" I thought if I just copied and pasted it from the instructions I was using that I would would avoid typos due to being tired. However, I found the my problem was due to my instructions saying to use the command "ADB reboot bootloader."
I am Trying to flash the stock rom via side load i flashed that few days back to at that time it was flashed success fully but now it always gives me error
Code:
"C:\android-sdk\platform-tools>adb sideload OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip
loading: 'OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip'
* cannot read 'OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip' *
C:\android-sdk\platform-tools>adb sideload <OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip>
The syntax of the command is incorrect.
C:\android-sdk\platform-tools>"
Mine would not sideload either. I downloaded the zip file to my PC, connected the phone to the PC, put the phone in USB mode, dragged the zip file from the PC to the phone root directory, disconnected from the PC, and flashed the ROM from the phone hard drive.
Faulty ADB drivers I guess. If you have TWRP you can try adb push name /sdcard/
Puddi_Puddin said:
Faulty ADB drivers I guess.
Click to expand...
Click to collapse
Isn't obvious this is not a driver problem?! Read the error message that is staring him in the face. He has not specified the correct file/path.
bulletmark said:
Isn't obvious this is not a driver problem?! Read the error message that is staring him in the face. He has not specified the correct file/path.
Click to expand...
Click to collapse
Second one is a invalid command because of those <> first command mainly happenda with wrong drivers, I and many other get the error it is quite unexplainable.
Any resolution to this? I'm getting the same problem, saying it cannot read the zip file when I try to sideload
trying to update my wifes phone now. getting the same issue. i typed in adb devices and it shows up, so i know its not driver related. wonder if its a faulty image? ill keep trying
---------- Post added at 03:59 AM ---------- Previous post was at 03:55 AM ----------
funny i think i just foud the issue. someone posted saying older adbs cant see larger than 1gb (i have a opo so never even heard of this). ill give it a try and report back...
this is the adb ill be using https://forum.xda-developers.com/showthread.php?t=2317790
Okay, now that may work for others but I could not get it... Sorry
I ended up just removing the encryption, flashing twrp, and flashing OOS that way. Make sure to make a backup... I made a backup of everything... Except contacts because I thought gmail handled that like on my phone. I left my wife a note saying sorry for when she wakes up ha.
At least the annoying updates available message will be gone that we've had since Aug or something
I was getting the exact same errors and was frustrated to no end..... till I figured out how to fix it =)
I had to use this program on my adb.exe to make it large address aware
https://www.techpowerup.com/forums/threads/large-address-aware.112556/
Grab the laa_2_0_4.zip from the website, open and run as administrator
Click on select executable and go to where your adb.exe is installed, for me it was in C:\adb\adb.exe
Then make sure the checkbox on step 2 is selected and then hit save
I rebooted my PC and upon using the adb on reboot I was finally able to flash the stock OOS roms via adb sideload on my phone
Yipeee!!
shoemocker said:
I was getting the exact same errors and was frustrated to no end..... till I figured out how to fix it =)
I had to use this program on my adb.exe to make it large address aware
https://www.techpowerup.com/forums/threads/large-address-aware.112556/
Grab the laa_2_0_4.zip from the website, open and run as administrator
Click on select executable and go to where your adb.exe is installed, for me it was in C:\adb\adb.exe
Then make sure the checkbox on step 2 is selected and then hit save
I rebooted my PC and upon using the adb on reboot I was finally able to flash the stock OOS roms via adb sideload on my phone
Yipeee!!
Click to expand...
Click to collapse
I used the same tool
Hi everyone. I am experiencing problems trying to flash RR Nougat to my Oneplus 3, currently on CM13 6.0.1. It just won't flash at all. I've wiped cache etc but it doesn't want to execute. I've also tried Lineage OS but failed, I have even tried pushing the file via Unified Android Toolkit and even that didn't work. Phone has an unlocked boot-loader (I'm pretty sure) USB debugging, root access etc. Unsure what the issue is so any help would be appreciated. This is what happened whilst using UAT.
Working out the best location to set for Internal Storage..
Waiting for Adb Mode
Device mode detected [device adb]
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /sdcard/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
File push did not work for sdcard
Setting push location to mnt/sdcard and trying again
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /mnt/sdcard/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
File push did not work for mnt/sdcard
Setting push location to storage/emulated/0 and trying again
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /storage/emulated/0/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
An Error Occured
The file did not push to the set location for some reason
Please report this in your device thread with details for more help
Press any key to return to the Main Menu..
Thank You.
I don't really have an answer for you but recently I tried to go back to stock, after I locked my bootloader I was unable to sideload anything with adb, have you tried flashing it with TWRP? Just a suggestion, are you able to use recovery at all, if uat can't find the directory, it could be a PC issue? I'm just throwing out ideas to try to help.
Update your adb drivers, now command prompt can push files larger then several mb's, don't know precisely how much.
Same problem I had couple of weeks back, don't know why but mine adb driver changed, set it back to the Google adb driver from sdk and the file was sideloaded.
Make sure you are on the latest firmware that is required.
I would just transfer through mtp or download on your op3, then just flash trough TWRP. That's what I do.
sv2203 said:
Update your adb drivers, now command prompt can push files larger then several mb's, don't know precisely how much.
Same problem I had couple of weeks back, don't know why but mine adb driver changed, set it back to the Google adb driver from sdk and the file was sideloaded.
Click to expand...
Click to collapse
Yup follow his method. This issue is somekind of adb sideload bug for huge files, name too long or not run as admin. Restarting PC, reinstall driver OP3 driver is another option if problem still persists.