Database Develop

[GUIDE] How to Unlock, install Recovery, and get Rooted

{
"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"
}
YOU NEED TO KNOW
IF YOU'RE 32BIT OR 64BIT
( How to find out if your device is 32bit or 64bit )
( Briefly: US = 32bit, EU/AUS = 64bit )
BEFORE CONTINUING, MAKE BACKUPS OF
ANYTHING ON YOUR DEVICE THAT YOU WISH TO KEEP!
ALL COMMANDS ARE IMPORTANT AND NEED TO BE FOLLOWED STRENUOUSLY!
BY FOLLOWING THIS GUIDE YOU ARE VOIDING YOUR WARRANTY
AND I DO NOT ASSUME ANY RESPONSIBILITY IF YOUR PHONE BLOWS UP
BACKUP YOUR STUFF!!!
MAKE A BACKUP OF STOCK WITH RECOVERY ASAP!!!!
For a GUI based method, try WinDroid
Please give Thanks to these people
for making this process possible:
@beaups, @Dees_Troy, @jmz,
@wolfaas12345, @CurbThePain,
@rbheromax, and @greeneyes2910​
Prerequisites
ADB & Fastboot (Also, add ADB to PATH)
HTC Drivers
An account with HTCdev (if you're not registered, you can do that here)
Enable Developer Options
If 32bit - TWRP image
If 32bit - SuperSU binary
If 64bit - PhilzTouch_Recovery image (You'll need to extract the recovery.img from the .zip)
If 64bit - @rbheromax's 64bit Rooted Kernel
Let's get to work.Unlocking the bootloader (This process is the same for 32bit and 64bit devices)
Power down the device
Hold the down volume and power buttons at the same time. This will boot you into hboot
Using the volume rocker select FASTBOOT and press the power button
Connect the device to your computer
Open cmd and ensure that your device is recognized by typing: fastboot devices
You should get something similar to the following: FA4AJxxxxxxx fastboot
Now type, fastboot oem get_identifier_token , this is your token you'll need for HTCdev
Minimize cmd and go to: htcdev.com/bootloader/ and select the HTC Desire from the dropdown
Skip to Step 5 and in cmd right click and select Mark, select the token starting at the top <<<< and ending at the bottom >>>>> (everything in the red square, see image), paste this into the textbox at the bottom of the page and submit
Go to the email address you used to register with HTCdev and there will be an email with an attachment named Unlock_code.bin, download the attachment
In cmd, cd to the folder you've downloaded Unlock_code.bin to
Now type, fastboot flash unlocktoken Unlock_code.bin
As I said above, this will erase everything on your phone (pictures, sms, videos, apps, etc) and restore it to stock, so I hope you made backups
Your device will now have a screen that asks if you want to unlock the bootloader, use the volume rocker to select and the power button to enter
Once it's done your phone will reboot, power back down (or remove the battery and reinsert) and boot to hboot, your device should now say **** UNLOCKED **** at the top
STOP!
LET'S BE CAUTIOUS AND MAKE A BACKUP OF STOCK BEFORE WE DO ANYTHING ELSE!​​
If your device is connected, disconnect it
Power down the device
Hold the down volume and power buttons at the same time to boot into hboot
Using the volume rocker select FASTBOOT and press the power button
Connect the device to your computer
If you closed cmd, reopen it and cd to the folder that you downloaded openrecovery-twrp-2.8.5.0-a11.img or extracted recovery.img to
32bit - Now type: fastboot boot openrecovery-twrp-2.8.5.0-a11.img
64bit - Now type: fastboot boot recovery.img
Tap Backup
Change the name of the backup to something like "Pure Stock"
Swipe to Back Up
Installing TWRP/PhilzTouch
If your device is connected, disconnect it
Power down the device (if you're still in TWRP from making a backup, back out to the main menu and tap Reboot, then tap Power Off)
Hold the down volume and power buttons at the same time to boot into hboot
Using the volume rocker select FASTBOOT and press the power button
Connect the device to your computer
If you closed cmd, reopen it and cd to the folder that you downloaded openrecovery-twrp-2.8.5.0-a11.img or extracted recovery.img to
32bit - Now type: fastboot flash recovery openrecovery-twrp-2.8.5.0-a11.img
64bit - Now type: fastboot flash recovery recovery.img
Let it do it's thing and now you have TWRP or PhilzTouch installed on your device
Getting Rooted (32bit)
Power down your device if it is booted (or by taking the battery out and reinserting it)
Hold the down volume and power buttons at the same time to boot into hboot
Using the volume rocker select RECOVERY and press the power button
This will boot you into TWRP
Open cmd and cd to the folder that you downloaded UPDATE-SuperSU-v2.40.zip
Now type: adb push UPDATE-SuperSU-v2.40.zip /sdcard/UPDATE-SuperSU-v2.40.zip
In TWRP tap install and in the file browser tap sdcard and then tap UPDATE-SuperSU-v2.40.zip
Flash UPDATE-SuperSU-v2.40.zip
Getting Rooted (64bit)
Power down your device if it is booted (or by taking the battery out and reinserting it)
Hold the down volume and power buttons at the same time to boot into hboot
Using the volume rocker select FASTBOOT and press the power button
Open cmd and cd to the folder that you downloaded HTC-Desire-510-64-Bit-Root.img
Type: fastboot flash boot HTC-Desire-510-64-Bit-Root.img
Then: fastboot reboot
Congrats, we're done!
So... what do I do now?
Check out the stuff going on over in the development sections of course!
Android Development - Original Android Development​
​

Great guide. That process worked for me, except SuperSU 2.16 is an old version and when the Play Store updated the front end I had a hard time updating the binaries. Maybe update the link to the newest 2.40 SuperSU or is there a reason I should use the old one?
Plus for anyone who is cautious (I believe there are different versions of the hardware) they can use the command "fastboot boot openrecovery-twrp-2.8.1.0-a11.img" to test and boot to the TWRP. If anyone doesn't want to change their recovery because they don't have a backup yet, then from the booted recovery. Backup the system to and SD and then install the SuperSU zip and it will be rooted. Then use flashify to backup the original recovery and kernels.

protectivedad said:
Great guide. That process worked for me, except SuperSU 2.16 is an old version and when the Play Store updated the front end I had a hard time updating the binaries. Maybe update the link to the newest 2.40 SuperSU or is there a reason I should use the old one?
Plus for anyone who is cautious (I believe there are different versions of the hardware) they can use the command "fastboot boot openrecovery-twrp-2.8.1.0-a11.img" to test and boot to the TWRP. If anyone doesn't want to change their recovery because they don't have a backup yet, then from the booted recovery. Backup the system to and SD and then install the SuperSU zip and it will be rooted. Then use flashify to backup the original recovery and kernels.
Click to expand...
Click to collapse
Thanks, I've updated the links so it's 2.40.

Does this also give you S-off?

Burtrum57 said:
Does this also give you S-off?
Click to expand...
Click to collapse
No, but flashing a kernel with write protection removed will allow you to manipulate system files, so you can remove bloatware and customize your device.
Sent from my HTC Desire 510

I guess you do this via fastboot?

You can flash and back up boot.img's via a free app from the Play Store called Flashify
Sent from my HTC Desire 510

Boost Mobile Desire 510
I have the Boost Mobile variant of the Desire 510, model number OPCV1. Before I follow through with this I am wondering if I have the 32 bit or 64 bit processor? I cannot seem to find a straight answer online anywhere. I have seen some apps that you can download and run to find the info but I do not have enough space to download them with all this crap that comes preloaded, hence my reason for wanting root. Any help is appreciated and thanks in advance!

jdelong90 said:
I have the Boost Mobile variant of the Desire 510, model number OPCV1. Before I follow through with this I am wondering if I have the 32 bit or 64 bit processor? I cannot seem to find a straight answer online anywhere. I have seen some apps that you can download and run to find the info but I do not have enough space to download them with all this crap that comes preloaded, hence my reason for wanting root. Any help is appreciated and thanks in advance!
Click to expand...
Click to collapse
Boost only sells the 32-bit variant.

hi
thanks for this topic
I have one HTC desire 510 can't turn it ON is stoping in HTC logo
I can get the Bootloader menu
could you help me to flash it please
thanks

So my htc desire 510 for virgin mobile has a 64-bit processor?

iversonwings said:
So my htc desire 510 for virgin mobile has a 64-bit processor?
Click to expand...
Click to collapse
Use this app to find out your processor: https://play.google.com/store/apps/details?id=com.cpuid.cpu_z&hl=en
And this will help you determine: http://forum.xda-developers.com/showpost.php?p=57900390&postcount=12

What a guy
Dude
you are the man,,!!
After my GF and I kinda got swindled into this phone by believing
in my long time friend HTC and Boost ,, I thought we were stuck with a dud
but thanks to you explaining in detail that boost only sells 32 bit versions etc and your simple to follow directions I AM ROOTED AND SO IS SHE now I think I can make this phone work thx
JD:highfive:

kidputer said:
Dude
you are the man,,!!
After my GF and I kinda got swindled into this phone by believing
in my long time friend HTC and Boost ,, I thought we were stuck with a dud
but thanks to you explaining in detail that boost only sells 32 bit versions etc and your simple to follow directions I AM ROOTED AND SO IS SHE now I think I can make this phone work thx
JD:highfive:
Click to expand...
Click to collapse
No problem. Thanks for the thanks. You should also go and thank these people if you've got the time:
dipspit said:
Please give Thanks to these people
for making this process possible:
@beaups, @Dees_Troy, @jmz,
@wolfaas12345, and @CurbThePain​
Click to expand...
Click to collapse

how to sim-unlock
my sprint HTC desire 510's bootloader is unlocked, TWRP is installed, and rooted.
how can i use it in CHINA with CDMA?
when i put i sim card in,it display unkown card

tianchaodiaosi said:
my sprint HTC desire 510's bootloader is unlocked, TWRP is installed, and rooted.
how can i use it in CHINA with CDMA?
when i put i sim card in,it display unkown card
Click to expand...
Click to collapse
Use the search function. We don't have a sim unlock developed yet. Try searching around in the other HTC forums for a CDMA unlock yourself or wait until someone confirms a method.

Recovery
Hi, first of all thanks for your tutorial !
I did all of the instruction but after installing custom recovery, it's impossible to get into it.
When i choose recovery, it reboot on normal mod.
What can i do to flash su binary ?
Thanks again !
Edit: After long research i finally understood there are 2 kind of 510... 32 & 64bits & i have this last one so i probably can't access to my recovery beacause of that... A bit disappointed, i had only 4gb free space right now on my phone & can't use an apps to link my sd.

I just successfully rooted my Virgin Mobile (VM) HTC desire 510 with this guide, thanks so much! I verified this with root checker basic. I came upon some hiccups, but that was because I had to follow every single step. I'm hoping the bloatware won't come back, I'll keep you guys updated. Is there a list of safe bloatware that I can remove?

iversonwings said:
I just successfully rooted my Virgin Mobile (VM) HTC desire 510 with this guide, thanks so much! I verified this with root checker basic. I came upon some hiccups, but that was because I had to follow every single step. I'm hoping the bloatware won't come back, I'll keep you guys updated. Is there a list of safe bloatware that I can remove?
Click to expand...
Click to collapse
In my opinion all carrier bloatware on the phone you can just remove. Same with most of the Google apps and most of the HTC apps. There's this thread.

when i try to run fastboot,keep getting message adbwinapi.dll is missing from computer! can anyone help with problem?

Huawei Honor Note 8 - Unlock Bootloader, TWRP, Xposed Framework

{
"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"
}
This is my first walkthrough so I will do my best to do this properly. The Honor Note 8 does not have a forum yet, and this is the third thread for this phone. Hopefully we can get a forum up soon.
PLEASE NOTE THAT UNLOCKING BOOTLOADER WILL WIPE YOUR DEVICE AND POSSIBLY VOID YOUR WARRENTY!!!
I'M NOT RESPONSIBLE IF SOMETHING DOESN'T WORK.
Unlock Bootloader
Follow the steps here to begin the Bootloader Unlock process:
https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code
1. a) Install the application
1. b) Follow the steps on the above page to put phone into "Manufacture Mode"
1. c) Under "Select Manufacturer", choose "Huawei Phones" and under "Select Model", choose the model of your phone
1. d) Click on "Buy Credits". You should end up being emailed a username and password, return to the Unlocker Client, and input those two
1. e) The Unlocker Client should return the bootloader unlock code
2. a) Enable Developer Options by clicking on the build number multiple times
2. b) Turn on USB Debugging
3. Prepare TWRP custom recovery before preceeding further. You can get it from here: https://drive.google.com/open?id=0B4xzs81XsmURVTRnUDJHdl9CQlE
3. Prepare and install ADB and Fastboot tools. I used this one http://forum.xda-developers.com/showthread.php?t=2588979
4. Go into the folder with your recovery and open a CMD (if you used system-wide ADB as linked above, otherwise place recovery in your ADB folder)
5. Put the phone into Bootloader mode with:
Code:
adb reboot bootloader
. This will take you to the bootloader mode (white screen with some small text)
6. Now type:
Code:
fastboot oem unlock <UNLOCK_CODE>
where
Code:
<UNLOCK_CODE>
is the bootloader code that the Unlocker Client gave you
Loading TWRP Custom Recovery
7. Your phone may reboot when the process is complete. We want to go back into Bootloader mode, so follow Step 5 again to go back to bootloader mode
8. Now type:
Code:
fastboot flash recovery <NAME_OF_YOUR_RECOVERY.img>
The recovery will flash over to your device. We want to reboot into the recovery mode.
9. Now type:
Code:
fastboot reboot
but just before you hit ENTER on that command, start holding VOLup and VOLdown at the same time (as explained below)
This phone has two recoveries on it, which is great since it makes it really hard to brick. In order to access custom recovery, you need to hold down both VOL buttons during boot process (from the very beginning) in order to access the custom recovery.
Once you have entered TWRP, you will most likely notice that it is in CHINESE. If you don't read chinese, follow the steps below to change to English UI in TWRP:
Change to English UI in TWRP
10. TWRP has two columns of 4 buttons, 8 buttons total. I have labeled the buttons as per their position as below:
1 2
3 4
5 6
7 8
11. Click button 6 to go to the Settings, then click on the "Globe" icon, then switch to english and click the button in the bottom right corner.
BACKUP!!
12. I highly recommend you now do a TWRP backup and place the backup on an External SD card (not the internal memory). This will save your ass if you mess anything up or it doesn't work for you. Do a full backup (select ALL of the options).
Installing Xposed
Grab the Installer APK here: http://forum.xda-developers.com/showthread.php?t=3034811
and the Framework zip here: http://dl-xda.xposed.info/framework/sdk23/arm64/
Put both files onto your SD card.
13. Boot into your rom, install the APK file (you may need to enable "unknown sources")
14. Then boot back into TWRP. Do this by restarting the phone, and just as the screen goes black, hold down both VOL buttons until you see text on the screen.
15. Install the framework, wipe cache/dalvik and reboot the phone
ROMs
There are several roms, all of which can be found here: http://forum.xda-developers.com/general/general/huawei-honor-note-8-roms-t3487575
I will try to update this post with instructions on how to install them once I have the process down properly.
Thanks to:
@benmeroff for his posting of all of those ROMs and his work on the original thread.

