Database Develop

[Q] Curious tutorial to return from 4.4.4 to 4.4.3 from Brazil

Hey, I was surfing the net and came across this website that ensures returned from 4.4.4 to 4.4.3 safely. Do you think, is it true?
www,motox-brasil.blogspot.com.br/2014/08/tutorial-fazendo-downgrade-do-android.html
Thanks for your comments

Ayel7bytes said:
Hey, I was surfing the net and came across this website that ensures returned from 4.4.4 to 4.4.3 safely. Do you think, is it true?
www,motox-brasil.blogspot.com.br/2014/08/tutorial-fazendo-downgrade-do-android.html
Thanks for your comments
Click to expand...
Click to collapse
There is risk involved. Notice that the author of that guide is telling you to remove the lines for flashing the partition table (gpt.bin) and the bootloader (motoboot.img)?
That means although you can get back to 4.4.3, you will most definitely have a mismatched partition table and/or bootloader. The biggest risk is when you take a future OTA. You risk bricking at that point - we have seen it happen multiple times here on XDA. While you might get away with it and be just fine, anyone who claims it to be perfectly safe is mistaken. There IS risk involved.
I'm really not understanding why one would even wish to downgrade back to a previous version anyways? Oh well - to each their own.
If you decide to follow that guide, you are doing it at your own risk.
Good Luck :good:

..

