Database Develop

[SOLVED]Sending back for warranty repair question

Hello all. My wife has a bionic that I rooted and installed for3ver root. I only debloated the phone and installed v6 supercharger on it. I just upgraded her to the OTA .905 now her speaker went out.
I need to send it in for warranty they are sending a new one. I tried last night to RSD lite it back to stock. Now I used RSD a lot on my x2 in the past so no stranger to it. Using RSD 5.6 it would not recognize her phone. I reinstalled drivers and rsd lite and rebooted the computer but the computer would see the usb connected but not RSD lite. After trying several ways to get RSD to recognize the phone I ended up using petes root method to unroot the phone. I unrooted it and was able to erase all rooted apps including SU.
So here is my million dollar question. Since it is stock rom and now unrooted if I do a factory reset will it be safe to send to verizon or do I need to try another computer and try the RSD lite all over again?
Thanks in advance. I think it will be okay after a factory reset but there is pople on here a lot smarter than I am

When you did RSD Lite did you use the provided factory cable with the Bionic? The most common issue with most windows computers not recognizing the phone is due to not using the factory cable. As far as wiping via factory reset I don't know if it leaves remnants of some files used. FXZ'ing it would be your best bet. However some other users have reported that they have sent their phones still rooted and had no issues. Might have been lucky. Good chance is Verizon employees don't check to see if the phone was rooted and send off the phone to Motorola to do whatever they do with the phones.

Thanks for the response. Yes I was using the factory cable and phone was chareged to over 80% battery. My next step was to use another computer and try all over again. But after getting it unrooted I was not sure if it would be needed after a factory reset. But yes I would feel much better if I was able to flash it in RSD. Also I did try multiple usb ports I know voltage can be an issue as well.

Search for rsd version 5.7 and try it that way. Haven't had an issue using 5.7 with the bionic
0001001- 0000011- 0010011
I. C. S.

elreydotcom said:
Search for rsd version 5.7 and try it that way. Haven't had an issue using 5.7 with the bionic
0001001- 0000011- 0010011
I. C. S.
Click to expand...
Click to collapse
Sorry I should of mentioned I also tried 5.7 as well after 5.6 did not work. I might try another computer later and try again tonight just for a piece of mind.
Also just a fyi I am using windows Vista. But same computer I always used on my X2 with no issues. I read someone uninstalled the moto helper and re installed and that worked for them. I think at this point another computer will be my next option if I really need to wipe it clean.

Travisdroidx2 said:
Sorry I should of mentioned I also tried 5.7 as well after 5.6 did not work. I might try another computer later and try again tonight just for a piece of mind.
Also just a fyi I am using windows Vista. But same computer I always used on my X2 with no issues. I read someone uninstalled the moto helper and re installed and that worked for them. I think at this point another computer will be my next option if I really need to wipe it clean.
Click to expand...
Click to collapse
are you making sure to plug the usb into computer first and then the phone?
You very well might be just fine sending it in as is.
If you want to be 100% certain tho, RSD/FXZ(or whatever they call it Lol, fastboot flash) is the way to go

So after talking with Ash and getting his and Nitro's advice it sounds like it is a driver issue for sure. Nitro and Ash pointed me in the right direction for the right drivers again. I will try again tonight. Hopefully tomorrow I can put solved in the title and I will post any links to drivers that helped me out.
Thanks to Ashclepdia and Nitro for the advice!!!! And all others that gave their opinion.

Hope it works!
Now back to playing final fantasy 3 on my nexus.
$16 for it but so far worth it if u like FF3 RPG game. Fun

