Related
Hi guys, my nexus 5x is locked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
MaxOptim said:
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
Click to expand...
Click to collapse
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
ybregeon2016 said:
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
Click to expand...
Click to collapse
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
MaxOptim said:
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
Click to expand...
Click to collapse
Forgive my ignorance but how can I do this?
ybregeon2016 said:
Forgive my ignorance but how can I do this?
Click to expand...
Click to collapse
follow instructions here: https://developers.google.com/android/ota
MaxOptim said:
follow instructions here: https://developers.google.com/android/ota
Click to expand...
Click to collapse
Actually I was talking about the RMA, I bought it in Egypt.
ybregeon2016 said:
Actually I was talking about the RMA, I bought it in Egypt.
Click to expand...
Click to collapse
ah, no idea then, sorry.
ybregeon2016 said:
Hi guys, my nexus 5x is unlocked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
Click to expand...
Click to collapse
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
dominoeflux said:
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Click to expand...
Click to collapse
Man i remind you that my bootloader is locked and for this reason can't start twrp.
ybregeon2016 said:
Man i remind you that my bootloader is locked and for this reason can't start twrp.
Click to expand...
Click to collapse
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
dominoeflux said:
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
Click to expand...
Click to collapse
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
ybregeon2016 said:
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
Click to expand...
Click to collapse
Oohhh OK I got you...have you been able to look in doing a tot recovery with Odin? I'm almost home so I'll see what I can do to help u out
Edit: have u tried unlocking it again in bootloader?
LGUP install a firmware as a TOT, it was a TOT file. Isnt Odin for Samsung phones?
tauio111 said:
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
Click to expand...
Click to collapse
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
ybregeon2016 said:
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
Click to expand...
Click to collapse
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
tauio111 said:
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
Click to expand...
Click to collapse
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
ybregeon2016 said:
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
Click to expand...
Click to collapse
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
tauio111 said:
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
Click to expand...
Click to collapse
Failed (remote: OEM unlock is not allowed)
Hey guys. Today I tried rooting for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for an encryption password(I hadn't put one yet). I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
porthumor said:
Hey guys. Today I tried boot for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for a password. I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
Click to expand...
Click to collapse
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Kap_Tutan said:
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Click to expand...
Click to collapse
Tried this . It displays :
"Your device has been unlocked and cannot be trusted.
ID: bad key"
Reboots to show :
"Your device has been unlocked and cannot be trusted.
ID: N/A"
and goes into TWRP .
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
mijing said:
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
Click to expand...
Click to collapse
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
mijing said:
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
Click to expand...
Click to collapse
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
porthumor said:
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
Click to expand...
Click to collapse
Are you sure OS is even there?
flashallthetime said:
Are you sure OS is even there?
Click to expand...
Click to collapse
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
porthumor said:
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
Click to expand...
Click to collapse
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
flashallthetime said:
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
Click to expand...
Click to collapse
Yes,exactly.
flashallthetime said:
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Click to expand...
Click to collapse
Which Custom ROM do you think is the safest possible alternative?
flashallthetime said:
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
Click to expand...
Click to collapse
Can you explain this a bit better ? I would like to understand what i'm getting into !
flashallthetime said:
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
Click to expand...
Click to collapse
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
porthumor said:
Yes,exactly.
Which Custom ROM do you think is the safest possible alternative?
Can you explain this a bit better ? I would like to understand what i'm getting into !
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
Click to expand...
Click to collapse
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
flashallthetime said:
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
Click to expand...
Click to collapse
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
porthumor said:
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
Click to expand...
Click to collapse
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
flashallthetime said:
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
Click to expand...
Click to collapse
I'll try to get this done by tomorrow and see if it helps !
porthumor said:
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
I'll try to get this done by tomorrow and see if it helps !
Click to expand...
Click to collapse
Hopefully it does
flashallthetime said:
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Click to expand...
Click to collapse
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Kap_Tutan said:
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Click to expand...
Click to collapse
You also need to flash the recovery image as well
I flashed the wrong bootloader so fastboot does not work. I still have TWRP Working but anything I flash does not boot. I am looking for a full factory OTA that I can flash via TWRP so it will re-flash the proper bootloader and all the other factory images so I can un-brick it through fastboot. I have tried to flash many different update files but it gives an error 7 and says to be on 6.0.1 or 7.0 before installing it. Can someone please help me un-brick this or link a full OTA that I can flash via TWRP. I attached the bootloader.img so if anyone could make a flashable zip to flash the stock bootloader that would probably work.
vibraniumdroid said:
I flashed the wrong bootloader so fastboot does not work. I still have TWRP Working but anything I flash does not boot. I am looking for a full factory OTA that I can flash via TWRP so it will re-flash the proper bootloader and all the other factory images so I can un-brick it through fastboot. I have tried to flash many different update files but it gives an error 7 and says to be on 6.0.1 or 7.0 before installing it. Can someone please help me un-brick this or link a full OTA that I can flash via TWRP. I attached the bootloader.img so if anyone could make a flashable zip to flash the stock bootloader that would probably work.
Click to expand...
Click to collapse
Follow this discussion.
"https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492"
ROM_HUNTER said:
Follow this discussion.
"https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492"
Click to expand...
Click to collapse
does not work
vibraniumdroid said:
does not work
Click to expand...
Click to collapse
If fastboot works then you're not hard bricked, most likes soft brick. I would suggest flashing magisks 14 after you flash the rom as dm-verity will check if your system is modified , dm-verity needs to be disabled
flashallthetime said:
If fastboot works then you're not hard bricked, most likes soft brick. I would suggest flashing magisks 14 after you flash the rom as dm-verity will check if your system is modified , dm-verity needs to be disabled
Click to expand...
Click to collapse
I already tried flashing magisk. Also I can boot into the bootloader but the computer does not see it in fastboot anymore (probably because I flashed the bootloader.img for the moto z play droid accidentally)
vibraniumdroid said:
I already tried flashing magisk. Also I can boot into the bootloader but the computer does not see it in fastboot anymore (probably because I flashed the bootloader.img for the moto z play droid accidentally)
Click to expand...
Click to collapse
Hard bricked for sure
flashallthetime said:
Hard bricked for sure
Click to expand...
Click to collapse
not exactly because twrp works. If I could flash fastboot images through TWRP I could un-brick it. If somebody could modify the stock rom's updater-script and remove the requirement to be running a stock rom then I could flash that and I would probably be unbricked.
vibraniumdroid said:
not exactly because twrp works. If I could flash fastboot images through TWRP I could un-brick it. If somebody could modify the stock rom's updater-script and remove the requirement to be running a stock rom then I could flash that and I would probably be unbricked.
Click to expand...
Click to collapse
Bootloader can not be flashed through twrp so you'll need to flash the bootloader through fastboot. If your device is not recognized when you plug it in your computer then you're hard bricked, if fastboot is not accessable then you're hard bricked
flashallthetime said:
Bootloader can not be flashed through twrp so you'll need to flash the bootloader through fastboot. If your device is not recognized when you plug it in your computer then you're hard bricked, if fastboot is not accessable then you're hard bricked
Click to expand...
Click to collapse
so you are sure that it is impossible to make a flashable zip of bootloader. Maybe it is just my computer I'll try booting of linux on usb and then see if fastboot can see it.
flashallthetime said:
Bootloader can not be flashed through twrp so you'll need to flash the bootloader through fastboot. If your device is not recognized when you plug it in your computer then you're hard bricked, if fastboot is not accessable then you're hard bricked
Click to expand...
Click to collapse
how do you fix a hardbrick?
vibraniumdroid said:
how do you fix a hardbrick?
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
flashallthetime said:
Here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
Click to expand...
Click to collapse
I tried that does not work:crying: also I got windows to see the phone as addison fastboot s but when i do fastboot devices it does not show up
vibraniumdroid said:
I tried that does not work:crying: also I got windows to see the phone as addison fastboot s but when i do fastboot devices it does not show up
Click to expand...
Click to collapse
Do you have the correct driver,, if you use Linux there is no need for the driver just install minimal ADB and fastboot
vibraniumdroid said:
I tried that does not work:crying: also I got windows to see the phone as addison fastboot s but when i do fastboot devices it does not show up
Click to expand...
Click to collapse
Have you tried using these albus (Z2 Play) blank flashes as mentioned here to repair your bootloader? https://forum.xda-developers.com/showpost.php?p=73402033&postcount=181
https://forum.xda-developers.com/showpost.php?p=73411048&postcount=206
These may hopefully get your device to the point where it's recognised in fastboot and you can then flash the stock ROM via fastboot.
vibraniumdroid said:
how do you fix a hardbrick?
Click to expand...
Click to collapse
You don't. That's why it's called a hard brick.
flashallthetime said:
Do you have the correct driver,, if you use Linux there is no need for the driver just install minimal ADB and fastboot
Click to expand...
Click to collapse
booted of linux from a usb and that worked thanks
Im getting very frustrate sorry for this message if its to mush to ask for
i have Oneplus 7T
and the bootloader is unlocked
I installe the lateste update OS OxygenOS 10.0.8 (EU)
And what to root it with magisk and i cant flash it in anyway i try to with cmd
So i need some help to get it to work .anyone in here that have the time to send me a guide
there are so many and i cant get to work
So what i need is a easy guide that show me how to do it step by step
zagget said:
Im getting very frustrate sorry for this message if its to mush to ask for
i have Oneplus 7T
and the bootloader is unlocked
I installe the lateste update OS OxygenOS 10.0.8 (EU)
And what to root it with magisk and i cant flash it in anyway i try to with cmd
So i need some help to get it to work .anyone in here that have the time to send me a guide
there are so many and i cant get to work
So what i need is a easy guide that show me how to do it step by step
Click to expand...
Click to collapse
So where are you stuck?
Let's go step by step:
So you have unlocked the bootloader and now you have the stock boot img for you rom patched?
Have you tried to install the patched img through adb?
Fastboot flash boot nameofimg.img
Make sure is the patched img.
Once you do that you have to go to magisk web site https://******************/ download the lastest apk.
Install remember to allow your browser to install unknown apps.
Once that happens magisk Wil tell you that it needs to install some extra things let it do it and it will reboot.
I know you said you tried it but in this guide you also get the patched boot img.
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
lil_kujo said:
So where are you stuck?
Let's go step by step:
So you have unlocked the bootloader and now you have the stock boot img for you rom patched?
Have you tried to install the patched img through adb?
Fastboot flash boot nameofimg.img
Make sure is the patched img.
Once you do that you have to go to magisk web site https://******************/ download the lastest apk.
Install remember to allow your browser to install unknown apps.
Once that happens magisk Wil tell you that it needs to install some extra things let it do it and it will reboot.
I know you said you tried it but in this guide you also get the patched boot img.
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Click to expand...
Click to collapse
The bootloader is onlocked YES
Im not sure about the ADB i dont now how it works ? I use to flash my OnePlus fon with cmd and before that twrp
And yes i have tryed fastboot and all you write , even with one patched img from my fon and dig from in here It wont work
zagget said:
The bootloader is onlocked YES
Im not sure about the ADB i dont now how it works ? I use to flash my OnePlus fon with cmd and before that twrp
And yes i have tryed fastboot and all you write , even with one patched img from my fon and dig from in here It wont work
Click to expand...
Click to collapse
when in fastboot if you write fastboot device does it show the number I'd of your device?
Also under developer option I guess you have advance reboot turned on and USB debugging on.?
Hey
lil_kujo said:
when in fastboot if you write fastboot device does it show the number I'd of your device?
Also under developer option I guess you have advance reboot turned on and USB debugging on.?
Click to expand...
Click to collapse
Sorry for the late repley
it show my Fon in fast boot
And i have set all things in dev like you say
it still will no accept any installing ??
I have magisk made a boot.img with magisk and put in my pc , and still the fastboot do nothing ???
Sorry for me being such a fool and for all my Q
Maybe its better to reset the Fon and punt on the lataest firmware and start from the begining ?
zagget said:
Sorry for the late repley
it show my Fon in fast boot
And i have set all things in dev like you say
it still will no accept any installing ??
I have magisk made a boot.img with magisk and put in my pc , and still the fastboot do nothing ???
Sorry for me being such a fool and for all my Q
Maybe its better to reset the Fon and punt on the lataest firmware and start from the begining ?
Click to expand...
Click to collapse
Place the boot.img in the fastboot folder file. What I had to do since I had downloaded this fastboot zip but it was two in one, forgot the name but I had to put the boot.img into the file folder of fastboot so when I open adb or whatever it will detect the boot.img file.
As Yelloman said you do have to put the img file in the Fastboot folder in order for it to transfer the img to your device.
I have unlocked bootloader for my Oneplus 7t. Can someone guide me from here?
Thanks for your repleys both of you two guy and i got to work now . thansk for your Help
-X3RX3S- said:
I have unlocked bootloader for my Oneplus 7t. Can someone guide me from here?
Click to expand...
Click to collapse
There is a forum on xda about it or just read this one. You should head first to the original thread.
zagget said:
Im getting very frustrate sorry for this message if its to mush to ask for
i have Oneplus 7T
and the bootloader is unlocked
I installe the lateste update OS OxygenOS 10.0.8 (EU)
And what to root it with magisk and i cant flash it in anyway i try to with cmd
So i need some help to get it to work .anyone in here that have the time to send me a guide
there are so many and i cant get to work
So what i need is a easy guide that show me how to do it step by step
Click to expand...
Click to collapse
Did u fastboot oem unlock, or did you use a different method?
can someone please help me or send me some service to unbrick my nubia?
i can pay
What's happened?
Stusick said:
What's happened?
Click to expand...
Click to collapse
i try to root the phone and now it's in corrupted file and when i press power to continue he show the logo of red magic and thats it
i can enter to fastboot mode but nothing help
How did you root your phone? Rooting the phone is as simple as flashing patched init_boot.img via fastboot flash init_boot. A lot of users here brick their phones because they patched and flashed the boot.img instead of the init_boot.img.
yakir150 said:
i can enter to fastboot mode but nothing help
Click to expand...
Click to collapse
If you can enter fastboot you can still fix..flash your original boot.img from fastboot.
fastboot flash boot boot.img
batuken said:
How did you root your phone? Rooting the phone is as simple as flashing patched init_boot.img via fastboot flash init_boot. A lot of users here brick their phones because they patched and flashed the boot.img instead of the init_boot.img.
Click to expand...
Click to collapse
yeah so did i also flash boot.img instead init_boot.img
but it's ok now
someone help me remotely and fix it
yakir150 said:
yeah so did i also flash boot.img instead init_boot.img
but it's ok now
someone help me remotely and fix it
Click to expand...
Click to collapse
If this is a paid service could you please give me the information so I can fix my phone. Thanks.
[email protected] said:
If this is a paid service could you please give me the information so I can fix my phone. Thanks.
Click to expand...
Click to collapse
Viet nam ah
izsdeaman said:
Viet nam ah
Click to expand...
Click to collapse
I am a Vietnamese and I live in California USA.
yakir150 said:
yeah so did i also flash boot.img instead init_boot.img
but it's ok now
someone help me remotely and fix it
Click to expand...
Click to collapse
So flashing stock boot.img with fastboot wouldn't fix?
JWnSC said:
So flashing stock boot.img with fastboot wouldn't fix?
Click to expand...
Click to collapse
i didnt try it i just talk to some service and pay ^_^
yakir150 said:
i didnt try it i just talk to some service and pay ^_^
Click to expand...
Click to collapse
Could you please give me the information to contact this service. Thanks.
Mod Edit: Quoted Post Removed
I buy and he fix
Price please and tag room share some more info please
Mod Edit: Quoted Post Removed
Have you seen which programs were used?
aaa.bbb111222 said:
Have you seen which programs were used?
Click to expand...
Click to collapse
He used miflash, QFIL (with various different parameters than normal use), QFL, and fastboot. Finally he recreated two super partitions for my phone and flash odm, system, and vendor images into the supper partitions. After 4 hr of trying, my phone boots however I still have the red warning "Your phone is corrupt".
[email protected] said:
He used miflash, QFIL (with various different parameters than normal use), QFL, and fastboot. Finally he recreated two super partitions for my phone and flash odm, system, and vendor images into the supper partitions. After 4 hr of trying, my phone boots however I still have the red warning "Your phone is corrupt".
Click to expand...
Click to collapse
lock bootloader and flash full rom
izsdeaman said:
lock bootloader and flash full rom
Click to expand...
Click to collapse
how do you flash a full rom?
yakir150 said:
how do you flash a full rom?
Click to expand...
Click to collapse
Put the rom in the root directory or on external SD card through the C connector. Use local update and choose the rom.