Database Info

[Q] AT&T Bootloader Unlock

Hey, I'm kind of a noob here. Where do I get fastboot.exe from? Im stuck on step 11 in the "[UNLOCK] AT&T Bootloader Unlock Through HTC-Dev" thread

you need to download the android sdk, it has it in there as stated in the htcdev unlocking instructions

Thanks, I was able to get it to work once the one click unlock tool was posted.
Sent from my HTC One X using Tapatalk 2

Stupid questions but I can't seem to find simple answers:
a) do I need to be on a specific FW version or have a specific bootloader to unlock?
b) how do I tell what version I have?
c) does/can this get rid of the "tampered" on the bootloader screen?
d) does/can this give us full S-Off?

I'm assuming you're on the HTCDEV part because if you're not using the tool and you're asking this question you're doing it wrong.
that being said, it should come in the android SDK, if it doesn't then just copy the exe file out of the tool folder that you unzipped.
Edit, I see you already got it answered.
---------- Post added at 10:43 AM ---------- Previous post was at 10:39 AM ----------
xeper said:
Stupid questions but I can't seem to find simple answers:
a) do I need to be on a specific FW version or have a specific bootloader to unlock?
b) how do I tell what version I have?
c) does/can this get rid of the "tampered" on the bootloader screen?
d) does/can this give us full S-Off?
Click to expand...
Click to collapse
a) do I need to be on a specific FW version or have a specific bootloader to unlock?
--- i did it on 1.7, although I think 1.82 works
b) how do I tell what version I have?
--- settings > about phone > Software
c) does/can this get rid of the "tampered" on the bootloader screen?
----- absolutely not, look at the screenshots on the OP in the dev section
d) does/can this give us full S-Off?
-----no

