Database Users

Flashing A Recovery Rom..

I have searched this forum multiple times and i can not find my answer so i am posting this hoping someone with some patience will help me.. when i followed these steps.. "III: Flashing a Custom Recovery
Flashing a custom recovery will make your life easier when flashing ROMs in the future.
1. Download this file: Recovery.zip
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up a command prompt and go to your tools directory, and execute these commands:
•adb shell mount -o rw,remount /dev/block/mtdblock3 /system
•adb push recovery.img /sdcard
•adb push flash_image /system/bin
•adb shell chmod 755 /system/bin/flash_image
•adb shell flash_image recovery /sdcard/recovery.img
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
It says that what i have typed is not an executible file.. someone please help.

are you 100% sure that you extracted the file out of the zip and not just put the zip into the folder?

yea im sure

Are you typing out each command? or are you pasting them into your terminal? Also, what OS are you running ADB from, and have you had success with it before? Or is the eris your first android device
Also, you did the previous steps first correct? IE: you're ROOTED

there is an easier way posted by i think Zinfab it was something like.
su
adb shell
reboot bootloader
at this point make sure it says fastboot USB on the screen
then in the same window fastboot flash recovery recovery.img (make sure your recovery.img is in the same directory as all your SDK tools)
this worked for me when the method u posted didn't work

where do i type this stuff in at.. i have my phone plugged in usb debug checked i installed the usb driver update it and i have the recovery thing extraced in my tools folder now what do i use my computers command prompt or my phones command prompt

ashertheplague said:
where do i type this stuff in at.. i have my phone plugged in usb debug checked i installed the usb driver update it and i have the recovery thing extraced in my tools folder now what do i use my computers command prompt or my phones command prompt
Click to expand...
Click to collapse
did u set the enviromental variable? its not that important I'm just curious.
if not in command prompt first command would be
(directory to tools)\adb shell
"su"
"Reboot bootloader"
then once its in bootloader
(directory to tools)\"fastboot flash recovery (directory to recovery.img)"
now the quoted sections should be typed exactly as is, without the quotes, but you have to know your own directory.

when i type it in on my phone it says adb not found

whats that

ok my phone now is in fastboot usb mode what do i do know

as suggested, did you set the variable? type fastboot devices to see if its even working correctly, to start.

how do i get out of fastboot usb

Type in the command fastboot flash recovery recovery.img

ok now it says waiting for device

You didn't search that well.
http://forum.xda-developers.com/showthread.php?t=647974

well i went to that forum and it was still giving me problems.. but i got help from spence_moore so its all good

ashertheplague said:
well i went to that forum and it was still giving me problems.. but i got help from spence_moore so its all good
Click to expand...
Click to collapse
What step were you having a problem with? If there is something wrong I would like to fix it.

[Q] boot logo brick (?) [SOLVED]

i'm VERY new to all of this, and i promise i tried my hardest to find an answer in existing threads and google, but haven't found anything to help with my prob:
I tried (?) to root kindle fire [android police thingy], not sure if I succeeded or not (had a lot of "device not found" at the beginning) and tried to install RTL languages support at the same time.
I haven't installed any "TWRP" or "firefirefire" or anything like it.
after the reboot at the end of the RTL, the kindle got stuck on "kindle fire". I tried 20 second power button for several times, on and off power.
kindle fire utlity ("run") says:
adb status: online
adb rooted: no
boot status: 4000
when trying to root through this (temp root), i get: adbd cannot run as root in production builds.
I get the same phrase trying to do anything on the utiility.
Can I do anything to save this from being a 200$ coaster?
THANKS!

you can try to install fff and twrp with kfu (option 5)
then copy one of the prerooted stock images to sdcard:
http://forum.xda-developers.com/showthread.php?t=1402440
would recommend the secure one
and install with twrp:
http://forum.xda-developers.com/showpost.php?p=20543289&postcount=47

imageshack. us/photo/my-images/515/brickc.jpg/
(delete spaces)
i get about the same thing for every option i choose.
any other option?
(and THANK YOU for answering so quickly)

open an (elevated) command prompt in the tools directory of kfu and type in:
adb shell
copy and paste what you get back

b63 said:
open an (elevated) command prompt in the tools directory of kfu and type in:
adb shell
copy and paste what you get back
Click to expand...
Click to collapse
$ sign.. (waiting does nothing, "enter" produces yet another $ sign :X )

