Okay, I need help flashing with Fastboot

[Daniel.Lynch]

So I had issues with every ROM I tried, so I decided I want to go back to stock Rooted. I found a copy of the stock image here:

[ROM] DNA Stock Rooted ROM v.1.15.605.4 710RD | Droid DNA > XDA


I flashed it in CWM Recovery, but it says that If I've installed a custom kernel I'd have to fastboot the image. I was coming from a different ROM but I don't remember ever installing a custom kernel. Maybe one of the ROMs I used installed one anyway?
Well to get on with it, I think that because I flashed it with CWM Recovery that I messed it up a little. I cannot use WiFi, it will not turn on at all which is the same problem that one of the guys in that thread there had because he didn't fastboot the image.

So I guess I have to fastboot the image. Does anybody have any idea how I would do this? I tried googling it and I found some tutorials on xda but they were all for different devices and seemed a little bit over my head. Any and all help here is greatly appreciated!

 

[bespinct]

I haven't played with fastest in a long time, my last couple of devices were Samsung and I used Odin. You might have good luck hitting up the Thunderbolt or Incredible forums if you don't want to ask at XDA.

Posted via Android Central App

 

[jec11718]

Can't you just take your original recovery and use it? It would have all your old settings too

sent from my Nos M7 DNA

 

[jgraves12]

Try extracting the boot.img from the rom zip, then place it in your adb folder, and then..
adb reboot bootloader
fastboot flash boot.img
fastboot reboot

Sent from my HTC6435LVW using Tapatalk 4 Beta

 

[Daniel.Lynch]

You know what, I ended up fixing my ViperDNA backup. It kept restarting, I think I was too close to filling up my phone and was probably running out of swap space or something. Starting to wish this phone had more storage...

Sent from my HTC6435LVW using Tapatalk 4 Beta

 

[karn101]

If you are S-ON, you have to flash kernels seperately (through fastboot) as they won't flash in recovery.

If you are S-OFF, then they will install from the package.

Which are you? It's also probably why you kept having issues trying out ROMs. What were those issues?

 

[Daniel.Lynch]

If you are S-ON, you have to flash kernels seperately (through fastboot) as they won't flash in recovery.

If you are S-OFF, then they will install from the package.

Which are you? It's also probably why you kept having issues trying out ROMs. What were those issues?

You're way off man, I'm S-Off. Read the link in the original post and you'll probably understand why I was having those issues.

Sent from my HTC6435LVW using Tapatalk 4 Beta

 

[karn101]

You're way off man, I'm S-Off. Read the link in the original post and you'll probably understand why I was having those issues.

Sent from my HTC6435LVW using Tapatalk 4 Beta

Actually, I wasn't. One can't assume which you were. The reason WIFI didn't work on the stock ROM you flashed is because that ROM wasn't packaged with its appropriate boot.img. Since you were S-OFF'd, it meant when you flashed another ROM that included it packaged (Viper, etc.) you had overwritten your stock boot.img. If you were S-ON, which is why I was asking, then your stock boot.img would have still been in place and you shouldn't have had any problems flashing the stock ROM (in other words, maybe something else was causing the issue).

Jeez, I guess it's sometimes better not to try to help others...

Anyway, to answer your OP in case anyone else needs help in the future:

Stock boot.img
https://www.dropbox.com/s/80clwh307eg5aa6/boot.img

Stock modules
https://www.dropbox.com/s/w952ki9iilmqt7g/Stock_Modules.zip

 

[Daniel.Lynch]

Actually, I wasn't. One can't assume which you were. The reason WIFI didn't work on the stock ROM you flashed is because that ROM wasn't packaged with its appropriate boot.img. Since you were S-OFF'd, it meant when you flashed another ROM that included it packaged (Viper, etc.) you had overwritten your stock boot.img. If you were S-ON, which is why I was asking, then your stock boot.img would have still been in place and you shouldn't have had any problems flashing the stock ROM (in other words, maybe something else was causing the issue).

Jeez, I guess it's sometimes better not to try to help others...

Anyway, to answer your OP in case anyone else needs help in the future:

Stock boot.img
https://www.dropbox.com/s/80clwh307eg5aa6/boot.img

Stock modules
https://www.dropbox.com/s/w952ki9iilmqt7g/Stock_Modules.zip

I think you might have read that wrong, because I didn't mean for you to get offended. I figured it was clear in the original post that I was S-Off because I've been flashing through recovery.

Sent from my HTC6435LVW using Tapatalk 4 Beta

 

[karn101]

I think you might have read that wrong, because I didn't mean for you to get offended. I figured it was clear in the original post that I was S-Off because I've been flashing through recovery.

Sent from my HTC6435LVW using Tapatalk 4 Beta

No worries, things can be misconstrued when read on the internet. I was a bit edgy as well. FYI, you can be S-On and flash through recovery, just so you know.

Glad to know you got it working though. I'm impatiently waiting for a solid 4.2.2 ROM to be released for our phones.

 

[Daniel.Lynch]

No worries, things can be misconstrued when read on the internet. I was a bit edgy as well. FYI, you can be S-On and flash through recovery, just so you know.

Glad to know you got it working though. I'm impatiently waiting for a solid 4.2.2 ROM to be released for our phones.