HydroSkillet said:
I'm assuming you're on the HTCDEV part because if you're not using the tool and you're asking this question you're doing it wrong.
that being said, it should come in the android SDK, if it doesn't then just copy the exe file out of the tool folder that you unzipped.
Edit, I see you already got it answered.
---------- Post added at 10:43 AM ---------- Previous post was at 10:39 AM ----------
a) do I need to be on a specific FW version or have a specific bootloader to unlock?
--- i did it on 1.7, although I think 1.82 works
b) how do I tell what version I have?
--- settings > about phone > Software
c) does/can this get rid of the "tampered" on the bootloader screen?
----- absolutely not, look at the screenshots on the OP in the dev section
d) does/can this give us full S-Off?
-----no
Click to expand...
Click to collapse
Thanks for the info.
Another couple of dumb questions:
Will we ever be able to get rid of that "tampered" notice?
How does that notice effect me should my phone, say, fall and break its screen or have some other hardware-related failure? (I'm a klutz)
What does SuperCID mean and how does that effect me?

xeper said:
Thanks for the info.
Another couple of dumb questions:
Will we ever be able to get rid of that "tampered" notice?
How does that notice effect me should my phone, say, fall and break its screen or have some other hardware-related failure? (I'm a klutz)
What does SuperCID mean and how does that effect me?
Click to expand...
Click to collapse
Maybe, who knows on the "tampered" and yea you void your warranty so if you are afraid of hardware failure then don't do it, or but insurance on it. That's what I have, if I brick it cost me 100.00 rather than 600.00.

"Waiting for device"
Every attempt and different ways always brings me to that part. I have does the oneClick supercid program and I've even gone through the HTCDEV website 6 times now. after it reboots into boot loader mode and I direct it to the folder with the 3 files in it through cmd and I get to the final step to where it says "Waiting for device" trying to get the cid codes for my phone and nothing. I am at the end of my ropes of how to unlock codes. if anyone can help me or walk me through via text or video I would be so happy. I just want this thing finally unlocked and over with.

I take it your on this step?
11. Type "dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4" and hit enter. To test if it worked restart the phone into fastboot (type "adb reboot bootloader" and hit enter) and once the bootloader screen comes up type "fastboot oem readcid" and hit enter. It should read "11111111".
12. Next type "fastboot oem get_identifier_token" and hit enter. Leave that up on your screen and go to HTCdev.com. Follow the instructions from there. Choose "All other supported models" from the dropdown menu.
If so, Step 11 is kinda tricky worded after you type the command to reboot the device. Just don't even wait put the second line in "fastboot oem readcid" the batch file will wait for the phone. I hope this helps ya I had the same problem before And booted the phone back up and tried again but last time I just rebooted with the command then right after than put in the second command.

xeper said:
Thanks for the info.
Another couple of dumb questions:
Will we ever be able to get rid of that "tampered" notice?
How does that notice effect me should my phone, say, fall and break its screen or have some other hardware-related failure? (I'm a klutz)
What does SuperCID mean and how does that effect me?
Click to expand...
Click to collapse
Devs will find a way to remove tampered label once we find S-OFF. After the device has been "tampered", if your phone breaks and you send it to HTC warranty, they will not replace your phone if you have flashed a custom ROM on it. How they know you've flashed a custon ROM, I'm not sure.
SuperCID is the development CID designed to work on HTC phones. It allows you to unlock your bootloader through HTCDev.com. It also allows you to flash RUUs, because RUUs check CIDs on phones to determine whether the RUU is a valid ROM for your phone. However, it has been said this is hit/miss.
Don't take my exact word for it, use GOOGLE.COM.

I waited for the one-click tools, and I'm glad I did.

Forgot to mention
my Main computer is my iMac and I have a windows 7 laptop I switch to for my flashing/rooting etc... because I am not good with terminal or adb steps after a few seizures I've had recently. So shell stuff is completely useless to me. I can follow the steps on the briefmobile website then I have the HTCDEV account. but still at a lost.. for some reason.

I never got a 1111111 or whatever message
It just went straight to "Waiting for/on device" I tried again even attempted somewhat the hex edit way. but I never saw any "CW__111" or whatever in the file that I threw into HxE I think that was the hex program I used on my laptop. To frustrated to check in other room. I even kept looking at 210 section and nothing. So I'm not sure what is going on that won't let me unlock. Maybe I'll check youtube to see if there is a video on unlocking the bootloader.

hazmatik said:
It just went straight to "Waiting for/on device" I tried again even attempted somewhat the hex edit way. but I never saw any "CW__111" or whatever in the file that I threw into HxE I think that was the hex program I used on my laptop. To frustrated to check in other room. I even kept looking at 210 section and nothing. So I'm not sure what is going on that won't let me unlock. Maybe I'll check youtube to see if there is a video on unlocking the bootloader.
Click to expand...
Click to collapse
You should just use the one-click Super-CID tool in the Developers section, it's much faster and hassle free.

Thanks but that option never succeeded
I finally got it to unlock and get past that "Waiting for device issue" it seems even though I had my device plugged in and all the android and HTC drivers installed, it never registered that it could sense android 1.0 plugged in. so I had to manually right click and force it to install the drivers and it finally found device. low and behold it clicked and I got my email instantly right afterwards. So now I need how on installing CWM any ideas how to? be I am wanting to try out Team nocturnal's Rom for a little bit to see what it has to offer. Thanks for comment also by the way.

relock bootloader for warranty?

ive been having this overheating issue with the phone, basically at times it gets really hto while chargeing. so im pretty sure i will have to send it in and id like to know a way to relock the bootloader so i may do so

Hi,
BootLoader unlocked by giving Motorola all infos to receive a bootloader unlock code ???
Obviously they already know your Moto G is unlocked...

im pretty sure that the motorola tech support doesnt even check for that, theyre not very bright. i would just like to relock the bootloader just so that warning doesnt come up when i turn it on

shatheone said:
im pretty sure that the motorola tech support doesnt even check for that, theyre not very bright. i would just like to relock the bootloader just so that warning doesnt come up when i turn it on
Click to expand...
Click to collapse
Ok ok...so, after just 10 secs of research, here you go : http://forum.xda-developers.com/showthread.php?t=2597856
(flashing a bootlogo will do the job, if it's only for warning message...flash a Motorola original one...)

satanas17 said:
Ok ok...so, after just 10 secs of research, here you go : http://forum.xda-developers.com/showthread.php?t=2597856
(flashing a bootlogo will do the job, if it's only for warning message...flash a Motorola original one...)
Click to expand...
Click to collapse
im on lollipop, every tut ive seen was only for kitkat

shatheone said:
im on lollipop, every tut ive seen was only for kitkat
Click to expand...
Click to collapse
I don't think it matters. Just do:
fastboot oem lock

im getting an error, sst lock failure

i used the guide form the motorola faq thread, the one that satanas posted has broken links and hard to follow

shatheone said:
ive been having this overheating issue with the phone, basically at times it gets really hto while chargeing. so im pretty sure i will have to send it in and id like to know a way to relock the bootloader so i may do so
Click to expand...
Click to collapse
Did you fix that bootloader/ I also have same problem help me

yes i did relock using the faq, my moto g actually ran into a problem where my moto g wouldnt boot, so i had no problem restore the phone in the process

How to restore status code to 0 from status code 2

Plzzz help!!!!!!!!!!!!!!!!!!!!!!

you can't
K.V.K said:
Plzzz help!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
well my friend sry but you can't restore this code
most of devices like samsung,motorola etc they have.... lets say a key for the bootloader(is the door) and this key if you root your device
breaks and the half key stays inside the door hole to reminds you that the key is broken(the devicesis root/unlockbootloader).
so if you root any motorola device the code state goes
automatically 2 and stays like this,you can flash again the stock rom and relock the bootloader sure
but the code stays 2 for ever.
i hope to help you
moto g XT1541 stock rom 6.0.1 lockbootloader

bromoxitos said:
well my friend sry but you can't restore this code
most of devices like samsung,motorola etc they have.... lets say a key for the bootloader(is the door) and this key if you root your device
breaks and the half key stays inside the door hole to reminds you that the key is broken(the devicesis root/unlockbootloader).
so if you root any motorola device the code state goes
automatically 2 and stays like this,you can flash again the stock rom and relock the bootloader sure
but the code stays 2 for ever.
i hope to help you
moto g XT1541 stock rom 6.0.1 lockbootloader
Click to expand...
Click to collapse
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.

yeap
acejavelin said:
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
Click to expand...
Click to collapse
YEAAA we say the same think,but i use an othey way to say it.
i say in the end you can relock the bootloader (more or less) when i say this i mean that you put some partitions back in boot loader
so when you flash the stock rom you can take any ota update,but the main bootloader is unlock always.
i know that form my old moto g2gen, moto x2013!!!

bromoxitos said:
YEAAA we say the same think,but i use an othey way to say it.
i say in the end you can relock the bootloader (more or less) when i say this i mean that you put some partitions back in boot loader
so when you flash the stock rom you can take any ota update,but the main bootloader is unlock always.
i know that form my old moto g2gen, moto x2013!!!
Click to expand...
Click to collapse
You could relock the bootloader on older Motos, but not anymore... Actually, it can be relocked but it will never report as locked or relocked, it will always be reported as unlocked. I don't how to be more plain in describing this.
And yes, you can take an OTA when unlocked, as long as you have a stock ROM and recovery and your bootloader is the correct version for your ROM. If your bootload and ROM are out of sync (ie. you have a Marshmallow bootloader and a Lollipop ROM), if your bootloader and ROM are out of sync, you could potentially get into a hard bricked situation.

ohh!!
acejavelin said:
You could relock the bootloader on older Motos, but not anymore... Actually, it can be relocked but it will never report as locked or relocked, it will always be reported as unlocked. I don't how to be more plain in describing this.
And yes, you can take an OTA when unlocked, as long as you have a stock ROM and recovery and your bootloader is the correct version for your ROM. If your bootload and ROM are out of sync (ie. you have a Marshmallow bootloader and a Lollipop ROM), if your bootloader and ROM are out of sync, you could potentially get into a hard bricked situation.
Click to expand...
Click to collapse
not any more? damn....yea we say the same think,sry for my english,yea i khow what you talking about i brick my moto x like this!!! any way.
ty for the new info about bootloader.
you was 100%
were you a clear,thanks a lot,and i hope to help him

Once I sent my hard bricked phone to Motorola. I had unlocked the bootloader and done the stupid mistake of sideloading an older version and upgrading to a newer, but still older version. When it came back, it said it was Status Code 0.
Wonder how they did it.

yagyaxt1068 said:
Once I sent my hard bricked phone to Motorola. I had unlocked the bootloader and done the stupid mistake of sideloading an older version and upgrading to a newer, but still older version. When it came back, it said it was Status Code 0.
Wonder how they did it.
Click to expand...
Click to collapse
They flash the eMMC chip (internal storage chip) directly... If you could get the right image you could possibly do it yourself with a few hundred to thousand dollar investment in a proper JTAG flashing unit.
Key would be getting the right Image, this would be far more than just a normal stock fastboot image, and is probably generated on the fly per device due to differences in serial number, IMEI, etc. These types of images don't get leaked out.

acejavelin said:
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
Click to expand...
Click to collapse
ok so what if you have never root unlocked, did nothing but use as intended to be.. never trying to do anything to it. wtf would i have a code 2 status then? care to sum that up for me.. cause 100% my situation.

wiytboi said:
ok so what if you have never root unlocked, did nothing but use as intended to be.. never trying to do anything to it. wtf would i have a code 2 status then? care to sum that up for me.. cause 100% my situation.
Click to expand...
Click to collapse
You unlocked the bootloader... It doesn't matter if you actually changed anything else or not. Once it's been done, this status code can never go back to 0. If the status code is 2 and you didn't unlock the bootloader, then someone else did.

acejavelin said:
You unlocked the bootloader... It doesn't matter if you actually changed anything else or not. Once it's been done, this status code can never go back to 0. If the status code is 2 and you didn't unlock the bootloader, then someone else did.
Click to expand...
Click to collapse
No I didn't.. I don't even know how to.. I just found out about recovery mode.. Wait wait before i say that.. How do you unlock boot loader? Turning developer mode on? Going to recovery menu? I've never hard reset it.. Just soft or doing new device. You said it could work fine for a while then shirt out? Like guy I bought from did and then I bought used for couple years and then went tits up?

wiytboi said:
No I didn't.. I don't even know how to.. I just found out about recovery mode.. Wait wait before i say that.. How do you unlock boot loader? Turning developer mode on? Going to recovery menu? I've never hard reset it.. Just soft or doing new device. You said it could work fine for a while then shirt out? Like guy I bought from did and then I bought used for couple years and then went tits up?
Click to expand...
Click to collapse
You unlock the bootloader with a series of steps that includes submitting a code to Motorola and getting an unlock code back... Performing it forces a factory reset as well. It's not something you can do by accident.
The issue with Status Code 2 was that an official update could have detected that and refused to update properly or done something worse... That never happened.
If everything is working fine, the status being 2 isn't important, it just means the previous owners had unlocked the bootloader and likely rooted or otherwise modified the phone.

Unlock bootloader and flash twrp with Spflashtool

Hi guys i want to share with you this methode to unlock bootloader on Oreo for Nokia 3 go to this thread and requests the files from @bigrammy
This is the thread link : https://forum.xda-developers.com/no...-t3708129/post76293046?nocache=1#post76293046
Don't forget to hit thank's to him and me 12 thanks is not enough ??

This methode work with So Flashtool ?

I'm going to make SPflashTool working. I have some issue

Riadh300 said:
Hi guys i want to share with you this methode to unlock bootloader on Oreo for Nokia 3 go to this thread and requests the files from @bigrammy
This is the thread link : https://forum.xda-developers.com/no...-t3708129/post76293046?nocache=1#post76293046
Don't forget to hit thank's to him and me 12 thanks is not enough ?
Click to expand...
Click to collapse
Thanks for your enthusiasm but my method does not Unlock the bootloader so you should change your thread title.
As I told you I will open a thread when the method is fully tested by a few advanced user's who are testing it now and you will be given full credit for all your help.
I do not want to risk anyone bricking their phones due to rushing. Many none advanced users bricked their sony c4 phones by Not following my instructions so I need this to be 100% clear and fully tested I hope you understand.

I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !

Riadh300 said:
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Click to expand...
Click to collapse
If the bootloader was unlocked fully you would be able to use fastboot to flash the device but we cannot so the bootloader is still locked to all intense purposes.
The secure boot chain does appear to be broken so we can use SPFlashTool to flash and boot our TWRP recovery but the secure boot chain may still be working if you have never unlocked the bootloader before like on Android 7.x. This means TWRP may Not boot up for everyone. Like I said it needs to be fully tested.

bigrammy said:
If the bootloader was unlocked fully you would be able to use fastboot to flash the device but we cannot so the bootloader is still locked to all intense purposes.
The secure boot chain does appear to be broken so we can use SPFlashTool to flash and boot our TWRP recovery but the secure boot chain may still be working if you have never unlocked the bootloader before like on Android 7.x. This means TWRP may Not boot up for everyone. Like I said it needs to be fully tested.
Click to expand...
Click to collapse
Thanks for this informations ! ?

Riadh300 said:
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Click to expand...
Click to collapse
Actually, spflashtool bypasses the bootloader in this instance, so the bootloader is untouched and you still flash twrp
---------- Post added at 08:35 AM ---------- Previous post was at 08:02 AM ----------
bigrammy said:
I do not want to risk anyone bricking their phones due to rushing. Many none advanced users bricked their sony c4 phones by Not following my instructions so I need this to be 100% clear and fully tested I hope you understand.
Click to expand...
Click to collapse
Not to be pessimistic, but you do realise that even with all your precautions,people will still not read properly and will still brick their phones, no matter how many precautions you take. Even if you had an app that requires you to click one button to do everything,there are still people who will do it wrong. That said I think I know of one or 2 people in this Nokia 3 forum who were able to recover their phones using spflashtool AFTER the phone couldn't even be detected by their pc, even OST flashing was not possible .
Another thing is, all the Nokia 3 is last year's phone, I wonder how many experienced users will be buying the phone now, and experienced people are probably not the best way to get something 100% tested, because they know the right steps to take.
I think you should make your method public after you hear from SkaboXD

redweaver said:
Another thing is, all the Nokia 3 is last year's phone, I wonder how many experienced users will be buying the phone now, and experienced people are probably not the best way to get something 100% tested, because they know the right steps to take.
I think you should make your method public after you hear from SkaboXD
Click to expand...
Click to collapse
Sorry I replied to your PM before seeing this.
True there is no accounting for people but I don't want to get bogged down by noob's. If you and maybe SkaboXD would like to open a thread and manage it using the method then that would be fine by me as long as credit is give to Riadh300 the original tester and who informed me SPFlashTool still worked and myself of course.
Please read my PM about the bootloader condition as I recommend only previously unlocked devices try this for now until tested by Advanced user able to recover the device should anything go wrong (EFuse Blown).

bigrammy said:
Sorry I replied to your PM before seeing this.
True there is no accounting for people but I don't want to get bogged down by noob's. If you and maybe SkaboXD would like to open a thread and manage it using the method then that would be fine by me as long as credit is give to Riadh300 the original tester and who informed me SPFlashTool still worked and myself of course.
Please read my PM about the bootloader condition as I recommend only previously unlocked devices try this for now until tested by Advanced user able to recover the device should anything go wrong (EFuse Blown).
Click to expand...
Click to collapse
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post

redweaver said:
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
Click to expand...
Click to collapse
Before on 7.0 I flashed a TWRP I was working on via SPFlashTool bootloader locked and ended up in a never ending recovery bootloop which none advanced users may find difficult to get out of now this may of been because I screwed up the TWRP or more likely because the bootloader was Locked.
I did not try any other TWRP's until I was bootloader Unlocked and I have not had the recovery bootloop since.
Not sure about OST as SPFlashTool is by far the best tool for MediaTek devices and recovery of said devices remember the SoC manufacturer knows best and I only ever see problems when the OEM's try to move away from it like Sony did.
Happy for you to take the lead I am too busy in other threads to worry about it

bigrammy said:
Before on 7.0 I flashed a TWRP I was working on via SPFlashTool bootloader locked and ended up in a never ending recovery bootloop which none advanced users may find difficult to get out of now this may of been because I screwed up the TWRP or more likely because the bootloader was Locked.
I did not try any other TWRP's until I was bootloader Unlocked and I have not had the recovery bootloop since.
Not sure about OST as SPFlashTool is by far the best tool for MediaTek devices and recovery of said devices remember the SoC manufacturer knows best and I only ever see problems when the OEM's try to move away from it like Sony did.
Happy for you to take the lead I am too busy in other threads to worry about it
Click to expand...
Click to collapse
So how did you get your phone back anyway?

redweaver said:
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
Click to expand...
Click to collapse
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.

redweaver said:
So how did you get your phone back anyway?
Click to expand...
Click to collapse
:laugh: Sorry mate this is what I mean. I simply don't have the time to sit answering every single question as there is no short answers
I hope you understand.

SkaboXD said:
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
Click to expand...
Click to collapse
OK, one thing though, before flashing the recovery you might want to do a backup of the stock recovery if you don't already have one. That's what I did, so after I got root, flashed back my stock recovery. Magisk is the root manager ,
---------- Post added at 12:17 PM ---------- Previous post was at 12:12 PM ----------
bigrammy said:
:laugh: Sorry mate this is what I mean. I simply don't have the time to sit answering every single question as there is no short answers
I hope you understand.
Click to expand...
Click to collapse
oh you mean you went through hoops to get your phone back? I thought you would say you got a stock recovery somewhere and flashed using spflashtool or used the ost method. I didn't actually expect you to outline the steps you used. BTW, first time I flashed twrp AFTER unlocking bootloader, I got stuck in a recovery bootloop too. I had to flash my phone with OST then retry the process again.
One other thing, I think OST is actually a propriety software that is supposed to work for lots of phones, at least I know that users of other non mediatek Nokia phones also use it to recover their phones (with the corresponding stock images of course)

SkaboXD said:
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
Click to expand...
Click to collapse
Magisk hide allows you get OTA's see the Magisk thread and yes it will work on any android version.
@redweaver
I am glad you got out of the loop but your clearly a more advanced user hence why I ask you to test. :good:
The OST is very convoluted for use on MediaTek devices and is very unnecessary it also requires unnecessary FIH software to be installed on the phone to work properly.
They likely choose this method to work across different SoC's but it's not what MediaTek use SPFlashTool is MediaTeks own software.
EDIT: Sorry lost internet for a while then.
I continue: Good news is I do not think they will be able to remove SPFlashTool use as it's binary on device which lives on a none volatile area ram chip or radio chip and is loaded at the factory so I doubt it can be updated via a OTA. :fingers-crossed:
Sony actually replaced this and this is the only device I have been unable to recover and even Sony were replacing the boards of bricked devices but if they had left the Mediatek binary in there it would not of been a issue as SPFlashTool would of been able to recover them. :good:

guys, old thread, i know, different device, i know, but ive been in the dark and this is what most resembles my issue.
any hints would be appreciated, read all 2 pages, can you believe it? im a very average xda enthusiast.
worries out of the way, my sincere thanks beforehand follow.
issue
carrier doesnt get in the way
oem doesnt get in the way
oem unlock toggle, check, adb debugging, you and i know the drill, no driver/cable issues
cannot for the life of me unlock bootloader, this one would take the newer command, however i tried them all ive come accross to no avail
output encourages me to unlock first, howwever not a clue is given as to how to accomplish it. this isnt the flash a file type of unlocking, either, at least not oem provided. going nuts.
go ahead and feel free to issue "advanced" directions (meaning, like your voicemail, instead of "for voicemail configurations press 8" and just "configurations 8"
spreatrum, not mtk
x120c
came with oreo go, treble enabled per getprop
i dont know what else, please

Question Questions about firmware, bootloder

Hello, this is my first Motorola phone, please bear with me, I have a Motorola G62 5G phone and I have a question about the firmware, where can I download it?
And how to install them on this phone?
Does anyone have a guide?
Or it's on the forum because I've been looking and can't find anything.
I would also like to unlock the bootloader, how do I do that?
Is TWRP for this model?
Thank you in advance for your response.

Firmware: https://mirrors.lolinet.com/firmware/motorola/rhodec/official/
Installation: If you really need it I can post a guide. But I can't explain all the steps in a few words.
Bootloader unlock: https://en-us.support.motorola.com/app/standalone/bootloader/unlock-your-device-a

Thanks for your answer, I'll see if I can do that.

WoKoschekk said:
Firmware: https://mirrors.lolinet.com/firmware/motorola/rhodec/official/
Installation: If you really need it I can post a guide. But I can't explain all the steps in a few words.
Bootloader unlock: https://en-us.support.motorola.com/app/standalone/bootloader/unlock-your-device-a
Click to expand...
Click to collapse
Bootloader unlock will give the weird message on boot, right?

SoundDrill said:
Bootloader unlock will give the weird message on boot, right?
Click to expand...
Click to collapse
that's correct.

also you cannot just flash super image files by fastboot -flash super super.img - you also need to have it including block size =256M command or you will find that it will fail - i also have the Moto Fastboot version which you can just use the base command with out including block size - i have also found some issues with later versions of fastboot r32+ i think off the top of my head (4am in the morning and i will update shortly as about to re-flash my super partition)
apart from that no issues flashing or unlocking bootloader - bootloader you just need to submit the form - you should get a reply from moto fairly quickly - but if it is a new phone you will have to have it connected to a network for at least 7 days before it will actually allow you to unlock bootloader
bootloader - yes that is if you want to jailbreak/root your phone

SoundDrill said:
Bootloader unlock will give the weird message on boot, right?
Click to expand...
Click to collapse
I have 1 more question: which firmware file to download from this site? I doubt that all of them, because together they weigh over 48 gb

the easiest option I actually found to make sure downloading the correct firmware for phone as there are a wide variety of RHODEC models xt2223-x(x being a different constant) - was use the motorola RSA(rescue & smart assistance) software, just connect phone via adb and it downloads the firmware for you, though for a boot image file - i dont see there being major differences except if single/dual sim variants