Since we have working TWRP for MHC19J build - HERE , I have one question about flashing MHC19J to my Nexus 5x.
Every month I'm flashing security updates this way:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Reboot to recovery
Flash the latest SuperSU
but in MHC19J build there is also a new bootloader - bootloader-bullhead-bhz10m.img and a new radio - radio-bullhead-m8994f-2.6.31.1.09.img . Do I need to flash this new bootloader and radio too? I assume yes, but I prefer ask first before RMA
New official TWRP build 3.0.0.1 released: https://dl.twrp.me/bullhead/
bmbm said:
Since we have working TWRP for MHC19J build - HERE , I have one question about flashing MHC19J to my Nexus 5x.
Every month I'm flashing security updates this way:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Reboot to recovery
Flash the latest SuperSU
but in MHC19J build there is also a new bootloader - bootloader-bullhead-bhz10m.img and a new radio - radio-bullhead-m8994f-2.6.31.1.09.img . Do I need to flash this new bootloader and radio too? I assume yes, but I prefer ask first before RMA
Click to expand...
Click to collapse
Yes. You need to flash the bootloader and radio because they have changed. When in doubt, flash all of them except for user data. I follow Heisenberg's directions (below).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Or you can type in "flash-all.bat" , yes this is less safe , but I have been doing this method since the day I got my Nexus 5X and I have never encountered any issue ever since ! This is the method recommended by google so ... And by the way thank you for posting the link to the new TWRP , I needed this
Rozalina340 said:
Or you can type in "flash-all.bat" , yes this is less safe , but I have been doing this method since the day I got my Nexus 5X and I have never encountered any issue ever since ! This is the method recommended by google so ... And by the way thank you for posting the link to the new TWRP , I needed this
Click to expand...
Click to collapse
Won't flash-all also write user data, thereby deleting everything? There's likely a reason that the experts on this forum have never recommended to use flash-all. If you follow Heisenberg's directions, everything will be fine, and you won't lose any data.
Edit: here's something stating that flash-all will erase data unless you modify the command.
http://9to5google.com/2015/10/05/ho...nexus-5-nexus-6-nexus-7-nexus-9-nexus-player/
I didn't know Heisenberg's method doesn't erase user's data. My bad then ^^
Sent from my Nexus 5X using Tapatalk
I've flashed the last two updates using flashfire from chainfire. It injects root during the process so twrp is easily installed using flashify. All without using PC (root is of course required for using flashfire)
Skickat från min Nexus 5X via Tapatalk
Related
Encountered this error message when trying to manually flash the N Dev 3 image, not via the flash-all bat. I'm very familiar when it comes to flashing images on my devices, fwiw.
I tried rebooting my PC, redownloading the image, and updating SDK Tools. No luck.
I've been able to reflash to mtc19t successfully.
My goal was to upgrade to the N Dev 3, then flash the decrypted modified N boot.img from Tigerstown in order to root.
Your fastboot is out of date or you have a bad download.
Sent from my SM-G930V using Tapatalk
Thanks. I'll give this a shot [TOOL]Minimal ADB and Fastboot [4-27-16]:
http://forum.xda-developers.com/showthread.php?t=2317790
bostonirishguy13 said:
Encountered this error message when trying to manually flash the N Dev 3 image, not via the flash-all bat. I'm very familiar when it comes to flashing images on my devices, fwiw.
I tried rebooting my PC, redownloading the image, and updating SDK Tools. No luck.
I've been able to reflash to mtc19t successfully.
My goal was to upgrade to the N Dev 3, then flash the decrypted modified N boot.img from Tigerstown in order to root.
Click to expand...
Click to collapse
You don't need to decrypt or flash a modified boot.img in order to root.
bobby janow said:
You don't need to decrypt or flash a modified boot.img in order to root.
Click to expand...
Click to collapse
Should have mentioned I'd prefer TWRP, too.
I ended up not using the unencrypted boot.img and rooted with CF Autoroot.
had same issue use fastboot from latest sdk
Hi I am new to the Nexus 5x and need assistance. I dont know what factory image from https://developers.google.com/android/images#bullhead I need if I have metro pcs. And every time I need to go into custom recovery do I need to flash it threw bootloader with the custom rom folder in the adb folder? Please someone help me I am really confused
HaxUrMom69 said:
Hi I am new to the Nexus 5x and need assistance. I dont know what factory image from https://developers.google.com/android/images#bullhead I need if I have metro pcs. And every time I need to go into custom recovery do I need to flash it threw bootloader with the custom rom folder in the adb folder? Please someone help me I am really confused
Click to expand...
Click to collapse
Factory images are universal for this device. All carriers are supported. Just flash the June factory image.
You can flash the boot, system, recovery, and vendor images through TWRP. Those same images can be flashed in the bootloader. Radio and bootloader images must be flashed in bootloader. Does that answer your question? If not, read my guide and see if that resolves your questions:
https://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Factory images are universal for this device. All carriers are supported. Just flash the June factory image.
You can flash the boot, system, recovery, and vendor images through TWRP. Those same images can be flashed in the bootloader. Radio and bootloader images must be flashed in bootloader. Does that answer your question? If not, read my guide and see if that resolves your questions:
https://forum.xda-developers.com/showthread.php?t=3206930
Click to expand...
Click to collapse
So when you install a new rom you don't need to flash the vendor image also? Because some ROMs say to also flash vendor image when installing a rom
tactical bacon said:
So when you install a new rom you don't need to flash the vendor image also? Because some ROMs say to also flash vendor image when installing a rom
Click to expand...
Click to collapse
This is covered in-depth with FAQ #9 of my link above. But in short, each monthly security update brings a new vendor image that must be installed. Each time your rom updates to a new month's security update, you need to install that vendor image. If you flash back to a previous month's rom, you need to flash that respective vendor image. Only exception is if your rom includes the vendor image in the rom zip.
Sent from my Nexus 5X using Tapatalk
Sorry one last question. I am on the latest security update stock, if I was to flash the latest AOSP extended on the latest security update all I would have to do is flash the ROM and gapps? But when the new security update is added to the ROM then I would flash the vendor image. Sorry if I'm asking to many questions but I don't want to run into a problem.
tactical bacon said:
Sorry one last question. I am on the latest security update stock, if I was to flash the latest AOSP extended on the latest security update all I would have to do is flash the ROM and gapps? But when the new security update is added to the ROM then I would flash the vendor image. Sorry if I'm asking to many questions but I don't want to run into a problem.
Click to expand...
Click to collapse
You're fine, ask away! Yes to both questions. Let's say the July security update is released for your custom rom. You would flash the July vendor.img then your rom and then that's it.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You're fine, ask away! Yes to both questions. Let's say the July security update is released for your custom rom. You would flash the July vendor.img then your rom and then that's it.
Click to expand...
Click to collapse
Just one more thing. I just realized there is no sd slot. where would I put the ROM and gapps
tactical bacon said:
Just one more thing. I just realized there is no sd slot. where would I put the ROM and gapps
Click to expand...
Click to collapse
I have my stuff in subfolders inside /sdcard
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
I have my stuff in subfolders inside /sdcard
Click to expand...
Click to collapse
Thanks for the help. I just flashed asop extended and everything works fine. Do you have a recommended ROM for stability?
Hi.
I rooted my M2 10 Wifi (A01W) with Kingroot and apparently now it's unroot (Magisk Manager said that). Even I made a factory reset.
I have the _B007 version and when I try to upgrade via OTA to _B008, it always fail and show "Failed to check the update files. Please download the package again".
I've working with ADB, Fastboot... and I could see that it's unroot, but the Bootloader is Unlock and I can't Relock it. Maybe it's the reason because the OTA doesn't work.
So I got a fastboot code with DC-UNLOCKER and tried to relock (fastboot oem relock CODE) and the answer was:
FAILED (Remote: root type is risk)
If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: RISK
change_time: xxxxxxxxx
Apparently, the Recovery is stock, with EMUI logo showing 3 options:
Reboot, Wipedata/factory reset and Wipe chache partition
I made the factory reset that way.
Any idea? Thanks.
ma2crmam said:
Hi.
I rooted my M2 10 Wifi (A01W) with Kingroot and apparently now it's unroot (Magisk Manager said that). Even I made a factory reset.
I have the _B007 version and when I try to upgrade via OTA to _B008, it always fail and show "Failed to check the update files. Please download the package again".
I've working with ADB, Fastboot... and I could see that it's unroot, but the Bootloader is Unlock and I can't Relock it. Maybe it's the reason because the OTA doesn't work.
So I got a fastboot code with DC-UNLOCKER and tried to relock (fastboot oem relock CODE) and the answer was:
FAILED (Remote: root type is risk)
If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: RISK
change_time: xxxxxxxxx
Apparently, the Recovery is stock, with EMUI logo showing 3 options:
Reboot, Wipedata/factory reset and Wipe chache partition
I made the factory reset that way.
Any idea? Thanks.
Click to expand...
Click to collapse
Well, I've read that flashing a system.img extracted from the UPDATE.APP I would can restore the Stock ROM... but I don't find a complete Stock ROM for Mediapad M2 10 Wifi (A01W).
I found the OTA in Romfirmware or Fordroid (sorry, I'm new user and I can not post external links). With this I can flash BOOT.img and RECOVERY.img, but the problem persist.
Does someone has any idea... or where can I get the complete Stock ROM?
Thanks!!!
ma2crmam said:
Well, I've read that flashing a system.img extracted from the UPDATE.APP I would can restore the Stock ROM... but I don't find a complete Stock ROM for Mediapad M2 10 Wifi (A01W).
I found the OTA in Romfirmware or Fordroid (sorry, I'm new user and I can not post external links). With this I can flash BOOT.img and RECOVERY.img, but the problem persist.
Does someone has any idea... or where can I get the complete Stock ROM?
Thanks!!!
Click to expand...
Click to collapse
Stokk ROM maybe available through a paid service by easy firmware. Got my LTE Stock ROM frim there. For the Wi-Fi edition you could first take a look here.
Sent from my HTC U11 using XDA Labs
5m4r7ph0n36uru said:
Stokk ROM maybe available through a paid service by easy firmware. Got my LTE Stock ROM frim there. For the Wi-Fi edition you could first take a look here.
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
Thanks!!! I didn't know that page. It's fine and does not look very expensive.
Just one more doubt.
The firmaware I need (as read on the tablet) is M2-A01w...B008 for West Europe
The firmware that the page shows is M2-A01w...B008CUSTC100D001
Do you know what CUSTC100D001 mean? Could I used it without problems?
ma2crmam said:
Thanks!!! I didn't know that page. It's fine and does not look very expensive.
Just one more doubt.
The firmaware I need (as read on the tablet) is M2-A01w...B008 for West Europe
The firmware that the page shows is M2-A01w...B008CUSTC100D001
Do you know what CUSTC100D001 mean? Could I used it without problems?
Click to expand...
Click to collapse
Glad it helped and yes it is not so expensive regarding the fact that there are all sorts of official firmware (mostly leaked ones) available for a lot of manufacturers.
The CUST reference at the end if the firmware version can be found in settings > about the tablet in the very last line. Mine is in German, So translated this line would state something like adapted/customized version. D001 is definitely Western Europe,this should be fine.
If not familiar how to install it google or search the forum for dload method. It will tell you what to do.
Sent from my HTC U11 using XDA Labs
I've done:
1. Get the correct firmware (version ...B007) and extract the RECOVERY.IMG and UPDATE.APP.
2. Flash the RECOVERY with Fastboot and install the UPDATE with the "dload" in the SD.
3. Reboot in RECOVERY MODE, wipe all and restore factory settings.
4. Then, the tablet was updated via OTA to the ...B008 version.
Then, positive:
1. The OTA works fine.
2. I was abble to install the Nextlix App and the HBO Spain App plays videos. Both didn't work before.
3. If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: SAFE
Then, negative:
1. I can't relock the Bootloader yet. When I try to relock (fastboot oem relock CODE) and the answer was again: FAILED (Remote: root type is risk)
Well, for normal use that's enough, but... THE RELOCK is becoming personal!!!
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!
Hi
I have google pixel 3 xl when I try to update July security patch upadat it's say there's no update my pixel is locked bootloader and no root it's original software and I buy it from Canada unlocked
OTA can take 2 weeks to be pushed to all devices
unlock oem bootloader in DEV options
fastboot
unlock device
flash image
reboot
if you want to keep all settings remove the -w in flash all
pacman photog said:
OTA can take 2 weeks to be pushed to all devices
unlock oem bootloader in DEV options
fastboot
unlock device
flash image
reboot
if you want to keep all settings remove the -w in flash all
Click to expand...
Click to collapse
Or just flash the OTA file using the stock recovery and it won't wipe either.
spotmark said:
Or just flash the OTA file using the stock recovery and it won't wipe either.
Click to expand...
Click to collapse
I found doing that sometimes creates issues with system.
Best to flash new image with -w
pacman photog said:
I found doing that sometimes creates issues with system.
Best to flash new image with -w
Click to expand...
Click to collapse
Hmm, interesting. That's the way I do it all the time. No problems. It's basically the same thing as receiving it OTA. I even installed Q4 that way, but in that case I had to wipe coming from Pie.
pacman photog said:
I found doing that sometimes creates issues with system.
Best to flash new image with -w
Click to expand...
Click to collapse
This method will wipe the device or no
If not can you show me the steps ?