Database Users

Upgrading from 4.4.2 with an unlocked bootloader (mdk)

I know there threads that cover some of my questions, but I want to make sure I have everything squared away before I go down path.
I currently have a Verizon Galaxy S4 with 4.4.2. It is rooted and has the MDK boot loader. I want to upgrade to 4.5 and use Magisk (mainly so my son can keep playing Pokemon). I am under the impression that to run Magisk I need a non rooted version of 4.5. Am I correct in this impression? Would a stock 4.5 that is Deodexed work with Magisk? Once I find one I can just flash with TWRP and then install magisk correct?
I have 3 main concerns
Don't want to lose the unlocked bootloader.
Don't want to have to wipe the phone.
Want to make sure I can still remove the OTA update app.

jed.padilla said:
I know there threads that cover some of my questions, but I want to make sure I have everything squared away before I go down path.
I currently have a Verizon Galaxy S4 with 4.4.2. It is rooted and has the MDK boot loader. I want to upgrade to 4.5 and use Magisk (mainly so my son can keep playing Pokemon). I am under the impression that to run Magisk I need a non rooted version of 4.5. Am I correct in this impression? Would a stock 4.5 that is Deodexed work with Magisk? Once I find one I can just flash with TWRP and then install magisk correct?
I have 3 main concerns
Don't want to lose the unlocked bootloader.
Don't want to have to wipe the phone.
Want to make sure I can still remove the OTA update app.
Click to expand...
Click to collapse
Well, first of all, there is no android 4.5 as far as I know.
There is 4.4 and then it jumps to 5.0.
Second, your device does not have an unlocked bootloader. Verizon phones pretty much all have a locked bootloader, and no way to unlock them.
Updating to the latest Android might make rooting impossible.
And since your bootloader is locked, Magisk won't work.

GDReaper said:
Well, first of all, there is no android 4.5 as far as I know.
There is 4.4 and then it jumps to 5.0.
Second, your device does not have an unlocked bootloader. Verizon phones pretty much all have a locked bootloader, and no way to unlock them.
Updating to the latest Android might make rooting impossible.
And since your bootloader is locked, Magisk won't work.
Click to expand...
Click to collapse
I was under the impression that MDK was the only unlocked bootloader Verizon ever had. It was only on the first round of phones.

jed.padilla said:
I was under the impression that MDK was the only unlocked bootloader Verizon ever had. It was only on the first round of phones.
Click to expand...
Click to collapse
I'm pretty sure it is locked. It's just easier exploitable.
But I may be wrong.
Edit: Apparently only the Developer Edition has the unlocked bootloader. The MDK is locked.

GDReaper said:
I'm pretty sure it is locked. It's just easier exploitable.
But I may be wrong.
Edit: Apparently only the Developer Edition has the unlocked bootloader. The MDK is locked.
Click to expand...
Click to collapse
So at this point my options are update the phone to something else with no root so I can continue to play.
Leave my phone rooted and no longer play.

jed.padilla said:
So at this point my options are update the phone to something else with no root so I can continue to play.
Leave my phone rooted and no longer play.
Click to expand...
Click to collapse
There was a way to "hide root", other than Magisk.
But it's a real pain. You'd have to go into recovery and type some terminal commands each time you want to hide root, and then go back into recovery and undo everything once you want to get root back.

GDReaper said:
There was a way to "hide root", other than Magisk.
But it's a real pain. You'd have to go into recovery and type some terminal commands each time you want to hide root, and then go back into recovery and undo everything once you want to get root back.
Click to expand...
Click to collapse
Well that is a big fat meh then. Thanks for the help.

[ZE552KL] I cannot unlock my bootloader.

I've been reading numerous threads in this forum in regards to rooting but I cannot unlock the bootloader.
Been trying to follow snowwolf's unofficial method to the letter but to no avail. Tried both .bat and manually doing fastboot .raw. https://forum.xda-developers.com/showpost.php?p=69001601&postcount=2.
Currently at the latest update as of today and have NOT rooted or unlocked bootloader prior to this.
USB debugging is also set to on.
I have uploaded screenshots of the error messages and information of the phone.
https://imgur.com/a/XPSDP
Any suggestions/opinions are welcome.

