[GUIDE]Unlocking, Rooting, Adding CWM, Customizing XPERIA S 6.1.A.2.45 Stock ROM

[GUIDE]Unlocking, Rooting, Adding CWM, Customizing XPERIA S 6.1.A.2.45 Stock ROM - Sony Xperia S, Acro S, Ion

Note: All the methods used here not belongs to me,
ALL CREDITS GOES TO ITS MAKERS
Here I am giving you some external threads and some guide lines explaining how to unlock,root,adding Recovery, Flashing Custom ROMS and How to unroot, locking bootloaders to get official OTA updates..
Lets start with usual warning, I'm not responsible if your Xperia S gets bricked
[UNLOCKING BOOTLOADER]
There is a great thread explaining how to unlock and relock bootloader by DooMLoRD, its very useful and I tested it and worked perfectly.Here is the link,
UNLOCKING AND RELOCKING BOOTLOADER XPERIA S
If you found its useful don't forget to thank him.
[ROOTING XPERIA S WITH 6.1.A.2.45]
Here I will give you two methods,
FIRST METHOD
This is for unlocked bootloader only and only for Xperia S LT26i. I have tested and working perfectly in my SXS
Warning: This is Exclusively for Xperia S with 6.1.A.2.45. I am not sure about other Other ROMS
Before Rooting you must have downloaded this,
1.Root Kit.zip (Zip containing everything you wanted to root)
2.Flashable SuperSU App (Thanks to Chainfire )
Inside the folder you have one .txt file its the commands you have to use in cmd, Any how I am adding the same below,
1.You must have enabled USB debugging in developer option under settings
2.Copy the "CWM-SuperSU-v0.96.zip" into your SD card
3.Switch off and connect your phone in fast boot mode (pressing Power button + Vol up)
If asked for drivers, update driver manually by directing to "USB driver folder" inside the "Root Kit folder".
Verify whether there is a BLUE LED is coming up.
Now you are in fastboot mode, type the commands line by line,
fastboot devices
Click to expand...
Click to collapse
you will get something like this,
PSDN: DW925S3BFT&POI fastboot
Click to expand...
Click to collapse
Now type this,
fastboot flash boot recovery-nozomi.img
Click to expand...
Click to collapse
you will be seeing this,
sending 'boot' (5414 KB)...
(bootloader) USB download speed was 9847kB/s
OKAY [ 0.579s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00002000-0x0000bfff
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.851s]
finished. total time: 2.432s
Click to expand...
Click to collapse
so the recovery image is flashed into the phone, now reboot device using below command,
fastboot reboot
Click to expand...
Click to collapse
Now the phone will boot into recovery mode and select the option “Install zip from SDCard”. Browse to the folder where you had copied the SU zip file (CWM-SuperSU-v0.96.zip), select it and install it.
Now select the “Reboot System” option and while it is booting press the VOL UP button to boot back into the fastboot mode. Now run
fastboot flash boot kernel.sin
Click to expand...
Click to collapse
You should see something like this
sending 'boot' (5590 KB)...
(bootloader) USB download speed was 9588kB/s
OKAY [ 0.612s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00002000-0x0000bfff
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 2.976s]
finished. total time: 3.589s
Click to expand...
Click to collapse
If its showing with "Okay and Finished", then you are done, Congrats now you have a rooted phone (check for SuperSU app inside the phone drawer)Note:
1.If you can't enter into fastmode after image flashing (sometimes you need to have a better timing to enter into flashmode during reboot by pressing vol up and power button), then do this,
Press power and volume up button till u get a vibration followed by three vibrations (now your phone is switched off, so you can enter into fastboot normally) IMPORTANT: Dont remove the usb cable ever till rooting finishes
2.If any step fails after flashing recovery image you can't able to enter into your phone, don't be panic we have solution for everything.
Flashing stock rom with flashtool will solve this issue.
SECOND METHOD
Follow thread here,
Root with Recovery by Bin4ry
Note:
It's the easiest method, but every time i tried, i am doing it wrongly, but you can use this as well for rooting.Don't forget to thank Bin4ry
[ClockWorkMod Recovery]
If you want to know "why recovery is need?" go through some search .
For stock Roms
Just download this and enjoy recovery.
RecoverX by LEDelete. Don't forget to thank him.
[Flashing Custom ROMs]
You will get a variety of Custom ROMs available for XSX, choose what you are in need of, am here adding some Custom ROMs and there respective links (but its not the end, there are many more search it)
10/03/2012 - KA15 Xperia SSpeed released|Stablity update|Smooth & Fast|4.0.4 | Direct Link
10/03/2012 - KA02 Xperia SSpeed released! Modded stock rom|Smooth & Fast | Direct Link
10/02/2012 - [AOKP][JB] Xperia S | Direct Link
09/30/2012 - [DEVELOPMENT] - CM9.1 | Direct Link
09/30/2012 - Erachter ROM v4.1 | Very smooth | Good battery life | Direct Link
09/28/2012 - [email protected] Rom v5.2 [Simple, Clean & Fast] | Bug Free and battery friendly | Jelly Bean Animation | Direct Link
09/27/2012 - [ICS] XcreaM-3.2 | Stable Highly and easily customizable | Direct Link
09/15/2012 - MIUI 2.9.14 | Direct Link
09/07/2012 - [Xperia S][ICS] ExtremeICSrom v3 [Fast & Smooth] | Direct Link
05/01/2012 - Ultimate Xperience™ |[UICSv1.0] | [USensev1.0] | Direct Link
Note: Don't forget to thank the authors
[CWM in Custom ROMs]
Mostly in all Custom ROms there are recoveries but rarely we can't find in some ROMs, for that you have to download the flashable recovery zip along with the ROMs, If you forget to do a recovery flash and you are unable enter recovery mode don't be panic, remember we have solutions everything, just go through this forum to know about doing recovery through PC.
Recovery through PC
Now its all done, Enjoy..
Note: For unrooting you have to flash the stock kernels
Note: Customization of SystemUI.apk will be posted soon.
If there is any problem with this threada kindly inform through PM, If any links not working let me know before blaming me
Hit thanks if i helped you.:laugh:.

http://forum.xda-developers.com/showthread.php?t=1526866

Yeah I know that post well, I got my basic from that post alone, thank you for adding that too in the thread. This is exclusively for XPERIA S with 6.1.A.2.45.
Sent from my LT26i using xda app-developers app

Related

[Q] Help with installing CM7.2.0 FXP049 from the FreeXperia Project

