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.
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 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!
900A, AT&T, WAS 4.4.4. I rooted my phone with towelroot by downgrading via ODIN then reflashing 4.4.4. I've had the phone for a year and wanted to experiment with some custom roms--specifically Twi5ted Lollipop. The version I found last night was V3. Anyways I followed the instructions of installing safestrap then attempting to create a partition to host the mod. Every time I tried to boot the partition I would wait 12 minutes with nothing but a black screen (I presume a bootloop.) After reading some posts here I found it requires a clean flash--not a dirty flash. So I used safestrap to backup, then I wiped it and installed the mod. Nothing--still black screen. I then attempted to restore the backup I saved--fails every time.
At this point being the noob I am, I started to get very concerned. I went into advanced wipe and for some reason selected 'system' and wiped it. After a reboot, it shows the Samsung logo, goes blank, vibrates then goes back to the Samsung logo. I went into the standard bootloader and attempted to restore to factory settings but there is nothing to restore of course cause I wiped everything.
I'm currently at work bored as heck cause my phone is wiped. I can still go into download mode thankfully. Should I have no problems flashing stock via ODIN when I get home on my lunch break? Which stock firmware should I flash for this phone?
Thanks!
http://forum.xda-developers.com/galaxy-s5/help
yes, wrong section, but hopefully the post is moved soon.
since you have a G900A, make sure you only flash an older 4.4.2 firmware, so you can still root. the newer 5.0 firmwares are currently unrootable.
I followed the instructions here http://forum.xda-developers.com/verizon-galaxy-s5/development/safestrap-odin-safestrap-flashable-t3161043 to install Safestrap on my phone with rooted BOE1, my phone rebooted, and I'm looking at a screen that say Android System Recovery <3e> LRX21T.G900VVRU2BOE1
I was trying to install the MOAR rom, but I fear that now I'm stuck in this strange recovery with no way out. Could someone please tell me exactly what I will need to do to get out, and possibly how to actually boot to Safestrap?
Not to leave anything out, though I'll look the fool if I don't, while in this recovery I wiped Data+Cache and attempted to install the ROM, got some sort of error about footers and signature verification (it happened pretty quick then rebooted) and wound up back in recovery, so I tried flashing the BOE1 kernel, same problem, back to recovery.
PhreeqQitsikk said:
I followed the instructions here http://forum.xda-developers.com/ver...t/safestrap-odin-safestrap-flashable-t3161043 to install Safestrap on my phone with rooted BOE1, my phone rebooted, and I'm looking at a screen that say Android System Recovery LRX21T.G900VVRU2BOE1
I was trying to install the MOAR rom, but I fear that now I'm stuck in this strange recovery with no way out. Could someone please tell me exactly what I will need to do to get out, and possibly how to actually boot to Safestrap?
Not to leave anything out, though I'll look the fool if I don't, while in this recovery I wiped Data+Cache and attempted to install the ROM, got some sort of error about footers and signature verification (it happened pretty quick then rebooted) and wound up back in recovery, so I tried flashing the BOE1 kernel, same problem, back to recovery.
Click to expand...
Click to collapse
S5 doesn't have a custom recovery per se, so any app that "reboots to recovery" will go to the Android stock recovery which your in. You can't flash anything of value in there, and can't install a custom recovery. You should just be able to turn the phone off then on again to get back to the stock rom, right?
It's been so long since I've done it, but won't safestrap only install on kitkat? Doors it even work in lollipop? Must people use flashfire I think
I should probably mention now that I got it fixed. Following more instructions in that thread, I did everything in the order of the first step again, using ODIN, flashed back to NC2 (I think? Going off memory) rooted, installed Safestrap, flashed MOAR, and the OC4 firmware, and here I am.
So I rooted, unlocked bootloader, flash custom recovery, flashed custom kearnel/rom, and somewhere in that process i unmounted or erased or something idk my internal sdcard.... Google and I have been looking for the latter part of the day for a fix or answer till I finally had to break down and open a thread. please can someone point me in the direction or instruct me on how to reformat or repartition my phone to have storage without flashing factory firmware? im also unable to mount my external sdcard aswell. Im running a 6.0 mm rom with missing storage.
Thanks,
DirtyWhiteBoy707
You have an unlocked bootloader and a custom recovery; "starting over" doesn't have to mean going back to full stock. (i.e., losing either the unlocked bootloader or your custom recovery)
One would surmise that because twrp offers the nuclear option of a full wipe (reformat) of the userdata partition, that it has the expectation that the kernel's init will recreate the "internal" sdcard if it doesn't exist on the first boot thereafter. Dunno, maybe your custom kernel doesn't do that; a stock ROM surely would though because a factory reset in stock always destroys the internal sdcard.
One of the freedoms that an unlocked bootloader gives you is the ability to flash whatever you please in Odin (so long as you don't nuke the now customized/unlocked bootloader).
So for instance if you thought the only way to do what you wanted was to "use the stock ROM for a few minutes", just hack together an Odin tar.md5** file containing ONLY the boot.img & system.img file blobs from the stock Odin file. Boot into TWRP, nuke (full wipe/reformat) of /data, & wipe cache. Then boot into Odin and flash your "almost stock" system.img/boot.img tar.md5 Odin file in the AP slot.
That would leave you with an "unrooted, pure stock ROM" - except for the fact that you still have both your custom recovery and an unlocked bootloader. So you could inject stock with root from the TWRP recovery (e.g. with the SuperSU flashable installer) if you wanted to go back to rooted stock, or you could nuke that ROM for a custom one afterwards using TWRP.
[ While you are making .tar.md5 blobs for Odin**, go ahead and make one up so you can reflash *only* your custom recovery anytime you like (just rename the twrp*.img file to "recovery.img" before putting it in the .tar file) - it sounds like you are accident prone. Note that if you did this you could even include the stock recovery.img in your "almost stock" custom Odin tarball; all it would take to restore TWRP would be a trip to Odin with your unlocked bootloader. This would let you perform the honest-to-dog factory reset/wipe if you thought that was critical ]
Myself I would first try a full userdata reformat (using TWRP) and see if your current ROM/kernel recreates the internal sdcard on boot. (OTOH, if your screwing around with the boot partition resulted in interfering with mount operation, maybe *existence* of the directories is not the problem.)
good luck
**instructions for creating Odin tar.md5 archives can be found all over XDA
solved
simply had to install the correct kernel for the partitions to be updated correctly. ended up using a kernel by Lsskernel for note5ports and 6.0.1
DirtyWhiteBoy707 said:
simply had to install the correct kernel for the partitions to be updated correctly. ended up using a kernel by Lsskernel for note5ports and 6.0.1
Click to expand...
Click to collapse
Makes sense.
Sort of a mystery that whatever boot partition (kernel+ramdisk) you started with didn't already do it... unless it was derived from a device that didn't use an "internal" pseudo-SDcard.
Probably even the stock kernel - dirty flashed - would have "fixed it" as well. It might not have booted into the UI, but by the time it wedged or bootlooped (late boot) what you wanted accomplished will have already happened (by "init" processing through the *.rc scripts.)
As often as people try it with the explanation "well, I tried it and it worked", when you mix-n-match ROMs with various boot partitions (particularly the contents of the ramdisk, far less so for the "kernel"), there's no guarantee that you didn't create a side effect in some subsystem (minor or major) as a result of changes written in to /data from that single boot cycle.
Dirty flashing leads to dirty behavior. Hard to predict how major or minor those problems might be though.