It's possible the unofficial unlock method was blocked in the newer firmware (bootloader) that you have installed. Try flashing the Marshmallow firmware, but you'll probably need to remove the checks in the updater script (first 7 lines or so). I'm not sure it'll work though, but worth a shot. If you can't downgrade though, then the only option is to use the official unlock method.

Yep, that seems to be the case. The official unlock method still works on the latest one and successfully rooted. Thank you for your help.

Sorry for the foolish question but what is the proper way to do a total clean "hard" reset to the latest version when its rooted? Just been messing with a lot of things and wanted to start anew since I'm relatively new to android from iOS.

droidoogle said:
Sorry for the foolish question but what is the proper way to do a total clean "hard" reset to the latest version when its rooted? Just been messing with a lot of things and wanted to start anew since I'm relatively new to android from iOS.
Click to expand...
Click to collapse
Factory reset through settings or in recovery mode

droidoogle said:
Yep, that seems to be the case. The official unlock method still works on the latest one and successfully rooted. Thank you for your help.
Click to expand...
Click to collapse
Will this work on version WW_14.2020.1703.28_20170410? Latest version of nougat. Even if its for marshmallow only? Thanks

no oem unlock area in the dev tab

hello all,
im currently working on a samsung S4 (GT-I9515) and i ran into a small problem.
i have rooted phones more then ones and i know the drill more or less.
but when i tried to sellect the unlock oem option in the dev options it was not there.
normally it is located under bluetooth HCI-snooplog and above Process stats but the oem unlock option seems to be non existing on this phone
can someone tell me whats wrong or is it not needed ? Because i did get a message when i tried to install something trough the default recovery menu that the system was still locked. (also it runs android 5.0.1(lolipop))
Best regards,
Darkdevel

You can't install anything unsigned with the stock recovery. No phone gives you such privileges. That's why people made custom recoveries.

Pwnycorn said:
You can't install anything unsigned with the stock recovery. No phone gives you such privileges. That's why people made custom recoveries.
Click to expand...
Click to collapse
true i also tried using twrp but when in boot twrp i cant swipe/select anything of the first screen do you have another idea what i can use ?

What are you trying to unlock with "unlock OEM option"?

audit13 said:
What are you trying to unlock with "unlock OEM option"?
Click to expand...
Click to collapse
well as far as i know i need it so i can try to flash a new android version on it im trying force 6.0 on it and yes i know there is no S4 (i9515) android 6.0 version but i still want to try and do it its a old phone anyway

ppl you can forget about this post i found the problem more or less first off i had the wrong twrp version that caused the bug on twrp afterward it was all smooth sailing
for all the other ppl who want a non official android 6.0
go to youtube and look for:
install Android 6.0.1 Marshmallow Galaxy S4 GT-I9515
posted by ما لا تعلم ?
all the files you need are in the discription
Best regards,
Darkdevel

Pwnycorn said:
You can't install anything unsigned with the stock recovery. No phone gives you such privileges. That's why people made custom recoveries.
Click to expand...
Click to collapse
But you can't install a CR without OEM unlocked.
I am having the same problem right now (same device, gt-i9515), no OEM unlock option in developer options.
I kinda need it to install TWRP, it won't let me do it otherwise. I openned a new thread about it and explained the issue I have in more details.

FurySh0ck said:
But you can't install a CR without OEM unlocked.
I am having the same problem right now (same device, gt-i9515), no OEM unlock option in developer options.
I kinda need it to install TWRP, it won't let me do it otherwise. I openned a new thread about it and explained the issue I have in more details.
Click to expand...
Click to collapse
Dude, all S4 models, except for the Verizon and AT&T models, have an UNLOCKED BOOTLOADER.
An OEM Unlock option is, therefore, redundant because there is absolutely nothing to unlock. And the ones that do have a locked bootloader CAN'T BE UNLOCKED.
If you want TWRP follow a guide on how to install it. They even have one on the TWRP website and nowhere does it say that you need to OEM unlock. In fact, no S4 rooting/twrp flashing guide will mention any OEM unlock option.
If it does, it's garbage.

