Related
Hello. The subject matter says it all.
I currently have a rooted and unlocked AT&T Atrix on 1.26 version (yeah...still in ice age ) with a locked bootloader. Im with a non-US telco carrier. It came unlocked and rooted so that was great. No hassle but now I have started doing research on custom roms and webtop mods. I am trying to get around the info overload, so pls bear with my questions.
The overall goal is to have a stock/custom rom devoid of all the bloatwares and can run webtop2sd, and if that is not possible then, webtop. Very simple needs.
Option 1
======
To remain on stock rom and update to 1.83 version, and then to install the webtop2sd mod. Ideally I would like to boot off Debian from the microsd card. There was a post in which a forumer mentioned that he was able to "frankenstein" the webtop2sd and webtop mods. Thats great if I understood correctly.
Option 2
======
To update to 4.5.91 (probably a custom rom like Aura) and then install the webtop2sd/webtop mod.
What should be done?
I am going to update 1.26 -> 1.57 -> 1.83 -> 4.5.91 via system update. (which means I now have to signed with moto account...yes I have not as I read that there were some privacy issues.)
Through the update process, I would lose root. To keep everything clean, I am going to go through factory reset and then perform the update.
Once I am in 1.83 or 4.5.91, I will apply the root and unlock the bootloader. Which is the best way to go about this? Should I just follow the instruction here or this way. Or is there any other better way?
This is all I have for now until I install the webtop mod or the custom rom...
update your phone to wherever you want it at, then use this script to unlock the bootloader:
http://forum.xda-developers.com/showthread.php?t=1182871
after that, you can easily root your phone using the preinstall method found here:
http://forum.xda-developers.com/showthread.php?t=1138204 (second post)
if you update to 4.5.91 though, as you attempt to unlock the bootloader you will get a semi-hard brick, just have it boot up into fastboot mode and continue using the script. easy as pie!
I never got a semi-hard or *soft* brick from unlocking but that's just cause I must love to eat pudding =D . Do all the OTA updates, unlock / root, and then install the 2.3.4 fruitcake and install webtop. Best option by far, IMO, as far as the ease of transition goes. Should be cake. That's what I did and as long as you don't RSD lite with an .SBF back once on 2.3.4 OTA yer good to go.
eat yer fruitcake once updated to 2.3.4 OTA *stock gingerbread*-http://forum.xda-developers.com/showthread.php?t=1163009
Install a custom kernel if ya wanna overclock or undervolt, I would personally suggest Faux123's. -http://forum.xda-developers.com/showthread.php?t=1156040
aaand freeeze all that bloatware!-http://forum.xda-developers.com/showthread.php?t=972459
I read that its easier to update via SBF than OTA? What have your experiences been so far?
Alcapone263 said:
if you update to 4.5.91 though, as you attempt to unlock the bootloader you will get a semi-hard brick, just have it boot up into fastboot mode and continue using the script. easy as pie!
Click to expand...
Click to collapse
Maybe I should try to unlock it now... And then update.
tech_girl said:
I read that its easier to update via SBF than OTA? What have your experiences been so far?
Click to expand...
Click to collapse
well, i can't find it anymore but there is an SBF in the development forum that will allow you to update to 2.3.4 android without getting the brickable bootloader, but i personally don't see a point in using SBF. it's not meant for the end user, and using it can be risky.
SBF flashing is faster i believe, but as i said can also potentially harm your device if you're unsure of what you're doing.
SamCripp, one of the most esteemed devs here, suggests for the average person to completely stay away from sbf flashing after you've unlocked your bootloader unless you absolutely have to use it for something.
remember though, if you use the OTA update you CANNOT downgrade your device through SBF flashing, you HAVE to use the fruitcakes method. it WILL brick your device to downgrade, but only with the OTA update.
EDIT: and it's a semi-hard brick, it doesn't hurt your device in the least. you might panic at first, but it's as simple as booting into fastboot mode and finishing the script. or if you're more tech inclined, you can just do the fastboot oem unlock command through fastboot.
Phalanx7621 said:
....
eat yer fruitcake once updated to 2.3.4 OTA *stock gingerbread*-....
Click to expand...
Click to collapse
Alcapone263 said:
......
remember though, if you use the OTA update you CANNOT downgrade your device through SBF flashing, you HAVE to use the fruitcakes method.....
Click to expand...
Click to collapse
Fruitcakes??? All this jargon.... Hmmm...gotta check this out.
http://forum.xda-developers.com/showthread.php?t=1163009
yep, Fruitcakes. it's a CWM alternative to sbf flashing, much safer since it doesn't edit the bootloader at all, so there's no risk in hard bricking your device.
after you unlock your bootloader, you should install Romracer's CWM recovery here: http://forum.xda-developers.com/showthread.php?t=1204500
do all of your flashing through CWM after you unlock your bootloader, just remember to clear cache/dalvik/data between each ROM or you might get stuck in a bootloop.
Ok...CWM sounds more familiar....
If I understand correctly, I actually dont have to go via OTA. As long as I have the img file for flashing to each version, I could just use the CWM and not via OTA, right?
tech_girl said:
Ok...CWM sounds more familiar....
If I understand correctly, I actually dont have to go via OTA. As long as I have the img file for flashing to each version, I could just use the CWM and not via OTA, right?
Click to expand...
Click to collapse
well, you have to have an unlocked bootloader to get CWM. and to unlock your bootloader, you have to update to 1.8.3 or later.
after you unlock your bootloader, you can install CWM and proceed to just use CWM for your flashing needs.
i repeat again though, after you unlock your bootloader you should stay away from SBF flashing altogether. it's the quickest way to brick your device.
Alcapone263 said:
well, you have to have an unlocked bootloader to get CWM. and to unlock your bootloader, you have to update to 1.8.3 or later.
after you unlock your bootloader, you can install CWM and proceed to just use CWM for your flashing needs.
i repeat again though, after you unlock your bootloader you should stay away from SBF flashing altogether. it's the quickest way to brick your device.
Click to expand...
Click to collapse
+1
Once you unlock and get CWM installed its just a case of wiping the device and flashing zip files.
Yep after unlocking and getting rom racers cwm in, you get to have lots of fun and almost zero chance of hard bricking. Make sure you understand the pudding part. After you unlock throw rsd lite away.
After updating to 1.83 and unlocked, can I immediately installing a GB custom rom like Aura or Alien? Or do I need to update to 4.5.91 stock before I can install a custom rom? Which I assume is pre-rooted, which mean I dont have to root it..
tech_girl said:
After updating to 1.83 and unlocked, can I immediately installing a GB custom rom like Aura or Alien? Or do I need to update to 4.5.91 stock before I can install a custom rom? Which I assume is pre-rooted, which mean I dont have to root it..
Click to expand...
Click to collapse
You should be able to start flashing if you used pudding. No need to upgrade to .91 stock. I didn't. I think most roms are pre rooted now. Not that the rooting method was hard for the atrix.
I voided my warranty.
pukemon said:
You should be able to start flashing if you used pudding. No need to upgrade to .91 stock. I didn't. I think most roms are pre rooted now. Not that the rooting method was hard for the atrix.
I voided my warranty.
Click to expand...
Click to collapse
Yep thats how it works. once BL unlocked and CWM installed you can flash anything, including yes .91 stock.
Note that .91 stock OTA is not only the operating system but also modifies the bootloader hence all the hard brick warnings about flashing sbfs. When you flash zip files you don't touch the bootloader, so there is no chance of hard bricking. i.e. if you flash .91 stock from zip file from CWM as opposed to OTA, you get only the OS, not the bootloader update (which doesn't matter ).
After flashing this file 'Xperia_U_ST25i_Relock_Bootloader.ftf' to my Xperia_U, the phone won't boot again
I had to flash again with 'ST25i_6.0.B.3.184_O2-CZ.ftf' in order to get the phone working gain
This also made me lose Root, so I had to reflash again with 'Xperia_U_ST25i-ROOT-ROM.img'
(and unlocking again with fastboot.exe -i 0x0fce oem unlock 0xkey)
so, it seems there's no way of keeping the phone rooted and locking the bootloader
(I want to lock the bootloader locked in order to get updated to 184 though PC-Companion)
ssuper2k said:
After flashing this file 'Xperia_U_ST25i_Relock_Bootloader.ftf' to my Xperia_U, the phone won't boot again
I had to flash again with 'ST25i_6.0.B.3.184_O2-CZ.ftf' in order to get the phone working gain
This also made me lose Root, so I had to reflash again with 'Xperia_U_ST25i-ROOT-ROM.img'
(and unlocking again with fastboot.exe -i 0x0fce oem unlock 0xkey)
so, it seems there's no way of keeping the phone rooted and locking the bootloader
(I want to lock the bootloader locked in order to get updated to 184 though PC-Companion)
Click to expand...
Click to collapse
I own an Xperia S, I flashed a custom kernel to root then flashed back the stock kernel and locked the bootloader again, the phone works perfect and kept the root!
ssuper2k said:
After flashing this file 'Xperia_U_ST25i_Relock_Bootloader.ftf' to my Xperia_U, the phone won't boot again
I had to flash again with 'ST25i_6.0.B.3.184_O2-CZ.ftf' in order to get the phone working gain
This also made me lose Root, so I had to reflash again with 'Xperia_U_ST25i-ROOT-ROM.img'
(and unlocking again with fastboot.exe -i 0x0fce oem unlock 0xkey)
so, it seems there's no way of keeping the phone rooted and locking the bootloader
(I want to lock the bootloader locked in order to get updated to 184 though PC-Companion)
Click to expand...
Click to collapse
Too keep your phone rooted you need to keep its bootloader unlocked and if you try locking it again you might brick it!!
So if you want to keep your root and bootloader locked then here's what you should do
1)Unlock bootloader
2)Flash a custom kernel which roots your phone
3)Flash with stock rom
Note : if still not rooted then untick the option in flastool to skip flashing kernel when flashing with stock rom!!
Pls correct me if m wrong!!
Sent from my Sony Xperia Sola White using xda app
reptile64 said:
I own an Xperia S, I flashed a custom kernel to root then flashed back the stock kernel and locked the bootloader again, the phone works perfect and kept the root!
Click to expand...
Click to collapse
Thanks, so now I need confirmation from an Xperia_U owner..
Anyone flashed Xperia_U_ST25i_Relock_Bootloader.ftf' and the phone kept working?
.
What I want to keep is:
---------------------------------
Kernel: Xperia_SSpeed_kernel_v6.1.zip
ROM: KA03_Xperia_SSpeed.zip
Then, lock bootloader again, withOUT losing ROOT
and then update to 1.84 (via Companion)
ssuper2k said:
Thanks, so now I need confirmation from an Xperia_U owner..
Anyone flashed Xperia_U_ST25i_Relock_Bootloader.ftf' and the phone kept working?
.
What I want to keep is:
---------------------------------
Kernel: Xperia_SSpeed_kernel_v6.1.zip
ROM: KA03_Xperia_SSpeed.zip
Then, lock bootloader again, withOUT losing ROOT
and then update to 1.84 (via Companion)
Click to expand...
Click to collapse
You cannot update via pcc even with Locked BL if you have custom rom or kernel.
Sent from my LT26i using Tapatalk 2
gm007 said:
You cannot update via pcc even with Locked BL if you have custom rom or kernel.
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
So what the best way/order to update the phone to 1.84 and also get Root?
Thanks
I thought it was necessary to unlock the bootloader on android phones before i could root them and flash different roms. A buddy of mine had rooted his old s3 but forgot to unlock the bootloader, so when he tried restarting it, it soft bricked. For the longest time I thought you had to unlock the bootloader then root the phone in order to flash custom roms, have I been wrong all this time?
Think of the Loki workaround as a way to trick the bootloader into flashing improperly signed files. Its like using a credit card on the bolt of a locked door. The door is still locked but you get through anyway.
brizey said:
Think of the Loki workaround as a way to trick the bootloader into flashing improperly signed files. Its like using a credit card on the bolt of a locked door. The door is still locked but you get through anyway.
Click to expand...
Click to collapse
And what are the risks of using the loki tool if you use it correctly? if there is an OTA update to the phone, will it mess it all up?
You don't you the tool...the developers do. And technically, it is only used for flashing a recovery and flashing ROMS with the recovery. You can root without unlocking the bootloader because there is an pre-release official rootable kernel than can be flashed with Odin. It flashes because it is legit.
So I should be able to just go to the how to root page on here http://forum.xda-developers.com/showthread.php?t=2290798 and follow the instructions and flash one of the roms as usual?
yes,go ahead
Hello dear XDA Community,
- Xperia Z Ultra
- 4.4.2
- 14.3.A.0.681
- C6833
I have a big problem with understanding all of this tutorials. I read everything about rooting and unlocking the Bootloader.
I understood that I need to backup my TA Partition for Unlocking my Bootloader so I can continue to use Sony technology.
Requirements ? Root. Okay that was my first problem. So i looked up how to root my phone and what do i need ? A phone with a unlocked bootloader. great! Sure you can say "look at this topic and carefully read" but I really did that and I am really helpless. Thanks for any help!
What did I read ?
- http://forum.xda-developers.com/showthread.php?t=2292598&nocache=1 (requires root)
- http://forum.xda-developers.com/showthread.php?t=2569904 (requires unlocked bootloader)
- watched severel youtube videos and encountered the same problem
Greets
tr0teK
When your bootloader is unlocked, you can never use X-Reality and any other item which requires the DRM in the Trim Area partition,
Restoring the TA partition without relocking the bootloader will not result in the return of X-Reality and such even if you are using a Sony ROM. This situation appears to have changed since the release of 4.4.
Backing up the TA partition is only good for relocking the bootloader on a Stock ROM (any custom AOSP, CM, AOSPA etc will fail to boot on a locked bootloader), for personal choice or returning the phone under warranty.
You can unlock the bootloader when not rooted, in fact you don't do it with the phone running normally anyway so root or not rooted, it does not matter in that sense.
You don't need to unlock the bootloader to root, if you are willing to re-set up your phone again. What you need to do is downgrade to 4.2, which is rootable, root, install recovery and flash the 681 pre-rooted zip, and use flashtool to flash the associated ftf file to get rooted on 681.
Follow the instructions in Lord Manhattan's thread that you linked to,in order to downgrade and install a recovery, then visit the following link to get the zip & ftf to re-up to 4.4 (681). You most likely will lose cellular connectivity whilst you are downgraded (there is a way around this, but as you are only going down to 4.2 to get a recovery, maintaining your IMEI for that short period of time is just a waste of effort), but it will return when you are back on 681 (4.4).
http://forum.xda-developers.com/showthread.php?t=2687848
- Downgrade to 532
- Root it using Bin4ry's tool
- Backup the TA partition
- Unlock bootloader
- Either update to 681 again and take it from there or flash a kernel with recovery/TWRP and flash a pre-rooted 681. It's easy to root 681, so whatever floats your boat.
Don't mean to hijack this topic but I don't want to open another thread,
if I back up the TA partition, unlock bootloader, root the phone, then relock bootloader, then restore TA partition to bring back the xreality,
I am not going to install custom recovery and Roms.
Thanks for the Informations. I will give it a try the next days and report you if it worked.
coolmingli said:
Don't mean to hijack this topic but I don't want to open another thread,
if I back up the TA partition, unlock bootloader, root the phone, then relock bootloader, then restore TA partition to bring back the xreality,
I am not going to install custom recovery and Roms.
Click to expand...
Click to collapse
Technically it'll work, but i have never done it before. Everything should go smoothly until you're going to re-lock the bootloader. You can't re-lock it on a custom kernel, and you'll be on a custom kernel once you flash Jackie's kernel with recovery, so you'll have to flash a complete stock kernel, then restore the TA partition with the TA Backup Tool, which will also automatically re-lock the bootloader. You should in theory end up with a complete stock ROM with root. That's on paper.
Worst case scenario? If you re-lock the bootloader while you're on a custom kernel, it'll explode it won't power on at all, and all you'll get is a blinking red LED and death. To fix this, just unlock the bootloader in Flashtool again and you're back to start again. It's not dangerous, but it's nerve wrecking to see it there, just blinking without any sign of life. I almost crapped my pants the first time i experienced it, and had no clue what was happening or what to do.
LordManhattan said:
Technically it'll work, but i have never done it before. Everything should go smoothly until you're going to re-lock the bootloader. You can't re-lock it on a custom kernel, and you'll be on a custom kernel once you flash Jackie's kernel with recovery, so you'll have to flash a complete stock kernel, then restore the TA partition with the TA Backup Tool, which will also automatically re-lock the bootloader. You should in theory end up with a complete stock ROM with root. That's on paper.
Worst case scenario? If you re-lock the bootloader while you're on a custom kernel, it'll explode it won't power on at all, and all you'll get is a blinking red LED and death. To fix this, just unlock the bootloader in Flashtool again and you're back to start again. It's not dangerous, but it's nerve wrecking to see it there, just blinking without any sign of life. I almost crapped my pants the first time i experienced it, and had no clue what was happening or what to do.
Click to expand...
Click to collapse
Thanks for the reply, I think I will ditch rooting from this phone, too much troubles, I don't understand why Sony put the DRM key in a trim partition, perhaps they don't want us to root the phone after all.
I did it guys. It worked!
My steps:
- Downgraded to 4.2.2 with Flashtool (.532)
- Rooted with Bin4ry's tool
- Installed CWM and TWRP Dual Recovery for Xperia Z locked Bootloader by krabappe12548
- Flashed to 4.4.2[rooted] (http://forum.xda-developers.com/showthread.php?t=2687848)
Now I have the newest version with Root Access. Everything works great
Greets
tr0teK
tr0teK said:
I did it guys. It worked!
My steps:
- Downgraded to 4.2.2 with Flashtool (.532)
- Rooted with Bin4ry's tool
- Installed CWM and TWRP Dual Recovery for Xperia Z locked Bootloader by krabappe12548
- Flashed to 4.4.2[rooted] (http://forum.xda-developers.com/showthread.php?t=2687848)
Now I have the newest version with Root Access. Everything works great
Greets
tr0teK
Click to expand...
Click to collapse
is this witout unlock the bootloader?
MjsNL said:
is this witout unlock the bootloader?
Click to expand...
Click to collapse
Yep, that will work well on a locked BL
If you are only downgrading to flash the current rooted firmware, you don't even need to root 532, as [nut]'s dual recovery can be installed by the same method that bin4ry's root is delivered, just install the recovery, flash the zip, flash the ftf and away you go
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