I know historically, the Exynos versions were easier to root - does this apply to the S8? Are there specific variants that are recommended if you're looking to root (I'd be using it on the US T-mobile network and don't care about WiFi calling)
Yes. It is largely a consequence of bootloader security: Qualcomm provides the secure bootloader for US Snapdragon S8/S8+. Samsung does not secure their Exynos S8/S8+ bootloader as restrictively. Bootloader is the key, because rooting is a minor afterthought if the bootloader allows you to boot a custom recovery like TWRP (i.e., flash SU in TWRP=rooted). Qualcomm's US Snapdragon S8/S8+ will not allow you to boot into or boot with an installed custom recovery like TWRP yet.
Related
I bought a chinese Huawei Mate 8 NXT-DL00. It is now unlocked, thanks to DC-unlocker:good:
It communicates with adb, and reboots in bootloader. For some reason adb will not flash TWRP 3.0.2.0. (or any other TWRP). Is there a known TWRP for DL00 chinese, or is it the same as AL-10?
is FRP unlocked?
No, FRP is not unlocked now, but I have unlocked in on DC before. After reboot it shows locked message in bootloader.
I see now that you mention it that it's possible to have the FRP stay unlocked. Is that necessary to flash twrp and SU?
Think City said:
No, FRP is not unlocked now, but I have unlocked in on DC before. After reboot it shows locked message in bootloader.
I see now that you mention it that it's possible to have the FRP stay unlocked. Is that necessary to flash twrp and SU?
Click to expand...
Click to collapse
In "Developer options", I do not have the "Enable OEM unlock" option. Does that mean my chinese phone does not have FRP?
Think City said:
I bought a chinese Huawei Mate 8 NXT-DL00. It is now unlocked, thanks to DC-unlocker:good:
It communicates with adb, and reboots in bootloader. For some reason adb will not flash TWRP 3.0.2.0. (or any other TWRP). Is there a known TWRP for DL00 chinese, or is it the same as AL-10?
Click to expand...
Click to collapse
The Chinese model does not have this option to Enable OEM unlock, and need not, in the Chinese versions google has less activity, which protects and blocks the device are the options of Huawei. In your case, only if you have installed the system in another model, international for example, then yes there would be this option, but it would not work. I did this idiocy, and I was blocked FRP, only the DC unlocker could release the lock. Anyway, it is not original firmware of another model, which is the version of your system? If you are in DL00C17B320 or above this, you need to downgrade to EMUI 4.0. In versions above it as the 320 for example, the system does not accept commands via fastboot. Only commands that do NOT change anything. And yes, everything works in AL10, DL00 serves in, you can install without fear ARE the same model, the difference is just the operator.
AL10 = chinese version, unlocked
TL00, DL00, CL00 = chinese versions, locked to chinese carriers
MarceloAF said:
The Chinese model does not have this option to Enable OEM unlock, and need not, in the Chinese versions google has less activity, which protects and blocks the device are the options of Huawei. In your case, only if you have installed the system in another model, international for example, then yes there would be this option, but it would not work. I did this idiocy, and I was blocked FRP, only the DC unlocker could release the lock. Anyway, it is not original firmware of another model, which is the version of your system? If you are in DL00C17B320 or above this, you need to downgrade to EMUI 4.0. In versions above it as the 320 for example, the system does not accept commands via fastboot. Only commands that do NOT change anything. And yes, everything works in AL10, DL00 serves in, you can install without fear ARE the same model, the difference is just the operator.
AL10 = chinese version, unlocked
TL00, DL00, CL00 = chinese versions, locked to chinese carriers
Click to expand...
Click to collapse
My system is DL00C17B197. I still can't flash twrp. ADB says: "error: cannot load "twrp.img"". Must I unlock the chinese carriers, or something?
Think City said:
My system is DL00C17B197. I still can't flash twrp. ADB says: "error: cannot load "twrp.img"". Must I unlock the chinese carriers, or something?
Click to expand...
Click to collapse
Forgive me for the delay, I only saw it now. I do not think so, does your mistake look like something else, the bootloader, it's unlocked?
New to rooting and unlocking bootloaders. I've managed to get through the rooting process but now i'm noticing I need to do something like unlocking the bootloader. I have no idea what im doing and would like a link to instructions or someone to walk me through the process. I've tried google but am unable to find anything.
Jbrasta said:
New to rooting and unlocking bootloaders. I've managed to get through the rooting process but now i'm noticing I need to do something like unlocking the bootloader. I have no idea what im doing and would like a link to instructions or someone to walk me through the process. I've tried google but am unable to find anything.
Click to expand...
Click to collapse
A boot loader is the code that executes specific system properties during boot. The perks of having an "unlocked" boot loader is that you can root and install custom firmware. Well the Sprint Galaxy S5 (SM-900P) already has an unlocked boot loader from Samsung. The Verizon and AT&T variants of the S5 only have a locked boot loader. Basically a "locked" boot loader is the boot.img that's been encrypted so nobody can make changes to the boot loader without exploitive means or exclusive software development. Meaning a difficult and potentially unstable root (if ever found) and probably no AOSP firmware.
T-Mobile also has a variant that is unlocked at the boot loader.
I was wondering if the newly released CF-Auto-Root for some s8 and s8+ models would root my phone even though there is no "OEM unlock" option under developer options. I was under the assumption that this phone would need an unlocked bootloader in order to root it , yet some websites have guides stating that it should root the phone
without a unlocked BL it's either give you an error while flashing or brick your device.
What will happen if I relock bootloader .. because I hate the pop up "your device has been unlocked .." while it boots.. does after relocking bootloader stops twrp to work ?
dhenewar said:
What will happen if I relock bootloader .. because I hate the pop up "your device has been unlocked .." while it boots.. does after relocking bootloader stops twrp to work ?
Click to expand...
Click to collapse
If you relock your bootloader with TWRP or anything else non stock, you'll likely boot loop until you unlock again. It's likely you'll trip the verification checks -performed by a locked bootloader - with TWRP, which means you need to be fully stock for a successful locked bootloader. If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues as you can't then unlock.
If you want to, you can flash a custom logo.bin (plenty of links in the Mods section) which will hide the warning, won't shorten the delay but it'll be nicer to look at.
echo92 said:
If you relock your bootloader with TWRP or anything else non stock, you'll likely boot loop until you unlock again. It's likely you'll trip the verification checks -performed by a locked bootloader - with TWRP, which means you need to be fully stock for a successful locked bootloader. If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues as you can't then unlock.
If you want to, you can flash a custom logo.bin (plenty of links in the Mods section) which will hide the warning, won't shorten the delay but it'll be nicer to look at.
Click to expand...
Click to collapse
Ok bro thanks for the info ..will SuperSu be as same as twrp causing bootloop?... luckily I have got stock recovery n firmware .. as u said "If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues " .. I am having the problem in other device(Samsung Galaxy grand prime G531H .. Cuz of my careless n rush.i forgot to enable oem n then flashed custom rom in Odin .. then it got bricked.. searched alot in internet for solution..also .. i have created post here.. still no solution .. and Now my device is just waste ..gave up on it ... RIP :angel: ..
dhenewar said:
Ok bro thanks for the info ..will SuperSu be as same as twrp causing bootloop?... luckily I have got stock recovery n firmware .. as u said "If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues " .. I am having the problem in other device(Samsung Galaxy grand prime G531H .. Cuz of my careless n rush.i forgot to enable oem n then flashed custom rom in Odin .. then it got bricked.. searched alot in internet for solution..also .. i have created post here.. still no solution .. and Now my device is just waste ..gave up on it ... RIP :angel: ..
Click to expand...
Click to collapse
I think so, a locked bootloader, as I understand it, checks the integrity of your recovery, kernel and system, and if it detects a break in the chain of trust (e.g. if there's a custom modification that changes the signature expected), then as a security measure the device just won't boot/bootloop. SuperSU or any root, custom kernel, or TWRP or even if you've allowed TWRP to make modifications may result in bootloops thus.
Therefore, if you wish to re-lock your device, you'll want to re-flash the stock firmware and then lock. You can only lock your device with the same firmware or newer than the version your device was updated to (including OTA updates). The latest version we have is the June fastboot ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Of course, flashing this will wipe TWRP, root and possibly your data from your device, so back up and keep the backups off your device. Alternatively, you may just wish to flash the custom logo.bin as mentioned previously, which would hide the bootloader warning.
About your Galaxy Grand Prime, ouch - that's a horrible situation to be in; unless there's a potential bootloader exploit, you're caught in the nasty situation where you can't unlock your bootloader (because of the OEM unlock) and because the security's been tripped, won't allow you to boot to get to the OEM unlock Are there any Samsung service centres or repair shops that could help you recover? You could have a look around the Galaxy Grand Prime forum, see if there's anything that could help: https://forum.xda-developers.com/grand-prime
echo92 said:
I think so, a locked bootloader, as I understand it, checks the integrity of your recovery, kernel and system, and if it detects a break in the chain of trust (e.g. if there's a custom modification that changes the signature expected), then as a security measure the device just won't boot/bootloop. SuperSU or any root, custom kernel, or TWRP or even if you've allowed TWRP to make modifications may result in bootloops thus.
Therefore, if you wish to re-lock your device, you'll want to re-flash the stock firmware and then lock. You can only lock your device with the same firmware or newer than the version your device was updated to (including OTA updates). The latest version we have is the June fastboot ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Of course, flashing this will wipe TWRP, root and possibly your data from your device, so back up and keep the backups off your device. Alternatively, you may just wish to flash the custom logo.bin as mentioned previously, which would hide the bootloader warning.
About your Galaxy Grand Prime, ouch - that's a horrible situation to be in; unless there's a potential bootloader exploit, you're caught in the nasty situation where you can't unlock your bootloader (because of the OEM unlock) and because the security's been tripped, won't allow you to boot to get to the OEM unlock Are there any Samsung service centres or repair shops that could help you recover? You could have a look around the Galaxy Grand Prime forum, see if there's anything that could help: https://forum.xda-developers.com/grand-prime
Click to expand...
Click to collapse
Thanx bro I will try it out .. yep bro I got it in service center n they told me .. No way of fixing it .. Aahh n that's it ? .well there was option change of hardware price was half of the phone cost ..better to buy new one ?
I know that some variants can't be unlocked,
but what if we downgrade with lgup and edz files, root using an exploit usable on the downgraded version, and then use su to dd an unlocked bootloader (extracted from a lucky guy that had the unlock.bin from lgdevs for the same model). Will it not boot because of imei or unique device ID ? Or worse the bootloader partition isn't r/w from the root ? Just asking because I don't really know how work the protection on Android.