Database Users

Urgent Help Needed!

My phone MOTO X PLAY got bricked after trying to root using the method specified in this site
http://theunlockr.com/2015/09/21/root-motorola-moto-x-play/
everything was success until the 4th step, successfully unlocked bootloader, installed recovery etc
after flashing superSu and rebooted phone stucked on boot screen
Then i wiped Dalvic Cache , System, Data partitions etc. ( I was dont know what to do )
Now the recovery says No OS installed
What should i do now?
I tried installing the rom on the below post,
http://forum.xda-developers.com/moto-x-play/general/moto-x-play-marshmallow-6-0-ota-t3267061
But its is also failed and got error with code 7 and it says this device has Motorola/omni_luz/lux:5.1.1/LYZ28J/sultan02101841 : userdebug/test-keys
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm confused to what to do now and i'm not expert in this. Please some one help me on this isssue

fr3akb0y said:
My phone MOTO X PLAY got bricked after trying to root using the method specified in this site
http://theunlockr.com/2015/09/21/root-motorola-moto-x-play/
everything was success until the 4th step, successfully unlocked bootloader, installed recovery etc
after flashing superSu and rebooted phone stucked on boot screen
Then i wiped Dalvic Cache , System, Data partitions etc. ( I was dont know what to do )
Now the recovery says No OS installed
What should i do now?
I tried installing the rom on the below post,
http://forum.xda-developers.com/moto-x-play/general/moto-x-play-marshmallow-6-0-ota-t3267061
But its is also failed and got error with code 7 and it says this device has Motorola/omni_luz/lux:5.1.1/LYZ28J/sultan02101841 : userdebug/test-keys
I'm confused to what to do now and i'm not expert in this. Please some one help me on this isssue
Click to expand...
Click to collapse
WHAT ARE THE ODDS, same thing happened to me on that site, and I tired on that site's method too... It bricked me phone too. I couldn't think of anything else to do so i tried to played dumb with the clerk of the place I bought my Moto x Play. they gave me back my money and I bought a new one, after that I used the method on XDA site, and nowhere else.

HerySean said:
WHAT ARE THE ODDS, same thing happened to me on that site, and I tired on that site's method too... It bricked me phone too. I couldn't think of anything else to do so i tried to played dumb with the clerk of the place I bought my Moto x Play. they gave me back my money and I bought a new one, after that I used the method on XDA site, and nowhere else.
Click to expand...
Click to collapse
Is there any way to get a ROM for X Play?

since you already have twrp installed, try flashing stock rom in this page - http://forum.xda-developers.com/moto-x-play/general/rom-xt1563-brasil-stock-6-0-twrp-t3272979

pijes said:
since you already have twrp installed, try flashing stock rom in this page - http://forum.xda-developers.com/moto-x-play/general/rom-xt1563-brasil-stock-6-0-twrp-t3272979
Click to expand...
Click to collapse
Thanks for the reply,
Post says to copy the zip file to twrp Backup folder.
But how can i copy without booting the device ?

fr3akb0y said:
Thanks for the reply,
Post says to copy the zip file to twrp Backup folder.
But how can i copy without booting the device ?
Click to expand...
Click to collapse
Micro SD card

fr3akb0y said:
Thanks for the reply,
Post says to copy the zip file to twrp Backup folder.
But how can i copy without booting the device ?
Click to expand...
Click to collapse
You could reboot the phone into recovery and connect the phone to the computer. You could then mount the USB storage onto the computer and simply copy paste the zip into the storage. Although I'm not up to date with the features of the current TWRP, but the mount USB storage option was present in a previous version of it. I dunno whether it's still there or not, but still worth a try.

Thanks a lot! it worked

Can't Re-Unlock the Bootloader

I read through the similar thread from yesterday, but this is a different issue...
I had unlocked, installed TWRP, and had been running a custom ROM (BadBoyz 1.2). This morning I re-locked so I could flash the updated firmware (v1.80) and now I am unable to re-unlock.
When I issue the command fastboot flash unlocktoken Unlock_code.bin, it works without errors, and the phone goes to the "Are you sure you want to unlock your bootloader?" screen.
However, at that screen, the volume buttons do nothing. I can't select yes OR no, it just sits there. Eventually it times out and just shows the battery charging on a black screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I flashed the firmware, it removed TWRP, and with a locked bootloader, I can't re-flash it.
I was able to get a fully stock rom up and running, so I'm not in brickville anymore (had a few hours of panic earlier today), and I've been able to confirm that the OEM Unlock option is checked. I've even unchecked and re-checked to be sure. Everything works except the ability to confirm my choice and move on. I'm kind of afraid that it's a glitch in the new firmware, at this point...
Anyone got any ideas?
Thanks!!

