Related
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
Hello,
if is one here to help me i wil give him thousands bottles with beers.
My s3 is stuck in boot loop, i cant to pass samsung logo, i cant to go in cwm or download mode. I have tried to connect on my pc via usb cable but nothing is happening, i have all drivers installed but odin cant to recognized my phone, i think debugging mode is off. When the phone is off and i connect the charger he show me battery what he trying to get power but is not green.
I attach two photos to be more suggestive.
How can to pass this logo to go in cwm or to make this phone to be recognized by odin?
Thank you for reading me and for your answers.
regards,
florin
DobreaFlorin said:
Hello,
if is one here to help me i wil give him thousands bottles with beers.
My s3 is stuck in boot loop, i cant to pass samsung logo, i cant to go in cwm or download mode. I have tried to connect on my pc via usb cable but nothing is happening, i have all drivers installed but odin cant to recognized my phone, i think debugging mode is off. When the phone is off and i connect the charger he show me battery what he trying to get power but is not green.
I attach two photos to be more suggestive.
How can to pass this logo to go in cwm or to make this phone to be recognized by odin?
Thank you for reading me and for your answers.
regards,
florin
Click to expand...
Click to collapse
First question.. Do you have the I9300 (is the international version of the S3) Sprint version is SPH-L710.. If you have the 710 and flashed I9300 stuff.. you probably bricked your phone. If you DO have the I9300 version, I would pop over to that section of the forums and ask there... Here's the I9300 Section. http://forum.xda-developers.com/forumdisplay.php?f=1563
They are not compatible sadly due to different hardware, so flashing something from here will break your I9300.
Ive been where you are about three times. What i have had to do is plug my phone into the computer and have terminal or cmd prompt open.
I have to navigate to a folder that has ADB in it.
I start the bootloop on the phone and when i see the samsung logo boot up i execute the command
./adb reboot recovery
in windows i think you have to go
adb
reboot recovery
not sure though because i currently dont have a windows machine at my disposal. But you have to time this right. There is a few seconds in the bootloop where you have the ability to adb into the phone and force it to reboot into recovery this way you can flush the bad rom/kernel you accidentally flashed.
Hope this helps.
Thank you for your helpp, quick answers, you are the best form internet. All the time i get solve here in xda.
Solved, my battery it was under 25% and he cant to pass on download mode, i charged to 100% and now i can to flash what i want in download mode.
Thank you again for your quick answers.
Regards,
Florin
Hamspiced said:
Ive been where you are about three times. What i have had to do is plug my phone into the computer and have terminal or cmd prompt open.
I have to navigate to a folder that has ADB in it.
I start the bootloop on the phone and when i see the samsung logo boot up i execute the command
./adb reboot recovery
in windows i think you have to go
adb
reboot recovery
not sure though because i currently dont have a windows machine at my disposal. But you have to time this right. There is a few seconds in the bootloop where you have the ability to adb into the phone and force it to reboot into recovery this way you can flush the bad rom/kernel you accidentally flashed.
Hope this helps.
Click to expand...
Click to collapse
hello can you please be specific how to go in adb folder can you please assist with if some kind of tutorial is there I have the same problem and I havent slept from last two nights trying to solve it please help me
rishidgr8143 said:
hello can you please be specific how to go in adb folder can you please assist with if some kind of tutorial is there I have the same problem and I havent slept from last two nights trying to solve it please help me
Click to expand...
Click to collapse
What S3 do you have and exactly what is wrong with it?
Have a great day!
edfunkycold said:
What S3 do you have and exactly what is wrong with it?
Have a great day!
Click to expand...
Click to collapse
I have GT-I9305
i installed cm 10.2 few days ago
it restarted suddenly and keeps restarting again and again
I cant enter into recovery mode nor in download mode
I some how manage to enter into recovery mode it starts again and give no time wipe factory data same is with download mode
please help me
rishidgr8143 said:
I have GT-I9305
i installed cm 10.2 few days ago
it restarted suddenly and keeps restarting again and again
I cant enter into recovery mode nor in download mode
I some how manage to enter into recovery mode it starts again and give no time wipe factory data same is with download mode
please help me
Click to expand...
Click to collapse
Ok your in the wrong section, this is Sprint d2spr. So you should be posting in the forum for your device.
But most likely what you have is SDS sudden death syndrome. Which means your power button has failed. Very common on the S3 devices. Try jiggling the power button maybe blowing some compressed air into the power button area. See if it will dislodge. It is a known defect.
Have a great day!
edfunkycold said:
Ok your in the wrong section, this is Sprint d2spr. So you should be posting in the forum for your device.
But most likely what you have is SDS sudden death syndrome. Which means your power button has failed. Very common on the S3 devices. Try jiggling the power button maybe blowing some compressed air into the power button area. See if it will dislodge. It is a known defect.
Have a great day!
Click to expand...
Click to collapse
Thanks I will try doing that. I hope this works
Stuck at splash screen.
Help! I have a D2SPR and was flashing my nightly for 9/6/13 CM10.2... and now I can't get past the splash screen. What, if anything, can I do to get recovery to boot? (yes, it was a dirty flash(
Power button + volume up + home button at same time should get you into recovery.
Have a great day!
same issue
I have the Sprint SPH-L710 and flashed a Cyanogenmod nightly this morning. At this point, the phone will not boot. I can get to the Samsung screen but there it hangs. I can also get the phone connected to a computer and Odin sees it but I can't do much else with it. Any thoughts on how to force it into recovery from Odin? Any help would be much appreciated.
midkemiapug said:
I have the Sprint SPH-L710 and flashed a Cyanogenmod nightly this morning. At this point, the phone will not boot. I can get to the Samsung screen but there it hangs. I can also get the phone connected to a computer and Odin sees it but I can't do much else with it. Any thoughts on how to force it into recovery from Odin? Any help would be much appreciated.
Click to expand...
Click to collapse
I was able to get into recovery mode after flashing the CWM recovery mod from here: http://forum.xda-developers.com/showthread.php?t=2391616. I also took a look at the Cyanogenmod forum here: http://forum.cyanogenmod.com/topic/77958-20130906-stuck-on-boot-screen-dont-install/.
johnbistricky said:
Help! I have a D2SPR and was flashing my nightly for 9/6/13 CM10.2... and now I can't get past the splash screen. What, if anything, can I do to get recovery to boot? (yes, it was a dirty flash(
Click to expand...
Click to collapse
Pull battery then do the recovery button combo. It is a a known issue that that nightly doesn't boot. You could just dirty flash another nightly that does work. May break some things though.
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
@rishidgb
what ive had to do in the past to resolve these issues. Ill Copy/Paste the instructions i have used to Install ADB on my past computers but ill also throw links for the origionals at the bottom of the post.
1. Verify Battery is at least 50% charged. I usually do this by turning the phone off and plugging it into the charger, you should be able to see the battery charging up.
2. Install ADB on your computer. I have a mac, and this was kind of a pain in the ass to do at first but ill explain.
Mac-
1. Download the latest Android SDK from Google: Android SDK - http://developer.android.com/sdk/index.html
2. Extract the ZIP file to your desired location
3. To get ADB, you need to install the SDK: Installing the SDK - http://developer.android.com/sdk/installing/index.html
If you are not a developer and not planning to develop, then just download the following zip file containing only the ADB tool and
proceed with the tutorial: ADB - http://esausilva.com/wp-content/plu...silva.com/misc/android/platform-tools-osx.zip
Create an environment variable (Optional) **This is good because once you create the variable you dont have to navigate to the ADB folder every time to use it.
1. Open Terminal
2. Type cd ~ this will take you to your home directory
3. Type touch .profile this will create a hidden file named profile
4. Type open -e .profile this will open the file you just created in TextEdit
In the file, type export PATH=${PATH}:/pathToTheAndroidSdkFolder/android-sdk-mac_86/platform-tools
Save file, close TextEdit, Quit Terminal, and Relaunch Terminal
NOTE: By creating an environment variable you won’t need to cd to the Android/tools folder every time you want to run ADB
You are good to go, type in terminal adb devices, this should give you a serial number, which corresponds to your phone. Looks something like this:
List of devices attached
HT99PHF02521 device
NOTE: If you did not create an environment variable, then cd to the AndroidSDK/platform-tools folder, then type ./adb devices
Also make sure you have your phone plugged in and have USB Debugging turned on (Settings > Applications > Development)
In Android 4.2.x and up Developer Options is hidden, to make it visible, do the following
Tap seven times in Build Number: Settings > About Phone > Build Number
You will get a message saying you have enabled Developer Options or something like that, go back to Settings and you will see Developer Options in there.
PC-
Step 1: Head over to this link to download the latest version of Android SDK. http://developer.android.com/sdk/index.html
Step 2: Extract the contents of the downloaded file to your hard drive. Within the unzipped “sdk” folder, you’ll find another folder labeled ‘platform-tools’. Since we’re interested in only ADB and Fastboot, this is the one that we’re looking for.
Step 3: Move the platform-tools folder to a convenient location on your PC. The root of C: drive is usually a good idea. I also recommend renaming the folder to something easier, like C:\Android-adb.
By this point, ADB is essentially set up, but to use it, you’ll first need to navigate your command prompt window to this Android-adb folder, and then run all ADB commands inside it. Since it’s too much hassle for most users, we’ll add this location to Windows’ System Path Variable, so you can run ADB commands from anywhere.
Step 4: Right-click the Computer icon on your desktop, and go to Properties.
Step 5: Under System Properties, go to the Advanced tab, and click Environment Variables.
Step 6: The system variables are contained within the lower pane. Locate “Path” here, highlight it, and click the Edit button.
Step 7: There will already be a string of locations here; navigate to the very end, and add the following text (assuming that you have chosen C:\Android-adb as the folder; otherwise, enter whatever path you’ve located adb at):
;C:\Android-adb
Click OK, finally.
Your ADB folder is now configured, and you can run both ADB and Fastboot commands from anywhere in command prompt. To verify, connect your Android device to PC with USB Debugging enabled, launch a command prompt window, and type “adb devices” (without quotes). The daemon will start up, and all connected devices will be listed.
Mac Instructions
http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/
Pc Instructions
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Now that ADB is installed. If you find yourself in a Bootloop, OR you find yourself in a situation where it wont pass by the boot animation, open up terminal or command prompt. Then type Adb Devices, it should recognize your device and list the serial. And from there you can use the command:
Adb Reboot Recovery
From there you can wipe/Factory Restore and then Flash a new rom.
If you cannot reboot recovery but ADB still sees your phone. You can use command ADB shell to open a linux command prompt through your phone to push and pull files. Ive done this to push roms when the phone wouldnt mount properly.
I know this isnt "THAT" thorough, however ADB has litterally saved my ass a BUNCH of times. Id reccomend setting it up if you flash frequently.
Sorry it took me a couple days to respond, i am not on XDA as much as i used to be.
RE:
Thanks for documenting this.
So any solutions/ideas to people who can't get our computer's to recognize our device? Unfortunately, that's the position I'm in
So I got myself a S4, & planned to give my wife the Nexus,, But I screwed up and, wiped EVERYTHING. Now I can't get my computer to recognize my phone to side load or install a ROM through adb. I feel like its the drivers won't install correctly. I've tried 2 different computers and am at a loss. I need help.. it just keeps saying ( I think it says) "hardware not installed correctly" :crying: anybody?
ttocsm said:
So I got myself a S4, & planned to give my wife the Nexus,, But I screwed up and, wiped EVERYTHING. Now I can't get my computer to recognize my phone to side load or install a ROM through adb. I feel like its the drivers won't install correctly. I've tried 2 different computers and am at a loss. I need help.. it just keeps saying ( I think it says) "hardware not installed correctly" :crying: anybody?
Click to expand...
Click to collapse
I had a similar situation yesterday with a failed 4.4 install on my Gnex and this is what worked for me, YMMV.
I installed the Minimal ADB package from here on my PC.
"adb devices" from within the ADB window showed my Gnex.
I downloaded the CM 10.2 Rom and placed the zip on the root c: of my PC for the shortest path to remember.
"adb push c:\'rom name' space '/sdcard/download' " to push the zip file to my Gnex. This can take a few seconds depending on the size of the zip.
Boot in recovery and flash the ROM zip.
Here's a link to an ADB guide
TCStehle said:
I had a similar situation yesterday with a failed 4.4 install on my Gnex and this is what worked for me, YMMV.
I installed the Minimal ADB package from here on my PC.
"adb devices" from within the ADB window showed my Gnex.
I downloaded the CM 10.2 Rom and placed the zip on the root c: of my PC for the shortest path to remember.
"adb push c:\'rom name' space '/sdcard/download' " to push the zip file to my Gnex. This can take a few seconds depending on the size of the zip.
Boot in recovery and flash the ROM zip.
Here's a link to an ADB guide
Click to expand...
Click to collapse
Thanks for your reply,, but I think I have adb installed correctly, but not sure about the drivers??
**************************************** UPDATE !!!! *******************************************
HOT DAMN!!! I got it.. I used wugs toolkit and was finally able to get my computer to recognize my Nexus.. I was about ready to skip this thing across the lake. I better make a back up before I screw with it to much more..
OK here is the story
FireTV 51.1.0.2_user_510058520 2 days old
Rooted and installed busybox everything was fine. So I figured I wanted the latest Rootable version.
Followed this guide (http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ )
Problems started here: at the end trying to push update.zip to cache got error "cannot stat ‘update.zip’: no such file or directory"
update.zip was in same directory as adb
So I went and Installed Clockworkmod Recovery and pushed it using "adbfire" since it can push files to /sdcard (used this other guide http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/)
Went and rebooted into clockworkmod and that's when I saw the Previous command running trying to install update.zip wich was not there cuz I was never able to push it in the first place.
Well I could not get out of there by any means since I don't have a USB keyboard with me anymore
well I pushed the update.zip to /sdcard (again using adbfire) and used the mv command to transfer the file to /cache aaaaaaand reboot
Now I have my android logo updating the firmware and rebooting the FireTV when reaching the middle of the process just to start again and again
note: I can still connect to my firetv via adb while the screen is on and lose connection when reboots.
Any help would be greatly appreciated
Thanks in advance
LastDeuS said:
OK here is the story
FireTV 51.1.0.2_user_510058520 2 days old
Rooted and installed busybox everything was fine. So I figured I wanted the latest Rootable version.
Followed this guide (http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ )
Problems started here: at the end trying to push update.zip to cache got error "cannot stat ‘update.zip’: no such file or directory"
update.zip was in same directory as adb
So I went and Installed Clockworkmod Recovery and pushed it using "adbfire" since it can push files to /sdcard (used this other guide http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/)
Went and rebooted into clockworkmod and that's when I saw the Previous command running trying to install update.zip wich was not there cuz I was never able to push it in the first place.
Well I could not get out of there by any means since I don't have a USB keyboard with me anymore
well I pushed the update.zip to /sdcard (again using adbfire) and used the mv command to transfer the file to /cache aaaaaaand reboot
Now I have my android logo updating the firmware and rebooting the FireTV when reaching the middle of the process just to start again and again
note: I can still connect to my firetv via adb while the screen is on and lose connection when reboots.
Any help would be greatly appreciated
Thanks in advance
Click to expand...
Click to collapse
Well you can do
Code:
adb reboot recovery
to get to recovery, Then in one window run
Code:
adb shell
and in then run
Code:
/sbin/recovery-input
and then in another window run adb shell again and this time run killall recovery. Then you can use recovery-input to control recovery. I would recommend pushing one of the prerooted updates, flashing it, doing a factory reset, then reboot and it should be fine. Another option is to use adb sideload.
rbox said:
Well you can do
Code:
adb reboot recovery
to get to recovery, Then in one window run
Code:
adb shell
and in then run
Code:
/sbin/recovery-input
and then in another window run adb shell again and this time run killall recovery. Then you can use recovery-input to control recovery. I would recommend pushing one of the prerooted updates, flashing it, doing a factory reset, then reboot and it should be fine. Another option is to use adb sideload.
Click to expand...
Click to collapse
First thanks for your quick reply
the thing is my current state is Recovery looping while the firetv tries to install the new software so what I see is
Amazon logo
Android logo updating but just the blue bar filling
then shuts down
then android logo again and again
the commands you recommended were adb reboot recovery ----> /sbin/sh: not found
adb shell ---->/sbin/sh: not found
/sbin/recovery-input ----> Welcome to recovery input (this one works but I'm not quite where I need to be to control anything)
killall recovery ----> This command just reboots again into the same state
You also mentioned adb sideload but that's after I regain control of recovery right???
Please let me know other options to get out of this loop
Thanks again
LastDeuS said:
First thanks for your quick reply
the thing is my current state is Recovery looping while the firetv tries to install the new software so what I see is
Amazon logo
Android logo updating but just the blue bar filling
then shuts down
then android logo again and again
the commands you recommended were adb reboot recovery ----> /sbin/sh: not found
adb shell ---->/sbin/sh: not found
/sbin/recovery-input ----> Welcome to recovery input (this one works but I'm not quite where I need to be to control anything)
killall recovery ----> This command just reboots again into the same state
You also mentioned adb sideload but that's after I regain control of recovery right???
Please let me know other options to get out of this loop
Thanks again
Click to expand...
Click to collapse
If recovery is still in some kind of a loop, doing rm /cache/recovery/* while in adb shell should clear that up.
rbox said:
If recovery is still in some kind of a loop, doing rm /cache/recovery/* while in adb shell should clear that up.
Click to expand...
Click to collapse
I tried rm /cache/recovery/* and I think it erases that folder cuz when trying to run same command again it states as no such file or directory but then I wait and reboots again into same loop
again ran killall recovery and nothing reboot again looping T_T
LastDeuS said:
I tried rm /cache/recovery/* and I think it erases that folder cuz when trying to run same command again it states as no such file or directory but then I wait and reboots again into same loop
again ran killall recovery and nothing reboot again looping T_T
Click to expand...
Click to collapse
I dunno. Recovery shouldn't be doing any looping... With an empty /cache/recovery it should just sit there and do nothing. And it makes it more difficult without a usb keyboard.
rbox said:
I dunno. Recovery shouldn't be doing any looping... With an empty /cache/recovery it should just sit there and do nothing. And it makes it more difficult without a usb keyboard.
Click to expand...
Click to collapse
I can bring a keyboard from work tomorrow if that would help us troubleshoot cuz right now my keyboard is wireless
I know I've been asking a lot this last hour but can you please point me in the right direction so tomorrow I can Try something else using an usb keyboard?
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset Cache
Reboot
or
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset to factory defaults
Reboot
roligov said:
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset Cache
Reboot
or
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset to factory defaults
Reboot
Click to expand...
Click to collapse
Well yesterday I couldn't bring the keyboard but now I have it in front of me but I haven't been able to reproduce the recovery mode with the keyboard combination.
I know it works because the firetv reboots but sometimes goes to the initial amazon logo and sometimes just the same updating android logo
So any suggestions now that we have the keyboard here???
OK I finally figured it out.
All started when I ran the command "echo --update_package=/cache/update.zip > command" to update to a stock ROM but was never able to PUSH the actual file... kept getting error "cannot stat ‘update.zip’: no such file or directory"
THEN
I successfully installed Clockworkmod Recovery (luckily) and when rebooted to recovery I was presented with Clockwmod Recovery asking if sure to install the NON PRESENT "rom.zip"
BUT i didn't have a keyboard with me at that moment and didn't know the "control recovery" command either... SO I thought to find a different way to PUSH the file....
So I used push file function in adbfire to get the file into /sdcard/ and the the mv command to get it to /cache
SO I got my problem right there wich I was able to reproduce today: When you connect to adb during recovery or booting the FireTV you will get this error for most commands including su ----> "/sbin/sh: not found"
NOW if you try to push a file it will say it got pushed but only half of it or some shortcut of it I'm not sure
The thing is with that half pushed file the system now obeys "echo --update_package=/cache/update.zip > command" and starts updating and shuts down reboots and update again, whatever you do it keeps on booting again to the same state(trust me nothing works)
What I did basically with the few seconds I got between reboots I ran "rm -f /cache/*.bin" and rm -f /cache/*.zip to erase all cache folder and then I was again asked to install the file (not there again) and disabled recovery flash
Anyways thanks for all the replys I got really appreciated all your help and keep up the good work ppl I hope this helps someone out there besides me.
I'm now running the latest prerooted rom from rbox thanks again for that
have a good one
question: Is there an actual gui windows app to transfer files to FireTV???
2: Do I need to block updates for this custom rom also or that's already implemented?
The pre-rooted ROM blocks updates. You can check using TiBU. I think three files are frozen.
Glad you pulled out of your crash.
schneid said:
The pre-rooted ROM blocks updates. You can check using TiBU. I think three files are frozen.
Glad you pulled out of your crash.
Click to expand...
Click to collapse
It doesn't. But if you had dcp blocked before installing it, it'll remain blocked. You should always have dcp blocked.
rbox said:
It doesn't. But if you had dcp blocked before installing it, it'll remain blocked. You should always have dcp blocked.
Click to expand...
Click to collapse
TiBU shows mine "frozen". Did I do that previously with something else?
schneid said:
TiBU shows mine "frozen". Did I do that previously with something else?
Click to expand...
Click to collapse
Either you froze it with titanium previously or you did the pm disable command.
rbox said:
Either you froze it with titanium previously or you did the pm disable command.
Click to expand...
Click to collapse
I did do the PM disable thing but thought your rooted ROM would undo it. Guess not. Anyway, I'm happy. Thanks.
Think I bricked mine
Just got my firetv and did the usual ie. rooted, su added , then I Installed Clockworkmod Recovery and tried to upgrade to the latest rootable firmware, using update.zip to /cache and then it just keeps rebooting.
No amazon screen, goes to Andriod loads 1/3 of the way andf reboots, over and over.
picture attached
Cant adb to it , when doing the alt+print screen+i with my keyboard just reboots it faster
Think i'm offically bricked and its a bummer , be careful when changing firmware with CWR and sending your update.zip .
I dont know where it went wrong but it did
Note3usr said:
Just got my firetv and did the usual ie. rooted, su added , then I Installed Clockworkmod Recovery and tried to upgrade to the latest rootable firmware, using update.zip to /cache and then it just keeps rebooting.
No amazon screen, goes to Andriod loads 1/3 of the way andf reboots, over and over.
picture attached
Cant adb to it , when doing the alt+print screen+i with my keyboard just reboots it faster
Think i'm offically bricked and its a bummer , be careful when changing firmware with CWR and sending your update.zip .
I dont know where it went wrong but it did
Click to expand...
Click to collapse
Don't use update.zip and don't put it in /cache. Since so many people seem to be screwing up by doing that, I'm going to disable the automatic flashing in the next version. As for not being able to adb to it, it's probably using a different ip than what you are expecting. In every instance of people doing this, adb has always worked. Then just rm whatever you put in /cache. Next time use sideload or put it in /sdcard.
rbox said:
Don't use update.zip and don't put it in /cache. Since so many people seem to be screwing up by doing that, I'm going to disable the automatic flashing in the next version. As for not being able to adb to it, it's probably using a different ip than what you are expecting. In every instance of people doing this, adb has always worked. Then just rm whatever you put in /cache. Next time use sideload or put it in /sdcard.
Click to expand...
Click to collapse
I send the update.zip to the ftv with Amazon FireTV Utility App and it looked like it went all the way through , by default isnt that where it send it to ? /cache
Ive been trying to ping the ip , or shell to it but how much times could I have when it just keeps cycling. I dont think its possible to adb to it at this point as I get the attached screen for like 10 seconds or something it will just hold at the all white amazon logo if i'm screwing around with the keyboard combantions , i'm just stuck at this point and dont wanna keep burning hours if i cant go further.
I'm assuming its trying to load whatever is in the /cache folder which is either nothing or ave an update.zip file no idea
thanks for the reply as i will try some more to adb in
I am in a similar boat. I tried to install "rom.zip" per the instructions here http://www.aftvnews.com/how-to-install-a-custom-rom-image-on-the-amazon-fire-tv/
but it would not install it from CWM. It would abort the installation instantly. I read another thread where someone wasn't able to do something through ADB Shell because of SU permissions. I tried to uninstalled it and sideloaded SuperSU again. When I accessed it instead of clicking on "Normal" I chose the other option. Well, it's not stuck in the same loop as mentioned here.
I see the Amazon logo briefly, then it shows the android logo and reboots. It disconnects for a few seconds with the TV saying there is no HDMI connection and then shows the amazon logo shortly after again. I can no longer ADB into it.
Please help.
Note3usr said:
I send the update.zip to the ftv with Amazon FireTV Utility App and it looked like it went all the way through , by default isnt that where it send it to ? /cache
Ive been trying to ping the ip , or shell to it but how much times could I have when it just keeps cycling. I dont think its possible to adb to it at this point as I get the attached screen for like 10 seconds or something it will just hold at the all white amazon logo if i'm screwing around with the keyboard combantions , i'm just stuck at this point and dont wanna keep burning hours if i cant go further.
I'm assuming its trying to load whatever is in the /cache folder which is either nothing or ave an update.zip file no idea
thanks for the reply as i will try some more to adb in
Click to expand...
Click to collapse
Hey your problem is really similar to mine and what I did was connect to adb in between the loops and erase all cache
try searching on your router or do a scan on your network and find the correct ip address for the firetv
also don't worry about not being able to SU just erase cache using "rm -f /cache/*.bin" and "rm -f /cache/*.zip"
then it will ask for the actual file and just choose "not to install" then "disable recovery flash"
pd: Don't try to enter recovery by keyboard combinations it's useless trust me I tried A LOT
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