Database Develop

Weird Brick?

Hello,
I seemed to have messed my phone up pretty bad, I was trying to unroot my phone and everything was going fine... but afterwards it just keeps booting into SPL, I can boot into recovery, and I can flash newer offically signed roms, but no matter what whenever i boot normally it just goes to the old rainbow spl screen. Any suggestions..?
Edit: Also I know it's not the camera button being stuck because it acts differently if I do so, i.e. if I press down the camera button it'll want to flash the .nbh but otherwise it just boots into the spl without mention of it.

worldestroyer said:
Hello,
I seemed to have messed my phone up pretty bad, I was trying to unroot my phone and everything was going fine... but afterwards it just keeps booting into SPL, I can boot into recovery, and I can flash newer offically signed roms, but no matter what whenever i boot normally it just goes to the old rainbow spl screen. Any suggestions..?
Edit: Also I know it's not the camera button being stuck because it acts differently if I do so, i.e. if I press down the camera button it'll want to flash the .nbh but otherwise it just boots into the spl without mention of it.
Click to expand...
Click to collapse
Wrong Forum ask in Q&A

since it will read the .nbh file, have you tried applying it?

no, you are wrong. this is a weirder brick
{
"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"
}

gridlock32404 said:
Click to expand...
Click to collapse
ummmm can i flash the old radio then the 1.33.2005 spl onto this and kill it? it scares me

david1171 said:
since it will read the .nbh file, have you tried applying it?
Click to expand...
Click to collapse
I tried applying it, and it goes through fine, but it just keeps rebooting to the spl...

worldestroyer said:
I tried applying it, and it goes through fine, but it just keeps rebooting to the spl...
Click to expand...
Click to collapse
is it the stock spl?
have you set up adb/fastboot before

hmmm, i remember someone else having this problem before but i forget what the solve was

I got this same problem. A temporary workaround is just to do
fastboot reboot to reboot into android as that command forces it to reboot directly, ignoring any other input commands (ie. Home+Power, Camera+Power).

h.nocturna said:
I got this same problem. A temporary workaround is just to do
fastboot reboot to reboot into android as that command forces it to reboot directly, ignoring any other input commands (ie. Home+Power, Camera+Power).
Click to expand...
Click to collapse
yeah i remember you saying you had that problem a while back, did you ever get a work around for it? or did you have to get a new phone?

maybe this might be helpfull to know

gridlock32404 said:
hmmm, i remember someone else having this problem before but i forget what the solve was
Click to expand...
Click to collapse
I had this problem too. It would boot just fine if I left the battery out for over 10 hours. But any reboots after that will go right to the SPL. Flashing RC29 doesn't solve it either. I ended up getting it replaced (waiting on it being shipped back).

david1171 said:
yeah i remember you saying you had that problem a while back, did you ever get a work around for it? or did you have to get a new phone?
Click to expand...
Click to collapse
No. That's the only way I can get it back into android =/
Fortunately, I bought another phone and now I just use that one for testing ROMs that aren't stable enough for me to keep.
I'll probably end up selling it for parts and recover a fraction of what I spent on it.

What did you do to get that way?

weird brick
Ok first of all your phone is not bricked.the defintion of a bricked phone is one that you cannot access recovery or fastboot.
Secondly it sounds as if the rc29 file you are flashing is corrupted can happen many different way I will give yoy an idea how to proceed
1st download dreaimg.nbh google it (download from a different source then you did last time)
2nd enter recovery. (Home + power) wipe phone
3rd turn off your phone remove battery and sim and sd card wait 10 seconds install battery and sims leave sd out)
4th format sd to fat 32 after formatting copy dreaimg.nbh to sd for computer install sd card into phone
5th power on the phone holding the camera button down to second stage till you get spl showing (rainbow)screen
6th set up phone
If this fails replace your sdcard and repeat the process

someone is late to the party.

weird brick
This should be posted in q&a mods

are you getting this error on your android device

Hazen said:
This should be posted in q&a mods
Click to expand...
Click to collapse
you have utterly failed. like for real.

david1171 said:
someone is late to the party.
Click to expand...
Click to collapse
Better late then never

problems flashing, stuck in boot loop

