Related
Hi folks,
Since last thursday I've got a problem with my WiFi on my wildfire. Every time I turn on the WiFi (via not. bar or settings) the little box is ticked but it does not scan or anything. A couple of seconds later I get the message that the WiFi process in the settings app is not responding together with the option to kill the process. Is my WiFi broken now? Or is there a fix?
Thanks in advance
P.S. I'm using CM7 7.1.0
Try flashing the latest nightly or the 7.1.0.1 update.
http://forum.xda-developers.com/showthread.php?t=1143125
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
Try flashing the latest nightly or the 7.1.0.1 update.
http://forum.xda-developers.com/showthread.php?t=1143125
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
It doesn't work. When I boot after applying the update after the bootanimation there's just a black screen. It hangs. I pulled the bat and tried it again but the same...
Usually this can be solved by wiping the dalvik cache, have you tried that?
henkdv said:
Usually this can be solved by wiping the dalvik cache, have you tried that?
Click to expand...
Click to collapse
I managed to update CM7 to 7.1.0.1, but Wi-Fi is still not working! It just hangs after switch-on. And the weirdest thing of all is that it just happened, I dind't change anything or install any new apps...
Try reflashing the radio?
3xeno said:
Try reflashing the radio?
Click to expand...
Click to collapse
Reflashed the radio, still no progress It just wont find any wifi networks and after leaving the settings app the WiFi is turned off automatically (or the app hangs and the same happens) Any other suggestions?
By the way, WiFi-Tethering does work. Still confused about this weird problem :S
Try this in a root shell (enter "su" at the prompt) with wifi enabled:
ip link set up eth0
Though the name might be different on your rom, it's commonly named "wlan0" (eth0 is usually a physical ethernet device). You can find out by running
ip link show
With wifi disabled and enabled, see what new device comes up or disappears. It doesn't hurt to test a name, as long as it isn't "lo" (the loopback device).
After setting the link state, re-scan for APs.
henkdv said:
Try this in a root shell (enter "su" at the prompt) with wifi enabled:
ip link set up eth0
Though the name might be different on your rom, it's commonly named "wlan0" (eth0 is usually a physical ethernet device). You can find out by running
ip link show
With wifi disabled and enabled, see what new device comes up or disappears. It doesn't hurt to test a name, as long as it isn't "lo" (the loopback device).
After setting the link state, re-scan for APs.
Click to expand...
Click to collapse
Could you explain these steps? I'm not so familiar with terminal inputs and especially IP adresses. Whats more strange is that my Wi-Fi disconnects automatically when leaving the Wi-Fi menu and that it doesn't show my saved accesspoints (once connected but not now). Isn't this a software problem?
tobitronics said:
Could you explain these steps?
Click to expand...
Click to collapse
Sure, here's the html formatted manual page. A relevant excerpt:
ip link set - change device attributes
dev DEVICE
DEVICE specifies network device to operate on. When configuring
SR-IOV Virtual Fuction (VF) devices, this keyword should specify
the associated Physical Function (PF) device.
up and down
change the state of the device to UP or DOWN.
Click to expand...
Click to collapse
When the device is down, it won't scan. Some ROMs have a different tool installed as /system/bin/ip though, just typing "ip" will tell you.
tobitronics said:
Whats more strange is that my Wi-Fi disconnects automatically when leaving the Wi-Fi menu and that it doesn't show my saved accesspoints (once connected but not now).
Click to expand...
Click to collapse
The saved networks aren't shown when wifi is turned off. It likely fails to enable the device and does this before attempting to read the saved networks, as this should never happen it might be related to the radio firmware on your phone. See this thread for the list of radio firmware versions. As for disconnecting when you leave the WifiSettings activity, wait a bit longer to see if it stays connected. There's definitely no intentional disconnect in the onPause handler.
tobitronics said:
Isn't this a software problem?
Click to expand...
Click to collapse
I see no reason to believe the contrary.
henkdv said:
Sure, here's the html formatted manual page. A relevant excerpt:When the device is down, it won't scan. Some ROMs have a different tool installed as /system/bin/ip though, just typing "ip" will tell you.The saved networks aren't shown when wifi is turned off. It likely fails to enable the device and does this before attempting to read the saved networks, as this should never happen it might be related to the radio firmware on your phone. See this thread for the list of radio firmware versions. As for disconnecting when you leave the WifiSettings activity, wait a bit longer to see if it stays connected. There's definitely no intentional disconnect in the onPause handler. I see no reason to believe the contrary.
Click to expand...
Click to collapse
I've tried your steps. When setting the IP link to up after switching on WiFi and then enter 'show' i get a whole page of numbers and complicated text, but in each line the State is specified as 'DOWN' or 'UNKNOWN'. It also says something about a loop? When I leave the terminal then to check if WiFi is still on, I find it turned off. When I turn it back on and then let the terminal show, sometimes I get 'DORMANT' and sometimes I get 'DOWN'. I also tried your suggestion about leaving the client on, it stays on for about a minute before it automatically disconnects or gives me the message that the system app is not responding. My radio is already up to date (I even reflashed it twice). And what was that link 'WiFiSettings activity'. I came to a website with lots of code and got immediately confused . I hope this problem can be solved....
tobitronics said:
When setting the IP link to up after switching on WiFi and then enter 'show' i get a whole page of numbers and complicated text, but in each line the State is specified as 'DOWN' or 'UNKNOWN'.
Click to expand...
Click to collapse
This is the RFC2863 state of the interface which is seldom relevant, the actual link state is between < and >.
tobitronics said:
It also says something about a loop?
Click to expand...
Click to collapse
That would be the loopback device. It is always present and its parameters are the same across nearly all Linux kernels, one might be funny and try to change the mtu, queueing discipline or address but it's pointless to do so.
tobitronics said:
When I leave the terminal then to check if WiFi is still on, I find it turned off. When I turn it back on and then let the terminal show, sometimes I get 'DORMANT' and sometimes I get 'DOWN'.
Click to expand...
Click to collapse
According to the documentation, DORMANT means
Interface is L1 up, but waiting for an external event, f.e. for a protocol to establish. (802.1X)
Click to expand...
Click to collapse
This could indicate a problem with wpa_supplicant rather then the radio firmware. Try to connect to an open AP such as the ones at the local Bakker Bart, NS station, McDonalds or T-Mobile shop.
tobitronics said:
I also tried your suggestion about leaving the client on, it stays on for about a minute before it automatically disconnects or gives me the message that the system app is not responding. My radio is already up to date (I even reflashed it twice). And what was that link 'WiFiSettings activity'. I came to a website with lots of code and got immediately confused .
Click to expand...
Click to collapse
It is the actual source code to "Wi-Fi settings" where you normally see the list of networks.
Thanks for your explanation. So what should I do/try now? I was thinking about reinstalling the settings.apk and settingsprovider.apk ....
Sent from my HTC Wildfire using XDA App
Like I said, try an open 802.11a/b/g access point.
henkdv said:
Like I said, try an open 802.11a/b/g access point.
Click to expand...
Click to collapse
I tried that at the McDonald's and it didn't want to search for available networks, so I couldn't connect
Go to settings > Wireless & Networks. Disable this option
Mobile network
Use phone for data connection when Wi-Fi is unavailable
It should change to
Mobile network
Connect to the Internet
Try going to /data/misc/wifi and rename the wpa_supplicant.conf to wpa_supplicant.conf.bak and try again, the system will recreate the file.
Sent from my HTC Wildfire using XDA App
Takudenatsu said:
Try going to /data/misc/wifi and rename the wpa_supplicant.conf to wpa_supplicant.conf.bak and try again, the system will recreate the file.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
IT WORKSSS!!!! Thank you all for your help. That such a small little text file could cause such a large annoying problem. I hope it won't happen again...
Sent from my HTC Wildfire using XDA App
could you write how?
I have a big problem on my HTC Droid Incredible.
Bypassing the activation screen really irritates me and i can't turn on the USB Debugging which is the key to root and s-off my phone and to bypass the activation screen.
The procedure i did for bypassing the activation screen are: tap 4 corners, safe mode, call *228 and end call after few seconds (did this several times), cdma workshop, ##778 change the nam setting, and non of them works for me.
cmlusco member of xda told me that the best way to bypass it is to change the build.prop in any rom i'm going to flash on my phone. Then he give me this link http://forum.xda-developers.com/showthread.php?t=1306400 and i think this is it, but in the end still failed because i need to turn on my USB Debugging.
Please help me to bypass my Droid Incredible.
I'm here in Philippines and there is no Verizon network provider here.
I already solve this problem and I can use my Droid Incredible. Sweet!!!View the 3rd post how did i do that.
Click to expand...
Click to collapse
are you able to fix this?im having EXACTLY the same problem.
yup I already fix it, just follow this procedure.
1) try to enable usb debugging mode by doing this procedures.
for this,you should need wi-fi.
so,let's start
1)when the phone calls to *228 tap contacts icon,right to the "end call"
2)try to add a new contact and enter facebook or other socialnet dialog.
phone asks you to enable wifi, do this and connect your wifi network
3)next hold the search button and (via voice search) search in google "market"
4)tap to the official market page, phone asks you about opening this page,choose market app.login in the google accounts,if you need.
5)search in market "usb debug" app. install it and tap "open' in the market app
6)enable usb debugging and enjoy)
and for those who don't have a wifi connection in there home, this procedure is for you.
1. call *228 and tap the contact on the right side of end call.
2. add contact and put any information.
3. try to connect it in facebook to prompt the setting window.
4. tap setting.
5. tap search softkey and type application.
6. finally you can enable usb debugging without any problem.
thanks to ramazancik94 for giving this life saver step for enabling usb debugging mode.
2) root and s-off your phone by following this procedure root 2.3.4,downgrade,and s-off
3) if you already have CWM, rooted, and s-off your phone try to install some ROM using CWM in development section. Double check if your phone is s-off via hboot (press and hold power button and volume down), your phone is rooted if you install CWM, and find some ROM that suits your need.
4) Try to use the "end call bypass" if this method doesn't work with you this will be your last resort. Delete the phone.apk before you install the rom, to delete the phone.apk open the "blah blah blah rom.zip" and go to data> system app> find phone.apk and please don't extract the rom and delete the phone.apk or i won't work, just delete it from the zip.
Note: Deleting the phone.apk will result for disable your phone signal. So you're going to use your phone for music, game, watch some movies and wifi internet. You won't be able to use it for call, text and mobile data, and also please read it carefully so you won't **** your phone. You've been warned
For more information visit this thread: help bypass the activation
All big thanks to cmlusco, ramazancik94 and tiny4579 for their help
need help
sir maybe you can help me with this...im new to android phones and i dont think i can make it
can you please send me the step by step procedure of the things i need to do after i put my phone in USB debugging mode?hope you dont mind
my email is [email protected]
my tcp account is kian0926, im here in the Philippines as well and im glad that you were able too fix yours, hoping that i can use mine as well, saving this device from a trash can
many thanx in advance...
i can't get my ADB working
after i extracted mini-adb under c drive (c:\mini-adb_inc) i extracted adb inside of it
but icant get adb working
when i tried to open adb it just flashes (like blink of an eye) and closes itself immediately
i cant proceed
pls help..............
Kian0926 said:
i can't get my ADB working
after i extracted mini-adb under c drive (c:\mini-adb_inc) i extracted adb inside of it
but icant get adb working
when i tried to open adb it just flashes (like blink of an eye) and closes itself immediately
i cant proceed
pls help..............
Click to expand...
Click to collapse
You cant just click on the adb.exe file, it is a cmd line program. Open a cmd prompt on your pc and type " cd C:\mini-adb_inc " then type in your adb command, example " adb devices " this should show the serial number of your phone if connected to the pc and adb and drivers are setup correctly.
thnx for the reply
but this " cd C:\mini-adb_inc " seems to be invalid when im trying to enter n the command prompt window
i already tried removing those that i downloaded and download them again but still the same thing...
---------- Post added at 02:19 AM ---------- Previous post was at 02:11 AM ----------
also inside of mini-adb extracted on my c drive theres no adb.exe.it just say's adb
under that is AdbWinApi....so cunfused now
Kian0926 said:
thnx for the reply
but this " cd C:\mini-adb_inc " seems to be invalid when im trying to enter n the command prompt window
i already tried removing those that i downloaded and download them again but still the same thing...
---------- Post added at 02:19 AM ---------- Previous post was at 02:11 AM ----------
also inside of mini-adb extracted on my c drive theres no adb.exe.it just say's adb
under that is AdbWinApi....so cunfused now
Click to expand...
Click to collapse
What makes you think the cd command didnt work, did it give an error? All cd does is change the directory to C:\mini-adb_inc where the adb file is located. It is ok if it says just adb and not adb.exe, your pc is just set to hide extensions. When you first open the cmd prompt to the left of where you type it will say something like C:\users\your_user_name\desktop >, when you type cd C:\mini-adb_inc it should go to the next line, and to the left of where you type now it should say C:\mini-adb_inc >Then type adb devices and see if a serial number comes up.
"C:\users\your_user_name\desktop" his is what i exactly saw on my laptop and when i tried enterring "c:\mini-adb_inc" a message appears say's like "incorrect path/directory"
im gonna try using another PC and hope this time it works..
Kian0926 said:
"C:\users\your_user_name\desktop" his is what i exactly saw on my laptop and when i tried enterring "c:\mini-adb_inc" a message appears say's like "incorrect path/directory"
im gonna try using another PC and hope this time it works..
Click to expand...
Click to collapse
You have to type " cd C:\mini-adb_inc " or what ever the path is to the adb file. here actually try this. Go to the folder where the adb file you unziped is. Then hold ctrl + shift and right click on an empty space in that folder, and select open cmd prompt here. then type in your adb command, ie adb devices.
after i successfully activated,rooted to 2.3.7 with cm7 ROM my droid incredible it was working perfectly fine,but after a couple of hours using my droid it unexpectedly shut itself down and left me with just a blinking orange led at the top of it..last application running is viber,im on a call actually..and my phone is on charge...
what might be the cause of it?and can this be fixed?..my phone is completely dead
i even tried resetting the phone(pressing volume down button and power button but still no reponse..
Kian0926 said:
after i successfully activated,rooted to 2.3.7 with cm7 ROM my droid incredible it was working perfectly fine,but after a couple of hours using my droid it unexpectedly shut itself down and left me with just a blinking orange led at the top of it..last application running is viber,im on a call actually..and my phone is on charge...
what might be the cause of it?and can this be fixed?..my phone is completely dead
i even tried resetting the phone(pressing volume down button and power button but still no reponse..
Click to expand...
Click to collapse
Sorry to say, but if you cant enter hboot, or boot up to the os or recovery, then the phone is more thsn likley bricked. Unless its a battery issue. Does it vibrate at all when trying to start?
Kian0926 said:
after i successfully activated,rooted to 2.3.7 with cm7 ROM my droid incredible it was working perfectly fine,but after a couple of hours using my droid it unexpectedly shut itself down and left me with just a blinking orange led at the top of it..last application running is viber,im on a call actually..and my phone is on charge...
what might be the cause of it?and can this be fixed?..my phone is completely dead
i even tried resetting the phone(pressing volume down button and power button but still no reponse..
Click to expand...
Click to collapse
Does it boot when plugged in? There MAY be some help if it can boot when connected to AC power.
Kian0926 said:
after i successfully activated,rooted to 2.3.7 with cm7 ROM my droid incredible it was working perfectly fine,but after a couple of hours using my droid it unexpectedly shut itself down and left me with just a blinking orange led at the top of it..last application running is viber,im on a call actually..and my phone is on charge...
what might be the cause of it?and can this be fixed?..my phone is completely dead
i even tried resetting the phone(pressing volume down button and power button but still no reponse..
Click to expand...
Click to collapse
I've experience this, just a blinking orange led. What did I do was i charge it and a couple of minute the the blinking orange led stops and it become a steady orange led.
Easier way (offline)
Found what could be an easier way, I'm playing with my sister's incredible and I can get usb debugging enabled by using any of the official verizon update packages (could be a rom, but I downloaded the smallest hboot upgrade from htcdev), it appears to send some commands in usb mode that trigger the activation of usb debugging, what's funny if that if you either disconnect before it's done, or it fails, it leaves usb debugging on.
Non-sense.
EDIT: You just have to open the utility, you don't to flash or disconnect.
Such and old thread but I have a Incredible that a friend gives me and I couldn't access the market app by search function. What I did was search anything with voice commands, then a navigator window opens and change the URL to: market://details?id=usb, it opens the market app and I can install the USB debug app
Simple method, without the use of USB Debudding/rooting flashing:
Go to Emergency dialer,
Enter ##778, and press 'call'
Select 'Edit Mode'.
Password is: 000000
Select 'NAM Settings'
Make the following changes:
MDN = your 10 digit phone# (0000000000)*
MIN1 = your 7 digit phone# (0000000)
MIN2 = the area code of your phone# (000)
Press the 'back' key and go to 'HOME SID/Home NID' settings
Select 'Home SID/NID #1', and change the first value to '189' (Leave the 65535 alone).
Now press your 'menu' key
Press 'commit modifications' "button"
Phone Should reboot now.
Changing MDN using cdmaDevTerm
In some phones MDN cannot be changed, in this case you need to connect the phone to the computer as a "modem" device, and use the opensource cdmaworkshoptool / cdmaDevTerm from here:
http://code.google.com/p/cdmaworkshoptool/
Connect the tool, select manually / automatically the COMPORT for your HTC device, Read from device, Change the MDN to 0000000000 Select write
Disconnect and reboot your device.
It should now by pass the activation.
most of the ref. from
http://androidforums.com/incredible...g-activation-screen-no-service-available.html
I think this app with 2 kind of sending without wifi direct
1)
Code:
Device B run app , on thether and on nfc
Device A on wifi and/or on nfc
Device B with nfc send command to device A to start wifi (connect to theter)and go in browser in one link
Device A can upload files in device B in this webpage and viceversa but device A cant see the files of device B for privacy
2)
Code:
Device B run app , on theter and on nfc
Device A on wifi and/or nfc
Device B show to device A the files that you select before in a webpage and device A download automatically all files
I search a developer
Sent from my lt26i 6.1.A.2.55 relocked bootloader using xda-developers app
You should change your name to ' WiFi-direct'
Sent from my LT26i using Tapatalk 2
I seriously don't understand why he is not banned yet.
revan17 said:
I seriously don't understand why he is not banned yet.
Click to expand...
Click to collapse
Is he a spammer??
Yea!!!
some else hit the report first!!!
Thanks
Cleaned thread. I suspect we are dealing with a language barrier issue
I've been side loading apps using ADB across my home network, but is there a way to use a file manager (like ES File Explorer) to install APKs? I put an APK on my Fire TV and tried using ES File Explorer and it gave my an error stating that the install was blocked because my "phone" was set to not allow installs from unknown sources. Is there a way around this restriction as this time?
http://www.xbmchub.com/forums/showthread.php?t=21380
Sent from my Nexus 7²
Vidikron said:
I've been side loading apps using ADB across my home network, but is there a way to use a file manager (like ES File Explorer) to install APKs? I put an APK on my Fire TV and tried using ES File Explorer and it gave my an error stating that the install was blocked because my "phone" was set to not allow installs from unknown sources. Is there a way around this restriction as this time?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=593538
should make it easier anyways
screwyluie said:
http://forum.xda-developers.com/showthread.php?t=593538
should make it easier anyways
Click to expand...
Click to collapse
Do you know the proper way to edit that command to work over a network? It seems to be set up assuming a direct connection. I tried a couple of things like throwing "connect <IP address>" in there, but nothing worked. But I'm probably not setting up the commands correctly.
Vidikron said:
Do you know the proper way to edit that command to work over a network? It seems to be set up assuming a direct connection. I tried a couple of things like throwing "connect <IP address>" in there, but nothing worked. But I'm probably not setting up the commands correctly.
Click to expand...
Click to collapse
All I did was make sure port 5555 was open on my router and the shell install is working over my network without any changes to the reg file.
DeVSS said:
All I did was make sure port 5555 was open on my router and the shell install is working over my network without any changes to the reg file.
Click to expand...
Click to collapse
Interesting.. It just says "waiting for device" when I try.
Vidikron said:
Interesting.. It just says "waiting for device" when I try.
Click to expand...
Click to collapse
Just double checking, but you did turn adb on on your fire tv right?
DeVSS said:
Just double checking, but you did turn adb on on your fire tv right?
Click to expand...
Click to collapse
Yes. I've been installing APKs via the command prompt on my PC and that works fine. But when doing that I have to use the connect command to connect to a specific IP. I guess I'm unclear on how adb is actually supposed to find my device without telling it where to look.
[edit] Well, I've sort of gotten around the issue. I just made a second shell command to connect. So now I right-click connect and then right-click install. Not as pretty as a single command, but much faster than what I was doing before. But if anyone knows how to merge the two into a single command please let me know.
hi everyone, i received today my phone, it seems to be a korean import unlocked for sims but not rooted.
i had a galsaxy s2 for a few years and know how to root and flash a rom, but problem is, on my htc one m8 there is no option to disable fast boot in the battery menu
i looked everywhere on the phone, it's just not there. i looked on the net and somebody suggested CleanFLASH 1.0 just to start the phone in hboot, but can't manage to find the file anymore, links are dead, any suggestion?
thanks
anybody can help with this? I'm bloody stuck without a rooted phone!!!! thank you
satello said:
i looked on the net and somebody suggested CleanFLASH 1.0 just to start the phone in hboot, but can't manage to find the file anymore
Click to expand...
Click to collapse
Is your main problem not being able to get into bootloader (I don't see how else the fast boot power option would prevent you from rooting)? Just hold the power button until the options come up, select Restart, then when the screen goes black, immediately (before the white HTC boot screen) hold the power down rocker, and don't let go until hboot appears.
Alternately, hold power and vol up to force a reboot of the phone, then when the screen goes dark, switch to holding the vol down rocker.
Why are you worry so much on "fast boot" ?
You don't necessarily need to press power + volume down to go to hboot/bootloader.
I never disable "fast boot". Just simply restart, wait for the downanimation complete (it turn black screen) then press volume down (no holding power button) ... it will go to hboot.
Or you can plug in your device to PC with USB debugging enabled. Open a command prompt from your adb folder, type command adb reboot bootloader
thank you. i've tried all the above all afternoon, including all the tools available but phone will only either reboot, sometimes in safe mode, or reboot regularly.
I think I know what I'm doing. I need to unlock bootloader to root, but this is not possible. When connecting to pc by usb, and using tools, from comand line, computer screen just hangs and nothing else happens. with another program I can only see a tiny "fast boot...." on the bottom left corner of the screen. I cannot basically unlock the bootloader hence root the device.
another few things i notice you may be able to double check.
trying to reboot in standard recovery, the android buddy comes up on the screen, like dead, with "no command" message. then pressing volume up will take to recovery screens, never seen this before.
And last, but not least, checking the serial number from the menu > about phone > status the serial number comes as
0123456789ABCDEF
I checked with HTC support on chat and they basically gave me the registered serial number for this IMEI and told me of course that it is impossible that it has another number as this cannot be changed.
Question is... Have I got a clone here??
edit: sorry about the data, it was not set the apn, now it works. normally used to have automatically apn from sim card, but it's not the case for this phone/sim
I bet you do have a clone, does the phone has a playstore ? Install some phone specs app and see what it comes up with.
satello said:
And last, but not least, checking the serial number from the menu > about phone > status the serial number comes as
0123456789ABCDEF
Question is... Have I got a clone here??
Click to expand...
Click to collapse
Is your about phone (there is no about phone on real HTC One M8, only "about") looks like these screenshots here : http://forum.xda-developers.com/showpost.php?p=54102512&postcount=7 and here : http://forum.xda-developers.com/showpost.php?p=54102633&postcount=8
Then it is a clone
ckpv5 said:
Is your about phone (there is no about phone on real HTC One M8, only "about") looks like these screenshots here : http://forum.xda-developers.com/showpost.php?p=54102512&postcount=7 and here : http://forum.xda-developers.com/showpost.php?p=54102633&postcount=8
Then it is a clone
Click to expand...
Click to collapse
it looks like that, checking the specs i can see a ARM v7 Processor, rev3 and a screen resolution of 1280 x 720...
Unfortunately, I think your device is a "Clone".
thanks guys, i've haven't been rooting for a couple of years, but really thougt something was wrong, terribly wrong. ok, will check back here when i get a real one, if needed.
I think he was talking about "Fast boot" option in battery settings and not the "Fastboot" everybody is talking about here. Nevermind. And yes, that phone is/was a clone
CNK80Q3MX said:
I think he was talking about "Fast boot" option in battery settings and not the "Fastboot" everybody is talking about here.
Click to expand...
Click to collapse
The subsequent responses by clpv5 and myself understood that he was talking about "Fast boot" in Settings.
The only reason the "old" root guides instructed to turn off "Fast boot" in power settings, is that this mode enabled would prevent you from entering bootloader from a "powered down" conditon (since with the "Fast boot" option enabled, the phone was never actually powered down, just a deep sleep mode).
But as we pointed out, you could always enter bootloader from a reboot, since a reboot is always a true reboot. This would work regardless of whether "Fast boot" was enabled or not in power settings.
Although it should be noted this thread is from July 2014, and the "Fast boot" option was removed some time ago.
redpoint73 said:
The subsequent responses by clpv5 and myself understood that he was talking about "Fast boot" in Settings.
The only reason the "old" root guides instructed to turn off "Fast boot" in power settings, is that this mode enabled would prevent you from entering bootloader from a "powered down" conditon (since with the "Fast boot" option enabled, the phone was never actually powered down, just a deep sleep mode).
But as we pointed out, you could always enter bootloader from a reboot, since a reboot is always a true reboot. This would work regardless of whether "Fast boot" was enabled or not in power settings.
Although it should be noted this thread is from July 2014, and the "Fast boot" option was removed some time ago.
Click to expand...
Click to collapse
Thanks. I was looking for an explanation like that; in fact, somehow that's why I ended up in this thread. Though, it's useful yet, since there must be lots of devices still running the 'Fast boot' option due to certain manufacturer's lack of firmware updates and because not every device in need for support out there is actually a new device
Sent from my LG-D693n using XDA Free mobile app
same problem
satello said:
thank you. i've tried all the above all afternoon, including all the tools available but phone will only either reboot, sometimes in safe mode, or reboot regularly.
I think I know what I'm doing. I need to unlock bootloader to root, but this is not possible. When connecting to pc by usb, and using tools, from comand line, computer screen just hangs and nothing else happens. with another program I can only see a tiny "fast boot...." on the bottom left corner of the screen. I cannot basically unlock the bootloader hence root the device.
another few things i notice you may be able to double check.
trying to reboot in standard recovery, the android buddy comes up on the screen, like dead, with "no command" message. then pressing volume up will take to recovery screens, never seen this before.
And last, but not least, checking the serial number from the menu > about phone > status the serial number comes as
0123456789ABCDEF
I checked with HTC support on chat and they basically gave me the registered serial number for this IMEI and told me of course that it is impossible that it has another number as this cannot be changed.
Question is... Have I got a clone here??
edit: sorry about the data, it was not set the apn, now it works. normally used to have automatically apn from sim card, but it's not the case for this phone/sim
Click to expand...
Click to collapse
oh man, i thought i was the only one !
i have the same exact phone !
my serial number is exactly 123456789ABCDEF !!!
mine is a chinese mtk htc one m8. after hours of search i figured my phone name is alps_htc one m8 and yes my friend, is a fu..... clone !!!
i tried everything ! and search whole bunch of websites and forums like xda and xda itself, nothing happened !
i also get the => fastboot....... every time i try to go to bootloader !
this is something that you guys who trying to help here had to understand, these clone phones settings is completely different from other phones and even the original one ! hold power button then hold volume up or down, doesn't work !
every time it stock in => fastboot..... none of the buttons of the damn phone works and i have to wait until the battery drain ! real pain in the ass !!! because you know, htc one m8 does not have battery removing option, another pain in the ass !!!!!!!!!
i had a another problem too, when i wipe this clone phone, amazingly, the IMEI was gone !!! the phone said "invalid IMEI" !!! witch after hours of search i flashed it with an app from mobileuncle tools, thank to them amazing app allowed me to flash a custom IMEI from a unused phone.
now i use another htc device from the original manufacturer.
a little piece of advice, do not buy a clone phone ! cause it's going to piss you off !!!
and if you don't know how to recognize a clone from a original phone, its simple, just check the serial number, if it's feel weird, just give back the phone to seller, smile, and run out of the store !
thanks to XDA btw.