Related
Stock recovery image for AT&T HTC One (m7): recovery_m7_att_stock.img
Flash using 'fastboot flash recovery recovery_m7_att_stock.img'
cschmitt said:
Stock recovery image for AT&T HTC One (m7): recovery_m7_att_stock.img
Flash using 'fastboot flash recovery recovery_m7_att_stock.img'
Click to expand...
Click to collapse
Thanks for this , you are awesome!
cschmitt said:
Stock recovery image for AT&T HTC One (m7): recovery_m7_att_stock.img
Flash using 'fastboot flash recovery recovery_m7_att_stock.img'
Click to expand...
Click to collapse
cschmitt, Moved to the one from your skyrocket? Nice
tjsooley said:
cschmitt, Moved to the one from your skyrocket? Nice
Click to expand...
Click to collapse
Ah, you found me! Actually SR -> GNex -> One.
cschmitt said:
Ah, you found me! Actually SR -> GNex -> One.
Click to expand...
Click to collapse
How did you like the GNex?
As for the one I got it because all the gsm hardware is the same and as far as aosp is now we have a truly dev friendly platform and phone. All we need is s-off and super cid so we can have total control. the one may be the next HD2.
I need to return my device (defective) and did not nandroid the stock ROM before flashing Renovate.
Is it best to flash this recovery and unroot?
If so, do I just boot into fastboot (hold power and volume down) and adb file from pc to phone? Can I flash?
Or, should I flash the rooted stock ODEX ATT ROM that is available here?
Im a newb, Thanks for the help.
michael.s.under said:
I need to return my device (defective) and did not nandroid the stock ROM before flashing Renovate.
Is it best to flash this recovery and unroot?
If so, do I just boot into fastboot (hold power and volume down) and adb file from pc to phone? Can I flash?
Or, should I flash the rooted stock ODEX ATT ROM that is available here?
Im a newb, Thanks for the help.
Click to expand...
Click to collapse
Flash odex att then this recovery and relock that will get you as close to stock as we can without a ruu
tjsooley said:
Flash odex att then this recovery and relock that will get you as close to stock as we can without a ruu
Click to expand...
Click to collapse
Sweet!!! Thanks much. (Pushing the button!)
I basically wipe/reset, wipe cache, flash odex att from CWM. Reboot.
Then (power/volume down) to fastboot recovery, then flash this through adb on my PC? So I need to put this in the file on my PC, right?
And how do I relock? I will search for a thread unless you know of one.
Again, thanks very much.
michael.s.under said:
Sweet!!! Thanks much. (Pushing the button!)
I basically wipe/reset, wipe cache, flash odex att from CWM. Reboot.
Then (power/volume down) to fastboot recovery, then flash this through adb on my PC? So I need to put this in the file on my PC, right?
And how do I relock? I will search for a thread unless you know of one.
Again, thanks very much.
Click to expand...
Click to collapse
Just search in the international forum. I think the command is fastboot bootloader relock or something
Fastboot oem lock
Thanks for everything guys.
Would the combination of ATT odexed ROM and ATT stock recovery still get OTAs etc.?
michael.s.under said:
Thanks for everything guys.
Would the combination of ATT odexed ROM and ATT stock recovery still get OTAs etc.?
Click to expand...
Click to collapse
It should
tjsooley said:
Flash odex att then this recovery and relock that will get you as close to stock as we can without a ruu
Click to expand...
Click to collapse
for relock you do need the stock ruu (which is currently not available for AT&T ) otherwise the phone wont exit out of the bootloader menu . I had to exchange my phone tried to relock i couldnt so ended just getting it back to stock and flashed this recovery and got it exchanged.
anilkuj said:
for relock you do need the stock ruu (which is currently not available for AT&T ) otherwise the phone wont exit out of the bootloader menu . I had to exchange my phone tried to relock i couldnt so ended just getting it back to stock and flashed this recovery and got it exchanged.
Click to expand...
Click to collapse
You need to flash stock recovery and unroot before you relock otherwise you get a boot loop. It has been tested on the international forum without using a ruu
tjsooley said:
You need to flash stock recovery and unroot before you relock otherwise you get a boot loop. It has been tested on the international forum without using a ruu
Click to expand...
Click to collapse
yes i had stock recovery and unroot before i relocked, after relock couldn't get out of bootloader .
anilkuj said:
yes i had stock recovery and unroot before i relocked, after relock couldn't get out of bootloader .
Click to expand...
Click to collapse
Did you also run the fastboot command fastboot erase cache after the relock?
tjsooley said:
Did you also run the fastboot command fastboot erase cache after the relock?
Click to expand...
Click to collapse
no i dint run that , i looked up on the forums and i read that i cant relock completely without flashing Stock RUU and thats exactly what i was seeing . So i just packed it up and got it exchanged dint bother to investigate further.
anilkuj said:
no i dint run that , i looked up on the forums and i read that i cant relock completely without flashing Stock RUU and thats exactly what i was seeing . So i just packed it up and got it exchanged dint bother to investigate further.
Click to expand...
Click to collapse
From what I understand it needs to be done in a specific order.
1) flash stock cwm backup MUST be stock kernel and rom without system RW, root, busybox or init.d support. I looked and the "Stock" roms on the dev forum are not fully stock. So unless you have a 100% stock nandroid backup this will not work.
2) In CWM factory reset and format in mounts data, cache & Dalvik cache
3) Flash in fastboot the stock recovery
4) run this command in fastboot "fastboot erase cache"
5) run this command in fastboot "Fastboot oem lock"
6) your system should boot fine to 100% stock att. This is worthless untill we get a 100% stock unmodified att backup so a rom can be made.
you are right the Stock i flash was stock but was rooted (although i unrooted it manually) and with System RW enabled maybe thats why i couldnt boot.
thanks for the detailed instructions , this is all new to me coming from Galaxy series (S, S2, S3 and Note 2)
anilkuj said:
you are right the Stock i flash was stock but was rooted (although i unrooted it manually) and with System RW enabled maybe thats why i couldnt boot.
thanks for the detailed instructions , this is all new to me coming from Galaxy series (S, S2, S3 and Note 2)
Click to expand...
Click to collapse
Me too this is my first htc device. I am currently downloading a nandroid backup that "gunnyman" made. He has told me that he rooted it and it has no other mods. I am going to try to un root it and post it
I may have executed
Code:
fastboot flash [B][COLOR="Red"]boot[/COLOR][/B] stock_recovery.img
instead of
Code:
fastboot flash [B][COLOR="red"]recovery[/COLOR][/B] stock_recovery.img
.
Is there a place were I can download the stock bootloader to flash it back into place?
neumannrf said:
I may have executed
Code:
fastboot flash [B][COLOR="Red"]boot[/COLOR][/B] stock_recovery.img
instead of
Code:
fastboot flash [B][COLOR="red"]recovery[/COLOR][/B] stock_recovery.img
.
Is there a place were I can download the stock bootloader to flash it back into place?
Click to expand...
Click to collapse
are we suppose to guess what phone it's for ?
boot.img is actually the kernel does your phone work at all ?
clsA said:
instead of .
are we suppose to guess what phone it's for ?
boot.img is actually the kernel does your phone work at all ?
Click to expand...
Click to collapse
Oh, sorry, I thought I had posted this thread to the Honor 5X forum, so that the phone would obvious to everyone reading the thread.
Arobase40 said:
There are almost a dozen of Honor 5x sub-versions and each file also depends on the Android version, and it's also hard to guess if you need a bootloader (kernel) or a recovery !
Anyway, watch at clsa's repository, you may find what you need...
Click to expand...
Click to collapse
It's for KIW-L24. Thanks for the suggestion!
I think I bricked my Moto Z XT1650-03 (the UK international unlocked version),
I unlocked the bootloader and flashed the official twrp recovery, but made the stupid mistake of cancelling the backup in progress in twrp. Now I am stuck at the warning of the unlocked bootloader. I am able to enter the bootloader and the recovery mode but can't get the device to start. I did a factory reset from twrp, still didn't help.
I think maybe flashing the stock recovery might help. But I haven't found any reliable links to the stock recovery for my particular device.
Any solution to this problem?
Tushar1550 said:
I think I bricked my (the UK international unlocked version),
I unlocked the bootloader and flashed the official twrp recovery, but made the stupid mistake of cancelling the backup in progress in twrp. Now I am stuck at the warning of the unlocked bootloader. I am able to enter the bootloader and the recovery mode but can't get the device to start. I did a factory reset from twrp, still didn't help.
I think maybe flashing the stock recovery might help. But I haven't found any reliable links to the stock recovery for my particular device.
Any solution to this problem?
Click to expand...
Click to collapse
Hello, So here https://firmware.center/firmware/Motorola/Moto%20Z/Stock/XT1650-03/ we are all the Stock Firmware for the Moto Z XT1650-03,You just have to look for the one you wanted, So download it and inside the .zip file'll find the files recovery.img and flash it manually with fastboot command.
but do not know if it will work, I think it is better to flash the entire system directly.
Sorry for my Bad English
here there are the commands: https://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
miki232 said:
Hello, So here https://firmware.center/firmware/Motorola/Moto%20Z/Stock/XT1650-03/ we are all the Stock Firmware for the Moto Z XT1650-03,You just have to look for the one you wanted, So download it and inside the .zip file'll find the files recovery.img and flash it manually with fastboot command.
but do not know if it will work, I think it is better to flash the entire system directly.
Sorry for my Bad English
here there are the commands: https://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
Click to expand...
Click to collapse
Can you please help me with which one of those firmwares I'm supposed to download? All I know is that mine is the UK version according to this thread
https://forum.xda-developers.com/moto-z/help/moto-z-griffin-versions-compatibility-t3470885
Thank you in advance.
Put the device in Fastboot mode, and type "fastboot getvar all". then go to "(bootloader) ro.carrier:" and see what is the carrier. after this go to the page to download the stock firmware and search you carrier .
Hello,
I've been looking through this forum for quite a while, but I have yet to stumble upon a guide that can fix me up for taking the next step after the bootloader unlocking process. Yet, there's been lots of custom roms made for rmx2001. So here I'm with my unlocked rmx2001 or realme 6, wondering if I am missing out on something crucial for the next step because this is my first time doing something like this on a mediatek based phone. Kindly help me out pweese.. thank you;
Update:
I've dwelled deep into the forest, fought clones of sundar pichai, then finally.. successfully flashed my phone with custom recovery.
From what I've had read around this forum and other places, before flashing any custom recovery, the vbmeta.img must be flashed with a patched one, which as usual, there are rules one must follow to modify this certain android component.
This is the first for me, as per Android 8 (or Android 7 with its super confusing arb system took in place), any changes inside the recovery, system, etc are being handled by this vbmeta module.
It seems that vbmeta.img changes for every android or system update and to patch this vbmeta.img, the android version must be the same as what the patch corresponds to... (correct me if I'm wrong; this is my understanding based solely from what I have read, please take this with a big chunk of salt).
I currently have the b.57 update installed on my device, and I only found b.55 here on the next forum's page... the point is I have to wait for the latest patch of vbmeta b.57. Am I understanding this correctly, or am I just talking in elven language to myself? Anyway thank you for reading.
zero help, good for nothing advices. Search on other forums ,you Will get at least real help
cristianwcw said:
zero help, good for nothing advices. Search on other forums ,you Will get at least real help
Click to expand...
Click to collapse
lmao
ignoll said:
From what I've had read around this forum and other places, before flashing any custom recovery, the vbmeta.img must be flashed with a patched one, which as usual, there are rules one must follow to modify this certain android component.
This is the first for me, as per Android 8 (or Android 7 with its super confusing arb system took in place), any changes inside the recovery, system, etc are being handled by this vbmeta module.
It seems that vbmeta.img changes for every android or system update and to patch this vbmeta.img, the android version must be the same as what the patch corresponds to... (correct me if I'm wrong; this is my understanding based solely from what I have read, please take this with a big chunk of salt).
I currently have the b.57 update installed on my device, and I only found b.55 here on the next forum's page... the point is I have to wait for the latest patch of vbmeta b.57. Am I understanding this correctly, or am I just talking in elven language to myself? Anyway thank you for reading.
Click to expand...
Click to collapse
Hi fellow weeb I'm curious of how did you manage to flash custom recovery?
Lyco. said:
Hi fellow weeb I'm curious of how did you manage to flash custom recovery?
Click to expand...
Click to collapse
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
Do you a vbmeta.img for the latest patches b.59 or any guide to extract vbmeta, Just like you said the vbmeta corresponds with the patch.
Lyco. said:
Do you a vbmeta.img for the latest patches b.59 or any guide to extract vbmeta, Just like you said the vbmeta corresponds with the patch.
Click to expand...
Click to collapse
We can just use the vbmeta.img from stock ROM .ozip
Thanks
HemanthJabalpuri said:
We can just use the vbmeta.img from stock ROM .ozip
Thanks
Click to expand...
Click to collapse
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right? Or do you have a stock vbmeta?
Lyco. said:
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right?
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Is this the stock vbmeta? Or do anyone have any?
Lyco. said:
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right? Or do you have a stock vbmeta?
Click to expand...
Click to collapse
No, we don't need to modify anything to it.
--disable-verity and --disable-verification options to fastboot will patch it and flash automatically for you.
Also you can use vbmeta.img from any version of stock .ozip.
I am a Realme C12 user.
Thanks
HemanthJabalpuri said:
No, we don't need to modify anything to it.
--disable-verity and --disable-verification options to fastboot will patch it and flash automatically for you.
Also you can use vbmeta.img from any version of stock .ozip.
I am a Realme C12 user.
Thanks
Click to expand...
Click to collapse
Ok so what would I do if pbrp didn't showed up? And goes to bootloop, Do i just need to flash ofp and use realme flash tool?
I'm a new at flashing firmware so sorry about that
Lyco. said:
Ok so what would I do if pbrp didn't showed up? And goes to bootloop, Do i just need to flash ofp and use realme flash tool?
I'm a new at flashing firmware so sorry about that
Click to expand...
Click to collapse
Then flash stock recovery.
HemanthJabalpuri said:
Then flash stock recovery.
Click to expand...
Click to collapse
So after i flash the stock recovery should I flash the ozip there? And thanks for all the information.
Really stupid question here folks.
I am trying to flash the modem.img file from a zenphone 8 device.
Now I can flash the factory modem.img via fastboot but not the zenphone 8 modem.img. I get an error saying that Flashing not allowed for modem partition. Any tips or advice?
Does somebody know a way to convert the file to a sin file and flash it via newflasher?
Cheers, Bentree.
Use fastbootd instead of plain fastboot.
Also:
You shold flash both modem_a and modem_b partitions.
For NTT version, you cannot flash modem in neither fastboot mode nor fastbootd mode.
Till now I only success flash in twrp mode.
cscomic said:
For NTT version, you cannot flash modem in neither fastboot mode nor fastbootd mode.
Till now I only success flash in twrp mode.
Click to expand...
Click to collapse
NTT?
Ainz_Ooal_Gown said:
NTT?
Click to expand...
Click to collapse
Yes, some carrier lock partitions, such as NTT Docomo.
If you bought SO-51B, flash modem partition will success in both fastboot and fastbootd mode, but when you boot to system and check files in path /vendor/firmware_mnt/image, you will find it doesn't take effort.
And for flash mode, you will receive the cms key error.
cscomic said:
Yes, some carrier lock partitions, such as NTT Docomo.
If you bought SO-51B, flash modem partition will success in both fastboot and fastbootd mode, but when you boot to system and check files in path /vendor/firmware_mnt/image, you will find it doesn't take effort.
And for flash mode, you will receive the cms key error.
Click to expand...
Click to collapse
Is this still true if the bootloader has been unlocked?
Santa Claus 228 said:
Is this still true if the bootloader has been unlocked?
Click to expand...
Click to collapse
yes