Hey peeps, hope somebody out there can help. I have quite a strange problem and have tried everything I know to sort it with no luck.
Ok before I start I just want to say I'm not playing the blame game, it was probably an unhappy coincidence it happened at the time it did.
I was on kingk's 2.0 hero rom, but decided i'd try maxisma's, so I wiped, formatted ext, flashed maxisma 2.0, then 2.0.1 which had just been released as a fix. Rebooted the phone. Everything was going smooth, I got a little flash of the notification bar same as what happens with every hero rom I've tried, then I got FC on messaging, then the phone froze. Thinking nothing of it, reboot, reflash after a wipe, but I repaired ext after wiping it. Flashed 2 and 2.0.1, then rebooted. Phone got to htc logo, then froze for a few seconds before going back to the animated android. Ok, this rom needs more time in the oven I thought.
I then wiped, formatted and repaired and flashed kingk's rom back to my phone, boot loop
I tried mlign, boot loop
I tried xrom, boot loop
I flashed htc image and then cyanogen's rom, finally got booted.
I've spoken with MikeTaylor (he has the patience of a saint, buy him a beer, I did) and he suggested clearing the dev folder, I tried and was prompted with "device or service in use" so that didn't work. I even thought going back to stock would help, but it didn't. I then thought it had something to do with the SPL, cyanogen's being the only rom not needing haykuros, so I flashed "the official donut" which also gave me a boot loop.
So here I am, asking for any suggestions, and I'm willing to try anything.
Many thanks in advance for any help, and I hope when I get fixed, this thread isn't used anymore, we don't want more people with my problem

The only suggestion I can make is recreating the partitions on your card using parted or something like that. I had the same problem as you going from Cyan to xROM, recreated the partitions and it was fine

well, not near computer to back things up, but i'l give it a go, it's either that or fastboot erase me thinks
if it works, thanks in advance, if it doesn't then thanks for trying

senaia said:
well, not near computer to back things up, but i'l give it a go, it's either that or fastboot erase me thinks
if it works, thanks in advance, if it doesn't then thanks for trying
Click to expand...
Click to collapse
Oh, I assumed that card wouldn't mount so it wouldn't matter if you couldn't back up
So what does fastboot erase do? Wipe out /system?

i was hoping somebody here could tell me that, i've never used fastboot other than changing the splash screen and that was done using a tool, so i didn't actualy use it lol. card mounts, the flash goes through ok, but it just never boots, unless it's cyanogen mod, which i've not used for about 2 months, xrom awesomeness got to me, but i decided to try out a few hero / sense roms while JAC was out of the office, and now i can't go back to it lol

Sorted, being lazy doesn't work. I used amonra recovery to make the partitions initially which worked, then had this problem. Tried using it again and it said it worked but I still couldn't flash. When I checked manually using parted, it showed 3 partitions. Fat32, blank, and swap. Recreated the partitions and I'm now back to full flashing fun. Unfortunate coincidence it happened right after flashing maxisma's 2.0.1

Reboots every 2 mins after update to sense 6.

After update to sense 6.0,
Just a quick overview:
I am rooted stock fw stock kernel and latest twrp recovery,unit rebooted prior to rooting also,however prior to update I was fine.
Handset was originally a Vodafone handset unlocked now on 3uk.
I've also included some screen shots of as version etc...
1. Phone auto reboots every 2 mins continuously (while on battery or on charger).
2. Battery drains in 4 to 5 hrs and phone becomes very hot.
3. SYNC is continuously ON most of the day.
4. Apps*requiring update from play store, keeps getting re-installed several times when the SYNC is ON.
I have performed a full factory reset 3 times,no avail.
If I leave at default*apps, my phone is OK. But once I reinstall all my*apps*from play store and setup (individual app manually, with out restoring from backup) the problems reappear.
Thanks for your time.
{
"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"
}
Sent from my HTC One using Tapatalk

Sounds like a 'stuck' sdcard, you may want to try restore tricks but may not help

Stuck sd card?
Sent from my HTC One using Tapatalk

Unfortunately, I have roughly the same problem. I have a rooted HTC One M7 (International), stock everything, unlocked, TWRP recovery.
After updating to Sense 6, the first time I rebooted my phone, it got stuck in a reboot loop (it did a full boot to Android without a hitch, I could even unlock my phone and access my home screen, but a few seconds later it would reboot). Manually restarting the phone didn't help. I finally managed to solve it by shutting the phone down, and then starting it again (instead of restarting). Today however I had to reboot the phone again, and now it's stuck once again in that reboot loop. Switching off the phone isn't working this time.
Any ideas anyone?

