Hi i tried to restore my Dirty unicorns backup and now i am stuck at the google screen. I booted to twrp and tried to erase the efs but it didn't work, still stuck at google screen. Also if I recollect i did not backup and restore the efs partition so i don't know what else it could be i did backup the vendor and the rest. Using twrp 3.1.0.0
Solved, flashed the vendor the the phone booted up. can somebody please write what you can backup up in twrp so i know to not bootloop again, thank you.
AndrewM3 said:
Solved, flashed the vendor the the phone booted up. can somebody please write what you can backup up in twrp so i know to not bootloop again, thank you.
Click to expand...
Click to collapse
To backup your current setup:
Boot
System
Data
Vendor
Is enough
Just in case: https://twrp.me/faq/whattobackup.html
If you switch to another ROM, wipe the above + dalvik/ART cache, data and cache partitions.
Then flash whatever you want with matching vendor. Redo the complete wipe above and restore your backup if you want to switch back. Backup your EFS at least once and keep it in a safe place...
Hopefully you won't end up bootlooping anymore! :good:
I have never succussfully restored a nandroid backup on this phone with any version of TWRP. I don't even try anymore because it's just a waste of disc space and time.
jhs39 said:
I have never succussfully restored a nandroid backup on this phone with any version of TWRP. I don't even try anymore because it's just a waste of disc space and time.
Click to expand...
Click to collapse
I'd be glad to help you if you wish..!
Related
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!
I just got a s5. And I got it succesfully rooted and also got TWRP working on it.
All the data from my previous phone was transfered to the s5.
Now I made some backups with TWRP with the default settings: Partitions boot, system and data.
With the backups in mind I was thinking I could easily restore it to a previous state.
Thinking I backed up all the data and wanted to make it fresh again, I wanted to restore it.
In the menu I chose the restore option with the same settings as the backup: Partitions boot, system and data.
And it gives a message restoring system succesfull.
But when rebooting, it keeps hanging and at the moment of loading the android system every bit of the system keeps 'hanging'
It keeps saying
'Unfortunately touchwiz startup unsuccesfully'
'Unfortunately youtube startup unsuccesfully'
'Unfortunately greenify startup unsuccesfully'
'Unfortunately app whatever startup unsuccesfully'
And so on and so on
Eventually it starts with a black screen with nothing loaded. Complete blackout.
So this backup doesn't work. And I try my second backup.
Unfortunately also the second backup gave these errors.
And also the third backup!
So the backup files seem the right size, it's some gigabytes, and it alway's keeps saying backup/restore succesfully.
But now it fails to restore and boot the backup
The things I tried.
-Trying three different backups
-Wiping cleaning data/dalvik/cache etc etc
-Restoring a part of the backup. First system, then data, then boot, no succes.
So i'm totally lost! Does somebody know how to fix this? Or have some tips to try??
You can't restore system and boot from a different model phone
That would be like trying to flash a ROM for one model phone to another without porting it
If it was an S5 you backed up, was it the exact same model (ie: G900F etc?)
Flash back to stock, then try restoring only DATA
Or use TiBu to restore your apps from the TWRP backup
*Detection* said:
You can't restore system and boot from a different model phone
That would be like trying to flash a ROM for one model phone to another without porting it
If it was an S5 you backed up, was it the exact same model (ie: G900F etc?)
Flash back to stock, then try restoring only DATA
Or use TiBu to restore your apps from the TWRP backup
Click to expand...
Click to collapse
Thanks for the reply! It was a backup and restore on the same phone. So that is why I thought it was supposed to be a easy restore.
But I found the solution hidden somewhere in one message on XDA:
"Originally Posted by Dr. Fed
Would you happen to know why, when restoring a TW 4.4.2 nandroid using TWRP 2.8.1 or 2.8.4, after running an AOSP lollipop ROM like CM12, the TW ROM boots but then the whole system force-closes? Before restoring the nandroid, I advance wipe system, data, cache, and dalvik. Then I restore the nandroid. It boots, but then some daemon crashes. Then all processes and apps. The screen goes black after a few crashes.
So, what I do is pull out the battery, boot into recovery, advance wipe system, data, cache, dalvik, flash a CM11 ROM, reboot. I let CM11 start up, skip the set-up, then I boot back to TWRP (2.8.1 and now 2.8.4), advanced wipe, restore TW nandroid, and now it works just fine.
It seems like TWRP doesn't fully wipe."
Here the steps for if other people will run into the same problem:
Problem: Android 5 is running, with twrp 2.7 performed a back up = Restoring the backup is difficult because it problably doesn't do a clean wipe somehow.
1. I downloaded a cyanogen 11 rom, a Android 4 version.
2. Installed it with TWRP. Somehow it 'wipes' it more efficiently.
3. From cyanogen 11 back to booting TWRP.
4. In TWRP trying the Android 5 restore.
And Amazingly this worked!! = Celebrate!!
chokolademan said:
Thanks for the reply! It was a backup and restore on the same phone.
Click to expand...
Click to collapse
Confused me with this line
chokolademan said:
All the data from my previous phone was transfered to the s5.
Click to expand...
Click to collapse
Good to see you solved it
So I have been running Pure Nexus rom with Elemental X kernel and SuperSU and it's been working just fine. Well I made a nandroid, and flashed a couple new roms to try out. Didn't like any of them better so I decided to restore back to my nandroid. I used TWRP 3.0.2-2 to make the nandroid and when I tried to restore using same version it just constantly bootloops between the Google splash screen and the"Your device software cannot be checked etc etc screen". I did update my radio and bootloader to the newest versions via a flashable zip and also updated my vendor to the latest vendor image N4F26J. One of the roms said my vendor image was out of date or whatever but still booted fine for me to try out. Regardless I have factory reset phone including internal storage and flashed the factory OTA image and still no luck. Odd thing is I can still boot TWRP and also access my internal storage and move files from PC to my phone. It will even flash Roms and everything but it will not get past the Google splash screen. So wth do I do lol?
Kochoa940 said:
So I have been running Pure Nexus rom with Elemental X kernel and SuperSU and it's been working just fine. Well I made a nandroid, and flashed a couple new roms to try out. Didn't like any of them better so I decided to restore back to my nandroid. I used TWRP 3.0.2-2 to make the nandroid and when I tried to restore using same version it just constantly bootloops between the Google splash screen and the"Your device software cannot be checked etc etc screen". I did update my radio and bootloader to the newest versions via a flashable zip and also updated my vendor to the latest vendor image N4F26J. One of the roms said my vendor image was out of date or whatever but still booted fine for me to try out. Regardless I have factory reset phone including internal storage and flashed the factory OTA image and still no luck. Odd thing is I can still boot TWRP and also access my internal storage and move files from PC to my phone. It will even flash Roms and everything but it will not get past the Google splash screen. So wth do I do lol?
Click to expand...
Click to collapse
Maybe stupid answer : 1 did you flashed boot.img ?
2. Is your data partition anything like ex4 or f2fs ?
Will it stuck on google logo ? (I had stucl for 10 min once ) or it just bootloops
Why not try to flash 3.0.3.0 recovery and try again?
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
Vaseag said:
Maybe stupid answer : 1 did you flashed boot.img ?
2. Is your data partition anything like ex4 or f2fs ?
Will it stuck on google logo ? (I had stucl for 10 min once ) or it just bootloops
Why not try to flash 3.0.3.0 recovery and try again?
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
Click to expand...
Click to collapse
I tried flashing the factory image via command prompt but still bootlooping. data partition has not been modified it is still same as stock.
Kochoa940 said:
I tried flashing the factory image via command prompt but still bootlooping. data partition has not been modified it is still same as stock.
Click to expand...
Click to collapse
Did you try to flash the OTA image or full factory image? I think there is a known problem with the latest build of Pure nexus where some people can't boot past the Google logo. If that's your issue there are workarounds. You should check the Pure nexus thread.
Try a full wipe(without internal) and restore your nandroid without the data partition and let me know how it went.
If your nandroid contained the efs backup (3.0.2-2 backs it up by default) and you restored your backup with the efs partition your borked since you used TWRP 3.0.2-2. That TWRP has a bug restoring EFS as there is efs.1 and efs.2 and I think it writes both efs 1 and 2 to just efs.1 on the phone which causes the boot loop.
You need to have had an EFS backup and then roll back your twrp to 3.0.0-0 and restore your EFS back from there.
---------- Post added at 05:00 PM ---------- Previous post was at 04:54 PM ----------
Kochoa940 said:
So I have been running Pure Nexus rom with Elemental X kernel and SuperSU and it's been working just fine. Well I made a nandroid, and flashed a couple new roms to try out. Didn't like any of them better so I decided to restore back to my nandroid. I used TWRP 3.0.2-2 to make the nandroid and when I tried to restore using same version it just constantly bootloops between the Google splash screen and the"Your device software cannot be checked etc etc screen". I did update my radio and bootloader to the newest versions via a flashable zip and also updated my vendor to the latest vendor image N4F26J. One of the roms said my vendor image was out of date or whatever but still booted fine for me to try out. Regardless I have factory reset phone including internal storage and flashed the factory OTA image and still no luck. Odd thing is I can still boot TWRP and also access my internal storage and move files from PC to my phone. It will even flash Roms and everything but it will not get past the Google splash screen. So wth do I do lol?
Click to expand...
Click to collapse
If your nandroid contained the efs backup (3.0.2-2 backs it up by default) and you restored your backup with the efs partition your borked since you used TWRP 3.0.2-2. That TWRP has a bug restoring EFS as there is efs.1 and efs.2 and I think it writes both efs 1 and 2 to just efs.1 on the phone which causes the boot loop.
You need to have had an EFS backup and then roll back your twrp to 3.0.0-0 and restore your EFS back from there.
Vaseag said:
Maybe stupid answer : 1 did you flashed boot.img ?
2. Is your data partition anything like ex4 or f2fs ?
Will it stuck on google logo ? (I had stucl for 10 min once ) or it just bootloops
Why not try to flash 3.0.3.0 recovery and try again?
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
Click to expand...
Click to collapse
Eric214 said:
If your nandroid contained the efs backup (3.0.2-2 backs it up by default) and you restored your backup with the efs partition your borked since you used TWRP 3.0.2-2. That TWRP has a bug restoring EFS as there is efs.1 and efs.2 and I think it writes both efs 1 and 2 to just efs.1 on the phone which causes the boot loop.
You need to have had an EFS backup and then roll back your twrp to 3.0.0-0 and restore your EFS back from there.
---------- Post added at 05:00 PM ---------- Previous post was at 04:54 PM ----------
If your nandroid contained the efs backup (3.0.2-2 backs it up by default) and you restored your backup with the efs partition your borked since you used TWRP 3.0.2-2. That TWRP has a bug restoring EFS as there is efs.1 and efs.2 and I think it writes both efs 1 and 2 to just efs.1 on the phone which causes the boot loop.
You need to have had an EFS backup and then roll back your twrp to 3.0.0-0 and restore your EFS back from there.
Click to expand...
Click to collapse
Ok I am gonna try and revert to 3.0.0 and restore the EFS and then the backup. Would that be the correct resolution?
Ok so I fixed it!!!!! Btw thank you guys for all your responses!!!
Even though my version of TWRP was 3.0.2-2 this still worked for me following these commands. I randomly found this page and said what the hell I have nothing to lose so I did it and it freakin' worked! anyways here's the link in case anyone else has this issue of not booting past google splash screen
http://www.droidorigin.com/warning-nexus-6p-users-twrp-3-0-2-1/
Again thanks to those who responded and tried to help!
Does backing up my phone using TWRP without the data partition fix the phone if it somehow got the OS removed?
CodeRida said:
Does backing up my phone using TWRP without the data partition fix the phone if it somehow got the OS removed?
Click to expand...
Click to collapse
Depends what got wiped or messed up. If it was just the System partition, then yes you can backup and restore System which should solve your problem.
It certainly helped me when I was trying to install the KangVIP rom. I couldn't initially get it to boot, so I restored previously backed up stock Boot and System partitions and all was fine.
Hi,
I've flashed TWRP for a sm-G900f via heimdall, booted into TWRP-Recovery, made an backup from the working Stock ROM to sd card, flashed lineage open gapps etc., all works well.
Because of somtimes not working Sensors I've tried to test if the sensor problem is an hardware or an software issue, so recovered the stock rom backup using the installed twrp 3.2.1-0. Therefor I've made these steps :
Boot into recovery
Wipe cache, system, davlink-cache, format data
restore the stock rom backup
reboot
Every reboot results in booting to recovery, Samsung system won't start.
Tried to disconnect battery for a few minutes etc.
Where is my mistake ? Could someone give me an advice ?
Every restore of the lineage backups using this way works well.
Regards
Fred
fred06007 said:
Hi,
I've flashed TWRP for a sm-G900f via heimdall, booted into TWRP-Recovery, made an backup from the working Stock ROM to sd card, flashed lineage open gapps etc., all works well.
Because of somtimes not working Sensors I've tried to test if the sensor problem is an hardware or an software issue, so recovered the stock rom backup using the installed twrp 3.2.1-0. Therefor I've made these steps :
Boot into recovery
Wipe cache, system, davlink-cache, format data
restore the stock rom backup
reboot
Every reboot results in booting to recovery, Samsung system won't start.
Tried to disconnect battery for a few minutes etc.
Where is my mistake ? Could someone give me an advice ?
Every restore of the lineage backups using this way works well.
Regards
Fred
Click to expand...
Click to collapse
Corrupted backup maybe?
A long time ago I made a backup of stock and was able to go back and forth with no issues. You can try and go back to stock, root again and try another back up.
Corrupted backup ? It's the only one I've made after flashing TWRP and before installing Lineage.
fred06007 said:
Corrupted backup ? It's the only one I've made after flashing TWRP and before installing Lineage.
Click to expand...
Click to collapse
It happens sometimes, I had an SD card with a bad sector so every time I would make a back up it would get corrupted if I deleted the back up. I ended up leaving the backup so it will no longer write on the bad sectors.
fred06007 said:
Where is my mistake ? Could someone give me an advice ?
Click to expand...
Click to collapse
I think, you have to flash or restore the right kernel.
Which partitions have you backed up?
Sorry for the late response, the backup includes in my mind system, data and boot partition because the backup consit's of the following files:
boot.emmc.win
boot.emmc.win.sha2
data.ext4.win
data.ext4.win.sha2
data.info
recovery.log
system.ext4.win000
system.ext4.win000.sha2
system.ext4.win001
system.ext4.win001.sha2
system.info