Pwnycorn said:
Dude, all S4 models, except for the Verizon and AT&T models, have an UNLOCKED BOOTLOADER.
An OEM Unlock option is, therefore, redundant because there is absolutely nothing to unlock. And the ones that do have a locked bootloader CAN'T BE UNLOCKED.
If you want TWRP follow a guide on how to install it. They even have one on the TWRP website and nowhere does it say that you need to OEM unlock. In fact, no S4 rooting/twrp flashing guide will mention any OEM unlock option.
If it does, it's garbage.
Click to expand...
Click to collapse
It's very strange then. When I had a root (same device gt-i9515 for SURE), I managed to flash TWRP on my first try, no mistakes.
I recently flashed a firmware (from sammobile. I9515XXU1BOE3_I9515DBT1BOE1_DBT, because my PDA is i9515xxu1boe3) and wiped everything. It's like a new device now.
In it's current state (non-root) I couldn't install TWRP via the same method I did before (ODIN + TWRP.tar).
About the comment on the other thread, yes, I am sure it's gt-i9515 and I know that if the USB is getting disconnected, ODIN writes it on screen, so I could see it.
Here's the guide that told me about OEM: http://www.theandroidsoul.com/how-to...ry-using-odin/ (I understand that it's a trash guide lol)
Update:
I finally did it, explained here: https://forum.xda-developers.com/ga...p-cr-galaxy-s4-gt-i9515-t3668461#post73680660
Thanks for your help!

Shortcut to being rooted on N910VVRU2CQI2

Here's my Cheat Sheet ! This is the same procedure I used a while back with N910VVRU2CPD1 . I just updated the thread to work with the newer package.
1. Odin SamMobile N910VVRU2BPA1
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CQI2
( ! System and Cache only ! )
Your mileage may vary.
Before I install my personal apps I remove as much Verizon, Samsung and Google spyware as possible.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting and unlocking of 5.1.1 and make the jump I described.
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
Hyperlinks are in the text to most of what's needed.
Credit AstonsAndroid I found it HERE

I keep seeing people saying there is a way to just flash TWRP and Magisk and you're done. I'd like to avoid SuperSU and the other root methods if possible. How would that work with your updated guide? Thanks

My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839

RootMyNote4Please said:
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
Click to expand...
Click to collapse
I'm not sure if it was spyware or what. but my phone performance better after cleaning out that folder.

Thanks doc. Is that a folder that gets overwritten when you flash a new room?

This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?

lodilovesmuffins said:
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
Click to expand...
Click to collapse
Kingroot needs to connected to root. I never seen it work without a connection. N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar brakes wifi but you get it back with N910VVRU2CPD1_StockRestore.tar, I dont know why. It just works

RootMyNote4Please said:
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
Click to expand...
Click to collapse
My best guess now is it's some kind of provisioning issue that is cleaned up. Some of the files deleted you may actually need some day.

does this require the developer version? btw how do i backup

I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.

RootMyNote4Please said:
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
Click to expand...
Click to collapse
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.

kevintm78 said:
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
Click to expand...
Click to collapse
That's weird. I flashed SuperSU but it didn't show up in the apps and when I tried to use Flashfire it said I didn't have root.

Got there. SuperSU had an error message when I tried to install it the 1st time after flashing full system. So I rebooted and installed again. Now Flashfire crashes and won't open. Switched to Flashify and it seems to work ok.
Edit - Stuck here for now. Flashify can't seem to find the CQI2 file and I still haven't been able to get Flashfire to work. Tried an older version and still crashes when it checks to see if I have the pro version or not.

In case someone else has the same problem with Flashfire, it's because the program expired April 1st, 2018. Turn the date back on your phone and it will load.

Finally completed it!!!
Ok, so the things I learned from my trials and errors.
1) DON'T flash the kernal and SU after you root with the N4 fix. I did this the 1st 15 times and could never get Flashfire to work later on. So skip all of the stuff in that post after you flash TWRP. Then flash the next firmware step.
2) Uncheck auto time and date on your phone and roll it back to before 4/1/18 to get Flashfire to work.
I'm sure there are some more things and I'll add whatever else I think can help the next guy along. Good luck! And thanks for the guide doc!
Note: Did the phone icon on your lock screen disappear as well when you were done? The camera is there on the bottom right like normal, but the phone is gone on the bottom left and it displays the charging info there now.