vlix said:
Unfortunately, I have roughly the same problem. I have a rooted HTC One M7 (International), stock everything, unlocked, TWRP recovery.
After updating to Sense 6, the first time I rebooted my phone, it got stuck in a reboot loop (it did a full boot to Android without a hitch, I could even unlock my phone and access my home screen, but a few seconds later it would reboot). Manually restarting the phone didn't help. I finally managed to solve it by shutting the phone down, and then starting it again (instead of restarting). Today however I had to reboot the phone again, and now it's stuck once again in that reboot loop. Switching off the phone isn't working this time.
Any ideas anyone?
Click to expand...
Click to collapse
well i had the same issue.
but after rebooting. the boot loop stopped. now the homescreen is just black. saying unauthorized device. i can still swipe down the notification bar and go to settings. but thats about it. i can for some reason still pick up the phone. but i can't navigate through my home screen because its black like i said above. nor can i go to my applications.:crying:

I at first managed to fix my problem by rolling back to the standard Android 4.4 without Sense 6. My phone worked fine for a few days, but now, after a manual reboot, it has started rebooting again! Exactly the same problem. Whatever is wrong with it, it's also related to a battery drain. The reason I had to reboot was because Google Services was sucking a lot of battery. But I guess it doesn't really have anything to do with the Sense 6 update.
What the hell is going on here....

vlix said:
I at first managed to fix my problem by rolling back to the standard Android 4.4 without Sense 6. My phone worked fine for a few days, but now, after a manual reboot, it has started rebooting again! Exactly the same problem. Whatever is wrong with it, it's also related to a battery drain. The reason I had to reboot was because Google Services was sucking a lot of battery. But I guess it doesn't really have anything to do with the Sense 6 update.
What the hell is going on here....
Click to expand...
Click to collapse
ehh possible to put back a custom recovery (TWRP) and flash a custom rom and then try again?

Davies_90 said:
After update to sense 6.0,
Just a quick overview:
I am rooted stock fw stock kernel and latest twrp recovery,unit rebooted prior to rooting also,however prior to update I was fine.
Handset was originally a Vodafone handset unlocked now on 3uk.
I've also included some screen shots of as version etc...
1. Phone auto reboots every 2 mins continuously (while on battery or on charger).
2. Battery drains in 4 to 5 hrs and phone becomes very hot.
3. SYNC is continuously ON most of the day.
4. Apps*requiring update from play store, keeps getting re-installed several times when the SYNC is ON.
I have performed a full factory reset 3 times,no avail.
If I leave at default*apps, my phone is OK. But once I reinstall all my*apps*from play store and setup (individual app manually, with out restoring from backup) the problems reappear.
Thanks for your time.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Same problem with my bro's HTC One Max but was fixed. I told him to go to recovery(TWRP), go to wipe, click "advanced wipe", check everything except usb-otg. Then click "format data" and type "yes" and install everything again.
Hope this helps

Hi, did you manage to solve that ? I'm having the same problem here and can't use my device

raphael.lira said:
Hi, did you manage to solve that ? I'm having the same problem here and can't use my device
Click to expand...
Click to collapse
did you read the post just above your's ?
did you format data in twrp and type yes and reinstall your Rom ?

I believe I have bricked my HTC One Mini 2?

