Database Develop

Why ODIN? WHY?!

It's driving me nuts, and I would like someone to help me understand. I came here with a bricked and completely unrepairable phone, and I have since managed to get a new Note. The completely stubborn side of me went right away flashing ICS ROMS...Okay, that's all good and well...No harm done anyway. But why don't developers include the "base" and root kernel files in their frickin' ROMS?! It's incredibly annoying. Why do I have to go into "ODIN" and download mode to flash some repack, wipe wipe wipe, reboot, flash another base, wipe wipe wipe, reboot, and finally flash a "custom" ROM. I should be able to flash a single .zip file through CWM and be down with it. I'm not bad talking at all, and I greatly appreciate what developers do around here.
For example, MIDNOTE includes ICS kernel and base...one integrated file. EVERYTHING works, and I have full root access. I'm wondering what it will be like when Samsung comes out with an official ICS version, will I have to flash ten different files to use a custom ROM or will developers be able to integrate it into their work? Just a question...not meant to cause trouble in the least...it just erks me the wrong way. And I'm sure others are wondering the same too.

They does it because you dont need to get those annoying yellow triangle and increase those custom binary counters....Would you like having triangles and increase counters?And the ICS roms are too early releases and are still in beta stages.So you need to go with the process.GB roms dont have these problems and are less hectic.Thats why I still stay in GB.Custom ICS roms will be ok when Official ICS is released.

@smalmagal
you are aboulutely right...
its a shame that they dont make it even easier to flash...
i mean please, the only thing that they are doing is:
- Prepare a Rom from scratch
- Provide updates
- Try to fix bugs
- And that in their free time for free
why not make a rom that i click on and its installed on my device...
like windows popups...
Click on Link and choose:
a- Save
b- Open
c- Flash to my Phone, make all the settings and text my GF that i love her...
Pleaseeee mate...
Not everyone is a dev here but at least we should be able to flash a rom...
Cooking takes days and week, flashing in WORST case 1 hour...

Bulut.O said:
@smalmagal
why not make a rom that i click on and its installed on my device...
like windows popups...
Click on Link and choose:
a- Save
b- Open
c- Flash to my Phone, make all the settings and text my GF that i love her...
Click to expand...
Click to collapse
Made my day!!! LOL !! could you please add
d-
e-
f-
ha ha ha ha ha ha hah!!

Bulut.O said:
@smalmagal
you are aboulutely right...
its a shame that they dont make it even easier to flash...
i mean please, the only thing that they are doing is:
- Prepare a Rom from scratch
- Provide updates
- Try to fix bugs
- And that in their free time for free
why not make a rom that i click on and its installed on my device...
like windows popups...
Click on Link and choose:
a- Save
b- Open
c- Flash to my Phone, make all the settings and text my GF that i love her...
Pleaseeee mate...
Not everyone is a dev here but at least we should be able to flash a rom...
Cooking takes days and week, flashing in WORST case 1 hour...
Click to expand...
Click to collapse
Are you serious???????Do you think rom flashing is like installing your favorite app???As I said when Stock ICS is released everything would become easy

Bulut.O said:
@smalmagal
you are aboulutely right...
its a shame that they dont make it even easier to flash...
i mean please, the only thing that they are doing is:
- Prepare a Rom from scratch
- Provide updates
- Try to fix bugs
- And that in their free time for free
why not make a rom that i click on and its installed on my device...
like windows popups...
Click on Link and choose:
a- Save
b- Open
c- Flash to my Phone, make all the settings and text my GF that i love her...
Click to expand...
Click to collapse
vijai2011 said:
Are you serious???????Do you think rom flashing is like installing your favorite app???As I said when Stock ICS is released everything would become easy
Click to expand...
Click to collapse
@vijai2011 you completely missed the point!! Didn't you??
The things said by @Bulut.O is called SARCASM
Read again!! And this time carefully!!
Peace