The link to the xposed installer is dead

jdantow said:
Installing Xposed
Grab the Installer APK here: http://forum.xda-developers.com/show....php?t=3034811
Click to expand...
Click to collapse
Just another small reminder this Xposed apk link is broken. Could I just download any Xposed apk or was this link for a specific version for the Note 8?
Thanks

remix435 said:
The link to the xposed installer is dead
Click to expand...
Click to collapse
Thank you! I updated the link, can you confirm it is working now from your end? Thanks so much!
The thread ID is 3034811 so if you take
Code:
http://forum.xda-developers.com/showthread.php
and add
Code:
?t=3034811
it should work for you

jlomein said:
Just another small reminder this Xposed apk link is broken. Could I just download any Xposed apk or was this link for a specific version for the Note 8?
Thanks
Click to expand...
Click to collapse
Thank you! I updated the link, can you confirm it is working now from your end? Thanks so much!
The thread ID is 3034811 so if you take
Code:
http://forum.xda-developers.com/showthread.php
and add
Code:
?t=3034811
it should work for you

Hopefully either a camera port or a camera hack can come about from developing. Anybody know about possible camera hack thats the only thing (IMO) this phone needs

jdantow said:
Thank you! I updated the link, can you confirm it is working now from your end? Thanks so much!
Click to expand...
Click to collapse
Thanks, downloaded Xposed 3.1.1 apk from that link now.
Cheers

