Hi
help me how to install .bin file
Standin.Weed said:
Hi
help me how to install .bin file
Click to expand...
Click to collapse
If you are asking this question (with no additional detail) you are in no position to be messing with this device. Mostly likely end up bricking it. There is a ton of information in these forums. Spend some time reading.
Davey126 said:
If you are asking this question (with no additional detail) you are in no position to be messing with this device. Mostly likely end up bricking it. There is a ton of information in these forums. Spend some time reading.
Click to expand...
Click to collapse
I have the kindle fire hdx 7 13.3.2.4 and I also have file:
mod-update-kindle-thor-13.3.2.8_user_713328020.bin
I do not know how to manually install this file
these words are translated by google because I have bad english
I don' know what you're up to, on 3.2.4 I'd suggest to downgrade to 3.1.0, install TWRP, update the bootloader to 3.2.3.2, unlock the bootloader. and use ROM of your choice.
3.2.8 would remove this option - probably forever. You can NOT downgrade below 3.2.8 once you're on 3.2.8 or higher due to rollback protection by Amazon (attempt would brick the device!).
Cl4ncy said:
I don' know what you're up to, on 3.2.4 I'd suggest to downgrade to 3.1.0, install TWRP, update the bootloader to 3.2.3.2, unlock the bootloader. and use ROM of your choice.
3.2.8 would remove this option - probably forever. You can NOT downgrade below 3.2.8 once you're on 3.2.8 or higher due to rollback protection by Amazon (attempt would brick the device!).
Click to expand...
Click to collapse
teach me how to install 13.3.1.0 install TWRP, update the bootloader to 3.2.3.2
Ok, listen - this is NOT for the faint of heart, 'cause it comes with a certain likelihood to brick the HDX, so if in doubt leave it be!
I'll give you all the info to read, you must understand what you have to do. If in doubt, ask before you brick your HDX!
First of all the easiest way (and this won't get any easier) is to root with HDX Toolkit, and install Safestrap v3.75 - if you haven't done it yet. Be sure to know what you're doing with rooting and Safestrap! Note that factory reset means the standard wipe only! Do NOT go into advanced wipe! Do NOT wipe System!
You can use the downgrade images provided by @ggow then, check page 2 her (page 1 is about 3.2.5/3.2.6 users who can NOT use those images).
After the downgrade to 3.1.0 you won't have Safestrap anymore, so you can Flash TWRP (either via adb or Flashify, if you use the latter be sure to backup the stock recovery, and to flash the image to the recovery partition!). Update the bootloader to 3.2.3.2 via TWRP then (TWRP can be accessed by pressing and holding both Power and Vol Up buttons during power on, release both when the grey Kindle Fire logo appears on screen).
Unlock the bootloader with the one click solution, if it fails, we'll have to do it the hard way, i.e. manually.
After unlocking you can use the available ROMs, i.e. CM11, CM12, SlimLP, Nexus or the (still in beta stage) new CM13.
Happy reading.
Be sure to Keep WLAN off/flight mode active so you won't get updated by Amazon!
Cl4ncy said:
Ok, listen - this is NOT for the faint of heart, 'cause it comes with a certain likelyhood to brick the HDX, so if in doubt leave it be!
I'll give you all the info to read, you must understand what you have to do. If in doubt, ask before you brick your HDX!
First of all the easiest way (and this won't get any easier) is to root with HDX Toolkit, and install Safestrap v3.75 - if you haven't done it yet. Be sure to know what you're doing with rooting and Safestrap! Note that factory reset means the standard wipe only! Do NOT go into advanced wipe! Do NOT wipe System!
You can use the downgrade Images provided by @ggow then, check page 2 her (page 1 is about 3.2.5/3.2.6 users who can NOT use those images).
After the downgrade to 3.1.0 you won't have Safestrap anymore, so you can Flash TWRP (either via adb or Flashify, if you use the latter be sure to backup the stock recovery, and to flash the image to the recovery partition!). Update the bootloader to 3.2.3.2 via TWRP then (TWRP can be accessed by pressing and holding both Power and Vol Up buttons during power on, release both when the grey Kindle Fire logo appears on screen).
Unlock the bootloader with the one click solution, if it fails, we'll have to do it the hard way, i.e. manually.
After unlocking you can use the available ROMs, i.e. CM11, CM12, SlimLP, Nexus or the (still in beta stage) new CM13.
Happy reading.
Be sure to Keep WLAN off/flight mode active so you won't get updated by Amazon!
Click to expand...
Click to collapse
I do not know to do this step:
cuberHDX from here: http://forum.xda-developers.com/showpost.php?p=58864282&postcount=46
then open another DOS box, change dir to your Python Directory with the .py script (enter cd\python27 or whatever the path of your Python directory is), then
python.exe cuberHDX.py 0xmmssssssss
with mm being the last two digits of your ID, and the ssssssss being your serial, the script should create the .unlock file then.
So assuming the numbers you mentioned are correct the python command would be
python.exe cuberHDX.py 0x45f0bf7e1d
Copy/move the .unlock file to your ADB directory then, open another DOS box for the adb reboot-bootloader command, and yet another DOS box for the fastboot commands (change dir cd\adb both times before you enter the adb & fastboot commands):
fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
fastboot -i 0x1949 reboot
this is not have to be?
That's the manual unlock procedure. Try the one-click-solution mentioned above first, should be a lot easier.
Cl4ncy said:
That's the manual unlock procedure. Try the one-click-solution mentioned above first, should be a lot easier.
Click to expand...
Click to collapse
Hi cl4ncy!
I can not unlock bootloader one lick and manual. See my picture:
http://www.upsieutoc.com/images/2016/01/21/12420d.png
http://www.upsieutoc.com/images/2016/01/21/29b3da.png
it just stops here although I did all the steps
Standin.Weed said:
Hi cl4ncy!
I can not unlock bootloader one lick and manual. See my picture:
http://www.upsieutoc.com/images/2016/01/21/12420d.png
http://www.upsieutoc.com/images/2016/01/21/29b3da.png
it just stops here although I did all the steps
Click to expand...
Click to collapse
Using the manual unlock procedure, try these drivers, if possible with Win7 (could be a pain in the ass to install them in Win8/10 x64). Should fix the "Waiting for device" issue.
Cl4ncy said:
Using the manual unlock procedure, try these drivers, if possible with Win7 (could be a pain in the ass to install them in Win8/10 x64). Should fix the "Waiting for device" issue.
Click to expand...
Click to collapse
tks you so much.
I did all :laugh:
Standin.Weed said:
tks you so much.
I did all :laugh:
Click to expand...
Click to collapse
You're welcome - enjoy your "free" HDX.
Related
Well Guys,
I finally got my hands on my dream phone, the N1. Hope this guide helps some n00bs out there like me.
Here is how to unlock the bootloader, root and install clockworkmod on the baby.
DISCLAIMER
I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE AND THIS WILL VOID YOUR WARRANTY AND ALSO WIPE ALL YOUR DATA TO FACTORY SETTINGS.
CREDITS
TO ALL THE VARIOUS WEBSITES WHERE I READ ALL THE INFORMATION MENTIONED BELOW. NONE OF THE BELOW IS MY WORK AND I TAKE NO CREDIT FOR IT.
HATS OFF
To all the developers who made this possible. superboot is work of Paul from Modaco, clockworkmod is work of Koush.
Step - 001
Install Android SDK from here.
Step - 002
Connect your phone to the PC using the data cable provided. If the drivers are installed successfully well and good, else download the one's from here and point windows to the folder where you extract the above drivers.
Step - 003
Open
Code:
settings - about
and note down the build number
Step - 004
Download Superboot from here depending on the build number noted above.Extract the archive to a folder.
Step - 005
Turn off the phone, boot into bootloader mode [press track ball and after that press the power button]
The phone will go into download mode. Connect USB Cable.
Navigate to the folder of superboot above using Windows command prompt.
Issue the following command
Code:
fastboot-windows devices
If this line does not return anything, do not continue: Your computer does not detect your Nexus.
Unlocking the Bootloader(this will void the warranty and also do a factory reset)
Code:
fastboot-windows oem unlock
The phone will display a warning, use the volume up down button to toggle between yes and no, we need to select yes, once yes is selected press the power button to confirm your decision.
The phone will reboot.
if you get the following error
FAILED <command write failed <Too many links>> error
ignore it and try giving the oem unlock command again and it should say bootloader already unlocked. Do not proceed until your bootloader has been unlocked.
Rooting
Boot the phone into bootloader mode. naviagte to the "superboot" folder in windows explorer. Double click the file "install-superboot-windows.bat" and viola you are rooted.
Installing recovery (I used clockworkmod, you can also use AmonRA)
Download the latest CWM from here, download the .img file and once downloaded check the md5 with the one on the link above. (passion is the name for Nexus One).
Put the above downloaded .img file in the 'superboot' folder and rename it to a simple name say "cwm.zip" (without the quotes)
Boot the phone into bootloader mode again.
Navigate to the superboot folder from Windows command prompt.
Issue the following command
Code:
fastboot-windows flash recovery cwm.img
You are now rooted and have installed ClockworkMod recovery.
I would advice you to flash a new custom ROM right away, do not boot into the stock ROM as it would end up breaking CWM. In case you want to be on stock ROM and still have recovery you need to do the following.
Boot into the stock ROM.
Connect USB.
Navigate to the superboot folder.
Give the following commands.
Code:
adb-windows shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
Now flash CWM again as described in the step above.
How to boot into CWM when phone is switched off.
press the volume power down button and while it is pressed press the power button.
The phone will boot into a white screen, wait for some time (7-8) seconds, some checks will take place, once those checks are complete use the volume buttons to go to recovery option and use the power button to select and you are into ClockworkMod.
Moderators Please move this to correct section if I posted in the wrong section.
Excellent post! Thanks for taking the time to put it together, i could've done with this a few months ago when i first got my n1... Nice one
tina333 said:
Excellent post! Thanks for taking the time to put it together, i could've done with this a few months ago when i first got my n1... Nice one
Click to expand...
Click to collapse
thanks a lot , have been waiting all day for a feedback and finally I got one .
Good one ..
siddharthsai said:
Good one ..
Click to expand...
Click to collapse
Thanks man .. it's an honor to get a nod from you ...
i guess unlocking the bootloader is very conventional..
no one unlocks the bootloader now....
there are many direct rooting methods available including one click root , universal androot, superoneclick etc, where we can root and also unroot afterwards thus the warranty is not void..
but in unlocking bootloader warranty is void and is also not very safe method .
while other methods are extremely safe, requires only one click...
you should have researched before unlocking the bootloader.
though you are from india like me so warranty void is no criteria as nexus one is not sold here officialy.
abhi0n0nakul said:
i guess unlocking the bootloader is very conventional..
no one unlocks the bootloader now....
there are many direct rooting methods available including one click root , universal androot, superoneclick etc, where we can root and also unroot afterwards thus the warranty is not void..
Click to expand...
Click to collapse
Precisely.
Although I never heard of HTC denying warranty(with unlocked bootloader), unlocking the bootloader is not necessary.
Just start with Rooting(super one click, or z4root), install recovery with adb or android shell, and go from there.
abhi0n0nakul said:
i guess unlocking the bootloader is very conventional..
no one unlocks the bootloader now....
there are many direct rooting methods available including one click root , universal androot, superoneclick etc, where we can root and also unroot afterwards thus the warranty is not void..
but in unlocking bootloader warranty is void and is also not very safe method .
while other methods are extremely safe, requires only one click...
you should have researched before unlocking the bootloader.
though you are from india like me so warranty void is no criteria as nexus one is not sold here officialy.
Click to expand...
Click to collapse
I guess it depends what you want your device to ultimately be capable of doing.... Being a person who has also researched... I personally needed to unlock the bootloader to flash a custom rom, although rooting is a vital aspect when customising devices, if you want to maximise the potential then sometimes voiding warrantee's is to be expected (note there are also ways and means of reverting most mods back to factory standard if needed )
Each to their own
Well it was my personal choice to unlock the bootloader, I wanted to do it just for the heck of doing it
The tutorial was made so as to help others and that is why "the void warranty" thing was mentioned in bold and red.
I was aware of methods which will root and not void the warranty but I wanted to "void the warranty" as we do not have it in India and yes the main reason was custom ROMS, my first phone the Samsung Spica (still own it) ran stock ROM for only a month and the N1 ran a stock for only 12 hours ...
tina333 said:
I guess it depends what you want your device to ultimately be capable of doing.... Being a person who has also researched... I personally needed to unlock the bootloader to flash a custom rom, although rooting is a vital aspect when customising devices, if you want to maximise the potential then sometimes voiding warrantee's is to be expected (note there are also ways and means of reverting most mods back to factory standard if needed )
Each to their own
Click to expand...
Click to collapse
can you tell me what things the rooted bootloader unlocked device can do that rooted bootloader locked device cant????
munchy_cool said:
Thanks man .. it's an honor to get a nod from you ...
Click to expand...
Click to collapse
LOL, I'm just like everyone else... anyways hard work should always be appreciated.
abhi0n0nakul said:
can you tell me what things the rooted bootloader unlocked device can do that rooted bootloader locked device cant????
Click to expand...
Click to collapse
well, for one thing... the methods to soft-root exploit software issues which are quite often patched...
Here is a thread showing how to LOCK the bootloader on n1 again.
http://forum.xda-developers.com/showthread.php?t=934965
[WIP] Nexus One - S-OFF (locking bootloader again)
Thanks, Please edit the link do download the CWM recovery by using this latest link from the Cyanogenmod Servers
http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.0.5-passion.img
Click to expand...
Click to collapse
Or By now linking this guide to the Nexus One Cyanogenmod Wiki where a full and updated tutorial is posted.
Thanks
I have a functioning but not up to date setup:
Apollo Nexus v2.0.1 which is unfortunately in the stock slot of Safestrap v3.75, no other ROM slots and previous FireOS backup leaves screen blank (boots and ADB accessible).
(The backstory to this: some update had gone wrong at the end of last year I this status is all I could manage to get to a functioning state.)
Now I would like to move to unlocked bootloader, TWRP and CM12.1
I tried to unlock the bootloader using the method with cuberHDX posted in other threads but in fastboot after
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
I am getting
FAILED (remote: Unlock code is NOT correct)
I don't know what seems to be the problem. After the messy "fixes" from the end of last year I cannot quite remember which was the last version of the FireOS (and hence the bootloader that came along with it) that was installed.
--> Can anyone tell me how to find out the version of the bootloader?
Any other suggestions how to get out of my non-upgradeable situation? Any help greatly appreciated.
scaftogy said:
I have a functioning but not up to date setup:
Apollo Nexus v2.0.1 which is unfortunately in the stock slot of Safestrap v3.75, no other ROM slots and previous FireOS backup leaves screen blank (boots and ADB accessible).
(The backstory to this: some update had gone wrong at the end of last year I this status is all I could manage to get to a functioning state.)
Now I would like to move to unlocked bootloader, TWRP and CM12.1
I tried to unlock the bootloader using the method with cuberHDX posted in other threads but in fastboot after
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
I am getting
FAILED (remote: Unlock code is NOT correct)
I don't know what seems to be the problem. After the messy "fixes" from the end of last year I cannot quite remember which was the last version of the FireOS (and hence the bootloader that came along with it) that was installed.
--> Can anyone tell me how to find out the version of the bootloader?
Any other suggestions how to get out of my non-upgradeable situation? Any help greatly appreciated.
Click to expand...
Click to collapse
Unfortunately, there is no reliable method to determine bootloader version. If you are confident in the steps you are taking to unlock the bootloader the your system may have upgraded past 3.2.3.2 which is the last version that contains the vulnerability that the unlock exploit leverages. You could try one of the Safestrap Flashable HDX Stock Images (suggest v3.2.6 for greatest compatibility) in the stock slot but this could result in a brick if everything doesn't line up properly. Not sure it is worth the risk given your device may have other lingering issues from the previous update attempt gone bad. Nexus v2 is still highly functional; you can safely update that to v2.05 and add a few Xposed modules to acheive a near KitKat experience.
OK, I was afraid that there wasn't any way to determine the bootloader version. Thanks for the clear answer.
Given that the state of my kindle HDX is somewhat complicated I agree that trying something like flashing a stock rom seems rather risky. I just needed someone else to confirm that.
I am fairly confident about the steps I took with cuber and the bootloader unlocking procedure (on linux VM which I use regularly). I am also 98% sure I never let FireOS update. Doing a bit more digging, I found that I have kept all files that I used for flashing last year. There are the following (relevant) files in that folder:
update-kindle-14.3.1.0_user_310079820.bin
update-kindle-14.3.2.4_user_324002120.bin
prerooted14.3.1.0.zip
Safestrap-Apollo-3.75-os3.2.4-B02.apk
apollo-nexus-rom-v2.0.1.zip
That leads me to believe that the bootloader should be version .3.2.4
Now I am a bit confused whether the version .3.2.4 should be unlockable. @Davey126, you wrote that the last one was .3.2.3.2. However the original thread by @dpeddi states in first post:
dpeddi said:
- Bootloader shipped with firmwareversion 1[34].3.1.0 <= x <= 1[34].3.2.4 (as we use the rsa bug)
Click to expand...
Click to collapse
Could anyone please confirm which one is actually the last version of the bootloader that can be unlocked?
scaftogy said:
OK, I was afraid that there wasn't any way to determine the bootloader version. Thanks for the clear answer.
Given that the state of my kindle HDX is somewhat complicated I agree that trying something like flashing a stock rom seems rather risky. I just needed someone else to confirm that.
I am fairly confident about the steps I took with cuber and the bootloader unlocking procedure (on linux VM which I use regularly). I am also 98% sure I never let FireOS update. Doing a bit more digging, I found that I have kept all files that I used for flashing last year. There are the following (relevant) files in that folder:
update-kindle-14.3.1.0_user_310079820.bin
update-kindle-14.3.2.4_user_324002120.bin
prerooted14.3.1.0.zip
Safestrap-Apollo-3.75-os3.2.4-B02.apk
apollo-nexus-rom-v2.0.1.zip
That leads me to believe that the bootloader should be version .3.2.4
Now I am a bit confused whether the version .3.2.4 should be unlockable. @Davey126, you wrote that the last one was .3.2.3.2. However the original thread by @dpeddi states in first post:
Could anyone please confirm which one is actually the last version of the bootloader that can be unlocked?
Click to expand...
Click to collapse
You need a version below 3.2.4, i.e. 3.2.3.2 or lower.
But the good news is, if you are on 3.2.4 you can use the rollback image provided by @ggow. Take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the rollback images).
Cl4ncy said:
You need a version below 3.2.4, i.e. 3.2.3.2 or lower.
But the good news is, if you are on 3.2.4 you can use the rollback image provided by @ggow. Take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the rollback images).
Click to expand...
Click to collapse
I am on @ggow's CM12.1 now! :victory:
Rolled back with this to .3.0.9, upgraded to stock .3.1.0, rooted, unlocked bootloader, flashed TWRP, and finally flashed CM12.1. Thanks so much for the hint to roll back!
To come full circle to the original question: Determining the version of the bootloader is not possible from adb or fastboot. If you don't know which version of the bootloader you have, it can help to try to find out which roms / updates you flashed before. In my case I had a folder on my PC that showed I must have had .3.2.4.
Due to a bug, I have been able to get root on my OnePlus 2 running Oxygen 2.1.1 without a wipe.
DISCLAIMER: This may not give you root on yours, and obviously it may also loose you data, so don't do it unless you know you can cope with that. YMMV, but I've documented here for posterity how to do it!
I had unlocked the bootloader previously, because my device is an import, so it is possible, though unlikely that it simply doesn't wipe on an unlock after re-lock (OTA locks bootloader).
The basic steps are :
Encrypt your device
Unlock the bootloader (this won't wipe because of encryption!)
Boot TWRP
use adb to push SuperSu to your device and then flash it
Then you will have root. Step by step instructions below.
Note that TWRP currently doesn't support encryption on our devices, so you'll have to use something other than that to back up your data if you want to use a custom rom. This simply gives you rooted stock Oxygen.
After rooting :
Code:
$ adb shell
[email protected]:/ $ su
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
Step 1: Encrypt your device.
This is irritating but fairly simple. You have to have fully charged your device AND keep it plugged in, and it takes ~50 minutes to complete. It's the standard android encryption, so follow any guide for this, such as https://support.google.com/nexus/answer/2844831?hl=en-GB
Step 2: Unlock the bootloader.
Again, this is well documented - here's a guide : http://forum.xda-developers.com/oneplus-2/general/guides-how-to-guides-beginners-t3146568 - The important thing is that if you're encrypted, this does not do a wipe, in my experience.
Step 3: Boot TWRP
Download TWRP from https://dl.twrp.me/oneplus2/ and save it somewhere you can find it later - I'm going to assume you're on linux and have saved it in ~/Downloads/TWRP.img
Reboot into bootloader mode (Power and Volume up) and start TWRP by issuing the following command (substituting your path to twrp) :
Code:
~$ fastboot boot Downloads/twrp-2.8.7.0-oneplus2.img
Step 4: Root it!
This is a bit tricky because once you're encrypted you can't access the SDCard, so you need a bit of magic to flash the zip.
First, do the swipe to enable modifications, then in mount, tick the /system option.
Then, on your PC, download SuperSU's .zip update from https://download.chainfire.eu/696/supersu/ (similar to above, assuming same download location) and use adb push to put it on the device in /tmp :
Code:
adb push Downloads/UPDATE-SuperSU-v2.46.zip /tmp/su.zip
Next, from the main TWRP menu, select Install. Navigate up (you start in sdcard that is empty) and into tmp, then select the su.zip file in there.
Swipe to install the zip - TWRP will complain because it can't access /data, but handily, /data is not needed to root!
Select Reboot, and viola, you have SuperSU and root! Now you can install Titanium Backup and back up your device.
Cool, perhaps renaming the title like "Unlock and root without wiping" could make more sense?
ranyardm said:
I had unlocked the bootloader previously, because my device is an import, so it is possible, though unlikely that it simply doesn't wipe on an unlock after re-lock (OTA locks bootloader).
Click to expand...
Click to collapse
OTAs don't re-lock the bootloader though...
If you've unlocked it previously, it'll stay unlocked unless you boot into fastboot mode and do a "fastboot oem lock".
Spannaa said:
OTAs don't re-lock the bootloader though...
If you've unlocked it previously, it'll stay unlocked unless you boot into fastboot mode and do a "fastboot oem lock".
Click to expand...
Click to collapse
Not true I'm afraid. The OP2 OTA to 2.1.0 did indeed relock the bootloader. I know this because I would never want to lock the bootloader, and I'm on a Chinese OP2 which came with masses of spyware, so to install clean 2.0.1 I had to unlock the bootloader originally (they managed to get the spyware into the recovery image!). Anyway, it's irrelevant to this thread how the bootloader got relocked, I just documented this fiddly way of getting an unlocked bootloader with root on a locked OP2.
ranyardm said:
Not true I'm afraid. The OP2 OTA to 2.1.0 did indeed relock the bootloader. I know this because I would never want to lock the bootloader, and I'm on a Chinese OP2 which came with masses of spyware, so to install clean 2.0.1 I had to unlock the bootloader originally (they managed to get the spyware into the recovery image!). Anyway, it's irrelevant to this thread how the bootloader got relocked, I just documented this fiddly way of getting an unlocked bootloader with root on a locked OP2.
Click to expand...
Click to collapse
Maybe my post should have said "OTAs don't re-lock the bootloader since 2.1.0"
Anyway, if your method works then great :good:
There's another way to do it here.
Can everyone who's done this attest that the data indeed doesn't get wiped?
cheekrox said:
Can everyone who's done this attest that the data indeed doesn't get wiped?
Click to expand...
Click to collapse
I'd also be very happy to have this confirmed by another party!
Confirmed. Data does NOT get wiped.
cheekrox said:
Confirmed. Data does NOT get wiped.
Click to expand...
Click to collapse
Confirmed on 2.2.0 or still on 2.1.X?
Can confirm, this still works on 2.2.0.
i didnt try this tutorial, but when i rooted my phone, my data didnt got wiped either.
will root on 6p running android n dev preview wipe phone?
Any chance this works also on 1+1? I'm desperate for a way to root without unlocking so I can install titanium/nandroid and do a full proper backup before wiping clean (battery life is utter crap). Running latest stock 6.01 COS. Never unlocked, never wiped since 15R.
Thanks!
anyone tried this on OOS 3 ?
Yeah, bump!
Now my OP2 is on Oxygen 3.0.2, and Android 6.0.1 - stock.
My phone had always been (bootloader) unlocked and rooted, since the day after I got it.
But to get the new OTA update to Oxygen 3, I tried a different method this time, where some people said you can do a temporary un-root, get the stock OTA update, and then re-root.
I followed their instructions, but I can't re-root as simple and easy as they said.
Before the process, I didn't do a nandroid backup because my sdcard doesn't have room :-|
So now I need to re-root without losing data.
And I've tried helium before, many times, and it never works for me.
Any other ideas, or has anyone tried this encryption trick yet with Oxygen 3?
Thanks!
tried it on oos 3.1:
everything worked until a bootloop at the last restart.
also twrp asked me to unlock the phone, i did that.
what to do now?
Did anyone ever have any success with this approach on 3.1?
LoL How do you boot/flash TWRP on locked bootloader?
aIecxs said:
LoL How do you boot/flash TWRP on locked bootloader?
Click to expand...
Click to collapse
Lol, you can't.
I saw someone mention bootloader unlock was only possible on .3.2.8 and earlier, but to my knowledge it was only .3.2.4 and earlier because it accepted the forged signatures. Is it possible from 13.3.2.5?
Good news is you can downgrade to unlock, bad news is, it's a bit tricky.
Check this thread, scroll down to the procedure for 3.2.5/3.2.6 users!
Make sure you understand all points of the procedure, if in doubt ask first, i.e. before you brick your HDX.
After you downgraded to 3.1.0 be sure to re-root (if required, HDX Toolkit here, also good to disable OTA updates), then you can unlock (try the one click solution first - might require the PDANet drivers), install TWRP 3.0.0-1, and use the ROM of your choice, create a backup of your current system before you flash anything though. It is recommended to update the bootloader to 3.2.3.2.
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