Related
When i try typing " adb devices" in CMD.
I get
"list of devices attached"
what am i doing wrong?
You need to be in bootloader, turn off, then turn on while pressing and holding the trackball. Make sure USB debug is enabled in the N1 Applications setting.
did as u said still the same thing "list of devices attached"
i downloaded latest sdk2.0
and did all as the google page says. its weire why it doest read ADB
fastboot read fine when i write fastboot devices, it show the serial of the phone...
can i add applications through fastboot? instead of adb?
did as u said still the same thing "list of devices attached"
i downloaded latest sdk2.0
and did all as the google page says. its weire why it doest read ADB
fastboot read fine when i write fastboot devices, it show the serial of the phone...
can i add applications through fastboot? instead of adb?
I have the exact same problem. Did you ever figure it out?
What directory are you working out of? If you did the default install of the Android SDK. Try this:
Code:
cd c:\android-sdk-windows\tools
Then:
Code:
adb devices
You have to open the command prompt from within the tools folder from sdk folder.
Also, its never worked for me while my phone is in the bootloader, i run abd commands while my phone is booted normally (with debugging enabled).
I use adb shell stop, adb remount, whatever commands you wanted to do originally, adb shell reboot.
Hope that helps, good luck man.
Sounds like maybe the driver isn't installed correctly. Check your device manager and see if the N1 shows up in there and what it's named.
tamarian said:
You need to be in bootloader, turn off, then turn on while pressing and holding the trackball. Make sure USB debug is enabled in the N1 Applications setting.
Click to expand...
Click to collapse
That is fastboot, fastboot for the bootloader, ADB for everywhere else
Are you on windows or linux?
Also try "adb remount" when you are in the /tools folder, then try "adb devices"
Make sure USB Debugging is on..that could be it
Hi,
I have a legend and everything was fine but after I tried to install the legend CM6RC2 BUILD 66 Rom from cynogenmod it would not reboot any more and I only saw the android robot. After that I tried to get into recovery but that's not possible anymore.
I al ready tried modaco's guide but I didn't understand.
Does anyone know how I can unbrick my usb to be able to get into recovery to install another Rom?
Thanks in advance!
you must unbrick your USB by following this step ( nobody can do it for you... ) :
http://android.modaco.com/content/h...com/309961/usb-brick-rickrolled-b0rked-fixed/
usb drivers
I tried to understand this guide but I don't understand this part:
"Move this to /data/ , and flash the modified image using:
"/data/flash_image misc /data/mtd0.img"
You can move both mtd0.img and flash_image by putting it on your sdcard, and issueing the following command in a terminal emulator:
'cat /sdcard/flash_image > /data/flash_image'
'cat /sdcard/mtd0.img > /data/mtd0.img'
You might have to do 'chmod u+x /data/flash_image' before you run the commands (or chmod 755 /data/flash_image)"
and also i cant do step one because device is not found
you must do this after starting your device.
Before starting your device you must mount you sdcard with 'fastboot oem enableqxdm 0' under fastboot mode ( device off : hold power button + volume down )
after your device started, go to market and install Connecbot.
Start connectbot, select ( at the bottom ) Local in place of ssh , and type 'su' 2 times.
If you get permission denied, do what he's done in his PS http://android.modaco.com/index.php?s=&showtopic=309961&view=findpost&p=1335813
i can type su as many times as i want and nothing happens.
YES i typed it in local.I re-installed htc sync and still my pc cant recognize my phone.
what should i do?
you type SU on your device ? ( in connectbot )
if you see a # at the begining of the line , you are logged as root , just follow the unbrink step
ilos said:
you must do this after starting your device.
Before starting your device you must mount you sdcard with 'fastboot oem enableqxdm 0' under fastboot mode ( device off : hold power button + volume down )
after your device started, go to market and install Connecbot.
Start connectbot, select ( at the bottom ) Local in place of ssh , and type 'su' 2 times.
If you get permission denied, do what he's done in his PS http://android.modaco.com/index.php?s=&showtopic=309961&view=findpost&p=1335813
Click to expand...
Click to collapse
could you explain it for me ? how to do fastboot oem enableqxdm 0 in fastboot.....
you must have android sdk installed to use adb
When you have installed android sdk, go to tools directory, open a command prompt ( MSDOS ) , type 'adb shell' and 'fastboot oem enableqxdm 0'
after that, just reboot your device.
Look that for adb : http://forum.xda-developers.com/showthread.php?t=517874
ilos said:
you must have android sdk installed to use adb
When you have installed android sdk, go to tools directory, open a command prompt ( MSDOS ) , type 'adb shell' and 'fastboot oem enableqxdm 0'
after that, just reboot your device.
Look that for adb : http://forum.xda-developers.com/showthread.php?t=517874
Click to expand...
Click to collapse
what should i do after i reboot my device?
Win7 said he cant recognize the usb device.
is this good? dont you have the drivers or something?
zorro12010 said:
what should i do after i reboot my device?
Win7 said he cant recognize the usb device.
is this good? dont you have the drivers or something?
Click to expand...
Click to collapse
see post #6
to be simple :
only the device will see your sdcard.. not your computer... all steps for unbrick must be done on the phone except the fastboot command
i also tried typing SU and sl
and instead of # it says sh-3.2#
so you are logged as root
just to be sure type : ls not sl
you will see same thing like my screenshoot posted early
now follow unbrick command
ilos said:
you must have android sdk installed to use adb
when you have installed android sdk, go to tools directory, open a command prompt ( msdos ) , type 'adb shell' and 'fastboot oem enableqxdm 0'
after that, just reboot your device.
Look that for adb : http://forum.xda-developers.com/showthread.php?t=517874
Click to expand...
Click to collapse
thousand thanks......for you man.....i made it...........
congratulations !!!
Hi ..
I do not speak English well ،But I'm trying to understand
Please have the same problem, and tried to solve, but to no avail
at the above link in comment # 14
Thanks to Google Translate
Anyone getting parsing error while trying to change the Model ID of their device using enghboot should follow these instructions:
Make sure you have the latest version of adb.exe and fastboot.exe files on your PC and that your device is S-OFF and rooted.
1. Navigate to the folder where adb is stored using command line.
2. Backup the original bootloader using the following commands.
Code:
adb shell
dd if=/dev/block/mmcblk0p12 of=/sdcard/mmcblk0p12.bin
adb pull /sdcard/mmcblk0p12.bin mmcblk0p12.bin
exit
Make sure you have a new file mmcblk0p12.bin in your fastboot and adb folder.
3. Download hboot.img from the link below and place it in the same folder as adb and fastboot.
https://www.dropbox.com/s/b695866du2dez3c/hboot.img
4. Place file on your device's sdcard using this command:
Code:
adb push hboot.img /sdcard/hboot.img
5. To write enghboot onto the device, use the following commands
Code:
adb shell
su
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p12
exit
adb reboot bootloader
6. Once in fastboot, use the commands below to change to the desired MID and cidnum.
Code:
fastboot oem writemid PN07xxxxx
fastboot oem writecid xxx__xxx
fastboot reboot
Thanks to the developers of eng hboot for creating such a wonderful utility!
Wow thanks for that!!
will try soon!
Tried 'fastboot oem writemid' it says unknown command...?>??
HTC ONe 802w
adb reboot bootloader
After this command phone went black screen and not responding hence in my device manager on PC i can see it android usb
HTCONE802W said:
adb reboot bootloader
After this command phone went black screen and not responding hence in my device manager on PC i can see it android usb
Click to expand...
Click to collapse
I followed the instructions and my phone has been bricked. I am getting snow error. Can anyone help?
Ive noticed alot of you are having trouble accessing the hidden menu on the N910P to enable GCF for your domestic unlocks so here you go
1. Must be rooted
2. adb sdk tools installed on your PC
3. Enable USB Debugging
4. Open up a command prompt and type the following commands below make sure you grant Root access when you type the "su" command
adb devices
adb shell
su
Once you allow adb root access your going to to see the # sign now copy and paste this command below and your hidden menu will appear. PROFIT
am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://IOTHIDDENMENU
Will this work on Oreo?
Okay, I have seen many people using the unofficial TWRP on their device, and that's a little dangerous because it may be malicious, and you might not even know that.
I am not saying it is, but it can be.
Now, back to the topic here,
HOW TO INSTALL TWRP[2] AND GET ROOT ACCESS[3] and moreHere goes..
Before anything, you need to get ADB and FASTBOOT programs on your PC and get your drivers installed so you can communicate with the device through your computer.
To Download ADB and fastboot program, you can download this file (not my upload)
Extract it anywhere you want(and remember that location).
(lets say "C:\workspace\ADB" and I will use this path for this guide).Typically, the driver for ADB will install the first time you connect your device to your computer and:
Internet is available
USB Debugging is enabled on your phone
But the FASTBOOT driver would probably not be available yet. to get fastboot drivers, follow these steps:
Turn on and Unlock your device and connect it to PC via the USB cable.
Open CMD and execute "cd C:\workspace\ADB".(or you can open C:\workspace\ADB in file explorer and type CMD in the address bar to open CMD directly there.
Type "adb devices".
Now, your phone will ask something(permission to allow ADB access on the connected PC)allow it. After you allow it, the CMD will show a list of attached devices and the mode they are attached in, your device should show "device" for now.
If it does not, there is some problem, search on internet or ask for help here
Now type "adb reboot bootloader".
now your Phone will shutdown and open in a different state. It will say Fastboot on the screen.
Now the driver is installing or is already installed, to check, type this:
"adb devices" and it should show a list and your device's mode should change to "fastboot".
That's it for the ADB and FASTBOOT. You have the necessary things to continue.
Continue to next post for TWRP and the post next to it for ROOT ACCESS.
Now, we will talk about how to install TWRP
@DroidThug has been kind enough to get Official support of TWRP for this device.
Head over to this thread to download the official image file of the TWRP Recovery and keep it on your computer, this is the very first step you need to take.
Here is the thread: https://forum.xda-developers.com/leeco-le-1s/development/official-twrp-t3527566
If you are lazy enough to go through the thread, which i suggest you to visit, here is the direct link to the download page: https://dl.twrp.me/x3/
And here is the direct download link of the v3.0.3(latest as of 31st Jan, 2017): https://dl.twrp.me/x3/twrp-3.0.3-0-x3.img
Once you have the recovery image, you need to flash it through fastboot.
If you are following this guide from start, you should already be in fastboot and have CMD open on your PC in adb folder.
Now, a few things you might want to follow strictly if you are unsure how to do it:
Copy the recovery image file to "C:\workspace\ADB" (adb folder).
Rename that file to "twrp.img"
Now you need to execute this command from CMD to flash the file:
"fastboot flash recovery twrp.img" and press enter.
This will take a few seconds and will will be over soon.
Now you need to reboot directly into RECOVERY, because if you will boot to the system first, the Device will replace your newly flashed recovery with the stock recovery and all this will be wasted. But if you reboot to recovery first, it will patch those things up and will stay.
So, to reboot to recovery, you need to use the key combo to get into the recovery,
Press and hold "Volume UP" and "Power" Buttons till the screen goes off(from fastboot mode) and is lit up again and then leave the power key and 2-3 seconds later, leave the Volume key too.
You will enter into recovery mode and it will ask you "if you want to keep the System partition to read only or not?"
I'd recommend keeping it to read only unless you know what you are doing.
There you have it!
You have successfully installed TWRP on your device!
GET ROOT ACCESS
Okay, So you have the RECOVERY installed already
Now go to this page and download the latest "Recovery Flashable ZIP" from there. (Here is the latest one as on 31st Jan, 2017).
You can do this in two ways through Phone(with TWRP already present) and through PC.
Through PhoneAll you need to do is flash it through the recovery and thats it, you will have root access!
Here are the steps to flash ZIPs from Recovery:
Get the zip file you want to flash(the one downloaded above) and place it somewhere in the Phone's internal storage.
Reboot to recovery(Power off and then hold "Vol UP" and "Power" keys till the screen is lit up.).
Tap on "Install".
Navigate to the ZIP file you placed in your phone's internal storage.
Select it and swipe to flash it.
The last step might take a few seconds and will be done then.
After its done, that't it!
Reboot to system and you have ROOT ACCESS!
Through PCOkay, you would still need to reboot to recovery, but you can follow this guide if you don't want to copy the zip file on your phone for whatever reason you may have.
Here are the steps:
Enter recovery.
Select "Advanced->ADB Sideload" and swipe to start sideload.
Now connect your phone to PC.
Now open CMD in ADB folder.
Check if your device is detected by typing "adb devices". It should show a device with sideload state.
Now type "adb sideload " and drag the zip file into the cmd window.
OR
you can copy the zip to the adb folder and rename it to supersu.zip and write "adb sideload supersu.zip" in the CMD.
Now Press enter.
After this, in a few seconds, it will be over and you can reboot to system(it might automatically reboot to system too).
And that's it! There you have it!
You have ROOT ACCESS on your device!
5. Now the driver is installing or is already installed, to check, type this:
"adb devices" and it should show a list and your device's mode should change to "fastboot".
Click to expand...
Click to collapse
If the phone is on fastboot mode, "adb devices" supposed to not give any output. "fastboot devices" will show the device and mode as fastboot.
You will enter into recovery mode and it will ask you "if you want to keep the System partition to read only or not?"
I'd recommend keeping it to read only unless you know what you are doing.
Click to expand...
Click to collapse
My screen is broken (that's only white light and no digitiser). I dont have any other Le 1S to get idea.
1. Are you sure Vol Up + Power will enter into Recovery? Mine is 5.5.014S.
2. I want to make my system partition as writable. Can you tell how to achieve with hardware keys like Vol Up or down & power.
3. After step 2. Can I flash SuperSu from PC without enabling sideload. While on custom recovery , "adb devices" will show mode as recovery. So flashing supersu from here. Not sure if this is correct. On my Moto G falcon. whenever I go into TWRP, adb recovery and MTP works.
Also can you check whats the combination Vol Up+Vol Dn+Power. When it starts I can connect to adb but all partitions are read only and not allowing to make any change to device. Not sure if its due to encryption.
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb devices
List of devices attached
0123456789ABCDEF device
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb shell
[email protected]_HK:/ $ cat /data/misc/adb/adb_keys
/system/bin/sh: cat: /data/misc/adb/adb_keys: Permission denied
1|[email protected]_HK:/ $ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
[email protected]_HK:/ $ su
/system/bin/sh: su: not found
[email protected]_HK:/ $ cd
[email protected]_HK:/data $ pwd
/data
[email protected]_HK:/ $ exit
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb reboot bootloader
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>fastboot devices
0123456789ABCDEF fastboot
**
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb devices
List of devices attached
0123456789ABCDEF device
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb install mirror.apk
[100%] /data/local/tmp/mirror.apk
Error: java.lang.NullPointerException: Attempt to invoke interface method 'android.os.IBinder android.os.IServiceManager.getService(java.lang.String)' on a null object reference
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb shell am start -n com.android.settings/.wifi.WifiSettings
java.lang.NullPointerException: Attempt to invoke interface method 'android.os.IBinder android.os.IServiceManager.getService(java.lang.String)' on a null object reference
at android.os.ServiceManager.getService(ServiceManager.java:55)
at android.app.ActivityManagerNative$1.create(ActivityManagerNative.java:2494)
at android.app.ActivityManagerNative$1.create(ActivityManagerNative.java:2492)
at android.util.Singleton.get(Singleton.java:34)
at android.app.ActivityManagerNative.getDefault(ActivityManagerNative.java:88)
at com.android.commands.am.Am.onRun(Am.java:295)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
at com.android.commands.am.Am.main(Am.java:99)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:250)
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb shell dumpsys wifi
adb shell dumpsys wifi^C
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb shell
[email protected]_HK:/ $ ls -ld sdcard
lrwxrwxrwx root root 2017-03-21 11:12 sdcard -> /storage/sdcard0
[email protected]_HK:/ $ cd /storage/sdcard0
/system/bin/sh: cd: /storage/sdcard0: Permission denied
2|[email protected]_HK:/ $ ls -ld
drwxr-xr-x root root 2017-03-21 11:12 .
[email protected]_HK:/ $ ls -ld /storage/sdcard0
d--------- system system 2017-03-21 11:12 sdcard0
[email protected]_HK:/ $
Update:
I some how managed to side load. My Phone got bootlop after installing twrp. Then flashed userdata by following http://forum.le.com/in/index.php?th...op-restart-solution-letv-le1s-x507-x509.1155/ . Now its factory reset as I can see the screenshot from PC.
Still interested in knowing what's that Vol Up+Vol Down + Power.
If any one have le 1s related problem and solution or any one want to try new rom or kernal asap then all of u are welcome in our group on telegram so plz join with us
Requriemt
1. Download telegram from play store
2. Just click below link
https://telegram.me/LeSuperGroup
Thanks all of u