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!
Related
Did anyone's TWRP become broken after updating to 4.4.2? Thought I'd ask because everytime I attempted to gain access to Recovery Mode, I would get an error (it said something like "No connecrtion"). I had to manually flash TWRP with Wugs and was able to successfully gain access to Recovery Mode again.
urbanman2004 said:
Did anyone's TWRP become broken after updating to 4.4.2? Thought I'd ask because everytime I attempted to gain access to Recovery Mode, I would get an error (it said something like "No connecrtion"). I had to manually flash TWRP with Wugs and was able to successfully gain access to Recovery Mode again.
Click to expand...
Click to collapse
I've not updated my Nexus 7 to KitKat yet, but I just noticed on my Nexus 5 that TWRP is broken after updating to the 4.4.2 OTA. I don't get the "No connection" error, I just get the little dead android icon with the red exclamation point. Too bad I'm at work and won't be able to re-flash it until I get home.
You're not alone.
urbanman2004 said:
Did anyone's TWRP become broken after updating to 4.4.2? Thought I'd ask because everytime I attempted to gain access to Recovery Mode, I would get an error (it said something like "No connecrtion"). I had to manually flash TWRP with Wugs and was able to successfully gain access to Recovery Mode again.
Click to expand...
Click to collapse
Lacking any and all details about how you upgraded, I would have to say that is to be expected. The OTAs usually directly overwrite the recovery with a new version of the stock recovery.
Moreover, the most recent OTA used that "/system/recovery-from-boot.p" patch file and associated script "/system/etc/install-recovery.sh" mechanism that automatically overwrites the recovery by patching the boot partition image; I think this happens either on every boot (or maybe during a clean shutdown).
So, not having noticed that, I flashed a custom recovery & booted the stock ROM... and next time I rebooted into recovery, I was back at the stock recovery ... WTF?, right?
I renamed those files to stop that from happening. I think some of the recoveries are aware of this and perform similar tricks on your behalf when they "install root" for you, but if you continue to get your recovery overwritten by stock, this is the place to look.
FYI I capture a full nandroid backup of every new stock release, whether or not I plan on using stock. I set them aside (copy them to a PC) so that they are always available.
I do this by:
- TiBu user app & data backup
- make a nandroid backup of my current ROM
- restore a nandroid backup of the prior release of the pure Stock ROM including it's matching stock recovery
- take the OTA and apply it (note everything is COMPLETELY, 100% stock during this operation)
- soft-boot a custom recovery via fastboot ("fastboot boot ...")
- make a nandroid backup of the new pure Stock ROM, including it's matching stock recovery
- flash a custom recovery and either restore a different ROM, or root the stock ROM and move forward with TiBu
This may seem like a lot of work, but it preserves maximum flexibility and safety:
(a) I can roll back to pure stock (any version!) any time I please from my archive of stock nandroid backups.
(b) I never - ever - have problems with OTA installation (including hazardous things like bootloader installs)
(c) I never need to go begging on the internet "please anybody, can you send me file "xxxx" from the stock release "xyz" ? I already have them - all of them.**
hope that helps
** note that TWRP's ".win" files are just tar archives. You don't even need to restore prior ROMs to pluck out individual stock ROM files.
I downloaded twrp and CM 10.1 CR2 for my MK2 4.3JB galaxy S4.
I made nandroids on the extra then went in used the wipe feature in twrp then loaded cm and gapps. Worked great and I love the ROM.
Went to put back nandroids. Used the wipe feature again then restored nandroid. Bootleg and stuck on the yellow sprint screen. Tried to flash Odin .tar and it started with a ton of FC then said something about data partition.
I had no choice but to factory wipe and I wanted to keep all my internal stuff. The stock to CM worked fine but just doing general wipe did not work to restore my nandroid.
The CM I noticed is 4.2.2. Is this an issue going back to stock 4.3 nandroid ?
I'm restoring the phone completely so it's fresh out of the box then rooting then using twrp to try to get back my old nandroid.
What did I do wrong in the process that caused it to stall on the yellow sprint screen ?
Now that I think about it I did probably a "dirty" flash since. I did not completely factory wipe the phone just the dalvik cache, cache and the last item on TWRP.
Once you go to 4.3...aka MJA or MK2 you cannot go backwards. So that may have been your issue. Try stayin with 4.3 or up
If you say "Please"... be sure and "Hit Thanks!!!"
OK I tried again after wiping, flashing 4.3, rooting, setting up TWRP.
I wiped everything and when I made my nandroids I checked ALL the boxes. I'm currently on CyanogenMod which works fine but I cant restore my nandroid. I wiped all then used restore from my SD card. I have twrp 2.6.3.0 I think.
I'm still getting stuck on the sprint screen. Help !
Don know about checking everything?? I make sure that SE Linux is checked (i use philz) and then save to SD. Have had zero issues so far and I bounce from 4.3 TW to 4.4 AOSP daily. Sorry I've never used TWRP so I cannot begin to help troubleshoot.
If you say "Please"... be sure and "Hit Thanks!!!"
I just want to make sure you are not wiping before you create the nandroid backup. I reread your post and it was unclear. When creating the backup you should not wipe first. Next, when switching between AOSP and Touchwiz things can get tricky. Usually a failure to boot is after doing a nandroid is caused by the kernel not being correct for the rom installed. It would probably be best to keep an AOSP kernel and a Touchwiz Kernel on your sdcard so you can flash it after you restore the nandroid backup to ensure the proper kernel is in place.
Secondly, it was mentioned above that you can't go back to 4.2.2 after going 4.3. This is actually incorrect. You cannot flash a stock tar of an older 4.2.2 rom through odin if you have the MJA (AKA Knox bootloader). You can however flash a 4.2.2 rom using recovery since it does not attempt to change the bootloader.
cruise350 said:
I just want to make sure you are not wiping before you create the nandroid backup. I reread your post and it was unclear. When creating the backup you should not wipe first. Next, when switching between AOSP and Touchwiz things can get tricky. Usually a failure to boot is after doing a nandroid is caused by the kernel not being correct for the rom installed. It would probably be best to keep an AOSP kernel and a Touchwiz Kernel on your sdcard so you can flash it after you restore the nandroid backup to ensure the proper kernel is in place.
Secondly, it was mentioned above that you can't go back to 4.2.2 after going 4.3. This is actually incorrect. You cannot flash a stock tar of an older 4.2.2 rom through odin if you have the MJA (AKA Knox bootloader). You can however flash a 4.2.2 rom using recovery since it does not attempt to change the bootloader.
Click to expand...
Click to collapse
I don't think I wiped before making the nandroid, but I'm not sure. I have the Sprint GS4, and the nandroid was a 4.3 (Dec 2013) firmware.
Can you help me out here, I'm really lost. Do I need to flash a Touchwiz kernel on top of the nandroid through TWRP (flashing multiple zips) ? Where do I get the kernel ?
Made a nandroid of my Cyanogen Mod. Wiped phone and restored Cyanogen Mod nandroid. No problem. Worked fine. Just the original that I made is not working.
mikeprius said:
Made a nandroid of my Cyanogen Mod. Wiped phone and restored Cyanogen Mod nandroid. No problem. Worked fine. Just the original that I made is not working.
Click to expand...
Click to collapse
There are a lot of people that have had problems switching between Cyanogen Mod and Touchwiz using nandroid restores. It usually is the Touchwiz kernel not being restored when restoring the backup. When you boot up, you won't get past the initial boot screen. If this happens, you should just have to reboot back in to recovery and flash a TW kernel then reboot or after your restore your nandroid backup, just flash the TW kernel before rebooting. Look in the Android Development section for a custom TW kernel or you can try this kernel that unkownforce posted from his Triforce rom: http://www.androidfilehost.com/?fid=23321874045862620
cruise350- You are my hero. The nandroid DID come back and is working This has racked my brain all night and I am so so glad that I got my nandroid back.
I do have a few more questions:
1. The Wifi is not working ?
2. It appears that my Sprint is on 3G, and not going to 4G LTE ? Do I need to do something with this ? I also am getting errors trying to update my profile and PRL.
3. Is a custom TW kernel always required to be used, is there a stock Samsung TW kernel ?
Thanks a TON ! I couldn't figure out it for the life of me. Other than that I have been enjoying Cyanogen Mod. Using goomanager it looks like some CM versions are not flashable with TWRP and only by Clockworkmod.
on some roms i know that if you don't use the kernel that comes with it the wifi doesn't work. maybe try stock? in your mobile network settings, is your preferred network type "lte/cdma/evdo'? i'm sure there's a stock kernel on the forum somewhere.
It was set on global, so I switched it thanks for the heads up. Wifi still out of commission though. Once I get this set up, I'm eager to try new ROMs. I'm still on the fence about TWRP though. It's a nice interface vs. Clockwork, but it seems like most files out there cater more to CWM
mikeprius said:
It was set on global, so I switched it thanks for the heads up. Wifi still out of commission though. Once I get this set up, I'm eager to try new ROMs. I'm still on the fence about TWRP though. It's a nice interface vs. Clockwork, but it seems like most files out there cater more to CWM
Click to expand...
Click to collapse
i can't really give advice on that since all i've used is cwm. idk what kernel that one is, but i think it now comes with kt-sgs4. maybe the one from before? i looked around and i couldn't find a stock kernel by itself for mja or later. if you extract the boot.img from a stock rom the kernel and ram disk are in there. how easily you could screw up your phone doing that is beyond my experience, so maybe try a different custom kernel and wait for somebody else's advice for the boot.img thing?
Wifi AND booting (as @cruise350 mentioned) are almost always a kernel issue.
What ROM are you actaully on?
How did you get there, your nandroid?
What kernel are you now using and how did you flash it?
Have you tried gonig into settings, turning off wifi, wait a moment and then trying to turn back on?
Sounds like you should flash a stock(based) TW ROM and go from there. That often clears up connection issues.
Also might want to set your 'network type' back to automatic.
As for CWM and TWRP both are superb just make sure you follow the ROM developers recommendation as to which to use. (Philz is a CWM based recovery). There are .tars and zips of the latest of each here in these forums.
Please spend some time here reading, searching and then reading some more. You will find all the answers to your questions and it will give you a huge grasp of what is what and how to do things properly.
Good luck.
I am currently on the L720VPUEMK2 ROM 4.3 for Sprint. Android version 4.3 (Dec 2013 update).
I used TWRP 6.2.3.0 to flash Cyanogen Mod 10.2 nightly version (not sure if matters specifically which one).
My kernel was from TriForceKernel on the link above. It says 3.4.0-gb72521e-dirty. I flashed it after I flashed my recovery after wiping the device including internal data, cache, dalvik cache via install .zip in TWRP then rebooted.
The phone has loaded up but does not seem to be toggling between 4G LTE and the wifi is busted. I checked my nandroid and it says there is a boot file in it.
When I created my nandroid, I checked all the boxes, then slide the toggle which was supposed to create a back up for all 6 segments. I'm not sure why the boot.img isn't loading, it's part of the recovery that saved it. The settings seem to be as I left them....there are just some little things that are problematic.
I have a boot.emmc and boot.emmc.win both that are part of the nandroid recovery that has been flashed yet it gets stuck on the splash screen.
Well I'd just wipe and try any one of the FIVE TW ROMs that have been dropped in the last 7 days.
Trying to fix whatever is your issue could take hours or days.
Wiping completely (as per whichever dev's ROM you choose), installing said ROM, and starting from scratch will assure you phone works AND give you the best chance to get stuff working.
I dirty flash, restore and install ROMs all the time.
However When I absolutely want to know I'll have a good working ROM I clean flash. Wipes, setup, let Google restore apps, debloat restored (and stock apps!) then setup each setting and app to my liking. Titanium comes in real handy - after all my apps are re-downloaded I can selectively restore data to those that need it (Kindle, newsreader, SMS, Call Logs etc.)
Try that - installing clean new ROM and see what happens. Then go from there. Or don't and spend another couple days without a completely working phone.
Ok, so I flashed a custom rom and kernal and all went wel except my contacts didn't sync. I couldn't pull them from my Nandroid or my Tibu backup. So I tried to flash the backup I did last night and it failed. So I tried to flash another backup from earlier and it said successful in TWRP but it wouldn't boot after. I tried to go back into recovery only to realize that I no longer have my custom recovery. I do have a working stock recovery though.I'm kind of in a jam here and really need the help guys. I probably should have just cut my losses with the contacts.
More details. I flashed Danv's ASOP Kitkat 4.4 with the latest Ktoonez kernal successfully. I tried to recover my stock rooted 1337m 4.3 rooted with Saferoot. It won't boot into it. Maybe the difference in kernal has an issue with that or would that have been taken care of in my Nandroid flash?
Going forward, I'm thinking about another factory wipe and going into download mode with Odin and flashing my stock 1337m firmware to the phone and booting up. I'm just looking for a little direction here since I got in a bit over my head. I thought I did it all by the book by doing a Nandroid,and Tibu backup, and backing Tibu up to Google drive and my SD card, but clearly something didn't go right and now I'm on the ropes. I just want a working phone again. I can't sleep lol. I'm serious.
Tough crowd eh? So I'm hanging at my boot screen after successfully restoring my Nandroid backup in TWRP. I've lost my custom recovery but I got root before I did through TWRP. If I did a factory reset in the stock recovery, could this potentially fix my boot hang? Or is flashing back to stock 4.3 in Odin the only option? Or is there another method I can force it to boot? I'l be honest: not having my custom recovery and going into the unknown is nerve racking here knowing I don't have my get out of **** card to save my ass. Can I push my Nandroid backup and relfash it through Odin?
crazymax1 said:
Tough crowd eh? So I'm hanging at my boot screen after successfully restoring my Nandroid backup in TWRP. I've lost my custom recovery but I got root before I did through TWRP. If I did a factory reset in the stock recovery, could this potentially fix my boot hang? Or is flashing back to stock 4.3 in Odin the only option? Or is there another method I can force it to boot? I'l be honest: not having my custom recovery and going into the unknown is nerve racking here knowing I don't have my get out of **** card to save my ass. Can I push my Nandroid backup and relfash it through Odin?
Click to expand...
Click to collapse
Can you get in to download mode and if so does it show KNOX security enabled?
By
crazymax1 said:
Tough crowd eh? So I'm hanging at my boot screen after successfully restoring my Nandroid backup in TWRP. I've lost my custom recovery but I got root before I did through TWRP. If I did a factory reset in the stock recovery, could this potentially fix my boot hang? Or is flashing back to stock 4.3 in Odin the only option? Or is there another method I can force it to boot? I'l be honest: not having my custom recovery and going into the unknown is nerve racking here knowing I don't have my get out of **** card to save my ass. Can I push my Nandroid backup and relfash it through Odin?
Click to expand...
Click to collapse
Tbh I would flash back to stock via a verified stock fw via odin, Reroot, reinstall cwm/twrp, and then flash rom from that point.
Ive never had luck recovering backups cross rom. Whether Nandroid or tb.
Sent from my SGH-I337M
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.
Really in a bind here. I have a VZW Note 3 with JasmineROM 6.1. This morning I was prompted to do a SuperSU update and I went along and now I'm stuck in a boot loop. When I did Jasmine 6.1 last October I stopped seeing any Safestrap boot, so I'm not sure how to get into a mode where I can grab data. Any help here would be greatly appreciated. Right now all I can do is get into stock recovery and download mode.
Reading between the lines it sounds like you:
- have a locked bootloader
- have no custom recovery
If that is the case, you probably have a trip back to stock in your future: you have lost the only root you had. An unlocked bootloader would allow you to flash whatever you wanted in Odin (for instance, re-flashing a Jasmine system.img or a twrp custom recovery), but without that you are restricted in Odin to only flashing Sammy-signed blobs.
You might spend some time to see if Jasmine supports a "safe mode" boot on the off-chance that the bootloop is being caused by a market app.
A "dirty Odin flash" of only the stock system.img probably will not boot correctly or will also boot-loop, so I suppose that means you are in danger of losing all data on your phone as well. But you could try this as a last-ditch desperation move. The worst that could happen is that you will still have to flash back to pure stock... and lose all your data. (The stock recovery "factory reset" wipes everything, including the so-called "internal" SD card).
sorry
bftb0 said:
Reading between the lines it sounds like you:
- have a locked bootloader
- have no custom recovery
If that is the case, you probably have a trip back to stock in your future: you have lost the only root you had. An unlocked bootloader would allow you to flash whatever you wanted in Odin (for instance, re-flashing a Jasmine system.img or a twrp custom recovery), but without that you are restricted in Odin to only flashing Sammy-signed blobs.
You might spend some time to see if Jasmine supports a "safe mode" boot on the off-chance that the bootloop is being caused by a market app.
A "dirty Odin flash" of only the stock system.img probably will not boot correctly or will also boot-loop, so I suppose that means you are in danger of losing all data on your phone as well. But you could try this as a last-ditch desperation move. The worst that could happen is that you will still have to flash back to pure stock... and lose all your data. (The stock recovery "factory reset" wipes everything, including the so-called "internal" SD card).
sorry
Click to expand...
Click to collapse
I wound up having to do a factory restore which restored me to a clean state of JasminROM. After that I performed the new bootloader unlock and installed TWRP. Lost some data, but didn't have a choice. Last fall when I upgraded JasmineROM to 6.1 it got rid of Safestrap which was the only way to get out of this bind. At least now I have TWRP and can use that in the future.