Was at work using both my company phone (iPhone 5) and my personal phone (HTC One Mini 2) just fine. Put my personal phone away to get on with actual work and came home at around 5:30'ish. Played a bit ("a bit") until about 9/10pm (I think?) whereby I looked for my phone to just check things like WhatsApp and Snapchat and the phone wasn't turning on when I was holding the power button. I just thought to myself "huh, the battery must be dead" and put it to charge and the charging LED (as well as the charging screen with the "do not distribute outside htc blabla" dev screen) displayed so I just assume it's charging as per usual. Fast forward to about 1am, I have finished using my computer and decide to hop into bed. I go to turn on my phone by first powering down with power, vol up and vol down (as usual) and then try to boot the phone up. It boots as normal up until the O/S loading screen with a pac-man boot animation (I have PAC ROM installed) whereby it will freeze on the "game over" image of the boot animation and then proceed to go to a black screen. I thought to myself "hm, must be a mistake or something" and try it again to no avail. So I then go into recovery to do a fresh install and I try to wipe the phone and I do a factory reset in twrp, but upon trying to format data, the progress bar doesn't move (and so I left it overnight as I couldn't be bothered to wait). Upon leaving it overnight (1am to 7am) to format the data, I wake up to see that the progress bar hadn't moved at all from 0%. I then just thought "maybe the phone has actually formatted it but hasn't updated the image on screen so me being the dumbo I am, decided to force shut down the phone (with power, volup and voldown) and upon trying to boot the phone up again, it displays the HTC logo with the red writing, tries to boot into the O/S, fails, and then tries to boot into recovery and gets stuck in a boot loop (it will show the twrp logo and then a black screen, twrp logo and then black screen etc.). I have tried to flash twrp again (without first removing the twrp currently on it) but I was wondering what I could do in this situation. I am able to access the bootmenu (for hboot and fastboot) but nothing else.
TL;DR: I think I bricked my HTC One Mini 2. Came home, charged phone and phone got stuck at boot animation. Wiped phone in recovery, it got stuck on formatting data and now It can't boot into the O/S since it's wiped and it can't boot into Recovery for whatever reason.

DistincTHD said:
blah blah
Click to expand...
Click to collapse
This is not Facebook, go straight to the point.
Did you install a different kernel?

kativiti said:
This is not Facebook, go straight to the point.
Did you install a different kernel?
Click to expand...
Click to collapse
{
"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"
}
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.

DistincTHD said:
[IMG="HTC Dev Message"]
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
Click to expand...
Click to collapse
Oops, Just realised you meant the whole post, not just the blah blah bit within the post. But yeah what I did, I explained above and in the original post. I basically just told a story to give a better idea of what generally happened before the phone just pooped out on me.

DistincTHD said:
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
Click to expand...
Click to collapse
Something its corrupted so try to reinstall everything using the files from this post plus your choosen ROM.
When rebooting phone unplug USB cable.

kativiti said:
Something its corrupted so try to reinstall everything using the files from this post plus your choosen ROM.
When rebooting phone unplug USB cable.
Click to expand...
Click to collapse
I can't access twrp recovery but I do have fastboot enabled and working and I can access the boot menu so how would I go about wiping everything before re-flashing the recovery and then re-installing the o/s and everything else?

Just tried to first erase everything before installing and it's locking me out of the phone? It's telling me that an administrator console is unable to erase the system or its data so I'm quite stumped at the moment

DistincTHD said:
Just tried to first erase everything before installing and it's locking me out of the phone? It's telling me that an administrator console is unable to erase the system or its data so I'm quite stumped at the moment
Click to expand...
Click to collapse
you don't need to do all that.
try to flash twrp. (if OK use it to wipe everything)
If NOT ok flash stock recovery and unlock bootloader( yes again, this will wipe your phone and fix permissions)
Then you can do all you want.
Good luck.
let me know...

kativiti said:
you don't need to do all that.
try to flash twrp. (if OK use it to wipe everything)
If NOT ok flash stock recovery and unlock bootloader( yes again, this will wipe your phone and fix permissions)
Then you can do all you want.
Good luck.
let me know...
Click to expand...
Click to collapse
Right, so before I read that message, I flashed stock recovery and tried to reformat data and now It won't let be get into the boot menu and the HTC dev writing is gone (so I think it's locked again). On top of this, it just keeps booting into the reformatting data screen and just ends up hanging so I think I will let the battery drain or something (no idea how long it would take, probably days) and then try again from there. Pretty sure it is bricked now though lol welp. Is there any way to cancel a format?

Confused about System Wipe!

So I'm fairly new to the N6 (first nexus device) community... That being said, been flashing for about 5-6 years now and from what understand up till now you SHOULD NOT under any circumstances use the WIPE SYSTEM option when in TWRP because it will completely... Well, wipe your system. I've done this twice before and almost ended up w 2 paperweights (once as a noob and the second time on my m8 by accident) no boot, no rom and no way to transfer a rom to flash. Now, could someone help me understand why wiping the system won't screw w this this device? Thank you.

I build for bliss. Wiping your system essentially formats it as does fastboot before Fashing a new system.img. custom ROMs include a highly compressed system image as seen I this screenshot of my out folder
{
"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"
}
Sent from my Nexus 6 using Tapatalk
---------- Post added at 19:46 ---------- Previous post was at 19:45 ----------
So its fine to wipe as long as your flashing a new system. Pay no attention to recovery, cache and userdata images. They're excluded from the final zip
Sent from my Nexus 6 using Tapatalk

DroidManIc said:
So I'm fairly new to the N6 (first nexus device) community... That being said, been flashing for about 5-6 years now and from what understand up till now you SHOULD NOT under any circumstances use the WIPE SYSTEM option when in TWRP because it will completely... Well, wipe your system. I've done this twice before and almost ended up w 2 paperweights (once as a noob and the second time on my m8 by accident) no boot, no rom and no way to transfer a rom to flash. Now, could someone help me understand why wiping the system won't screw w this this device? Thank you.
Click to expand...
Click to collapse
It is advised to wipe/format system when flashing. Once wiped it is ready for a rom to flash. There is always a way to recover from wiping the system but not having a rom to flash on the device.
Most roms wipe the system as they flash.

