Database Develop

Observation On Infinix Hot 2 [X510-D5110-Androidone-20151208] on Root

So today I embarked on what seemed to be a fruitless journey as I tried to root the Infinix Hot 2 on the latest build (December Security Patch of course) and I observed the following:
1. Flashing TWRP Recovery that was previously made for this device doesn't Flash. SP/Infinix Flash Tool flashes the recovery quite alright but booting to recovery with ADB afterwards gives a "No command" screen.
2. Kingroot (PC & Mobile) can't root this device as of yet :'(
3. I think the bootloader can be unlocked using the Android One Toolkit that was created for 1st Gen Android One devices. Reason being the fact it booted to fastboot and prompted me with the option to accept bootloader unlock or not.
Should you come come successful with flashing recovery or rooting this latest build, please comment your method. Thank you...

Link to Android One Toolkit:
http://forum.xda-developers.com/crossdevice-dev/android-one-general/toolbox-android-one-toolkit-one-click-t3030165

recovery partition is protected, it will get back to stock recovery if you boot the system. so you really need to boot recovery as the first thing you do after flashing.
which because of the similar bug we can't unlock our bootloader, is impossible to do with default setting. flash your lk partition with this:
http://www80.zippyshare.com/v/X4etwppD/file.html
taken from: http://forum.xda-developers.com/hot-2/development/android-one-rom-recovery-twrp-root-sp-t3227682

sabcpj said:
recovery partition is protected, it will get back to stock recovery if you boot the system. so you really need to boot recovery as the first thing you do after flashing.
which because of the similar bug we can't unlock our bootloader, is impossible to do with default setting. flash your lk partition with this:
http://www80.zippyshare.com/v/X4etwppD/file.html
taken from: http://forum.xda-developers.com/hot-2/development/android-one-rom-recovery-twrp-root-sp-t3227682
Click to expand...
Click to collapse
Thanks I will try this in the morning...
One more question... Does this mean after flashing recovery I can boot directly into TWRP using key combo?

iAmWiz said:
Thanks I will try this in the morning...
One more question... Does this mean after flashing recovery I can boot directly into TWRP using key combo?
Click to expand...
Click to collapse
yes, you should be. and you need to

Alright then

sabcpj said:
yes, you should be. and you need to
Click to expand...
Click to collapse
there is no scatter file for the lk-recovery.. I do not think I can flash it directly with Flash Tool without the scatter file

iAmWiz said:
there is no scatter file for the lk-recovery.. I do not think I can flash it directly with Flash Tool without the scatter file
Click to expand...
Click to collapse
why do you think you need another scatter file. you already tried flashing twrp right? use that one. then change the location of partition named "lk" to point this file. that's all.

sabcpj said:
why do you think you need another scatter file. you already tried flashing twrp right? use that one. then change the location of partition named "lk" to point this file. that's all.
Click to expand...
Click to collapse
Alright. If I cannot get a workaround on this, I'll just Flash Infinix 5.1 ROM and wait till M

Try using towel root
https://towelroot.com/

Mysteryagr said:
Try using towel root
https://towelroot.com/
Click to expand...
Click to collapse
Thanks but towelroot didn't work out.

Root achieved... More at
http://forum.xda-developers.com/hot-2/development/root-recovery-xposed-successfully-t3276420

please can you help me sp flashtool stuck at 0 and nothing happens

Guide to install Nougat / Emui5 on BTV-DL09

Okay, managed to get Nougat and root for my BTV-DL09. Here is a fast forward tutorial how to do that.
I could only root it by using Magisk, Supersu (even the special emui5 ones) did not work for me.
Files:
ROM: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1224/g490/v78425/f1/full/update.zip (BTV-DL09C233B336)
Data: http://update.hicloud.com:8180/TDS/...full/dualcu/cn/update_data_full_dualcu_cn.zip
TWRP, make sure to use twrp_BTV-DL09_5_greatslon.img : https://androidfilehost.com/?fid=817550096634750327 (thanks to greatslon)
Root: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I came from version BTV-DL09C100B006, this is how I did it:
Bootloader must be unlocked, custom recovery installed (Do not install the one for EMUI5 yet, it won't boot).
Enter recovery by adb reboot recovery
Wipe, reboot recovery
Flash ROM + Data
Flash Magisk Root
Flash Recovery again (will be overwritten by the udate)
Reboot, Done.
Download playstore / vending APK from APKmirror: http://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-7-6-08-release/ and transfer it on the device.
There is an app called "Downloads" preinstalled (there is pretty much nothing on the tablet, not even a browser after flashing it), you can use that to open/install the play store APK and get things going.
Please make sure you know what you are doing and you know how to recover from a soft brick. I take no responsibility if anything goes wrong.
The version you should have now is BTV-DL09C233B336 with security update from February included.

Thank you very much, and how to downgrade ?

can someone upload a youtube video showing us the the new EMUI5 on this tablet, and give us an overview about the new features and performance?

Beware that:
1) this is a chinese ROM
2) Nougat version 7.0.0
3) if you don't like the downgrade process is difficult
4) if you want to downgrade have to find another ROM!!!