that is very good - you did not mess up your shell !!!
ok - what version of kfu do you have ?
would recommend the newest one - 0.9.2 - extract it to c:\ and rename the folder to "kfu" so that it looks c:\kfu
then give it a retry with option 3 and then 5
please copy and paste the output that i can see what it is doing

b63 said:
that is very good - you did not mess up your shell !!!
ok - what version of kfu do you have ?
would recommend the newest one - 0.9.2 - extract it to c:\ and rename the folder to "kfu" so that it looks c:\kfu
then give it a retry with option 3 and then 5
please copy and paste the output that i can see what it is doing
Click to expand...
Click to collapse
the kf is on 6.2.1 and the kfu is 0.9.2.
img521.imageshack .us/slideshow/webplayer.php?id=brick2m.jpg
(again, delete space)
on the first attempt with no. 5, it started downloading something but my internet went bad and the dl stayed on 52%. I manually downloaded the file and named it "recovery" (in the correct folder). after that, i got the message in "brick 3"
and another thing - even though i keep getting "adb rooted: no", after each time i "root", the device reboots, but it doesn't reboot after the "installation" of the twrp.

that with the recovery was right - it has to be recovery\recovery.img
the file should be ~10mb - maybe we have to do it manually
the problem is that burritoroot is allready installed and kfu can't gain root
you did not install burritoroot with kfu ? (kfu has a special version)
therefor we get the message "... can not run on production builds"
now we can look where the file is located and install with kfu or
install fff and twrp manually
i think in this case it will be easier to install manually:
first fff 1.2 manuell:
•download from here:
http://forum.xda-developers.com/attachment.php?attachmentid=850008&d=1326179460
•extract to the folder where adb.exe & fastboot.exe is located
•"adb shell idme bootmode 4002" & "adb reboot"
•flash with "fastboot -i 0x1949 flash bootloader u-boot.bin"
second twrp manuell:
•copy recovery.img which you downloaded and renamed to the folder where adb.exe & fastboot.exe is located
•install with "fastboot -i 0x1949 boot recovery.img"
now we reboot into recovery:
•"fastboot -i 0x1949 oem idme bootmode 5001"
•"fastboot -i 0x1949 reboot"
now we should have the recovery system installed ...

b63 said:
i think in this case it will be easier to install manually:
first fff 1.2 manuell:
•download from here:
http://forum.xda-developers.com/attachment.php?attachmentid=850008&d=1326179460
•extract to the folder where adb.exe & fastboot.exe is located
•"adb shell idme bootmode 4002" & "adb reboot"
•flash with "fastboot -i 0x1949 flash bootloader u-boot.bin"
Click to expand...
Click to collapse
itmw,
"adb shell idme bootmode 4002" (in c:\KFU\tools)
gave me:
"<idme> invalid permission"
(and thank you again for all the help)

RYuval said:
itmw,
"adb shell idme bootmode 4002" (in c:\KFU\tools)
gave me:
"<idme> invalid permission"
(and thank you again for all the help)
Click to expand...
Click to collapse
looks like you have messed up the permissions !
ok - then we use this to get into fastboot:
download this and extract in the tools folder:
http://forum.xda-developers.com/attachment.php?attachmentid=833582&d=1325144494
then:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
now we should continue the steps above

