Database Info

adb devices command returns no devices

I have followed the tutorial (http://forum.xda-developers.com/showthread.php?t=1170760) after reading through it several times to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...

follow-up
i have since uninstalled the "other device" instance, copied the superuser, su and rootboot to platform tools and re-tried, but no joy. tried with elevated admin privileges, etc., still no joy. next i will stand on one foot with a sparkler in my...ear and see how that goes. there must be a simple solution that i am too dense to see: check list 1-usb debugging on...check 2-necessary files Xoom USB drivers and Fastboot, boot (kernel) partition and Superuser.apk and su binary...check 3-Place rootboot.img, superuser.apk & su binary in the same place you will open your command window...check (hell, i put them all over and no place works)...check 4-read this bad boy cover to cover 3 times (http://forum.xda-developers.com/showthread.php?t=879701)...check 5- open command window in 10 different places where the files above are...check 6-type in adb devices and get device returned...(loser klaxton sound)

I had the same problem. And also saw my Xoom as the MZ#. I just reinstalled the drivers. Worked fine after that. If all else Fails..try rebooting the pc first...sometimes dumb crap like that is all it takes. Once you see it in adb the rest is easy.
Took me awhile to get mine working. Had all the adnroid SDK stuff installed. And was in the c:\android-sdk-windows\platform-tools\ directory with all the files for rooting there while in command prompt. I thought I had the right drivers installed cause it could see my Xooms drives on USB. Guess not, cause once i Just reinstalled the drivers and unplugged and plugged back in the device and boom. I saw it connect. XD felt great to see that.
Sent from my Xoom using XDA Premium App

I had the same problem as you, this is what I did:
1. Activate USB Debugging
2. Disconnect pad from computer
3. You need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
4. Restart computer
5. Connect pad

big flamingo said:
I have followed the tutorial (http://forum.xda-developers.com/showthread.php?t=1170760) after reading through it several times to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
Click to expand...
Click to collapse
check out the "Idiot's Guide to Flashing..." in the Development section. http://forum.xda-developers.com/showthread.php?t=1130996 Follow the steps there, except substitute the actual rooting section from the thread you quoted for the same portion (step #5), but also using the files in jase33's post--the Idiot's Guide was for rooting from HC3.1 and you are coming from 3.2.
Most important...you have to have the files you will be flashing through ADB (only img files, never zip files!) in your platform tools folder (sdk)...you can't just change directory. It sounds like you have a few issues going on at the same time, so I suggest you start over, get everything prepared in advance, run through your steps, then go for it.
On edit, I see you put all your files in one place...good.
Best of luck!

thanks to all
i have now attempted each of the methods above, but am having no luck getting adb to recognize my xoom. i have rebooted both laptop and xoom several times while uninstalling and reinstalling drivers, but still no listed adb devices. i feel it is something simple. i have installed everything you can download and install through sdk manager. i have no experience with sdk or adb so i don't know if i have too much or too little of whatever in there.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
two captures, i don't know what to do about mz604. i can move files around and interact with the xoom from the laptop all i want, so maybe it is unimportant...maybe not?
to summarize: I WENT BACK (TWICE) and removed xoom and all sdk things rebooted and started anew. result: the same as originally posted. i am officially stumped and any help would be greatly appreciated.

problem solved
had to download 64 bit driver from motodev arcanely called handset drivers
View attachment Motorola_End_User_Driver_Installation_5.2.0_64bit.msi.7z
thanks to all again and wish me luck as i hopefully end up with a rooted device

big flamingo said:
had to download 64 bit driver from motodev arcanely called handset drivers
View attachment 673634
thanks to all again and wish me luck as i hopefully end up with a rooted device
Click to expand...
Click to collapse
Please keep us posted. Good luck!

another problem
i cannot chmod for some reason. this is what it says...
i retried because of the syntax error, but that didn't work either so i am holding right here until someone saves my bacon

solved
syntax error way earlier...all is well and rooted

big flamingo said:
i cannot chmod for some reason. this is what it says...
View attachment 673644
i retried because of the syntax error, but that didn't work either so i am holding right here until someone saves my bacon
Click to expand...
Click to collapse
this is what I have:
after reboot, type;
adb remount
adb push su /system/bin
adb shell
ln -s /system/bin/su /system/xbin/su
chmod 4755 /system/bin/su
exit
adb push Superuser.apk /system/app
This is a different set of instructions, but even following the guide you were using (a bit out-dated), you missed a forward slash. You've really got to watch that syntax. ;^)
On edit: I see you've resolved it. Great!

[Q] Updated to JB, and a few issues started happening...

I updated to Jellybean last night, and was in the process of rooting it and installing CWM again. I plug the pad into my computer, and realized that it's not being recognized by my computer. It's not even charging it! However, when I attach the wire to the wall adapter, it's charging. When I plug it into my comptuer, and if the pad's screen is on sleep, it autowakes it though.
I tried using someone else's cable and the same issue still occurs. Is there a way I can install CWM on my pad and root it without using adb commands on my computer? because that could be my only solution now. Unless, there's a way I can get it to recognize on my computer.
P.S. I had root+CWM installed when I was on ICS.

BUMP.
No one else has this issue? I'm 99% sure its my port, but how can i ota fastboot and flash cwm and root?

Caduceus46 said:
I updated to Jellybean last night, and was in the process of rooting it and installing CWM again. I plug the pad into my computer, and realized that it's not being recognized by my computer. It's not even charging it! However, when I attach the wire to the wall adapter, it's charging. When I plug it into my comptuer, and if the pad's screen is on sleep, it autowakes it though.
I tried using someone else's cable and the same issue still occurs. Is there a way I can install CWM on my pad and root it without using adb commands on my computer? because that could be my only solution now. Unless, there's a way I can get it to recognize on my computer.
P.S. I had root+CWM installed when I was on ICS.
Click to expand...
Click to collapse
It's a problem that some users have, and in my mind it was not resolved.
But If you want to install your recovery, you can do with TWRP recovery and Terminal Emulator app (play store)
You should search if you can make it by the same process for CWM, apparently no, cause you need fastboot.
Try this : [GUIDE] Help for flash more faster when you use Fastboot Line Command maybe you've got a problem with your fastboot. I don't know.
It's an easy installation of fastboot.

Caduceus46 said:
BUMP.
No one else has this issue? I'm 99% sure its my port, but how can i ota fastboot and flash cwm and root?
Click to expand...
Click to collapse
There is an option to allow ADB over network, but I haven't experimented with it. If you were adventurous, you could try it and let the community know what happens?
In the ROM I'm running (Baked Blackbean #5, Android 4.1.1 and based on CyanogenMOD) you can select this option by going to Settings-->Developer Options--->"ADB over network"
I just attempted to do this, and it worked rather flawlessly. Enable ADB over network, and it will give you the IP address of your device (in my case, 172.16.1.22:5555).
Then, follow the steps below. This assumes you have a rooted device. To do the terminal commands on my tablet, I use the "Terminal Emulator" program, free from the Market.
This is really simple.
First make sure you are rooted. Download a terminal emulator from market (there are lots that are free). Make sure that your android is connected to your WiFi and get the WiFi IP address. Open the terminal program and type:
su
setprop service.adb.tcp.port 5555
stop adbd
start adbd
Now go to your computer (assuming that you are using windows) create a shortcut on the desktop for "cmd.exe" (without the quotations).
Right click on the cmd shortcut and choose "Run as Administrator"
Change to your android-sdk-windows\tools folder
Type:
adb connect ***wifi.ip.address***:5555
(example: adb connect 192.168.0.105:5555)
adb should now say that you are connected. Note: if you are too fast to give the connect command it may fail. so try at least 2 times 5 seconds apart before you say this doesn't work.
Click to expand...
Click to collapse
To put the device back to USB, once you get it working (because ADB over network is NOT SECURE):
And you can disable it and return ADB to listening on USB with
setprop service.adb.tcp.port -1
stop adbd
start adbd
Click to expand...
Click to collapse
Got this information from: Here
I do want to note that all I did was verify that ADB is detected over wifi. When I type 'adb devices' on my Windows 7 PC, it detects the IP address of my tablet, which indicates the two devices are communicating correctly. I didn't try pushing/pulling files since I have no need for that, but hopefully this helps you.

I will try next week (cause I'm off @t work) this process, just for seen if it works well.
I don't need it, but it's interesting to know this.
The post which speak about this use is in N1 forum => here -> Post #22.
But it's more complete here : How can I connect to Android with ADB over TCP?
Apps which are automate this process :
- adbWireless - no updated since Sept 5 - 2010 - You need root access
- WiFi ADB - You need root access - Updated September 29, 2012
- ADB WiFi - Updated August 27, 2012 - You need root access
Well done @opethfan89 :good:

philos64 said:
I will try next week (cause I'm off @t work) this process, just for seen if it works well.
I don't need it, but it's interesting to know this.
The post which speak about this use is in N1 forum => here -> Post #22.
But it's more complete here : How can I connect to Android with ADB over TCP?
Apps which are automate this process :
- adbWireless - no updated since Sept 5 - 2010 - You need root access
- WiFi ADB - You need root access - Updated September 29, 2012
- ADB WiFi - Updated August 27, 2012 - You need root access
Well done @opethfan89 :good:
Click to expand...
Click to collapse
Thanks!!
Sent from my Transformer Pad TF300T using xda app-developers app

@opethfan89, ADB over network will probably not work for me because I don't have root anymore. Appreciate the help :good:
@Philos64, thank you for your post as well. I will try that sometime this week and let you know the results as well.

Oh wait, I don't think that method will work. I will need su permission to flash twrp. I don't have root anymore either

Caduceus46 said:
Oh wait, I don't think that method will work. I will need su permission to flash twrp. I don't have root anymore either
Click to expand...
Click to collapse
Perhaps I'm wrong, but you don't need root to be able to flash a custom recovery, since the recovery operates outside of the Android OS (and root only affects app permissions within the OS). You would just need fastboot to be able to flash the recovery. Do you have the proper drivers installed on your computer? Can you try different USB ports? Maybe a USB hub? Try it on a different computer to, just to process of eliminate any kinks between the tablet and the physical connection of the USB cable.
Sent from my Transformer Pad TF300T using xda app-developers app

[Resolved] How to successfully root PTCL Charji Wingle R660 and enable security and NAT features

Goal has been successfully achieved by a little bit of research and careful experimentation. Got to the middle of this post to find the complete solution.
I have a 4g Router Model: R660 also called 4g Wingle. The manufacturer is unknown as there is no branding on the device. But some say it is a GadgetIT product. I have scoured the internet and I cannot find the vendor named GadgetIT. But that is a separate discussion.
Main Goal: My main goal is to enable Virtual Server/Port forwarding in the device. The UI available when the device is connected is available at 192.168.1.1 with credentials admin/admin and Looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This device is marketed by ISP PTCL as CHARJI EVO . The users of PTCL charji on this forum might say that port forwarding is not possible in this device but I disagree. and I have evidence to support otherwise but again that is a separate discussion.
What I have found so far?
I am able to telnet to this device at 192.168.1.1 via admin/admin credentials. Here is what I get.:
Version
LNX.LE.4.1-41009-9x35
But admin is not root. There is a separate user called root which obviously has a different password. I have tried all common router password (not sure what all will constitute...but i have tried many).
The goal here is to root this device so that I can perform the necessary changes such as the following:
As you might have guessed by now, that i cannot unless I am root which I am not.
So I need your help guys. Here are other interesting things to look at:
I could edit mobileap_cfg.xml but I cannot because the file is readonly and I was unable to chmod it to 777 with an error message "Operation not permitted" indicating that I am not root and I can not make that happen.
The second thing i would like to do is to enable SNMP monitoring which I cannot do from the main interface because the vendor hid the option.
Lastly, enable firewall.
Interestingly, all these options are available in a tab called "Security" which the vendor has hidden from the configuration interface available at 192.168.1.1
So I am inviting the expert comments of all hackers that can help me make get it sorted out. Ideally, it would be awesome to have these options enabled from the UI (I am willing to hack, root this device and modify firmware if needed) to get this done.
This can potentially help millions of PTCL Charji Users who cannot run any kind of server using this device (including game servers) and any kind of listening services (sockets or WEB or FTP) r those who would like use torrents but suffer from terrible low download speeds on torrents because of not being able to open ports for incoming connections that significantly raise download speeds for torrent.
More details:
mobileap_cfg.xml ownership and permissions:
Appreciate your help. Waiting to hear helpful responses soon. Successfully rooted without any busy box.
Solution Achieved successfully- See Steps & detail as follows:
I was able to switch device to bootloader mode and was able to change root password and now I am able to switch to root mode when logged in via admin using telnet. I have successfully change the DMZ but i have yet to observe its effects. If it works, I will work on changing other values as well.
Detail:
The device closely resembles D-Link DWR 901 But mind you, it is NOT DWR 901. Even thought the radio matches, if you flash the firmware from DWR 901 (which will be successful), the device will NOT work. Since there is no available source of the original firmware of the device, the device will be of no use anymore. So do not do it.
Similary D-Link's DWM 222 is also similar to this device (only that DWM 222) is a 3G modem. I downloaded both firmwares and found out upon extraction of these firmwares, that it contains the following files.
Files that you actually need are present in this archive -
WARNING
Use at your own RISK!!. Flashing this directly to your Charji will brick you Charji device. So just follow the procedure I described and do not try to flash it directly otherwise it will render your device unable to connect even though everything will look all right in the software. The device will never connect again...ever!
https://www.dropbox.com/s/hqa2m4499pyrj3z/R660A-Donot-Flash-it-On-Charji-It-Will-Brick-Your-device.7z?dl=0
There is a file called dl.exe which can turn the device into download mode assumung you have the PTCL Charji Wingle R660 plugged into the USB port.
After that running adb devices command will list all the devices.
After that you need to run the following commands
Code:
adb shell
passwd
The adb shell command will take you to the shell.
The passwd command executed from shell will tell you to enter a new password for root user
You will have to provide a secure password for it to be accepted.
After that, it will update the root password.
exit the shell using the exit or quit command or simply close the command prompt.
Now, you can telnet to the device using the command
Code:
telnet 192.168.1.1
Login with username admin and password admin (if these are your credentials to access the router page, Use your credentials. Mine were admin/admin)
The issue the following command to switch to root mode
Code:
su
It will ask for root password. Enter the password you set using the adb shell you had used before. and viola. You will turn to root mode.
You you have two ways to fix the NAT/DMZ problem.
Either you can directly use the vi editor (my OpenEmbedded Linux OS installed on the device has only vi support) to edit the file mobileap_cfg.xml and update DMZ value and port forwarding values.
or you can enable the security tab by editing the menu.js file which is located in /WEBSERVER/www/ directory. Now I had a PTCL Charji R660. If you have a different device, your files will be located elsewhere with different sets of issues.
You can do whatever you want!
Older Updates
Update# 02:
DMZ is now working !!
Update# 03
Successfuly unlocked the hidden security tab but still untested. Will test it shortly.
Update # 04
Successfully unlocked Wizard
Update# 05
NAT Rules persisting and working, tested by download torrents and using CanYouSeeMe.ORG
Torrents Downloads working on max available speeds

Reserved 1

Reserved for additional instructions etc
Reserved 2

Good find but instructions are really ambiguous and unclear. What are you supposed to do with dl.exe? run it, stare at it, run it and press enter????
You are just trapping people into bricking their devices with this instruction.

Yes I am bad at providing instructions.
dl.exe once run, turns the charji into bootloader mode and then it is possible to run adb shell and adb commands.
Hope this helps. I will update the article to be more descriptive in future sometime. Don't have time right now.
Regards.

timematcher said:
dl.exe once run, turns the charji into bootloader mode and then it is possible to run adb shell and adb commands.
Click to expand...
Click to collapse
Ok you are still not being clear. What do you mean by run once? currently dl.exe shows
Code:
Welcome to use OnekeyUpdate Tool.
The Software to be updated:Desktop
Press 'Enter' to update or 'Q' to quit.
on opening. Should I press Enter?
Sorry about being rude in first comment. I am really angry right now over this device right now, what kind of stupidity is not allowing user to port forward.

raza1080p said:
Ok you are still not being clear. What do you mean by run once? currently dl.exe shows
Code:
Welcome to use OnekeyUpdate Tool.
The Software to be updated:Desktop
Press 'Enter' to update or 'Q' to quit.
on opening. Should I press Enter?
Sorry about being rude in first comment. I am really angry right now over this device right now, what kind of stupidity is not allowing user to port forward.
Click to expand...
Click to collapse
When you click Enter, it will say "Waiting for device...." and then "found"
That is the point the device will appear in device manager (on windows) as well. and Now is the time to run adb shell and corresponding commands in my first article.
Important thing to note is that if you have never rooted any android (or linux) based device/phone/tablet, I suggest you read more about running adb.
The goal of my article was the following:
1. reset root password on the OpenEmbedded Linux variant on teh charji wingle device
2. Login via Telnet to 192.168.1.1 (Charji web console) using admin/admin (default credentials of Charji)
3. change to root mode using su command
4. Be able to change the xml files ( i mentioned in the first post) that allow the user to create the firewall rules and virtual server entries.
Now at this point I did not know that the person who whitelabelled Charji wingle for PTCL simply had disabled the relevant code in menu.js that enabled the Virtual server entries and firewall entries and DMZ fields (that allow pot forwarding, open firewall or simply set an ip address for DMZ that opens everything to a single IP on charji local network).
Once I found out, I was really happy and now I created the virtual server entries for torrent which was my main problem.
Thanks to Dr.hack who created a proper tutorial on his blog based on information in this article in a more streamlined manner.
Dr. Hack's Blog, Root-hack-ptcl-charji-evo-nat/

thank you for the tutorial.I am trying it on a charji cloud R500A. when dl.exe finds the device it goes to "6% Downloading hex image" .Am i suppose to wait at this point?
And will i be able to use other sim on the the device after the root?

Tarar said:
thank you for the tutorial.I am trying it on a charji cloud R500A. when dl.exe finds the device it goes to "6% Downloading hex image" .Am i suppose to wait at this point?
And will i be able to use other sim on the the device after the root?
Click to expand...
Click to collapse
First things first!, Are you trying to flash the image from the firmware link I gave? You should really not do that!
The link i gave is only provided for firmware modding experts. It is not the firmware of Charji. So if you flash it, it will brick your device and it will become useless.
What you really need to use is th dl.exe file , copy it into a separate folder with no other stuff in it.
If you run it from the same folder, it will brick your device by flashing a firmware which will not work for your Charji. CHarji will never connect after that!
dl.exe must be run to turn the device into booloader mode, After that you have to run adb shell commands and make the necessary changes to reset the root user password.
I don't know if it will allow you to use another SIM or not. PTCL devices are usually NOT network locked. But again, this is not a tutorial for allowing the users to use another sim. It merely allows the user unlock Virtual Server, Firewall, DMZ settings and similar features which are hidden by PTCL.
And there is no such thing as "Telenet". Telnet is a client application in windows which is not installed by default. You will have to install Telnet Client from "Add Remove programs" in Windows. It is needed to access the device using the telnet protocol. Do some research on Telnet.

timematcher said:
First things first!, Are you trying to flash the image from the firmware link I gave? You should really not do that!
The link i gave is only provided for firmware modding experts. It is not the firmware of Charji. So if you flash it, it will brick your device and it will become useless.
What you really need to use is th dl.exe file , copy it into a separate folder with no other stuff in it.
If you run it from the same folder, it will brick your device by flashing a firmware which will not work for your Charji. CHarji will never connect after that!
dl.exe must be run to turn the device into booloader mode, After that you have to run adb shell commands and make the necessary changes to reset the root user password.
I don't know if it will allow you to use another SIM or not. PTCL devices are usually NOT network locked. But again, this is not a tutorial for allowing the users to use another sim. It merely allows the user unlock Virtual Server, Firewall, DMZ settings and similar features which are hidden by PTCL.
And there is no such thing as "Telenet". Telnet is a client application in windows which is not installed by default. You will have to install Telnet Client from "Add Remove programs" in Windows. It is needed to access the device using the telnet protocol. Do some research on Telnet.
Click to expand...
Click to collapse
Thank you so very much for the details.
Yeah i found out about telnet commands.but i was using the dl.exe in the same folder.i guess that's why adb devices wasn't able to find my device.
Luckily it didn't install that firmware.

I have bricked my device by accidentally runing the gui.exe and i was dont know that it will flash new firmware. is there any way to get back ?:crying:

If you are able to switch to fastboot mode and you have the original software in the right format, then you should be able to flash the new firmaware using the utilities provided in the original post. The only way I think. I will try to see if I can create an image for my Charji R660 but I can not promise anything.
Note that I bricked first of mine and I took it to the people who upgrade firmware of the device and they were unable to fix it. and I got a new one by being sneaky (and playing dubm) about it.
Or if you want to learn, maybe start experimenting a little bit but I think you will need the original firmware.

timematcher said:
When you click Enter, it will say "Waiting for device...." and then "found"
That is the point the device will appear in device manager (on windows) as well. and Now is the time to run adb shell and corresponding commands in my first article.
Important thing to note is that if you have never rooted any android (or linux) based device/phone/tablet, I suggest you read more about running adb.
The goal of my article was the following:
1. reset root password on the OpenEmbedded Linux variant on teh charji wingle device
2. Login via Telnet to 192.168.1.1 (Charji web console) using admin/admin (default credentials of Charji)
3. change to root mode using su command
4. Be able to change the xml files ( i mentioned in the first post) that allow the user to create the firewall rules and virtual server entries.
Now at this point I did not know that the person who whitelabelled Charji wingle for PTCL simply had disabled the relevant code in menu.js that enabled the Virtual server entries and firewall entries and DMZ fields (that allow pot forwarding, open firewall or simply set an ip address for DMZ that opens everything to a single IP on charji local network).
Once I found out, I was really happy and now I created the virtual server entries for torrent which was my main problem.
Thanks to Dr.hack who created a proper tutorial on his blog based on information in this article in a more streamlined manner.
Dr. Hack's Blog, Root-hack-ptcl-charji-evo-nat/
Click to expand...
Click to collapse
Hi dear friend how are you? I need original webui of PTCL Charji device For Huawei Ec8372u-876 device please can you share the link or any guidance for this

saqi755 said:
Hi dear friend how are you? I need original webui of PTCL Charji device For Huawei Ec8372u-876 device please can you share the link or any guidance for this
Click to expand...
Click to collapse
Or any other links of non modified original Loced Huawei firmware and Webui

Huawei Ec8372u-876 is a very good device compared to sh!t devices offered by PTCL before.
Here is what I have found on the web.
Its probably an unlocking solution and not a locked file.
I am in no way responsible for the quality of the file or the steps as I dont have this device and I can not test it before posting.
Please use these are your own risk. I at least downloaded the file and executed on local PC.
but that is pretty much it. Please use at your own risk.
PTCL Evo Charji Cloud
E5377u-872
How to Unlock Evo Charji E5377u-872
1: Battery Should be 100% Charged
2: Data Cable
3: A Pin
4. Unlocked file
Click to expand...
Click to collapse
Code:
www.mediafire.com/file/6td2bh12b4l6g9o/PTCL_charji_E5377u-872-www.hispeedsolution.com.exe/file
Process>>
1. Remove the battery from the device
2. Press & Hold Power Button + Reset Button on the same time after 5 seconds device will boot into download mode.
3. Connect to PC
4. Wait for drivers
5. After the drivers installed go to device manager & note down the port # namely appplication UI interface.
6. Run the *.exe file & enter the port # (E.g 19 or 20 or etc etc)
7. Let it flash the device, it will take about 5 minutes, after the flashing let the device reboot. Your device will stuck on the Huawei screen, Don't worry wait for 3 minutes then remove the battery insert any Sim card & turn on the device.
8. Your device is successfully unlocked on all network Sim.
9. Connect the device to PC & set up accordingly.
Click to expand...
Click to collapse

timematcher said:
Huawei Ec8372u-876 is a very good device compared to sh!t devices offered by PTCL before.
Here is what I have found on the web.
Its probably an unlocking solution and not a locked file.
I am in no way responsible for the quality of the file or the steps as I dont have this device and I can not test it before posting.
Please use these are your own risk. I at least downloaded the file and executed on local PC.
View attachment 5369881
but that is pretty much it. Please use at your own risk.
Code:
www.mediafire.com/file/6td2bh12b4l6g9o/PTCL_charji_E5377u-872-www.hispeedsolution.com.exe/file
Click to expand...
Click to collapse

Thanks for your cooperation but I need file for Ec8372u-876 this file is not working on this please check this again this is not a device with battery

Let me look into it.

timematcher said:
timematcher said:
Can we use other networks 4G in this device?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Please reply if possible

sparking111 said:
Please reply if possible
Click to expand...
Click to collapse
Huawei 4G wingle should support other networks/SIMs once rooted.
I had a E8372h-608 4G wingle which was network locked to Telenor. After flashing it with network-neutral, universal firmware from huawei, it works for Ufone, Telenor, Warid/Jazz after appropriate AP configuration within the device UI.
Does that answer your query?

Galaxy S5 with broken screen, need help controlling it from PC

Hi, I've got an old S5 with a broken screen. There's no image going on and there's no indication that the touchscreen is working.
I'm not looking to recover data, I'm looking to play around with it by controlling it from my PC. Last I remember, the phone is running a Cyanogenmod OS (I don't think LineageOS was around at that time) with either TWRP or CWM recovery, but I'd bet on TWRP.
Now: the device reaches the OS properly, I can tell because if I try to turn the ringing sound up it gives me an audio feedback.
If I connect it to a PC from the OS:
- the phone shows up in Windows Explorer as "SM-G900F"
- Device Manager shows me a "SAMSUNG Mobile USB Composite Device" under Universal Serial Bus controllers
However I cannot access any files (Windows Explorer shows the device as empty), and if I attempt to 'adb devices' in the console it shows me an empty devices list.
Now, I suspect that USB debugging might be off. So I also tried connecting it to a PC from recovery and the exact same thing as above can be observed, PLUS:
- Device manager also shows me a "SAMSUNG Android Phone" list which can be expanded to show me one entry called "SAMSUNG Android ADB Interface"
However it's the same as before, no files available and 'adb devices' shows an empty list.
Now I heard that I can theoretically enable USB debugging through ADB, by writing to a config file. That would allow me to enable USB debugging and try something like Vysor in order to control the phone from my PC.
However that's a moot point until I can figure out why the ADB service on my PC isn't seeing the device. Any help would be greatly appreciated, and if you need more info I can provide it.
Extra info:
- I installed Samsung USB drivers at some point while trying to make it work
- Windows Explorer shows a phone icon for this device, and if I recall correctly that's what happens when it's connected through MTP (Mass Storage should show it like a memory card)

_sepiroth said:
Hi, I've got an old S5 with a broken screen..........
Click to expand...
Click to collapse
I've never experienced this situation myself but, I've seen that the following thread has worked for many individuals.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.

Ibuprophen said:
I've never experienced this situation myself but, I've seen that the following thread has worked for many individuals.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Click to expand...
Click to collapse
Thanks a bunch, that pointed me in the right direction with my research! I solved my issue, I can now control my phone from my PC.
By doing this I ran into a couple of problems, I'm going to describe them and their solutions:
Problem 1: couldn't ADB into the device when in Recovery Mode. That is because after a long head scratching session I came to the conclusion that I didn't have TWRP Recovery installed (I had Philz Touch CWM Recovery and LineageOS 14.1 instead).
Solution 1: ADB mode is enabled in TWRP by default. So I flashed the latest TWRP through Odin, ADB instantly started working afterwards in Recovery Mode.
Problem 2: USB Debugging was disabled inside the OS.
Solution 2: from the thread that Ibuprophen posted, you can enable USB debugging in your OS by opening an ADB shell into your device and modify the build.prop like so
Code:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop
reboot
Problem 3: /system was empty so there was no build.prop. If I attempted to create a build.prop file it wouldn't be saved after a device reboot, so USB debugging still didn't work.
Solution 3: it seems like TWRP doesn't mount /system by default, only /data. You can mount it manually through ADB like this:
Code:
mount -o rw /dev/block/bootdevice/by-name/system /system
I found this out from this stackexchange question: https://android.stackexchange.com/q...data-partitions-in-recovery-mode-in-adb-shell
Problem 4: When an app tries to use USB Debugging you need to allow it to do so from the phone. Since the screen was broken, I couldn't do this.
Solution 4: You'll need to push a public key to your device with ADB. Boot into Recovery Mode and make sure your device is recognized by your PC and type
Code:
adb push <path to adbkey.pub on your PC> /data/misc/adb/adb_keys
This solution is from: https://stackoverflow.com/questions...b-rsa-key-with-broken-touch-screen-on-android
This will make sure that you won't need to confirm debugging permissions for apps coming from your machine.
So for anyone who has a broken phone screen (my screen is dead and touchscreen/touch buttons are kaput too) and wishes to control their phone from their PC but USB debugging is disabled:
1. Boot device in TWRP Recovery (flash it if you don't have it)
2. ADB into the device
3. Make sure /system is mounted (if it's empty it means it's not mounted), else mount it manually like in Solution 3
4. Configure build.prop to have USB Debugging enabled like in Solution 2
5. Push your public key to the device like in Solution 4
6. Restart the phone (into its OS)
7. Download the Chrome extension called Vysor and launch it
8. Connect your phone through a USB cable
9. The device should appear in Vysor, connect to it and have fun controlling it
Note that if you just want to backup your files, steps 1 + 2 are sufficient. After making sure ADB works you can just 'adb pull' all your files which should be located in /sdcard. Google it, it's easy to find.
The same goes for backups, you can do them directly through ADB.
Again, thanks Ibuprophen!

Vysor does not work on all graphic cards. a good free alternative is scrcpy
btw instead of flashing twrp, you can flash a modified system partition with proper entries in build.prop (for those with no custom recovery available)

aIecxs said:
Vysor does not work on all graphic cards. a good free alternative is scrcpy
btw instead of flashing twrp, you can flash a modified system partition with proper entries in build.prop (for those with no custom recovery available)
Click to expand...
Click to collapse
Very well pointed out, thanks for this.

TiVo Stream 4K

Has anyone had much experience with the TiVo Stream 4K yet? I have 2 questions really. I would like to accomplish both without rooting the device.
1) Is there a way to skip the initial TiVo activation? I've tried powering off the device once it gets to that screen, but it starts right back up to the activation. I've tried hitting home, back, skip, everything I can think of, but it won't let me move on until the device is activated on a TiVo account. I want to help a buddy out by setting up his device for him, but I don't want the device to be locked to my TiVo account. I may be able to clear data on the TiVo app and remove it from my TiVo account manually (I haven't tried that yet), but I'd like to just skip the whole TiVo activation and let my friend do it all himself (set preferences, services to monitor, etc).
2) Has anyone been able to remove the TiVo Suggestions Channel from the Android TV home screen? When you go into the Channel Customization, you can deselect all channels but the TiVo Suggestions Channel. I can't even get it to move down the list (all other channels you can go left on the channel and move or remove, but that option isn't available for the TiVo suggestions Channel). I've tried clearing data on the TiVo apps. I've even tried disabling the TiVo and Sling apps, but the channel remains (and if you click it when the apps are disabled, it just errors out loading the app).
The important thing with both of those is it must be done without Root. I want Google Play to remain genuine so Netflix and other streaming apps work properly.

From what I can tell, No and No unfortunately. If you disable the Tivo app as well, the block in the launcher remains and won't go away. If you click it, its magically working again and not disabled. I'm fairly certain they modified the launcher and worked the Tivo stuff is permanent as for the price. The hardware is made by another company, same one that makes their AirTV2 tuner for sling. So I would just setup the tivo stuff under your tivo email. If your friend isn't going to use Tivo services in any way, it won't be an issue for you.

https://photos.app.goo.gl/pNcD361dJLsxTxMK9
I went through the original setup and configured it as it expected me to. Then I uninstalled most of the apps it comes bloated with. The ones I couldn't uninstall, I disabled at least visually. Then I installed Wolf Launcher and modified it to my liking. I then moddifed the remote to make the tivo button to open tivimate with a single click and vod apk with double click. I also made the Guide single click to open app history and double to open "Power off, Restart and Screenshot". Sometimes pressing tivo button would bring up the tivo guide and tivimate, so I disabled the tivo app, sling and most other crap entirely I didn't want running in the given app settings.
The only button I could not override was the Netflix button. You cannot uninstall Netflix either, but I believe you can disable it. My device runs incredibly smooth now and my display stays off when I use the power options above. Playback of vod does flicker sometimes, but I feel sure that will get resolved with a future update.

USAMac said:
https://photos.app.goo.gl/pNcD361dJLsxTxMK9
I went through the original setup and configured it as it expected me to. Then I uninstalled most of the apps it comes bloated with. The ones I couldn't uninstall, I disabled at least visually. Then I installed Wolf Launcher and modified it to my liking. I then moddifed the remote to make the tivo button to open tivimate with a single click and vod apk with double click. I also made the Guide single click to open app history and double to open "Power off, Restart and Screenshot". Sometimes pressing tivo button would bring up the tivo guide and tivimate, so I disabled the tivo app, sling and most other crap entirely I didn't want running in the given app settings.
The only button I could not override was the Netflix button. You cannot uninstall Netflix either, but I believe you can disable it. My device runs incredibly smooth now and my display stays off when I use the power options above. Playback of vod does flicker sometimes, but I feel sure that will get resolved with a future update.
Click to expand...
Click to collapse
Which button remapper app did you use? Might want to do something similar.
Also, not sure if it's just the hub I bought, but the Aukey USB type c 4 port hub doesn't work on the stream, but it does on my Huawei. Strangely a generic type c otg with a USB Ethernet adapter works fine.

siralsmooth said:
Which button remapper app did you use? Might want to do something similar.
Also, not sure if it's just the hub I bought, but the Aukey USB type c 4 port hub doesn't work on the stream, but it does on my Huawei. Strangely a generic type c otg with a USB Ethernet adapter works fine.
Click to expand...
Click to collapse
Yea I've had issues with ethernet connection as well. I believe there will be an update soon to resolve alot of the issues. My anker and amazon after ethernet adapters don't work, but I've read ugreen works but some say its unstable.
Anyhow, I used ButtonMapper

siralsmooth said:
Which button remapper app did you use? Might want to do something similar.
Also, not sure if it's just the hub I bought, but the Aukey USB type c 4 port hub doesn't work on the stream, but it does on my Huawei. Strangely a generic type c otg with a USB Ethernet adapter works fine.
Click to expand...
Click to collapse
Hey sorry for the delay! I used ButtonMapper.. and yea, there are alot of externals not working.. hopefully, the pending update will resolve these issues as well!

Is there a way to install the Tivo app on this thing? Kind of ironic it doesn't come with it.

there is a debug version of the firmware
TIVO - Google Drive
drive.google.com
adb shell reboot fastboot
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot reboot
adb disable-verity
adb reboot
adb root
adb remount
relook command is
fastboot flashing lock_critical
fastboot flashing lock
fastboot reboot

ben1226 said:
there is a debug version of the firmware
TIVO - Google Drive
drive.google.com
adb shell reboot fastboot
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot reboot
adb disable-verity
adb reboot
adb root
adb remount
relook command is
fastboot flashing lock_critical
fastboot flashing lock
fastboot reboot
Click to expand...
Click to collapse
what is the point of debug version of the firmware? sorry just asking to clarify

chinkster said:
what is the point of debug version of the firmware? sorry just asking to clarify
Click to expand...
Click to collapse
i'm curious about this too. the new ts4k software is absolute trash, would love to be able to go backwards and keep it from doing updates if possible...but i need more clarity on what exactly this does.

crackers8199 said:
i'm curious about this too. the new ts4k software is absolute trash, would love to be able to go backwards and keep it from doing updates if possible...but i need more clarity on what exactly this does.
Click to expand...
Click to collapse
I see the commands but do you know exactly how to implement them to flash the firmware? Just asking I've been watching this thread for a while

jmanley69 said:
Has anyone been able to remove the TiVo Suggestions Channel from the Android TV home screen?
Click to expand...
Click to collapse
Might be a year late and I'm sure everyone knows this already but.
If you go to apps system apps then disable the app I circled in this picture then restart your system it will let you freely customize everything on the homescreen. (Besides play next but that can be disabled)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ben1226 said:
there is a debug version of the firmware
TIVO - Google Drive
drive.google.com
adb shell reboot fastboot
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot reboot
adb disable-verity
adb reboot
adb root
adb remount
relook command is
fastboot flashing lock_critical
fastboot flashing lock
fastboot reboot
Click to expand...
Click to collapse
So, it is important not to have the erase button checked. I mistakenly had it checked and now the device is stuck in USB download mode showing GX-CHIP (instead of worldcup) that is password protected and the password.bin provided does not seem to unlock it. Any guidance would be helpful.
For others, I have successfully downloaded the ota and have flashable images for anyone interested. If you haven't updated you can flash from fastboot, if you haven't then follow what @ben1226 has in TiVo gdrive remember to uncheck erase and then you should be able to unlock flashing from fastboot. The Rom already has a su binary (in /xbin) which can be enabled (permissions are set off by default) for those interested if one wants root.
EDIT: Attached the unmodified OTA update.
ota-type=BLOCK
post-build=eSTREAM4K/SEI400TV/SEI400TV:9/PI/5614:user/release-keys
post-build-incremental=5614
post-sdk-level=28
post-security-patch-level=2021-04-05
post-timestamp=1622542764
pre-device=SEI400TV

jahrule said:
So, it is important not to have the erase button checked. I mistakenly had it checked and now the device is stuck in USB download mode showing GX-CHIP (instead of worldcup) that is password protected and the password.bin provided does not seem to unlock it. Any guidance would be helpful.
For others, I have successfully downloaded the ota and have flashable images for anyone interested. If you haven't updated you can flash from fastboot, if you haven't then follow what @ben1226 has in TiVo gdrive remember to uncheck erase and then you should be able to unlock flashing from fastboot. The Rom already has a su binary (in /xbin) which can be enabled (permissions are set off by default) for those interested if one wants root.
EDIT: Attached the unmodified OTA update.
ota-type=BLOCK
post-build=eSTREAM4K/SEI400TV/SEI400TV:9/PI/5614:user/release-keys
post-build-incremental=5614
post-sdk-level=28
post-security-patch-level=2021-04-05
post-timestamp=1622542764
pre-device=SEI400TV
Click to expand...
Click to collapse
Is there a guide to do this the links you gave me dont show anything . I'm about to buy one and attempt this but I need instructions I mainly want root .

@tokoam The tools etc are found here https://drive.google.com/drive/folders/18PWax4UPUBAdgAz1R9KnmCNFlt6a3fjA?usp=sharing where @ben1226 linked.
basically don't update it when you first get it. In a few days I will have more as m currently working on something for it.
If you are inpatient and have some know how then: flash the update I provided above, but NOT the bootloader from there (the updated bootloader enables oem lock and so far have not found a way to expose the option in dev options). Then chmod the `su` binary located in /xbin/ and you should have root and be good to go.

flash the update I provided above ... Then chmod the `su` binary located in /xbin/ and you should have root and be good to go
Click to expand...
Click to collapse
I installed the update that you attached above (in post #13) but there is not any su binary located in /xbin/, or anywhere else.
This seems to make sense, because you say in post #13:
EDIT: Attached the unmodified OTA update.
But I'm not sure why you suggested that the 'su' binary would be there, if the update attached to post #13 was installed.
flash the update I provided above, but NOT the bootloader from there (the updated bootloader enables oem lock and so far have not found a way to expose the option in dev options)
Click to expand...
Click to collapse
I didn't flash the bootloader from the update (in post #13), but still the bootloader was locked after I installed the rest of the update. Even if I didn't update bootloader.img or boot.img, the bootloader still gets locked when installing the rest of the update attached to post #13. So, the update is locking the bootloader by other means, probably via system.
I could unlock the bootloader again only by re-flashing the userdebug verson via usb burning mode. But then, of course, I no longer have 5614.

Right the bootloader lock happens only when you flash a system.IMG which is not a user debug version. The su binary is in the debug system img. I think if we can expose the allow OEM unlock option in Dev settings then we would be good to ho. My device bricked in gx-chip mode that apparently uses a different password then the one provided by Ben so im stuck there for now

goapy said:
I installed the update that you attached above (in post #13) but there is not any su binary located in /xbin/, or anywhere else.
This seems to make sense, because you say in post #13:
EDIT: Attached the unmodified OTA update.
But I'm not sure why you suggested that the 'su' binary would be there, if the update attached to post #13 was installed.
I didn't flash the bootloader from the update (in post #13), but still the bootloader was locked after I installed the rest of the update. Even if I didn't update bootloader.img or boot.img, the bootloader still gets locked when installing the rest of the update attached to post #13. So, the update is locking the bootloader by other means, probably via system.
I could unlock the bootloader again only by re-flashing the userdebug verson via usb burning mode. But then, of course, I no longer have 5614.
Click to expand...
Click to collapse
jahrule said:
Right the bootloader lock happens only when you flash a system.IMG which is not a user debug version. The su binary is in the debug system img. I think if we can expose the allow OEM unlock option in Dev settings then we would be good to ho. My device bricked in gx-chip mode that apparently uses a different password then the one provided by Ben so im stuck there for now
Click to expand...
Click to collapse
Here is something that can be done:
if (!showEnableOemUnlockPreference()) {
removePreference(this.mEnableOemUnlock);
this.mEnableOemUnlock = null;
That needs to he removed from tvsettings.apk
doing that is the easy part.. but installing the custom apk is the hard part.
need bootloader unlocked so we make changes to system.
the above is decompiled from the userdebug build.
also:
private static boolean showEnableOemUnlockPreference() {
return !SystemProperties.get("ro.frp.pst").equals("");
}
private boolean isOemUnlockAllowed() {
return !this.mUm.hasUserRestriction("no_oem_unlock");
}
pretty much: ro.frp.pst = 1 or true should turn on OEM unlock in developer options.
BTW: user restrictions only means, you must be logged into box with correct username and all..
bypassing settings and logging on as guest or whatever will not show any developer options..
that is what it means about user restrictions..

The circuit board used in the tivo stream 4k has a place for a micro sd card socket. I'm going to install a socket and check if it works.

I read on reddit this morning that the android 10 update started on 3/17. No sign of it on my hardware yet.