Database Develop

[Q] Rooting & Unrooting question

Hi guys, i've seen that custom roms are in an early state of developement so i'm thinking of rooting my OB just to remove some useless default applications. Now the questions:
If an official update is released by LG (gingerbread hopefully), do i have to unroot the phone before i upgrade it by pc-suite?
if yes, how could i unroot the phone?
Thank you so much!

It was answered many times.
Use Search function...
Sent from my LG-P970 using XDA Premium App

I have a noob question guys. I root my phone and delete some default apps like Car Home, News, Finance. Now Car Home, News etc is deleted it is possible to UNROOT my phone? Do you think if i UNROOT my phone it can cause a problem/bug? I try to restore some of my default apps using titanium backup but after 30 mins of waiting nothing happens. Still i can't restore it.

of course you can't restore stock apps if you have deleted sources apk without backups. So you must find stock apps, copy them to /system/app (root needed) then installing them

Ilko said:
of course you can't restore stock apps if you have deleted sources apk without backups. So you must find stock apps, copy them to /system/apps (root needed) then installing them
Click to expand...
Click to collapse
I do backup before i delete the apps using titanium backup, But the problem is when i try to restore the stock/default apps after 30 mins nothing happens. I check my sd card in titanium folder and the backup is still there. I also try to delete some apps that can be found in the market like angrybird etc then i try to restore it and it works! So I'm just wondering, when it comes to stock/default apps why l can't restore them even though i have a backup.
Sent from my LG-P970 using XDA App

you may haven't write permission. Are you fully rooted ?