I'm serious guys! This is the only device I've ever owned where I have to flash a million different files just to get my phone booting...so I'm just trying to understand what's up. And obviously I LOVE the Note or else I wouldn't have bought two.
Developers do this for free...okay, yeah...but they don't have to do it half-assed? If I was going to sell you a car, I'd probably give it to you one piece. I wouldn't make you take all the parts and put them together yourself only in the end to find out that you're missing the engine and have to start all over again. And honestly, that's how I feel around here sometimes.
And the comment about Windows is out of line. I don't use Windows...why does everyone assume Windows? Honestly don't know why more don't use Linux around here. Windows just plan ol' sucks.
Edit: Custom ROMS aren't build from "scratch" by the way...and not everyone around here who posts a ROM is a "developer."

This issue is not because of lazy developers. It is because Samsung is tired of replacing devices under warranty when the terms of said warranty have been broken, and as a result putting extra security measures in place.
Lazy developers would let you get the yellow triangle, and then let you foot the bill for your mistakes while flashing.

beestee said:
This issue is not because of lazy developers. It is because Samsung is tired of replacing devices under warranty when the terms of said warranty have been broken, and as a result putting extra security measures in place.
Lazy developers would let you get the yellow triangle, and then let you foot the bill for your mistakes while flashing.
Click to expand...
Click to collapse
Huh? I'm talking about doing everything from CWM...not from ODIN. So no yellow triangle...and as far as I know, every custom ROM around here is a CWM flashable .zip file...minus the oh so coveted ICS repack...which needs ODIN for some unknown reason to me. So now, I'm not calling myself lazy, or the developers around here for that matter. There's a good reason, I know it...I want to find out. Samsung is a different beast for sure, and this is the first Samsung device I've owned, and I'm trying to avoid bricking again, so I'd like to learn all the procedures and such...and why they're necessary. It's for my piece of mind really.

smalmagal said:
Huh? I'm talking about doing everything from CWM...not from ODIN. So no yellow triangle...and as far as I know, every custom ROM around here is a CWM flashable .zip file...minus the oh so coveted ICS repack...which needs ODIN for some unknown reason to me. So now, I'm not calling myself lazy, or the developers around here for that matter. There's a good reason, I know it...I want to find out. Samsung is a different beast for sure, and this is the first Samsung device I've owned, and I'm trying to avoid bricking again, so I'd like to learn all the procedures and such...and why they're necessary. It's for my piece of mind really.
Click to expand...
Click to collapse
You just answered your own question. The process is long and somewhat complicated because it HAS to be done via recovery. If it were done via download mode in ODIN, it would be much simpler; but it would trip the counter. Using recovery instead of download mode sidesteps this problem, but it introduces others. That is why flashing to/from ICS/GB via recovery is so complicated.
Sent from my GT-N7000 using xda premium

I appreciate you bleeding edge types, but this is why I wait a few weeks AFTER an official rom is released, before I even consider a custom rom.
ICS is still an infant...I'd rather have one that was at least able to drive a car before I install it.

geo.samuel said:
@vijai2011 you completely missed the point!! Didn't you??
The things said by @Bulut.O is called SARCASM
Read again!! And this time carefully!!
Peace
Click to expand...
Click to collapse
Lol....Ok.understood it now.Now generally as said in above post,lazy developers would let you get triangles and increase custom binaries.So they need to make multiple files which makes your phone ready for flashing your favorite firmware.If you probably own a galaxy s series you would know how easy it was to flash firmwares.Thats because sammy did not implement any security measures which Gnote has.Hope you understand

smalmagal said:
every custom ROM around here is a CWM flashable .zip file...minus the oh so coveted ICS repack...which needs ODIN for some unknown reason to me.
Click to expand...
Click to collapse
It's because of the kernel and root. Unlike GB kernels, this one seems to be a bit wonky, and your root permissions get lost easily in CWMR flashing or Nand restoring. Hence the convoluted flashing procedures. Lack of code sources, I suppose.
All of us have to accept this if we want a taste of Roms based on the Chinese leak. No-one is happy with the current state of the affairs, but we manage.
Nobody is forcing you to deal with it. If you can't, stick with GB Roms until the final version of ICS drops.