Thanks for this - it was helpful to make clear that in my mind that despite what other guides say, there is no need to unlock a Lollipop bootloader with a Lollipop kernel + ROM first, and that we can boot a Lollipop kernel + ROM with a Marshmallow bootchain and unlock the Marshmallow bootloader from the get-go.
I tracked down the CQI2 full Odin and I made hybrid Odins that get you "rooted on N910VVRU2CQI2" in fewer steps, following hsbadr's file naming scheme:
N910VVRU2BPA1_N910VVRU2CQI2_FullFirmware.tar.md5: MM CQI2 bootchain/firmware/modem, LL BPA1 ROM/kernel/recovery
N910VVRU2CQI2_StockRestore.tar: MM CQI2 ROM/kernel (no recovery - TWRP isn't overwritten)
These should be fine as drop-in replacements for the files mentioned in steps 2 and 5 of your guide.
Using these obviously means that you are unlocking the CQI2 aboot instead of the CPD1 aboot in step 3 while temprooted, and - importantly - step 7 is unnecessary to get to a CQI2 ROM, which is good because Flashfire is now expired :3
I doubt there's much of a real benefit to being on the newer aboot, but hey, why not.

Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?

lodilovesmuffins said:
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
Click to expand...
Click to collapse
No, this will work with both versions of the verizon note 4.

kevintm78 said:
No, this will work with both versions of the verizon note 4.
Click to expand...
Click to collapse
Ok, thank you very much. I'll try and root my phone with this tutorial now.

Please help!!!!
I followed this link because its supposed to be a way to downgrade from 6.1.0 to 5.1.1 so I can unlock boot loader. However, these instructions make no sense to me. Can someone PLEASE help me. I've been searching and searching for a way to root my note 4 (N910VVRS2CQA1) and can't seem to find a way. I've never done this before so I'm pretty clueless. When I read these instructions, I just don't understand what I'm supposed to be doing. A lot of this tech lingo means nothing to me unfortunately. I'm starting to thing I should just give up the idea of rooting this Note 4 that's getting slower and slower and just get a new one. I don't really want to though bc I love the fact that you can replace the battery. It'd be much easier to just root and upgrade.....well, easier if I actually knew how.

Only official released binaries are allowed to be flashed: What causes this?

Hi!
I just rooted my S8 today for the first time and within 5 mins I got this: Only official released binaries are allowed to be flashed
I know what I did but not why it happened.
Installed:
TWRP
RMM State Bypass
Magisk
Samsung Antiroot removal
Cause:
I open Magisk - Accepted the prompts to update and followed whatever it asked - about 3 options if I recall.
Then it said reboot; then boom! Only official released binaries are allowed to be flashed.
Cant remember what it was but it was the third prompt - first was magisk manager v (****whatever), second I think was similar to magisk manager, third... cant remember but it had a pop up asking how to flash and I hit the "recommended" option.
Then I spent hours trying to fix it Got it after 6 beers and a few hours of screwing around.
But what causes this?
Ive been seeing a lot of XDA threads showing it can happen by a random reboot?? Is this a common thing?
I rooted after using it since launch with no issue so now I'm a little worried about trying to use the S8 rooted if this is something that can happen.
I want to play with xposed and magisk but this reboot hell is a little scary.
I have got it up and running again today - Had to spoof the date to get OEM Unlock to reshow up :good:
Rooted and on Aug 1 security update.
Is there something I should NOT do to avoid this error? I got it within 5 mins because I accepted the update promps then it flashed and reboot.

Damn... Rebooted and same error. Terrible
I think its tied to Knox... Restore and going back to stock

I believe Knox and RMM state are two different security features. The RMM state is for bootloader unlocking control.
I would say the RMM bypass zip didn't work did you allow twrp to make system modifications before flashing.
Also there is a ver 2 rmm state bypass

kingoddball said:
Damn... Rebooted and same error. Terrible
I think its tied to Knox... Restore and going back to stock
Click to expand...
Click to collapse
I've only ever seen this happen when OEM unlock is disabled, then rebooted. That will for sure cause this. But if your OEM unlock was definitely enabled then it's very strange. Aslong as you followed the steps exactly then you should be fine. Did you flash twrp, then format, then after format, copy rmm state fix zip to sd then flash? Other than I see no reason why it's happening

callumbr1 said:
I've only ever seen this happen when OEM unlock is disabled, then rebooted. That will for sure cause this. But if your OEM unlock was definitely enabled then it's very strange. Aslong as you followed the steps exactly then you should be fine. Did you flash twrp, then format, then after format, copy rmm state fix zip to sd then flash? Other than I see no reason why it's happening
Click to expand...
Click to collapse
Yes sir, I was unlocked, did the format and then installed the files.
It is a little odd. Potentially RMM v2 noted above could be the difference but unsure. Not really wanting to try again for a 3rd time
We'll see how bored I get on the weekend, maybe try again.

spawnlives said:
I believe Knox and RMM state are two different security features. The RMM state is for bootloader unlocking control.
I would say the RMM bypass zip didn't work did you allow twrp to make system modifications before flashing.
Also there is a ver 2 rmm state bypass
Click to expand...
Click to collapse
I dont know if I allowed it - I think I left it read only as it's what the instructions said to do. But it flashed magisk correctly so unsure.
Edit: Is there an XDA guide for rooting the S8? I used one from youtube which not have been the best?

kingoddball said:
I dont know if I allowed it - I think I left it read only as it's what the instructions said to do. But it flashed magisk correctly so unsure.
Edit: Is there an XDA guide for rooting the S8? I used one from youtube which not have been the best?
Click to expand...
Click to collapse
There are a few guides for this but try this guide as it incorporates everything in one :.ie installing twrp,rooting,OEM fix and data mount fix for twrp.
This would be better than giving you 3 or 4 seperate threads to look through. With twrp use latest version 3.2.3.0.
Read through the guide and comments just to make sure it suits your needs
https://forum.xda-developers.com/ga...ment/fix-data-mount-fix-s8-twrp-oreo-t3769254

kingoddball said:
I dont know if I allowed it - I think I left it read only as it's what the instructions said to do. But it flashed magisk correctly so unsure.
Edit: Is there an XDA guide for rooting the S8? I used one from youtube which not have been the best?
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
When installing twrp, swipe to allow modifications

callumbr1 said:
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
When installing twrp, swipe to allow modifications
Click to expand...
Click to collapse
Ok... So... I did what that page said, tried out the new file as noted, allowed modifications and... Boom - first reboot red error.
I'm trying to flash back to stock but now I'm trying to fix this: <ID:0/010> Complete(Write) operation failed.
I'll get this flashed back today and leave it there.
NOT sure if this is a consideration but I am on the September 2018 security update.
DOA: Phone is in a dead loop. Cant flash.
galaxy s8 check fail (boot loader) device 4 binary 3
If I skip the BL file I get some other crap errors. What the hell.
Smart Switch wont recognise the phone. says not unrecognised.
FINALLY FOUND A V4 bootloader image!
G955FXXU4CRI5
http://samsung-updates.com/device/?id=SM-G955F
Damn this phone is a *****!

kingoddball said:
Ok... So... I did what that page said, tried out the new file as noted, allowed modifications and... Boom - first reboot red error.
I'm trying to flash back to stock but now I'm trying to fix this: <ID:0/010> Complete(Write) operation failed.
I'll get this flashed back today and leave it there.
NOT sure if this is a consideration but I am on the September 2018 security update.
DOA: Phone is in a dead loop. Cant flash.
galaxy s8 check fail (boot loader) device 4 binary 3
If I skip the BL file I get some other crap errors. What the hell.
Smart Switch wont recognise the phone. says not unrecognised.
FINALLY FOUND A V4 bootloader image!
G955FXXU4CRI5
http://samsung-updates.com/device/?id=SM-G955F
Damn this phone is a *****!
Click to expand...
Click to collapse
Ok so what error did you get
The device 4 binary 3 error in Odin means you are flashing older firmware than what is on your phone
Software updates seem to make things harder
If still interested have a look at this thread below l think this is based on latest update (your firmware version).
https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-root-galaxy-s8-crgh-rom-t3846009