The original question from gabrieles84 is still valid in my opinion. As radkor indicated I searched the forum, but there are many methods and can't find a conclusive answer.
I was wondering the same thing. There are a number of methods of upgrading the firmware. Which is safe with a rooted phone?
1. FOTA (from settings menu): in this thread (http://forum.xda-developers.com/showthread.php?t=1204903&highlight=unroot+before+upgrade) it is indicated the root was the cause of the bricking. So it is safe to update this way with a rooted phone? Or is this dependant on the firmware and recovery? (my firmware is V10A no CWM)
2. LGMobileupdater (B2C). Is this safe with rooted phone? In my case it tells me there is a new firmware, but I'm not sure if it is safe to upgrade since I rooted with SOC 1.95, unrooting is not that simple in that case.
This will not work in this case, factory reset does not unroot, http://forum.xda-developers.com/showpost.php?p=16519995&postcount=19
3. KDZ. This post indicates it is not nessecary to unroot: http://forum.xda-developers.com/showpost.php?p=16522163&postcount=23
(I'm not mentioning the R&D Test Tool in this list, since that is only needed in case of a brick right?)
Thanks in advance!

1. FOTA - isn't safe with root - I bricked my phone with that
2. Safe
3. Safe

R&D Test Tool method is the same that KDZU but with a final factory reset.
Then, it's the way to flash devices that doesn't run well after reflash because of data inside the phone in conflict with new flash.
But, IMHO, I¡ll recommend ALLWAYS use R&D Test Tool method instead KDZU because IT'S THE SAME but additionally makes a hard reset, that is what usually we have to make after a KDZU reflash.
Regards.

Just to confirm: yesterday evening I updated my phone with LGUpdater (B2C) from V10A to V10E without removing root. No problems and now running newest fw.
Thanks guys!

[Q] Updating over root.

I rooted my gf's nook last year. It's been running rooted 1.1.0. Now, she could care less about root, but she just wants to retain her 50+ magazines and books. Can I just manually download the .zip from B&N, stick it on the root, and let it update? Also, is this a full install? Or, just an update where I'd have to update 1.2.0 then 1.3.0 first?
Sorry about all the questions. I've been out of the loop for a very long time and don't want to lose her data. Any help is greatly appreciated! Thanks!
Edit: I've been reading up on this and many suggest doing a full restore to stock and going from there. If at all possible, I would like to avoid that in an effort to retain all data. I did find an article where a guy claimed to rename the clockwork recovery image and put the official 1.2 recovery image in it's place so an auto-update can run successfully. Otherwise, it sounds like clockwork "gets on the way" and won't allow an update to run entirely. Can anyone confirm this?
Sent from my ADR6400L using XDA App

[Q] OTA Update and Safestrap Clarification

Hello all,
I've been running Eclipse 2.2 on 902 for some time and I've stubbornly refused to switch away from using bootstrap for all my backup needs, however, after reading enough about it I decided to give safestrap a try. I've had a little trouble with the process however and was looking for a little clarity...
My understanding with safestrap was that in addition to giving me a safe (technically unsafe) 2nd partition/access to recovery in case I messed something up, that it would also pretty easily transfer data, apps, etc from one partition to the next, making flashing roms (and I thought updating) much easier and quicker without needing to backup individual portions of my system, Is this correct or am I mistaken?
Onward to what I did (my goal is to update to 905 and install eclipse 3.0) - Installed safestrap, backed up safe and unsafe side. I then went to unsafe and used bootstrap to restore to IMMEDIATELY after I applied the 902 update (had backed it up previously). This backup was literally a stock Bionic which I had updated from 886 all the way to 902, rooted, then installed bootstrap to backup. I then updated this to 905 with no issue, and of course backed it up... From here, my understanding was that I could simply swap over to safe side, then install the eclipse 3.0 through finding a zip in recovery - Recovery would not do this for me. It gave me an error similar to "cannot apply eclipse3.0.zip (bad)"
I tried to push the ROM both without making any changes (just switching from unsafe to safe and immediately trying to apply the zip) and when that didn't work I wiped data, formatted system, and wiped cache/dalvik and got the same error. (the net result through all of this was making my safe side non-responsive, and me ending up restoring safe side system to the initial backup I had made about 30 minutes prior).
Is this working as intended? Should I look at safestrap as purely an extra failsafe to keep me from bricking my phone and not an easier method to flash/update? If I have to expect that I need to go to safe, follow the same path to apply the update as I did on unsafe, then flash 3.0 and restore with titaniumbackup, sms/call log backup, etc, I will, but I just wanted to make sure I'm not misunderstanding something with safestrap that may allow me to make this whole process easier - I'd be much more interested in trying out a variety of ROMs if the restoring of my data wasn't such a hassle when I did it.
Sorry for the long post - I'm long winded and also wanted to get all of the information out there for anyone who may answer.
Thanks in advance!
-Jamie

Guess I was too wordy and nobody wants to read it (or posted in the wrong spot maybe) -
tldr:
Is there a way to use safestrap as having a way to easily transfer data etc from one rom/update to the next? or should I be using it solely to have an extra backup to prevent me from bricking my phone, and just do the longer more arduous methods of restoring data and settings after a rom swap/update?

I'm no expert but I have successfully used Safestrap, installed eclipse 3.0 as well as tried other roms and themes, and have other Android experience as well. Sounded like you may have used bootstrap and Safestrap at the same time. Am I wrong? If not, from my understanding that is a no no. Uninstall bootstrap completely and use Safestrap only. I also upgraded my "unsafe" system to .905 via OTA before attempting 3.0. My first experience with Safestrap, however, was not entirely positive either. I think my download was corrupt because it stopped working correctly. I downloaded again and haven't had any problems since. I followed this guide http://forum.xda-developers.com/showthread.php?t=1455888 and it worked. He's not really all that clear at times. It's also not necessary to factory reset after flashing a new rom. Always do it, but it can be done before too. I always do it before and have no problems. Also if you decide to apply a theme make sure you boot up the new ROM before flashing the theme. This guide was not entirely clear on that and it got stuck in a wicked boot loop that ended with me on stock and Safestrap gone. Keep trying. Hope some of this helped. I'm wordy too
Sent from my Galaxy Nexus using xda app-developers app

Btw, to answer your first question, the best way I've found to transfer user apps from ROM to ROM is with titanium backup. Other data will still be on your sd cards and accessible to the new ROM. I never use titanium to restore system settings and most system apps though. Things tend to get messed up if you try to do this from one rom to another. System apps can be converted to user apps with titanium which is cool then backed up and restored to new ROM. And never restore Google play app with titanium. Some go so far as to say don't restore apps with data but I haven't had any trouble except with core google apps like play, gmail, voice. Usually flash gapps if I have to and restore other core Google apps directly from play store. Sometimes titanium "hangs" on some apps. Not to much trouble with it lately maybe it's fixed used to be a PIA though.Sorry there's still plenty of setup involved any time you want to "dial in" a new ROM.
Sent from my Galaxy Nexus using xda app-developers app

Thanks G-diddy,
To clarify, I knew bootstrap and safestrap didn't play well together. That being said, I did NOT use safestrap to try and restore to a bootstrap backup. I installed safestrap, then swapped to my UNSAFE side, then restored to a previous bootstrap backup (using bootstrap), then OTAd to .905. I then backed up this fresh near stock but rooted .905 with safestrap (thus should never have to use bootstrap ever again). I then tried to swap over to safe and push eclipse 3.0 but had no success... At present my phone has near stock but rooted .905 on my unsafe side, and the same .902 with 2.2 eclipse on my safe side that I've been running for months...
I guess I have no choice but to restore my present safe side to the old bootstrap backup, then manually ota, then install the rom, I just thought that Safestrap would make all of this process easier - in as much as since my unsafe side is successfully updated, I was hoping my safe side would be too, making the process somewhat simpler. Sounds like I'm wrong in this assumption though, unless someone else can say otherwise?
Thanks for the tip on Titanium Backup too, although I've been using the premium version of that for months now, ever since I decided I was going to turn my phone into a toy

CM 10.1 Upgrade Procedure

Given that CM 10.1 is still a work in progress, I was looking to see if there was some kind of typical upgrade procedure. Flashing the new ROM is going to essentially wipe the device... is there a 3rd party app that can backup your data? Is it pretty standard to just go through and reinstall everything from scratch?
Thanks!

PenduncleSwazzle said:
Given that CM 10.1 is still a work in progress, I was looking to see if there was some kind of typical upgrade procedure. Flashing the new ROM is going to essentially wipe the device... is there a 3rd party app that can backup your data? Is it pretty standard to just go through and reinstall everything from scratch?
Thanks!
Click to expand...
Click to collapse
If you read the upgrade guides they recommend that you use the same tool (CWM) that you do the flashing with to first backup your existing ROM.
Sent from my Nook HD+ running CM10.1 on emmc.

But this is a backup of the ROM, which from what I understand would have nothing to do with getting things set up once the new version of CM is flashed, correct?

PenduncleSwazzle said:
But this is a backup of the ROM, which from what I understand would have nothing to do with getting things set up once the new version of CM is flashed, correct?
Click to expand...
Click to collapse
You could root stock using my guide in my HD/HD+ CWM guide linked in my signature, then install Titanium Backup (TB requires root) and backup your installed apps. Then after you install CM10.1 to emmc, you can use titanium backup to restore your installed apps. That does not restore your system settings, but you don't want to anyway since they are different systems.
I thought you meant backing up the ROM, not your installed apps. You talked about a work-in-progress and I thought maybe you wanted to be able to go back to stock if you did not like it.
Sent from my Nook HD+ running CM10.1 on emmc.

[Q] Can we verify whether or not our backups have been corrupted?

Hey guys, I just have a general question that (seemingly) applies to all Android phones. I'm posting this question in the GS3 mini section because I have a MetroPCS Galaxy Exhibit [SGH-T599N] and I guess that's where we're we've been relegated to, but this question, as I said, could really apply to any phone. My question is this: how can I verify that my NAND backups are not corrupted?
Here's some context: I recently flashed to CM 11. Everything's running great, it's my daily driver, and I love it. It's easily the best, most smooth ROM I've ever used but I recently discovered a need to flash back to the stock ROM backup I was running pre-CM 11. Before I flashed to CM 11 I was running the standard JB stock and incidentally I was also using a different Kik username. After flashing to CM 11 and installing Kik, I decided to make a new username. Now, given that I never logged out of that old username (the one I was using on JB stock), I know that if I were to flash back to that old ROM, I'd boot into a ROM that's logged into that old account. I need to be able to do this because I need to access that old Kik account's chat logs for personal reasons. My problem now is due to two issues: my amazing stupidity and...well, no that's really it.
At the time I was running stock I was running CWM recovery. I made a backup using Rom Manager but like an idiot I backed up to my internal SD card. In order to flash to CM 11 I had to wipe my internal memory, which eventually lead to me losing that backup. My only silver lining is this: I made one backup to external sd about a week before I flashed to CM 11.
Here's where it gets messy: Not knowing that the backup on the external sd was for my stock pre-CM 11 ROM, I stupidly deleted it to free up space and began saving files onto the external sd card. After I had flashed to CM 11 I made about three CM 11 backups. I deleted my pre-CM 11 backup because I mistook it for one of these three CM 11 backups. Upon realizing the height of my stupidity, I just finished recovering these lost folders and files using a data recovery program, but I have no idea whether or not the files have been irreparably corrupted. Is there any way I can verify that this backup is still good to use? I don't want to risk attempting to flash back to my old ROM only to have it wind up bricking my phone. Does anyone know of a good way I can figure this out? Any help is appreciated.
Thanks,
an idiot

adamryanx said:
Hey guys, I just have a general question that (seemingly) applies to all Android phones. I'm posting this question in the GS3 mini section because I have a MetroPCS Galaxy Exhibit [SGH-T599N] and I guess that's where we're we've been relegated to, but this question, as I said, could really apply to any phone. My question is this: how can I verify that my NAND backups are not corrupted?
Here's some context: I recently flashed to CM 11. Everything's running great, it's my daily driver, and I love it. It's easily the best, most smooth ROM I've ever used but I recently discovered a need to flash back to the stock ROM backup I was running pre-CM 11. Before I flashed to CM 11 I was running the standard JB stock and incidentally I was also using a different Kik username. After flashing to CM 11 and installing Kik, I decided to make a new username. Now, given that I never logged out of that old username (the one I was using on JB stock), I know that if I were to flash back to that old ROM, I'd boot into a ROM that's logged into that old account. I need to be able to do this because I need to access that old Kik account's chat logs for personal reasons. My problem now is due to two issues: my amazing stupidity and...well, no that's really it.
At the time I was running stock I was running CWM recovery. I made a backup using Rom Manager but like an idiot I backed up to my internal SD card. In order to flash to CM 11 I had to wipe my internal memory, which eventually lead to me losing that backup. My only silver lining is this: I made one backup to external sd about a week before I flashed to CM 11.
Here's where it gets messy: Not knowing that the backup on the external sd was for my stock pre-CM 11 ROM, I stupidly deleted it to free up space and began saving files onto the external sd card. After I had flashed to CM 11 I made about three CM 11 backups. I deleted my pre-CM 11 backup because I mistook it for one of these three CM 11 backups. Upon realizing the height of my stupidity, I just finished recovering these lost folders and files using a data recovery program, but I have no idea whether or not the files have been irreparably corrupted. Is there any way I can verify that this backup is still good to use? I don't want to risk attempting to flash back to my old ROM only to have it wind up bricking my phone. Does anyone know of a good way I can figure this out? Any help is appreciated.
Thanks,
an idiot
Click to expand...
Click to collapse
if you recovered it immediately after deletion - then it's most likely still good. I don't think there's any way to fully verify backups; but I will say this if you do chose to use that backup and it fails, you should easily be able to flash any rom over again to correct it, or even use odin to go back to stock rom and try again. The only way you truly hard-brick phones is flashing something over usb and it gets disconnected haflway through, or you accidently flash somethign to the wrong partition (if you were using hiemdall), generally speaking for nearly 80% of bricks are sem-bricks and should easily be able to recover from.

Exothermic said:
if you recovered it immediately after deletion - then it's most likely still good. I don't think there's any way to fully verify backups; but I will say this if you do chose to use that backup and it fails, you should easily be able to flash any rom over again to correct it, or even use odin to go back to stock rom and try again. The only way you truly hard-brick phones is flashing something over usb and it gets disconnected haflway through, or you accidently flash somethign to the wrong partition (if you were using hiemdall), generally speaking for nearly 80% of bricks are sem-bricks and should easily be able to recover from.
Click to expand...
Click to collapse
Thanks for your quick reply, Exo. I'm curious, do you think inspecting the .log file would be able to give me an indication about the integrity of the backup? In going through old backups I was able to open the .log file in Notepad and read in plaintext what was written there. If this could be used as an marker of the backup's health, then it seems I may be out of luck as the .log file for this backup seems like nothing but jibberish. I've opened it with Notepad, Notepad++, and I even installed a different third party program that's reads .log files exclusively (called Baretail), all to no avail. I'll try flashing to this backup in the meantime but I'm curious: do you think attempting to read the .log file could be a good way to verify the backup's integrity, or is there something I'm missing here? Thanks for your time.
Adam

First you should make a nandroid of your current ROM (CM I presume) so that if you brick your phone while trying to restore the stock backup, you'll still have the CM backup to restore if something goes wrong and the phone can't boot or says that there's no os installed.