Database Users

My backups are not working....

Ok so first off I was successful in rooting the phone, installing twrp rec., flashing loki files, and then flashing wicked rom with ktweaker tw kernel. I made a backup of the stock rooted rom before wicked was flashed. Then my troubles started when I wanted to go back to my stock backup. The rom booted but has serious issues like black screen with only status bar working and then eventually freezing. I also made a backup of a working wicked and tried restoring that but then I just get stuck in boot loop. Any help would be greatly appreciated.

what twrp version
did you wipe all before restoring
you could try to install Phils cwm recovery, folks say it works great and will restore twrp backups also

thesystem90 said:
Ok so first off I was successful in rooting the phone, installing twrp rec., flashing loki files, and then flashing wicked rom with ktweaker tw kernel. I made a backup of the stock rooted rom before wicked was flashed. Then my troubles started when I wanted to go back to my stock backup. The rom booted but has serious issues like black screen with only status bar working and then eventually freezing. I also made a backup of a working wicked and tried restoring that but then I just get stuck in boot loop. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Follow full wipe procedures, have the same recovery you made the backup with, and try again.

rugmankc said:
what twrp version
did you wipe all before restoring
you could try to install Phils cwm recovery, folks say it works great and will restore twrp backups also
Click to expand...
Click to collapse
I flashed the stock firm. Soft brick averted. Did the same goo manager recovery method, but now i'm thinking of flashing that cwm as ppl have reported the same nandroid backup issues with twrp. My version is 2.5.0.2. I will keep trying to get twrp for a while with others users till i get sick of it (semi twrp fan). Any further advice would be cool. Oh and I did a factory twrp wipe the first time this problem occurred.

I wipe data caches and system before flashing. No more advice. Had newest TWRP hang on Team Win screen. Several manual reboots into recovery till it worked. Maybe I better do restore to see if it works.
Sent From My 32gb Samsung Galaxy S4 Running Tapatalk 4 Beta

[Q] "Kernel/Recovery is not seandroid enforcing" Removal Question

I have a Sprint Samsung Galaxy S4 that was running JB 4.3. When I decided to root and ROM it, I read a lot. I'll tell you what I did and where I got my files so you know exactly what happened:
In Download Mode:
First I Odined UnknownForce's NAE Modem Only Firmware with No Bootloader
Then I Odined Philz Touch Recovery 6.15.6
I booted to Recovery.
I cleared Cache and Davlic Cache twice.
I did Wipe/Factory Reset twice.
Then I flashed using Rawintellect's Stock(ish) Rom.
I install Ktoonsez Kernel for Sprint Touchwiz
At this point I am running a custom rom with a custom recovery and a custom kernel. It runs great.
I have no SEAndroid messages about the kernel or recovery at this point.
I decided to upgrade to Kit Kat 4.4. I did a nandroid backup. Then I took the official Sprint MD5 update and Odin it right over my rom. It worked. When the system boots up, it is running the Touchwiz version of Kit Kat. But I don't have root.
So I go to recovery to flash CF-Auto-Root-jfltespr-jfltespr-sphl720.zip but I'm back to stock recovery. So I go to download mode and re-Odin Philz Touch Recovery 6.15.6. Then I reboot to recovery.
There is an SEAndroid Recovery Message! But it lets me into recovery and I flash the zip. Reboot.
Since I was back to stock recovery, I check the kernel in settings. It's back to stock to. So I boot back to recovery and reinstall the custom kernel. Reboot to system.
There is an SEAndroid Kernel Message now! But it lets me into the system and I have root. I run Titanium Backup and remove Knox Files according to these instructions. I used method two for rooted phones. I also use method three.
Rebooted. Still showing the SEAndroid messages.
So I booted to download mode and re-Odined the NAE Modem Only Firmware with No Bootloader. Shut down phone and rebooted.
Still have the messages! Now I'm frustrated. So I do a Nandroid Backup of the KitKat Version and restore my nandroid backup of the Stock(ish) rom.
Phone works but I still have the SEAndroid messages! So I restore my nandroid backup of Kit Kat and started researching this.
What I know:
Though the messages may cause issues and boot loops for some, it is not doing it for me.
The messages do not hurt the functioning of the system.
I know the Knox counter was tripped from 0x0 to 0x1. (I never saw the Knox counter till I did this In fact!)
I know going back to stock recovery and kernel will remove the messages.
What I want:
I know the "Kernel/Recovery is not seandroid enforcing" doesn't hurt the phone but I want the message gone. I was on a rooted phone with custom rom, recovery and kernel without these messages showing up. Something is different from the way the phone was setup before and now. I don't want to go back to stock anything.
The SEAndroid is software. Software can be removed.
How do you remove it?
I know Knox was tripped somewhere in this process. Will that cause the message to appear even if your running without a boot loader?
How can I remove the SEAndroid software so it doesn't even run? Any ideas?

