I have access to an engineering bootloader for the Tmo Note8 and I would like to know how to test if it is unlocked.
Is there a specific process to determine if the bootloader is locked? Are there steps to permanently unlock the bootloader from an engineering bootloader?
I've searched all the Note8 forums and haven't found any answers.
Sent from my SM-G892U using Tapatalk
reukiodo said:
I have access to an engineering bootloader for the Tmo Note8 and I would like to know how to test if it is unlocked.
Is there a specific process to determine if the bootloader is locked? Are there steps to permanently unlock the bootloader from an engineering bootloader?
I've searched all the Note8 forums and haven't found any answers.
Click to expand...
Click to collapse
Flashing it and then checking if you can unlock it would be how to go about it. Except you can't flash unsigned images without unlocking so it's a catch 22 really. And it may just brick your phone even if you flashed it successfully. No way of knowing if that bootloader will even boot your device or play nice with the other partitions.
Gizmoe said:
Flashing it and then checking if you can unlock it would be how to go about it. Except you can't flash unsigned images without unlocking so it's a catch 22 really. And it may just brick your phone even if you flashed it successfully. No way of knowing if that bootloader will even boot your device or play nice with the other partitions.
Click to expand...
Click to collapse
The eng bootloader is signed, so there is no problem flashing the eng bootloader. I just do not know how to test if it is unlocked, as I can't find a recovery image to flash, and I do not know how to create one myself.
Sent from my SM-G892U using Tapatalk
reukiodo said:
The eng bootloader is signed, so there is no problem flashing the eng bootloader. I just do not know how to test if it is unlocked, as I can't find a recovery image to flash, and I do not know how to create one myself.
Sent from my SM-G892U using Tapatalk
Click to expand...
Click to collapse
probably just the combo files that are used for samfail imo. if you want to upload and have me check them lmk but more then likely all you have is the combo firmware we have been using since day one
Team DevDigitel said:
probably just the combo files that are used for samfail imo. if you want to upload and have me check them lmk but more then likely all you have is the combo firmware we have been using since day one
Click to expand...
Click to collapse
https://drive.google.com/file/d/1PIVZs-uB8kKb9YbY_fAcYJCGIfdb27W5/view?usp=drivesdk
This might only work on the T-Mobile version.
reukiodo said:
https://drive.google.com/file/d/1PIVZs-uB8kKb9YbY_fAcYJCGIfdb27W5/view?uk
This might only work on the T-Mobile version.
Click to expand...
Click to collapse
Do you have the boot.img that matches this?
Unable to check the rest without as it won't boot the combo img.
Yes it is a eng img.
We are on multi csc devices so all are same for flashing sake, as long as it's not the exynos.
Please remove the public link and we can move to pm/telegram and speak further
Team DevDigitel said:
Do you have the boot.img that matches this?
Unable to check the rest without as it won't boot the combo img.
Yes it is a eng img.
We are on multi csc devices so all are same for flashing sake, as long as it's not the exynos.
Please remove the public link and we can move to pm/telegram and speak further
Click to expand...
Click to collapse
I disabled the link, though not sure why I should? I haven't gotten telegram yet. I just want to know if it is unlocked for flashing custom recovery such as TWRP.
reukiodo said:
I disabled the link, though not sure why I should? I haven't gotten telegram yet. I just want to know if it is unlocked for flashing custom recovery such as TWRP.
Click to expand...
Click to collapse
No one has compiled twrp for snapdragon because we dont have a unlocked bl. Removing link is primarily to avoid people flashing this or reposting it with incorrect info and causing confusion.
If I can get the boot.img as well that is compiled for this bootloader I can get a running system and see if it can be unlocked. Otherwise without it there's no way to determine some of the important factors here. Just flashing against device to test is quite risky.
The bl is compatible with all snapdragon and does install correctly but it won't boot with the combo imgs we use for samfail or a stock img.
Link is still active fyi and I've sent you a pm with telegram info. It's a group for us and a few other devs that can work with us to get things sorted.
I used the engineering bootloader with Odin, after it flashed showed it as an eng boot loader not user, says Samsung official and is still locked. I booted with a binary .img booted and oem option from the settings was there, showed the same unlocked img on boot as samfail also. But I didn't do much other than check those things. I tried to load samfail system but it didn't load I figured as much seeing samfail boot.img is user-test not user-release and has custom binary but I don't know that much
I am wondering if we don't have to leave the eng boot loader on and oem toggled for a week like exyos versions before we can flash custom binary
DroidisLINUX said:
I used the engineering bootloader with Odin, after it flashed showed it as an eng boot loader not user, says Samsung official and is still locked. I booted with a binary .img booted and oem option from the settings was there, showed the same unlocked img on boot as samfail also. But I didn't do much other than check those things. I tried to load samfail system but it didn't load I figured as much seeing samfail boot.img is user-test not user-release and has custom binary but I don't know that much
I am wondering if we don't have to leave the eng boot loader on and oem toggled for a week like exyos versions before we can flash custom binary
Click to expand...
Click to collapse
I'm wondering if after flashing this engineering bootloader we can root phone just by simply using command prompt and sideloading root files. Any ideas? I don't know enough to do this.
Sent from my [device_name] using XDA-Developers Legacy app
Eudeferrer said:
I'm wondering if after flashing this engineering bootloader we can root phone just by simply using command prompt and sideloading root files. Any ideas? I don't know enough to do this.
Click to expand...
Click to collapse
I don't believe so, until we can get it unlocked, when in download mode it says the boot loader is still locked and says system secure in red and official binaries but if we can get the boot loader to say unlocked then I believe it will probably be possible. At least it says eng boot loader and tells us it's locked and that means it can be unlocked it's just a matter of time until someone gets it unlocked now
I am glad I haven't updated to boot loader 3 now, this is bootloader 2 so if you go to oreo you won't be able to use this when and if it's unlocked
DroidisLINUX said:
I don't believe so, until we can get it unlocked, when in download mode it says the boot loader is still locked and says system secure in red and official binaries but if we can get the boot loader to say unlocked then I believe it will probably be possible. At least it says eng boot loader and tells us it's locked and that means it can be unlocked it's just a matter of time until someone gets it unlocked now
I am glad I haven't updated to boot loader 3 now, this is bootloader 2 so if you go to oreo you won't be able to use this when and if it's unlocked
Click to expand...
Click to collapse
Has anyone tried the same procedure/comands used to unlock the Pixel XL? Would they even work I this phone if it had this eng bootloader? I wish I knew enough about this stuff to try it out or even know if it would work.
Sent from my [device_name] using XDA-Developers Legacy app
DroidisLINUX said:
I used the engineering bootloader with Odin, after it flashed showed it as an eng boot loader not user, says Samsung official and is still locked. I booted with a binary .img booted and oem option from the settings was there, showed the same unlocked img on boot as samfail also. But I didn't do much other than check those things. I tried to load samfail system but it didn't load I figured as much seeing samfail boot.img is user-test not user-release and has custom binary but I don't know that much
I am wondering if we don't have to leave the eng boot loader on and oem toggled for a week like exyos versions before we can flash custom binary
Click to expand...
Click to collapse
you could test,
but if you look under the info on the boot up screen, secure boot is still set to : enabled
IE: each and every boot it checks for a modified boot.img and if found it fails secure check.
I never tested the oem unlock options etc, or waiting any time frame, just mostly seeing what we could use with it.
The phone wont boot a modified system as well. has to be unrooted stock system + stock boot.img to boot with the eng bootloader.
Unfortunately i havent heard anything back, was hoping we could get the boot.img that is ENG so we can boot the entire setup and go.
Related
Hey all,
I'm fairly new to unlocking/rooting (I'm from the simple iPhone jailbreak world).
I have my Atrix 4G rooted with no issues and ClockworkMod installed... that was the easy part it seems.
Where I am struggling is to figure out IF I can unlock my Atrix 4G and if it is safe to do.
I am running Android 2.3.6 on the Bell network. I see a bunch on unlocks for bootloader 2.3.4 and am confisued if that bootloader version has any relation to the android version? How can I figure out what bootloader I have? Would it also be 2.3.6?
If it is indeed 2.3.6, is it possible to unlock, I see no specific unlocks for that version.
Thanks,
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Random Canadian said:
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Click to expand...
Click to collapse
Sorry should have been a little more clear, I have installed ROM Manager and choose the CWM install, but I cannot boot into it, I get a boot error 2 (I think). Sorry phone is at home now so I can't recall exact error will post later.
I got phone 6 month ago, was used phone. I am fairly certain its not unlocked because I cannot boot with CWM, hence cannot install custom ROM.
Thanks for the reply.
Random Canadian said:
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Click to expand...
Click to collapse
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
cerps said:
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
Click to expand...
Click to collapse
Right, my phone is rooted so I have CWM, just can't boot it. My understanding is because I need to unlock, but I don't know how to unlock because I don't know how to figure out what bootloader I have.
cerps said:
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
Click to expand...
Click to collapse
Locked or it just didnt say unlocked at the top? two very different things.
avalanche333 said:
Right, my phone is rooted so I have CWM, just can't boot it. My understanding is because I need to unlock, but I don't know how to unlock because I don't know how to figure out what bootloader I have.
Click to expand...
Click to collapse
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one. Aside from the fact you no longer have any sort of a functional recovery mode.
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Random Canadian said:
Locked or it just didnt say unlocked at the top? two very different things.
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Click to expand...
Click to collapse
Yes I see what your saying, but I am saying that I cannot run CWM. I can only install onto my SD card. But the boot in recovery does not work (ie it will not run CWM). I'll post the error little later tonight when I try at it again.
I realize there is lots of info on unlocking bootloader and I am not concerned about doing the unlock, once I find a way to verify my bootloader version. Ive seen a few posts warning that bootloader must be v 2.3.4 or you can brick the phone.
So I guess ultimately my question is, how can I figure out my bootloader version? Have not seem this answers after some googling.
http://forum.xda-developers.com/showthread.php?t=1136261
Read that and your version will be in settings and then about phone. although I do believe that 234 and 236 unlock via the same method.
If you are going to install Custom roms CM7/9/10 or a blur based then you dont need to even worry about root. otherwise there are instructions in that thread to root that SBF
Random Canadian said:
Locked or it just didnt say unlocked at the top? two very different things.
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one. Aside from the fact you no longer have any sort of a functional recovery mode.
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Click to expand...
Click to collapse
I'm positive it was locked, running 1.83, and had CWM on it. I bought the phone at an AT&T store myself. I rooted it and put CWM on it. The early version of CWM for the Atrix only was accessible by turning the phone on while plugged into the wall charger that came with the phone.
I was wondering if the S6 on Vodafone in the UK came with a locked bootloader, and if so how difficult was it to unlock? I have an S7 Edge on pre-order, and presume that would come locked too if the S6 did. I can't live without root. Cheers.
No one has an S6 Edge on Vodafone?
Beefheart said:
I was wondering if the S6 on Vodafone in the UK came with a locked bootloader, and if so how difficult was it to unlock? I have an S7 Edge on pre-order, and presume that would come locked too if the S6 did. I can't live without root. Cheers.
Click to expand...
Click to collapse
Seems so, as I have had the same problem by installing MM 6.0.1 firmware with the UK csc code VOD (appearing as BTU on phone). The bootloader wouldn't let me flash TWRP through ODIN (sorry, could flash, but not boot into TWRP, stuck on bootloader).
So i took the provided MM 6.0.1. bootloader from Carotix CarHDRom, flashed it together with at the same place provided TWRP for
MM (the old 2.8.7.0/2.8.7.1 or even new TWRP 3.0 provided on the homepage of TWRP.me , won't work on MM) throught ODIN.
Within TWRP flashed hybridmax's S5E-AELKernel_MM...kernel 1.5 and superSU beta 2.67 (previosly stored/copied to the mobile device) and rebooted - rooted and all working fine.
Take a look at : http://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519
coco722 said:
Seems so, as I have had the same problem by installing MM 6.0.1 firmware with the UK csc code VOD (appearing as BTU on phone). The bootloader wouldn't let me flash TWRP through ODIN (sorry, could flash, but not boot into TWRP, stuck on bootloader).
So i took the provided MM 6.0.1. bootloader from Carotix CarHDRom, flashed it together with at the same place provided TWRP for
MM (the old 2.8.7.0/2.8.7.1 or even new TWRP 3.0 provided on the homepage of TWRP.me , won't work on MM) throught ODIN.
Within TWRP flashed hybridmax's S5E-AELKernel_MM...kernel 1.5 and superSU beta 2.67 (previosly stored/copied to the mobile device) and rebooted - rooted and all working fine.
Take a look at : http://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519
Click to expand...
Click to collapse
Did you have the OEM Unlock toggle in dev options?
Beefheart said:
Did you have the OEM Unlock toggle in dev options?
Click to expand...
Click to collapse
Do not know if or not.
Just flashed first the original VOD 6.0.1 fw and then tried to have a working TWRP recovery, but could't boot into TWRP recover, the original bootloader did not let me... this for, bootloader and twrp from carotix (and eventually his provided kernel and/or rom) , and everything goes fine.
coco722 said:
Do not know if or not.
Just flashed first the original VOD 6.0.1 fw and then tried to have a working TWRP recovery, but could't boot into TWRP recover, the original bootloader did not let me... this for, bootloader and twrp from carotix (and eventually his provided kernel and/or rom) , and everything goes fine.
Click to expand...
Click to collapse
My understanding of a locked bootloader is that you can't flash anything that isn't official, including a replacement bootloader, which you indicate you did successfully. Otherwise Verizon Samsung customers would simply flash a new bootloader over their locked one. Ever TWRP wouldn't have flashed, it would have kicked out an error in Odin as you made the attempt because the bootloader wouldn't have allowed it. It sounds like your attempt at flashing it finished successfully, but just wouldn't boot into it. I'm wondering if this was caused by something other than the bootloader being locked.
Beefheart said:
My understanding of a locked bootloader is that you can't flash anything that isn't official, including a replacement bootloader, which you indicate you did successfully. Otherwise Verizon Samsung customers would simply flash a new bootloader over their locked one. Ever TWRP wouldn't have flashed, it would have kicked out an error in Odin as you made the attempt because the bootloader wouldn't have allowed it. It sounds like your attempt at flashing it finished successfully, but just wouldn't boot into it. I'm wondering if this was caused by something other than the bootloader being locked.
Click to expand...
Click to collapse
All possible. However, sometimes we'll just have to give it a try, by using the information and software available. I do have to mention, that my mobile is/was provider-free (not locked to a specific provider). But even a locked mobile can be handeld to get
in free and unlocked. In such case, this should be done first and after that the upgrade to rooted MM and ROM, etc.
No worries, cheers for the reply. I'll wait until I receive it then simply return it and cancel the contract if it's locked.
Hi, i had the same problem. I flashed TWRP, but i could not boot to TWRP. I found that I also have locked bootloader. No OEM Unlock toggle in dev options.
Login on this site
https://findmymobile.samsung.com/login.do
and try Disable Reactivation lock if you can.
vrzy007 said:
Hi, i had the same problem. I flashed TWRP, but i could not boot to TWRP. I found that I also have locked bootloader. No OEM Unlock toggle in dev options.
Login on this site
https://findmymobile.samsung.com/login.do
and try Disable Reactivation lock if you can.
Click to expand...
Click to collapse
I've not received my phone yet, but this doesn't look good. Were you able to disable the reactivation lock on your S6? Or, alternatively, like coco722, were you able to simply overwrite the bootloader? I'm not concerned with Knox or Vodafone's warranty, as long as I'm able to overcome the locked bootloader and root.
Hello,
situation ist this:
Cyanogen Recovery is installed and there is no rom on the phone. But it won't install a new one through apply update. So I tried installing twrp through fast boot. But it failed with:
FAILED (remote: Device not unlocked cannot flash or erase)
So i tried to unlock it which gave me:
FAILED (remote: oem unlock is disabled)
oem devices gave me tampered = false and unlocked = false
What can I do.
Would appreciate help
Morishno
Flash stock recovery and try unlock again.
Dumb Question but how exactly do I do that?
Just flash it via fast boot? And where do i get it?
Morishno said:
Dumb Question but how exactly do I do that?
Just flash it via fast boot? And where do i get it?
Click to expand...
Click to collapse
You can get it from oneplus downloads section, if you cant find it ask me... Yes you have to flash official stock recovery through fastboot
Exodusche said:
Flash stock recovery and try unlock again.
Click to expand...
Click to collapse
cva_kabil said:
You can get it from oneplus downloads section, if you cant find it ask me... Yes you have to flash official stock recovery through fastboot
Click to expand...
Click to collapse
Not really, OP reports that the unlock command gave him FAILED (remote: oem unlock is disabled)
Hey OP, did you enable OEM Unlocking from Developer options ?
Joshwin Aranha said:
Not really, OP reports that the unlock command gave him FAILED (remote: oem unlock is disabled)
Hey OP, did you enable OEM Unlocking from Developer options ?
Click to expand...
Click to collapse
If not is there any other way?
cva_kabil said:
If not is there any other way?
Click to expand...
Click to collapse
I'm sorry but i do not know any other method that works without flipping that switch in Developer Options.
Joshwin Aranha said:
I'm sorry but i do not know any other method that works without flipping that switch in Developer Options.
Click to expand...
Click to collapse
You dont need to be sorry, thats okay i jus asked... Maybe OP didnt enable oem unlocking.
I didnt enable oem unlocking because it wasnt necessary. The device was unlocked and twrp and cyanogenmod were installed. But somehow cyanogen recovery was installed. Super user was away and I tried to reinstall it. Not knowing the recovery had changed I chose twrp/cwm to install it what resulted in a boot loop. No problem I thought just flash a ROM which didn't worked. No problem just flash a proper recovery it didn't worked. And somehow the device is locked again..
Sorry I was little brief when I said flash stock recovery. I believe if you revert back completely stock you can start the process from the beginning again. That would mean fastboot flash stock recovery then any firmware of OnePlus X. I'm not sure how a bootloader can relock itself.
Exodusche said:
Sorry I was little brief when I said flash stock recovery. I believe if you revert back completely stock you can start the process from the beginning again. That would mean fastboot flash stock recovery then any firmware of OnePlus X. I'm not sure how a bootloader can relock itself.
Click to expand...
Click to collapse
But I couldn't flash twrp.. Is it possible to flash the stock recovery with a locked boot loader? I don't have access to the phone at the moment and i want to gather as much information possible thats why i'm asking
Morishno said:
But I couldn't flash twrp.. Is it possible to flash the stock recovery with a locked boot loader? I don't have access to the phone at the moment and i want to gather as much information possible thats why i'm asking
Click to expand...
Click to collapse
I'm not sure but this has been addressed many times. Comb the threads you will find the information you need.
Exodusche said:
I'm not sure but this has been addressed many times. Comb the threads you will find the information you need.
Click to expand...
Click to collapse
Found a hard brick guide. You mean that?
So I just remembered something was able to help someone else with a similar issue. If you can boot Into something and your rooted download the app Rashr. With it you can flash stock recovery and be back in business.
The problem is i dont have anything to Boot
//UPDATE: So I tried booting with fastboot boot but it said cannot boot device isn't unlocked.
Edited
So i managed to save the Phone using the Hard Brick Guide. Thanks everyone!
Thank goodness for the hard brick guide. ?
Exodusche said:
I think your gonna have to go through the hard bricked guide.
Click to expand...
Click to collapse
Yeah i did that and it worked thank you
Hello guys,
I've been trying to root this phone since i've bought it, problem is every option i read on the web doesnt work because phone's bootloader is locked, and all methods get to this point when u have to unlock ur phone bootloader but in order to do that u have to get in the phone bootloader wich is locked. So who the hell is giving advices like these i dont know. Problem is that i am motivated to still root it, nothing its impossible.
So i am asking, did anyone from EU, with the EU ROM (full of mallware) MIUI 8, managed to unlock its bootloader and then managed to root it ?! please lets discuss here the options that work and the options that didnt work so we can make it through and solve this problem, everything thats on web at this moment 27-11-2016 doesnt work on the False EU MIUI 8.
Thanks.
CatalinSava said:
Hello guys,
I've been trying to root this phone since i've bought it, problem is every option i read on the web doesnt work because phone's bootloader is locked, and all methods get to this point when u have to unlock ur phone bootloader but in order to do that u have to get in the phone bootloader wich is locked. So who the hell is giving advices like these i dont know. Problem is that i am motivated to still root it, nothing its impossible.
So i am asking you did anyone from EU, with the EU ROM (full of mallware) MIUI 8, managed to unlock its bootloader and then managed to root it ? please lets discuss here the options that work and the options that didnt work so we can make it through and solve this problem, everything thats on web at this moment 27-11-2016 doesnt work on the False EU MIUI 8.
Thanks.
Click to expand...
Click to collapse
Not posibble without unlocked bootloader. Even the pre-rooted China Developer rom needs phone with unlocked bootloader. Good luck with unlocking the bootloader.
EU ROM full of malware?!?! Where did you get that idea? Completely false.
Anyway as said, yes you do need to unlock bootloader. Impossible any other way, because the system has dm-verity (similar to HTC S-On) which prevents modification to /system. So if you can't modify system or boot partition then you can't put Superuser binaries anywhere. Unlocked bootloader allows to put Superuser on boot pertition.
Sent from my Redmi Note 4 using Tapatalk
CosmicDan said:
EU ROM full of malware?!?! Where did you get that idea? Completely false.
Anyway as said, yes you do need to unlock bootloader. Impossible any other way, because the system has dm-verity (similar to HTC S-On) which prevents modification to /system. So if you can't modify system or boot partition then you can't put Superuser binaries anywhere. Unlocked bootloader allows to put Superuser on boot pertition.
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Can't we just flash a recovery-that can disable dm-verity using SP Flash and root the phone that way?
I am guessing not because no one has said it works
I'm getting rly impatient because I still havent got my bootloader unlock request approved yet lol
asusm930 said:
Can't we just flash a recovery-that can disable dm-verity using SP Flash and root the phone that way?
I am guessing not because no one has said it works
I'm getting rly impatient because I still havent got my bootloader unlock request approved yet lol
Click to expand...
Click to collapse
No because dm-verity is enabled/set in the kernel (ramdisk on boot partition), and if you modify the boot partition with a locked bootloader then it won't boot
Locked bootloader = prevents boot partition from being tampered with
dm-verity = set in boot partition, prevents system partition from being tampered with
So you simply need to unlock bootloader, there is just no other way to exploit the device (no possible attack vector). The device is very secure, like all Marshmallow devices.
So what is this false EU firmware you speak of? Obviously not the xiaomi.eu one because that requires unlocked bootloader.
You can flash global stable via SP Flash Tool, that's your best bet while waiting for bootloader unlock. If it's taking more than 1 week then you can contact official support or something via en.miui.com forum (its down at the moment for some reason).
CosmicDan said:
No because dm-verity is enabled/set in the kernel (ramdisk on boot partition), and if you modify the boot partition with a locked bootloader then it won't boot
Locked bootloader = prevents boot partition from being tampered with
dm-verity = set in boot partition, prevents system partition from being tampered with
So you simply need to unlock bootloader, there is just no other way to exploit the device (no possible attack vector). The device is very secure, like all Marshmallow devices.
So what is this false EU firmware you speak of? Obviously not the xiaomi.eu one because that requires unlocked bootloader.
You can flash global stable via SP Flash Tool, that's your best bet while waiting for bootloader unlock. If it's taking more than 1 week then you can contact official support or something via en.miui.com forum (its down at the moment for some reason).
Click to expand...
Click to collapse
have you atempted to see what actually happens when a bootloader is unlocked? Like what does the miunlocker do/flash on the phone?
---------- Post added at 05:20 AM ---------- Previous post was at 05:04 AM ----------
CosmicDan said:
No because dm-verity is enabled/set in the kernel (ramdisk on boot partition), and if you modify the boot partition with a locked bootloader then it won't boot
Locked bootloader = prevents boot partition from being tampered with
dm-verity = set in boot partition, prevents system partition from being tampered with
So you simply need to unlock bootloader, there is just no other way to exploit the device (no possible attack vector). The device is very secure, like all Marshmallow devices.
So what is this false EU firmware you speak of? Obviously not the xiaomi.eu one because that requires unlocked bootloader.
You can flash global stable via SP Flash Tool, that's your best bet while waiting for bootloader unlock. If it's taking more than 1 week then you can contact official support or something via en.miui.com forum (its down at the moment for some reason).
Click to expand...
Click to collapse
I'm gonna try to flash a twrp recovery using this guide http://en.miui.com/thread-371349-1-1.html
and replace the recovery file with TWRP. Will report if it works
Yea it doesnt work haha
CosmicDan said:
No because dm-verity is enabled/set in the kernel (ramdisk on boot partition), and if you modify the boot partition with a locked bootloader then it won't boot
Locked bootloader = prevents boot partition from being tampered with
dm-verity = set in boot partition, prevents system partition from being tampered with
So you simply need to unlock bootloader, there is just no other way to exploit the device (no possible attack vector). The device is very secure, like all Marshmallow devices.
So what is this false EU firmware you speak of? Obviously not the xiaomi.eu one because that requires unlocked bootloader.
You can flash global stable via SP Flash Tool, that's your best bet while waiting for bootloader unlock. If it's taking more than 1 week then you can contact official support or something via en.miui.com forum (its down at the moment for some reason).
Click to expand...
Click to collapse
Hey can you upload you miunlock tool folder here? Want to see if the miunlock tool downloaded anything that enabled the bootloader unlock
asusm930 said:
Hey can you upload you miunlock tool folder here? Want to see if the miunlock tool downloaded anything that enabled the bootloader unlock
Click to expand...
Click to collapse
You can download it for free, just search for MiFlash - it's not a secret tool or anything.
Attempting to see what actually happens...? Even if I had the skills to reverse engineer MediaTek security, I wouldn't do it.
You're trying to do such simple things to trick the system but you need to realize that this hardware has been verified by Google themselves as secure and safe enough for Android Pay and SafetyNet and such. It *can not* be easily cracked, accept it.
Replacing recovery.img with TWRP? Seriously? How dumb do you think these companies are? Sorry for being rude but you really are just being silly.
You are wasting your own time, and now mine too... Sorry but I'm going to unsubscribe now because these questions are just getting silly.
Sent from my Redmi Note 4 using Tapatalk
CosmicDan said:
You can download it for free, just search for MiFlash - it's not a secret tool or anything.
Attempting to see what actually happens...? Even if I had the skills to reverse engineer MediaTek security, I wouldn't do it.
You're trying to do such simple things to trick the system but you need to realize that this hardware has been verified by Google themselves as secure and safe enough for Android Pay and SafetyNet and such. It *can not* be easily cracked, accept it.
Replacing recovery.img with TWRP? Seriously? How dumb do you think these companies are? Sorry for being rude but you really are just being silly.
You are wasting your own time, and now mine too... Sorry but I'm going to unsubscribe now because these questions are just getting silly.
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Man, I did not know that xiaomi actually put that much effort on making their mediatek phones actually google levels of secure.
Was always under the impression that they sorta skimped out on their mediatek lines (as they had before).
Now I'll just not try to unlock it unofficially lol
asusm930 said:
Man, I did not know that xiaomi actually put that much effort on making their mediatek phones actually google levels of secure.
Was always under the impression that they sorta skimped out on their mediatek lines (as they had before).
Now I'll just not try to unlock it unofficially lol
Click to expand...
Click to collapse
They had before sure, but in the recent year or so (since they started actually locking bootloaders) things changed - they want to target international market too.
Only reason the devices are not sold globally is because of some Mediatek patent/legal battle or something, not too sure (it's literally the only reason why they have snapdragon "pro" versions). But the device has a global firmware sold in Taiwan and some other places, and it is Google CTS certified (preinstalled with Google Play) and, since it's Marshmallow, requires all kinds of Google-approved security measures these days, which a lot of countries need legally too, so yeah.
Glad you understand. I read that if it takes too long to get unlock code, you should try/already be flashed on China dev ROM - so do that if you have not already.
Have you tried the unlocking link on this link? http://xiaomi-mi.com/redmi-note-4/
Cleaning this up and clarifying as my original post was vague:
It is recommended that you unlock your bootloader before the 7.0 Nougat update. Although it will still be possible the process will be more difficult and risky afterwards.as you will need to use one of the edl mode tools (axon7backup, axom7tool).
The easiest way is to download this kit f you have the A2017U: (I can't speak to other models) (This kit and instructions are thanks to @jcadduono)
https://build.nethunter.com/misc/axon7/AXON7-A2017U-BL-UNLOCK-KIT.zip
https://build.nethunter.com/misc/axon7/INSTRUCTIONS.txt
The basic steps, which the above zip with take you through in detail are:
1. Flash Official B20 , enable OEM UNLOCKING after flashing.
2. Flash BLFastboot zip provided by ZTE when they had unlock method.
3. Enable OEM UNLOCKING in Developers Option
4. Boot to Bootloader
5. type : fastboot oem unlock
6. Done
Note: If you do not have the OEM UNLOCKING flag set in developer options you will get a soft brick. Also bear in mid this will wipe data.
All that being said I've heard Nougat to is going to be great from those in the know. In their words ”Well worth the wait! Hang in there!” from a HIGHLY credible source.
Why would anyone relock before update? I do agree anyone who wants to unlock should do it now.
lokissmile said:
For anyone looking to bootloader unlock, I've heard that the methods might change when the N update rolls out. It's a major update and although I personally don't have N and can't get a direct answer because those who know for sure are under NDA. I can tell you that the advice given to me is to not re-lock. So if you are thinking of unlocking your bootloader I'd do it soon while the methods are stable. Google confirmed that daydream is certified in an upcoming update so the daydream version of the stock ROM has been through googles QA. Might as well get ready now, we will probably have another surge of custom ROMS shortly after. I'm just sharing what I think is a best practice.
Click to expand...
Click to collapse
OK, so just to make it quick, for everyone, unlock your bootloader sooner than later. It is safe since you can revert it to a locked state at any time later.
lafester said:
Why would anyone relock before update? I do agree anyone who wants to unlock should do it now.
Click to expand...
Click to collapse
I do it on occasion to test things I'm working on. Better to warn people who might do it to get PoGo or SafetyNet working I figured.
lokissmile said:
I do it on occasion to test things I'm working on. Better to warn people who might do it to get PoGo or SafetyNet working I figured.
Click to expand...
Click to collapse
No need to bootloader lock an Axon 7 to get SafetyNet (Android Pay, PoGo, etc). Just do it the XDA way. But never relock!!!!
Could one of you guys explain whats so dangerous about relocking bootloader since u seem to know something I don't.
I have unlocked and relocked my bootloader several times by fastboot oem lock and restoring my stock fbop partition.
Have I done something wrong?
Regards,
mischa_martin
mischa_martin said:
Could one of you guys explain whats so dangerous about relocking bootloader since u seem to know something I don't.
I have unlocked and relocked my bootloader several times by fastboot oem lock and restoring my stock fbop partition.
Have I done something wrong? [emoji14]
Regards,
mischa_martin
Click to expand...
Click to collapse
Read the OP.
I think what the op is trying to say is that by unlocking the bootloader you won't get ota updates. You would need to wait until a twrp flashable update is out or a rom running Android 7.
stevecaboose said:
I think what the op is trying to say is that by unlocking the bootloader you won't get ota updates. You would need to wait until a twrp flashable update is out or a rom running Android 7.
Click to expand...
Click to collapse
That's how it's been since modifying the bootloader was a thing. Unlocked bootloader = no OTA.
tzbigworm said:
That's how it's been since modifying the bootloader was a thing. Unlocked bootloader = no OTA.
Click to expand...
Click to collapse
@stevecaboose
Unlocking Bootloader = Yes to OTA's.
Modding System and Boot = NO OTA's
hope that clear things up.
Close enough lol!
To be clear, it would be best to unlock before N is pushed out. I have it on good authority that unlocking your bootloader after you update to N will be more difficult and risky. Relocking would put you in the same situation. It's trivial to return to stock system+boot with an unlocked bootloader and TWRP and then the OTA will come through just fine. Or you can just wait for the TWRP flashable N stock ROM.
So to be clear, since I'm not 100% sure what affects the "system" and "boot" areas: I can unlock my BL using only guide 2 in this link ( https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ) and still get OTAs? If I install TWRP does that make me OTA-ineligible?
ScaryBugThing said:
So to be clear, since I'm not 100% sure what affects the "system" and "boot" areas: I can unlock my BL using only guide 2 in this link ( https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ) and still get OTAs? If I install TWRP does that make me OTA-ineligible?
Click to expand...
Click to collapse
TWRP/BL unlock doesn't affect OTA, ROOT does.
raystef66 said:
TWRP/BL unlock doesn't affect OTA, ROOT does.
Click to expand...
Click to collapse
You're totally wrong there,
TWRP will affect OTA's if the OTA need to check/patch recovery, BUT been Bootloader Unlock will NOT effect OTA.
To manage a clean/successful OTA's installation, you need to be FULL STOCK. (System, boot, Recovery, aboot if the OTA need to patched).
I think the OP was trying to say that it's possible current tools will not work to unlock the bootloader after the 7.x ota is installed.
DrakenFX said:
You're totally wrong there,
TWRP will affect OTA's if the OTA need to check/patch recovery, BUT been Bootloader Unlock will NOT effect OTA.
To manage a clean/successful OTA's installation, you need to be FULL STOCK. (System, boot, Recovery, aboot if the OTA need to patched).
Click to expand...
Click to collapse
I'm not fully agreed with that. You can install OTA's when you receive it, download it, install it when first booted into twrp cache. Only if you're not rooted. When you're rooted first unroot and in principle this should work.
There are several cases on internet about that. Even I did it with an unrooted but TWRP-ed Zopo C2. Received an OTA and installed it.
Im always glad to learn but IMO there are some possibilities to do the ota after all. But I am willing to accept it's a general fact that twrp could affect the normal OTA.
Edit : let's wait and see when B10 is rolling out and if I get a notification about that and if I can install it as a normal OTA(not with SD) with TWRP. Keep you updated:cyclops:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
eladmitz said:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
Click to expand...
Click to collapse
I`m on the same boat. What should be the safer procedure to unlock BL an still get the N OTA?
eladmitz said:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
Click to expand...
Click to collapse
felipe.vella said:
I`m on the same boat. What should be the safer procedure to unlock BL an still get the N OTA?
Click to expand...
Click to collapse
1- Download Official B20 from ZTE SITE (look Software Updates for the 6gb variant)
2- look in the forum for the B20fastboot zip file
3- Move both files to your SDCARD.
4- Enable OEM Unlocking under Developers Option
5- boot to stock recovery.
6- Install B20 official update via SDCARD (this will wipe Data)
7- boot and re-enable OEM Unlocking
8- boot to recovery and install B20fastboot zip
9- boot to Bootloader and Unlock bootloader using this command.
Code:
fastboot oem unlock
If I remember correctly will reboot and factory reset the device , you'll need to re-enable OEM UNLOCKING and boot to Bootloader to flash TWRP 3.0.3 USING fastboot commands