Travisdroidx2 said:
Sorry I should of mentioned I also tried 5.7 as well after 5.6 did not work. I might try another computer later and try again tonight just for a piece of mind.
Also just a fyi I am using windows Vista. But same computer I always used on my X2 with no issues. I read someone uninstalled the moto helper and re installed and that worked for them. I think at this point another computer will be my next option if I really need to wipe it clean.
Click to expand...
Click to collapse
Windows Vista/7 is notorious for not detecting stuff without the correct driver. I know i've had issues with my Bionic and Kindle Fire on my home computer running Windows 7. Those problems went away but before that I had to bring my stuff to work and try it off my Windows XP work computer which worked flawlessly on both.

amageus said:
Windows Vista/7 is notorious for not detecting stuff without the correct driver. I know i've had issues with my Bionic and Kindle Fire on my home computer running Windows 7. Those problems went away but before that I had to bring my stuff to work and try it off my Windows XP work computer which worked flawlessly on both.
Click to expand...
Click to collapse
Yep during my googling search last night I seen where a lot of people with Vista had the same issue. Damn drivers and Vista I am sure I will get it tonight. I have another computer in the house without vista if it comes down to it.

Thanks everyone specially Ash and Nitro. So my problem was the drivers. Nitro suggested I get the drivers from motorola support website. I deleted my old drivers from my Dinc2 and started over. Installed drivers from the motorola website and re install RSD lite again 5.7 this time. But the main thing is after I downloaded the device manager for the drivers when I plugged the phone in RSD could see it. I flashed it back to ,902 and now going to update it to .905. I feel much better now that I know it had a clean wipe. THANKS! To everyone that gave me suggestions. If anyone else is having this issue feel free to PM me and I can give you files needed.

[Q] I Think I Really Screwed The Pooch

So i brilliantly unlock the bootloader on the moto x and rooted the phone also installed the su and then the real genius part came out and i accidentally wiped the whole fing phone all the sdcard and the entire os and now all i have is a wonderful beautiful white motorola moto x and cant use it oh and to make things really worth it i just open the account with sprint so the phone is only 3 days old. Can someone Please Help me i am at a lost and dont have a clue what to do. I dont know how to reinstall the OS.:crying::crying::crying:

lsl73 said:
So i brilliantly unlock the bootloader on the moto x and rooted the phone also installed the su and then the real genius part came out and i accidentally wiped the whole fing phone all the sdcard and the entire os and now all i have is a wonderful beautiful white motorola moto x and cant use it oh and to make things really worth it i just open the account with sprint so the phone is only 3 days old. Can someone Please Help me i am at a lost and dont have a clue what to do. I dont know how to reinstall the OS.:crying::crying::crying:
Click to expand...
Click to collapse
I am having somewhat the same issues. Someone is helping me out and if I get an easy solution I will be happy to share.

This should help you:
http://forum.xda-developers.com/showthread.php?t=2446515

superaj13 said:
I am having somewhat the same issues. Someone is helping me out and if I get an easy solution I will be happy to share.
Click to expand...
Click to collapse
Thanks i hope you can get yours going as well

fabriciosr said:
This should help you:
http://forum.xda-developers.com/showthread.php?t=2446515
Click to expand...
Click to collapse
The rsd lite cant see my moto x i can only access it thru the fastboot but when i try the rsd way it doesnt see the phone.

Download/find the correct system.img and boot.img for your device, then push/install them via fastboot. You shouldn't need anything else. Recovery, bootloader, and other firmware should be untouched. Only issue is if it's a safestrap device, then I have no clue.

gokart2 said:
Download/find the correct system.img and boot.img for your device, then push/install them via fastboot. You shouldn't need anything else. Recovery, bootloader, and other firmware should be untouched. Only issue is if it's a safestrap device, then I have no clue.
Click to expand...
Click to collapse
Gokart i have tried that i dont think i am doing it wrong i got the system.img and the boot.img from here but just incase i ride the small yellow bus with a helmet on can you please point me to the direction i need to go AGAIN.

try to
fastboot flash system system.img

The obvious thing is make sure you have fastboot set up correctly... Drivers as well.