Ayel7bytes said:
samwathegreat Thank you very much for your advice. I prefer to believe you. The only reason for wanting to downgrade was because I'm from South America (Chile) and I made the mistake of following the footsteps of dashiell.cano to have verizon 4.4.4. It works, but wanted the rom Brazilian Retail 4.4.3 to access your OTA 4.4.4 already arrived. But you know a lot and it's smart to follow his advice. Greetings and thanks for your time.
Sorry for my poor English management
Click to expand...
Click to collapse
No worries. As soon as the FULL 4.4.4 Brazilian SBF is released (not the OTA), you can safely flash the entire sbf without risk of bricking. It may take a couple more weeks or a month (can't say exactly when), but it will be leaked eventually and you can safely go back to your proper rom at that time.
:good:

@Ayel7bytes , keep in mind that besides the many posts of bricking from those who downgraded by skipping GPT.BIN and MOTOBOOT.IMG, we've also seen the phones not behave properly.
One of the best examples that come to mind is App Drawer -> Settings -> Security would kick you back out to the settings menu when downgrading from 4.4.2 to 4.4 (aka 4.4.0).
You are right in asking about it. And as @samwathegreat said, just sit tight until the 4.4.4 SBF for your carrier/model leaks, and then flash all parts of it.

KidJoe said:
@Ayel7bytes , keep in mind that besides the many posts of bricking from those who downgraded by skipping GPT.BIN and MOTOBOOT.IMG, we've also seen the phones not behave properly.
One of the best examples that come to mind is App Drawer -> Settings -> Security would kick you back out to the settings menu when downgrading from 4.4.2 to 4.4 (aka 4.4.0).
You are right in asking about it. And as @samwathegreat said, just sit tight until the 4.4.4 SBF for your carrier/model leaks, and then flash all parts of it.
Click to expand...
Click to collapse
I can conclude with this situation every moto x is a story itself. I faithfully well-intentioned warnings but after you do this Brazilian tutorial with something of fear and see that I had no problem (my phone is perfect and better than before), I suspect that perhaps the Latin American models allow modify XT1058 but other versions like American XT1060 with all your locks maybe not. In my case I got my bike from verizon x 4.4.4 root and recovery modified brazil retail removing lines xml and then un updating OTA 4.4.4. It worked immediately.
But of course I do not recommend everyone do this. I just want to say that nothing is absolute and every moto x has its risks depending on the model and what their owners have done.

[Q] OTA Requires Carrier Approval ?

My new N6 (Google Play Store) with a Verizon sim card has not been offered the 5.1 update OTA. It was offered the 5.01 OTA update on first boot. I ran across the following statement on the web.
As for who handles updates, it all comes from Google, no matter what. However, Google will withhold updates based on SIM card pending carrier approval. AT&T has not approved Android 5.1 yet, and therefore, anyone with an AT&T SIM card in their Nexus 6, no matter where it was purchased, will not be offered the OTA until AT&T approves it. So far, the only US carriers to approve Android 5.1 are T-Mobile and Sprint.
Click to expand...
Click to collapse
So, has any non-branded Verizon N6 received the 5.1 OTA yet? Please exclude any "forced" or manual OTAs.
I was hoping that at last my carrier would not interfere with updates.
Thanks ...

clairez said:
I was hoping that at last my carrier would not interfere with updates.
Thanks ...
Click to expand...
Click to collapse
Yeah this is a new thing. Ridiculous. Its never been tied to SIM provision before.

clairez said:
My new N6 (Google Play Store) with a Verizon sim card has not been offered the 5.1 update OTA. It was offered the 5.01 OTA update on first boot. I ran across the following statement on the web.
So, has any non-branded Verizon N6 received the 5.1 OTA yet? Please exclude any "forced" or manual OTAs.
I was hoping that at last my carrier would not interfere with updates.
Thanks ...
Click to expand...
Click to collapse
Based on recollection, a few. But not many. And yes, AT&T is definately trying to control updates. I suspect Verizon will, too.
Based on the following article, I doubt that you will ever get a Verizon specific OTA on your device > http://www.androidpolice.com/2015/0...te-one-that-wasnt-purchased-from-the-carrier/

No mine would only update to 5.01. GPS N64.

Maybe pull Sim card reboot and check via only WiFi?

dahlem said:
Maybe pull Sim card reboot and check via only WiFi?
Click to expand...
Click to collapse
You might get D this way, but not E.

dahlem said:
Maybe pull Sim card reboot and check via only WiFi?
Click to expand...
Click to collapse
That didn't work for me - I had to also perform a factory reset to get the "D" OTA (tried this yesterday). I'm on Verizon with a Nexus 6 bought directly from Motorola.
At least this thread sort of answers my question posed in the linked post above. However, I'm wondering if there's something on the phone we can "clear" (so to speak) after removing the SIM in order to help trigger OTAs from Google, bypassing carrier interference.
I've been thinking of staying stock for awhile, due to expectations of quick-from-Google OTAs . . . but, this is driving me to consider custom ROMs and not looking back.
- ooofest

ooofest said:
However, I'm wondering if there's something on the phone we can "clear" (so to speak) after removing the SIM in order to help trigger OTAs from Google, bypassing carrier interference.
Click to expand...
Click to collapse
I'm not sure about this, but when you pull your SIM, I think Google sees it as a generic N6 via WiFi. So if you do generate an OTA download, it's the general one.

I wonder if you have to put another SIM card in. I know in Play, my device shows as a carrier, even though its a play store device. I imagine you'd have to use another sim in it to allow that sim to be "registered" with Google, to "overwrite" the previous one. I doubt there is anything you can clear to do that.

Pulling The String !
What I have learned so far ( rest of you gals/guys already know this! ) is that one has to be very careful with the information in these/all forums.
There are users who say they have received the automatic 5.1 OTA with a non VZ branded phone ( both GPS and Motorola variants ). But when you start to pull the string with more questions, answers start to become vague. And why people post information that is not factual is the subject of another post.
My experience at this point is as follows. With a Verizon nano sim in the N6, I will not receive any OTAs, now or in the future. The reason is not clear at this time. It may be because the N6 is listed as a non-VZ phone in Verizon's system. Which, in turn, may be caused by the IMEI not being registered in Verizon's database. All conjecture at this point. ( More factual information required )
What is clear to me is that Motorola and Google should post a warning about the N6 not being compatible with Verizon (presently). And recommend purchase of the N6 directly from Verizon. Not holding my breath on this one !
Back to the problem at hand. I have tried the various suggestions.
1. Removing the VZ sim and connecting via wifi does NOT produce an OTA (5.1) offer.
2. Removing the VZ sim and connecting via wifi and doing a factory reset DOES produce an OTA (5.1) offer. This requires a backup/restore of user data. Follow this procedure exactly:
a. Backup your Nexus 6 (go to “settings” >> “backup & reset” >> select an account to back-up by clicking on “backup” and selecting the account you want to backup)
b. Remove your SIM card (while the phone is on)
c. Reset your Nexus 6 (go to “settings” >> “backup & reset” >> “factory reset data”)
d. Restore your Nexus 6 during set-up but DO NOT insert your SIM card
e. At the end of the setup, you should be offered the 5.1 update
d. Download (~450MB) will take awhile dependent on connection speed
e. After download is complete, press the "restart and install" button
f. Android icon with spinning symbol during install system update ( 3-5 minutes)
g. N6 will restart automatically (Optimizing apps 126)
h. Home screen, Settings --> About phone --> Build number, LMY47D --> Version 5.1
But, this approach, for me, would be too onerous for future/routine OTAs. My purpose behind purchasing the N6 was the timely, automatic delivery of OTAs by Google without carrier interference. The referenced article by the Android Police may be the reality. The ultimate solution is of course with Verizon, which leaves me with an uncomfortable feeling.
As always, thanks for the help ...

@clairez,
Very good post, and summarized very concisely.

I got mine thru VZ, this is most likely the only time I'll ever say this about them - At least they released it, though being late to the party, with 5.1 already installed.
(I feel so bad for those who may have bricked trying the OTA or image and running into issues ...)
As to how they will affect us moving forward, I'm crossing my fingers, but while I hate it, let me play devil's advocate here, they didn't place a boot animation, sounds, or other oem crap on it, there are the small system services, but that's the same amongst all of the N6's. and the tramp stamp was easily removed aka ATT's.
So far, it could have been way worse as far as getting one from VZ, but I feel for you guys that had it early and are now waiting on them to get an OTA, or even have the unit register correctly on their systems.
But the overall answer to the overall thing, is that if they did hold up updates down the road, we do what any crackflasher would, flash the image when released, right? Why we got the thing in the first place

This emerging situation where carriers apparently delay our Nexus 6 OTA timings is leading me to stay on the flashing path.
Running stock and locked 5.1 E for now, might just run unlocked and accept potential decrease in local security to minimize danger in future flashes. I like stock so far, but being unlocked will probably tempt me to root and try custom ROMs, I expect.
If Verizon wanted us to stay on the pure OTA path with this phone, they don't appear to be showing that intent.
- ooofest

clairez said:
What I have learned so far ( rest of you gals/guys already know this! ) is that one has to be very careful with the information in these/all forums.
There are users who say they have received the automatic 5.1 OTA with a non VZ branded phone ( both GPS and Motorola variants ). But when you start to pull the string with more questions, answers start to become vague. And why people post information that is not factual is the subject of another post.
My experience at this point is as follows. With a Verizon nano sim in the N6, I will not receive any OTAs, now or in the future. The reason is not clear at this time. It may be because the N6 is listed as a non-VZ phone in Verizon's system. Which, in turn, may be caused by the IMEI not being registered in Verizon's database. All conjecture at this point. ( More factual information required )
What is clear to me is that Motorola and Google should post a warning about the N6 not being compatible with Verizon (presently). And recommend purchase of the N6 directly from Verizon. Not holding my breath on this one !
Back to the problem at hand. I have tried the various suggestions.
1. Removing the VZ sim and connecting via wifi does NOT produce an OTA (5.1) offer.
2. Removing the VZ sim and connecting via wifi and doing a factory reset DOES produce an OTA (5.1) offer. This requires a backup/restore of user data. Follow this procedure exactly:
a. Backup your Nexus 6 (go to “settings” >> “backup & reset” >> select an account to back-up by clicking on “backup” and selecting the account you want to backup)
b. Remove your SIM card (while the phone is on)
c. Reset your Nexus 6 (go to “settings” >> “backup & reset” >> “factory reset data”)
d. Restore your Nexus 6 during set-up but DO NOT insert your SIM card
e. At the end of the setup, you should be offered the 5.1 update
d. Download (~450MB) will take awhile dependent on connection speed
e. After download is complete, press the "restart and install" button
f. Android icon with spinning symbol during install system update ( 3-5 minutes)
g. N6 will restart automatically (Optimizing apps 126)
h. Home screen, Settings --> About phone --> Build number, LMY47D --> Version 5.1
But, this approach, for me, would be too onerous for future/routine OTAs. My purpose behind purchasing the N6 was the timely, automatic delivery of OTAs by Google without carrier interference. The referenced article by the Android Police may be the reality. The ultimate solution is of course with Verizon, which leaves me with an uncomfortable feeling.
As always, thanks for the help ...
Click to expand...
Click to collapse
thank you for your helpful post!
i just had a few clarifying questions. my current setup is 5.01 with an unlocked bootloader, rooted phone and twrp recovery.
in order for me to be able to accept the OTA update, i have to flash the stock image and stock recovery, unroot, and relock my phone. is that correct?

gunit34328 said:
thank you for your helpful post!
i just had a few clarifying questions. my current setup is 5.01 with an unlocked bootloader, rooted phone and twrp recovery.
in order for me to be able to accept the OTA update, i have to flash the stock image and stock recovery, unroot, and relock my phone. is that correct?
Click to expand...
Click to collapse
You don't need to re-lock your bootloader. Otherwise, yes on the others.

Evolution_Freak said:
You don't need to re-lock your bootloader. Otherwise, yes on the others.
Click to expand...
Click to collapse
thank you for your reply!

gunit34328 said:
thank you for your reply!
Click to expand...
Click to collapse
No problem at all.

just wanted to give my experience...
bought a nexus 6 from best buy last week and it came with 5.0 installed. right away it took a 5.0.2 update but nothing after that. I had to manually flash the 5.1 "E" build on it, which I did because I'm on verizon and felt it was the best to be on

dansan382 said:
just wanted to give my experience...
bought a nexus 6 from best buy last week and it came with 5.0 installed. right away it took a 5.0.2 update but nothing after that. I had to manually flash the 5.1 "E" build on it, which I did because I'm on verizon and felt it was the best to be on
Click to expand...
Click to collapse
Are you sure it was 5.0.2 ??? Should have been 5.0.1 no? Anyway, good job getting updated anyway. :good: Yes, Verizon users should be on E.

Evolution_Freak said:
Are you sure it was 5.0.2 ??? Should have been 5.0.1 no? Anyway, good job getting updated anyway. :good: Yes, Verizon users should be on E.
Click to expand...
Click to collapse
im sorry, you're right.. it was 5.0.1 because it was LRX22C.. my bad.

Upgrade to 5.1 (OTA or not) with possible downgrade to 4.4.4??

Hi!
I was searching for this but cant get clear info about it.
I m totally noob in android flashing, etc... I never touch my phone but now the warranty is expired... so i want to root and other stuff, but that's not the reason I'm here....
I have a Moto X 2013 XT 1058
Personal Argentina Kitkat 4.4.4 (212.44.26.ghost_row.Personal.en.AR - KXA21.12-L1.26)
Unrooted - bootloader locked (stock)
I recieved yesterday the OTA to update to Lollipop 5.1. I downloaded and saved for later, but i dont dare to install it, becouse with KK all things going great!.. i use Nova Launcher, Tasker, autovoice, and lots of custom stuff... I dont know what's gonna happend with all that if I update..
But the thing is that i read there's no way to downgrade once you updated to 5.1 (by OTA)
My question is...
What should i do to mantain the possibility of downgrade?
My guess is ..
1. Unlock the bootloader
2. flash 5.1 firmware (can i do this without update the bootloader?? and without wipe user data?, how?)
3. Use the phone, and if i dont like it.. (if the bootloader was not updated) downgrade to KK 4.4.4 again
4. flash 4.4.4.
Is would be a problem if runs 5.1 rom and KK bootloader?...
is possible any of this... without unlock bootloader? (guess not.. but still ask)
any other special procedure or "notes" that i should take care of?
If I root my current rom, can i make an image of the system, and then restore after taking the above mentioned steps?..
(what should i use to do that?)
Thank you very much for helping!! because, I m not going to install OTA update without knowing this things...
P.s. Sorry for my bad english.. , and really sorry if i m posting in wrong way

I would suggest you fully read -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202

What I did so I could go back to kit kat was wait for a developer to make a version that doesn't update the bootloader. There is a rom now that I'm running for the xt1053 model on 5,1, that doesn't update the bootloader. I'm in the same boat as you, using xt1058, but mines Rogers. The only thing that doesn't work is speaker phone. There should be a version available soon for our model, so you can wait. Lollipop has its issues, high cell stanby, which can be fixed by turning off carrier internet. If you want to do what I did, so you can go back if wanted is unlock the bootloader, root, flash custom recovery, then flash the xt1053 rom that doesn't update the bootloader. I will post link to rom
---------- Post added at 11:01 AM ---------- Previous post was at 10:59 AM ----------
http://forum.xda-developers.com/showthread.php?t=3155843
---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------
May I also suggest flashing xposed module, it is amazing. Then download gravitybox. It makes it so you have most of the features of a custom rom on stock

According to KidJoe's thread he is referencing, even you unlock the bootloader and successfully turn on your phone after flash the 4.4 SBF. You may experience bugs here and there. In a word, don't do it.

Sorry for no feedback... i didt have time for my beloved phone...
i read the threads, but there are many unrelated things that i lost the trail!
I downloaded a file... :
Code:
XT1058_GHOST_RETBR_5.1_LPA23.12-15_cid12_CFC.xml.zip
This is a RSDlite file... isnt it? but... it contains:
Code:
boot.img
factory_version_info_cfc.txt
flashfile.xml
fsg.mbn
gpt.bin
logo.bin
motoboot.img
NON-HLOS.bin
recovery.img
servicefile.xml
system.img
if i unlock my bootloader and flash SOME of this files (boot.img, system.img, and logo.bin)... with mfastboot.. what happend?
boot.img, system.img... and what else do i need?.. (I know that i dont have to flash motoboot.img and gpt.bin in order to leave my bootloader alone)
I m going to get 5.1 with KK bootloader doing this or i will brick my phone?.. (dont?. Why??)
Should i flash the other files?
fsg.mbn (dont know what this is)
NON-HLOS.bin (modem?... should i flash it?... should i erase modemst1 and st2 partition if i flash this?)
recovery.img (what if i want to put TWRP recovery? .. can i flash TWRP.img instead of recovery.img???)
is erasing data necessary?..
flashfile.xml file for RSDlite is:
Code:
<?xml version="1.0" ?>
<flashing>
<header>
<phone_model model="ghost_retbr"/>
<software_version version="ghost_retbr-user 5.1 LPA23.12-15 20 release-keysMSM8960PRO_BP_23255.138.89.00R"/>
<interfaces>
<interface name="AP"/>
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-download-size"/>
<step operation="oem" var="fb_mode_set"/>
<step MD5="3e8836a120a564338f472f0895c947c8" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="d089f063b897f108729d6ffcf63679e2" filename="motoboot.img" operation="flash" partition="motoboot"/>
<step MD5="4bfe6f5412c1c419150bf25f953b61d4" filename="logo.bin" operation="flash" partition="logo"/>
<step MD5="d2d88677984930fc2a0e8e167bbccad0" filename="boot.img" operation="flash" partition="boot"/>
<step MD5="e55b202a063a58cc1d7b47dcb65658cf" filename="recovery.img" operation="flash" partition="recovery"/>
<step MD5="35a58369963b281e963920bd4d9e1b77" filename="system.img" operation="flash" partition="system"/>
<step MD5="3a094721acc8fcd15ae114c0854f3395" filename="NON-HLOS.bin" operation="flash" partition="modem"/>
<step operation="erase" partition="modemst1"/>
<step operation="erase" partition="modemst2"/>
<step MD5="76b8c66ef4480e84a8f1b69800541115" filename="fsg.mbn" operation="flash" partition="fsg"/>
<step operation="erase" partition="cache"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="customize"/>
<step operation="erase" partition="clogo"/>
<step operation="oem" var="fb_mode_clear"/>
</steps>
</flashing>
if i go with RSDLite... this modifications will work for what i want??
Code:
<?xml version="1.0" ?>
<flashing>
<header>
<phone_model model="ghost_retbr"/>
<software_version version="ghost_retbr-user 5.1 LPA23.12-15 20 release-keysMSM8960PRO_BP_23255.138.89.00R"/>
<interfaces>
<interface name="AP"/>
</interfaces>
</header>
<steps interface="AP">
---------DELETE <step operation="getvar" var="max-download-size"/>
<step operation="oem" var="fb_mode_set"/>
---------DELETE <step MD5="3e8836a120a564338f472f0895c947c8" filename="gpt.bin" operation="flash" partition="partition"/>
---------DELETE <step MD5="d089f063b897f108729d6ffcf63679e2" filename="motoboot.img" operation="flash" partition="motoboot"/>
<step MD5="4bfe6f5412c1c419150bf25f953b61d4" filename="logo.bin" operation="flash" partition="logo"/>
<step MD5="d2d88677984930fc2a0e8e167bbccad0" filename="boot.img" operation="flash" partition="boot"/>
---------DELETE <step MD5="e55b202a063a58cc1d7b47dcb65658cf" filename="recovery.img" operation="flash" partition="recovery"/>
<step MD5="35a58369963b281e963920bd4d9e1b77" filename="system.img" operation="flash" partition="system"/>
<step MD5="3a094721acc8fcd15ae114c0854f3395" filename="NON-HLOS.bin" operation="flash" partition="modem"/>
<step operation="erase" partition="modemst1"/>
<step operation="erase" partition="modemst2"/>
<step MD5="76b8c66ef4480e84a8f1b69800541115" filename="fsg.mbn" operation="flash" partition="fsg"/>
<step operation="erase" partition="cache"/>
---------DELETE <step operation="erase" partition="userdata"/>
---------DELETE <step operation="erase" partition="customize"/>
<step operation="erase" partition="clogo"/>
<step operation="oem" var="fb_mode_clear"/>
</steps>
</flashing>
Should i delete any other line??.. (or undelete?)
And most important..
Can i flash stock rom if something goes wrong?.. (loading logo hangs... dont like LP.. etc?) or a rom backup (if i find the way to make a backup of my actual rom.. =)... can it be done with TWRP?)
Thanks!... and sorry if i'm asking something basic... but .. the more i read, more confused i am!

