Develop Bugs

[Q] Easiest way to get out of this boot loop?

Specs: I had Galaxy Nexus LTE 4.0.4 w/ unlocked bootloader and root access. I have the GN toolkit if that helps.
Cause: I used the Font Installer app to change system font. I now know that not all of the fonts are working properly and emailed the developer about it. However, I am currently stuck in a boot loop after changing to one of the fonts.
I would prefer to not lose everything and if I didn't care about that, then I would just go for it and I think that I could get it working again. But since it was just a font change, I thought it might be possible to fix it without going through all of that. I am hoping I can just change some system files or something and get it to boot then select a different .tff font that I know works. THANKS!
If I reload the 4.04 update.zip that I still can access, will that wipe everything/will I have to re-setup a bunch of things? Is it OK to clear cache partition and Dalvik Cache? Thank you.

Did you take a nandroid backup of this ROM at any point? If so, you could do an advanced restore of system only.
Sent from my Galaxy Nexus using Tapatalk

cmstlist said:
Did you take a nandroid backup of this ROM at any point? If so, you could do an advanced restore of system only.
Click to expand...
Click to collapse
No, unfortunately I did not, but I will look into that once I am back up and running.
**EDIT: I have CWM Recovery v5.5.0.4 running now. Is it possible to do a backup at THIS point in time and then restore everything but system?

Druas said:
No, unfortunately I did not, but I will look into that once I am back up and running.
**EDIT: I have CWM Recovery v5.5.0.4 running now. Is it possible to do a backup at THIS point in time and then only restore system?
Click to expand...
Click to collapse
Okay. In that case, flashing the ROM's update.zip should work and shouldn't wipe your data. Best to take a nandroid backup first, just in case of trouble.
Sent from my Galaxy Nexus using Tapatalk

cmstlist said:
Okay. In that case, flashing the ROM's update.zip should work and shouldn't wipe your data. Best to take a nandroid backup first, just in case of trouble.
Click to expand...
Click to collapse
Ok I made the backup first. When I try to load the update.zip though, it says, "assert failed: appy_patch_check("/system/fonts/Roboto-Regular.ttf" <then a whole BUNCH of numbers and letters which I can type out if they will actually be helpful> "E:Error in /sdcard/Download/update.zip (Status 7) Installation aborted."

Is that an incremental update.zip for upgrading? What you need is a zip containing the entire ROM.
Alternately use fastboot to flash system.img from the stock ROM if you were already using stock.
Sent from my Galaxy Nexus using Tapatalk

cmstlist said:
Is that an incremental update.zip for upgrading? What you need is a zip containing the entire ROM.
Click to expand...
Click to collapse
Yeah I used: http://forum.xda-developers.com/showthread.php?t=1481044 So I need to install 4.0.2 first? Unfortunately that is the only upgrade.zip I have on my phone and I don't know how to load new ones on there without booting into Android.
cmstlist said:
Alternately use fastboot to flash system.i mg from the stock ROM if you were already using stock.
Click to expand...
Click to collapse
What? Can you explain further? I was using stock 4.0.4

