Database Users

Stuck on Google Logo after TWRP Backup Restore.

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!

Please help! MXP stuck on "warning bootloader unlocked"

Hey guys,
I unlocked my bootloader and flashed a recovery succesfully. When I entered into recovery mode, I enter into TWRP, get to install SuperSU, but when I reboot my device, it is stuck on "warning etc..."
What could I have done wrong? How can I fix this? Any help would be very much appreciated.
I have a MXP XT1563
I installed this TWRP http://forum.xda-developers.com/devdb/project/?id=11587#downloads
And this SuperSU https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
I honestly can't remember what fastboot files I download, but I suppose it was ok since I got to enter my unlocking code and unlock it.
Thanks in advance.
Regards from Mexico

When I enter into TWRP and enter somewhere, for instance Install, I can see my folders: amazon, kindle, whatsapp, etc... I suppose that's good news.
I've tried doing a factory reset from Wipe, no sucess.
Please help! I will be uncommunicated until I solve this

you should have read the forums first. did you take a nandroid before flashing su? of yes then restore that,
you need su 2.62-3
download the su then flash it again. here is the su.forum.xda-developers.com/moto-x-play/general/root-how-to-root-6-0-easly-t3277202

bablu048 said:
you should have read the forums first. did you take a nandroid before flashing su? of yes then restore that,
you need su 2.62-3
download the su then flash it again. here is the su.forum.xda-developers.com/moto-x-play/general/root-how-to-root-6-0-easly-t3277202
Click to expand...
Click to collapse
hi bablu048, I did not "nandroid" before flashing su. I did it after I flashed it and when I try to restore it it says it's read only.
Do I download su 2.62-3, copy it into my storage and flash it again, no matter all I've done by now?

when it asks to keep read only refect it select allow modifications,
yes, download that su , copy it to storage and flash.

bablu048 said:
when it asks to keep read only refect it select allow modifications,
yes, download that su , copy it to storage and flash.
Click to expand...
Click to collapse
ok, this is what I did: I downloaded the su, put in internal storage, went into recovery mode, got into twrp, installed new su.
Now it gets past the warning, but gets stuck now in the water-ish motorola logo...
When I go into Restore, I can see two back ups, when I try to restore any of them, it says "cannot restore system - - mounted read only" and no option to modify it.
thanks a lot for your help! I'm trying to follow your every advice as best as I understand it

DO NOT restore the old backup it has the old su you will be back to where you started.
]boot into twrp clear cache/dalvic cache and leave the phone on the watery logo for a few minutes..it takes some time to boot

bablu048 said:
DO NOT restore the old backup it has the old su you will be back to where you started.
]boot into twrp clear cache/dalvic cache and leave the phone on the watery logo for a few minutes..it takes some time to boot
Click to expand...
Click to collapse
I see... actually I didnt get to restore any of them. I cleared both caches and now I'm waiting in the watery logo.
In case I don't make it, I'll have to let it for a while like this: on the watery logo, the MXP is quite hot now... no problem if I let it like that for half a day? I'm worried about that
In case it doesn't pass from there... is downloading twrp backups still an option? I just finished downloading RSD lite.

fsae3 said:
I see... actually I didnt get to restore any of them. I cleared both caches and now I'm waiting in the watery logo.
In case I don't make it, I'll have to let it for a while like this: on the watery logo, the MXP is quite hot now... no problem if I let it like that for half a day? I'm worried about that
In case it doesn't pass from there... is downloading twrp backups still an option? I just finished downloading RSD lite.
Click to expand...
Click to collapse
just let it on the watery logo for 15-20 minutes if it's still not going any further you can download the backups and wipe the system, cache, dalvic cache then restore the backup
RSD lite is used to flash the original factory firmware then you have to root again.