hi
after i flashed trwp and did back up i stuck in bootloop
tried to flash kingvip rom - no luck. tried to recover from back up but stil in boot loop.
can anyone help me, please

Anyone happen to have the img for the modem? I believe mine may be corrupted.

hi i will my boodloader unlock my Note 8. The phone will not unlock. I have the ulock key. I hvae the Build Nummber B027.

Hi guys, a question...
The is no way I can install this drivers that are required... if I click the setup icons nothing happens at all, and if i try manually all i get is 4x "Android device" in the device manager, and locating drivers in the designated folders does not help, it still says "windows did not find the driver for your device...."
Anyone maybe had a similar problem/solution?
Thanksss

Bubreg said:
Hi guys, a question...
The is no way I can install this drivers that are required... if I click the setup icons nothing happens at all, and if i try manually all i get is 4x "Android device" in the device manager, and locating drivers in the designated folders does not help, it still says "windows did not find the driver for your device...."
Anyone maybe had a similar problem/solution?
Thanksss
Click to expand...
Click to collapse
Just google huawei drivers.... I had the same question but when i installed HiSuite the drivers was inside - it work fine, but it will always pop up when you connecting phone...

falc1 said:
Just google huawei drivers.... I had the same question but when i installed HiSuite the drivers was inside - it work fine, but it will always pop up when you connecting phone...
Click to expand...
Click to collapse
Thank you man, worked like a charm! I got the bootloader code... but since it's gonna wipe everything if I unlock it, I'm gonna wait until the next weekend most probably, too busy these days.