Make sure all drivers are installed, trust me redlite works with a soft bricked moto x, I found out today, my phone was bootlooping, nandroids failed soi wiped the sdcard and realized at that point I did the noob thing, well it worked like a charm rsdlite
Sent on my Moto X

this is the error i keep getting

lsl73 said:
this is the error i keep getting
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2489249

i would like to thank all you guys for all the advise that was given to help me bring my moto x back to life i finally got it up and running again using the moto x toolkit it seemed like the only thing that would of work in my situation again thank yall so much :victory::victory::victory:

Who unlocks their bootloader but doesn't know what to do when stuff goes bad, like this?
If you read enough to unlock the bootloader, you should have read enough to know what to do here. Coming here frantic without even checking the eleven billion threads already is silly. We have about 12 threads about the new update and similar high number threads about restoring your phone.
Too many repetitive threads for the Moto X on xda. Some people just need to take 5 minutes and look through general or Q&A before they blindly post. Clutter everywhere.
And finally, dude! I do not have any pity for you. I'm on Verizon and cannot unlock my bootloader maybe that's why I just ranted. Nothing personal, just a general consensus of this section as of late...
Sent from my XT1060 using Tapatalk

oh brother i am not mad at you but as a by the way i DID try different ways of trying to load the os back using this site as a guidance before i made this post this post was a last ditch effort before i smash the moto x and use the insurance claim on it i have been a member of this site since 2010 i just didnt create this account

[Q] How would you root? I'm on day FOUR of unsuccessful attempts

It started here:
http://forum.xda-developers.com/showthread.php?t=2530605
I followed this post.
http://forum.xda-developers.com/showthread.php?t=2509676
Got nowhere because of the puttytel window timeout problem.
Related to this post was this post:
http://forum.xda-developers.com/showthread.php?p=47749358#post47749358
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:

bullpen7979 said:
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:
Click to expand...
Click to collapse
Are you on 4.4 and what computer OS are you using?

I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.

bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
Here, go into Settings -> About Phone and tell me what your Build Number is (at the very bottom).

Do not put in the cmd window mfastboot, just try fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img. Now also put the recovery image in the same folder as fast boot, I believe its SDK tools folder
Sent on my Moto X

bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
The method that you thought was confusing, is the one you should use. If I have time, I could try helping you with it.

ALU0506, the build number is 13.9.0Q2.X-116-MX-17-57-1. Thanks everyone for your help.

I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great

bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
I can try helping over gtalk.

bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?

I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app

bullpen7979 said:
I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app
Click to expand...
Click to collapse
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all

jayboyyyy said:
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all
Click to expand...
Click to collapse
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.

aooga said:
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.
Click to expand...
Click to collapse
ya during his four days of misery, he could have just read for 1 hour on the stuff so it would seem confusing anymore and then he would have had a rooted phone. But either way, his problem is solvable with a few simple instructions.

OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.

OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.
Phone is in fastboot mode with white, yellow green text.
Device is unlocked. Status code 3.
Battery OK Charging
Transfer mode USB connected.
It looked as though I had to be able to accept the 4.4 kitkat OTA in order to get this done. but when i went to the usual spot to look for system updates it said there were none available.
Anyhow, I am super grateful for your help. Sorry to be such a remedial doofus

Looks like we can wait till tomorrow. Or today. Or whatever timeline it is.

Bricked? Say it ain't so.

So trying any and everything to remove safestrap and install the latest ota i think i wiped all my data and my system cause now i just sit on the blue motorola m forever. I have an at&t moto x. the only thing i can do is fastboot with vol down and after that none of those options bring me anywhere. am i completely f'd or is there some way to fix this? thanks for the help guys.

Rsdlite back to stock
Sent from my Nexus 7 using Tapatalk