Druas said:
Yeah I used: http://forum.xda-developers.com/showthread.php?t=1481044 So I need to install 4.0.2 first? Unfortunately that is the only upgrade.zip I have on my phone and I don't know how to load new ones on there without booting into Android.
What? Can you explain further? I was using stock 4.0.4
Click to expand...
Click to collapse
You can download another zip to your computer and use adb push to get it onto the GN's internal storage.
I don't have the CDMA version but here's what I am able to find. Check this thread:
http://forum.xda-developers.com/showthread.php?t=1481613
A completely stock 4.0.4 (aside from root, busybox, de-odex) from that thread is here:
http://dev-host.org/uMJ
So you download that to your computer and put it in the same folder as adb. Boot the phone into Clockwork Recovery and then plug it into your computer. (There are other guides to getting adb to work on your phone so I won't cover that here.) Run adb devices to make sure it sees your phone. In Clockwork you also have to go to mounts and storage and make sure /data is mounted.
Then:
adb push GalaxyNexusCDMA-4.0.4-StockRootedNoRadio.zip /sdcard/stock.zip
Subsequently in Clockwork, you will be able to find that stock.zip in the list of zips you can apply. After applying that zip, any damage caused by messing with the fonts should be reverted.
---- or ----
The alternative would be to download the factory 4.0.2 image from here:
https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz
Inside that archive is a system.img file which you can flash to the phone by fastboot over USB. Immediately afterwards, you would then boot into CWM and apply the incremental update.zip you already have on there. This will take you to stock 4.0.4 unrooted and hopefully bootable!

cmstlist said:
The alternative would be to download the factory 4.0.2 image from here:
Inside that archive is a system.img file which you can flash to the phone by fastboot over USB. Immediately afterwards, you would then boot into CWM and apply the incremental update.zip you already have on there. This will take you to stock 4.0.4 unrooted and hopefully bootable!
Click to expand...
Click to collapse
While your instructions were good, I tried some things on my own about 20 min before you made that post and screwed up and erased userdata. So, I cannot say for sure if it would have worked, but I bet it would have and I wish I had been more patient.

Sorry to hear. Is it bootable now at least?
The userdata erase problem is why I now have to remember in every phone recovery situation - adb pull the entire contents of internal storage from within CWM before doing anything risky.
Sent from my Galaxy Nexus using Tapatalk

Yeah the phone has booted, I just have to spend some time recovering what I can. I will hopefully make better backups for the future. At least I learned some stuff. I still can't believe this was all caused by changing a FONT in a program designed to change fonts.

Druas said:
Yeah the phone has booted, I just have to spend some time recovering what I can. I will hopefully make better backups for the future. At least I learned some stuff. I still can't believe this was all caused by changing a FONT in a program designed to change fonts.
Click to expand...
Click to collapse
Right, well this font changer program edits the system partition of your phone, which makes it risky. In the future, the best course of action with any "risky" change is:
- Take a nandroid backup first.
- Copy the nandroid backup out of the phone (it's in a subfolder of clockworkmod on internal storage).
- If you are doing anything that leads you to fear that the whole internal storage could get blanked, copy all of that out of the phone too.
- Now if you can't boot, you can selectively restore the system partition or the whole thing to try and fix it.
- And now if your internal storage gets blanked, your backup is safe.

cmstlist said:
Right, well this font changer program edits the system partition of your phone, which makes it risky. In the future, the best course of action with any "risky" change is:
- Take a nandroid backup first.
- Copy the nandroid backup out of the phone (it's in a subfolder of clockworkmod on internal storage).
- If you are doing anything that leads you to fear that the whole internal storage could get blanked, copy all of that out of the phone too.
- Now if you can't boot, you can selectively restore the system partition or the whole thing to try and fix it.
- And now if your internal storage gets blanked, your backup is safe.
Click to expand...
Click to collapse
Yeah I had no idea that there was a significant risk involved, otherwise I would have been more cautious. Some questions I have:
-With Titanium Backup, the only thing I need to be running batch backups of is all user apps + system data correct? And only restore apps not system data unless I am on the exact same ROM as before?
-Again with TB, is there stuff it consistently misses that I should backup manually?
-I always launched CWM Recovery through the GN toolkit using "6. Flash CWM Recovery, Standard." And sometimes I would select Recovery from the Fastboot menu and it would be back at the regular recovery. Is there a different way I should have been going about getting to the nandroid backup?
-I have now installed ROM Manager and hit "Flash CWM Recovery" and I have a nandroid backup when I reboot into recovery. Does this mean any time I choose Recovery from the Fastboot menu that it will boot into CWM Recovery?
Thanks again for all your help and advice!

CWM 6.0.0.5 backup/restore question...

I just did a CWM backup of my awesome ROM before I flasha new one (like I always does) and noticed it backed up awfully fast.
I just flashed the new 6.0.0.5 touch recovery so I booted back into Android before flashing a new ROM and noticed my backup folder in CWM was 20 megs...
Did my ROM really get backed up with data? Is all the info now in the "blobs" folder?
I am honestly tempted to just reflash the older CWM and do a backup just in case.
Is this normal?

Normal.
Backups are handled VERY differently for CWM now.
From what I understand:
Each file is diffed from the backup you're currently making to any old backups.
If the file was modified...a copy is made for your new backup.
If it wasn't...a reference to the file is made so that it doesn't have to copy said file over...it just says: Yes. File exists...it's here.
This cuts down on the a)
TIME. By a lot.
b)
Size...of incremental backups.
Edit:
This is just how my brain is processing the new CWM's features.
I've read nothing that states how it works...all I know is that YES, the above sizes are normal.
I'm generally pretty close in my assumptions...but I'm not a dev. Just...intuitive.
So if I'm wrong ::: Don't shoot me.

Makes sense.
here goes nothing...

Have done some reading a yesterday about this since I wanted to see if this was worthy of leaving my Old Touch Recovery.
It was worthy because the one feature that caught my eye was that it makes files smaller by compressing and preventing duplicated files in a back up.
This is why the back up is smaller(ish) and faster to back up and restore.
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^

How can we safely delete old backups? I've read up on how it works, but it's still not clear. If I delete my oldest backup, will it render all the new ones useless because they don't have the duplicated files?

Well the ROM I flashed was fubar, couldn't get past the boot-animation, so I had to ADB enter recovery and did a CWM restore on 6.0.0.5 Touch, seems to work fine.

grantith said:
How can we safely delete old backups? I've read up on how it works, but it's still not clear. If I delete my oldest backup, will it render all the new ones useless because they don't have the duplicated files?
Click to expand...
Click to collapse
This is a good question. I'm thinking the same thing. If I have backup #1, #2, and #3 (the newest) where #3 is incremental differences from #1 and #2 will backup #3 be trash if I delete backup #1 and #2??

VTENGR said:
This is a good question. I'm thinking the same thing. If I have backup #1, #2, and #3 (the newest) where #3 is incremental differences from #1 and #2 will backup #3 be trash if I delete backup #1 and #2??
Click to expand...
Click to collapse
You delete the entire CWM folder and do a fresh backup.

Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1757146
"Simple delete the usual backup directory." Unfortunately I don't really get what that means. Any ideas?

grantith said:
How can we safely delete old backups? I've read up on how it works, but it's still not clear. If I delete my oldest backup, will it render all the new ones useless because they don't have the duplicated files?
Click to expand...
Click to collapse
Just to add, it looks like the app data and such is stored in the blobs folder, so if you delete an old "backup" from backup folder, but keep the blob folder intact, it will still restore fine.

grantith said:
http://forum.xda-developers.com/showthread.php?t=1757146
"Simple delete the usual backup directory." Unfortunately I don't really get what that means. Any ideas?
Click to expand...
Click to collapse
exactly what I just said above

This jump in recovery version confuses the hell out of me, I honestly don't understand it. I have 9 different rom's backed up on my phone and I want to update them but I've read stories of people having issues restoring old backups. My question is do I need restore to each rom with a version of clockworkmod 5 then flash clockworkmod 6 and back up with clockworkmod 6?

masully84 said:
This jump in recovery version confuses the hell out of me, I honestly don't understand it. I have 9 different rom's backed up on my phone and I want to update them but I've read stories of people having issues restoring old backups. My question is do I need restore to each rom with a version of clockworkmod 5 then flash clockworkmod 6 and back up with clockworkmod 6?
Click to expand...
Click to collapse
That's what I did.
Not sure if you "have to" but I didn't want to chance it.

orangekid said:
That's what I did.
Not sure if you "have to" but I didn't want to chance it.
Click to expand...
Click to collapse
Thanks man, yeah it seems like the safest way to approach it

masully84 said:
Thanks man, yeah it seems like the safest way to approach it
Click to expand...
Click to collapse
And it also sounds like it will conserve a lot of space because it won't double up on app data which matches your other ROMs.

[Q] CWM, TWRP, and Switching - Think I Understand, Just Want To Clarify

Hey guys, now that we can backup our IMEI (Thanks to peoplearmy and geek!) I feel like flashing roms like a mad man. But before I start I was wondering if theres any differences between the CWM and TWRP? I want to be able to backup my current stock state and flash new roms.
Still new and it's taking a bit of time learning the vast ocean of android modding/development. When I hear people saying backup your stock rom before flashing, does this mean basically backing up the system or EVERYTHING including apps, music, sms etc? Correct me if I'm wrong but backing up with CWM or TWRP basically means just the system recovery kinda backup right? Like the CD's manufacturers give you when you first purchase a laptop.
Okay so if I'm correct on that, it basically means that if I were to flash a new rom or revert back to my stock rom. I'll lose all the files I've added on to the device aside from the factory starter apps/settings right? If this is the case than I would have to use QCOM Toolkit by mskip or titanium backup to backup all my apps (while i would have to manually backup photos,sms,music,videos etc through just normal USB?) or does our files get transferred over as well? I doubt that since it's basically a new "OS" right?
lol it's pretty cool learning all these new ideas as it'll be beneficial to everyone and myself on how to fully use the android phones. Now say if I want to switch roms with ease, is there such feature?
Last but not least, can all this be done with just the internal memory? I currently don't have any micro sd cards and waiting for the price drop on the 64gb sandisk because I have a huge playlist of FLAC files to add (living in Canada sometimes suck... all the good deals especially free shipping is in the usa lol..)
Thanks again xda-community

Intercrew said:
Hey guys, now that we can backup our IMEI (Thanks to peoplearmy and geek!) I feel like flashing roms like a mad man. But before I start I was wondering if theres any differences between the CWM and TWRP? I want to be able to backup my current stock state and flash new roms.
Still new and it's taking a bit of time learning the vast ocean of android modding/development. When I hear people saying backup your stock rom before flashing, does this mean basically backing up the system or EVERYTHING including apps, music, sms etc? Correct me if I'm wrong but backing up with CWM or TWRP basically means just the system recovery kinda backup right? Like the CD's manufacturers give you when you first purchase a laptop.
Okay so if I'm correct on that, it basically means that if I were to flash a new rom or revert back to my stock rom. I'll lose all the files I've added on to the device aside from the factory starter apps/settings right? If this is the case than I would have to use QCOM Toolkit by mskip or titanium backup to backup all my apps (while i would have to manually backup photos,sms,music,videos etc through just normal USB?) or does our files get transferred over as well? I doubt that since it's basically a new "OS" right?
lol it's pretty cool learning all these new ideas as it'll be beneficial to everyone and myself on how to fully use the android phones. Now say if I want to switch roms with ease, is there such feature?
Last but not least, can all this be done with just the internal memory? I currently don't have any micro sd cards and waiting for the price drop on the 64gb sandisk because I have a huge playlist of FLAC files to add (living in Canada sometimes suck... all the good deals especially free shipping is in the usa lol..)
Thanks again xda-community
Click to expand...
Click to collapse
The differences in the recoveries that will matter for you, is that you're going to have an SD card in the future, currently only recovery 5.8.4.5 supports SD card in FAT32 format, later version recoveries don't have extSD support, the 5.8.4.5 images and zips are HERE
So after you've followed the root no-trip counter method, which is what is recommended, you can flash a different recovery from that thread, or just download the zip of the one you want, the recovery is inside the zip and can be pushed via ADB... refer to mrRobinson's thread for help with all that, and links to images... It'll need a recovery after getting rooted, might as well put the proper one on then...
Performing a backup is done from recovery, do an nandroid backup, it backs up the present state of your phone, so if you restore to it, it will be exactly like it was, when you backed it up...
No need for the toolkit, use Titanium Backup to backup apps or apps data if you want to restore them on a new ROM, and it's only recommended to back up USER apps and data, nothing system related, it will cause issues... The paid version is highly recommended if you're going to be relying on backups of your apps and such... I personally don't use it...
Without the SD, yea you'll be using internal memory... and it'll fill up quick with nandroids and ROMs... I never made an nandroid for my phone, but im sure its well over a gig in size...

B-Naughty said:
Without the SD, yea you'll be using internal memory... and it'll fill up quick with nandroids and ROMs... I never made an nandroid for my phone, but im sure its well over a gig in size...
Click to expand...
Click to collapse
You are correct. Its quite a large file. Around 1.6GB
Sent from my GS3

B-Naughty said:
The differences in the recoveries that will matter for you, is that you're going to have an SD card in the future, currently only recovery 5.8.4.5 supports SD card in FAT32 format, later version recoveries don't have extSD support, the 5.8.4.5 images and zips are HERE
So after you've followed the root no-trip counter method, which is what is recommended, you can flash a different recovery from that thread, or just download the zip of the one you want, the recovery is inside the zip and can be pushed via ADB... refer to mrRobinson's thread for help with all that, and links to images... It'll need a recovery after getting rooted, might as well put the proper one on then...
Performing a backup is done from recovery, do an nandroid backup, it backs up the present state of your phone, so if you restore to it, it will be exactly like it was, when you backed it up...
No need for the toolkit, use Titanium Backup to backup apps or apps data if you want to restore them on a new ROM, and it's only recommended to back up USER apps and data, nothing system related, it will cause issues... The paid version is highly recommended if you're going to be relying on backups of your apps and such... I personally don't use it...
Without the SD, yea you'll be using internal memory... and it'll fill up quick with nandroids and ROMs... I never made an nandroid for my phone, but im sure its well over a gig in size...
Click to expand...
Click to collapse
Is there a specific reason why the toolkit isn't recommended? Wouldn't it be easier to just backup all the stuff to the pc?
Now if I can backup all the nandroid, ROMs, and app&data through to the pc. Then titanium wouldn't be needed and the differences between the TWRP and CWM would be non? And is it okay to have the nandroid and ROM backup on the computer and not the device or sd card, or is it a good idea to keep it on the deivce/sdcard? If thats the case I will go with the link you gave me which is 5.8.4.5 CWM, (not sure the difference between the Touch and just normal, and which one I should downloaded out of the three (I own the Telus which should be equivalent to the AT&T))
Lastly, you mentioned if I wanted a different recovery I would go and flash the one in Robinson's thread (which i did on my last root but un-rooted and went to factory after having some issues with the homescreen). The ones in his thread aren't SD-card compatibility are they? or Are they?

Intercrew said:
Is there a specific reason why the toolkit isn't recommended? Wouldn't it be easier to just backup all the stuff to the pc?
Now if I can backup all the nandroid, ROMs, and app&data through to the pc. Then titanium wouldn't be needed and the differences between the TWRP and CWM would be non? And is it okay to have the nandroid and ROM backup on the computer and not the device or sd card, or is it a good idea to keep it on the deivce/sdcard? If thats the case I will go with the link you gave me which is 5.8.4.5 CWM, (not sure the difference between the Touch and just normal, and which one I should downloaded out of the three (I own the Telus which should be equivalent to the AT&T))
Lastly, you mentioned if I wanted a different recovery I would go and flash the one in Robinson's thread (which i did on my last root but un-rooted and went to factory after having some issues with the homescreen). The ones in his thread aren't SD-card compatibility are they? or Are they?
Click to expand...
Click to collapse
Just follow his steps to get it rooted and install a recovery, his thread is using a 5.8.4.5 version, you'll be fine with the SD card... keep at least one working nandroid on you device... and it's not that toolkit isn't recommended, it's highly useful, but to me thats one extra time you're hooking your phone to computer, doing something... just make sure it isn't backing up / restoring system apps, and only user apps... If you just want to feel safer and stuff, use to toolkit to back up what you'd like, and keep a working nandroid on your phone... It's all user preference, I never back anything up... some people back up everything they possibly can...

B-Naughty said:
Just follow his steps to get it rooted and install a recovery, his thread is using a 5.8.4.5 version, you'll be fine with the SD card... keep at least one working nandroid on you device... and it's not that toolkit isn't recommended, it's highly useful, but to me thats one extra time you're hooking your phone to computer, doing something... just make sure it isn't backing up / restoring system apps, and only user apps... If you just want to feel safer and stuff, use to toolkit to back up what you'd like, and keep a working nandroid on your phone... It's all user preference, I never back anything up... some people back up everything they possibly can...
Click to expand...
Click to collapse
lol okay thanks a lot mate

I just have one last concern is it a good idea to make a nandroid backup while your in a different ROM from stock? Like for example if I downloaded some apps, got new sms, new settings etc and wanted it to maintain even though I switched ROMs or go back to stock, everything would transfer over but the ROM that I was in before (Kyan in this case) would also transfer so stuff like (apps) gallery, google chrome, google music, and other things that were special to the custom ROM?
If this is true, I guess the best thing to do is make a backup before switching ROM's than make separate backups of all the apps+data, sms etc before switching to either a stock or another custom ROM?

Intercrew said:
I just have one last concern is it a good idea to make a nandroid backup while your in a different ROM from stock? Like for example if I downloaded some apps, got new sms, new settings etc and wanted it to maintain even though I switched ROMs or go back to stock, everything would transfer over but the ROM that I was in before (Kyan in this case) would also transfer so stuff like (apps) gallery, google chrome, google music, and other things that were special to the custom ROM?
If this is true, I guess the best thing to do is make a backup before switching ROM's than make separate backups of all the apps+data, sms etc before switching to either a stock or another custom ROM?
Click to expand...
Click to collapse
All ROM devs recommend that you make an nandroid before flashing their ROM just in case you need it... Most people made one on stock, and everytime before they flash something else... Like I said, I never make one, if I have issues I'll fix it some other way... and the backup will restore EVERYTHING back to exactly as it was when you made it... which is also why you don't need to backup apps with toolkit, etc... just make nandroids, and use TiBu for other stuff...

B-Naughty said:
All ROM devs recommend that you make an nandroid before flashing their ROM just in case you need it... Most people made one on stock, and everytime before they flash something else... Like I said, I never make one, if I have issues I'll fix it some other way... and the backup will restore EVERYTHING back to exactly as it was when you made it... which is also why you don't need to backup apps with toolkit, etc... just make nandroids, and use TiBu for other stuff...
Click to expand...
Click to collapse
Yes I know that, but what I mean is, is it okay to make a nandroid backup while your on a different ROM, and once you switch ROM is it safe to restore the nandroid you made backup of while in a different ROM?
Cause like you said and other the nandroid backups EVERYTHING to exactly how it was before. So that means the stuff that weren't or were in different ROMS will appear/disappear in the other ROM's I'm using?
EDIT: I'm just curious weather or not if I have to reinstall all the new apps i've downloaded and sms backup while in a different ROM to prepare myself for the reset on the new ROM

Intercrew said:
Yes I know that, but what I mean is, is it okay to make a nandroid backup while your on a different ROM, and once you switch ROM is it safe to restore the nandroid you made backup of while in a different ROM?
Cause like you said and other the nandroid backups EVERYTHING to exactly how it was before. So that means the stuff that weren't or were in different ROMS will appear/disappear in the other ROM's I'm using?
Click to expand...
Click to collapse
No don't restore the nandroid unless you want to go back, or something has gone wrong and you have to... If you want to backup your apps and app data use Titanium Backup...

B-Naughty said:
No don't restore the nandroid unless you want to go back, or something has gone wrong and you have to... If you want to backup your apps and app data use Titanium Backup...
Click to expand...
Click to collapse
thank you lol

I just wanted to chime in and say thanks for the educational read. It's nice to see well articulated thoughts exchanged (with correct spelling might I add).
Cheers

Be careful as telus is NOT exactly the same as at&t. I'm rogers and although yes we have to use the at&t forum 747 and our 747m phones do have a few key differences so be careful. The cwm recovery is actually an older version that works for us as we can't install the newest version. And our modem or broadband is DIFFETENT then at&T's so that has to be remembered when flashing roms and mod'ing. Just some advise to remember with our Canadian variants.
Sent from my SGH-I747M using xda premium

pchemerys said:
Be careful as telus is NOT exactly the same as at&t. I'm rogers and although yes we have to use the at&t forum 747 and our 747m phones do have a few key differences so be careful. The cwm recovery is actually an older version that works for us as we can't install the newest version. And our modem or broadband is DIFFETENT then at&T's so that has to be remembered when flashing roms and mod'ing. Just some advise to remember with our Canadian variants.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Wow... I undertsood what you were saying... but then i dismissed it as drunken typing with nothing that makes sense... I understood you..
CWM 5.8.4.5 supports extSD
Modem doesn't have to be changed, so it has nothing to do with it...

Just out of curiousity for those using CWM:
Does your nandroid backup have incorrect date stamps?
Mine says my phone was backup in the 1970s

Sort if this is a dumb question but why cant we use the newest version?
Sent from my A501

twanskys204 said:
Sort if this is a dumb question but why cant we use the newest version?
Sent from my A501
Click to expand...
Click to collapse
You can use newest version if you want, but only 5.8.4.5 supports extSD :good:

B-Naughty said:
You can use newest version if you want, but only 5.8.4.5 supports extSD :good:
Click to expand...
Click to collapse
Are u sure the newest cwm works on the 747m variant? I was informed ( on several posts) that it doesn't and will cause problems and a few have posted them. Keep in mind this is the Canadian version not at&t. Even in the root sticky for this747m device it talks about this and why it gives the install instructions for the earlier version for our devices. Sure I could be wrong but there is plenty on this site to support what I'm saying.
---------- Post added at 05:44 AM ---------- Previous post was at 05:31 AM ----------
B-Naughty said:
Wow... I undertsood what you were saying... but then i dismissed it as drunken typing with nothing that makes sense... I understood you..
CWM 5.8.4.5 supports extSD
Modem doesn't have to be changed, so it has nothing to do with it...
Click to expand...
Click to collapse
Lol..I now get why u were saying this...I apologize cuz I just realized that i was talking about the modems in this thread and that was an accident...when I was replying here I had a lot of reply windows open and got mixed up..(I'm not a drinker btw so no drunken typing btw) ..but just as a very general point it still applies..be careful with "some at&t roms" as there are some differences that could cause issues...that's all..but as for cwm rec..its all good and I will have to look into this again about the latest versions because I was under the impression from some here that it is not advised...maybe wrongly. Thanks and I'll check it out.

pchemerys said:
Are u sure the newest cwm works on the 747m variant? I was informed ( on several posts) that it doesn't and will cause problems and a few have posted them. Keep in mind this is the Canadian version not at&t. Even in the root sticky for this747m device it talks about this and why it gives the install instructions for the earlier version for our devices. Sure I could be wrong but there is plenty on this site to support what I'm saying.
---------- Post added at 05:44 AM ---------- Previous post was at 05:31 AM ----------
Lol..I now get why u were saying this...I apologize cuz I just realized that i was talking about the modems in this thread and that was an accident...when I was replying here I had a lot of reply windows open and got mixed up..(I'm not a drinker btw so no drunken typing btw) ..but just as a very general point it still applies..be careful with "some at&t roms" as there are some differences that could cause issues...that's all..but as for cwm rec..its all good and I will have to look into this again about the latest versions because I was under the impression from some here that it is not advised...maybe wrongly. Thanks and I'll check it out.
Click to expand...
Click to collapse
Well I can't confirm whether it will work flawlessly like on an AT&T phone, or will it produce assert errors, because I don't have a Canadian variant... and mostly because I don't come into the Q/A forum very often, and read the threads... I'll just check to see if it's swamped the I'll help out...but the fact still remains that only 5.8.4.5 supports extSD.... Try one of these CWM recoveries, flash it in your current recovery... Worst that will happen is that you'll be changing recoveries again, if it throws script / assert errors...
Possibly someone with an I747M can chime in about which 5.8.4.5 to use for extSD support...

E975: Backuping original LG's Software before going CM?

Hello there,
I googled a lot, I searched a lot here, but I did not find what I searched for.
I am thinking about testing the new Version of Cyanogenmod, the problem is that I in fact never did anything like this.
I want to set back the device to manufactures setting and then backup the original LG Software, so that I can go back to the standard before selling, or if CM isnt quite mine.
Anyone tips or links how to manage that?
Thank a lot before, sorry if this was asked before (I'm pretty shure), I couldn't find.
5MinutesAloneLG

After rooting and unlocking,make sure you place the efs backup somewhere safe. You can also make a nandroid backup and restore it if you don't like cm. or you can use kdz updater to flash stock firmware.
I'm sure you looked all the places,except the FAQ

Okay, this sounds good to me.
Does any of the 3 Methods give me the same way of a full backup from the original software, or is there something else that has to be done?
I searched for the Faqs, but I couldn't find any?
Thanks a lot!

5MinutesAloneLG said:
Does any of the 3 Methods give me the same way of a full backup from the original software, or is there something else that has to be done?
Click to expand...
Click to collapse
No, these are different things. EFS backup is to save your butt in case something happens with your IMEI. This is one of the most important things, don't overlook it! Nandroid backup is a "snapshot" of your existing ROM, including all your installed apps and their settings. This is the easiest way to get back to your previous ROM after experimenting with others. And KDZ is not a backup - it's a factory image that will return your phone to the exact same state as it was when brand new.
I searched for the Faqs, but I couldn't find any?
Click to expand...
Click to collapse
Look in @kimitza signature. It's his baby. :good:

the nandroid backup is like a restore image for windows. you will have all apps/settings from that time saved. here is a scenario:
1. On clean stock rom,root and unlock(unlock will also flash cwm recovery). Place FREEGEE folder somewhere safe.
2. Enter recovery mode and make a backup.
3. Flash any other rom ...and if you don't like it, restore the backup you made earlier.
4. Restore EFS with freegee.
5. Use Unroot from supersu.
6. Backup all your files(photo and other media to pc) then do a hard reset.
7. You will have a clean stock/official rom,like it came from factory.
All of this can be simplified by backing up your files and use kdz updater,followed by a hard reset. .It takes less time and it's safer.

I rooted it, but I dont have an hint of an idea how to do these efs backup?
http://forum.xda-developers.com/showpost.php?p=38886073&postcount=1&nocache=1&z=7530246020855317
what is to do with that zip? I'm from germany and I have no clue what run in recovery mode should tell me. On the Phone or on the PC?
If unzipped, what is there to do?
As I want to use the cm installer with 10.2 stable, I just want to backup everything important..

Sorry, wrong link, i meant this of course, its allready rooted
http://forum.xda-developers.com/showpost.php?p=38438579&postcount=1

Sorry for posting again, but honestly, I'm not allowed to post in the efs thread, so I cant do anything right now.
Im still waiting to flash it.
Anyone should do efs backup, so basicly people should be able to tell me how to do that or?
Please anyone!

When you unlock the bootloader with freegee, it automagically makes a backup of the EFS,amongst other things(like bootloader state,imei,partitions etc). It's enough to place that FREEGEE folder somewhere safe. If you ever run into troubles(like no IMEI shown or you just want to go back to stock without using KDZ updater),just restore with freegee. It will relock you bootloader and restore EFS(with imei).

Titanium Backup Restores (ROOT)

Since rooted phones can't take OTA's, we have special considerations before updating. (flash/wipe/then recover ... ). Google restores a lot but I've discovered not many system or app settings. TWRP makes full backups, but if your data is full of pics and videos there's not enough available space for backups.
I have Titanium Backup Pro but I'm not sure 'when' to use it for recovery. Individual app restores sure, but what about a complete restore? After a flash and boot, should I bypass the Google setups, install TiB, and restore with that? Will that give me a 100% restored device (all system and app settings)?
Will this work? Is there a better strategy? Or is it impossible to get 100% recovery.
Insight/ Advice are appreciated.

Can't systemless root take OTAs?

Keithn said:
Can't systemless root take OTAs?
Click to expand...
Click to collapse
From my limited understanding ... no! Any boot, recovery, or system mods cause OTAs to fail when trying to apply. Getting AP working is a different issue.

since i'm not comfortable using command line programs i find myself using NRT when an update is due. in the end it's just a graphical frontend with some instructions but it makes me feel more secure.
enough rambling, your question is answered in one of the FAQs in wugs homepage:
http://www.wugfresh.com/faqs/how-to-update-ota-not-working/ said:
If you use Titanium Backup it is recommended to only backup user apps + data (not system apps), because when you update to the new android version, the system apps are most likely updated, so restoring an old system app backup will overwrite your new system app with the legacy version; and if you were just to restore the data, it may be incompatible with the new version of the system app. There are some exceptions to this rule; as in – you might be able to get away with restoring some system data, however if you chose to go this route then make sure you just restore the data (not the app), you do so selectively (as in – one system app at a time), and you know how to delete that app data if it doesn’t work properly (Settings > Apps > All > navigate to the particular app > clear data > reboot your device.)
Click to expand...
Click to collapse
following that link, i mostly find my self making complete backups with TiBa and then following option #1 for smaller updates and #2 for bigger ones.

Broken303 said:
...
following that link, i mostly find my self making complete backups with TiBa and then following option #1 for smaller updates and #2 for bigger ones.
Click to expand...
Click to collapse
Thanks for the valuable info. It appears a full restore (all system settings) is impossible after an upgrade/update. Maybe restoring app data with a TiBackup is possible, but I'm still confused about the 'when' to do this - after the Google restore? Bypass the Google restore?
I recently moved away from Apple where their update/upgrade restore was almost 100%. Maybe some day Google will follow and this will be a moot point.

Mesmurized said:
Thanks for the valuable info. It appears a full restore (all system settings) is impossible after an upgrade/update. Maybe restoring app data with a TiBackup is possible, but I'm still confused about the 'when' to do this - after the Google restore? Bypass the Google restore?
I recently moved away from Apple where their update/upgrade restore was almost 100%. Maybe some day Google will follow and this will be a moot point.
Click to expand...
Click to collapse
google is certainly impoving on that part, it's only a matter of time until this kind of backup is fully implemented.
if you took a look at the link, you may have realised that at least with option 1 you would not have to go through the setup/restore process again.
in my case, i usually go for the restore option given, as it restores some of the system settings in a compatible way, which TiBa can not as already said.
another option, to carry over all of your settings to the update is to:
make a full backup with TiBa
unroot/reflash your current build (if you are using NRT choose 'no wipe mode' similar to the description in the FAQ. this way you don't have to restore anything and can ignore the next step.)
restore your full backup without fear of compatibility issues(never mind, can't restore system settings without root. stupid me.)
take OTA or trigger the update otherwise
in this case it would of course be pretty much useless to restore the google backup.

Broken303 said:
google is certainly impoving on that part, it's only a matter of time until this kind of backup is fully implemented.
if you took a look at the link, you may have realised that at least with option 1 you would not have to go through the setup/restore process again.
in my case, i usually go for the restore option given, as it restores some of the system settings in a compatible way, which TiBa can not as already said.
another option, to carry over all of your settings to the update is to:
make a full backup with TiBa
unroot/reflash your current build (if you are using NRT choose 'no wipe mode' similar to the description in the FAQ. this way you don't have to restore anything and can ignore the next step.)
restore your full backup without fear of compatibility issues(never mind, can't restore system settings without root. stupid me.)
take OTA or trigger the update otherwise
in this case it would of course be pretty much useless to restore the google backup
Click to expand...
Click to collapse
I checked out Option #1 and the rest of NRT for that matter. In fact I have NRT installed. What is does mostly depends upon stock and I have Pure Nexus. In addition, it's a toolkit. Toolkits isolate users from an "understanding" of the process. However, it's the understanding that is necessary to have a fully integrated backup/restore process and to respond to issues/problems that may arise. Bottom line, I don't use toolkits.

Mesmurized said:
I checked out Option #1 and the rest of NRT for that matter. In fact I have NRT installed. What is does mostly depends upon stock and I have Pure Nexus. In addition, it's a toolkit. Toolkits isolate users from an "understanding" of the process. However, it's the understanding that is necessary to have a fully integrated backup/restore process and to respond to issues/problems that may arise. Bottom line, I don't use toolkits.
Click to expand...
Click to collapse
ok then, i thought your switch to android was very recent and therefore you had very little experience. indeed toolkits are in the way of a learning curve when it comes to android.
to my knowledge the closest thing you can get to a full backup/restore process for manual updates is to use the google backup to restore the system settings and use TiBa to restore your own (user)apps and data (possibly overwriting the apps google may have tried to restore/-install). with pure nexus afaik being very close to stock using the tag to not wipe user data should in theory still work without causing problems.

Broken303 said:
ok then, i thought your switch to android was very recent and therefore you had very little experience. indeed toolkits are in the way of a learning curve when it comes to android.
to my knowledge the closest thing you can get to a full backup/restore process for manual updates is to use the google backup to restore the system settings and use TiBa to restore your own (user)apps and data (possibly overwriting the apps google may have tried to restore/-install). with pure nexus afaik being very close to stock using the tag to not wipe user data should in theory still work without causing problems.
Click to expand...
Click to collapse
If I understand correctly, do you recommend allowing Google to restore everything it wants, then running TiB restore after that?

Mesmurized said:
If I understand correctly, do you recommend allowing Google to restore everything it wants, then running TiB restore after that?
Click to expand...
Click to collapse
yes, basically. i would still be cautious when it comes to sms/mms and make a copy of every important file on the sdcard aswell.
the only problem i ever encountered this way was with whatsapp, which i had to reinstall and then manually move over its folder on the sd card from the previous installation.

Broken303 said:
yes, basically. i would still be cautious when it comes to sms/mms and make a copy of every important file on the sdcard aswell.
the only problem i ever encountered this way was with whatsapp, which i had to reinstall and then manually move over its folder on the sd card from the previous installation.
Click to expand...
Click to collapse
I have a separate app for call logs and SMS/text messages. I'll use it!
I always have everything on /sdcard backed up .... It's just those darn system/app settings that are missing. Oh well, thanks for your help. Think I've come a little closer to a full 100% restore.

Mesmurized said:
Since rooted phones can't take OTA's, we have special considerations before updating. (flash/wipe/then recover ... ). Google restores a lot but I've discovered not many system or app settings. TWRP makes full backups, but if your data is full of pics and videos there's not enough available space for backups.
I have Titanium Backup Pro but I'm not sure 'when' to use it for recovery. Individual app restores sure, but what about a complete restore? After a flash and boot, should I bypass the Google setups, install TiB, and restore with that? Will that give me a 100% restored device (all system and app settings)?
Will this work? Is there a better strategy? Or is it impossible to get 100% recovery.
Insight/ Advice are appreciated.
Click to expand...
Click to collapse
Just follow #10 from Heisenberg's rooting guide & your apps/data stay intact.

ING3NIEUR said:
Just follow #10 from Heisenberg's rooting guide & your apps/data stay intact.
Click to expand...
Click to collapse
That's the easy part! Restoring app settings and all of system settings is the hard part

Mesmurized said:
That's the easy part! Restoring app settings and all of system settings is the hard part
Click to expand...
Click to collapse
As long as you follow the guide and don't wipe your phone, then there's no need to restore your apps/settings. They should still be there on your phone. The only thing you have to restore is TWRP/root.

ING3NIEUR said:
... The only thing you have to restore is TWRP/root.
Click to expand...
Click to collapse
If a flash update is performed, do you still restore TWRP/root? I would think not as it would overwrite the newly flashed update and likely make the system unstable in the least or unbootable at the worst!

Mesmurized said:
If a flash update is performed, do you still restore TWRP/root? I would think not as it would overwrite the newly flashed update and likely make the system unstable in the least or unbootable at the worst!
Click to expand...
Click to collapse
If you are rooted, your phone will not take an OTA update. So you have two options....flash the new factory image or wait for somebody to upload a flashable update zip. The easiest way is to just download and flash the new factory image. If you follow the guide, you are also flashing stock recovery. So, you have to re-flash TWRP and root. Your data/apps stay intact.

ING3NIEUR said:
If you are rooted, your phone will not take an OTA update. So you have two options....flash the new factory image or wait for somebody to upload a flashable update zip. The easiest way is to just download and flash the new factory image. If you follow the guide, you are also flashing stock recovery. So, you have to re-flash TWRP and root. Your data/apps stay intact.
Click to expand...
Click to collapse
Thanks for you input, but after all this, at the least many system settings are lost even after Google does it's full restore. I know, I've done it many times. I'm looking for a process/strategy that restores system settings (and all data settings) after an upgrade.

Mesmurized said:
Thanks for you input, but after all this, at the least many system settings are lost even after Google does it's full restore. I know, I've done it many times. I'm looking for a process/strategy that restores system settings (and all data settings) after an upgrade.
Click to expand...
Click to collapse
Im very confused by this whole thread you have unlocked bootloader rooted phone running twrp and wondering how to stay up to date with latest google factory images?
You dont have to backup your phone to install the factory images and you can flash the new one over the current one. You can simply download the latest factory image from google and manually flash the files from fastboot or use the flashall.bat. just make sure to edit the flash allscript so it doesn't flash userdata or recovery as the flashing of userdata will delete your user data)
Flash the following from the factory image. Dont flash recovery or userdata (recovery will over write twrp and userdata will wipe your data partition.
Boot.img
Cache.img
System.img
Vendor.img
Radio.img
Then boot into recovery and reinstall su.

The_Automator said:
Im very confused by this whole thread you have unlocked bootloader rooted phone running twrp and wondering how to stay up to date with latest google factory images? ...
Click to expand...
Click to collapse
No. Please re-read post #1.
I want to restore all system and app settings AFTER a flash update. It is possible to retain many (most) app settings if the internal storage is not wiped, but this does not apply to system settings.

Mesmurized said:
No. Please re-read post #1.
I want to restore all system and app settings AFTER a flash update. It is possible to retain many (most) app settings if the internal storage is not wiped, but this does not apply to system settings.
Click to expand...
Click to collapse
Updates modify the system partition of the phone i have found that using titanium backup to restore system apps has always caused issues for me as the files have been modified by the update and you are then overwriting the update with settings from a previous version this can make settings copied incorrectly or cause issues with new features that have been implemented to the system partition. Personally I think it could create more issues than it solves is there a specific setting or thing you are trying to preserve?