Database Info

[Rom][NXH20B] Huawei Watch 2 BT LEO-B09/LEO-BX9 Global Fastboot [Factory Images]

Finally The wait is over
For all of you outside waiting for Global Firmware ROM... here it is:
I have tried it in a LEO-BX9 working flawless... last version received with chinese firmware by OTA was NXH19R
As previously done text is copied from giangishanghai as most are applicable. Thanks @giangishanghai for all the help and the patience :angel
- Make sure you have ADB activated on watch and all files needed on your pc (there are plenty of guides on xda so please search and read it if needed).
- Download 7z file from here : https://mega.nz/#!ozB12QrD
Decription Key
!U6_ZwGwPNUNj3P0PCfpsDtVoGpPG_x1csvR8I1ECOqU
-Edit: You will find 6 .img files:
bootloader, boot, cache, recovery, system, userdata.
-EDIT: In this link you will find whole Recovery software and images if needed:
https://mega.nz/#!YiZkjKyR
Decription Key
!vlUDAZz3mEJsSOpKYgbX5YaITUN59uL3YaVRSOtpVcU
-Edit: Before going to Bootloader, make sure ADB is working and your watch is recognized properly:
Run
Code:
adb devices
Result should be your Watch ID and the word "device" (unathorized or anything else will not work, when unathorized appears make sure to check your Watch for a prompt to authorize something, as it is in Chinese, choose the option with more characters - third one as I remember-)
-Boot the watch into bootloader mode
shut down the watch, press the power button and quickly press twice when the first vibration finished.
-Use the following commands one by one:
(DO NOT flash the bootloader.img)
IMPORTANT!!!: Make sure to run ALL commands below, from the ADB folder, where you have to previously copied all 6 *.IMG files, otherwise you will receive a lot of errors.
For Example if your ADB folder is in C:\adb, the command prompt should be in "C:\adb" so you make a DOS dir command and you see all 6 *.img files plus some ADB files
Then start with following commands one by one in exact order....
fastboot oem unlock (no needed if you already unlock your watch)
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
DONE!!
EDIT: ****PLEASE READ IF YOU EXPERIENCE ANY TOUCH ISSUES******Thanks @mcdull
I were able to flash the rom without any issues. HOWEVER...
Originally I suggested NOT to temper with the bootloader so that we can keep the very low level of the device untouched to prevent hard bricking.
But I experienced inaccurate touch screen after applying the ROM. And then I finally convinced myself to flash the bootloader to see if it can fix it.
It is now confirmed that flashing the bootloader will NOT change the model number. So the device model is determined by its hardware. And I can check the FCC of Leo-bx9 in official website, so there must be somewhere in the world selling this BX9 with global rom.
What's more important is that the touch screen is now working perfectly. All part of the screen is now touchable and accurate.
All in all, if you have any touch issue, you may be able to resolve it by flashing the bootloader. Bare in mind that Huawei can be told that you have tempered the bootloader if they dig deep. But I am prepared to give up the warranty for a Global Rom.
Click to expand...
Click to collapse
*****END OF EDIT******
After all this steps your watch reboot and the first thing you will see is a message in English, then you can choose the language you want.
Please don't forget to say thanks and also to @giangishanghai who was really really helpful on remote assistance and also @mcdull who was always promptly replying to help the community

Thank @dr_chch for your great contribution.
I were able to flash the rom without any issues. HOWEVER...
Originally I suggested NOT to temper with the bootloader so that we can keep the very low level of the device untouched to prevent hard bricking.
But I experienced inaccurate touch screen after applying the ROM. And then I finally convinced myself to flash the bootloader to see if it can fix it.
It is now confirmed that flashing the bootloader will NOT change the model number. So the device model is determined by its hardware. And I can check the FCC of Leo-bx9 in official website, so there must be somewhere in the world selling this BX9 with global rom.
What's more important is that the touch screen is now working perfectly. All part of the screen is now touchable and accurate.
All in all, if you have any touch issue, you may be able to resolve it by flashing the bootloader. Bare in mind that Huawei can be told that you have tempered the bootloader if they dig deep. But I am prepared to give up the warranty for a Global Rom.
@dr_chch, grateful if you could include this in your tutorial. Thanks a lot for your contribution that making all these possible.

thank you. It was a pleasure for me to help.
sorry but I am trying to hit thanks button since two days ago with no result.... dunno why...
regards

mcdull said:
thank @dr_chch for your great contribution.
I were able to flash the rom without any issues. However...
Originally i suggested not to temper with the bootloader so that we can keep the very low level of the device untouched to prevent hard bricking.
But i experienced inaccurate touch screen after applying the rom. And then i finally convinced myself to flash the bootloader to see if it can fix it.
It is now confirmed that flashing the bootloader will not change the model number. So the device model is determined by its hardware. And i can check the fcc of leo-bx9 in official website, so there must be somewhere in the world selling this bx9 with global rom.
What's more important is that the touch screen is now working perfectly. All part of the screen is now touchable and accurate.
All in all, if you have any touch issue, you may be able to resolve it by flashing the bootloader. Bare in mind that huawei can be told that you have tempered the bootloader if they dig deep. But i am prepared to give up the warranty for a global rom.
@dr_chch, grateful if you could include this in your tutorial. Thanks a lot for your contribution that making all these possible.
Click to expand...
Click to collapse
done updated thanks!!

Thx all you guys

Will try this out today
I have a LEO-BX9 currently running the Chinese ROM version. I've downloaded the new files. I will try this out later today and post my results as well.
A real huge thanks for getting the ROM and posting the steps. I've been following the forum for a month and it's impressive to see how you guys kept at it until you reached the finish line! Keep up the good work bro's! @giangishanghai and @dr_chch - You guys rock!
Edit: Works flawlessly! Just follow the instructions to the letter. Shiny new English ROM purring like a kitten!

Big thanks, I have the chinese LEO-BX9, works perfectly. the installation only takes less than 2-3 mins.

Will flashing bootloader and re-locking get Android Pay working?

mrgnarchr said:
Will flashing bootloader and re-locking get Android Pay working?
Click to expand...
Click to collapse
hello,
yes it should work.
regards

Hi guys
I flashed the below ROM on my BT version
Leo-L09S 2.1.7_Firmware_general_05014AHH from (Guide: How to flash english firmware to chinese huawei watch 2 sim card variant) on my BT version by mistake....
The watch does not boot at all.. No response when I press the power button cant go into fastboot or anything... its completely dead... Please let me know what can be done...

dr_chch said:
Finally The wait is over
For all of you outside waiting for Global Firmware ROM... here it is:
I have tried it in a LEO-BX9 working flawless... last version received with chinese firmware by OTA was NXH19……
Click to expand...
Click to collapse
Thx for all you do .May I know would you like 2 share a Chinese firmware?
Regards