When you created your backup via Philz/CWM did you make sure to set the nandroid settings to back up SE Linux context? if not that is probablye your issue.

SE Linux context?
leaderbuilder said:
When you created your backup via Philz/CWM did you make sure to set the nandroid settings to back up SE Linux context? if not that is probablye your issue.
Click to expand...
Click to collapse
I don't know what SE Linux context is? Is it something I can do now? If not, what other options do I have?

It's in the misc nandroid settings.
Too late now if you didn't do it when you created your 4.3 backup though.

Will Any Nandroid Backup Work?
My wife and I bought the exact same phones on the same day. When it came to installing the Stock(ish) rom, I did the exact same thing to her phone. She insist that I experiment on mine before I do anything to her phone.
She does not have the "Kernel/Recovery is not seandroid enforcing" messages.
Can I do a complete Nandroid back up of her system and the SE Linux Context, copy it to my SD card and install it? I know it would be an exact duplicate of her system but I have all my apps backed up with Titanium Backup so I can re-install them easily. And of course I would have to log into my Google account and delete her account. Would that put me back the way I was?

I doubt it -device id stuff in Android.
BUT there is a way to get you back most likely.
IF you didn't upgrade to NAE(or MK2) bootlader and just the modem (as you mentioned) the simplest thing to do would be to install stockish fresh.
Let it boot and then add your google account and let all the apps update - about 1/2 hour on wifi
Then load/install titanium ( if it didn't install) go to preferences and let it find/search for your backup directory and restore - you'll be asked first to 'restore device ID' choose YES and let it reboot!
Then you should be good to go. I know I've done this a few times.
Another bonus is that you'll have a fresh install to 'start from'

Titanium Backup May Hold The Key?
leaderbuilder said:
I doubt it -device id stuff in Android.
BUT there is a way to get you back most likely.
IF you didn't upgrade to NAE(or MK2) bootlader and just the modem (as you mentioned) the simplest thing to do would be to install stockish fresh.
Let it boot and then add your google account and let all the apps update - about 1/2 hour on wifi
Then load/install titanium ( if it didn't install) go to preferences and let it find/search for your backup directory and restore - you'll be asked first to 'restore device ID' choose YES and let it reboot!
Then you should be good to go. I know I've done this a few times.
Another bonus is that you'll have a fresh install to 'start from'
Click to expand...
Click to collapse
That was one thing I was worried about. When the update I did redid the recovery and kernel, did it redo the boot loader too? That was one reason I re-installed the NAE modem without bootloader a second time.
So are you saying that I re-install Stock(ish) fresh then do a COMPLETE Titanium restore and not just certain apps? Would that reset the SE Linux Context so the SEAndroid messages don't appear?
I know in the past when I have played around with roms, Titanium may prompt me to "Restore My Device ID" so that all my apps will work. If I used my wife's Nandroid backup, wouldn't it ask to restore my device ID anyway? Would that bypass the Device ID problem?
Thoughts?
EDIT: I just saw THIS in another thread! It looks like the Nandroid backup may work.

When you say you did the update I believe you are/were talking about just the firmware/modem, is that correct?
And if you added a recovery that won't affect the bootloader.
You can try the nandroid option it may work
If you have a titanium backup of your phone you'll be able to restore nearly everything after you re-flash stockish.
So if you dont' then don't user hers.
As for SE linux context as long as you MF9 Booloader and you can check by downloading this app and running it (It'll show bootloader version) then you can re-install stockish and then as above re-sync your google account which will grab your apps and other settings -wifi, hotspots email etc. (just not specific application settings)
One thing I got to thinking if you are on MF9 and just borked you restore you can always just try 'dirty flashing' stockish. Just go to recovery, wipe cache, wipe dalvik and then flash over existing ROM (don't delete data) and you might just be good to go! If not then full wipe and restore.
Again just make sure we are talking apples to apples with regard to the bootloader being MF9.

Here's an update:
I made a fresh nandroid backup of my wife's phone. Copied it to mine. Wiped the phone and installed backup. Phone worked fine but the seandroid message is still there.
Wiped phone again. Reinstalled Stockish rom. Then installed an old nandroid backup I had from January. Message till there.
Then I went crazy. I went to Odin, did a nandroid wipe and re-partioned the whole phone. (Don't not try this at home! Seriously. DON'T.) I was able to bring back the phone because I had the pit file for the partitions.
No pit file, no partitions, no phone. You will have a brick.
Then I installed the modem without the boot loader and recovery. Booted to recovery.
The message was still there.
WTF!
Installed Rom and brought phone back to life. I'm on the NAE bootloader. When I've tried to downgrade, Odin errors out.
Where does the boot loader reside? It wasn't there when I bought the phone. It was installed later so it had to go somewhere.
Thoughts anyone?
Sent from my SPH-L720 using xda app-developers app

Well right now I'd just Odin the NAE .tar. It's got all partition info and will load, boot, recovery(stock), system, data, modem/baseband. Wiping all other/old partitions.
Only thing is you'll have the knox bootloader. BUT that really isn't a big deal - you can root using the LATEST CF-Autoroot from Chainfire's thread/site. Install a custom recovery and then install just about anything (well following the devs instrucions as per their OP).
The 'knox bootloader' is more than just a simple 'boot' partition - it's an actual cmos/chip write change! That's how they know and can track if you've tripped it. So far no, that I know of, has found away around this. The boot partition - in standard terms is still editable; hence the ability to create custom recoveries.
Good luck.

My girls S4 is Sprint.. Also with the NAE bootloader and I've wondered how to get rid of this stupid boot screen.
I've Odin the thing at least 3 times and rooted with CF then installed Philz. Each time no dice.
Now my Verizon S4 automatically backs up SE Linux Context. I never noticed a setting for that in Philz. Now maybe I just missed it since her phone doesn't get flashed all that much and like I said I'm on a Verizon S4.
I figured this was just a bi product of having a Knox Bootloader and having the phone rooted/custom recovery.
I'd love to figure out how to get rid of that screen though. I'll have to do some searching. Tri Angle Away gets rid of my " custom" Splash screen at boot... It'd be nice it it also got rid of this screen on the Sprint S4. I'll at least give it a whirl but something tells me its not that easy.
Sent from my SCH-I545 using Tapatalk

running this rom and gapps. upon boot up i receive this message in the top left hand corner: kernel is not seandroid enforcing, set warranty bit: recovery.
the phone seems to function fine. Whats up with it?

It's purely cosmetic. The shop can tell at a glance it's not stock rom this way.
Would be nice to find a way of making it disappear though, just plain untidy lol

same here
i guess still no solution to this? I have an s6 & have scoured the web & this thread has been the most informative resource on this issue that i've found. I started getting "kernel not seandroid enforcing" red text ever since i upgraded to 5.1. pretty strange. I know its proly different but my last phone was m8,and there was a red warning text on boot after root too (something about being for developers only...) . But there was a a special hboot mod that when flashed would remove it. Wish it could be that simple here ha! It drives me nuts, I dont know why but it does!

[Q] N910G won't boot after TWRP restore?

Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS

MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
This http://forum.xda-developers.com/note-4/help/n910c-to-stock-rom-cm13-t3321132 :good:

One possible solution is to flash the appropriate stock rom via odin. After booting, install twrp and root your phone. After this you can restore your previously saved stock rom via twrp.

MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
Sorry no help from me but I have a similar problem. At some point mine quit booting to TWRP and I got a huge OTA update a few days ago and every time I try to boot into recovery it ends up in Stock Recovery only after going to little android saying installing updates(it fails & eventually goes to stock recovery.) I did a reset and still have 5.1.1 installed and still have the same behavior.
I have the professional version of the unified toolkit and it says if it is still booting into stock recovery select options 7, 3 which I did but it didn't fix the problem. I think what's getting me is it thinks there are still system updates to install.

s5 fix from bootloop what to do?

So after a week of just bootloop, black screen of death and hard reset my rooted s5 suddenly open again.
Now that its open again what can I do to fix this? Cause im afraid that if i'll restart my phone i will get stuck in the bootlooop.
Suggestions?
Just to give you an update my s5 has been rooted for the past 2 years ...its just now that it got stuck in the bootloop.. im not really sure what caused this cause havent installed any apps that could affect the system...
Any ideas how can I fix it while its working again?

Would help if you gave us the model S5 it is, which firmware it's running, recovery etc?

Its g900f using stock rom... stock recovery
Please see attached file
Thanks in advance.

Download stock ROM using samfirm (or sammobile .com)
http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Put phone in download mode
Connect to PC USB > add .MD5 ROM to AP section in ODIN 3.10.7
Flash
Boot to recovery > Factory reset

Any other fix without flashing?

Any other fix.. that doesnt require flashing?

kenchii17 said:
Any other fix.. that doesnt require flashing?
Click to expand...
Click to collapse
Why don't you want to reflash? If you're rooted you should have backups.

Ok I think I missed that part... ok so if I flash, everthing will be wiped out right?
How do I back it up?

kenchii17 said:
Ok I think I missed that part... ok so if I flash, everthing will be wiped out right?
How do I back it up?
Click to expand...
Click to collapse
No it won't, and for a proper backup you need TWRP recovery
If your phone is having problems like it is, you very likely need to flash
Just flash the stock ROM over the top and your apps and data will remain
But backup photos and important files first by connecting the phone to USB and copying to PC
Forget about apps, you can reinstall them if something goes wrong

Ok thanks im starting to understand it now.. i just need to confirm a few things before i start doing it...i have watched a few vids and ok i think i missed installing a custom recovery... ill install it later and go with cwm...
Flashing the stock.. means getting my firmware(which has the size of 1gig+) in sammobile ang flashing it using odin right?

Read my 2nd post

Thanks alot got it! One last question , suppose that im not going to lose my apps but am i going to lose root once i have flashed the stock rom?

Yep, just root again, instructions are all over the forum, easy to find
Because you're getting bootloops, I suggested factory reset too, that will wipe the device, the flash won't, the reset will

I assume here's the steps that i need to take
1. Back up through cwm
2. Flash stock rom through odin
3. Clear dalv cache
4. Factory reset through recovery or from the homescreen setting?(will this removed supersu?)
6. Root device again
5. Restore back backup from cwm recovery?

Better method:
Flash TWRP 3.0.2.0 (Much more powerful recovery)
Make full Nandroid backup in TWRP
Wipe everything apart from Internal and External storage
Boot into Download Mode
Flash stock ROM with ODIN 3.10.7
Reboot
Now boot back into download mode
Flash TWRP 3.0.2.0 again
Boot into TWRP
Flash systemless SuperSU 2.72 beta or whichever is the latest beta atm
Don't restore your backup or you could end up with the same problems as before, I recommend using TiBu to restore your apps and data from the backup you made in TWRP

*Detection* said:
Better method:
Flash TWRP 3.0.2.0 (Much more powerful recovery)
Make full Nandroid backup in TWRP
Wipe everything apart from Internal and External storage
Boot into Download Mode
Flash stock ROM with ODIN 3.10.7
Reboot
Now boot back into download mode
Flash TWRP 3.0.2.0 again
Boot into TWRP
Flash systemless SuperSU 2.72 beta or whichever is the latest beta atm
Don't restore your backup or you could end up with the same problems as before, I recommend using TiBu to restore your apps and data from the backup you made in TWRP
Click to expand...
Click to collapse
I have tried to flash twrp on my galaxy s5 (SM-G900V) and it did not work I am kinda stuck in the same problem. But I hit softbrick. Can you take a look at my post also?

jakeh9777 said:
I have tried to flash twrp on my galaxy s5 (SM-G900V) and it did not work I am kinda stuck in the same problem. But I hit softbrick. Can you take a look at my post also?
Click to expand...
Click to collapse
Verizon lock their bootloaders

*Detection* said:
Verizon lock their bootloaders
Click to expand...
Click to collapse
It's unlockable nowadays

*Detection* said:
Verizon lock their bootloaders
Click to expand...
Click to collapse
Can you check out my situation see if it is fixable without loading data? http://forum.xda-developers.com/galaxy-s5/help/how-recover-data-softbricked-galaxy-s5-t3382554

Rakuu said:
It's unlockable nowadays
Click to expand...
Click to collapse
Yep, but without unlocking it, he can't flash anything
jakeh9777 said:
Can you check out my situation see if it is fixable without loading data? http://forum.xda-developers.com/galaxy-s5/help/how-recover-data-softbricked-galaxy-s5-t3382554
Click to expand...
Click to collapse
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
Unlock your bootloader and try again

Back to stock Nougat?

I have a Moto X Style XT1572 Indian version. I updated it to stock Nougat 7.0 via OTA when it was rolled out in India. Later in January I unlocked the bootloader and installed unofficial TWRP recovery for flashing custom ROMs. I did take a full backup of stock ROM immediately when I installed the recovery. Since then I'm using custom ROMs built for Nougat modem.
At present, how can I go back to stock Nougat? I did do a full wipe (except internal memory) and tried to restore the stock Nougat backup which I took in January. The backup always gets successfully restored. However, when the phone boots up completely and reaches the language selection screen(the first screen when the phone boots up), the phone reboots and goes into a bootloop just displaying the bootloader unlocked screen. The only option I have then is to flash any custom ROM again and they do work perfectly. So what must be restricting the stock backup to boot? Also, is there any other way to go back to stock Nougat?

anyone, please?

AsquareX said:
anyone, please?
Click to expand...
Click to collapse
This thread looks like it has the nougat full firmware package for your phone. Try fastboot flashing all of it: https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257
If that doesn't work out, here's another trick I've seen work on occasion. Restore your TWRP backup, but do not reboot into it. After restoring the backup, use TWRP to flash stock recovery, then reboot to recovery and do a factory reset with the stock recovery. Then reboot into the stock rom. That can clear up some internal storage problems that hang things up. There are other ways to do it, but this is easiest.

jason2678 said:
This thread looks like it has the nougat full firmware package for your phone. Try fastboot flashing all of it: https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257
If that doesn't work out, here's another trick I've seen work on occasion. Restore your TWRP backup, but do not reboot into it. After restoring the backup, use TWRP to flash stock recovery, then reboot to recovery and do a factory reset with the stock recovery. Then reboot into the stock rom. That can clear up some internal storage problems that hang things up. There are other ways to do it, but this is easiest.
Click to expand...
Click to collapse
I'll give a try to the fastboot version.