any idea to downgrade please

drlsd said:
any idea to downgrade please
Click to expand...
Click to collapse
You need another ROM, FULL not OTA.
1) extract from the .APP the recovery (both) and boot images
https://forum.xda-developers.com/showthread.php?t=2433454
2) get a build.prop from the ROM you want to install
3) copy the build.prop in the /system folder, overwriting the original: now the old ROM will unlikely boot!
4) go in fastboot mode and flash recovery, recovery2 and boot images
5) copy the update.app in the dload folder
6) reboot and maintain pressed both volume keys to start recovery
7) if you are lucky the recovery will install the ROM.
Of course you will loose all your data (uhm, not even but... MAKE A BACKUP before!)
If you don't know well how to do ALL this don't even try!
If you have the original european LTE ROM please share it!!!
Nicola

2) get a build.prop from the ROM you want to install
i can t found these file in the new full rom (in my case BTV-DL09C233B035 )

drlsd said:
2) get a build.prop from the ROM you want to install
i can t found these file in the new full rom (in my case BTV-DL09C233B035 )
Click to expand...
Click to collapse
I attached that I extracted from the same ROM.

nicolap8 said:
I attached that I extracted from the same ROM.
Click to expand...
Click to collapse
Please share your oeminfo if you can. Thank you.

thank u very muatch nicolap8 ,is it normal i have NRD90M test-keys like number of software in my medipad m3 european LTE ?

drlsd said:
thank u very muatch nicolap8 ,is it normal i have NRD90M test-keys like number of software in my medipad m3 european LTE ?
Click to expand...
Click to collapse
What are you saying about???
It depends from which ROM have you installed!
Often the truly incompetent Huawei developers uses the wrong keys...

nicolap8 said:
What are you saying about???
It depends from which ROM have you installed!
Often the truly incompetent Huawei developers uses the wrong keys...
Click to expand...
Click to collapse
from europien lte to BTV-DL09C233B336 and now my build verson is NDR90M test-key

nicolap8 said:
You need another ROM, FULL not OTA.
1) extract from the .APP the recovery (both) and boot images
https://forum.xda-developers.com/showthread.php?t=2433454
2) get a build.prop from the ROM you want to install
3) copy the build.prop in the /system folder, overwriting the original: now the old ROM will unlikely boot!
4) go in fastboot mode and flash recovery, recovery2 and boot images
5) copy the update.app in the dload folder
6) reboot and maintain pressed both volume keys to start recovery
7) if you are lucky the recovery will install the ROM.
Of course you will loose all your data (uhm, not even but... MAKE A BACKUP before!)
If you don't know well how to do ALL this don't even try!
If you have the original european LTE ROM please share it!!!
Nicola
Click to expand...
Click to collapse
rom-stock-btv-dl09c100b009-european
https://forum.xda-developers.com/mediapad-m3/how-to/rom-stock-btv-dl09c100b009-european-t3588477

nicolap8 said:
What are you saying about???
It depends from which ROM have you installed!
Often the truly incompetent Huawei developers uses the wrong keys...
Click to expand...
Click to collapse
Hi nicolap8 even I followed the same steps as you suggested with the file links you shared and I am also NRD90M test-keys on my Mediapad BTV-DL09
installing Magisk first time gave me a fail message but second time it works like a charm. thanks
could you help, thanks

Switched to eu rom, updated to nougat.. unlocked bootloader and rooted with magisk
But using magisk caused the fingerprint sensor not to work at all and there is no settings for the FP in the settings menu.
Uninstalled magisk and the fingerprint worked again but obviously I lost root.
Flashing SuperSU didn't work gives an error in twrp no matter what version I try.
Any idea on how to root without compromising the fingerprint sensor?? :/

Half Alive said:
Flashing SuperSU didn't work gives an error in twrp no matter what version I try.
Click to expand...
Click to collapse
Error? we do not see errors...
Post recovery.log

question
how to flash firmware for Huawei Mediapad M3 ? I know how to do it for galaxy with odin ?.
where I download firmware for Huawei Mediapad M3 ?

carlo67 said:
question
how to flash firmware for Huawei Mediapad M3 ? I know how to do it for galaxy with odin ?.
where I download firmware for Huawei Mediapad M3 ?
Click to expand...
Click to collapse
You have more than 600 posts and yet have not understod the rules here???
SEARCH and READ!