Done updated,google fit is awesome.Thx dr_chch.

I'm trying to do this, but my Huawei Watch 2 is being recognized as a MTP device and wont appear under the device list when I type "abd devices". How do I fix this? Thanks.
---------- Post added at 02:44 PM ---------- Previous post was at 02:21 PM ----------
So, somehow I made it work. But I didn't do the commands properly and now the watch seems to be bricked. Is there any way I can bring it back into fastboot mode so I can flash the image correctly?
---------- Post added at 02:53 PM ---------- Previous post was at 02:44 PM ----------
Managed to get into fastboot and it seems to work fine. Thank you

What is the difference between this and stock?

devilsden said:
Hi guys
I flashed the below ROM on my BT version
Leo-L09S 2.1.7_Firmware_general_05014AHH from (Guide: How to flash english firmware to chinese huawei watch 2 sim card variant) on my BT version by mistake....
The watch does not boot at all.. No response when I press the power button cant go into fastboot or anything... its completely dead... Please let me know what can be done...
Click to expand...
Click to collapse
I have the same problem :crying: , anyone can help ?? thank so much

Black screen after flash bootloader
Hi Friends,
I tried the installed the first 6 file but it stuck at fastboot page, I restart several times but still not help.
After bootup it goes to fastboot mode.
then I tried to flash the bootloader to see whether it could help, but it turns to black screen.
totally no response , only a black screen, no vibrate holding the power button.
please help !!
thank you for any advice!

[Rom][NWD1.170711.002] Huawei Watch 2 BT LEO-B09 Chinese Fastboot [Factory Images]
I finally have uploaded the Chinese version of the Factory Images, and here is the link:
https://www.jianguoyun.com/p/DRcrvN0Q3O-HBhjeiTQ (The file is currently under transmission by the time of this post. It should be available within hours.)
On download completion, find the .exe file in the zip archive and open it with any compressed file manager, where you will see several .img images. Flash them right onto your watch following the instructions on https://forum.xda-developers.com/wa...09-leo-bx9-t3616779/post72542838#post72542838 with ADB and FASTBOOT tools.
It works quite perfectly on my watch. Nevertheless, I am not responsible for any possible damages.
Go check it out! @dr_chch

Yonghao Liu said:
I finally have uploaded the Chinese version of the Factory Images, and here is the link:
https://www.jianguoyun.com/p/DRcrvN0Q3O-HBhjeiTQ (The file is currently under transmission by the time of this post. It should be available within hours.)
On download completion, find the .exe file in the zip archive and open it with any compressed file manager, where you will see several .img images. Flash them right onto your watch following the instructions on https://forum.xda-developers.com/wa...09-leo-bx9-t3616779/post72542838#post72542838 with ADB and FASTBOOT tools.
It works quite perfectly on my watch. Nevertheless, I am not responsible for any possible damages.
Go check it out! @dr_chch
Click to expand...
Click to collapse
Hi, I flash your images, everything works normally expect notify. When notify appears on phone, there is no vibrate and no sound on wear, just notify card shown silently.
My wear had global version system, but Google Map gave a wrong location, so I try China version.
I use light flow to test notify. When I open option "silence phone while wearing watch", phone doesn't sound too but still vibrate. If I close this option, phone sound and vibrate. But watch always doesn't action.

Yonghao Liu said:
I finally have uploaded the Chinese version of the Factory Images, and here is the link:
https://www.jianguoyun.com/p/DRcrvN0Q3O-HBhjeiTQ (The file is currently under transmission by the time of this post. It should be available within hours.)
On download completion, find the .exe file in the zip archive and open it with any compressed file manager, where you will see several .img images. Flash them right onto your watch following the instructions on https://forum.xda-developers.com/wa...09-leo-bx9-t3616779/post72542838#post72542838 with ADB and FASTBOOT tools.
It works quite perfectly on my watch. Nevertheless, I am not responsible for any possible damages.
Go check it out! @dr_chch
Click to expand...
Click to collapse
Hi friend!I'm a Chinese Huawei Watch 2 User,do you have the LTE version Chinese Factory Image?I spend a lot of time to find it.But I falied.By the way,Are the LEO-B09S and the LEO-DLXX the same model?My device is LEO-DLXX,if I got a LEO-B09S Chinese Factory Image,can I flash it?
Thanks a lot!

CallMeEggLeader said:
Hi friend!I'm a Chinese Huawei Watch 2 User,do you have the LTE version Chinese Factory Image?I spend a lot of time to find it.But I falied.By the way,Are the LEO-B09S and the LEO-DLXX the same model?My device is LEO-DLXX,if I got a LEO-B09S Chinese Factory Image,can I flash it?
Thanks a lot!
Click to expand...
Click to collapse
I tried the international image on a LEO-DLXX, works fine, but without the SIM capabilities (4G, calls and etc), and during the boot there is a message about being using a different operating system. I suppose you'd get the same with the Chinese version.

[Recovery] TWRP for the Nubia Z18(NX606J)

Hey,
youyim123 recently made his TWRP build available that I was trying to compile myself. So without further ado, here is a more or less working TWRP for the Nubia Z18 with instructions of how to install it.
Link to recovery.img
How to install it:
Boot into bootloader using
Code:
adb reboot bootloader
Unlock the bootloader using
Code:
fastboot oem nubia_unlock NUBIA_NX606J
Flash the recovery.img using
Code:
fastboot flash recovery recovery.img
IMPORTANT! Navigate to "reboot to emergency recovery mode". Do not use
Code:
fastboot reboot recovery
as it might not work correctly!
I found disconnecting the device from USB to be more reliable, so do that for stability
If it gets stuck, repeat steps 1 and 4. No need to reflash, just be patient
Language will be Chinese, so change that by using the settings button (second from below on the right)
That's it, you have a working TWRP now Enjoy!
EDIT: DO NOT TRY FLASHING MAGISK AS IT WILL DAMAGE DM-VERITY AND YOU'LL HAVE TO BOOT RESCUE YOUR DEVICE! YOU CAN USE MY recovery script in the bloat remover thread to fix your device
In case you get stuck in a bootloop, repeat the installation guide, then use
Code:
adb push stock.zip /data/media/0
and reflash stock firmware as a last resort until a custom ROM is available.
All credit for this goes to youyim123 and his amazing work! I know he struggled releasing this because his work is often used or redirected without his consent or giving him credit, so I'm grateful he decided to release it.

*reserved*

Can i use this to flash Gapps

aqblwd said:
Can i use this to flash Gapps
Click to expand...
Click to collapse
In theory, yes. In practice, it somehow doesn't give me any GApps when flashing it. I'm trying to cooperate with the OpenGapps team to fix this.