I have flashed several ICS Roms and only flashed the chainfire repack the very first time when I moved to ICS from gingerbread. I have flashed Criskelo, rocket and midnote just from CWM. Never had a triangle, SOD etc...just full wipe before I flashed and then cleared caches after.

development to get around all the security in 4x

Lets see if we can get
- Locked bootloader
- Custom rom security issues
and maybe other security related problems in one development thread and how we make apps to get around this
I take the lead for now, since i started testing custom roms (JellyBean) right now.
and the DRM check at bootup is important to get around, otherwise we end up, having to restore a v10 image again and again, too often.
i suspect that it can be done using a bind folder. but lets see where this takes us.
just update with other issues seen.

Dexter_nlb said:
Lets see if we can get
- Locked bootloader
- Custom rom security issues
and maybe other security related problems in one development thread and how we make apps to get around this
I take the lead for now, since i started testing custom roms (JellyBean) right now.
and the DRM check at bootup is important to get around, otherwise we end up, having to restore a v10 image again and again, too often.
i suspect that it can be done using a bind folder. but lets see where this takes us.
just update with other issues seen.
Click to expand...
Click to collapse
Sounds little bit like Chinese for me but hope you can get a break through and goodluck for all who trying to make it for us an even great phone

ok, i have had my jellybean semi running and oneX rom running, both not very functional, as most hardware did not work well.
the lgdrmserver kept crashing on me as well, but probably less important.
the solution i made was the early boot used the original libraries from /lib from and vendor/lib , so i simply mapped the 2 files in /lib with a symlink to the /system/drm folder and ran the wallpaper binary and it worked fine.
secondly changed a vold binary to be a little script, that
1: bind'd new libraries for drm in drm2 folder (mount -obind drm2 drm) so the new booting os would get related files.
2: start vold
and the workaround seemed to do just fine for the drm security check.
IF it fails during regular boot if you unintentionally copied over the files, do not worry. booting into safe mode (keep VOL UP pressed and press power) you can connect with a shell and bypass the check, and fix your failure and reboot.

Hi
Is DRM checking forced from kernel?
Can we live without it?

no, its called from init.d

Dexter_nlb said:
Lets see if we can get
- Locked bootloader
- Custom rom security issues
and maybe other security related problems in one development thread and how we make apps to get around this
I take the lead for now, since i started testing custom roms (JellyBean) right now.
and the DRM check at bootup is important to get around, otherwise we end up, having to restore a v10 image again and again, too often.
i suspect that it can be done using a bind folder. but lets see where this takes us.
just update with other issues seen.
Click to expand...
Click to collapse
It is allways exciting to see people like you fellow.
Curious, courageous, openminded, wise and most of all doing all without expecting anything.
Success on your way..:good:

Dexter_nlb, You're a hero :good:
When will be released some beta?

since we have root, shouldnt init.d be accessable and easily modifyable?

The Troll said:
since we have root, shouldnt init.d be accessable and easily modifyable?
Click to expand...
Click to collapse
its part of the boot.img (ramdisk), so not really, but the 2nd-init makes it possible to make a new ramdisk and start it. but its only ramdisk, not the kernel, which remains static.

downgrade mode?
sorry, im a htc user thinking of buying this phone.. *since s3 isn't tegra, not thd games and one x kinda sucks with the lack of sd card and stuff..*
but htc has a dorwngrade mode.. 2 exposed connectors close to the camera.. short circuit them to access downgrade mode.. and then flashable though linux..
if im right, that should give u open access to bootloader..
evo 3d cdma used this method to get s-off.. as in bootloader unlocked and accessable with all write restrictions removed on all partitions..
oh forgot to meantion, this can brick ur device.. actually downgrade mode itself is a bricking method.. so i'd be careful *assuming this method is true for gs as well*

