Related
i recently flashed the eXistenZ Ultra 2, and im sure i did everything fine, after flashing the rom in recovery and flashing suprsu and wifi fix, i powered off the phone, and powered on but sony logo has apeared until now , and welcoming`s sounding 999..times. i cant turn it off, or i should say i cant do anything.
please help,
After flashing ROM and the fixes you should flash the 12.1.A.0.266 Firmware with FlashTool!
If problem still persists:
http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
Take a look at this site A recovery would be quite useful, but I think the kernel of eXistenZ ROM has one. If not, you'll find one in the development section. Otherwise, use the ADB as solution.
Good luck
Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?
eefathi said:
Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?
Click to expand...
Click to collapse
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!
Schokonuss said:
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!
Click to expand...
Click to collapse
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.
eefathi said:
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.
Click to expand...
Click to collapse
You're welcome
1. Do you have SuperSU installed? On AOKP ROM I'm running it asked for superuser permission for ROM Control (the control center implemented in the settings of the ROM). Maybe it'll ask you if SuperSU is installed. Otherwise, because it is after the first boot it needs to rebuild cache and so on.. If problem persists after reboot, just use an other clock speed controler (No-frills CPU, SetCPU..)
2. If you did that at the same time, maybe Go Backup didn't really backup your data. Try again, if it doesn't work and if you have a nandroid backup (backup from recovery) you can go into recovery, then to advanced restore and restore data. Otherwise your data is unfortunately gone I think :/
PS: I prefer Titanium Backup
I am planning to flash a custom rom on my phone (for the first time).
Model : Xperia SP(C5302)
Build : 12.1.A.1.205 (Stock) running JB 4.3 with LB
I have rooted my phone using the towelroot method and installed supersu. I have also installed custom recovery from here http://forum.xda-developers.com/showthread.php?t=2649923
I am planning to flash this custom rom http://forum.xda-developers.com/xperia-sp/development/cyanogenmod-11-locked-bootloader-users-t2868398
So I have a few questions that I am not clear about(even after searching the forums). And sorry if they are dumb. I really want to understand as much as possible before flashing roms.:fingers-crossed:
1. After reading the thread of my recovery, from what I understand, the recoveries are installed in /system. But on OP of the custom rom, I am about to install, there is an instruction to format /system before flashing the rom. So my question is if I format the /system partition, won’t my recoveries be removed (by the recoveries itself) before I even flash the rom?
2. Also will the recovery still be available to me if say I enter bootloop for some reason during flashing the rom?(asking for the same reason as above that is wiping my /system should also remove my recoveries)
3. Does CM 11 come with any inbuilt custom recovery? If not can I install the one I am already using (assuming installing a custom rom will remove my installed recoveries)?
4. Say I screw up during the flashing procedure. So if I want to rectify this I should first flash the stock .205 ftf, root, install a recovery again and then restore using the nandroid backup. Am I correct?
5. Is it necessary to wipe cache and dalvik cache before flashing rom? I see this instruction in some roms but not in others. And dalvik should be wiped after flashing rom and gapps, right?
6. Should I install supersu again after I flash the rom. I read in an article that it causes problems with CM. As far as I know CM11 comes pre-installed with superuser. But it also supposedly causes some problems.
7. Is it safe to restore user app+data, messages and contacts backed up using Titanium backup on a newly flashed rom? I have seen conflicted views on this.
Click to expand...
Click to collapse
And that’s it for my questions (for now at least... ).
A Big Thanks in advance for all your helpful answers
Prat92 said:
I am planning to flash a custom rom on my phone (for the first time).
Model : Xperia SP(C5302)
Build : 12.1.A.1.205 (Stock) running JB 4.3 with LB
I have rooted my phone using the towelroot method and installed supersu. I have also installed custom recovery from here http://forum.xda-developers.com/showthread.php?t=2649923
I am planning to flash this custom rom http://forum.xda-developers.com/xperia-sp/development/cyanogenmod-11-locked-bootloader-users-t2868398
So I have a few questions that I am not clear about(even after searching the forums). And sorry if they are dumb. I really want to understand as much as possible before flashing roms.:fingers-crossed:
And that’s it for my questions (for now at least... ).
A Big Thanks in advance for all your helpful answers
Click to expand...
Click to collapse
First of all, I am only explaining the one I know about
1. Well, wiping the system will remove the recovery. That's why you'll have to flash the ROM after wiping the system. Do not ever reboot the phone after wiping the system but haven't yet flashed the ROM zip, else you'll have to do more work to flash the Stock ROM. This is due to the fact your phone does not have an OS to boot into! When flashing the ROM zip, the recovery will be automatically installed.
2. This is based on luck, most of time you'll end up unable to boot into anything. A fix is to flash the Stock ROM again.
3. Every ROM has recovery built with it (unless stated otherwise in the thread)! Upon flashing, it will be automatically installed too.
4. The methods you mentioned is correct. However, only restore the nandroid backup if you want to stay on stock. You could always retry to flash the ROM again. Nandroid backup is an image backup of your android. If you restore your nandroid backup, you'll end up with your previous version of android (like the way before you started flashing the ROM)
5. Wiping /cache and dalvik-cache is a really good practise! It doesn't really matter when you will need to wipe them, but personally I wipe them all before flashing the ROM. Wiping /data and performing a factory reset through recovery is recommended if you're coming from a different ROM. That's why backing up user apps through TiB (Titanium Backup) is recommended for you to easily get your installed apps back. Remember, nandroid backup and apps backup from TiB is different to each other.
6. No, this might cause extreme conflicts. No, I am using SuperUser as long as I have used CM. It never fails to give root permission at all despite the hatred I sense in some apps that overly-recommends SuperSU.
7. Of course it is very safe to restore them backups with TiB. However, based on my experience, messages and contacts were unable to be restored due to the difference in ROM version. I don't know if anyone else faces the same problem as mine. As of this, I really recommend your contacts to be synced with Google.
Heads up!
Based on this post, the dev of the ROM you wanted to flash, MrSteve555, recommends PhilZ when flashing the ROM.
TechnoSparks said:
First of all, I am only explaining the one I know about
1. Well, wiping the system will remove the recovery. That's why you'll have to flash the ROM after wiping the system. Do not ever reboot the phone after wiping the system but haven't yet flashed the ROM zip, else you'll have to do more work to flash the Stock ROM. This is due to the fact your phone does not have an OS to boot into! When flashing the ROM zip, the recovery will be automatically installed.
2. This is based on luck, most of time you'll end up unable to boot into anything. A fix is to flash the Stock ROM again.
3. Every ROM has recovery built with it (unless stated otherwise in the thread)! Upon flashing, it will be automatically installed too.
4. The methods you mentioned is correct. However, only restore the nandroid backup if you want to stay on stock. You could always retry to flash the ROM again. Nandroid backup is an image backup of your android. If you restore your nandroid backup, you'll end up with your previous version of android (like the way before you started flashing the ROM)
5. Wiping /cache and dalvik-cache is a really good practise! It doesn't really matter when you will need to wipe them, but personally I wipe them all before flashing the ROM. Wiping /data and performing a factory reset through recovery is recommended if you're coming from a different ROM. That's why backing up user apps through TiB (Titanium Backup) is recommended for you to easily get your installed apps back. Remember, nandroid backup and apps backup from TiB is different to each other.
6. No, this might cause extreme conflicts. No, I am using SuperUser as long as I have used CM. It never fails to give root permission at all despite the hatred I sense in some apps that overly-recommends SuperSU.
7. Of course it is very safe to restore them backups with TiB. However, based on my experience, messages and contacts were unable to be restored due to the difference in ROM version. I don't know if anyone else faces the same problem as mine. As of this, I really recommend your contacts to be synced with Google.
Heads up!
Based on this post, the dev of the ROM you wanted to flash, MrSteve555, recommends PhilZ when flashing the ROM.
Click to expand...
Click to collapse
Thanks for such detailed answers. That cleared most of my doubts
Just some last few questions(promise!)
1. If wiping /system does remove the recovery before I install the rom, how is it possible to access it even to flash the rom? Shouldn't it like just close right when I wipe /system. Or does it not work like that?
2. Just to be sure the nandroid backup I made on my stock rom won't work if I later try to flash it through recovery while using CM,right?
Prat92 said:
Thanks for such detailed answers. That cleared most of my doubts
Just some last few questions(promise!)
1. If wiping /system does remove the recovery before I install the rom, how is it possible to access it even to flash the rom? Shouldn't it like just close right when I wipe /system. Or does it not work like that?
2. Just to be sure the nandroid backup I made on my stock rom won't work if I later try to flash it through recovery while using CM,right?
Click to expand...
Click to collapse
1. Wiping system wont close the recovery at all. It still runs and you can still navigate within it. But remember do not reboot unless you've flashed the ROM! The mechanism of how the magic works is yet to be acknowledged. So I can't tell why it doesn't closes upon wipe. My best guess here is that the recovery might be running on a temporary partition perhaps. I hope a developer see this post and explains the magic.
2. Nandroid backup works all the time (if they are no errors when you are creating them). Nandroid backup is simply a backup of your whole device. If you're on CM, restoring nandroid backup will get your phone back to the way when you attempted the nandroid backup (stock ROM, rooted, and triple recoveries installed). Nandroid backup is useful when you're about to try something that may damage your ROM, without doing so much work to restore your device.
Say, you created a nandroid backup in cwm in which Cyanogenmod was installed. And then you flashed something afterwards. If that "something" damages the ROM and gives you bootloop, you can simply flash Stock ROM, root it again, install recoveries again, and restore the nandroid backup. Then, voilà, cyanogenmod is back. This will simplify your work rather than flash CM again, then gapps, then restore your apps and all those other things that will consume so much time
So a new nandroid backup will backup the whole device, in a form of an image.
Hello,
So my Galaxy S6 is stuck in a boot loop and i've literally tried EVERYTHING already and nothing will solve the problem. Safe mode won't work, clearing the cache partition won't work and USB Debugging was turned off so adb wasn't seeing my device either. I also tried Kies and Smart Switch. I am convinced my phone is soft bricked and I need to recover some very important pictures and files from it. At this point my last hope is to flash the stock ROM via Odin and I saw that some people said that they have successfully done this without losing any of their data. Is this possible? If so how do I go about doing it properly?
Thanks for any help!
Phone is not rooted and 100% stock.
Recovery and Download screens are working.
How did Kies not work for you? I used it about 4 times to restore to like new.
cwhiatt said:
How did Kies not work for you? I used it about 4 times to restore to like new.
Click to expand...
Click to collapse
Because the phone is stuck in a boot loop. Kies won't detect my phone because it never fully boots.
Weird. I completely removed the system on one before reinstalling the system via Kies before sending it back via warranty exchange. I'd suggest trying again. Obviously you will need model and serial #.
cwhiatt said:
Weird. I completely removed the system on one before reinstalling the system via Kies before sending it back via warranty exchange. I'd suggest trying again. Obviously you will need model and serial #.
Click to expand...
Click to collapse
Tried Kies multiple times but it just won't work. Uninstalled and reinstalled drivers, disconnected and reconnected the phone, nothing works. That's why I turned to Odin.
1337Dev said:
Tried Kies multiple times but it just won't work. Uninstalled and reinstalled drivers, disconnected and reconnected the phone, nothing works. That's why I turned to Odin.
Click to expand...
Click to collapse
Since you can get into recovery, if I were you I'd flash Unikernel (latest version is 9.1 I believe) and then flash a custom rom. If you can get it to boot you shouldn't lose data in the sdcard/download.
---------- Post added at 09:48 PM ---------- Previous post was at 09:46 PM ----------
I am running Sick as Hell version X rom and loving it.
cwhiatt said:
Since you can get into recovery, if I were you I'd flash Unikernel (latest version is 9.1 I believe) and then flash a custom rom. If you can get it to boot you shouldn't lose data in the sdcard/download.
---------- Post added at 09:48 PM ---------- Previous post was at 09:46 PM ----------
I am running Sick as Hell version X rom and loving it.
Click to expand...
Click to collapse
Forgot to mention but I am going to have to return this phone to T-mobile for a warranty exchange, that's why I was trying to avoid custom rom's thinking it might become ineligible. Want to be able to recover data and then reset the phone for return
The phone i wiped the system on was returned via warranty with Tmobile (of course I later reinstalled it via Kies). I would install a custom rom to attempt to get the thing up and running. Once you do that then go from there (back to Kies or factory reset...)
cwhiatt said:
The phone i wiped the system on was returned via warranty with Tmobile (of course I later reinstalled it via Kies). I would install a custom rom to attempt to get the thing up and running. Once you do that then go from there (back to Kies or factory reset...)
Click to expand...
Click to collapse
Ok, Thank you! I was worried about the warranty exchange. I will attempt to install a custom rom let's see how it goes.
The purpose of installing the custom rom is to attempt to retrieve your data. If you can boot and then successfully get your data, it would be advisable to remove the custom rom and restore it to factory. Let me know how it goes...
cwhiatt said:
The purpose of installing the custom rom is to attempt to retrieve your data. If you can boot and then successfully get your data, it would be advisable to remove the custom rom and restore it to factory. Let me know how it goes...
Click to expand...
Click to collapse
Hello another User here , I am in a similar situation . I installed some theme [live] from theme store , then it started acting wierdly. Finally a bad combination of Good Lock , System UI and Safe Mode my phone is in a bootloop.
I want to recover my data mostly videos and pictures. What shall I do. I am unrooted , I can access recovery , adb sideload from recovery , I can get into download mode. Will wipe data option save my Pictures?
y2k2r2d2 said:
Hello another User here , I am in a similar situation . I installed some theme [live] from theme store , then it started acting wierdly. Finally a bad combination of Good Lock , System UI and Safe Mode my phone is in a bootloop.
I want to recover my data mostly videos and pictures. What shall I do. I am unrooted , I can access recovery , adb sideload from recovery , I can get into download mode. Will wipe data option save my Pictures?
Click to expand...
Click to collapse
If you've got recovery installed it would be just for that purpose. Restoring your backup (i.e., recovery). I gather you don't have a backup?
What device do you have?
G920F International. The Recovery is not a custom one . It is the default recovery that doesn't have backup mode.
y2k2r2d2 said:
G920F International. The Recovery is not a custom one . It is the default recovery that doesn't have backup mode.
Click to expand...
Click to collapse
Ahh gotcha. Well...if it were me what I'd do is to boot to download mode and flash TWRP custom recovery file using Odin. Once that passes I'd boot into TWRP and do a backup.
You can then reboot into TWRP and try to restore your backup but you'll likely end up in a bootloop again. If that happens...
Then, I'd download a stock recovery (looks like they have your variant here.
I'd then flash the stock recovery using TWRP and then reboot.
If you get stuck in a bootloop again then I would do a factory reset (which doesn't wipe storage which is where your photos etc. are) and then reflash the stock recovery zip file.
I can't say for certain if that'll wipe your photos, etc. or not but I'm not inclined to think it would.
cwhiatt said:
Ahh gotcha. Well...if it were me what I'd do is to boot to download mode and flash TWRP custom recovery file using Odin. Once that passes I'd boot into TWRP and do a backup.
You can then reboot into TWRP and try to restore your backup but you'll likely end up in a bootloop again. If that happens...
Then, I'd download a stock recovery (looks like they have your variant here.
I'd then flash the stock recovery using TWRP and then reboot.
If you get stuck in a bootloop again then I would do a factory reset (which doesn't wipe storage which is where your photos etc. are) and then reflash the stock recovery zip file.
I can't say for certain if that'll wipe your photos, etc. or not but I'm not inclined to think it would.
Click to expand...
Click to collapse
Thanks. It will help in the backup.
Will factory reset/wipedata from stock recovery remove the pictures ?
Can you backup data using OTG/pendrive from TWRP recovery?
y2k2r2d2 said:
Thanks. It will help in the backup.
Will factory reset/wipedata from stock recovery remove the pictures ?
Can you backup data using OTG/pendrive from TWRP recovery?
Click to expand...
Click to collapse
factory reset doesn't erase storage data.
Not sure about otg/pendrive
Sent from my SM-G920T using XDA-Developers mobile app
I didn't flash TWRP as I learned that Samsung Pay will never work not even Stock ROM flash. I instead pulled some vital data files from adb pull on 'the window of around 1 minute' each time it was active during safe mode rebooting and thankfully Google Photos had a backup of my Photos and videos.
I used the wipe data option on stock recovery that wiped everything. The device is like new.
hi all, i made an xda account because i really cant understand whats going on with my phone
HTC One M8 running Android 6.0 (rooted)
so after rooting my phone, i proceeded to install xposed.
i flashed the zip - no problem
i installed the apk, and after choosing 4/5 modules that i wanted, i went ahead and enabled them all and rebooted to activate them.
this is where the problems started. my phone booted, however it kept on flashing a screen with the deafult One M8 wallpaper at me. after a few seconds, it came up with an error "com.android.systemui has stopped"
not sure what was going on, i went to twrp and directly restored my nandroid backup, but after waiting for 15 mins, i realised my phone was in bootloop, so i went back to twrp and did a factory reset and restored my nandroid. but again, it went into bootloop. i tried factory resetting and restoring 3 times before giving up.
my phone isnt connecting to my laptop anymore either, but if i need to flash anything i can do it with my sd card.
im not a complete noob but im still learning and ive never not been able to restore my nandroid.
thanks in advance for any help i can get
chaitra26 said:
hi all, i made an xda account because i really cant understand whats going on with my phone
HTC One M8 running Android 6.0 (rooted)
so after rooting my phone, i proceeded to install xposed.
i flashed the zip - no problem
i installed the apk, and after choosing 4/5 modules that i wanted, i went ahead and enabled them all and rebooted to activate them.
this is where the problems started. my phone booted, however it kept on flashing a screen with the deafult One M8 wallpaper at me. after a few seconds, it came up with an error "com.android.systemui has stopped"
not sure what was going on, i went to twrp and directly restored my nandroid backup, but after waiting for 15 mins, i realised my phone was in bootloop, so i went back to twrp and did a factory reset and restored my nandroid. but again, it went into bootloop. i tried factory resetting and restoring 3 times before giving up.
my phone isnt connecting to my laptop anymore either, but if i need to flash anything i can do it with my sd card.
im not a complete noob but im still learning and ive never not been able to restore my nandroid.
thanks in advance for any help i can get
Click to expand...
Click to collapse
*. Flash xposed uninstaller zip and try booting your device. Link here - http://dl-xda.xposed.info/framework/uninstaller/
-->> use this» make a full wipe from recovery, then restore nandroid backup.
*.While restoring nand. from recovery, make a full wipe like wipe system etc.. Then restore your nand. Then you're good to go.
thanks a ton for your reply
i already tried flashing the uninstaller - didnt work
but ill try your second method. thanks once again
chaitra26 said:
thanks a ton for your reply
i already tried flashing the uninstaller - didnt work
but ill try your second method. thanks once again
Click to expand...
Click to collapse
Hey, the 1st one won't works, Cuz you'd already did a factory data reset, so that's gonna be won't work. And you'd tried restoring nandroid over that, so that's failed.
I hope second one will works.
sachin n said:
*. Flash xposed uninstaller zip and try booting your device.
-->> use this» make a full wipe from recovery, then restore nandroid backup.
*.While restoring nand. from recovery, make a full wipe like wipe system / data etc.. Then restore your nand. Then you're good to go.
Click to expand...
Click to collapse
Um i think i seriously screwed up - i deleted everything including system and data and stuff - but now my nandroid is gone
what can i do now i dont even have a nandroid!
oh my god my phone doesnt have an os anymore... what have i done wrong?????
chaitra26 said:
Um i think i seriously screwed up - i deleted everything including system and data and stuff - but now my nandroid is gone
what can i do now i dont even have a nandroid!
Click to expand...
Click to collapse
Deym!!
So, look at the One m8 forums, you'll get the workarounds.
I've found one here - https://forum.xda-developers.com/ht...k-twrp-t3086860?_e_pi_=7,PAGE_ID10,5801529172
@chaitra26, either DL any custom ROMs and flash it via custom recovery [Twrp].
Look here for custom ROMs - https://forum.xda-developers.com/htc-one-m8/development?
Regarding that '' no OS installed'' error, that's common when you try to reboot your device from twrp without installing any system images /ROMs.
FYI - when you full wipe your device and tries to power up you'll get the same warning.
I have Xperia Z3c 5.1.1 rooted with locked bootloader. It is on wifi only. Yesterday I've turned wifi on and suddenly have got device off. I tried to reboot. I see the Xperia logo and bluish Xperia start screen with waving elements. However, the home screen and apps are not appeared, have just black screen. The battery is fully charged (green led). I tried several times reboot today as well with the same result. I believe the phone is soft bricked.
The phone is rooted with NDR Utils and TeamWin Recovery (TWRP). I also have Titanium backup.
After reading this forum I found several ways to unbrick the phone:
1. Soft reset (Power + VolUP) up to 1 vibration.
2. Hard reset (Power + VolUP) up to 3 vibrations.
3.Use flashtool (flashmode) and flash ftf file. Should I flash Kernel as well?
4. Use phone System recovery (Power + VolDown).
Which method I should try first? Can I save root and my current Lollipop firmware or I should go and start from the scratch with rooting and flashing 5.1 again?
Thank you for your suggestions.
Try soft reset and hard reset. This don't break your phone but it is worth a try. If this will not work do NAND backup (full backup of phone) in recovery. Now you can try clear cache in TWRP (wipe -> advanced wipe -> check cache -> swipe to wipe). If this don't work try clear dalvik/art cache.
If this metods didn't work flash same rom (if rom was't pre-rooted root after flash). If system starts you can restore NAND backup without system partition and cache.
If system don't start after restore backup the last chance is clear rom flash.
I don't know where the problem is but in my place I would do that
Thank you krzysiek546 for your help.
I have tried soft and hard reset, both unsuccesful. I made backup and wiped cache and dalvik from within TWRP. The phone after apps optimization has started the system (there was black screen but I was able to see home and Back buttons, which were non-functional, i.e non-responsive.) The screen became black again after a few secs and did not return to the life then.
I think I'm going to flash the Rom. My question is there is any chance to get brick again in case I will restore from the TWRP backup (if there was a virus or something?). May be I should wipe data, cache and dalvik and only then made a backup?
Also, when you saying "a clear rom flash" as a last chance do you mean factory reset?
Thank you.
Don't wipe data before backup. This is like doing backup after format system. It doesn't make sense.
Have you tried this metod with flash with nand backup and flash same rom (zip from twrp or ftf from flashtool) and restoring data without system partition (it's important)? In this i mean something corrupted system files. In this metod you can save your data. You just reinstall system and restore data from nand backup.
When I sayed "a clear rom flash" i mean wiping all data in recovery and flash rom from flashtool or twrp without restoring anything. You can do it first. I think now it's beter because you can check did that fixed your problem and if this "clear rom flash" repair your problem you can restore data from backup.
As to your question. Yes you can get brick from restoring data from twrp but in my opinion this virus or something must have root permissions to do this.
After installing the newest supersu, I also get this bootloop. Is there a chance to undo this without wiping data?
Edit: ok, after hard reset, flashing SU, cleaning caches etc. (which all did not help) I reflashed the ROM, now it works again. Pheeew.
firox said:
After installing the newest supersu, I also get this bootloop. Is there a chance to undo this without wiping data?
Click to expand...
Click to collapse
Try to install SuperSU v2.81 - author apologized for inconvenience caused regarding 2.80 update. I got this bootloop too and solved it by installing SuperSU v2.81.
MATPOC said:
Try to install SuperSU v2.81 - author apologized for inconvenience caused regarding 2.80 update. I got this bootloop too and solved it by installing SuperSU v2.81.
Click to expand...
Click to collapse
When I had that error, it was still V2.80 and no update round the corner.
Thank you for the link. Worked great for me. Installed per TWRP.
Well, in my case I didn't updated SuperSU, just have turned on wifi. I think the problem may be in Wallpaper app I have installed previously. It changes wallpaper every day, but I noticed sometimes the background of my home screen where all apps are became black.
Anyway, only "clear rom flash" with wiping cache, dalvik and data helped me. I then installed pre-rooted Lollipop ROM I made before and restored all custom apps from the Titanium backup. BTW, don't try to restore system apps from the Titanium, I've got the error with Xperia keyboard and have to make a restore whole system from TWRP.
Thank you krzysiek546 very much for your help.
MATPOC said:
Try to install SuperSU v2.81 - author apologized for inconvenience caused regarding 2.80 update. I got this bootloop too and solved it by installing SuperSU v2.81.
Click to expand...
Click to collapse
I also got bootloop after installing latest SuperSU from Google Play.
How can I install 2.81 (or 2.79) when phone is in bootloop?