any update info for flashing gapps ? i really want to use my nubia z18 with google environment on it. tks

shevaman7 said:
any update info for flashing gapps ? i really want to use my nubia z18 with google environment on it. tks
Click to expand...
Click to collapse
None yet. I'd say community involvement isn't exactly one of the OpenGapps team's good points
See the Gitter thread for tracking updates here: https://gitter.im/opengapps/general
If you know of any other way to contact them, feel free to do so and send them the logs I attached in the gitter post (same username as here)

shevaman7 said:
any update info for flashing gapps ? i really want to use my nubia z18 with google environment on it. tks
Click to expand...
Click to collapse
You can use google xspace

elnas1369 said:
You can use google xspace
Click to expand...
Click to collapse
EDIT: Okay I tried the app and it's doing something that looks like installing play services? @elnas1369 would you mind explaining what you did in detail? Because most of us probably can't speak chinese and it's not intuitive unfortunately

curtisy said:
EDIT: Okay I tried the app and it's doing something that looks like installing play services? @elnas1369 would you mind explaining what you did in detail? Because most of us probably can't speak chinese and it's not intuitive unfortunately
Click to expand...
Click to collapse
I did it on my Nubia X and it works pretty good, you just have to follow the steps, i've found some tutos on youtube it's very easy. You can search for google xspace installing or something like that

curtisy said:
Hey,
youyim123 recently made his TWRP build available that I was trying to compile myself. So without further ado, here is a more or less working TWRP for the Nubia Z18 with instructions of how to install it.
Link to recovery.img
How to install it:
Boot into bootloader using
Code:
adb reboot bootloader
Unlock the bootloader using
Code:
fastboot oem nubia_unlock NUBIA_NX606J
Flash the recovery.img using
Code:
fastboot flash recovery recovery.img
IMPORTANT! Navigate to "reboot to emergency recovery mode". Do not use
Code:
fastboot reboot recovery
as it might not work correctly!
I found disconnecting the device from USB to be more reliable, so do that for stability
If it gets stuck, repeat steps 1 and 4. No need to reflash, just be patient
Language will be Chinese, so change that by using the settings button (second from below on the right)
That's it, you have a working TWRP now Enjoy!
EDIT: DO NOT TRY FLASHING MAGISK AS IT WILL DAMAGE DM-VERITY AND YOU'LL HAVE TO BOOT RESCUE YOUR DEVICE! YOU CAN USE MY recovery script in the bloat remover thread to fix your device
In case you get stuck in a bootloop, repeat the installation guide, then use
Code:
adb push stock.zip /data/media/0
and reflash stock firmware as a last resort until a custom ROM is available.
All credit for this goes to youyim123 and his amazing work! I know he struggled releasing this because his work is often used or redirected without his consent or giving him credit, so I'm grateful he decided to release it.
Click to expand...
Click to collapse
any news update about stable TWRP for Z18. I have Z18, a very beautiful and strong device

md07 said:
any news update about stable TWRP for Z18. I have Z18, a very beautiful and strong device
Click to expand...
Click to collapse
It is stable. Just make sure to unplug your phone after flashing it as otherwise it will probably get stuck after a few seconds. If you need to have your device connected to your pc, do the following:
Start adb sideload in TWRP, connect your phone to your pc, stop sideload. That way you have a working connection with adb again
Hope this helps!

curtisy said:
It is stable. Just make sure to unplug your phone after flashing it as otherwise it will probably get stuck after a few seconds. If you need to have your device connected to your pc, do the following:
Start adb sideload in TWRP, connect your phone to your pc, stop sideload. That way you have a working connection with adb again
Hope this helps!
Click to expand...
Click to collapse
i read somewhere in Nubia forums (chinese language), some dev is going to release TWRP for Z18, but it need poll to decide.
So that, i dont know this version on XDA is official or unofficial ? And as you said, if it is stable, so can i flash Gaap package to get full Goolge and service for Z18? have you tried ?

Already try few weeks ago, not working...!
The only temperary solution is "Google Space", or just wait for the global version release
As one Dev which working on LOS fot this machine point out that Lineage is very hard to compile since there's no other Dev help him, the System is block by something call AVB2...pretty ironic as this twrp not even let us using Magisk at all!
md07 said:
i read somewhere in Nubia forums (chinese language), some dev is going to release TWRP for Z18, but it need poll to decide.
So that, i dont know this version on XDA is official or unofficial ? And as you said, if it is stable, so can i flash Gaap package to get full Goolge and service for Z18? have you tried ?
Click to expand...
Click to collapse

sky104hk said:
Already try few weeks ago, not working...!
The only temperary solution is "Google Space", or just wait for the global version release
As one Dev which working on LOS fot this machine point out that Lineage is very hard to compile since there's no other Dev help him, the System is block by something call AVB2...pretty ironic as this twrp not even let us using Magisk at all!
Click to expand...
Click to collapse
I tried Gplay space. But all app installed from there seem work slowly and not appear on home screen (must go Gplay space and run app)

md07 said:
i read somewhere in Nubia forums (chinese language), some dev is going to release TWRP for Z18, but it need poll to decide.
So that, i dont know this version on XDA is official or unofficial ? And as you said, if it is stable, so can i flash Gaap package to get full Goolge and service for Z18? have you tried ?
Click to expand...
Click to collapse
Please read the first post precisely and then the post in the nubia forum again. Youyim is the guy who made the poll and he made it public. I simply brought it to a wider audience and link to his official GitHub for the img.
You cannot flash Gapps with this because it errors. I said so a couple of times before and would appreciate a bit of effort reading before asking. You probably spent more time on writing this than you would've reading the first three post entries here, disregarding the fact that I'm trying to reply in detail. It's all in the first post, please read that before asking next time..
To sum up:
- It's the "official" TWRP from youyim, all credit goes to him
- You can not install Gapps with this, I haven't found a resolution for this but am working on an alternative. See my other thread or post #3 here