Hi guys,
i was able to unlock the bootloader but i can't flash the recovery and every time i try it display "remote: command not allowed".

Good morning.
I hope for Christmas to be a holder of Honor Note 8.
To unlock the bootloader you need to pay 4 euro through dc-unlocker.com program?
Thank you

m3sari0 said:
Hi guys,
i was able to unlock the bootloader but i can't flash the recovery and every time i try it display "remote: command not allowed".
Click to expand...
Click to collapse
Same thing happend to me
I relocked the bootloader then unlock it again and it works

player1990 said:
Same thing happend to me
I relocked the bootloader then unlock it again and it works
Click to expand...
Click to collapse
thanks man it worked.

TWRP - changing language
OP - thank you for this thread. Was able to follow the steps and get most of the things accomplished.
One thing that i am having trouble with is - changing the TWRP language from Chinese to English. In button #6, the globe icon is not even clickable. All others are, but that one is not. Any ideas? Thanks!
EDIT: I got it to work. It seems some icons in the corners of the screen can be a little hard or slow to respond... if you (a future reader) are having the same issue - try kind of mini swiping in circles over that icon and it will eventually respond.

Hi,
I requested the unlock code on the Huawei site but I get this error:
The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.
How can I do?
Some might apply to me

MarkAndroid said:
Hi,
I requested the unlock code on the Huawei site but I get this error:
The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.
How can I do?
Some might apply to me
Click to expand...
Click to collapse
You have to wait 14 days or pay for the credits on DC-unlocker app

[RECOVERY] TWRP 3.3.1 Lenovo Z6 Pro

DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION:
Pre-Requirements
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here
Pre-Requisite 3
Your device needs this with unlocked bootloader
Pre-Requisite 4
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device
Settings -> Advanced settings -> Developer Options
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'ZUI version' entry
A pop-up should appear, telling you 'now you are a developer'
And now, how to install:
1.Reboot phone to Fastboot mode (via adb -type adb reboot bootloader)
2.Download patched vbmeta and TWRP recovery
3.Extract it to folder with minimal adb and fastboot
4.Open cmd in this folder and type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5.Then type fastboot reboot bootloader
6.Type fastboot flash recovery twrp_3.3.1_decrypt_works_by_alexeei.img
7.Press volume - and select Reboot recovery, then press power button
8.Enjoy
What worked:
All functions (may be if not, please say). Also TWRP now see exFAT microsd.
Thanks wzsx150 for it's TWRP for Lenovo Z5 Pro GT, some decrypt stuff taken from it.