KidJoe said:
I would suggest you fully read -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
Click to expand...
Click to collapse
Buddy, your info is not very accurate, don't care to blame you, but you can't flash gpt or motoboot if you have newer version, the bl just won't let you.
Also I've downgraded 4 Moto X 2013 from 5.1 to 4.4.4 without any issue.
Unless you can somehow prove your info there, better correct it.
Ppl just tend to do stupid things like going 4.4.2 or earlier and update via OTA, which causes the broken bl.Also some get soft bricked coz of not wiping user data....

liveroy said:
Buddy, your info is not very accurate, don't care to blame you, but you can't flash gpt or motoboot if you have newer version, the bl just won't let you.
Click to expand...
Click to collapse
"Buddy"?? I don't know you, so as written, it comes across with a negative connotation. I'm not really sure how you meant it, or what your feelings are there...
But I suggest you step back and read that post (and the thread) a little closer, because the entire point of that is you can't flash an older GPT.BIN or Motoboot.img (or the parts included in motoboot.img), or downgrade them. Read FAQ #1 in that post, that calls out GPT/Motoboot while suggesting not downgrading... as do others, like #16. So maybe I generalized more than you like with the term "downgrade" but most will attempt using RSDlite and NOT edit the XML. Plus skipping parts (using fastboot or editing the XML with RSDLite) while trying to downgrade can cause other issues, so again, downgrading is generally not advised.
liveroy said:
Also I've downgraded 4 Moto X 2013 from 5.1 to 4.4.4 without any issue.
Click to expand...
Click to collapse
As I said in that thread (just maybe not the first post), some have claimed success... and 5.1 to 4.4.4 does appear to be less risky... We're seeing more try 5.1 -> 4.4.4 and posting "it worked," where as with 4.4.4 -> 4.4.2 and 4.4.2 -> lower nearly everyone who attempted had bricked and needed help recovering their phone. And because of the amount of bricks from attempts at downgrading in the past, the MODS would close and delete any posts suggesting downgrading was anything but risky.
In any case, you now have GPT and parts contained in Motoboot (specifically Bootloader, potentially TZ, and other parts) from 5.1 with the rest of 4.4.4 parts. And we've seen some features not working this way (speaker phone, Settings -> Security kicks you out, etc.)
Also in its current state, if your phone prompts you about the 5.1 OTA, and you click the wrong thing and accept it, then as even you mention, taking an OTA could cause you issues. (I also mentioned in that post/thread.)... So you'd also need to take steps to prevent being prompted for the OTA if your downgrade attempt is successful.
liveroy said:
Unless you can somehow prove your info there, better correct it.
Click to expand...
Click to collapse
Well, I do have a few threads linked in the OP of that thread from people who did try to downgrade and bricked, including some who skipped GPT/MOTOBOOT. So I would hope that counts as proof, or at least sufficient supporting evidence for providing warnings and caution messages if/when suggesting someone else downgrades their phone. And if you search, I'm sure you could find the many 4.4.4 -> 4.4.2 downgrade attempts that resulted in bricks.
Are all the bricks Hard/Solid? No. And I say that in the post and later in that thread.. there are varying degrees, some could be recovered and some couldn't. s5610 has done a lot with helping many who bricked downgrading from 5.1 to 4.4.4 recover.
liveroy said:
Ppl just tend to do stupid things like going 4.4.2 or earlier and update via OTA, which causes the broken bl.Also some get soft bricked coz of not wiping user data....
Click to expand...
Click to collapse
Funny, I mention to not downgrade then take an OTA as that causes a problem. (faq #1)
So it pretty much looks like you are agreeing with my warnings in that post/thread, so I'm not sure what your problem is? Just that I didn't word it clearly enough? or???
If you have specific points/numbers that you disagree with, please post in that thread, quoting what you think is wrong, what evidence you have that its wrong (other than it works on your phone, please provide me with posts supporting your stance), and I'll be happy to discuss and/or make corrections if I agree with you.

KidJoe said:
"Buddy"?? I don't know you, so as written, it comes across with a negative connotation. I'm not really sure how you meant it, or what your feelings are there...
But I suggest you step back and read that post (and the thread) a little closer, because the entire point of that is you can't flash an older GPT.BIN or Motoboot.img (or the parts included in motoboot.img), or downgrade them. Read FAQ #1 in that post, that calls out GPT/Motoboot while suggesting not downgrading... as do others, like #16. So maybe I generalized more than you like with the term "downgrade" but most will attempt using RSDlite and NOT edit the XML. Plus skipping parts (using fastboot or editing the XML with RSDLite) while trying to downgrade can cause other issues, so again, downgrading is generally not advised.
As I said in that thread (just maybe not the first post), some have claimed success... and 5.1 to 4.4.4 does appear to be less risky... We're seeing more try 5.1 -> 4.4.4 and posting "it worked," where as with 4.4.4 -> 4.4.2 and 4.4.2 -> lower nearly everyone who attempted had bricked and needed help recovering their phone. And because of the amount of bricks from attempts at downgrading in the past, the MODS would close and delete any posts suggesting downgrading was anything but risky.
In any case, you now have GPT and parts contained in Motoboot (specifically Bootloader, potentially TZ, and other parts) from 5.1 with the rest of 4.4.4 parts. And we've seen some features not working this way (speaker phone, Settings -> Security kicks you out, etc.)
Also in its current state, if your phone prompts you about the 5.1 OTA, and you click the wrong thing and accept it, then as even you mention, taking an OTA could cause you issues. (I also mentioned in that post/thread.)... So you'd also need to take steps to prevent being prompted for the OTA if your downgrade attempt is successful.
Well, I do have a few threads linked in the OP of that thread from people who did try to downgrade and bricked, including some who skipped GPT/MOTOBOOT. So I would hope that counts as proof, or at least sufficient supporting evidence for providing warnings and caution messages if/when suggesting someone else downgrades their phone. And if you search, I'm sure you could find the many 4.4.4 -> 4.4.2 downgrade attempts that resulted in bricks.
Are all the bricks Hard/Solid? No. And I say that in the post and later in that thread.. there are varying degrees, some could be recovered and some couldn't. s5610 has done a lot with helping many who bricked downgrading from 5.1 to 4.4.4 recover.
Funny, I mention to not downgrade then take an OTA as that causes a problem. (faq #1)
So it pretty much looks like you are agreeing with my warnings in that post/thread, so I'm not sure what your problem is? Just that I didn't word it clearly enough? or???
If you have specific points/numbers that you disagree with, please post in that thread, quoting what you think is wrong, what evidence you have that its wrong (other than it works on your phone, please provide me with posts supporting your stance), and I'll be happy to discuss and/or make corrections if I agree with you.
Click to expand...
Click to collapse
I won't multi-quote, to reduce size.
You seem very offended, even though I meant exactly the opposite, this was more like creative criticism. That's why I've used "buddy" instead of smth offensive, just fyi.I also said I won't bother to actually blame you for posting info that is not entirely true and many ppl want to downgrade, because the LP build is buggy, the Moto X just doesn't feel right on it.
Actually for the sake of the argument I can do a live session on downgrade from 5.1 to 4.4.4 on Twitch ot Youtube, but if that's the case you'll owe me an apology, which is not my sole intent.
I agree that you have mentioned about gpt and motoboot, but you still strongly advice against downgrade, when that actually is NOT so dangerous if done right and basically it's not very hard to do either.
Also to be honest, use of RDS from users that for no idea what they are doing is probably the biggest problem. While using fastboot is way safer and the way to go.
Anyway, tone down a bit and let's have a healthy conversation, so the users can actually get a grip on the stuff and what is actually possible , while keeping the risk at minimum.

liveroy said:
...Actually for the sake of the argument I can do a live session on downgrade from 5.1 to 4.4.4 on Twitch ot Youtube, but if that's the case you'll owe me an apology, which is not my sole intent.
I agree that you have mentioned about gpt and motoboot, but you still strongly advice against downgrade, when that actually is NOT so dangerous if done right and basically it's not very hard to do either.
Click to expand...
Click to collapse
I apologize if you didn't mean offence by it. You've been on line long enough to know that type written communications on these boards can be misunderstood. i.e. you can't hear the inflection in a person's voice, see their body language, so its hard to read some meanings. So I hope you can understand how, not seeing, hearing or knowing you, that calling me "buddy" could be taken in a way you might not have meant. And yeah, some of my frustration may have shown through the words and phrasing I chose when typing because that bothered me.
That being said...
I know why people would want to downgrade (see FAQ #4 in that post)
As for a live session, I'm not sure what that will do... I've already said people can downgrade by skipping parts (i.e. GPT/Motoboot) BUT that it does cause its own issues. We've seen reports of more bugs, and or things not working properly, some can live with those bugs and others can't. And of course people who accidentally took the OTA later usually, but not always, run into problems.
So if that is how you are downgrading, then there is nothing new to show me.
Your post said that you have "downgraded 4 Moto X 2013 from 5.1 to 4.4.4 without any issue." but you haven't said how. Did you skip flashing gpt/motoboot? In my reply to you, I state that you have mixed gpt/motoboot parts on the phone now. In your response, you did not comment. I've addressed your points, albeit with a slightly aggravated tone for which I apologize, so I was hoping that you could respond to them.
As you say... "if you do it right".... Ok, but no one has provided a "right way" that is 100% fool proof and has been 100% safe.
I've said in the past, I don't know everything. I don't claim to be the "end all/be all" source. In a discussion with someone claiming to be from Moto a while back who started a thread saying it was safe to downgrade and it does work (which was later deleted by the MODs because of all the people that jumped into that thread having bricked attempting it).. I said, I don't know how moto expects it should work, I just know based on hanging in this and other forums, of what actually happens. And that is still my position today.
So I don't mind if someone can show me I'm wrong. I welcome it, and appreciate the corrections as I don't want to spread WRONG/BAD info!
If you want to have a discussion, by all means, lets, but please provide a little more explanation around your difference in opinion.

KidJoe said:
I apologize if you didn't mean offence by it. You've been on line long enough to know that type written communications on these boards can be misunderstood. i.e. you can't hear the inflection in a person's voice, see their body language, so its hard to read some meanings. So I hope you can understand how, not seeing, hearing or knowing you, that calling me "buddy" could be taken in a way you might not have meant. And yeah, some of my frustration may have shown through the words and phrasing I chose when typing because that bothered me.
That being said...
I know why people would want to downgrade (see FAQ #4 in that post)
As for a live session, I'm not sure what that will do... I've already said people can downgrade by skipping parts (i.e. GPT/Motoboot) BUT that it does cause its own issues. We've seen reports of more bugs, and or things not working properly, some can live with those bugs and others can't. And of course people who accidentally took the OTA later usually, but not always, run into problems.
So if that is how you are downgrading, then there is nothing new to show me.
Your post said that you have "downgraded 4 Moto X 2013 from 5.1 to 4.4.4 without any issue." but you haven't said how. Did you skip flashing gpt/motoboot? In my reply to you, I state that you have mixed gpt/motoboot parts on the phone now. In your response, you did not comment. I've addressed your points, albeit with a slightly aggravated tone for which I apologize, so I was hoping that you could respond to them.
As you say... "if you do it right".... Ok, but no one has provided a "right way" that is 100% fool proof and has been 100% safe.
I've said in the past, I don't know everything. I don't claim to be the "end all/be all" source. In a discussion with someone claiming to be from Moto a while back who started a thread saying it was safe to downgrade and it does work (which was later deleted by the MODs because of all the people that jumped into that thread having bricked attempting it).. I said, I don't know how moto expects it should work, I just know based on hanging in this and other forums, of what actually happens. And that is still my position today.
So I don't mind if someone can show me I'm wrong. I welcome it, and appreciate the corrections as I don't want to spread WRONG/BAD info!
If you want to have a discussion, by all means, lets, but please provide a little more explanation around your difference in opinion.
Click to expand...
Click to collapse
I might end up writing a how-to sometime this weekend.
I started getting pms on how I did it, so that guide might help.
Also on a side note, I kinda sorry that you felt like you felt about my post, if something is still concerning you, feel free to contact me and we can discuss the matter.
With that said, I'm gonna work on the guide and post it and maybe get your input on it later on.

RAZR I On Stock Firmware- Recover From Bootloop w/o Erasing Data?

Recover from bootloop w/o erasing data?
This morning my phone decided not to boot anymore, but to go into a bootloop instead. The system is totally stock, no unlocked bootloader, no custom rom, nothing. Also, no OTA update was involved. Frankly, I know nothing about Android, so I appreciate all help I can get. I can't even remember which Android version it was running on (but I'm guessing it was JB). Before not booting anymore, I got various error messages from crashed apps and services, and I rebooted it manually.
Is there a way which I can try to recover from this without erasing all my data?
By now I figured out how to get into fastboot and talk to my phone from my computer (fastboot, not adb).
TIA Sebastian

You can use RSD Lite to flash your stock firmware again, problem is finding it, I guess, since you don't know what version you were running. Try to search for people with the same problem in your country, see where they get their firmware if they need to flash it. In my case I used that JellyBean Brazilian retail one, I don't know if that would work for you. I'm not even sure it worked for me, since my phone is crashing again.
You need to alter the XML file, erase the lines saying
<step operation="erase" partition="userdata"/> (or something like that)
and
<step operation="erase" partition="cache"/>
Then it won't erase anything.
To alter it, open it with Notepad++ or plain old notepad.exe (it's just harder to find the lines)
I'm a noob, so don't trust this too much. I'm only answering you because no one else did, maybe you still need help. And it's similar to my situation.
Good luck!

COVID 19 Downgrade

The latest update issued from Samsung for the T Mobile variant of the note 9 has slipped in an Android “Coronavirus Tracker” without Consent.
I just found this in my phone! See attachment.
Anyone with a tutorial for downgrading the OS?

It only works is you have a covid 19 app on your phone. No reason to downgrade
Sent from my SM-G988U using Tapatalk

This is not a tracker. It is only the framework for Google services to work with an app provided by governed agencies. If you do not opt in to the contact tracing , the files that are on your phone do nothing.
Sent from my SM-N960U using Tapatalk

Thanks for clarifying guys. I still want to be able to go back to an earlier firmware to this recent release. Is there a way to successfully accomplish this without root? I am attempting the ODIN method, but constantly being met with "FAILED". Any insight would be greatly appreciated. Thanks in advance.

michel5891 said:
Thanks for clarifying guys. I still want to be able to go back to an earlier firmware to this recent release. Is there a way to successfully accomplish this without root? I am attempting the ODIN method, but constantly being met with "FAILED". Any insight would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
Seems like that Samsung may have disabled the ability to revert back to Pie with their latest OS update.

You can only downgrade to an earlier firmware if it is the same bootloader version. For example, if you are on Android 10 with the June security patch (probably bootloader 3) you would be able to downgrade to the May firmware. I'm not sure if you can go back to March or April unless it's the same bootloader version.
Sent from my SM-N975U using Tapatalk

iceepyon said:
Seems like that Samsung may have disabled the ability to revert back to Pie with their latest OS update.
Click to expand...
Click to collapse
Yes, it does seem that way. However, I did a complete reset after backing up, did a search for the covid19 thing and it doesn't show up. So, I guess all is well for now.
Being unable to downgrade to previous OS releases is quite curious.

Look at the firmware version... For instance, my baseband version is N975FXXS4CTD1. The 5th number from the right is the bootloader version, in my case 4. If the bootloader version you are trying to flash is LOWER than the one you have it WON'T allow you to flash the firmware, you will get an error and fail. Higher number is a later bootloader and will flash but no love to get back to the older firmware...
Hope this helps a little...

I got rid of the Covid-19 thing from my Note 9 by uninstalling updates to Google Play Services. I can't remember the exact process, as this well several weeks ago, but it shouldn't be hard to find.
Also, proceed with caution. Removing Play Services updates may cause various Google apps to dysfunction.

I didn't even realize this was installed onto the phones.
Thank you for the heads-up.

I believe it is regional as I haven't encountered this on my Australian Note 9 or Note 10+ both running OneUI2.1...

michel5891 said:
The latest update issued from Samsung for the T Mobile variant of the note 9 has slipped in an Android “Coronavirus Tracker” without Consent.
I just found this in my phone! See attachment.
Anyone with a tutorial for downgrading the OS?
Click to expand...
Click to collapse
This worked for me!
Easy STEPS to TURN OFF COVID-19 Exposure Notifications on Android

Wise2TheLies said:
I got rid of the Covid-19 thing from my Note 9 by uninstalling updates to Google Play Services. I can't remember the exact process, as this well several weeks ago, but it shouldn't be hard to find.
Also, proceed with caution. Removing Play Services updates may cause various Google apps to dysfunction.
Click to expand...
Click to collapse
Correct. The only way to get rid of it is to delete Google Play Services. That's how they snuck it in. On Android Pie it's simple. Just debloat via ADB using pm list packages prompt and voila! it's gone. On Android 10 it works the same EXCEPT none of the google apps, firefox, instacart, or anything like that will WORK. So you can de-google all you want - they've baked it into everything. It's something I'm struggling with now since I was forced to upgrade.

Articul8Madness said:
Correct. The only way to get rid of it is to delete Google Play Services. That's how they snuck it in. On Android Pie it's simple. Just debloat via ADB using pm list packages prompt and voila! it's gone. On Android 10 it works the same EXCEPT none of the google apps, firefox, instacart, or anything like that will WORK. So you can de-google all you want - they've baked it into everything. It's something I'm struggling with now since I was forced to upgrade.
Click to expand...
Click to collapse
You don't need to delete the Google Play Services.
The actually Service is called "exposurenotification", and there are a couple of this service entries inside the Google Play Services App.
The last Version I could find was around Jun/Jul 2020, which had none of these entries.
I was able to "kick" the services with a Service Disabler APP, but the modified Settings Entry remained.
Perhaps it could be worth to dig deeper into this, but it is a bit over the level of my understanding.
Spoiler: com.google.android.gms.nearby.exposurenotification
XML:
<permission android:name="com.google.android.gms.nearby.exposurenotification.EXPOSURE_CALLBACK" android:protectionLevel="signature" />
<uses-permission android:name="com.google.android.gms.nearby.exposurenotification.EXPOSURE_CALLBACK" />
<activity android:enabled="true" android:excludeFromRecents="true" android:exported="false" android:name="com.google.android.gms.nearby.exposurenotification.settings.SettingsCheckerActivity" android:process="com.google.android.gms.ui" android:taskAffinity="" android:theme="@style/ExposureNotificationDialogStyle" chimera:autoEnabled="true">
<intent-filter>
<action android:name="com.google.android.gms.nearby.exposurenotification.settings.CHECK_SETTINGS" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
<service android:enabled="@bool/platformIsAtLeastL" android:exported="false" android:name="com.google.android.gms.nearby.exposurenotification.service.ExposureNotificationInternalService" android:process="@string/common_persistent_process" chimera:autoEnabled="@bool/platformIsAtLeastL" />
<service android:exported="true" android:name="com.google.android.gms.nearby.exposurenotification.WakeUpService" android:permission="com.google.android.gms.nearby.exposurenotification.EXPOSURE_CALLBACK" />
...