sky104hk said:
Already try few weeks ago, not working...!
The only temperary solution is "Google Space", or just wait for the global version release
As one Dev which working on LOS fot this machine point out that Lineage is very hard to compile since there's no other Dev help him, the System is block by something call AVB2...pretty ironic as this twrp not even let us using Magisk at all!
Click to expand...
Click to collapse
It's the same dev I'm the guy working on LineageOS as well and yes AVB2 (Basically think of it as Android's answer to secure boot on Computers) is a pain in the a** to deal with. Compiling itself is rather easy compared to the pain that comes after it, it's just killing lots of time and I unfortunately don't have that with a full time job. That's why I tried getting more people involved but (again) failed apparently.
TWRP doesn't have anything to do with Magisk either. Magisk is modifying the boot partition as far as I'm aware (don't hate me topjohnwu) and it relies on either no AVB/DM-Verity or a flag that doesn't work here either. TWRP in contrast just modifies/overrides the boot partition and is (mostly) used to flash many things including Magisk.

I think Z18 not have a global version, so we'll never see international firmware for this product. The only way I hope is some one or some dev support official method for install Google. And hope good news come soon.
Thanks all!

md07 said:
I think Z18 not have a global version, so we'll never see international firmware for this product. The only way I hope is some one or some dev support official method for install Google. And hope good news come soon.
Thanks all!
Click to expand...
Click to collapse
Isn't a global release coming in like 2 weeks or something? At least that's what I read last time I checked
I can tell you an official method. Root your phone and rewrite google services to system. Otherwise wait until developers can take a look at Rom building like I do now or even better, get involved. Being a one man show isn't helping the cause even if you have a couple spectators because it makes you feel more or less like a monkey in a cage

curtisy said:
Isn't a global release coming in like 2 weeks or something? At least that's what I read last time I checked
I can tell you an official method. Root your phone and rewrite google services to system. Otherwise wait until developers can take a look at Rom building like I do now or even better, get involved. Being a one man show isn't helping the cause even if you have a couple spectators because it makes you feel more or less like a monkey in a cage
Click to expand...
Click to collapse
Where did you read about global version Z18??? I checked only on Nubia website, in some global region (like India...) they are only going to release global Red Magic Mars.
I know method get Google and service by rooted and I read in Nubia forums they released tool to root current Version Z18, but I can not download

md07 said:
Where did you read about global version Z18??? I checked only on Nubia website, in some global region (like India...) they are only going to release global Red Magic Mars.
I know method get Google and service by rooted and I read in Nubia forums they released tool to root current Version Z18, but I can not download
Click to expand...
Click to collapse
https://www.gadgetsnow.com/mobile-phones/Nubia-Z18 for instance. India isn't global lol. They mostly just buy masses of phones and then resell. And yeah I can understand they won't release a global version anytime soon. The phone is great but looking at the source code, it's horrible. I even had to submit a patch so they get their build fixed!
As for the download, try the second one. Baidu is blocking anything non China by now afaik. It will also be included in the LineageOS ROM whenever I'll get that done..

AIO Alcatel ToolKit- Windows/Linux

AIO Alcatel ToolKit
Built By: PizzaG & LgPWN'd
Build Version Paid: 2.14
Build Version Free: 2.03
Paid Features
All Options 99.9% Fully Automated
Install ADB/Fastboot Drivers to PC
Free Features
Telegram + Download Link​https://t.me/Android_General_Chat​

New Website Live: 12-20-2019
Website Updated: 12-26-2019
AIO Software Versions Updated: 12-26-2019
AIO Features Added: 12-26-2019

..

Wowzers,
Thread been up since 16th October 2019 and nobody bothered with 1 post?
Well... Good work Broski we got the best AIO tool for Alcatel Tetra around

Question is there an updated site or something for download? When click on link just gives dns error.

thugporn* said:
Question is there an updated site or something for download? When click on link just gives dns error.
Click to expand...
Click to collapse
I just checked it, all links are working fine here....

still getting error message.
PizzaG said:
I just checked it, all links are working fine here....
Click to expand...
Click to collapse

thugporn* said:
Click to expand...
Click to collapse
please share both the ERROR and the Link your trying to use
otherwise i can't help you.
I am 1 of the site dev's

Download link doesn't exist.

Dns error
Also getting link error
Link to image. https://ibb.co/qdVzXzr
https: // ibb.co / qdVzXzr
Added spaces to link in hopes of it coming through so you can see the error

SORRY FOR THE CONFUSION OUR SERVER HAS MOVED LOCATIONS....
For current links to our website our notes our Roms and our Tools AIO included plz check our Telegram Group it stays up-to-date.
https://t.me/Android_General_Chat

@PizzaG - Question for you - I see in one screenshot that there is an option, "enable fastboot". I have an A501DL, and currently using mtk-su with Magisk successfully, but no access to fastboot to unlock bl, and no chance of r/w access in system otherwise. Could this help me get into fastboot, and, if so, is there some way I could try to just make that happen, without necessarily using the program?
Here's more detail, if you want :
https://forum.xda-developers.com/showthread.php?p=81780645#post81780645
https://forum.xda-developers.com/showthread.php?p=81911519#post81911519
Thanks

levone1 said:
@PizzaG - Question for you - I see in one screenshot that there is an option, "enable fastboot". I have an A501DL, and currently using mtk-su with Magisk successfully, but no access to fastboot to unlock bl, and no chance of r/w access in system otherwise. Could this help me get into fastboot, and, if so, is there some way I could try to just make that happen, without necessarily using the program?
Here's more detail, if you want :
https://forum.xda-developers.com/showthread.php?p=81780645#post81780645
https://forum.xda-developers.com/showthread.php?p=81911519#post81911519
Thanks
Click to expand...
Click to collapse
You have to have the fastboot lk to unlock bootloader. Unless you can find that, not gonna happen.
PS- 1 option that comes to mind is trying to flash a bad boot to the device with sugar and then hope and pray that it reboots into fastboot. It's my understanding that fastboot is still there, just the commands to get to it have been removed. I was able to recovery from a bad brick on my device by flashing a bad boot to it and it rebooted to fastboot. Get ahold of me on Telegram if you'd like to discuss itmore

PizzaG said:
You have to have the fastboot lk to unlock bootloader. Unless you can find that, not gonna happen.
PS- 1 option that comes to mind is trying to flash a bad boot to the device with sugar and then hope and pray that it reboots into fastboot. It's my understanding that fastboot is still there, just the commands to get to it have been removed. I was able to recovery from a bad brick on my device by flashing a bad boot to it and it rebooted to fastboot. Get ahold of me on Telegram if you'd like to discuss itmore
Click to expand...
Click to collapse
Thanks for the reply. I'm new to mtk. I guess by 'lk' you mean little kernel. From the searching I did, it seems a bit over my head. Is there a way to get that?
I'll look into Sugar at some point. Back on my Xperia XC running Sailfish at the moment..

levone1 said:
Thanks for the reply. I'm new to mtk. I guess by 'lk' you mean little kernel. From the searching I did, it seems a bit over my head. Is there a way to get that?
I'll look into Sugar at some point. Back on my Xperia XC running Sailfish at the moment..
Click to expand...
Click to collapse
Yes, Little Kernel on MTK is where fastboot lives. I have a couple ideas you could try to force the device into fastboot . Our fastboot lk's we were lucky enough to find in an old dump. Best bet is to scour the net looking for the oldest dump you can and pray the fastboot lk is enabled. You can find me here live: https://t.me/Android_General_Chat

This Should Be Updated Into the OP But @PizzaG will have to do that as he has ownership of the thread.
Group on Telegram listed in OP is still the place to find Us and others who can help you out.
Our Site Is HERE:
https://a-team-solutions-downloads.myddns.rocks/Site
and a direct shortcut to the Free Version Of the Tool Is HERE:
https://a-team-solutions-downloads.myddns.rocks/Free/AIO-ToolKit/
It's available in several flavors.
windows and linux on the free.
It was still functioning for the basics like it alwas has last i checked.
However the Paid version does have some neat perks
Hope This Helps everyone
sorry for my late reply as i've said elsewhere i am very busy and don't see XDA much.
If needed i can be found on the telegram group in OP.
LgPWNd

How to root Ulefone Power Armor 13! Now with TRP recovery and Magisk included

Hello,
Below is a guide on how to root Ulefone Power Armor 13 using Magisk, changing/restoring IMEI etc.
Before you continue, I take no responsibility for any bricked devices.
*Note: Before you begin, make sure you install the latest software update. If you already have data on the phone and apps. make sure you make a backup with Titanium backup or other similar apps. This process will reset the phone. ALL USER DATA WILL BE LOST!!!!
Gain access to developer options.
Go to Settings - About phone. Press repeatedly on Build Number until the phone will show a message You are now a developer or something similar.
Navigate to System - Advanced - Developer options.
Find OEM unlocking and turn on together with USB debugging. Turn off Verify apps over USB (very useful if you use Titanium Backup to restore apps).
2. Rooting boot stock image with Magisk
*Note: when connecting the phone via USB the first time, make sure you allow (click ok and check the box) to always always allow USB debugging when connecting to your PC. You need this for later steps to use with the ADB commands.
Install Magisk apk
Copy the boot/recovery image to your device
Press the Install button in the Magisk card
If you are patching a recovery image, make sure “Recovery Mode” is checked in options.
In most cases it should already be automatically checked.
Choose “Select and Patch a File” in method, and select the stock boot/recovery image
The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.
Copy the patched image to your PC
*Note: Make sure you pay attention if your phone is EEA (for EU countries) or NON EEA (for the rest of the world). Attached you will find stock images for both variants (stockEEAboot.img and stockNONEEAboot.img).
If your phone is for EU (EEA) you can directly use the already patched boot image (patchedEEAboot.img) and skip this step.
3. Install drivers and ADB.
Download latest ADB - Fastboot version from the link below.
https://www.getdroidtips.com/download-adb/
Extract the ADB files to a new folder.
Download Ulefone drivers from the link below and follow instructions to install them (you need ADB drivers).
https://gsmusbdriver.com/ulefone-power-armor-13 can also find the stock ROMs for this phone.
*Note: without these drivers installed you cannot use ADB properly.
4. Rooting the phone
Copy the patched boot image and vbmeta_null.img in the adb folder.
Connect phone to PC (with USB debugging activated)
Open CMD window (with admin privilege) and and change directory to the adb folder (instructions can be found online depending on your OS version)
Now type the commands below exactly as they are written:
adb devices
Click to expand...
Click to collapse
- this initializes the ADB. Your device (specific strings of letters and numbers) should appear. If no device is detected please make sure you have followed the previous steps correctly.
adb reboot bootloader
Click to expand...
Click to collapse
- wait until device reboots in bootloader
When done verify the connection with the phone:
fastboot devices
Click to expand...
Click to collapse
Again, your device name from previous command should appear
fastboot flashing unlock
Click to expand...
Click to collapse
A message on the phone should appear. In order to unlock it follow the instructions on the screen (press Volume up key - if I remember correctly).
fastboot flash vbmeta vbmeta_null.img
Click to expand...
Click to collapse
This disables the safety check of the boot.img otherwise you will have a bootloop.
If you receive a positive answer we can go to next step. Second string has TWRP recovery and Magisk root included.
fastboot flash boot patchedEEAboot.img OR fastboot flash boot boot_TWRP_220321_magisk_v24300.img
Click to expand...
Click to collapse
patchedEEAboot.img - replace this with the actuale name of the patched boot image. Leave unchanged if you use the attached patched boot image (FOR EU VARIANT OF THE PHONE!!!).
Assuming everything went good you can reboot your phone:
fastboot reboot
Click to expand...
Click to collapse
The phone should now reboot without any issues. Open Magisk app and check if it shows as installed.
If you chose the TWRP and Magisk version of the boot image, Open Magisk app and follow the instructions to update the Magisk App and Magisk itself.
I DO NOT TAKE THE CREDIT FOR THE TWRP&MAGISK RECOVERY!!! ALL CREDIT GOES TO Бывалый
Ulefone Power Armor 13 - Обсуждение - 4PDA
Ulefone Power Armor 13 - Обсуждение, Смартфон, 6.81"
4pda.to
Congratulations, now you have successfully rooted your Ulefone Armor 13.
5. Additional steps if something goes wrong:
If your phone is bricked, do not despair. Simply patch the stock boot image using the same method. If that does not work, download the stock firmware and flash it with SPFlashtool following the instructions from the link below. Again make sure you install the correct firmware type (EU or NON-EU).
Ulefone Power Armor 13 Firmware Flash File MT6785 11.0
Download Ulefone Power Armor 13 Firmware Flash File Stock ROM, here we share latest firmware for Ulefone Power Armor 13 TF2 with flash tool & usb driver
romprovider.com
If you want to install Lucky Patcher and their version of Google Store (check online more info on the app) you need to install via Magisk Riru v25.4.4 and Riru EdXposed (instructions can be found online). Edxposed does not work with other Riru versions. Make sure you enable Lucky Patcher in Edxposed.
6. Missing IMEI/IMEI change
If you lost your IMEIs on your phone, you cannot connect to the GSM network. This is easily fixed using the SM Writer tool. You can download it from the link below.
Download SN Write Tool v1.2020 (Mediatek IMEI Write Tool)
Download the official SN Write Tool v1.2020 which allows you to Flash or Write IMEI on Mediatek Chipset Powered Smartphone, Tablets, FeaturePhone.
snwritetool.com
Use the instructions in the link below to change the IMEI. The original IMEI can be found on the phone´s box. If you want to change the IMEI just use a random number generator to generate new IMEIs (make sure they are the same length).
How to use SN Write Tool to Write, Flash, Fix IMEI on MediaTek Devices
Step-by-Step guidelines to Write, Flash, Fix or Change the IMEI on MediaTek devices using the SN Write Tool.
androidmtk.com
The files needed for the SMWrite tool can be found in the attached rar file SNWriter files.rar.
7. Custom recovery
Currently this phone does not have a custom recovery. With Magisk one is not truly needed.
Credits for the vbmeta_null.img go to Harlock1978 in the thread below.
How to root Ulefone Armor 11 5G
I'm pleased to report I've successfully done systemless root with MAGISK on the Ulefone Armor 11 5G. Turns out the process is nearly identical to the Armor 10. Most of the information I found on this thread First of all you need to unlock the...
forum.xda-developers.com

Nice write-up!
I just finished rooting my Power Armor 13 using your instructions, and now I'm trying to figure out what to do next. My last rooted phone was a OnePlus One (yep, the O.G. ), so I assume a LOT has changed since then.
Two questions for you:
Now that it's rooted, can I re-lock the bootloader to make that stupid "condition orange" bootup message go away, or do I have to keep it unlocked?
I seem to recall reading something a while back about rooted phones not being able to use Google Pay, but that rooting with Magisk can circumvent that limitation. Do you know if this is true, and if so, whether any additional setup is required?

foamrotreturns said:
Nice write-up!
I just finished rooting my Power Armor 13 using your instructions, and now I'm trying to figure out what to do next. My last rooted phone was a OnePlus One (yep, the O.G. ), so I assume a LOT has changed since then.
Two questions for you:
Now that it's rooted, can I re-lock the bootloader to make that stupid "condition orange" bootup message go away, or do I have to keep it unlocked?
I seem to recall reading something a while back about rooted phones not being able to use Google Pay, but that rooting with Magisk can circumvent that limitation. Do you know if this is true, and if so, whether any additional setup is required?
Click to expand...
Click to collapse
Thanks mate! Happy I could help
1. Relocking the bootloader check the link below. Honestly I would not recommend it. Higher chances of messing up the system. It does not affect system functionality and the reboot time are just slightly longer.
How to Relock Bootloader via Fastboot on Android
Although having an unlocked bootloader is useful in many ways like flashing firmware (factory images), installing TWRP and getting root, but it can also lead to blocked services on your device due …
nerdschalk.com
2. I am unsure but I do not think it is true. I do not use Google Play since I use the patched LuckyPatcher version. Not sure about the forum rules around this app but just do a Google on that the LP version does.

denis9rafael said:
Thanks mate! Happy I could help
Click to expand...
Click to collapse
There were a couple of steps where I was a little confused (it seemed like there was some "assumed knowledge," which I of course didn't have, since I've been out of the root/ROM game for way too long), but otherwise, it was a nice, straightforward tutorial, which was great. I won't give unsolicited advice, but if you're interested in some constructive criticism on the bits that had me scratching my head, let me know.
denis9rafael said:
1. Relocking the bootloader check the link below. Honestly I would not recommend it. Higher chances of messing up the system. It does not affect system functionality and the reboot time are just slightly longer.
How to Relock Bootloader via Fastboot on Android
Although having an unlocked bootloader is useful in many ways like flashing firmware (factory images), installing TWRP and getting root, but it can also lead to blocked services on your device due …
nerdschalk.com
Click to expand...
Click to collapse
Sounds like I should probably just suck it up then. Not really a big deal, since I rarely have to reboot, and the warning message is only there for a few seconds.
denis9rafael said:
2. I am unsure but I do not think it is true. I do not use Google Play since I use the patched LuckyPatcher version. Not sure about the forum rules around this app but just do a Google on that the LP version does.
Click to expand...
Click to collapse
Sorry, I must not have been very clear. I was referring to Google PAY, not Google PLAY. Google Pay is the app which uses the NFC chip in the phone to pay for goods and services at retail establishments where contactless payments are supported. It's the Android equivalent of Apple Pay, and I believe Samsung has their own version for their phones, which also works the same way. Basically, most financial/banking apps (and some games) have built-in rooted device detection, and if you try to run them on a rooted device, they'll refuse to work.
Fortunately, with a little research of my own, I found out that Magisk has a feature called MagiskHide, which allows it to evade rooted device detection on a per-app basis. I also found a Magisk Module called MagiskHide Props Config by Didgeridoohan , which opens up more customization possibilities, though I haven't explored that much.
Anyway, after configuring MagiskHide and telling it to hide Magisk from the apps I mentioned, I have successfully tested my primary banking app, and I'll be taking Google Pay for a test run at the grocery store, hopefully this evening.

Thank you very much for the info. Well written and extremely helpful.

foamrotreturns said:
There were a couple of steps where I was a little confused (it seemed like there was some "assumed knowledge," which I of course didn't have, since I've been out of the root/ROM game for way too long), but otherwise, it was a nice, straightforward tutorial, which was great. I won't give unsolicited advice, but if you're interested in some constructive criticism on the bits that had me scratching my head, let me know.
Sounds like I should probably just suck it up then. Not really a big deal, since I rarely have to reboot, and the warning message is only there for a few seconds.
Sorry, I must not have been very clear. I was referring to Google PAY, not Google PLAY. Google Pay is the app which uses the NFC chip in the phone to pay for goods and services at retail establishments where contactless payments are supported. It's the Android equivalent of Apple Pay, and I believe Samsung has their own version for their phones, which also works the same way. Basically, most financial/banking apps (and some games) have built-in rooted device detection, and if you try to run them on a rooted device, they'll refuse to work.
Fortunately, with a little research of my own, I found out that Magisk has a feature called MagiskHide, which allows it to evade rooted device detection on a per-app basis. I also found a Magisk Module called MagiskHide Props Config by Didgeridoohan , which opens up more customization possibilities, though I haven't explored that much.
Anyway, after configuring MagiskHide and telling it to hide Magisk from the apps I mentioned, I have successfully tested my primary banking app, and I'll be taking Google Pay for a test run at the grocery store, hopefully this evening.
Click to expand...
Click to collapse
Hi,
Sorry for the late reply. I never used Google Pay and honestly sometimes I forget it even exists .
Sure send me in a PM all the feedback you have in order to not clutter this thread! I´m always interested in improving myself. Also this was the first post I ever did here. Usually I am just using what other people have done.
I am happy I managed to help someone else for a change. Not that I have any real merit as I only put together info from other sites or threads.

Good day guys..
Love the info and genuine exchange of ideas I am seeing here..
Actually my first time trying to root..got a new ulefone armor 13.
Downloaded all the neccesarry file as mentioned above. But I have a challenge, don't know exactly from where to Copy or get boot/recovery image.
Tried using Mtkdroid to back up and extract the boot image..but got unknown ROM structure as a response,so couldn't scatter files nor go ahead with other steps..Is the any other way to get around this?

Otapiapia said:
Good day guys..
Love the info and genuine exchange of ideas I am seeing here..
Actually my first time trying to root..got a new ulefone armor 13.
Downloaded all the neccesarry file as mentioned above. But I have a challenge, don't know exactly from where to Copy or get boot/recovery image.
Tried using Mtkdroid to back up and extract the boot image..but got unknown ROM structure as a response,so couldn't scatter files nor go ahead with other steps..Is the any other way to get around this?
Click to expand...
Click to collapse
Hi,
Thanks for your feedback. Boot images for both EU and non EU phone versions are attacked to my first post. Boot images have .img at the end of the file. If you have an EU phone you already have a rooted boot image there.

denis9rafael said:
Hi,
Thanks for your feedback. Boot images for both EU and non EU phone versions are attacked to my first post. Boot images have .img at the end of the file. If you have an EU phone you already have a rooted boot image there.
Click to expand...
Click to collapse
Thanks...But keeps getting stucked on fastbootmode.. don't know the average time it takes to reboot in bootloader..or should I go on with the next commands regardless?

Otapiapia said:
Thanks...But keeps getting stucked on fastbootmode.. don't know the average time it takes to reboot in bootloader..or should I go on with the next commands regardless?
Click to expand...
Click to collapse
On what step do you get stuck? After you flash the boot image, you should get an ok message in the CMD window and then it should allow you to type the next command. After you flash the boot, you need to enter the reboot command in fastboot/adb.
Also remember to flash the vbmeta image first and then the boot image. Otherwise you will get stuck in a reboot loop.

denis9rafael said:
On what step do you get stuck? After you flash the boot image, you should get an ok message in the CMD window and then it should allow you to type the next command. After you flash the boot, you need to enter the reboot command in fastboot/adb.
Also remember to flash the vbmeta image first and then the boot image. Otherwise you will get stuck in a reboot loop.
Click to expand...
Click to collapse
After entering the "adb reboot bootloader" command, the phone goes blank, indicating FASTBOOT mode at the down left of the screen and doesn't reboot.

Otapiapia said:
After entering the "adb reboot bootloader" command, the phone goes blank, indicating FASTBOOT mode at the down left of the screen and doesn't reboot.
Click to expand...
Click to collapse
Adb reboot bootloader is supposed to bit the phone into fastboot mode. It does not reboot the phone into the OS because then you cannot flash a patch image. After it is in fastboot you continue with the next steps.
After you flash everything the OS reboot command is fastboot reboot.

Hi.. thanks for your time.
I carried on with other steps like you said..
But noticed no change nor response after typing the command "fastboot flashing unlock"..
Only saw "waiting for other devices" as a response in the CMD..as couldn't type any command again in the CMD..
Morealso, the phone screen remain blank and stucked in the fastbootmode..
I got it snapped,don't know if it against the rules to post pictures here.

Otapiapia said:
Hi.. thanks for your time.
I carried on with other steps like you said..
But noticed no change nor response after typing the command "fastboot flashing unlock"..
Only saw "waiting for other devices" as a response in the CMD..as couldn't type any command again in the CMD..
Morealso, the phone screen remain blank and stucked in the fastbootmode..
I got it snapped,don't know if it against the rules to post pictures here.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Otapiapia said:
Hi.. thanks for your time.
I carried on with other steps like you said..
But noticed no change nor response after typing the command "fastboot flashing unlock"..
Only saw "waiting for other devices" as a response in the CMD..as couldn't type any command again in the CMD..
Morealso, the phone screen remain blank and stucked in the fastbootmode..
I got it snapped,don't know if it against the rules to post pictures here.
Click to expand...
Click to collapse
With how your device looks, it appears it is not properly connected. Did you install all the drivers?
Under fastboot devices you should see a message as in the image below.
I will also add the direct image link.
https://www.androidjungles.com/wp-content/uploads/2018/11/ADB-Fastboot-Commands-List.png
Without this, the phone is not properly connected.
Did you unlock the fastboot in developer options as well? It is called there OEM unlock and you need debugging activated in the same place.

Thanks..
denis9rafael said:
With how your device looks, it appears it is not properly connected. Did you install all the drivers?
Under fastboot devices you should see a message as in the image below.
I will also add the direct image link.
https://www.androidjungles.com/wp-content/uploads/2018/11/ADB-Fastboot-Commands-List.png
Without this, the phone is not properly connected.
Did you unlock the fastboot in developer options as well? It is called there OEM unlock and you need debugging activated in the same place.
Click to expand...
Click to collapse
actually started the whole process afresh, downloaded and installed properly the driver's from the links you provided..Unlocked the OEM bootloader in the developer settings and also allowed for debugging...but couldn't still get past the Fastboot mode /waiting for a device.Once I input the "Fastboot devices" command, the command which you post its link
https://www.androidjungles.com/wp-content/uploads/2018/11/ADB-Fastboot-Commands-List.png
doesn't display either.
Checked device manager..for the status of the Installed driver, says up to date..
But the general info says "this device cannot start" (code 10)

Otapiapia said:
Thanks..
actually started the whole process afresh, downloaded and installed properly the driver's from the links you provided..Unlocked the OEM bootloader in the developer settings and also allowed for debugging...but couldn't still get past the Fastboot mode /waiting for a device.Once I input the "Fastboot devices" command, the command which you post its link
https://www.androidjungles.com/wp-content/uploads/2018/11/ADB-Fastboot-Commands-List.png
doesn't display either.
Checked device manager..for the status of the Installed driver, says up to date..
But the general info says "this device cannot start" (code 10)
Click to expand...
Click to collapse
Hi, did you do a PC restart? Did you install the drivers manually? It appears there is a problem with the drivers on your PC. They did not install properly.

denis9rafael said:
Hi, did you do a PC restart? Did you install the drivers manually? It appears there is a problem with the drivers on your PC. They did not install properly.
Click to expand...
Click to collapse
I restarted the PC..and while in fastbootmode..I tried updating the driver manually from the device manager.. Android ADB interface..
Says "windows encountered a problem installing the driver software for your device"
Had to uninstall and reinstall again...Same problem!

Otapiapia said:
Thanks..
actually started the whole process afresh, downloaded and installed properly the driver's from the links you provided..Unlocked the OEM bootloader in the developer settings and also allowed for debugging...but couldn't still get past the Fastboot mode /waiting for a device.Once I input the "Fastboot devices" command, the command which you post its link
https://www.androidjungles.com/wp-content/uploads/2018/11/ADB-Fastboot-Commands-List.png
doesn't display either.
Checked device manager..for the status of the Installed driver, says up to date..
But the general info says "this device cannot start" (code 10)
Click to expand...
Click to collapse
I think you may need to disable the driver signature verification in Windows 10 before you can install the drivers. Not sure though if that is the case .

Otapiapia said:
I restarted the PC..and while in fastbootmode..I tried updating the driver manually from the device manager.. Android ADB interface..
Says "windows encountered a problem installing the driver software for your device"
Had to uninstall and reinstall again...Same problem!
Click to expand...
Click to collapse
Hi...made progress
But one more thing... should I input the magisk patched file...or StockNONEEAboot.img
My phone is non EU variant..
AND FINALLY ROOTED with no issues..
Used the magisk patched file...
Thanks so much for you support, patience and guidance.
I so much appreciate!!

Please Help Me😭

I was trying to root my phone but i failed, doing so many wrong steps,now my samsung a7 is bricked, i cant charge it and i cant power it on, i also tried connecting it to a pc but the pc cant recognize it, any advice please to fix this? I really dont know what should i do now, thank you so much guys.

Can you talk us through the steps you did.
Is usb debugging enabled?
You may be able to use the samsung flashing software to recover but if you missed 1 or maybe 2 steps and have now wiped the device fully then you need to RMA. No os then no proof of your actions for a warranty claim to be rejected

enter download mode and flash firmware from Odin3

aIecxs said:
enter download mode and flash firmware from Odin3
Click to expand...
Click to collapse
Pretty much spot on, If all else fails then RMA

FKX1997 said:
Can you talk us through the steps you did.
Is usb debugging enabled?
You may be able to use the samsung flashing software to recover but if you missed 1 or maybe 2 steps and have now wiped the device fully then you need to RMA. No os then no proof of your actions for a warranty claim to be rejected
Click to expand...
Click to collapse
Im really sorry but i was actually not hard bricked, i thought i was hard bricked and i eventually got it turned on, so here is the whole story, i was about to root my phone and i watched a tutorial on how to but for some reason i trusted myself and didnt watch the video so i got into this situation, i enable USB debugging and OEM unlock( it deletes all of my files like a factory reset) i didnt know that i have to paste the magisk and the magisk apk to my phone and i flashed the bootloader thing from the tutorial i watched and then after that i decided to watch the tutorial and to my surprise the tutorial paste the magisk, so i panicked, i dont know what to do and i thought i was stucked at the downloading process so i decided to search more while panicking and i found that tenoshare Reiboot and Ult has this feature that will exit you to the downloading and now i tried them both but it failed, and i panicked more because now my phone just wont stop bootlooping so i just decided to drain its battery because its built in, i also tried flashing twrp but it cause me more panicking because it kind of glitches more so good thing i tried to go to downloading again by connecting to a pc and it worked, and the good thing is that the file i downloaded has a recovery flashable thing so i flashed it again, i escaped the teamwin bootloop and now i tried researching more causing me to figure it and i think i need to download the firmware again, but here is my biggest problem, i dont know the original place of the phone(i only know the country because its like a phone given only to me) i also dont know what is the original patch security of my phone( idk if its safe to just download the latest of the firmware) thank you for any advice

FKX1997 said:
Pretty much spot on, If all else fails then RMA
Click to expand...
Click to collapse
What is RMA? Please help me

Hi, i just wanna know if flashing the orginal firmware of a samsung phone, is it important to know the original patch security and the region(i know the country)? Thank you for all advice

Yatsuko said:
Hi, i just wanna know if flashing the orginal firmware of a samsung phone, is it important to know the original patch security and the region(i know the country)? Thank you for all advice
Click to expand...
Click to collapse
All you need is the correct firmware for your specific model number for your specific region/carrier and the firmware must have a binary that is equal to or higher than the binary of your currently installed firmware. The binary is indicated by the 5th character from the right in the firmware build number. Find that character in the build number of your currently installed firmware and compare it to the same character in the build number of the firmware that you want to flash. If the binary of the firmware that you want to flash is equal to or higher than the binary of your currently installed firmware then you can safely flash it, if the binary is lower than the binary of your currently installed firmware, you will not be able to flash the firmware that has a lower binary.

Droidriven said:
All you need is the correct firmware for your specific model number for your specific region/carrier and the firmware must have a binary that is equal to or higher than the binary of your currently installed firmware. The binary is indicated by the 5th character from the right in the firmware build number. Find that character in the build number of your currently installed firmware and compare it to the same character in the build number of the firmware that you want to flash. If the binary of the firmware that you want to flash is equal to or higher than the binary of your currently installed firmware then you can safely flash it, if the binary is lower than the binary of your currently installed firmware, you will not be able to flash the firmware that has a lower binary.
Click to expand...
Click to collapse
Oh, ok ^ ^ thank you so much!!

I fixed my problems now but i have another problem, i have flashed the bootloader and the twrp but now i am stucked at teamwin logo bootloop thing, i dont know how to fix this any advice? Thank you so much

Oh i forgot, when its like the 2nd or 3rd boot i got a black stripes on the screen, im also trying to press the volume up/down/up and down+power,

Boot into fastbooot and Flash stock boot img.

BadGirlNila said:
Boot into fastbooot and Flash stock boot img.
Click to expand...
Click to collapse
Is fastboot an application or an option in boot settings?

Hi Im trying to root my phone but whenever i do this method i got stuck at bootloop, here is the link
)
And the things i have
Patch security:Sep,2,2021
Device:Samsung-A750FN
OEM:Unlocked
USB debugging:Unlocked
Magisk being used:The one from the link
Any advice how to do it properly? Thank you so much

O
Yatsuko said:
Hi Im trying to root my phone but whenever i do this method i got stuck at bootloop, here is the link
)
And the things i have
Patch security:Sep,2,2021
Device:Samsung-A750FN
OEM:Unlocked
USB debugging:Unlocked
Magisk being used:The one from the link
Any advice how to do it properly? Thank you so much
Click to expand...
Click to collapse
Oh, my : become a sad emoji