This is f*cking awesome. Thank you for your efforts. Will install asap and bring some feedback.

Is it working ? Any custom roms then ?

Please provide custom ROM the official ROM is no less than terrible and bad.

Finally compiled TWRP with decryption support, added in first post

hammad5507 said:
Please provide custom ROM the official ROM is no less than terrible and bad.
Click to expand...
Click to collapse
There are some "globalised" china roms which are doing a decent job (with notifications sound fixed, chinese bloatware removed and google services installed), I recommend the one made by Francko76.
Also you can try all the treble stuff out there. I only tried two GSIs so far and I went back to Francko´s build.
Anyway I´m like you looking forward z6 pro dedicated custom roms.

descarao81 said:
I recommend the one made by Francko76.
Click to expand...
Click to collapse
Can you share a link to the Roms you mentioned ?
thanks

descarao81 said:
There are some "globalised" china roms which are doing a decent job (with notifications sound fixed, chinese bloatware removed and google services installed), I recommend the one made by Francko76.
Also you can try all the treble stuff out there. I only tried two GSIs so far and I went back to Francko´s build.
Anyway I´m like you looking forward z6 pro dedicated custom roms.
Click to expand...
Click to collapse
benjieb said:
Can you share a link to the Roms you mentioned ?
thanks
Click to expand...
Click to collapse
what rom is Francko´s build? if you have a link, can you share it please?

Sorry to ask, is this vbmeta patched only for this device or can i installed in others device ?

Please share the links
Please share links for the Franko's build.
and also is there any custom pie rom available??
Pls share if any.. I am very unsatisfied with the global rom. Pls help.

@alexei sir, can you make custom kernel or give way to our devices gets exfat support ?

this is twrp for Lenovo Z6 (not pro) ?

geepnozeex said:
this is twrp for Lenovo Z6 (not pro) ?
Click to expand...
Click to collapse
No this is Twrp for Z6 Pro ( L78051 )

Very tempted to get this phone... has anyone try with phh’s GSI? Does under screen scanner works?

alexeei said:
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION:
Pre-Requirements
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here
Pre-Requisite 3
Your device needs this with unlocked bootloader
Pre-Requisite 4
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device
Settings -> Advanced settings -> Developer Options
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'ZUI version' entry
A pop-up should appear, telling you 'now you are a developer'
And now, how to install:
1.Reboot phone to Fastboot mode (via adb -type adb reboot bootloader)
2.Download patched vbmeta and TWRP recovery
3.Extract it to folder with minimal adb and fastboot
4.Open cmd in this folder and type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5.Then type fastboot reboot bootloader
6.Type fastboot flash recovery twrp_3.3.1_decrypt_works_by_alexeei.img
7.Press volume - and select Reboot recovery, then press power button
8.Enjoy
What worked:
All functions (may be if not, please say). Also TWRP now see exFAT microsd.
Thanks wzsx150 for it's TWRP for Lenovo Z5 Pro GT, some decrypt stuff taken from it.
Click to expand...
Click to collapse
At step 4 I'm getting "fastboot: unknown option -- disable-verity"
Any idea?
Thanks

threeeye said:
At step 4 I'm getting "fastboot: unknown option -- disable-verity"
Any idea?
Thanks
Click to expand...
Click to collapse
NVM, just updated the adb tools and now everything is good

Restore stock bootloader?
Hello, I recently went through the whole process of unlocking bootloader, installing TWRP recovery and flashing ROM, and I am at version 11.0.350 ST ROW currently.
The ROM works fine, but now at every boot I am greeted by the "The boot loader is unlocked and software integrity cannot be guaranteed. <snip> Press power button to pause boot/continue" notice.
According to google, it's apparently a result of the bootloader unlocking process.
I tried to lock the bootloader again using "fastboot flashing lock", but then the phone stopped booting normally. It got stuck at the boot logo (which I believe means bricked?).
It wouldn't work until I unlocked bootloader and reflash the ROM.
So what I want to ask is, is it possible at this time to restore the bootloader to stock to avoid that "boot loader unlocked" notice and possibly become eligible for warranty again?

kagoromo said:
Hello, I recently went through the whole process of unlocking bootloader, installing TWRP recovery and flashing ROM, and I am at version 11.0.350 ST ROW currently.
The ROM works fine, but now at every boot I am greeted by the "The boot loader is unlocked and software integrity cannot be guaranteed. <snip> Press power button to pause boot/continue" notice.
According to google, it's apparently a result of the bootloader unlocking process.
I tried to lock the bootloader again using "fastboot flashing lock", but then the phone stopped booting normally. It got stuck at the boot logo (which I believe means bricked?).
It wouldn't work until I unlocked bootloader and reflash the ROM.
So what I want to ask is, is it possible at this time to restore the bootloader to stock to avoid that "boot loader unlocked" notice and possibly become eligible for warranty again?
Click to expand...
Click to collapse
Share screenshot, I think this normal boot step when BL is unlocked on lenovo / Zuk phones.

benjieb said:
Share screenshot, I think this normal boot step when BL is unlocked on lenovo / Zuk phones.
Click to expand...
Click to collapse
Here is the "The boot loader is unlocked..." screen:
{
"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"
}
And here's the boot loader:

