Related
Hey guys I have some questions. First of all I own an sk17i with ics. I had locked the bootloader and flashed ics now I wanna unlock it again, should I do this via the official way or via test method. If I unlock the bootloader will everything be deleted? And if I flash a custom kernel will I be able to flash super charger script?
*sorry but I am a newbie!
Sent from my SK17i using Tapatalk
If you do it with official method, you will lose your warranty, if you do it with tespoint method, you can unlock and relock and sony won't recognize, so your warranty is keepen up!
Here is the official method of sony, where you will loose your warranty.
Here you will find information on unlocking without loosing drm keys.
Unlocking the bootloader will delete all personal data, so do a nandroid backup via cwm before, so you can restore your current rom later.
nks13 said:
Hey guys I have some questions. First of all I own an sk17i with ics. I had locked the bootloader and flashed ics now I wanna unlock it again, should I do this via the official way or via test method. If I unlock the bootloader will everything be deleted? And if I flash a custom kernel will I be able to flash super charger script?
*sorry but I am a newbie!
Sent from my SK17i using Tapatalk
Click to expand...
Click to collapse
If you've previously unlocked the bootloader, then RE-locked it, you need to use the official method again.
You can use the same key to unlock it as before.
Unlocking bootloader does not affect any system or data files. So no, you don't loose any data.
V6 supercharger script requires init.d. Stock kernel doesn't support that ability unless you install it.
Anyway, you can install V6 with any kernel supposedly it supports init.d.
As far as I know, every custom kernel has support...
Michi_optimus_me said:
If you do it with official method, you will lose your warranty, if you do it with tespoint method, you can unlock and relock and sony won't recognize, so your warranty is keepen up!
Here is the official method of sony, where you will loose your warranty.
Here you will find information on unlocking without loosing drm keys.
Unlocking the bootloader will delete all personal data, so do a nandroid backup via cwm before, so you can restore your current rom later.
Click to expand...
Click to collapse
I do not have cwm installed and that's why I want to unlock bootloader. I have unlocked via official way so I think I should unlock it again via official way.
iONEx said:
If you've previously unlocked the bootloader, then RE-locked it, you need to use the official method again.
You can use the same key to unlock it as before.
Unlocking bootloader does not affect any system or data files. So no, you don't loose any data.
V6 supercharger script requires init.d. Stock kernel doesn't support that ability unless you install it.
Anyway, you can install V6 with any kernel supposedly it supports init.d.
As far as I know, every custom kernel has support...
Click to expand...
Click to collapse
So the apps will not be deleted? Cause the other man said that everything is gonna be deleted:S Please tell me man. I will unlock bootloader via official way, then I will install a custom kernel and finally I will install super charger
EDiT: you loose data partition so do make a backup
You can easily find a backup app on the market.
After that, you can flash a custom kernel and install V6
Official unlock method makes factory reset, so yes, you lose all data.
Thank you guys! when I will finish everything I'll tell you
Sent from my SK17i using Tapatalk
The other day, I set about installing Cyanogenmod 11 on my Xperia Z2 D5603. I was already rooted on the stock rom 4.4.4 Kitkat 23.0.1.A.0.167. I used flashtool to downgrade to 4.4.2 17.1.2.A.0.314, rerooted it, and installed dualrecovery from this link: http://forum.xda-developers.com/showthread.php?t=2785598
But upon choosing reboot after flashing the custom ROM via TWRP, the phone went dark, and wouldn't turn on. The only response I got was a quick vibration every second or two if I hold down the power button. I could not access recovery either.
I was able to revive it by using flashtool to reflash 4.4.2 17.1.2.A.0.314. I tried the same procedure with AOKP ROM, which had the same result. After trying many different things, I realized that factory reset, or wiping 'system' under advanced wipe would cause this to happen. Flashing without factory reset either returns an error, or finishes, but doesn't actually flash the ROM (stock ROM boots)
How to I flash a ROM without this happening? Any help is appreciated.
Have you unlocked your bootloader? It doesn't sound like it.
These roms require another kernel and you need to unlock your bootloader to install it.
o0 Matt 0o said:
Have you unlocked your bootloader? It doesn't sound like it.
These roms require another kernel and you need to unlock your bootloader to install it.
Click to expand...
Click to collapse
I thought that the fact that it was successfully rooted meant that the bootloader was unlocked. Is this not the case?
How do I unlock the bootloader and install whatever kernel I need?
ljapplebaum said:
I thought that the fact that it was successfully rooted meant that the bootloader was unlocked. Is this not the case?
How do I unlock the bootloader and install whatever kernel I need?
Click to expand...
Click to collapse
Hmm no.
Root ! = unlocked bootloader.
Go to the sony website ( http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader) to get instructions to unlock your bootloader.
But with your first assumption in mind, I suggest you read up about it first. Understand the risks and limitations.
o0 Matt 0o said:
Hmm no.
Root ! = unlocked bootloader.
Go to the sony website to get instructions to unlock your bootloader.
But with your first assumption in mind, I suggest you read up about it first. Understand the risks and limitations.
Click to expand...
Click to collapse
Perfect! I unlocked the bootloader by using the instructions on sony's website. It did the trick, and CM11 is running successfully.
Thanks so much!
Hi!
Today I tried for a few hours the official bootloader unlock method and I never succeded, or so it seems???
I always got stuck at 50% and never reached 100%.... But once I was in fastboot after trying for a few hours I could see that the bootloader was unlocked by typing
fastboot oem device-info
So can I in some way see if the device is unlocked by the official method, or that I actually got it unofficial unlocked from the seller (geekbuying).
More than likely it is unofficial unlocked by your seller.
Check you MIUI Version: - Settings - About Phone - MIUI Version
Report what you find there, you may also have a vendor rom!
corkiejp said:
More than likely it is unofficial unlocked by your seller.
Check you MIUI Version: - Settings - About Phone - MIUI Version
Report what you find there, you may also have a vendor rom!
Click to expand...
Click to collapse
MIUI Global 8.0 Stable 8.0.1.0.0 (LHOCNDG)
Are you sure? Cause it might have still "worked" while I was testing... If it helps to answer the question MI Unlock says "Couldn't verify device - No need to unlock this device"
katolo said:
MIUI Global 8.0 Stable 8.0.1.0.0 (LHOCNDG)
Are you sure? Cause it might have still "worked" while I was testing... If it helps to answer the question MI Unlock says "Couldn't verify device - No need to unlock this device"
Click to expand...
Click to collapse
It is a Vendor Rom!
Official roms come with four numbers (x.x.x.x)!
And since you can only unlock the bootloader on official roms. It has definitely been unlocked by the unofficial method.
Vendor roms may come with spyware/adware, so I would advise you to flash an official rom as soon as possible.
As your unlocked unofficially take care how you flash roms.
If you flash the latest Marshmallow roms, your bootloader may be locked again.
See the linked wiki above and read some of the threads here.
corkiejp said:
It is a Vendor Rom!
Official roms come with four numbers (x.x.x.x)!
And since you can only unlock the bootloader on official roms. It has definitely been unlocked by the unofficial method.
Vendor roms may come with spyware/adware, so I would advise you to flash an official rom as soon as possible.
As your unlocked unofficially take care how you flash roms.
If you flash the latest Marshmallow roms, your bootloader may be locked again.
See the linked wiki above and read some of the threads here.
Click to expand...
Click to collapse
Ok. Thanks.. But what would you recommend? I want to unlock the offical way. So should I flash the Marshmallow rom and let it lock and I unlock via the official?
@katolo That is a good question, which I don't have an answer for.
It may work, but also you may end up with a device you can not unlock officially.
See here :- https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
And this thread: - http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Flash Alka TWRP and make backup of all partitions first.
corkiejp said:
@katolo That is a good question, which I don't have an answer for.
It may work, but also you may end up with a device you can not unlock officially.
See here :- https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
And this thread: - http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Flash Alka TWRP and make backup of all partitions first.
Click to expand...
Click to collapse
Just for info for other people... I just flashed the MIUI Global DEV ROM and went into fastboot and checked the bootloader and now it is LOCKED again.
Now I will try to unlock it officially. Crappy geekbuying putting ****ty ROM on phone..
Thanks for the help.
katolo said:
Hi!
Today I tried for a few hours the official bootloader unlock method and I never succeded, or so it seems???
I always got stuck at 50% and never reached 100%.... But once I was in fastboot after trying for a few hours I could see that the bootloader was unlocked by typing
fastboot oem device-info
So can I in some way see if the device is unlocked by the official method, or that I actually got it unofficial unlocked from the seller (geekbuying).
Click to expand...
Click to collapse
corkiejp said:
@katolo That is a good question, which I don't have an answer for.
It may work, but also you may end up with a device you can not unlock officially.
See here :- https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
And this thread: - http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Flash Alka TWRP and make backup of all partitions first.
Click to expand...
Click to collapse
Just got to be a bit careful here. I'd recommend flashing "Safe TWRP" recovery once you have backed up all your partitions with alka TWRP.
@katolo Report back if you can successfully unlock by the official method.
Plenty of threads here on the steps required to do so.
corkiejp said:
@katolo Report back if you can successfully unlock by the official method.
Plenty of threads here on the steps required to do so.
Click to expand...
Click to collapse
Worked perfectly. Thanks for the help.
I'm on MM MIUI now... Will flash ALKA TWRP > FULL BACKUP > CM13 (goodix) then I'm set...
Jeanz Sensation said:
Just got to be a bit careful here. I'd recommend flashing "Safe TWRP" recovery once you have backed up all your partitions with alka TWRP.
Click to expand...
Click to collapse
Can I use Safe TWRP to flash CM13/CM14 and MIUI roms?
What is the difference between ALKA and SAFE TWRP?
katolo said:
Can I use Safe TWRP to flash CM13/CM14 and MIUI roms?
What is the difference between ALKA and SAFE TWRP?
Click to expand...
Click to collapse
If your bootloader is unlocked officially then you can use either of the recoveries. But if the bootloader has been unlocked unofficially then strictly use SAFE TWRP if you are flashing MIUI ROM.
The main difference between SAFE and Alka is that Alka gives you the option to backup few more partitions within the phone's memory as compared to SAFE. Bear in mind that these extra partitions may not be necessary for you to backup, hence eliminating the need for Alka recovery at all.
Jeanz Sensation said:
If your bootloader is unlocked officially then you can use either of the recoveries. But if the bootloader has been unlocked unofficially then strictly use SAFE TWRP if you are flashing MIUI ROM.
The main difference between SAFE and Alka is that Alka gives you the option to backup few more partitions within the phone's memory as compared to SAFE. Bear in mind that these extra partitions may not be necessary for you to backup, hence eliminating the need for Alka recovery at all.
Click to expand...
Click to collapse
Ok. Thanks.
I was unofficially unlocked. But after I flashed MIUI via edl method it got locked again. So then I officially unlocked it.
I guess I can keep alka then. Or?
Sent from my Redmi Note 2 using XDA-Developers mobile app
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
want know if i do Unlock Bootloader i will lose the update or no
No... You will lose nothing
typed through a vantablack POCOPHONE F1 using Tapatalk
tadtadros said:
want know if i do Unlock Bootloader i will lose the update or no
Click to expand...
Click to collapse
U will not lose update and stay on the same version. But you will lose all data and everything on the internal storage
if twrp is installed, do i lose the update feature?
zuhero said:
if twrp is installed, do i lose the update feature?
Click to expand...
Click to collapse
Twrp is a custom recovery only, why do you think the recovery would effect your updates any way if the unlocked bootloder wont..
shadow78 said:
Twrp is a custom recovery only, why do you think the recovery would effect your updates any way if the unlocked bootloder wont..
Click to expand...
Click to collapse
I thought xiaomi worked like samsung, once the knox is tripped, the system otas feature won't work...