Related
Hello, i have a big doubt about unlock my Mate 9.
I have read some guides but i'am confused, i will not lose the warranty and i see that with software dc-unlocker is possible relock the bootloader at original status, it is right? there are other softwares that do same job?
Sorry for my bad english.
thanks for help
Khris00 said:
Hello, i have a big doubt about unlock my Mate 9.
I have read some guides but i'am confused, i will not lose the warranty and i see that with software dc-unlocker is possible relock the bootloader at original status, it is right? there are other softwares that do same job?
Sorry for my bad english.
thanks for help
Click to expand...
Click to collapse
There's a difference between lock and relock.
Relock will say 're-locked' in the bootloader, and that's probably voiding warranty.
You can get it to say 'locked' by flashing official firmware, you have a few options here...
1. Firmware Finder
2. Flash update guide
3. Dload method (only for C636B136 and AL00C00B115)
4. FunkyHuawei (paid)
5. Dc unlocked (i think anyway, and paid)
ante0 said:
There's a difference between lock and relock.
Relock will say 're-locked' in the bootloader, and that's probably voiding warranty.
You can get it to say 'locked' by flashing official firmware, you have a few options here...
1. Firmware Finder
2. Flash update guide
3. Dload method (only for C636B136 and AL00C00B115)
4. FunkyHuawei (paid)
5. Dc unlocked (i think anyway, and paid)
Click to expand...
Click to collapse
thanks for answer
So is possible change the status just flashing the stock firmware? is so simple?
i need to do then unlock bootloader>>install modded recovery>>flash modded rom. For return to the stock firmware and bootloader locked what i need to do? i flash the stock firmaware but the twrp remain?
thanks
Khris00 said:
thanks for answer
So is possible change the status just flashing the stock firmware? is so simple?
i need to do then unlock bootloader>>install modded recovery>>flash modded rom. For return to the stock firmware and bootloader locked what i need to do? i flash the stock firmaware but the twrp remain?
thanks
Click to expand...
Click to collapse
No. When you flash stock firmware everything is back to stock. If there was a way to flash a modified update.zip with Twrp as recovery instead of stock recovery it would be possible. But as far as I know we can't yet. I've tried to repack using Huawei Update extractor but it doesn't want to, header mismatch. (this is on all extracted files, not just twrp)
The only reason to get locked bootloader would be if you needed to return the phone because of a software error. If it's hardware it should be replaced anyway.
ante0 said:
There's a difference between lock and relock.
Relock will say 're-locked' in the bootloader, and that's probably voiding warranty.
You can get it to say 'locked' by flashing official firmware, you have a few options here...
1. Firmware Finder
2. Flash update guide
3. Dload method (only for C636B136 and AL00C00B115)
4. FunkyHuawei (paid)
5. Dc unlocked (i think anyway, and paid)
Click to expand...
Click to collapse
ante0 said:
No. When you flash stock firmware everything is back to stock. If there was a way to flash a modified update.zip with Twrp as recovery instead of stock recovery it would be possible. But as far as I know we can't yet. I've tried to repack using Huawei Update extractor but it doesn't want to, header mismatch. (this is on all extracted files, not just twrp)
The only reason to get locked bootloader would be if you needed to return the phone because of a software error. If it's hardware it should be replaced anyway.
Click to expand...
Click to collapse
thanks for help Ante and sorry for my newbie questions, i will just flash one mod rom instead a stock i have now(B182) because i don't like emui, but if is possible when i'll go to sell i can back to stock condition and warranty Ok, i can do that?
thanks
Khris00 said:
thanks for help Ante and sorry for my newbie questions, i will just flash one mod rom instead a stock i have now(B182) because i don't like emui, but if is possible when i'll go to sell i can back to stock condition and warranty Ok, i can do that?
thanks
Click to expand...
Click to collapse
Yep. Flashing stock firmware will do that.
You won't get rid of emui though. We don't have AOSP so emui is always there...
ante0 said:
Yep. Flashing stock firmware will do that.
You won't get rid of emui though. We don't have AOSP so emui is always there...
Click to expand...
Click to collapse
you mean all modded roms are emui based?
Khris00 said:
you mean all modded roms are emui based?
Click to expand...
Click to collapse
Yes.
And there are only 2. RomAur and Ephemeral
ante0 said:
Yep. Flashing stock firmware will do that.
You won't get rid of emui though. We don't have AOSP so emui is always there...
Click to expand...
Click to collapse
ante0 said:
Yes.
And there are only 2. RomAur and Ephemeral
Click to expand...
Click to collapse
thanks again
ante0 said:
There's a difference between lock and relock.
Relock will say 're-locked' in the bootloader, and that's probably voiding warranty.
You can get it to say 'locked' by flashing official firmware, you have a few options here...
1. Firmware Finder
2. Flash update guide
3. Dload method (only for C636B136 and AL00C00B115)
4. FunkyHuawei (paid)
5. Dc unlocked (i think anyway, and paid)
Click to expand...
Click to collapse
sorry for my bad thing. But can i ask you help me this case:
i have Mate 9 Pro LON-L29C636C361 (lastest Oreo ) , but my bootloader is unlocked, and maybe not have stock recovery .
So, which method can flash again full rom C361 (3 file : update.zip, data full, hw...etc) and complete back to stock with locked bootloader???
I read somewhere about method LON-HWOTA, but it fail when flash TWRP step, because i am on Oero, so this method can not use in this my case . Can you show me another way ?
to relock bootloader on Android 8 (MUI8), only works if you have your CORRECT oeminfo.bin. make sure you backup yours before rebranding
1. just flash TWRP
2. make folder folder HWOTA8 on SD card
3. Download HWOTA8 and copy "hwota8_rebrand" to SDcard
4. Copy your oeminfo.bin file to HWOTA8 folder.. Make sure to rename your file to oeminfo.bin
5. Boot into TWRP and install from SDcard hwota8_rebrand
Done bootloader relocked
hi guys i'm brasilian and my english is pretty poor but lets try. i was flash 4.4.4 rom br retail. and i update via ota for lollipop.. and brick .. i search in forums here ... and i go it to put in boot loader without robot.. already try many ways to recovery my boot loader but always get error remote failure.. and already used 6.0.1 stock .. maybe i need to files atualy for this? i'm very sad my maxx is dead .. someone give me light .. help me fix this ... thank you guys
Is your bootloader locked or unlocked?
ChazzMatt said:
Is your bootloader locked or unlocked?
Click to expand...
Click to collapse
unlocked
kenedi jr said:
unlocked
Click to expand...
Click to collapse
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
ChazzMatt said:
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
Click to expand...
Click to collapse
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
kenedi jr said:
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
Click to expand...
Click to collapse
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
So I'm stuck on the bootloader. If I connect charger or pc it will already pro boot loader without the robot. I have already tried to pass stock 4.4.4 and 6.0 and more etc always from the failure remote failure in bootloader appears in the log something with gt bin downgrade
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
kenedi jr said:
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
Click to expand...
Click to collapse
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
I do not have twrp backup and I can not even install the recovery stock
kenedi jr said:
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
Click to expand...
Click to collapse
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that version to repair. Just reflash the entire full firmware.
Click to expand...
Click to collapse
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
thanks bro you saved me
kenedi jr said:
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
Click to expand...
Click to collapse
You can not flash any older gpt.bin files. You have to omit (leave out) that flash command.
Your gpt.bin file is 6.0.1, and you cannot downgrade. Even on 4.4.4, trying to accept the 5.0.2 OTA update is still older gpt.bin file in that OTA than your 6.0.1.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
i don't have link .. i will wanting you so
kenedi jr said:
i don't have link .. i will wanting you so
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?p=72846593
ChazzMatt said:
https://forum.xda-developers.com/showthread.php?p=72846593
Click to expand...
Click to collapse
I was a bit confused with this link which is the last one? I discovered because I am Brazilian and my English was developed only by playing
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
ChazzMatt said:
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
Click to expand...
Click to collapse
Face first you're a myth. I just passed gpt.bin and got the bootloader ... I'm very happy. Do I need to pass the entire rom ??
:good::laugh:
Hi! I'm really humbly sorry, I'm new to this stuff, so I have to ask you...
I have a Galaxy S8+ Duos (SM-GD955FD). I bricked it once or twice trying to root it. So I had to flash a sammobile.com ROM...
Now this is done, I have a successfully rooted phone with with the Baseband version G955FXU1AQH3 and the irritating "security notice" (since I was not able to install Magisk, and the NotifyClean app doesn't work either).
I would like to flash the latest Oreo and root it. I also heard good things about the Oreo ROM by alexega.
So: I'm on AQH3 rooted. What can I do?
Thank you for your patience.
If wou want to install stock ROM you must follow this instructions: https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-flash-crap-using-odin-t3748555. Bear in mind that if you install stock due to security issues you can't unlock OEM for 7 days after flashing (you must not reboot your phone for 170 hours).
If wou want to flash a custom rom you must have TWRP installed, move the zip rom to your SD card and just flash it from recovery. Make sure to format data before flashing.
josegon30 said:
If wou want to install stock ROM you must follow this instructions: https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-flash-crap-using-odin-t3748555. Bear in mind that if you install stock due to security issues you can't unlock OEM for 7 days after flashing (you must not reboot your phone for 170 hours).
If wou want to flash a custom rom you must have TWRP installed, move the zip rom to your SD card and just flash it from recovery. Make sure to format data before flashing.
Click to expand...
Click to collapse
Nice, thank you. So I have just flashed the thing with the sammobile.com ROM again (so, no root) and updated to the oroginal firmware Oreo following your link (I worked parallel).
I was just about to root Oreo and was googling for a way... But did I get you right? I should not reboot my phone for 170 hours now?!? So, no rooting until next week?!
Edit: I have developer options enabled and the "OEM unlock" switch is on (it says: "Bootloader is already unlocked.""). So... confusion...
andifla852 said:
Nice, thank you. So I have just flashed the thing with the sammobile.com ROM again (so, no root) and updated to the oroginal firmware Oreo following your link (I worked parallel).
I was just about to root Oreo and was googling for a way... But did I get you right? I should not reboot my phone for 170 hours now?!? So, no rooting until next week?!
Edit: I have developer options enabled and the "OEM unlock" switch is on (it says: "Bootloader is already unlocked.""). So... confusion...
Click to expand...
Click to collapse
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.
Just rooted the new Oreo ROM with TWRP. Works just fine, thank you.
So, what are the advantages of the Oreo ROM by alexega compared to XXU1CRAP?
josegon30 said:
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.
Click to expand...
Click to collapse
Hi Jose. I am with stock nogat. Not root. Any advice for flash stock oreo firmware?
Allrey know about odin. Im talking about unlock options, etc.
Thks
Juan from Argentina.
juange said:
Hi Jose. I am with stock nogat. Not root. Any advice for flash stock oreo firmware?
Allrey know about odin. Im talking about unlock options, etc.
Thks
Juan from Argentina.
Click to expand...
Click to collapse
Just follow the steps from the link in my previous repply. As it's an original software, it won't trip knox or void your warantee.
hi, does anybody knows how to install the oreo firmware using odin but without changing the csc I already have?
josegon30 said:
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.
Click to expand...
Click to collapse
Do you need a custom rom to not have the RMM lock anymore? A stock with BlackMesa's RMM START .zip is not right?
costafabiof said:
Do you need a custom rom to not have the RMM lock anymore? A stock with BlackMesa's RMM START .zip is not right?
Click to expand...
Click to collapse
There's no need to have a custom rom, if you flash the fix in stock RMM lock gets killed everytime.
josegon30 said:
There's no need to have a custom rom, if you flash the fix in stock RMM lock gets killed everytime.
Click to expand...
Click to collapse
Did not work.
I can not find out where I went wrong.
developer11 said:
Android.com.pl **** you
Little cocksucker
Click to expand...
Click to collapse
Translation?
costafabiof said:
Did not work.
I can not find out where I went wrong.
Click to expand...
Click to collapse
First you have to install OREO and wait 7 days without reseting your phone. After 170 hours, you get OEM unlock in developer options and you will be able to flasf TWRP. After flashing TWRP you flash RMM-State_Bypass_Mesa and that´s all.
josegon30 said:
First you have to install OREO and wait 7 days without reseting your phone. After 170 hours, you get OEM unlock in developer options and you will be able to flasf TWRP. After flashing TWRP you flash RMM-State_Bypass_Mesa and that´s all.
Click to expand...
Click to collapse
That did not work out. But thank you for your attention.
I sucessfully installed Orange Fox Recovery in my Redmi Note 7 Pro (violet). But then after that I wanted to go back to the stock rom so I flashed it with Mi Flash. The Rom which I flashed was Global Stable Fastboot Rom (Version 11.0.8.0) but after flashing an error appeared that the system has been destroyed. Then I tried to unlock my bootloader, that took place successfully and my phone booted but the bootloader was still unlocked, I want to lock my bootloader. But whenever I do this the System Gets Destroyed.
You probably have the Chinese version and are flashing the Indian rom. Try to flash the Chinese rom and lock the bootloader and see if it works.
Harsh Ahuja 2509 said:
I sucessfully installed Orange Fox Recovery in my Redmi Note 7 Pro (violet). But then after that I wanted to go back to the stock rom so I flashed it with Mi Flash. The Rom which I flashed was Global Stable Fastboot Rom (Version 11.0.8.0) but after flashing an error appeared that the system has been destroyed. Then I tried to unlock my bootloader, that took place successfully and my phone booted but the bootloader was still unlocked, I want to lock my bootloader. But whenever I do this the System Gets Destroyed.
Click to expand...
Click to collapse
U cant relock ur bootloader bruh ri8 now.
sourav24071999 said:
U cant relock ur bootloader bruh ri8 now.
Click to expand...
Click to collapse
When it can be relock again?
sourav24071999 said:
U cant relock ur bootloader bruh ri8 now.
Click to expand...
Click to collapse
Then when can I relock my bootloader again? Because I want to lock my bootloader
dark3578 said:
You probably have the Chinese version and are flashing the Indian rom. Try to flash the Chinese rom and lock the bootloader and see if it works.
Click to expand...
Click to collapse
No, I never had the China Version it is the Indian Version. Can u send me the link of the Chinese Rom
Harsh Ahuja 2509 said:
Then when can I relock my bootloader again? Because I want to lock my bootloader
Click to expand...
Click to collapse
Let's see.. no info yet
I am also having the same issue. I have tried multiple methods. I flashed Chinese rom, and then tried relocking the bootloader. It did not work.
I also tried flashing MIUI 10, and after flashing the fastboot rom of MIUI, I tried relocking bootloader. It did not work as well.
I want to relock my bootloader.
After unlocking bootloader I am facing just one issue, that is, my internet goes off (volte signal + internet) while receiving an incoming call. While it does not goes off and internet works fine when making outgoing calls. Are you also facing this issue? I am using Airtel.
Also, can someone please help us out?
I have did same it will work for me with unlocked bootloader and got a little issue with accessibility player in youtube
Not a big deal ?
Hi,
i want to go back to stock rom and re-lock the bootloader.
I tried to flash the fastboot rom "lmi_eea_global_images_V12.5.1.0.RJKEUXM" via MiFlash (2018.5.28.0), but it failed because of anti rollback.
Current installed rom is xiaomi.eu weekly 21.7.28 (miui 12.6). TWRP is also installed.
Whats the right way to get back to stock?
Thanks
Spillunke said:
Hi,
i want to go back to stock rom and re-lock the bootloader.
I tried to flash the fastboot rom "lmi_eea_global_images_V12.5.1.0.RJKEUXM" via MiFlash (2018.5.28.0), but it failed because of anti rollback.
Current installed rom is xiaomi.eu weekly 21.7.28 (miui 12.6). TWRP is also installed.
Whats the right way to get back to stock?
Thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/guide-use-xiaomi-flash-tool.4262425/
@NOSS8
perfect, thanks!