kagoromo said:
Hello, I recently went through the whole process of unlocking bootloader, installing TWRP recovery and flashing ROM, and I am at version 11.0.350 ST ROW currently.
The ROM works fine, but now at every boot I am greeted by the "The boot loader is unlocked and software integrity cannot be guaranteed. <snip> Press power button to pause boot/continue" notice.
According to google, it's apparently a result of the bootloader unlocking process.
I tried to lock the bootloader again using "fastboot flashing lock", but then the phone stopped booting normally. It got stuck at the boot logo (which I believe means bricked?).
It wouldn't work until I unlocked bootloader and reflash the ROM.
So what I want to ask is, is it possible at this time to restore the bootloader to stock to avoid that "boot loader unlocked" notice and possibly become eligible for warranty again?
Click to expand...
Click to collapse
Do you try flash qfil rom after lock bootloader?

Mi A2 - Failed to boot - after system update

Hello everyone, yesterday morning, Sunday 12/15/19, the system message "restart the device to make the system update effective".
So I do as I have always been.
The phone, an Mi A2, goes into bootloop and then a white screen appears on a black background with the title:
"<!> Failed to boot"
"Press the Volume keys to select then the Power button to continue.
RETRY
POWER OFF "
Choosing "RETRY" verifies bootloop 3 or 4 times and then the recovery mode screen appears which says:
"Can't Load Android system. Your data may be corrupted. You should get the message you need to perform at factory data reset and erase all user data stored on this device."
It gives me the choice between:
-Try again
-Factory data reset
Choosing "Try again" returns the same routine as when "RETRY" is selected In the previous black background screen, bootloop and then the black background white screen described at the beginning.
I MUST ACCESS AND SAVE THE VERY IMPORTANT CONTENT. :crying:
I have all the photos and videos of my newborn daughter. I usually backup but this inconvenience suddenly caught me.
I surfed and I saw that many people found this problem after an update .. but I never found any solutions. I called the Xiaomi center in Novara indicated by the site but they told me that they only serve as a collection center to send to the assistance in the company Xiaomi, saying that the assistance resets the phone to restore its functioning and does not save the data. I tried to start the fastboot, the device is recognized by the PC and shows the locked bootloader. The program MiFlash asks me to start to install a set of drivers and then immediately generate an unhandled exception and crash.
Attached the images.
Can you help me? I do not know what to do..
{
"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"
}

You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".

Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.

Aerobatic said:
Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.
Click to expand...
Click to collapse
Thank you, can you explain me better what I should try to do?

HTCDevil said:
You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".
Click to expand...
Click to collapse
Is there any guide to do that?

pedrix82 said:
Is there any guide to do that?
Click to expand...
Click to collapse
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.

pedrix82 said:
Thank you, can you explain me better what I should try to do?
Click to expand...
Click to collapse
First you can try to search this forum and read dozens of discussions of the same issue. Meanwhile you can plug in power adapter and reboot several times with pauses, probably sometimes switching to stock recovery and to fastboot mode, and then leave phone powered for a night.

HTCDevil said:
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.
Click to expand...
Click to collapse
Thanks....I will try, I don't remember if I enabled the usb debugging mode, for sure I saw with fastboot that I have the bootloader Locked.

nothing to do...i tried ADB mode, but it is not enabled, only fastboot mode where i can do nothing because the bootloader is locked.
I also tried to install the Xiaomi tool, but it doesnt recognize the device.
i dont know what to do....

Did you try the factory data reset?

1N4148 said:
Did you try the factory data reset?
Click to expand...
Click to collapse
Hello...ehm...not, the aim is to recover all the data, photos and documents that are stored inside...

Same thing happened to me. You should manually switch the active partition in fastboot.

Zedsdeadbaby said:
Same thing happened to me. You should manually switch the active partition in fastboot.
Click to expand...
Click to collapse
Hi, I already tried to do what you suggest, but it is not possible with the bootloader Locked.
Anyway, can you tell me what I have to do to change the active partition? Maybe I don't do it as I should....

@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.

Aerobatic said:
@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.
Click to expand...
Click to collapse
Thanks,
It's really long time that I'm rebooting the mobile since it happened...
But cyclically and alternate I got the two image attached to the main post....

try a "fastboot continue" in adb

hello everyone, update.
unfortunately I was unable to recover anything and proceeded with the factory reset.
The phone has reset and everything is working.
So I thought to try to do a file recovery as you do for deleted files.
for the various recovery applications I need to root the device.
For this phone should be really simple but I'm still stuck in.
I followed one guide, then another, and then another .... all with the same procedures.
the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone.
but from this recovery, even if I install Magisk, with a successful results from the recovery, I do not root the device. I verified root with Magisk manager and rootchecker.
Help.... thanks

