Phone Bricked, planning suicide :( - X Play Q&A, Help & Troubleshooting

So I bought this moto X Play a few weeks ago and it was fine. Then I rooted it to gain access to some shady things but didn't change much in the phone, nor did I install many ROMs or however you call it. It was fine till I learned that Niantic was blocking access to pokemon go to rooted phones.
So I tried unrooting it, to root it again with the Magisk root or something. I couldn't unroot with SuperSU, even though when I rooted it, that was the only thing I used. So I followed instructions, I backed up my data, I factory reset using TWRP, then it was time to flash a factory image, so I downloaded the ADB fastboot and the stock rom, I downloaded the firmware:
"XT1563_LUX_RETLA_DS_6.0.1_MPD24.107-52.xml" (I searched through the options and found my area, Latin America, made sure it was 6.0.1 just like I used, and made sure it had the correct build number).
So I followed the instructions, did everything correctly, and when I entered the code fastboot reboot, my phone got stuck in a Warning, Bootloader Unlocked screen, followed by an "erasing" screen with the android logo moving its antennae, followed by a vibration and a restart which starts everything again. I'm heartbroken now, I don't know what to do.
PD: I think I might have downloaded the wrong firmware, (it says DS in the name, which I think is Dual Sim, and I only have 1 inside), don't know if I can keep trying.
PD2: Pls halp
PD3: Like you might have guessed, I did unlock the bootloader before rooting, but now it seems that's the problem for the unrooting.

sher_31 said:
So I bought this moto X Play a few weeks ago...
Click to expand...
Click to collapse
Maybe you didn't flash all the sparsechunks? Get single sim firmware and try again

minimale_ldz said:
Maybe you didn't flash all the sparsechunks? Get single sim firmware and try again
Click to expand...
Click to collapse
I love you :highfive:

Related

Need help flashing stock S5 G900R4

Hello there,
So, I have a Samsung Galaxy S5 G900R4 with U.S. Cellular. I've heard of rooting your phone, and I decided I'd give it a try. Now, the rooting went fine, and the phone was working like a charm, until I started to have some issues. SuperSU needed to update its binary, and I allowed it to try, but it continued to tell me that it could not update it. Hence, I let it reboot when it offered. Now, for whatever reason, the phone won't boot past the U.S. Cellular 4G logo that appears, it just sits there on that screen.
Now so far, I haven't been able to find anyone that has encountered this specific problem, as most people say their soft-bricks are bootlooping and whatnot. I'm not sure if my specific case is technically a soft brick, or something else, but I wanted to just return it to stock format. I loaded up Odin again, downloaded the 1.5g firmware file, and I got the SW REV CHECK FAIL error.
I did some research, and I searched EVERYWHERE, and the closest I could find to a solution was http://forum.xda-developers.com/showthread.php?t=2798396 <-- this thread. Which makes sense, when I read it. I'm guessing the bootloader is locked on my phone, or something. The problem is that this thread is for the Galaxy S5 G900AU, and I don't have that phone.
Maybe I'm just not searching on the web enough, or I didn't search the site well enough, but I have not been able to locate a similar set of AP, CP and CSC files for my specific model.
I would really appreciate it if someone could point me in the right direction or, if the issue I'm actually having with my phone is NOT a soft-brick and there is another solution, suggest another way for me to fix the phone.
Thank you.
First off, I'd try clearing the caches from recovery
If that fails, factory reset from recovery
If that fails, (And I'm not sure about stock firmwares with ODIN & locked bootloaders) I'd try flashing stock from ODIN also
Grab stock ROMs from here
sammobile . com / firmwares / database /SM-G900R4/
Can't link it here, as SM links are not allowed - just remove the spaces
*Detection* said:
First off, I'd try clearing the caches from recovery
If that fails, factory reset from recovery
If that fails, (And I'm not sure about stock firmwares with ODIN & locked bootloaders) I'd try flashing stock from ODIN also
Grab stock ROMs from here
sammobile . com / firmwares / database /SM-G900R4/
Can't link it here, as SM links are not allowed - just remove the spaces
Click to expand...
Click to collapse
Well last night I went ahead and used recovery to clear cache, and then I did a factory reset. I just did it again, now, but I guess I'll have to download the file from SM to try. I already have a stock ROM, but I can't remember where I downloaded it from, so it may actually be a 4.4.2 ROM or something, which would explain why it won't work. I'll wait for the 5.0 ROM to download and give it a try, should take a little more than an hour and a half, then I'll report back.
Xeretius said:
Well last night I went ahead and used recovery to clear cache, and then I did a factory reset. I just did it again, now, but I guess I'll have to download the file from SM to try. I already have a stock ROM, but I can't remember where I downloaded it from, so it may actually be a 4.4.2 ROM or something, which would explain why it won't work. I'll wait for the 5.0 ROM to download and give it a try, should take a little more than an hour and a half, then I'll report back.
Click to expand...
Click to collapse
Try this link, if it works, it won't work for long
Code:
http://am4-r1f4-stor08.uploaded.net/dl/800e713b-624b-4a91-a57c-1639c6b5071e
*Detection* said:
Try this link, if it works, it won't work for long
Click to expand...
Click to collapse
It worked, it's downloading now, just have to give it some time.
nice one
*Detection* said:
nice one
Click to expand...
Click to collapse
I really hope this works, when it finishes >.>
Any idea what's happening with the phone to cause it to stay at the U.S. Cellular screen?
I never let SuperSU reboot when I let it update the binaries
Could be a number of things, possibly just corrupted a file necessary for boot, but as SuperSU has root, it could be anything
I don't know the ins and outs of how SuperSU works, but I know a few carrier specific US S5s have a locked bootloader, Verizon, AT&T etc - not sure if rebooting to allow the binary update requires an unlocked bootloader, maybe that bricked it, half assed attempt at a root process failed maybe
*Detection* said:
I never let SuperSU reboot when I let it update the binaries
Could be a number of things, possibly just corrupted a file necessary for boot, but as SuperSU has root, it could be anything
I don't know the ins and outs of how SuperSU works, but I know a few carrier specific US S5s have a locked bootloader, Verizon, AT&T etc - not sure if rebooting to allow the binary update requires an unlocked bootloader, maybe that bricked it, half assed attempt at a root process failed maybe
Click to expand...
Click to collapse
As far as I know, though, U.S. Cellular has confirmed that this device has an unlocked bootloader. And besides that, if it were locked, wouldn't that have come up as an issue when I rooted the device? I used the CWM custom recovery tool.
On a similar note, I'm not even sure if the problem was a locked bootloader. It's just that, from what I've read with other people having the same issue, they solved it by excluding the BL file from the flash and instead only using the AP, CP and CSC files.
Xeretius said:
As far as I know, though, U.S. Cellular has confirmed that this device has an unlocked bootloader. And besides that, if it were locked, wouldn't that have come up as an issue when I rooted the device? I used the CWM custom recovery tool.
On a similar note, I'm not even sure if the problem was a locked bootloader. It's just that, from what I've read with other people having the same issue, they solved it by excluding the BL file from the flash and instead only using the AP, CP and CSC files.
Click to expand...
Click to collapse
If you can flash anything custom from ODIN, bootloader is unlocked, afaik, locked bootloaders require a right mess on to get anything flashed to them
To root with a locked bootloader, is easily possible if you're on a certain KitKat ROM, and use Towelroot - other than that, (From what I've read), you need to use specific tools, so it sounds like your bootloader is indeed unlocked - which makes this next ROM flash, much more likely to work using only ODIN
Use ODIN 3.10.6 though
My experience with the S5 is with an unlocked bootloader (G900F), so I can only quote what I know about locked from what I've read, but it sounds like that doesn't matter in your case
*Detection* said:
If you can flash anything custom from ODIN, bootloader is unlocked, afaik, locked bootloaders require a right mess on to get anything flashed to them
To root with a locked bootloader, is easily possible if you're on a certain KitKat ROM, and use Towelroot - other than that, (From what I've read), you need to use specific tools, so it sounds like your bootloader is indeed unlocked - which makes this next ROM flash, much more likely to work using only ODIN
Use ODIN 3.10.6 though
My experience with the S5 is with an unlocked bootloader (G900F), so I can only quote what I know about locked from what I've read, but it sounds like that doesn't matter in your case
Click to expand...
Click to collapse
It worked! Thank you so much for the help, I really appreciate it.
Well, my warranty is now void. Is there a safer way to root the phone, or should I just leave it be?
Xeretius said:
It worked! Thank you so much for the help, I really appreciate it.
Well, my warranty is now void. Is there a safer way to root the phone, or should I just leave it be?
Click to expand...
Click to collapse
Great
Flashing a stock ROM won't void your warranty, but if it is indeed void (KNOX 0x1), then just flash this with ODIN
http://download.chainfire.eu/404/CF-Root1/CF-Auto-Root-klteusc-klteusc-smg900r4.zip
Tripping KNOX only happens when you flash something not signed by Samsung, IE: A custom recovery, ROM or Kernel etc
I have the same issue, same phone I ended up flashing a custom ROM because I luckily flashed twrp before it bricked on the us cellular screen.. How did you fix this I just want to get back to stock remove my root completely

Moto X Style (XT1572) Rooting issues - No Wifi

Hey guys,
I've had some experience rooting other phones but never a Moto X before so I tried following this guide: https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
Then I got to the bit where it says if running 6.0 I need to follow these steps: https://forum.xda-developers.com/mo...t-moto-x-style-xt1572-br-marshmallow-t3259380
Went through that successfully and it seemed to work OK until I realised I had no wifi. It was toggled off so I tried turning it back on with no success. It just instantly toggles off as soon as I turn it on. So I just tried to revert back and try again by using the provided boot_orig.img but same thing. It removed the root but Wifi still has issues so I am thinking the img is probably wrong for my model despite it saying it is for the XT1572 model.
I searched for the wifi issue problem and found a few people having the same issues. Followed the guides about flashing twrp and loading SuperSu 2.62 which some stated fixed their issues. Unfortunately it didn't work for me. I'd still like to root but at this stage I just want to get wifi working but I think I'll need a proper boot image for my model of phone.
Anyone got any suggestions?
Thanks!
stumbows said:
Hey guys,
I've had some experience rooting other phones but never a Moto X before so I tried following this guide: https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
Then I got to the bit where it says if running 6.0 I need to follow these steps: https://forum.xda-developers.com/mo...t-moto-x-style-xt1572-br-marshmallow-t3259380
Went through that successfully and it seemed to work OK until I realised I had no wifi. It was toggled off so I tried turning it back on with no success. It just instantly toggles off as soon as I turn it on. So I just tried to revert back and try again by using the provided boot_orig.img but same thing. It removed the root but Wifi still has issues so I am thinking the img is probably wrong for my model despite it saying it is for the XT1572 model.
I searched for the wifi issue problem and found a few people having the same issues. Followed the guides about flashing twrp and loading SuperSu 2.62 which some stated fixed their issues. Unfortunately it didn't work for me. I'd still like to root but at this stage I just want to get wifi working but I think I'll need a proper boot image for my model of phone.
Anyone got any suggestions?
Thanks!
Click to expand...
Click to collapse
So basically, you followed an ANCIENT guide that had you replace your kernel with one that is too old for your modem firmware. (That's a statement, not a question)
Hopefully you did a full backup in TWRP before you rooted, because you need to restore it, and then root properly... otherwise you need to reflash the stock firmware, but if you were on the latest version there no current firmware image available, so we have a conundrum.
Can you tell us your radio baseband and kernel versions from Settings - About Phone please?
acejavelin said:
So basically, you followed an ANCIENT guide that had you replace your kernel with one that is too old for your modem firmware. (That's a statement, not a question)
Hopefully you did a full backup in TWRP before you rooted, because you need to restore it, and then root properly... otherwise you need to reflash the stock firmware, but if you were on the latest version there no current firmware image available, so we have a conundrum.
Can you tell us your radio baseband and kernel versions from Settings - About Phone please?
Click to expand...
Click to collapse
I didn't take a backup as TWRP broke during the process but the root worked. I am only on 6.0 so is that ok to resolve? I can't see the baseband details at the moment as I am boot looping due to trying to follow another guide on resolving my issues. Trying to load a stock rom on to my device through TWRP now. Will report back soon.
OK I have managed to restore the phone to stock and got wifi working again which is great. Now to attempt rooting again. What method do you recommend for this phone running 6.0?
stumbows said:
OK I have managed to restore the phone to stock and got wifi working again which is great. Now to attempt rooting again. What method do you recommend for this phone running 6.0?
Click to expand...
Click to collapse
Magisk is probably the easiest now days, and most flexible but I haven't tested it... or the method in my signature which I know works.
Get the latest version of TWRP, and backup, and get it off the device... it can be a life saver later.
acejavelin said:
Magisk is probably the easiest now days, and most flexible but I haven't tested it... or the method in my signature which I know works.
Get the latest version of TWRP, and backup, and get it off the device... it can be a life saver later.
Click to expand...
Click to collapse
OK yep installed TWRP, performed backup, flashed supersu, booted and confirmed root, updated supersu, downloaded and installed magisk.
Now what I want to do is load the sony framework and get a root cloak. Any ideas of best way for that?
stumbows said:
OK yep installed TWRP, performed backup, flashed supersu, booted and confirmed root, updated supersu, downloaded and installed magisk.
Now what I want to do is load the sony framework and get a root cloak. Any ideas of best way for that?
Click to expand...
Click to collapse
Nope... Not a clue, sorry.

NO OEM unlocking with S off

I just bought a new Verizon HTC 10 that is S off. The bootloader is locked and I don't have an option to check the OEM unlocking, just isn't there.
download mode
*** LOCKED***
htc_pmewl PVT S-OFF
CID-VZW_001
Any idea on how I can get the OEM unlocking to show so I can unlock the bootloader?
The only thing I am not sure of is that there is no simm card yet. Do I need to have my simm card in to get the OEM unlocking to appear.
anderson96007 said:
I just bought a new Verizon HTC 10 that is S off. The bootloader is locked and I don't have an option to check the OEM unlocking, just isn't there.
download mode
*** LOCKED***
htc_pmewl PVT S-OFF
CID-VZW_001
Any idea on how I can get the OEM unlocking to show so I can unlock the bootloader?
The only thing I am not sure of is that there is no simm card yet. Do I need to have my simm card in to get the OEM unlocking to appear.
Click to expand...
Click to collapse
If its S-off already there is no need for the bootloader to be unlocked.
Thanks
Thanks for the help the reason I ask is because I thought I read that the bootloader has to be unlocked in order to root and install a custom rom. I've done this before but always started from a factory phone so getting one s off already is new to me.
anderson96007 said:
Thanks for the help the reason I ask is because I thought I read that the bootloader has to be unlocked in order to root and install a custom rom. I've done this before but always started from a factory phone so getting one s off already is new to me.
Click to expand...
Click to collapse
The 10 is a little different.
Locked and unlocked work basically the same, and it's my understanding it's suggested to be S-OFF locked from Sunshine crew.
I've been S-OFF locked since release of vzw S-OFF and everything works perfectly.
Hope this helps a little.
Just doesn't work
I have been trying for hours to get it to accept Supersu but it just doesn't. I flashed TWRP and when I try to flash Supersu it goes through the motions and says everything is OK but my phone never gets rooted. I was thinking of trying fastboot OEM unlock. I don't know how they achieved S off and read that may have something to do with it. I wanted to flash the new Venom ROM but maybe I will have to stick with TWRP and the stock ROM if I can't get it figured out. Thanks for your help so far I do appreciate it.
Steve
anderson96007 said:
I have been trying for hours to get it to accept Supersu but it just doesn't. I flashed TWRP and when I try to flash Supersu it goes through the motions and says everything is OK but my phone never gets rooted. I was thinking of trying fastboot OEM unlock. I don't know how they achieved S off and read that may have something to do with it. I wanted to flash the new Venom ROM but maybe I will have to stick with TWRP and the stock ROM if I can't get it figured out. Thanks for your help so far I do appreciate it.
Steve
Click to expand...
Click to collapse
I would leave the phone locked.
If you plan on flashing Venom, and you have already flashed twrp, there really is no need to root the current rom. Just make a backup of it in twrp (just in case) and flash Venom. Just make sure you select the correct firmware that matches the phones firmware in the aroma installer.
OK will give that a shot tomorrow thanks
If you're S-OFF. You shouldn't have any issues flashing the latest N firmware for your device, latest TWRP, and then latest N ViperROM. And since Viper comes pre-rooted, you will only need flash ViperROM.
Get a hold if you need some help, I'll do my best to assist.
Andy Bones in May I was asking you about flashing the Viper rom then got sidetracked. Now I would like to do it. I have an HTC 10 I bought that was already S off and locked. I installed TWRP 3.1.0.1 and my firmware is 6.0.1. I tried to flash Viper 10_5.9.0. I use the 6.0.1 button when asked which firmware I want to flash to although the 7. is already checked. Everything installs OK as far as the info page goes but when trying to restart the HTC start screen comes up and the phone just hangs. Reflashed backup and the phone is back to how I got it now. If you can tell me what I am doing wrong that would be great thanks.
anderson96007 said:
Andy Bones in May I was asking you about flashing the Viper rom then got sidetracked. Now I would like to do it. I have an HTC 10 I bought that was already S off and locked. I installed TWRP 3.1.0.1 and my firmware is 6.0.1. I tried to flash Viper 10_5.9.0. I use the 6.0.1 button when asked which firmware I want to flash to although the 7. is already checked. Everything installs OK as far as the info page goes but when trying to restart the HTC start screen comes up and the phone just hangs. Reflashed backup and the phone is back to how I got it now. If you can tell me what I am doing wrong that would be great thanks.
Click to expand...
Click to collapse
My HTC 10 is S-OFF Locked bootloader, this is what Sunshine crew suggests, and works the same (on the 10, previous devices are different) as unlocked bootloader.
It seems you are in a simple bootloop. Would need recovery log to see more, and Viper devs would be able to understand their stuff better than myself.
I do have suggestion as to what I would do.
You are on 6.0.1, you should update to the latest Nougat 2.41.605.18. Either by flashing the firmware, or flashing the RUU. Read up on encryption with Nougat.
Everything you said you did sounds correct to me. And as are as selecting the correct firmware in Aroma, that is for the fingerprint to work, and can easily be fixed if you accidentally select N instead of MM.
I hope this helps in some way.

G5 Plus Help unroot help!

Ok so I am just going to say I am a idiot and need some help. Please don't hate on me. I am not good with phone technology, but I followed directions to root my phone with TWRP & Magisk 12.0 and everything is working ok for the most part. The problem is I need a specific app to work for my job, but it fails to start due to the failed Safety Net. I would probably be able to figure out how to unroot it & relock the bootloader, but in my haste to root my phone, I did not backup the stock ROM image 1st. If anyone can help me figure out the next step to go back to a factory phone, I would forever be indebted to you. My specific model is an XT-1681 dual sim which I believe is from Brazil. I am in the US and not sure if I can use a different stock rom because I have tried searching to no avail. Please help if you can.
Thanks for your time.
There's a flash file for magisk which allows it to pass safety net. I saw it in the Lineage thread a few days back, but I don't know the exact origin.
Secondly, you can't relock the bootloader anyways. I don't know for sure if that in itself would cause safety net issues.
Karlinski said:
There's a flash file for magisk which allows it to pass safety net. I saw it in the Lineage thread a few days back, but I don't know the exact origin.
Secondly, you can't relock the bootloader anyways. I don't know for sure if that in itself would cause safety net issues.
Click to expand...
Click to collapse
I appreciate the response, but I was able to finally locate the stock rom from a site linked on here & flashed and relocked the bootloader using ADB. Basically my phone is stock again & working like I need it to. I tried hiding the app in Magisk, but was unsuccessful. So I guess this post can be locked.
ronefx said:
I appreciate the response, but I was able to finally locate the stock rom from a site linked on here & flashed and relocked the bootloader using ADB. Basically my phone is stock again & working like I need it to. I tried hiding the app in Magisk, but was unsuccessful. So I guess this post can be locked.
Click to expand...
Click to collapse
Which phone version you have retin?
Sent from my Moto G (5) Plus using Tapatalk

Please, please help. Can't Unroot or Return X-Play to Stock

I've really reached the end of the road here and I don't know anything else to do other than throw the phone in the bin. I bought an X Play XT1562 in the UK last year and I made the stupid, stupid mistake of flashing LineageOS on to it.
I followed all of the instructions to the letter, did all the necessary android upgrades, unlocked the bootloader, rooted it e.t.c... and it worked fine.
When it came time to restore it to a stock rom, I found out that I couldn't downgrade it and return it to stock due to LineageOS being a newer version of Android - either that or something to do with the bootloader. I've spent so long trying to rectify this situation, my memory is starting to get a bit fuzzy !
Anyway, I eventually found this thread with instructions on how to use ADB to flash the UK stock rom. I got errors on the partition flashing but I read somewhere else that you needed to keep going and enter all of the commands, which i did.
The phone did reboot and it did appear to be returned to stock, but when I went to check if it was still rooted, Super Su kept giving me the error "root access is not properly installed in this device".
And I simply cannot correct this, no matter what I try. I've tried flashing different versions of TWRP, re-rooting it with different versions of Super Su and even King Root and then using Super Su to remove root.
I've even tried re-rooting it and flashing the @osm0sis unSU script which flashes in TWRP and says it's removed root, but when i reboot and re-run Super Su, it still gives me "root access is not properly installed in this device". It's almost like it's burnt in to the rom of the phone at this rate.
If i can't remove this or correct it, the phone is as good as junk to me because I can't sell it otherwise so i'm really hoping someone has an idea or suggestion as to what might correct this situation.. thankyou if you can help.
That's the message SuperSU gives you when it's unrooted. Uninstall SuperSU again (or flash unSU again since it'll do that too), `fastboot format userdata` and you're done.
Thanks for the reply. Funnily enough I'm just waiting for the phone to boot up at the moment and optimise the apps after running your script so i'll try what you've suggested.
I was told in the second hand shop i tried to initially sell the phone in that when they run root checker, it shouldn't come up with any message regarding root, so if i can just get to that point then i can sell the damn thing.
It didn't work. The phone booted up and i ran root checker and still got the error "root access is not properly installed in this device".
I rebooted to TWRP and re-flashed it. I then rebooted back to the bootloader to try the erase userdata command but i kept getting an error saying something about it couldn't erase the date on a filesystem marked as "raw". I thenk rebooted the phone again and ran rootchecker again and it still gave me the error.
I used super su to unroot after that, rebooted and still got the error.
That all said, I've found another second hand shop that will take the phone as long as it works - the root error won't be an issue. as long as the phone is ok with receiving OTA updates (which it is, as i'm doing them at the moment) and is properly unlocked (which i'll test shortly) then I can sell it for some much needed money.
I've really run out of patience, energy and enthusiasm to try and fix this issue now so i'll take it to the other shop tomorrow. I just wish i'd never flashed LineageOS on it - i would have easily been able to return it to unrooted stock if i hadn't.
Try searching for any su folder in general. Due to systemless root, root goes away after a reset. I am guessing you flashed a version which was not systemless on MM and that caused the **** up. Why don't you try flashing the custom ROM and be happy with it ? The stock ROM are bloated and crap anyway. If you are planning to give your phone for updating/repair, it's futile anyway. Upgrade your phone to N or use other custom ROMs.
If you are still hell bent on getting rid of those files, root the phone using magisk and rule out any su files that you can find.
Sent from my SM-J730GM using Tapatalk

Categories

Resources