Related
disclaimer!
*this thread is not intending to promote the sale of any particular service or cell phone reseller.
*this thread is intended to provide info only. any questions,please ask,some i may add to the FAQ.
*please abide by all forum rules in posting so this thread can remain open
this method uses an official htc java card to turn off the phones security data. the card exists as a legitimate tool for cell phone shops and re-sellers,primarily for the purpose of removing the phones simlock.
since this method of s off is somewhat unusual,this thread is intended to help support folks that are unsure of the differences and similarities. use this info at your own risk.
in this first post,i thot a few FAQs needed to be put in one place,as they are being asked over and over again in the thread.
Frequently Asked Questions
Q: what is s off?what does it do for me?
A: in a nutshell,s-off=security off. it removes all security checks and allows access to all partitions of the phone this means you can:
-change hboot
-change splash inage
-change radios
-flash unsigned files
-go backwards in firmware versions
-other things that maybe ill add later
Q: is this java card process legit??
A:yes,it is. as mentioned above,the java card is a legitimate tool used by some large cell phone repair shops and re-sellers.
Q: how does this work?
A:the java card is plugged into a USB On The Go cable,and plugged into the phone. the java card contains htc-signed diagnostic files wich are used to clear security data. when the phone is booted to hboot with the java card plugged in,it finds the diagnostic file and jumps to a mode where the user can clear "s58" data. this removes any simlock,changes the CID to a generic "supercid",and most importantly,turns off the phones radio secure flag. hooray!
this video of an htc one x will give you a good idea what the process looks like:
HTC One X S-OFF
Q: what exactly is a java card?
A: simply,a java card is an sd card with a microprocessor in it. if someone wishes to provide a more detailed definition,id be happy to put it here.
Q: can we clone the java card so everyone can have s off?
A: yes. but its complicated,and the card to begin with is expensive. there have been some technical discussions about this,but the simple answer is that it is not easy,or practical to clone the java card.
Q: why do i have to pay for this?? shouldnt s off be free?
A: if you have a prollem paying for this service,you are welcome to purchase your own java card and offer the service for free. as has been stated,the java card is expensive- upwards of $1000 depending how may credits are included.
further,even if a software exploit was available,it is good custom to donate to the devs who brought you the tool. remember,no one here owes you custom roms,s-off,etc. support your devs and what they bring you.
Q: is the card good forever?
A: NO! the java card has a limited number of uses.
Q: how do i use this service?
A: you will need to track down a phone shop or reseller that has a card. these are not common,but are available in most countries with some searching.
Q: if im allready unlocked,should i still get s off?
A: in my opinion,yes. wether done via a java card or software exploit,s off is better. it allows more options to recover soft-bricked devices,and allows access to all partitions. an s on phone is still doing plenty of security checks. it also allows a permantly installed recovery to install the boot image. the downside is that your phone WILL let you brick it if your not careful. know what your flashing and why. double check md5 sums to verify the integrity of your downloads. a corrupt bootloader ot radio can damage your phone,potentially unrecoverably. if you just asked "what is an md5sum?" stop and google it now. there are numerous md5summers avaialable for free on the vast interweb,download one and start using it.
Q: if im allready unlocked and running a custom rom and recovery,do i need to take any precautions?
A: yes. the diag file is designed to work on stock software and firmware. i would strongly recomend to:
-restore a bone stock nandroid,or flash a bone stock rom
-reflash your stock recovery
-reflash your stock boot image if you were running a custom kernel
-select 'factory reset' option from hboot
Q: will this wipe my phone?
A: yes it will. so back up your sd card to the pc,and be prepaired to have to re-set everything up when you get it back.
Q: does my phone need to be active?
A: no it does not.
Q: does my sim card need to be present?
A: no it does not.
Q: how do i activate a spare phone while mine is away?
A:it depends on the phone. if you have a gsm phone,or a 4g vzw phone,you can simply swap over your active sim. if the sim is larger in the spare phone,adapters do exist for extremely cheap on ebay and amazon. alternately,you can call vzw,sprint,or your other cdma carriers, or go to their website to activate an older 3g device.
Q: how do i activate my phone when it comes back?
A: like you normally would. s off by itself does not change anything about the phone or how it oporates. its what you do afterward/modify that can have an impact on "normal" operation. so if you moved your sim into another phone,just move it back. if you mailed your phone directly to a reseller with the protective film still on it,then take everything out of the box and activate just like you would if it had just come from htc or your carrier.
Q: if my phone was carrier blocked by htc dev,will i be able to unlock the bootloader if my phone is s off?
A: yes. when the phone comes back,it will have "supercid". this ignores the mid(model id) check that htcdev does on the phone,and will let you get a token and unlock.
Q: are there advantages to unlocking the bootloader?
A: you have a couple extra fastboot commands you can use:
fastboot flash partition imagename.img
and
fastboot boot imagename.img
these commands are useful to install recovery,and boot images into phone memory. with fastboot bootfor example,you can temporarily launch recovery on the phone to flash su if you dont want to permantly install it.
Q: so do i NEED to unlock the bootloader to install recovery?
A: no,you do not. you can install recoveries and all other partitions as zip files. more info on that later.
Q: does superCID give you any benefits?
A: in a word,maybe. on a gsm device where you have multiple carrier and regional firmwares that will work,supercid is of value. with a device on vzw sprint,or other cdma carriers using specific firmware,you can only use those specific ruus anyway. further,accepting an OTA with supercid could leave you unrecoverably bricked,plus it may interfer some some verizon functions(i remember inc 4g users having issue,but the details escape me)
IMO,after unlocking your bootloader,if you choose to do so,you should change your CID back to stock VZW__001 (thats 2 underscores- cid is always 8 digits),HTC__001(again 2 underscores) or whatever it happened to be.
Q: is my cid unique to my particulare phone?
A: no,it is not. it is unique to a carrier or region. all verizon phones ever made have a cid of VZW__001
Q: how do i change my cid back to stock?
A: with this fastboot command:
fastboot oem writecid xxxxxxxx
Q: why is my cid always present on the hboot screen?
A: i dont know htc's logic,but this is simply what the phone does while its s off. it will display whatever your cid is,and is not dependent of your bootloader being locked or unlocked.
Q: what about the TAMPERED and unlocked/relocked badges?
A: if your phone was unlocked when you sent it in, youll get it back factory fresh locked. the tampered badge,i am unsure of at this time,and will update as more info is obtained.
if you sent in a brand new phone,it obviously wont be different(with exception of s off)
one of the big advantages of s off,is that the tampered flag is not triggered by adding a custom recovery or kernel,and since s off removes the various write protections that exist,it is posible to reset either flag. more info on the lock status flag here
Q: will an OTA change my s-off or lock status?
A: it is possible. altho,it is highly unlikely since turning the radio secure flags on via an OTA would also do so on legitimate pre-release test phones.
however...
it really is not reccomended that you try and take an OTA while rooted. a custom recovery is unable to install HTC's OTA pacakage,and attempting to do so ca jam you up horribly. taking an OTA with bloat and system files remove will typicaly result in failure,and taking an OTA with supercid could lead to a processor "do not boot" mode,wich is very effectively a hard brick only recoverable via jtag. or a new device.
the best way to update a rooted device is to update the rom with a recovery-flashable zip file,and the firmware extracted from the OTA package. this will update you just like taking the OTA. there is nothing magical about over the air updates. please,just do it manually. leave the OTAs for the stock crowd.
last and not least!
Q:what do i do once i get back my stock,s-off phone?
A: please see post 2
once you have recieved your stock,s off device back,your basic steps are:
1)change CID/MID back to stock
2)install a recovery
3)install a rom or root access
you have 2 options to install recovery:
1)unlock the bootloader and use fastboot commands
2)leave the bootloader locked,and flash a recovery as a zip file in RUU mode
either way works. i personally always keep my bootloader unlocked so i can use fastboot commands,but that is a personal preference.
to "root by recovery" is not a new concept. once there are no write protections,its easy to install a custom recovery,and use that recovery to either insert the superuser files into the stock rom,or replace the rom entirely.
1) change cid back to stock
this is actually very easy. simply put the phone in fastboot,change to fastboot directory,and enter in a cmd window:
fastboot oem writecid xxxxxxxx
in the case of vzw:
fastboot oem writecid VZW__001
yes,those must be capital letters,and there are 2 underscores.
2) install a recovery
via one of these 2 methods:
1)unlock the bootloader
your phone has come back from sonic with "supercid",wich will allow you to unlock the bootloader natuarally via the htcdev website. see this post for a bit more info on that.
unlocking the bootloader is fairly straightforward,just make sure you use a vzw one specific image. download from one of the following threads:
*links provided when available
the image is easily installed via an unlocked bootloader with the following command:
fastboot flash recovery imagename.img
for example,recovery named CW_touch_recovery:
fastboot flash recovery CW_touch_recovery.img
the image must be in your fastboot working directory.
if you need more specific help with unlock/recovery flashing you can use this guide.
2) keep locked bootloader
the bootloader can stay locked for this method. you can in fact use this to install a new image to any partition,as long as the image is packed up in a proper file.
this assumes a working adb/fastboot and drivers installed. if you dont have these things,you can use this guide from above,downloading the files in post 1,and following the set up adb and prepair to root part in step 2.
once you have adb and fastboot working,download one of the following recovery zip files. do NOT unzip or extract.
*links provided when available
your zip file is flashed in the following manner:
if youre working with a booted,operational phone,you can flsh the file in the following manner:
-open a cmd window
-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )
-place the zip file you want to flash into adb/fastboot directory
-enable usb debug,disable fastboot,plug in phone
-check for connectivity
adb devices (should return serial number)
-boot to fastboot
adb reboot bootloader
-check for connectivity again
fastboot devices
-flash the file
fastboot erase cache
fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)
fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)
*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish
-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)
-reboot back to the OS
fastbooot reboot
you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices
Click to expand...
Click to collapse
3) install a rom or root access
this is a simple matter of using recovery to either flash superuser,or flash a new rom. in either case,MAKE A BACKUP OF YOUR STOCK UNROOTED ROM!
flash superuser just as you would a rom,after a cache/dalvik wipe. theres tons of info out there on using recovery,so im not going in to great detail on that here.
i dont have this device(well,i dont have the vzw version) so dont ask me whats the best rom to flash. browse the development and original development sections and pick a couple out to try.
if you wish to just run rooted stock,i perosnally prefer superSU to other versions of superuser. you can download it from this thread
_____________________________________________________________________________________________
optional:
if you sent in your phone with a custom recovery installed,and it still is displaying the tampered banner,see this thread to remove it:
*link provided when available
if you want to lock,or unlock your bootloader without messing with htcdev,see this thread for those directions:
*link provided when available
if you want to restore your supermid from 0P6B2**** back to stock ,see this thread:
http://forum.xda-developers.com/showthread.php?p=51677666
_____________________________________________________________________________________________
*work in progress. there will likely be some revisions,but i wanted to get something up for the folks whose devices are coming back
I'm serious considering doing this, if only just so I can have full root. I understand that there won't be any developer support or roms until someone achieves a software exploit. But it would be nice to be able to flash full root.
One question though: I don't have much experience with HTC devices as I always used Samsung before but I'm tired of their locked bootloaders. Basically my question is, one method of s-off is as good as another right? S-off is s-off? And it won't effect my ability to get s-on again? Or use other people's methods for recovery/root and s-off/s-on right?
nicholi2789 said:
I'm serious considering doing this, if only just so I can have full root. I understand that there won't be any developer support or roms until someone achieves a software exploit. But it would be nice to be able to flash full root.
One question though: I don't have much experience with HTC devices as I always used Samsung before but I'm tired of their locked bootloaders. Basically my question is, one method of s-off is as good as another right? S-off is s-off? And it won't effect my ability to get s-on again? Or use other people's methods for recovery/root and s-off/s-on right?
Click to expand...
Click to collapse
Once you are S-Off u are S-Off unless you really screw something up but I have NEVER had any issues and I have owned 4 HTC devices with S-Off via exploits. S-Off is where it's at! Period Will have mine early next week with a Java S-Off... :good: And, we will have a recovery soon enough for our variant so it's just a matter of time before you can flash full root from recovery and then you are good to go. We probably won't see much development until enough people or devs get S-Off or unlocked bootloader. Time will tell but it WILL happen.
shojus said:
Once you are S-Off u are S-Off unless you really screw something up but I have NEVER had any issues and I have owned 4 HTC devices with S-Off via exploits. S-Off is where it's at! Period Will have mine early next week with a Java S-Off... :good: And, we will have a recovery soon enough for our variant so it's just a matter of time before you can flash full root from recovery and then you are good to go. We probably won't see much development until enough people or devs get S-Off or unlocked bootloader. Time will tell but it WILL happen.
Click to expand...
Click to collapse
Thanks for the response. Yeah I've been reading up on S-OFF and all the things you can do to HTC devices since before I got the M8 and still had my S4. I just haven't done any of it yet. It really seems like S-OFF is the only way to go if you want to have complete device freedom. Never had to have anything special to flash radios on Sammy devices. Anyways, yeah I have full faith that we will get S-OFF via an exploit sooner or later. That's why I chose the M8. Because in the past, no matter what, HTC devices always have bootloader exploits it seems like, or at least some development.
This thread is on zero tolerance as of now and will be closed permanently with the next breach of forum rules.
NotATreoFan said:
This thread is on zero tolerance as of now and will be closed permanently with the next breach of forum rules.
Click to expand...
Click to collapse
shojus said:
Click to expand...
Click to collapse
i think they dont want a name given
it also might be the grey market that java cards are. 1/2 this FAQ is not factual, but what do I know? *wink*
dr_drache said:
it also might be the grey market that java cards are. 1/2 this FAQ is not factual, but what do I know? *wink*
Click to expand...
Click to collapse
What is not factual? I'd be happy to correct anything that is not.
Sent from my HTC6435LVW using Tapatalk
scotty1223 said:
What is not factual? I'd be happy to correct anything that is not.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
well, not to go too deep, javacards at the price you posted, are clones of real ones, sold on the grey market. not necessarily legal, using NDA covered files.
dr_drache said:
well, not to go too deep, javacards at the price you posted, are clones of real ones, sold on the grey market. not necessarily legal, using NDA covered files.
Click to expand...
Click to collapse
That number was for a small credit card from the UK. It was supposed to be legit, but I obviously can't prove or verify it.
Thanks for the info
For the record, my main intention is to provide info about the mechanics. Not really trying provide cost or purchase info
Sent from my HTC6435LVW using Tapatalk
scotty1223 said:
That number was for a small credit card from the UK. It was supposed to be legit, but I obviously can't prove or verify it.
Thanks for the info
For the record, my main intention is to provide info about the mechanics. Not really trying provide cost or purchase info
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
So, how do I know if my phone was S-Off'd via a java card or Firewater? What is the difference? TIA
shojus said:
So, how do I know if my phone was S-Off'd via a java card or Firewater? What is the difference? TIA
Click to expand...
Click to collapse
If it comes back supercid and supermid,then it was s offed via the java card. If cid and mid are correct you have no way of knowing for sure,since the cid and mid are easily restored
Sent from my HTC PG09410 using Tapatalk 2
scotty1223 said:
If it comes back supercid and supermid,then it was s offed via the java card. If cid and mid are correct you have no way of knowing for sure,since the cid and mid are easily restored
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
I'm not sure but from pics I seen of exploit don't it throw the tampered flag? As last time I used java card that was not the case
I know that can be restored. I'm guessing he restored cid mid because there were people complaining that he should change this back if you use his services. Just a total guess
Sent from my HTC6525LVW using XDA Premium 4 mobile app
scotty1223 said:
If it comes back supercid and supermid,then it was s offed via the java card. If cid and mid are correct you have no way of knowing for sure,since the cid and mid are easily restored
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
That's my dilemma here... Mine came back yesterday with cid and mid correct.
Tigerstown said:
I'm not sure but from pics I seen of exploit don't it throw the tampered flag? As last time I used java card that was not the case
I know that can be restored. I'm guessing he restored cid mid because there were people complaining that he should change this back if you use his services. Just a total guess
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
the java card will not throw the tampered flag. the exploit... i dont think so,but im not 100% sure.
shojus said:
That's my dilemma here... Mine came back yesterday with cid and mid correct and I am a tad skeptical.
Click to expand...
Click to collapse
i would assume that he corrected the cid and mid in order to provide better service. sorry i cant think of any other ways to know for sure.
Me either but I will discuss this elsewhere . Thanks
scotty1223 said:
i would assume that he corrected the cid and mid in order to provide better service. sorry i cant think of any other ways to know for sure.
Click to expand...
Click to collapse
That is what he said to me he did.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Good day to all,
my first post after trying everything
I am currently on BLN-TL10C01B380 EMUI 5.01 Android 7 on my 6x BLN-TL10
AFTER I messed up by running a OTA on rooted and unofficial unlocked previous EMUI/Android version.
Well, device is back alive BUT I lost the OEM Unlock function in developers and what's worse the external SD card is bricked. Apparently pin codes are lost after a full wipe, update to different android version and any previous used external card won't be accessible anymore.It is asking for SDcard PIN though but the one I used is getting rejected. ..
I tried several recovery apps on mobile and PC but no success. I removed the extSD to be save and now this !!
Additional problem, I need ROOT back ! I tried multi tool, paid services etc.... NO OEMUNLOCK option visible. I even tried official unlock but got told I have to visit Huawei Center. Which I cannot since I am in Swaziland/Africa.
A rollback is not available for this model. Could I use firmware finder? Move to older version?
Any help is greatly appreciated
No advise? Am I the only one? ... no phone isn't stolen either.
At first relock bootloader.the phone will be reset factory.then oem unlock.and again bootloader unlock and root the phone
Hi everyone.
I'm thinking in buying a phone from CAT (CAT S42) and I'm not sure if I can unlock its bootloader. But I've seen on another forum that the CAT S31 has root available for it through Magisk, and I didn't see anyone mentioning having unlocked the bootloader. S42 has a MediaTek chipset and S31 has a Qualcomm chipset, if that helps.
So my question is: is unlocking bootloader MANDATORY to root a device? Can I just run a custom recovery, root the phone with that, and then the recovery gets overwritten on system boot? Or can I root through USB debugging without even needing custom recovery?
The CAT S31 I mentioned was rooted with Magisk, and as I said, I didn't see anyone talking about unlocked bootloader. But I also read Magisk changes the boot partition and the bootloader checks if it was modified. So I'm a bit confused with this too. It's also written that MiracleBox was used and I'm not sure that's the reason that I'm getting confused or not (I had never heard of this tool until now).
A set of software for obtaining ROOT privileges.
Driver_Qualcom_m.7z (9.27 MB) [link]
Enter HS QDSLoad 9008 mode from Vol + and Vol- off state and connect without releasing to USB
MiracleBox [link]
The Boot image is processed on the phone by the Magisk manager, then uploaded to the phone using Miracle again from the computer.
MagiskManager-v7.3.2.apk (2.71 MB) [link]
Just in case,
Backup firmware without / Data partition
Attached files
XposedInstaller_3.1.5-Magisk.apk (2.96 MB) [link]
Click to expand...
Click to collapse
How may they have done that?
I'm sorry, I don't understand a lot of the root requirements part, since I was lucky and my 1st phone had the bootloader unlocked alreaedy for some reason and the second was as easy as writting a single command. But about this phone there's almost nothing and I'd like to know the general about this. If it's really necessary to have the bootloader unlocked, for example. And if it's not, then what methods can I use with it still locked?
Thanks in advance for any help!
Hello DADi590,
Unfortunately I can't answer all of your questions about S42. I have one of them and I am also looking for and confused with root procedures. But I can tell you that unlock boot loader was just a matter of get developer options on (tapping version # 10 times), and inside you can toogle lock/unlock bootloader...
How to root it safely is what I do not know yet.
good luck!
@DADi590
Rooting the Android OS of a device in practice is nothing more than adding the su cmdlet known from Linux OS to the Android OS. To root Android OS in no case requires device's bootloader must get unlocked to do so.
FYI: The bootloader of an Android device is comparable to the BIOS of a Windows computer.
Actually, after some time I decided to leave CAT alone and buy a Blackview one. If I'd break the phone, at least it wouldn't be as expensive as the CAT S42 (I bought a BV9500 - not Pro or Plus, the normal one).
Since then (with help of adventures with a tablet of mine) I've learned some more things. One of them I was suspecting and was now confirmed (thank you @jwoegerbauer) which is to root the device, just a binary file is needed to be on the correct place: su. I didn't know it was on other Linux OSes though. Interesting!
So the idea is that just a recovery must be installed to root a device. That's it and nothing else, I believe. To install the recovery is the part where one might need to unlock the bootloader - or not, if the chipset manufacturer left a tool to write partitions directly, like MediaTek or Rockchip. On these 2 it's possible to write partitions directly with a locked bootloader (this means the bootloader on my 1st phone was and still is probably locked - like my BV9500 one is, and I flashed various partitions on it already, one of them, a TWRP recovery).
This explanation is for anyone else like me who would have this question. Bootloader is just to flash partitions and I think run modified ROMs too, but not too sure about that (I never use custom ROMs). [Btw, if I said something wrong, I'm happy to be corrected!]
armandrix said:
Hello DADi590,
Unfortunately I can't answer all of your questions about S42. I have one of them and I am also looking for and confused with root procedures. But I can tell you that unlock boot loader was just a matter of get developer options on (tapping version # 10 times), and inside you can toogle lock/unlock bootloader...
How to root it safely is what I do not know yet.
good luck!
Click to expand...
Click to collapse
I believe I asked this because I prefer that it's not required to unlock a bootloader to do stuff. If you screw the phone somehow with the bootloader locked and there's no tool to flash partitions on it and you must be on fastboot with an unlocked bootloader or whatever, you just bricked the phone. And I'd prefer that not to happen. That's why I chose to buy phones that don't need me to unlock the bootloader to do anything on them. That might mean I can't ever brick them (at least I never bricked my 1st phone with the various things I did on it which I later found out not being recommended at all XD).
I've unlocked the bootloader on my Cat S42. Can be done.
Hi community
First Thanks to the people who take time to help, and admin that create that forum. Im always glad to see that s there is still people caring about helping each other
I come to you cause I spent the last 2 days trying to fix my brand new phone.
Brand : Xiaomi
Model : Mi ultra
My Computer : MacBook Air
Problem : "The system has been destroy"
Other problem :
- USB debugging OFF (not able to access to the phone in any way)
- Bootloader Locked
How its happen :
After installing an EU Rom, I re locked the boot loader using Adb... And it crashed.
I tried almost everything you find on internet using a Mac and till now nothing worked.
I tried to unlock the boot loader using ADB, which one the only thing who seems to be working and I got an error message saying that the Miunlocktools was too old ... ?
The token was available, as I already unlock it.
Does anyone know how I can switch ON the debugging mode without accessing my phone, or Unlock the boot loader using my Mac.
It seems there is solution possible but using windows computer, and tbh I will not buy a computer just for that.. for the moment
Thanks in advance to everyone
PS : I will offer 50USD straight in BTC to the one who will provide me the solution that will help me to fix it
Locking / unlocking a phone's bootloader is done by means of Fastboot, not ADB.
ADB & Fastboot are 2 completely different things. Don't confuse them.
AFAIK you can't enable ADB ( USB debugging ) from outside, this can only get enabled from inside ( Android Settings -> Developer options ) unless one creates/provides a flashable, properly signed ZIP that contains the code ( read: update-binary script ) to rewrite device's build.prop file entries accordingly.
BTW: A locked bootloader always tries to run device's Stock ROM.
Thanks for your quick answer. In other word, is it possible ? I am looking for what you say.
If I rewrite it, will I be able to switch it ON then ?
Im not at all a professional , that's my first step in this "world". It seems difficult, I will need to read a lot I think
What do you think about the EDL cable also, do you think it can work ?
thxx
Kayzers0ze said:
What do you think about the EDL cable also, do you think it can work ?
Click to expand...
Click to collapse
IDK.
Never have bricked a phone. And I never owned a Xiaomi device.
locking a bootloader (at least in xiaomi phones )results in the phone being reformatted and the stock rom is installed
also try installing the newest version of miunlock https://en.miui.com/unlock/download_en.html
you might have to wait 7 days or less or more or might not have to
historys said:
locking a bootloader (at least in xiaomi phones )results in the phone being reformatted and the stock rom is installed
also try installing the newest version of miunlock https://en.miui.com/unlock/download_en.html
you might have to wait 7 days or less or more or might not have to
Click to expand...
Click to collapse
Hi
I re locked the boot loader myself so I unlocked it before
Thats the version I have but in the terminal I got a message saying version is too old...
DO NOT LOCK THE BOOTLOADER WHILE ROOTED!
When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader.
Locking the bootloader will not fix most issues. It will allow you to use apps that check for an unlocked bootloader without the need for any additional modification. That is the ONLY benefit.
If you still want to lock your bootloader, make sure you can say yes to each of the following:
1. Have you restored the stock boot.img / vendor_boot.img and the phone functions normally?
Spoiler: Restore Stock Boot
Boot / DTBO Images [Root / Stock] - 5 / Pro / Ultimate (NOT S)
These images are NOT built from source. These are the stock images from the firmware provided by Asus that are extracted with payload dumper and uploaded without modification. 18.0840.2202.231 18.0840.2201.226 18.0840.2112.211...
forum.xda-developers.com
Follow the instructions in the thread above.
Use only the boot and vendor_boot images.
Do NOT flash any images that end with "-magisk.img"
2. Have you made a backup of everything you do not want to lose when wiping the phone?
Spoiler: Make a Backup
The sdcard is part of the internal storage and is cleared by a factory reset
Copy everything you want to keep to a computer or USB-C storage device
Apps and settings can be backed up by enabling the Google Backup option
Open Settings
Select Google
Select Backup
Select Back up now
Wait for the backup to complete
3. Have you flashed raw firmware and made sure the phone and updates function normally?
Spoiler: Flash Raw Firmware
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Follow the instructions in the thread above.
If you perform a wipe, you may skip step 4.
4. Have you performed a factory reset and made sure the phone functions normally?
Spoiler: Factory Reset
Open Settings
Select System
Select Reset options
Select Erase all data (factory reset)
Follow the instructions
Once you have verified all of the above requirements, you are now ready to lock the bootloader.
Spoiler: Lock Bootloader
From the bootloader (volume up + power):
Code:
fastboot oem asus-csc_lk
Reserved for QA information
I don't want to spread false information here, but here is a question post I created recently with two replies showing me contacting the help center (two different agents) confirming that I can use the app more than once to unlock the device's bootloader: https://forum.xda-developers.com/t/...nlock-relock-for-asus-rog-phone-5-5s.4367047/ . @Andrologic also confirms the case there for global (EU) version. I have a feeling that for the Tencent version it is because the sellers lock it on a wrong official ROM, or wrong ROM in general, e.g. global ROM, and therefore it confuses the unlock app. I am surprised the device did not even get hard bricked from locking on not the original ROM. By the way, I have contacted the help center of the US store, but I have a feeling it should work on the global (EU) version as well.
falhumai96 said:
I don't want to spread false information here, but here is a question post I created recently with two replies showing me contacting the help center (two different agents) confirming that I can use the app more than once to unlock the device's bootloader: https://forum.xda-developers.com/t/...nlock-relock-for-asus-rog-phone-5-5s.4367047/ . @Andrologic also confirms the case there for global (EU) version. I have a feeling that for the Tencent version it is because the sellers lock it on a wrong official ROM, or wrong ROM in general, e.g. global ROM, and therefore it confuses the unlock app. I am surprised the device did not even get hard bricked from locking on not the original ROM. By the way, I have contacted the help center of the US store, but I have a feeling it should work on the global (EU) version as well.
Click to expand...
Click to collapse
Based on new information, it does seem possible to repair the issues caused by converting.
That said, this guide is still quite relevant. After all, most of the issues people were having were caused by unlocking the bootloader, converting, rooting, and locking the bootloader. The warning for possibility of not being able to unlock have been removed, but the info about restoring to stock before locking has been left.
I send mine in for a motherboard repair I was rooted and everything I unrooted installed stock firmware and locked the bootloader again once I got the phone back I unlocked the bootloader once again and I am rooted again
chairman011 said:
I send mine in for a motherboard repair I was rooted and everything I unrooted installed stock firmware and locked the bootloader again once I got the phone back I unlocked the bootloader once again and I am rooted again
Click to expand...
Click to collapse
@chairman011 what variant of the phone it is (e.g. CN or WW or US, ...etc.)? Also, when they returned it to you and you were able to unlock it again, was it on the original firmware (or any version in its lineage (i.e. not a ROM that's not original))?
If by using ASUS unlock utility one was able to oneself unlock the boot-loader once, then is it safe to say that (after relocking it) it'd be possible to unlock it again?
nexusnerdgeek said:
If by using ASUS unlock utility one was able to oneself unlock the boot-loader once, then is it safe to say that (after relocking it) it'd be possible to unlock it again?
Click to expand...
Click to collapse
Some people have reported that you can't unlock the bootloader again after relocking, using the official "Unlock Device App", but I suspect it is an OS mismatch. This issue has only been observed on Tencent (CN) version with global ROM. Have anyone been able to unlock->relock->unlock on the same version of the phone, but not relocking while on the global ROM (i.e. relocking while on stock CN ROM)?
I am surprised the phone did not hard brick. Usually, and this is a general case in almost all Android phones with bootloader unlock capability, when you relock on a different ROM your phone hard bricks. Always restore to original ROM before relocking. Can people with Tencent (CN) phones with global ROM and locked bootloader flash the original CN ROM without unlocking the bootloader? If so, can you test the "Unlock Device App" to see if it works while on the CN (official) ROM? I gotta a feeling it might work in that situation.
falhumai96 said:
Some people have reported that you can't unlock the bootloader again after relocking, using the official "Unlock Device App", but I suspect it is an OS mismatch. This issue has only been observed on Tencent (CN) version with global ROM. Have anyone been able to unlock->relock->unlock on the same version of the phone, but not relocking while on the global ROM (i.e. relocking while on stock CN ROM)?
I am surprised the phone did not hard brick. Usually, and this is a general case in almost all Android phones with bootloader unlock capability, when you relock on a different ROM your phone hard bricks. Always restore to original ROM before relocking. Can people with Tencent (CN) phones with global ROM and locked bootloader flash the original CN ROM without unlocking the bootloader? If so, can you test the "Unlock Device App" to see if it works while on the CN (official) ROM? I gotta a feeling it might work in that situation.
Click to expand...
Click to collapse
It's an identification mismatch. It's similar to when you throw your SIM card in a different phone and your carrier lists you as having a different phone. Based on the information that has been discovered, it would appear that CN to WW conversions were wiping out the stuff that makes your device your device.
twistedumbrella said:
It's an identification mismatch. It's similar to when you throw your SIM card in a different phone and your carrier lists you as having a different phone. Based on the information that has been discovered, it would appear that CN to WW conversions were wiping out the stuff that makes your device your device.
Click to expand...
Click to collapse
So, basically the bootloader unlock for tencent devices will always locked unless asus uodate their unlock app or has their been another way around it yet?
The unlock app should unlock the bootloader at least once. Unlocking it a second time has mixed results.
Hi there, can you guys help me? I'm one of those unlucky ones who got my phone corrupted and won't boot anymore due to the boot loader. is there a way to fix this?? I've got an ROG phone 5s 16/512 on android12.
Hope you guys can help me! I know you guys have amazing brain cells than me when it comes to these things lol
Oh! and my rog is not the china version thanks
0v3rkill said:
Hi there, can you guys help me? I'm one of those unlucky ones who got my phone corrupted and won't boot anymore due to the boot loader. is there a way to fix this?? I've got an ROG phone 5s 16/512 on android12.
Hope you guys can help me! I know you guys have amazing brain cells than me when it comes to these things lol
Oh! and my rog is not the china version thanks
Click to expand...
Click to collapse
TYou should be able to RAW flash yourself out of it if a factory reset doesn't work. This does happen when re-locking the WW.
Andrologic said:
TYou should be able to RAW flash yourself out of it if a factory reset doesn't work. This does happen when re-locking the WW.
Click to expand...
Click to collapse
Hi there mate, thanks heaps for taking time.on my post. how do i do that? can you send me a link of the step by step guide? again thanks
0v3rkill said:
Hi there mate, thanks heaps for taking time.on my post. how do i do that? can you send me a link of the step by step guide? again thanks
Click to expand...
Click to collapse
Below post from the help guide (credits to the contributors) has links to RAW firmware packages. You just need any one of the WW packages. Download it and with your device in bootloader mode, run one of the .bat flash scripts that you'll find in the RAW package. The version doesn't matter, you can simply update to the latest firmware once you're back up.
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Andrologic said:
Below post from the help guide (credits to the contributors) has links to RAW firmware packages. You just need any one of the WW packages. Download it and with your device in bootloader mode, run one of the .bat flash scripts that you'll find in the RAW package. The version doesn't matter, you can simply update to the latest firmware once you're back up.
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi there, I did follow and did the raw setup it did got me through the boot loop. However, its stuck on the system start up updating screen and stays in 0%.
Darn i thought im already dead! i didn't even know how i fixed it hahahaha! but its working now successfully downgraded to android 11 because its the only firmware i found and managed to make it work again combination of alot of research in google and here xda. working 100% imei two of them, finger print and sn are all intact. thanks guys
For these few reasons I have to give up root & lock the boot-loader: 1. Financial apps stop working from time to time causing much grief; 2. I've used root functionality precisely for nothing for a year I've had it; 3. It was getting all too complicated to keep up with it all.
(The original intention for unlocking/rooting was to get some sort of unofficial VoLTE and VoWiFi for the mobile operator of my choice; however, it didn't help. Then a newer firmware implemented VoLTE and VoWiFi! So my impatience, admittedly couldn't be known at that point in time, backfired.)
I've nothing to preserve on the phone, due to having a Moto G 5G backup phone. I only had it working with adb & fastboot in my Linux laptop (up to date Fedora 36). I had no working Windows laptop then. But I do now. However, adb on Windows says the device is "unauthorised" (as expected); fastboot in it doesn't list the device. So I might be limited to my Linux laptop only. The phone was previously working on the last A11 WW firmware fine.
I've tried to follow the steps from the original post of this thread. First one worked with vendor_boot, dtbo & boot images (used only 18.0840.2202.231 versions of them). Second N/A. With third step, flash_raw_and_wipe_data.sh fails by core dumping.
Right now, the phone boots to fastbootd & not further. Any help is much appreciated.
(I think I'm inching towards fully bricking this phone. I'm not there yet, but getting closer . It'd be nice to get it working again without root & with locked boot loader. Any help is much appreciated.)
This is where I'm at while executing step 3 of the initial guide in this post:
When powered on, in the usual boot loader unlocked warning page, it prompts for power key to be pressed to continue.
(Here if power switch is not pressed within 30 odd seconds, phone powers down automatically.)
Once power key is pressed, it lands in boot loader. Selecting Start, it goes back to boot loader. I think this is called a boot loop.
While in boot loader, selecting "Recovery mode", it progresses to "Android Recovery". Here selecting "Enter fastboot" appears to take it furthest in the booting process of landing at "Android Fastboot".
(The version info showed in Fastboot -- 18.0840.2202.231-0 -- matches with the last A11 update I downloaded from Asus website & had it installed late March this year.)
I don't think it can boot any further at the state that it's in now.
I think this is where it needs a raw firmware to be flashed. This step keeps core-dumping in my Linux laptop when trying to use WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw file that was linked in the original post. This version appears to be quite old. Could the version mismatch between what the phone was running recently (18.0840.2202.231) and the raw file (18.0840.2106.83) cause the core-dump issue? IOW, would somebody have a link for 18.0840.2202.231 raw file please?
I couldn't use my work Windows laptop due to an issue I cannot overcome (installation of driver needed for the phone is somehow blocked in it). So, soon I'll try it from a personal Windows laptop of my neighbor. Let's see if it can progress any further with the help of Windows platform.
In the meantime, I can appreciate to be informed about any tips and tricks such as if this is something that the phone cannot be recovered from. Or even somebody highly skilled would like to help me to achieve a fully functional phone (with bootloader locked please) for a fair compensation. Please let me know. Thanks for any guidance.
nexusnerdgeek said:
This is where I'm at while executing step 3 of the initial guide in this post:
When powered on, in the usual boot loader unlocked warning page, it prompts for power key to be pressed to continue.
(Here if power switch is not pressed within 30 odd seconds, phone powers down automatically.)
Once power key is pressed, it lands in boot loader. Selecting Start, it goes back to boot loader. I think this is called a boot loop.
While in boot loader, selecting "Recovery mode", it progresses to "Android Recovery". Here selecting "Enter fastboot" appears to take it furthest in the booting process of landing at "Android Fastboot".
(The version info showed in Fastboot -- 18.0840.2202.231-0 -- matches with the last A11 update I downloaded from Asus website & had it installed late March this year.)
I don't think it can boot any further at the state that it's in now.
I think this is where it needs a raw firmware to be flashed. This step keeps core-dumping in my Linux laptop when trying to use WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw file that was linked in the original post. This version appears to be quite old. Could the version mismatch between what the phone was running recently (18.0840.2202.231) and the raw file (18.0840.2106.83) cause the core-dump issue? IOW, would somebody have a link for 18.0840.2202.231 raw file please?
I couldn't use my work Windows laptop due to an issue I cannot overcome (installation of driver needed for the phone is somehow blocked in it). So, soon I'll try it from a personal Windows laptop of my neighbor. Let's see if it can progress any further with the help of Windows platform.
In the meantime, I can appreciate to be informed about any tips and tricks such as if this is something that the phone cannot be recovered from. Or even somebody highly skilled would like to help me to achieve a fully functional phone (with bootloader locked please) for a fair compensation. Please let me know. Thanks for any guidance.
Click to expand...
Click to collapse
Confirm that you can send fastboot commands to the device. It's a prerequisite for flashing the original boot img back or doing a RAW flash if boot looped. That's the very first step you need sorted and confirmed. Sounds like you may not be in the right Fastboot mode. The RAW version doesn't matter too much as long as it's in line with your device version, you just need it to get back up and can upgrade normally to other versions.