Related
[me176c/x] [K013] How to Root and update from .182 to Lollipop release
Stock ROMs up to v.182, all languages
ASUS' Download Center for the MeMo Pad 7 Link is now inaccessible as ASUS has redesigned their site. Even the support page for this tablet no longer has any links to download ROMs/updates. Sad panda. However, the ones below (ASUS' direct links included) still work! I am also in the process of reuploading/rehosting all of these as well, so stay tuned! So far everything is rehosted on Google Drive, and I plan to add more mirrors in the next couple of days. Pleasse bear with my snarkiness, I have been up late and it's now 4am. I must crash now.
Anyway........ Enjoy!!
WW 182 Full ROM
ASUS
Google Drive
WW OTA 191
ASUS
Google Drive
Google Drive (alt)
WW OTA 198
Google Drive
WW OTA 199
Mediafire
Google Drive
WW OTA 201
Google Drive
Zippyshare (ew)
WW Lollipop release
Mediafire
Google Drive
If you have other links to share, especially direct links from ASUS or non-GDrive hosts, please feel free to post them and I will credit you!
(Manually) Flashing Updates
Sometimes (read: often) an update will fail to install and reboot, and then the tablet will claim you're up to date when you check for updates (and we know it's full of crap). So you'll have to manually update yourself, and often, if only works if you start from .182 (or above), and flash each file in consecutive order. So here's how it works. Be sure to read over this before starting, to get an idea of what's in store for you. And to be safe, read it again. And to be doubly-sure, read it AGAIN (I cannot stress this enough).
Obligatory warnings:
Your warranty (expired by now, for sure) is now null and void. Regardless of whether you do this, it's no longer valid either way! :laugh:
I am not liable for any damages to your device (or your brain) that this process may cause. What you do to your device is on you, but if you play it safe and read this all carefully (and read it again! And AGAIN!), you shouldn't have any trouble.
Instructions:
First things first, install your drivers if you haven't already, and set up the Android Platform Tools (adb and fastboot exes and such, also attached to this OP). I highly suggest trying the Latest ADB Fastboot and USB Driver installer tool for Windows by @fawazahmed0 (or the various attached drivers below, if you still somehow have trouble with getting your PC to recognize this dinosaur of a device).
Next, before we continue, make sure USB debugging is enabled on your tablet. Go to Settings > About tablet, and tap on Build Number 7 times, and you'll see a toast, "You are now a developer!" Back out once and scroll down a bit, you'll now see Developer Options. Enter, and near the top you'll see an option for USB debugging, so check that box. Plug in your tablet to the PC, then open a command line interface (Hit Windows Key + R, then type in "cmd" and press enter). Type in "adb devices" (without quotes) and look at your tablet's screen for a prompt. Check the box and tap OK. Now. back in the command prompt, press up and enter on your keyboard (which will repeat that last command), and you'll see your tablet's serial number (a string of letters/numbers) and the word "device" if you did it correctly. Now you're ready for the next part.
1. Install the "RootZenFone-1.4.6.8r.apk" (attached to this OP, below) and run it. Beware, it may have some Chinese text/Engrish. It's fairly simple to figure out though, thankfully.
2. Turn on USB debugging if you haven't already (didn't you read this first? You're already slacking!).
3. Download the zip file(s) you need and rename it update.zip and transfer it to your tablet. Or copy all files to the tablet and rename them (with a file manager of your choice, see next step) as you go.
4. Download a file manager that has root access (such as MiXplorer or Root Browser).
5. Go to / (root) and manually copy your update.zip to the /data folder.
6. Download this command file (also attached below, in a zip) and copy it to the /cache/recovery folder. This must be present each time you install an update via this method, so leave a copy on your device.
7. Back to Windows Command Prompt, run the command, "adb shell" (without quotes, as before), wait a moment for it to reload the server, then type, "su" (again, without quotes). When you type in the "su" command for the first time, it will prompt for SuperSU access on your tablet, similar to how it requested the RSA perms with adb debugging. You must allow this root permission, or the following won't work!Now, type line by line (or better yet, copy and paste into the command prompt (a right click automatically pastes copied text into it, btw):
Code:
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
In brief, what this means is that you just ordered the "command" file to boot as a "recovery" in order to flash the update package you copied and renamed previously. Thus, the tablet will reboot and commence flashing. At least, I think that's what's happening here. Sorry, I'm no rocket surgeon. All I know, is that it works. However, if you are getting an error during the update process, as mentioned above, you will likely have to flash the next incremental update (the one just above your current version) instead and go from there, flashing each OTA in order using the coded commands above every time. Be sure to rename EACH ZIP to "update.zip" as you do this or the command cannot find the file! Yes, this sounds like a pain, and it is! But this has worked when the direct approach had failed.
Archive folder of everything needed, on Google Drive
ROOT ZenFone FAQ has a translated guide on how to fix ptotential issues with the root process.
Credits:
@plopingo and @jerbear294 for some of the links.
@lethardicus for finding most of the OTA zips again when one weirdly went missing @fawazahmed0 for the driver installer tool
@slayeralive for providing the basis for these instructions
Nice work sub
No need for adb just copy zip ti /data and command file to /cache/recovery and reboot to recovery
@GuyInDogSuit
Update
mirrored OTA 191, 198, 199, 201 & RootZenFone-1.4.6.8r apk => https://drive.google.com/folderview?id=0B5G23fyE72tnLS0yaXlUamVmcXc&usp=sharing#list
@GuyInDogSuit @slayeralive
I've try to update manually but it failed
how to flash .182 if I'm already in .191 ?
slayeralive said:
No need for adb just copy zip ti /data and command file to /cache/recovery and reboot to recovery
Click to expand...
Click to collapse
You don't have to do all the typing anymore?
GuyInDogSuit said:
You don't have to do all the typing anymore?
Click to expand...
Click to collapse
I've try, the tablet show android logo with no command on the screen after reboot without entering command
you did something wrong. command file is just txt file , and echo command in terminal is used for writing text in txt files.try to copy command file and reboot to recovery from terminal emulator with reboot recovery command. I created this method mainly for unbricking read post
http://forum.xda-developers.com/memo-pad-7/general/unbrick-asus-memopad-7-me176c-cx-t2970049
GuyInDogSuit said:
Thanks to @plopingo and @jerbear294 for some of the links.
Click to expand...
Click to collapse
OMG, I can't believe I JUST found this thread.
I have two of these tablets that I use as wall-mounted controllers for HA. One of them accepted the OTA updates and I was able to get it to .201 and keep it rooted. The other one, no matter what I tried, would not pull down anything above the .182 it was running.
This post has EVERYTHING you need to go from whatever all the way to .201 quickly and very easily. I installed 15 Second ADB, the ASUS ADB drivers, and ran through all of the updates. This, my friends, is awesomesauce.
HUGE THANK YOU to @GuyInDogSuit, @plopingo, and @jerbear294!
No luck
im on .182. When I move the files to the directories and reboot to recovery it fails. i get an error. Could this be becuase i had modified the build prop with xblast
peldo123 said:
im on .182. When I move the files to the directories and reboot to recovery it fails. i get an error. Could this be becuase i had modified the build prop with xblast
Click to expand...
Click to collapse
It could. I have made that last year and end up with a bricked tablet...
I had to make a complete reset.
I made a few tries until I get it right and found out that using certain terminal apps don't allow spaces between commands whilst others do... Try commands without breaks if you're using a terminal app. Or try temp cwm to update all the updates at once.
Can't get it to work
Every time i try this procedure this happens:
The tablet restarts after executing the adb shell step.
The tablet starts to update the firmware, but then suddenly throws an error. This happens with both the rom and the update files.
Anyone has any idea how to fix this?
Thx in advance!
kdlannoy said:
Every time i try this procedure this happens:
The tablet restarts after executing the adb shell step.
The tablet starts to update the firmware, but then suddenly throws an error. This happens with both the rom and the update files.
Anyone has any idea how to fix this?
Thx in advance!
Click to expand...
Click to collapse
Did you unzipped the file? You see, there's a zip inside another zip. Unzip the 1st time into root/data folder and rename it to update.zip!
This fixed it! That was a stupid mistake
kdlannoy said:
This fixed it! That was a stupid mistake
Click to expand...
Click to collapse
I'm glad it worked. I once made the same mistake.
I an on 191
there is no /cache/recovery folder
ls /cache
aplogs
backup
lost+found
modemcrash
Should i create /cache/recovery ?
mrseverin said:
I an on 191
there is no /cache/recovery folder
ls /cache
aplogs
backup
lost+found
modemcrash
Should i create /cache/recovery ?
Click to expand...
Click to collapse
Should be safe. I had a recovery folder, but nonetheless I don't see why it would harm anything.
I've had several Android devices. That was the easiest root I've ever done.
bravesoul said:
Did you unzipped the file? You see, there's a zip inside another zip. Unzip the 1st time into root/data folder and rename it to update.zip!
Click to expand...
Click to collapse
Could you give me a little more detail? I can't seem to make it work. Also, I don't have a "data" folder in /root? Can I create one? Thanks. Nevermind, I got it to work.
regele said:
Could you give me a little more detail? I can't seem to make it work. Also, I don't have a "data" folder in /root? Can I create one? Thanks. Nevermind, I got it to work.
Click to expand...
Click to collapse
"/root" isn't a folder. It's the source. For example. When you copy something to a hard drive you are copying to the root of that hard drive. The same goes with the root of the android. So. Copy the unzipped .zip file to root and to inside data folder. Rename it into update.zip and run the commands.
I realise you got it to work, but since this is a community I have explained to others.
2015/10/07 The information below will be kept to help folks make backups and for linux/mac users to have some images to restore but if you have bricked your phone the recommended solution now is to install Alcatel's Mobile Q software version 4.9.2 or newer and use it to restore your phone to factory condition. Basically turn off the phone..plug it up to the pc via usb and run the software...it should prompt you from there. The link to download the software is here: http://alcatelonetouch.com/global-en/support/download/pixi_3_7_4g.html
*****Warning***** Recent updates from Alcatel have REMOVED the fastboot commands that allow root and custom recovery for some models of the 6039. Before updating read the details here: http://forum.xda-developers.com/showthread.php?t=3173598 and make sure the new update doesn't do the same!
You should also be aware that if your phone hangs on boot and you are rooted don't do a factory reset or you will lose adb access if you had it enabled which can be used to restore your phone
Table of Contents
Post #1: Intro
Post #2: Backup Instructions http://forum.xda-developers.com/showpost.php?p=62006344&postcount=2
Post #3: System Images http://forum.xda-developers.com/showpost.php?p=62006344&postcount=3
Post #4: Restore Instructions and firmware issues http://forum.xda-developers.com/showpost.php?p=62006344&postcount=4
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Folks, OTA updates for Lollipop check if your system has ever been mounted read/write (which is required to root) and if it has they do not allow the update to install. What that means is before you root you need to first go into fastboot and do a fastboot boot of TWRP (this boots twrp on your phone without installing it) then go into twrp and backup your system directory so you always have something to restore to if you want future OTA updates.
The bad news is that for folks who have already rooted, we need TWRP backups of the system partition for each model of the idol 3 BEFORE someone has rooted. 6045i, 6045k, 6045y...are there more?
If you have NOT yet rooted your phone and are willing to help out please post here with your model number(It shows in settings, about phone as Model Number). I'll add some instructions on how to take a backup then the backup needs to be uploaded online somewhere we can access it. The system partition is normally read only so it contains NONE of your personal information.
This paragraph from the TWRP documentation is taken from: https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.]
Here's an article that explains it better than I can: https://www.androidpit.com/android-5-0-lollipop-ota-update-fail
20150810 - Turns out all thats required to get updates at least for now is doing a FULL unroot. (That may not be the case with a major jump such as from 5.0.2 to 5.1.1) Failure to do a full unroot can result in boot loops after applying updates that currently DO NOT HAVE A SOLUTION because the default recovery for the 6045i and 6045Y do not have the reboot to bootloader option that IS present in the 6045K and all models of the 6039 Idol 3. Thanks Alcatel! An easier solution is to flash an already upgraded firmware if it is available. Canadian users have also found it useful to flash USA firmware (both have a 6045i) to get updates sooner than being released by the cell providers in canada.
Instructions to backup your system prior to rooting.
-Get/install Alcatel USB driver if Windows. (no need for Mac). FROM HERE: http://54.247.87.13/softwareupgrade/Driver/ALCATEL_ADB_ Driver Qualcomm_ADB.rar , or just connect your idol3 to the computer and from the phone select "cd rom" drive..it will install the drivers automatically
Windows and Mac users should have downloaded the android sdk to get adb and fastboot. [ https://developer.android.com/sdk/ ] Linux (ubuntu based) users should install packages android-tools-adb and android-tools-fastboot Windows users can try a minimal adb and fastboot install using the instructions here: http://forum.xda-developers.com/showthread.php?t=2317790 or here: http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
download twrp from here: https://www.androidfilehost.com/?fid=24052804347778862
-Set USB debugging on in Developer settings (if these are not exposed, go to Settings/About Phone/Build number, and tap 7 times.)
-Plug in USB cable to phone and computer. Tap on USB icon in notifications panel; select MTP (file transfer) mode or PTP also works fine.
-ON your pc open command prompt in the directory where you have placed twrp-2.8.7.0-idol3.img (when using windows in the directory hold shift and press the right button on the mouse, it will pop-up a window where you have to select "open command prompt here" and type "adb reboot-bootloader" to reboot into bootloader
-Then type "fastboot -i 0x1bbb devices" This should show the device
-Type "fastboot -i 0x1bbb boot twrp-2.8.7.0-idol3.img" This will boot twrp on your phone without installing it.
-On your phone do a normal backup but make sure only "system image" (not system) and Boot (to keep the kernel in sync with the system) is checkmarked to be backed up. You can go into TWRP settings and have it write to the external_sd vs using internal "sdcard" before starting the backup if you have one installed
-After backup has completed it will have created a folder named TWRP on your /sdcard or /storage/sdcard1 depending on which you selected (/sdcard by default). Assuming this is your first use of twrp then copy the whole twrp folder over to your pc and zip or rar it then post a message with your model stating you have a backup and we'll work to get it uploaded. If you have previously used twrp and have multiple backups then just go one directory in "/sdcard/TWRP/" and backup only the directory with the date timestamp of your most recent backup.
When uploading to the cloud zip'ing or rar'ing the file will cut it's size by about half. (it's 3gb initially and roughly 900mb afterward) It's still a rather large file so you might look at http://www.filedropper.com/ to upload the file...they claim files allowed up to 5gb and no registration required. https://mega.co.nz is also a good alternative but can be slow. If you have suggestions for a better place to put the files please let me know.
If you are willing to contribute space that will not expire to host the system backups please contact me via pm. Make sure to hit thanks for our generous uploaders.
System Downloads Available [Each download is +- 1GB in size]
(Do not crossflash devices ie flash the 6045i image to a 6045K or 6045Y. We don't know what the results will be!):
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
6045 (5.5 inch model)
From most recent back to "out of the box".
Model: 60450(USA-Cricket) Firmware: 5.0.2-010 03 Link: https://mega.nz/#!xhhy0AKC!hWhDgXCQOGt0cNHcfkkejEEBiP1pjOT5-ZK6mAY5MUU Thanks to squeakychu for the upload!
Model: 6045i(usa) Firmware: 5.0.2.7SRA-UEA2 Link: https://mega.nz/#!dRkgxA5L!z7yVmmgeUWBpAGwJW6ixnGhGBzUky1dfhKksu3yGPKg Thanks to Brian117 for the uploads! (09/28/2015)
Model: 6045i(usa) Firmware: 5.0.2.7SR4-UE40 Link: https://mega.co.nz/#!K9szRIKR!ZdjIiH2Ol0ZCNe2VTSl6cbRyQeZFtafG3Y9CM0ecCkg 20150810 md5sum: 56376824f7c10d8debaec6c3a7100e50
Model: 6045i(usa) Firmware: 5.0.2-7SQR-UER0 Link: https://mega.co.nz/#!FB0DQAhQ!rQ4H39hQR2tDhfniEej-RvsSe5OqWY42_xCsjY08o4k Thanks to buggleston for the upload!
Model: 6045i(usa) Firmware: 5.0.2-7SQ3-UE30 Link: https://mega.co.nz/#!focwnJJL!VQW3Omi3TF4iJzIyNLu73P9gb8i_WKA_fu7ZWUiIsN0 Thanks to Electriccars for the upload!
Model: 6045i(usa) Firmware: 5.0.2.7SMA-UEA1 Link: https://mega.nz/#!pdlWhQLR!D2-mEnxp2SnxH0QBDsSSZ-YrDooJC8BdKronYxziF_A Thanks to lordlittlebrooks for the upload!
Model: 6045i(canada) Firmware: 5.0.2-7SQB-UCB0 Link: https://mega.nz/#!opolxbIY!A9dEfORplfhkmuNwobKsEF2wX6yY3oLq8M9dgWpDNq8 Thanks to KryPTiCk0d3 for the upload!
Model: 6045i(canada) Firmware: 5.0.2-7SQ9-UV93 Link: http://drive.google.com/file/d/0B8Gqss1TYorTaXZrRFdBdDJ2Vnc/view Thanks to green3water5 for the upload!
Model: 6045K(Serbia, Bulgaria, Macedonia and maybe Cz) Firmware: 5.0.2-010 0101001 Link: https://mega.nz/#!L5El0QqA!IrxnA4qyXONyWehaJltc7JsE5TgaAXIdT9RQ73K0Rdw Thanks to bokaco7 and Nikola Jovanovic for the upload!
Model: 6045Y(Europe) Firmware: 5.0.2-010 06 Link: https://mega.nz/#!N9phSbTR!hH0bTJnHcUrwKxdpA-RKyecHNPKls7Cy0fi-Ih3BWkM Thanks to Gynoid for the upload!
Model: 6045Y(Europe) Firmware: 5.0.2-010 05 Link: https://mega.nz/#!pxgwXKIA!TInG7xK9Z-qObX1Cc3BObGp88zx0FCpWI3RDt_wdD0Q and https://mega.nz/#!l5xnSDrL!-y2ye27vODfNAR2qcBAQN7q0gGYA579iRzla07lFkd4 [You will need to flash both as one has the system backup and the other has the boot] Thanks to Gynoid for the upload!
Model: 6045Y(Europe) Firmware: 5.0.2-010 03 Link: http://mega.co.nz/#!CYk2mBCa!XJd1nJI1cUcTcGjwzhApcAyABQ8y54D-bATvgxxHMsE Thanks to zrkkrz for uploading this 2 times!
Model: 6045Y(Europe) Firmware: 5.0.2-010 01 Link: http://data.nettitoimisto.com/f/e308c56574/ Thanks to tommihut for the upload!
Other models not listed? NEEDED!
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
All backups will eventually be mirrored to MEGA. If the file is missing I'm more than likely still trying to get it uploaded. MEGA can be slow however the files should never expire. The folder is here: https://mega.co.nz/#F!DgNhkDKR!GyJsku7nw4F6nLiT4XFRKA
If an individual download link is dead please let me know via post or pm.
Thanks to kirplunk and zrkkrz for uploading backups that ended up having to be replaced due to incorrect instructions to backup system instead of "system image" from within TWRP.
When using these backups.....
There is currently a bug in TWRP that appears to be showing 6045Y for ALL idol3 devices in the recovery.log so make SURE the system image you are flashing is meant for your device to the best of your ability.
Restoring a TWRP backup image:
If you wish to update to a newer firmware or restore an older one you can follow purple.epod's basic instructions here but use the firmware you want to restore: http://forum.xda-developers.com/showpost.php?p=62313284&postcount=1 Also make sure you restore both boot AND system image in the newer firmware's when selecting what to restore.
When restoring the UE40 firmware the first time you go into system update checker you need to delete the existing UE40 update as it kept it around...you should then be able to check updates as normal.
This was brought up in the main rooting thread, but you might also be able to unroot via SuperSU with the Full Unroot option. Haven't tried it yet but if it works, you can just unroot, install whatever OTA there may be, and re-root.
brian117 said:
This was brought up in the main rooting thread, but you might also be able to unroot via SuperSU with the Full Unroot option. Haven't tried it yet but if it works, you can just unroot, install whatever OTA there may be, and re-root.
Click to expand...
Click to collapse
Yeah, I'm the one who brought it up. I thought those about to root should be made aware.
Based on the twrp documentation it sounds like once it's been mounted once as read/write there is a way for them to check and it will kill the ota update. unrooting isn't going to fix that. We also have no good way to intercept the updates so we could alter them to install anyway. I used a squid transparent proxy to find the download url but won't do me any good if my phone can't download the update. If it lets the phone dwonload and then when it runs aborts I may still be able to grab the url and the update could be modified to apply anyway.
tried to upload stock system backup for 6045i
famewolf said:
Reserved 1
Click to expand...
Click to collapse
i have backed up the stock system twrp backup for 6045i zipped in folder then tried your file link to up load, after about 15 minutes it was still uploading seemed to long so i stopped the upload. do you or dallascz have another place to upload or email maybe? i still have not installed the recovery or rooted yet, trying to give back to Idol3ers.
---------- Post added at 01:51 AM ---------- Previous post was at 01:34 AM ----------
famewolf said:
Folks, OTA updates for Lollipop check if your system has ever been mounted read/write (which is required to root) and if it has they do not allow the update to install. What that means is before you root you need to first go into fastboot and do a fastboot boot of TWRP (this boots twrp on your phone without installing it) then go into twrp and backup your system directory so you always have something to restore to if you want future OTA updates.
The bad news is that for folks who have already rooted, we need TWRP backups of the system partition for each model of the idol 3 BEFORE someone has rooted. 6045i, 6045k, 6045y...are there more?
If you have NOT yet rooted your phone and are willing to help out please post here with your model number(It shows in settings, about phone as Model Number). I'll add some instructions on how to take a backup then the backup needs to be uploaded online somewhere we can access it. The system partition is normally read only so it contains NONE of your personal information.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.]
Click to expand...
Click to collapse
i have backed up the stock system twrp backup for 6045i zipped in folder then tried your file link to up load, after about 15 minutes it was still uploading seemed to long so i stopped the upload. do you or dallascz have another place to upload or email maybe? i still have not installed the recovery or rooted yet, trying to give back to Idol3ers.
kirplunk said:
i have backed up the stock system twrp backup for 6045i zipped in folder then tried your file link to up load, after about 15 minutes it was still uploading seemed to long so i stopped the upload. do you or dallascz have another place to upload or email maybe? i still have not installed the recovery or rooted yet, trying to give back to Idol3ers.
---------- Post added at 01:51 AM ---------- Previous post was at 01:34 AM ----------
i have backed up the stock system twrp backup for 6045i zipped in folder then tried your file link to up load, after about 15 minutes it was still uploading seemed to long so i stopped the upload. do you or dallascz have another place to upload or email maybe? i still have not installed the recovery or rooted yet, trying to give back to Idol3ers.
Click to expand...
Click to collapse
kirplunk, how large is the file after you have zipped it? I'll check into some more services. I'm limited by the fact I don't have hi speed and I don't think xda rules allow me to mention any file sharing service that requires registration. If you do a google of "upload large file" and find a service that works for you let me know. If others have a suggestion also let me know. I'm reply back as soon as I find some other sites. Thanks for your assistance!
*update* In other areas of XDA they suggest https://mega.co.nz/ for large file uploads however it would require creating your own account. They give you 50GB. Let me know if this works for you please.
size reply
famewolf said:
kirplunk, how large is the file after you have zipped it? I'll check into some more services. I'm limited by the fact I don't have hi speed and I don't think xda rules allow me to mention any file sharing service that requires registration. If you do a google of "upload large file" and find a service that works for you let me know. If others have a suggestion also let me know. I'm reply back as soon as I find some other sites. Thanks for your assistance!
Click to expand...
Click to collapse
the unzipped folder with files was 2.1gb in size, the zipped folder with files that i tried to upload is 855mb in size. i do not use the cloud at all so i don't have a drop box or any thing of the type. the site you referenced said it was uploading but it seemed 15 minutes was more than enough time for that size of file. my browser kept saying it was uploading and connecting to site.
kirplunk said:
the unzipped folder with files was 2.1gb in size, the zipped folder with files that i tried to upload is 855mb in size. i do not use the cloud at all so i don't have a drop box or any thing of the type. the site you referenced said it was uploading but it seemed 15 minutes was more than enough time for that size of file. my browser kept saying it was uploading and connecting to site.
Click to expand...
Click to collapse
Can you please try https://mega.co.nz/ and see if it works better for you? It will require creating an account but they will give you 50GB and you could use a disposable email address if you prefer. I'm checking other areas of xda to see how they handle large file uploads and this is what I've seen so far.
I have no problem sharing one I've created but there will always be that one person who wants to come along and delete everything in it.
Another is http://www.filedropper.com/ which allows up to 5gb files and keeps them till 30 days of not being downloaded. No registration required.
Also is your backup after the two system updates? Just FYI your upload bandwidth is not going to be as high as your download typically so uploads of large files can take a while.
attempting the second site now, called file dropper.
the file folder i'm uploading is called, 6045i twrp stock system backup.7z
upload is at 10% right now
now at 20%, yes with updates firmware is 5.0.2-7sqr-uero
30% my upload speed should put this file up in 3 minutes but their server is taking it like sucking coffee up through a stir stick, slow
will update when it reaches 100%, but as a junior member i can not post links so you will have to find it at the file dropper.
100% uploaded,
as a junior member this is the best i can do for the link.
www dot filedropper dot com/6045itwrpstocksystembackup
hope this helps
Uploads tend to be much slower than downloads. LTE connections are an exception, but cable and DSL upstream speeds aren't fast.
kirplunk said:
the file folder i'm uploading is called, 6045i twrp stock system backup.7z
upload is at 10% right now
now at 20%, yes with updates firmware is 5.0.2-7sqr-uero
30% my upload speed should put this file up in 3 minutes but their server is taking it like sucking coffee up through a stir stick, slow
will update when it reaches 100%, but as a junior member i can not post links so you will have to find it at the file dropper.
Click to expand...
Click to collapse
Feel free to send me the link in a PM and I'll post it so others can download it in addition to me or I'm sure I can find it based on filename if they have search.
With your permission I'll put it in post #3 with your name and a thank you. I'll have to visit the local library that has rather fast internet to get these files downloaded and moved to one folder for everyone assuming others share theirs as well.
So using stock recovery to Wipe Data/Factory Reset back to new doesn't remove root or r/w status?
mk3 said:
So using stock recovery to Wipe Data/Factory Reset back to new doesn't remove root or r/w status?
Click to expand...
Click to collapse
A factory reset wipes the data and cache partitions. It does nothing to /system since it expects it to be read only.
famewolf said:
A factory reset wipes the data and cache partitions. It does nothing to /system since it expects it to be read only.
Click to expand...
Click to collapse
ahhh.... bummer. Thanks for the clarification.
So I used Hide My Root to hide su binary and the system update doesn't give me the error (like all is fine). Prior to hiding the su binary it throws the error about being rooted.
.
Is the /system partition different than the /system directory that's in the root of the device? If it's the same, we can change the read/write permissions with ES File Explorer if the device is rooted? I'm not sure if it'll offer us the chance, if we want it, to make all the contents of the dir have the same permissions we set for the dir itself. Can the same thing be done from a command line in TWRP?
Why does TWRP show "system" and "system image" as two different options and sizes to backup? I've never seen that before.
maigre said:
Is the /system partition different than the /system directory that's in the root of the device? If it's the same, we can change the read/write permissions with ES File Explorer if the device is rooted? I'm not sure if it'll offer us the chance, if we want it, to make all the contents of the dir have the same permissions we set for the dir itself. Can the same thing be done from a command line in TWRP?
Click to expand...
Click to collapse
The system partition is the same as the /system folder however it's not a file permission that's an issue and you'd never want to set all your files to the same permissions. Here is an article that explains it better than I can: https://www.androidpit.com/android-5-0-lollipop-ota-update-fail
kirplunk said:
the file folder i'm uploading is called, 6045i twrp stock system backup.7z
upload is at 10% right now
now at 20%, yes with updates firmware is 5.0.2-7sqr-uero
30% my upload speed should put this file up in 3 minutes but their server is taking it like sucking coffee up through a stir stick, slow
will update when it reaches 100%, but as a junior member i can not post links so you will have to find it at the file dropper.
100% uploaded,
as a junior member this is the best i can do for the link.
www dot filedropper dot com/6045itwrpstocksystembackup
hope this helps
Click to expand...
Click to collapse
Thanks kirplunk! I've got it downloading and will add my folder as a mirror to try to prevent the file from expiring.
If you are like me, you own an LG G4 with a bootloader that cannot be unlocked. This, at least for the moment, means that we cannot have both Android 6.0 Marshmallow and our beloved root access. We must choose one or the other. I assume that if you are reading this, that you have chosen root over marshmallow. If you did choose to stay rooted on 5.1, then I am sure you are being harassed to update. Well, I believe that I have your solution.
First, I must explain what this guide will do and what you will need.
What we're doing.
1. We will delete the update.zip.
2. We will make a dummy update.zip that will not be replaceable or modifiable, even by the root user. This fake update file will prevent a legitimate update from downloading and installing.
3. [OPTIONAL] We will remove the annoying update notification.
What is needed.
1. Root. [duh...]
2. File explorer with root privileges a.k.a. a "root explorer". (If you need one, I personally recommend the free yet feature packed ES File Explorer.)
3. A proper Busybox installation.
4. A terminal emulator.
5. A few minutes of your time.
***AS ALWAYS, I, XDA, XDA MODERATORS, XDA MEMBERS, OR ANYONE ELSE IS NOT RESPONSIBLE FOR THE CONSEQUENCES OF FOLLOWING THIS GUIDE. THE DEVICE YOU HOLD IS YOURS AND ANYTHING THAT HAPPENS TO IT IS YOUR FAULT. YOU HAVE BEEN WARNED!***
The procedure.
-Part 1.
1. Open your root explorer and make sure that it has root privileges.
2. Navigate to /cache
3. If you have a file called update.zip then delete it, if not, then just move on to part 2.
-Part 2.
4. Make a new .zip file with nothing in it and save it as update.zip (make sure it is saved to "/cache" and nowhere else, not even in a folder inside "/cache"!)
5. From here move on to your terminal emulator.
6. Once inside the terminal emulator, type the following commands.
Code:
su
cd /cache
ls
chattr +i update.zip
From here I recommend that you check that it worked by typing in
Code:
lsattr update.zip
If the command works you will see a lowercase 'i' amongst a string of letters and dashes.
-Part 3. [Optional] (I don't recommend doing this, but the harm is non-existent as far as I can tell.)
The annoying update notifications are actually Google Play Services fault. All you have to do is go to "Settings > Apps > All" and find Google play services and disable the apps ability to show you notifications.
Thats pretty much it. Now I must tell you that you will still receive notifications saying an update was downloaded, verified, and is ready to install, assuming that you did not go through with part 3. All you have to do is click the install button, and let it restart to install the bogus update. The update process will error and all you have to do now is pull and reinsert the battery and power on the phone. I have been doing this myself for a few weeks now and have not had a single issue. This also includes 4 times that it has failed to install the update from within recovery.
I hope that you find this useful and happy modding!
Reserved
Reserved.
BLU R1-HD bootloader unlock script tool, and TWRP install tool.
Download is a zip file, unpack it to somewhere you will remember. Run the dirty-cow-tool.bat // mtk-su-tool.bat
The included files and folders are set to hidden, in effort to keep them safe from accidental delete.
Must have adb+fastboot + drivers installed and setup prior to using tool
Easiest method to install adb + fastboot on windows is with "15 second adb + fastboot install TOOL"
LINK==>ADB+FASTBOOT
It is for windows
In linux :
"sudo apt-get install android-tools-adb"
"sudo apt-get install android-tools-fastboot" Some fastboot commands were missing when i used this one ie "fastboot flashing get_unlock_ability"
"sudo apt-get install fastboot" worked better when I tried. ( i used that command as a check before doing the unlock, so it was needed only for that check)
Using Tool
On Windows?
Unzip the downloaded file to a new folder, open new
folder and click on "dirty-cow-tool.bat". // "mtk-su-tool.bat"
Do the steps in order (1-2-3-4) to be unlocked, then
Step (5) to get to second page where step (1) is root
The rest is optional
On Linux?
Unzip downloaded file to new folder folder .
Open folder. Then open R1-Linux-tool-v2 folder
Open terminal from that folder and type
" . R1-HD-TOOL.sh "
Same order of steps (1,2,3,4) step (5) for extra
Steps (1 on second menu) for superSU root.
Second menu steps (2,3,4,5,6,7,8) are optional.
**Linux Note**
The tool uses "fastboot flashing get_unlock_ability" as one of the methods to check before doing the unlock.
The version of fastboot that installed with "apt-get install android-tools-fastboot" did not recognize
this command. But "apt-get install fastboot" updated some version and then the command was recognized.
******OTHER NOTES****
--- this has been mentioned in the general thread and the modified v17 thread, but It has come up again so I wanted to make note of it.----
--- The newest blu versions (V7.4.2 and V17) Have made changes to "toolbox" and this effects things like "adaway" and "titanium backup"
--- The suggested fix is to install busy-box. I have had success with the version from play store, some prefer to use f-droid version. Either one will do. Install it and open the app. From in the app you need to do an install.
CHANGE LOG
V1:. Initial release : removed
V2:. : fixed typos preventing proper function
V3:.: switch file verification to md5 check instead of "ls-l" comparison.
V4: current version: add extras page, add SU flash, de-bloat script, Added Fm Radio, Added pre-loader roll back
V5: Fixed wrong loop "goto" line that made preloader rollback do "MTK_BLU Debloat v2" instead
V6: Added manual pause to script for mods that need recovery (Extra's 5) . Added redundent recovery flash command .
Few reports of recovery "not Sticking" and needed to run the flash commands manually one by one. Maybe the redundent
flash will make it survive. If still having problem with recovery "staying install" try manually flashing
here is link to the steps needed. FLASH RECOVERY
V7 Improved logs Added line to make batch run as sub-process so if error occurs , will not close
V7.1 : Updated the fm radio install zip and include the needed selinux mode changer app
V8: fixed dependency of needing to be unzipped to location w/o spaces in name. (when used from location with spaces, tool used to fail to push needed files).
.. added more time to allow dirtycow to "spawn" its root shell. Recent testing has shown sometimes it takes longer than the 60 seconds allowed in the script. Now it is looped 3 times.
V9 Added full path to abd push lines for recovery flash files. included fastboot.exe file to address some version issue where user s version would not output text file I coded into script for a verification ( included file is called by script, no need to do anything different with it)
V10: Moved zip file to included folder to help preserve locations when unpacked, added device check before running tool; So tool not used on wrong device, Rearranged order of operations on extra's page. (recovery installed options) Push files while in android before rebooting to recovery( should improve reliability for multiple reports of not automatically installing options for some)
******I have received some reports that some devices are reporting "ro.build.product =R1_HD and not "BLU_R1_HD" like mine, so the added device check is blocking tool from starting If this happens to you , you can make edit to the .bat file like below.
Change this line
Code:
:next_check
find "BLU_R1_HD" "%~dp0workingproduct.txt"
To this
Code:
:next_check
find "R1_HD" "%~dp0workingproduct.txt"
it is line #23
V11: Updated device model verification lines
MTK-SU: Replaced all dirty-cow part with New MTK-SU binary(elf) from @diplomatic
source
Click to expand...
Click to collapse
Credits to @Diplomatic for his work on the Mtk_su that I used used to make this tool work again after Dirty-Cow was patched.
DOWNLOAD LINK
Preferred to use the Downloads tab of this thread.
Archived downloads on android file host also == link
XDA:DevDB Information
R1-HD Dirty-cow Unlock Tool, Tool/Utility for the BLU R1 HD
Contributors
mrmazak, vampirefo for his recovery, lopestom for his recovery, emc2cube for his debloat zips, christianrodher for his dirtycow method,
Source Code: https://github.com/mrmazakblu/DirtyCow-R1_HD
Version Information
Status: Testing
Current Stable Version: V11
Stable Release Date: 2017-04-11
Current Beta Version: MTK-SU
Beta Release Date: 2019-04-14
Created 2017-02-22
Last Updated 2019-04-18
Reserved
Items planed to be addressed in next release:
--Add few more file integrity checks to the extra's page
--Add copy log to clipboard option so it is easier to post log entry if needed-------*********----already-_added to github copy of batch file
--Add a verification step that checks what recovery is installed( to prevent trying to do steps on extra's page with stock recovery)
--Possibly move to a "fastboot boot recovery" instead of "adb reboot recovery" for the same reason as above
--Add wget or similar to the extra's items so initial "TOOL" size is smaller (not that 40-50MB is big, but to some it may be )
--Add additional "selinux mode changer apk" for fm radio install rather than just the note that says it needs to be found.
Reserved
Works great on OEM 6.6, thanks for the tool!
So I got the one-click-root.sh done, maybe. Can some linux users go over it, make sure I didn't do anything stupid? I don't exactly have a device to check it with atm, and I am not pro with scripting, barely novice, so it is a pretty basic conversion of the batch file. Still, it might work . Just would like a few eyes on first.
https://github.com/theredbaron1834/Scripts/blob/master/one-click-root.sh
Also, I looked at dirty-cow-tool.bat. However, wow, more an advanced batch file, and I am not sure what the first half does, so not sure how to convert . However, it seems if anyone does get it, the eqiv of goto for linux is funtions. simple cheatsheet:
Code:
function stuff {
echo "this stuff is run via the function"
{
stuff #goes to stuff and runs function
theredbaron1834 said:
So I got the one-click-root.sh done, maybe. Can some linux users go over it, make sure I didn't do anything stupid? I don't exactly have a device to check it with atm, and I am not pro with scripting, barely novice, so it is a pretty basic conversion of the batch file. Still, it might work . Just would like a few eyes on first.
https://github.com/theredbaron1834/Scripts/blob/master/one-click-root.sh
Also, I looked at dirty-cow-tool.bat. However, wow, more an advanced batch file, and I am not sure what the first half does, so not sure how to convert . However, it seems if anyone does get it, the eqiv of goto for linux is funtions. simple cheatsheet:
Code:
function stuff {
echo "this stuff is run via the function"
{
stuff #goes to stuff and runs function
Click to expand...
Click to collapse
thank you for your input.
As far as the begining of the batch, It is adding a few folders to the "path" variable so help ensure the "adb push" commands find the files it is trying to push. Then it sets some folder "flags" to hidden so that the files the batch needs don't get accidentally moved or changed. Then the large section with mostly "echo" that is to set up the "simulated" G.U.I.
The lines of just "::::::::::" are simply used to help with reading the batch file. i use them to seperate functions. They are not needed.
The lines with only 2 "::" are standard windows comment / remark line entries
The lines with 1 ":" are the beginning line of the loop/ function == the line that "goto *" searches for
Does Works to unlock 7.4.2?
khyr said:
Does Works to unlock 7.4.2?
Click to expand...
Click to collapse
It is supposed to. It is the same base codes used from original script, and that one was confirmed to work. I Do not have first hand use of V7.4.2 so it is only confirmed through other users.
The dirty-cow being used has been patched by google in Dec but blu has not rolled out the patch. So there is no reason for it not to work.
edit:
I have the linux version ready.
-the first step, (ADB Push) is ready. including md5 file checks
-step 2 is ready= running dirty-cow with md5 check before final writing to mmcblk device
-step 3 is ready unlocking bootloader = including check if unlock is done, but need to fix the "unlock_adility" check
I can make to file to compare and grep the line needed, but cannot "sed" the extra information or do a > < comparison
-step 4 is ready .--flash twrp
Finished 90% of tool.
still need to tweek the log feature.
I ran tests on the lop back to menu and test ran
1. push files for dirty-cow and md5 check . then made push fail to verify the check method was valid ==pass
2. run dirty cow commands and md5 verification on resulting file. ==pass
3.unlock bootloader --- I ran it (needed to fake the already unlocked check) it works == pass
4 . flash twrp --installed both version i have, both install fine ===pass
5 extra menus -- ran . install su-----debloat---rebloat--- add fm radio--- preloader roll back =====all pass
(bootloader roll back needs manual intervention to re-enter fastboot during the boot loop that is unavoidable)
6. instruction ====not written yet
7. exit yes it closes == pass
8. logs --- needs completeing
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
torchredfrc said:
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
Click to expand...
Click to collapse
no it does not.
the /sdcard is the internal memory and the Download folder is already there.
you might be having issues but the folder is already part of normal system
mrmazak said:
no it does not.
the /sdcard is the internal memory and the Download folder is already there.
you might be having issues but the folder is already part of normal system
Click to expand...
Click to collapse
Fair enough, my restore didn't have /sdcard/Download and I made an assumption that /sdcard was my mounted card. Thanks for the insight.
OOPS
found typo on V4 of tool. batch files sets variables for "return", from loop functions. And two returns were set to same label9, so if you had tried to do extra's menu option #8. "ROLL Back Preloader" , instead it was running option # 5. " MTK_BLU Debloat v2"
fixed and still reading and re-reading to search for errors.
This looks bad.
The reason I put together this tool was I felt it was important to make a way to minimize the problems usually associated with android modifications. By making "typo's" a thing of the past, and I found them in my own script.
re-posted V5 combined with linux V2--
torchredfrc said:
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
Click to expand...
Click to collapse
I'm a total noob, and I'd like to know how to proceed with the supersu and all the other parts of step 5. Thank you
gabriel986 said:
I'm a total noob, and I'd like to know how to proceed with the supersu and all the other parts of step 5. Thank you
Click to expand...
Click to collapse
Ok. After you have completed upto twrp install. You can do the options on #5. It is all programed and automatic. What is does is put zip files onto the phone and reboots phone into recovery, then recovery installs them.
mrmazak said:
Ok. After you have completed upto twrp install. You can do the options on #5. It is all programed and automatic. What is does is put zip files onto the phone and reboots phone into recovery, then recovery installs them.
Click to expand...
Click to collapse
I get up to the recovery installation, but then I can not access such recovery on the phone, If I turn it on with power+vol up, it takes me to the default factory recovery by blu.
And If I try to the super su step with the phone on, it resets it, and get it to the screen with the dead android, while the script just shows the ADB DETECTED message.
In case it's needed, my R1 HD is running on
BLU_R0010UU_V7.4.2_GENERIC 09-11-2016 13:38
gabriel986 said:
I get up to the recovery installation, but then I can not access such recovery on the phone, If I turn it on with power+vol up, it takes me to the default factory recovery by blu.
And If I try to the super su step with the phone on, it resets it, and get it to the screen with the dead android, while the script just shows the ADB DETECTED message.
Click to expand...
Click to collapse
You missed a step in the process.
As tool finishes the recovery install it comes to a "pause" in the script, you need to hold the volume up button on phone "before" pressing button on pc keyboard to continue.
If phone does a normal reboot at this point then the system will replace the newly installed recovery with the stock one.
Giving you the situation you have now.
This step I cannot control, you must press volume button on phone to get the boot menu, and directly boot into recovery to ensure that the install sticks.
mrmazak said:
You missed a step in the process.
As tool finishes the recovery install it comes to a "pause" in the script, you need to hold the volume up button on phone "before" pressing button on pc keyboard to continue.
If phone does a normal reboot at this point then the system will replace the newly installed recovery with the stock one.
Giving you the situation you have now.
This step I cannot control, you must press volume button on phone to get the boot menu, and directly boot into recovery to ensure that the install sticks.
Click to expand...
Click to collapse
trying again....
for how long should I press the volume up key?
gabriel986 said:
trying again....
for how long should I press the volume up key?
Click to expand...
Click to collapse
When tool says Hold button , keep it held. Then continue the script. Phone should reboot to the boot menu. Then let go of volume
Some phones do not accept the fastboot reboot command, on those phones need to hold power to shut off. Then volume and power together to come on, release power when screen come on
mrmazak said:
When tool says Hold button , keep it held. Then continue the script. Phone should reboot to the boot menu. Then let go of volume
Some phones do not accept the fastboot reboot command, on those phones need to hold power to shut off. Then volume and power together to come on, release power when screen come on
Click to expand...
Click to collapse
ok.. trying again
---------- Post added at 02:00 PM ---------- Previous post was at 01:46 PM ----------
gabriel986 said:
trying again....
for how long should I press the volume up key?
Click to expand...
Click to collapse
it beat me!
I get stuck in that part of the process, If anyone uploads a video to check what i'm doing wrong, I'll be grateful.
I want to capture OTA update file.
The plan is to power down the device during OTA (when exactly?). Then, boot to TWRP and copy the FW update file. I looked up the OTA update file Blur*.zip , but could not find it
Which folder do look at?
I have also tried to capture OTA URL adb logcat > log.txt , but could not get working URL.
In the log file, I did see something like
Code:
downloadUrl = https://dlmgr.gtm.svcmot.com/dl/dlws/1/download/5a695MmLWnZQIL7IPS5cD4nkj9%2FmlRBFuisKgbOUteZFGF0LVIr3fZGsyTBNleklN%2BvGu2j4xooz5Ky%2Fve7SfWcmRdeS8aXEqSgmHrq6dVou%2BSZiZPovBazKrFv%2FJoXkyH7iWsYR8xYS3OnEgEHCmVoZXEBUKY59HhFInaxCzVy0cBpVlJH1nkYcaGn4tEV1OcTQjLUHJm1jGxmqUAatFw%3D%3D
which decodes to
Code:
https://dlmgr.gtm.svcmot.com/dl/dlws/1/download/5a695MmLWnZQIL7IPS5cD4nkj9/mlRBFuisKgbOUteZFGF0LVIr3fZGsyTBNleklN+vGu2j4xooz5Ky/ve7SfWcmRdeS8aXEqSgmHrq6dVou+SZiZPovBazKrFv/JoXkyH7iWsYR8xYS3OnEgEHCmVoZXEBUKY59HhFInaxCzVy0cBpVlJH1nkYcaGn4tEV1OcTQjLUHJm1jGxmqUAatFw==
but still without success
Un-rooted Pie with un-locked BL
You're getting close...
Here are the steps which worked for me:
1. open this file /data/data/com.motorola.ccc.ota/shared_prefs/dl_prefs.xml (it only appears after first update attempt)
2. after a few lines you can find s.th. like this for example:
Code:
<string name="downloadRequest">
{"downloadRequest":
{"contentResource":"
{\"proceed\":true,\"wifiUrl\
":\"https:\\\/\\\/dlmgr.gtm.svcmot
.com\\\/dl\\\/dlws\\\/1\\\
/download\\\/Ig7qWQDh9p68jhxIGs
L7D4nkj9%2FmlRBFuisKgbOUteZFGF0L
VIr3fZGsyTBNleklN%2BvGu2j4xooz5Ky
%2Fve7SfZ5%2F7SIx tZe8aC%2BjQKdzC6g
u%2BSZiZPovBazKrFv%2FJoXktakuX
8J%2FXekJkTtRmbyNA59LsD0cJ%2F
PGoMafEslS1aOcnWbxMUaAS2gAna
GCZgerOcTQjLUHJm1jGxmqUAatFw
%3D%3D\",\"
3. copy the URL https://...= and delete all \ between the / before open it in your browser.
ATTENTION:
The URL is only valid while your system is attempting to update your device. If you cancel the (attempt to) update, the URL is not longer valid!
WoKoschekk said:
open this file /data/data/com.motorola.ccc.ota/shared_prefs/dl_prefs.xml
Click to expand...
Click to collapse
I think I will not be able to access this file on un-rooted phone unless I boot to TWRP.
WoKoschekk said:
The URL is only valid while your system is attempting to update your device. If you cancel the (attempt to) update, the URL is not longer valid!
Click to expand...
Click to collapse
if I power off my Wi-Fi router and then power off my phone, will the URL remain valid for a while?
Better yet, if I cancel the download and re-attempt it, say, in 15 min, will the the URL be different or the same?
Why do you need the OTA.zip when unrooted?
Try it this way:
While your device is running and attempting to update connect it to your PC and run following command:
Code:
adb logcat | grep dlmgr > log.txt
copy the URL shown in log.txt in any browser on your PC and download the ota.zip
Don't forget to erase the \ in the shown URL if necessary.
WoKoschekk said:
Code:
adb logcat | grep dlmgr > log.txt
Click to expand...
Click to collapse
Does it have to be a Linux PC?
On Windows PC, I am getting
'grep' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
Regardless, I found a download URL and downloaded "ab_delta-Blur_Version.29.291.8-29.321.13.evert.retail.en.US.zip" ( 148 MB), which updates to 116-11-11
Then, I found another URL and and downloaded "ab_delta-Blur_Version.29.321.13-29.351.21.evert.retail.en.US.zip" (86Mb), which updates to 116-11-13
II was not able to manually install the above Blurs until I re-lock the boot-loader.
So Moto becomes more and more picky and strict and not only root, but also unlocked BL and stock FW for non-matching channels is not tolerated
The download URL is present in both files:
/data/data/com.motorola.ccc.ota/shared_prefs/dl_prefs.xml
/data/data/com.motorola.ccc.ota/shared_prefs/ota_prefs.xml
To make things right:
The ota.zip contains only pieces/updates of your current FW. During the installation process the .zip overwrites targeted files of your significant partitions. If Motorola wouldn't proof these files to be stock, then the installation could lead into a bootloop or hard bricked device. Motorola's developers only know their own filestructure but not custom roms'. To avoid fatal failures of your device they have to check your system before doing any modifications. If it isn't stock then the installation will be cancelled.
BTW: There's no need to relock the bootloader. Running a stock FW meets the criteria to receive and to install a OTA update.