So I made a backup as I wanted to dirty flash PN again to change kernel. My phone bootlooped after I flashed PN and franco kernel. So i decided to restore my working backup..still boot looping... WHY?! this phone never successfully restores backups in my experience.
gman88667733 said:
So I made a backup as I wanted to dirty flash PN again to change kernel. My phone bootlooped after I flashed PN and franco kernel. So i decided to restore my working backup..still boot looping... WHY?! this phone never successfully restores backups in my experience.
Click to expand...
Click to collapse
Try flashing stock boot image back to device first. Then do a factory wipe and then try the restore.
XxMORPHEOUSxX said:
Try flashing stock boot image back to device first. Then do a factory wipe and then try the restore.
Click to expand...
Click to collapse
How do i do that? Never done that before!! Thanks
gman88667733 said:
How do i do that? Never done that before!! Thanks
Click to expand...
Click to collapse
Look in heisenburgs guide about restoring. The steps to flash the factory images is the same. Just do the boot.img
I think i solved the issue, thank you for the help, I appreciate it a lot
I managed to get my backup restored.. But it gives me a google services force close.. Whyyyy
Wipe your cache and dalvik cache. It should clear up the issue.
Related
Any ideas on this one? I don't get any errors on the restore, but I am stuck on the eye every time I boot. I have tried wiping cache and dalvik cache.
About to just restore from Matt's tool, but this has me worried, you know?
Coronado is dead said:
Any ideas on this one? I don't get any errors on the restore, but I am stuck on the eye every time I boot. I have tried wiping cache and dalvik cache.
About to just restore from Matt's tool, but this has me worried, you know?
Click to expand...
Click to collapse
Well, have to say, thanks matt. The included RSD helped.
I forgot I was also restoring stock over CM10, which may have also been the issue, but I am back into the phone now.
You shouldn't have issues restoring backup from the older version, and you shouldn't have issues restoring a stock build over CM. Did you use the restore option or did you try to install the backup?
Sent from my Slim Scorpion-mini
RikRong said:
You shouldn't have issues restoring backup from the older version, and you shouldn't have issues restoring a stock build over CM. Did you use the restore option or did you try to install the backup?
Sent from my Slim Scorpion-mini
Click to expand...
Click to collapse
I have no idea what caused the issue. I did a backup of CM10, wiped data, cache, dalvik, and system. Hit restore on my old Stock backup (created in TWRP, not safestrap), wiped dalvik and cache again, and rebooted (and allowed TWRP to fix root first). It booted to the droid eye, but then just hung there for about 10 minutes.
I used Matt's utility to restore the system and it failed (tried to install the same part of system over and over again, 3mb in 4 seconds, 100k in .4 seconds, over and over again). So I had to force stop that and use RSD which worked fine.
No idea what all that was about.
So I think I found the culprit. My backups from the older version of TWRP don't have BOOT, only SYSTEM and DATA. So I was probably having my stock rom install while the CM10 BOOT was still in place.
The more you know
So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!
alphamini said:
So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!
Click to expand...
Click to collapse
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??
Rohit02 said:
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??
Click to expand...
Click to collapse
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?
alphamini said:
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?
Click to expand...
Click to collapse
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.
Rohit02 said:
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.
Click to expand...
Click to collapse
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?
alphamini said:
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?
Click to expand...
Click to collapse
Did you use the Franco.Kernel for the JSS build?
Sent from my Nexus 4 using Tapatalk 4
Hey guys,
So i rooted my Verizon LG G2 a couple months ago and was trying out all the ROMs. I started with Paranoid Android, then AOKP, then Malladus, then Flex ROM, and now i'm back to the Paranoid Android Beta 4. It's been running great for me but I wanted to go back to stock for a little so I've come here with a question. I did a backup of my stock ROM in TWRP and still have it. What would be the process to install a brand new stock rom (completely stock, no bells and whistles)? Can I restore the backup, then go into TWRP and wipe date/cache/etc, then reboot? Should that work? It's probably a super easy question, I just don't want to mess anything up.
Thanks in advance!
Mike
That will do the trick for you. After restoring the factory backup just doing a factory reset will wipe out all of the bells and whistles you put into your backup. Should boot up just like new. I would boot the phone up first before doing the reset though. Maybe not necessary but I like to be cautious too! :laugh:
Really now said:
That will do the trick for you. After restoring the factory backup just doing a factory reset will wipe out all of the bells and whistles you put into your backup. Should boot up just like new. I would boot the phone up first before doing the reset though. Maybe not necessary but I like to be cautious too! :laugh:
Click to expand...
Click to collapse
Thank you! Yep, i'll restore the backup and make sure it boots with no problems. Then boot into recovery and wipe data/etc.
I'll make sure to backup my current rom just in case. :laugh: Better safe than sorry!
Really now said:
That will do the trick for you. After restoring the factory backup just doing a factory reset will wipe out all of the bells and whistles you put into your backup. Should boot up just like new. I would boot the phone up first before doing the reset though. Maybe not necessary but I like to be cautious too! :laugh:
Click to expand...
Click to collapse
Ut oh didn't seem to work for me. What did I miss? When i wiped, then rebooted, i was frozen at the LG screen.
Are you saying that the stock rom rebooted ok and then you wiped and it won't reboot?
Really now said:
Are you saying that the stock rom rebooted ok and then you wiped and it won't reboot?
Click to expand...
Click to collapse
Yep, I restored the file and it booted perfectly fine. Then I rebooted to recovery, wiped data, and rebooted system. It got stuck at the LG screen, so I manually entered recovery with the back keys. What did I do wrong?
WCM3 said:
Yep, I restored the file and it booted perfectly fine. Then I rebooted to recovery, wiped data, and rebooted system. It got stuck at the LG screen, so I manually entered recovery with the back keys. What did I do wrong?
Click to expand...
Click to collapse
Restore you backup again and this time when you go into TWRP don't wipe data, just swipe the Factory Reset slider. See if that solves the problem for you.
Really now said:
Restore you backup again and this time when you go into TWRP don't wipe data, just swipe the Factory Reset slider. See if that solves the problem for you.
Click to expand...
Click to collapse
Will that wipe internal storage too? I usually go into the advanced wipe and wipe everything but internal storage.
No it won't, it will dump your apps and clean the caches and reset the settings.
You can do the same thing from inside the rom by going to system settings/backup reset and doing a reset. I don't know if TWRP does a better or more thorough job of it or not but both ways work.
Hi,
Coming from PureNexus, I wanted to give CM13 a try. Made a nandroid backup so none of my data is lost, and put that backup on pc. I installed CM13 which went fine. It stopped at the CM booting animation and did not go further, so I cleanflashed Purenexus to restore my backup later on. Now PureNexus won't boot either. I'm out of ideas to try, and I want to get my phone back up and running ASAP.
Can anyone help me with this issue?
Riyge said:
Can anyone help me with this issue?
Click to expand...
Click to collapse
When you clean flashed, did you also wipe system? If you did and you're still hung at boot, your best bet would be to flash the factory images via fastboot and start fresh.
Riyge said:
Hi,
Coming from PureNexus, I wanted to give CM13 a try. Made a nandroid backup so none of my data is lost, and put that backup on pc. I installed CM13 which went fine. It stopped at the CM booting animation and did not go further, so I cleanflashed Purenexus to restore my backup later on. Now PureNexus won't boot either. I'm out of ideas to try, and I want to get my phone back up and running ASAP.
Can anyone help me with this issue?
Click to expand...
Click to collapse
Are you wiping properly (system, data, cache, dalvik cache) before installing a ROM? Are you making sure you flash the appropriate vendor image after flashing the ROM? When you made your backup which options did you check? And which options are you restoring?
Heisenberg said:
Are you wiping properly (system, data, cache, dalvik cache) before installing a ROM? Are you making sure you flash the appropriate vendor image after flashing the ROM? When you made your backup which options did you check? And which options are you restoring?
Click to expand...
Click to collapse
When I try to wipe, it's only wiping cache for some reason. My backup consists of everything except cache.
Riyge said:
When I try to wipe, it's only wiping cache for some reason. My backup consists of everything except cache.
Click to expand...
Click to collapse
What do you mean it's only wiping cache? Explain to me how you're doing the wipe. Also, when creating a backup (and restoring it) you should only be selecting system, data, boot, and vendor.
PS. You didn't answer my question about whether you're flashing the vendor after flashing the ROM. If you want help you need to answer the questions that are asked.
Heisenberg said:
What do you mean it's only wiping cache? Explain to me how you're doing the wipe. Also, when creating a backup (and restoring it) you should only be selecting system, data, boot, and vendor.
Click to expand...
Click to collapse
I'll keep that in mind. When I boot up TRWP, I wiped system, dalvik, data, internal storage and cache. After that I pushed CM13 through adb. That's where the problems started.
EDIT: I flashed the most recent vendor after I flashed the ROM.
Riyge said:
I'll keep that in mind. When I boot up TRWP, I wiped system, dalvik, data, internal storage and cache. After that I pushed CM13 through adb. That's where the problems started.
EDIT: I flashed the most recent vendor after I flashed the ROM.
Click to expand...
Click to collapse
Ok, you definitely don't need to wipe internal storage before flashing so don't worry about that part. Only system, data, cache, and dalvik cache. You said before only cache was being wiped, can you please elaborate on that?
Are you sure the ROM zip didn't become corrupt during the download? Did you check the MD5 to ensure that it didn't? That could be what's causing your problems. Also, what gapps are you flashing?
If you want to go back to Pure Nexus just to get your phone working you can just restore that backup, just make sure you only restore system, data, boot, and vendor.
Heisenberg said:
Ok, you definitely don't need to wipe internal storage before flashing so don't worry about that part. Only system, data, cache, and dalvik cache. You said before only cache was being wiped, can you please elaborate on that?
Are you sure the ROM zip didn't become corrupt during the download? Did you check the MD5 to ensure that it didn't? That could be what's causing your problems. Also, what gapps are you flashing?
If you want to go back to Pure Nexus just to get your phone working you can just restore that backup, just make sure you only restore system, data, boot, and vendor.
Click to expand...
Click to collapse
It won't wipe anything other than cache, no matter what I'm trying to do. Now when I'm trying to push a ROM through adb, I can install it but it won't boot.
Riyge said:
It won't wipe anything other than cache, no matter what I'm trying to do. Now when I'm trying to push a ROM through adb, I can install it but it won't boot.
Click to expand...
Click to collapse
I'm trying to help you here but if you keep failing to answer my questions it's impossible for me to do so. At this point I can only think that it's user error, I'd flash the factory images to return to stock and start fresh. I have detailed instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
I'm trying to help you here but if you keep failing to answer my questions it's impossible for me to do so. At this point I can only think that it's user error, I'd flash the factory images to return to stock and start fresh. I have detailed instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I found your guide by googling, thanks for making that! Flashing the factory image worked, and I succesfully restored my backup. The only problem left is that it won't accept my pattern lock. I have used the same one for years across multiple android devices, so I'm absolutely sure I have the right pattern. Any way to bypass this?
Riyge said:
I found your guide by googling, thanks for making that! Flashing the factory image worked, and I succesfully restored my backup. The only problem left is that it won't accept my pattern lock. I have used the same one for years across multiple android devices, so I'm absolutely sure I have the right pattern. Any way to bypass this?
Click to expand...
Click to collapse
You need to remove all security before making a backup because the security information is encrypted and doesn't get backed up or restored properly. You can delete some files using TWRP (see section 3 of my guide) in order to remove the security so you can get into Android. This will cause problems with Smart Lock though.
Heisenberg said:
You need to remove all security before making a backup because the security information is encrypted and doesn't get backed up or restored properly. You can delete some files using TWRP (see section 3 of my guide) in order to remove the security so you can get into Android. This will cause problems with Smart Lock though.
Click to expand...
Click to collapse
Tried that, fixed my phone. Thanks so much! Is it possible to restore these functions or should I clean flash to get it?
Riyge said:
Tried that, fixed my phone. Thanks so much! Is it possible to restore these functions or should I clean flash to get it?
Click to expand...
Click to collapse
I'd be clean flashing.
Attempt 1 to install Lineage
Tried installing the Lineage 14.1, it kept doing a blank-but-illuminated screen, then turned off and back on, resulting in a boot loop.
We tried a couple of things - first the more conservative wiping of just data, dalvik and cache.
This did the boot loop described above. I then restored the stock backup and all was well.
Attempt 2 to install Lineage
The second time we wiped the system partition in addition to the above. Same bootloop.
Went to restore the backup of stock again, but now it's getting stuck at "I'm not a phone I'm a comprehensive yada yada" screen. It never progresses past this.
Attempts to get Stock Restore working
We've tried restoring just the system, data and dalvik
We've also tried System Image in addition to these.
No joy.
We don't have a laptop or other device to hand for a few days so we have just what's on the phone - the Lineage 14.1 zip, the stock backup and TWRP.
Any ideas how we can get back to a working phone with either OS?
What type of LePro3 do you have?
X720,X722,X727?
It's the X722
kenbw2 said:
It's the X722
Click to expand...
Click to collapse
The X722 model is not supported by Lineage.
I think that you have a problem. Hope anyone can help you to go back to stock successfully.
When doing the stock restore, we didn't restore the boot image.
Is that something worth trying?
kenbw2 said:
When doing the stock restore, we didn't restore the boot image.
Is that something worth trying?
Click to expand...
Click to collapse
Yes, you could try it. Please, write, was it useful or not)
Success!
Restored System,. System Image, Cache, Data and Boot partitions and all is now back to normal.
Phew!
kenbw2 said:
Success!
Restored System,. System Image, Cache, Data and Boot partitions and all is now back to normal.
Phew!
Click to expand...
Click to collapse
That is great. So, is bluetooth works fine after that?