Related
This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
First go here and download the RUU:
http://www.pcdphones.com/downloads/Eris%20MR1.zip
Next you need to go to verizon's website and login to your account. Click "Suspend/Resume Service" and suspend your phone. You can resume service on the phone after you are done here with no penalties or charges.
Please follow these directions, taken from the first root thread
bftb0 said:
Steps:
[Binny knows this, but if anyone else is reading, it is the same as a factory reset - you will lose all your settings and apps (but not the contents of the SD card)]
1) Unpack the 1.16.605 RUU - by running it as if you were going to actually do the RUU using the USB cable and your host PC, but stop right before you would apply the update to the phone. Pull the "rom.zip" file out of the temporary area that the RUU installer unpacks.
(Poke around under C:\Documents and Settings\<Username>\??? (I can't remember - you'll see folders with names that look like registry entries). You have to do this while the RUU installer is sitting there waiting for you - if you cancel the install, it will nuke everything it unpacked. I just made copies of the entire subtrees.
2) Cancel the RUU install.
3) Move the ROM.ZIP file to the root folder of your SD card, and rename it PB00IMG.ZIP
4) You can cancel the RUU install session on the PC, and unplug the USB cable if you want (so long as you have a well-charged battery!)
3) Power down the phone, and boot it back up holding the Call and End buttons simultaneously
4) Scroll down (or whatever it asks) to go from Fastboot mode to HBOOT mode
5) The phone will automatically discover the PB00IMG.ZIP file, and unpack it and verify it.
6) It will ask you if you want to install; when you (select and) enter Yes, the phone will reboot, and come up again - appearing as if it is repeating the same thing. This time, however, it won't stop and ask you - it will just begin the install.
7) Wait... Wait... Wait... Wait... and then wait some more. If I recall correctly, it seems to hang a little bit at the HTC splash screen after the reboot. That is normal - just WAIT and let the phone do it's thing.
That's it, except for:
8) You probably will want to dial *228 and choose option 1 to complete the programming of your phone - it will reboot after it completes.
Click to expand...
Click to collapse
After you are done, DO NOT start the OTA update that it prompts you to do.
Now we are going to install wireshark and setup the capture environment:
Download wireshark from http://www.wireshark.org/download.html for your versions of windows
Install it - make sure you also install WinPcap
At this point you should turn off any wireless encryption on your router. I know it's not necessary but it makes it easier to go through the captures.
Setup the wireless on your phone to connect to your wireless router and turn off your mobile data connection.
After you have turned off the wireless security on your router, we are going to start the wireshark capture.
Run wireshark - if you are on vista or windows 7 make sure to run it as an administrator
Click "Capture" then "Interfaces"
Click "options" next to the interface that your computer has an IP for
Make sure to check "Capture packets in promiscuous mode"
In the Capture Filter box, type "host <ip_address>" where <ip_address> is the ip address your router gave your phone
Make sure that "Automatic scrolling in live capture" is checked so you can ensure the capture is working
Click "Start"
At this point, you should browse the web with your phone. You should see lots of stuff scrolling by in the wireshark window.
If there isn't, you messed up something above and should try again.
If there is a lot of stuff scrolling by, continue:
Close the browser
In wireshark, click "Capture" then "Restart"
Reboot your phone
On your phone, go to "Settings" -> "About Phone" -> "Check for Updates" and go through with the OTA update
After the update is done and your phone is rebooted, go to wireshark and click "Capture" -> "Stop"
Then click "File" -> "Save As" and give it a name.
Upload that file to Megaupload, or Mediafire, or some other file sharing site, or any private server that I can get access to.
After you have uploaded the file please message me through the forums with a link to the file.
Thanks a ton.
e-mail me at [email protected] i got my wifes phones todo this to shes still on 1.5
NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.
Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip
FireSokar said:
NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.
Click to expand...
Click to collapse
You CANNOT downgrade from 2.1 to 1.5.
Videofolife13 said:
Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip
Click to expand...
Click to collapse
We don't need the location of the update file, we need all the extra network traffic that surrounds the OTA process.
Ah. My bad.
We need to know, exactly, how the update process works.
I'm currently working on downgrading 2.1. Will post back a tut if i get it working
Can't we create an AVD to run with a custom rom and use the Eris MR1 ROM to do it?
Scratch that. I don't think AVDs will get OTAs.
zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Sadly I tried this a while ago when messing around with AVD Skins but wasn't able to figure it out. If anyone can figure it out please let me know how you do it! -_-"
zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Wait can't you set it to wireless only mode and get the OTA through wireless? (Simulated by your network connection)
nindoja said:
This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
...
Thanks a ton.
Click to expand...
Click to collapse
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0
Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.
FYI,
When you roll back to MR1, the phone seems to have already grabbed and downloaded the OTA update... in less time than it takes to hand-configure the phone. If you want to observe the OTA process via wireless, you need to prevent the phone from having Mobile network access, since that comes up by default after a FR or MRx rom burn.
Here's a long shot. Perform the MR1 rollback inside a cell dead zone, and conduct a MIM attack by setting up a server on the wireless net so the phone downloads a different OTA zip. You control DHCP for WiFi, so you also in principle control the DNS and routing the phone sees via WiFi. In principle, it's not possible because https should prevent Man-In-the-Middle... but if that (Google) server isn't correctly configured, maybe the phone is not really being too careful about certificate problems. (Either that or the Google server is tuning its' responses based on UA strings).
bftb0
bftb0 said:
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0
Click to expand...
Click to collapse
bftb06: could you please PM me? I am going to trade my phone this week if you understand what I am getting at.
nindoja said:
Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.
Click to expand...
Click to collapse
Sorry, my bad. I didn't read carefully enough.
I could probably attempt what you are asking for - I am quite familiar with wireshark (and even hardware sniffing of WiFi, so long as you have the right nic), but the fact that the phone seems to go and look for updates immediately after a FR or MRx update means that the "check for updates" thing may not do anything useful for you if there is already an update on the phone waiting to be installed by the time you start pressing menu buttons. (Thus the idea about "do MR1 in a cell dead zone")
Beyond that, there is a possibility that the update app does not do a wildcard host bind() when it sets up the socket when it inquires about updates with the Verizon servers - for instance, MMS service works exactly that way (it will only use the mobile network interface), and precisely so because of security considerations. Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0
bftb0 said:
Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0
Click to expand...
Click to collapse
You can force updates to occur over WiFi if the mobile network is turned off. Do you think this would work:
1. on 1.17 do a factory reset but do not activate the phone.
2. Initiate the downgrade process
2a. while downgrading, turn on packet capture
3. When the phone boots back up and wants you to call a number to activate, hang up
I think if you can skip the activation the phone will not have a mobile data connection, which would allow you to turn on wifi and initiate the update process.
Im still on 1.5 PM me and ill help if needed
Do you guys still need this?
TGA_Gunnman created a one click root that new users will want to use, said thread is a sticky in Captivate Development. If you still want to use the old method (and install ADB) please use this one.
I followed my own guide! This works perfectly if you read everything and follow the instructions.
Also: once you are rooted, be EXTREMELY careful! Half of the new threads are people who have screwed up their phones by deleting this or corrupting that. Please, for the sanity of all of the devs and Android veterans, make backups and just be all around careful. Almost all problems that anyone has had are repareable AND PREVENTABLE with a little reading and care. Just to clarify, rooting does not automatically enable sideloading. Please follow http://forum.xda-developers.com/showthread.php?t=738376 to enable sideloading.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way. Your warranty is also void, but you could have figured that out for yourself.
Now that that's over with, lets get to the fun bit. If you are on Windows, you can follow this procedure, or for TGA_Gunnman's one click root program (only on Windows), you can go ahead and skip to the bottom.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/s...iver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. (If you are on a Mac, DO NOT USE SAFARI to download the file, it automatically unzips any zip file. Use Google Chrome or firefox instead.) Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) EDIT--There is an easier way to get to recovery, but do this step anyway. Turn the phone off, then hold power, volume up and volume down. If you still want the android SDK (which will be very useful throughout your rooted experiences) follow the old procedure:
This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
Click to expand...
Click to collapse
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Can we please have more detailed instructions? I don't understand the part where it says "type in the terminal"
I am very new to android as this will be my first Android phone.
Also, after rooting will we be able to install 3rd party applications? Or do we have to do anything else to bypass ATT's restrictions?
adb terminal is software you need to install on your PC , will probably need samsung drivers also , guide is indeed not noob friendly. This will help you get needed bits including ADB
Probably None of us have captivate , so writing a guide is a bit troublesome
Ditto, a guide to the adb terminal please! I will acquire this phone, this Sunday.
Actually, you'd have to install a custom ROM for that. MoDaCo should be coming out with them pretty soon, and so will XDA. It won't be too long. BTW, once you have ADB installed on your computer, you can sideload apps all you want. The command is
Code:
adb install /directory/of/app/on/computer
point me to some functioning samsung drivers and I can do this!
If you cant get it to work on windows, try a ubuntu live cd. All you need to do is go to ubuntu and burn a disc and reboot.
Are there no Windows 64 bit drivers?
Edit- I found some that work. I think. Haven't tried it (yet).
http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Edit 2- Just did the root. Seems to have worked (no errors) but how do I know if it did? How do I delete say, ATT Maps?
Thanks for this. I am new to smartphones and plan on purchasing the Samsung Galaxy-S, but don't want to mess it up. I am new to editing the OS of any smartphone, but I think if I have a tutorial I will be fine
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
NOSintake said:
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
Click to expand...
Click to collapse
if you are in the directory above yes. the ./ just saves you from writing out the full path
lets say adb is in "/home/user/Downloads/sdk/tools"
you could type out "/home/user/Downloads/sdk/tools/adb command" regardless of where your terminal window was focused
or if you were currently in the directory "/home/user/Downloads/sdk/tools"
you could use the shortcut "./adb command"
OP I'd change your post based on my experiences... Here's a little more detail and I've rearranged it (you need the drivers before running these commands, for example).
blackjackboy said:
Please let me know if this rooting method works as I have no Captivate to test on. I'm not taking any credit for any of these files, LeshaK made the original file to root the European Galaxy S, Justadude modified it for the T-Mobile Vibrant and chaoscentral edited the file for use on the Captivate.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way.
Now that that's over with, lets get to the fun bit.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
Thank you to LeshaK, Justadude, and chaoscentral. Once again, I didn't discover how to root, that credit goes to LeshaK, bringing it over to the USA was Justadude's doing, and chaoscentral edited the file for use on our Captivates.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Click to expand...
Click to collapse
Ubuntu 10.04 - adb
Any step by step instructions just to get adb running enough on 10.04 to root and side load software? I'm getting command not found when I try to run adb, even after downloading packages.
Hi,
Did this thread worked well to Root the Captivate or anyother suggested link? I'll appreciate any help.
Thanks
rerooting captivate
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Thanks for the answer & More Queston
cellgeek said:
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Click to expand...
Click to collapse
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Muhamadabdelaall said:
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Click to expand...
Click to collapse
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Thanks Drachen
Drachen said:
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Click to expand...
Click to collapse
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Muhamadabdelaall said:
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Click to expand...
Click to collapse
The ATT stuff doesn't actually run so they aren't a big deal at this point. I also don't see Amazon MP3 background stuff like some Android devices have, so... There's really not a huge case for rooting yet.
That said, when Custom ROMs for this come out I'll still be getting one.
For those of you having a hard time installing ADB Shell, try this video. It worked for me.
http://www.youtube.com/watch?v=YeWH6Bj1DYw&feature=related
Cant figure out for the life of me how to reroot after doing the 340 ota. I came from 2.2 ota.
I tried z4root multiple times, no dice.
Tried the DoRoot Automatic script. Didnt fully work.
Tried the manual method on the phone with term emu.
Tried the manual method...and im getting stuck here...
Factory Reset and did it all AGAIN... So annoyed
Mod note from Sleuth
Wispirer figured this out further down in the thread. It has to do with different versions of the superuser apk file confusing z4root. His post is here
nicely done btw
end mod note
[*] Searching for adb ...
[+] Found adb as PID 6025[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] [email protected] so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
$
C:\Users\matt\Desktop\android-sdk-windows\platform-tools>adb kill-server
C:\Users\matt\Desktop\android-sdk-windows\platform-tools>adb.exe devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015A9D7E1303301A device
C:\Users\matt\Desktop\android-sdk-windows\platform-tools>adb shell
$ mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: Operation not permitted
$
z4root sat for 5-10 minutes on "running exploit" when I ran it. Others have also reported this.
I experiened that ONCE too, but i pulled the battery after a few minutes since it went through the full process so many times before.
anyone any ideas?
same problem here...can't get root back yet
Just to make sure, when you guys are rooting you have USB debugging on, yeah?
Also, does 1click root work? Several DX flavors. Check the Wiki. Link in DX android development.
Some questions:
What precisely happens when you try to use z4root? Give me the step by step.
Can you get temporary root with z4?
Sleuth255 said:
Also, does 1click root work? Several DX flavors. Check the Wiki. Link in DX android development.
Some questions:
What precisely happens when you try to use z4root? Give me the step by step.
Can you get temporary root with z4?
Click to expand...
Click to collapse
It goes through the whole process, says its rooting, getting shell, etc, goes white for a second, says rebooting, come back up and no root. And nope, tried both options.
Same here. The main thread about the update says it can take as many as 10 tires. I'm on about #5. we'll see.
That doesnt quite make any sense to me....
Same thing is happening to me, z4root says using exploit, acquiring root shell, goes to white screen then goes back and says rebooting. After it reboots still no root.
Tried 1 click method and it hangs at performing the rage command. Manually tried rooting and after applying the ./rage it kicks me off like its supposed to then says my device isn't found when I do adb devices command.
Yup, Same. I even factory reset twice.
Interesting. I have both copies of the update.zip. I did notice that they were slightly different in size. I used the very first one that was posted. I'm gonna do a quick hex compare to see if they're the same...
edit: uh oh, the two update files are totally different. The original one is slightly larger and HexCMP finds no similarities after the first 1K or so. The one I used had a size of 26,358. The other, more recent one has a size of 26,259.
So whats that mean exactly? Two versions of OTA were pushed out? One rootable and one not?
It sure looks like there's two different sizes and a hex compare shows significant differences. Take a look at your update.zip. What is the precise size? If everybody who can't root has a size of 26,259 then the validity of your thought is supported.
Remember, the original update only went out to a special beta test group and then was quickly pulled. The one I used was that update.
Where do i find the update.zip file? I did the ota update
Review the Droid X 2.3.340 Update thread in this forum. Good history about this update there including the information you seek.
I tried to root with Sil3ntK1ll Root X 2.2 and it looked like it was taking until about 3/4 of the way it said waiting for device. I left it for 5 min and it was then locked up solid. I had to pull the battery and reboot. No ill effects after the reboot but I am not rooted.
So I assume the root authors are already hard at work on fixing this issue?
same story as everyone else, had root, did update, cant get it back
Found this method, hxxp://forum.androidcentral.com/motorola-droid-2/40283-how-root-droid-2-without-computer.html (note: change x's to t's) and lo and behold it worked! Did from top to bottom and now back to being rooted. Hopefully this method works for you guys.
SBF flash for Cellular South MB809 - Milestone X
Android 2.2.2
SHADO_X6_3.2.6_SHADOW_BP_C_02.06.00R_AP_BP_Flex_21_signed_secure_cell_south_1ff_P3_USERBLD.sbf.gz
http://www.filesonic.com/file/13015...igned_secure_cell_south_1ff_P3_USERBLD.sbf.gz
Compression MD5 - D5391DA5535ACBB1B381E300240FEFA5
SBF MD5 - A40CCF0B7B8C11BFC7F73743D2F7D7AE
Awesome man, thanks!
Sent from my MilestoneX using XDA Premium App
Not working for me. I'm getting getting device not compatible error.
Thanks brother
The Best Firmware Team
I still can't get this to work. Can someone please help?
Sent from my DROIDX using XDA App
bigballa39213 said:
I still can't get this to work. Can someone please help?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
you have a verizon droid x. this sbf file is for Cellular South Milestone X. It runs a check to make sure you have the proper hardware before flashing.
Im sure its the same phone.
Sent from my DROIDX using XDA App
In this post here, you say you have a verizon droid x.
http://forum.xda-developers.com/showpost.php?p=14829484&postcount=21
Thats why it wont work.
I thought it was the same phone just different software.
Sent from my DROIDX using XDA App
I found the sbf for cs online but I still don't have data.
rummelball88 said:
I found the sbf for cs online but I still don't have data.
Click to expand...
Click to collapse
Have you tried "*228"? I had that problem after an OTA upgrade to gb.
Have found SBF, but am getting "Critical Errors 1337 & 510B"
The tale...
* Had Milestone X rooted using one of several methods readily available for download.
** Overzealously updated using the OTA about two weeks ago from Motorola without removing Superuser or Busybox.
*** Messed up and tried to flash using a verizon sbf to return phone. (Didn't brick it, but it would stop at the boot loader with errors waiting for a reflash from usb.
**** Got a warranty return!
*****Tried different methods to no avail!
************************************************************
Thought because of the info in this URL that I'd screwed up in returning my phone or trying to flash in the first place (just needed to use the adb interface to uninstall, remove, the files from their locations) and reinstall-->
WARNING for Droid X: Previously rooted DX owners who took an OTA update and then lost root should proceed with caution. This seems to only work flawlessly on SBF'd DX's or fully factory stock ones(read: never been rooted). The problem is with getting Superuser installed because it is already on your phone from when you were rooted previously.
rootzwiki.com/topic/3216-rootunroot-droid-3-root-instructions-one-click-added-for-windows-linux-osx/
Using info contained here might have worked...
psouza4.com/droid3/#droidx
If you are trying to root from the OTA Gingerbread update and you were previously rooted, you will probably experience problems with this root method because of the pre-existence of busybox and superuser.apk. For that reason, you may need to attempt both the script method (for Windows XP users) and program executable method (Windows Vista/7 users). If you are still having problems, please follow these instructions:
Open a Command Prompt in the folder where you extracted the one-click root package (see instructions for rooting). If you are using Windows 7, you can just use Shift+Right-Click on the folder you extracted the package and choose to "Open a command prompt here". For other operating systems or versions of Windows, you may require some DOS experience or need to Google how to change directories.
In the command prompt, type the following command:
adb shell
If you receive any kind of error, then you may not be in the folder where you extracted ADB.exe or you may need to reboot your computer, your phone, or check the connection. You should receive an ADB prompt ending with either a # or a $.
If the line ends with a $, then run the one-click exploit for Windows XP (even if you have Windows Vista or 7) and only complete step 1.
When you have adb shell ending with a #, type the following commands:
mount -o remount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
Ignore any messages that warn you about the file not being found/missing. We're removing old copies of su/superuser which are causing this one-click root method to fail.
************************************************************
NOW TRYING TO GO BACK TO 2.2.2 Froyo! Why, so I can try to root uninstalling the Su and Busybox rooting after OTA update. Would reinstall and try later.
************************************************************
Since I've gotten a fresh phone but the 2.3.5 update applied, I'm trying to return it to 2.2.2 stock. I've tried two different SBF claiming to be the correct ones. The one that is recognized by 4.9 RSDLite can be found here-->sites.google.com/site/1kdsdroidx/home/milestone-x-sbf-files
But I get those funky errors for which I can see no end except maybe trying XP. I've placed at the root of C: and given RSDLite administrative privs.
************************************************************
The other one that I've tried is named SHADO_X6_3.2.6_SHADOW_BP_C_02.06.00R_AP_BP_Flex_21_signed_secure_cell_south_1ff_P3_USERBLD.sbf.gz
but isn't even recognized!
Forgot url.
Please Help?!
Oh yes, I may have to crank up Debian or Kubuntu (have been with Debian since Inspiron 8200 and bf2.4 ! Just have gotten spoiled by Kubuntu (apt-get from terminal though) on this same laptop. They're already installed.
Just kinda frustrated. I've done a bit of homework and gotten a bunch of bought sense. Please help me out. Maybe I just get back to 2.2.2 and wait or try to root, remove offenders, and re-root.
Thanks.
a Droid X and Milestone X are different. Which do you have?
Yup, using Milestone X now to write thiz reply. I'm getting the idea that somehow the OTA blocks downgrading. This OTA has hosed tethering even with Easy Tether unless, there's user error. I'd like to go back to 2.2.2 cause it was a cinch to root. The interface for 2.3.5 is just plain easier to use. I can deal w Froyo though. Any help would be appreciated.
---------- Post added at 10:16 PM ---------- Previous post was at 10:11 PM ----------
Almost forgot, cellular south....C-Spire. Need it to tether wirelessly to post grades and lesson plans online when my renter is just to slow to get a line added for at&t. Heck, took 9wks just to get gas hooked up.
I don't know specifics about cellular south or how the milestone x, different from the DX, but you should be able to sbf back to froyo kernel if the sbf for your carrier and version exist. Also, tethering without the carriers permission requires root and you said you lost it.
Sent from my DROIDX using xda premium
Have tried to sbf using rsdlite 4.9 and files listed in my first post. Using rsdlite with one file yields errors of 510B and 1337. The other file after decompression is not even recognized. I've been looking all over for those errors and have not found a definitive explanation. Furthermore, I've used both Windows 7, administrative rights, and XP in an administrative account with the files always at the root of the drive with the same ends.
Also, I've running installs of Debian and Kubuntu, but think I'll run into similar problems/errors. If I find someone who hasn't performed the update, reverted their phone back to stock, could I generate that sbf file?
Any suggestions about the errors or recreating a viable sbf file? How about using rsdlite 4.8, an earlier version?
Thanks.
just got my milestone x already had 2.3.5 update on it. can i root?
not at the time of this post that I can tell, unless you can sbf back to froyo (2.2.2) and apply one of the many rooting solutions found on the net.
I believe, more than look and feel, or even functionality or bug fixes, that 2.3.5 more so than the other releases offered by other carriers such as 2.3.4, was to do away with rooting or more likely tethering (wirelessly).
I've gotten errors or an unrecognized sbf from those found on the net (reputable sources) that would revert me back to froyo.
I'll list my steps to the error within a couple of days to see if it were just operator error.
ridnout said:
not at the time of this post that I can tell, unless you can sbf back to froyo (2.2.2) and apply one of the many rooting solutions found on the net.
I believe, more than look and feel, or even functionality or bug fixes, that 2.3.5 more so than the other releases offered by other carriers such as 2.3.4, was to do away with rooting or more likely tethering (wirelessly).
I've gotten errors or an unrecognized sbf from those found on the net (reputable sources) that would revert me back to froyo.
I'll list my steps to the error within a couple of days to see if it were just operator error.
Click to expand...
Click to collapse
you may be right, about the reason for the update. it's a real let down, just upgraded from my rooted hero (that i was forced to turn in (well forced is a way of saying they gave me $80. in trade for it)) to the x and i love it just want my wireless tether back. i can still tether with easytether (paid version) using usb. haven't tried pdanet yet. (i think pdanet allows for wireless connections. been a while since i used it) nope... no wifi tether with pdanet.
otherwise i will more than likely just wait until one of these amazingly intelligent devs figures out how to root it.
i have seen this asked but i haven't found a good answer, is it possible to pull the stock sbf from a non-rooted phone? and if so is there somewhere that the instructions are available.
i am new to motorola, coming from htc, so please forgive my ignorance if this is all common knowledge stuff.
So I got sick of Oreo constantly crapping out, being buggy and decided to give 7.1.2 a whirl again just because I remember it working so much better and it's been announced there are no more updates. After fighting with it for a while, I finally got it downgraded and staying there. I found another post detailing some of this but wanted to write a howto from scratch.
Here's how I did it:
Download the factory image for fugu 7.1.2 from here: https://developers.google.com/android/images
Download the latest version of Magisk from here: https://github.com/topjohnwu/Magisk/releases
Download ADB/Fastboot of your choice and install it. I use this on windows: https://forum.xda-developers.com/showthread.php?t=2317790
Download TWRP for fugu here: https://dl.twrp.me/fugu/twrp-3.2.2-0-fugu.img.html
Reboot your nexus into bootloader mode (hold button on bottom while plugging in, light turns on, then blinks, release button) Connect it to your computer with a MicroUSB cable.
First thing you need to do is ensure your player is unlocked. When in the fastboot screen it should show the lock state. If it's locked, you need to run this command twice from your computer: "fastboot oem unlock"
Okay, now you're ready to go, you need to extract the factory firmware and use adb to flash it. Extract the main firmware file. Inside is another large zip file with the broken out recovery and system images. Extract that file also.
First flash the 7.1.2 bootloader: fastboot flash bootloader bootloader-fugu-fugu-02.13.img
Reboot into the flashed bootloader: fastboot reboot-bootloader (If it doesn't reboot in the bootloader, unplug and use the hold button and plug in to get back to the bootloader screen)
There is usually another ZIP in the factory images archivce, you can flash all with the included script or I usually just unzip that archive and flash one at a time.
Flash System: fastboot flash system system.img
Flash Boot: fastboot flash boot boot.img
You can skip flashing the recovery because you are going to flash TWRP with: fastboot flash recovery twrp-3.2.2-0-fugu.img
Okay, now you need to go into TWRP. You can press the button once on the player and it will say recovery mode, then hold the button for a few seconds and let go and it should boot int TWRP.
You need a mouse to control TWRP unfortunately and I had to use a USB OTG adapter to get a mouse connected to the NexusPlayer MicroUSB port.
TWRP Might ask if you want to keep system Read Only. Push the button that says Keep Read Only.
Once you are in TWRP, you need to sideload the Magisk ZIP file. Go to Advanced, select USB sideload and swipe to start it.
Now you need to hook the player up to the computer again with MicroUSB.
On your computer do: adb sideload Magisk-v17.3.zip (Or whatever version of Magisk you happened to download)
It should load Magisk and patch everything for you. I have found that I need to then hook the mouse back up, go back to the main menu, and perform a wipe/factory reset of the Data partition before it will allow it to boot for some reason.
Once that is done, boot up the Nexus Player. It will ask you to connect Wifi and register. If you have non 5g Wifi, connect to that first as you are racing against the clock to install Magisk Manager before the Oreo Update downloads and installs.
The first thing you need to do is allow Unknown Sources from Settings -> Security & Restrictions -> Enable Unknown Sources
Next install Magisk Manager -> Go to Settings -> Apps -> Magisk and hit Open, it should download the Magisk Manager application and ask you to install.
Once that is done, immediately go to network settings and disable WiFi, this will stop the download of the Oreo Update and you have time to finish up.
Now you need to go to About and click 5 times on Build version to become a developer. Go to Settings -> Developer options and enable USB debugging. It
Connect the Nexus Player back to your computer (it should ask if you want to allow developer access, select yes) and do:
adb shell
Once in the shell type: su
It should pop up a dialog asking you to approve root, say yes.
Okay, now you are going to disable the otacerts.zip This will disallow updates to be applied.
Remount the system partition as readwrite
cd /
mount -o rw,remount /system
Disable otacerts.zip
cd /system/etc/security
mv otacerts.zip otacerts.disabled.zip
exit
exit
Okay, now your nexus player will no longer to able to apply updates. If you are happy here, you are good to go. The nexus player will still continue to try to download updates though so if you want, you should be able to disable it with this script: https://pastebin.com/E7QuvFdQ
Save as disupdate.sh on your computer
You put this script on your nexus player by using adb
adb push disupdate.sh /sdcard/disupdate.sh
You should then use adb shell again and move the script into place
adb shell
su (accept request on screen if it asks to become root)
mv /sdcard/disupdate.sh /sbin/.core/img/.core/service.d/disupdate.sh
chmod 755 /sbin/.core/img/.core/service.d/disupdate.sh
This will automatically disable the update service when the box boots. If there is no directory /sbin/.core/img/.core/service.d then Magisk isn't likely properly installed. You might need to reboot or something to get it to load.
That's it, enjoy Nougat, IMO the best running rom for the Nexus Player.
Thank you! My player started random reboots then lost wifi on android 8. This worked great and she seems to be running properly again.
The final step fails for me. I run adb push to move the script and it looks like it does it, no error message but the file doesn't copy. Not a big deal, I can watch netflix again.
---------- Post added at 12:32 PM ---------- Previous post was at 11:47 AM ----------
I worked around it. What I did was push the file to a location I had permission to write to on the nexus.
Then I copied the file using a root powered file manager, Solid Explorer in this case, to /sbin/.core/img/.core/service.d/
Hopefully this helps others to keep their nexus player alive. 7.1.2 runs very nice.
Update: After running great for the past week my nexus player how just sits at the black google screen.
You lost me at the "USB OTG adapter"
I wonder if your problem with Ver. 8 (which is Oreo?) has to do with unplugging or losing power to the device? - After I lost power for just a second (blink) the unit partially bricked and finding your post got me to a different page that showed how to sideload (via ADB) the ver. 8 OTA onto the device.
That worked OK until the unit lost power again (I unplugged it to move it). The problem returned and since I don't have the mouse adapter, I just tried to sideload a ver. 7.1.2 OTA but that refused to load with an error message that I didn't grok but probably meant that it was incompatible with stuff that Ver. 8 had on the filesystem.
So I restored again the latest Ver. 8 ota.zip and for now (until the next power off) it is working.
-----
Seems like they have a problem serious enough thought that another update will have to happen.
-----
Thanks!
snowzach said:
So I got sick of Oreo constantly crapping out, being buggy and decided to give 7.1.2 a whirl again just because I remember it working so much better and it's been announced there are no more updates. After fighting with it for a while, I finally got it downgraded and staying there. I found another post detailing some of this but wanted to write a howto from scratch.
Here's how I did it:
Download the factory image for fugu 7.1.2 from here: https://developers.google.com/android/images
Download the latest version of Magisk from here: https://github.com/topjohnwu/Magisk/releases
Download ADB/Fastboot of your choice. I use this on windows: https://forum.xda-developers.com/showthread.php?t=2317790
Download TWRP for fugu here: https://dl.twrp.me/fugu/twrp-3.2.2-0-fugu.img.html
Reboot your nexus into bootloader mode (hold button on bottom while plugging in, light turns on, then blinks, release button) Connect it to your computer with a MicroUSB cable.
Once you are in fastboot mode, you need to extract the factory firmware and use the minimal adb to flash it.
First flash the 7.1.2 bootloader: fastboot flash bootloader bootloader-fugu-fugu-02.13.img
Reboot into the old bootloader: fastboot reboot-bootloader
There is usually another ZIP in the factory images archivce, you can flash all with the included script or I usually just unzip that archive and flash one at a time.
Flash System: fastboot flash system system.img
Flash Boot: fastboot flash boot boot.img
You can skip flashing the recovery because you are going to flash TWRP with: fastboot flash recovery twrp-3.2.2-0-fugu.img
Okay, now you need to go into TWRP. You can press the button once on the player and it will say recovery mode, then hold the button for a few seconds and let go and it should boot int TWRP.
You need a mouse to control TWRP unfortunately and I had to use a USB OTG adapter to get a mouse connected to the NexusPlayer MicroUSB port.
Once you are in TWRP, you need to sideload the Magisk ZIP file. Go to Advanced, select USB sideload and swipe to start it.
Now you need to hook the player up to the computer again with MicroUSB.
On your computer do: adb sideload Magisk-v16.7.zip
It should load Magisk and patch everything for you. I have found that I need to then hook the mouse back up, go back to the main menu, and perform a wipe of the Data partition before it will allow it to boot for some reason.
Once that is done, boot up the Nexus Player. It will ask you to connect Wifi and register. If you have non 5g Wifi, connect to that first as you are racing against the clock to install Magisk Manager before the Oreo Update downloads and installs.
The first thing you need to do is allow Unknown Sources from Settings -> Security & Restrictions -> Enable Unknown Sources
Next install Magisk Manager -> Go to Settings -> Apps -> Magisk and hit Open, it should download the Magisk Manager application and ask you to install.
Once that is done, immediately go to network settings and disable WiFi, this will stop the download of the Oreo Update and you have time to finish up.
Now you need to go to About and click 5 times on Build version to become a developer. Go to Settings -> Developer options and enable USB debugging. It
Connect the Nexus Player back to your computer (it should ask if you want to allow developer access, select yes) and do:
adb shell
Once in the shell type: su
It should pop up a dialog asking you to approve root, say yes.
Okay, now you are going to disable the otacerts.zip
This will disallow updates to be applied
cd /system/etc/security
mv otacerts.zip otacerts.disabled.zip
Okay, now your nexus player will no longer to able to apply updates. If you are happy here, you are good to go. The nexus player will still continue to try to download updates though so if you want, you should be able to disable it with this script: https://pastebin.com/E7QuvFdQ
Save as disupdate.sh on your computer
You put this script on your nexus player by using adb
adb push disupdate.sh /sbin/.core/img/.core/service.d/disupdate.sh
You may also need to use adb shell again and run:
chmod 755 /sbin/.core/img/.core/service.d/disupdate.sh
This will automatically disable the update service when the box boots.
That's it, enjoy Nougat, IMO the best running rom for the Nexus Player.
Click to expand...
Click to collapse
First off great starting point to get nougat back on nexus player but a few points...
a) I had to do "mount -o rw,remount /system" after SU to get write on /system
b) The method you outlined for running script on boot didn't work for me and i ended up having to use https://play.google.com/store/apps/details?id=com.k2.bootshellprokey with the script you provided
Other than those two points worked great and staying on 7.1.2
Questions:
"cd /system/etc/security mv otacerts.zip otacerts.disabled.zip" is this typed in the adb shell?
Where on the computer should I save this "Save as disupdate.sh on your computer"?
Thanks
texasjmzmd said:
Questions:
"cd /system/etc/security mv otacerts.zip otacerts.disabled.zip" is this typed in the adb shell?
Where on the computer should I save this "Save as disupdate.sh on your computer"?
Thanks
Click to expand...
Click to collapse
I answered these questions. However I get an error of failed to copy when I adb push the sh file.
Had to do this 4 times to get it to stick. The second to the last step preventing the update is what was difficult. It kept upgrading to Android 8. I couldn't get the script part to work. So far so good this has worked for me. Kibmcz's "a)" suggestion allowed me to stop the automatic upgrade. So far it's sticking and working really well. I did this to prevent the black screen of death that everyone's getting with Android 8.0 upgrade.
Got the OTG adapter - questions & comments
Finally got an adapter to run that allowed a mouse hookup to run TWRP. Followed the directions and have a couple of questions and deviations that I had to take.
1. Now that TWRP takes the place of Recovery, does a manual backup of the changed version of what we have here have to be done in order to restore if something compromised the system again?
2. TWRP shows up in the Player app and if you launch it tells you to download as it is only a placeholder?
3. The script disupdate.sh wouldn't copy to the required destination even if I ran "adb root" so I had to push it to /sdcard then shell in, become su and mv it to ~/service.d Then chmod worked and I rebooted.
4. Turned back on the wifi and saw items updating. I went to About > Update and saw that Vers. 8 was downloading. At the end it claims that 489.2 MB downloaded but then - Verification failed. That shows that the moving of the 'cert' file worked but perhaps not the script? Is that space recoverable? What directory is it put in?
Otherwise, seems to be working - Many thanks to you !
A couple of days later, the 4 balls animation returned. Brought up Restore, TWRP and attempted to revert to a backup made with it but it would not restore it. So... Flashed boot and Flashed system and it came back to life for another couple of days. TWRP doesn't load anymore though so the un-altered system without the script still doesn't want to load Oreo as there is a copy of Oreo still there that didn't pass verification.
Still busted every couple of days though.
ggregor said:
Finally got an adapter to run that allowed a mouse hookup to run TWRP. Followed the directions and have a couple of questions and deviations that I had to take.
1. Now that TWRP takes the place of Recovery, does a manual backup of the changed version of what we have here have to be done in order to restore if something compromised the system again?
2. TWRP shows up in the Player app and if you launch it tells you to download as it is only a placeholder?
3. The script disupdate.sh wouldn't copy to the required destination even if I ran "adb root" so I had to push it to /sdcard then shell in, become su and mv it to ~/service.d Then chmod worked and I rebooted.
4. Turned back on the wifi and saw items updating. I went to About > Update and saw that Vers. 8 was downloading. At the end it claims that 489.2 MB downloaded but then - Verification failed. That shows that the moving of the 'cert' file worked but perhaps not the script? Is that space recoverable? What directory is it put in?
Otherwise, seems to be working - Many thanks to you !
Click to expand...
Click to collapse
I couldn't get the script to work either.
Did this August 21st. Still working today [Sept 2].
For those of you still having trouble, it seems like you are having an issue with installing Magisk. When you have Magisk installed, it actually creates linked directories in the system partition. You aren't making changes to system. I am going to update the original post to push the script and then move it to a directory that Magisk manages. That hopefully fixes everyone else.
Thanks for posting and updating your instructions. I used my own workaround for keeping my 3 Nexus Players alive and locked on Nougat 7.12...
Do you have a theory on how to make the LED light work again on those NPs that have gone dark and unresponsive to the OTG connection from a laptop or PC?
Instead of rooting or using Magisk, just use TWRP and its file manager to rename the ota certs file. You can also use it to put in the script if you want, or use it to remove gms and gsf to stop GPS from updating which actually is more the problem - people on lineage 15.1 are still bricking.
Did this August 21st. Still working today [Sept 20].
Mine is dead now.... No light on powerup, quickboot screen or any other sign of life. Forced to move on to a non-branded Android box. Boot loop even started after using LineageOS 15.1 (which required starting with 8.0 Oreo)
thanks for the guide, I did this and it worked great. Used the script as well and all 3 of my players are still working 2+ weeks after doing this.
I did notice I can't stream anything from some apps anymore though. Is there a way to remove root, so I can stream from certain apps again?
Triumph said:
I did notice I can't stream anything from some apps anymore though. Is there a way to remove root, so I can stream from certain apps again?
Click to expand...
Click to collapse
Which specific streaming apps are you referring to and what do the error msgs say?
growsonwalls said:
Which specific streaming apps are you referring to and what do the error msgs say?
Click to expand...
Click to collapse
They are HGTV, Travel Channel, Cooking Network, and ABC.
When I open them up they show a "Live Channel" option, and I enter in my online information for the channel (That has always worked in the past, and works on my Nvidia Shield device that isn't rooted.)
If I choose the Live Channel quick enough it tries to play then times out and says "There was an error playing this content."
If I open the app, and stay at the main screen for a minute or so, the Live Channel option disappears from the header, and I don't see it again, until I reboot the player.
I can play previous show episodes, just not the live stuff.
Triumph said:
They are HGTV, Travel Channel, Cooking Network, and ABC.
I can play previous show episodes, just not the live stuff.
Click to expand...
Click to collapse
In order to recreate this, I am still missing vital information.
Is this happening inside of Kodi or did you download these 4 apps (channels) through the Google Play Store?
In Kodi, I've never seen a "Live Channel" option for these channels, just several old episodes listed.
As for the 4 channels from the Play Store, they each have a stream live option where you sign in to your tv provider. My tv provider isn't on that 'sign in' list so can't watch it live.
If in Kodi, were they installed from the Kodi repo or did you install a 'build' that came with them already installed?
Or is there a different streaming app that is hosting these apps?