deleted

So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app

have you tried running RUU.exe? i took that route and was able to unlock my bootloader again, flash twrp and upgrade to bb 2.0 with no problems

I had the same problem and had to flash a stock rom back on the phone before the unlocker would work.

I figured it out! I can't explain WHY it worked, but it worked...
I had re-flashed several times using the official RUU, and the results never changed...
Then yesterday I went through a mental checklist of what was different when I unlocked the first time... and the only thing, was that I hadn't put my SD Card in the phone yet when I unlocked the first time. So I went through the motions again to verify that it still didn't work, and it didn't. Then I ejected the SD Card and tried it - and BOOM, I was able to unlock!
The only thing I can think of is that the SD Card did have the Firmware .zip on it, which the phone auto-detected and asked if I wanted to install... even though I said no. As soon as I tried it without the card, it worked like it always had, I'm back to unlocked, and back to the custom ROM I had been enjoying so much...
Thanks for the tips, everyone, and I hope this thread helps someone else who finds themselves in the same boat!

scottspa74 said:
So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, that is EXACTLY where I was at. However, finally found the way out of the mess.. (see above post)

Little Help needed to get my 6p alive again

please help me.
I have completely wiped my device. nothing is there in internal storage. Just the TWRP folder.
it has unlocked bootloader and twrp installed
but it is the unrooted device.
so please tell me what is best for me?
shall I root it or can I directly go to stock Oero?
I have already downloaded stock file '8.1.0 (OPM6.171019.030.E1, Jul 2018)- angler-opm6.171019.030.e1-factory-1abcb2f1.zip'
I am confused, how should I proceed?
please explain me stepwise, so I can save my phone.

smartpreet said:
please help me.
I have completely wiped my device. nothing is there in internal storage. Just the TWRP folder.
it has unlocked bootloader and twrp installed
but it is the unrooted device.
so please tell me what is best for me?
shall I root it or can I directly go to stock Oero?
I have already downloaded stock file '8.1.0 (OPM6.171019.030.E1, Jul 2018)- angler-opm6.171019.030.e1-factory-1abcb2f1.zip'
I am confused, how should I proceed?
please explain me stepwise, so I can save my phone.
Click to expand...
Click to collapse
You will be fine I wipe my internal from time to time. Just make sure you update your bootloader and vendor. If you use the flash all I'm pretty sure it's done for you but if using fastboot method follow the steps in the hiesenberg guide. Just so you know once on the latest Oreo builds from what I've read can no longer downgrade. I haven't verified or read up on it myself but maybe look into if you think you might want to go back to nougat .

Exodusche said:
You will be fine I wipe my internal from time to time. Just make sure you update your bootloader and vendor. If you use the flash all I'm pretty sure it's done for you but if using fastboot method follow the steps in the hiesenberg guide. Just so you know once on the latest Oreo builds from what I've read can no longer downgrade. I haven't verified or read up on it myself but maybe look into if you think you might want to go back to nougat .
Click to expand...
Click to collapse
i have tried that earlier, but still i got the red triangle.
since i failed to go to stock today i installed latest twrp-3.2.2-0-angler using latest SDK tool.
then i flashed Magisk-v16.0 and then ResurrectionRemix-M-v5.7.4-20161008-angler and it immediately went to google logo and stuck there.

just use this to get back to stock https://developers.google.com/android/images
all you do is boot in to fast boot plug into pc and run flash all
there are ways to save data but you already wiped so no need
if your still confused just look up a guide of how to flash factory images and install the usb drivers

billycar11 said:
just use this to get back to stock https://developers.google.com/android/images
all you do is boot in to fast boot plug into pc and run flash all
there are ways to save data but you already wiped so no need
if your still confused just look up a guide of how to flash factory images and install the usb drivers
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
these are my files.
as you said i I had connected the phone and double-click the flashall
the process started and finish but still i am on google logo.it keeps booting to logo. nothing else is happening

smartpreet said:
these are my files.
as you said i I had connected the phone and double-click the flashall
the process started and finish but still i am on google logo.it keeps booting to logo. nothing else is happening
Click to expand...
Click to collapse
What did the command line windows say when it was flashing

billycar11 said:
What did the command line windows say when it was flashing
Click to expand...
Click to collapse

smartpreet said:
Click to expand...
Click to collapse
It looks good but didn't seem to flash radio and bootloader maybe just not in screen shot should boot but if it still won't boot in to the stock recovery and factory reset might help