Okay, Ive watched the Noob video when making an account and i have searched around for a while but no luck
Okay basically, I need help! I have an Xperia Arc S and wanted to install the FXP CM7 Rom onto it. Ive seen all the tutorials and unlocked the bootlader, rooted my device etc.
Then I downloaded the CM7 files from the Thread for FXP and then pasted the boot.img file to the fastboot folder. Then i launched fastboot and flashed the boot.img and it was successful. The two zip folders are already in the SD card. I then restart my phone and try to press the volume down key and it doesn't launch the screen that is supposed to appear or anything. and it's just stuck on the boot loop ( I assume that's the blacklight back screen before the Sony erricson logo appears on booting acoording to other threads) I then keep having to flash back to 4.0.2.A.0.42.ftf via the flashtool file.
I then downloaded the recoveryARC file etc and it launches to the Clockworkmod recovery thing at recovery and i try to install the update.zip but it says No such file exists.
What am I doing wrong after I flashed the new boot.img ? Help please.
Thank you guys.

Did you wipe data?
Sent Via LT15i - FXP46-CM7

Is it required to wipe data? As in wipe data in the Clockwordmod before I install the update.zip? Or..

dinesh690 said:
Is it required to wipe data?
Click to expand...
Click to collapse
It does state so in the instructions to do so so yes.
Sent Via LT15i - FXP46-CM7

Didn't work
Okay thanks but that doesn't seem to help it. I booted the recoveryARC.img and it goes into Clockworkmod recovery menu. I wiped data, wiped cache partition etc and try to apply udate from sdcard and it still says E:Can't open /sdcard/udapte.zip No such file or directory Installation aborted.
What am I doing wrong.
This is my fastboot log:
C:\Users\Dinesh\Contacts\Roms etc\fastboot_with_Android_USB_file\fastboot_with_A
ndroid_USB_file\fastboot>fastboot flash boot boot.img
sending 'boot' (5272 KB)...
(bootloader) USB download speed was 9212kB/s
OKAY [ 0.590s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.090s]
finished. total time: 1.680s
C:\Users\Dinesh\Contacts\Roms etc\fastboot_with_Android_USB_file\fastboot_with_A
ndroid_USB_file\fastboot>fastboot boot recoveryARC.img
downloading 'boot.img'...
(bootloader) USB download speed was 9207kB/s
OKAY [ 0.465s]
booting...
(bootloader) Download buffer format: boot IMG
OKAY [ 0.002s]
finished. total time: 0.467s
C:\Users\Dinesh\Contacts\Roms etc\fastboot_with_Android_USB_file\fastboot_with_A
ndroid_USB_file\fastboot>
In my SDCard on the phone i have the GAPPS zip and the CM7 zip which is called update(.zip)
(That boots me into the Clockworkmods, which is where everything starts to go wrong for me) Is the method im doing wrong? But i can't seem to use the method in the FreeXperia thread as after I flash the boot.img file provided, it just goes into a bootloop so i can't press down the volume down key or anything obviously. Thanks again.

Okay Guys I fixed this, I basically installed FXP047 which seems to work perfectly fine, and boots into the freexperia logo and i have installed CM7 now. Moreover, the E:Can't open /sdcard/udapte.zip No such file or directory Installation aborted problem was fixed by ejecting the Arc S from the PC safely and not just pulling out the cable Sorry for wasting your time guys. BUT THANK YOU CM7 IS AWESOME. If anyone has this similair problem then use this and hope it helps

i have a little problem.
-Place the CyanogenMod update.zip file on the root of the SD card.
-Optional: Place the Google Apps .zip on the root of the SD card also.
Click to expand...
Click to collapse
what is the root of sd card? where is it? i put the files in the sd card, but after that i cant flash (this commands dont work fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot)

I have a question
If i have 4.0.2.A.0.58 , can i install the CM 7.2 ?
thanks

Hi
Please , someone can help with my question?
Thanks
Sorry for my bad english

xviu said:
If i have 4.0.2.A.0.58 , can i install the CM 7.2 ?
Click to expand...
Click to collapse
Yes, you can.
http://forum.xda-developers.com/showthread.php?t=1299729

dp94 said:
Yes, you can.
http://forum.xda-developers.com/showthread.php?t=1299729
Click to expand...
Click to collapse
Thanks for your help

FAILED (remote: The Device must be rooted first)

Hi, I have several questions about flashing a ICS beta kernel on my arc s
I have android 2.3.4 ...42, rooted by superoneclickv2+busybox+cwm, Im trying to install this kernel http://forum.xda-developers.com/showthread.php?t=1514849
to use with this rom http://forum.xda-developers.com/showthread.php?t=1540072
But when I try to flash by fastboot I get this log
2/024/2012 01:24:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
12/024/2012 01:24:19 - INFO - Device connected with USB debugging on
12/024/2012 01:24:19 - INFO - Connected device : LT18
12/024/2012 01:24:19 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
12/024/2012 01:24:19 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
12/024/2012 01:24:41 - INFO - Root Access Allowed
12/025/2012 01:25:24 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
12/025/2012 01:25:24 - INFO - Device Status: ADB mode
12/025/2012 01:25:27 - INFO - Please wait device is rebooting into fastboot mode (via ADB)
12/025/2012 01:25:28 - INFO - Device will soon enter fastboot mode
12/025/2012 01:25:29 - INFO - Device disconnected
12/025/2012 01:25:30 - INFO - Device connected in fastboot mode
12/025/2012 01:25:33 - INFO - Please wait device is rebooting into fastboot mode (via Fastboot)
12/025/2012 01:25:33 - INFO - Device will soon reboot back into fastboot mode
12/025/2012 01:25:34 - INFO - Device disconnected
12/025/2012 01:25:36 - INFO - Device connected in fastboot mode
12/025/2012 01:25:40 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\boot.img
12/025/2012 01:25:40 - INFO - Flashing selected kernel
12/025/2012 01:25:40 - INFO - FASTBOOT Output:
sending 'boot' (5850 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
Click to expand...
Click to collapse
What Im doing wrong?
I dont know if my bootloader is unlocked or not, if I press *#*#7378423#*#*
it says "Bootloader unlock allowed: Yes"
Im very confused about this because somewhere in this forum I read that if you root your phone then bootloader get unlock...
Please help me, flashing my brothers x10 was soo easy with .ftf files, but I really dont know how to flash .img kernels or if my bootloader still locked
Need a guide for noobs
or should I wait until sony releases ICS update?

Rooting doesnt unlock the bootloader.. Is ur bootloader unlocked? how did u do it? SE has given official instructions on how to unlock the bootloader..
http://unlockbootloader.sonymobile.com/
R u trying to flash this Kernel via the Flash tool software? I would suggest you to connect ur cell in the fastboot mode.
Switch it off and connect it to PC via USB by pressing the menu button (A blue LED will be seen)
U need to have working fastboot for that..
http://www.mediafire.com/?b2of5mpqi2bwczt
Extract this file and when u'll connect ur cell to PC as stated above, for the first time, it will ask for drivers... browse to the USB driver folder which is in the .rar file.
Once u r done with the unlocking bootloader, download the kernel img file and save it in the folder where fastboot.exe is.
Now open the command promt (if u r using windows 7, just press shift and do a right click, select open command prompt here from the menu) and go to the fastboot folder in the cmd. once u r on the path of fastboot. Enter following commands :
fastboot flash boot KernelFile.img (ur copied kernel file)
it will start flashing the kernel, once it is done, type following
fastboot reboot
Ur cell be restarted, when u'll c the kernel booting, keep pressing the volume button to go into the recovery mode..
I cant be held responsible if u damage ur device!!!
Hit thanks if I helped u..

same issue
so ive tried everything i can come across to figure out why it gives me the same error. my bootloader is unlocked and phone is rooted. but i still get the phone must be rooted message no matter what i do and its so irritating cuz i want to put miui on it but cant for the life of me flash anything except stock roms. fastboot not working for me at all. any help please
edit
even though store claimed it to be unlocked the bootloader was not phone just wasnt branded to any carrier so had to unlock the bootloader and everything is glorious now:}

iKevinShah said:
I have got the same stuff (but on my xperia neo)
same exact problem.
The is nothing with bootloader or root, i guess
what my experience is, when i open with cmd in windows and type fastboot devices, i get none but in flashtool it recognised the device in fastboot.
Do you also have the same status as this ?
Click to expand...
Click to collapse
Seriously bro.. you're doing something wrong.. once install all the drivers and execute this command..
Fastboot.exe -i 0x0fce getvar version
If u get 0.3 or something its all fine..
Don't forget to hit 'THANKS' if I helped..
Sent from my Xperia Pro using XDA

You need to unlock your bootloader....
unlockbootloader.sonymobile.com/instructions
I has the same problem, after unlock bootloader, its fine!

I solve it
Overdose1986 said:
Hi, I have several questions about flashing a ICS beta kernel on my arc s
I have android 2.3.4 ...42, rooted by superoneclickv2+busybox+cwm, Im trying to install this kernel http://forum.xda-developers.com/showthread.php?t=1514849
to use with this rom http://forum.xda-developers.com/showthread.php?t=1540072
But when I try to flash by fastboot I get this log
What Im doing wrong?
I dont know if my bootloader is unlocked or not, if I press *#*#7378423#*#*
it says "Bootloader unlock allowed: Yes"
Im very confused about this because somewhere in this forum I read that if you root your phone then bootloader get unlock...
Please help me, flashing my brothers x10 was soo easy with .ftf files, but I really dont know how to flash .img kernels or if my bootloader still locked
Need a guide for noobs
or should I wait until sony releases ICS update?
Click to expand...
Click to collapse
Hi,after "BootLoader" again,it's OK.I hope it's useful for U.

i have the same problem
it says that you device must be rooted
and i have my xperia ray rooted and unlocked bootloader
please help me to solve this problem:crying:

I cannot unlock the bootloader
I do have the same problem, my device is rooted as per doomlord method and I when I try to install a custum kernel I too get the error
failed remote the device must be rooted first.
Also I could not unlock the bootloader when I try the steps mentioned in sony website, I got the unlock code and it says " need a unlocked device" while I try to unlock the bootloader: fastboot -i 0x0fce oem unlock 0x<unlockcode>

mail_venu said:
I do have the same problem, my device is rooted as per doomlord method and I when I try to install a custum kernel I too get the error
failed remote the device must be rooted first.
Also I could not unlock the bootloader when I try the steps mentioned in sony website, I got the unlock code and it says " need a unlocked device" while I try to unlock the bootloader: fastboot -i 0x0fce oem unlock 0x<unlockcode>
Click to expand...
Click to collapse
Put the unlock code in the command, enter it, while having phone in fastboot mode, and bootloader should get unlocked. That is only if you do have SIM-unlocked phone, that is no SIM-lock.

--

same problem
Overdose1986 said:
Hi, I have several questions about flashing a ICS beta kernel on my arc s
I have android 2.3.4 ...42, rooted by superoneclickv2+busybox+cwm, Im trying to install this kernel http://forum.xda-developers.com/showthread.php?t=1514849
to use with this rom http://forum.xda-developers.com/showthread.php?t=1540072
But when I try to flash by fastboot I get this log
What Im doing wrong?
I dont know if my bootloader is unlocked or not, if I press *#*#7378423#*#*
it says "Bootloader unlock allowed: Yes"
Im very confused about this because somewhere in this forum I read that if you root your phone then bootloader get unlock...
Please help me, flashing my brothers x10 was soo easy with .ftf files, but I really dont know how to flash .img kernels or if my bootloader still locked
Need a guide for noobs
or should I wait until sony releases ICS update?
Click to expand...
Click to collapse
same problem, who to fix?

joaoandre23 said:
same problem, who to fix?
Click to expand...
Click to collapse
Download the lastest flashtool available, now allows you to flash .img kernels

joaoandre23 said:
same problem, who to fix?
Click to expand...
Click to collapse
Rooting does not unlock your bootloader. They are not even related to each other!
There is a big difference between "Bootloader unlock allowed: Yes" and "Bootloader unlocked: Yes". I think you understand the difference.
Unlock bootloader and then try to flash kernel again.

Someguyfromhell said:
Put the unlock code in the command, enter it, while having phone in fastboot mode, and bootloader should get unlocked. That is only if you do have SIM-unlocked phone, that is no SIM-lock.
Click to expand...
Click to collapse
That's right.
The whole process look like (with my phone:
Code:
E:\Download\Mobile\Xperia>fastboot devices
CB5121CFWR&ZLP fastboot
E:\Download\Mobile\Xperia>fastboot.exe -i 0x0fce getvar version
version: 0.5
finished. total time: 0.001s
E:\Download\Mobile\Xperia>fastboot flash boot boot.img
sending 'boot' (8617 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.005s
E:\Download\Mobile\Xperia>fastboot.exe -i 0x0fce oem unlock 0xUNLOCK-KEY
...
(bootloader) Unlock phone requested
OKAY [ 0.500s]
finished. total time: 0.501s
E:\Download\Mobile\Xperia>fastboot flash boot boot.img
sending 'boot' (8617 KB)...
(bootloader) USB download speed was 20960kB/s
OKAY [ 0.438s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 0.482s]
finished. total time: 0.922s
E:\Download\Mobile\Xperia>

mandarjoshiin said:
Rooting doesnt unlock the bootloader.. Is ur bootloader unlocked? how did u do it? SE has given official instructions on how to unlock the bootloader..
http://unlockbootloader.sonymobile.com/
R u trying to flash this Kernel via the Flash tool software? I would suggest you to connect ur cell in the fastboot mode.
Switch it off and connect it to PC via USB by pressing the menu button (A blue LED will be seen)
U need to have working fastboot for that..
http://www.mediafire.com/?b2of5mpqi2bwczt
Extract this file and when u'll connect ur cell to PC as stated above, for the first time, it will ask for drivers... browse to the USB driver folder which is in the .rar file.
Once u r done with the unlocking bootloader, download the kernel img file and save it in the folder where fastboot.exe is.
Now open the command promt (if u r using windows 7, just press shift and do a right click, select open command prompt here from the menu) and go to the fastboot folder in the cmd. once u r on the path of fastboot. Enter following commands :
fastboot flash boot KernelFile.img (ur copied kernel file)
it will start flashing the kernel, once it is done, type following
fastboot reboot
Ur cell be restarted, when u'll c the kernel booting, keep pressing the volume button to go into the recovery mode..
I cant be held responsible if u damage ur device!!!
Hit thanks if I helped u..
Click to expand...
Click to collapse
can you re-upload the files you uploaded on mediafire please?

isko95 said:
can you re-upload the files you uploaded on mediafire please?
Click to expand...
Click to collapse
Can you use the search button please?
僕のINO2から送られてきた

Solved
I was having the same problem and it was due locked bootloader
then i unlocked the bootloader and every thing goes fine

so, dudes, I had the same problem... beyond others
the situation is: YOUR BOOTLOADER LOOKS LIKE UNLOCKED,
BUT IT ISN'T!!
When you rooted your phone, the rooting method modificated this notification. But the true story is that you need to go to Sony website and claim your BOOTLOADER UNLOCK CODE.
Unless you do this, you'll never flash any thing on your smartphone.
Hugs and kisses!!

[q] htc wildfire wont turn on red led keeps flashing

So my Wildfire was working fine but run out of charge, now when I put it on charge the notification led just flashes red and wont turn on the phone :crying:

zonda2323 said:
So my Wildfire was working fine but run out of charge, now when I put it on charge the notification led just flashes red and wont turn on the phone :crying:
Click to expand...
Click to collapse
Try this. Take the battery out and then put it back and turn the phone on.
Are you on CWM 4? If yes, its a bug in that version. When you charge the phone while turned off, to turn it on you'll have to take the battery out and put it back in.

zonda2323 said:
So my Wildfire was working fine but run out of charge, now when I put it on charge the notification led just flashes red and wont turn on the phone :crying:
Click to expand...
Click to collapse
Clear battery stats. Switch off the phone. Charge straight for 2.5-3 hrs. Disconnect the charger. Power on.
Sent from my Nexus 4

I'll chime here, as I do have the same problem...
lakshan_456 said:
Are you on CWM 4? If yes, its a bug in that version. When you charge the phone while turned off, to turn it on you'll have to take the battery out and put it back in.
Click to expand...
Click to collapse
I do have v2.5.0.1 --> also buggy?
What is your suggestion on ROM/CWM to avoid this kind of problems?
gobz said:
Clear battery stats. Switch off the phone. Charge straight for 2.5-3 hrs. Disconnect the charger. Power on.
Click to expand...
Click to collapse
Will this solve the problem permanently or do I have to repeat this everytime?
@OP: Have you solved the problem?
Thanks,
Guntram

Guntram said:
I'll chime here, as I do have the same problem...
I do have v2.5.0.1 --> also buggy?
What is your suggestion on ROM/CWM to avoid this kind of problems?
Thanks,
Guntram
Click to expand...
Click to collapse
I'd recommend this one,
http://forum.xda-developers.com/showthread.php?t=1014498
Cheers

lakshan_456 said:
I'd recommend this one,
http://forum.xda-developers.com/showthread.php?t=1014498
Cheers
Click to expand...
Click to collapse
I can't get it installed...tried the zip from the thread (with CWM-2.5) and
fastboot flash recovery ./recovery.img
The latter yields:
sending 'recovery' (3010 KB)...
OKAY [ 0.846s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.556s
Here (http://forum.xda-developers.com/showthread.php?t=2277112) they write about "unsigned" images...
Any ideas?

Guntram said:
I can't get it installed...tried the zip from the thread (with CWM-2.5) and
fastboot flash recovery ./recovery.img
The latter yields:
sending 'recovery' (3010 KB)...
OKAY [ 0.846s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.556s
Here (http://forum.xda-developers.com/showthread.php?t=2277112) they write about "unsigned" images...
Any ideas?
Click to expand...
Click to collapse
Did you try the PC49IMG.zip method? It's in the last page of that thread.
And, I'm not very acquainted with fastboot. Sorry...
Sent from my HTC Wildfire using Tapatalk 2

lakshan_456 said:
Did you try the PC49IMG.zip method? It's in the last page of that thread.
Click to expand...
Click to collapse
I downloaded the zip and flashed it via Recovery - but this seems to fail (I don't get any error message, but it simply doesn't succeed).
I also tried unrevoked3.
Do I miss something? My "active time" with the Wildfire was some years ago...

Guntram said:
I downloaded the zip and flashed it via Recovery - but this seems to fail (I don't get any error message, but it simply doesn't succeed).
I also tried unrevoked3.
Do I miss something? My "active time" with the Wildfire was some years ago...
Click to expand...
Click to collapse
The zip isn't flashed from recovery. The process is explained in the post which has the zip file attached. Please try following that instructions.
Sent from my HTC Wildfire using Tapatalk 2

lakshan_456 said:
The zip isn't flashed from recovery. The process is explained in the post which has the zip file attached. Please try following that instructions.
Click to expand...
Click to collapse
I always thought, the recovery-zip-installation would simulate the very same process. I tried this way, too.
However, this didn't work, either ;-(. I put it into SDCARD-root, chose Reboot into Bootloader -> there it seems to check the corresponding ZIP but no questioning to install it...
Maybe some problem of my HBOOT-version? I'm still on 0.8 (and couldn't find any update instructions, yet).
How did you install your recovery? The zip method was posted just at the end of the thread?

Guntram said:
I always thought, the recovery-zip-installation would simulate the very same process. I tried this way, too.
However, this didn't work, either ;-(. I put it into SDCARD-root, chose Reboot into Bootloader -> there it seems to check the corresponding ZIP but no questioning to install it...
Maybe some problem of my HBOOT-version? I'm still on 0.8 (and couldn't find any update instructions, yet).
How did you install your recovery? The zip method was posted just at the end of the thread?
Click to expand...
Click to collapse
Yes, I use the pc49.zip method.
And, yes. Maybe your hboot version is causing this. But I'm not familiar with these issues.
Maybe @heavy_metal_man can help you. As I know he has lot of knowledge regarding these than myself.
Sent from my HTC Wildfire using Tapatalk 2

zonda2323 said:
So my Wildfire was working fine but run out of charge, now when I put it on charge the notification led just flashes red and wont turn on the phone :crying:
Click to expand...
Click to collapse
does your phone power on at all? or just the red led flash. this is usually caused my the battery being fully depleted and the bootloader not having enough power to boot at all. if leaving it on charge for 24H+ does not fix the issue then either buy a new battery and/or a external wall charger like this one . you may need an adapter for the wall, depending where you live. This should not fail and in future be careful to never fully deplete your battery
Guntram said:
I always thought, the recovery-zip-installation would simulate the very same process. I tried this way, too.
However, this didn't work, either ;-(. I put it into SDCARD-root, chose Reboot into Bootloader -> there it seems to check the corresponding ZIP but no questioning to install it...
Maybe some problem of my HBOOT-version? I'm still on 0.8 (and couldn't find any update instructions, yet).
How did you install your recovery? The zip method was posted just at the end of the thread?
Click to expand...
Click to collapse
since you rooted your phone using unrevoked your hboots security was never deactivated, just bypassed temporarily. this means that if you know what your doing with root, you can flash a custom recovery but i dont recommend this as its a but outdated. i recommend you upgrade your hboot stock rom and radio using a RUU. then run the program revolutionary to remove the security on your bootloader. then fastboot and pc49img.zip methods will be available to you, so you can flash a more updated recovery without issue Since you have fastboot commands set up on your pc please issue the command
Code:
Fastboot getvar cid
for me and post the cid here. i will then have a look for you and see if i can find a ruu for you to upgrade easily
lakshan_456 said:
Yes, I use the pc49.zip method.
And, yes. Maybe your hboot version is causing this. But I'm not familiar with these issues.
Maybe @heavy_metal_man can help you. As I know he has lot of knowledge regarding these than myself.
Sent from my HTC Wildfire using Tapatalk 2
Click to expand...
Click to collapse
cheers for the heads up

Hello heavy_metal_man and thanks for chiming in!
I have my phone always on a charger, but sometimes it seems to be shut down and remain unresponsive until I remove the battery. So I do rule out a battery issue (though not any other hardware issues ).
This happens sometimes(!) when I'm on charging (via computer USB) and simply shut down the phone. It becomes unresponsive, the red LED still glows and I have to remove the batter.
Trying to get a RUU with the HBOOT 1.00 included resulted in the following (using OpenRUU from http://forum.xda-developers.com/showthread.php?t=711298 and a RUU downloaded from http://forum.xda-developers.com/showthread.php?t=1275680, namely the first FROYO ROM, second download link) :
Code:
42turkeys presents...
____ _____ _ _ _ _
/ __ \ | __ \| | | | | | |
| | | |_ __ ___ _ __ | |__) | | | | | | | FASTBOOT
| | | | '_ \ / _ \ '_ \| _ /| | | | | | | FLASH
| |__| | |_) | __/ | | | | \ \| |__| | |__| | VERSION
\____/| .__/ \___|_| |_|_| \_\____/ \_____/
| |
|_| Version 1.1.2-LINUX
1. HTC GSM Hero
2. HTC Desire
3. HTC Tattoo
4. HTC CDMA Hero
5. HTC Legend
6. HTC Droid Incredible
7. HTC EVO 4G
8. Other
Please enter the corresponding number above: 8
WARNING! THE UPDATE PROCESS WILL ERASE ALL DATA, APPS & APP DATA ON YOUR DEVICE! (But not SDCard)
Please reboot your device into fastboot by turning your phone on holding power + back
When you see FASTBOOT USB on the screen press enter.
Press enter to Continue
If you see a device below then your device is ready to be updated and you have the correct drivers installed.
[sudo] password for guntram:
HT076PY02508 fastboot
If you could see your device above then you are ready to proceed.
If not, then you need to make sure that your device is connected in fastboot mode and that you have the drivers/HTC Sync installed.
Press enter to continue...
Fetching Current Device Info...
ROM Version:
version-main: 1.25.405.1
Press enter to continue...
Bootloader Version:
version-bootloader: 0.80.0007
Device:
product: buzz
Battery Status: (Must be good or better to proceed)
battery-status: good
OK to proceed? (Press enter)
Erasing Cache...
erasing 'cache'... OKAY
Done!
Rebooting in RUU mode...
... OKAY
Flashing ROM... DO NOT TOUCH YOUR DEVICE!
< waiting for device >
sending 'zip' (127911 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
You may get an error message above (HBOOT Pre Update!) don't worry, this is normal.
Reflashing... DO NOT TOUCH YOUR DEVICE!
sending 'zip' (127911 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
If you got another error message above, please run this script again.
If the process completed with no errors the second time, you have successfully updated/downgraded your ROM!
Press enter to continue...
Rebooting Device... (First boot will take a while)
[sudo] password for guntram:
rebooting...
OK to disconnect
Thanks for using OpenRUU! If you can, please donate so I can buy some hosting to implement some cool features...
Donate: https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=max%40maxmarroni%2eco%2euk&lc=GB&item_name=OpenRUU&no_note=1&no_shipping=1&currency_code=GBP&bn=PP%2dDonationsBF%3abtn_donateCC_LG%2egif%3aNonHosted
Have a nice day... :)
Press enter to exit.
This procedure also created a ROM.zip - may this be of any use? It seems to be not flashable via recovery.
The demanded cid: VODAP129
Thanks,
Guntram
heavy_metal_man said:
does your phone power on at all? or just the red led flash. this is usually caused my the battery being fully depleted and the bootloader not having enough power to boot at all. if leaving it on charge for 24H+ does not fix the issue then either buy a new battery and/or a external wall charger like this one . you may need an adapter for the wall, depending where you live. This should not fail and in future be careful to never fully deplete your battery
since you rooted your phone using unrevoked your hboots security was never deactivated, just bypassed temporarily. this means that if you know what your doing with root, you can flash a custom recovery but i dont recommend this as its a but outdated. i recommend you upgrade your hboot stock rom and radio using a RUU. then run the program revolutionary to remove the security on your bootloader. then fastboot and pc49img.zip methods will be available to you, so you can flash a more updated recovery without issue Since you have fastboot commands set up on your pc please issue the command
Code:
Fastboot getvar cid
for me and post the cid here. i will then have a look for you and see if i can find a ruu for you to upgrade easily
cheers for the heads up
Click to expand...
Click to collapse

Guntram said:
Hello heavy_metal_man and thanks for chiming in!
I have my phone always on a charger, but sometimes it seems to be shut down and remain unresponsive until I remove the battery. So I do rule out a battery issue (though not any other hardware issues ).
This happens sometimes(!) when I'm on charging (via computer USB) and simply shut down the phone. It becomes unresponsive, the red LED still glows and I have to remove the batter.
Trying to get a RUU with the HBOOT 1.00 included resulted in the following (using OpenRUU from http://forum.xda-developers.com/showthread.php?t=711298 and a RUU downloaded from http://forum.xda-developers.com/showthread.php?t=1275680, namely the first FROYO ROM, second download link) :
Code:
42turkeys presents...
____ _____ _ _ _ _
/ __ \ | __ \| | | | | | |
| | | |_ __ ___ _ __ | |__) | | | | | | | FASTBOOT
| | | | '_ \ / _ \ '_ \| _ /| | | | | | | FLASH
| |__| | |_) | __/ | | | | \ \| |__| | |__| | VERSION
\____/| .__/ \___|_| |_|_| \_\____/ \_____/
| |
|_| Version 1.1.2-LINUX
1. HTC GSM Hero
2. HTC Desire
3. HTC Tattoo
4. HTC CDMA Hero
5. HTC Legend
6. HTC Droid Incredible
7. HTC EVO 4G
8. Other
Please enter the corresponding number above: 8
WARNING! THE UPDATE PROCESS WILL ERASE ALL DATA, APPS & APP DATA ON YOUR DEVICE! (But not SDCard)
Please reboot your device into fastboot by turning your phone on holding power + back
When you see FASTBOOT USB on the screen press enter.
Press enter to Continue
If you see a device below then your device is ready to be updated and you have the correct drivers installed.
[sudo] password for guntram:
HT076PY02508 fastboot
If you could see your device above then you are ready to proceed.
If not, then you need to make sure that your device is connected in fastboot mode and that you have the drivers/HTC Sync installed.
Press enter to continue...
Fetching Current Device Info...
ROM Version:
version-main: 1.25.405.1
Press enter to continue...
Bootloader Version:
version-bootloader: 0.80.0007
Device:
product: buzz
Battery Status: (Must be good or better to proceed)
battery-status: good
OK to proceed? (Press enter)
Erasing Cache...
erasing 'cache'... OKAY
Done!
Rebooting in RUU mode...
... OKAY
Flashing ROM... DO NOT TOUCH YOUR DEVICE!
< waiting for device >
sending 'zip' (127911 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
You may get an error message above (HBOOT Pre Update!) don't worry, this is normal.
Reflashing... DO NOT TOUCH YOUR DEVICE!
sending 'zip' (127911 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
If you got another error message above, please run this script again.
If the process completed with no errors the second time, you have successfully updated/downgraded your ROM!
Press enter to continue...
Rebooting Device... (First boot will take a while)
[sudo] password for guntram:
rebooting...
OK to disconnect
Thanks for using OpenRUU! If you can, please donate so I can buy some hosting to implement some cool features...
Donate: https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=max%40maxmarroni%2eco%2euk&lc=GB&item_name=OpenRUU&no_note=1&no_shipping=1&currency_code=GBP&bn=PP%2dDonationsBF%3abtn_donateCC_LG%2egif%3aNonHosted
Have a nice day... :)
Press enter to exit.
This procedure also created a ROM.zip - may this be of any use? It seems to be not flashable via recovery.
The demanded cid: VODAP129
Thanks,
Guntram
Click to expand...
Click to collapse
ok, im on the lookout for a RUU for you. can you upload the rom.zip from that program somewhere for me to download. im interested in what it has outputted. also, what hboot and recovery version are you on?
UPDATE: ok we are out of luck for an official update from vodaphone that has hboot 1.01.0001 as they upgraded straight to hboot 1.01.0002. but this is not the end
we can use a Goldcard to bypass the htc's check of the phone cid, allowing us to flash other carriers updates. as such we can flash a WWE (world wide english, unbranded) rom with the hboot we need.
follow this part of my guide
Code:
step 6. now we need to make a gold card. if you already have one, you can skip this part. first using your working android phone, download and install Goldcard helper from the android market. Run the app and copy down your sd cards reverse cid.
step 7. now go to this website [URL="http://huygens.hoxnet.com/goldcard.html"]here[/URL] and enter in your reverse cid. it will then let you download a goldcard.img.
step 8. now go back to our c:\adb\ folder and run the goldcardtool.exe, this will flash the goldcard to your sd card. Warning! this will format your card!!
step 9. once that is done we are now ready for the final push
once you have made a working goldcard then run the RUU in this download package all going well your device will flash the update. if it gives you the error 42, or 131 then the goldcard has failed.
once you have that ran and successfully then reboot and quick setup your phone and then run this tool called revolutionary as this will make your bootloader s-off
finally install this recovery here to fix the charging issue. place it onto the sdcard and allow the bootloader to flash the recovery
then its just install any custom rom you want pal
more info on revolutionary instructions here

Guntram said:
Bootloader Version:
version-bootloader: 0.80.0007
Click to expand...
Click to collapse
rom.zip is here:
https://www.dropbox.com/s/ttjpn8uw9drwtja/rom.zip

Guntram said:
rom.zip is here:
https://www.dropbox.com/s/ttjpn8uw9drwtja/rom.zip
Click to expand...
Click to collapse
turns out, i believe this is the same as you are downloading from me you will still need to have a goldcard functioning and the clickable ruu is more user friendly

heavy_metal_man said:
finally install this recovery here to fix the charging issue
Click to expand...
Click to collapse
Download link won't work .
Does this CWM involve the same "improvements" as the one from arco68 (http://forum.xda-developers.com/showthread.php?t=1014498)?

Guntram said:
Download link won't work .
Does this CWM involve the same "improvements" as the one from arco68 (http://forum.xda-developers.com/showthread.php?t=1014498)?
Click to expand...
Click to collapse
http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-buzz.zip new link from source. All cwm Recovery's v.5 + up to some 6+ have the charging bug fixed.
Sent from my Nexus 7 using Tapatalk 4

heavy_metal_man said:
once you have made a working goldcard then run the RUU in this download package all going well your device will flash the update.
Click to expand...
Click to collapse
I did this with the help of OpenRUU (no Windows here) and it (for the first time) installed the ROM. But my bootloader is still claims to be 0.80?
heavy_metal_man said:
http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-buzz.zip new link from source. All cwm Recovery's v.5 + up to some 6+ have the charging bug fixed.
Click to expand...
Click to collapse
You're awesome! Thanks!

Guntram said:
I did this with the help of OpenRUU (no Windows here) and it (for the first time) installed the ROM. But my bootloader is still claims to be 0.80?
You're awesome! Thanks!
Click to expand...
Click to collapse
Are you sure it installed the rom? The rom.zip that you linked to me earlier, rename it to PC49IMG.zip and put it onto the root of your SD card. Them boot into the bootloader and let it pick it up. If it asks you to flash it say yes, if it does not then your goldcard has failed.
Sent from my Nexus 7 using Tapatalk 4

[Official]TWRP Recovery for Moto G4 Plus

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
We have our set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
Motorola Moto G4 Plus
NOTE: If you are flashing TWRP for the first time then you need to check this thread and then flash TWRP.
XDA:DevDB Information
TWRP Recovery for the Moto G4 Plus
Contributors
yeshwanthvshenoy, pranav01
Device Tree:https://github.com/TeamWin/android_device_motorola_athene
Version Information
Status: Stable
Created 2016-05-26
Last Updated 2017-05-03

Reserved!

Awesome! Will try it out right now

awesome......will try it and let u know......

Great work !!

Thanks people..... great work..... I'll try it now.....
---------- Post added at 07:42 AM ---------- Previous post was at 07:41 AM ----------
It requires unlocked bootloader right?

cool_sid said:
Thanks people..... great work..... I'll try it now.....
---------- Post added at 07:42 AM ---------- Previous post was at 07:41 AM ----------
It requires unlocked bootloader right?
Click to expand...
Click to collapse
yes it require unlocked bootloader

on flashing it says image not signed or corrupt ..... please guide

[email protected] said:
on flashing it says image not signed or corrupt ..... please guide
Click to expand...
Click to collapse
Don't worry. You will get this even if you flash the stock recovery or the stock kernel via fastboot. Just reboot to recovery and it will be fine.

when i boot into recovery mode
it still says Anrdoid Recovery
motorola/ athene_retail/athene

[email protected] said:
when i boot into recovery mode
it still says Anrdoid Recovery
motorola/ athene_retail/athene
Click to expand...
Click to collapse
Reboot to recovery after flashing the twrp image. Then reboot your device from recovery.
If you reboot your phone from fastboot aftwr flashing twrp, it gets overwritten by stock recovery.

Silesh.Nair said:
Reboot to recovery after flashing the twrp image. Then reboot your device from recovery.
If you reboot your phone from fastboot aftwr flashing twrp, it gets overwritten by stock recovery.
Click to expand...
Click to collapse
He is right. Flash twrp and boot into recovery, if you boot normally, it will patch back the recovery.

Thanks mate, it did worked, installed xposed tweaked my phone , but after installing xposed file manager refuses to open

[email protected] said:
Thanks mate, it did worked, installed xposed tweaked my phone , but after installing xposed file manager refuses to open
Click to expand...
Click to collapse
Don't you need SuperSu for Xposed? I never use Xposed so have no idea. Were you able to root the device or how did you get it working?

after instaling TWRP , i installed xposed .......... i dont think i need root or for what ........... with xposed i installed ADblocker and vibrate on call connect .......... its charm now

Error!!
C:\Users\xxxx\Downloads\mfastboot-v2>mfastboot flash recovery twrp_athene_20150526.img
target max-sparse-size: 256MB
sending 'recovery' (12498 KB)...
OKAY [ 0.453s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
Downloaded from gdrive link. Tried several times. Same error.
Someone help?

carreddy said:
C:\Users\xxxx\Downloads\mfastboot-v2>mfastboot flash recovery twrp_athene_20150526.img
target max-sparse-size: 256MB
sending 'recovery' (12498 KB)...
OKAY [ 0.453s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
Downloaded from gdrive link. Tried several times. Same error.
Someone help?
Click to expand...
Click to collapse
Just reboot to recovery. It shows this error even when flashing the stock recovery. Works fine.

carreddy said:
C:\Users\xxxx\Downloads\mfastboot-v2>mfastboot flash recovery twrp_athene_20150526.img
target max-sparse-size: 256MB
sending 'recovery' (12498 KB)...
OKAY [ 0.453s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
Downloaded from gdrive link. Tried several times. Same error.
Someone help?
Click to expand...
Click to collapse
@Silesh.Nair is right. Even if you flash stock boot.img or recovery.img, you will get the error but just flash and reboot to recovery immediately(if you boot normally, stock rom will replace twrp with stock recovery). i do believe that Moto is just trying to scare us not to flash anything via fastboot

Okay folks, we are now Official Enjoy!

Hi ... the phone is bootloader unlocked and twrp installed and xposed is installed as well
now if there is an Android N update .... can i still update my phone and if no ... how do i update my phone
(supersu) is not installed
Regards

[HOW-TO] BQ Aquaris X Pro | [Stock-ROM] Unlock,Recovery,Root,Upgrade (TWRP/Magisk)

Hi everyone.
This Post (post #1) shows the complete process of unlocking, flashing, rooting etc. in general, it may refer to old firmware and/or tool versions but the steps remain the same for newer versions. The chapters rely on each other so to be sure, just follow every step. Note: Check out post #2 for additional information regarding updating, tools, known problems/pitfalls.
----- Info [2021-02-05] -----
BQ/Mundo Reader S.L. stopped producing Smartphones (since ~2019(?)), the website is down since March 2020. Original BQ firmware is still available for download (see post #230):
Last version of BQs website via archive.org: https://web.archive.org/web/20200320014304/https://www.bq.com/en/support/aquaris-x-pro/support-sheet
Direct link to latest firmware file:
Firmware 2.11.0 (Android 8.1.0 Oreo) (MD5: CA7DCCB4BD101AF64DCFFAAB71CBD476 )
https://storage.googleapis.com/otas...-1510-bardockpro_bq-user-2395-Fastboot-FW.zip
----- End of Info [2021-02-05] -----
After all steps you will have your Aquaris X / X Pro with:
- BQ stock ROM
- (unlocked bootloader)
- TWRP recovery
- Magisk
° root access (managed by Magisk)
° (the possibility to install additional Magisk modules)
° pass Google SafetyNet checks
Disclaimer:
I am in no way responsible for anything resulting in you following the provided instructions in this thread.
It worked for me, but that does not mean it will 100% work for you. You are responsible for any side effects and damage caused to your device which includes, but is not limited to software and/or hardware destruction of the device etc. Rooting may void your warranty.
Only continue if you feel safe in what you are doing.
(Thanks to @shifattk for some text parts (seen here).)
Let's start with an index:
Intro
Boot modes
Set up the PC / Get all files
Start from scratch
Update to newest firmware
Notes/Troubleshooting
Links
Changelog
1 Intro
Recently got me the BQ Aquaris X Pro 128GB and wrote this because of the lack of any documentation on xda regarding unlocking/flashing/rooting/...
In this post you will find a collection of information i found spread over various sources.
I don't know if everything is right, so please report any wrong parts or missing information.
Just a sidenote: At the moment i will be using the stock rom, because it is really clean and slim and i don't want to continuously keep on track with all updates some custom roms have (and get along with possible restrictions in functionality). Because of this, an important advantage for the stock rom is that is 'just works'™ and there are regular updates which are (hopefully ) tested by BQ before release.
So here is a screenshot what the default app launcher looks like and which apps are preinstalled
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The following parts will include:
- unlocking the bootloader
- installing TWRP recovery and Magisk (low level system access, root, ...)
- update BQ firmware
- re-installing TWRP/Magisk/root
Alternatively, one could easier update first and then do all the Recovery- and rootstuff, but I wanted to verify that a system update will be possible without data loss at any time later on. As i read in other forums, it is a bad idea to use the OTA functionality (over-the-air = regular/stock way for system updates) when running a rooted system with unlocked bootloader. (I didn't test this, but i didn't want to find out either..)
Warning: If you used the phone before - backup your files! The phones data will get wiped in the process (at least while unlocking the bootloader)!
Note: I took out my SIM card for the whole process and never set up WLAN, so the phone never got internet access until i disabled the search for software updates. This may prevent the update notifications.
Thanks to
- everyone at the android-hilfe.de forum, especially syscrh and blur for their threads (see [9],[10])
- topjohnwu, developer of Magisk
- Kra1o5, the TWRP maintainer for the Aquaris X Pro
- the BQ team for their firmware and of course for packaging and hosting the firmware
2 Boot modes
Precondition for both modes: phone off, no usb connection
Fastboot mode: vol_down + pwr
(if entered accidentally, long press pwr for >12sec, screen switches off, then phone will reboot (to system) after 10-20secs)
Recovery: vol_up + pwr
(navigate with vol_up and vol_down buttons, select/confirm with power button)
In detail (for new users): while phone is off, press and hold the volume-up/down button and directly after this (still holding vol_up/down) press and hold the power button as well. Hold both buttons until you see the logo and hold for approx. 1 more second. then release both buttons.
For further information or other BQ phones, take a look here: [8]
3 Set up the PC / Get all files
Get Android Debug Bridge (adb) drivers and newest firmware from BQ [1](DE) / [1](EN)
- Install drivers
- extract the firmware zip
If you already got adb on your computer, check the version - some commands may not be availlable.
For adb sideload via TWRP recovery, you should have at least adb version 1.0.32 [2]
You can get the SDK Platform Tools from Google. [3] At the time of writing (2017-09-14), they are on version 1.0.39.
A good choice may be to use the adb tools packaged in the firmware update .zip from BQ.
For the Aquaris X Pro firmware 1.4.3_20170809-1111-bardock-user-983-Fastboot-FW.zip, the tools are on version 1.0.36.
Get the TWRP image file for the Aquaris X Pro [4].
(Take a look at [5] if you own the Aquaris X.)
Get Magisk flashable .zip [6]
To be sure get the uninstaller and the Magisk Manager .apk as well.
4 Start from scratch
preconditions:
- New phone with unmodified stock rom
- Versions as reference:
- using windows 10 here, so some of the following parts may be windows specific. Linux users (ok, debian based linux users) should take a look at the packages 'android-tools-adb' and 'android-tools-fastboot'.
4.1 Prepare phone
Activate developer mode and, from the developer options:
- allow unlocking of the bootloader
- enable USB debugging mode.
Disable software update search:
- Settings -> About phone -> System updates -> untick the checkbox 'Auto-check'
Detail regarding activation of developer options:
cite from [4]
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging.
Click to expand...
Click to collapse
On the same screen enable the option 'OEM unlocking' as well.
Note: User overbim reported in post #240 that the 'OEM unlocking' option was greyed out. After having activated WIFI and having connected to a WLAN the option was accessible short time after that.
4.2 Unlock the bootloader
Go to fastboot mode (Power off, then hold vol_down + pwr).
Connect to PC via USB.
After allowing unlocking in the developer options, you should see:
We will be using the following fastboot commands: (from 'fastboot --help')
flashing get_unlock_ability
Queries bootloader to see if the device is unlocked.
flashing unlock
Unlocks the device. Allows flashing any partition except bootloader-related partitions.
flashing unlock_critical
Enables flashing bootloader-related partitions.
Click to expand...
Click to collapse
Check if bootloader unlocking is allowed, it should give the response '1'
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 1
OKAY [ 0.018s]
finished. total time: 0.020s
If you missed the 'OEM unlocking' option earlier, then you'll get:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.013s]
finished. total time: 0.013s
Stop here and go back to step '4.1 Prepare phone'
FYI, additional information:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.053s]
finished. total time: 0.053s
Okay, now the first part of the unlocking process:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot flashing unlock
...
OKAY [ 0.074s]
finished. total time: 0.076s
Choose yes:
wait a couple of minutes, there will be this screen:
After that, you will get to the welcome screen.
Disconnect USB and switch off the phone.
Enter fastbook mode again, connect usb
Now the first lock should be gone:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.054s]
finished. total time: 0.058s
And now for part two of the unlocking process:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot flashing unlock_critical
...
OKAY [ 0.075s]
finished. total time: 0.076s
Choose yes again:
You will get the encrypting screen again:
Followed by the screen with the 'Aquaris X' animation and finally the welcome screen.
Disconnect USB, switch off.
Enter fastbook mode again, connect usb and check if both unlocks went fine:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.058s]
finished. total time: 0.060s
Done.
Stay in fastboot mode for the next step.
4.3 Install TWRP and Magisk
Now we only need one command to flash the TWRP recovery (adjust to your filepaths)
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot flash recovery ..\..\03_TWRP_Magisk\twrp-3.1.1-0-bardock_pro.img
target reported max download size of 536870912 bytes
sending 'recovery' (28078 KB)...
OKAY [ 0.635s]
writing 'recovery'...
OKAY [ 0.180s]
finished. total time: 0.817s
Now we restart the phone and go into TWRP recovery immediately at reboot - there will be an info screen with a 5 second timeout. press volume_up as soon as you see this screen.
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot reboot
rebooting...
finished. total time: 0.006s
Here is the screen you'll see after reboot:
After pressing volume_up, you'll see an options menu
Select 'Recovery' with vol_up/down and chose the option with the power button.
You'll see the options screen again, but this time just wait 5 seconds or press the power button and TWRP recovey will start.
TWRP will ask if it should modify the system partition. Don't apply the modifications, instead choose 'Keep Read Only'.
Note: If you chose 'yes', then take a look at section '6.1 troubleshooting'.
Now we flash Magisk from TWRP with the adb sideload function.
In TWRP choose 'Advanced' and there 'ADB sideload'. Just swipe and start the sideload mode.
From the PC, we initiate the transfer and installation of the Magisk .zip:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>adb sideload ..\..\03_TWRP_Magisk\Magisk-v14.0.zip
loading: '..\..\03_TWRP_Magisk\Magisk-v14.0.zip'* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Total xfer: 1.69x
Now we can reboot to system. TWRP will be kept (although we only selected the temporary variant before).
This should be the first system bootup after the wipe from the bootloader unlocking process, so you will get to the welcome wizard. At this point I chose to skip the SIM card step (because i did not insert any SIM) and leave the WLAN unconfigured.
In the settings menu, go to 'About Phone' and 'Software Update' and disable the automatic updates
This should prevent any notifications regarding OTA updates as we will update via PC with the .zip firmware downloaded from BQ.
In the system you will notice the Magisk Manager App. Through this App, you can allow and deny root access for any app (a notification will pop up if any app requests root permission).
Enable developer options (see step '4.1 prepare phone') and enable USB debugging mode again.
Allow your PC in the popup notification and check the option to always allow this PC.
5 Update to newest firmware
preconditions:
- some older stock firmware
- unlocked bootloader (both options 'unlock' and 'unlock_critical')
- TWRP recovery
- Magisk
(these should be met if you went through all steps above...)
- newest BQ firmware from step '3 Set up the PC / Get all files'
On the PC go to the folder with the extracted BQ firmware .zip
Create a copy of 8953_fastboot_all_images.bat
Comment out or delete the following lines:
Code:
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot reboot
Here is a patch, if anyone is interested:
Code:
--- 8953_fastboot_all_images.bat 2017-08-09 12:27:24.000000000 +0200
+++ 8953_fastboot_all_images_nuv.bat 2017-09-10 22:07:54.794986400 +0200
@@ -37,8 +37,11 @@
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash cache cache.img
-fastboot flash userdata userdata.img
-fastboot flash recovery recovery.img
+
+rem nuv: omit userdata and recovery to keep data and TWRP
+rem fastboot flash userdata userdata.img
+rem fastboot flash recovery recovery.img
+
rem fastboot flash sec sec.dat
fastboot flash dsp adspso.bin
fastboot flash mdtp mdtp.img
@@ -47,7 +50,9 @@
fastboot erase DDR
fastboot flash boot boot.img
-fastboot reboot
+rem nuv: omit reboot to allow a manual reboot and start of TWRP before first boot of new image
+rem fastboot reboot
+
pause
exit
With the modified batch file ready to start, we connect our phone (phone is switched on and in system) and run the batch.
Code:
[...]
erasing 'DDR'...
OKAY [ 0.020s]
finished. total time: 0.023s
target reported max download size of 536870912 bytes
sending 'boot' (22485 KB)...
OKAY [ 0.502s]
writing 'boot'...
OKAY [ 0.132s]
finished. total time: 0.636s
Drücken Sie eine beliebige Taste . . .
After the batch file finishes, manually reboot the phone and go directly to recovery! Do not boot the system yet!
Reboot:
Code:
fastboot reboot
and choose recovery with volume up and volume down like earlier in section '4.3 Install TWRP and Magisk'
Now we flash Magisk from TWRP with the adb sideload function. (again , see step 4.3 Install TWRP and Magisk'
Code:
adb sideload ..\..\03_TWRP_Magisk\Magisk-v14.0.zip
Reboot to system.
All done.
6 Notes/Troubleshooting
6.1 System update notifications
As written in step '1 Intro' and '4.3 Install TWRP and Magisk' i did not let the phone get an internet connection after the wipe (bootloader unlock) and disabled the software update feature.
I don't know if this will reliably prevent the update notifications.
As a further note, user Schubbie stated on android-hilfe.de [10], that the OTA updates get saved to the path /data/data/com.bqreaders.ota/files/bq_update_ota.zip so maybe you can delete the file if an unwanted update notification pops up.
6.1 Troubleshooting
As an additional information to step '4.3 Install TWRP and Magisk'
At the point after flashing TWRP and starting it the first time, I let TWRP apply the system modifications.
After that i rebooted to check if the TWRP installation was successful...
I got "device is corrupt" when I wanted to boot into system. I continued the boot process with the power button and after that, the phone got stuck at the screen with the BQ logo and the text 'Powered by Android' (waited >10min).
To revive the phone from that state, you can flash the recovery and system images from the BQ firmware .zip
Important: Use the 'old' firmware which is still on your phone - the images have to match your current installation!
Bring the phone into fastboot mode and use the commands:
Code:
1.3.5_20170620-0532-bardock-user-594-Fastboot-FW\fastboot flash recovery recovery.img
1.3.5_20170620-0532-bardock-user-594-Fastboot-FW\fastboot flash system system.img
(In my case, the phone came with 1.3.5, so obviously I used this firmware .zip from BQ)
Now the phone is back to the state unlocked bootloader with stock rom and stock recovery.
Continue with step '4.3 Install TWRP and Magisk'.
7 Links
[1]
Official BQ website - Downloads Aquaris X Pro
https://www.bq.com/de/support/aquaris-x-pro/support-sheet
https://web.archive.org/web/20200320014304/https://www.bq.com/en/support/aquaris-x-pro/support-sheet
(
Firmware 1.4.3 | MD5: 16ff81c74642189a5d09f6b73feb06d5 | https://storage.googleapis.com/otas...0170809-1111-bardock-user-983-Fastboot-FW.zip
Drivers | https://shenron.bq.com/otas/2014/Smartphones/Aquaris_E5_LTE/Tools&Drivers/Drivers qualcomm + adb.rar
)
[2]
TWRP - ADB sideload information
https://twrp.me/faq/ADBSideload.html
[3]
SDK Platform Tools
https://developer.android.com/studio/releases/platform-tools.html
[4]
TWRP recovery
https://twrp.me/bq/bqaquarisxpro.html
Section 'Download Links'
[5]
TWRP - BQ devices
https://twrp.me/Devices/BQ/
[6]
[2017.9.6] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+]
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
https://github.com/topjohnwu/Magisk/releases
[7]
root Alternative
TWRP maintainer for Aquaris X (Kra1o5) mentions SuperSU in a forum about flashing TWRP and rooting
http://www.htcmania.com/showthread.php?t=1312725
http://download.chainfire.eu/supersu
[8]
[info] recovery menu on BQ devices
http://www.mibqyyo.com/en-articles/...lla/discussion/embed/?vanilla_discussion_id=0
[9]
[Anleitung] Aquaris X/X Pro Bootloader entsperren/unlock
https://www.android-hilfe.de/forum/...-pro-bootloader-entsperren-unlock.830125.html
[10]
Aquaris X/X Pro - Firmwareupdate mit Root
https://www.android-hilfe.de/forum/...s-x-x-pro-firmwareupdate-mit-root.834283.html
8 Changelog
2021-12-27: added info in chapter '4.1 Prepare phone' regarding OEM unlocking and WIFI
2021-02-05: added Info regarding BQs website on top of post
2020-07-31: added link to Magisk Github release page
2018-03-23: Added disclaimer...
2017-12-31: Edited info at top of post
2017-12-30: Played with the hide-content-buttons. Hopefully it'll be easier to navigate through the long post now. Adapted First sentences.
2017-12-26: Edited info at top of post
2017-11-18: Added info at top of post, moved changelog to post #1
2017-11-11: Added links to the [<number>] References - wow!
2017-11-11: fixed typos, little cosmetics, little text changes in '4.1 Prepare phone', corrected section references
2017-09-23: added pictures, codeblocks, formating...
2017-09-23: initial post, work in progress
[EOF]

9 Additional information, comments, ...
9.0 Latest working versions:
9.0.1 Android Oreo (Android 8.1.0)
Firmware 2.11.0 (Android 8.1.0 Oreo)
Download BQ Firmware 2.11.0 for BQ Aquaris X Pro
Download BQ Firmware 2.11.0 for BQ Aquaris X
TWRP 3.4.0-0 [2019-07-20]
Download TWRP for BQ Aquaris X Pro
Download TWRP for BQ Aquaris X
Magisk v20.4 stable (20400) / Magisk Manager App v7.5.1 (267)
Download from Magisk Forum Thread
Download from Magisk Github release page
Minimum required versions for Oreo:
BQ Firmware: 2.0.0 (Android Oreo 2.1.0)
prerelease from beta (see screenshot below for details)
the official update .zip (confirmed by iss0 in post#95))
TWRP 3.2.1-1 (<-- new version needed for Oreo)
Magisk v16.7 beta (see screenshot below)
MagiskManagerApp 5.8.3 (129)
9.0.2 Android Nougat (Android 7.1.1)
[2018-04-21]
BQ Firmware: 1.8.0
TWRP 3.2.1-0
Magisk v16.0
MagiskManagerApp 5.6.4 (112)
9.1 Update to firmware 1.5.1
As of 18.11.2017, BQ forgot to include adb and fastboot binaries in the new firmware package 1.5.1.
To update, simply copy the following files from the previous firmware package to the new directory:
Code:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
Proceed with instructions from post #1, section '5 Update to newest firmware'.
Don't forget to modify the .bat (comment out userdata, recovery and the reboot) and don't boot up to system after flashing. Directly go to recovery and reflash Magisk. (as described in section '5 Update to newest firmware'.)
The update has been successfully tested by ryazor (post #16) and me coming from firmware 1.4.3 and updating to 1.5.1)
For reference (maybe BQ will replace the .zip later), here is the checksum for the firmware which doesn't contain the binaries:
1.5.1_20171110-0910-bardockpro-user-1336-Fastboot-FW.md5
Code:
738664221520D446F689DCDDD5C611DF *1.5.1_20171110-0910-bardockpro-user-1336-Fastboot-FW.zip
9.2 Adb and fastboot on Linux/Ubuntu
User torbol reported that the adb and fastboot versions packaged with Ubuntu 16.04 are too old and don't support the commands for unlocking the bootloader. See his blog linked in Post #22 for further information.
Solution is to manually fetch the newer versions from the Android SDK.
9.3 Use of adblockers
If you want to use adblockers like AdAway which rely on the /system/etc/hosts file, you'll have to enable the support in the Magisk Manager app.
Symptom when trying to use the app without the switch: phone freezes when the app is given root access and tries to write it's changes.
9.3.1 Magisk v18.0 and up
Starting with Magisk v18.0, the setting for systemless hosts changed a little.
go to settings and tap the entry 'Systemless hosts', a notification toast will pop up at the bottom of the screen: 'added systemless hosts module'
check the modules tab; there will be a new module for systemless hosts support
reboot to activate the module
start your adbocker app and apply the /system/etc/hosts file changes
9.3.1 Before Magisk v18.0
Open MagiskManager, hop to settings and enable the switch 'Systemless hosts' (subtext "Systemless hosts support for Adblock apps").
9.4 Update TWRP
- Connect USB cable to PC
9.4.1 Flash new TWRP
- Boot into fastboot mode
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.5.1_20171110-0910-bardockpro-user-1336-Fastboot-FW>fastboot flash recovery ..\..\03_TWRP_Magisk\2017-12_Magisk-v15.0_TWRP-3.2.1-0\twrp-3.2.1-0-bardock_pro.img
target reported max download size of 536870912 bytes
sending 'recovery' (28152 KB)...
OKAY [ 0.636s]
writing 'recovery'...
OKAY [ 0.203s]
finished. total time: 0.845s
Stay in fastboot mode.
9.4.2 Reflash Magisk
Now reboot and directly start recovery:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.5.1_20171110-0910-bardockpro-user-1336-Fastboot-FW>fastboot reboot
rebooting...
finished. total time: 0.002s
- Start adb sideload mode ('Advanced' | 'ADB sideload').
Reflash Magisk:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.5.1_20171110-0910-bardockpro-user-1336-Fastboot-FW>adb sideload ..\..\03_TWRP_Magisk\2017-09_Magisk-v14.0_TWRP-3.1.1-0_xda-post\Magisk-v14.0.zip
Total xfer: 1.69x
Reboot to system.
9.5 Update Magisk
9.5.1 Update MagiskManager app
- Start MagiskManager
- when prompted (see screenshot) install new version.
9.5.2 Install new Magisk Version
Variant 1 (Update via TWRP recovery | adb sideload)
- Ignore the Update Notification in the MagiskManager app for the Magisk update (in this case v14.0 --> v15.0)
- Connect USB cable to PC
- Boot into TWRP recovery
- Start adb sideload mode ('Advanced' | 'ADB sideload')
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.5.1_20171110-0910-bardockpro-user-1336-Fastboot-FW>adb sideload ..\..\03_TWRP_Magisk\2017-12_Magisk-v15.0_TWRP-3.2.1-0\Magisk-v15.0.zip
Total xfer: 1.82x
Reboot to system.
Variant 2 (Update via MagiskManagerApp)
- Open MagiskManager App
- Tap 'install' on Update notification
- Choose 'Direct Install'
- Update will be installed
- Reboot
9.6 Uninstall Magisk+TWRP/Get back to stock
Use the following steps to unroot/uninstall Magisk and TWRP.
You'll need a PC with adb and fastboot and installed drivers, of course.
Tested with:
- BQ Firmware: 1.8.0
- TWRP 3.2.1-0
- Magisk v16.0
- MagiskManagerApp 5.6.4 (112)
9.6.1 Uninstall Magisk
- Open MagiskManager app
- select 'uninstall' | 'complete uninstall'
- wait a minute or so
- reboot via power button
- phone will be booting, do one reboot (at least for me), booting again
- phone is back in system without Magisk
9.6.2 Uninstall TWRP/Install stock recovery
- Get BQ Firmware .zip which matches your currently installed system (For example '1.8.0_20180323-0901-bardockpro-user-1421-Fastboot-FW.zip')
- Extract the file 'recovery.img'
- Connect the phone to PC via USB and boot into fastboot mode:
Code:
adb reboot bootloader
- Flash stock recovery:
Code:
fastboot flash recovery recovery.img
- wait a minute or so (just to be sure)
- reboot phone:
Code:
fastboot reboot
- phone boots,
- phone is back in system
Congratulations, not you got your phone in stock state with one exception: the bootloader is still unlocked! That means, that the google safety net check will fail (CTS profile).
Now you could re-lock the bootloader if you want to completely go back to the factory state, but if you choose to do so, keep in mind that the phone will be erased completely when locking the bootloader!
9.7 re-locking the bootloader
This chapter describes how to re-lock the bootloader. After doing that, your phone will be in the default factory state regarding all previous modifications.
Before going on, you should have uninstalled Magisk and TWRP (see chapter '9.6 Uninstall Magisk+TWRP/Get back to stock').
Warning: All data+settings will be erased when locking the bootloader! (Everything; That means apps, app settings, personal data like pictures, music, etc.)
As reference, here are the tool versions I used in my successful test:
Code:
>adb version
Android Debug Bridge version 1.0.40
Version 4797878
Installed as D:\programme\Android\platform-tools\adb.exe
Code:
>fastboot --version
fastboot version 28.0.0-4797878
Installed as D:\programme\Android\platform-tools\fastboot.exe
Follow these steps to lock the bootloader:
- action: switch off phone
- action: remove SIM and Micro-SD
- action: enter fastboot mode: vol_down + pwr
- action: connect usb cable
Code:
>fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
OKAY
Code:
>fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY
Code:
>fastboot flashing lock_critical
OKAY
- reboot
- screen: 'erasing'
- reboot
- screen: 'Aquaris X' boot screen
- screen: 'Encrypting' with green android logo
- screen: 'Aquaris X' boot screen
- several minutes ...
- screen: 'Welcome'
- action: restart with power button
- action: choose 'fastboot' with volume buttons and confirm with power button
Code:
>fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY
Code:
>fastboot flashing lock
OKAY
- reboot
- screen: 'erasing'
- reboot
- screen: 'Aquaris X' boot screen
- screen: 'Encrypting' with green android logo
- several minutes ... (approx. 3 minutes)
- screen: 'Welcome'
- action: disconnect usb cable
- action: switch off with power button
- action: enter fastboot mode: vol_down + pwr
- action: connect usb cable
Code:
>fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY
Code:
>fastboot reboot
Rebooting
Finished.
- phone will be booting to system.
- action: skip through the welcome screens
- action: go to settings | system | about phone | tap 'build number' 7 times
- action: go to settings | system | developer options | OEM unlocking
- note: without internet connection, the OEM unlocking option will be greyed out.
- action: connect to wifi, go back to the system menu and wait a minute
- action: go back to developer options | OEM unlocking
- action: switch off OEM unlocking
- action: disconnect usb cable
- action: switch off with power button
- action: enter fastboot mode: vol_down + pwr
- action: connect usb cable
Code:
>fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY
Code:
>fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 0
OKAY
Code:
>fastboot reboot
Rebooting
Finished.
DONE
9.8 update the phone via official OTA
This chapter describes how to use the OTA update feature. Personally, I like the other way (flashing the update zip) much more and think the other way is easier, but I recently did this, because I needed the OTA for the Oreo beta, so here is the information.
Precondition: Phone with stock rom (obviously), uninstalled Magisk+TWRP (stock recovery)! See chapter '9.6 Uninstall Magisk+TWRP/Get back to stock'. The bootloader can stay unlocked.
- Go to settings | about phone | System updates | update (check for updates)
- You should get a notification similar to the following one in the screenshot:
- Download and install the System update
done
9.8 Install TWRP+Magisk on BQ FW 2.0.0 (Android Oreo 2.1.0)
colors: PC, phone
Started with the stock firmware 2.0.0 (Android 8.1.0 Oreo) with unlocked bootloader (and stock bootimage and recoveryimage).
> adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
>fastboot flash recovery twrp-3.2.1-1-bardock_pro.img
target reported max download size of 534773760 bytes
sending 'recovery' (35304 KB)...
OKAY [ 0.813s]
writing 'recovery'...
OKAY [ 0.250s]
finished. total time: 1.063s
> fastboot reboot
rebooting...
finished. total time: 0.016s
Don't boot. Directly go to recovery
Advanced | ADB Sideload
>adb sideload Magisk-v16.4.zip
Total xfer: 1.68x
9.9 to be continued
[...]
10 Changelog (this post)
2020-07-31: updated latest version info
2019-10-12: updated latest version info
2019-10-08: updated latest version info
2019-06-15: updated latest version info
2019-06-05: updated latest version info
2019-05-22: updated latest version info
2019-05-20: updated latest version info
2019-05-03: updated latest version info
2019-04-18: updated latest version info
2019-04-02: updated latest version info
2019-02-04: updated latest version info
2019-01-26: updated latest version info
2019-01-14: updated latest version info
2018-12-17: updated+expanded section '9.3 Use of adblockers'
2018-12-08: updated latest version info
2018-11-04: added chapter '9.7 re-locking the bootloader'
2018-10-30: rearranged the chapters, fixed 9.7/9.8
2018-10-21: updated latest version info
2018-09-29: updated latest version info
2018-09-01: updated latest version info
2018-08-xx: updated latest version info
2018-07-12: updated latest version info
2018-07-08: updated latest version info
2018-05-08: updated latest version info + added 9.8 BQ FW 2.0.0 / Oreo 2.1.0
2018-04-22: added 9.6 and 9.7 - Uninstall + OTA updates
2018-03-28: updated latest version info
2018-04-21: updated latest version info
2018-03-23: updated latest version info
2018-03-11: updated latest version info
2018-02-22: updated latest version info
2018-02-10: updated latest version info
2018-01-13: updated latest version info
2018-01-12: updated latest version info
2018-01-03: added latest version info
2017-12-30: added hide-content buttons
2017-12-29: changes in 9.5 - How to update Magisk
2017-12-26: added 9.4 + 9.5 - How to update TWRP and Magisk
2017-12-26: added 9.3 with information for adblocker users (systemless hosts file/AdAway)
2017-11-19: added 9.2 with Information for linux users
2017-11-18: added additional/dynamic information here in post #2, general documentation still in post #1

many thanks for the guide
just a question
If we choose to Keep Read Only in TWRP, at the next reboot the recvoery was overwrited by stock....

ironia. said:
many thanks for the guide
just a question
If we choose to Keep Read Only in TWRP, at the next reboot the recvoery was overwrited by stock....
Click to expand...
Click to collapse
Hi ironia,
hm..
There is no single restart in between the steps mentioned below. I think i had kind of the same problem when restarting at any point.
When i chose to apply the TRWP changes, my phone did not boot anymore, so that was no option for me.
The steps i mean are from section '4.3 Install TWRP and Magisk':
choose 'Keep Read Only' on first TWRP start
flash Magisk from TWRP with the adb sideload
reboot to system from TWRP
get to the welcome wizard
Did you restart before finishing the steps?

I still don't know where do I need to type all of that commands can you please explain a bit ? My phone is already in Fastboot Mode but where do I need to type those commands in?

roanepv said:
I still don't know where do I need to type all of that commands can you please explain a bit ? My phone is already in Fastboot Mode but where do I need to type those commands in?
Click to expand...
Click to collapse
Hi roanepv,
the commands are for the Windows/DOS command prompt on the PC.
You can open the prompt with win+r and type 'cmd' then you'll have to change to the correct directory where you downloaded the files...
Keep in mind that you can brick your phone if something goes wrong.

On the first step I open cmd then I type this? : C:\Users\André\Downloads\BQ\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot flashing get_unlock_ability
---------- Post added at 01:27 PM ---------- Previous post was at 12:39 PM ----------
roanepv said:
On the first step I open cmd then I type this? : C:\Users\André\Downloads\BQ\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot flashing get_unlock_ability
Click to expand...
Click to collapse
It says is not a recognized as an internal or external operable program or batch file. What to do?
---------- Post added at 01:51 PM ---------- Previous post was at 01:27 PM ----------
roanepv said:
On the first step I open cmd then I type this? : C:\Users\André\Downloads\BQ\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot flashing get_unlock_ability
---------- Post added at 01:27 PM ---------- Previous post was at 12:39 PM ----------
It says is not a recognized as an internal or external operable program or batch file. What to do?
Click to expand...
Click to collapse
Ok , I unlocked bootloader with BQ Firmware Flash Tool and then proceed to install TWRP , everything went fine but ADB Sideload is taking alot to start.... Can I flash Magisk Directly without ADB?

You'll have to copy the zip to the phone, but yes, you can install the zip from within TWRP.

Thank a lot for the detailed guide which is extremely helpful indeed! I've gone through all the steps and everything works fine! Thanks again.

vomil said:
Thank a lot for the detailed guide which is extremely helpful indeed! I've gone through all the steps and everything works fine! Thanks again.
Click to expand...
Click to collapse
Hi vomil, thanks for the feedback!
Hoped it would work when reproducing everything step by step.

Thank you for this comprehensive guide. It worked like a charm!

Hello, I've been trying to install modules on the Magisk manager but they don't install whatever the method I use.
I tried installing it directly from the modules download page within the app, it downloads and shows it installing on the terminal, I then reboot but when I go to the modules section I have no modules installed.
I tried flashing directly from within the app, rebooted, no modules installed again..
I even tried flashing from TWRP it said successful installation, I rebooted but still as always no modules were installed again...
Does anyone shares this problem or knows a way of fixing it? Thank you for your time.
I'm using app version 5.4.0(57) and Magisk version 14.0
Sent from my Aquaris X Pro using Tapatalk

Hi krillin666,
i didn't use the module feature so far.
Can you give me a link to a module i can test? What should i do? Add it in Magisk Manager, reboot and check if its still there?

nuv said:
Hi krillin666,
i didn't use the module feature so far.
Can you give me a link to a module i can test? What should i do? Add it in Magisk Manager, reboot and check if its still there?
Click to expand...
Click to collapse
Hello, just try any module really, because I tried at least 10 different.
You could try installing the busybox module or the xposed for example.
As I said I tried 3 different methods, the easiest one is to go to the downloads tab and search for a module and install it, reboot and then go to the modules tab to see if it's installed.
Thank you.
Sent from my Aquaris X Pro using Tapatalk

Hi krillin666,
took TaskerRootBuildProp-1.03.zip from here: https://forum.xda-developers.com/showpost.php?p=71862904&postcount=12243
used the '+' Sign in MagiskManager to add the module:
Directly after install:
Rebooted via power button menu.
After reboot in MagiskManager:
..seems to work I guess? (Didn't verify otherwise, but according to your previous post, the module entry should not be there if i had the same problem?)

Will step 5 (upgrading Firmware) work with the new FW 1.5.1 without losing data?
Thanks in advance!
Update: Yes, can confirm, it works

ryazor said:
Will step 5 (upgrading Firmware) work with the new FW 1.5.1 without losing data?
Thanks in advance!
Click to expand...
Click to collapse
UUh, new firmware -- I don't know yet. Don't know if i can update this weekend.
If you are faster than me, please give feedback, i will refresh some information in first/second posts.
Better create a TWRPbackup before
edit: I have not looked into the update .zip yet - if the batch file is identical/similar to the one before, it should work accourding to section 5 ... I hope so...

nuv said:
Hi krillin666,
took TaskerRootBuildProp-1.03.zip from here: https://forum.xda-developers.com/showpost.php?p=71862904&postcount=12243
used the '+' Sign in MagiskManager to add the module:
View attachment 4335160
Directly after install:
View attachment 4335161
Rebooted via power button menu.
After reboot in MagiskManager:
View attachment 4335162
..seems to work I guess? (Didn't verify otherwise, but according to your previous post, the module entry should not be there if i had the same problem?)
Click to expand...
Click to collapse
Strange, that doesn't happens to me at all maybe it's a bug. What's the magick version and manager you're using?
Sent from my Aquaris X Pro using Tapatalk

krillin666 said:
Strange, that doesn't happens to me at all maybe it's a bug. What's the magick version and manager you're using?[...]
Click to expand...
Click to collapse
oh, sorry, forgot to mention; the same as yours: Magisk v14.0 and Manager App 5.4.0 (57).
edit: maybe try with the simple module I linked in my prev. post?

ryazor said:
Will step 5 (upgrading Firmware) work with the new FW 1.5.1 without losing data?
Thanks in advance!
Update: Yes, can confirm, it works
Click to expand...
Click to collapse
Hey, thank for testing! Seems BQ forgot to include adb and fastboot in the update package
I assume, you used the binaries from the prev. zip (1.4.3)?
Successfully updated the phone myself and will update thread posts 1+2 shortly.

Develop Bugs

welcome