T-mobile has introduced rollback protection for both kernel and bootloader. There is no going back or flashing a non signed kernel for now.
More info as this develops.
This is true, this OTA does NOT allow you to odin @eousphoros TWRP version. It also does not allow you to downgrade kernel or bootloader, this leaving you on stock until @Chainfire and @bigbiff can have a look at the OTA..This is a sad day for T Mobile users
Notice the splash screen as well, it says "RECOVERY IS NOT SEANDROID ENFORCING". Youl will get the same message when attempting to downgrade your kernel...
Bl rollback protection
so does the switch to unlock the bootloader in the developer options not have any bearing on the rollback protection?
This is great news, not more than 1 hour prior to the message getting posted i had finished loading 5.11, without greenify in rooted mode, it's already using more battery life than previously with root.. This totally stinks.
Dangit. If only I had waited 2 hours more.
bsimpson1 said:
so does the switch to unlock the bootloader in the developer options not have any bearing on the rollback protection?
Click to expand...
Click to collapse
It didn't for me. After switching that enable oem unlocking to on, I still had the above mentioned issues
Surge1223 said:
Bl rollback protection
Click to expand...
Click to collapse
Is it possible that this is fundamental to all 5.1.1 builds? The same thing happened to us on the Nexus 6. There were a few whom unknowingly downgradded their bootloaders, and ended up hard bricking their devices.
Even on reboot, in developer options, the toggle for "Allow OEM Unlock" would switch to the off position. This didn't mean that the bootloader was locked, but it did mean that you had to reset it. Most rom devs have since flipped the switch on startup.
My hope is that you will soon have working recovery and root on the latest firmware, irrespective of whether you can or cannot downgrade.
Curious, can we build a new ROM that includes the @eousphoros kernel, the OF6 system.img, and modem.bin? (without including the new OF6 kernel or the new sboot.img?)
Edit: Upon further thinking, there'd be no reason to use a different kernel, just NOT include the new bootloader, right?
Aou said:
Curious, can we build a new ROM that includes the @eousphoros kernel, the OF6 system.img, and modem.bin? (without including the new OF6 kernel or the new sboot.img?)
Edit: Upon further thinking, there'd be no reason to use a different kernel, just NOT include the new bootloader, right?
Click to expand...
Click to collapse
Here's what's interesting about that....the eousphoros leaked 5.1.1 kernel is NOT seandroid enforcing, and the new bootloader recognizes that and doesn't let you boot with it.
It also recognizes the 5.0.2 kernel is another android version and it will fail during an odin flash
bajasur said:
Here's what's interesting about that....the eousphoros leaked 5.1.1 kernel is NOT seandroid enforcing, and the new bootloader recognizes that and doesn't let you boot with it.
It also recognizes the 5.0.2 kernel is another android version and it will fail during an odin flash
Click to expand...
Click to collapse
I'm talking about for those who haven't already taken the OTA or haven't Odin'ed the new one yet.
Aou said:
I'm talking about for those who haven't already taken the OTA or haven't Odin'ed the new one yet.
Click to expand...
Click to collapse
I think if you can include the leaked 5.1.1 bootloader you might be golden
bajasur said:
I think if you can include the leaked 5.1.1 bootloader you might be golden
Click to expand...
Click to collapse
Actually, I'm just going to include system.img, boot.img, cache.img and modem.bin.
anyone know wtf cm.bin is? I can't seem to find out any info on what it is or if it should be included.
Edit: well, I upgraded from the unofficial 5.1.1 to OF6, only flashing the four partitions mentioned above. It booted fine, rebuilt the dalvik cache for all my apps, and was doing OK.... except that the fingerprint reader wasn't working and LTE was also not working. Strange. So, I rebooted.... and bootloop.
So, I boot into TWRP (because I still have that!), and wiped cache/dalvik. Stilla bootloop (immediate bootloop). Dang. Wiped cache/dalvik again. Still the same.
So, I flashed the unofficial 5.1.1 via TWRP. This time, it's stuck at the first "galaxy s6 edge" screen.
So, I've re-created my odin package again. This time without cache.img, but I included cm.bin. Let's see if I just shot myself in the foot?
Edit2: Well, it's booting again, for what it's worth... at least to the Android is Starting screen again... it'll be a few minutes...
Aou said:
Actually, I'm just going to include system.img, boot.img, cache.img and modem.bin.
anyone know wtf cm.bin is? I can't seem to find out any info on what it is or if it should be included.
Edit: well, I upgraded from the unofficial 5.1.1 to OF6, only flashing the four partitions mentioned above. It booted fine, rebuilt the dalvik cache for all my apps, and was doing OK.... except that the fingerprint reader wasn't working and LTE was also not working. Strange. So, I rebooted.... and bootloop.
So, I boot into TWRP (because I still have that!), and wiped cache/dalvik. Stilla bootloop (immediate bootloop). Dang. Wiped cache/dalvik again. Still the same.
So, I flashed the unofficial 5.1.1 via TWRP. This time, it's stuck at the first "galaxy s6 edge" screen.
So, I've re-created my odin package again. This time without cache.img, but I included cm.bin. Let's see if I just shot myself in the foot?
Edit2: Well, it's booting again, for what it's worth... at least to the Android is Upgrading screen again... it'll be a few minutes...
Click to expand...
Click to collapse
I could be wrong but I believe the bootloader may be in more than just sboot.bin, @Surge1223 would know better than I.
A quick update: It booted fine, but the fingerprint reader still borked. I was thinking that the LTE wasn't going to work again (stuck on Edge), but I think I just didn't give it enough time last go-around. The LTE cam up after turning mobile data off/on again.
The phone was going very slow, not snappy at all. So I rebooted. And, this time, no bootloop! yay. The fingerprint reader is still not working, though. The speed picked up. I'm also noticing that the brightness sensor isn't working right, perhaps?
Now the next question: Can I still downgrade?
Edit: Well, so far, it's letting me Odin back to OCG stock. The "RP SWREV:" is 1 and "Kernel RP SWREV:" is also 1. Downloading...
(I've had issues using Odin-to-stock after running the unofficial 5.1.1 update, so I might not be able to boot after this...)
Edit2: Well, it worked. I'm back on OCG stock. I can't fully boot (I can only get as far as the TMobile screen), but that's a side-effect of trying to Odin back to OCG without wiping data/cache/dalvik. If I were to do that, I'd be back on OCG stock fully. For the meantime, though, I'm going to jump back on the unofficial 5.1.1 update.
Edit3: Well, for some reason I'm not able to seamlessly boot back into the unofficial 5.1.1. I was able to flash TWRP just fine and flash the 5.1.1, but I get stuck on the "galaxy s6 edge" screen on subsequent boots. Tried formatting System/cache/dalvik. Not willing to format Data yet, though.
Older kernels often don't boot on new bootloaders. This is fairly common on Samsung devices (and also very annoying). This would in fact often halt at the "kernel is not SEAndroid enforcing" line. Rolling back bootloaders to older versions also usually doesn't work.
A rebuild of TWRP or whatever custom kernel you're using may be all there is needed. I wouldn't be scared of bootloader locks just now. On the other hand, I wouldn't flash it yet either
Chainfire said:
Older kernels often don't boot on new bootloaders. This is fairly common on Samsung devices (and also very annoying). This would in fact often halt at the "kernel is not SEAndroid enforcing" line. Rolling back bootloaders to older versions also usually doesn't work.
A rebuild of TWRP or whatever custom kernel you're using may be all there is needed. I wouldn't be scared of bootloader locks just now. On the other hand, I wouldn't flash it yet either
Click to expand...
Click to collapse
Thanks for dropping in and shedding some light on this Chainfire. We all greatly appreciate it.
Hopefully this is just a minor hiccup.
The kernel revision is in the decrypted boot.img signature, and the bootloader rollback protection is in eFuse bank. I've not yet researched any Exynos devices before, but in the past they've used the RPMB (a special, protected hardware partition on the eMMC) to store their 'fuse' bits. However, with recent hardware trends, I wouldn't be surprised if they implemented a true one-time-programmable fuse bank. This is the future of Samsung.
Alright, screw it. I'm just going to flash the full OF6. Chainfire has a very valid point. We faced this same kind of crap on the T-Mobile Galaxy S5. It wasn't really a problem with locked bootloaders, it was a problem of downgrading the kernel/recovery (or trying to downgrade the bootloader itself). He's absolutely right.
Yes, there's some chance that they've added some sort of hash-checking for flashing new binaries (essentially locking the bootloader), but I'm not terribly worried. I've been using the leaked 5.1.1 update for a while now without root, and I've been "mostly" okay with it. I'm really just waiting for Chainfire to graciously invest some of his time in finding a root for the Samsung version of Android 5.1.1. I can wait.
So, here goes taking the plunge, the full OF6 and all... 3...2...1...
Chainfire said:
Older kernels often don't boot on new bootloaders. This is fairly common on Samsung devices (and also very annoying). This would in fact often halt at the "kernel is not SEAndroid enforcing" line. Rolling back bootloaders to older versions also usually doesn't work.
A rebuild of TWRP or whatever custom kernel you're using may be all there is needed. I wouldn't be scared of bootloader locks just now. On the other hand, I wouldn't flash it yet either
Click to expand...
Click to collapse
Yea I remember the downgrading bootloaders and modem issue on many other Samsung devices kit kat on up, ie s3, s5, note 3 excluding the engineered bootloader work around. But we were still ok moving forward, but I think I'll hold off on the update to see what happens now
Related
Hey guys,
I've been working on rooting the new Captivate Glide, and unfortunately my kernel flash with ODIN failed (inexplicably). Now the device is complaining I need to perform an emergency recovery, but of course the device isn't listed in the KIES panel.
Apologies if this is covered elsewhere, but I searched and didn't find anything.
Can anyone explain how KIES works? What is a recovery code? Do I need to get one from Samsung? Is there any other way to force it to perform the recovery on my semi-bricked phone?
Wrong forum ...
There isn't a forum for him yet, so this is the best he could do.
Try going to download mode and flashing again! Try again, until it works, redownload the kernel.
Sent from my SGH-I897 using xda premium
Actually, strangely enough ... I entered 3e recovery (out of desperation) and rebooted, and it cleared the flag, allowing it to boot up normally.
I checked the kernel timestamp (cat /proc/version) and it appears to still be the stock kernel, so the NAND update completely failed.
I still would like to figure out how to force a KIES recovery, but at least for the moment I'm back up and running (till I take my next shot ).
Kies is garbage, don't worry about it.
It's just like Odin only there are a retarded amount of checks to make sure it's a supported phone...which usually fail if you're on anything other than stock or your imei has changed to a generic one, or any other reason it wants to make up to fall.
To root you should be able to flash the fugu kernel, which will cause a bootloop, then flash that stock kernel again, then once that boots you should have root.
studacris said:
Kies is garbage, don't worry about it.
It's just like Odin only there are a retarded amount of checks to make sure it's a supported phone...which usually fail if you're on anything other than stock or your imei has changed to a generic one, or any other reason it wants to make up to fall.
To root you should be able to flash the fugu kernel, which will cause a bootloop, then flash that stock kernel again, then once that boots you should have root.
Click to expand...
Click to collapse
Frustrating. The n900 flashing tool was so excellent (and cross-platform). Wonder why Samsung would release such a piece of junk.
Anyway, I'm back in business now and still working on it.
I'd love to try one of the other kernels, but since I don't have any recovery path (stock kernel / image / firmware), I'm really nervous now.
Hello All,
Due to my endless frustrations, this might be a long one so please bear with me!
So I purchased a Verizon Global HTC ONE M7 from the States, I am currently in Nigeria and the only thing that makes me sadder and more frustrated than the state of my phone right now is the incessant terror attacks in the country! Initially, almost everything worked fine when i popped in my new Etisalat sim card into the phone, except for the mobile hotspot (which just conveniently turns out to be the one of the top 3 most important features in a phone for me - probably the feature I use the most) this message kept popping up about how hotspot couldn't be used without a VZW sim, etc (also with the non-verizon sim warning when the phone boots up). I tried all I could, eventually deciding to flash a new ROM to clear out everything Verizon and start fresh.
Enter Viperone 6.2.0 - everything worked initially, but after a few weeks i noticed if I did anything like watch a youtube video or download something over a few MBs 90% of the time the data drops (no visible signs like changes from E to H or 3g or the likes, everything looks the same, just that the data stops), toggle mobile data on/off and data connection is back. It worsened and became more frequent over time. Upgraded to Viperone 6.2.1, no difference, so i figured its probably the viperone rom.
Enter Cyanogenmod - http://forum.xda-developers.com/ver...-oneplus-one-stock-rom-cm11s-verizon-t2857425 - and its the same exact issue from the beginning, so im guessing its not to do with the ROM at all (though there are one or two niggling issues with the ROM - cant change BBM display pic, etc)?! I've really tried to comb through the forum and see what makes sense that i could try without bugging y'all - I did a factory reset, wiped everything completely and its the same thing.
I've seen suggestions to similar issues like: flash stock recovery, update radio/firmware/kernel, flash back to custom recovery and some other things which are beginning to sound quite dangerous in my ignorance!! I did believe updating the firmware made sense but after digging deeper, i must honestly say i'm quite confused on what to do. what radio/firmware/kernel works with what software version, etc- most firmware that i've seen are 4.4.3 compatible, while this ROM is 4.4.4., some of them seem to be for stock ROMs only and a lot of other confusions.
So, I'm not gonna be a hero and brick my phone from trying to do what i do not understand, instead here i am, hat in hand, crying out for help after suffering for 3 months! Its really frustrating as, downloads break causing me to lose data, skype or MSLync calls always break and im beginning to look unprofessional to people! This is why I have decided to put up a post of my own specific to my case so i don't medicate for someone else's ailments. So please........ WHAT EXACTLY DO I DO??
PHONE DETAILS (typing it out as i've just realized on this ROM i can't take screenshots with Power+Home button combo anymore and can't be bothered at this point!!!)
ANDROID VERSION: 4.4.4
BASEBAND VERSION: 1.12.41.1112_2
KERNEL VERSION: 3.4.82-gfe09065; [email protected] #1; Wed oct 8 01:36:03 PDT 2014
BUILD DATE: SUN AUG 3 23:00:51 PDT 2014
BUILD NUMBER: CYANOGENMOD 11S v5 (Verizon)
SELinux status: Enforcing
Thanks
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Can you flash stock recovery from Santod's firmware thread and do a factory reset? It could be a corrupt nv partition which would only be fixed by doing a factory reset via stock recovery. (If you must, make a nandroid of system and data in your recovery of choice so you can restore your data if you wish).
Uzephi said:
Can you flash stock recovery from Santod's firmware thread and do a factory reset? It could be a corrupt nv partition which would only be fixed by doing a factory reset via stock recovery. (If you must, make a nandroid of system and data in your recovery of choice so you can restore your data if you wish).
Click to expand...
Click to collapse
Thanks for the responses folks, i'll try out your suggestions and revert..
8100
brymaster5000 said:
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Click to expand...
Click to collapse
So.. i found time to get to this and decided to go with your suggestion of Santod's stock rom... and now, i think i've done the unthinkable!! After WIPING EVERYTHING "All partitions except SD!" as the instructions stated... i attempted to reboot into bootloader and got a message saying "no OS installed, are you sure you want to reboot"... that scared me a bit, but i thought surely, it must be part of the process! I proceed to reboot to bootloader to flash the firmware and i cant seem to do anything!!
Fastboot is stuck on " waiting for device" for everything i try.
Also, i rebooted back into recovery and attempted to install the stock rom: i get the error message "unable to open zip file"..
Have i destroyed my phone with my own hands, people? :crying:
Mr HaRR said:
So.. i found time to get to this and decided to go with your suggestion of Santod's stock rom... and now, i think i've done the unthinkable!! After WIPING EVERYTHING "All partitions except SD!" as the instructions stated... i attempted to reboot into bootloader and got a message saying "no OS installed, are you sure you want to reboot"... that scared me a bit, but i thought surely, it must be part of the process! I proceed to reboot to bootloader to flash the firmware and i cant seem to do anything!!
Fastboot is stuck on " waiting for device" for everything i try.
Also, i rebooted back into recovery and attempted to install the stock rom: i get the error message "unable to open zip file"..
Have i destroyed my phone with my own hands, people? :crying:
Click to expand...
Click to collapse
FALSE ALARM FOLKS!!! I decided to attempt flashing the CM11 rom i just uninstalled and it worked. Turns out its a known issue with the .zip file for that rom - i am now re-downloading from another mirror. Meanwhile the Fastboot thing was just a driver issue - though i'm surprised because i had all the drivers installed on the system and have used fastboot successfully - anyway i reinstalled the drivers and all was well with fastboot again.
NB: Don't get tired of me just yet please!
brymaster5000 said:
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Click to expand...
Click to collapse
hello!
Thanks for your ideas guys. I'm currently running Santod's stock rom (which is brilliant, i must say, i actually wanna stay on this rom) since friday - thought i'd give it the whole weekend and see how it goes.. BUT! i still get thoseconnection drops.. and frequently too.
Any other ideas on what the issue could be?
Mr HaRR said:
hello!
Thanks for your ideas guys. I'm currently running Santod's stock rom (which is brilliant, i must say, i actually wanna stay on this rom) since friday - thought i'd give it the whole weekend and see how it goes.. BUT! i still get thoseconnection drops.. and frequently too.
Any other ideas on what the issue could be?
Click to expand...
Click to collapse
If doing factory reset from stock recovery doesn't fix it, it is most likely a burned SIM. It has happened to me. (Average 150+ GB a month in data, so I burn em easily)
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uz has it right, you need to flash a stock recovery and THEN do a factory reset, then reload your custom recovery and rom. I had the exact same issue before. Or you could flash an ruu file which would reset the partitions also.
ccarr313 said:
Uz has it right, you need to flash a stock recovery and THEN do a factory reset, then reload your custom recovery and rom. I had the exact same issue before. Or you could flash an ruu file which would reset the partitions also.
Click to expand...
Click to collapse
Hey folks, apologies for the touch and go nature of this thread - i just don't have a lot of free time on my hands and other reasons..
Anyhow, i think I want to try out ur suggestion of flashing an RUU - I noticed that im unable to actually enter recovery after flashing stock recovery from Santod's thread (i flashed the latest three recoveries). I can get to bootloader, but when i select recovery, the phone goes black for a few seconds and then i get the RED TRIANGLE WITH THE EXCLAMATION MARK INSIDE, obviously something's wrong, few seconds later the phone reboots itself into normal mode. I did do a factory reset from bootloader, but issue persists.
So now to the RUU flashing issue - could you suggest one for me to flash?
By the way though, isn't flashing an ruu gonna take me back to stock completely (as in back to S-ON, ETC..)?
Thanks a whole bunch - IM DETERMINED TO GET THIS TO WORK!!!
Mr HaRR said:
Hey folks, apologies for the touch and go nature of this thread - i just don't have a lot of free time on my hands and other reasons..
Anyhow, i think I want to try out ur suggestion of flashing an RUU - I noticed that im unable to actually enter recovery after flashing stock recovery from Santod's thread (i flashed the latest three recoveries). I can get to bootloader, but when i select recovery, the phone goes black for a few seconds and then i get the RED TRIANGLE WITH THE EXCLAMATION MARK INSIDE, obviously something's wrong, few seconds later the phone reboots itself into normal mode. I did do a factory reset from bootloader, but issue persists.
So now to the RUU flashing issue - could you suggest one for me to flash?
By the way though, isn't flashing an ruu gonna take me back to stock completely (as in back to S-ON, ETC..)?
Thanks a whole bunch - IM DETERMINED TO GET THIS TO WORK!!!
Click to expand...
Click to collapse
That is in fact stock recovery man. When you get the triangle press volume up and power at the same time. You will enter stock recovery.
Any of my ruu will run fine. You won't lose s-off or unlocked status. You flash them in boot loader fastboot mode.
dottat said:
That is in fact stock recovery man. When you get the triangle press volume up and power at the same time. You will enter stock recovery.
Any of my ruu will run fine. You won't lose s-off or unlocked status. You flash them in boot loader fastboot mode.
Click to expand...
Click to collapse
HA! and now i feel :silly: !!
Bless your soul! i'll give it a go shortly...
I want to secure my phone from the recently discovered StageFright Android hack.
I want to remove the component/package that this bug is linked to.
I am running AT&T Rooted Stock (minus bloatware) 4.4.2 Baseband: I747UCUFNE4.
I want to remove the offending package with titanium backup until an Update can be issued.
Can someone let me know what package I need to remove?
You will be better off waiting for a xposed patch, stagefright (if you have been paying attention) is the media processor in android so if you take it out you loose most media playback
Sent from my Nexus 7 2013 using Tapatalk
crazymonkey05 said:
You will be better off waiting for a xposed patch, stagefright (if you have been paying attention) is the media processor in android so if you take it out you loose most media playback
Sent from my Nexus 7 2013 using Tapatalk
Click to expand...
Click to collapse
AT&T is never going to release an patch for my Device.
mrnapolean1 said:
AT&T is never going to release an patch for my Device.
Click to expand...
Click to collapse
No they're not, but CM apparently has stagefright patched.
Maybe it is time to give a custom ROM a shot. :good:
jason2678 said:
No they're not, but CM apparently has stagefright patched.
Maybe it is time to give a custom ROM a shot. :good:
Click to expand...
Click to collapse
I have CM on my Captivate up until my screen took a ****.
Do you know any good tutorials for installing CM on the SIII?
mrnapolean1 said:
I have CM on my Captivate up until my screen took a ****.
Do you know any good tutorials for installing CM on the SIII?
Click to expand...
Click to collapse
There are some guides linked to these forums, but the ones I know of are pretty old and out of date. Samsung pushed Knox with the newer firmware updates, and that really changed how we have to handle this phone. The information you're after has been written all over this forum by many members, myself included, but I can't seem to find a decent post to link to right now. The problem is there is a lot of information, it is all fragmented across thousands of posts, hard to search (hard to find what you're after anyway), and some of the old information can be a little dangerous with the newer bootloaders.
The key to not bricking this phone is to know what bootloader and modem you're on and never, ever try to downgrade it (if you're on a newer one). First thing to do is install the Samsung phone info app from the play store and check your bootloader and baseband. Alternately enter this in a terminal:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
If your bootloader ends in MJB, NE4, or NJ1 don't ever try to downgrade it. The result is a hard brick that is very difficult to recovery from. That means never Odin back to stock if you're on MJB, NE4, or NJ1. The only stock Odin package AT&T allowed to be released is the "ancient", new bootloader bricking LK3 Android 4.1.1 firmware.
If your bootloader or modem end in NE4 or NJ1 you're good to go. You can flash any newer ROM you want. If you're on MJB you're probably ok too. If you're on anything else your mobile data probably won't work with CM 12.1. You'll have to look into updating.
Another good thing to know is that the i747/d2att bootloaders are not locked and have never been locked. Do not attempt to unlock them. Any GS3 bootloader unlock procedure you come across is probably for the Verizon variant, and if you try it on a d2att you'll likely have a hard brick.
Also be aware that the i9300 was marketed as Galaxy S3 as well, but it is a totally different device on the inside. Never flash an i9300 ROM on a d2att phone.
Once you've verified what bootloader/modem you're on, and that it is good to go with CM 12.1, these are the basic steps I'd take if starting with an unmodded phone:
1) Download a SuperSU TWRP flashable zip and store it somewhere on your phone.
2) Use Odin to flash the latest version of TWRP for d2att. Uncheck everything but f.reset time so the phone doesn't auto reboot. Upon success pull battery.
3) Replace battery. Boot straight into recovery by holding vol up + home + power until you see some tiny blue text in the upper left then releasing. If you mess up and accidentally boot into your stock ROM your custom recovery will likely get overwritten with stock and you'll have to repeat step 2 and try again.
4) Flash SuperSU in TWRP.
5) Reboot to stock ROM. Use play store to update your SuperSU binary. You'll probably have to reboot once or twice, but eventually you'll get working root and Knox disabled.
6) In stock ROM open a terminal and enter:
Code:
su
reboot nvbackup
Your phone will reboot. It will seem like a pretty normal reboot, but you'll see some quick flashes of blue text in the upper left if your looking for it. This fixes a Samsung derp and makes sure you have a working EFS backup. This was the only reason we rooted your stock ROM; sorry about all that work just to do this but if your phone ever panics from a bad flash and triggers its autorestore function you'll be happy you did it.
7) Download ROM for d2att and matching gapps. Store them on external SD if you have one. Otherwise verify you can copy files from PC to phone via USB when your phone is booted into TWRP. With TWRP up an running you should just have to plug it in and phone will be recognized by PC as a media device you can transfer files to.
8) Reboot to recovery. Make a backup in TWRP. Store copies on external SD and somewhere off phone for safekeeping. In fact, always keep a nandroid backup or two, a ROM you know works, and a gapps package on an external SD - just in case.
9) Do wipe -> advanced wipe. Tick dalvik, cache, system, and data.
10) Do wipe -> format data. This is why your new ROM and gapps need to be on external SD. Otherwise you'll have a blank phone and you'll have to copy something over via usb or push it via adb to have something to flash. You don't need to do this every time you flash a ROM, but you do need to do it when switching from touchwiz to AOSP and vice versa.
11) Flash ROM
12) Flash gapps
13) Reboot - be patient. 1st boot might take 10 - 15 minutes on a lollipop ROM with this phone.
14) Profit
This probably isn't detailed enough to use as a walkthrough. It will give you an idea what to search and do more research and reading on, and I think I flagged most of the hard bricking pitfalls owners of this phone run into.. Make sure you understand the whole procedure before proceeding. Wouldn't want you to brick your phone trying to deal with a potential vulnerability there's a remote chance you might be targeted with.
Good luck. I made it sound a little scary, but as long as it is handled properly this phone is a flashing beast. If I haven't flashed mine dozens of times, then its in the hundreds. Never had anything go so wrong to the point that I could boot up into recovery and restore or flash my way out of it.
I have NE4 bootloaders
mrnapolean1 said:
AT&T is never going to release an patch for my Device.
Click to expand...
Click to collapse
I never said att, I meant Xposed framework. People release security patches on their all the time
Sent from my Nexus 7 2013 using Tapatalk
Hello Everyone,
I've been up literally all night (I know, that old line) trying to fix what happened. I bought this phone last year. It was unlocked and rooted. I never updated because it was never giving me issues. But the lagging and battery has finally got to me. So I decided to upgrade to this new rom(http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-0-t3094423).
It looked clean and minimal bloat, just the way I like it. However, I didn't get past updating the Bootloader. As soon as I did in Odin it went into a bootloop. Try as I might I couldn't get into recovery. Luckily I can still get into download mode. So I read up and found that I should flash the original firmware. Unfortunately it failed because I tried to upload an older version. Is there anyway I can flash this rom via odin? Sorry for the noobish questions here but it's past 8am and I've just about given up. If I see recovery is not seandroid enforcing or rev check fail s6 device 3 binary 2 I'm going to lose my mind lol. I did have TWRP installed if that makes a difference. Just can't access it. Any help would be greatly appreciated. Thanks guys
P.S. I know I used buy instead of buy but can't fix it. It was really early in the morning haha
Ok I managed to download the stock MM version for my phone. I still have bootloop issues but I'm in recovery mode at least. However not TWRP though, if I try downloading a custom recovery it says the dreaded "recovery is not seandroid enforcing" also it says Device does not have DRK. Any guesses here?
Well, I've just about given up. I've searched extensively and it appears that the fix is to download a different kernel. However, the G925T has no support yet for any custom MM kernels. I made a backup of my phone via TWRP before this whole mess but the problem is I can't get to it. And to be honest I'm not entirely sure if it's still there. Here are the steps I have taken thus far.
1. Downloaded MM Bootloader: this was the start of my issues. Started bootloop, couldn't get into recovery.
2: Attempted to download original LP firmware: Odin denied it, there was another version I download from zidroid called "downgradeable". Obviously did nothing because I was still running MM bootloader and was effectively the same thing.
3. Downloaded stock MM firmware: Finally was able to boot into recovery but it was useless as it was the stock one. Also wouldn't boot up due to "Device does not have DRK" and boots straight into download mode. Tried to download recovery but none of them worked. Kicked me back to "Recovery not Seandroid enforcing".
So this is where I'm at, I just want to get back to my old device I honestly would rather have a clunky phone than one that doesn't work at all. Is it possible to downgrade back to LP and get back into TWRP and flash my backup? Do I still have root after taking all those steps? Any help would be greatly appreciated because this has officially ruined my weekend?
I guess I'm talking to myself here but if anyone ever encounters this issue at least it will be documented if I ever do fix it.
I managed to get into TWRP. Although arter doesn't have a kernel that supports our system yet. The twrp recovery he has does, ours is compatible with the fi variant. Again that's only the recovery no the kernel.
So I was at a cross roads, do I restore my backup or do I continue with the download. Unfortunately none of those options worked. When restoring the backup I get stuck on the samsung page with "kernel not enforcing" or whatever. Do be fair, before I did this with my device it had already said that. So I gave it some time, but alas no luck. And the same issue with the when I tried to continue the download. I'm a little lost as to how to continue now. I just want my device back.
try dd the mm firmware
Nickle60 said:
I guess I'm talking to myself here but if anyone ever encounters this issue at least it will be documented if I ever do fix it.
I managed to get into TWRP. Although arter doesn't have a kernel that supports our system yet. The twrp recovery he has does, ours is compatible with the fi variant. Again that's only the recovery no the kernel.
So I was at a cross roads, do I restore my backup or do I continue with the download. Unfortunately none of those options worked. When restoring the backup I get stuck on the samsung page with "kernel not enforcing" or whatever. Do be fair, before I did this with my device it had already said that. So I gave it some time, but alas no luck. And the same issue with the when I tried to continue the download. I'm a little lost as to how to continue now. I just want my device back.
Click to expand...
Click to collapse
Not sure what state your phone is in. To begin with, the not Seandroid message with recovery is normal, if you are on marshamallo. If you are on LP then you get the same with the Kernel message when it boots up. BOTH are normal depending on which Firmware you are on. But that said you shouldn't be trying to downgrade, if that's even possible. Have you tried smartswitch and the emergency software restore function. It will wipe out everything on your phone but at least will boot up with the latest MM. Then simply Odin the arter TWRP and then install XTRESTOL which I am using NO PROBLEMS on my TMobile 925T variant. NOT sure about the DRK root key problem. But when you install stock MM with smartswitch you should have also gone into settings and enable developer settings to make sure OEM unlock was enabled before doing anything else.
Lastly, the Arterkernel will actually work fine as far as booting up. The ONLY issue is call audio which we all are waiting for a patch, or a kernel that supports everything. But, I have TWRP installed that arter kernel, and the phone boots up just fine. You just do NOT have call audio. My suggestion at this point is smartswitch. Just know your serial number so that when asked you can plug that in to the menus smartswitch goes thru before wiping and restoring current MM latest and greatest.
Docmjldds said:
Not sure what state your phone is in. To begin with, the not Seandroid message with recovery is normal, if you are on marshamallo. If you are on LP then you get the same with the Kernel message when it boots up. BOTH are normal depending on which Firmware you are on. But that said you shouldn't be trying to downgrade, if that's even possible. Have you tried smartswitch and the emergency software restore function. It will wipe out everything on your phone but at least will boot up with the latest MM. Then simply Odin the arter TWRP and then install XTRESTOL which I am using NO PROBLEMS on my TMobile 925T variant. NOT sure about the DRK root key problem. But when you install stock MM with smartswitch you should have also gone into settings and enable developer settings to make sure OEM unlock was enabled before doing anything else.
Lastly, the Arterkernel will actually work fine as far as booting up. The ONLY issue is call audio which we all are waiting for a patch, or a kernel that supports everything. But, I have TWRP installed that arter kernel, and the phone boots up just fine. You just do NOT have call audio. My suggestion at this point is smartswitch. Just know your serial number so that when asked you can plug that in to the menus smartswitch goes thru before wiping and restoring current MM latest and greatest.
Click to expand...
Click to collapse
Thanks for the reply, I don't have the box for the phone and couldn't boot it up so that was a no go. But luckily for me I decided to give that rom one more go. I flashed bootloader and modem again, then flashed TWRP, and finally installed the rom. And boom! It worked, and it's better and faster than ever. I'm not sure what all that other mess was but I am going to say I have everything I need at the moment and won't be flashing anything anytime soon. I've learned a great deal through this process though. Thanks for everyone's help.
So, I've tried booting (fastboot boot twrp***.img) all 3 alternate TWRP versions found on XDA for my Z2 Play. On all 3 versions, the TWRP logo comes up and the phone immediately freezes. I've waited over 5 minutes on each and it's definitely frozen up. My goal is to make a full backup, then flash 64-bit TWRP and unofficial LOS 15.1 builds with Moto mod support.
I want to be able to make a full backup of my stock recovery before permanently flashing TWRP so I can, in theory, fully return to stock if something goes wrong or I'm not happy with the LOS ROM. From the many threads I've browsed, it appears TWRP may have some limited write permissions while only temporarily booted vs permanently flashed, but should still boot and provide enough access to make a backup on internal storage. I'd imagine I could just flash TWRP and it would work. But I'd really like the peace of mind of having a backup of stock recovery prior to flashing.
I have also seen some stock firmware posted. Could I just flash back to stock using that? I'm on the latest build and security patch, NPSS26.118-24-29 with Feb. 1, 2018 security patch.
Thanks for any help! I've done plenty of flashing ROM's, but the Z2 Play is a little more complex with DM Verity and forced encryption, along with much more limited dev support than other models I've flashed.
I suppose before somebody has to ask... The bootloader is unlocked. It does say "Bad Key" on the warning screen upon boot. Is that normal?
DeadEye J said:
I suppose before somebody has to ask... The bootloader is unlocked. It does say "Bad Key" on the warning screen upon boot. Is that normal?
Click to expand...
Click to collapse
I can only say, if you have not tripped DM verify, it would not say 'Bad key'.
I personally backup the whole thing except recovery on mine. I believe that should be enough. I had to reset once with the original firmware people posted here, and also with my backup, it worked fine.
But for your information, my phone was not on Feb update but the previous one, so I don't know if the new one breaks stuffs. Maybe someone with more experience here has the answer.