b63 said:
looks like you have messed up the permissions !
ok - then we use this to get into fastboot:
download this and extract in the tools folder:
http://forum.xda-developers.com/attachment.php?attachmentid=833582&d=1325144494
then:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
now we should continue the steps above
Click to expand...
Click to collapse
those steps went fine.
but now we're back to "error: device not found"
reinstalled the drivers, shut down, restarted and reinstalling again to see if it helps. (maybe it's just me, but it feels like anything that can go bad, does. )

RYuval said:
those steps went fine.
but now we're back to "error: device not found"
reinstalled the drivers, shut down, restarted and reinstalling again to see if it helps. (maybe it's just me, but it feels like anything that can go bad, does. )
Click to expand...
Click to collapse
that's quite normal
what say your device manager about adb or kindle ?

b63 said:
that's quite normal
what say your device manager about adb or kindle ?
Click to expand...
Click to collapse
until recently, "adb android device" or something like that..
now it says the driver does not suit 64bit... (currently: unknown USB device)

it should say "android adb interface"
update the driver with the one from c:\kfu\drivers - they can 64bit
if it does'nt work you can run install_drivers.bat from c:\kfu - maybe 2 times
for information in device manager:
normal boot (4000) -> android composite adb interface
fastboot (4002) -> android adb interface

b63 said:
it should say "android adb interface"
update the driver with the one from c:\kfu\drivers - they can 64bit
if it does'nt work you can run install_drivers.bat from c:\kfu - maybe 2 times
Click to expand...
Click to collapse
for some reason, that still doesn't work..
and the driver was properly installed earlier..

RYuval said:
for some reason, that still doesn't work..
and the driver was properly installed earlier..
Click to expand...
Click to collapse
for normal boot - have you ever been/worked in/with fastboot mode ?
we have to get the right drivers for every mode working
i just switched my kf to fastboot and return to normal boot to verify
try to update the driver manually (select manually)
alternately you can delete every driver with kindle or adb and then unplug and replug the kf
that' only a loose description that you see how it is done:
if you' asked
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select okay and okay
just in case you'r not asked:
-Go to device manager
-right click on the exclamation mark kindle
-Choose update driver software
-choose browse my computer for driver software
-choose let me pick from a list of devices on my computer
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select okay and okay

will be updated (drivers installed.) the name's without "composite"

if you have a 32 bit pc - that's the better choice
what os is it ? xp 7 or ?
on the 32 bit you can try an alternate set
download it from this post:
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
and run the included batch and then install the driver

b63 said:
if you have a 32 bit pc - that's the better choice
what os is it ? xp 7 or ?
on the 32 bit you can try an alternate set
download it from this post:
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
and run the included batch and then install the driver
Click to expand...
Click to collapse
i have 32bit win7 (and 64 on win7)
it identified as an "adb interface device" but still "device not found" on cmd..

RYuval said:
i have 32bit win7 (and 64 on win7)
it identified as an "adb interface device" but still "device not found" on cmd..
Click to expand...
Click to collapse
device not found on what command ?
your on an elevated command prompt (as administrator) ?
fastboot -i 0x1949 getvar product
it should return "kindle"

[Q] HD2 don't see of the pc when in fastboot mode (menù of clk)

Hello to all.
I am writing here because surely one of you will help me.
I have a notebook with windows xp 32bit, on which I regularly installed java jdk and android sdk (with whom I have downloaded the google usb drive).
When the phone is switched on (ROM started to understand), from the command prompt, running the command "adb devices" everything works perfectly, but as I enter fastboot (menu 'clk) and launch the command "fastboot devices" or tend to flash a recovery or simply to update clk, out the word "waiting of device" and does not go forward.
I state that I position it in the folder C: \ ....... platfotm-tools (where there are the files that I need).
thanks

g.andy said:
Hello to all.
I am writing here because surely one of you will help me.
I have a notebook with windows xp 32bit, on which I regularly installed java jdk and android sdk (with whom I have downloaded the google usb drive).
When the phone is switched on (ROM started to understand), from the command prompt, running the command "adb devices" everything works perfectly, but as I enter fastboot (menu 'clk) and launch the command "fastboot devices" or tend to flash a recovery or simply to update clk, out the word "waiting of device" and does not go forward.
I state that I position it in the folder C: \ ....... platfotm-tools (where there are the files that I need).
thanks
Click to expand...
Click to collapse
did you install fstboot drivers ? you should install fastboot drivers for install recovery on cLK do U
You can found the drivers here
http://cyanogenmod.arif-ali.co.uk/tools/windows/google_android_sdk_fastboot_adb_drivers.zip
or
You can use cLK 1.5 it is have recovery inside and allow you power off charge u can download it from here
http://www.fileswap.com/dl/oeioqdavTA/CLK_1.5.zip.html
hit Thanks if i helped Sorry for my bad english

AladdinSy said:
did you install fstboot drivers ? you should install fastboot drivers for install recovery on cLK do U
You can found the drivers here
http://cyanogenmod.arif-ali.co.uk/tools/windows/google_android_sdk_fastboot_adb_drivers.zip
or
You can use cLK 1.5 it is have recovery inside and allow you power off charge u can download it from here
http://www.fileswap.com/dl/oeioqdavTA/CLK_1.5.zip.html
hit Thanks if i helped Sorry for my bad english
Click to expand...
Click to collapse
I have CLK 1.5.1.6 with recovery touch b8, bit i want to upgrate at last version with not change recovery (the new version have twrp) and it is possible only with fastboot
I have unstalled fastboot driver(download with sdk), infact ADB work great, but fastboot don't see the telephone
Inviato dal mio HD2 - Pixeldroid v3.0 aokp JB 4.2.2

g.andy said:
I have CLK 1.5.1.6 with recovery touch b8, bit i want to upgrate at last version with not change recovery
Click to expand...
Click to collapse
Hi,
Try this:
On your device, enter recovery and connect via usb cable to your pc.
On your pc, download the latest Black-cLK (black_lk_20130314.img) and put it in the same folder you have adb.
Do a [Shift+RightClick] in that folder and select "Open command window here".
Execute these commands:
Code:
adb push black_lk_20130314.img /sdcard/black_lk_20130314.img
adb shell erase_image lk
adb shell flash_image lk /sdcard/black_lk_20130314.img
*I don't remember if the recovery you have now, has the erase_image & flash_image binaries. If not, you can take them from a rom and push them to your device.
Regards!

kokotas said:
Hi,
Try this:
On your device, enter recovery and connect via usb cable to your pc.
On your pc, download the latest Black-cLK (black_lk_20130314.img) and put it in the same folder you have adb.
Do a [Shift+RightClick] in that folder and select "Open command window here".
Execute these commands:
Code:
adb push black_lk_20130314.img /sdcard/black_lk_20130314.img
adb shell erase_image lk
adb shell flash_image lk /sdcard/black_lk_20130314.img
*I don't remember if the recovery you have now, has the erase_image & flash_image binaries. If not, you can take them from a rom and push them to your device.
Regards!
Click to expand...
Click to collapse
I will try. Thanks.
Inviato dal mio HD2 - Pixeldroid v3.0 aokp JB 4.2.2
EDIT:
Thank you all for the advice.
Honestly with ADB from recovery I have not tried but I solved by using another pc with w7. The only thing I do not spego is that with nthe same procedure on my pc does not work while on another it works perfectly.
I'll probably have to change pc.

[HELP!!] Need To Delete Chainfire3D, But Dont Know How!

I installed "chainfire3d" on my phone which is running on jellybean,
when it self-reboot for installing library for "chainfire" it get stuck in android logo
after searching on net i figured out the way of disabling it (but works only one adb shell)
which is :
Code:
cd/system/lib/
sh cf3d_uninstall.sh
.
but the problems are:
Not able to get into recovery mode! As bootloader is locked ?
.
I already "wiped Data/cache"
using :
Code:
fastboot -w
it did wipe all data and cache but / still stuck in android logo ()
.
Ques are,.. :
1. How to get into recovery mode!
2. How to unlock bootloader!
3. Is it possible to get into adb shell using fastboot ?
4. Is their any command for rebooting into recovery mode via fastboot ????
My device is Iconbit Mercury q4 (Rooted)

SOLVED
.
(Device must be rooted, because we need to run ADB SHELL commands !)
.
Steps:
1. Install ADB on your Windows PC
2. Install ADB Drivers ( your device must be Detected by computer, otherwise you wont able to proceed!! )
----->remove battery and then put in again<----------
----->your device reboot itself (i guess)<--------
------>& then it will stuck in Android logo<------------------
(but the ,main thing is YOU CAN STILL ABLE TO USE ADB )
3. Connect your device with PC & then press (SHIFT+mouseRightClick) or simply open cmd ; )
type these command in command prompt :
4. adb devices (hit enter)
1234 iconbit <---- it looks somthing like that.. // If this command not work for you, try to install ADB drivers first !! //
5. su <--- ( this command gives you superuser permission )
----------> now # will appear <--------------
6. cd system <------- Change Directory to system
7. cd lib <------- Change Directory to lib
8. sh cf3d_uninstall.sh <----- it will delete Chainfire3D
------->your device reboot itself<--------------
9. Go to application Uninstall "Chainfire3D"
0. Cheers \../,
.
.
Command:
Code:
adb devices
su
cd system
cd lib
sh cf3d_uninstall.sh

[GUIDE][ROOT]How to install TWRP and ROOT your X507, X509 (PC Guide)

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 more​Here 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 Phone​All 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 PC​Okay, 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