The Troll said:
downgrade mode?
sorry, im a htc user thinking of buying this phone.. *since s3 isn't tegra, not thd games and one x kinda sucks with the lack of sd card and stuff..*
but htc has a dorwngrade mode.. 2 exposed connectors close to the camera.. short circuit them to access downgrade mode.. and then flashable though linux..
if im right, that should give u open access to bootloader..
evo 3d cdma used this method to get s-off.. as in bootloader unlocked and accessable with all write restrictions removed on all partitions..
oh forgot to meantion, this can brick ur device.. actually downgrade mode itself is a bricking method.. so i'd be careful *assuming this method is true for gs as well*
Click to expand...
Click to collapse
nah, we haven't nothing to lose... someone should try it

The Troll said:
but htc has a dorwngrade mode.. 2 exposed connectors close to the camera.. short circuit them to access downgrade mode.. and then flashable though linux..
if im right, that should give u open access to bootloader..
evo 3d cdma used this method to get s-off.. as in bootloader unlocked and accessable with all write restrictions removed on all partitions..
Click to expand...
Click to collapse
i believe you reference a different hardware platform not Nvidia based. o4x is nvidia tegra3 and different from omap and other platforms security wise.
can you link to the tegra fuse , you reference here? (fuse is a connector which will break the firmware open and full access granted, but can also cause firmware to not load, since fuse is broken)

reas0n said:
nah, we haven't nothing to lose... someone should try it
Click to expand...
Click to collapse
flash image GUI..
someone rooted should try that first..
also, unlimited.io <--- website.. for details of the downgrade mode trick..
http://forum.xda-developers.com/showthread.php?t=1547695
http://forum.xda-developers.com/showthread.php?t=1491107
http://forum.xda-developers.com/showthread.php?t=1563342
http://forum.xda-developers.com/showthread.php?t=1627917
the basic idea of this is 2 connectors close to the camera.. short circuit them to switch the phone to downgrade mode *QHSUSB_DLOAD*.. bricking the device and mounting all partitions as read and writable.. then using linux to find the right partition to flash/dump the hboot *the bootloader*
at the end, if it uses fastboot/adb, i dun think this will be too different from the evo 3d..
try it.. but dont say i didnt warn you..
im not sure its a fuse, its more of a reset?
also, i dont exactly have the phone *yet* so i cant tell..
but for the 3d, its exposed.. 2 holes in the back under the cover, next to the camera..
http://unlimited.io/juopunutbear-public-beta-0-1/instructions/evo-3d-cdma-shooter/
or you can find a schematic of the phone itself..
if you dont mind me asking, whats the reason for the lack of devs?
this is an excellent phone..
is it the extreme security?
iphone got a jailbreak too :/

ok, this is a QUALCOMM solution, not for our tegra3 based platform

Dexter_nlb said:
ok, this is a QUALCOMM solution, not for our tegra3 based platform
Click to expand...
Click to collapse
how did one x get the kernels running?
**edit.. nvm.. htcdev.. forgot..

Hope you guys can pass by all that anoyeingsecurity. Would like to buy that phone but without real controll over the hardware aand custom rom community i would seariously reconsider buying it...

Dexter, the One X solution is for Tegra3 devices. The QUALCOMM-Device is called HTC One XL. So if the chipset is nearly the same, there must be a solution? If I could code anything, I would. But I cannot

Hilmy said:
Hope you guys can pass by all that anoyeingsecurity. Would like to buy that phone but without real controll over the hardware aand custom rom community i would seariously reconsider buying it...
Click to expand...
Click to collapse
Instead of trying to bypass, people should be asking LG for an unlock mechanism. I've been talking to them about this for over half a year, and today they still feel there is no demand for it (unlock tools)
Show of hands: How many people here have actually e-mailed LG asking for an unlock procedure, for this or any other of the current locked generation?

