Hi everyone,
I flashed pixel rom and my bootloader has changed to that of pixel with all the white and new icons.
Is there a way that i can revert back to the old black bootloader that came out of the box. I wish to come back to the old hence the new one doesn't seem to have access to the adb
Thanks,
Charles
Flash bootloader from latest factory img.
icrunchbanger said:
Flash bootloader from latest factory img.
Click to expand...
Click to collapse
via TWRP?
charlesco29.cc said:
via TWRP?
Click to expand...
Click to collapse
No. Via bootloader. After -flash bootloader bootloader.img-
Do a reboot and you are done.
How to go back to stock.. Please helppppp?? The new bootloader in this rom doesnot allow me to flash stock image. Help pleaseeee
Do you have fastboot working? If yes, simply flash sock ROM via fastboot: https://developers.google.com/android/images
If no, maybe flashing TOT can help you (I didn't test): https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Related
Got the update at 2am, posting it so maybe custom roms can get WiFi calling, feel free to mirror just asking you keep them in the thread.
https://docs.google.com/file/d/0B7lAMKoPVdWKU1VfSnRNZS10Zjg/edit?usp=docslist_api
would i be able to just flash this if i wanted to with twrp. just curious.
Android6190 said:
would i be able to just flash this if i wanted to with twrp. just curious.
Click to expand...
Click to collapse
Twrp won't have the decryption keys or some of the HTC specific functions required to apply the OTA. You'll need a stock /system and a stock recovery.
dang. okay
T-Mobile US 4.20.531.4 firmware
Here is the new T-Mobile US firmware from today with the recovery and boot.img removed, just need someone to do their magic and remove red text.
https://dl.dropboxusercontent.com/u/...4/firmware.zip
do we just flash in twrp? Thank you by the way
No it's a stock ota you have to use HTC recovery.
rubyman94 said:
do we just flash in twrp? Thank you by the way
Click to expand...
Click to collapse
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
bradley_e_smith said:
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
Click to expand...
Click to collapse
Umm... your Firmware file is corrupted
Azuske said:
Umm... your Firmware file is corrupted
Click to expand...
Click to collapse
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
bradley_e_smith said:
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
Click to expand...
Click to collapse
I mean it could be my computer but it keeps saying its corrupted when I download it.
Azuske said:
Umm... your Firmware file is corrupted
Click to expand...
Click to collapse
It's not, it's encrypted.
bradley_e_smith said:
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
Click to expand...
Click to collapse
gamer765 said:
It's not, it's encrypted.
Click to expand...
Click to collapse
Oh, well it won't let me put it on my device because the computer thinks it's corrupted
Fenny said:
Twrp won't have the decryption keys or some of the HTC specific functions required to apply the OTA. You'll need a stock /system and a stock recovery.
Click to expand...
Click to collapse
Would this explain the error that I'm getting?
Package expects build fingerprint of htc/tmous/htc_m8:4.4.4/KTU84P/396641.2:user/release-keys or htc/tmous/htc_m8:5.0.1/htc_m8: 5.0.1/LRX22C/464190.4:user/release-keys.; this device has htc/tmous/htc_m8:4.4.3/KTU84L/365360.5/user/release-keys.
I flashed stock recovery, but my phone is still root. Did a full wipe/restore, still getting same thing. The error looks like it's not happy about a missing update perhaps, if I'm reading that correctly. Best I know, I have the latest kitkat version. But, I've had twrp for awhile so maybe I missed an OTA update along the way.
cyclonesworld said:
Would this explain the error that I'm getting?
Package expects build fingerprint of htc/tmous/htc_m8:4.4.4/KTU84P/396641.2:user/release-keys or htc/tmous/htc_m8:5.0.1/htc_m8: 5.0.1/LRX22C/464190.4:user/release-keys.; this device has htc/tmous/htc_m8:4.4.3/KTU84L/365360.5/user/release-keys.
I flashed stock recovery, but my phone is still root. Did a full wipe/restore, still getting same thing. The error looks like it's not happy about a missing update perhaps, if I'm reading that correctly. Best I know, I have the latest kitkat version. But, I've had twrp for awhile so maybe I missed an OTA update along the way.
Click to expand...
Click to collapse
If you're SOFF and supercid just flash the lollipop ruu T-Mobile just release. It doesn't matter what previous rom you're on. Then reflash custom recovery and rooted. I've done this alot of time already.
bradley_e_smith said:
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
Click to expand...
Click to collapse
So the steps would be:
- Flash stock recovery via fastboot
- Flash firmware via fastboot
- Flash twrp via fastboot
- Flash Lollipop via twpr
Is this correct?
rickpref said:
So the steps would be:
- Flash stock recovery via fastboot
- Flash firmware via fastboot
- Flash twrp via fastboot
- Flash Lollipop via twpr
Is this correct?
Click to expand...
Click to collapse
For me (I am s-on) I did it in this order:
- flashed twrp stock rom
- rebooted and made sure the rom worked
- flashed stock recovery via fastboot
- rebooted and downloaded and installed OTA.
If you are s-off I believe (someone correct me if I am wrong) you can use the RUU instead.
I did have a wifi issue which was solved by a factory wipe ( yes I had to re-install and setup the phone again).
-brad
bradley_e_smith said:
For me (I am s-on) I did it in this order:
- flashed twrp stock rom
- rebooted and made sure the rom worked
- flashed stock recovery via fastboot
- rebooted and downloaded and installed OTA.
If you are s-off I believe (someone correct me if I am wrong) you can use the RUU instead.
I did have a wifi issue which was solved by a factory wipe ( yes I had to re-install and setup the phone again).
-brad
Click to expand...
Click to collapse
Wow, that sounds much simpler, thanks...gonna try that now.
Radio
Any chance someone can please post a flashable zip with the new t-mo radio?
Where would I get the stock recovery for this fw and update. I want to root but keep my ota
Hey!
I have a Zenfone 2 ze550cl (Z00D) with cyanogenmod 12.1
I think i flashed something wrong from adb and now my bootloader mode don't work anymore :cyclops:, when i restart the phone in the bootloader mode it show me the cyanogenmod logo forever.
When i restart in normal mode i have no problem and the recovery mode (twrp 2.8.7.0) work fine too!!!! The problem is JUST the bootloader that i dunno how reinstall it. I can do all except enter in the bootloader mode.
Do u guys have some idea on how to reinstall the bootloader in my phone?
Thank you in Advice !!!!:laugh:
Flash stock recovery using twrp.
Boot to stock recovery and sideload stock firmware.
INDIAN-MAfIA said:
Flash stock recovery using twrp.
Boot to stock recovery and sideload stock firmware.
Click to expand...
Click to collapse
Thanks for the response,
Where i can find the stock recovery for my phone?
Giammaofwar said:
Thanks for the response,
Where i can find the stock recovery for my phone?
Click to expand...
Click to collapse
Either extract from the firmware zip
Or you'll find in the 'general' tab
When i extract the file from the zip firmware i found:
- ifwi.zip
-asusfw.img
-boot.img
-droidboot.img
......
Wich one of this file for restore the stock recovery mode?
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
Whats the process to flashing a custom rom on the pixel devices? i read something about having to flash stock first?
xSpartacusx said:
Whats the process to flashing a custom rom on the pixel devices? i read something about having to flash stock first?
Click to expand...
Click to collapse
Your bootloader, radio and vendor should match whatever ROM you want to flash.
Basically you should flash and boot March stock first, set up and set pin
Download rom, twrp installer zip
Remove screen lock pin
Fastboot boot (twrp.img)
Factory reset
Flash rom + twrp installer
Reboot system
If you want to flash a 9 based ROM like carbonrom you'll have to format userdata and flash and boot August factory image then repeat the steps above
Either way you should learn the fastboot commands and do things manually, it comes in handy updating both slots if needed.
oh yea i got it figured out! now, if i go back to stock from a custom rom, using the stock March image, will i still get OTA updates or will i need to flash through the OTA images that are provided?
xSpartacusx said:
oh yea i got it figured out! now, if i go back to stock from a custom rom, using the stock March image, will i still get OTA updates or will i need to flash through the OTA images that are provided?
Click to expand...
Click to collapse
You'll need to relock your bootloader, just make sure you're full stock on both slots or you will brick your phone. I personally don't think it's worth the risk and just update through twrp or fastboot
Hello, I am wondering if I can flash the stock boot.img again to de-root my device in case I want to go back. Is it also possible to reflash the entire stock rom again from fastboot? If not how would I go about doing that.
Drysauce said:
Hello, I am wondering if I can flash the stock boot.img again to de-root my device in case I want to go back. Is it also possible to reflash the entire stock rom again from fastboot? If not how would I go about doing that.
Click to expand...
Click to collapse
Yes flashing the original unpatched boot.img will unroot.
If you made any changes while rooted, they will remain and may cause issues,
sd_shadow said:
Yes flashing the original unpatched boot.img will unroot.
If you made any changes while rooted, they will remain and may cause issues,
Click to expand...
Click to collapse
Thank you for your quick response.
unrelated question, but I also plan on porting TWRP onto this phone too. Is there any chance of bricking my phone if I were to boot up a custom recovery from fastboot, not flash, but BOOT it? If its incompatible would it just default back into fastboot or something like that?
Drysauce said:
Thank you for your quick response.
unrelated question, but I also plan on porting TWRP onto this phone too. Is there any chance of bricking my phone if I were to boot up a custom recovery from fastboot, not flash, but BOOT it? If its incompatible would it just default back into fastboot or something like that?
Click to expand...
Click to collapse
Only booting it shouldn't cause anything.
Kuntitled said:
Only booting it shouldn't cause anything.
Click to expand...
Click to collapse
ok thank you