[Q&A] [TOOL] WinDroid Universal Android Toolkit | Unlock | Root | Flash | G Watch R - LG G Watch R

[Q&A] [TOOL] WinDroid Universal Android Toolkit | Unlock | Root | Flash | G Watch R
Q&A for [TOOL] WinDroid Universal Android Toolkit | Unlock | Root | Flash | G Watch R
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TOOL] WinDroid Universal Android Toolkit | Unlock | Root | Flash | G Watch R. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

toenail78 said:
thank you for this app.. i rooted my watch with ease..
Click to expand...
Click to collapse
I stuck on the screen "unlocking bootloader", i cant choose to OK ....
is there any solution?

make sure you are in fastboot.. to enter fastboot power off your watch and as soon as you boot up swipe your finder from the 10'oclock to 4'oclock position while the lg logo is displayed.. then run the toolkit

TWRP not working
Hi. My problem is that everything went fine untill unlocking the bootloader. in the 3rd step pushing the superSU zip and should reboot to TWRP but instead it goes to recovery mode. the program reports success in all steps. but TWRP just not working,, on LG G WATCH R
Please help.
That problem solved. now i got a much bigger.. TWRP working. but im stuck in TWRP. no mether how i reboot or restart it never boot anymore to system or recovery. it starts TWRP instead.
Problem resolved

...

The link in the OP to the actual tool does not seem to work...

Cannot load a ROM after TWRP installed
I successfully unlocked the bootloader and flashed the recovery, but I must be missing a step to flash a ROM. I put the phone into ADB Sideload mode and select a ZIP file for the 5.1.1 ROM. After only a few seconds it says it was successful and that my watch should be flashing the ROM, but the watch isnt doing anything (just sitting on the ADB sideload screen).

How did you resolve first problem. Can't get to twrp. Running 5.1.1 unlocked.
Fixed by relocking BL. Then starting over. Now can't flash system.IMG for leedroid. Ugh. Bad day for me.
Sent from my Nexus 6 using XDA Free mobile app

Hey. Just unlocked and then flashed twrp using this app. Now rebooting watch always goes to twrp recovery. Any ideas? Now on twrp 2.8.6.1.
Also when trying to mount gives error. Can't mount data
Enviado do meu LG-D802 através de Tapatalk

It's better not to use winDroid it has to many bugs for me it's not good when I tried it for several times stays on twrp when set to reboot system. Go for cmd line that's the best way.

asus5 said:
It's better not to use winDroid it has to many bugs for me it's not good when I tried it for several times stays on twrp when set to reboot system. Go for cmd line that's the best way.
Click to expand...
Click to collapse
Just flash the recovery on cmd? And the flash the rom?
Enviado do meu LG-D802 através de Tapatalk

I'm rebooting straight into TWRP each time. Is there a fix for this?
*I flashed TWPR 2.8.6.1 and then flashed the LeeDroid ROM using minimal ADB and I am still getting straight to TWRP reboot. What did I miss.
After a lot of flashing I've finally escaped TWRP after bootlooping and bricking my watch. I followed this guide
forum.xda-developers.com/g-watch-r/development/emergency-guide-how-to-blank-regenerate-t2984678 but used 5.1 files instead since I was already on 5.1 prior.

Caution everyone don't use this to flash TWRP, it flashes TWRP to the system instead of the recovery image so you won't be able to boot into android and you'll get errors trying to mount the images!! If you want TWRP just use fastboot to flash it!

BrickStar said:
I'm rebooting straight into TWRP each time. Is there a fix for this?
*I flashed TWPR 2.8.6.1 and then flashed the LeeDroid ROM using minimal ADB and I am still getting straight to TWRP reboot. What did I miss.
After a lot of flashing I've finally escaped TWRP after bootlooping and bricking my watch. I followed this guide
forum.xda-developers.com/g-watch-r/development/emergency-guide-how-to-blank-regenerate-t2984678 but used 5.1 files instead since I was already on 5.1 prior.
Click to expand...
Click to collapse
Hi, i have exactly the same problem...flash trwp with this crap software and my watch keeps booting on TRWP...
I want to use your method, but my watch is no longer recognize by adb drivers... Is there something i must do on the watch? Please help, i have my watch since 2 days only...