aremcee said:
Instead of trying to bypass, people should be asking LG for an unlock mechanism. I've been talking to them about this for over half a year, and today they still feel there is no demand for it (unlock tools)
Show of hands: How many people here have actually e-mailed LG asking for an unlock procedure, for this or any other of the current locked generation?
Click to expand...
Click to collapse
do you have the mail address we can use? then we can engage a mailrobot to send them 10000s of mails regarding the unlocker, and maybe they will follow asus and motorola/google on this one.

Dexter_nlb said:
do you have the mail address we can use? then we can engage a mailrobot to send them 10000s of mails regarding the unlocker, and maybe they will follow asus and motorola/google on this one.
Click to expand...
Click to collapse
I'd rather not forewarn them by asking for a contact for this
My personal opinion: a mailrobot would be a bad idea, they'd just filter it out. Actual users, with actual devices (serial numbers in the message and all that) would carry much more weight than just generic "gimme". From experience... petitions don't work, either, unless they hit visible news outlets;
My suggestion would be to hit a support contact, consistently (instead of dispersing the message to random contacts); most companies will escalate any issue given enough occurrences of it. On the other hand, I can't find contacts besides the country-specific ones at http://www.lg.com/global/supports/service-sites.jsp ...

Some questions about root and roms

I was never into following what is going on with smartphones. So i have a few questions so that i dont feel lost.
So i want to root my phone. I have done it before, its pretty simple, i will just follow the guide. Are there any reported bricks coming out because of rooting moto g2 or is it relatively safe?
Then since i was going to do a hard reset for the root i thought about using another ROM. I dont generally know anything about mods. I only know the famous cyanogen mod. Is it working good with moto g2? Are there any problems? Is development ongoing? I think i saw a guide but i missed the link btw.
Now i generally dont care about my phone looking great with 3D stuff and gimmicks for showing. I want it to be as fast as it can be and ready to do as many things as it can. Thats why i am rooting it btw. So that i can do things that unrooted wont permit me and so that i can block adds for example in order to make it a bit faster and less power/data draining.
So is the CM mod okay with what i need?
And finally, since lollipop is coming out, should i wait for it to be available before i do anything in case that there would be a lollipop CM for moto g 2 or this would probably take too much time so i better do the hard reset now? Btw i am not sure if CM mod can be upgraded without hard reset in which case i am good to go.
P.S. I am not even sure if CM is really better than official. Any hints why it is better?
Thanks for your time.

U can easily root without brick.