Fingerprint Button
Hello, velocity.
Worked for me, thx.
The fingerprint button doesn't work anymore.
Is there a way to activate it (without loosing root by uninstalling magisk)?
Kind regards

veloc1ty said:
Okay, managed to get Nougat and root for my BTV-DL09. Here is a fast forward tutorial how to do that.
I could only root it by using Magisk, Supersu (even the special emui5 ones) did not work for me.
Files:
ROM: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1224/g490/v78425/f1/full/update.zip (BTV-DL09C233B336)
Data: http://update.hicloud.com:8180/TDS/...full/dualcu/cn/update_data_full_dualcu_cn.zip
Click to expand...
Click to collapse
Those Links are dead. Anyone save a copy? Willing to share? Thanks.

Magisk 14 News

Wow no need for custom recovery...
http://www.androidpolice.com/2017/0...hout-root-installing-without-custom-recovery/

@ultramag69 Maybe he doesn't follow Magisk closely? I know I don't. Magisk is only on used my stepmom's OP3T H2OS (which I update but don't look at the change log since it's only there in case I need it in the future), the other 2 phones I support don't use Magisk they use LOS su add-on. Not everyone who uses root cares about all the bloated/"nifty" features that come out, some just want plain old root.

I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.

I'm letting people know that with 14 they can keep stock recovery and take OTAs

ultramag69 said:
I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.
Click to expand...
Click to collapse
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS

lollyjay said:
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS
Click to expand...
Click to collapse
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.

ultramag69 said:
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.
Click to expand...
Click to collapse
No need to do that now

Honestly, who roots a phone without flashing a custom recovery the very second after? Unless they are forced to use Flashfire without BL unlock, I guess.

lollyjay said:
No need to do that now
Click to expand...
Click to collapse
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...

ultramag69 said:
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...
Click to expand...
Click to collapse
No problems at all with my OP5

Magisk 14.0 breaks XPosed so had to go back to Magisk 13.3

Now where can we obtain a copy of the stock boot.img?

almostthere said:
Now where can we obtain a copy of the stock boot.img?
Click to expand...
Click to collapse
What you're supposed to do is make a backup of your boot partition any time you update your rom. So if you didn't do that then you can dirty flash your current Rom and that would give you the stock boot.img and again, go into recovery and make a backup of your boot partition. then if you want to flash a custom kernel you can.

Help the noobs
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.

s_ofer said:
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.
Click to expand...
Click to collapse
I have the stock 4.5.10 boot.img for download here:
https://drive.google.com/file/d/0B3gcDbDvV4Mkbm5EMEZ4dnpSbk0/view?usp=drivesdk
Sent from my OnePlus5 using XDA Labs

Thanks.
Do any of you think it is possible to FLASH anything without unlocking the bootloader?
There is a thread somewhere for OP3T that shows somehow that is possible to load TWRP on the phone without unlocking the bootloader or wiping data.

I only use for root too but every so often I open magisk manager as it updates also both the manager app and magisk itself. But using magisk to root my Axon 7 with unlocked bootloader.

Stuck in Fastboot

Hey everyone got my Pixel 5 yesterday and unlock and flash Magisk patched 21005 but after flash i’m stuck in fastboot when i presss start nothing happen, if i try to power off it goes back fastboot . I post in the Tutorial tread but haven’t gotten any answer yet .
What’s the procedure to get out of this . I’ve had pixels before but haven’t for a while , kinda rusty .
Thanks

What method did you use to flash Magisk? You patched the boot.img with the Magisk app?
To get out of your bootloader loop, flashing the stock boot.img should get out of it, then you could try again. Make sure your SDK Platform Tools is up to date.
Also, if you are on the Android 12 Developers Preview, fastboot boot the patched boot.img instead of flashing it.

xunholyx said:
What method did you use to flash Magisk? You patched the boot.img with the Magisk app?
To get out of your bootloader loop, flashing the stock boot.img should get out of it, then you could try again. Make sure your SDK Platform Tools is up to date.
Also, if you are on the Android 12 Developers Preview, fastboot boot the patched boot.img instead of flashing it.
Click to expand...
Click to collapse
No used a patched magisk which was post in one of the guides to unlock and root pixel 5.

Could downloading full factory image and extract the boot.img and flash it in fastboot fix this ?.

jawonder said:
No used a patched magisk which was post in one of the guides to unlock and root pixel 5.
Click to expand...
Click to collapse
The guide might be outdated

