Related
Hi to all members of XDA forums, I've been trying to install xperia play drivers in windows 8 (drivers from flashtool). but it always fails...does anyone have an idea how to install flashtool drivers in windows 8?
rbeldua said:
Hi to all members of XDA forums, I've been trying to install xperia play drivers in windows 8 (drivers from flashtool). but it always fails...does anyone have an idea how to install flashtool drivers in windows 8?
Click to expand...
Click to collapse
You have to disable driver signature checks as windows won't allow them, if you know how then upon boot go to troubleshoot settings (If you do not dual boot then you are forced to pull in your installation CD and go to Repair Computer section)
Then you go to advanced settings and after you hit boot in Safe Mode, reboot and then install the drivers and after that you need to reboot again to go to normal mode.
sewer56lol said:
You have to disable driver signature checks as windows won't allow them, if you know how then upon boot go to troubleshoot settings (If you do not dual boot then you are forced to pull in your installation CD and go to Repair Computer section)
Then you go to advanced settings and after you hit boot in Safe Mode, reboot and then install the drivers and after that you need to reboot again to go to normal mode.
Click to expand...
Click to collapse
thanks for the reply, i'll try that :fingers-crossed:
rbeldua said:
thanks for the reply, i'll try that :fingers-crossed:
Click to expand...
Click to collapse
Appears it worked since you 'thanked' the post.
I successfully installed the driver but still cant flash my lt18i yet... flash still aborted.. why? am I missing something?
daniLaLaLaLaLa said:
I successfully installed the driver but still cant flash my lt18i yet... flash still aborted.. why? am I missing something?
Click to expand...
Click to collapse
Same situation as mine. I successfully installed the drivers by disabling integrity check for drivers. But whenever I'm flashing, it aborts and then a pop-up appears saying that my device is not recognized
daniLaLaLaLaLa said:
I successfully installed the driver but still cant flash my lt18i yet... flash still aborted.. why? am I missing something?
Click to expand...
Click to collapse
same like me, but with a lt26i xperiaS
Help please!
In Windows 8, I have problems to flash my Xperia, I use Delphi, Eclipse, etc, the Delphi debug not work fine, I returned to Windows 7 and Flash tool work again, for now, I stay in W7.
Sory for my bad english
Hi Guys
Another rooting/flashing noob here that's messed up his N7 sorry
I know there's other threads with similair issues but they all advise fixes involving using adb connection and usb debugging which I cannot do (explained below)
My device will turn on, it goes to the google logo with the green start icon, I can select and go into bootloader and recovery, if I press start it says booting failed in the upper left corner and will go no further.
My device is plugged in via usb, i have the latest rookit 1.5.5, and sdk installed etc, i also have the naked drivers and the factory images from google on my pc.
The machine came with 4.1.2 installed (nakasi-jzo54k).
To mess it up, somewhere in between updating to 4.2, rooting and unrooting it, and flashing it i must have done something wrong but being a happy button bashing noob I don't know what exactly...
And yes I also didn't make a backup of any kind because well I'm just a moron and lesson well learnt.
So yeah, I have no adb connection, can't go into debuging mode and it won't boot.
Does anybody know if there is anyway I can restore my tablet please? Any help would be hugely appreciated!
Many thanks
greyphox said:
Hi Guys
Another rooting/flashing noob here that's messed up his N7 sorry
I know there's other threads with similair issues but they all advise fixes involving using adb connection and usb debugging which I cannot do (explained below)
My device will turn on, it goes to the google logo with the green start icon, I can select and go into bootloader and recovery, if I press start it says booting failed in the upper left corner and will go no further.
My device is plugged in via usb, i have the latest rookit 1.5.5, and sdk installed etc, i also have the naked drivers and the factory images from google on my pc.
The machine came with 4.1.2 installed (nakasi-jzo54k).
To mess it up, somewhere in between updating to 4.2, rooting and unrooting it, and flashing it i must have done something wrong but being a happy button bashing noob I don't know what exactly...
And yes I also didn't make a backup of any kind because well I'm just a moron and lesson well learnt.
So yeah, I have no adb connection, can't go into debuging mode and it won't boot.
Does anybody know if there is anyway I can restore my tablet please? Any help would be hugely appreciated!
Many thanks
Click to expand...
Click to collapse
If you got half way through rooting, what has happened to your ADB?
Try the option "Return to stock and Flash stock image" try that.
What message does ADB give you etc?
Wilks3y said:
If you got half way through rooting, what has happened to your ADB?
Try the option "Return to stock and Flash stock image" try that.
What message does ADB give you etc?
Click to expand...
Click to collapse
Hi thanks
Well when I run 'adb devices' in dos the device does not come up, blank etc
but if in the advanced utilities section of the rookit it will reboot it and say connected etc when i try to boot/flash image for bootloader, system, recovery etc but always goes back to google logo and won't boo up, can still get into bootloader and recovery though
i fully rooted it and unrooted it, i tried to flash 4.1.1 to see if i could thats when this all started
if i try flash stock + unroot option (device is on/normal) sub option the rootkit tries to check adb status and says not connected etc which makes sense as dos won't detect it, if this helps in device manager its coming up as...
samsung android phone
android bootloader interface
so i that driver in rootkit to manually install the naked drivers in device manager and it will say they are up to date etc
so the advanced utilities section for boot/flash image will communicate but no other.....
flash stock root used to detect it but even then in dos it would give me the 'too many links error'
I just hope there is a solution.... and i hope all that makes sense sorry
Cheers
greyphox said:
Hi thanks
Well when I run 'adb devices' in dos the device does not come up, blank etc
but if in the advanced utilities section of the rookit it will reboot it and say connected etc when i try to boot/flash image for bootloader, system, recovery etc but always goes back to google logo and won't boo up, can still get into bootloader and recovery though
i fully rooted it and unrooted it, i tried to flash 4.1.1 to see if i could thats when this all started
if i try flash stock + unroot option (device is on/normal) sub option the rootkit tries to check adb status and says not connected etc which makes sense as dos won't detect it, if this helps in device manager its coming up as...
samsung android phone
android bootloader interface
so i that driver in rootkit to manually install the naked drivers in device manager and it will say they are up to date etc
so the advanced utilities section for boot/flash image will communicate but no other.....
flash stock root used to detect it but even then in dos it would give me the 'too many links error'
I just hope there is a solution.... and i hope all that makes sense sorry
Cheers
Click to expand...
Click to collapse
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
nexus toolkit from dev section
ngoralph said:
nexus toolkit from dev section
Click to expand...
Click to collapse
Have you even read what hes said?
He's already tried the toolkit...
Wilks3y said:
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
Click to expand...
Click to collapse
The first step in the full driver guide in wugs kit is to enable usb debugging which i cannot do though as it won't power on.......
I have added the environmental variabes before yes sorry, qbkings utube vids showed me how to do that
Just tried these steps
toolkit home screen, flash stock + unroot (softbricked bootloop)
then naksaki 4.2 jzo54k, auto download and extract.
it got to dos stage and i get 'Failed bootloader is locked'
??? thanks again
Wilks3y said:
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
Click to expand...
Click to collapse
OK unlocked it via the main unlock option on rootkit and it unlocked ok, so im now re-trying te softbricked option to flash etc and its currently.. writing system...
greyphox said:
OK unlocked it via the main unlock option on rootkit and it unlocked ok, so im now re-trying te softbricked option to flash etc and its currently.. writing system...
Click to expand...
Click to collapse
Sounds good mate !
Need any extra help drop us a PM I'd be happy to lend a hand.
Wilks3y said:
Sounds good mate !
Need any extra help drop us a PM I'd be happy to lend a hand.
Click to expand...
Click to collapse
MOOOOOO!
It wrote to the system ok and now its hanging on erasing user data, googled and its happend to others.......
OK, more help please, been hanging for5 mins lol
Issue Fixed I think, he PM'd me.
Unlocked but... what do I do now?
Newbie but old or old but newbie - With the need and not just a curious want, to be able to "rename" my Nexus 7 v1 so I can see a friendly name in my old DD-WRTed Linksys GL, I finally had enough gumption to try rooting this tablet.
So, I was excited that when I used Nexus Root Toolkit v1.6.8 on my Nexus 7 v1, following the "easy and visual" steps, I actually managed to unlock this device. But when it came to the "root" part, the ADB repeatedly failed to recognize this tablet. I tried all the suggested steps and remedies, but so far, nada.
The tablet now boots past the white "Google" with an unlocked icon at the bottom, but nothing beyond thea big white "right-arrow" on the screen. I can choose a Wi-Fi signal to connect to, but that's it.
This is my first tablet and I have been playing with it for the past 3 months. I know people here are more than willing to help, so thank you in advance.
BTW, I am not that young to spend hours way past sleeping time to scour for answers and piece it together.
Wilks3y said:
Issue Fixed I think, he PM'd me.
Click to expand...
Click to collapse
Could you let me know his solution as I have exactly the same problem and have used all of his previous (unsuccessful) fixes myself?
Kindred Mole said:
Could you let me know his solution as I have exactly the same problem and have used all of his previous (unsuccessful) fixes myself?
Click to expand...
Click to collapse
+1
This worked for me...
Download the image file for your device which you can find at the Google Developer's site
Copy the uncompressed files from the image archive to the platform-tools folder of the Android SDK
Use the up and down volume on the device to get into bootloader mode. Connect the device to a usb port.
Open a command prompt in the platform tools folder and run the flash-all batch file to load the image to your device. After a few minutes I got the happy X logo to get me back to a blank slate.
Hi
Tried to flash a new kernel and all seemed ok (flashed phones and nexus 7 few times now) when I came out of flashing I hit a bootloop, I though nothing of it and tried to restart....same issue, so next I tried to go into cw recovery, no joy, it will not show again.
I can power/vol keys to android fastboot screen with start power restart boot and so on but if I choose recovery nothing happens, I am stuck with either a bootloop or stuck on android fastboot screen and not able to move from either.
I have tried the toolkit and most other things but the problem is it cannot see my nexus 7, even after installing drivers and so on the toolkit (top right) does not list my nexus as found, because of this I cannot reflash any stock firmware/recover/reflash cwr.
Not sure how I can get around this if my pc cannot see the nexus 7.
Thanks for any help
voodoochild2008 said:
Hi
Tried to flash a new kernel and all seemed ok (flashed phones and nexus 7 few times now) when I came out of flashing I hit a bootloop, I though nothing of it and tried to restart....same issue, so next I tried to go into cw recovery, no joy, it will not show again.
I can power/vol keys to android fastboot screen with start power restart boot and so on but if I choose recovery nothing happens, I am stuck with either a bootloop or stuck on android fastboot screen and not able to move from either.
I have tried the toolkit and most other things but the problem is it cannot see my nexus 7, even after installing drivers and so on the toolkit (top right) does not list my nexus as found, because of this I cannot reflash any stock firmware/recover/reflash cwr.
Not sure how I can get around this if my pc cannot see the nexus 7.
Thanks for any help
Click to expand...
Click to collapse
try to flash recovery again via fastboot...or doesnt pc recognize divice at all?
S.R
shivasrage said:
try to flash recovery again via fastboot...
S.R
Click to expand...
Click to collapse
Hi
I cannot flash anything. On the fastboot screen I can scroll up and down powr off/start/recovery....if I choose any (apart from power off) nothing happens.
When I hook it up to my pc it cannot see it, nexus 7 toolkit also cannot see it, it does not list it as found so I cannot flash anything on to it, if I try it just says waiting for device, tried other things and same thing either waiting for device or asks if fastboot installed.
voodoochild2008 said:
Hi
I cannot flash anything. On the fastboot screen I can scroll up and down powr off/start/recovery....if I choose any (apart from power off) nothing happens.
When I hook it up to my pc it cannot see it, nexus 7 toolkit also cannot see it, it does not list it as found so I cannot flash anything on to it, if I try it just says waiting for device, tried other things and same thing either waiting for device or asks if fastboot installed.
Click to expand...
Click to collapse
f****
have you tried flashing factory image from google site.with flash all-sh?
shivasrage said:
f****
have you tried flashing factory image from google site.with flash all-sh?
Click to expand...
Click to collapse
I have a image ready but not able to flash....but what is flash all-sh? trying to search for it, is it a tool to force flash?
voodoochild2008 said:
I have a image ready but not able to flash....but what is flash all-sh? trying to search for it, is it a tool to force flash?
Click to expand...
Click to collapse
no its included in the factory image to flash all i one so it looks like for the nexus 4:
flash-all .....its a windows batch image with all included.... try this
S:R.
shivasrage said:
no its included in the factory image to flash all i one so it looks like for the nexus 4:
flash-all .....its a windows batch image with all included.... try this
S:R.
Click to expand...
Click to collapse
Thanks....but still get waiting for device, thats the problem, nothing seems to see it so I cannot flash anything to it.
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
i thought the same as you but fastboot isn recognizig N7 anymore....always wating for device....
Hemidroids said:
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
Click to expand...
Click to collapse
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
[/COLOR]
voodoochild2008 said:
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
Click to expand...
Click to collapse
read this... i hope you can follwow that easily like me...
greets S.R.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
voodoochild2008 said:
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
Click to expand...
Click to collapse
EXE? doh.......Windows.......sorry cant help.
shivasrage said:
[/COLOR]
read this... i hope you can follwow that easily like me...
greets S.R.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Click to expand...
Click to collapse
Tried some of that already but will try again tomorrow.
Thanks for help with this and will post tomorrow if I can sort it. cheers
I hope this instructions can help you a little bit...but if it fails don´t be angry its all I can think of ...at this time ....merry christmas
S.R.
http://forum.xda-developers.com/showthread.php?p=31931117:D
Sent from my Nexus 7 using xda premium
Well after using bits of jrom flasher and nexus toolkit I got it working again, main issue was making the tablet seen, abd and fastboot would not show device.
All up and running again THANKS TO ALL WHO HELPED
voodoochild2008 said:
Well after using bits of jrom flasher and nexus toolkit I got it working again, main issue was making the tablet seen, abd and fastboot would not show device.
All up and running again THANKS TO ALL WHO HELPED
Click to expand...
Click to collapse
How did you get it to work? I have problem getting my device to be recognized. Stuck on boot loop too..
Hey man, how did you get your computer to recognize your device? Would be great to finally fix mine as this is the same exact problem -- computer doesn't recognize it even though in fastboot.
Quacker245 said:
Hey man, how did you get your computer to recognize your device? Would be great to finally fix mine as this is the same exact problem -- computer doesn't recognize it even though in fastboot.
Click to expand...
Click to collapse
I don't understand exactly what you are trying to do, sorry: you said the pc does not see the nexus, "even thought in fastboot".. If you say even thought, it seems to me that you are able to access Android itself or maybe recovery? In that case I can't see the issue.. Sorry my fault, non english mother tongue
But, if have the device soft bricked and you are able to enter ONLY the bootloader (that is what we call often fastboot), then you should start to remove the not working fastboot drivers installed into your PC: launch the nexus in fastboot mode, go to Device Manager into your PC and search for a driver with an yellow exclamation point. This issue is very common so I hope that you have it, too.. So, uninstall that driver, then unlink the nexus from your PC; after a few seconds attach it to another USB port and see if Windows install a driver (it should). If this new driver doesn't work, too, or if Windows does no install any, try this one: http://forum.xda-developers.com/showthread.php?t=1426502
Hope it helps, let us know, see you!
EDIT: also, if you still have no luck, you should find a Linux or Mac PC/laptop and download the adb/fastboot binary files for that OS; this will definitively solve your driver issue ( @#ò#@!"@# Winzozz )
brainvision said:
I don't understand exactly what you are trying to do, sorry: you said the pc does not see the nexus, "even thought in fastboot".. If you say even thought, it seems to me that you are able to access Android itself or maybe recovery? In that case I can't see the issue.. Sorry my fault, non english mother tongue
But, if have the device soft bricked and you are able to enter ONLY the bootloader (that is what we call often fastboot), then you should start to remove the not working fastboot drivers installed into your PC: launch the nexus in fastboot mode, go to Device Manager into your PC and search for a driver with an yellow exclamation point. This issue is very common so I hope that you have it, too.. So, uninstall that driver, then unlink the nexus from your PC; after a few seconds attach it to another USB port and see if Windows install a driver (it should). If this new driver doesn't work, too, or if Windows does no install any, try this one: http://forum.xda-developers.com/showthread.php?t=1426502
Hope it helps, let us know, see you!
EDIT: also, if you still have no luck, you should find a Linux or Mac PC/laptop and download the adb/fastboot binary files for that OS; this will definitively solve your driver issue ( @#ò#@!"@# Winzozz )
Click to expand...
Click to collapse
Hi sorry for not being clear. Basically I am only allowed to access the bootloader and my device is soft-bricked. I'm pretty sure I tried uninstalling and reinstalling the drivers about a year ago when I originally did it, but I'll try again and let you know. Thanks!
*EVERY ACTION YOU PERFORM FOLLOWING THIS GUIDE IS AT YOUR OWN RISK*
That to be said, let's start: i am currently running the latest official nightly build on my d855 and it took me a while to get there. I couldn't find any (real) step-by-step-guide, where i would not have to google any errors or anything else.
Everything you find here is NOT my own knowledge, it is just compilation of sources, that i found on the internet.
Note:
Android 6.0: if you are on 6.0 and you always updated so you're on the latest security-patch-level the one-click-root-method won't work. I recommend downgrading your phone, which will be explained in the following.
Android 5.0: if you're on 5.0 you need to upgrade to 6.0 anyways, bc you need a different baseband-version to install LineageOS. This will also be explained in the following.
1. Make a backup of your phone
this is recommended, although i didn't do this, this is why i am not gonna explain it one here. I just saved my pics and contacts and did a factory reset, restarted my phone, did all the "first time turned on stuff" and connected to my wifi.
Note: Make sure your phone is charged to 60% at least
2. Download the following
a. Download LG G3 Drivers 4.0.4 and install them (i believe there are more recent ones, but this worked for me)
b. Download LG UP
- Download: LG UP Ver. 1.14: LGUP_Install_Ver_1_14_3.msi and LGUP_8974_DLL_Ver_0_5.MSI
- Make sure to install the DLL first and then the other .msi
SOURCE: Thanks to hyelton
c. Download the proper KDZ for you phone.
Note: I got this infos from a german site.
This is the 30C KDZ for the 32gb AND 16gb version: Download here
SOURCE: Thanks to mr bo
3. Downgrade/Upgrade your android-version
1. Turn off your phone.
2. Run LG UP (the tool you just installed) and press okay when you see the error message, that no phone is connected.
3. Press "Volume Up" on your phone and HOLD it, connect your phone to you computer via USB 2.0 PORT! This is important, bc connecting via 3.0 won't let LG UP recognize your phone.
4. Your phone is now in download-mode and LG UP should have recognized your phone.
5. Press SELECT, click on UPGRADE, then click on FILE PATH, choose you prefered .KDZ.
6. i recommend refurbishing your phone (This will wipe your entire system and make a clean install).
CLOSE LG UP and start it back up. The .KDZ should still be there. Now select REFURBISH and click on START. Wait until 100% completed and you phone has booted up completely.
Source and further information: Hail hyelton!
Also here is a youtube video: Thanks to kiaTech
4. Root your phone
1. Download the latest kingroot.apk from here.
2. Connect your phone (turned on, after all the "first time turned on stuff") and move the .apk to your Download-folder.
3. Open the (stock) filemanager on your phone and navigate to Downloads.
4. Install the kingroot.apk (enable third party .apk, when asked)
5. Open the app and root your phone (it's simple, believe me).
6. Your phone is now rooted (leave it turned on, DON'T restart)
5. Install TWRP and update to the latest version
1. Download this pack and unzip it.
2. Move the AutoRecMMD855.apk to your phone and install it just like kingroot.apk before.
3. Open the app and follow the instructions.
4. You now got TWRP on your phone.
SOURCE for #4 and #5 till here: Thanks to tute123456
5. Boot into recovery mode (either with the app itself i think or manually. If you have to do it manually. Turn of your phone. Press POWER and VOLUME DOWN at the same time until the screen shows soemthing. Release and immideatly press again. Your phne will ask you if you want to FACTORY RESET. Press YES and YES. If everything is working properly, TWRP should start up).
6. Connect your phone and download the latest TWRP.img you. In example here's the european one Latest LG G3 TWRP EUROPE
7. I assume you never disconnected your phone since moving kingroot.apk to it. So now you just move the TWRP.img to your Download folder.
8. Choose INSTALL on your phone and search for the TWRP.img. Select RECOVERY and flash it.
9. Choose REBOOT and then RECOVERY.
10. Your phone will boot into TWRP again. It should be updated to the latest version 3.0.2-0.
SOURCE: Thanks to everyone who contributed
6. Flash LineageOS and install GApps
1. Download the latest version of LineageOS (nightly) from here
Optional: make a backup of your phone using TWRP and safe it on your pc or internal SD Card, bc in the next step you will wipe your entire system, to get a clean installation.
2. Press WIPE in TWRP and select ADVANCED WIPE. Select everything but "Micro SD Card" and perform the wipe. This will wipe your entire system!
3. Move the .zip file to the Download folder on your phone and press INSTALL in TWRP. Search for the .zip and flash it.
Note: you'll see two red error messages. This is normal!
4. Wipe cache and dalvik as recommended.
5. Download your desired Open GApps package from here. Use "ARM" and "7.1", i recommend the "mini"-package.
6. Move the downloaded file to your Download folder on your phone and flash it just like you did the LineageOS file.
7. Wipe cache and dalvik.
8. In the main menu of TWRP choose REBOOT and then SYSTEM.
9. It will take a while to boot up, don't worry, just leave it there.
10. You succesfully installed the latest LineageOS build on your phone - you can now unplug your phone from your PC also :good:
SOURCE: LineageOS official wiki
*reserved*
*reserved for further changes*
Hi pheb92,
Big Thank You, If I had to do it bymyself it would have take me hours!!
-3. Downgrade/Upgrade your android-version -- I had trouble finding the right DLL on my Windows 10 system, onetime I managed to use LG - Up. At that moment the DLL loaded was 4.2.0.0. date 23-8-2016 device name "LGE AndroidNet USB Serial Port (COM6)"
- 6. Flash LineageOS and install GApps -- I flashed straight from a uSD card inserted in the LG G3.
Thank you for the great Setp-by-Step!
Regards, Onedutch
onedutch said:
Hi pheb92,
Big Thank You, If I had to do it bymyself it would have take me hours!!
-3. Downgrade/Upgrade your android-version -- I had trouble finding the right DLL on my Windows 10 system, onetime I managed to use LG - Up. At that moment the DLL loaded was 4.2.0.0. date 23-8-2016 device name "LGE AndroidNet USB Serial Port (COM6)"
- 6. Flash LineageOS and install GApps -- I flashed straight from a uSD card inserted in the LG G3.
Thank you for the great Setp-by-Step!
Regards, Onedutch
Click to expand...
Click to collapse
hi onedutch. i am glad, that i could help you. concerning your quotes: are those questions? do you need any further help?
pheb92 said:
hi onedutch. i am glad, that i could help you. concerning your quotes: are those questions? do you need any further help?
Click to expand...
Click to collapse
Those are remarks, I think it could help others if they run in trouble aswell.
Cheers, Tom
unrooted?
i did everythimg step by step.right now im running lineage OS. the problem is that rootchecker says im unrooted.im also tryimg to setup supersu from play store but it cant staart cause it says im unrooted.any ideas here? thanks in advance!!
teridona said:
i did everythimg step by step.right now im running lineage OS. the problem is that rootchecker says im unrooted.im also tryimg to setup supersu from play store but it cant staart cause it says im unrooted.any ideas here? thanks in advance!!
Click to expand...
Click to collapse
as far as i know LineageOS doesn't have an inbuilt root access (so far) like cyanogenmod did. you can only enable root access via adb in the developer options.
i did not root lineageOS myself so far, but you can try the following:
- Download superSU.zip from their official website and flash it via TWRP.
i would appreciate it, if you would share the outcome
pheb92 said:
as far as i know LineageOS doesn't have an inbuilt root access (so far) like cyanogenmod did. you can only enable root access via adb in the developer options.
i did not root lineageOS myself so far, but you can try the following:
- Download superSU.zip from their official website and flash it via TWRP.
i would appreciate it, if you would share the outcome
Click to expand...
Click to collapse
LineageOS does have built in root management, but it doesn't ship rooted by default.
This change was made so SafetyNet doesn't get triggered by root and you can use Android Pay on your device.
Just download the su zip from LineageOS download page and flash.
pheb92 said:
3. Downgrade/Upgrade your android-version
1. Turn off your phone.
2. Run LG UP (the tool you just installed) and press okay when you see the error message, that no phone is connected.
3. Press "Volume Up" on your phone and HOLD it, connect your phone to you computer via USB 2.0 PORT! This is important, bc connecting via 3.0 won't let LG UP recognize your phone.
4. Your phone is now in download-mode and LG UP should have recognized your phone.
Click to expand...
Click to collapse
I am stuck on this step. My d855 gets into download mode and LG UP recognizes the phone, but I'm getting the "You have to select a known model, please" error in LG UP. I have uninstalled and reinstalled LG UP and the DLL multiple times, same problem. I also tried uninstalling and reinstalling the driver, and I tried other drivers, same problem. I tried the tip in another thread (https://forum.xda-developers.com/showthread.php?t=2785089) to change the port to COM41 in device manager, but it didn't help. Btw I also unrooted my d855 (it has 4.4.2 currently) in case that's why the tool couldn't recognize it. Please help!!
Also @hyelton if you can help...
@engmia since you were helping me earlier...
Thanks.
supperbowl said:
I am stuck on this step. My d855 gets into download mode and LG UP recognizes the phone, but I'm getting the "You have to select a known model, please" error in LG UP. I have uninstalled and reinstalled LG UP and the DLL multiple times, same problem. I also tried uninstalling and reinstalling the driver, and I tried other drivers, same problem. I tried the tip in another thread (https://forum.xda-developers.com/showthread.php?t=2785089) to change the port to COM41 in device manager, but it didn't help. Btw I also unrooted my d855 (it has 4.4.2 currently) in case that's why the tool couldn't recognize it. Please help!!
Also @hyelton if you can help...
@engmia since you were helping me earlier...
Thanks.
Click to expand...
Click to collapse
hi supperbowl,
are you sure you're using a USB 2.0 port and the original LG-USB-Cable, that came with the phone?
as far as i experienced it, 4.4.2 should not be an issue.
supperbowl said:
I am stuck on this step. My d855 gets into download mode and LG UP recognizes the phone, but I'm getting the "You have to select a known model, please" error in LG UP. I have uninstalled and reinstalled LG UP and the DLL multiple times, same problem. I also tried uninstalling and reinstalling the driver, and I tried other drivers, same problem. I tried the tip in another thread (https://forum.xda-developers.com/showthread.php?t=2785089) to change the port to COM41 in device manager, but it didn't help. Btw I also unrooted my d855 (it has 4.4.2 currently) in case that's why the tool couldn't recognize it. Please help!!
Also @hyelton if you can help...
@engmia since you were helping me earlier...
Thanks.
Click to expand...
Click to collapse
Have you tried it with the phone booted into the OS? With USB debugging on? Also if running 4.4.2 why not just use the old method?
Sent from my iPhone using Tapatalk
hyelton said:
Have you tried it with the phone booted into the OS? With USB debugging on? Also if running 4.4.2 why not just use the old method?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
No I've only tried it with download mode. I have USB debugging enabled in the OS. I am now trying the old method with LG flash tool, so far I'm getting stuck with the LG mobile support tool which keeps saying "upgrade stopped due to an error".
Edit: LG UP doesn't recognize the handset at all with it booted into the OS.
pheb92 said:
hi supperbowl,
are you sure you're using a USB 2.0 port and the original LG-USB-Cable, that came with the phone?
as far as i experienced it, 4.4.2 should not be an issue.
Click to expand...
Click to collapse
Yes it's USB 2.0 and the original cable.
supperbowl said:
No I've only tried it with download mode. I have USB debugging enabled in the OS. I am now trying the old method with LG flash tool, so far I'm getting stuck with the LG mobile support tool which keeps saying "upgrade stopped due to an error".
Yes it's USB 2.0 and the original cable.
Click to expand...
Click to collapse
Just use lgup with the device booted into android
Sent from my iPhone using Tapatalk
hyelton said:
Just use lgup with the device booted into android
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
LG UP doesn't recognize the device at all with it booted into Android, the "Model List" comes up empty.
supperbowl said:
LG UP doesn't recognize the device at all with it booted into Android, the "Model List" comes up empty.
Click to expand...
Click to collapse
And USB debugging enabled?
If it's at least detecting unknown device while in download mode it most definitely should show up in lgup when boot up.
Choose MTP mode? And it's not just in "charging mode" or try vice versa?
Sent from my iPhone using Tapatalk
hyelton said:
And USB debugging enabled?
If it's at least detecting unknown device while in download mode it most definitely should show up in lgup when boot up.
Choose MTP mode? And it's not just in "charging mode" or try vice versa?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Yes, USB debugging is enabled and my computer is allowed permissions.
Yes it's MTP and I also tried charge only and LG software modes. With LG Software mode it comes up with the unknown device in the model list again.
supperbowl said:
Yes, USB debugging is enabled and my computer is allowed permissions.
Yes it's MTP and I also tried charge only and LG software modes. With LG Software mode it comes up with the unknown device in the model list again.
Click to expand...
Click to collapse
what also worked for me once was just retrying the process --> turn off, go into LG UP, go into download-mode. if LG UP does not recognize the phone: put the battery out of your phone, close LG UP and start the process again (also with different USB ports and other USB-Cables).
Hello,
Need to have unlocked bootloader ? Work on SEA version ?
You did not installed LG UP DLL properly
supperbowl said:
I am stuck on this step. My d855 gets into download mode and LG UP recognizes the phone, but I'm getting the "You have to select a known model, please" error in LG UP. I have uninstalled and reinstalled LG UP and the DLL multiple times, same problem. I also tried uninstalling and reinstalling the driver, and I tried other drivers, same problem. I tried the tip in another thread (https://forum.xda-developers.com/showthread.php?t=2785089) to change the port to COM41 in device manager, but it didn't help. Btw I also unrooted my d855 (it has 4.4.2 currently) in case that's why the tool couldn't recognize it. Please help!!
Also @hyelton if you can help...
@engmia since you were helping me earlier...
Thanks.
Click to expand...
Click to collapse
1) Remove LG UP DLL completey
2)Install the LG UP DLL again
3)Put your phone into recovery mode, wipe data and cahce
4)put your phone into download mode, then run the LG UP
Hello guys. I have the x720 leeco. My problem is that i wiped all and no rom is installed and when i connect the phone to the pc i cant get it done with the drivers so i cant see the internal storage. I can boot on REcovery and Fastboot. Can anyone help me??
Thanks in advance
TrelosEisai said:
Hello guys. I have the x720 leeco. My problem is that i wiped all and no rom is installed and when i connect the phone to the pc i cant get it done with the drivers so i cant see the internal storage. I can boot on REcovery and Fastboot. Can anyone help me??
Thanks in advance
Click to expand...
Click to collapse
Put the rom on an USB stick, connect the stick to the phone with adapter, go into TWRP and flash the rom.
Easyest solution.
Okk i ll try it
Unlucky cant read otg, just putted an micro usb to typec adapter and a micro usb flash drive and cant see it
TrelosEisai said:
Unlucky cant read otg, just putted an micro usb to typec adapter and a micro usb flash drive and cant see it
Click to expand...
Click to collapse
Ok. Than try to flash a stock rom through all in one tool:
https://www.google.com/amp/s/forum....ment/tool-tool-one-mauronofrio-t3580611/amp/5
Oel said:
Ok. Than try to flash a stock rom through all in one tool:
https://www.google.com/amp/s/forum....ment/tool-tool-one-mauronofrio-t3580611/amp/5
Click to expand...
Click to collapse
Agreed,
You are not bricked.
i cant see my device thats the problem
TrelosEisai said:
i cant see my device thats the problem
Click to expand...
Click to collapse
Worst case you can use Qfil.
But first disconnect all unneeded peripherals, and try another cable if possible. Go read the unbricked tested and working. Search the thread for my name, to everything you need in 3 or four posts
Sent from my Pixel XL using XDA Labs
TrelosEisai said:
i cant see my device thats the problem
Click to expand...
Click to collapse
Yeah, but did you installed the all in one thing with the right drivers?
Oel said:
Yeah, but did you installed the all in one thing with the right drivers?
Click to expand...
Click to collapse
which drivers?? i cant do the qfil cause i cant see the phone in pc. when i open it in leeco logo when i connect the phone to pc it says windows cant recognize it.
TrelosEisai said:
which drivers?? i cant do the qfil cause i cant see the phone in pc. when i open it in leeco logo when i connect the phone to pc it says windows cant recognize it.
Click to expand...
Click to collapse
Go read the unbricking thread, it is going to take you days to read, understand, and finally unbrick it. If you are not seeing the device in the system manager of your computer ( Assuming you have a PC) then maybe you are actually bricked.
But, you own a phone that can be unbricked, no not a big deal. It can be resolved, the instructions in the unbricked tested and working thread are explicit go read it.
I create several how to's within that thread on unbricking, and have updated the links on the software tools needed. I have personally unbricked 7 leeco, and several others unbricked their phones by following the advice of everyone who contributed to the thread.
Everything you need and more is there that thread, waiting for you.
Go there get the files, read the instructions and soon you phone will work again. Do not download the qfil from the Original post...it doesn't work. I don't have the links to paste at the moment, nor the time to search for you Just use the thread search bar and type my name to get consolidated steps read through all of the posts, because its a progression.
There are three methods you can use to unbrick, the easiest method is probably Qfil, and Flash 2.0
Essentially you need the Qfil: le_zl1_qfil_ufs_fix , FlashOne2.0 files, go ahead and download prog_ufs_firehose_8996_ddr just in case. But it should download automatically. You need to follow the steps to get your computer ready to unbrick the phone...all in the thread instructions.
Once you do it once successfully, it will become easier with each try.
tsongming said:
Go read the unbricking thread, it is going to take you days to read, understand, and finally unbrick it. If you are not seeing the device in the system manager of your computer ( Assuming you have a PC) then maybe you are actually bricked.
But, you own a phone that can be unbricked, no not a big deal. It can be resolved, the instructions in the unbricked tested and working thread are explicit go read it.
I create several how to's within that thread on unbricking, and have updated the links on the software tools needed. I have personally unbricked 7 leeco, and several others unbricked their phones by following the advice of everyone who contributed to the thread.
Everything you need and more is there that thread, waiting for you.
Go there get the files, read the instructions and soon you phone will work again. Do not download the qfil from the Original post...it doesn't work. I don't have the links to paste at the moment, nor the time to search for you Just use the thread search bar and type my name to get consolidated steps read through all of the posts, because its a progression.
There are three methods you can use to unbrick, the easiest method is probably Qfil, and Flash 2.0
Essentially you need the Qfil: le_zl1_qfil_ufs_fix , FlashOne2.0 files, go ahead and download prog_ufs_firehose_8996_ddr just in case. But it should download automatically. You need to follow the steps to get your computer ready to unbrick the phone...all in the thread instructions.
Once you do it once successfully, it will become easier with each try.
Click to expand...
Click to collapse
Ok i am starting now i will come back with the results
As i understand my phone is not bricked cause i can go into fastboot and REcovery. The problem is i dont have OS installed so i stuck at Leeco image. The other problem is when i connect the phone with the Pc this happens on device manager. So how i can make it to see the internal storage and put inside the phone the rom.
TrelosEisai said:
As i understand my phone is not bricked cause i can go into fastboot and REcovery. The problem is i dont have OS installed so i stuck at Leeco image. The other problem is when i connect the phone with the Pc this happens on device manager. So how i can make it to see the internal storage and put inside the phone the rom.
Click to expand...
Click to collapse
Install Google's USB ADB and Fastboot drivers.
https://developer.android.com/studio/run/win-usb
Can you boot into download mode (I think it's volume down + power) and then connect to PC. After that, you should see the unknown device on device manager. Try to right-click on it and update drivers. On the next screen, select that you have drivers and you'd like to pick your own (not the Windows Update option!) Then select Manufacturer Google and Fastboot/ADB debugging option. Device might work in fastboot now, you can test by doing "fastboot devices". If that works, then you can install ROM via Fastboot.
If this doesn't work, you can revert changes by going into device manager and uninstalling the driver for that device.
Ascertion said:
Install Google's USB ADB and Fastboot drivers.
https://developer.android.com/studio/run/win-usb
Can you boot into download mode (I think it's volume down + power) and then connect to PC. After that, you should see the unknown device on device manager. Try to right-click on it and update drivers. On the next screen, select that you have drivers and you'd like to pick your own (not the Windows Update option!) Then select Manufacturer Google and Fastboot/ADB debugging option. Device might work in fastboot now, you can test by doing "fastboot devices". If that works, then you can install ROM via Fastboot.
If this doesn't work, you can revert changes by going into device manager and uninstalling the driver for that device.
Click to expand...
Click to collapse
I cant find the option for Manufacturer Google for the Fastboot/Adb debugging options
TrelosEisai said:
I cant find the option for Manufacturer Google for the Fastboot/Adb debugging options
Click to expand...
Click to collapse
Hi, sorry for the late reply.
Are you able to see these in screenshots? Between steps 2 and steps 3, you might need to select Android ADB or Android Device before you can see Google in the dropdown.
Maybe after these you might be able to see device in fastboot?