Database Info

[Let's Get] Root Achieved for Le Pan II (TC979)

JCASE HAS DONE IT GUYS:
http://www.forum.lepanlife.com/showthread.php?tid=322

No luck,
I followed the steps, but when I connected the Lepan2 to the computer, it started to find devices, and finally it got this as I show in this graphic:
imageshack.us/f/838/anydatahsusbdevice.jpg (I cannot post links so I place it like that)
So I tried the 'update driver software" for the one with the yellow question mark under "Other Devices" called ANY_DATA HSUSB Device" and none i386 or amd64 work with that device. I don't know why it shows 2 devices, the other as you can see is under "Portable Devices" and it was recognized by Windows 7 64-bit witch is the OS i'm running. Also if I right-click on that "LePanII" device and select 'update driver software' and point to the unzipped files that you posted above, it says that "The device LepanII already has the best windows drivers"
So when I run SuperOneclick, the one you also posted above, the application became "unresponsive' after clicking on "Root"
I checked on windows task manager and there are 2 adb.exe processes running, and the only way I can terminate the Superoneclick app is by terminating those 2 adb.exe processes. I have tried several times and same result, it becomes unresponsive after starting adb server on port 5037

rocketero said:
No luck,
I followed the steps, but when I connected the Lepan2 to the computer, it started to find devices, and finally it got this as I show in this graphic:
imageshack.us/f/838/anydatahsusbdevice.jpg (I cannot post links so I place it like that)
So I tried the 'update driver software" for the one with the yellow question mark under "Other Devices" called ANY_DATA HSUSB Device" and none i386 or amd64 work with that device. I don't know why it shows 2 devices, the other as you can see is under "Portable Devices" and it was recognized by Windows 7 64-bit witch is the OS i'm running. Also if I right-click on that "LePanII" device and select 'update driver software' and point to the unzipped files that you posted above, it says that "The device LepanII already has the best windows drivers"
So when I run SuperOneclick, the one you also posted above, the application became "unresponsive' after clicking on "Root"
I checked on windows task manager and there are 2 adb.exe processes running, and the only way I can terminate the Superoneclick app is by terminating those 2 adb.exe processes. I have tried several times and same result, it becomes unresponsive after starting adb server on port 5037
Click to expand...
Click to collapse
Yep, Bear was having the same issues when he tried. Adam and I have fixed the drivers partially (they are re-uploaded, so re-download them). When you use the re-up'ped drivers and update the AnyData HSUSB Device it will work now and change it to an Android ADB Composite Interface Device.
However, getting ADB working is another story. Adam and myself have been working on Bear's computer remotely and we've done what we can do from there. When we both get our Le Pan II's this week (Tues/Wednesday, respectively), we are going to push forward full speed ahead in Linux to attempt to get ADB to recognize the device.
It's started to look like the drivers that leaked are not for the LP2, which is disappointing to say the least. In order to root it without the drivers, it's gonna take time and patience and we're going to need to find an unpatched exploit in the HC OS by modifying Gingerbreak or Zerg.
I'll keep you updated as it progresses.

Hey,
Could any of you owners of the Le Pan II (TC979) do a dump of the ROM?
(including the drivers, kernel, etc)
It would be GREATLY beneficial to the XDA / RootzWiki HP TouchPad community since it would assist with the development of Ice Cream Sandwich, given how similar, if not identical the hardware on the Le Pan II is to the HP TouchPad.
Thanks.

PresidentMcCain said:
Hey,
Could any of you owners of the Le Pan II (TC979) do a dump of the ROM?
(including the drivers, kernel, etc)
It would be GREATLY beneficial to the XDA / RootzWiki HP TouchPad community since it would assist with the development of Ice Cream Sandwich, given how similar, if not identical the hardware on the Le Pan II is to the HP TouchPad.
Thanks.
Click to expand...
Click to collapse
As soon as we get this thing rooted, I'd be more than happy too
We have no firmware files, just OTA updates - they do not post firmwares, source code, adb drivers or anything on their site. But we'll get it and when we do, I'll get you that info.

dbaybay said:
As soon as we get this thing rooted, I'd be more than happy too
We have no firmware files, just OTA updates - they do not post firmwares, source code, adb drivers or anything on their site. But we'll get it and when we do, I'll get you that info.
Click to expand...
Click to collapse
Maybe this will help you with ADB drivers:
http://rootzwiki.com/topic/15624-how-tocm9-adb-interface-on-usb/
---------- Post added 24th January 2012 at 12:15 AM ---------- Previous post was 23rd January 2012 at 11:50 PM ----------
If you can at least use Root Explorer to zip up some of it, it'd be helpful
(I believe the drivers are .so files in the lib folder under /)

dbaybay said:
Yep, Bear was having the same issues when he tried. Adam and I have fixed the drivers partially (they are re-uploaded, so re-download them). When you use the re-up'ped drivers and update the AnyData HSUSB Device it will work now and change it to an Android ADB Composite Interface Device.
However, getting ADB working is another story. Adam and myself have been working on Bear's computer remotely and we've done what we can do from there. When we both get our Le Pan II's this week (Tues/Wednesday, respectively), we are going to push forward full speed ahead in Linux to attempt to get ADB to recognize the device.
It's started to look like the drivers that leaked are not for the LP2, which is disappointing to say the least. In order to root it without the drivers, it's gonna take time and patience and we're going to need to find an unpatched exploit in the HC OS by modifying Gingerbreak or Zerg.
I'll keep you updated as it progresses.
Click to expand...
Click to collapse
I just downloaded again the link for "Drivers" and I connected the Lepan2 again to the computer and the same problem as before.
Then I checked the "File hashes" for the files "WdfCoInstaller01009.dll" and the other 2 inside the folder "amd64" and the cr32/md5/sha-1 are identical for the ones I had downloaded before and this ones. So where are the new ones you said you re-uploaded ?
About the ROM, I am also interested on obtaining the "original" ROM that came with the LepanII, as I updated the system with a still-in-development that Lepan tech support had uploaded to the server without even first testing it, and now I can not revert back to the original because they have not provided to me in a support-ticket I opened at their website. I don't know much about ROM extracting or management but I could learn a thing or two about it.

WHOOOOOOOOOOOOOOOOOOOO!!!!
I got ADB working on the Le Pan 2!!! Screw Le Pan and their locked down drivers!
I can't get root access yet, but I got a sysdump and am combing through it. Recovery doesn't show the device being plugged in and I can't figure out how to get into fastboot as of yet, but progress is being MADE!

There is not rush, in the mean time I opened a ticket at lepan.supportsync.com to see if they supply me with this driver. who knows I may get lucky.

rocketero said:
There is not rush, in the mean time I opened a ticket at lepan.supportsync.com to see if they supply me with this driver. who knows I may get lucky.
Click to expand...
Click to collapse
Been there, done that. Hopefully you'll have better luck, but their standard reply is to email two people from HQ if you are a developer, which I've also been there and done that. They don't reply. I'm fairly positive that we are on our own considering they didn't release the ADB drivers for the LP1 or LP2 as of yet and no source code for either, either. They are GPL-violators to the MAX. *puke*
We'll get it tho.

dbaybay said:
WHOOOOOOOOOOOOOOOOOOOO!!!!
I got ADB working on the Le Pan 2!!! Screw Le Pan and their locked down drivers!
I can't get root access yet, but I got a sysdump and am combing through it. Recovery doesn't show the device being plugged in and I can't figure out how to get into fastboot as of yet, but progress is being MADE!
Click to expand...
Click to collapse
Can you please upload somewhere zip with content of /system/lib/? One of the major problems community have with porting of ICS to any Qualcomm platform is absense of userspace video drivers (and inability to run hw-acceleration). TC979 seems to have hw-accel enabled in Honeycomb, which is quite close to ICS in this area.

ghuron said:
Can you please upload somewhere zip with content of /system/lib/? One of the major problems community have with porting of ICS to any Qualcomm platform is absense of userspace video drivers (and inability to run hw-acceleration). TC979 seems to have hw-accel enabled in Honeycomb, which is quite close to ICS in this area.
Click to expand...
Click to collapse
As soon as I can get ADB working in recovery or fastboot and have root access, I will be glad to, as I already said before. ADB is working when the device is running normally, but I do not have SU privileges. I can see the list of files, but can't copy, push, pull, or anything as of right now. My project for today is to get ADB working in fastboot so I can get root permissions.

dbaybay said:
As soon as I can get ADB working in recovery or fastboot and have root access, I will be glad to, as I already said before. ADB is working when the device is running normally, but I do not have SU privileges. I can see the list of files, but can't copy, push, pull, or anything as of right now. My project for today is to get ADB working in fastboot so I can get root permissions.
Click to expand...
Click to collapse
I thought adb pull /system/lib/ does not require root

ghuron said:
I thought adb pull /system/lib/ does not require root
Click to expand...
Click to collapse
Nor did I, but I'm getting permission denied for about everything except adb reboot [recovery / bootloader] or 'ls'. SU, Pull, Push, Root, Remount, etc. etc. etc. are giving me "permission denied" or "can't in manufactor mode" errors.
I'm working on getting it to work in Fastboot, but ADB just won't recognize the device in Fastboot no matter what I do. I'm at a loss right now, so any suggestions would be helpful. I'm gonna keep trying different methods to get ADB to work with root permissions.
Code:
$ pull /system/lib c:\users\admin\desktop
pull /system/lib c:\users\admin\desktop
pull: permission denied
$
A list of the contents is the best I can get for you atm - http://pastebin.com/ZqvXqE0Q

Those files are exactly what the HP Touch pad needs
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
are you sure you can't install superuser ?

PresidentMcCain said:
Those files are exactly what the HP Touch pad needs
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
are you sure you can't install superuser ?
Click to expand...
Click to collapse
110% positive.
I have no permissions to do anything except CD into folders and get a list, or reboot into recovery or bootloader. In bootloader ADB and fastboot do not recognize the device and the modified drivers do not work. We are working on it, but no such luck as of yet. As soon as I can gain SU permissions in ADB, I'll get you the files, don't worry.

dbaybay said:
110% positive.
I have no permissions to do anything except CD into folders and get a list, or reboot into recovery or bootloader. In bootloader ADB and fastboot do not recognize the device and the modified drivers do not work. We are working on it, but no such luck as of yet. As soon as I can gain SU permissions in ADB, I'll get you the files, don't worry.
Click to expand...
Click to collapse
just a simple question: how do you get out of bootloader mode? After I did "adb reboot bootloader", I got to a black screen with the text "Fastboot Mode" and then nothing works, not even the power button. Can't access it via USB either. Guess I can wait till the battery runs down, but there should be a simpler way...
Edit: never mind, the reset button worked

anonguy2 said:
just a simple question: how do you get out of bootloader mode? After I did "adb reboot bootloader", I got to a black screen with the text "Fastboot Mode" and then nothing works, not even the power button. Can't access it via USB either. Guess I can wait till the battery runs down, but there should be a simpler way...
Click to expand...
Click to collapse
Try holding power button + home button at same time for 10 seconds.

Bootloader/fastboot are the same thing from my understanding. When I use adb reboot bootloader, it reboots to my fastboot screen. I use the reset button, as you figured out to get out of it.
I need to get adb or fastboot.exe [platform tools] working in fastboot mode and I should have root access but no such luck.
Any Le Pan II users who managed to get the v116 update - did you get an update.zip placed on your SD Card that you can share? If I can get an properly signed update.zip with the stock ROM inside, I can most likely modify it for with SU access built in.

this may be a stupid question, does this app http://www.androidapps.com/finance/apps/299480-root-explorer-file-manager-speed-software give you root access or do you need to have root permission in order to use that app.

[Q] Can someone explain QHUSB_DLOAD to me??

From researching around XDA, it looks like a "mode" either the PC or the phone enters into.... but what does it mean or do?
My problem is that when I plug my device into the laptop, it tries to install the necessary drivers, but states that it "Cannot install QHUSB_DLOAD"...
Any knee-jerk ideas as to why this would be? Is this one the drivers I install with the HTC drivers? I installed the drivers that are in the hasoon2000 post which contains the AIO toolkit. The driver file is called: HTC 3.0.0.007. I was thinking I could install it manually if it was a driver from this file....but I also tried to extract it (thinking I would get the necessary inf or .dll files), but it wouldn't let me extract it.
Any help is appreciated...!

http://www.google.nl/search?hl=en&s...s;..0.0...1ac.1j2.6.mobile-gws-hp.I6MZc5Yffqg
Or
http://www.google.nl/search?q=brick...ZSN0wXvoYHQAw&ved=0CAgQ_AUoAQ&biw=360&bih=567
Verstuurd van mijn HTC One S met Tapatalk

It seems you are in a brick! Do not use unlimited.io's tool, just not yet. That will hamper your efforts to rescue your phone.
Use the unbrickig thread in development. You need an Ubuntu LiveCD / Wubi
Sent from my One S using Tapatalk 2

Well that would make sense. The phone is an old 1S which I took for a swim (inadvertently) and it is damaged (it works, but the display is barely operable). Thankfully, I have a brand new replacement from TMO, but the problem is that I <b>really, really need the contents of my SD card</b> from the damaged phone. Before I go through the unbricking procedure, let me ask... Do you know of any simpler way to recover the contents of the SD?? That's all I need. Them I'm shipping it back to TMO.
Regarding a live Ubuntu CD...I have a dual boot setup but it's a debian distro...but I cannot imagine that would be an issue...but I guess I will find out.
Sent from my HTC VLE_U using xda premium

syntropic said:
Well that would make sense. The phone is an old 1S which I took for a swim (inadvertently) and it is damaged (it works, but the display is barely operable). Thankfully, I have a brand new replacement from TMO, but the problem is that I <b>really, really need the contents of my SD card</b> from the damaged phone. Before I go through the unbricking procedure, let me ask... Do you know of any simpler way to recover the contents of the SD?? That's all I need. Them I'm shipping it back to TMO.
Regarding a live Ubuntu CD...I have a dual boot setup but it's a debian distro...but I cannot imagine that would be an issue...but I guess I will find out.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Debian shouldn't really be an issue but I would work with Ubuntu just to be on the safe side. Not sure of a quicker way to rescue the contents of the SD card. Maybe if you enumerate the partitions you can save a copy of the SD card? Not sure though, touch of jobo would be a better person to ask since I am not too experienced with Linux.
I would unbrick it the normal way, unless someone knows otherwise.
Sent from my One S using Tapatalk 2

I wanted to do some testing, but I seem unable to boot into QHSUSB mode. On my other OneS I could do it by holding vol-up while rebooting bootloader, but not anymore.
Look at the downgrade thread. You can skip the step where you have to brick the device.
If you can see your partitions in your devices, you can try and mount the partition directly.
mkdir mydeadsdcard
mount -r -t vfat /dev/hdx36 mydeadsdcard
Chances are you can not see your partitions tho. I think the reason you boot into QHSUSB is that your emmc is defective.
-Jobo

touch of jobo said:
I wanted to do some testing, but I seem unable to boot into QHSUSB mode. On my other OneS I could do it by holding vol-up while rebooting bootloader, but not anymore.
Look at the downgrade thread. You can skip the step where you have to brick the device.
If you can see your partitions in your devices, you can try and mount the partition directly.
mkdir mydeadsdcard
mount -r -t vfat /dev/hdx36 mydeadsdcard
Chances are you can not see your partitions tho. I think the reason you boot into QHSUSB is that your emmc is defective.
Click to expand...
Click to collapse
I actually got it to connect (or I no longer so the QHUSB error). However, when I type adb devices, this is displayed.
C:\HTCOne>adb devices
List of devices attached
HT244W403652 recovery
So.. Is this phone in recovery right now??? (remember my screen is non-functional). And I was running Jellybean 4.2.2 on that phone....I tried "adb pull /mnt/sdcard" "adb pull /storage/sdcard" "adb pull /mnt/sdcard0" and "adb pull /storage/sdcard0"
And in all cases, it reported that the remote object "does not exist". Am I referring to the SDcard correctly??? Or is this an issue with the fact that it seems to be in recovery??
Thanks!!!

syntropic said:
I actually got it to connect (or I no longer so the QHUSB error). However, when I type adb devices, this is displayed.
C:\HTCOne>adb devices
List of devices attached
HT244W403652 recovery
So.. Is this phone in recovery right now??? (remember my screen is non-functional). And I was running Jellybean 4.2.2 on that phone....I tried "adb pull /mnt/sdcard" "adb pull /storage/sdcard" "adb pull /mnt/sdcard0" and "adb pull /storage/sdcard0"
And in all cases, it reported that the remote object "does not exist". Am I referring to the SDcard correctly??? Or is this an issue with the fact that it seems to be in recovery??
Thanks!!!
Click to expand...
Click to collapse
You can try referring to the internal storage using the mmcblk number (mmcblk0p12 is HBOOT for example)
Sent from my One S using Tapatalk 2

usaff22 said:
You can try referring to the internal storage using the mmcblk number (mmcblk0p12 is HBOOT for example)
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
What is the block number for the SD card? I apologize for my ignorance....

syntropic said:
What is the block number for the SD card? I apologize for my ignorance....
Click to expand...
Click to collapse
/dev/block/mmcblk0p36

You're aces...
Sent from my HTC VLE_U using xda premium

Also see here: http://forum.xda-developers.com/showthread.php?t=2091801

touch of jobo said:
Also see here: http://forum.xda-developers.com/showthread.php?t=2091801
Click to expand...
Click to collapse
That's awesome! I had no idea someone had figured that many of them out...
I think i will thumbtack that to my wall.

OK... well here is what happened so far...
I tried using the block number but that wasn't recognized either... apparently the phone was off or actually in recovery (as it says "recovery" after I run "adb devices".
Then I decided to hit the power button. To my surprise, the screen flashed on. It made it all the way through to the home screen and then snapped off.... but I hear text message notifications so I know it is on. When I do "adb devices" now, I get "XXXXXXX offline" (see below for a cut/paste of my shell (I am in dos unfortunately).
C:\Windows\system32>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT244W403652 recovery
C:\Windows\system32>cd\
C:\>adb pull /dev/block/mmcblk0p36 c:\sdcardbak\
remote object '/dev/block/mmcblk0p36' not a file or directory
<<<At this point I powered up the phone... the screen went dead, but the phone is still running. Windows informed me that Linux Gadjet drivers were installed... However, I have no access to a pass-through storage device, and as you can see below, adb states that it is offline.>>>
C:\>adb devices
List of devices attached
HT244W403652 offline
I ran "adb pull /dev/block/mmcblk0p36/ ..." again and I recieved an error: device offline. I don't even know what offline means in this context. I always have USB debugging on this phone and I would be surprised if it wasn't still turned on. So what does offline mean??? Any ideas??
I have to copy this SD card in the next 24 hours and send this non-functioning 1S back to TMO, or they are going to screw me out of $850.....any help is sincerely appreciated!!!!!
EDIT: From a glance around the web and XDA... this seems like a driver issue... however, I just finished rooting my new 1S and everything worked fine. I tried switching USB jacks. As far as rebooting.... I can try, but I doubt the screen will turn on during the boot animation.... from experience it takes about 3 days for the screen to work... then it dies upon hitting the desktop (just like the scenario above). The only thing I can think of doing is installing HTC Sync... it is a longshot, but I cannot think of another solution.

Well HTC Sync didn't make a difference. I still get Error: device Offline when I try to do any action.
Is there any adb expert here who knows something??? I am trying to go through the adb commands (the few listed in windows), and hoping that something can be done.
As mentioned earlier.... I have some very important files on this SD card, and because I have been sent a replacement, I need to return this phone to TMO by thursday morning, or they will debit my card $850. Beyond important files, I also just have several GB of pictures and things that I really hate to lose.
So if there are any talents here who could think out of a box I would really really appreciate it.

syntropic said:
Well HTC Sync didn't make a difference. I still get Error: device Offline when I try to do any action.
Is there any adb expert here who knows something??? I am trying to go through the adb commands (the few listed in windows), and hoping that something can be done.
As mentioned earlier.... I have some very important files on this SD card, and because I have been sent a replacement, I need to return this phone to TMO by thursday morning, or they will debit my card $850. Beyond important files, I also just have several GB of pictures and things that I really hate to lose.
So if there are any talents here who could think out of a box I would really really appreciate it.
Click to expand...
Click to collapse
Are you running a CM10.1 or Android 4.2.2 ROM?
Device offline is usually when you haven't allowed adb to perform operations on your phone.
If yes, once you do adb devices and if USB debugging is enabled, you need to press "always allow from this computer" and "OK" (obviously you have to simulate where the buttons are since your touchscreen doesn't work)
Here's a screenshot from a different device to help you.
{
"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"
}
Sent from my One S using Tapatalk 2

usaff22 said:
Are you running a CM10.1 or Android 4.2.2 ROM?
Device offline is usually when you haven't allowed adb to perform operations on your phone.
If yes, once you do adb devices and if USB debugging is enabled, you need to press "always allow from this computer" and "OK" (obviously you have to simulate where the buttons are since your touchscreen doesn't work)
Here's a screenshot from a different device to help you.
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
Thank you... that's very helpful... I was running a baked bean version I built and that was based on cm10.1/ 4.2.2.
But the only puzzling thing is: (i) I have never seen that message before and yet (ii) was—before the phone was damaged—in ADB all of the time...
So I will trying poking around the screen. I only hope that when the screen goes out it doesn't also render touchscreen non-functional. Since we cannot "wake-up" our phones if they are in sleep mode, right?? We always need to use a hardware button like Power or the volume rocker. But I will give it a shot...
THANKS!

Well, know the screen is on all the time, but there is nothing to see... it is all distorted video... like chomatic noise basically. And I tried several times to run "adb devices" and when I would get
error: device offline
I would try to press the part of the screen I surmised would be correct.
Eventually I launched some app I have on my desktop...so the touchscreen is working.
But I don't think that message is the problem (or rather, I don't think it is coming up).
I know this is not an easy nut to crack, but if you have any other ideas, please let me know. I am going to scour the web for any other posts about offline devices. I just cannot imagine that, since ADB was built for a developer to use from a special shell on the computer that there isn't some way to hack through this....

syntropic said:
Well, know the screen is on all the time, but there is nothing to see... it is all distorted video... like chomatic noise basically. And I tried several times to run "adb devices" and when I would get
error: device offline
I would try to press the part of the screen I surmised would be correct.
Eventually I launched some app I have on my desktop...so the touchscreen is working.
But I don't think that message is the problem (or rather, I don't think it is coming up).
I know this is not an easy nut to crack, but if you have any other ideas, please let me know. I am going to scour the web for any other posts about offline devices. I just cannot imagine that, since ADB was built for a developer to use from a special shell on the computer that there isn't some way to hack through this....
Click to expand...
Click to collapse
So the screen half-works now? Does it show part of the screen?
I would keep trying to get the device online using the accept RSA fingerprint method. You can connect the phone via USB to a different computer with adb. Type adb devices on the cmd/terminal and then the "Accept RSA fingerprint" dialog should come up.

syntropic said:
Am I referring to the SDcard correctly??? Or is this an issue with the fact that it seems to be in recovery??
Click to expand...
Click to collapse
When you boot into recovery, your sdcard is not yet mounted.
Boot your device into recovery.
Get into an adb shell and type 'mount /sdcard'.
In you adb shell, type 'df' (or 'mount') before and after you mount the sdcard partition to make sure it got mounted. Type 'ls /sdcard/' to check whether you can see your files on your sdcard. If your sdcard partition is now properly mounted in recovery, then from your PC you can adb pull /sdcard/
-Jobo

[ Logcat or it didn't happen! ] How To Logcat (updated 9/6/13 - added 4.3 reqmnts)

Ok, so there's a lot of new people in the Blaze forums here on XDA, and that's great! That means we got more people buying a Blaze, which means more popularity, which hopefully means more support.
However, that also means the forums are getting choked up with "X isn't working, how do I fix?" on things that aren't known issues, and certainly are not the norm.
The first thing everybody should do BEFORE flashing a new ROM is to read all posts made by the OP, usually the top 2 or 3. Those contain critical information, directions, known bugs, fixes, downloads, etc.
Once you flash, if you run into a problem, what should you do? Ask about it in the dev forum?
{
"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"
}
Read the ENTIRE post. The whole thing, from page one to the last. If the post is more than 20 pages long and you've spent less than 35 minutes reading it, then FAIL.
Once you've read the entire forum post from front to back and you're 100% sure this hasn't been covered, then should you ask about it?
Not necessarily.
Logcats. Logcats are important. Logcats are Android's method of telling developers
instead of it being a functioning operating system.
Logcatting is easy. Its fun. It makes you feel important when you give the devs something to go off of instead of "duh, it aint workin', bossman!"
So here's how to logcat:
FIRST! You must have the latest version of ADB on your computer. The only surefire way to get ADB that hasn't been compromised or altered in a malicious way is to download it directly with the Android SDK >>>HERE<<<
For the minimalist, you can get ADB and Fastboot only. See @Romman0's post #6
There are installers for Windows, Linux, and OS X.
Prerequisites
You must have the Android SDK and/or ADB on your computer already set up
You must have your phone's drivers installed on your computer
Your phone must be able to boot past the loading screen
You must connect your phone to your computer with the supplied manufacturers USB data/charging cable
How to logcat: Linux, Windows, and OS X
WARNING! With Android 4.3 (CM 10.2 and 10.2-based ROMs), ADB version 1.0.31 is REQUIRED. You can find out your adb version by running:
Code:
~/.android/sdk/platform-tools$ adb version
C:/Android/SDK/platform-tools>adb version
You may also need to fully boot into Android and and accept Debugging from that computer (you will have to check the box marked always accept, or always trust, or something along those lines) and restart your phone to start the logcat
(Pictures coming soon guys, I'm tired lol)
Open up a terminal (Linux or OS X) or a command prompt (Windows).
Navigate to where the Android SDK is installed on. I always install at:
Code:
Linux: [email protected]: ~$: cd ~/.android/sdk/platform-tools
Windows: C:/Windows/System32> cd C:/Android/SDK/platform-tools
OS X: I dont know where, never done it on Android, but I will soon for the sake of this guide
Your location may be different!
type the following command to make sure ADB recognizes your device is connected. If it's not, Google "ADB wont connect to my device"
Code:
Linux: ~/.android/sdk/platform-tools$ adb devices
Windows: C:/Android/SDK/platform-tools>adb devices
If it is connected, power off your phone completely and type the following command:
Code:
Linux: ~/.android/sdk/platform-tools$ adb logcat > {name of logcat here}.log
Windows: C:/Android/SDK/platform-tools>adb logcat > {name of logcat here}.log
I normally name my logcats with a naming convention, example:
logcat-ROM-version-device-date_time_timezone_of_log.log
example:
CM10.1-20130729-UNOFFICIAL-t769-09AUG2013-2033EST.log
This way, when looking at my logcats, I know:
[LIST]
[*]The Rom
[*]The Build Number
[*]The Device
[*]The date and time the logcat was captured
[/LIST]
your terminal/command prompt will say "Waiting for device to connect...". THIS MESSAGE WILL NOT CHANGE! Just trust that the log cat is will start as soon as the adb service on the phone initiates.
Power on your phone as normal
Try to make the problem appear again
When you've catted as much log as you think you need, hit CTRL + C on Linux or Windows (It's probably CMD + C on OS X, as I said, I've never done this on Mac (yet), but I know how they like to be aggravatingly different so that when I'm using Synergy to share a Mouse and Keyboard between Linux, Windows, and OS X, I keep hitting the wrong keystrokes because I re-grew accustomed to whatever OS i'm using as the primary at the moment). Now hit dir.
Upload your logcat for developer review
Now, I know for a fact that Samsung USB Drivers and ADB communicate perfectly well with the Blaze using the following operating systems. I have tested them personally.
Ubuntu 12.04 x64
Ubuntu 12.10 x64
Ubuntu 13.04 x64
Fedora 17 x64
Fedora 18 x64
Fedora 19 x64
Windows 7 x64
Windows 8 x64
Windows 8.1 Developer Preview x64
I will test out OS X 10.8.4 tomorrow and make sure it works for certain-like
That's it. Any questions, comments, gripes, or complaints? Write your congressman!

Reserved: Because I Can!

I am so happy you did this.
Edit: You should ask a mod to pin this. This is really useful and should be on the top when needed.

Thank you so much for this. I've never been completely sure how to get a logcat, and always felt kind of worthless because of this. Thanks again!
Sent from a Paranoid Blaze

Very nice!
While Windows-specific, beyond this the next best reference I've found was this - just a nice link for sdk/logcat info.
Again, great job on getting this around. Stuff like this should be standard sticky/first post stuff for just about any forum

Here is a modified minimalist version of adb, if anybody wants it.......
http://forum.xda-developers.com/showthread.php?t=2317790

Pin request sent to a mod. here's hoping!
On an additional note, I dont exactly like how it looks and I've never been good with BBcode formatting... is HTML allowed on XDA???
---EDIT---
And we're pinned! Thanks, Naddict

I've read that terminal emulator can do a logcat as well, is that true? Is it the same as doing a logcat through this method?
Sent from a Paranoid Blaze

njstein said:
I've read that terminal emulator can do a logcat as well, is that true? Is it the same as doing a logcat through this method?
Sent from a Paranoid Blaze
Click to expand...
Click to collapse
yes, if running from terminal emulator:
Code:
logcat > /sdcard/logcat.log
That will place the logcat on the root of your SD Card.

jparnell8839 said:
yes, if running from terminal emulator:
Code:
adb logcat > /sdcard/logcat.log
That will place the logcat on the root of your SD Card.
Click to expand...
Click to collapse
Just thought I'd mention the adb shouldn't be there if running from terminal emulator

dwitherell said:
Just thought I'd mention the adb shouldn't be there if running from terminal emulator
Click to expand...
Click to collapse
thanks... dont know what I was thinking :silly:
BTW...
POST # 500!!!!

Okay, call me dumb if you want to but I have a question. As I do not have a manufacturers USB cord, I cannot use this method. However, I'm tired of being useless, can I use CatLog from the Play Store?
It appears to have the ability to record logs, but I honestly have no clue if it's the same thing.

FroBreadCreamJellyPie said:
Okay, call me dumb if you want to but I have a question. As I do not have a manufacturers USB cord, I cannot use this method. However, I'm tired of being useless, can I use CatLog from the Play Store?
It appears to have the ability to record logs, but I honestly have no clue if it's the same thing.
Click to expand...
Click to collapse
Yes. But adb is needed to debug booting issues. Catlog will work fine capturing logs for bugs on working roms.

Romman0 said:
Yes. But adb is needed to debug booting issues. Catlog will work fine capturing logs for bugs on working roms.
Click to expand...
Click to collapse
Awesome, thank you.

FroBreadCreamJellyPie said:
Okay, call me dumb if you want to but I have a question. As I do not have a manufacturers USB cord, I cannot use this method. However, I'm tired of being useless, can I use CatLog from the Play Store?
It appears to have the ability to record logs, but I honestly have no clue if it's the same thing.
Click to expand...
Click to collapse
a manufacturers cord is recommended because it's known and proven to work as is, however, I can tell you that I have yet to run across a MicroUSB cable that didn't work for strictly adb purposes, and I've only seen very few that wouldn't charge my phone.

jparnell8839 said:
a manufacturers cord is recommended because it's known and proven to work as is, however, I can tell you that I have yet to run across a MicroUSB cable that didn't work for strictly adb purposes, and I've only seen very few that wouldn't charge my phone.
Click to expand...
Click to collapse
Then in that case, I'm doing something terribly wrong, lol thanks anyways

Lol
Gửi từ GT-S5360 của tôi bằng cách sử dụng Tapatalk 2

[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?

Nexus 5 WiFi problem...acting strange....turning ON / OFF and Power ON/ OFF

Gentlemen/ Ladies,
I am NOT a developer, in fact I need a little help here, and searching all over internet, I bet you guys are probably the last resort of true assistance to my problem.
I am a proud Nexus 5 (Hammerhead) phone user, yes, still Nexus 5 because it is such a good reliable phone.
But started the day before, the WiFi is turning itself OFF, and although I tried turning it ON, it just keep searching and searching (where the screen usually display all WiFi networks around, it just shows a energy-bar running from left to right, while bottom is pretty much blank except saying turning ON wifi).
The phone then shutting down itself, OR I have to turn the phone OFF, wait to power ON again, sometimes WiFi works , sometimes it does not, or turn if OFF itself after a few minutes. when it's back ON, it works normally for a short time, then OFF again....
All other functions of the phone are flawless, blue tooth, my t-mobile LTE, have no problems.
At this stage, I can’t tell, it is a software and hardware error.
Did’nt drop on the floor, no water damages, no crack on screen, I have been use it nicely. I noticed the battery drinks fast, and I worried that this problem is the result of bad battery/ shutting down due to empty battery, so yesterday I finally replaced the battery with a brand new one.
I checked my charter internet modem, and wireless router, all seems to be ok, as my other PC and laptop both using hard cable and wireless, other cell phone also use the same WiFi at home, they all function OK.
I ran malwarebytes and panda anti-virus on the Nexus 5, no virus.
I tried suggestions from youtube:
-turn the airplane mode ON/OFF
-turn t mobile, bluetooth ON/OFF
-reset network connection, ( that only brings my t mobile ON)
-Developer mode ON, select legacy DHCP,
As you notice, it’s a Nexus, it still runs on Android 6.01 version, not the latest. And I really do not want to “manufacturer re-set” back to original setting, just too much work, not to mention, a reality that I may not able to get updates from Android as the version is old, which really put me in a more difficult position. I am financially tight now and hoping to continue to use this Nexus 5 for another year before I can afford a new phone.
I also noticed from the website here, there is a "FirstEver" Andriod 8.1 for nexus 5 hammerhead available, Will it solve my WiFi problem/ error? Also, it will be nice for my Nexus 5, right? My phone is still running on Android 6 !
Any suggestions, please. Thank you all !

Hello, unfortunately this was very common on the nexus 5. It is a hardware issue. It has something to do with the WiFi chip that's on the motherboard.
It happened to me and funny enough I'm responding to you on that same Nexus 5.
My solution was to buy a used (damaged external) Nexus with functioning internals; CPU, motherboard, BT, WiFi etc etc and then swap out the damage motherboard with the used one. You would have to either flash/reset an OS on the replacement motherboard to "clean" it up.
There's a few tutorials here on XDA on how to disassemble the the back and battery removal. Do a quick search on Google with the addition of "XDA" on the end of the search criteria. The search bar here on XDA is terrible.
Good luck.

Mojar7070 said:
Hello, unfortunately this was very common on the nexus 5. It is a hardware issue. It has something to do with the WiFi chip that's on the motherboard.
It happened to me and funny enough I'm responding to you on that same Nexus 5.
My solution was to buy a used (damaged external) Nexus with functioning internals; CPU, motherboard, BT, WiFi etc etc and then swap out the damage motherboard with the used one. You would have to either flash/reset an OS on the replacement motherboard to "clean" it up.
There's a few tutorials here on XDA on how to disassemble the the back and battery removal. Do a quick search on Google with the addition of "XDA" on the end of the search criteria. The search bar here on XDA is terrible.
Good luck.
Click to expand...
Click to collapse
@Mojar7070,
Thanks for yr reply.
My situation is WiFi sometimes works, sometimes it does'nt. That's why it is difficult for me to determine IF it is a hardware/software issue. Do you think by replacing the pair antenna will work?
https://www.ebay.com/itm/1-Pair-Wir...-LG-Google-Nexus-5-D820-D821-USA/252497470238
I hear what you said, it just that it is difficult to determine the used one truly does not have other hardware error inside, until it's too late, more importantly, I am not someone who is really good in repairing hardware.
Can you share with me how do I go by backing-up the whole Android OS + all data onto my computer? Especially the Android OS....
Million thanks,

Hello, I don't think the wire itself is the issue. You can try, I'm just not sure.
Do you have custom recoveryOr at least have have the boot bootloader unlocked on your phone??
Having TWRP recovery simplifies everything as far as backing up information on the phone.
Your options for downloading from your phone is limited since WiFi is broke. Do you have some data room to upload information to Google backup?? That may be your only option, especially if you're not on a custom recovery.

Mojar7070 said:
Hello, I don't think the wire itself is the issue. You can try, I'm just not sure.
Do you have custom recoveryOr at least have have the boot bootloader unlocked on your phone??
Having TWRP recovery simplifies everything as far as backing up information on the phone.
Your options for downloading from your phone is limited since WiFi is broke. Do you have some data room to upload information to Google backup?? That may be your only option, especially if you're not on a custom recovery.
Click to expand...
Click to collapse
Hello,
Thanks for yr replies.
At this stage, I don't a custom recovery/ boot-loader/ TWRP, BUT see this link below especially step 4 and 5 are exactly what you are saying?! :
https://www.firstever.eu/first-ever-android-8-1-for-nexus-5/#comment-113
If I go get the Android 8 thru them now, it seems to me step 4 & 5 cover what you just mentioned !?
But the thing is, from logical thinking, I should be backing up FIRST, in case if anything don't work out ! Right ?? I know Windows PC, not anroid phones/ OS !!
You are right ON, unless I want to pay more $ for data thru T-mobile LTE for this backup....
When I connect the phone to my PC thru USB, seems to me all things are presented. Can I just copy/ paste onto a folder I create on my PC, but I take it that's NOT bootable ? Or should then put it onto a USB flash drive to make it bootable?
Thank you,

STDupont said:
Hello,
Thanks for yr replies.
At this stage, I don't a custom recovery/ boot-loader/ TWRP, BUT see this link below especially step 4 and 5 are exactly what you are saying?! :
https://www.firstever.eu/first-ever-android-8-1-for-nexus-5/#comment-113
If I go get the Android 8 thru them now, it seems to me step 4 & 5 cover what you just mentioned !?
But the thing is, from logical thinking, I should be backing up FIRST, in case if anything don't work out ! Right ?? I know Windows PC, not anroid phones/ OS !!
You are right ON, unless I want to pay more $ for data thru T-mobile LTE for this backup....
When I connect the phone to my PC thru USB, seems to me all things are presented. Can I just copy/ paste onto a folder I create on my PC, but I take it that's NOT bootable ? Or should then put it onto a USB flash drive to make it bootable?
Thank you,
Click to expand...
Click to collapse
Hello,
Yes, steps 4 and 5 from that site is what I'm referring to. Like I've mentioned before search here on XDA for actually guides and tutorials.
Installing TWRP recovery is the very first step in "fully" backing up your device. Data, OS, user preference and all apps. Plugging into a PC and moving personal folders and files is just that. Transferring files and folders. Now, you can definitely do that and have your personal data on the PC but if you plan to install the 8.1 Android OS anyways you'll need TWRP recovery. So why not "kill two birds with one stone."
You are correct, simply transferring files/folders will not translate to a bootable medium. Having a TWRP backup will do just that. It will act like a "bootable" file whenever you need to roll back to a previous state.
Once you search a guide/tutorial, you'll find that the whole process is done through a PC. So you'll be fine. But please read through the guides first and get familiar with the process before typing any commands in.
Good luck.

Mojar7070 said:
Hello,
Yes, steps 4 and 5 from that site is what I'm referring to. Like I've mentioned before search here on XDA for actually guides and tutorials.
Installing TWRP recovery is the very first step in "fully" backing up your device. Data, OS, user preference and all apps. Plugging into a PC and moving personal folders and files is just that. Transferring files and folders. Now, you can definitely do that and have your personal data on the PC but if you plan to install the 8.1 Android OS anyways you'll need TWRP recovery. So why not "kill two birds with one stone."
You are correct, simply transferring files/folders will not translate to a bootable medium. Having a TWRP backup will do just that. It will act like a "bootable" file whenever you need to roll back to a previous state.
Once you search a guide/tutorial, you'll find that the whole process is done through a PC. So you'll be fine. But please read through the guides first and get familiar with the process before typing any commands in.
Good luck.
Click to expand...
Click to collapse
Hello,
Thank you for yr confirmation, I was not sure, but you strengthen my thought.
Would you please pinpoint to me just where exactly I can read the "guide/ tutorial" section that applies in my situation? This website is so big, I almost "lost in ocean" here....
I will first backup my Nexus 5 today, and waiting for yr "guide/ tutorial" section, mostly like do the installation android 8.1 either Monday night or tuesday night. I notice the guy at FirstEver already produced his custom Android 9.0 version, but it is too new for me, I am thinking he is still perfecting his version, just a thought !
Have you tried the new 9.0 Android yet?
Thank you,

Mojar7070 said:
Hello,
Yes, steps 4 and 5 from that site is what I'm referring to. Like I've mentioned before search here on XDA for actually guides and tutorials.
Installing TWRP recovery is the very first step in "fully" backing up your device. Data, OS, user preference and all apps. Plugging into a PC and moving personal folders and files is just that. Transferring files and folders. Now, you can definitely do that and have your personal data on the PC but if you plan to install the 8.1 Android OS anyways you'll need TWRP recovery. So why not "kill two birds with one stone."
You are correct, simply transferring files/folders will not translate to a bootable medium. Having a TWRP backup will do just that. It will act like a "bootable" file whenever you need to roll back to a previous state.
Once you search a guide/tutorial, you'll find that the whole process is done through a PC. So you'll be fine. But please read through the guides first and get familiar with the process before typing any commands in.
Good luck.
Click to expand...
Click to collapse
Hello Mojar7070,
I ran into some difficulties as I am trying to back-up, seeking guidance:
On Step4 of the FirstEver pages-https://www.firstever.eu/first-ever-android-8-1-for-nexus-5/#
When I typed adb root bootloader, on my DOS black screen of my computer, it says:
"adb" is not recognized as in internal or external command operable program or batch file.
Earlier, as I was doing the ADB , step 9 and step 10 did not pop up, but it did say completed in blue little screen, I did that 3 times, same thing, following their instruction as below:
https://androidmtk.com/download-best-android-adb-driver
Any suggestions ? Thank you,

STDupont said:
Hello Mojar7070,
I ran into some difficulties as I am trying to back-up, seeking guidance:
On Step4 of the FirstEver pages-https://www.firstever.eu/first-ever-android-8-1-for-nexus-5/#
When I typed adb root bootloader, on my DOS black screen of my computer, it says:
"adb" is not recognized as in internal or external command operable program or batch file.
Earlier, as I was doing the ADB , step 9 and step 10 did not pop up, but it did say completed in blue little screen, I did that 3 times, same thing, following their instruction as below:
https://androidmtk.com/download-best-android-adb-driver
Any suggestions ? Thank you,
Click to expand...
Click to collapse
https://forum.xda-developers.com/go...ide-nexus-5-how-to-unlock-bootloader-t2507905
https://forum.xda-developers.com/google-nexus-5/general/how-to-nexus-5-one-beginners-guide-t2510966
Hello,
Try out 1 or both of the links above. That should get you started in the right direction.
---------- Post added at 03:28 AM ---------- Previous post was at 03:26 AM ----------
Mojar7070 said:
https://forum.xda-developers.com/go...ide-nexus-5-how-to-unlock-bootloader-t2507905
https://forum.xda-developers.com/google-nexus-5/general/how-to-nexus-5-one-beginners-guide-t2510966
Hello,
Try out 1 or both of the links above. That should get you started in the right direction.
Click to expand...
Click to collapse
https://forum.xda-developers.com/go...ol-tool-one-driversunlocktwrpfactory-t3358707
Try this one as well. It's an all in one root tool.
Good luck.

Mojar7070 said:
https://forum.xda-developers.com/go...ide-nexus-5-how-to-unlock-bootloader-t2507905
https://forum.xda-developers.com/google-nexus-5/general/how-to-nexus-5-one-beginners-guide-t2510966
Hello,
Try out 1 or both of the links above. That should get you started in the right direction.
---------- Post added at 03:28 AM ---------- Previous post was at 03:26 AM ----------
https://forum.xda-developers.com/go...ol-tool-one-driversunlocktwrpfactory-t3358707
Try this one as well. It's an all in one root tool.
Good luck.
Click to expand...
Click to collapse
Hello Mojar7070,
From the first link you gave me, I ran into more difficulties....( the instruction of that link is no where near the actual scene I ran into....see below 1-5 )
I clicked the download link for Android SDK, my plan was first to get the ADB working.
I got the Android Studio thing that's about over 1GB,
From the link-ADB and Fastboot Installation
1. Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks @El Daddy)
Link removed since it expired
2. Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
3. Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
4. Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
5. To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are ....
#2-5 are no where like that at all. See the photo below:
{
"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"
}
After the download installation, i got the first photo, double click to install, took more than hour and half, finally says cannot be done, see photo #2, also during installtion, see Java error.
What did i do wrong??

STDupont said:
Hello Mojar7070,
From the first link you gave me, I ran into more difficulties....( the instruction of that link is no where near the actual scene I ran into....see below 1-5 )
I clicked the download link for Android SDK, my plan was first to get the ADB working.
I got the Android Studio thing that's about over 1GB,
From the link-ADB and Fastboot Installation
1. Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks @El Daddy)
Link removed since it expired
2. Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
3. Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
4. Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
5. To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are ....
#2-5 are no where like that at all. See the photo below:
After the download installation, i got the first photo, double click to install, took more than hour and half, finally says cannot be done, see photo #2, also during installtion, see Java error.
What did i do wrong??
Click to expand...
Click to collapse
Hello,
I think you should try the last link. The all in one tool. I know it took me a few times to figure out how to correlate the instructions to what is on the PC screen. The all in one tool simplifies everything.
You can YouTube the tutorials as well get a step by step process.
Good luck.

Hello,
Seems to me that All-In-1 tool can do many things.
But in my situation now, i first need to get the ADB works otherwise I cannot move forward getting back-up, does that "install driver" will get the adb works? If not, which function should I select?
Thanks,

Mojar7070 said:
Hello,
I think you should try the last link. The all in one tool. I know it took me a few times to figure out how to correlate the instructions to what is on the PC screen. The all in one tool simplifies everything.
You can YouTube the tutorials as well get a step by step process.
Good luck.
Click to expand...
Click to collapse
Hello Mojar7070,
Just now, i tried SDK thing again, noticed that JAVA error, i went ahead the got the latest JAVA April 2019 version, this time, the SDK went ok without any error this time.
My question is: when I go back to DOS, to type the cmd command(s) according the FirstEver's instruction #4/ 5, how do I use the SDK thing to solve the " adb is not recognized as an internal or external command operable program or batch file" error ??
Thank you,

STDupont said:
Hello Mojar7070,
Just now, i tried SDK thing again, noticed that JAVA error, i went ahead the got the latest JAVA April 2019 version, this time, the SDK went ok without any error this time.
My question is: when I go back to DOS, to type the cmd command(s) according the FirstEver's instruction #4/ 5, how do I use the SDK thing to solve the " adb is not recognized as an internal or external command operable program or batch file" error ??
Thank you,
Click to expand...
Click to collapse
Gentelmen/ Ladies,
I truly need some help here !
FYI, I did not try the last link, as it seems more complicated and does not looks like it can solve my situation.
I am stuck, first link: downloaded and installation the thing SDK, tried typing the command in DOS, same thing. It is very very frustrated when the instruction(s) are no where near the actual thing from what I see....
Anyone here located near downtown Los Angeles ? Thank you...