Yatsuko said:
Is fastboot an application or an option in boot settings?
Click to expand...
Click to collapse
Bootloader is fastbooot. Boot into bootloader and do it

Hi, i just wanna know if i want to root my phone, is it important to unlock bootloader? And if yes, how should i do it in a samsung a7? Thanks!

Hi, i was planning to root my samsung a7 but i have a question that i dont know the answer, if OEM Unlock is enabled, USB debugging is also already enabled, why my OEM unlocked says bootloader is already unlocked even thought its still blue and not gray? Do i need to void my warranty and make OEM unlock colored gray or is blue enough? Thanks for all advice

MOD ACTION:
@Yatsuko
I had merged your multiple threads into this one yesterday and also sent an alert about it requesting you not to create multiple threads. Today I find that you have created a fresh thread. I have merged that post also in this thread.
With millions of users and messages, the forum is already overloaded. Please do not add to it when you can ask all your questions here.
Thank you!

TNSMANI said:
MOD ACTION:
@Yatsuko
I had merged your multiple threads into this one yesterday and also sent an alert about it requesting you not to create multiple threads. Today I find that you have created a fresh thread. I have merged that post also in this thread.
With millions of users and messages, the forum is already overloaded. Please do not add to it when you can ask all your questions here.
Thank you!
Click to expand...
Click to collapse
Oh, im really sorry,thank you so much