Good stuff, thank you both for the reply. I'm unlocked rooted and twrp installed and ready to flash!

DroidManIc said:
So I'm fairly new to the N6 (first nexus device) community... That being said, been flashing for about 5-6 years now and from what understand up till now you SHOULD NOT under any circumstances use the WIPE SYSTEM option when in TWRP because it will completely... Well, wipe your system. I've done this twice before and almost ended up w 2 paperweights (once as a noob and the second time on my m8 by accident) no boot, no rom and no way to transfer a rom to flash. Now, could someone help me understand why wiping the system won't screw w this this device? Thank you.
Click to expand...
Click to collapse
That is not even close to being true for basically any phone with TWRP/custom recovery.
The recovery loads well before the system, and is on a different partition. TWRP has supported sideloading for quite a few versions now, and any phone with an unlocked bootloader can likely use fastboot or an equivalent to rewrite the system from bootloader mode.
It's perfectly fine to not understand or not be informed... By why does every person who has little idea what they are doing have to over emphasise that they have been flashing for years? Its fine to have a gap in understanding or a lack of knowledge. Particularly with Android which is not as well documented as other systems... Even better to ask... But man everytime I read "I am not new at this, I have been flashing for years..." its followed by a fairly basic question.
So that I am not just *****ing, let me ramble about booting ... Read as much or as little as you like Anyone who wants to correct me please do, this will mostly be rough and loosely worded
Its important to understand that when turning on your phone, it doesn't just send electricity to Android, and spring to life.
If you think about it... If everything was fully shut down and lifeless with nothing active... How would your phone even know the power button was pressed? How would power button do one thing, but the bootloader key stroke combo (power and vol down at the same time) boot to a different mode? How does power button require being held down and time how long?
The hardware the power buttons attach to sit active and watch for button presses. When it sees the proper combination It will tell the "motherboard" its time to power up.
But still, It just can't be android... Android is stored on your internal SD card, which is partitioned... The data is split up into different chunks and the phone does not even know what chunk the system is in.
So motherboard starts to initialize very basic stuff. It will find its CPU, and will find storage, ect...
When it finds the storage, it will look for a special flagged partition that contains a simple program, the bootloader.
Bootloader is not android and almost has nothing to do with android, the system partition... whatever. Its running on VERY minimal hardware (hence when your in bootloader mode, you use the volume keys to scroll up and down... touch isn't loaded yet).
As long as bootloader is not broken/corrupt/erased and is not locked... Your pretty much safe. It has basic tools to receive data from a computer via fastboot, it can mount/write/wipe other partitions.
It also knows where your kernel is, and where your recovery is. Typically it will automatically just load the android kernel, which will continue to initialize the rest of your hardware, and and get all the software that gives you a user interface and control going.
It can also boot into recovery mode instead of booting into android. Recovery mode is yet another self contained program/operating system/partition that runs independent of android. It offers more interface and functionality then bootloader mode, but is still basic. I am sure you remember when recovery didn't used the touch screen either... This was because the factory touch screen drivers had not been loaded yet, the teams that write these recovery programs eventually included software to instruct the system how to read touch input though.
The point is the phone boots and initially only knows/needs/cares about the partition called "bootloader", which has a self contained program that has basic recovery options when paired with a computer and fastboot.
That bootloader looks for the partition "boot" which contains your kernel which will load the android OS off "system", and your personal data/preference off "userdata"
OR
The bootloader can load your custom recovery off the "recovery" partition, which can mount/read/write most other partitions.
The warnings about not wiping system were likely based off the idea that you needed to boot into android in order to download a rom to flash... but really you should always have a backup that you have made at a point when your system was working good stored on your "userdata" partition, or on an external SD card if you phone supports it.
However lacking those two options, at some point in the past you may have had trouble... But TWRP has supported MTP transfer for a while now, and failing that the sideload command, that flashes a rom from your computer via ADB has been supported for quite a few version, and even before that (starting in 2014 with TWRP 2.8.0.0) ADB was supported so the "adb push" command could be used to send data to a phone with no rom on it.
ANY of the above paragraph only really matters on a phone with a locked bootloader and custom recovery installed though, which is why people point the the nexus as being different (even though other phones have unlocked bootloaders). As long as you have a factory image of the phone, fastboot can be used to re-write the partitions to the phone without it even having a custom recovery (that how your custom recovery likely got on your phone in the first place... the same can be done for system or boot as well as the other partitions too).
Phones with a locked bootloader and/or no publicly released factory images are probably why you heard this warning in the first place.