pedrix82 said:
... So I thought to try to do a file recovery as you do for deleted files.
Click to expand...
Click to collapse
I do no believe you'll be able to undelete files after factory reset.
pedrix82 said:
... for the various recovery applications I need to root the device. ... I followed one guide, then another, and then another .... all with the same procedures.
Click to expand...
Click to collapse
This guide works for everybody, except that
(1) there is obsolete "fastboot oem unlock" command stated which should better be changed to "fastboot flashing unlock", and
(2) guide does not mention that each unlock step is to be approved on phone, and
(3) guide skips step of patching stock boot.img in phone with MagiskManager, - while exactly this step creates archived copy of stock boot image in /data root, thus allowing to restore images (actually restoring stock boot image) before downloading next OTA, and
(4) only 1st variant - that is booting into patched boot image and then making "Direct Install" is safe - it allows to check that patched boot image is suitable for ROM.
pedrix82 said:
...the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone....
Click to expand...
Click to collapse
IMHO that just means that you did not do your homework (I mean you have not read guides and discussions and Google info with links I provided) well enough to understand that with A/B slots partitions structure there is no separate /recovery partition in phone (instead, recovery is embedded into /boot image), and thus we cannot just "flash TWRP" into MiA2.
Instead, TWRP can only be embedded into boot image (patching previously flashed suitable boot image), which is made by installing TWRP.zip in temporarily booted TWRP.img. Thus, if you want to have both root and permanent TWRP (I still do not see why anybody needs permanent TWRP with rooted stock), first get root with patched boot image, and then install TWRP patching this Magisk-patched boot image once more.
And I do think that "TWRP 4pda edition" is working better than so called "official TWRP".

Found the solution,
First u need to get to the recovery menu by pressing vol up + power, tap it multiple times after retry boot...you have to be quick...and eventually will get to the android robot pic with "no command"....keep pressing till you get to the full recovery menu. (this might take multiple tries)
Then go to update using adb. (you need all the files for adb, usb drivers, latest mi a2 update zip, you can find tutorials in youtube/google )
after updating it should boot up fine with all data intact.
If latest update versions dont boot, try repeating will older version.
Make sure you backup everthing afterwards! and enable oem unlocking &usb debugging for potential future issues.
Hope this helps!

Question Custom Binary Blocked by OEM Lock - Edit: it was the bootloader

Today the A33 5G 128GB arrived, to flash twrp on it i had to enable oem unlock and usb debugging first in develeoper options.
To do that i had to complete the setup first, it's sick that the phone did NOT even let me complete the setup without connecting to the internet... this is out of control.
Now, i have oem unlock enabled aswell as usb debugging.
{
"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"
}
Next i connect the phone to PC and booted in download / odin mode.
Then i tried to flash this a33x_experimental_twrp.tar created by Zillion with odin, however as you can see on the next screenshot... the phone says "Custom Binary Blocked by OEM Lock"...
Why does the Phone say Custom Binary Blocked by OEM Lock even when i have it enabled in developer options??!
The Phone-Model is SM-A336B/DSN if that matters? I contacted my service provider from who i bought this phone and they told me that they are selling only this model.
Any help is welcome ...

My last hope is that someone from this forum can help me get twrp and lineage running, otherwise i'll have no choice but to return the phone within 14 days. No way i will use this device with the sick psycho spyware it contains.
PS: My only idea that might be worth a shot is booting twrp from adb terminal on pc, but i'm not sure how that works, how do i flash twrp permanently and how do i flash lineageos from adb, while i might be able to flash lineageos i'm not sure if that would work with the stock recovery..?

You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.

V0latyle said:
You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.
Click to expand...
Click to collapse
Thanks for the info, i tried doing as you told boot in downloadmode and hold volume up untill unlockscreen appears, i'f been holding volume up for over 20 seconds but nothing happens.
Not that i doubt your instructions but are you sure this has to be done in downloadmode and not recovery?
Or do i have to press another button instead? Vol + doesn't seem to do anything.

You can also use Adb ( Adb reboot download)

Privacydroid said:
Thanks for the info, i tried doing as you told boot in downloadmode and hold volume up untill unlockscreen appears, i'f been holding volume up for over 20 seconds but nothing happens.
Not that i doubt your instructions but are you sure this has to be done in downloadmode and not recovery?
Or do i have to press another button instead? Vol + doesn't seem to do anything.
Click to expand...
Click to collapse
Yes, I am sure, bootloader unlock is never done through recovery.
Turn your device off completely with USB disconnected. Leave it off for a minute or so. Then, hold both Volume buttons (DO NOT press Power) and plug in the USB cable from your computer.
This should start the device in Download mode.
Now, hold Volume Up until the bootloader unlock screen appears, which should have an instruction to either press or hold Volume Up to unlock the bootloader.

V0latyle said:
Yes, I am sure, bootloader unlock is never done through recovery.
Turn your device off completely with USB disconnected. Leave it off for a minute or so. Then, hold both Volume buttons (DO NOT press Power) and plug in the USB cable from your computer.
This should start the device in Download mode.
Now, hold Volume Up until the bootloader unlock screen appears, which should have an instruction to either press or hold Volume Up to unlock the bootloader.
Click to expand...
Click to collapse
Thank you Sir. i totally forgot about the bootloader, and i didn't know how it works on the newer models (android 12), thanks to your easy insturctions i was able to unlock the bootloader.

V0latyle said:
You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.
Click to expand...
Click to collapse
I think the bootloader was sucessfully unlocked, just want to mention that after doing that (and the phone was erased) i do not see the oem unlock option under develeoper settings, all other options seem to be listed as normal.
So you are saying i must take care of vaultkeeper before finally flashing lineageos?
How would i handle that?

