Related
since the brand new root for ota rc30 i can not find the general stickies for "how to keep root" installing "eng bootload" and "updating to jf 1.3" for the 90% of users who had ota rc30 where do we look. i tried checking darkrifts wiki but it is no where as detailed as these subtopics here. its telling me to copy the androidmod1.0.zip to my /system/recovery partition and copy the jf 1.3.zip to the /sdcard not renaming either but then doing a reboot... am i missing something.
can we clarify this?
i got the root... but what order do we do this in now?
edit didnt work but it seems as All of the prior stickies are over written by all of the new root your ota rc30 topics
http://forum.xda-developers.com/showthread.php?t=466455
Theres links in that thread to the wiki that explains how to install the modified updates after down grading. You have to install the recovery test keys to allow the modifed updates to be installed.
The terminal commands for doing the test key stuff is down using a terminal on your phone. Download telnet from the market and connect to localhost. You will need root access. Restart your phone and once booted, type telnetd then enter. Dont worry about a contact search coming up. Ignore it. You now have root.
ok what you are missing verbatim from rifts wiki.....
AndroidMod1.0 .xxx file G1 downloadable link (rename to .zip)
AndroidMod1.0 .zip file Non G1 download, no need to rename,
Unzip the file and copy (or adb push) recovery_testkeys.img to /sdcard
Download the modified update (Do not unzip it!):
ok its worded so funny recovery test keys is in the file mod1.0.zip but it explicitly tells you DO NOT UNZIP it ? but line 2 says copy the recovery keys in that zip to the card... then it skips to updating to jf.1.3.zip
and more glaring errors in directions?
Its a bit of a confusing read at first. Thetres 2 files to download. 1 has the tesst keys which u extract and copy to the sd card. With root access this gets written to the system artition ia terminal on the phone. then the other download is rc30 or tc8 depending if you r us which gets renamed to update.zip and goes to your sd card.
So I have tried searching some and my case might be a little different so I thought I would just ask.
I have a G2 that i am trying to retrieve data from. Specifically the SMS database file. I have found that in android, the sms messages are not kept on the sim car or the SD, its kept in a .db file in the internal memory. Unfortunately these files are restricted without root/su access.
From what I have read, the only way to root right now is to downgrade the OS to a previous version to obtain root. Unfortunately, doing that would erase the .db file and would be counter productive.
I have tried using ADB to obtain root/su access to extract a copy of the DB to no avail. I tried visionary and z4 to temp root and neither seemed to allow me to su in the terminal.
Again, all I need is SU access for a short ammt of time to copy out a file in a section that is restricted. Does anyone know any way to do this? Though backups? copying the whole file system to my cpu hdd? Temp root program that does work?
Any ideas?
Go to this guide
Follow the 'Gaining Temp-Root' and '
Temp-Rooting to Backup' sections.
-Nipqer
Why do you need su to copy a file from /system?
Ok, here is a new version of OTA2 for US tablets that should be flashable in CWR and should keep CWR and root without requiring the use of OTA rootkeeper. I would still protect root with OTA Rootkeeper and temp unroot before updating (you can try it without temp unroot but it has caused some problems for other users). This update will still scan all your system apps so you need to restore or unfreeze any system apps that you deleted or froze using Ti Backup.
Instructions:
This update is for owners of US tablets with root and ClockworkMod Recovery. Make sure your battery is well charged before flashing this, a dead battery mid update can create major problems!
1. Install OTA Rootkeeper and protect root. You should now temp unroot. Users who did not temp un-root have had issues with su access after updating.
2. Download the update below and put it on your external sdcard
3. Restore any system apps that you have removed
4. Reboot into ClockworkMod Recovery (Shutdown Thinkpad, turn on and press vol+ repeatedly until you see booting recovery image)
5. I would also highly recommend making a nandroid backup if you have not previously done so.
6. Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
7. update.zip will run, it will check your system apps during the update and may fail if you have changed something, if so the error message should explain why
8. Reboot tablet; it will be a very long reboot. This is normal; it seems to take forever but just let it boot.
9. Use OTA Rootkeeper to restore root.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip
-----------------------------------------
Original Message
So I would like to modify the new OTA so I get the updates without losing root and my current recovery. It is my understanding that the file: \META-INF\com\google\android\updater-script contains the instructions for how the update should run. Can I simply modify this script so that it won't delete root or overwrite my recovery or boot and then flash it in CWR? It looks like it would be pretty straight forward but it would be nice to get some information from someone more knowledgeable so that I don't mess something up and brick my TpT. One obvious line to remove would be where it deletes superuser.apk and su. There is also a section where it patches the boot image, I'm not sure what this patch does but I am worried that maybe somehow they might lock the bootloader. EDIT: I updated, and still have CWR so the bootloader didn't get locked. The other lines I would remove are the ones that reference recovery. If someone with knowledge of android would be willing to help me with this then I will upload my modified update.zip (assuming it works) so that others can avoid the hassle.
So I think that the process would be to delete the current \META-INF\ folder, then put in my modified updater script in \META-INF\com\google\android\updater-script and sign the update with SignApk.jar? Is this the correct process? Any help would be greatly appreciated.
Thanks.
I attached the original updater-script below for anyone interested in taking a look.
I appreciate you posting the file. I've never worked with Android code and this was a great intro.
I'm not sure this will work. Although I'm not super knowledgeable in this.
I did find these two threads.
http://forum.xda-developers.com/showthread.php?t=1185881
http://forum.xda-developers.com/showpost.php?p=21351145&postcount=101
Of course, the latter is in respect to the Galaxy Nexus, and I am sure most of those people have unlocked bootloaders, etc. So again, not sure if those shed any more light on it, but am also curious on a process like this.
The update popped up on my tablet last night and I clicked "more info" and from what it lists, does not seem to be very many fixes
So I successfully updated in ClockworkMod Recovery without losing CWR and without deleting my Superuser.apk and su files by modifying the updater-script in the update.zip. Unfortunately it still messed up my superuser permissions somehow and I ended up having to use ADB while booted into CWR to push and symlink the proper files to get su working again (OTA Rootkeeper wasn't functioning properly because the files were there but the permissions were messed up). I have modified the update.zip so that now it deletes the superuser.apk and su files but keeps clockworkmod recovery. With this and OTA Rootkeeper I think you should be able to update while keeping CWR and restoring root. I will also provide directions here for those seeking to make their own modifications and possibly improve upon my efforts, but proceed with caution.
So what I did was open the zip in winrar and extracted the updater-script. I then edited some lines of code using Notepad++, deleting the ones that referred to deleting recovery or installing a new recovery as well as the lines to delete superuser.apk and /system/bin/su and /system/xbin/su. I also commented out a couple lines at the beginning (assert(getprop("ro.product.device") == "Indigo") because I was getting an error code status 7 when it was trying to perform this check while using clockwork mod. I checked my build.prop and it does say Indigo so I don't know why the check failed but just removing the check was easier for me than figuring out the problem (generally it is not good to remove such checks but I was sure I had the right file). In Notepad++ you must select save as and choose type all files then just save it with the same name. Then replace the updater-script in your zip file with the modified one, I used winrar and chose the compression to just be store (ie no compression). Then you need to delete the CERT.RSA, CERT.SF, and MANIFEST.MF files in the META-INF folder of your update.zip and you sign the update.zip using testsign.jar. Then your new modified update.zip is ready to go.
I think that the reason things did not work out for me is that there are a bunch of lines in the updater script about symlinking and setting permissions for stuff in /system and I think /system/bin/su was originally symlinked to /system/xbin/su which is the real file so things got messed up and I had the files still but the symlink and or permissions were messed up. I eventually fixed this by booting into CWR mounting system and using adb to repush /system/xbin/su and setting permissions and making the new symlinked su file in /system/bin just like the last lines of Dan's Thinkpad root bat file did.
Here is a modified update.zip that should delete your Superuser files but keep your ClockworkMod Recovery. I think that with this file you can use OTA Rootkeeper to make a root backup, temp unroot, then boot into CWR and update to the new OTA then you should be able to reboot and use OTA Rootkeeper to restore root and download Superuser from the market, while keeping CWR through the entire process.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
That being said I think it will work. I followed this guide to sign my update.
Original updater-script
Modified updater-script in the update.zip linked above (this one deletes Superuser /system/bin/su and /system/xbin/su but keeps CWR)
Modified updater-script that I flashed on my tablet (this one messed up my su but doesn't delete the files)
If you need a good online file locker join Dropbox here and we'll both get an extra 250mb of space.
Unfortunately that update.zip didn't work for me, game me an error in CWR.
Is the other method, replacing the update scrip in the OTA and trying it ?
freezepop said:
Unfortunately that update.zip didn't work for me, game me an error in CWR.
Is the other method, replacing the update scrip in the OTA and trying it ?
Click to expand...
Click to collapse
Depending on the error you can likely edit the updater-script yourself and successfully installed. Most errors are due to changes in system apps causing them to fail checks. If you remove an app check you should probably remove the corresponding patch for that app in the updater script. What error did you have?
Ok, here is a new version of OTA2 for US tablets that should be flashable in CWR and should keep CWR and root without requiring the use of OTA rootkeeper. I would still protect root with OTA Rootkeeper and temp unroot before updating (you can try it without temp unroot but it has caused some problems for other users). This update will still scan all your system apps so you need to restore or unfreeze any system apps that you deleted or froze using Ti Backup.
Instructions:
This update is for owners of US tablets with root and ClockworkMod Recovery. Make sure your battery is well charged before flashing this, a dead battery mid update can create major problems!
1. Install OTA Rootkeeper and protect root. You should now temp unroot. Users who did not temp un-root have had issues with su access after updating.
2. Download the update below and put it on your external sdcard
3. Restore any system apps that you have removed
4. Reboot into ClockworkMod Recovery (Shutdown Thinkpad, turn on and press vol+ repeatedly until you see booting recovery image)
5. I would also highly recommend making a nandroid backup if you have not previously done so.
6. Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
7. update.zip will run, it will check your system apps during the update and may fail if you have changed something, if so the error message should explain why
8. Reboot tablet; it will be a very long reboot. This is normal; it seems to take forever but just let it boot.
9. Use OTA Rootkeeper to restore root.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip
jhankinson said:
Ok, here is a new version of OTA2 for US tablets that should be flashable in CWR and should keep CWR and root without requiring the use of OTA rootkeeper. I would still protect root with OTA Rootkeeper just in case something goes wrong but don't temp unroot before updating and see if root still works after the update. This update will still scan all your system apps so you need to restore or unfreeze any system apps that you deleted or froze using Ti Backup.
Instructions:
This update is for owners of US tablets with root and ClockworkMod Recovery. Make sure your battery is well charged before flashing this, a dead battery mid update can create major problems!
1. Install OTA Rootkeeper and protect root (just in case), you shouldn't need to temp unroot though with this update.
2. Download the update below and put it on your external sdcard
3. Restore any system apps that you have removed
4. Reboot into ClockworkMod Recovery (Shutdown Thinkpad, turn on and press vol+ repeatedly until you see booting recovery image)
5. I would also highly recommend making a nandroid backup if you have not previously done so.
6. Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
7. update.zip will run, it will check your system apps during the update and may fail if you have changed something, if so the error message should explain why
8. Reboot tablet; it will be a very long reboot. This is normal; it seems to take forever but just let it boot.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip
Click to expand...
Click to collapse
Thank you for your work. I have ROW version and waiting OTA2 for that, but still now I know how to modify update-script. I have a question, why not to remove any unneeded software from update and remove check for installed software which are already removed?
redbaron said:
Thank you for your work. I have ROW version and waiting OTA2 for that, but still now I know how to modify update-script. I have a question, why not to remove any unneeded software from update and remove check for installed software which are already removed?
Click to expand...
Click to collapse
Different people have removed different apps so one person may want the patch while another might want it skipped. I was just posting a generic version here that works for stock system apps. If others want to further customize their script then they are welcome improve upon it or customize it for their own system.
jhankinson said:
Ok, here is a new version of OTA2 for US tablets that should be flashable in CWR and should keep CWR and root without requiring the use of OTA rootkeeper. I would still protect root with OTA Rootkeeper just in case something goes wrong but don't temp unroot before updating and see if root still works after the update. This update will still scan all your system apps so you need to restore or unfreeze any system apps that you deleted or froze using Ti Backup.
Instructions:
This update is for owners of US tablets with root and ClockworkMod Recovery. Make sure your battery is well charged before flashing this, a dead battery mid update can create major problems!
1. Install OTA Rootkeeper and protect root (just in case), you shouldn't need to temp unroot though with this update.
2. Download the update below and put it on your external sdcard
3. Restore any system apps that you have removed
4. Reboot into ClockworkMod Recovery (Shutdown Thinkpad, turn on and press vol+ repeatedly until you see booting recovery image)
5. I would also highly recommend making a nandroid backup if you have not previously done so.
6. Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
7. update.zip will run, it will check your system apps during the update and may fail if you have changed something, if so the error message should explain why
8. Reboot tablet; it will be a very long reboot. This is normal; it seems to take forever but just let it boot.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip
Click to expand...
Click to collapse
I flashed this zip. It didn't delete su or Superuser.apk, yet apps cannot get root access afterward. any suggestions?
mandrsn1 said:
I flashed this zip. It didn't delete su or Superuser.apk, yet apps cannot get root access afterward. any suggestions?
Click to expand...
Click to collapse
That is what happened to me originally, it can be fixed though. Did you make a backup with OTA Rootkeeper? If so open Android Terminal emulator and type:
/system/su-backup
mount -o remount,rw /system
cp -f /system/su-backup /system/xbin/su
ln -s /system/xbin/su /system/bin/su
chown root /system/xbin/su
chmod 6755 /system/xbin/su
Then reboot your tablet. I believe this should fix your root access. If you don't have a backup I think you can also fix it by running adb while booted into CWR. I can give you those instructions if this doesn't work.
Apparently you should temp un-root before installing my update then restore your su backup with OTA Rootkeeper after updating.
You wear the crown
Thanks for posting the fix, too. Waiting for reboot to finish.
Really appreciate all your hard work. The instructions you posted for me in thinkpad forums worked perfectly and I learned a lot in the process.
toenail_flicker said:
Thanks for posting the fix, too. Waiting for reboot to finish.
Really appreciate all your hard work. The instructions you posted for me in thinkpad forums worked perfectly and I learned a lot in the process.
Click to expand...
Click to collapse
Did the fix work for you?
Still waiting for reboot. I waited about 20 minutes and rebooted manually. So far it still hasn't made it in for me to try the fix.
---------- Post added at 09:58 PM ---------- Previous post was at 09:44 PM ----------
jhankinson said:
Did the fix work for you?
Click to expand...
Click to collapse
Fix not yet working. Got this far
/system/su-backup
mount -o remount,rw /system
cp -f /system/su-backup /system/xbin/su
error message
cp: applet not found
Any ideas?
toenail_flicker said:
Still waiting for reboot. I waited about 20 minutes and rebooted manually. So far it still hasn't made it in for me to try the fix.
---------- Post added at 09:58 PM ---------- Previous post was at 09:44 PM ----------
Fix not yet working. Got this far
/system/su-backup
mount -o remount,rw /system
cp -f /system/su-backup /system/xbin/su
error message
cp: applet not found
Any ideas?
Click to expand...
Click to collapse
try
busybox cp -f /system/su-backup /system/xbin/su
may have to type busybox before some of the other commands too if they give an error.
So my line would be
busybox cp -f /system/su-backup /system/xbin/su
cp: applet not found
Just a quick note of thanks for getting me through this. Root is wonderful!
If
cp -f /system/su-backup /system/xbin/su
fails, use
dd if=/system/su-backup of=/system/xbin/su
instead.
jhankinson said:
Ok, here is a new version of OTA2 for US tablets that should be flashable in CWR and should keep CWR and root without requiring the use of OTA rootkeeper. I would still protect root with OTA Rootkeeper just in case something goes wrong but don't temp unroot before updating and see if root still works after the update. This update will still scan all your system apps so you need to restore or unfreeze any system apps that you deleted or froze using Ti Backup.
Instructions:
This update is for owners of US tablets with root and ClockworkMod Recovery. Make sure your battery is well charged before flashing this, a dead battery mid update can create major problems!
1. Install OTA Rootkeeper and protect root. You should now temp unroot. Users who did not temp un-root have had issues with su access after updating.
2. Download the update below and put it on your external sdcard
3. Restore any system apps that you have removed
4. Reboot into ClockworkMod Recovery (Shutdown Thinkpad, turn on and press vol+ repeatedly until you see booting recovery image)
5. I would also highly recommend making a nandroid backup if you have not previously done so.
6. Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
7. update.zip will run, it will check your system apps during the update and may fail if you have changed something, if so the error message should explain why
8. Reboot tablet; it will be a very long reboot. This is normal; it seems to take forever but just let it boot.
9. Use OTA Rootkeeper to restore root.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip
Click to expand...
Click to collapse
Thx jhankinson, this work for me. my TPT 1838 US.
Does anyone know an alternative method to getting CWM or rooting you phone because i updated my android to the official 2.3 update
and now i cant do anything and it says im not rooted when i am so could someone give me a link to get CWM without connecting it to the computer via USB?
Thanks!
You can replace the recovery.img, which is on .cust_backup/image with a file explorer with root access from the device(e.g es file explorer, root explorer...). You also need the "remount" app(you can find it on google play).
You must first run remount app, find the .cust_backup and remount it as rw. Then just copy the cmw recovery.img(from sd card in which you have previously put it) to the .cust_backup/image folder with the help of file explorer app.
need more info, what phone type?, what 2.3.5 upgrade did you use? if it is B526 or below, get hold of super one click 2.3.3(I think) and use it to root the phone, there is a thread on how to do this in the u8800 android development section. Then do as above and copy the recovery.img into the correct folder. Reboot and you will have cwm recovery.
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.