NUKE1989 said:
So i want to root my phone.
Click to expand...
Click to collapse
No bricks reported from rooting only so far. It's a relatively safe procedure. CM12 is still in it's early days. Across all devices there are still various bugs. If you like to try lollipop there are two possibilities. Wait for ota (be sure to unroot and restore stock recovery. OTA won't install if you are rooted or have a custom recovery). Or you can try TitanPrimeROM (not the cm version). Its based on stock and runs quite nicely.

Thank you for the replies.
So i think i am going to just root the phone. But i wanna ask why is this thread locked? Is there any problems with this guide?
http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245

Dont take tention root the device.

NUKE1989 said:
Thank you for the replies.
So i think i am going to just root the phone. But i wanna ask why is this thread locked? Is there any problems with this guide?
http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245
Click to expand...
Click to collapse
Outdated and unofficial. Use this TWRP 2.8.4.0 Touch Recovery [OFFICIAL] [TITAN]

doppelhelix said:
Outdated and unofficial. Use this TWRP 2.8.4.0 Touch Recovery [OFFICIAL] [TITAN]
Click to expand...
Click to collapse
Damn i just rooted it with 2.7.1.1 cause i saw there were backs with the one i posted but couldnt find a more recent one.
I guess i will have to do it again... Thanks though!
And one final question, every time i want to change a rom it is like doing a hard reset right? There isnt anything like backup or something that will help me keep apps and data while changing roms.

NUKE1989 said:
Damn i just rooted it with 2.7.1.1 cause i saw there were backs with the one i posted but couldnt find a more recent one.
I guess i will have to do it again... Thanks though!
And one final question, every time i want to change a rom it is like doing a hard reset right? There isnt anything like backup or something that will help me keep apps and data while changing roms.
Click to expand...
Click to collapse
You can try Titanium Backup.. It allows you to backup your apps and reload them in a new ROM..

unrootable (prototype N6)

hey everyone just picked up a prototype N6 from a buddy and having serious issues rooting this verion. i have rooted my other N6 with no issues but this build (shamu-userdebug l lrw80j 1454210 dev-keys) just wont seem to work if anyone can point me in the right direction that would be great ty. this version included a power button on the back of the phone which was nice and why it caught my eye.

What have you tried and where does it fail?
Root is usually unlock bootloader, flash recovery, flash supersu from recovery.
The problem you may have if the hardware is different is that the kernel would then be different, meaning there wont be a version of TWRP with a bootable kernel for your device. So just like you cannot run TWRP for a HTC on the Nexus 6, that could be the same case.

oh ok i see what you mean. everytime it gets to the try to temp load twrp it never seems to boot up im using the toolkit .and now it seems that i can't even boot into the system anymore just into fast boot but i can still use the flash boot flash options in root tool kit and i think you are so right about the kernel but just dont know which one to use i tried restoring /baseband /boot/system with a orignal factory 6.0 but individually but not working . is there a different method you think i can try? ty for your help.

sunnybwoy1 said:
oh ok i see what you mean. everytime it gets to the try to temp load twrp it never seems to boot up im using the toolkit .and now it seems that i can't even boot into the system anymore just fast boot. is there a different method you think i can try? ty for your help
Click to expand...
Click to collapse
If you're going to root, recovery is important.
There are apps that can root once booted into android, but you're playing with fire, especially if there hardware is different - as that means you will not have a factory image to flash either. These things are best kept untouched.

Great and I just messed up this systems IMG. cause I'm just stuck at the fastboot now I hope there is away around this. I had a feeling I shouldn't have gotten this version but wanted to be different now it just cost me smfh. Here are the pics of the phone and info

Here are some pics of the phone and build number

sunnybwoy1 said:
Here are some pics of the phone and build number
Click to expand...
Click to collapse
I cant think of a way around it. You could try flashing a stock system.img via fastboot but I cant say I'm hopeful and likely will make things worse. Without custom recovery, it is unlikely that you can repair it.
You can of course try and factory reset it. Who knows, may make it boot?

Yea flashing the system. IMG in fastboot made it worst well I used the new android m system so maybe that's why. Not looking good I hope I can get some answers soon or if maybe someone can mod a system. IMG I can use with this hardware .

sunnybwoy1 said:
Yea flashing the system. IMG in fastboot made it worst well I used the new android m system so maybe that's why. Not looking good I hope I can get some answers soon or if maybe someone can mod a system. IMG I can use with this hardware .
Click to expand...
Click to collapse
I don't think you'll get help here.

to me, it doesnt look like a n6, it looks like a moto x pro..

simms22 said:
to me, it doesnt look like a n6, it looks like a moto x pro..
Click to expand...
Click to collapse
It does, but it definitely does have an engineering bootloader and says shamu XT1103, so it's another one of "those"

danarama said:
It does, but it definitely does have an engineering bootloader and says shamu XT1103, so it's another one of "those"
Click to expand...
Click to collapse
yup. i bet it was the moto x pro, but in development still. they probably used all the shamu software on it at first. im curious whether it would take the moto x pro software.

I'm going to try to flash a stock N6 ROM to see if it will load.

Is this prototype the one with fingerprints sensor on the back?

It has a power button on the back.

sunnybwoy1 said:
Great and I just messed up this systems IMG. cause I'm just stuck at the fastboot now I hope there is away around this. I had a feeling I shouldn't have gotten this version but wanted to be different now it just cost me smfh. Here are the pics of the phone and info
Click to expand...
Click to collapse
PM Me if you decide to "part" with it.

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!