Hi,
I put all information into "zui.com/iunlock" correctly, but I get a "Please enter the correct IMEI1" error, and I'm entering it correctly
Please help...
If it's a brand new phone, the imei is not registred by the website at the start.
After a couple of day of use it must work.
Same problem for me at the start and after two day of using the phone my imei is working on the website.
Thanks for the reply
Do I need to put my sim in the phone?
Or is it enough just to connect to wifi?
I used my sim for about 3h, and I got the site to take my IMEI!
Now my bootloader is unlocked
Thanks
Your welcome
I received my smartphone for 10 days. but my emei is still not recognized.
I installed a firewall and everything is blocked except the browser and the messages. I have to authorize a specific program for zui to integrate it?
hello, after 25 days of waiting my imei still did not pass. yesterday I sent an email to devworld and today I had my file
YES :good:
lecomte_jean said:
hello, after 25 days of waiting my imei still did not pass. yesterday I sent an email to devworld and today I had my file
YES :good:
Click to expand...
Click to collapse
Good to know, thank's for the feedback
Bypass
I had the exact same issue and for some weird reason the weirdest glitch ever helped my bypass ZUI all together:
I made a little .bat file to automate all the adb and fastboot commands once I'd get the bootloader unlock file
I didn't know for sure if I had referred to the subfolders in my adb map correctly so I wanted to test it out:
adb reboot bootloader
fastboot flash unlock ".\Z6 Pro\Bootloader.img"
fastboot oem unlock-go
fastboot reboot
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta ".\Z6 Pro\vbmeta.img"
fastboot reboot bootloader
fastboot flash recovery ".\Z6 Pro\twrp.img"
that's what it was gonna be^
but to test out if I had referred correctly I changed vbmeta.img's name into bootloader.img since it was the first path and I expected it to fail but this way I'd at least find out if I got a file not found error or a incorrect boot loader unlock file error.
It flashed correcty, the os is stable and I just installed TWRP.
Idk if this can be done with any img, but the vbmeta file shouldn't have done that. XD
Related
Help! "Your device is corrupt. It can't be trusted and may not work properly." (Red)
Hello,
just recently i rooted my Nexus 6p device and unlocked the bootloader, i noticed however, after rooting the device i received an error on boot up stating "Your device software can't be checked for corruption. Please lock the bootloader." (Orange), but after researching on the internet many people said that was normal due to the boot loader being unlocked...
however my concern for today is i have flashed back to the factory images of marshmallow, and am now experiencing an error on boot up that Your device is corrupt. It can't be trusted and may not work properly." i followed the exact step-by-step guide on how to unroot and lock the boot loader on the link below however am still experiencing the issue, please help it will be ever so much appreciated.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(the error that i am receiving after flashing stock image)
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
I've had that as well with mine before. The way I fixed mine was a somewhat tedious process but it did work for me. Start by downloading one of the angler images from Google, then with 7zip, decompress the .tgz which gives you a .tar. Once more will get you a folder named xxxxxx-angler. (I think it was that way but not 100% sure since I'm not at my laptop at the moment). With your phone (unlocked) in bootloader/fastboot mode, run flash-all.bat. this gets you back to a fully stock system but still has the corruption flag tripped. Run stock recovery and do a factory reset and the corruption warning should be gone and back to the "normal" screen saying please lock the bootloader.
bb1981 said:
I've had that as well with mine before. The way I fixed mine was a somewhat tedious process but it did work for me. Start by downloading one of the angler images from Google, then with 7zip, decompress the .tgz which gives you a .tar. Once more will get you a folder named xxxxxx-angler. (I think it was that way but not 100% sure since I'm not at my laptop at the moment). With your phone (unlocked) in bootloader/fastboot mode, run flash-all.bat. this gets you back to a fully stock system but still has the corruption flag tripped. Run stock recovery and do a factory reset and the corruption warning should be gone and back to the "normal" screen saying please lock the bootloader.
Click to expand...
Click to collapse
thank you but i have already done all that, the problem is that i have flashed the angler image from google and did a factory reset,however, i am selling the phone soon and the warning message is still there even though the boot loader is locked and am not rooted
Moddy98 said:
thank you but i have already done all that, the problem is that i have flashed the angler image from google and did a factory reset,however, i am selling the phone soon and the warning message is still there even though the boot loader is locked and am not rooted
Click to expand...
Click to collapse
Try doing this process manually, if you're selling it. I would infer the data doesn't matter on the device.
Depending on which OS you are on. Focus your command prompt with fast boot installed to your directory containing the stock files (unzip the image zip)
Now do the following process manually. Step by step
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash vendor vendor.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot flash cache cache.img
Now, if you still get the red warning. Repeat the process and add :
fastboot format userdata
DO NOT FLASH THE USERDATA IMAGE
If this does not work, I have other suggestions.
same prob in orange..plz help bro
TnT_ said:
Try doing this process manually, if you're selling it. I would infer the data doesn't matter on the device.
Depending on which OS you are on. Focus your command prompt with fast boot installed to your directory containing the stock files (unzip the image zip)
Now do the following process manually. Step by step
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash vendor vendor.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot flash cache cache.img
Now, if you still get the red warning. Repeat the process and add :
fastboot format userdata
DO NOT FLASH THE USERDATA IMAGE
If this does not work, I have other suggestions.
Click to expand...
Click to collapse
I flashed my nexus 5x with marshmallow from nougat...but at the end i didn't lock the oem bootloader...so now i am repeatedly getting an error message "your device software can't be checked for corruption.Please lock the bootloader nexus"(orange color)..i had downgraded my nexus to marshmallow because i was having a bootloader stuck up loop problem...
And to do any of the steps I have to switch on the usb debugging mode right ??? But the problem is this message is constantly coming and i am unable to do anything for the past 2 days
vigy321 said:
I flashed my nexus 5x with marshmallow from nougat...but at the end i didn't lock the oem bootloader...so now i am repeatedly getting an error message "your device software can't be checked for corruption.Please lock the bootloader nexus"(orange color)..i had downgraded my nexus to marshmallow because i was having a bootloader stuck up loop problem...
And to do any of the steps I have to switch on the usb debugging mode right ??? But the problem is this message is constantly coming and i am unable to do anything for the past 2 days
Click to expand...
Click to collapse
To flash back to stock, you have to boot into bootloader and using fastboot to flash factory image.
But hey, you're in the Nexus 6P forum, try following this guide in the Nexus 5X forum:
https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I just went through this. Just unlock your bootloader with the Nexus toolkit and it'll go away that's all i did
Sent from my Nexus 6P using Tapatalk
---------- Post added at 06:45 PM ---------- Previous post was at 06:42 PM ----------
Moddy98 said:
Hello,
just recently i rooted my Nexus 6p device and unlocked the bootloader, i noticed however, after rooting the device i received an error on boot up stating "Your device software can't be checked for corruption. Please lock the bootloader." (Orange), but after researching on the internet many people said that was normal due to the boot loader being unlocked...
however my concern for today is i have flashed back to the factory images of marshmallow, and am now experiencing an error on boot up that Your device is corrupt. It can't be trusted and may not work properly." i followed the exact step-by-step guide on how to unroot and lock the boot loader on the link below however am still experiencing the issue, please help it will be ever so much appreciated.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(the error that i am receiving after flashing stock image)
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
Click to expand...
Click to collapse
It happened to me just last week. Just unlock your bootloader with the Nexus toolkit and it'll go away. That's all i did and it went away i got it the same way you did and that's all I did
Sent from my Nexus 6P using Tapatalk
I just wanted to report that I successfully re-locked my bootloader (did not find that here).
I have an H850 with GPS problems. To return it I wanted it to be as stock as possible.
I used TWRP to flash LG-H85010E-Flashable.COMPLETE.zip from Codefire. Back to unrooted.
I also tried to flash recovery.img from the same source. This seemed to work (no more TWRP), but did not allow for OTAs (update error 0x1125000).
Then I put the phone in download mode, started LG bridge and did the "Updatefehler korrigieren" thing (German, roughly translates to "correct update errors").
To re-lock the bootloader, I put the phone in USB Debugging mode and entered the following commands:
Code:
adb reboot bootlaoder
fastboot oem lock
fastboot reboot
The phone gets wiped by this, but you need to do the initial dialog again: enable developer mode, then go there an disable OEM unlock. After that do a factory data reset one last time.
You should contact @autoprime and have him add this to his all in one thread.
Thanks for the info!
@bornheim2
It's good to see that we have option to turn back to stock, and maybe send phone for warrianty repair. But I have one question... If you had tried to unlock phone once again, would You had to enter LG Unlock Code again?
Hazard17 said:
If you had tried to unlock phone once again, would You had to enter LG Unlock Code again?
Click to expand...
Click to collapse
Obviously. The command to unlock is
Code:
fastboot flash unlock unlock.bin
which means you need to have the unlock.bin file available. You did archive the mail, didn't you?
bornheim2 said:
Obviously. The command to unlock is
Code:
fastboot flash unlock unlock.bin
which means you need to have the unlock.bin file available. You did archive the mail, didn't you?
Click to expand...
Click to collapse
I haven't unlocked my phone yet, but it is important message for me.
bornheim2 said:
Obviously. The command to unlock is
Code:
fastboot flash unlock unlock.bin
which means you need to have the unlock.bin file available. You did archive the mail, didn't you?
Click to expand...
Click to collapse
No I didn't archive the mail
I've got the same problem - seller deceived me and sold phone after water damage. My microphone stopped work and I should send it back. How to lock the bootloader on RS988 model?
Dear All,
I have a Problem with my Moto X play XT 1562. I have brought it a year back.
For some strange reason, My phone stopped working all of a sudden.
when I connect it to a PC via USB I'll get a boot-loader menu which says "StartUp failed Please connect the phone to a software repair assistant on the PC". Though I have figured out the problem I am unable to do anything about it.The problem is simple yet complex at the same time,
Problem: Though I have rooted many android phones previously, I never rooted this one. So My boot-loader is locked. I have got the Unique unlock key from Motorola site But when I get to this commad
HTML:
fastboot oem unkock [MY_UNLOCK_KEY]
I get an error message saying "Check 'Allow unlock OEM' in developer options". But my phone is not booting so far so that I can check that.
The basic problem is, My phone's OS is corrupted and I am unable to boot a new OS to it, As the boot loader is locked, I am unable to unlock the boot loader because I have not checked on 'Allow OEM unlock'. I am unable to check 'Allow OEM Unlock' because I The os is corrupted. - (This looks like a riddle )
1.Is there any way I can either bypass this?
2.Is there any way I can check 'Allow unlock OEM' using fastboot or any other tool?
I have tried the following already,
1.tried to clear user data and cache with fastboot - Still remains the same
2.tried to flash a recovery image even though the boot-loader is locked - No Use.
3.contacted service centre just to realise that I have to change the PCB which will cost me a new phone!
Can anyone of you please help me out with this.
Thanks a Ton in Advance.
pldeep said:
Dear All,
I have a Problem with my Moto X play XT 1562. I have brought it a year back.
For some strange reason, My phone stopped working all of a sudden.
when I connect it to a PC via USB I'll get a boot-loader menu which says "StartUp failed Please connect the phone to a software repair assistant on the PC". Though I have figured out the problem I am unable to do anything about it.The problem is simple yet complex at the same time,
Problem: Though I have rooted many android phones previously, I never rooted this one. So My boot-loader is locked. I have got the Unique unlock key from Motorola site But when I get to this commad
HTML:
fastboot oem unkock [MY_UNLOCK_KEY]
I get an error message saying "Check 'Allow unlock OEM' in developer options". But my phone is not booting so far so that I can check that.
The basic problem is, My phone's OS is corrupted and I am unable to boot a new OS to it, As the boot loader is locked, I am unable to unlock the boot loader because I have not checked on 'Allow OEM unlock'. I am unable to check 'Allow OEM Unlock' because I The os is corrupted. - (This looks like a riddle )
1.Is there any way I can either bypass this?
2.Is there any way I can check 'Allow unlock OEM' using fastboot or any other tool?
I have tried the following already,
1.tried to clear user data and cache with fastboot - Still remains the same
2.tried to flash a recovery image even though the boot-loader is locked - No Use.
3.contacted service centre just to realise that I have to change the PCB which will cost me a new phone!
Can anyone of you please help me out with this.
Thanks a Ton in Advance.
Click to expand...
Click to collapse
You can still flash the firmware that is meant for your model/carrier without unlocking bootloader. run getvar all command in fastboot to determine what firmware exatly do you need if unsure.
minimale_ldz said:
You can still flash the firmware that is meant for your model/carrier without unlocking bootloader. run getvar all command in fastboot to determine what firmware exatly do you need if unsure.
Click to expand...
Click to collapse
Can you please guide me trough the steps in a very vauge way(I'll be able to folllow) thanks a ton for the response
pldeep said:
Can you please guide me trough the steps in a very vauge way(I'll be able to folllow) thanks a ton for the response
Click to expand...
Click to collapse
Connect your phone in fastboot mode and type this command:
Code:
fastboot getvar all
in output look for this:
Code:
(bootloader) ro.build.fingerprint:
It's the firmware version that you currently have on your phone. Download exactly the same one and you'll be able to flash it with bootloader locked.
minimale_ldz said:
Connect your phone in fastboot mode and type this command:
Code:
fastboot getvar all
in output look for this:
Code:
(bootloader) ro.build.fingerprint:
It's the firmware version that you currently have on your phone. Download exactly the same one and you'll be able to flash it with bootloader locked.
Click to expand...
Click to collapse
Hey Sorry minimale_ldz,
I got it till this step. I wanted to know what command should I use to flash the os into the phone.
I know how to do Recovery though
HTML:
Fastboot flash recovery recovery.img
I want to know how to do the same with OS.
Thanks again
pldeep said:
Hey Sorry minimale_ldz,
I got it till this step. I wanted to know what command should I use to flash the os into the phone.
I know how to do Recovery though
HTML:
Fastboot flash recovery recovery.img
I want to know how to do the same with OS.
Thanks again
Click to expand...
Click to collapse
You've got instructions in this thread:
https://forum.xda-developers.com/mo...de-how-to-flash-factory-image-return-t3261486
Mind that you'll likely have more system.img_sparsechunk files, so make sure you flash all of them (just change commands accordingly).
Guys I had no luck in doing that.
When ever I try to flash the contents of the stock os, I get a error message which says Pre Flash validation failed.
Can any one help me please
pldeep said:
Guys I had no luck in doing that.
When ever I try to flash the contents of the stock os, I get a error message which says Pre Flash validation failed.
Can any one help me please
Click to expand...
Click to collapse
Your emmc ship is corrupt. That means your whole storage is broken and not fixable.
But i am able to flash some of the contents of the stock ROM. I get this "Pre flash validation failed" error only when I try to flash some of the files like (system.img_sparsechunk.0-9,recovery.img and gpt.bin). I even tried to reset the emmc_chip, I says that the command was succesfully executed.
Is there any other option left??
I am fighting this battle since a week now.
pldeep said:
Dear All,
I have a Problem with my Moto X play XT 1562. I have brought it a year back.
For some strange reason, My phone stopped working all of a sudden.
when I connect it to a PC via USB I'll get a boot-loader menu which says "StartUp failed Please connect the phone to a software repair assistant on the PC". Though I have figured out the problem I am unable to do anything about it.The problem is simple yet complex at the same time,
Problem: Though I have rooted many android phones previously, I never rooted this one. So My boot-loader is locked. I have got the Unique unlock key from Motorola site But when I get to this commad fastboot oem unkock [MY_UNLOCK_KEY]
I get an error message saying "Check 'Allow unlock OEM' in developer options". But my phone is not booting so far so that I can check that.
The basic problem is, My phone's OS is corrupted and I am unable to boot a new OS to it, As the boot loader is locked, I am unable to unlock the boot loader because I have not checked on 'Allow OEM unlock'. I am unable to check 'Allow OEM Unlock' because I The os is corrupted. - (This looks like a riddle )
1.Is there any way I can either bypass this?
2.Is there any way I can check 'Allow unlock OEM' using fastboot or any other tool?
I have tried the following already,
1.tried to clear user data and cache with fastboot - Still remains the same
2.tried to flash a recovery image even though the boot-loader is locked - No Use.
3.contacted service centre just to realise that I have to change the PCB which will cost me a new phone!
Can anyone of you please help me out with this.
Thanks a Ton in Advance.
Click to expand...
Click to collapse
Bull**** about the PCB. Use RsdLite, had the same issue. Flash the latest package and use the USB at the back of the PC
kpamkar said:
Bull**** about the PCB. Use RsdLite, had the same issue. Flash the latest package and use the USB at the back of the PC
Click to expand...
Click to collapse
Hey Kpamkar,
I have tried it with RSD Lite, But no luck. on the RSD interface it says that flash failed,
On the mobile it says
version downgraded for primary_gpt
Can you please help me out with the latest stock rom for Moto x play, I am unable to get the exact stock rom any where, I have looked at this link: https://github.com/motoxplay/stock
My phone finger prints details are as follows(I got it with
HTML:
fastboot getvar all
command):
ro.build.fingerprint[0]: motorola/lux_retasia_ds/lux_uds:6.
ro.build.fingerprint[1]: 0.1/MPDS24.107-70-1-5/5:user/relea
ro.build.fingerprint[2]: se-keys
ON the phone these are the details that are shown:
baseband version:M8936_2020632.44,03.21.57R LUX_EMEA_DSDS_CUST
Product/Variant: LUX XT1562 32GB P2C
It wold be great if you could please share with me any kind of links that you have used which can guide me through this whole process.
Thanks a lot again!
pldeep said:
Hey Kpamkar,
I have tried it with RSD Lite, But no luck. on the RSD interface it says that flash failed,
On the mobile it says
version downgraded for primary_gpt
Can you please help me out with the latest stock rom for Moto x play, I am unable to get the exact stock rom any where, I have looked at this link: https://github.com/motoxplay/stock
My phone finger prints details are as follows(I got it with fastboot getvar all
command):
ro.build.fingerprint[0]: motorola/lux_retasia_ds/lux_uds:6.
ro.build.fingerprint[1]: 0.1/MPDS24.107-70-1-5/5:user/relea
ro.build.fingerprint[2]: se-keys
ON the phone these are the details that are shown:
baseband version:M8936_2020632.44,03.21.57R LUX_EMEA_DSDS_CUST
Product/Variant: LUX XT1562 32GB P2C
It wold be great if you could please share with me any kind of links that you have used which can guide me through this whole process.
Thanks a lot again!
Click to expand...
Click to collapse
In my case I had. 52 version of the ROM. I had a locked bootloader boot loop. But I was able to fix it using rsdLite. Are you using the latest version of the firmware and connecting the ports at the back of the pc? Also install proper drivers
You need to use RETASIA DS, the most recent version
@pldeep
firmware is here.
minimale_ldz said:
@pldeep
firmware is here.
Click to expand...
Click to collapse
Tried this. But no luck.
It still shows the same error "version downgrade for gpt_bin"
pldeep said:
Tried this. But no luck.
It still shows the same error "version downgrade for gpt_bin"
Click to expand...
Click to collapse
try flashing it without gpt.bin and bootloader
Try booting into twrp without flashing it. Use fastboot boot command
---------- Post added at 08:44 PM ---------- Previous post was at 08:29 PM ----------
pldeep said:
Tried this. But no luck.
It still shows the same error "version downgrade for gpt_bin"
Click to expand...
Click to collapse
What are you trying to flash?
Same problem over here... Did you solve it?
Downloading right now the latest rom image for Moto X Play from this site.... //firmware.center/firmware/Motorola/Moto%20X%20Play/Stock/XT1563/
Hey install Fastboot files and download twrp image for Lux and place it in the Fastboot folder.
Then run :- Fastboot reboot recovery.img
It will boot to twrp.
Any update for this? I'm in a similar situation now :-/
Tried RSD, it doesn't see my device (fastboot and adb works fine)
install Fastboot files and download twrp image for Lux and place it in the Fastboot folder.
Click to expand...
Click to collapse
How can I do that?
Also, someone mentioned emmc_chip reset - how to do that?
Thanks
Hello all! I have been trying to unlock my bootloader on my SGP311. I have searched the threads, followed the instructions, and still have problems. i initially looked at my service menu to determine if it is unlockable and it said yes. I then went through the steps to unlock it and it kept saying failed. Then, it finally worked, and my tablet rebooted. i got dual recovery loaded and then proceeded to wipe and install lineageOS from recovery. recovery kept failing to install the new rom. i then had to reflash a stock rom because the tablet wouldnt even boot into recovery again. now my service menu simply says rooting status: unknown and says nothing about the bootloader. What the heck happened?
Gilly86 said:
Hello all! I have been trying to unlock my bootloader on my SGP311. I have searched the threads, followed the instructions, and still have problems. i initially looked at my service menu to determine if it is unlockable and it said yes. I then went through the steps to unlock it and it kept saying failed. Then, it finally worked, and my tablet rebooted. i got dual recovery loaded and then proceeded to wipe and install lineageOS from recovery. recovery kept failing to install the new rom. i then had to reflash a stock rom because the tablet wouldnt even boot into recovery again. now my service menu simply says rooting status: unknown and says nothing about the bootloader. What the heck happened?
Click to expand...
Click to collapse
You can't install LOS Rom from the dual recovery (XZDR). By flashing stock ROM, you bootloader may be locked again.
Check this guide to unlock it, and install LOS.
It simply will not let me unlock the bootloader anymore. And I can't seem to find a firmware that I can flash to get me to the appropriate version
so far, part of the problem is flashtool in androxyde still using the command fastboot -i 0x0fce oem unlock 0xkey. windows 10 denies this command every time and should be fastboot oem unlock 0xkey. But even doing so manually through the cmd prompt, it still will not let me unlock the bootloader. does anyone have a ftf file that has an unlockable bootloader? seems mine locked up completely when i reflashed the rom
Gilly86 said:
so far, part of the problem is flashtool in androxyde still using the command fastboot -i 0x0fce oem unlock 0xkey. windows 10 denies this command every time and should be fastboot oem unlock 0xkey. But even doing so manually through the cmd prompt, it still will not let me unlock the bootloader. does anyone have a ftf file that has an unlockable bootloader? seems mine locked up completely when i reflashed the rom
Click to expand...
Click to collapse
bootloader is in device, not in firmware, so no such firmware exist you ask for.
Hi everyone,
Today I tried unlocking the bootloader on my Lenovo Z6 Pro to root my phone but I've hit a dead end.
I've enabled OEM unlocking and USB debugging on the developer options before using "adb reboot bootloader". I managed to get to bootloader mode alright, but neither "fastboot flashing unlock" nor "fastboot oem unlock-go" works; I always get "remote: flashing unlock is not allowed" or "remote: oem unlock is not allowed".
This makes it seem like I didn't enable OEM unlocking before, but I made sure it was enabled. Any ideas how I might solve this?
Hi,
First you have to get the sn.img file for unlocking your bootloader from the zui website. Reboot to bootloader, first flash the img file and then enter the command for unlocking. As far as I have tried, you have to use this image file every time you need to unlock the bootloader(if you have locked it)
Good luck
Sayi Keshkar said:
Hi,
First you have to get the sn.img file for unlocking your bootloader from the zui website. Reboot to bootloader, first flash the img file and then enter the command for unlocking. As far as I have tried, you have to use this image file every time you need to unlock the bootloader(if you have locked it)
Good luck
Click to expand...
Click to collapse
Thanks for the reply. I gave up rooting my device for a while but I got tired of my phone bugging all the time so decided to give it another shot. This time I have another problem and it's driving me crazy: ADB wouldn't detect my phone when it's connected so I still can't unlock my bootloader. I tried installing every driver I could find but nothing works, but I can transfer files through explorer just fine. It occured to me that the USB might be the problem but it's the exact same one I used the last time I tried rooting it and I didn't have this problem back then.