My twrp is gone after an ota update on my sailfish. So I thought I'll tried out flashify because I don't have a pc or a laptop. For some reason I thought that flashify can install twrp back. I tried to install it using flashify but it says it ran to a problem, so my stupid brain decide to I flash gapps first using the app because I have deleted some of the gapps. I deleted google playstore with the gmscore. Then my phone stucked on a bootloop, so I did a factory reset and my phone did reboot but now I'm stuck on the android setup which cannot open without google playstore. (f'in great) I cant reboot to bootloader and I cant connect to pc with usb debugging (greatest thing that can happen) Now, does anybody know how to fix this?
Edit: you know maybe im a genius, i fix it by myself
1. Boot to bootloader (mine work again after I type adb reboot bootloader on the terminal. Volume down + power button
2. I tried to reboot to lineage recovery but apparently it seems to ignore it so I flash twrp fastboot flash (I drag my twrp file here)
3. On twrp I reboot to recovery to get to lineage is recovery
4. I tapApply update and the From adb
5. On the terminal I type adb sideload (I drag lineage system file here)
4. And that's it,
aL_09 said:
My twrp is gone after an ota update on my sailfish. So I thought I'll tried out flashify because I don't have a pc or a laptop. For some reason I thought that flashify can install twrp back. I tried to install it using flashify but it says it ran to a problem, so my stupid brain decide to I flash gapps first using the app because I have deleted some of the gapps. I deleted google playstore with the gmscore. Then my phone stucked on a bootloop, so I did a factory reset and my phone did reboot but now I'm stuck on the android setup which cannot open without google playstore. (f'in great) I cant reboot to bootloader and I cant connect to pc with usb debugging (greatest thing that can happen) Now, does anybody know how to fix this?
Click to expand...
Click to collapse
Hey there, what happens when you try to get into the bootloader?
I don't want to be rude but next time please refrain from using unconventional methods because these may not give you the results you want if you don't know how to use them correctly. Also, Gapps packages are only meant to be used on custom ROMs that don't bring any Google apps by default.
All-In-One said:
Hey there, what happens when you try to get into the bootloader?
I don't want to be rude but next time please refrain from using unconventional methods because these may not give you the results you want if you don't know how to use them correctly. Also, Gapps packages are only meant to be used on custom ROMs that don't bring any Google apps by default.
Click to expand...
Click to collapse
Hi, I'm new and I'm actually on lineage os and I flashed mindthegapps included and also I'm stupid. Bootloader did not open when I press the power button during reboot
aL_09 said:
Hi, I'm new and I'm actually on lineage os and I flashed mindthegapps included and also I'm stupid. Bootloader did not open when I press the power button during reboot
Click to expand...
Click to collapse
Hey there, to access the bootloader you have to press Power + Volume Down for a few seconds. Try that.
All-In-One said:
Hey there, to access the bootloader you have to press Power + Volume Down for a few seconds. Try that.
Click to expand...
Click to collapse
Well yeah, it seems to be ignoring it too if I do that and also there is a screen that says press power button to open up bootloader during reboot.
aL_09 said:
Well yeah, it seems to be ignoring it too if I do that and also there is a screen that says press power button to open up bootloader during reboot.
Click to expand...
Click to collapse
Is there any chance you can take a photo and show me that screen? Never heard of it before.
All-In-One said:
Is there any chance you can take a photo and show me that screen? Never heard of it before.
Click to expand...
Click to collapse
Edit: I fix it myself with adb sideload, apparently bootloader work again but still thank u
aL_09 said:
Edit: I fix it myself with adb sideload, apparently bootloader work again but still thank u
Click to expand...
Click to collapse
Hey aL, that's good to hear. As I've told you before, I think you should stick to normal flashing methods just so you can be sure of what you're doing.
Also, it would be nice if you can post a little walkthrough of what you've done to get your device working again as it can be useful if anyone else reads this thread looking for a solution. Do not forget to contact a mod so it can be closed after a solution is posted.
All-In-One said:
Hey aL, that's good to hear. As I've told you before, I think you should stick to normal flashing methods just so you can be sure of what you're doing.
Also, it would be nice if you can post a little walkthrough of what you've done to get your device working again as it can be useful if anyone else reads this thread looking for a solution. Do not forget to contact a mod so it can be closed after a solution is posted.
Click to expand...
Click to collapse
Who's the mod?
https://forum.xda-developers.com/attachment.php?attachmentid=4929067&stc=1&d=1579303524
Related
firsth of all hi to everyone, im new here , so be patient.
i was searching on the forum and try to solve my problem, but no succes.
all the methods ive tried are a no go
my problem here is that im already rooted (razorclaw tool), superuser installed aswell, so i dont know what else do i need to enter on the recovery mod (i know i have to press down power button and volume - , at the same time), no succes either, the TF just restar as always or the little android with an exclamation sign appears and i have to restart the TF again
my problem is that i cant install custom ROMS, because it always skip to home screen or to the android with the exclamation.
i cant see all those options that lot of people tallk(install from zip, backup current rom, install X rom)because i never get to that part....
so my problem again, how to install some tool that will allow me to enter in clockwork mode (??) ??, and enable those option at the intial boot (power button & vloume - at same time ) to be abble to access the install from zip, backup current rom, wipe data , etc etc
please if someone can help me with another step by step i will be really happy
I am having the same problem
Sent from my Transformer TF101 using xda premium
i think i have this problem since i got the " FIX the problem with DOWNGRADE from .21 to .19", something along those lines, with the method someone posted before (add both files to SD card but rename one of those and then apply update)
jesesystem said:
my problem here is that im already rooted (razorclaw tool), superuser installed aswell,
please if someone can help me with another step by step i will be really happy
Click to expand...
Click to collapse
but have you installed CWM recovery?
User RecoveryInstaller to install CWM.
http://forum.xda-developers.com/showthread.php?t=1346180
/agree with @baseballfanz
Check that you have CWM installed. Then you should hold volume down + power button till you see in the screen something like (push vol+ to enter recovery). It will appear on the top of the screen. You have to wait a little since it first appears the ASUS screen and if you stop pushing the buttons at that time, the TF starts normally. You have to hold them a little longer till the text appears in the screen.
AzureusPT said:
/agree with @baseballfanz
Then you should hold volume down + power button till you see in the screen something like (push vol+ to enter recovery). It will appear on the top of the screen. You have to wait a little since it first appears the ASUS screen and if you stop pushing the buttons at that time, the TF starts normally. You have to hold them a little longer till the text appears in the screen.
Click to expand...
Click to collapse
OR you can install 'transformer reboot to recovery' from market
Pepecillo said:
OR you can install 'transformer reboot to recovery' from market
Click to expand...
Click to collapse
If they don't have CWM installed, that will only reboot the TF, not get them to recovery.
AzureusPT said:
If they don't have CWM installed, that will only reboot the TF, not get them to recovery.
Click to expand...
Click to collapse
This is 100%. We've already told you this, in this thread This Thread.
You need to install a recovery image access recovery.
If you are this unsure of what you are doing i HIGHLY suggest stepping back and reading all about SU access and the rooting procedures again.
The "flash a new ROM to ________ device" steps are pretty much the same for every Android device w/o a locked bootloader.
Root
make sure SU access can be obtained
flash a custom recovery image
reboot into recovery
do a nandroid back up
wipe
flash
reboot
If you cannot get to where you want. You are doing something wrong. millions of people have followed these same step on millions of devices w/o any problems.
neidlinger said:
This is 100%. We've already told you this, in this thread This Thread.
You need to install a recovery image access recovery.
If you are this unsure of what you are doing i HIGHLY suggest stepping back and reading all about SU access and the rooting procedures again.
The "flash a new ROM to ________ device" steps are pretty much the same for every Android device w/o a locked bootloader.
Root
make sure SU access can be obtained
flash a custom recovery image
reboot into recovery
do a nandroid back up
wipe
flash
reboot
If you cannot get to where you want. You are doing something wrong. millions of people have followed these same step on millions of devices w/o any problems.
Click to expand...
Click to collapse
Thank you¡¡¡¡¡¡¡
Thats the step i was mising , all the instructions are for ppl that actually had cwm recovery, and i was taking advices from posts about installing custom roms and not the 1sth root
Its solved now ,thank you all for your help.
sorry, my bad for asking for help
Sent from my Transformer TF101 using xda premium
Bobsinclair25 said:
sorry, my bad for asking for help
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
In essence there is nothing wrong with asking for help. Heck even the smartest of android hackers started somewhere, asking questions the selves.
The problem lays in the fact that is is pretty common knowledge and a simple search would of gave you the answers you wanted.
Keep in mind nothing i say is meant to come across rude. Sharp maybe, rude? no. If you take what i say as rude. I'm sorry.
No problem. I have been trying very hard to learn on my own. The problem I had with this was trying to find information specific to the transformer. I have done quite a bit with my other android devices and the transformer is new to me and since I use it at work every day I am probably a bit more cautious about it. Thanks, I am working on it.
Sent from my Transformer TF101 using xda premium
so i really need help rooting my htc one vx! im following the tutorial here http://forum.xda-developers.com/show....php?t=2203225 but the thing is when i enter recovery mode i get teh red triangle. how do i fix this? please help iv tried other methods but none have worked i really want to have my phone rooted. also i think anotehr problem i am having is that i have to use another program to flash boot my android. it says its unlocked but i cant fastboot it i hold the power and vol down and it just reboots it. and iv tried the Run the command "fastboot flash recovery twrprecovery.img" without quotes and it just never goes past 0%
LordXombie said:
so i really need help rooting my htc one vx! im following the tutorial here http://forum.xda-developers.com/show....php?t=2203225 but the thing is when i enter recovery mode i get teh red triangle. how do i fix this? please help iv tried other methods but none have worked i really want to have my phone rooted. also i think anotehr problem i am having is that i have to use another program to flash boot my android. it says its unlocked but i cant fastboot it i hold the power and vol down and it just reboots it. and iv tried the Run the command "fastboot flash recovery twrprecovery.img" without quotes and it just never goes past 0%
Click to expand...
Click to collapse
I will help you fore sure, BUT pls post the downloadlink again. I cant open it
well i would if i posted a download link well if this helps i have an HTC One VX with android version 4.0.4
LordXombie said:
well i would if i posted a download link well if this helps i have an HTC One VX with android version 4.0.4
Click to expand...
Click to collapse
the link is broken, i cant open the website
And THX it helps of course
Just to be safe: is your BOOTLADER UNLOCKED already via HTCDev.com?
LS.xD said:
the link is broken, i cant open the website
And THX it ehlps of course
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2203225
LordXombie said:
http://forum.xda-developers.com/showthread.php?t=2203225
Click to expand...
Click to collapse
As i suppose BOOTLOADER is UNLOCKED according to 1. post.
HTC Sync completely UNINSTALLED?
Do you have enabled USB-Debugging?
Latest drivers --> HTC driver
And latest ADB/Fastboot --> http://d-h.st/KIP
Now you just have to be back and we'll root your device pretty quick
ok i the adb installed but when i run the driver install it doesnt run. but i think that they are up to date since i just installed the htc sync manager.
LordXombie said:
ok i the adb installed but when i run the driver install it doesnt run. but i think that they are up to date since i just installed the htc sync manager.
Click to expand...
Click to collapse
UNISTALL IT completely this is killing fastboot!!! (HTC Sync)
Now we found the error i suppose Its always recommended to disconnect phone from pc during driver installs.
well i had it unistalled but the drivers still wont install
LordXombie said:
well i had it unistalled but the drivers still wont install
Click to expand...
Click to collapse
You run windoes 7, restarted computer after uninstall? And can you enter bootloader? (Vol - and Power) after some seconds release power and keep vol- pressed, if not --> release battery for soem minututes and then try again
i have entered bootloader threw the phone for the first time ^^.
ok so im trying to do the "fastboot flash recovery twrprecovery.img" command but it wont send the file...
ok so now that i did got it to work. there is one thing that is still acting odd. its Supersu it wont update. but the otehr superuser works
just install "SuperSU" from playstore
i did that 3 times now weith the same result. well i wont update and then pone time it crashed the phoine
ok everything but the supersu is working. i have no clue why sometimes it says there is no su binary and other times it says failed to update. iv uninstalled it and re-installed it a few times. is it absolutely needed?
LordXombie said:
ok everything but the supersu is working. i have no clue why sometimes it says there is no su binary and other times it says failed to update. iv uninstalled it and re-installed it a few times. is it absolutely needed?
Click to expand...
Click to collapse
So here we go again:
Here's is the link for latest SuperSu again
-> http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
PLs falsh it again using your custom recovery
worked like a charm thanks a ton for helping me root my android ^^ you are officially the best
Seems I'm an idiot.
Recently bought a Kobo Arc 10HD, my first Android device. I rooted it according to Dazza9075's guide on here. I didn't update the recovery image, because in my ignorance I thought it'd allow me to recover to factory settings.
Apparently not.
I've just reset it, and now I've lost everything. The base OS is still working, but there is no loader, no settings widget, nothing. The battery remaining indicator and time are showing in the top right, the three Android buttons are showing at the bottom. It's powering down the screen properly. That's it. If I press the recent apps button the old wallpaper comes up. Any swiping on the recent apps and the System UI stops responding.
Edit: Might also be worth mentioning it'll only restart after the first power on after a reset - any subsequent attempts and it stays on the Kobo loading screen.
Have I just completely buggered it, or do I have some options available?
Okay, I'm able to sideload using ADB in the recovery settings - is this of any use?
Hello
Yes you can sideload recovery using ADB as given in the guide you mentioned . Ensure that the device drivers and ADB drivers are properly installed on your PC before sideload.
Hope it works
4shreyas said:
Hello
Yes you can sideload recovery using ADB as given in the guide you mentioned . Ensure that the device drivers and ADB drivers are properly installed on your PC before sideload.
Hope it works
Click to expand...
Click to collapse
Don't think that's going to help. I'm unable to access dev mode as the settings app isn't there. There's no way to go into ADB shell, I can only use the sideloader mode in the recovery settings.
Glompish said:
Don't think that's going to help. I'm unable to access dev mode as the settings app isn't there. There's no way to go into ADB shell, I can only use the sideloader mode in the recovery settings.
Click to expand...
Click to collapse
Flash stock rom back
Sent from my GT-S7582 using XDA Premium 4 mobile app
Unfortunately don't have one. I didn't install a custom ROM on it because they're unavailable on Kobos. If I get a stock upgrade.zip I think it should work, but I haven't managed to find one.
Hello
Search on the internet if someone has uploaded your stock rom . You can use ADB Fast boot to flash recovery and without stock rom , recovery alone won't help you . If you find a custom rom try that
All the best
I'll try having a further look. Thus far no luck though.
Thanks for the help.
Glompish said:
If I get a stock upgrade.zip I think it should work, but I haven't managed to find one.
Click to expand...
Click to collapse
If you go this route you'll need to sniff out the url on an update from Kobo. I know this works on the original arc but they may have smartened up and started using ssl.
I never tried flashing a custom kernel before on my phone, but I downloaded Code Blue last night latest (615 I think) and I tried flashing it this morning. I have MultiROM installed with TWRP. When I rebooted my phone, MultiROM came up and I selected my internal 4.4.4 stock ROM. It then went to a black screen and stayed there for about 5 minutes until I rebooted the phone. Now I am currently sitting at a "Google" logo and the phone is completely stuck and won't move. I'm guessing the kernel wiped MultiROM or it wasn't compatible and now it's trying to boot something that is corrupted.
What's weird is, if I go into TWRP and go to MultiROM, it tells me it isn't installed.
Does anyone know how to fix this
I tried downloading MultiROM uninstaller tool and lo and behold, my data wont mount in TWRP on my laptop or desktop to put it on there :'(
Is there anyway to install the uninstaller without it on my internal
snappycg1996 said:
I tried downloading MultiROM uninstaller tool and lo and behold, my data wont mount in TWRP on my laptop or desktop to put it on there :'(
Is there anyway to install the uninstaller without it on my internal
Click to expand...
Click to collapse
Hello,
use wugs nexus toolkit, you can flash back to stock with this tool.
There ist a point named flash stock and unroot, there you must set the point by current status, bricked/bootloop.
Freddy Krüger said:
Hello,
use wugs nexus toolkit, you can flash back to stock with this tool.
There ist a point named flash stock and unroot, there you must set the point by current status, bricked/bootloop.
Click to expand...
Click to collapse
Thank you for the reply just to ensure, this will wipe everything right is there any way to save my data
I really don't know much about multitom.. But just use adb to pull your sdcard data then factory reset.
You could return to stock but please don't use toolkit as mentioned above. I'm really not sure why people insist on this being then answer.
2 links in my signature. 1 about why toolkits are not the answer. Another about guides and info threads. You can read about fastboot and adb. There and never think about pesky toolkits again.
Also no such thing as partially bricked. Its either bricked or not. This is not. Just a boot loop
do not use root toolkits. the reason you listed your phone as "partially bricked" is because you dont know better. a phone is either completely bricked or not. you do not learn how to do things using root toolkits. root tooolkits are not meant for noobs. what you want to do is flash the factory img via fastboot while you are in the bootloader.
Your phone isn't bricked at all, it can be easily fixed.
1) Downlaod 4.4.4 stock rom for nexus 5 on the offical site : https://developers.google.com/android/nexus/images
2) Unzip the folder and click the "flash all.bat" file inside the folder. This will install 4.4.4 on your nexus 5. (connect nexus 5 to your computer first)
3) You're done. (During the installation process from flash.all, all your data will be deleted).
So next time you get bricked, you can rely on that flashall bat but in the future, read the general info in the forums about how to use adb and fastboot without flashall.bat so you can unbrick your phone in minutes.
Link for all the general info you need to know : http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
EDIT: Nvm, others have already explained above
rootSU said:
I really don't know much about multitom.. But just use adb to pull your sdcard data then factory reset.
You could return to stock but please don't use toolkit as mentioned above. I'm really not sure why people insist on this being then answer.
2 links in my signature. 1 about why toolkits are not the answer. Another about guides and info threads. You can read about fastboot and adb. There and never think about pesky toolkits again.
Also no such thing as partially bricked. Its either bricked or not. This is not. Just a boot loop
Click to expand...
Click to collapse
How could I go about pulling the sdcard and resetting that would save data
I have no idea at all how to do those things, kind of in the dark without being able to mount anything. I just don't want to lose anything if it's possible, and if I wipe the phone, I have a feeling MultiROM will still be there. I'll check out the links
snappycg1996 said:
How could I go about pulling the sdcard and resetting that would save data
I have no idea at all how to do those things, kind of in the dark without being able to mount anything. I just don't want to lose anything if it's possible, and if I wipe the phone, I have a feeling MultiROM will still be there. I'll check out the links
Click to expand...
Click to collapse
Like I said, there's a guides and info link in my signature. If you click that and then read "adb and fastboot. What is it?" - all your answers are there..
rootSU said:
Like I said, there's a guides and info link in my signature. If you click that and then read "adb and fastboot. What is it?" - all your answers are there..
Click to expand...
Click to collapse
Thank you so much for your help, I really do appreciate it. however I installed abd and I went into TWRP and went to abd sideload and I typed in CMD "abd devices" and it don't show my phone, it shows "adb devices attached" but no serial numbers. Is there something I must do before it will show up
btw, I always typed abd wrong lol and it never showed up. I felt dumb when I realized it's actually adb.
EDIT fastboot works just fine showing serial numbers adb still nothing..
snappycg1996 said:
Thank you so much for your help, I really do appreciate it. however I installed abd and I went into TWRP and went to abd sideload and I typed in CMD "abd devices" and it don't show my phone, it shows "adb devices attached" but no serial numbers. Is there something I must do before it will show up
btw, I always typed abd wrong lol and it never showed up. I felt dumb when I realized it's actually adb.
Click to expand...
Click to collapse
No idea what happens when you enter adb sideload. That's not what you should be doing. Just test adb from the main menu of TWRP. If no devices, driver, USB issue.
rootSU said:
No idea what happens when you enter adb sideload. That's not what you should be doing. Just test adb from the main menu of TWRP. If no devices, driver, USB issue.
Click to expand...
Click to collapse
When I enter recovery on my laptop and desktop, it makes the "usb failed sound" the du du dun. Not sure if that is my problem. Is there anyway to fix the issue I think it isn't possible with fastboot to put stuff on any storage.
snappycg1996 said:
When I enter recovery on my laptop and desktop, it makes the "usb failed sound" the du du dun. Not sure if that is my problem. Is there anyway to fix the issue I think it isn't possible with fastboot to put stuff on any storage.
Click to expand...
Click to collapse
Fix the drivers
rootSU said:
Fix the drivers
Click to expand...
Click to collapse
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
snappycg1996 said:
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
Click to expand...
Click to collapse
Its all in my "adb and fastboot" thread. I thought you were reading it?
snappycg1996 said:
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
Click to expand...
Click to collapse
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
jmtjr278 said:
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
The universal naked driver is already linked in my thread that he was supposed to be reading
jmtjr278 said:
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
LOL. They're directly linked in rootSU's thread.
EDIT: rootSU beats me to it again. One day my friend, one day, I'll learn to type faster.
rootSU said:
Its all in my "adb and fastboot" thread. I thought you were reading it?
Click to expand...
Click to collapse
Maybe my phone is just done for. I download that driver and another one from a different thread and everytime I try to update it is says "nothing is found for your Nexus 5". If I'm in the bootloader it shows "Android Composite Device" with no yellow exclamation mark, however when I try to update there is just says everything is up to date. So I know the drivers work, but what I don't get is why it won't update.
theesotericone said:
LOL. They're directly linked in rootSU's thread.
EDIT: rootSU beats me to it again. One day my friend, one day, I'll learn to type faster.
Click to expand...
Click to collapse
Maybe one day you'll have as little to do on a Sunday as me and you'll beat me tonight
Marshmallow OTA for canadian xt1563 : https://mega.nz/#!1pxWiSIS!u279kerhsu1HspzFZ4-wrzYfWgtSUqb3o8K8ffLw4lM
For the procedure, look down. Someone posted it on 1st page.
If you altered system ( ex:root) you'll need to go back to stock:
http://forum.xda-developers.com/showpost.php?p=62708260&postcount=5
Root (optional)
TWRP recovery (after applying the OTA) : http://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656
The correct SuperSU: http://forum.xda-developers.com/showpost.php?p=64161125
The X Play is actually XT1563. This firmware is for the Moto G.
Update: the above statement is wrong. I can confirm this update is running perfectly on my Koodo X Play!
bngrybt said:
The X Play is actually XT1563. This firmware is for the Moto G.
Click to expand...
Click to collapse
Yeah, but the file listed on mega has lux_retca in its name. Moto X Play is codenamed as Lux, so maybe it is in fact the right file for XT1563? Maybe, it was just an error from poster MerlinMerlinMerlin?
Hmm... I have a Koodo X Play and just checked for the OTA and it wasn't available for me yet, but that has me wondering now. I don't wanna risk it until I'm sure though. Hopefully this means the OTA is out soon though.
Oops! I messed up the title.
Corrected the incorrect xt1053 by the correct xt1563
Just finished installing it through ADB sideload (I'm a Canadian Koodo user), I reinstalled the stock firmware before so that I could start on a fresh image. I had trouble getting into stock recovery at first. I was seeing a no command message when trying to enter it but, then I found the solution:
To get passed that point, you have to use the hold power + vol up button solution but, it's tricky, I had to try 3-4 times before getting it right. This part is kind of messed up, if you hold power button for too long, the phone interpret it as a reboot command. What worked best for me was holding vol up button alone for 5-6 seconds and then, I'd tap and release power button while still holding volume up button.
Click to expand...
Click to collapse
It worked perfectly...
How do you install it? Simply install it in recovery or do we need to install it by adb?
baskwo said:
How do you install it? Simply install it in recovery or do we need to install it by adb?
Click to expand...
Click to collapse
First, you need to have stock recovery, if you installed TWRP custom recovery, you will need to reinstall stock recovery. Entering stock recovery can be tricky, at first you may get an Android robot laying down with a "No command" message.
To get passed that point, you have to use the hold power + volume up button solution but, it's tricky, I had to try 3-4 times before getting it right. This part is kind of messed up, if you hold power button for too long, the phone interpret it as a reboot command. What worked best for me was holding vol up button alone for 5-6 seconds and then, I'd tap and release power button while still holding volume up button.
Edit: a user reported that this method work better (your mileage may vary)
Press and hold the Power Button for 2-5 seconds, while holding it, press and release the Volume Up button. You should now be seeing all the Recovery options.
Click to expand...
Click to collapse
Once you are booted in stock recovery mode, you can simply follow those steps:
Setup ADB and Fastboot on your PC.
Download the OTA update .zip file on your PC and rename it to ota.zip.
Enable USB debugging:
Go to your phone’s settings » About phone » and tap “Build number” Seven times. This will enable Developer options on your phone.
Now go to Settings » Developer options » and tick the USB debugging check box.
Connect your phone to PC.
Now open the folder where you downloaded the OTA update .zip file and then open a command window inside the folder. To do that, do a “Shift + Right click” on any empty white space inside the folder and select “Open command window here” from the context menu.
Now issue the following window to command window to reboot your device into recovery mode:
adb reboot recovery
└ Check your phone’s screen, if it asks for “Allow USB debugging”, accept it by selecting OK/Yes.
Once in recovery mode, use Volume buttons to navigate up and down between options and Power button to select an option.
Select the “Apply update from ADB” option.
Now issue the following command to finally begin installing the OTA:
adb sideload ota.zip
└ This will begin the OTA installation.
Once the OTA zip is installed, select reboot from the main menu of recovery.
Click to expand...
Click to collapse
Please take note that once Marshmallow is installed, nothing is stopping you from reinstalling TWRP and then, it will work as if nothing ever happened. If you need SuperSU, make sure to use SuperSU 2.62, earlier version may cause problem with Marshmallow. Also, if TWRP , ask if you want to install Root, click "Do not install" as it would install an older version of SuperSU. That's why you need to flash SuperSU 2.62 zipfile.
And if I want to keep TWRP?
Any chance someone could post a TWRP backup after installing the OTA?
baskwo said:
And if I want to keep TWRP?
Click to expand...
Click to collapse
You'll just have to reinstall TWRP after. No big deal, you can easily reinstall it afterward. That's what I did and TWRP is working perfectly as if nothing ever happened.
Nico3d3 said:
You'll just have to reinstall TWRP after. No big deal, you can easily reinstall it afterward.
Click to expand...
Click to collapse
Alright, thank you boy! <3 Where can I find the stock recovery?
baskwo said:
Alright, thank you boy! <3 Where can I find the stock recovery?
Click to expand...
Click to collapse
Just grab it from the original firmware zip file... : http://forum.xda-developers.com/moto-x-play/general/official-stock-firmwares-added-xt1562-t3195364
Nico3d3 said:
Just grab it from the original firmware zip file... : http://forum.xda-developers.com/moto-x-play/general/official-stock-firmwares-added-xt1562-t3195364
Click to expand...
Click to collapse
Does the XT1563_LUX_RETLA_DS_5.1.1_LPD23.118-32_cid12_subsidy-DEFAULT_CFC_v2.xml.zip file is ok if I'm from Koodo? Sorry I'm new to the Moto X Play I worked on a S3 before..
baskwo said:
Does the XT1563_LUX_RETLA_DS_5.1.1_LPD23.118-32_cid12_subsidy-DEFAULT_CFC_v2.xml.zip file is ok if I'm from Koodo? Sorry I'm new to the Moto X Play I worked on a S3 before..
Click to expand...
Click to collapse
Yes, it would work but, knowing how slow download from filefactory is, it would be probably take a looonnnggg time to download. That's why I uploaded the correct recovery.img file on my Google Drive, for the benefit of everyone: https://drive.google.com/file/d/0B-OWWP0oC4yLRDhsSDV0Mng3cVk/view?usp=sharing
Nico3d3 said:
Yes, it would work but, knowing how slow download from filefactory it would be probably take a looonnnggg time to download. That's why I uploaded the correct recovery.img file on my Google Drive, for the benefit of everyone: https://drive.google.com/file/d/0B-OWWP0oC4yLRDhsSDV0Mng3cVk/view?usp=sharing
Click to expand...
Click to collapse
Do you have a link the 5.1.1 fw?
I'd like to do a total fresh install then kick off the ota.
Anyone tested this on the xt1562?
Sent from my XT1562 using XDA Free mobile app
I misread last post, sorry about it, that's why I'm editing my post
Nico3d3 said:
Pleaaassseee, at least take the time to read a bit, no more than one page ago, you will have all informations regarding installation and how it worked.
Click to expand...
Click to collapse
There is nothing on that page about the xt1562, Just asking if anyone tested it on that device
Sent from my XT1562 using XDA Free mobile app
Nico3d3 said:
Pleaaassseee, at least take the time to read a bit, no more than one page ago, all informations regarding installation and how it worked are there.
Click to expand...
Click to collapse
Lol, you should read first before telling someone else
Sent from my Nexus 5 using Tapatalk