How is that possible? I had to S-Off in order to install a custom recovery?

Viper started restarting on me randomly again. I couldn't find a solution to the problem so I went ahead and installed CM 10.1 and so far so good. I'll post if I notice anything, or run into issues.

 

[Jennifer Stough]

I thought Kernels or "boot img" can be flashed through recovery? Most Roms bundle the boot.img with the Rom, as long as you are running a sense Rom, and using the stock kernel, it isn't necessary to flash the boot.img. Once you start using vanilla android Roms, though, like CM10.1, is where you will run into issues with needing to flash a kernel as well. I flashed the cpalmer kernel through recovery at the same time I flashed CM10.1. And when I switched back to sense 5, I flashed the cpalmer sense kernel in recovery right after flashing the Rom. Everything has gone smoothly. S-offed and bootloader unlocked.

Jennifer Stough
Forums Moderator
Droid DNA

 

[karn101]

I thought Kernels or "boot img" can be flashed through recovery? Most Roms bundle the boot.img with the Rom, as long as you are running a sense Rom, and using the stock kernel, it isn't necessary to flash the boot.img. Once you start using vanilla android Roms, though, like CM10.1, is where you will run into issues with needing to flash a kernel as well. I flashed the cpalmer kernel through recovery at the same time I flashed CM10.1. And when I switched back to sense 5, I flashed the cpalmer sense kernel in recovery right after flashing the Rom. Everything has gone smoothly. S-offed and bootloader unlocked.

Jennifer Stough
Forums Moderator
Droid DNA

You can, if you're S-Off (which you are). If S-On, you have to flash them separately through fastboot.

Sent from my HTC6435LVW using Tapatalk 4 Beta

 

[karn101]

How is that possible? I had to S-Off in order to install a custom recovery?

Viper started restarting on me randomly again. I couldn't find a solution to the problem so I went ahead and installed CM 10.1 and so far so good. I'll post if I notice anything, or run into issues.

No, you didn't. You just had to be unlocked.

BTW, how do you like it? I'm afraid to try any 4.2.2 ROM because audio streaming over Bluetooth doesn't work and Pandora in the car is pretty vital to me.

Sent from my HTC6435LVW using Tapatalk 4 Beta

 

[Daniel.Lynch]

No, you didn't. You just had to be unlocked.

BTW, how do you like it? I'm afraid to try any 4.2.2 ROM because audio streaming over Bluetooth doesn't work and Pandora in the car is pretty vital to me.

Sent from my HTC6435LVW using Tapatalk 4 Beta

Are you sure? Because after 2.4 or whatever it was, none of us could root until they got the S-Off method, then we were able to install a custom recovery. I know before that update s-off was not necessary for root. I believe it is necessary now. Or am I missing something?

I do like it a lot, I mean, its CyanogenMod so you know what to expect. I've been running their mods since the very beginning and I love them. I'm a big fan of vanilla android. I've only been running it for a couple days so I'm not too sure about stability, but I haven't run into any issues YET. Next time I'm hanging out with my dad I'll try out bluetooth audio in his car! Haha, I'm getting a new stereo in my car soon that'll have that feature, and it will probably be pretty important to me as well.

 

[karn101]

Are you sure? Because after 2.4 or whatever it was, none of us could root until they got the S-Off method, then we were able to install a custom recovery. I know before that update s-off was not necessary for root. I believe it is necessary now. Or am I missing something?

I do like it a lot, I mean, its CyanogenMod so you know what to expect. I've been running their mods since the very beginning and I love them. I'm a big fan of vanilla android. I've only been running it for a couple days so I'm not too sure about stability, but I haven't run into any issues YET. Next time I'm hanging out with my dad I'll try out bluetooth audio in his car! Haha, I'm getting a new stereo in my car soon that'll have that feature, and it will probably be pretty important to me as well.

If the only way to unlock was through an S-Off method, then that's different. The unlocking portion is what was truly important. S-Off simply allowed you to write to /system while booted in Android.

If you were able to SuperCID (I did it when it was first released), then you can just unlock through HTCDEV.com and be S-On and flashing away. Eventually, I believe it was Beaups, found a method to allow you to write to /system even while being S-On but if you flashed a ROM you still had to fastboot the kernel as it wouldn't flash through recovery.

 

[bespinct]

No worries, things can be misconstrued when read on the internet. I was a bit edgy as well. FYI, you can be S-On and flash through recovery, just so you know.

Glad to know you got it working though. I'm impatiently waiting for a solid 4.2.2 ROM to be released for our phones.

Me too. I don't think it will happen until the HTC One is released though.

Sent from my Nexus 7 using Tapatalk HD

 

[Daniel.Lynch]

If the only way to unlock was through an S-Off method, then that's different. The unlocking portion is what was truly important. S-Off simply allowed you to write to /system while booted in Android.

If you were able to SuperCID (I did it when it was first released), then you can just unlock through HTCDEV.com and be S-On and flashing away. Eventually, I believe it was Beaups, found a method to allow you to write to /system even while being S-On but if you flashed a ROM you still had to fastboot the kernel as it wouldn't flash through recovery.

Yeah, I hadn't gotten around to rooting in time. I had to wait for the S-Off method.

Sent from my HTC6435LVW using Tapatalk 4 Beta