I am running Stock-Rooted with the Faux123 Kernel and I recently got a notification from GooManager that there was a Gapps update so I ran the update. Now every time I reboot, I get the Android is Upgrading dialog. I know this is usually done when you wipe Cache or install another rom but this is happening on every reboot now. ALso, I keep losing sound as well. Does anyone know how I can fix this issue or should I backup everything and load the factory image? I did do a nandroid backup but I the backup was corrupted so I cannot load that. I do have one other backup but that was from back in August. I know that I should of made a more recent backup but I did not.
BTW: I have Clockworkmod as my recovery and this has nothing to do with the Faux123 kernel as I have been using the same version for months without any issues.
Thanks
OK I did have a sooner backup - 10/09 right before the 4.1.2 update but it was made using TWRP and now I use ClockWorkMod. So can I restore a TWRP backup using CWM or do I need to reinstall TWRP and then restore?
comhack said:
I am running Stock-Rooted with the Faux123 Kernel
Click to expand...
Click to collapse
Errm, that's not very stock....
I can't be the only one who read the title and got happy thinking 4.2 was rolling out..
Misleading title is misleading.
I thought the same, though it's only the 7th.
Related
I'm sorry in advance if it has been asked already.
Do I need to perform any wipes before restoring a backup? I'm currently on CM7.2 RC1 and made a backup of it and want to switch to Defy+ CM9 build for a while then go back to CM7.2. Last time I did it (restored CM7 backup after installing CM9) it just stuck on Boot logo and couldn't move on so I had to start from scratch (new installation). Any guides just mention clicking on restore and that's all. Thanks in advance for an answer!
Can anyone help me? I did as I wrote (switched for a while to CM9 GB build from CM7.2 FROYO) then wanted to restore CM7 backup, tried both with and without wipes (data, cache, dalvik) but it just gets stuck on boot logo and won't move on. What am I doing wrong?
You don't need to do a wipe for restoring a nandroid..
I assume you're using the same recovery with which you made the backup..
neo.ank said:
You don't need to do a wipe for restoring a nandroid..
I assume you're using the same recovery with which you made the backup..
Click to expand...
Click to collapse
Thanks for an answer! I made a backup with CM7 (froyo) recovery and was restoring with the one that was installed along with CM9 (gb). So that was the cause?
You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..
MarcinRN said:
I'm sorry in advance if it has been asked already.
Do I need to perform any wipes before restoring a backup? I'm currently on CM7.2 RC1 and made a backup of it and want to switch to Defy+ CM9 build for a while then go back to CM7.2. Last time I did it (restored CM7 backup after installing CM9) it just stuck on Boot logo and couldn't move on so I had to start from scratch (new installation). Any guides just mention clicking on restore and that's all. Thanks in advance for an answer!
Click to expand...
Click to collapse
Why don't you try Dual Boot...
refer to the below mentionedlink:
http://forum.xda-developers.com/showthread.php?t=1364659
However, to install CM9 I'm not sure if someone uploaded itsnandroid backup. Please note that to use the backup and restore youcan only use a Nandroid backup as ROM.zip file can not be restored.
What I understand from your post is that you have CM9 rom in zipformat; if this is the case then you can only install it usingInstall from SD card option from Custom Recovery.
---------- Post added at 11:09 PM ---------- Previous post was at 11:09 PM ----------
neo.ank said:
You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..
Click to expand...
Click to collapse
Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.
neo.ank said:
You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..
Click to expand...
Click to collapse
Yes, i flashed CM9 through recovery.
Rajneeshgadge17 said:
Why don't you try Dual Boot...
refer to the below mentionedlink:
http://forum.xda-developers.com/showthread.php?t=1364659
However, to install CM9 I'm not sure if someone uploaded itsnandroid backup. Please note that to use the backup and restore youcan only use a Nandroid backup as ROM.zip file can not be restored.
What I understand from your post is that you have CM9 rom in zipformat; if this is the case then you can only install it usingInstall from SD card option from Custom Recovery.
Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.
Click to expand...
Click to collapse
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?
MarcinRN said:
Yes, i flashed CM9 through recovery.
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?
Click to expand...
Click to collapse
Technically, you haven't done anything wrong. What I've learnt from my experience and posts, this is one heck of a weird phone.
Might be a chance your backup is corrupted or incomplete (highly unlikely bt I've seen it in a device)
Or some other glitch which m nt sure of..
Sent from my MB526 using Tapatalk 2
Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.
Click to expand...
Click to collapse
Well as I said..this phone definitely acts senseless sometimes.. a data wipe in my case didn't remove the recovery or bootmenu.
Even reported it in the app thread..
Sent from my MB526 using Tapatalk 2
neo.ank said:
Technically, you haven't done anything wrong. What I've learnt from my experience and posts, this is one heck of a weird phone.
Might be a chance your backup is corrupted or incomplete (highly unlikely bt I've seen it in a device)
Or some other glitch which m nt sure of..
Click to expand...
Click to collapse
It was second time it failed to restore a backup I was trying to do the same a while ago and was unsuccesfull too. Seems like my phone is cursed
Thanks for trying anyway!
MarcinRN said:
Yes, i flashed CM9 through recovery.
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?
Click to expand...
Click to collapse
Now, I understand your issue.
Try using below mentioned steps:
1. Boot into latest/custom recovery;
2. Wipe data/cache;
3. Restore the complete Nandroid backup;
4. Now from advance wipe dalvik cache and battery logs;
5. Now reboot the phone.
Please use above mentioned steps and share the results.
Hope this helps!!
Also try to install latest clockwordmod backup.
check this website for more detail http://www.clockworkmod.com/
@MarcinRN
I think your problem is kernel related, if you switch to CM7 from CM9 with GB-Kernel you must restore the froyo-kernel for CM7.
RATTAR said:
@MarcinRN
I think your problem is kernel related, if you switch to CM7 from CM9 with GB-Kernel you must restore the froyo-kernel for CM7.
Click to expand...
Click to collapse
That's the problem. You can find the kernels on epsy's site. Flash the kernel and restore the nand (there are also options in advanced restore if it still doesn't work, don't know if you need them)
Sent from my MB525 using XDA
Thanks guys I'll try it next time. However, I read somewhere that backup contains kernel too, don't know how much true is in that.
So, I thought I'd see what Jelly Bean was like on the Galaxy S. I have had CM9 on there for a while.
Thought I'd be sensible and do a Nandroid backup - never done that before but seems like a sensible thing.
It all backs up fine. So I reboot the phone and it's in a boot loop. I also can't use the three button combo to get back to recoverly - only the three button download combo works.
What is going on? I only did a backup!
Just to add the complete set of steps. I have the latest stable CM9 installed already.
Boot into recovery.
Select backup/restore.
Select backup.
Wait for backup to finish.
Back one screen.
Reboot phone.
magneze said:
Just to add the complete set of steps. I have the latest stable CM9 installed already.
Click to expand...
Click to collapse
Try flashing the ICS semaphore kernel from My Android Collections to recover
xsenman said:
Try flashing the ICS semaphore kernel from My Android Collections to recover
Click to expand...
Click to collapse
I reflashed using stock 2.3.6 and Odin and then I could restore from the Nandroid backup.
Bit weird all in all. I could understand this if I had flashed or restored something, but I just did the backup!
magneze said:
I reflashed using stock 2.3.6 and Odin and then I could restore from the Nandroid backup.
Bit weird all in all. I could understand this if I had flashed or restored something, but I just did the backup!
Click to expand...
Click to collapse
Its possible when you reboot phone, your new settings might have taken effect that were there earlier . ( Normally for a complete change of ROM, you need to wipe before and after flashing a ROM, failing to do so, can have some effect when phone is rebooted. )
So ive been having this issue and it started all after i tried to flash the ubuntu zips that were supposed to work with a custom recovery. I flashed correctly as everyone said to do so, and my recovery would restart during flashing of the armhf.zip(the larger zip). The armhf.zip would get around 2/3 done and then just restart the recovery but now i am having the problem that i cannot recover from any of my recoveries without my recovery restarting. TWRP will recover the system and then while it is recovering the /data partition it restarts back into the recovery, but does not finish the restore. I am running the latest twrp 2.4.1.0. Please let me know if anyone knows how to fix this issue, or if you have experienced this.
Thanks in advance,
I am wondering if i am going to have to flash factory firmware and rom from google and unroot, and then reroot and what not. Just let me know if any of this would help.
Ran into the same exact thing. Had limited success wiping, restoring nandroid backups, or installing CM10 nightlies. I was finally able to get back up and running this morning using http://forum.xda-developers.com/showthread.php?t=2121673 to do a full wipe then install a clean Android ROM.
Sent from my Nexus 10 using Tapatalk HD
melvis02 said:
Ran into the same exact thing. Had limited success wiping, restoring nandroid backups, or installing CM10 nightlies. I was finally able to get back up and running this morning using http://forum.xda-developers.com/showthread.php?t=2121673 to do a full wipe then install a clean Android ROM.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
I am able to flash ROMs fine, its just restoring from nandroid that messes it up, did you do the kernel cleaner and superwipe or just the super wipe zip?
Edit: nevermind I just flashed super wipe, and everything is all good now, I can fully restore. Thanks for the help, I appreciate it.
Sent from my Nexus 10 using xda app-developers app
Hello, I am on CM10.2 nightlies for now but I would like to test out paranoid android 3.97.
If I make a nandroid of my current ROM, and then wipe data and stuff and then flash the rom and gapps, is it then possible to restore my nandroid and just update the cm10.2 nightlies with cyandelta like I used to do before?
Yes but if you referring to the OTA Updater then that is currently not working due to server maintenance to fix a redirection issue causing the page to redirect to the device page which is an issue to the updater.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Yes but if you referring to the OTA Updater then that is currently not working due to server maintenance to fix a redirection issue causing the page to redirect to the device page which is an issue to the updater.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
How do you mean? If I install PA now, and then restore my nandroid of CM10.2, I wont be able to use Cyandelta?
Thibaultvw said:
How do you mean? If I install PA now, and then restore my nandroid of CM10.2, I wont be able to use Cyandelta?
Click to expand...
Click to collapse
If you did a nandroid of your CM10, wiped everything except for your userdata partition and flashed PA, it'll work.
If you flashed PA on top of CM10 WITHOUT WIPING, it PROBABLY would work but you'd run into a bunch of errors.
What the user on top was saying is that the OTA updater for PA is not really working right now. Nothing to do with Cyandelta.
And yes, if you want to restore your CM10 nandroid, just wipe the phone and restore the nandroid. (or just restore.. but i'd still wipe first.) and it'll work exactly as it is before.
I just flashed a 802d stock ROM through TWRP 2.7 (AutoRec). I started out by wiping dalvik cache, cache and data. I then pressed Install and found the zip and installed that. After it was done, I did a dalvik + cache wipe again just to be safe (It asked if I wanted and I complied). Rebooted into system. It was quite buggy to begin with, so I wanted to try re-flashing, but it looks like my custom recovery has disappeared. I assume my root access went with it.
Everytime I try to get into recovery. It doesn't show the TWRP recovery, but merely ask if I want to factory reset my phone.
Currently, I'm downloading a clean kdz of the 802d ROM (it's taking a while) and aim to start all over with rooting and installing custom recovery and re-installing apps, but if anyone has a different solution, it would be most welcome. I'm quite the noob here. I thought TWRP would be fool-proof and would therefore allow me to restore a backup at any time. But currently, that does not appear to be the case.
Please do prove me wrong
Depends on what custom rom you were installing.
Trixanity said:
I just flashed a 802d stock ROM through TWRP 2.7 (AutoRec). I started out by wiping dalvik cache, cache and data. I then pressed Install and found the zip and installed that. After it was done, I did a dalvik + cache wipe again just to be safe (It asked if I wanted and I complied). Rebooted into system. It was quite buggy to begin with, so I wanted to try re-flashing, but it looks like my custom recovery has disappeared. I assume my root access went with it.
Everytime I try to get into recovery. It doesn't show the TWRP recovery, but merely ask if I want to factory reset my phone.
Currently, I'm downloading a clean kdz of the 802d ROM (it's taking a while) and aim to start all over with rooting and installing custom recovery and re-installing apps, but if anyone has a different solution, it would be most welcome. I'm quite the noob here. I thought TWRP would be fool-proof and would therefore allow me to restore a backup at any time. But currently, that does not appear to be the case.
Please do prove me wrong
Click to expand...
Click to collapse
Ok first if you really do have custom recovery in the factory reset screen clicking the power button three times will boot you into recovery, if you can boot into the Rom then download a root checker app to check if you still have root
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
Ok first if you really do have custom recovery in the factory reset screen clicking the power button three times will boot you into recovery, if you can boot into the Rom then download a root checker app to check if you still have root
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2736854 <- this is the ROM I flashed. It's a stock ROM containing the latest d firmware for the D802.
I just checked for root access - it's not there anymore. I will try to boot into recovery now through the method you suggested. I'll edit my post with the results.
Edit: Your method worked My recovery is there. Great! I thought it would boot straight into recovery, so the factory reset option mislead me. Now, I have to ask: did I do anything wrong in my flashing? For example. In the Mount section, only Data and Cache is mounted. Should system be mounted or is it irrelavant? Is there anything in particular I need to do in Wipe? I merely pressed Advanced Wipe and seleceted Dalvik Cache, Data and Cache and swiped to wipe. That's it.
Trixanity said:
http://forum.xda-developers.com/showthread.php?t=2736854 <- this is the ROM I flashed. It's a stock ROM containing the latest d firmware for the D802.
I just checked for root access - it's not there anymore. I will try to boot into recovery now through the method you suggested. I'll edit my post with the results.
Click to expand...
Click to collapse
well if you would have noticed in the install process it states to flash supersu after flashing the rom
XxZombiePikachu said:
well if you would have noticed in the install process it states to flash supersu after flashing the rom
Click to expand...
Click to collapse
Yeah, I did read that. This might sound stupid, but I figured that the listed SuperSU update was meant for people with an older version of SuperSU as in making sure to have the latest version of SuperSU, since I already had the latest version, I neglected to do that step. My bad. I will copy the zip in question to my phone and try re-flash both zips and see what happens. At least I have my backups to fall back on.
Another dumb question if you will. Since I didn't wipe any of my data. My apps are still present in the file system, but they are not installed nor do they have market links. Is there a way to install them or should I try to recover them through Titanium Backup? Or is it easier to simply wipe the data as well and use Titanium Backup to restore my apps?
Trixanity said:
Another dumb question if you will. Since I didn't wipe any of my data. My apps are still present in the file system, but they are not installed nor do they have market links. Is there a way to install them or should I try to recover them through Titanium Backup? Or is it easier to simply wipe the data as well and use Titanium Backup to restore my apps?
Click to expand...
Click to collapse
I think you should wipe and restore from tibu since there isn't a guarantee that redownloading your apps from the playstore will keep there old data
Thank you so much for taking your time to answer my questions. The second flash seemed succesful, but it didn't fix my biggest reason for flashing the ROM in the first place: the hissing audio bug. So I'll just try to do a restore of my latest backup and I'll make do with my temporary fix that actually works.
While it may seem to that I have wasted everyone's time, I think I've learned some valuable lessons, so I don't think it was entirely a bad thing
Hopefully, my restore will be succesful
Trixanity said:
Thank you so much for taking your time to answer my questions. The second flash seemed succesful, but it didn't fix my biggest reason for flashing the ROM in the first place: the hissing audio bug. So I'll just try to do a restore of my latest backup and I'll make do with my temporary fix that actually works.
While it may seem to that I have wasted everyone's time, I think I've learned some valuable lessons, so I don't think it was entirely a bad thing
Hopefully, my restore will be succesful
Click to expand...
Click to collapse
just in case since you don't mention the fix, I know the kk audio bug has a fix with g2tweaksbox over in the faq of first post it explains what needs to be done
XxZombiePikachu said:
just in case since you don't mention the fix, I know the kk audio bug has a fix with g2tweaksbox over in the faq of first post it explains what needs to be done
Click to expand...
Click to collapse
I did try that fix. It didn't remove the hiss entirely for me. Maybe removed 50% of the hiss, but I've heard of it working 100% for a lot of people. I've been using the ELT > Audio Loopback test from the hidden menu. It removes the hiss by about 99%. Only annoying thing is that I need to do it on every reboot which is why I wanted a more permanent fix.
Seems like my restore has caused a bootloop. Everything went accordingly, except the installation of SuperSU afterwards. Kept saying it failed to copy to the system folder despite system being mounted. The bootloop started when trying to boot into system after restore + failed SuperSU installation.
Edit: Fixed the SuperSU failure to install by wiping dalvik etc. but bootloop persists. I somewhat assume this is because the restore function doesn't work when the current ROM is different from the ROM the backup was made with? The backup was made with D802 20b firmware and the current ROM which is the one I flashed was the D802 20d firmware. Am I on to something?
Trixanity said:
I did try that fix. It didn't remove the hiss entirely for me. Maybe removed 50% of the hiss, but I've heard of it working 100% for a lot of people. I've been using the ELT > Audio Loopback test from the hidden menu. It removes the hiss by about 99%. Only annoying thing is that I need to do it on every reboot which is why I wanted a more permanent fix.
Seems like my restore has caused a bootloop. Everything went accordingly, except the installation of SuperSU afterwards. Kept saying it failed to copy to the system folder despite system being mounted. The bootloop started when trying to boot into system after restore + failed SuperSU installation.
Edit: Fixed the SuperSU failure to install by wiping dalvik etc. but bootloop persists. I somewhat assume this is because the restore function doesn't work when the current ROM is different from the ROM the backup was made with? The backup was made with D802 20b firmware and the current ROM which is the one I flashed was the D802 20d firmware. Am I on to something?
Click to expand...
Click to collapse
A backup restore should always work whether different versions or not, are you able to get into download mode?have you tried kdz to stock?
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
A backup restore should always work whether different versions or not, are you able to get into download mode?have you tried kdz to stock?
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
I just fixed it by going into recovery and flashing the D802 20d firmware again. It'll do for now. Honestly don't know why the restore from backup didn't work. Either the backup was corrupt or I've done something wrong.
I did restore my apps (so far) flawlessly and the rom does appear to perform similarly to my older firmware. Plus there's added features such as knock code so it's not all bad.
I do have a D802 20d kdz firmware available on my computer in case I want to go completely stock and/or start over. But I'll give this one a try over the next few days and see whether I'll keep this.
Trixanity said:
I just fixed it by going into recovery and flashing the D802 20d firmware again. It'll do for now. Honestly don't know why the restore from backup didn't work. Either the backup was corrupt or I've done something wrong.
I did restore my apps (so far) flawlessly and the rom does appear to perform similarly to my older firmware. Plus there's added features such as knock code so it's not all bad.
I do have a D802 20d kdz firmware available on my computer in case I want to go completely stock and/or start over. But I'll give this one a try over the next few days and see whether I'll keep this.
Click to expand...
Click to collapse
yea I'm still waiting for that knock code update on my g2, times like these make you hate being with carriers