Apologies if this has been covered anywhere; I couldn't find it. When the bootloader on the Mediapad is unlocked a 'warning: bootloader unlocked" screen appears on boot. Is it possible to remove/hide/replace this warning while also keeping the tablet rooted?
Sorry mate, this is not possible. Similar to Samsung boot message when knox is tripped.
Regards
On the Moto X Style a flashing a new boot.img with it removed fixed the problem, I don't know if there is anything similar?
For now we have no sources to make a boot.img for M3.
Well... damn, didn't greatslon provide a boot.img? Although I think it was a complete custom make rather than an adaptation of stock.
Cheers anyways; hopefully a solution will appear in the future.
Will relocking it keep the root?
Ok so I am just going to say I am a idiot and need some help. Please don't hate on me. I am not good with phone technology, but I followed directions to root my phone with TWRP & Magisk 12.0 and everything is working ok for the most part. The problem is I need a specific app to work for my job, but it fails to start due to the failed Safety Net. I would probably be able to figure out how to unroot it & relock the bootloader, but in my haste to root my phone, I did not backup the stock ROM image 1st. If anyone can help me figure out the next step to go back to a factory phone, I would forever be indebted to you. My specific model is an XT-1681 dual sim which I believe is from Brazil. I am in the US and not sure if I can use a different stock rom because I have tried searching to no avail. Please help if you can.
Thanks for your time.
There's a flash file for magisk which allows it to pass safety net. I saw it in the Lineage thread a few days back, but I don't know the exact origin.
Secondly, you can't relock the bootloader anyways. I don't know for sure if that in itself would cause safety net issues.
Karlinski said:
There's a flash file for magisk which allows it to pass safety net. I saw it in the Lineage thread a few days back, but I don't know the exact origin.
Secondly, you can't relock the bootloader anyways. I don't know for sure if that in itself would cause safety net issues.
Click to expand...
Click to collapse
I appreciate the response, but I was able to finally locate the stock rom from a site linked on here & flashed and relocked the bootloader using ADB. Basically my phone is stock again & working like I need it to. I tried hiding the app in Magisk, but was unsuccessful. So I guess this post can be locked.
ronefx said:
I appreciate the response, but I was able to finally locate the stock rom from a site linked on here & flashed and relocked the bootloader using ADB. Basically my phone is stock again & working like I need it to. I tried hiding the app in Magisk, but was unsuccessful. So I guess this post can be locked.
Click to expand...
Click to collapse
Which phone version you have retin?
Sent from my Moto G (5) Plus using Tapatalk
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.
I want to remove 'Unlocked bootloader warning' which displays whenever I power on my phone(zenfone max pro m1 4gb). In one of my previous phone I overcome this problem by flashing logo.bin file. So, can this bootloader Unlocked warning be removed by flashing original splash partition?If yes, please provide the twrp flashable file or suggest some other method to do so.
+1
Yes we need it. I also had this on my moto x pure
i +1 this
the startup time is significantly increased by this
Same problem here..that warning kinda annoying.
up
we need it
Agree with you guys man. Wish we could do something about it!
Change the splash.img or something.
Relocking bootloader
Hello, I tried to root my lenovo k8 note twice but i was not successful to do so. Later, i discovered that banking apps didnt worked anymore even though my phone was not properly rooted(as per apps like root checker and universal unroot). I think its probably becuz of unlocked bootloader or may be encryption that i removed before formatting while in recovery. But i'm not sure and now, i dont want to root my device. Is there a way to make it as it was before i tried to root it? Any help is appreciated...
Bump
Its actually way more easier using an adroid without root. Iv tried a week askin for assistant to encrypt this fone. But no one replies on here. I have this fone rooted, flash disabler and it will not encrypt. Tried flashin multi disabler with encrypt keep, nothing, then found that twrp might not be flashing the partition correctly so figured out resizing blocks to free 16kb. nothing. Again, does anyone have ANY IDEA why ? all these devs coming out with all these useless flashable zips that break more than work. It all points to disabler disabling the encryption WITH NO WAY OF UNDOING THE ZIP. All these flashable zips actually fuk up more than they do.
Im just gonna go back to stock relock BL and forget about this site. Root is actually becoming so useless because the manufacteres are going out of the way to implement too much security.
You got the general idea... good for you..
The leak might give some new hope, but I don't know anything about that...