You could have the bad big cores try flashing one of the 4 core fixes. Also I wait to flash magisk until after first boot. It can hang you on the Google screen .

Boost E4 1766 Only Boots to TWRP

-Screwed up somewhere as my goal was to install LineageOS and try to use it on an At&t mvno.
-Package was unopened for months, so it still had the older firmware.
-Everything seemed okay after I unlocked the bootloader.
-Then I installed TWRP.
-Did a backup of everything using TWRP before I was going to try and root the device.
-I knew something was wrong when no verity opt encrypt and Magisk gave some error message and failed.
-Now whenever I boot the device, I get a N/A in the top left corner and then goes into TWRP.
-Restoring the backup using TWRP did nothing.
-I thought this would be the solution (dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M), but I get the bad key first and then N/A before going back to TWRP.
https://forum.xda-developers.com/moto-e4/help/moto-e4-metro-variant-rebooting-to-twrp-t3825841
What should I do now?
Any help would be appreciated. Even links to other posts that dealt with this issue is fine. Be aware that my skill level is only a little better than following Youtube videos.
Thank you.

N/A is normal. It will be there forever after you unlock bootloader. Did you format data in TWRP and type yes to format?

Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.

ah-le-le said:
Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.
Click to expand...
Click to collapse
once you flash TWRP you have to flash a no verity zip and probably magisk and definitely format data to remove encryption for your phone to boot.

Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ah-le-le said:
Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
Click to expand...
Click to collapse
I can't read that, LoL. Maybe... Failed toount data? That's because you're still encrypted.
Put the zips on external storage. Format data, type yes.
Now reboot recovery (not system) then flash the zips.
And you can take screenshots in TWRP.

Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.

One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.

ah-le-le said:
Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.
Click to expand...
Click to collapse
ah-le-le said:
One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.
Click to expand...
Click to collapse
Use caution going with a custom ROM on this device, especially with a mvno. You may score far more hurt than benefit. Also consider what you are trying to accomplished going with custom ROMs given the clean stability of Moto stock ROMs. Toss in Xposed framework and a few modules like Gravitybox for full control/customization.
OTA updates can not be processed with a custom recovery (one of several prerequisites that your device no longer meets). You may get notified but the update won't install; you'll be dumped into TWRP. You can easily disable the update engine and corresponding notifications on a rooted device.

Question Help……Is there still warranty for brick the phone

This machine got bricked by me… Stuck at fast boot not turning on

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Purchase, Root, Use, Brick, Contact For Support, Just in one day……

how did you brick it?

Just wait for the factory or full OTA image to unbrick

Qiyue_ said:
Purchase, Root, Use, Brick, Contact For Support, Just in one day……
Click to expand...
Click to collapse
I warn you to wait slowly with your root without test another things.
You are not brick, you must only reinstall rom, you can always access fastboot/Bootloader
Have you tried to access to Recovery ?

Me also bricked my nothing phone 1 but it's bootloader is locked
I have only access to fastboot
When i try to boot in recovery or system it's boot into fastboot
I was trying to install dynamic system update from developer option. While phone was installing dsu phone has turned off for rebooting and never turned on again.
How can i get full rom for nothing os and flash tool

Pho3nX said:
I warn you to wait slowly with your root without test another things.
You are not brick, you must only reinstall rom, you can always access fastboot/Bootloader
Have you tried to access to Recovery ?
Click to expand...
Click to collapse
I tried to use fastbootd for accessing system_b but after once I tried I can’t open this mode again, same as recovery.

Qiyue_ said:
I tried to use fastbootd for accessing system_b but after once I tried I can’t open this mode again, same as recovery.
Click to expand...
Click to collapse
And right now it’s just bootloader, the warn of the bootloader unlock sigh didn’t even come up

Displax said:
Just wait for the factory or full OTA image to unbrick
Click to expand...
Click to collapse
You also need the unbricking tool like MsmDownloadTool to flash full rom right? Having the rom file isn't enough.

Displax said:
Just wait for the factory or full OTA image to unbrick
Click to expand...
Click to collapse
Pheggas said:
You also need the unbricking tool like MsmDownloadTool to flash full rom right? Having the rom file isn't enough.
Click to expand...
Click to collapse
You will find the latest Full Nothing OS 1.1.0 HERE
@Displax , I don't know if MsmDownloadTools is operationnal for the Phone(1) because it mainly concerns all devices produced by the BBK Electronics consortium.
I don't know if someone want to try, you will find here the link to MsmDownloadTools