Strangely in the initial update prompt (which I don't have a screenshot of unfortunately, so if someone has an XT1092 and can corroborate it would be much appreciated) it says Android 6.0.1 and not security update, but the Android version remains at 6.0 and by all accounts remains 6.0. The new emoji aren't supported either. Back in Lollipop I also got an update that says Android 5.0.2 but the version stayed at 5.0 after the update. Anyways, this update is 15MB and takes around 20 minutes to install, contrary to what Motorola says.
Also, really Motorola? MAY?! I'd be expecting you to roll out the QuadRooter (August/September) patch by now.
Hi,
thnx for the info.
Any suggestions if anyone is making update zip for twrp installation?
Regards
LK82
Hi, it downloaded the 15Mb update when I came back home. Do I lose root if I update ?
YassGo said:
Hi, it downloaded the 15Mb update when I came back home. Do I lose root if I update ?
Click to expand...
Click to collapse
I think these official updates fail if you are rooted.... but if it succeeds i don't know if you retain root.
Again the RetGB variant being overlooked apparently. Spanish version got it and British version nothing...
Do anyone have some changelog for this security update? Does it fix Bluetooth issues (sometimes not routing audio via BT when connected to Nokia car kit)?
AB__CD said:
Strangely in the initial update prompt (which I don't have a screenshot of unfortunately, so if someone has an XT1092 and can corroborate it would be much appreciated) it says Android 6.0.1 and not security update, but the Android version remains at 6.0 and by all accounts remains 6.0.
Click to expand...
Click to collapse
I was surprised and exited that there was an update to 6.0.1 for my XT1092, which would fix the bluetooth BLE issue. No screenshot unfortunately, but I clearly remember it stating "6.0.1", not just a security upgrade.
I've contacted Motorola UK support though their email (sic) contact form with below message:
Hello
This weekend I got a prompt on my phone (model XT1092) to upgrade to android 6.0.1.
I was happy about this upgrade because it solves a bug that prevented me from using bluetooth tracking devices [1].
However, after the upgrade the android version mentioned in the phone settings is still 6.0 and not "6.0.1" as expected. The only change I notice is that the "security patch" level is now May 1 2016.
Please confirm which version is actually is and/or if the specific bluetooth low-energy fix mentioned in link [1] is included.
Thanks
Click to expand...
Click to collapse
[1] URL can't link to in this forum, but search for "tileapp 6.0.1" in google
No OTA when rooted.
My MOTOX is rooted and has TWRP, so no OTA possible.
Any chance of this upgrade being downloadable somewhere alreadY?
bart.cerneels said:
I was surprised and exited that there was an update to 6.0.1 for my XT1092, which would fix the bluetooth BLE issue. No screenshot unfortunately, but I clearly remember it stating "6.0.1", not just a security upgrade.
I've contacted Motorola UK support though their email (sic) contact form with below message:
Click to expand...
Click to collapse
I can confirm that notification says "New version: 24.201.3.en.EU" and "Android 6.0.1, Marshmallow".
OK, in OP there is a screenshot with 6.0 still. So no go for BT patch I think...
Screenshot Android 6.0.1 promt
They instead labeled this as the 6.0.1 update.
I tried to inform Motorola (lenovo) about it but it seems that it didn't came through, it was pretty hilarious:
Initial mail:
Subject: Software update labeled wrong
Dear Motorola,
This morning I received an software update saying that it would update my phone to Android 6.0.1 . This was not the case, it was merely the may security update (those are important to, don't get me wrong).
Response:
Dear Customer,
Thank you for contacting Motorola.
It is an official update form the Motorola end.So please update your device.
Me:
I did perform the update on my device, that was not my question/problem.
I meant to say that the update said it was 6.0.1 but it isn't. It updates the device to a new security patch, not form 6.0 to 6.0.1. This was probably not the intention (to say that it would update to 6.0.1) and I tried to attend you on this mistake.
Second response:
Dear Customer,
Thank you for contacting Motorola.
After updating the security patch update you will receive the official update of 6.0.1
And then I gave up on the matter, it would have been pointless to go on.
sgpieter said:
They instead labeled this as the 6.0.1 update.
I tried to inform Motorola (lenovo) about it but it seems that it didn't came through, it was pretty hilarious:
Initial mail:
Subject: Software update labeled wrong
Dear Motorola,
This morning I received an software update saying that it would update my phone to Android 6.0.1 . This was not the case, it was merely the may security update (those are important to, don't get me wrong).
Response:
Dear Customer,
Thank you for contacting Motorola.
It is an official update form the Motorola end.So please update your device.
Me:
I did perform the update on my device, that was not my question/problem.
I meant to say that the update said it was 6.0.1 but it isn't. It updates the device to a new security patch, not form 6.0 to 6.0.1. This was probably not the intention (to say that it would update to 6.0.1) and I tried to attend you on this mistake.
Second response:
Dear Customer,
Thank you for contacting Motorola.
After updating the security patch update you will receive the official update of 6.0.1
And then I gave up on the matter, it would have been pointless to go on.
Click to expand...
Click to collapse
Yeah, Motorola might just as well be Chinese now.
maybe this helps someone
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
4. Reboot into the bootloader, and then reflash stock recovery (download mentioned in step 1) with the command
"fastboot flash recovery 6.0_recovery.img"
5. Then reboot into recovery. From here, it will say "no command". Hold the power button and press the volume up key, then select apply patch from SD and choose the OTA you put on your internal memory. If all your system files are stock then this should run smoothly, if not, you might get a status error 7 and it will tell you which files are not stock. If you can, try to change them, but otherwise, you would need to download the stock files for 6.0 (you can also get them on the same link I suggested to get the stock recovery in step 1) and reflash everything to stock
Click to expand...
Click to collapse
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody
JonesMuc said:
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
4. Reboot into the bootloader, and then reflash stock recovery (download mentioned in step 1) with the command
"fastboot flash recovery 6.0_recovery.img"
5. Then reboot into recovery. From here, it will say "no command". Hold the power button and press the volume up key, then select apply patch from SD and choose the OTA you put on your internal memory. If all your system files are stock then this should run smoothly, if not, you might get a status error 7 and it will tell you which files are not stock. If you can, try to change them, but otherwise, you would need to download the stock files for 6.0 (you can also get them on the same link I suggested to get the stock recovery in step 1) and reflash everything to stock
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody
Click to expand...
Click to collapse
Hi, could you possibly upload the OTA file you downloaded? Could come in handy
Thnx in advance.
Cheers
Sent from my MOTO X using XDA Labs
As I'm new to this forum I cannot post links directly:
amazon.
de/clouddrive/share/dGQUmD6a5DvQrxlmSocfHr0Pm2XgIS9gBZ9b6lZAlla
(if the link is not working, you have to add https and www)
The file is called Blur_Version.24.11.18.victara_retde.retdeall.en.DE.zip so I think It's made for an update from 24.11.18 to 24.201.3
JonesMuc said:
As I'm new to this forum I cannot post links directly:
amazon.
de/clouddrive/share/dGQUmD6a5DvQrxlmSocfHr0Pm2XgIS9gBZ9b6lZAlla
(if the link is not working, you have to add https and www)
The file is called Blur_Version.24.11.18.victara_retde.retdeall.en.DE.zip so I think It's made for an update from 24.11.18 to 24.201.3
Click to expand...
Click to collapse
Thnx m8, really appreciated:good:
Cheers
Sent from my MOTO X using XDA Labs
JonesMuc said:
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody
Click to expand...
Click to collapse
May you tell the name of the post after searching "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1" ?
or some clues,
smthg plz ?
I suppose this is for rooting again
I'm looking for the stock recovery.img and the stock boot.img.
May you tell what to search to obtain them plz ?
Thx
You can find the recovery.img and boot.img in any stock firmware.
I used one from this site because it had the same version as mine:
androidsage.com/2016/02/09/install-official-marshmallow-ota-for-moto-x-android-6-0-ota-capture/
When you google for "blur_version.24.11.18" (or the version you need) you will find a lot of firmwares to download.
You are right, the other post is just for rooting again, after you updated
OK, thx :good:
Don't know why it took so long for you guys in Europe, but here in Brazil we've been using the may security patch since, errr... may! Hahahaha
theoblackhawk said:
Don't know why it took so long for you guys in Europe, but here in Brazil we've been using the may security patch since, errr... may! Hahahaha
Click to expand...
Click to collapse
One word: Lenovo
Actually four words: Lenovo being an ass
Related
Hello guys!
I've found the way for getting Android 4.4.4 rooted without write-protection on root filesystem
Original post on 4pda.ru Warning! Russian language detected!)
So, this is small and very simple instruction:
Preparation:1. You should be on SU2-3.3 (Blur 19.6.3) or SU2-3-15 (Blur 19.5.3) rooted and have SafeStrap installed!
2. You have never flashed SU4.21 (Blur 21.11.21) Android version 4.4.4 via RSDLite and you have never taken OTA with 4.4.4!!!
Let's do it and enjoy fully rooted 4.4.4!1 I've done 2 ZIP-files, download one, you prefer:
full rooted stock 4.4.4 SU4.21 with hosts-file ADBLOCK trick.
Download 4.4.4_full here
full rooted Debloated stock 4.4.4 SU4.21, with Touchless Control, Active Display, NFC, Wireless Monitor (inc. Cromecast)
Download 4.4.4_debloated here
Debloated ROM develompent was stopped, due to my smartphone physical damage. Im' sorry.
Regards, Dmitry.
2. Copy downloaded zip in to device storage.
3. Reboot to SafeStrap
4. Select Insall button, select ZIP, you prefer.
5. For locked bootloader: when installation will finish, reboot you device in to bootloader and flash stock kernel from SU4.21
you could take it here or from ZIP-file.
6. After flashing boot.img just reboot you smartphone and enjoy 4.4.4 with root and writable /system
For unlocked bootloader - all done, just reboot your device .
DO NOT PERFORM ANY WIPES!
If something happend with you phone, you can revert to SU2-3-15 (Blur 19.5.3) via RSDLite, get root, install SafeStrap
If you need to clean bloatware, use my Custom Recovery compatibility scripts, could be downloaded in this topic
If you found any features, you need, missing, please, pm me.
i am BL Unlocked, so no need for this for me... but if this is the case and it works then great find my man!!
Given the recent vulnerability published by Dan Rosenberg, I'm hesitant to update to 4.4.4, as it may patch this vulnerability - keeping the bootloader locked indefinitely. I would just keep this in mind if considering this update.
EDIT: Got my information wrong. The date on the OTA is before the date the vulnerability was published. 4.4.4. seems good to go in that case.
has anyone tried this yet?
Thinking about trying this - doing a backup now in Safestrap.
Would like to be able to see this...
"2. You have boot.img from SU4-21, you can download it below "
Where do you see this information? How do I know what version I have in 4.4?
rdenova said:
Thinking about trying this - doing a backup now in Safestrap.
Would like to be able to see this...
"2. You have boot.img from SU4-21, you can download it below "
Where do you see this information? How do I know what version I have in 4.4?
Click to expand...
Click to collapse
Settings>About Phone>Build number
summer.cat said:
1. You should be on SU2-3.3 rooted and have SafeStrap installed!
Click to expand...
Click to collapse
This, I see under Build Number.
summer.cat said:
2. You have boot.img from SU4-21, you can download it below
Click to expand...
Click to collapse
This, I do not see any place and is why I asked.
Wait so is this a fully write protection off?
mrwinkle said:
has anyone tried this yet?
Click to expand...
Click to collapse
Looks like this fella did...
http://forum.xda-developers.com/droid-ultra/general/update-19-5-3-obake-t2845903
ceelos218 said:
Wait so is this a fully write protection off?
Click to expand...
Click to collapse
sertainly)
PS: i've read many questions about build versions and firmware versions, so if you couldn't understand which firmware you have, follow this:
First update 4.4 - SU2.3-15 (suits for gaining root and wp off by @beaups wbegone)
Second update 4.4 - SU2.3-3
Latest update 4.4.4 - SU4.21
hope, it will be helpfull.
summer.cat said:
sertainly)
PS: i've read many questions about build versions and firmware versions, so if you couldn't understand which firmware you have, follow this:
First update 4.4 - SU2.3-15 (suits for gaining root and wp off by @beaups wbegone)
Second update 4.4 - SU2.3-3
Latest update 4.4.4 - SU4.21
hope, it will be helpfull.
Click to expand...
Click to collapse
Instead of using the SU for identifying builds, you should probably the system version number as that is more frequently used. 19.5.3, 19.6.3, 21.11.21
summer.cat said:
Hello guys!
I've found the way for getting Android 4.4.4 rooted without write-protection on root filesystem
Original post on 4pda.ru Warning! Russian language detected!)
So, this is small and very simple instruction:
Preparation:
1. You should be on SU2-3.3 rooted and have SafeStrap installed!
You have never flashed 4.4.4 via RSDLite and you have never taken OTA with 4.4.4!!!
2. You have downloaded boot.img from SU4-21
can be downloaded here https://drive.google.com/file/d/0B_kAWkXp3XK9VmpnSGNaVUZtTDQ/edit?usp=sharing
Let's do it!
1. Download 4.4.4_rooted.zip here
https://drive.google.com/file/d/0B_kAWkXp3XK9amVwNjJKUjk4QmM/edit?usp=sharing
2. Copy 4.4.4_rooted.zip in to device storage.
3. Reboot to SafeStrap
4. Select Insall button, select 4.4.4_rooted.zip
5. After flashing reboot to bootloader and flash via fastboot tools boot.img file from point 2 above
Code:
fastboot flash boot boot.img
6. Reboot after flashing boot.img
7. Enjoy 4.4.4 with root and writable /system
If something happend with you phone, you can revert to SU2-3.15 via RSDLite, get root, install SafeStrap
PS: You flashing clean from bloatware system! As clean as possible, but everything works fine!
Click to expand...
Click to collapse
....So, does this mean I can finally install some ROMs on my retail Moto? I came from a bootloader-locked 4.4 install with root.
thebenshow said:
....So, does this mean I can finally install some ROMs on my retail Moto? I came from a bootloader-locked 4.4 install with root.
Click to expand...
Click to collapse
i mean, you can use 4.4.4 without write protection
I'm about to try this out to n my xt1080 on 4.4.4... I will update when I'm finished
Can this be used for the droid mini?
I should have read closer I got too excited about about getting root... I already took 4.4.4 OTA... I need root
Am I the only one waiting for clear confirmation from someone who was rooted on 19.6.3 that did the steps in this thread that they are now on 4.4.4 with root and write protection permanently off?
BriCo84 said:
Am I the only one waiting for clear confirmation from someone who was rooted on 19.6.3 that did the steps in this thread that they are now on 4.4.4 with root and write protection permanently off?
Click to expand...
Click to collapse
I am too lol. Been refreshing this thread ever since I ran across it.
Anyone try this?
He is talking about using safestrap on a 4.4 ROM. If you EVER updated to 4.4.4, this will never work for you as you will never be able to disable write-protect to be able to install safestrap.
OP: perhaps you should make this more clear in the original post. Specifically that it will not work if you ever updated to 4.4.4 (Actually, the OP DOES say this...), AND that you're not actually running the 4.4.4 rom, but rather a 4.4.4 stock-based, safestrap-compatible ROM. If you are using this successfully, your bootloader AND your partition table are still on 4.4, which allows you to retain WP-off, safestrap, and root.
But yeah...this will absolutely work if you never updated past 4.4. We have known about this for a long time...I'm surprised a guide was just recently put out about this.
I just got the new OTA for Lolipop 5.0.1. I used ADB to pull the URL for the download and downloaded the attached ZIP using my browser. The URL pulled from ADB was an extremely long randomized string of characters that expired the moment my device was done updating. It seems the link is only active during the update process, so the only way to leave the link active longer is to battery pull or something in the middle of the update. I love you guys... but not that much
Keep in mind that this OTA was offered to me on 22.21.16, so I am assuming that you probably need to be on that update before you can use this OTA.
Let me know if you guys have any questions or run into any issues!
I'm rooted and running TWRP on my XT1064 with 22.21.16. Is there a way to just fastboot flash this update? I don't mind losing root. Thanks!
Okay, I had upgraded to 22.21.16 via TWRP using KennyWuLee's packaged tool. This morning I received a notice that I had an update available for 22.21.25. So like a dummy I went ahead and accepted. Now all it does is boot into TWRP. When I restart to system from TWRP it boots up just fine then after about 15 seconds reboots to TWRP.
I assume it is looking for the stock recovery which will then allow me to install the update? So will I be safe to go ahead and reflash the stock recovery, reboot and go from there? Or should I go all the way back to stock everything?
I have an XT1063.
Edit: I went ahead and flashed stock recovery and rebooted. After boot looping several times it rebooted into the system and gave me the message "Software update unsuccessful. There was a problem ....blah, blah, blah." But I still show an update available when I check.
I suspect it is because I am unlocked and rooted, even though I have stock recovery installed. Any thoughts on this guys? I am going to hold fast until I know for sure.
The update failed because you were rooted. You need a 100% stock /system since updates after 5.0 check the integrity of the filesystem before updating.
I may sound like a noob, but just to be sure..
Name of update says ".en.us".
Is it ok to use it for a french moto G 2d generation?
French will be available?
Thanks!!
DoubleIk said:
I may sound like a noob, but just to be sure..
Name of update says ".en.us".
Is it ok to use it for a french moto G 2d generation?
French will be available?
Thanks!!
Click to expand...
Click to collapse
Not sure if it makes a difference or not. I just put what the build was listed as when I got the update notification.
I put that there in case that was why some people couldn't update from 22.21.6 to 22.21.16
shishir95 said:
The update failed because you were rooted. You need a 100% stock /system since updates after 5.0 check the integrity of the filesystem before updating.
Click to expand...
Click to collapse
Nice theory, but I am now totally restored back to stock with stock recovery and unrooted. Still no luck with the update. Same thing happens.
I'm still stuck on 22.11.6, so I'm assuming I can't install this update until I'm on 22.21.16?
thisisjason said:
I'm still stuck on 22.11.6, so I'm assuming I can't install this update until I'm on 22.21.16?
Click to expand...
Click to collapse
From what I've seen, that is correct.
Any news XT1068 android 5.0.1 #India?
Moto G 2014 5.0.1
Hello good day friends will have some manual to perform the installation ?? and try it for apply update from ADB and I mark error in sideload package , installation aborted
How do I can install this update?
By now, with all the OTA's, unless you are brand new to the 2013 X, you know you have to have stock recovery on your phone for an OTA Update or Soak Test to install, and your system can't be modified too much or it will fail the pre-flash validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
If you have an unlocked bootloader, and rooted by flashing a 3rd party recovery (like TWRP, CWM, Philz, etc) and installing SuperSU, you likely didn't put stock recovery back on your phone.
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
The steps in this post help you do that, or get ready to do that, in case you are not near your PC when an OTA comes, of if you just don't want to use your PC.
NOTE: If you have changed too much of stock that the OTA fails, please see -> [FAQ] How to prepare for and take an OTA update (All Carriers)
NOTE: the following worked when updating 4.4 to 4.4.2, and 4.4.2 to 4.4.4 on my VZW Dev Edition X. Since Lollipop has not yet been released for my phone, I can't test this yet.
Note: If you have flashed your phone with another carrier's ROM, or have only flashed "parts" of your phone, these steps may not work!! Or they may cause you to brick!
NOTE: If your Bootloader version does NOT match the one for your phone's software version, taking an OTA could brick your phone!
You must have an Unlocked Bootloader and be rooted for these steps to work:
Obtain the STOCK Moto Recovery image, and TWRP image, for your phone:
On you phone, go App Drawer -> Settings... Make note of what is listed under System Version, and Android Version.
Visit one of the sites listed in -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347 and obtain the EXACT same ROM/SBF file that is currently on your phone. Download the ZIP to your PC.
Unzip or extract the RECOVERY.IMG file from the SBF ZIP file.
Download the latest TWRP Recovery from -> http://teamw.in/project/twrp2/234 (under the Download-Fastboot heading)
the latest SuperSU from -> http://download.chainfire.eu/supersu or the latest CWM / TWRP / MobileODIN installable ZIP from http://forum.xda-developers.com/showthread.php?t=1538053
Flashing Recovery
Place your stock recovery.img, the latest TWRP img, and the latest SuperSU.zip in your phone's DOWNLOAD folder.
Install Rashr.
On your phone, launch Rashr.
Scroll down and select other from storage
Browse and select your stock recovery
When it completes, pick the option to reboot to stock recovery.
Your device should reboot and display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key. You should be in Stock recovery now.
Reboot your phone as normal.
To reflash TWRP or other custom recovery, as long as you are still rooted, you can repeat the same steps, selecting your custom recovery in step 5.
How to SIDE LOAD an OTA.ZIP via this process
If your carrier has started the push of the OTA ZIP for your phone, but you haven't received it, and you've found the correct OTA ZIP posted online and would like to flash it, the following steps can be used...
Download the OTA ZIP file (usually named as BLUR_XXX.XXX.XXX.zip, where XXX.XXX.XXX is the build number the ZIP will update) to your phone's /SDCard
Perform steps 1-7 under Flashing Recovery above to flash STOCK recovery onto your phone, and reboot into Stock Recovery.
Use the Vol Down key to scroll to Apply Update From SDCard, and press the Power key to select.
Use Vol Down key to scroll to your OTA zip file, and press Power to select.
The install will begin by verifying the update package, then verifying files on your phone match.
If the install fails, it will be reported on the screen, along with why. (usually because you have modified system files, or are not on the correct ROM version). You need to fix these errors and try again.
If verifications are successful, the patching process steps will begin. This may take several minutes.
Your phone should report Script Succeeded and Install from sdcard Complete.
Ensure Reboot System Now is highlighted, and press the Power key to reboot the phone.
The initial reboot may take longer than a regular reboot.
Note: You will see Android Is Upgrading or Optimizing screen during the boot process, that is normal.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
How to Root with unlocked bootloader...
If you unlocked your bootload by getting the code from Moto, after taking the OTA you may root by following ->http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 NOTE: while the thread is titled for 5.1, it works on older Android versions as well.
Good work KidJoe :laugh::good:
I guess this will be more relevant as Soaks start heading out for the 2013 X...
Good post. Can I use the same process on MotoX 2014 pure? I have turned Moto OTA to get rid of constant "update available" notification, if I turn that back on, do you know where the OTA zip file is downloaded (i'm thinking cache )
ks73417 said:
Good post. Can I use the same process on MotoX 2014 pure? I have turned Moto OTA to get rid of constant "update available" notification, if I turn that back on, do you know where the OTA zip file is downloaded (i'm thinking cache )
Click to expand...
Click to collapse
Yes, the OTA zip is usually stored in /cache (at least is is on the 2013 X, and my past Moto phones). it is usually named for the rom it is upgrading, not what the upgrade takes you to.
I don't see why this wont work on the 2014 X, as it did on older motos too.
Brother i got Motorola updates services update today. I will try your method once there will be available ota. And can you tell me how to backup my whole rom?
Sent from my XT1052 using XDA Free mobile app
ajsonofgod said:
Brother i got Motorola updates services update today. I will try your method once there will be available ota. And can you tell me how to backup my whole rom?
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
In TWRP you can make a nandroid backup. I've never done it. I haven't had need because I run stock. If I need to reflash, I just reflash the same SBF I've been running.
I followed the instructions in the OP to return to stock recovery, then applied the OTA update Blur_Version.213.44.1.ghost_row.Retail.en.US, but am failing with this message
/system/etc/install-recovery.sh has unexpected contents
I haven't knowingly modified any system files, although I am rooted. Any thoughts about what this error might mean and how to resolve it?
ejlmd said:
I followed the instructions in the OP to return to stock recovery, then applied the OTA update Blur_Version.213.44.1.ghost_row.Retail.en.US, but am failing with this message
/system/etc/install-recovery.sh has unexpected contents
I haven't knowingly modified any system files, although I am rooted. Any thoughts about what this error might mean and how to resolve it?
Click to expand...
Click to collapse
What ROM is on you phone to start with? On your phone go App Drawer -> Settings -> About.. tell me the Android Version, System Version and Build Number. Also what model X do you have?
213.44.1.ghost_row.Retail.en.US is an XT1053 4.4.4 update file for the XT1053 if I'm not mistaken. It is meant to be applied to a 4.4.3 stock rom, and it might apply to a 4.4.2 stock rom..
The OTA file will fail its pre-flash validation checks if you are not on the intended stock rom.
KidJoe said:
What ROM is on you phone to start with? On your phone go App Drawer -> Settings -> About.. tell me the Android Version, System Version and Build Number. Also what model X do you have?
213.44.1.ghost_row.Retail.en.US is an XT1053 4.4.4 update file for the XT1053 if I'm not mistaken. It is meant to be applied to a 4.4.3 stock rom, and it might apply to a 4.4.2 stock rom..
The OTA file will fail its pre-flash validation checks if you are not on the intended stock rom.
Click to expand...
Click to collapse
Thank you. I'm embarrassed that I didn't perform sufficient due diligence. I am already on the same system version as the update (213.44.1.ghost_row.Retail.en.US ), which I mistakenly thought was to get to Lollipop from 4.4.4.
there any way to make a dump the stock recovery in Lollipop, without the need root?
ejlmd said:
Thank you. I'm embarrassed that I didn't perform sufficient due diligence. I am already on the same system version as the update (213.44.1.ghost_row.Retail.en.US ), which I mistakenly thought was to get to Lollipop from 4.4.4.
Click to expand...
Click to collapse
Yeah, OTA Update files are often named including the version the phone must be on, not the version it takes the phone to.
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
ks73417 said:
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
Click to expand...
Click to collapse
It's ABSOLUTELY BEST you avoid the update............but....
If you can't, it is highly recommended that you clean flash it...kind of the only choice. Flash the 4.4.4 Brazilian stock ROM. And install the update from recovery. You can reroot after adding TWRP back.
I am also on stock rom 4.4.4. But i dont have this rom on my pc for reflashing. Please provide link for download or some info related to it
Sent from my XT1052 using XDA Free mobile app
ajsonofgod said:
I am also on stock rom 4.4.4. But i dont have this rom on my pc for reflashing. Please provide link for download or some info related to it
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Please see the LINK in my signature for sites to download stock SBF files
ks73417 said:
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
Click to expand...
Click to collapse
As explained elsewhere... Xposed makes changes to /system which cause OTA updates to fail their pre-flash validation checks.
It is recommended to boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip then uninstall XPosed.
You will also need to undo any changes to /system or other parts the the OTA tries to validate before installing, or else it will fail.
You are correct that a newer version of Xposed is needed.
You may also want to wait on trying the 5.0.2 Leaks because if they are an early limited early test version, rather than a soak which is nearly ready to be pushed to all, you could be stuck on this version until an SBF leaks.
Update
Does anyone know how to return to stock recovery for lollipop? New update came up today but I have TWRP.
upload the stock recovery lollipop please!!!!
Good work, love your detailed explanations always .
Update : Oct 24, 2015 It looks like the bricking scare is over, and there is an updated guide on how to upgrade to the latest Lollipop without bricking :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
PUBLIC SERVICE ANNOUNCEMENT :
There are now several reports of super hard bricks (not even Amazon logo shows up) when people attempted to load 5.2.2 version via TWRP.
My best guess is that it has something to do with the 5.x update from Amazon that people request before downgrading to 4.5.3. If Amazon is providing a newer 5.x. update, it can be blocking the older 5.2.2 from working after the downgrade-upgrade procedure. When it bricked before, it would at least show "Amazon" logo, but now even the logo is gone.
One would have to capture this current 5.x update, and see what's in it. It's probably updating another partition out of those that were previously untouched :
http://forum.xda-developers.com/fire...idden-t3122246
All the downgrade-upgrade guides are on hold for now ... You are still safe to exist in the 4.5.x space (with root).
bibikalka said:
One would have to capture this current 5.x update, and see what's in it.
Click to expand...
Click to collapse
I assume I can capture file by reversing rename of DeviceSoftwareOTA.apk but leaving OTA updating blocked. Is that the method?
EDIT: Well, just did rename. No download yet. I've got otaverifier blocked. If nothing soon, I'll enable that and block dcp.
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
siegesoldier said:
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
Click to expand...
Click to collapse
All that downloaded for me were apk update files, no .data, but device>updates shows:
10.0.42-D-20150925-NA-4 is ready to install
I ran logcat during download and a couple of manual installs (pressing Install button, but I do have updates blocked). I didn't see anything obviously related to update in the logcats, but not sure what to look for. Since I didn't get the .data, will I find anything helpful in logcat? What should I look for? thx
p.s., Or must I unblock updating to capture?
siegesoldier said:
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
Click to expand...
Click to collapse
Yep, this is weird. I wonder if one should flash 4.5.3 bootloaders with TWRP in Lollipop first as per this post http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2 , and let it try to upgrade. This way whatever files it downloads, they will be sitting in /cache. But nothing will be run as it is a non-Amazon recovery.
Another poster indicated that the tablet rebooted about 3 times, and then he got new icons and Amazon launcher :
http://forum.xda-developers.com/showpost.php?p=63116048&postcount=141
bibikalka said:
I wonder if one should flash 4.5.3 bootloaders with TWRP in Lollipop first as per this post http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2 , and let it try to upgrade. This way whatever files it downloads, they will be sitting in /cache. But nothing will be run as it is a non-Amazon recovery.
Click to expand...
Click to collapse
I'm more than willing to try to capture this if one of you can tell me how.
I don't quite follow the above. I'm running rooted 5.2.2. So I'd flash bootloaders and TWRP per guide, install OS 4.5.5, boot to OS and try to upgrade? Is this any different from someone already on 4.5.5 trying to upgrade? thx
DoLooper said:
I'm more than willing to try to capture this if one of you can tell me how.
I don't quite follow the above. I'm running rooted 5.2.2. So I'd flash bootloaders and TWRP per guide, install OS 4.5.5, boot to OS and try to upgrade? Is this any different from someone already on 4.5.5 trying to upgrade? thx
Click to expand...
Click to collapse
Not this complicated. I think you could flash 4.5.3 bootloaders + TWRP under 5.2.2, enable OTA updates, and continue working. When it decides to self-reboot (after the update is copied to /cache), it won't find stock 5.2 recovery. Instead, it'll hang (4.5.3 bootloaders cannot boot 5.2.2). At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
bibikalka said:
Not this complicated. I think you could flash 4.5.3 bootloaders + TWRP under 5.2.2, enable OTA updates, and continue working. When it decides to self-reboot (after the update is copied to /cache), it won't find stock 5.2 recovery. Instead, it'll hang (4.5.3 bootloaders cannot boot 5.2.2). At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
Click to expand...
Click to collapse
OK, I'll try this later or tomorrow. Still wonder though, couldn't you--anyone on 4.5.5--leave OTA package blocked but rename OTAsoftware extension back to apk, allowing the update to download but not install?
)':
Hello, I am french sorry for my english
My kindle fire is bricked
how to repair !! :crying::crying:
help me please :/
bibikalka said:
. . . At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
Click to expand...
Click to collapse
@bibikalka OK, ready to do this and (more or less) prepared to get replacement Fire . Just one question: Why do you think there will be anything in cache after the update and reboot attempt? i.e., wouldn't deleting it be part of the update process? Thanks! (Edit: NVM--I see your explanation above.)
EDIT @bibikalka, @everyone Thought the update was out for my region, but guess not: With DeviceSoftareOTA.apk named as originally and otaverifier enabled, Device>Updates just returns "no updates." Disabled otaverifier again and will wait on this.
I believe the update will download with DeviceSoftwareOTA.apk properly named--and hope it won't update with otaverifier disabled. So maybe I can get it. Anyway, I'll check for it over next few days, but maybe someone else will try this method first. (I am west-coast US and it seems always last to get updates.)
DoLooper said:
@bibikalka OK, ready to do this and (more or less) prepared to get replacement Fire . Just one question: Why do you think there will be anything in cache after the update and reboot attempt? i.e., wouldn't deleting it be part of the update process? Thanks!
Click to expand...
Click to collapse
I think it will prepare to update by staging the required files in /cache, but then it'll try to reboot to apply those files (usually updates are applied in recovery ...). So when reboot fails (as it should with TWRP & 4.5.3 bootloaders which don't boot Lollipop), you intercept the stuff in /cache and see what it has.
Added: If this works, do wipe /cache before leaving TWRP (when you restore 5.2 bootloaders). This way it won't pick up the scripts and run them ...
See edit here. Forgot that I'm always last to get an upgrade. Hope someone who might get it sooner will use bibkalka's method so we can get this show back on the road.
After downloading the 5.0.1 update once I have been unable to get it again. My build number has not updated so its possible they pulled it. Root etc still works so it doesn't look like it applied.
Hello, just wanted to say that I can testify to the fact that after updating to 5.2.2, then downgrading and going into TWRP, flashing all the zips, and then wiping cache before rebooting..... gets you a BRICK!! I've stupidly done it.... to my replacement from Amazon! Hopefully sometime in the future someone can get me out of this one....
hello there recently my rooted fire os 5 with xposed playstore just updated to 5.0.1 by it self and i swear i did have com.amazonotaverifier blocked its weird because it updated when i left my fire hd 6 on charge
it just updated itself to fire os 5.0.1 il stay on that fire os because people are saying you get bricked if you do the whole procedure like downgrade back to 4.5.3 and root and get custom recovery and flash all the zips = brick
2nd try to get 5.0.1 update
I didn't capture the update, but maybe learned something about OTA. Two things I hope someone can explain.
First, I've had extension of DeviceSoftwareOTA.apk renamed back to (plain) .apk since last attempt to capture update. Today:
1. "Check for updates" returned: 10.0.43.-D-20151007-NA-5 is ready to install
(last week there was one named: 10.0.42-D-20150925-NA-4)
2. I dd'd the 4.5.3 bootloaders and twrp (with otaverifier blocked)
3. Unblocked otaverifier, but the only thing that downloaded to /cache was "amazonmp3_10004310.apk" (update to mp3 player, i guess).
(last week they were apks for map and photo apps)
4. Hit "check for updates" again, but now it said "none" and /cache was empty.
(same thing last week)
Does anyone know about updates named like "10.0.43.-D-20151007-NA-5?" I've only seen them since I "corrected" the deviceSoftwareOTA.apk extension, and only apk files get downloaded. A couple logcats I got, however, have many more update entries than I've seen before, but I don't understand logcats very well. If someone who knows logcats could have a look, I'd appreciate it. Just tell me where to post. I think it would help us to know if these updates do more than update the accompanying apks.
------------------------
EDIT: NVM below! I'm getting # prompt because I recently set "adbd insecure" app to start at boot <doh> .
Second, I decided to start over and see if there was a different update waiting. So:
1. Went to twrp and flashed 5.2.0_stock_recovery_uboot.zip (for 5.0 stock recovery and bootloaders, i hope), wiped cache, and booted to OS.
2. Got l o o o n g startup. When OS finally loaded, "adb shell" hung CMD. I had to run TASKKILL /F /IM adb* >nul 2>&1 before adb shell was recognized. And when it was, it consistently returned # prompt: ([email protected]:/ #)
I'm definitely rooted, all google works, version still shows 5.0.0, build date July 20, but even after rebooting both tablet and computer, "adb shell" still always returns # prompt.
Can anyone tell me what's going on here? (Sorry this is tldr; hope a few of you slog through.) Thanks.
EDIT: it's late, maybe I'm nuts, but seems "adb shell" should return $ prompt, then "su" returns #.
DoLooper said:
I didn't capture the update, but maybe learned something about OTA. Two things I hope someone can explain.
First, I've had extension of DeviceSoftwareOTA.apk renamed back to (plain) .apk since last attempt to capture update. Today:
1. "Check for updates" returned: 10.0.43.-D-20151007-NA-5 is ready to install
(last week there was one named: 10.0.42-D-20150925-NA-4)
2. I dd'd the 4.5.3 bootloaders and twrp (with otaverifier blocked)
3. Unblocked otaverifier, but the only thing that downloaded to /cache was "amazonmp3_10004310.apk" (update to mp3 player, i guess).
(last week they were apks for map and photo apps)
4. Hit "check for updates" again, but now it said "none" and /cache was empty.
(same thing last week)
Does anyone know about updates named like "10.0.43.-D-20151007-NA-5?" I've only seen them since I "corrected" the deviceSoftwareOTA.apk extension, and only apk files get downloaded. A couple logcats I got, however, have many more update entries than I've seen before, but I don't understand logcats very well. If someone who knows logcats could have a look, I'd appreciate it. Just tell me where to post. I think it would help us to know if these updates do more than update the accompanying apks.
.
Click to expand...
Click to collapse
These updates appear to be just individual apps, nothing to do with the system. You can google the version numbers, and it'll find that stuff.
The only hope is to checksum all partitions, and find the one that was updated in the latest version 5, but otherwise does not change in earlier versions. One could right a script for that. Then we could overwrite it.
But I suspect the new update may have written into one of the partitions that have other stuff, so the checksum identification won't help.
bibikalka said:
The only hope is to checksum all partitions, and find the one that was updated in the latest version 5, but otherwise does not change in earlier versions. One could right a script for that. Then we could overwrite it.
But I suspect the new update may have written into one of the partitions that have other stuff, so the checksum identification won't help.
Click to expand...
Click to collapse
Would that mean 5.0.1 would not be rootable?
Hello, I am curious, would it be possible to use "fastboot boot recovery.img" instead of actually flashing it in order to get root in the new 5.2.2 (build date sep 23)? It seems this would solve the hard brick problem with flashing twrp.
I'm on a never-rooted 2014 HD6 with gapps & OS 5.2.2. Very interested in rooting this tablet.
hi,
my Eng is not good, i don't understand the title
Stop !!! Do not upgrade to lollipop via twrp !!!
on today i'm receive Fire HD 7 from my phone provider. This is free.
i was rooted it with kingroot. It was succesfull. But i want setup it with android with vietnames because my boy are 10 age.
it run fire os 4.5.3 now.
can i upgrade to android 5.x?
thank for read
ASUS ZenFone 2=ZE551ML(Z00AD/Z00ADA/Z00ADB/Z00ADC) software Image: V4.21.40.223 for WW SKU only* (andriod M)
Improvement Item:
1)Improve Wi-Fi/Bluetooth stability
2)Update Security patch
3)Improve system stability
4)Support India SOS call (India only)
Full Rom Download Link: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-4.21.40.223-user.zip
Hi,
How to install it on a rooted ZE551ML ?
When checking for OTA, it is not purposing the update for the moment.
Thanks
fredlamour said:
Hi,
How to install it on a rooted ZE551ML ?
When checking for OTA, it is not purposing the update for the moment.
Thanks
Click to expand...
Click to collapse
It is, but not if your bootloader is unlocked.
Rodepo said:
It is, but not if your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks.
bootloader unlocked so no way.
I am thinking about jumping into a lineage rom.
VoLte support?? in this new update....
I felt like this was happening today! came in and here it is. Updating right now.
Thanks
any update for this update of asus zenfone 2
optimumgiant said:
any update for this update of asus zenfone 2
Click to expand...
Click to collapse
Hello. This forum is for galaxy 8.07. We don't know about zendroid 2 or whatever you ask.
Just joking. This IS for zenfone 2.
I'm currently using the update. Screen flickering has stopped for the time being.
i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance
crownpiyush said:
i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance
Click to expand...
Click to collapse
it seems you are first. Give it a try and find it out for yourself and let us know!
crownpiyush said:
i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance
Click to expand...
Click to collapse
My way is unroot and uninstall Xposed first, than sideload the whole rom with stock recovery.
I had failed to OTA many times because I modified some system files (forgot to restore them), so now I just reflash rom to save the trouble.
Wifi auto-connect problem seems fixed and the phone has more available ram after "power and boost".
It's worth to update imo.
Battery life seems the same
All sensors working with this version in my brazilian zenfone 2 z00a.
Running this for last two days so far , yup Wi-Fi connects quicker , graphics seem sharper round the web and there's the security patch .
To update ..
Coming from .184 rooted and twrp.
Full unroot first.
Then used the modder tool , to "return back to stock " option. Select boot.img then recovery.img, remember it flashes .134 .img's and I was coming from .184 to begin with.
Then boot to stock recovery .
Scroll to update from adb. Then adb cmd >
adb sideload MOFD_SDUPDATE.zip
Remembering to put the new firmware in adb/fastboot folder first and changing the file name to MOFD_SDUPDATE before sideloading.
Will give it a few more days then will try to use the modder tool to get back to lineage os and back up the new firmware.
I was on rooted .184 and twrp. I booted into fastboot, flashed recovery, booted to recovery, and updated from SD card. After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit
audit13 said:
After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit
Click to expand...
Click to collapse
I had unlocked the BL before so i updated and directly tried regaining root and xposed but failed (softbrick at asus loading screen), I confirm that applying the whole ota from sideload sort of relocks the bootloader and you must do it again, now it is booting and rebuilding the dalvik cache.
audit13 said:
I was on rooted .184 and twrp. I booted into fastboot, flashed recovery, booted to recovery, and updated from SD card. After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit
Click to expand...
Click to collapse
In conclusion you did only flashed stock recovery and, from that, you flashed the whole zip in the first post, right?
Inviato dal mio ASUS_Z00AD utilizzando Tapatalk
timbernot said:
Running this for last two days so far , yup Wi-Fi connects quicker , graphics seem sharper round the web and there's the security patch .
To update ..
Coming from .184 rooted and twrp.
Full unroot first.
Then used the modder tool , to "return back to stock " option. Select boot.img then recovery.img, remember it flashes .134 .img's and I was coming from .184 to begin with.
Then boot to stock recovery .
Scroll to update from adb. Then adb cmd >
adb sideload MOFD_SDUPDATE.zip
Remembering to put the new firmware in adb/fastboot folder first and changing the file name to MOFD_SDUPDATE before sideloading.
Will give it a few more days then will try to use the modder tool to get back to lineage os and back up the new firmware.
Click to expand...
Click to collapse
Running this update since it came out 5hrs SOT over a 26hr period seems very good :good:
Still on stock no mods apart from using firefox browser with adblock .
Good to know too .... official downgrade version of LP WW-52.20.40.196 firmware is on my ext SD card and i still get notification for this downgrade update OTA after a reboot on this WW-4.21.40.223(andriod M) latest firmware
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
timbernot said:
Running this update since it came out 5hrs SOT over a 26hr period seems very good :good:
Still on stock no mods apart from using firefox browser with adblock .
Good to know too .... official downgrade version of LP WW-52.20.40.196 firmware is on my ext SD card and i still get notification for this downgrade update OTA after a reboot on this WW-4.21.40.223(andriod M) latest firmware
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
Click to expand...
Click to collapse
can you please share your adblock app with us.
thanks
crownpiyush said:
can you please share your adblock app with us.
thanks
Click to expand...
Click to collapse
its a add-on downloaded and installed from ` tools ` in firefox browser settings :good:
ps, i had trouble using adblockplus add-on from firefox ,when viewing XDA pages ..they turned out blank , XDA i think prevented the use of such adblock , so now i use the less blocking add-on in firefox called `uBlock`
its good enough