Database Develop

[Q&A] Collection

Disclaimer: I try my best to produce valid answers, but if you have no idea what you're doing, don't do it.
Terms and Definitions
NVflash / APX mode
This is the lowest level of software that can talk to an Nvidia Tegra device. Basically this is the Holy Grail of memory modification, which can even fix a damaged bootloader.
To use it, one boots the tablet with [Vol +] + [Power]. This will lead to the PC detecting an "APX" device. The screen stays blank.
This is no working solution for anything yet, as not only there is no leaked NVflash binary yet, but also the communication is encrypted via an unique 128bit AES key. This key is at no stage accessible, but can be used to encrypt data during boot. This is where the wheelie tool for previous transformers was of help. The Communication itself happens via a protocol called nv3p, which actually is open source, but as long as the key is unreachable, that's not a lot of use. NOTE: I will create an extra post with a lot more details about this.
Fastboot
The Android Bootloader.
This is the essential part of software which loads Android/a Recovery image/rooting ramfs/etc.
This is the most delicate part in the Android boot process, as fastboot is the lowest level of communication we have so far. In other words: The only way to fix a damaged bootloader would be NVflash, which is not yet available for this device.
Generally the Bootloader is locked as a method to prevent unauthorized access to data stored on the device. A locked Bootloader means no Fastboot.
Bootloader unlocking
To gain access to fastboot devices, the Bootloader needs to be unlocked. This can be as simple as installing an APK provided by the manufacturer or running "fastboot unlock".
Unlocking the Bootloader always leads to three resulting actions: Fastboot now works, all data on the device is wiped, the device's warranty is now void.
Unlocking the bootloader via unlock app can require you to have internet access and a valid google account. This can be problematic in the case of one-time-passwords, as the normal password will possibly not work (and you'll wonder why the heck it doesn't run).
Bootloader locking
This is (at least currently) not possible. Warranty void remains permanent.
RamFS
Simple file system in a file, which gets loaded into RAM. We use this for rooting.
Boot image
A file generally called "boot.img". This contains the kernel.
Recovery image
A partition image that contains a bootable linux kernel and file system, which server the purpose of creating and restoring nandroid backups and perform related tasks.
Brick - general
A device with messed up software, not being able to boot let alone perform any higher task other than being a brick.
Soft brick
A device not booting, which still responds to fastboot queries.
Hard brick / Brick
Fastboot doesn't work anymore. Maybe a visible boot loop, maybe nothing. The only point in which this differs from scrap is the ability to get into APX mode.
Chances are, there will be a way to use NVflash to fix this sometime.
Unbrick
Fixing a bricked device. Currently only soft bricked devices can be unbricked.
Root
General term for having super user abilities on a linux powered device. This can be used for reading/writing/executing restricted files, modifying things, loading custom ROMs etc.
Also having Root can mean "running with scissors", as there's not much left to prevent you from deleting important files and bricking your device.
Remember: Having Root is a very useful device, but with power comes responsibility. Also there is Android malware, which specifically targets rooted devices.
Rooting
The process of gaining Root. In early methods this generally starts with unlocking the device's Bootloader, then booting a Kernel with a purposely prepared ramfs to install and modify certain files.
As always, unlocking the Bootloader means all data will be wiped. By chance at some point someone will figure out a way to do this without unlocking.
ROM
A stock or custom Android ROM image. This contains everything needed for a running system. Custom ROMs contain tweaks, themes, improvements, styles, preloaded apps etc. Also more often than not, a load of bloat ware will be removed.
Bloat ware
Apps nobody needs/many fail to understand what they actually do/bring new ways to crash your device/sniff your precious data/revive long fixed and forgotten security leaks/the manufacturer adds to promote sales ("hey look, we've got an app for that pre installed").
Most importantly, cannot be removed from your device without Root.
Stock
A mint Android ROM, just like what the device gets shipped with.
Guides
Rooting
Requirements: Currently none
Compatible versions: anything > 10.14.1.47
Method: Booting custom Kernel and ramfs
Status: Proven
Link: http://forum.xda-developers.com/showthread.php?t=2516215
Recovery
Creator: Drgravy
Version: 6.0.3.7
Status: Abandoned but functional
Requirements: Bootloader <= 10.14.1.47 (this will not work with 10.26.1.7. Trying to do so will not work, but still boot Android as usual.)
Link: http://forum.xda-developers.com/showthread.php?t=2524401
Recovery
Creator: lpdunwell
Version: 6.0.4.5
Status: Experimental, WIP
Requirements: Bootloader >= 10.26.1.7
Link: http://forum.xda-developers.com/showthread.php?t=2556944
Various information
Hardware assembly date
On the box, rear side label.
Partition information / Unbricking
Link: http://forum.xda-developers.com/showthread.php?t=2546941
Keyboard key remapping
The physical keyboard has custom keys, with functions of debatable value. Here's how to remap them to suit your needs.
Note: This also works for other ASUS Transformers.
Warning: Backup any file you attempt to edit!
Method: The keyboard mapping is described in /system/usr/keylayout/asuspec.kl. The structure is pretty straight forward.
After saving the file, reboot the device.
Code:
Key: Function: Key number: Text:
lock Delete 142 "key 142 FORWARD_DEL WAKE UNLOCK"
search ALT 217 "key 217 ALT_LEFT WAKE UNLOCK"
HDMI configuration
The HDMI resolution can be adjusted. This can be handy under certain circumstances, although results may vary.
Method: Via terminal; disable frame buffer 1, change resolution, enable frame buffer 1
Info: To get a list of valid settings, run "cat /sys/class/graphics/fb0/modes".
This will reset at reboot.
This example enforces 1920x1200 @ 59Hz, in my case to force a HP Compaq monitor to keep running (without this it'll go to sleep for whatever reason).
Code:
echo 0 > /sys/class/graphics/fb1/device/enable
echo "D:1920x1200p-59" > /sys/class/graphics/fb1/mode
echo 1 > /sys/class/graphics/fb1/device/enable
Teardown
Teardown with two images and a brief description of the process: http://forum.xda-developers.com/showthread.php?t=2564143
Q&A
Q: "I have never rooted anything before. Can you send me some fairy dust to fix my bricked tablet if anything goes wrong?"
A: No. And if you are not absolutely sure of what you're doing, there's a fair chance you'll mess it up. Been there, done that.
Q: "What are known causes of bricked TF701?"
A:
Failed upgrade
Flashing incompatible boot.img and blob
Flashing something other than blob to staging
Removal of important files after rooting
Q: "I had a quick look at your instructions for xxx and I don't understand..."
A: Tough luck.
Q: "I re-read your instructions for xxx, searched the forum and I still cannot understand..."
A: Check if there's a matching thread. If there isn't create one with a diagnostically conclusive title. Use as much detail as possible.
Final notes
I hope this helps. As always, updates will follow.
Want to see your tutorial/guide/etc. here? Send me a detailed PM with the subject "TF701 Q&A extension".
You can help making this even better!
Found a mistake or believe I'm wrong about something? Let's discuss it.
Has this helped you? Consider clicking thanks.

THANK YOU for the hack to get a forward delete on the keyboard! That has been bugging me for a year!
Works just the same on the TF700 keyboard, btw.

Ask the mod to make it sticky, then it will always be at the top of the main thread.
Sent from my superfast Asus Infinity TF701with Dock

Snah001 said:
Ask the mod to make it sticky, then it will always be at the top of the main thread.
Sent from my superfast Asus Infinity TF701with Dock
Click to expand...
Click to collapse
he is retired .... Doesnt reply to any request ...

berndblb said:
THANK YOU for the hack to get a forward delete on the keyboard! That has been bugging me for a year!
Works just the same on the TF700 keyboard, btw.
Click to expand...
Click to collapse
yeah, the keymapping crap...
I found tons of "unpack this apk, edit soandso..." but I wanted to have it changed on a lower level. the remapping should work on most if not all transformers, and be easily portable to anything that has a hardware keyboard...

Rikodu said:
he is retired .... Doesnt reply to any request ...
Click to expand...
Click to collapse
Huh? Wut?????
Considering this is the first "Q & A" post, I will sticky it.
Provided the OP updates and maintains it.
MD

I'm pretty sure the resolution hack can be improved, but it's all I needed for now...
anybody write an app for that?

Moscow Desire said:
Huh? Wut?????
Considering this is the first "Q & A" post, I will sticky it.
Provided the OP updates and maintains it.
MD
Click to expand...
Click to collapse
go for it, it's sinking...
cheers

lpdunwell said:
go for it, it's sinking...
cheers
Click to expand...
Click to collapse
Seeing if you were paying attention..... :good:

lol

Maybe you could explain where to see the build date.
As far as I know its in the serial number after the characters. But in my case (and maybe others) I can´t see a date in 160074 .

done

hard bricked tf701t
Dear lpdunwell,
I have a bricked tf701, only asus logo available and loopboot, fastboot menu is broken as well. Only APX mode working, but I could not find appropriate nvflash for my pad (s I see there is no nvflash currently available for my tab)
In your explanation about bricked device, you wrote that there is possibility to recover tf701?
Please describe what nvflash version should I use to succeed?
Thanks in advance,
stream1313

stream1313 said:
Dear lpdunwell,
I have a bricked tf701, only asus logo available and loopboot, fastboot menu is broken as well. Only APX mode working, but I could not find appropriate nvflash for my pad (s I see there is no nvflash currently available for my tab)
In your explanation about bricked device, you wrote that there is possibility to recover tf701?
Please describe what nvflash version should I use to succeed?
Thanks in advance,
stream1313
Click to expand...
Click to collapse
Sorry mate we don't have nvflash and it is too late for you now anyway If you only have access to APX you are hard bricked. Best to sell it for parts and move on.... Or if you want to revive it send it to Asus to fix at a cost or source a replacement mainboard and do it yourself.

sbdags said:
Sorry mate we don't have nvflash and it is too late for you now anyway If you only have access to APX you are hard bricked. Best to sell it for parts and move on.... Or if you want to revive it send it to Asus to fix at a cost or source a replacement mainboard and do it yourself.
Click to expand...
Click to collapse
Hi man.. Why do you think I have to forget about my toy.. It was my Christmas (New Year in Tbilisi, Georgia, opposite planet side) present to myself But it is all the lyric only
Pls explain - do you really think that for ex., several weeks / months later, smb will create the nvflash or any similar SW which will be able to fix my problem? Actually I believe that until all electronic components are ok, device is not "dead" forever... Why you so pessimistic exactly for 701 transformer tab? Pls if you have time reply me
Kind regards,
Stan

stream1313 said:
Hi man.. Why do you think I have to forget about my toy.. It was my Christmas (New Year in Tbilisi, Georgia, opposite planet side) present to myself But it is all the lyric only
Pls explain - do you really think that for ex., several weeks / months later, smb will create the nvflash or any similar SW which will be able to fix my problem? Actually I believe that until all electronic components are ok, device is not "dead" forever... Why you so pessimistic exactly for 701 transformer tab? Pls if you have time reply me
Kind regards,
Stan
Click to expand...
Click to collapse
the way nv flash works is you need to flash the special bootloader to extract your device blobs and device specific keys. As you haven't been able to do it and you CANNOT do it once you have bricked you will have no chance. How are you going to flash a bootloader that you need fastboot for?
Sorry to bring bad news but if you only have APX with no saved nv flash files (which is not yet avail for our device) then you currently have 0% chance of recovering.

sbdags said:
the way nv flash works is you need to flash the special bootloader to extract your device blobs and device specific keys. As you haven't been able to do it and you CANNOT do it once you have bricked you will have no chance. How are you going to flash a bootloader that you need fastboot for?
Sorry to bring bad news but if you only have APX with no saved nv flash files (which is not yet avail for or device) then you currently have 0% chance of recovering.
Click to expand...
Click to collapse
Thanks a lot for reply (as well as for my another, initial thread reply) I have only CWM backup of my tab, on the MD card. But I do not know, does this backup contain all needed stuff? At list, I did not found there saved nv flash or blob files. Just "blobgenerator" (462Kb) and "blobtester" (370Kb), also some system files with "nv" in the name. But I do not have Idea, does CWM saving the low level loader files, at list I was not able to recognize them there...
my apologize for too many questions as well as for my poor English - it is not my native lang
Kind regards,
Stan

stream1313 said:
Thanks a lot for reply (as well as for my another, initial thread reply) I have only CWM backup of my tab, on the MD card. But I do not know, does this backup contain all needed stuff? At list, I did not found there saved nv flash or blob files. Just "blobgenerator" (462Kb) and "blobtester" (370Kb), also some system files with "nv" in the name. But I do not have Idea, does CWM saving the low level loader files, at list I was not able to recognize them there...
my apologize for too many questions as well as for my poor English - it is not my native lang
Kind regards,
Stan
Click to expand...
Click to collapse
No having CWM backups saved won't help you as you have no way of getting to the bootloader which would then be used to open the recovery so you could restore. WIthout a working bootloader you can't proceed. NV Flash uses APX mode to restore the blobs via the wheelie binary. You haven't captured the blobs to restore and as they are encrypted to your device you can't use anyone elses.
It's a new main board or nothing I'm afraid.

sbdags said:
No having CWM backups saved won't help you as you have no way of getting to the bootloader which would then be used to open the recovery so you could restore. WIthout a working bootloader you can't proceed. NV Flash uses APX mode to restore the blobs via the wheelie binary. You haven't captured the blobs to restore and as they are encrypted to your device you can't use anyone elses.
It's a new main board or nothing I'm afraid.
Click to expand...
Click to collapse
I see, everything is clear. Thanks for your time man. But I beleive that Asus has some kind of "backdoor" for such cases, for internal usage, of course. Asus manifest about "mainboard replacement" probably just for business, normally must be some way to crack this protection. I hope somebody from Asus will share some useful info or even software for public usage... Maybe it's my dreams only, I'm realistic (I'm working as IT/IS/GSM/WCDMA, but I'm so far from programming..)
Again, thank you. Pls notify me in case of any news about K00C hack

Problems flashing CWM recovery
stream1313 said:
I see, everything is clear. Thanks for your time man. But I beleive that Asus has some kind of "backdoor" for such cases, for internal usage, of course. Asus manifest about "mainboard replacement" probably just for business, normally must be some way to crack this protection. I hope somebody from Asus will share some useful info or even software for public usage... Maybe it's my dreams only, I'm realistic (I'm working as IT/IS/GSM/WCDMA, but I'm so far from programming..)
Again, thank you. Pls notify me in case of any news about K00C hack
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------
Sorry I am not yet familiar with how to ask questions.
I recently bought a TF701T having used a TF700T now for two years and before that the TF101, TF201 and TF300T.
All these tabs I installed a recovery: CWM or TWRP and flashed the best ROM I could find. Usually Cyanomod or CROMi-X.
Everything worked fine so I was very excited when I got hold of the TF701T with its incredible Q-ratings and smoothness.
Unlocking worked just fine but installing CWM just does not work: flashing with Fastboot works OK but when I boot into recovery the little green man falls down and stays there
FYI: I am on the latest BL: 10.26.1.28, so newer than the mentioned 10.26.1.18 !
Please could anyone respond ?
Regards, JOTX10 from the Netherlands.

Need help

Hey guys n girls,
I'm going to root my phone. First off the why? I recently discovered PlayStation remote play and use it on my computer. I was excited to use it on my phone but then found out only Sony phones work I guess... So I read somewhere don't remember, that if I root my phone, I can add Sony files to rooted phone to allow it to use PlayStation remote.
1st phone is moto x 2nd
2nd phone zte maven 2
First phone I use for an actually phone 2nd one is brand new never used.
So I heard I need to use adb and something else I believe. Can someone help me? Once again main reason PlayStation remote play

mike543210 said:
Hey guys n girls,
I'm going to root my phone. First off the why? I recently discovered PlayStation remote play and use it on my computer. I was excited to use it on my phone but then found out only Sony phones work I guess... So I read somewhere don't remember, that if I root my phone, I can add Sony files to rooted phone to allow it to use PlayStation remote.
1st phone is moto x 2nd
2nd phone zte maven 2
First phone I use for an actually phone 2nd one is brand new never used.
So I heard I need to use adb and something else I believe. Can someone help me? Once again main reason PlayStation remote play
Click to expand...
Click to collapse
First you must unlock bootloader from official motorola site.
Google unlock moto x 2014 and do it.
Second you must download adb and fastboot to your pc.
Third with adb flash twrp.
And last flash supersu with tuttorial from xda .
Keep walking.

Thanks. Any chance you can attach links for downloads for PC and also files. If u can add tutorials I can follow those too. I have rooted couple times before but if I do the moto that's my actual phone and I don't want to mess it up. Will it mess with my plan or screw me over in any way? I've only done phones I don't use.
Thanks again for any help

So Ive been reading and need a little help.
1. I have moto x2014 (is it pure edition?)supposedly. (It's at&t white front wooden back 8gb. Believe 5.1.1) I need to know so I can do the first step.
2.downloads to adb and fastboot for PC? I was hoping someone had a link so I know I don't download anything bad.
*Edit* I used this
https://forum.xda-developers.com/showthread.php?p=48915118
3. How to flash? And need the zip packs/files for twrp and SuperSU? (Which I put on root of SD card?)
*Edit*
Also by doing this will my phone operate the same?(no extra step to put kernal/os on?) I just want to know how to root and add Sony software to use the app. Thanks again for anyone's knowledge
*Edit*
I'm having a tough time navigating the forum, thank for the help people

mike543210 said:
So Ive been reading and need a little help.
1. I have moto x2014 (is it pure edition?)supposedly. (It's at&t white front wooden back 8gb. Believe 5.1.1) I need to know so I can do the first step.
2.downloads to adb and fastboot for PC? I was hoping someone had a link so I know I don't download anything bad.
*Edit* I used this
https://forum.xda-developers.com/showthread.php?p=48915118
3. How to flash? And need the zip packs/files for twrp and SuperSU? (Which I put on root of SD card?)
*Edit*
Also by doing this will my phone operate the same?(no extra step to put kernal/os on?) I just want to know how to root and add Sony software to use the app. Thanks again for anyone's knowledge
*Edit*
I'm having a tough time navigating the forum, thank for the help people
Click to expand...
Click to collapse
Here is my help....
Twrp
https://dl.twrp.me/victara/twrp-3.1.1-0-victara.img.html
Moto drivers
https://mobilesupport.lenovo.com/us/en/solution/MS88481
Unloack bootloader
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Minimal fastboot an adb
https://androidfilehost.com/?fid=745425885120698566
Here toutorial for the root.
https://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105

Thank you I will read and try. And as far as if I root the zte maven 2 I would just get the drivers for zte and switch the product name in command lines correct?

First off thanks for your help and anybody else who may contribute.
ive been trying to listen and follow lol. anything with (...) is stuff
i added
First you must unlock bootloader from official motorola site.
Google unlock moto x 2014 and do it.
(the link you added brought my to a page i click next and tryed to sign up
it said i had an account so i signed in with the email on my phone an then it
brought me to a page that wasnt available. So do you have another link or is
there something im missing. im having trouble unlocking it)
Second you must download adb and fastboot to your pc.
(i downloaded
*minimal_adb_fastboot_v1.4.2_setup application
*motoroladevicemanager_2.5.4 application)
Third with adb flash twrp.
(few things.
*adb is just command prompt right?
*flash? i know means install sorta of. do you have command line?
*the link had three things to click on
1.this was on white screen
58337e4962e12d37f740a417601db4e3 twrp-3.1.1-0-victara.img
2. twrp-3.1.1-0-victara disc /image file
3. twrp-3.1.1-0-victara.img.asc /asc file)
And last flash supersu with tuttorial from xda .
(once again, flash? im assuming i just need command line like,
adb install supersu.apk.
*also files i downloaded were
1. update-supersu-v2.76-20160630161323 /compressed zip
2. root-boot-6.0-xt1097-mpes24.49-18-7 /compressed zip)
***So is there any files im missing to root?
How do i unlock my bootloader or whatever it is? (link didnt work for me)
What is flash?(i think install)

it says my device does not qualify to unlock bootloader. so yea I don't want to give up but that killed my hopes. I can get into fasboot flash mode and have boot mode selection menu and it says device is still locked. I got the link to work and used fastboot oem get_unlock_data used their program to have same layout for unlock code and it says your device does not qualify for bootloader unlocking. if anyone can help thanks

mike543210 said:
it says my device does not qualify to unlock bootloader. so yea I don't want to give up but that killed my hopes. I can get into fasboot flash mode and have boot mode selection menu and it says device is still locked. I got the link to work and used fastboot oem get_unlock_data used their program to have same layout for unlock code and it says your device does not qualify for bootloader unlocking. if anyone can help thanks
Click to expand...
Click to collapse
Some variants of the Moto X 2014 cannot be unlocked. Put the phone in Bootloader Mode and:
fastboot getvar all
Copy and save all the info into a Notepad file, then go to the Moto/Lenovo Forums here:
https://forums.lenovo.com/t5/MOTORO...ock-Problems/m-p/3222809/highlight/true#M2654

mike543210 said:
it says my device does not qualify to unlock bootloader. so yea I don't want to give up but that killed my hopes. I can get into fasboot flash mode and have boot mode selection menu and it says device is still locked. I got the link to work and used fastboot oem get_unlock_data used their program to have same layout for unlock code and it says your device does not qualify for bootloader unlocking. if anyone can help thanks
Click to expand...
Click to collapse
What model do you have my friend?
Fot the tutorial ...
First unlock bootloader and install twrp.
All other you can flash them from the twrp recovery and i mean supersu and many more.
From adb can flash stock rom clean.

hey gus I did that command and made a save file in notepad. so just post it?
and pap I believe xt1097

according to ur link gus my phone is not unlockable becaue my cid was 0x001. so yea I guess im giving up thanks guys for your time. im really bummed because I modded and rooted things in the pass and this by far has been the hardest. I figured I could do it manually or a custom firmware would help. if I install twrp somehow as a recovery is there a way to root of that? I just don't get y I cant unlock bootloader. I understand that I cant, but don't get how there isn't a way around it. once again thanks people. this is a bummer...........................

is there any way to get unique_key for the command line?
fastboot oem unlock UNIQUE_KEY

im so annoyed right now that i cant unlock this phone. its ridiculous that i cant unlock it, like seriously please help from anyone. i dont know y i cand get the unique key to unlock my phone. can i call motorola to ask for it? or at&t? i just dont get y i cant unlock it with any method. i know there is someone out there who can help, please spare me some time and help me i beg of u.

u think this will work?
https://forum.xda-developers.com/moto-x-2014/general/root-bootloader-unlock-att-xt1097-5-1-t3309889
or is there a way to make my bootloader unsigned?
if i unlock my phone from at&t would that help?

Unlock carrier locked bootloader Pixel [BETA]

UPDATE AS OF 16 OF MAY 2023
This project isn't working right now, but I am still working on it.
However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get to functional state.
If anyone has any idea please contact me, any hell is welcome!
______________________________________________________
Hi!
So I decided I wanted to flash custom software into my phone, but it's bootloader was locked so I figure a way to unlock it!
I am going to leave 2 methods:
1. It's the most risky but has more chance of working. The idea is to flash the whole firmware again to the phone, but from an unlocked model.
This is posible using the EDL mode and Sahara protocol.
The EDL mode is an emergency mode which allows user to flash firmware in case fastboot and ADB fails. It's also available in all Qualcomm devices.
It is also completly independent from the rest of the phone, and it's the first bootloader we have. If everything is ok it triggers the second bootloader(fastboot) which then boots the system(See the diagram if you want).
As we want to reflash the firmware keep in mind this could brick your phone and I won't take any resposability if it happen
Materials:
-QPST
-Qualcomm Driver
-Working USB Cable
-Fastboot and ADB set up and working
-knoledge on using ADB
Procedure:
1. Download and install Qualcomm drivers
2. Download and install QPST
4.Downlaod the MBN file
3. Reboot
4. Connect the phone to the PC, then open cmd and run "adb reboot edl".
If you are on fastboot mode, then try "fastboot oem edl", "fastboot reboot-edl", "fastboot reboot edl". One of this should work
5. Go to C:\Program Files\Qualcomm\QPST\bin\
6.Open QPST Config(it's a blue phone, see picture)
7. Click on "Start clients" and then "Software download". A new window should open
8. Now we need to select the phone image using the browser button
9. Click on start to flash ⚡️
Please be aware the method wasn't tested, so this could brick your phone.
If you decide to try it, and have questions or ru into problems during the process, please let me know.
Also remember to take a backup of your data, as it is goig to be lost. ℹ
____________________________________________________________________________
As for the second method, I tried it and it didn't work for me, but is completly safe so you may want to give it a try.
1. Enrrol on the android 12 beta program, AND MAKE A BACKUP OF YOUR DATA
2. Install the update
3. Now exit from the beta program
4. Now you should have an update, it's a rollback to the stable version of android 12. After you installed the update the phone will restart and factory reset.
5. Do the setup as normal
In the end you may have unlocked the bootloader, to check just go to developer options and check if it is enabled or not.

Can we get a video of how to do this?

trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
So you attempted one of these methods and did it work or not work.What device did you use?

trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
That seems to be a probelm with the drivers. Did you install everything properly?
You may want to uninstall them and reinstall again to see if we solve the problem. Also try to run the app with admin privileges
Let me know how if you have more issues or if this doesn;t solve the problem at all.

AtrixHDMan said:
Can we get a video of how to do this?
Click to expand...
Click to collapse
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.

#mcl said:
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
Click to expand...
Click to collapse
I understand thanks

#mcl said:
这似乎是驱动程序的问题。您是否正确安装了所有内容？
您可能需要卸载它们并重新安装，看看我们是否能解决问题。还尝试以管理员权限运行该应用程序
如果您有更多问题，或者这根本无法解决问题，请告诉我
MOD EDIT: You may need to uninstall them and reinstall to see if we can fix the problem. Also tried running the app with admin rights
Let me know if you have more questions, or if this doesn't solve the problem at all.
Click to expand...
Click to collapse
同样的问题，无法解决。
MOD Edit: Same problem, can't solve it.

Looks like this is a common issue, I will look the documentation of QPST and see if I see the cause of the problem. Thank you guys for helping up this project

So I found that that version of QPST is outdated(it's the 2.7 build 140 and the latest version is 2.7 build 460). I am leaving a zip with it here.
Try and see if this time around we manage to unlock the bootloader

MOD EDIT:
This is the latest version
这是最新版本

#mcl, I have the same problem as you have, I live in Portugal and bought a used Pixel 4 but apparently it's origin is the US, Verizon. From your original post I take it that you didn't try this method yourself and hope others will try? Or were you successful?

for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"

gentle_giant said:
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
Click to expand...
Click to collapse
Hey I am quite busy recently so I haven't really had time to look more on the thread, though I believe there will always be a way, it may be hard to find but no OS is perfect, and Android is no exception. As it turns out, even if this method worked, when it connect to the internet there will be a high chance that using the IMEI of the phone it will "remember" it's a locked model and won't allow you to flash new firmware.
However I am working on a new method, which is also safer, though I have still work to do, so when It is ready I am going to publish another guide.
Good luck all untill them

Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.

gentle_giant said:
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
Click to expand...
Click to collapse
Hahah yeah we are definitely neighbors.
Well I do want to become a software engineer though right now I am just a busy enthusiastic.
I also really enjoy custom OS, when I had my Galaxy S9 I used to have custom ROMs.
Hope I manage to find a new solution as soon as posible for all if you guys!!!

How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com

any luck with that? can I backup my firmware before doing it?

darknmy said:
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
Click to expand...
Click to collapse
We are not doing physical atack, so that is not a problem for us.
Also, I don't believe the pixel 4 XL is perfect, for sure there are errors and security vulnerabilities. We just need to find them.

Development Prototype ABL Binary from Nokia XR20 for Bootloader Unlock.

Few months ago a customer asked me to flash couples of Nokia XR20 prototype unit for him, so I managed to get prototype ABL dump of this phone.
WARNING: This is not a guide! DO NOT TRY IT ON OTHER SNAPDRAGON 480 BASED NOKIA PHONES INCLUDING G50, X10, X20, X100, G300 - UNLESS YOU KNOW WHAT YOU'RE DOING!
To use it:
1. Enable flashing permission with HDK (an internal flash tool used by triple-color company, sorry can't disclose more details about that). Please search for related service online, we don't provide or promote such service.
2. Download Prototype ABL from following URL:
Click here
3. Flash prototype ABL and OEM unlock enabled frp partition manually, then you can confirm bootloader unlock:
Code:
fastboot flash abl TTG-abl.elf
fastboot reboot-bootloader
fastboot flashing unlock
fastboot flashing unlock_critical
4. Once bootloader unlock completed, please reinstall stock OS to restore ABL back to normal.
SHA256 checksum of ABL image: ac8143f6e0b449c39127aedd6463e2b9242cf37ce90a86c2988b885e34b0587f
Root Key Hash of ABL image: 622D3D5FE38C4198DDFABB264034EFDE58B986B510393A0CF163E803A3FD985E
Proof of concept is attached below, thanks to @singhnsk for testing.

Bro, Nokia x10 please?

HDK.
Where can I get?
Full name please of this app.

mishak750 said:
HDK.
Where can I get?
Full name please of this app.
Click to expand...
Click to collapse
nope, you can't use it, even if you get the full name

hikari_calyx said:
Few months ago a customer asked me to flash couples of Nokia XR20 prototype unit for him, so I managed to get prototype ABL dump of this phone.
WARNING: This is not a guide! DO NOT TRY IT ON OTHER SNAPDRAGON 480 BASED NOKIA PHONES INCLUDING G50, X10, X20, X100, G300 - UNLESS YOU KNOW WHAT YOU'RE DOING!
To use it:
1. Enable flashing permission with HDK (an internal flash tool used by triple-color company, sorry can't disclose more details about that). Please search for related service online, we don't provide or promote such service.
2. Download Prototype ABL from following URL:
Click here
3. Flash prototype ABL and OEM unlock enabled frp partition manually, then you can confirm bootloader unlock:
Code:
fastboot flash abl TTG-abl.elf
fastboot flash frp frp_oemunlock.img
fastboot reboot-bootloader
fastboot oem unlock-go
4. Once bootloader unlock completed, please reinstall stock OS to restore ABL back to normal.
SHA256 checksum of ABL image: ac8143f6e0b449c39127aedd6463e2b9242cf37ce90a86c2988b885e34b0587f
Proof of concept is attached below, thanks to @singhnsk for testing.
Click to expand...
Click to collapse
man, I'm jealous of XR20 users!
here's hoping that someone will find a X10 prototype soon!

AltFantasy said:
man, I'm jealous of XR20 users!
here's hoping that someone will find a X10 prototype soon!
Click to expand...
Click to collapse
THAT CAME TRUE, **** YEAH!!!

Posted new topic in X10/ X20 phone section, before reading everything up here...
Seems "up the sh*t creek without a paddle" situation.
Damn Nokia, but if anyone would get it working- I'll subscribe to this topic too.
Cheers!

Visionu said:
Bro, Nokia x10 please?
Click to expand...
Click to collapse
Prototype ABL binaries from Nokia X10 and X100, for bootloader unlock purpose.
If you've followed my prototype ABL image release topics so far, then you should know where it comes from. This topic will be edited later if X20 one is available. WARNING: This is not a guide! Prototype ABL binaries are provided as-is...
forum.xda-developers.com
Here you go

Trying not to be offtopic, why a decent phone, from a well known brand like Nokia, that often offered android one devices has now low to zero interest from developers? It's not polemic, I am just curious

phaleg said:
Trying not to be offtopic, why a decent phone, from a well known brand like Nokia, that often offered android one devices has now low to zero interest from developers? It's not polemic, I am just curious
Click to expand...
Click to collapse
Politics+proffits= end user loss
as it comes to coders, it's only so far we get allowed to delve in to, there was time, when I have physically remodded ZTE phone, from non funcioning device in to best phone at the time ALL- during one day on PC using no more that 3 tools and 2 ROM's... now you are constrained to even to get an access to bootloader or the way to extract it without phone started. Silly win for the google (nokia) developers in constraining modifications, with time, (loss of sales) that might change, hence "politics"

Anyone managed to enable boot loader access? Mine had already A13 (funk it) with oem function access disable (grey) in developer mode

phaleg said:
Trying not to be offtopic, why a decent phone, from a well known brand like Nokia, that often offered android one devices has now low to zero interest from developers? It's not polemic, I am just curious
Click to expand...
Click to collapse
because HMD just keeps on locking down everything, and tries to stop people from even unlocking the bootloaders by using broken bootloaders for retail units.
Hikari_Calyx once wrote a whole article on Medium on why it's stupidly hard to unlock the retail units (that are made by HMD), but TL;DR: HMD locks the bootloaders even further every time a new security/feature update is released to its phones by itself, and it even janks the code that makes up the phones' bootloaders, forcing people to use prototype ABL images to unlock the phones.
The fact that you even need prototype/unreleased models of the damn retail units to unlock those units themselves is stupid enough...
As for the older models (e.g: 8 PureView, or 6.1, or whatever before 2021-or-so, I suppose? because there are exceptions, like the G10/G20) though, they're fine. All you need is an unlock key (though, unfortunately, you have to buy the key...), and adb, then use the unlock key, and you're done! Nokia even provided a bootloader unlocking service before (although, they only offered it for a limited time, and it doesn't even work across all of their phones! - they only supported the Nokia 8, and the phone had to run on Android 8 with an old security patch, or else they wouldn't allow the unlocking!)

alegatorul said:
Anyone managed to enable boot loader access? Mine had already A13 (funk it) with oem function access disable (grey) in developer mode
Click to expand...
Click to collapse
that option is useless. Ignore that.

AltFantasy said:
because HMD just keeps on locking down everything, and tries to stop people from even unlocking the bootloaders by using broken bootloaders for retail units.
Hikari_Calyx once wrote a whole article on Medium on why it's stupidly hard to unlock the retail units (that are made by HMD), but TL;DR: HMD locks the bootloaders even further every time a new security/feature update is released to its phones by itself, and it even janks the code that makes up the phones' bootloaders, forcing people to use prototype ABL images to unlock the phones.
The fact that you even need prototype/unreleased models of the damn retail units to unlock those units themselves is stupid enough...
As for the older models (e.g: 8 PureView, or 6.1, or whatever before 2021-or-so, I suppose? because there are exceptions, like the G10/G20) though, they're fine. All you need is an unlock key (though, unfortunately, you have to buy the key...), and adb, then use the unlock key, and you're done! Nokia even provided a bootloader unlocking service before (although, they only offered it for a limited time, and it doesn't even work across all of their phones! - they only supported the Nokia 8, and the phone had to run on Android 8 with an old security patch, or else they wouldn't allow the unlocking!)
Click to expand...
Click to collapse
It's sad that Nokia so fiercely fights people that would like to use android "open" as it should be :/

phaleg said:
It's sad that Nokia so fiercely fights people that would like to use android "open" as it should be :/
Click to expand...
Click to collapse
nah, blame HMD for that.
Nokia is trying to distance itself from its past with their legendary phones (like the N95, E95, N97, 3310, and soooo much more!) now, starting from when they redesigned their logo to a more.... minimalistic look, I guess? and their booths in tech events (e.g: CES) now market their IoT tech, routers, and whatnot...
As for HMD, though, they'll keep on using the old logo, because muh homage to le legendary phones and all that, blah blah. (even though their "new" N95 prototype (you can view it in MrMobile's video about the old Nokia N95) is just essentially very uniform (with just a kickstand built into the camera unit, and speakers that slide out from the left side of the phone....))

HDM or Nokia, logic is the same, it is strange to be so stricth about modding android from a company that used to produce devices with Android one (if I am not mistaken, was the type of android very stock without producers modifications in the SW)

Right, now back as we should on topic..
How did you manage to unlock the bootloader & install twrp or similar app?

alegatorul said:
Right, now back as we should on topic..
How did you manage to unlock the bootloader & install twrp or similar app?
Click to expand...
Click to collapse
I don't know if my guide will also work for your device (though, I suspect it'll still work with the XR20, since all you have to do is flashing the ABL, then do the unlocking commands and all), but here's my guide on how to unlock the bootloader.
Do note, however, that my guide is for a different device (the X10), so it has a few differences here and there, from the XR20 (the unlock commands, and the ABL files). Hikari_Calyx has already given you the commands and files in his post, so just grab that from there.
As for TWRP, you'll have to port the recovery to your phone, which means learning programming and dealing with image layouts and whatnot...

phaleg said:
HDM or Nokia, logic is the same, it is strange to be so stricth about modding android from a company that used to produce devices with Android one (if I am not mistaken, was the type of android very stock without producers modifications in the SW)
Click to expand...
Click to collapse
hahaha, nah, just because a phone runs Android One, doesn't mean its manufacturer will do such a thing. Android One is just the software/operating system part of the phones, and as for the bootloader (which is in the firmware part of the phone), they can just modify it however they want, for the sake of "security" and "stability" and blah blah blah.
It's just like if PC motherboard manufacturers like MSI and ASUS lock people to just using Windows, without any capabilities to use other OSes (e.g: Linux), then claim that they haven't done any modifications to the OS.

AltFantasy said:
hahaha, nah, just because a phone runs Android One, doesn't mean its manufacturer will do such a thing. Android One is just the software/operating system part of the phones, and as for the bootloader (which is in the firmware part of the phone), they can just modify it however they want, for the sake of "security" and "stability" and blah blah blah.
It's just like if PC motherboard manufacturers like MSI and ASUS lock people to just using Windows, without any capabilities to use other OSes (e.g: Linux)
Click to expand...
Click to collapse
Cheers mate.
I'll try with unblocking...
Anyway, the phone is 1 month old under warranty still

Question Disadvantages of Onlocking Bootlaoder

i ordered a X30 pro with CN ROM but the seller sent one with GLOBAL ROM installed . He agreed to revert from Global ROM to CN ROM but said that relocking the device would damage the phone.
I want to know if i revert the Bootloader unlocked phone to CN ROM , will i be able to use Netflix,Google Services and OTA updates?
Is there something i am missing out compared to the Bootloader Locked device with CN ROM?
I have an option to legally force him to replace the device, but it will be a loss for the local seller who procured it from china and i dont want to impact the poor guy's profits if there is no major feature i will be missing out.

Device can be returned to CN and relocked safely. As I am dumb enough not to notice that people repeatedly use my work to further grow their business I am not gonna post a link to the guide.
However: If you receive a Frankenstein device that was converted to global and then locked you can not unlock it again on your own and need people with the proper tools and edl mode probably.
The cleanest way is to receive an original device and then do the work yourself. You'll learn and you will only have yourself to blame if things go wrong.
Netflix, google service and ota's are all working on my relocked phone. Can not say how far Netflix is working but it does start (which it refused to do on global firmware)

@Killuminati91 RSA tool said my device is out of warranty I think he perceives the situation, but what he perceives is this: The situation i noticed in a few videos i watched on Youtube; Those who use this software box, that is, the software developers who made my device, take the device from fastboot mode to a so-called "factory mode" in order to write global software or imei change to Motorola devices, and do the operations that way. That mode also does not require the unlocked bootloader to perform these operations. In Factory mode, the screen is black, nothing is visible, but the box continues to perform operations Very interesting...

Killuminati91 said:
Device can be returned to CN and relocked safely. As I am dumb enough not to notice that people repeatedly use my work to further grow their business I am not gonna post a link to the guide.
However: If you receive a Frankenstein device that was converted to global and then locked you can not unlock it again on your own and need people with the proper tools and edl mode probably.
The cleanest way is to receive an original device and then do the work yourself. You'll learn and you will only have yourself to blame if things go wrong.
Netflix, google service and ota's are all working on my relocked phone. Can not say how far Netflix is working but it does start (which it refused to do on global firmware)
Click to expand...
Click to collapse
Thanks for the reply and i absolutely understand your concern. But what if i return to CN ROM and leave the Bootloader unlocked? Will there still be Netflix, google service and ota working ? Will i be losing out on something apart from the manufacturer's warranty?

Killuminati91 said:
Device can be returned to CN and relocked safely. As I am dumb enough not to notice that people repeatedly use my work to further grow their business I am not gonna post a link to the guide.
However: If you receive a Frankenstein device that was converted to global and then locked you can not unlock it again on your own and need people with the proper tools and edl mode probably.
The cleanest way is to receive an original device and then do the work yourself. You'll learn and you will only have yourself to blame if things go wrong.
Netflix, google service and ota's are all working on my relocked phone. Can not say how far Netflix is working but it does start (which it refused to do on global firmware)
Click to expand...
Click to collapse
hello I have a moto edge 30 ultra region reteu with its stock rom with locked bootloader, it opened and then I closed it it stayed bricked I had to fix it remotely but now it won't let me unlock bootloader because it hasn't been certified do you know if it's possible to go back to unlock bootloader to leave it already open?

cascade128 said:
@Killuminati91 RSA tool said my device is out of warranty I think he perceives the situation, but what he perceives is this: The situation i noticed in a few videos i watched on Youtube; Those who use this software box, that is, the software developers who made my device, take the device from fastboot mode to a so-called "factory mode" in order to write global software or imei change to Motorola devices, and do the operations that way. That mode also does not require the unlocked bootloader to perform these operations. In Factory mode, the screen is black, nothing is visible, but the box continues to perform operations Very interesting...
Click to expand...
Click to collapse
Yeah that is EDL mode if im not mistaken. You can force it by bridging pins on the motherboard, but there must be other options to boot into it. (Xiaomi supported a certain USB cable that bridged the pins basically for a few devices). Its like a really low level flash mode.
@ragz85: I think netflix wont work with an open bootloader but I never did any research about it. There might be magisk modules that can fix it.
If your bootloader is open you bascially NEED root / magisk to fix problems like online banking, google certification and safetynet.
Root on the other hand seems to disable OTA updates. Not too sure because I am certain that I received an update after converting to RETEU with an unlocked bootloader but didnt get any more OTAs after that.
@iron maiden: The guy who fixed your phone might be able to do it. No other ideas here.

Killuminati91 said:
Yeah that is EDL mode if im not mistaken. You can force it by bridging pins on the motherboard, but there must be other options to boot into it. (Xiaomi supported a certain USB cable that bridged the pins basically for a few devices). Its like a really low level flash mode.
@ragz85: I think netflix wont work with an open bootloader but I never did any research about it. There might be magisk modules that can fix it.
If your bootloader is open you bascially NEED root / magisk to fix problems like online banking, google certification and safetynet.
Root on the other hand seems to disable OTA updates. Not too sure because I am certain that I received an update after converting to RETEU with an unlocked bootloader but didnt get any more OTAs after that.
@iron maiden: The guy who fixed your phone might be able to do it. No other ideas here.
Click to expand...
Click to collapse
hello then who revived it for me via remote can? So it's not impossible then? thanks for your answer
regards

iron maiden said:
it's possible to go back to unlock bootloader to leave it already open?
Click to expand...
Click to collapse
You can no longer open the bootloader on your device.

baikal0912 said:
You can no longer open the bootloader on your device.
Click to expand...
Click to collapse
but I have a problem and it is that being blocked it does not let me pay with a card, it detects it as root, how is it possible?

I assume you already have the answers to your questions... I'll still leave it here for anyone who might be interested:
1 With unlocked bootloader, no matter the ROM version (EU, BR, CN) you will NOT have Netflix, HBOMax, or Disney (the ones I tested).
2 It is possible YES to lock the Bootloader again. With that you have Streaming services and you can use almost everything from Google. Except Assistant(OK Google) and Android Auto.
To carry out the Block follow https://rentry.org/edge30ultra-relock even without the backup (because I acquired it already unlocked) I managed.

RicoMartins said:
I assume you already have the answers to your questions... I'll still leave it here for anyone who might be interested:
1 With unlocked bootloader, no matter the ROM version (EU, BR, CN) you will NOT have Netflix, HBOMax, or Disney (the ones I tested).
2 It is possible YES to lock the Bootloader again. With that you have Streaming services and you can use almost everything from Google. Except Assistant(OK Google) and Android Auto.
To carry out the Block follow https://rentry.org/edge30ultra-relock even without the backup (because I acquired it already unlocked) I managed.
Click to expand...
Click to collapse
I bought the moto edge x30 pro with the global ROM installed the same. Even though I don't have the backup of the original Chinese ROM that was on the cell phone, can I do the procedure with a Chinese ROM from the Lolinet site? After you blocked the bootloader again, the banking apps and Googlepay work normally? I want to do this but I'm not sure. If I dare to do it, what version of the Chinese ROM did you download?

marc182 said:
I bought the moto edge x30 pro with the global ROM installed the same. Even though I don't have the backup of the original Chinese ROM that was on the cell phone, can I do the procedure with a Chinese ROM from the Lolinet site? After you blocked the bootloader again, the banking apps and Googlepay work normally? I want to do this but I'm not sure. If I dare to do it, what version of the Chinese ROM did you download?
Click to expand...
Click to collapse
Yes friend, you can go to lolinet website go to the folder (EQS CN) download the oldest version (the first of the three from top to bottom) unzip open the file flashfile.xml with notepad (Or the one you prefer) copy everything and paste it on the site that will general the codes (the link is on the site I posted above) have magisk installed and saftnetyfix module (Install to enable OEM unlock in developer ) enabled uninstall magisk (by magisk itself ) format device and enable USB debugging, in bootloader Connect to the PC open CMD in the ROM folder and change the channel to retcn then copy all the codes from the website and paste in CMD and wait when finished restart the device configure (or skip) and activate USB debugging And connect to Lenovo Recue it should recognize your device and it will download the latest ROM follow the steps until restart installed skip and enable USB debugging open CMD and lock with Fastboot oem Lock You will have EVERYTHING working, Banks, Google play, FHD streaming (except Android auto and Ok Google)