darsonic said:
Hi, i have exactly the same problem...flash trwp with this crap software and my watch keeps booting on TRWP...
I want to use your method, but my watch is no longer recognize by adb drivers... Is there something i must do on the watch? Please help, i have my watch since 2 days only...
Click to expand...
Click to collapse
Ok i juste did it!!! Finaly i managed to flash stock rom and recovery...

Related

[Q&A] [RECOVERY][victara] TWRP 2.8.0.1 touch recovery [2014-10-20]

Q&A for [RECOVERY][victara] TWRP 2.8.0.1 touch recovery [2014-10-20]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][victara] TWRP 2.8.0.1 touch recovery [2014-10-20]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
dmbfan13 said:
Has anyone been able to install via TWRP Manager? every time i select "select device", it crashes. Anyone else?
Click to expand...
Click to collapse
I was unable to install via adb, so i tried using the app, it worked perfect.
Question
Hi, first at all: sorry my english, i'm a little rust; i have an Moto X 2014 (xt1097), with Android Lollipop (22.21.17.victara_retbr.retbr.en.BR amxcl), does this version of TWRP works 100%? O almost? i'm most interested to get Root and instal a recovery, my (sold) Moto x 2013, have TWRP and root. honestly, i want root to use Power Toogles, should i have to change the recovery? Or only with root can use it?
Twrp is good except time and date
Question
michyall said:
Twrp is good except time and date
Click to expand...
Click to collapse
Hi, sorry but what do you mean about time and date? It changes time and date on cellphone? Thanks
Yup. Every time i go into twrp date is wrong. Usually 6 days before and time wrong too.
When booting phone i get whatsapp time and date error: no trouble, when radio signal is up android is synchronizing and everything return right. Except twrp.
Have read about a bug
Cant make a backup TWRP
I get the error:
Backup complete. Failed.
unable to create backup folder errno=13
Using either twrp-2.8.6.0-victara or twrp-2.8.5.0-victara
Before trying to use 2.8.6 I could.
Thanks
Revert back to stock recovery on xt1092?
So I flashed TWRP on my xt1092 but I want to revert back to stock recovery. How to do it? My Moto X came with lollipop 5.0 with build no. LXE22.46-19
5.1 Support
Just upgraded to the 5.1 soak test (23.1.28) from a clean 22.46-11 installation and can no longer flash twrp (I tried 2.8.0.3, 2.8.0.5, 2.8.0.6, and crpalmer's unofficial build). They all complain about mismatched partition size, and if the flash is successful the recovery partition must be overwritten immediately by the stock recovery. I'm hoping someone comes up with a workaround or new build soon.
kevind23 said:
Just upgraded to the 5.1 soak test (23.1.28) from a clean 22.46-11 installation and can no longer flash twrp (I tried 2.8.0.3, 2.8.0.5, 2.8.0.6, and crpalmer's unofficial build). They all complain about mismatched partition size, and if the flash is successful the recovery partition must be overwritten immediately by the stock recovery. I'm hoping someone comes up with a workaround or new build soon.
Click to expand...
Click to collapse
Flash from within Android and it will stick.
korockinout13 said:
Flash from within Android and it will stick.
Click to expand...
Click to collapse
How can I do that? Thanks!
EDIT - I'm an idiot, I didn't boot into recovery straight away after flashing the image, so it was overwritten on boot up.
kevind23 said:
How can I do that? Thanks!
EDIT - I'm an idiot, I didn't boot into recovery straight away after flashing the image, so it was overwritten on boot up.
Click to expand...
Click to collapse
Sent from my XT1095 using XDA Free mobile app
Guys, fast question. I've flash stock firmware, flash twrp latest version, then cm and start setting up, deleted some apps wipe Cache and dalvik and when I tried to reboot into recovery to flash a kernel it just boot loops into recovery boot image.... Phone is working great, but can't get into recovery.... Any idea? Already tried flashing previous version and same result
Enviado desde mi XT1095 mediante Tapatalk
I installed this recovery 1 month ago, but now i am trying to boot into recovery but it stucks on TWRP screen, there are no menus like backup, install etc, it just stucks on twrp blue screen. Even i flashed older twrp 2.8.x.x by fastboot mode but same thing happens only twrp blue screen...?
Could someone help me?
P.S: it was working fine 1 month ago when i flashed RR.
I have the exact same issue on my Xt1060. It has flashed several Roms fine, but hangs up on the TWRP blue screen too! I also reflashed 2.8.7.1 with no difference. Any ideas?
I uninstalled twrp and rebooted the phone. I then reinstalled twrp using 2.8.6.0 version. I rebooted and tried opening the recovery. It now works fine. I have since installed the cyanpop nightly and updated happy. Phone works!!!! Not sure why but it does. I will stay with the older version. Thanks.
Guys, I'm having this problem, I'm on 3.0.0.0 and every time I wipe Cache and dalvik/art Cache (I'm on stock marshmallow only tip root and krait kernel) it doesn't wipe anything..... Any idea? Or what do I have to do?
Enviado desde mi XT1097 mediante Tapatalk
On version 3.0.2-2 I get a corrupt zip file error every time I try to flash. This has happened 5 times since encrypting the phone with two different ZIP files.
Is this due to TWRP not supporting Nougat encryption?
Is this resolved in 3.1.0?
Sent from my 2014818 using Tapatalk

[Q&A] [RECOVERY][shamu] TWRP 2.8.2.0 touch recovery [2014-11-19]

Q&A for [RECOVERY][shamu] TWRP 2.8.2.0 touch recovery [2014-11-19]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][shamu] TWRP 2.8.2.0 touch recovery [2014-11-19]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Can't find device listed in app
Maybe I'm missing something, but I can't find the device listed in the app to install the recovery.
I ran CF-auto, then rebooted and installed the TWRP app and busybox, granted permissions, but I don't see the device listed. Did I do something wrong?
I checked for "Nexus 6", "Shamu", and "Motorola Nexus" and couldn't find anything. Sorry if this is a noob question and I'm missing something easy.
Its possible that the app hasn't been updated to include shamu. Just download it from their website and manually flash it via bootloader mode. But then again I see the app has been updated, follow the instructions
http://www.teamw.in/project/twrp2/270
Edit: Someone in the thread confirmed its not in the app yet. Manually fastboot flash it.
Done!
Thanks for the speedy reply!
Sent from my Nexus 6 using XDA Free mobile app
I'm flashing twrp with fastboot, but the recovery will not stick. I'm not rooted. I flash tarp recovery, reboot the boot loader, go into twrp recovery, select reboot system. When I try to get into recovery again, I just get the stock recovery. Any help? If I rename tarp recovery to recovery.IMG and flash it will this perhaps eliminate this backup recovery.img I'm having a problem with?
Solution: in /system rename the file recovery-from-boot.p to something else. This will allow the recovery to stick. I flashed twrp. Within TWRP I used twrp options to: mount the system then used twrps file manager to rename the file.
Sent from my Nexus 6 using Tapatalk
TWRP not 'sticking'
Another user mentioned earlier in this thread that TWRP isn't persistent, and recovery reverts to stock after a full reboot. Anyone else seeing this? Any tips on avoiding it?
This person also reports the same issue in the development section TWRP post: http://forum.xda-developers.com/showpost.php?p=56907694&postcount=35
twrp crashed att nexus 6!!!
Can somebody help me out?
I installes twrp manager theb i went select the model and it crashes.
Has someone tried to use the QHD material theme in TWRP?
I mean this: http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
Does anyone have a flashable zip for Twrp 2.8.2.0? Some how I'm using TWRP 2.8.2.1 AND everything I flash isn't working. I tried to down grade by TWRP IMG and its not working thx in advance
NEXUS 6/TEAM BLACKOUT
freddienux said:
Does anyone have a flashable zip for Twrp 2.8.2.0? Some how I'm using TWRP 2.8.2.1 AND everything I flash isn't working. I tried to down grade by TWRP IMG and its not working thx in advance
NEXUS 6/TEAM BLACKOUT
Click to expand...
Click to collapse
there is no twrp 2821 for shamu did you flash the wrong recovery? 2820 is the only version and you can use flashify to flash the img, flashify is available in the market
---------- Post added at 12:36 PM ---------- Previous post was at 12:35 PM ----------
mouse100 said:
Has someone tried to use the QHD material theme in TWRP?
I mean this: http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
Click to expand...
Click to collapse
yup it works great use 1440x2560 Themes (ported by @gaich)
Circaflex said:
there is no twrp 2821 for shamu did you flash the wrong recovery? 2820 is the only version and you can use flashify to flash the img, flashify is available in the market
Click to expand...
Click to collapse
This is not true. I unlocked bootloader, rooted, and flashed TWRP on Thanksgiving day. The TWRP image that I downloaded from their site is most definitely 2.8.2.1, and is for Shamu.
And it works just fine for me. Wiping, flashing, etc.
Sent from Shamu
freddienux said:
Does anyone have a flashable zip for Twrp 2.8.2.0? Some how I'm using TWRP 2.8.2.1 AND everything I flash isn't working. I tried to down grade by TWRP IMG and its not working thx in advance
NEXUS 6/TEAM BLACKOUT
Click to expand...
Click to collapse
I am also having issues with flashing ROMs. I am able to backup/restore with no issues. I was barely able to get Euphoria-OS installed (home screen wasn't setup correctly after first boot). I am going to reflash back to stock and start over again. Is there anyone else with this issue? I do have the 64gb T-mo variant.
Is anyone else having an issue with the vibration? I flashed the most current build and I can't disable it. There should be 3 sliders in the menu but I only have 2 and the one to disable vibration is gone and it just says "80". I would really appreciate any help with this
I also tried flashing other builds for shamu with the same issue.
Nexus 6 Can someone help please! I'm trying to restore backup and its restoring but it stuck restoring @962 [email protected] data part. Its been stuck on that stage for awhile now
I'm not sure what happened either. I installed the 2.8.2.0 image, but ended up with 2.8.2.1. Flashed back to stock recovery, reinstalled twrp 2.8.2.0, and again it's 2.8.2.1.. It hangs forever when flashing roms.. I would love a flashable 2.8.2.0 zip.
Sent from my Nexus 6 using XDA Free mobile app
Anyone gotten a bootloop from wiping the cache?
So I tried to update with the twrp app and got a notification that instructed me to double check that the correct partition path is "dev/block/platform/msm_sdcc.1/by-name/recovery".
I looked through es browser and found that file, but wanted to double check that I won't ruin anything my continuing.
Sent from my Nexus 6 using XDA Free mobile app
how to update TWRP if stock on bootloop
my situation:
nexus 5
(android 4.4.2)
rooted
encrypted (i have set a pattern to unlock)
TWRP 2.6.3.4.
Xposed module (not sure which version or if it is relevant at all)
suddenly, while i was surfing the twitter app, the phone restarted and attempted to install an update (not sure if it was 4.4.3 or 5.0).
The phone went into bootloop. I held the power button and volume down and this took me into bootloader. from there i started TWRP. I was greeted with "please enter your password". I entered my pattern following the below arrangement
1 2 3
4 5 6
7 8 9
after several attempts which always ended with "Password failed. Please try again" i hit "cancel". This took me to the main TWRP screen. I hit "mount" to find the following..
"Select Partition to Mount:"
[ ] System
[ ] Cache
[ ] Persist
[ ] firmware
[ ] USB-OTG
below them there is a line that says "Storage: Internal Storage (0 MB)"
below that it says "Decrypt Data". If i touch it, it asks to enter my password. Again, i enter my password and it says password failed.
The log has this:
Updating Partition details...
E:Unable to mount ' /cache'
E:Unable to mount ' /persist'
E:Unable to mount storage
E:Unable to mount ' /cache'
E:Unable to mount ' /cache'
E:Failed to decrypt data.
IMHO, i think that i need to have TWRP 2.8.2.0 at least in order to decrypt my data as previous versions don't support decryption and/or pattern passwords. Am i right?
if so, how can i update TWRP to the latest version ? can it be updated from within TWRP itself ?
flashing usig ubuntu fails
Hi there,
i tried flashing recent version of TWRP from ubuntu. All i tried was "fastboot oem unlock" and "fastboot flash recovery openrecovery-twrp-2.8.4.0-shamu.img"
When i try to restart my phone, the "teamwip" screen just flashes. And i am stuck with that... Any idea or any kind of work around for this??
deepujames said:
Hi there,
i tried flashing recent version of TWRP from ubuntu. All i tried was "fastboot oem unlock" and "fastboot flash recovery openrecovery-twrp-2.8.4.0-shamu.img"
When i try to restart my phone, the "teamwip" screen just flashes. And i am stuck with that... Any idea or any kind of work around for this??
Click to expand...
Click to collapse
In my haste to unlock and root, i did the same thing when I got my shamu back in December. After you unlock, you have to boot into android once, "fastboot reboot", then go back to the bootloader and fastboot flash recovery. There might be an easier way, but I just downloaded and flashed the factory images to correct my derp.

[Q&A] [GUIDE][HOW-TO] Root Moto G 2014 WITHOUT flash a custom recovery

Q&A for [GUIDE][HOW-TO] Root Moto G 2014 WITHOUT flash a custom recovery
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE][HOW-TO] Root Moto G 2014 WITHOUT flash a custom recovery. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Error
thomstrack said:
What is this?
I have seen several people wanting to root on your Moto G 2014 and not doing because they do not want to install a custom recovery, and stick with the stock recovery to receive OTA updates. After some research and a little study, i made this procedure and it worked perfectly on my Moto G XT1069. Here we go!
Note:
Tested on Moto g 2014 DTV XT1069 (Sotck KitKat 4.4.4), but should work on other versions of Moto G 2014 also.
Requirements:
- Unlocked bootloader
- Usb debugging enable on your phone.
- Adb and Fastboot into your PC: Donwload
- Custom recovery: Donwload
- Latest SuperSu: Download
Instructions:
- Copy SuperSu from your SDcard;
- Open CMD or Terminal into the folder where you placed the Custom recovery and reboot on bootloader:
Code:
adb reboot bootloader
- After reboot in bootloader, boot on temp custon recovery:
Code:
fastboot boot recovery_file_downloaded.img
- Your phone will restart in temporary Custon Recovery.
- Now just flash the SuperSU (which you copied to your sdcard before)
- Reboot system
- Enjoy!
Credits:
Snoop05 (Adb and Fastboot drivers)
adrianom (TWRP Custom recovery)
Chainfire (SuperSu)
Click to expand...
Click to collapse
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Moto G2014 (XT1063) - With Lollipop
blopez23 said:
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Moto G2014 (XT1063) - With Lollipop
Click to expand...
Click to collapse
This error its in adb, adb don't find device.
You need install Adb and Fastboot into your PC and Motorola drivers.
Wolfcity said:
Is it possible to root the moto g (after unlockling the bootloader) with "fastboot boot recovery.img" without making any changes but the installed Super SU-zip like in this thread for Lenovo? http://forum.xda-developers.com/showthread.php?t=2597590
Can I use the recovery from here? http://forum.xda-developers.com/mot...covery-cwm-philz-touch-6-moto-g-2014-t2896586 ?
and enter bootloader, type fastboot command
fastboot boot CWM_Touch_Titan.img
and then flash SuperSU zip from Recovery?
Click to expand...
Click to collapse
I asked about this procedure in another thread a little while ago and just to be sure:
If I do so I can recieve lollipop ota with the unlocked bootloader,only thing to do may be using full unroot in superSU?
Nothing more to do?
Anyone?
Sent from my XT1068 using XDA Free mobile app
thomstrack said:
This error its in adb, adb don't find device.
You need install Adb and Fastboot into your PC and Motorola drivers.
Click to expand...
Click to collapse
Motorola driver's and adb are installed, I may need to try again
I rooted my phone following the post, now i had a little problem, when the phone started super su was installed correctly, everything looked right, but when i took a photo i couldn't save it. I don't know what to do, thanks for the guide ?, now i hope that somebody help me.
Moto G XT1063 Android 5.0.2 Stock
eltejeiro said:
I rooted my phone following the post, now i had a little problem, when the phone started super su was installed correctly, everything looked right, but when i took a photo i couldn't save it. I don't know what to do, thanks for the guide , now i hope that somebody help me.
Moto G XT1063 Android 5.0.2 Stock
Click to expand...
Click to collapse
Where do you try to save the photos? External SD or internal storage? Have you tried to save some other data there? Maybe you have no write permisson?
Else you can try another photo app just to check that out.
Wolfcity said:
Where do you try to save the photos? External SD or internal storage? Have you tried to save some other data there? Maybe you have no write permisson?
Else you can try another photo app just to check that out.
Click to expand...
Click to collapse
I tried to save in both, internal storage and external sd, but anything worked, with other kind of data it's the same, you know how can i change the write permisson?
Thanks for answering ☺☺

[Q&A] [ROM] [3/18] Stock Rooted 5.1 - LMY47E - Root, Busybox, init.d - Odex / DeOdex

[Q&A] [ROM] [3/18] Stock Rooted 5.1 - LMY47E - Root, Busybox, init.d - Odex / DeOdex
Q&A for [ROM] [3/18] Stock Rooted 5.1 - LMY47E - Root, Busybox, init.d - Odex / DeOdex
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [3/18] Stock Rooted 5.1 - LMY47E - Root, Busybox, init.d - Odex / DeOdex. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
thank u so much.do we flash firmware in recovory? because it gives me error msg when i do
reazon87 said:
thank u so much.do we flash firmware in recovory? because it gives me error msg when i do
Click to expand...
Click to collapse
No it has to be flashed from PC in bootloader mode on the phone.
I have the D build flashed but its not decrypted so is it OK for me to flash your E build since it's decrypted
Verizon
I have flashed many roms on many devices over the years, I would say I have moderate to expert knowledge of the process and practice.
When I flash this on my (newly received Verizon) Nexus 6, it boots to a black screen. I can hold power and see the "power off" option, but that is it.
Here is the actions I took:
Fastboot
OEM Unlock
ChainFire Auto Root Nexus 6
Boot and Verify SU Binaries
Reboot into TWRP
Wipe Cache/Davlik/System/Data
Flash Odex (also tried De-Odex) Rom
Reboot
I tried using your Radio and Bootloader files, as well as the latest ones in the Nexus 6 factor image file hosted by Google, same result.
Any thoughts on why this might happen?
I have since manually flashed system, cache, boot, and userdata from the stock image and booted fine with root (and am currently running this).
Domosham said:
I have flashed many roms on many devices over the years, I would say I have moderate to expert knowledge of the process and practice.
When I flash this on my (newly received Verizon) Nexus 6, it boots to a black screen. I can hold power and see the "power off" option, but that is it.
Here is the actions I took:
Fastboot
OEM Unlock
ChainFire Auto Root Nexus 6
Boot and Verify SU Binaries
Reboot into TWRP
Wipe Cache/Davlik/System/Data
Flash Odex (also tried De-Odex) Rom
Reboot
I tried using your Radio and Bootloader files, as well as the latest ones in the Nexus 6 factor image file hosted by Google, same result.
Any thoughts on why this might happen?
I have since manually flashed system, cache, boot, and userdata from the stock image and booted fine with root (and am currently running this).
Click to expand...
Click to collapse
Did you tick the box in developer options to "unlock bootloader" before OEM unlock?
Sent from my Nexus 6 using XDA Free mobile app
RUISOU said:
Did you tick the box in developer options to "unlock bootloader" before OEM unlock?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Yes,
Just curious, wouldn't fastboot oem unlock fail if that wasn't enabled?
Domosham said:
Yes,
Just curious, wouldn't fastboot oem unlock fail if that wasn't enabled?
Click to expand...
Click to collapse
My understanding is the unlock process goes normally then hangs infinitely during the first boot.
Sent from my Nexus 6 using XDA Free mobile app

TWRP not working: D405

Dear all,
got a LG D405 with Android 5.0.2 and Version V20b here. Wanted to install LineageOS. First I enabled USB Debugging and rooted the device. Then I used ADB to flash the newest Version of TWRP (twrp-3.1.1-0-w7.img). I typed:
adb push twrp-3.1.1-0-w7.img /sdcard/twrp-w7.img
*then*
su (+granting rights on the phone)
dd if=/sdcard/twrp-w7.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Then I shut down the phone and reboot using the key combinations (vol down + power).
After rebooting into recovery mode, nothing happens. I see a blue screen for a fraction of a second, then it goes black and off. Then I can restart the phone normally. How can I get a working TWRP? Thanks for any help!!!
tracko123 said:
Dear all,
got a LG D405 with Android 5.0.2 and Version V20b here. Wanted to install LineageOS. First I enabled USB Debugging and rooted the device. Then I used ADB to flash the newest Version of TWRP (twrp-3.1.1-0-w7.img). I typed:
adb push twrp-3.1.1-0-w7.img /sdcard/twrp-w7.img
*then*
su (+granting rights on the phone)
dd if=/sdcard/twrp-w7.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Then I shut down the phone and reboot using the key combinations (vol down + power).
After rebooting into recovery mode, nothing happens. I see a blue screen for a fraction of a second, then it goes black and off. Then I can restart the phone normally. How can I get a working TWRP? Thanks for any help!!!
Click to expand...
Click to collapse
Did you unlock bootloader?
0000.0000.00 said:
Did you unlock bootloader?
Click to expand...
Click to collapse
No. Basically I follow this guide here:
lineageos.org/devices/w7/install
Now I read a lot here in the forum and think the guide there is very misleading and forgetting a lot of steps. I am very confused because the issue seems to be very complicated and there are so many different versions and solutions. Can someone please tell me which is *the* guide to follow for my phone (LG D405 with Android 5.0.2 and Version V20b)?
tracko123 said:
No. Basically I follow this guide here:
lineageos.org/devices/w7/install
Now I read a lot here in the forum and think the guide there is very misleading and forgetting a lot of steps. I am very confused because the issue seems to be very complicated and there are so many different versions and solutions. Can someone please tell me which is *the* guide to follow for my phone (LG D405 with Android 5.0.2 and Version V20b)?
Click to expand...
Click to collapse
So there is no guide for this and the lineageos one is terrible. So what you have to do basically is get root. Unlock bootloader look around on xda and you have to get patched aboot for your device and stock rom version and flash it. Then flash twrp. With twrp wipe system cache and data partitions. Then flash lineageos and if you want root flash root zip. And if you want gapps flash that too then reboot and setup lineageos.
So, since my device is already rooted... Can I now just flash with a new aboot or do I have to install another stock? As my Version is V20b, this post here says I just can use V20a.
https://forum.xda-developers.com/lg-l90/help/aboot-zip-lg-d405-v20b-t3533401
Is this correct? Or do I have to get a totally different version first? If so, which one? My IMEI tells me this:
Model:LGD405
Suffix:ADEUOP
Latest Firmware40520B_00
I really appreciate any hints. Thank you.
EDIT:
Now I used this file here (https://forum.xda-developers.com/showpost.php?p=54358527&postcount=2), Version 405_v20a with my v20b and it worked perfectly. After I followed this guide here (https://forum.xda-developers.com/lg-l90/general/guide-guide-to-unlocking-bootloader-l90-t2852917) and could install LineageOS 14! Works!!!
tracko123 said:
So, since my device is already rooted... Can I now just flash with a new aboot or do I have to install another stock? As my Version is V20b, this post here says I just can use V20a.
https://forum.xda-developers.com/lg-l90/help/aboot-zip-lg-d405-v20b-t3533401
Is this correct? Or do I have to get a totally different version first? If so, which one? My IMEI tells me this:
Model:LGD405
Suffix:ADEUOP
Latest Firmware40520B_00
I really appreciate any hints. Thank you.
EDIT:
Now I used this file here (https://forum.xda-developers.com/showpost.php?p=54358527&postcount=2), Version 405_v20a with my v20b and it worked perfectly. After I followed this guide here (https://forum.xda-developers.com/lg-l90/general/guide-guide-to-unlocking-bootloader-l90-t2852917) and could install LineageOS 14! Works!!!
Click to expand...
Click to collapse
Good you figured it out but since you didnt quote my post I didnt get notification so I did not see this.

Categories

Resources