I am on stock, but rooted, nexus 7 4.2.2. I got notification of the software update sometime last week. I decided I would update. First, of course, I made a full nandoid backup, and titannium backup of all my apps and data. I downloaded rootkeeper and using rootkeeper "unrooted" and set about updating.
The Nexus rebooted, and entered the custom recovery mode (I think it is Amon RA) and then the update failed.
How can I update? What are your thoughts on the update? If I should avoid updating, how can I get rid of the software upgrade nag?
wiredwrx said:
I am on stock, but rooted, nexus 7 4.2.2. I got notification of the software update sometime last week. I decided I would update. First, of course, I made a full nandoid backup, and titannium backup of all my apps and data. I downloaded rootkeeper and using rootkeeper "unrooted" and set about updating.
The Nexus rebooted, and entered the custom recovery mode (I think it is Amon RA) and then the update failed.
How can I update? What are your thoughts on the update? If I should avoid updating, how can I get rid of the software upgrade nag?
Click to expand...
Click to collapse
You would need stock Android recovery for it to work I believe, so if you have a custom recovery, that is why it failed.
RMarkwald said:
You would need stock Android recovery for it to work I believe, so if you have a custom recovery, that is why it failed.
Click to expand...
Click to collapse
Thanks. I will look into that. Any thoughts on the update?
wiredwrx said:
Thanks. I will look into that. Any thoughts on the update?
Click to expand...
Click to collapse
You'd have to get stock Android recovery on there somehow, but if you're doing the official update and you removed any /system/app apps with Titanium Backup or anything, it'll also fail. If you flashed a custom kernel, it'll fail as well. Official updates run system checks to see that the stock files are all there and the correct versions.
You could backup everything you want to save on internal sd card (pictures/music etc), and flash the official factory Google images via fastboot. Or flash custom recovery and flash a 4.2.2 ROM. Either way, you'll have to wipe everything so you'll loose apps and app data, which you'll have to re-install again.
wiredwrx said:
The Nexus rebooted, and entered the custom recovery mode (I think it is Amon RA) and then the update failed.
Click to expand...
Click to collapse
The reason it failed is given in the recovery log file located at /cache/recovery/recovery.log
In general, OTAs are meant for 100% stock devices. When someone attempts an OTA on a rooted device, it can fail for hundreds of independent reasons - usually files in /system that got altered or removed by various root-privileged apps. (Sometimes it is not apparent to the end user that their root-using apps have even made such changes). In the current JOP40D -> JDQ39 OTA, the boot partition is also checked, so the OTA will certainly fail if you are using a custom kernel (in addition to any issues with modified files in /system).
Sounds like you are a person who makes Nandroid backups; good for you. If you have a Nandroid backup taken immediately after rooting (before any of these changes took place), it is possible that you could replace the altered files (by pulling the unaltered versions out of the old Nandroid Backups). Unfortunately, it is hard to know how much work this will be**, because during the initial check sequence that the OTA performs, it halts on the first error encountered. There could be only a single altered file causing trouble, several, or many.
** If you use TWRP recovery, the system (& data) image backups are tar files - you don't even need to restore an old backup to retrieve files from other backups.
As you mentioned TiBu, it sounds like your are farmiliar with all this stuff already. Rather than hand-patching your existing ROM, perhaps the right thing to do is to
- Make your TiBu & Nandroid Backups of your current ROM
- Install 4.2.2 factory image & Re-Root
- Make a Nandroid Backup of this (vanilla stock) ROM before you even boot it
- Boot it and restore your Market Apps. (I'm not a big fan of restoring System Apps or their data).
good luck
bftb0 said:
The reason it failed is given in the recovery log file located at /cache/recovery/recovery.log
In general, OTAs are meant for 100% stock devices. When someone attempts an OTA on a rooted device, it can fail for hundreds of independent reasons - usually files in /system that got altered or removed by various root-privileged apps. (Sometimes it is not apparent to the end user that their root-using apps have even made such changes). In the current JOP40D -> JDQ39 OTA, the boot partition is also checked, so the OTA will certainly fail if you are using a custom kernel (in addition to any issues with modified files in /system).
Sounds like you are a person who makes Nandroid backups; good for you. If you have a Nandroid backup taken immediately after rooting (before any of these changes took place), it is possible that you could replace the altered files (by pulling the unaltered versions out of the old Nandroid Backups). Unfortunately, it is hard to know how much work this will be**, because during the initial check sequence that the OTA performs, it halts on the first error encountered. There could be only a single altered file causing trouble, several, or many.
** If you use TWRP recovery, the system (& data) image backups are tar files - you don't even need to restore an old backup to retrieve files from other backups.
As you mentioned TiBu, it sounds like your are farmiliar with all this stuff already. Rather than hand-patching your existing ROM, perhaps the right thing to do is to
- Make your TiBu & Nandroid Backups of your current ROM
- Install 4.2.2 factory image & Re-Root
- Make a Nandroid Backup of this (vanilla stock) ROM before you even boot it
- Boot it and restore your Market Apps. (I'm not a big fan of restoring System Apps or their data).
good luck
Click to expand...
Click to collapse
Thanks for the detailed breakdown. I may just update with your instructions. Are you aware of a way to suppress the nag screen.
Related
Rooted my G2 in December 2010 but did not install any custom ROMs on it. I have SuperUser and ClockWork Mod on it. The OTA 2.3.3 update finally made its way to my phone, but does not update because of root.
I have seen too many threads explaining how to update the phone, leaving me confused Can somebody please explain how to or point me to a relevant thread.
Thanks.
There are pre-rooted versions posted in Development. Just download from there, put on your SD card, and flash from ROM Manager. You are also S-Off?
If you install an official ROM, you lose root. You don't want that.
redpoint73 said:
You are also S-Off?
Click to expand...
Click to collapse
Yes, I am S-Off
FullScreen57 said:
Yes, I am S-Off
Click to expand...
Click to collapse
I used this one: http://forum.xda-developers.com/showthread.php?t=1211143
bone stock pre-rooted OTA. Flash through CWM recovery. Doesn't replace Radio or anything. Its just a ROM.zip you can flash. Wipe data/factory reset before flashing of course.
Thanks redpoint73 and martonikaj for your help. I was able to update the ROM.
One last question for the folks here, I performed a Titanium Pro Backup before upgrading the ROM.
Which one of the following restores should I perform now that I have upgraded to 2.3.4?
1. Restore missing apps with data
2. Restore all system data
3. Restore missing apps + all system data
4. Restore newer versions of user apps
5. Restore all apps with data
Thanks.
FullScreen57 said:
Thanks redpoint73 and martonikaj for your help. I was able to update the ROM.
One last question for the folks here, I performed a Titanium Pro Backup before upgrading the ROM.
Which one of the following restores should I perform now that I have upgraded to 2.3.4?
1. Restore missing apps with data
2. Restore all system data
3. Restore missing apps + all system data
4. Restore newer versions of user apps
5. Restore all apps with data
Click to expand...
Click to collapse
I usually do 5. Restore all apps with data when moving to a new ROM. (never restore system data unless you're re-flashing the same ROM). I usually select it, then scroll through the list and uncheck some apps that may cause issues. Things like Clocks, Browsers, etc. often overwrite system-level apps and can cause problems. YMMV.
Its in your best interest to perform a nandroid backup before doing a big restore of 100's of apps, as there is a chance that there may be some problems or incompatibilities that cause issues, and you want to be able to go back to a state before installing all those apps to troubleshoot without having to re-flash the entire ROM.
Hello,
My device is a NEXUS 7 3G (GSM / HSPA +) and am using Twrp recovery and have a question about backup menu.
Are the default options checked enough (Boot, System and Data)? Do I click check the radio option? When it is necessary the radio option?
I Know cache and recovery are not necessary but the question is the radio.
Thanks and sorry for my writing in English, very poor ... sorry
It would be rather unusual for a radio to be flashed by anything other than a factory ROM; so the need to be restoring it is somewhat unusual.
As with the bootloader, it is probably best to minimize the amount of flashing you do of the radio partition.
TWRP also lets you choose which partitions are restored using the same toggles, so even if it were present in a backup, I don't think TWRP forces you to restore it.
I have a grouper (not tilapia) N7, and (besides more typical ROM backups) I keep a pure-stock, completely unconfigured ROM TWRP backup including the stock recovery standing by (plus a copy stored safely off the device).
I think having pure stock backups is something everybody should do. Not only for factory return scenarios, but also for applying OTAs (make custom ROM backup, revert to pure stock, apply OTA, capture yet another pure-stock backup, restore back to custom ROM). This gets you:
- return to stock any time
- for RMA / relock scenarios
- no problem OTA installs
- reference stock ROMs from every release (for restoring individual stock files)
good luck.
bftb0 said:
It would be rather unusual for a radio to be flashed by anything other than a factory ROM; so the need to be restoring it is somewhat unusual.
As with the bootloader, it is probably best to minimize the amount of flashing you do of the radio partition.
TWRP also lets you choose which partitions are restored using the same toggles, so even if it were present in a backup, I don't think TWRP forces you to restore it.
I have a grouper (not tilapia) N7, and (besides more typical ROM backups) I keep a pure-stock, completely unconfigured ROM TWRP backup including the stock recovery standing by (plus a copy stored safely off the device).
I think having pure stock backups is something everybody should do. Not only for factory return scenarios, but also for applying OTAs (make custom ROM backup, revert to pure stock, apply OTA, capture yet another pure-stock backup, restore back to custom ROM). This gets you:
- return to stock any time
- for RMA / relock scenarios
- no problem OTA installs
- reference stock ROMs from every release (for restoring individual stock files)
good luck.
Click to expand...
Click to collapse
Thank you very much for the reply. Now I have the bootloader open and I'm leaving the tablet as I like and I intend to make a backup before root.
Thanks
Hi all,
I have a nexus 7 running Android 4.1.2 stock w/ root. Some months ago, I disabled the OTA update notification - but I can't seem to remember how!
I want to now re-enable OTA updates so that I can update to the latest android version, and not lose my installed apps.
I've searched the device for FOTAKill.apk inside /system/app, and its not found
I've also searched for frozen / hidden apps using Titanium Backup Pro... nothing
When I enter Settings -> About Tablet -> System Updates... it says I'm up to date... but I'm not, considering I'm running 4.1.2.
Any help or pointers in re-enabling OTA is appreciated!!
- make a full nandroid backup.
- using fastboot, flash the system.img file from the 4.2.2 factory image to the system partition.
- using your custom recovery, reflash a SuperSU root kit bundle.
- using the custom recovery, wipe cache and dalvik-cache.
If you don't like the result, restore the nandroid backup and proceed in a different fashion. It will probably break things like stickmount and any other changes that you caused in /system.
Note the above method is for use by lazy and sloppy users. A better approach is to make TiBu backups of only your market apps, bite the bullet, and start from scratch with a flash & (new) configuration of a pure stock ROM. In any case, every conceivable procedure should start with making a full nandroid backup and getting it copied to a safe place off the tablet.
I will also say that unless odd problems crop up, the portions of the factory install procedure (using fastboot) that deal with erasure or flashing of the userdata partition should be skipped, as these steps completely wipe your /data storage - including your /sdcard area in /data/media/0 and any CWM/TWRP nandroid backups!
It's not really clear why these steps would be needed unless the /data ext4 filesystem in the userdata partition got corrupted somehow. A more sly approach would be to use the custom recovery's "factory reset" procedure to clean up /data - either before or after flashing the factory ROM - and completely skip anything that touches the userdata partition in the factory install instructions.
good luck
Sorry guys may I ask a question relative to restoring apps via TiBU?
Before flashing stock 4.3 I had updated TiBU and backed up my apk's+data
Wiped everything to have a clean slate for TRIM to work perfectly and I've started to restore my apps.
TIBU takes forever to install a single apk, actually never ends.
Reboot.....
If I try to install apk from the market and then restore only the data from TiBU the app crashes.
After that I cannot reinstall the app anymore even from the play store.
Is there a way to overcome this?
Thanks
PS: I have already tried the solution Menu/Preferences/backup folder location
PS2: Nexus 4 - built JWR66Y - FRANCO r178
vagos696 said:
Sorry guys may I ask a question relative to restoring apps via TiBU?
Before flashing stock 4.3 I had updated TiBU and backed up my apk's+data
Wiped everything to have a clean slate for TRIM to work perfectly and I've started to restore my apps.
TIBU takes forever to install a single apk, actually never ends.
Reboot.....
If I try to install apk from the market and then restore only the data from TiBU the app crashes.
After that I cannot reinstall the app anymore even from the play store.
Is there a way to overcome this?
Thanks
PS: I have already tried the solution Menu/Preferences/backup folder location
PS2: Nexus 4 - built JWR66Y - FRANCO r178
Click to expand...
Click to collapse
I don't trust TiBU. its a real mess for me. I for one backup my ANDROID folder, and flash all apps through recovery. and then copy back the Android folder on SDCARD.
How did you root your 4.3 image? Many custom kernels break root on 4.3. Try re-flashing SuperSU or re-flash ROM and stick to the stock kernel.
via Nexus Toolkit. I'm still rooted even after applied Franco, but I'll revert back to stock kernel just to check your possibility.
Even the saved TiBU apk's are not getting installed.
How can I re-install the broken apps which were affected from TiBU? As I mentioned even fresh installation from the play store is not processed.
I was hoping to avoid re-flashing and re-rooting from scratch.
Nope even with stock kernel I face the same problems. Any suggestions?
I guess there's something wrong with your /data partition. I'd either start over with flashing the factory image or at least format /data (not wipe, really format). Don't forget to backup your internal sdcard content first, it will be deleted with both methods.
Also I'd recommend not using a toolkit for flashing the factory image and rooting. It's easy enough using fastboot and a custom recovery. This way you'll be on the safe side, not missing any errors etc.
Make sure your TiBU directory is set to storage/emulated/legacy/TitaniumBackup, not storage/emulated/0/TitaniumBackup.
It worked for me, anyway. Well, after having to perform a factory reset, as it screwed up the UUIDs, that is
Thanks for the suggestion. You were right my path was storage/emulated/0/TitaniumBackup.
I revert it to the suggested one but I have the same issue.
Factory reset, start from scratch, initial path storage/emulated/legacy/TitaniumBackup
The same problem which also end up destroying the fresh apk as well.
Hopeless
Tell us exactly what you're doing. Which ROM / image, software, versions, procedure, all the details. Maybe something other well ring a bell.
As already quoted
1. Before updating to 4.3, I updated TiBU to the latest version and kept backup of the apps+data
2. Clean flash of stock 4.3 ROM (JWR66Y) via Nexus Toolkit
3. Root (Busybox, SU etc)
4. Flashing Franco Kernel r178
5. Installation of TiBU
6. Try to restore - PROBLEM
Plan B:
1. Factory Data Reset
2. BusyBox gone but still have root access
3. Stock ROM - Stock Kernel - Rooted
4. Install TiBU
5. Restoring - PROBLEM
Description of the PROBLEM:
I cannot restore apk's is getting into a loop and never ends.
I can restore data to an installed apk, but then the app crashes
I cannot re-install the (restored) app via playstore, I get "unknown error code during installation -24-"
Current situation
1. Factory Data Reset again
2. Franco r178
3. No restores via TiBU
Don't shoot me, but it still sounds like the TiBu 4.3 ROM backup folder path problem. Here's what I do and what works for me:
1. Open TiBu
2. Click on "Menu"
3. Click on "Preferences"
4. Click on "Backup folder location"
5. Click on "DETECT!"
6. Click on "Whole device"
7. Choose "/storage/emulated/legacy/TitaniumBackup"
8. Click on "Use the current folder"
9. TiBu will now ask if it should move the other backups to the new folder, say no.
10. Exit the preferences with the back key
11. TiBu will now reload with the new preferences
Now restoring should work if the path is the problem.
About loosing root with a custom kernel on 4.3 ROMs:
If you lose root by flashing a custom kernel it may still seem like root is active, i.e. the root frontend app will still be there and ask for root permissions etc. Try the following to ensure that TiBu is running with full root privileges: Uninstall some unimportant system application (some Gapp for example, like Google Currents - backup first if you need it). If uninstalling gets cancelled with a message like "Can't find the apk file", it's likely that root doesn't work properly.
Come on man, I hate to give up
Thanks for the inspiration but unfortunately:
1. I can unistall, backup and restore properly Google Currents (hence proper root)
2. Back up folder was set properly also by verifying your steps (2-10)
And again if I try to restore an old app (not the data) it gets to the familiar loop.
Ok. I'd now flash the full factory image, thus resetting every partition (backup internal sdcard first). Please try without a toolkit to be safe. You need the drivers installed (your toolkit should already have taken care of that) and have adb and fastboot ready. There are batch/shell scripts included in the factory image which invoke the fastboot commands in one step.
Next flash a custom recovery with fastboot and use it to flash SuperSU for root access.
Refrain from flashing a custom kernel now and try if you can successfully restore with TiBu at this point.
If you can, the problem was either one of your partitions/filesystems f_cked up or the toolkit doing something wrong.
I currently have JB MJE rooted with Kingo on my Note 3. I am constantly getting a software update notice popup that will most certainly update my phone to KK with NC4 bootloader. When I first got the message, I accepted the OTA update, but the update failed because the phone is rooted; which I am glad it failed. After spending the past few days reading up on several threads in this forum, I would prefer to do my own update to KK so I can restrict the update of the bootloader to NC2, rather than NC4, so I can keep the option of going back to JB.
In the main thread that I've been reading, http://forum.xda-developers.com/showthread.php?t=2787627, bigzilla recommended to people who were having trouble updating to KK that they should follow the instructions for updating by Odin the MJE tar, then use Kingo to root the phone (which would put a person into the same state that I have). Then, go through the MJE to NC2 KK update described in this thread
http://forum.xda-developers.com/showthread.php?t=2726558
I would have (and might still) followed those instructions except for one thing... I would prefer not to completely wipe data factory reset my phone. I have a number of apps & games that I would prefer to not lose all the data (e.g., high scores, levels completed, badges earned, etc..).
So, my question is two-fold. Is there a way for me to update to KK with NC2 bootloader without having to wipe data factory reset the phone and without tripping KNOX? And, if not, is there a way to back up my apps & data and then restore them after the factory reset? For example, use Titanium Backup to make full backup to extSD beforehand. And then, afterwards, reinstall Titanium and use the earlier backup from extSD to reinstall the apps & data. In theory, the latter seems like it should work, but I've not tried it myself so would rather ask the experts here before I do anything rash.
donkyflip said:
I currently have JB MJE rooted with Kingo on my Note 3. I am constantly getting a software update notice popup that will most certainly update my phone to KK with NC4 bootloader. When I first got the message, I accepted the OTA update, but the update failed because the phone is rooted; which I am glad it failed. After spending the past few days reading up on several threads in this forum, I would prefer to do my own update to KK so I can restrict the update of the bootloader to NC2, rather than NC4, so I can keep the option of going back to JB.
In the main thread that I've been reading, http://forum.xda-developers.com/showthread.php?t=2787627, bigzilla recommended to people who were having trouble updating to KK that they should follow the instructions for updating by Odin the MJE tar, then use Kingo to root the phone (which would put a person into the same state that I have). Then, go through the MJE to NC2 KK update described in this thread
http://forum.xda-developers.com/showthread.php?t=2726558
I would have (and might still) followed those instructions except for one thing... I would prefer not to completely wipe data factory reset my phone. I have a number of apps & games that I would prefer to not lose all the data (e.g., high scores, levels completed, badges earned, etc..).
So, my question is two-fold. Is there a way for me to update to KK with NC2 bootloader without having to wipe data factory reset the phone and without tripping KNOX? And, if not, is there a way to back up my apps & data and then restore them after the factory reset? For example, use Titanium Backup to make full backup to extSD beforehand. And then, afterwards, reinstall Titanium and use the earlier backup from extSD to reinstall the apps & data. In theory, the latter seems like it should work, but I've not tried it myself so would rather ask the experts here before I do anything rash.
Click to expand...
Click to collapse
Get Tibu paid. Backup your apps. Use Tibu batch to make a flashable zip of your backup. Move that to your external sd and flash after your done... ��. I'm at the gym right now, I'll give the post with instructions when I get home.
Edit : Here you go,
1) Get Titanium Backup paid version. If you're going to be flashing roms it's a no brainer.
1.5) Change titanium backup location to external sd card. I mistakenly wiped my internal once and lost everything.
2) I use batch backup of user apps only. I don't do system apps.
3) Go through Tibu and make sure things you want are backed up, for example Chrome bookmarks don't backup in batch mode you have to do it manually. Check for any games you have, etc.
4) Go to Batch mode> Recovery mode> Run create an update zip+data backup
5) Check and make sure what you want is there before zip is made.
6) Make zip, once it's done you will have an update.zip on your internal storage. I rename the zip and move to my external sd card. Depending on how many apps it should be over 1gb to say the least but it depends on how many apps it is.
7) Once you're done you can do your NC2 upgrade, it won't trip knox so just take your time, follow the instructions and find any youtube videos on it. There are some in the thread on how to do it.
8) Once you're done with that and you're on the custom rom of your choice install Tibu from market. Change default location to your external sd card tibu location.
9) Reboot rom into safe strap, wipe cache & dalvik cache, flash your backup zip(whatever you named it or it will be update.zip)
10 Once it's flashed restart phone...:victory::victory::victory:
I can't take any credit for this. I learned it in the Baja rom now Alliance thread. I do this with Tibu before I flash any new rom now.
EDIT: MAKE SURE YOU ARE USING RETAIL NOTE 3 KK UPGRADE IF YOU HAVE A RETAIL NOTE 3 AND DEVELOPER STEPS FOR DEVELOPER NOTE 3 OR YOU WILL POSSIBLY BRICK YOUR PHONE!!
I'm not yelling at you but I want to make sure you don't brick your phone.
Sent by Darkseid from Apokolips
thegamerdarkseid said:
Get Tibu paid. Backup your apps. Use Tibu batch to make a flashable zip of your backup. Move that to your external sd and flash after your done... ��. I'm at the gym right now, I'll give the post with instructions when I get home.
Edit : Here you go,
1) Get Titanium Backup paid version. If you're going to be flashing roms it's a no brainer.
1.5) Change titanium backup location to external sd card. I mistakenly wiped my internal once and lost everything.
2) I use batch backup of user apps only. I don't do system apps.
3) Go through Tibu and make sure things you want are backed up, for example Chrome bookmarks don't backup in batch mode you have to do it manually. Check for any games you have, etc.
4) Go to Batch mode> Recovery mode> Run create an update zip+data backup
5) Check and make sure what you want is there before zip is made.
6) Make zip, once it's done you will have an update.zip on your internal storage. I rename the zip and move to my external sd card. Depending on how many apps it should be over 1gb to say the least but it depends on how many apps it is.
7) Once you're done you can do your NC2 upgrade, it won't trip knox so just take your time, follow the instructions and find any youtube videos on it. There are some in the thread on how to do it.
8) Once you're done with that and you're on the custom rom of your choice install Tibu from market. Change default location to your external sd card tibu location.
9) Reboot rom into safe strap, wipe cache & dalvik cache, flash your backup zip(whatever you named it or it will be update.zip)
10 Once it's flashed restart phone...:victory::victory::victory:
I can't take any credit for this. I learned it in the Baja rom now Alliance thread. I do this with Tibu before I flash any new rom now.
EDIT: MAKE SURE YOU ARE USING RETAIL NOTE 3 KK UPGRADE IF YOU HAVE A RETAIL NOTE 3 AND DEVELOPER STEPS FOR DEVELOPER NOTE 3 OR YOU WILL POSSIBLY BRICK YOUR PHONE!!
I'm not yelling at you but I want to make sure you don't brick your phone.
Sent by Darkseid from Apokolips
Click to expand...
Click to collapse
Thank you so much for confirming that restoring with TiBU will bring back all my apps & games with their data. I would not have thought to use Safe Strap to flash the backup zip. I'll give it a go this evening.
Also, to answer another part of your question. No, it will not trip knox.
donkyflip said:
Thank you so much for confirming that restoring with TiBU will bring back all my apps & games with their data. I would not have thought to use Safe Strap to flash the backup zip. I'll give it a go this evening.
Click to expand...
Click to collapse
Me neither, I've done something similar in trwp on my s3 but I never knew Tibu did it. There are some awesome guys on here.
Sent by Darkseid from Apokolips
Just a quick follow up. I was able to successfully update from JB MJE to the leaked KK NC2, and then updated to KK NC4 (keeping the NC2 bootloader). Per the instructions, I did wipe memory. I also made backups of my apps + data beforehand. I also created an update.zip using the TiBU restore batch action.
However, I was not able to figure out how to use SafeStrap to flash the update.zip. The good news, though, is that I did successfully use the TiBU batch action to restore all the apps from the backup on the extSD (not the update.zip). Everything is back to the way it was before the android update, except now I'm running KK rather than JB.
I would like to know how to use SS to flash my apps so I can use the update.zip.
thegamerdarkseid - Can you provide a little more detailed documentation for how to flash a TiBU update.zip to a new ROM?
donkyflip said:
Just a quick follow up. I was able to successfully update from JB MJE to the leaked KK NC2, and then updated to KK NC4 (keeping the NC2 bootloader). Per the instructions, I did wipe memory. I also made backups of my apps + data beforehand. I also created an update.zip using the TiBU restore batch action.
However, I was not able to figure out how to use SafeStrap to flash the update.zip. The good news, though, is that I did successfully use the TiBU batch action to restore all the apps from the backup on the extSD (not the update.zip). Everything is back to the way it was before the android update, except now I'm running KK rather than JB.
I would like to know how to use SS to flash my apps so I can use the update.zip.
thegamerdarkseid - Can you provide a little more detailed documentation for how to flash a TiBU update.zip to a new ROM?
Click to expand...
Click to collapse
You would go to "Install" in SafeStrap, locate the update.zip file that you made with TiBu and flash. Depending on the location of the folder where your TiBu would have put the file, you can navigate thru the folder directories to locate the zip file in SafeStrap. I would locate the folder first, or move it to the External SD card for quick access. That way, when you do go to flash, you can just locate the ExtSD card directory in SafeStrap and flash it.
shaggy_kobain said:
You would go to "Install" in SafeStrap, locate the update.zip file that you made with TiBu and flash. Depending on the location of the folder where your TiBu would have put the file, you can navigate thru the folder directories to locate the zip file in SafeStrap. I would locate the folder first, or move it to the External SD card for quick access. That way, when you do go to flash, you can just locate the ExtSD card directory in SafeStrap and flash it.
Click to expand...
Click to collapse
Thanks Shaggy...:good::highfive::good:
---------- Post added at 11:20 AM ---------- Previous post was at 11:17 AM ----------
donkyflip said:
Just a quick follow up. I was able to successfully update from JB MJE to the leaked KK NC2, and then updated to KK NC4 (keeping the NC2 bootloader). Per the instructions, I did wipe memory. I also made backups of my apps + data beforehand. I also created an update.zip using the TiBU restore batch action.
However, I was not able to figure out how to use SafeStrap to flash the update.zip. The good news, though, is that I did successfully use the TiBU batch action to restore all the apps from the backup on the extSD (not the update.zip). Everything is back to the way it was before the android update, except now I'm running KK rather than JB.
I would like to know how to use SS to flash my apps so I can use the update.zip.
thegamerdarkseid - Can you provide a little more detailed documentation for how to flash a TiBU update.zip to a new ROM?
Click to expand...
Click to collapse
Glad that worked out for you, that's what's up!!...