bablu048 said:
just let it on the watery logo for 15-20 minutes if it's still not going any further you can download the backups and wipe the system, cache, dalvic cache then restore the backup
RSD lite is used to flash the original factory firmware then you have to root again.
Click to expand...
Click to collapse
I went to sleep and it didn't pass from the watery logo.
I manually backed up my files, so I'm not worried about anything I might have on the phone; still, I think flashing a new firmware will factory reset my MXP correct?
Is the original factory firmware the same as a stock image? I found this list of resources: https://github.com/motoxplay/stock. Under XT1563 - México, I can see my carrier, Iusacell. Will this do it?
Please do let me know.

fsae3 said:
I went to sleep and it didn't pass from the watery logo.
I manually backed up my files, so I'm not worried about anything I might have on the phone; still, I think flashing a new firmware will factory reset my MXP correct?
Is the original factory firmware the same as a stock image? I found this list of resources: https://github.com/motoxplay/stock. Under XT1563 - México, I can see my carrier, Iusacell. Will this do it?
Please do let me know.
Click to expand...
Click to collapse
yes it will wipe,
that's the correct firmware. 6.0.1
always take a nandroid before flashing su 2.62-3
after flashing twrp again when you boot into twrp do "swipe to allow modifications to /system"..you didn't do this that's why you were not able to restore backups.

bablu048 said:
yes it will wipe,
that's the correct firmware. 6.0.1
Click to expand...
Click to collapse
hi bablu048,
I found in here a "unSu" guide. I ran it, it deleted Su, then ran Su you recommended and I still got suck in the watery logo.
Then I "unSu" it again, now didn't run any Su, reeboted device and it finally started.
I think su is the problem. Where can I check what su should I use?

great first take a nandroid.
finding the correct su is hit and trial method. generally su 2.62-3 worked. try other su's 2.65,2.66