jawonder said:
Could downloading full factory image and extract the boot.img and flash it in fastboot fix this ?.
Click to expand...
Click to collapse
Yes, that's exactly what I meant.
Then after you are fixed up, install the new Magisk app. Transfer the boot.img to your phone's download folder. Open up the Magisk app and choose to install. That will give you an option to patch the image. Select that. Navigate to your phone's download folder and select the boot.img . When that's done, transfer the patched image to your PC (in your ADB/fastboot folder makes for the easiest way). After that fastboot flash boot **drag and drop the patched boot.img here**
If you are running the 12 developers preview through, flashing it isn't working yet. You'll have to fastboot boot it for temporary root, and have to do that again every time you reboot. This should be fixed soon though. It might already be. I'm not sure if Magisk v22.0.0 had fixed that yet. I'll know in the next couple of hours when I have time to play with my phone.

Ahh!, that’s straight forward . I had pixels phones before so i remember a little .
I’m on android 11 Fi version, just got my phone yesterday and updated it .
Thanks will do that when i get home .

jawonder said:
Ahh!, that’s straight forward . I had pixels phones before so i remember a little .
I’m on android 11 Fi version, just got my phone yesterday and updated it .
Thanks will do that when i get home .
Click to expand...
Click to collapse
Yeah, the game changed after Android 10 got released. I won't get into specifics of why, but devices released with Android 10 and later don't have twrp anymore mostly

Question root failed and bootloop

I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks

leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Hey,
If you've only booted the image, then you only need to reboot and the image is lost, the only way that it would be permanent is if it was flashed: fastboot flash not: fastboot boot.
Usually what happens is when you obtain a firmware to install or in your case change region, and you wish to root this firmware you would extract payload.bin then use fastboot enhance to extract the boot.img
Then copy to your phone and patch it with the latest stable Magisk (in this case 24.3)
So again, if you've only booted the image then just reboot your phone and it'll turn on using the actual flashed boot.img from the firmware, not the one you booted.
If that doesn't work then you must have flashed it. In which case you can either re-flash your original boot.img or boot then direct install a correctly patched image for the correct firmware (after a success boot) via Magisk.

leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Here's a good "how to" to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/

Canuck Knarf said:
Here's a good how to to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/
Click to expand...
Click to collapse
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse

dladz said:
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse
Click to expand...
Click to collapse
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk

Canuck Knarf said:
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk
Click to expand...
Click to collapse
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
If what he's advised is true then he's successfully changed OS/region and now wants to root, the only thing he's done thus far is to boot a boot image. I think he's flashed it as booting is not permanent, to suggest to go ahead and attempt to obtain a color OS boot image or vendor image is absolutely ridiculous.
He's on an EU firmware. So he requires an EU boot image.

He's in boot loop cause he is booting to A slot...

Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode

dladz said:
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
Click to expand...
Click to collapse
oxygen OS using the firmware EU 11_A.12.... He still needs boot img ...vender_boot form the firmware EU 11_A.12 . to root

leofung_wai said:
Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode
Click to expand...
Click to collapse
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance

He already had boot?? What are you talking about???
He had a functional OS, in order to root you only need ONE image.
The boot image which comes from OOS. The link you sent is for Color OS?? Make sense now ??
He just needs to patch it correctly and boot it then direct install.
Im going over this again with someone who's incapable of understanding the basics.

Canuck Knarf said:
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance
Click to expand...
Click to collapse
You do realise that booting an image does not need to be directed don't you?
Only by flashing should you direct the image to a particular slot.
By flashing you are permanently flashing an image.
I don't think you understand this so I'll make it simple for you.
You want to root your phone. You have an image you've just patched, from boot.img to magisk_patched.img
Firstly you would want to send this via fastboot, you do not need fastboot enhance for this.
The preferred way to do this is to fastboot boot magisk_patched.img
Why is this preferred??
Because if it fails as it may. Then you are not stuck in a boot loop, you just reboot and you're back in the OS.
The 2nd method is flashing.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
fastboot reboot
Press enter.
Now although this can work it is not the preferred method because you aren't just booting the image you are flashing it, this means that if it fails you cannot just reboot and get back to the OS you have to either obtain a new boot image and patch it although you cannot do this yourself as your phone no longer boots or you obtain an already patched boot image, again the last one I wouldn't recommend..

Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root

leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
Ok so if you've got into the system..
You need to follow the instructions I have in my guide in order to get root...
You can use the boot image I have there.

leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
It is always better to patch boot.img of your own version (you can dump it from payload dumper etc.) and then only fastboot boot patched_image.img and then directly install it via Magisk.

Boot this image.
192 MB folder on MEGA
mega.nz

Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally

Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done

leofung_wai said:
Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally
Click to expand...
Click to collapse
If you've patched your own image and booted it then click Magisk then install. Then direct install and you're done..

dladz said:
Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done
Click to expand...
Click to collapse
thanks i success root by your image now
but i had a question, i messed up the slot B and now can only boot through slot A Will it affect anything