From what I understand, the REVVLRY is just the Moto G7 Play rebranded. From that, I assumed that the method of using Magisk to root Moto devices would also work for the device (Unlocking bootloader, patching a file with Magisk using the stock firmware [learned that the hard way, ty sd_shadow], flashing that file with ADB, rebooting).
However, when finishing this and rebooting the phone, instead of "bad key" or "N/A" showing up, a serial code-like text is in its place. I hadn't taken the time to figure out what it actually is or means, but all I know is that it gets stuck on that screen, forcing me to use LMSA again which successfully returns the phone back to normal.
I am not a professional in development or code, but one thing I can point out is that the final number of the build number is different from my current one (file QPYS30.85-18-9-8 vs device QPYS30.85-18-9-10). Maybe this could be the issue? Although I have seen threads that managed to root even with a different version. Is there any potential reason that this happens? And what guide should I follow to root the REVVLRY if it is possible?
A question I probably should have asked from the start; about how long should I wait for the phone to reboot after Magisk is flashed? I may have just been impatient with the phone and not given it enough time to finish whatever it needed to.
Try this method instead:
Reflash stock and boot normally > (unlock bootloader if you haven't already) > reboot into bootloader > fastboot boot twrp > adb sideload magisk zip > reboot into system > install magisk apk
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
This is what I get when doing sideload with the magisk.zip. Is this normal, or is this already a sign of doing something wrong?
Thfaro said:
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
This is what I get when doing sideload with the magisk.zip. Is this normal, or is this already a sign of doing something wrong?
Click to expand...
Click to collapse
Looks like the ADB connection isn't getting established. In TWRP, make sure to go into the Options (I think) mention and select the "ADB Sideload" option.
It seems to have worked, neither TWRP nor the Command returned any bad results. From here, do I continue as normal from the Magisk method?
Thfaro said:
It seems to have worked, neither TWRP nor the Command returned any bad results. From here, do I continue as normal from the Magisk method?
Click to expand...
Click to collapse
Yeah, after you flash the Magisk.zip, reboot back into the OS, rename Magisk.zip into Magisk.apk, and then install it like a normal app. Open it up and it'll detect root.
Flashing the zip went well, so I opened the app after renaming it and the "Installed" says N/A. Do I continue from there? I am sorry about all the questions by the way, it's my first go at rooting, and I haven't proven successful so far lol
Just to rule out the possibility of using Magisk to then patch the file like normal, sure enough, I get the same text. This time I managed to get a picture of it, though, not very clear.
The second picture is what happens after I wait for a bit. I'm going to put the phone back to the state after the zip flash with TWRP though.
Edit: Redoing all the step and not continuing forward, the string of text also seems to happen anyways, but I do manage to get past it and start the phone like normal. Magisk still says N/A however.
Related
I have a nexus 7 2013 LTE build KOT49H
I initially managed to unlock and root using nrt 1.8...everything was perfect...there was some confusion getting adb setup though..
(for WugFresh...your instructions are fantastic but you should add a line to "check your device for the message to accept a connection for adb and select ok"...I found myself waiting and waiting, staring at my computer screen thinking that the nrt was hanging when all I needed to do was press "ok" on my device.)
Like I said...everything was perfect but I had to go one step further...
I then installed cyanogenmod 10.2 using twrp...tihs also went fine but I hated it and wanted to get back to my original google os. I had a really hard time getting adb set up once cyanogen was installed but once I finally did I was able to get back to stock again using nrt 1.8.
So now I'm back to stock image KOT49H. Everything runs fine and I see the unlocked logo when I boot so I assume I'm still unlocked.
Here's the problem..
When I try to root now, (I always run the NRT driver test until I get "success" message first) my device hangs on the "Booting modified boot.img to enable..." message.
And I mean hangs...can't even power it down without popping the cover and disconnecting the battery! Thankfully this gets me back to a running device but I still want to root this thing.
Any idea what might be wrong or where I should go to from here?
Thanks for any help you can suggest!
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
mdamaged said:
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Click to expand...
Click to collapse
Thanks for the response...
All these check...I do have to switch to PTP to get adb functional and I do get success on the full driver test before I try rooting...device still hangs at "Booting modified boot.img to enable running privileged commands" message and then wont power down without disconnecting battery...
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
datallboy said:
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestions...
I lost twrp when I went back to stock build.
Sorry...I'm real green at all of this...
You think I should:
power up to fastboot mode...select boot loader mode...then select recovery to see if it boots?
You need to be real clear for me, I'm a total newb
I would need a link to thorough instructions for wiping to factory reset and flashing the supersu.zip...I do have adt installed and have my path modified so that I can run instructions like "adb devices" in a command window but I'm unclear as to where to place files so they will be seen if I try to flash them via adt. (like I say...this is all new to me and I'm not even sure if that last sentence makes sense)
mdamaged said:
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
Click to expand...
Click to collapse
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
SMELZBAD said:
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
Click to expand...
Click to collapse
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest zip, save it to your device (in the root of the sdcard).
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run busybox and see what happens.
Click to expand...
Click to collapse
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
SMELZBAD said:
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
Click to expand...
Click to collapse
Wug's toolkit is doing exactly that, the main difference in doing it manually is we get to see where the problem is.
If this fails then I would probably say you should backup anything on your device you don't want wiped, and try one click restore and try rooting again.
Good luck.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
Click to expand...
Click to collapse
Followed your instructions...everything went as it should until I got to:
fastboot boot openrecovery-twrp-2.6.3.1-deb.img
instead of rebooting the device I only got waiting for device message in command window...
is device supposed to be put in bootloader mode before entering this instruction maybe???
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
SMELZBAD said:
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
Click to expand...
Click to collapse
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
mdamaged said:
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
Click to expand...
Click to collapse
Ya...something likely still abit wacky...I'll be sure to post if anything weird starts happening but for now all is good...I'm definitely rooted though...I was just able to mount a flash drive via Stick Mount and run a video off of it!
Hi all,
I have seen mentions in several places (including here http://9to5google.com/2014/12/18/how-to-update-android-wear-manually-ota-downloads/ and there http://forum.xda-developers.com/showpost.php?p=61430452&postcount=6 ) that it is possible to sideload an OTA to the SmartWatch 3 without using fastboot or rooting, just rebooting in recovery and running adb sideload.
However, in my case, although the watch properly appears in "adb devices" when it's powered on, when I go into recovery, it does not appear anymore... And thus I can't run "adb sideload" as adb, obviously, says "no devices found"
Any idea? Am I missing some trick? I have tried this both on Windows 8 and on Ubuntu, both behave in the exact same way.
I have also tried going into recovery using two different means: "adb reboot recovery" and using the menu that has fastboot/recovery options, nothing solves the issue.
Thanks!
PS: The reason why I am trying to sideload the OTA is to go 4.4 -> 5.0.1 and not 4.4 -> 5.1.1 because of all the 5.1.1 issues + I hate 5.1.1 UI
Did you click the adb sideload button in recovery? This enables adb.
If that does not work, try using fastboot to temporarily boot twrp from fastboot, but you will need to install fastboot drivers on your p.c. and find a 4.4 version of twrp.
The command is
Code:
fastboot boot twrp.img
From there you should be able to use adb.
Hi!
Do you mean selecting the "sideload" option in recovery? Yes I have selected this (by swiping down and then right to validate the choice) and my device still does not show up in adb. Have you been able to do this on the SmartWatch3? I feel like most people have experience with the LG G Watch...
In order to flash TWRP. I need to unlock the bootloader, don't I? If I can avoid voiding my warranty, that'd be great...
Thanks!
My first thought was the sideload option. I did not do it, but am on an SW3. I went right to option 2.
This does not unlock your boot loader, or void your warranty. What it does is hotboot another Rom (in this case recovery) without writing it to disk. I did do this, and it worked well.
This is the thread I followed. Skip the fast foot unlock step. That. An void your warranty.
http://forum.xda-developers.com/showthread.php?t=3107501
Oh! This is pretty awesome. Trying it, thanks a lot!
YESS! lekofraggle, I owe you a good one
So, for future readers, here is the procedure I went through. I have tried many different ways, this is the only which yielded results, so I'll only explain this one:
1) First, make sure that when your watch is connected to your phone, it displays the notification prompting you to upgrade your andoird wear version (I am not sure it will work if you don't have this notificaiton) (note that this notification only appears when the watch is connected to the phone in bluetooth, for me)
2) Follow http://forum.xda-developers.com/showthread.php?t=3107501 instructions to hot boot TWRP 5.0.2 (yes, even though you're in 4.4, does not matter (too much)). (command: fastboot boot twrp.img)
3) Root your watch by downloading the rooting zip from http://forum.xda-developers.com/attachment.php?attachmentid=3342605&d=1433157678 and "adb push yourzip /sdcard/root.zip"
4) In TWRP, your watch, go to "Install" and select "root.zip". You watch is now rooted.
5) Reboot your watch in normal android boot. Now push the OTA zip to it: "adb push yourota.zip /sdcard/update.zip"
6) Now is the trick: Replace the official OTA by yours: do "adb shell" and then "rm /cache/update.zip" and "cp /sdcard/update.zip /cache/update.zip".
7) Now check you still have the notification prompting for upgrade (your watch needs a bluetooth connection to phone, else it does not display it). Check the zip in /cache is still your by looking at the size, for instance: "ls -l /cache/update.zip" and compare with the size of your file.
8) If you're confident it is still your file, use the notifcation prompt on the watch and say you are ready to apply the upgrade.
9) Watch restarts and upgrade.... using your OTA file !
I tried using the custom "recovery command" that tutorials like http://www.carbontesla.com/2014/12/tutorial-update-smartwatch-3-lwx48p-android-5-0-1/ tell you to use but it would not work for me, only the notification would really trigger the upgrade...
Hope it helps!
PS: The reason for not using "adb sideload" directly from TWRP is that my OTA package (4.4 -> 5.0.1) would not be applied, it would complain that I am trying to apply it from a 5.0.2 system while it should be applied from a 4.4 system (oh, really?).
Great, I am glad it worked for you.
Two points for others travelling this path.
1)I am not sure you need to be rooted to do this, because twrp has its own permissions.
2) Did you try to use the install update.zip feature of twrp? That should have worked too.
Either way, I am glad you got there.
~Leko
Hi all,
It seems I come back a n00b every few years.
I rooted my Zenfone 2 to remove some clutter and guess what I did today? I updated. Didn't know that would brick my phone but well here I am.
I followed these steps:
http://www.asus-zenfone.com/2015/06/how-to-update-ota-without-bootloop-on-rooted-zenfone2.html
Only to find that it wouldn't boot.
Went into recovery and tried to factory reset... went on for more than 15 minutes (I didn't want to stop the process....). I then had to hard reset then boot into recovery and tried to wipe cache which yielded nothing...
BTW, I think the failed wipe and reset messed up permissions as fastboot yields an error (even though the "flash recovery" bit seems to work).
I tried installing TWRP and it only boots back into fastboot. Reinstall the recovery from the link above and I can go back into recovery but can't seem to use any of the functions.
Any ideas?
p.s. I did do a few searches. Can't find anything specific about
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
adramelch said:
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
Click to expand...
Click to collapse
Have you installed all your drivers correctly?
In TWRP, have you gone into advanced and selected ADB Sideload? I've also had issues with sideloading, I think it's a TWRP issue though.
Here's what you can try:
Boot into TWRP and make sure the phone is detected on the PC.
open up adb
type: adb devices
hit enter
your device should be listed
type: adb push -p rom.zip /sdcard0/
-for push, it's just the command to push files to your phone. Alternatively, pull is for taking files from your phone (in the event you can't boot up and need a certain file)
-for -p, it just means show progress, so in CMD you'll see a percentage sign which is always a good thing to know
-for rom.zip you type in the location of the file
-for /sdcard0/ you can leave that, as that is the send destination and should land right in your main folder.
And once the file is transferred over, install through TWRP.
Wipe Dalvik/Cache.
Reboot system.
Profit.
If all this doesn't work, try a microsd card with the file on it.
EDIT: I just realized you meant you meant stock recovery. In that case...it should still allow you to adb sideload, but I'm not sure. As long as you can still use ADB, you can follow my instructions above.
adb push yields "error: closed"
adb sideload says it needs adb 1.0.32 to do operation...
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
badaboomBURP said:
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
Click to expand...
Click to collapse
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
adramelch said:
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
Click to expand...
Click to collapse
in my experience, it automatically install the zip if i go to recovery
Update: Sideload worked and I've been back to stock since. Didn't want to flash because I was ok with stock but didn't want the clutter. Will find another stable firmware if need be.
Thanks again for the help!
I have a Motorola Z play which was running 7.1.1. It is a Verizon version, so it is said to be unrootable. But I tried it anyway.
I flashed twrp-3.2.1-addison first. After I did some thing (data wiping, etc), it does not reboot to normal os anymore. At one point, I noticed it says "no OS to boot into”. I searched online and found that the only solution is to install new rom. So I downloaded oreo zip and ran adb to sideload it to my phone. However it failed due to the following error:
Code:
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Then I tried another option which is to save the zip to my phone and install it in recovery mode ( installed twrp this way). When I opened my phone with PC, it is empty. I tried to drag the zip file to the root dir of my phone, I got the following error:
Code:
Cannot copy item
The device has either stopped responding or has been disconnected.
I think it probably had to do with the data wiping. "adb devices" still shows the device is connected with the ID though.
How do fix this?
jiddy0001 said:
I have a Motorola Z play which was running 7.1.1. It is a Verizon version, so it is said to be unrootable. But I tried it anyway.
I flashed twrp-3.2.1-addison first. After I did some thing (data wiping, etc), it does not reboot to normal os anymore. At one point, I noticed it says "no OS to boot into”. I searched online and found that the only solution is to install new rom. So I downloaded oreo zip and ran adb to sideload it to my phone. However it failed due to the following error:
Code:
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Then I tried another option which is to save the zip to my phone and install it in recovery mode ( installed twrp this way). When I opened my phone with PC, it is empty. I tried to drag the zip file to the root dir of my phone, I got the following error:
Code:
Cannot copy item
The device has either stopped responding or has been disconnected.
I think it probably had to do with the data wiping. "adb devices" still shows the device is connected with the ID though.
How do fix this?
Click to expand...
Click to collapse
Uhhh.......yeah I have the same phone as u and I'm pretty sure u just bricked your phone as the Droid version DOES NOT have a unlockable bootloader which u would need to be able to install the stock firmware/rom that came from the phone from the fact....
Sent from my XT1635-01 using Tapatalk
Yeah dude, you just bricked your phone probably. Take it to Verizon and hopefully they will help reset it to stock but since you put twrp on, they might not. Always unlock your bootloader unless following a guide that is SAFE for locked bootloader
so no way flash custom rom to verizon moto z play?
Before I begin, just know I am aware I am an idiot for this.
I decided I was going to install LineageOS onto my Pixel XL today, something I have done many times before with different phones. In my haste, I ended up on the wrong install guide (my own stupid fault for not double checking, I know) and I accidentally installed TWRP on the boot partition. When I boot my phone, it just goes right into TWRP, regardless of whether I pick Start or Recovery Mode from the bootloader. I tried sideloading Lineage from TWRP, but it got to 47% done according to adb before abruptly stopping. My phone was then stuck in a boot loop where I couldn't even get into TWRP. The furthest I could get was the bootloader. After restarting my phone a number of times, I was finally able to get back into recovery mode with TWRP. I can reboot into Bootloader or Recovery (TWRP) from TWRP. If I try to reboot into System, I get the warning about my bootloader being unlocked, the Google splash screen, and then I get booted back into TWRP. If I try booting into Slot A or Slot B I get the following:
Code:
Could not mount /data and unable to find crypto footer.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
More details:
Phone is not rooted
The original command I ran that started this whole mess was
Code:
fastboot flash boot /path/to/twrp.img
As long as I am in TWRP, I can see my phone from my computer if I run "adb devices"
My original thought was to try to flash the stock .img file (or the Lineage one if I could find it), but any time I run any fastboot commands, my terminal just says "< waiting for any device >" and hangs until I kill the process. I assume this is because my device isn't actually booted. I'm not sure if there is a way to accomplish the same thing using adb.
All adb commands seem to still work fine. I can still sideload with TWRP (sort of, see above paragraph), and I can use the push and pull commands to add and remove things from the phones memory
Have I bricked this phone or is there a way to fix this?
RyanDMC said:
Before I begin, just know I am aware I am an idiot for this.
I decided I was going to install LineageOS onto my Pixel XL today, something I have done many times before with different phones. In my haste, I ended up on the wrong install guide (my own stupid fault for not double checking, I know) and I accidentally installed TWRP on the boot partition. When I boot my phone, it just goes right into TWRP, regardless of whether I pick Start or Recovery Mode from the bootloader. I tried sideloading Lineage from TWRP, but it got to 47% done according to adb before abruptly stopping. My phone was then stuck in a boot loop where I couldn't even get into TWRP. The furthest I could get was the bootloader. After restarting my phone a number of times, I was finally able to get back into recovery mode with TWRP, which is where I am now, as I am terrified to touch anything else.
More details:
Phone is not rooted
As long as I am in TWRP, I can see my phone from my computer if I run "adb devices"
All adb commands seem to still work fine. I can still sideload with TWRP (sort of, see above paragraph), and I can use the push and pull commands to add and remove things from the phones memory
Have I bricked this phone or is there a way to fix this?
Click to expand...
Click to collapse
If you can get to fastboot mode. Use the flash-all to install the March 2019 factory image.
Ignore this, I lied. Trying the above now.
Homeboy76 said:
If you can get to fastboot mode. Use the flash-all to install the March 2019 factory image.
Click to expand...
Click to collapse
That worked. Had to fidget with it a bit because fastboot kept complaining about ANDROID_PRODUCT_OUT not being set but I got it to work.
In case anyone happens upon this in the future, if you get that error, you need to create an environment variable on your machine called ANDROID_PRODUCT_OUT and set it to the path to a very specific folder in the image .zip you download from Google. When you extract that .zip, you should get a folder, that contains another folder, that contains two image files (a bootloader one and a radio one), three "flash-all" script files, and yet another .zip file. Extract that .zip and the folder that it creates is the one you need to set the environment variable to.
RyanDMC said:
That worked. Had to fidget with it a bit because fastboot kept complaining about ANDROID_PRODUCT_OUT not being set but I got it to work.
In case anyone happens upon this in the future, if you get that error, you need to create an environment variable on your machine called ANDROID_PRODUCT_OUT and set it to the path to a very specific folder in the image .zip you download from Google. When you extract that .zip, you should get a folder, that contains another folder, that contains two image files (a bootloader one and a radio one), three "flash-all" script files, and yet another .zip file. Extract that .zip and the folder that it creates is the one you need to set the environment variable to.
Click to expand...
Click to collapse
Glad you got it fixed :good:
Another solution is use this guide and do #4 'keep data':
[Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76