zeer.row said:
So trying any and everything to remove safestrap and install the latest ota i think i wiped all my data and my system cause now i just sit on the blue motorola m forever. I have an at&t moto x. the only thing i can do is fastboot with vol down and after that none of those options bring me anywhere. am i completely f'd or is there some way to fix this? thanks for the help guys.
Click to expand...
Click to collapse
Do you have any experience with fastboot? If not, google how to download it for whatever type of computer you have. I'm on a linux machine so its pretty straight forward, but I think its easy on any machine. If you're on windows you'll need the motorola drivers as well. You'll also need a factory stock image for at&t moto x.
After that it's just a matter of flashing the image to your phone and starting over.
I'm sorry, forgot about the locked bootloader. Listen to the guy before me.
If there are any pictures or stuff like that on your phone, i'm afraid those will probably be lost.
I will try to find helpful links for all this stuff, but I just wanted to give you something to look for while I did that.

Anthony04x said:
Rsdlite back to stock
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
lnstalling rsdlite now. will update. thanks a ton.

Okay, got it.
1. Go here and download that (hopefully you're on a windows machine):
http://forum.xda-developers.com/showthread.php?t=1348587
2. then go here and download the AT&T one. The third one down is KitKat, so just go with that, since it's what you're trying to do anyway.
http://sbf.droid-developers.org/ghost_rcica/list.php
3. Make sure you have these drivers installed:
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
Now, go into RSDLite, click on load or open or whatever it says and go to the FXZ from step 2.
Click start.
Should be that easy, let me know if there are any hiccups.

thank you sooo much!

Hey no problem, we've all been there at some point. Did you get it working?
ps. Don't forget about that thank you button.
Sent from my XT1060

You can use the moto x toolkit here in this forum too. Install, open as administrator, install drivers from main menu, pick back to stock from main menu. Follow on screen instructions and it will do the rest from there
http://forum.xda-developers.com/showthread.php?t=2477132

This is in the completely wrong section. Needs to be moved to Q&A. Questions and help posts don't belong in a Development section.
Sent from my Nexus 5

Moto X was Bricked - Fixed - Thanks for the help
Thank you - it worked -
For some reason VZW wouldn't update my Moto X from 4.2.2 to Kit Kat. I bricked it trying. RSDLite fixed it with your instructions and now I'm on 4.4 Kit Kat.
Thanks!
JetOhmNet said:
Okay, got it.
1. Go here and download that (hopefully you're on a windows machine):
http://forum.xda-developers.com/showthread.php?t=1348587
2. then go here and download the AT&T one. The third one down is KitKat, so just go with that, since it's what you're trying to do anyway.
http://sbf.droid-developers.org/ghost_rcica/list.php
3. Make sure you have these drivers installed:
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
Now, go into RSDLite, click on load or open or whatever it says and go to the FXZ from step 2.
Click start.
Should be that easy, let me know if there are any hiccups.
Click to expand...
Click to collapse

OP - you can use my script here:
http://forum.xda-developers.com/showthread.php?t=2603051
choose Advanced Menu and then #2 - Flash Binaries (no wipe)
it uses the mfastboot method and may be able to save your data.

Delete all files and re-partition all?

If you ever had loaded into recovery in temporary TWRP you'll note that even after formating /data/ and doing an advance wipe (selecting everything), then enter the file manager there is still a bunch of folders and some files throughout your device.
Is there a way to wipe out everything and start completely 100% fresh?

DO NOT DO THIS --- OR --- DO but do not cry about it
I have an answer to my question and it is as I suspected. The short and more official answer is, no. The longer answer is, yes, technically. -- But you should not try it unless you are 100% sure you can live without your phone (forever).
As it turns out no one had a full 100% flash for the whole device and its complete file system structure (except for Motorola). But as it turns out without a manufacturing cable it would be useless anyway. This is because part of your phone is protected and cannot be wiped clean and flashed so blindly... ie... Unlike your desktop computer. But if you're like me you have noticed some orphan files (a few logs).
Is it worth taking the risk just to clear some orphan files? Probably not. But since you do not have a manufacturing cable and technically, your phone can recover, what you can do is the following.
Do NOT use the TWRP installed on your phone. Rather use it in memory
Code:
sudo fastboot boot twrp-3.3.1-0-payton.img
Load TWRP and format DATA
Reboot, go to advance wipe, wipe everything.
Reboot to TWRP (again)
In TWRP via the terminal type in
HTML:
rm -r -f *
You will see a lot of things that cannot be deleted. This is because you do not have permission to do so. What little is removed will likely be restored after reboot from the master rom hidden somewhere on your phone which cannot be played with unless you have a manufacturing cable (so I am told). ---- If you have such a cable --- DO NOT DO THIS. --- If you suspect you have such a cable --- Do NOT do this. -- I did this with just my normal charging cable.
After you have run the command which will take forever. Tell TWRP to reboot to bootloader. You will now have a BLACK screen. This is where I panicked. I waited a while and long pressed down the power button (presumably turning off my device). Then I pressed down the power button and the lower volume button. -- Keep holding the buttons. -- It will take longer than you like but your phone will boot up. And low and behold everything that was in the master rom (chip?) has been restored and you will now see the bootloader screen (finally). Load TWRP and install your ROM of choice.
How many times have I done this successfully? 2x
Does this mean this is dependable? Unlikely
Do I recommend this? No.
Should you depend on this? No.
Are you taking a large gable? YES
Can this brick your device? YES, more than likely.
Should you do this if you have any doubts? NO.
Will you get any help if this goes wrong? NO.
So why did I do it? As I look to possibly upgrade my phone in the future I feel a little more daring and can afford to do so. lol

you say "yes, technically", but I have yet to see someone get back to a fully operational stock. The best they can do is get to a mostly operational custom ROM. I (and a bunch of other folks here) would love to be proven wrong.

KrisM22 said:
you say "yes, technically", but I have yet to see someone get back to a fully operational stock. The best they can do is get to a mostly operational custom ROM. I (and a bunch of other folks here) would love to be proven wrong.
Click to expand...
Click to collapse
After performing this I installed only the official firmware. No additional ROM or GSI. The firmware itself includes the stock software.
A word of caution. --- I did this on 3 phones now. 2 work just fine. But 1 does not. The one that does not reports my IMEI as 0. This means it boots, it loads, it will play games and apps and update via Google Play Store, but it will never make a single phone call ever again. --- Food for thought.

Thanks. That got me thinking - I wonder if you took the one with no IMEI and plugged it to Moto's Smart Assistant, would it recognize it? Would it allow you to force flash it?

KrisM22 said:
Thanks. That got me thinking - I wonder if you took the one with no IMEI and plugged it to Moto's Smart Assistant, would it recognize it? Would it allow you to force flash it?
Click to expand...
Click to collapse
The world will never know. lol --- I'm a Linux user and their app doesn't seem to like Wine. I suppose I could set up a virtual machine with Windows and hope to connect through that. But I was once informed you really cannot do that via a virtual machine. Unless I was misinformed?! In any case, flashing the phone is not a problem. I can wipe it and reinstall any ROM or GSI at the moment. Or I can repeat my process too back to stock under a full wipe. The results appear to be the same.
I already have ordered a cheap Moto G7 from Google as a replacement. My current plan will be to find a very light (small), bare-bones ROM / GSI and install it onto this Moto X4. From there I'll load it up with games and such and let the kids play with it. Figure since it cannot make or receive calls anymore (or text messages either) it will make for a fun little toy.

MotoX4 said:
The world will never know. lol --- I'm a Linux user and their app doesn't seem to like Wine. I suppose I could set up a virtual machine with Windows and hope to connect through that. But I was once informed you really cannot do that via a virtual machine. Unless I was misinformed?! In any case, flashing the phone is not a problem. I can wipe it and reinstall any ROM or GSI at the moment. Or I can repeat my process too back to stock under a full wipe. The results appear to be the same.
I already have ordered a cheap Moto G7 from Google as a replacement. My current plan will be to find a very light (small), bare-bones ROM / GSI and install it onto this Moto X4. From there I'll load it up with games and such and let the kids play with it. Figure since it cannot make or receive calls anymore (or text messages either) it will make for a fun little toy.
Click to expand...
Click to collapse
Thanks! Yeah, in the past I have been a lot on Ubuntu and stuff like this is not forgiving for wine.
It's a darn shame that we can't just send these phones to Moto with $25 and get it fixed. Oh well!

KrisM22 said:
Thanks. That got me thinking - I wonder if you took the one with no IMEI and plugged it to Moto's Smart Assistant, would it recognize it? Would it allow you to force flash it?
Click to expand...
Click to collapse
Moto smart assistant can`t recognize the phone in rescue mode..

St.Noigel said:
Moto smart assistant can`t recognize the phone in rescue mode..
Click to expand...
Click to collapse
I know it can't on yours, and most folks with this prob. I was wondering about MotoX4's case. But thanks for trying it!
I had high hopes for that smart assistant when I discovered it, but no joy. When we lost RSDlite, we lost a lot - unless they upgrade it...

KrisM22 said:
I know it can't on yours, and most folks with this prob. I was wondering about MotoX4's case. But thanks for trying it!
I had high hopes for that smart assistant when I discovered it, but no joy. When we lost RSDlite, we lost a lot - unless they upgrade it...
Click to expand...
Click to collapse
RSDlite? Lost? Is this what you seek? https://rsdlitetool.com/

MotoX4 said:
RSDlite? Lost? Is this what you seek? https://rsdlitetool.com/
Click to expand...
Click to collapse
6.2.4 won't recognize a Moto X4 after it is upgraded to Pie.

I used RSDLite since the times of the P2K and MAGX (Linux)... but since it's easier to use fastboot commands...
I have a stock X4 Android One around, if I want to flash Pixel Experience, can I go back to stock in the future?

joel_sinbad said:
...snip...
I have a stock X4 Android One around, if I want to flash Pixel Experience, can I go back to stock in the future?
Click to expand...
Click to collapse
In all probability, NO.

Then I'm gonna stay on Stock Rom, so... If I want to flash custom Roms, there's not way back...

joel_sinbad said:
Then I'm gonna stay on Stock Rom, so... If I want to flash custom Roms, there's not way back...
Click to expand...
Click to collapse
If you read a lot on this forum, that's the message I see.

I agree, NO going back. You can, I have... flash any factory Pie rom . All will flash fine and no IMEI, wifi. Radios are gone. I use Google Fi and cell data services go wierd on custom roms, if you want carrier switching.

This makes me think that the Moto X4 is more dangerous than the back then Atrix 4G with their Tegra 2 chipset...

joel_sinbad said:
This makes me think that the Moto X4 is more dangerous than the back then Atrix 4G with their Tegra 2 chipset...
Click to expand...
Click to collapse
I don't recall thinking that the Moto Atrix 4g was at all dangerous when I had one - a rather nice phone imho, though that was a very long time ago. I don't think of the Moto X4 as "dangerous" - it is simply that there is not a correct understanding of the Pie file structure by the custom ROM devs such that their ROMs would not so change the file structure of the phone as to prevent it from being flashed back to stock.
Users need to recognize that, with this phone, you can't get back to stock if you flash any custom ROM.
afaik.
This change happened with the file structure and boot structure changes of the Pie update. Prior to that, folks could get away with all manner of mods. Devs for this phone need to approach modifications with the idea of assuring that any mod can be flashed back to stock, BEFORE it is released. That has not happened. And likely won't. User beware!

KrisM22..... Thank you for stating what I could not do as well.

kkjb said:
KrisM22..... Thank you for stating what I could not do as well.
Click to expand...
Click to collapse
we ALL do it, and CAN do it - all in hopes of saving some newbie from disaster!