Privacydroid said:
I think the bootloader was sucessfully unlocked, just want to mention that after doing that (and the phone was erased) i do not see the oem unlock option under develeoper settings, all other options seem to be listed as normal.
So you are saying i must take care of vaultkeeper before finally flashing lineageos?
How would i handle that?
Click to expand...
Click to collapse
See Magisk installation instructions:
Unlocking the bootloader on modern Samsung devices have some caveats. The newly introduced VaultKeeper service will make the bootloader reject any unofficial partitions in some circumstances.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Click to expand...
Click to collapse
If OEM Unlocking is not visible, Vaultkeeper has not unleashed the bootloader yet and you must fix this before proceeding. Look for "KG STATUS" on the screen when your device is in download mode; if this says "PRENORMAL" you cannot flash a custom image. If it says "CHECKING" you should be fine to flash TWRP, and once you flash TWRP, you can install LineageOS.

V0latyle said:
See Magisk installation instructions:
If OEM Unlocking is not visible, Vaultkeeper has not unleashed the bootloader yet and you must fix this before proceeding. Look for "KG STATUS" on the screen when your device is in download mode; if this says "PRENORMAL" you cannot flash a custom image. If it says "CHECKING" you should be fine to flash TWRP, and once you flash TWRP, you can install LineageOS.
Click to expand...
Click to collapse
Well, i tried flashing twrp right now without using magsik, might have been a bad idea.. there's some error now.
Not really a surprise.. i never managed to brick a phone by all the idiotic things i'f done, no clue how to perceed now as the phone keep rebooting to the exact same screen with the exact same error message.
Did i damage the recovery?

You seem softbricked. You can always flash stock recovery. What happens when you try to boot to system? Is it just stuck in Odin mode?

Arealhooman said:
You seem softbricked. You can always flash stock recovery. What happens when you try to boot to system? Is it just stuck in Odin mode?
Click to expand...
Click to collapse
How do i boot to system? Just hold power button? Yes it keeps booting to odin mode, it does not even allow me to shutdown, keep booting to Odin.
Remember when you could simply unplug the battery...
Can i use Frija to download stock recovery or is it only for the "system os"?

Privacydroid said:
How do i boot to system? Just hold power button? Yes it keeps booting to odin mode, it does not even allow me to shutdown, keep booting to Odin.
Remember when you could simply unplug the battery...
Can i use Frija to download stock recovery or is it only for the "system os"?
View attachment 5790277
Click to expand...
Click to collapse
Yes.
Guide to Extract Stock Recovery:​
First, download the preferred Samsung stock firmware for your device model.
Extract the firmware zip file on your computer within a folder.
Open the .tar.md5 file using 7Zip. (Download 7Zip)
You will find the ‘recovery.img’ file. This is the stock recovery file for your Samsung device. Select it and hit Extract.
Compress the recovery image file via 7Zip tool in “.tar” format.
Put your Samsung device in Odin Download mode, select ‘AP’ or ‘PDA’ in Odin tool and select the new recovery.tar file, then hit the Start button.
(credit to Getdroidtips)

Btw its in the AP file

Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of

V0latyle said:
Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of
Click to expand...
Click to collapse
After re-flashing the stock firmware i checked the KG-STATUS and it says "broken"
Indeed the twrp i tried to flash is experimental and made by @Zillion
Might sound like a stupid question, people like andy yan appear to provide GSI's (generic system images) just curious if the same would be possible with twrp? A generic twrp image that is compatible with any/most devices? Basically, if mr Zillions twrp does not function yet, what other twrp could i try?

Arealhooman said:
Yes.
Guide to Extract Stock Recovery:​
First, download the preferred Samsung stock firmware for your device model.
Extract the firmware zip file on your computer within a folder.
Open the .tar.md5 file using 7Zip. (Download 7Zip)
You will find the ‘recovery.img’ file. This is the stock recovery file for your Samsung device. Select it and hit Extract.
Compress the recovery image file via 7Zip tool in “.tar” format.
Put your Samsung device in Odin Download mode, select ‘AP’ or ‘PDA’ in Odin tool and select the new recovery.tar file, then hit the Start button.
(credit to Getdroidtips)
Click to expand...
Click to collapse
Thanks, i managed to re-flash the stock firmware!
I actually didn't want to whole system (the os) the be re-flashed but only the recovery, however when i extract the AP file i do not get any recovery.img file.
`
Edit: i see recovery.img.lz4 (can i use that aswell to re-flash stock recovery, i never saw .lz4 whatever that is.

I tried flashing twrp with odin by placing it in the AP slot, so since that didn't work would it be worth a shot trying to flash it with adb via pc instead? Or is magisk a hard requirement now to bypass Vaultkeeper to be able and flash twrp?

V0latyle said:
Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of
Click to expand...
Click to collapse
actually theres a way of repacking using lz4 images, but i dont really know how to do it

Privacydroid said:
After re-flashing the stock firmware i checked the KG-STATUS and it says "broken"
View attachment 5790319
Indeed the twrp i tried to flash is experimentla and made by @Zillion
Might sound like a stupid question, people like andy yan appear to provide GSI's (generic system images) just curious if the same would be possible with twrp? A generic twrp image that is compatible with any/most devices? Basically, if mr Zillions twrp does not function yet, what other twrp could i try?
Click to expand...
Click to collapse
Wich device is that
*A33 TWRP was never meant for final users
The latest build was just a testing one