Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS
kradkovich said:
Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS
Click to expand...
Click to collapse
By default, you have to backup Boot, System and Data
Braakie said:
By default, you have to backup Boot, System and Data
Click to expand...
Click to collapse
and that will bring me back like i left off if i restore boot, system, and data?
Don't you have to disable all security passwords like pattern lock and fingerprints before making a nandroid or it won't work when you restore? I read that in the How to thread for the 6P. Wondering if this is true or not.
kradkovich said:
Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS
Click to expand...
Click to collapse
See section 4 of my guide.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
See section 4 of my guide.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?
Krunk83 said:
Don't you have to disable all security passwords like pattern lock and fingerprints before making a nandroid or it won't work when you restore? I read that in the How to thread for the 6P. Wondering if this is true or not.
Click to expand...
Click to collapse
Yes that would be true, you would have to disable any type of lockscreen security because it wont let you unlock your phone after restoring.
kradkovich said:
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?
Click to expand...
Click to collapse
Thats not even remotely a clean wipe and would cause nothing but issues.
I would highly recommend not doing that.
Sent from my Nexus 6P, Note 5, Nexus 6 or Note 4
kradkovich said:
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?
Click to expand...
Click to collapse
Noooooooo. When flashing a different ROM you need to clean flash (wipe system, data, cache, dalvik cache).
I have a pattern lock and fingerprints and restore my backup without any problems?
Braakie said:
I have a pattern lock and fingerprints and restore my backup without any problems?
Click to expand...
Click to collapse
Which partitions do you backup and restore?
I don't feel the original question has been fully answered and explained.
The usual answer is: boot, system, data.
In the guide, section 4 that Heisenberg links however, vendor is added to the mix.
Remaining questions:
- Is vendor needed for usual backup together with boot, system and data. If so, why? What does it contain?
- What about the remaining partitions? Vendor image, system image. What do they contain and why do we not need them backed up?
---------- Post added at 01:40 PM ---------- Previous post was at 01:39 PM ----------
Also, yes you can still get back into a backup with fingerprint lock still active. See this post:
http://forum.xda-developers.com/showpost.php?p=64321640&postcount=91
TigerSoul925 said:
I don't feel the original question has been fully answered and explained.
The usual answer is: boot, system, data.
In the guide, section 4 that Heisenberg links however, vendor is added to the mix.
Remaining questions:
- Is vendor needed for usual backup together with boot, system and data. If so, why? What does it contain?
- What about the remaining partitions? Vendor image, system image. What do they contain and why do we not need them backed up?
---------- Post added at 01:40 PM ---------- Previous post was at 01:39 PM ----------
Also, yes you can still get back into a backup with fingerprint lock still active. See this post:
http://forum.xda-developers.com/showpost.php?p=64321640&postcount=91
Click to expand...
Click to collapse
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.
Gizmoe said:
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.
Click to expand...
Click to collapse
The only issue with not backing up and restoring the vendor partition, and the reason I include that in my guide, is if you have themes applied they will survive through the wipe and be carried onto the restore/flash, potentially causing compatibility issues and a failure to boot or a wonky/unusable system after boot.
Gizmoe said:
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.
Click to expand...
Click to collapse
Heisenberg said:
The only issue with not backing up and restoring the vendor partition, and the reason I include that in my guide, is if you have themes applied they will survive through the wipe and be carried onto the restore/flash, potentially causing compatibility issues and a failure to boot or a wonky/unusable system after boot.
Click to expand...
Click to collapse
Oh so that's the reason! Well thanks, then I know what to do! I'll include the vendor partition then just for safety. I already have a complete backup of all partitions except recovery and cache too so I'll just keep that safe somewhere just in case.
Thanks for the replies!
Heisenberg said:
Which partitions do you backup and restore?
Click to expand...
Click to collapse
I backup/restore my boot, data and system partitions to data/media (SDCard)
So what are other options such as system image?
Is it necessary to back it up? I just backed up the default ones
survivor_evil said:
So what are other options such as system image?
Is it necessary to back it up? I just backed up the default ones
Click to expand...
Click to collapse
System.img is just that. An exact image copy of the system image in one chunk. So you would end up with IMG files. It's not necessary to choose the IMG options. Default options for boot, system and data is a complete backup.
Related
Hello!
Only one question..
Im on 4.2.2 with new baseband
When i want to wipe all my data,so i have the whole space back, what button i have to push in twrp ? Wipe data only or more?
And after that i can push my PA 3.0 via adb push on my nexus and flash it without problems ? Thank you guys and sorry for my noob english,i hope u understand what i want to do
Sent from my Nexus 4 using xda premium
In TWRP, click Wipe, then Format Data. Be warned, you'll lose everything, including backups.
USSENTERNCC1701E said:
In TWRP, click Wipe, then Format Data. Be warned, you'll lose everything, including backups.
Click to expand...
Click to collapse
Does it erase TWRP itself?
Does it erase EFS as well?
I assume after I press this, I will have to push a rom in via Odin for example?
the_hatrix said:
Does it erase TWRP itself?
Does it erase EFS as well?
I assume after I press this, I will have to push a rom in via Odin for example?
Click to expand...
Click to collapse
Are you joking mate or just trolling. I hope so otherwise you better buy a iPhone
No not really as I never clicked Format Data before.
I assume it doesn't wipe TWRP itself... but I just want to be sure.
As for EFS I asked because I have a persistent No Service - Selected Network Unavailable showing up since a few days ago. Restore, Full Wipe, Restart, Reconnecting, nothing works. I suspect it might be the EFS partition (TWRP never backed it up as it always fails when it gets to that point, the backup works fine regardless)
So I am down to probably doing a Full Data wipe and install a fresh rom to see if it will fix it.
the_hatrix said:
No not really as I never clicked Format Data before.
I assume it doesn't wipe TWRP itself... but I just want to be sure.
As for EFS I asked because I have a persistent No Service - Selected Network Unavailable showing up since a few days ago. Restore, Full Wipe, Restart, Reconnecting, nothing works. I suspect it might be the EFS partition (TWRP never backed it up as it always fails when it gets to that point, the backup works fine regardless)
So I am down to probably doing a Full Data wipe and install a fresh rom to see if it will fix it.
Click to expand...
Click to collapse
You don`t have to wipe if you flash a factory image in fastboot. Everything will be erased after the wipe. Look here for how to do it http://forum.xda-developers.com/showthread.php?t=2010312.
I'd like an answer to this too.
I want to nuke all data on my N4 (I've saved backups and media on my PC), so that i have a clean phone ready to flash a new ROM (copied across by USB after the wipe) so that any old program folders are gone and I've got a clean slate. But don't want to lose my TWRP recovery/root etc.
I recall that CWM had an option to wipe everything but still had the sense to avoid wiping itself! What's the point of a recovery that nukes itself in the process? That's just retarded - no offence.
Thanks.
gee2012 said:
You don`t have to wipe if you flash a factory image in fastboot. Everything will be erased after the wipe. Look here for how to do it http://forum.xda-developers.com/showthread.php?t=2010312.
Click to expand...
Click to collapse
So thanks to this forum, I thought I bricked my phone last night (well I kinda did). I used the format option on TWRP and magic happened, I was stuck at the logo. I figured I'd just use Odin to flash my official rom, which worked fine. Now I wanna flash the rom I had before formatting but want all the space back (I dont want all of the bloatware folders and bull**** that result from the official rom, which is why I used format in the first place). My questions is: Can I use format now that I have my official rom running and then push a custom rom through Odin? Will that work or not?
Globespy said:
I'd like an answer to this too.
I want to nuke all data on my N4 (I've saved backups and media on my PC), so that i have a clean phone ready to flash a new ROM (copied across by USB after the wipe) so that any old program folders are gone and I've got a clean slate. But don't want to lose my TWRP recovery/root etc.
I recall that CWM had an option to wipe everything but still had the sense to avoid wiping itself! What's the point of a recovery that nukes itself in the process? That's just retarded - no offence.
Thanks.
Click to expand...
Click to collapse
If you use twrp and factory reset it will wipe data not the sd partition if you wipe system it wipes the ROM if you wipe data it will wipe SD partition including your backups. None of those will remove your recovery. Nothing will touch efs partition this is not a Samsung device
Sent from my Nexus 4
Globespy said:
I'd like an answer to this too.
I want to nuke all data on my N4 (I've saved backups and media on my PC), so that i have a clean phone ready to flash a new ROM (copied across by USB after the wipe) so that any old program folders are gone and I've got a clean slate. But don't want to lose my TWRP recovery/root etc.
I recall that CWM had an option to wipe everything but still had the sense to avoid wiping itself! What's the point of a recovery that nukes itself in the process? That's just retarded - no offence.
Thanks.
Click to expand...
Click to collapse
You are showing a complete lack of understanding on the subject. I would recommend doing more reading before you mess with your device.
It is impossible to have root when you don't have a rom on your phone. Clearing all data erases root as well. Flashing a rooted rom (nearly all are rooted) establishes root again.
Wiping data in recovery does not wipe the recovery for one extremely simple reason - recovery has its own partition on any device. The only way recovery could ever be wiped is by flashing a recovery.img file by fastboot (such as the Google factory images).
Sent from my iPad 4
---------- Post added at 03:03 PM ---------- Previous post was at 02:58 PM ----------
FlashThisB said:
So thanks to this forum, I thought I bricked my phone last night (well I kinda did). I used the format option on TWRP and magic happened, I was stuck at the logo. I figured I'd just use Odin to flash my official rom, which worked fine. Now I wanna flash the rom I had before formatting but want all the space back (I dont want all of the bloatware folders and bull**** that result from the official rom, which is why I used format in the first place). My questions is: Can I use format now that I have my official rom running and then push a custom rom through Odin? Will that work or not?
Click to expand...
Click to collapse
Odin?????????
Do you have a Samsung Nexus 4????
Sent from my iPad 4
For some reason in my HTC One X wipe sdcard doesn't work with twrp. I've noticed that in the hardest and surprising way once that j was trying to flash a new rom and before flash I hit the wipe sdcard button. It supposed to delete everything but I didn't. Thanks god it didn't wiped my data, but now that I am safe I want to delete all from recovery and it just don't work.
Sent from The HTC One X Mongrel Cat.
mitchdickson said:
You are showing a complete lack of understanding on the subject. I would recommend doing more reading before you mess with your device.
It is impossible to have root when you don't have a rom on your phone. Clearing all data erases root as well. Flashing a rooted rom (nearly all are rooted) establishes root again.
Wiping data in recovery does not wipe the recovery for one extremely simple reason - recovery has its own partition on any device. The only way recovery could ever be wiped is by flashing a recovery.img file by fastboot (such as the Google factory images).
Sent from my iPad 4
---------- Post added at 03:03 PM ---------- Previous post was at 02:58 PM ----------
Odin?????????
Do you have a Samsung Nexus 4????
Sent from my iPad 4
Click to expand...
Click to collapse
lol nonono I have a samsung galaxy S4 i337M. Sorry for posting in the wrong section but this is all I found on XDA regarding TWRP formatting option.
mitchdickson said:
You are showing a complete lack of understanding on the subject. I would recommend doing more reading before you mess with your device.
It is impossible to have root when you don't have a rom on your phone. Clearing all data erases root as well. Flashing a rooted rom (nearly all are rooted) establishes root again.
Wiping data in recovery does not wipe the recovery for one extremely simple reason - recovery has its own partition on any device. The only way recovery could ever be wiped is by flashing a recovery.img file by fastboot (such as the Google factory images).
Sent from my iPad 4
---------- Post added at 03:03 PM ---------- Previous post was at 02:58 PM ----------
Odin?????????
Do you have a Samsung Nexus 4????
Sent from my iPad 4
Click to expand...
Click to collapse
Thanks for your reply, sorry my knowledge of this subject isn't as strong as yours.
So I can choose wipe data, then copy a new ROM using USB and flash on a clear device?
Globespy said:
Thanks for your reply, sorry my knowledge of this subject isn't as strong as yours.
So I can choose wipe data, then copy a new ROM using USB and flash on a clear device?
Click to expand...
Click to collapse
Yes. U will need to use adb to push the ROM after wiping data though.
Sent from my HTC Desire using xda app-developers app
hey im using paranoid android 3.56 and i want to update it to 3.60 will i loose my data if i do so and also im using nexus 4
yes u will loose
but u can take backup also
rasroh said:
yes u will loose
but u can take backup also
Click to expand...
Click to collapse
how to i backup my entire phone data to my pc
sum93 said:
hey im using paranoid android 3.56 and i want to update it to 3.60 will i loose my data if i do so and also im using nexus 4
Click to expand...
Click to collapse
No. You will not lose your data if you dirty flash the new rom. That means, if you just clear cache andd dalvik cache before flashing the new rom, your data wont be deleted. As you are upgrading from one version of the same rom to another, this will function as well as a clean flash.
A clean flash implies you will have to clear data too in the recovery along with cache and dalvik cache. As I said before, this isnt needed when upgrading from one version of a rom to another of the same. However, if you are shifting from one rom to a different one, clean flash is recommended.
So in conclusion, these are the steps you will have to follow to upgrade to the new rom -
1. Download the new upgraded version of the rom and gapps(if not included in the rom). Also take backups (titanium or/and nandroid as required)
2. Boot into recovery.
3. Clean cache.
4. Clean dalvik cache.
5. Flash new rom.
6. Flash gapps.(if not included in the rom)
7. Clean cache and dalvik again.
8. Reboot to system.
Thus, no data wipe required. Your data and applications will be safe.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
---------- Post added at 05:27 PM ---------- Previous post was at 05:24 PM ----------
rasroh said:
yes u will loose
but u can take backup also
Click to expand...
Click to collapse
Please do research some on the topic before giving any advice
Most roms do not ask for a clean flash when upgrading the rom, so he won't lose his data. Unless oyherwise recommended by the developer, he doesnt have to clear his data when going from one version of a rom to a new one.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
use a backup app like titanium, helium etc
sum93 said:
hey im using paranoid android 3.56 and i want to update it to 3.60 will i loose my data if i do so and also im using nexus 4
Click to expand...
Click to collapse
If you're just updating a rom you wont lose any data. All you have to do is flash the new rom on top of the old one and that's it. No need to wipe anything.
If you are upgrading from one version of a rom to a higher version of the same rom, you can usually dirty flash (flash on top without wiping) without losing any data.
Also even if you did "wipe date", it won't touch your /data/media which is basically where your /sdcard stuff lives (it will just wipe your apps, settings, etc data, so a backup via recovery is usually advised anyways).
On a related note: what does it take to wipe all of your data off your phone? Basically, to get the Nexus 4 back to brand-new, out-of-the-box fresh? Is there an easy way to do it or do you have to manually wipe different locations and if the latter, what locations must you wipe?
Johmama said:
On a related note: what does it take to wipe all of your data off your phone? Basically, to get the Nexus 4 back to brand-new, out-of-the-box fresh? Is there an easy way to do it or do you have to manually wipe different locations and if the latter, what locations must you wipe?
Click to expand...
Click to collapse
If you are on a stock rom, a simple "format data" from recovery would do the trick as it would wipe /data and /data/media. As the stock rom on /system never changes unless you rooted and added stuff to it. (fastboot can do this too from the bootloader with fastboot erase userdata).
Alternatively, you can just unpack the factory firmware and flash the *.img to their respective partitions (boot[kernel], system, userdata, etc) from this list https://developers.google.com/android/nexus/images#occamjdq39 (PS: I wouldn't bother touching the bootloader as most people never changed it other than to maybe unlock it).
Nutshell version: All your user-specific stuff lies under /data (settings, downloaded apps, media, etc)
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Tried clearing cache? Also, what things did you precisely backup?
DJBhardwaj said:
Tried clearing cache? Also, what things did you precisely backup?
Click to expand...
Click to collapse
almost everything including vendor ; no cache
setul34 said:
almost everything including vendor ; no cache
Click to expand...
Click to collapse
I had the same issue when I backed up system image.
DJBhardwaj said:
I had the same issue when I backed up system image.
Click to expand...
Click to collapse
okay so any solution?
Try it without the system image.
DJBhardwaj said:
Try it without the system image.
Click to expand...
Click to collapse
i did but that did not install root / apps / settings. basically i just got data and stock rom.
setul34 said:
i did but that did not install root / apps / settings. basically i just got data and stock rom.
Click to expand...
Click to collapse
No idea, I myself haven't tried further.
Lets see if someone else comes up with something
setul34 said:
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Click to expand...
Click to collapse
Let me guess you are on TWRP 3.0.0.0?
Yes
oneandroidnut said:
Let me guess you are on TWRP 3.0.0.0?
Click to expand...
Click to collapse
@oneandroidnut Yes.
setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
You don't backup system image, only backup system, data, and boot.
setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
pm me if you are still having issues we can go to hangouts or something and i can walk you through
oneandroidnut said:
pm me if you are still having issues we can go to hangouts or something and i can walk you through
Click to expand...
Click to collapse
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Heisenberg said:
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Click to expand...
Click to collapse
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
this worked for me thankyou
Heisenberg said:
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
Click to expand...
Click to collapse
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
setul34 said:
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
this worked for me thankyou
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
Click to expand...
Click to collapse
No problem man glad it worked!!
I had the same problem.
I tried to restore a backup (MMB29Q - system+data+boot, done after installing the last factory image without root) and I got blocked on the Google logo. I tried twice without managing.
In the end I solved the problem installing supersu v2.68 zip before restarting.
It's as though the restore needs the root to work properly.
What do you think?
Thanks.
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!
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.
Just got my RMA, so of course I instantly unlock, root, and go to disable forced encryption and i keep getting a password error, my only pin i've ever used won't work, so I flashed factory, reset it up, made sure i didn't use a pin or anything, tried again, still asks for a password and won't accept mine. Am I missing something or is the fact they sent me a remanufactured phone screwing me because of the previous users pin?
kickenwing13 said:
Just got my RMA, so of course I instantly unlock, root, and go to disable forced encryption and i keep getting a password error, my only pin i've ever used won't work, so I flashed factory, reset it up, made sure i didn't use a pin or anything, tried again, still asks for a password and won't accept mine. Am I missing something or is the fact they sent me a remanufactured phone screwing me because of the previous users pin?
Click to expand...
Click to collapse
What TWRP version are you using? Are you on the newest 3.03? If not that's more than likely your problem.
murphyjasonc said:
What TWRP version are you using? Are you on the newest 3.03? If not that's more than likely your problem.
Click to expand...
Click to collapse
OMG I'm confident it's 3.02. So I need to update that before I try the decrypting thing. I need to go root, twrp 3.3 then unencrypt ?
Thanks man I wouldn't ahve thought of that .
kickenwing13 said:
OMG I'm confident it's 3.02. So I need to update that before I try the decrypting thing. I need to go root, twrp 3.3 then unencrypt ?
Thanks man I wouldn't ahve thought of that .
Click to expand...
Click to collapse
Just download the updated TWRP from this link. Boot back into recovery and choose flash IMG instead of zip. Install to recovery partition and then reboot. You should be good to go.
http://dl.twrp.me/angler/
murphyjasonc said:
Just download the updated TWRP from this link. Boot back into recovery and choose flash IMG instead of zip. Install to recovery partition and then reboot. You should be good to go.
http://dl.twrp.me/angler/
Click to expand...
Click to collapse
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?
found something on a N6 thread that says wipe user data and it should work .
kickenwing13 said:
found something on a N6 thread that says wipe user data and it should work .
Click to expand...
Click to collapse
Yeah that will work and shouldn't be an issue backing up everything with a new phone. TWRP should be able to read an encrypted device though as long as you gave it permissions to change system. No kernel will decrypt a device but most do not force encrypt.
---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------
kickenwing13 said:
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?
Click to expand...
Click to collapse
Are you by chance trying to restore a backup on your RMA?
kickenwing13 said:
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?
Click to expand...
Click to collapse
I had a similar problem with TWRP 3.0.3-0 when I tried to restore a backup. It asked for a password, which has never happened before. I couldn't access my backup or any of my data or boot up. I had to restore stock. Clearing user data did nothing.
murphyjasonc said:
Yeah that will work and shouldn't be an issue backing up everything with a new phone. TWRP should be able to read an encrypted device though as long as you gave it permissions to change system. No kernel will decrypt a device but most do not force encrypt.
---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------
Are you by chance trying to restore a backup on your RMA?
Click to expand...
Click to collapse
I was not . Just trying to disable force encrypt root and get PN back on it . Wiping worked for me. Also on 3.03, but that alone didn't solve, had to wipe . May be because I was using WUGS instead of manually doing it . Not sure, but it worked .
kickenwing13 said:
I was not . Just trying to disable force encrypt root and get PN back on it . Wiping worked for me. Also on 3.03, but that alone didn't solve, had to wipe . May be because I was using WUGS instead of manually doing it . Not sure, but it worked .
Click to expand...
Click to collapse
Hey, I'm running into the same problem after an RMA. I'm currently on stock unrooted 7.1.1 and want to flash custom rom but want to disable encryption beforehand. Can you advise proper wipe steps, or is this correct?
- unlock bootloader
- restart phone, enable developer options for USB debugging
- fastboot twrp-3.0.3-0-angler.img
- factory reset
- wipe everything (all checkboxes) including internal? (will this format with no encryption?)
- wipe system, data, cache
- push ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip to phone via ADB in TWRP
- flash ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip
- restart
Or is there another way to decrypt data or is it not an issue when clean wiping a new ROM?
Thanks and appreciate any help.
martinomac said:
Hey, I'm running into the same problem after an RMA. I'm currently on stock unrooted 7.1.1 and want to flash custom rom but want to disable encryption beforehand. Can you advise proper wipe steps, or is this correct?
- unlock bootloader
- restart phone, enable developer options for USB debugging
- fastboot twrp-3.0.3-0-angler.img
- factory reset
- wipe everything (all checkboxes) including internal? (will this format with no encryption?)
- wipe system, data, cache
- push ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip to phone via ADB in TWRP
- flash ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip
- restart
Or is there another way to decrypt data or is it not an issue when clean wiping a new ROM?
Thanks and appreciate any help.
Click to expand...
Click to collapse
You need to Format Data, Not Wipe to decrypt. It WILL wipe EVERYTHING so make sure anything in internal storage you want is backed up.
CyberpodS2 said:
You need to Format Data, Not Wipe to decrypt. It WILL wipe EVERYTHING so make sure anything in internal storage you want is backed up.
Click to expand...
Click to collapse
Thanks for confirming, I wasn't aware that there's a difference between Format Data and Wipe Data. After formatting data, I should be able to sideload the ROM, gapps, etc back via TWRP right?
I always try to keep an emergency folder on the PC with the minimum needed to copy back to the phone through recovery. In my case I keep a copy of pure nexus, dynamic gapps, supersu and elementalx. That combination never fails to boot and I know it well enough to get back in business in short order if it all went to hell. Do what's best for you.
Sent from my Nexus 6 using XDA-Developers Legacy app