Develop Bugs

[Firmware][Mod][HBOOT 1.61] Verizon Lollipop Firmware

This is the lollipop firmware (minus kernel, recovery, system, data, and splash) that has been modified to remove the developer (red) text on boot, show S-ON and *** LOCKED *** in fastboot. Don't worry it is still s-off and unlocked, just says it's not if someone at a Verizon store looks at it. If someone know fastboot commands they can still clearly see that it has been S-Off. Please not this requires an S-Off Verizon HTC M7! Flash at own risk!
If you S-On with this flashed it will hard brick your phone! (DON'T S-ON UNTIL YOU FLASH A SIGNED RUU) Plus it will cost another $25 when you s-off again
That being said it is working great for me Screenshot shows the modified bits at the end of the post.
Flash instructions (Taken from Here):
Boot your phone into the bootloader by holding the power and vol up/down buttons at the same time until you see the bootloader screen or if you have your phone booted you can use the ADB command:
Code:
adb reboot-bootloader
Now use these fastboot commands:
Code:
fastboot oem rebootRUU
Should see the Silver HTC logo. Now issue this command to flash your phone using the firmware_1.61_mod.zip file:
Code:
fastboot flash zip firmware_1.61_mod.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
Code:
fastboot flash zip firmware_1.61_mod.zip
The green status bar usually does not reach the 100% mark. When the output in the command window is complete, you can reboot:
Code:
fastboot reboot
or
Code:
fastboot reboot-bootloader
1.61
Download Here
MD5: 630ca6e0bb65de7d5182d6a955d53e03
SHA1: 5a9d749cf47654b41fd03c20468668564e7c00bb
Old Versions:
1.57
Download Here
MD5: 95aab1c6eb1f7987ca020fc91cd3fee2
SHA1: 62381fd6f05b8920578a24f1a4a4ab72b48e36ee
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Please edit post to reflect "firmware" in the command and not "frimware"

ccsoccer03 said:
Please edit post to reflect "firmware" in the command and not "frimware"
Click to expand...
Click to collapse
Oops Thanks for the catch.

Flash was successful on my device. Thank you OP
EDIT:
I am running CM12.1 5/13 nightly FWIW

Has this been tested with Santod's NuSense 7 Version 4.00?
Thanks for posting.

Lt. Belspur said:
Has this been tested with Santod's NuSense 7 Version 4.00?
Thanks for posting.
Click to expand...
Click to collapse
Running it right now with no apparent issues.

No new radio?

eriknors said:
No new radio?
Click to expand...
Click to collapse
baseband changed:
KK
1.13.41.0702
L
1.13.41.1209

Is the radio included in the zip?

Yes

jmstumme said:
Yes
Click to expand...
Click to collapse
+1 its in there

Update to HBOOT 1.61
Edit:
If you get stuck booting your rom, restart. NuSenseSeven 4.00 worked after doing that

unable to flash TWRP on my BQ Aquaris X2 Pro

i have a Encrypted BQ Aquaris X2 pro and want to flash los according to this guide https://wiki.lineageos.org/devices/zangyapro/install
oem-unlock = done
debugging mode = done
fastboot flash recovery twrp-3.3.1-0-zangyapro.img
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (63984 KB)...OKAY [ 2.005s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)finished. total time: 2.005s
I also changed the slot to a. That doesn't help either
if i try fastboot boot twrp-3.3.1-0-zangyapro.img, TWRP asking for password
Is there a known problem with TWRP?
May i get some help in here?
thanks in advance, and sorry english is not my first language

presely said:
i have a Encrypted BQ Aquaris X2 pro and want to flash los according to this guide https://wiki.lineageos.org/devices/zangyapro/install
oem-unlock = done
debugging mode = done
fastboot flash recovery twrp-3.3.1-0-zangyapro.img
I also changed the slot to a. That doesn't help either
if i try fastboot boot twrp-3.3.1-0-zangyapro.img, TWRP asking for password
Is there a known problem with TWRP?
May i get some help in here?
thanks in advance, and sorry english is not my first language
Click to expand...
Click to collapse
When German is your native language then study this thread:
https://www.android-hilfe.de/forum/...e-to-device-failed-command-failed.942534.html
In short, you can't flash a recovery that's why you have to boot the recovery directly.

AndroidenKalle said:
When German is your native language then study this thread:
https://www.android-hilfe.de/forum/...e-to-device-failed-command-failed.942534.html
In short, you can't flash a recovery that's why you have to boot the recovery directly.
Click to expand...
Click to collapse
Thanks a lot for your answer.
when i boot twrp directly, twrp asking for password. after cancel and format data i got an error failed to mount /data (no such device).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

presely said:
Thanks a lot for your answer.
when i boot twrp directly, twrp asking for password. after cancel and format data i got an error failed to mount /data (no such device).
Click to expand...
Click to collapse
Any news?

AndroidenKalle said:
Any news?
Click to expand...
Click to collapse
im sorry, im late
everything is working fine.
You have to extract the los.img and then install it via
HTML:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot erase userdata
because there is no working twrp for the device, you have to need the lineage recovery.
This is the solution in a german forum.
thanks everybody!

[Recovery] Flashing TWRP - issue solved

Good morning all.
I've a problem during the flashing of TWRP.img
- adb-Driver installed
- Mi A2 lite booted into fastboot
- computer and phone can't connect
- phone aborted the fastboot mode after some minutes
Phone Mi A2 lite latest Stock ROM
Computer windows 11 pro

Code:
C:\Users\Username>fastboot boot "D:\Username\Downloads\twrp-3.5.2_9-2-daisy-unofficial.img"
downloading 'boot.img'...
OKAY [ 0.643s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.665s

Have you enabled bootloader unlocking in developer options?

Tech0308 said:
Have you enabled bootloader unlocking in developer options?
Click to expand...
Click to collapse
OEM Unlock
(Allow bootloader unlock)
yes, i did

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

And then run fastboot flashing unlock?
It'll erase your data unless you keep volume down button held while running this command

Tech0308 said:
And then run fastboot flashing unlock?
It'll erase your data unless you keep volume down button held while running this command
Click to expand...
Click to collapse
this command doesn't work, i'll get the output of all aviable commands, that's all

Ahh sorry I meant fastboot oem unlock here's the link to a guide, use the first half for what you want, the instructions are valid and still work
Thread '[GUIDE] How to enable Camera2 API persistently and keep bootloader locked' https://forum.xda-developers.com/t/guide-how-to-enable-camera2-api-persistently-and-keep-bootloader-locked.3851414/

Tech0308 said:
Ahh sorry I meant fastboot oem unlock here's the link to a guide, use the first half for what you want, the instructions are valid and still work
Thread '[GUIDE] How to enable Camera2 API persistently and keep bootloader locked' https://forum.xda-developers.com/t/guide-how-to-enable-camera2-api-persistently-and-keep-bootloader-locked.3851414/
Click to expand...
Click to collapse
thank you, that's it

Question Help I failed when trying to flash a room

As the title says... I messed up when I was trying to flash the EUR version on my Global Pad 5... I did't check and the boot loader got loked and now I can't start the tablet....
Is there a way to fix this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hello, you can now restore only the bootloader and the system via fastboot. To do this, download the rom ,, https://xiaomirom.com/en/download/xiaomi-pad-5-nabu-stable-V13.0.4.0.RKXMIXM/#global-fastboot ".
You must have previously unlocked the bootloader via MI unlock tool before you can flash the Global rom .
Then you will have the normal Global MIUI Android on again.

tobyw121 said:
Hello, you can now restore only the bootloader and the system via fastboot. To do this, download the rom ,, https://xiaomirom.com/en/download/xiaomi-pad-5-nabu-stable-V13.0.4.0.RKXMIXM/#global-fastboot ".
You must have previously unlocked the bootloader via MI unlock tool before you can flash the Global rom .
Then you will have the normal Global MIUI Android on again.
Click to expand...
Click to collapse
Thanks, but the problem is that I flashed a different rom using the flash tool and accidentally looked the boot loader, after this it won't start, the boot loader is locked and I'm not able to do anything.

You should be able to unlock it again using the xiaomi unlock tool, because it should keep oem unlock setting open.

You must boot at fastboot and Unlovk with the Tool. You dosnt wait 7 days. It works Instant and then you can flash fastboot Rom of your choice

You mean you unlocked a global one and flashed a Europe official rom and locked it and it got stuck?? I'm in the same boat, i have TR and i want to flash EU. I'm waiting the 7 days at the moment to unlock the bootloader. Advice pls
TDrkKnight said:
Thanks, but the problem is that I flashed a different rom using the flash tool and accidentally looked the boot loader, after this it won't start, the boot loader is locked and I'm not able to do anything.
Click to expand...
Click to collapse

Update... The bad I wasn't able restore it (I'm not up to date with all the "new" locks on android). The Good, I was able to return it, thats how I resolved the issue...

Question How to relock bootloader on Oneplus 11 CPH2447

Hello, can anyone share a complete proper tested process to relock Oneplus 11 bootloader after updating to OOS 13.1

Aka9413 said:
Hello, can anyone share a complete proper tested process to relock Oneplus 11 bootloader after updating to
Click to expand...
Click to collapse
Hi, check out this tutorial.

Aka9413 said:
Hello, can anyone share a complete proper tested process to relock Oneplus 11 bootloader after updating to OOS 13.1
Click to expand...
Click to collapse
i have not done it, buts its probably 'fastboot flashing lock' without the quotes
Also, it will wipe your data

kevp75 said:
i have not done it, buts its probably 'fastboot flashing lock' without the quotes
Also, it will wipe your data
Click to expand...
Click to collapse
Locking or Unlocking your bootloader will always format your device.

I just tried to do "fastboot oem lock" and it failed.
FAILED (remote: unknown command)
finished. total time: 0.002s
If someone has successfully done it, let me know.

maamdroid said:
I just tried to do "fastboot oem lock" and it failed.
FAILED (remote: unknown command)
finished. total time: 0.002s
If someone has successfully done it, let me know.
Click to expand...
Click to collapse
try
fastboot flashing lock

kevp75 said:
try
fastboot flashing lock
Click to expand...
Click to collapse
That worked.
I wasn't on my main machine, so I also updated to make sure to have the latest fastboot. Just used the portable version from here: https://forum.xda-developers.com/t/tool-windows-adb-fastboot-february-2023.3944288/
I think my issue was I was on an old version of fastboot.
Edit: I fixed the below issue by doing a factory reset. I setup the phone after the first "lock" reset it does and I had the issue. After a factory reset from within android, all is working well.
I am though no longer able to set a screen lock. Any ideas other than flashing the beta?
Screen lock was already charged. Try again with the new screen lock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

maamdroid said:
That worked.
I wasn't on my main machine, so I also updated to make sure to have the latest fastboot. Just used the portable version from here: https://forum.xda-developers.com/t/tool-windows-adb-fastboot-february-2023.3944288/
I think my issue was I was on an old version of fastboot.
Edit: I fixed the below issue by doing a factory reset. I setup the phone after the first "lock" reset it does and I had the issue. After a factory reset from within android, all is working well.
I am though no longer able to set a screen lock. Any ideas other than flashing the beta?
Screen lock was already charged. Try again with the new screen lock.
View attachment 5922405
Click to expand...
Click to collapse
I personally havent seen that, however, there are some threads here that address it... basically to fix, you have to disable... reunlock ... disable... relock... disable