bablu048 said:
great first take a nandroid.
finding the correct su is hit and trial method. generally su 2.62-3 worked. try other su's 2.65,2.66
Click to expand...
Click to collapse
Ok, I get it now. I backup my device with nandroid to make sure I have it there in case something goes wrong. If I have no info I want to save (my phone is blank, it's factory resetted from the bootloader unlocking) is it still necessary to nandroid? It's necessary in case a su fails right?

nandroid backup takes a backup of your OS with data and everything.
I think you didn't allow/system to be modified when you first booted into twrp. that's why su is failing, as su modifies the /system partition.

bablu048 said:
nandroid backup takes a backup of your OS with data and everything.
I think you didn't allow/system to be modified when you first booted into twrp. that's why su is failing, as su modifies the /system partition.try
Click to expand...
Click to collapse
by now, my MXP is factory resetted, I'm trying to read more before doing anything.
Since is factory resetted, it doesn't have developer mode (oem unlocking, usb debugging). I still see TWRP in recovery mode.
I suppose if I want to try another SU, I have to enable develper of course, oem-usb, obviously. Do I have to flash TWRP again? Or can I just try a SU? Of course, after having done a nandroid.

fsae3 said:
by now, my MXP is factory resetted, I'm trying to read more before doing anything.
Since is factory resetted, it doesn't have developer mode (oem unlocking, usb debugging). I still see TWRP in recovery mode.
I suppose if I want to try another SU, I have to enable develper of course, oem-usb, obviously. Do I have to flash TWRP again? Or can I just try a SU? Of course, after having done a nandroid.
Click to expand...
Click to collapse
you don't need to take nandroid backup always, once is sufficient unless you want to backup the latest data. no need to flash twrp again. just flash su.
take a nandroid backup once (everything system, boot, data) . after successfully flashing su you can keep another backup that contains su.

bablu048 said:
you don't need to take nandroid backup always, once is sufficient unless you want to backup the latest data. no need to flash twrp again. just flash su.
take a nandroid backup once (everything system, boot, data) . after successfully flashing su you can keep another backup that contains su.
Click to expand...
Click to collapse
ok, finally! My device is rooted. Thanks a lot!
I think I forgot to select external storage when taking a nandroid, so it went into internal storage, it filled a little more than 5 GB. I can't see this backup neither in TWRP, PC or an android file explorer. How can I get rid of those 5 GB? I take a nandroid on external storage and already copied it in my PC.
Is there a way via TWRP to get rid of it? Wiping something? I'm very cautios from now on.

it's stored at /data/media/twrp delete those backups. or boot into twrp >restore> it'll show all the backups delete those.

edit: Im stuck in the "watery logo" I need help unistalling SU can some1 point me to that guide?
I've already flashed SuperSU 2.62-3
edit 2: I flashed SU 2.65 and it did the trick! solved, i think
original post:
Hi guys hope you can help me
I have a XT1563, single sim. I unlocked bootloader, flashed recovery, went directly to TWRP to flash SuperSU v2.46, it finished, I restarted using TWRP option but hasnt restarted is stuck in the warning screen "Warning bootloader unlocked...your device's bootloader has been unlock...." I do not know what to do
I press power-off and any key combination and it doesnt do anything is just stuck at that warning screen. Unlike the OP I dont get the watery logo

restoring from TWRP

hello all
i have ZTE AXON 7 U model.
i did bootloader unloock and instaled TWRP 3041 and did this "Once you booted to TWRP , Tap Mount and Check "Mount, System as Read-only", this is very important".
now im on the A2017UV1.1.0B15_systemstock_by_DrakenFX.zip. all works great.
in twrp when i do backup and want to restore it i get this massage: " cannot restore system--mounted read only".
how can i backup and restore in the wright way?
ty all

le011 said:
hello all
i have ZTE AXON 7 U model.
i did bootloader unloock and instaled TWRP 3041 and did this "Once you booted to TWRP , Tap Mount and Check "Mount, System as Read-only", this is very important".
now im on the A2017UV1.1.0B15_systemstock_by_DrakenFX.zip. all works great.
in twrp when i do backup and want to restore it i get this massage: " cannot restore system--mounted read only".
how can i backup and restore in the wright way?
ty all
Click to expand...
Click to collapse
"Mount and Check "Mount, System as Read-only", this is very important".
What you have quoted is only to complete the installation Flash. Go ahead and uncheck 'Mount System Read-Only' for normal operation and you are ready to go!

amphi66 said:
"Mount and Check "Mount, System as Read-only", this is very important".
What you have quoted is only to complete the installation Flash. Go ahead and uncheck 'Mount System Read-Only' for normal operation and you are ready to go!
Click to expand...
Click to collapse
To for your replay.
When I unchecked the System read only and trying to restore the phone from the backup I made in Twrp the phone stucks after reboot on the screen that says the bootloader is unlocked and that's it.

le011 said:
To for your replay.
When I unchecked the System read only and trying to restore the phone from the backup I made in Twrp the phone stucks after reboot on the screen that says the bootloader is unlocked and that's it.
Click to expand...
Click to collapse
You should see that screen and the phone should continue to boot after 5 seconds.
To recap:
1. You stated all was fine in B15 after following the upgrade steps.
2. You made a TWRP backup (system, data & boot) of your new B15
3. When attempting to TWRP restore the B15 backup it could not as system was still mounted "read only"
4. You unchecked "read only" and then did the restore
5. Now system does not boot (hangs on bootloader unlocked warning screen)
If that is correct it sounds as if you have a bad or incomplete B15 backup or you are attempting to restore a B29 backup to a B15 bootstack.

amphi66 said:
You should see that screen and the phone should continue to boot after 5 seconds.
To recap:
1. You stated all was fine in B15 after following the upgrade steps.
2. You made a TWRP backup (system, data & boot) of your new B15
3. When attempting to TWRP restore the B15 backup it could not as system was still mounted "read only"
4. You unchecked "read only" and then did the restore
5. Now system does not boot (hangs on bootloader unlocked warning screen)
If that is correct it sounds as if you have a bad or incomplete B15 backup or you are attempting to restore a B29 backup to a B15 bootstack.
Click to expand...
Click to collapse
All correct.
After Im making backup, I'm wiping, and trying to restore the backup I just did.
No luck.

le011 said:
All correct.
After Im making backup, I'm wiping, and trying to restore the backup I just did.
No luck.
Click to expand...
Click to collapse
Confusing to me. How are you using phone after a bad restore?
What revision TWRP did you flash? Did you flash SU 2.79 after flashing ROM?
Perhaps someone w/ more knowledge can chime in, but sounds as if you are a candidate to begin again following the steps carefully
Goodluck

amphi66 said:
Confusing to me. How are you using phone after a bad restore?
What revision TWRP did you flash? Did you flash SU 2.79 after flashing ROM?
Perhaps someone w/ more knowledge can chime in, but sounds as if you are a candidate to begin again following the steps carefully
Goodluck
Click to expand...
Click to collapse
hi
i have TWRP version 3041.
after i'm trying to restore and wont succeeded , i flash the rom again. the rom im flashing is : A2017UV1.1.0B15_systemstock_by_DrakenFX.
then the phone boot up and work great.
im not flashing supersu because i dont want root.

le011 said:
hi
i have TWRP version 3041.
after i'm trying to restore and wont succeeded , i flash the rom again. the rom im flashing is : A2017UV1.1.0B15_systemstock_by_DrakenFX.
then the phone boot up and work great.
im not flashing supersu because i dont want root.
Click to expand...
Click to collapse
Interesting. How long are you waiting on the Bootloader unlocked warning screen?
Next time in TWRP look at the data partition and verify it is formatted as ext4 not f2fs. I might also download a different version of TWRP and reflash the IMG file from within TWRP. I reference @DrakenFX here as he may have the easy solution.

amphi66 said:
Interesting. How long are you waiting on the Bootloader unlocked warning screen?
Next time in TWRP look at the data partition and verify it is formatted as ext4 not f2fs. I might also download a different version of TWRP and reflash the IMG file from within TWRP. I reference @DrakenFX here as he may have the easy solution.
Click to expand...
Click to collapse
How i check in TWRP how the data partition formated?
I trayid the new version of TWRP 3100 and same thing.
after restoring the phone stuck on the Bootloader unlocked warning screen -last time i waited for 5 min before i
shut down whit power button.

le011 said:
hi
i have TWRP version 3041.
after i'm trying to restore and wont succeeded , i flash the rom again. the rom im flashing is : A2017UV1.1.0B15_systemstock_by_DrakenFX.
then the phone boot up and work great.
im not flashing supersu because i dont want root.
Click to expand...
Click to collapse
amphi66 said:
Interesting. How long are you waiting on the Bootloader unlocked warning screen?
Next time in TWRP look at the data partition and verify it is formatted as ext4 not f2fs. I might also download a different version of TWRP and reflash the IMG file from within TWRP. I reference @DrakenFX here as he may have the easy solution.
Click to expand...
Click to collapse
Easy fix, go back to TWRP,
* Wipe Data (if you are in different ROM a or version) - Dalvik- Cache
* Check MOUNT SYSTEM AS READ-ONLY
* Reflash B15 system
Happy reboot
If you Previously were using B15 , you may restore data only, other wise is a no go.

DrakenFX said:
Easy fix, go back to TWRP,
* Wipe Data - Dalvik- Cache
* Check MOUNT SYSTEM AS READ-ONLY
* Reflash B15 system
Happy rebokt
Click to expand...
Click to collapse
hi
i did that for 3 tomes ending whit the same result :
the rom working great after clean instal...restoring from TWRP....ending whit stuck phone.

le011 said:
How i check in TWRP how the data partition formated?
I trayid the new version of TWRP 3100 and same thing.
after restoring the phone stuck on the Bootloader unlocked warning screen -last time i waited for 5 min before i
shut down whit power button.
Click to expand...
Click to collapse
You may not have seen this on another thread with a similar issue:
"did find something else out. Under [TWRP] settings, if I enabled the "Use rm -rf instead of formatting", then I can restore successfully."
Goodluck

amphi66 said:
You may not have seen this on another thread with a similar issue:
"did find something else out. Under [TWRP] settings, if I enabled the "Use rm -rf instead of formatting", then I can restore successfully."
Goodluck
Click to expand...
Click to collapse
OK ty
i will try that and post if sucssed.

can't extract apps from nandroid made otg with twrp

My phone was stuck in a bootloop where it could only get to recovery. Using the recovery I created a nandroid backup to the a USB stick using an OTG cable. I flashed the stock firmware and got things setup but I can't restore individuals apps from the nandroid. I copied the nandroid from the usb to sd card but it still doesn't work. I tried restoring apps using Nandroid Manager but when the app is launched it gives the error "app has stopped, close app". For some reasons sms succesfully restored but no user apps. I tried restoring with AppExtractor but it gives the error "unable to generate apk listing"
I also have titanium backup pro but couldn't get it to find the location of the nandroid to try extracting with it.
Any ideas? I really just want my messages back from Whatsapp.
My phone had stock Nougat with busybox installed and elementalx kernel. It should be the same environment now as when the backups were made.

@twoplustwo can you tell us why your phone went into bootloop ? If you know then you can restore /data from TWRP and revert the cause of bootloop..
Also can you confirm it's in capital letters as you have mentioned in small letters in another thread that twrp/backups rename them to TWRP/BACKUPS or move them to internal storage.. (in stock ROM if i am not wrong, TWRP folder is not accessible, so try to install custom ROM for temporary purpose, then move backup to internal and then try with titanium backup..)

____Mdd said:
@twoplustwo can you tell us why your phone went into bootloop ? If you know then you can restore /data from TWRP and revert the cause of bootloop..
Also can you confirm it's in capital letters as you have mentioned in small letters in another thread that twrp/backups rename them to TWRP/BACKUPS or move them to internal storage.. (in stock ROM if i am not wrong, TWRP folder is not accessible, so try to install custom ROM for temporary purpose, then move backup to internal and then try with titanium backup..)
Click to expand...
Click to collapse
yes it was in capital letters
the problem in the first place that sent the phone into a bootloop was I installed the OTA security update. I'm running stock rom but I guess because it was rooted and had busybox, that made it incompatible with the update?

twoplustwo said:
yes it was in capital letters
the problem in the first place that sent the phone into a bootloop was I installed the OTA security update. I'm running stock rom but I guess because it was rooted and had busybox, that made it incompatible with the update?
Click to expand...
Click to collapse
If you have TWRP and take update, it don't cause bootloop, but it cause your device to boot into recovery when you turn on your device.. can you confirm if it was bootloop or problem of booting to TWRP ?

I am unable to copy the nandroid to internal storage. I tried using usb to computer and it just does nothing. I tried root explorer and it says 'copy failed' and file manager says 'cannot load'. This only happens with the TWRP folder inside the internal memory specifically.

____Mdd said:
@twoplustwo can you tell us why your phone went into bootloop ? If you know then you can restore /data from TWRP and revert the cause of bootloop..
Also can you confirm it's in capital letters as you have mentioned in small letters in another thread that twrp/backups rename them to TWRP/BACKUPS or move them to internal storage.. (in stock ROM if i am not wrong, TWRP folder is not accessible, so try to install custom ROM for temporary purpose, then move backup to internal and then try with titanium backup..)
Click to expand...
Click to collapse
____Mdd said:
If you have TWRP and take update, it don't cause bootloop, but it cause your device to boot into recovery when you turn on your device.. can you confirm if it was bootloop or problem of booting to TWRP ?
Click to expand...
Click to collapse
I can confirm it was only booting TWRP. So even when I tried to boot to system it just booted to TWRP again.

twoplustwo said:
I can confirm it was only booting TWRP. So even when I tried to boot to system it just booted to TWRP again.
Click to expand...
Click to collapse
You don't need to worry,
Do you have any important data for any app currently ?
Take backup of new important data with titanium.. (and then again take backup from TWRP, for safety )
And then simply restore /data from TWRP backup, it will give you older data back without any bootloop but you will loose new data/messages that you got after flashing/ on current running ROM..

____Mdd said:
You don't need to worry,
Do you have any important data for any app currently ?
Take backup of new important data with titanium.. (and then again take backup from TWRP, for safety )
And then simply restore /data from TWRP backup, it will give you older data back without any bootloop but you will loose new data/messages that you got after flashing/ on current running ROM..
Click to expand...
Click to collapse
Thank you sir! To confirm, when backing up to USB stick with OTG, does the format of the USB matter? Is fat32 safe?

twoplustwo said:
Thank you sir! To confirm, when backing up to USB stick with OTG, does the format of the USB matter? Is fat32 safe?
Click to expand...
Click to collapse
Not familiar with different formats, it should work.. bu t
You can backup to internal storage too, since you don't have to flash fastboot ROM again..

____Mdd said:
Not familiar with different formats, it should work.. bu t
You can backup to internal storage too, since you don't have to flash fastboot ROM again..
Click to expand...
Click to collapse
Just want to confirm everything is working perfect now. Thank you again!

[STOCK PIE (march)] Will I get my data wiped if I hotboot TWRP?

Hello, I've been trying to root my phone, I followed a guide that tell me to
Code:
fastboot flash twrp.img
and got all my data wiped for some reason. LATER, i found out that you souldn't be doing that, instead you should be doing
Code:
fastboot boot twrp.img
But by then, I got everything on my phone deleted (i flashed an original rom from MI forums and restored a manual backup of data and some apps i had, but still I lost like a day setting up everything).
My questions are, if I hotboot TWRP will I get my data wiped again? (my bootloader is still unlocked so no danger there)
If not, can I backup my data normally using TWRP GUI on hotboot?
Also, once I've installed magisk, will I stop receiving OTAs?
Thanks

No, you won't get data wiped if you boot twrp. I'm doing this periodically and everithing is ok.
Probably you flashed twrp wrong. It should be
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
You can receive ota's with magisk. Prior to installing ota, you should uninstall/"restore partitions" with magisk but not reboot. After ota is installed, you install magisk into secondary partition (with magisk manager) and reboot.

BlackChimaera said:
No, you won't get data wiped if you boot twrp. I'm doing this periodically and everithing is ok.
Probably you flashed twrp wrong. It should be
You can receive ota's with magisk. Prior to installing ota, you should uninstall/"restore partitions" with magisk but not reboot. After ota is installed, you install magisk into secondary partition (with magisk manager) and reboot.
Click to expand...
Click to collapse
But isn't HIGHLY recommended to NOT flash the recovery?

I'm not flashing it too, just "fastboot boot" it when I need it.

BlackChimaera said:
I'm not flashing it too, just "fastboot boot" it when I need it.
Click to expand...
Click to collapse
I hotbooted TWRP and made a backup, after rebooting from TWRP, the phone boots slowly and hangs at the lock screen. Any ideas what could have triggered this?
The only "abnormal"thing i did was to rename the media folder in "data" so TWRP could include it into the backup. After that I renamed the folder to "media" again, and rebooted.
There was a "mediadrm" folder, but I don't remember if it was already there or not.

Why do you want to include media folder into backup? It has only mount points to sdcards. Do you want to include sdcard content into backup? Where is backup stored? On the same sdcard which content you backing up?

BlackChimaera said:
Why do you want to include media folder into backup? It has only mount points to sdcards. Do you want to include sdcard content into backup? Where is backup stored? On the same sdcard which content you backing up?
Click to expand...
Click to collapse
Media folder has internal storage. Anyway, i was able to boot again by flashing to latest stock rom and then restoring "data" from my backup.
Enviado desde mi Mi A1 mediante Tapatalk

BlackChimaera said:
No, you won't get data wiped if you boot twrp. I'm doing this periodically and everithing is ok.
Probably you flashed twrp wrong. It should be
You can receive ota's with magisk. Prior to installing ota, you should uninstall/"restore partitions" with magisk but not reboot. After ota is installed, you install magisk into secondary partition (with magisk manager) and reboot.
Click to expand...
Click to collapse
On Mi A1, TWRP can't be flashed from fastboot, because it doesn't have /recovery