I'm facing a weird problem with my wifi on nexus5x
I can only open/access wifi on just marshmallow 6.0.1 firmware which is MTC20K
I tried flashing around 6 different stock firmwares including the latest 4 oreo firmwares. On every firmware other than mtc20k i can't turn on wifi.
Any way to fix this on oreo or nougat?
Any one else having this issue?
Note : i have fixed BLOD. Is that the reason for this?
I don't think so you probably have bad vendor.img
kastik4 said:
I don't think so you probably have bad vendor.img
Click to expand...
Click to collapse
I tried flashing stock firmware via fastboot which includes vendor image right?
Hassan_Elyas said:
I tried flashing stock firmware via fastboot which includes vendor image right?
Click to expand...
Click to collapse
it does include vendor img but depends if it gets flashed you can try flashing it manually. Extract the vendor img from the zip and move it to the folder you have fastboot "installed" and flash it with the command fastboot flash vendor vendor.img if that doesn't help either maybe its because you're radio img doesn't match the firmware you have and you can re flash it with with the command fastboot flash radio radio-bullhead-yourfirmware'sradio.img you need to extract that to the fastboot folder too
kastik4 said:
it does include vendor img but depends if it gets flashed you can try flashing it manually. Extract the vendor img from the zip and move it to the folder you have fastboot "installed" and flash it with the command fastboot flash vendor vendor.img if that doesn't help either maybe its because you're radio img doesn't match the firmware you have and you can re flash it with with the command fastboot flash radio radio-bullhead-yourfirmware'sradio.img you need to extract that to the fastboot folder too
Click to expand...
Click to collapse
Will try tonight. Thanks.
did it work? i have the same issue
Didn't work for me I'm running 8.1 Oreo with June security patches. Also my MAC address is weird 02:00:00:00:00:00 never seen one like this.
Did you do a full firmware flash, or just boot and system?
Related
When I upgrade Cyanogenmod, I download the matching archive from here:
https://developers.google.com/android/nexus/images#bullhead
and do (with MTC20F for example):
flashboot flash bootloader bootloader-bullhead-bhz10r.img
flashboot flash radio radio-bullhead-m8994f-2.6.32.1.13.img
flashboot flash vendor vendor.img
Are there any other files I should be flashing such as boot.img?
xdadevelopersrocks said:
When I upgrade Cyanogenmod, I download the matching archive from here:
https://developers.google.com/android/nexus/images#bullhead
and do (with MTC20F for example):
flashboot flash bootloader bootloader-bullhead-bhz10r.img
flashboot flash radio radio-bullhead-m8994f-2.6.32.1.13.img
flashboot flash vendor vendor.img
Are there any other files I should be flashing such as boot.img?
Click to expand...
Click to collapse
No. Everything else is contained in the rom zip.
Sent from my Nexus 5X using Tapatalk
OK, is there a better way of figuring out which version to download from developers.google.com than watching the output from TWRP when installing a ROM?
xdadevelopersrocks said:
OK, is there a better way of figuring out which version to download from developers.google.com than watching the output from TWRP when installing a ROM?
Click to expand...
Click to collapse
The rom dev will inform you which Android base is installed if you read their changelog. Then you download that factory image from Google to flash vendor. Radio and bootloader are optional.
Sent from my Nexus 5X using Tapatalk
Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.
Nobody got the same problem? Maybe phone is damaged?
messiahxavier said:
Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.
Click to expand...
Click to collapse
messiahxavier said:
Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.
Click to expand...
Click to collapse
1. It's always hard to help without logs. Error codes are too unspecific
2. Check the mount settings, under the partition list there is an option for mounting /system as read only. It has to be disabled for installing custom ROMs.
Found something intresting,when I flash twrp without any problem and boot to system...then again tomorrow recovery via hardbuttons over bootloader there comes stock recovery????what ist that? Not able to go to twrp,only after new flash in fastboot.
Then you didn't flash it but just boot it
Hi bro.
I did face same problem here.
Follow the below steps:
Take download a nougat firmware, currently the "NPNS26.118-22-1"
Enter fastboot mode and type these comands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
You can do on any rom. For example: You are on AEx nougat, enter fastboot mode and type the comands above.
I hope that helped you.
tiago1966 said:
Hi bro.
I did face same problem here.
Follow the below steps:
Take download a nougat firmware, currently the "NPNS26.118-22-1"
Enter fastboot mode and type these comands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
You can do on any rom. For example: You are on AEx nougat, enter fastboot mode and type the comands above.
I hope that helped you.
Click to expand...
Click to collapse
Current firmware is 118-22-2-17! Older builds could lead to downgrade issues!
http:
//imgur.com/a/
W8Hb3SW
new user, can't attach imgs yet.
Got this phone to fix. Flashed latest firmware but no luck after a few different tries... Only this time it starts booting up with the animation and after a few seconds goes back to fastboot.
If anyone can help I'm thankful.
gabrielizador said:
http:
//imgur.com/a/
W8Hb3SW
new user, can't attach imgs yet.
Got this phone to fix. Flashed latest firmware but no luck after a few different tries... Only this time it starts booting up with the animation and after a few seconds goes back to fastboot.
If anyone can help I'm thankful.
Click to expand...
Click to collapse
You need to flash your proper firmware. Which model are you? (xt1952-?) I also need to know your carrier and country. I'll link the right firmware for you.
it's the xt1952-2, I flashed the latest firmware available for it from lolinet.
it's from brazil and has no carrier.
gabrielizador said:
it's the xt1952-2, I flashed the latest firmware available for it from lolinet.
it's from brazil and has no carrier.
Click to expand...
Click to collapse
The firmware on the lolinet seems to be the latest.
How did you try to flash the firmware? As long as the bootloader is locked the most devices only accept to flash the complete firmware images. They should be flashed in the same order as listed in flashfile.xml inside the zip.
WoKoschekk said:
The firmware on the lolinet seems to be the latest.
How did you try to flash the firmware? As long as the bootloader is locked the most devices only accept to flash the complete firmware images. They should be flashed in the same order as listed in flashfile.xml inside the zip.
Click to expand...
Click to collapse
I don't know much about how to use ADB, I got it from a stockrom, that had a tutorial on how to fix failed startups.
https://drive.google
.com/file/d/1G8AeMUfFbAroan5S1mpojyMYpUvKsR1N/view?usp=drivesdk
I just threw these files onto the firmware's files' folder.
How do I flash It in the correct order?
1. install ADB/Fastboot tools
https://forum.xda-developers.com/showthread.php?t=2317790
2. boot into bootloader (when power off, hold Vol- and power) and connect the device to your PC
3. A short introduction to ADB/fastboot:
While in bootloader menu you can only use the command "fastboot + <options>" to communicate with the device. Type
Code:
fastboot help
to show the options for this tool.
First of all extract the whole firmware zip into the ADB/fastboot folder on your PC. Copy also the attachment into this folder.
In this file you'll find all the flash commands you need to flash the new firmware. I extracted them from your current firmware .zip for the build no. QPYS30.52-22-2.
Run it as a batch script on your Windows cmd line by typing
Code:
bat flashfile.txt
. The other option would be to run all the commands manually.
As you can see in the script the "HLOS issue" affects your modem partition. At least you need to flash the NON-HLOS.bin to it. But I guess it wouldn't be possible to flash only this single partition while your bootloader is locked.
That's all. Good luck!!
the attachment...
gabrielizador said:
it's the xt1952-2, I flashed the latest firmware available for it from lolinet.
it's from brazil and has no carrier.
Click to expand...
Click to collapse
You're RETBR if you have no carrier branding. This firmware should work for you.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
After reverting back to stock miui from evolution x android 13 the persist partition was corrupted. I extracted the persist.img file from fastboot rom and flashed it in twrp then I flashed the lastest global miui and locked the bootloader. But safetynet is not passing and device is not sertified in playstore. How can I fix it? I don't have a backup of persist partition.
Arsenij12 said:
After reverting back to stock miui from evolution x android 13 the persist partition was corrupted. I extracted the persist.img file from fastboot rom and flashed it in twrp then I flashed the lastest global miui and locked the bootloader. But safetynet is not passing and device is not sertified in playstore. How can I fix it? I don't have a backup of persist partition.
Click to expand...
Click to collapse
Flash fastboot stock rom with xiaomitools or trough .bat file you'll find extracting rom from downloaded fastboot file
bozinsky73 said:
Flash fastboot stock rom with xiaomitools or trough .bat file you'll find extracting rom from downloaded fastboot file
Click to expand...
Click to collapse
I have already done it. The problem is still here
Arsenij12 said:
I have already done it. The problem is still here
Click to expand...
Click to collapse
Have u used flash_all.bat?
I use to reload the bootloader later, with a CMD session
I used flash_all_lock.bat
May it be an attestation keys lost?
removed
I found on another page here the CPH2451 patched A07 boot. I followed all the directions to the letter. I have done this on my OP8Pro many times. After flashing init_boot (fastboot flash init_boot patched.boot.img) I'm now in a bootloop. I reset first the didn't setup anything after update to A07. Any help would be appreciated.
Anyone have another boot.img that's patched or maybe the stock boot?
I'm waiting for this as well
have you tried changing your active slot to the other one and see if you can boot?
use fastboot to see which slot you are on, then set it as the other and reboot
this will get your current slot
Code:
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.034s
set your active slot opposite of what you are currently on (slot b)
Code:
fastboot set_active a
if you are on b, set it to a
if you are on a, set it to b
give that a try and see if you can boot. you can revert it back it it doesnt help. worth a shot though.
shootind5nukes said:
I found on another page here the CPH2451 patched A07 boot. I followed all the directions to the letter. I have done this on my OP8Pro many times. After flashing init_boot (fastboot flash init_boot patched.boot.img) I'm now in a bootloop. I reset first the didn't setup anything after update to A07. Any help would be appreciated.
Anyone have another boot.img that's patched or maybe the stock boot?
Click to expand...
Click to collapse
You didn't by chance flash a patched boot.img to your init_boot partition did you? That could very well cause a soft brick. For rooting, you would need to patch init_boot and flash to init_boot.
Init_boot isn't the same as boot.
H4X0R46 said:
You didn't by chance flash a patched boot.img to your init_boot partition did you? That could very well cause a soft brick. For rooting, you would need to patch init_boot and flash to init_boot.
Init_boot isn't the same as boot.
Click to expand...
Click to collapse
I was very careful not to do that.
You flashed to boot not init_boot you need to reflash the boot.img to boot partition then boot your phone. Then you can go back and fastboot flash init_boot_a magisk_patched_init_boot.img
Then the same to init_boot_b do it to both slots you can extract the boot image with payload dumper and flash it to boot partition that should get you back running
shootind5nukes said:
I found on another page here the CPH2451 patched A07 boot. I followed all the directions to the letter. I have done this on my OP8Pro many times. After flashing init_boot (fastboot flash init_boot patched.boot.img) I'm now in a bootloop. I reset first the didn't setup anything after update to A07. Any help would be appreciated.
Anyone have another boot.img that's patched or maybe the stock boot?
Click to expand...
Click to collapse
shootind5nukes said:
I was very careful not to do that.
Click to expand...
Click to collapse
Both slots need to be flashed the init_boot read my post
shootind5nukes said:
I was very careful not to do that.
Click to expand...
Click to collapse
Somehow you screwed up the boot partition that's why it won't boot
str8str said:
You flashed to boot not init_boot you need to reflash the boot.img to boot partition then boot your phone. Then you can go back and fastboot flash init_boot_a magisk_patched_init_boot.img
Then the same to init_boot_b do it to both slots you can extract the boot image with payload dumper and flash it to boot partition that should get you back running
Click to expand...
Click to collapse
I assure you I did not flash to boot. I am the type that reads instructions 100 times. I know I must have did something wrong but it wasn't that.
https://www.droidwin.com/msm-download-tool-read-back-mode-create-oneplus-backup/
If you want to back up so you have all the bace files your phone will still connect to the MSM tool and you don't need to unlock the bootloader and you can extract every partition this way you can use the fast food tool to flash your phone this increases the recovery and boot image you don't need the payload.bin file
AkayamiShurui said:
https://www.droidwin.com/msm-download-tool-read-back-mode-create-oneplus-backup/
If you want to back up so you have all the bace files your phone will still connect to the MSM tool and you don't need to unlock the bootloader and you can extract every partition this way you can use the fast food tool to flash your phone this increases the recovery and boot image you don't need the payload.bin file
Click to expand...
Click to collapse
I forgot to mention this does work on bricked devices
Anybody with a corrupt boot.img that needs a factory one...
Does this one work ?
I would think it would work?
as it's a generic kernel image.
https://dl.google.com/android/gki/gki-certified-boot-android13-5.15-2023-02_r1.zip
shootind5nukes said:
I found on another page here the CPH2451 patched A07 boot. I followed all the directions to the letter. I have done this on my OP8Pro many times. After flashing init_boot (fastboot flash init_boot patched.boot.img) I'm now in a bootloop. I reset first the didn't setup anything after update to A07. Any help would be appreciated.
Anyone have another boot.img that's patched or maybe the stock boot?
Click to expand...
Click to collapse
Well if you trying to update to A.08 don't try flashing the boot.img I, I tried everything too and almost bricked my phone twice. if rooted you can't update with incremental updates in the USA ROM you only can do that with the EU ROM because they get a full ROM every time.
So I downloaded the EU ROM using oxygen updater App from play store then I used the OPLocalUpdate_For_Android12 App to force the update locally. The EU ROM looks the same to me so far but when we get a full ROM update in USA will switch back. Hope that helps