why exactly do i have to flash fastboot.img ? is it actually necessary ?
do i have to flash fastboot.img -every-single-time i want to flash a rom ?
sorry for asking, i've done some research and i simply couldn't find any kind of answer to my question.
i haven't actually done anything yet, because i know from experience that you don't want to mess with this stuff if you don't understand absolutely everything. i had a desire z before i got an HTC One S, and before i could just flash away with roms, taking my usual precautions like wiping of course.
Correctly it's named BOOT.IMG
Yes, if you're not s-off you have to flash it everytime you flash a ROM... otherwise you don't need it
foeti said:
Correctly it's named BOOT.IMG
Yes, if you're not s-off you have to flash it everytime you flash a ROM... otherwise you don't need it
Click to expand...
Click to collapse
So if I have s-off I don't need to flash boot.IMG. because I've flashed two different ROMs and I've been getting no vibrations
Sent from my One S using xda app-developers app
skinzy98 said:
So if I have s-off I don't need to flash boot.IMG. because I've flashed two different ROMs and I've been getting no vibrations
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
No vibrations is most likely an hardware issue or rom setting.
Verstuurd van mijn One S met Tapatalk
skinzy98 said:
So if I have s-off I don't need to flash boot.IMG. because I've flashed two different ROMs and I've been getting no vibrations
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
The boot.img contains (mostly) the kernel. If you are S-OFF, the boot.img file contained within the ROM's zip will be flashed during the installation of the ROM in recovery. If you are not S-OFF and you want to go with the boot.img (kernel) contained in the ROM, you have to fastboot flash the boot.img file separately.
As a side note - you don't have to flash the boot.img if you are not S-OFF. In fact, if you have a custom kernel you may not want to (or perhaps the kernel has not changed - as with many of the CM nightlies...)
real187 said:
No vibrations is most likely an hardware issue or rom setting.
Verstuurd van mijn One S met Tapatalk
Click to expand...
Click to collapse
Yet the phone had vibrations fine right up until. I flashed my first ROM. That was dirty unicorn vibrations didn't work. Now I'm on deviant and it still doesn't qork
Sent from my One S using xda app-developers app
foeti said:
Correctly it's named BOOT.IMG
Yes, if you're not s-off you have to flash it everytime you flash a ROM... otherwise you don't need it
Click to expand...
Click to collapse
oh, my bad, brainfart ! yeah, i meant boot.img, but anyway... :laugh:
Got a link to the ROM? You flashed?
And if you flash something like bb8 or cm10.1 or sense based does it work?
Verstuurd van mijn One S met Tapatalk
I flashed dirty unicorn deviant and root box none with vibrations. I'm trying to get on a sense ROM to see if it will fix vibrations. If it doesn't then it will be going back as there is a 1 year warranty
Sent from my One S using xda app-developers app
My phone has no vibrations since a long time now. I also installed a rom - miui i think - some month ago and since this time there were no more vibrations any more ony any rom i tried. So i think, it is a hardware problem.
Sent from my HTC One S using xda app-developers app
customromfan said:
My phone has no vibrations since a long time now. I also installed a rom - miui i think - some month ago and since this time there were no more vibrations any more ony any rom i tried. So i think, it is a hardware problem.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
From what I've read it is a problem on a decent amount of one s phones where the vibrator module flakes out. If the sense ROM I'm gonna try doesn't work then I'm.sending it back in
Sent from my One S using xda app-developers app
Related
Hello everyone
Thanks to all the help from u guys, I'm enjoying my one s with unlocked bootloader, custom recovery and Rom. However I would like to know if there s anyway at all to get rid of that message everytime I turn the phone on, I may be a bit obsessed but I really don't like that message. It feels weird...
Thank you so much if anyone have any idea
Regards
Sent from my HTC One S using xda app-developers app
Jasonhhx said:
Hello everyone
Thanks to all the help from u guys, I'm enjoying my one s with unlocked bootloader, custom recovery and Rom. However I would like to know if there s anyway at all to get rid of that message everytime I turn the phone on, I may be a bit obsessed but I really don't like that message. It feels weird...
Thank you so much if anyone have any idea
Regards
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Return to stock with RUU.
I think stock kernel does not have it
Sent from my HTC One S using xda premium
k1llacanon said:
I think stock kernel does not have it
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Pretty sure you're right. When I ran 1.84 stock, even rooted, debloated with CWR, no message. Once I installed a ROM with modified kernel, it appeared.
This has been covered many times, just search. If everything is stock (ROM, recovery, etc) then you will not get it. Stock kernel + TWRP recovery means when you boot into recovery you will get it because it is not stock. Get it?
Sorry I forgot to mention it's not just happening when boot into recovery, it happens everytime I turn the phone on normally
Sent from my HTC One S using xda app-developers app
Jasonhhx said:
Sorry I forgot to mention it's not just happening when boot into recovery, it happens everytime I turn the phone on normally
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Well custom ROM + modded stock kernel or any other kernel = the text. It's nothing go worry about, I don't understand why everyone is freaking out about it
Sent from my HTC One S using Xparent Blue Tapatalk 2
invasion2 said:
Well custom ROM + modded stock kernel or any other kernel = the text. It's nothing go worry about, I don't understand why everyone is freaking out about it
Sent from my HTC One S using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
lol thanks im a bit weird, really likes a bit of perfection, especially on this expensive phone
thank you for the help :good:
invasion2 said:
Well custom ROM + modded stock kernel or any other kernel = the text. It's nothing go worry about, I don't understand why everyone is freaking out about it
Sent from my HTC One S using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Are you sure?
I think it's only due to the kernel because i had trickdroid with stock kernel and it didn't show the message, when i changed the kernel (not the rom) the message appeared.
I may be wrong of course
Alie360 said:
Are you sure?
I think it's only due to the kernel because i had trickdroid with stock kernel and it didn't show the message, when i changed the kernel (not the rom) the message appeared.
I may be wrong of course
Click to expand...
Click to collapse
No, you're right. torxx is using the stock kernel on TrickDroid 7.0 and 7.1. As long as htc won't publish the sources for its Android 4.04 kernel, there will be no alternative kernels. So besides booting into recovery there won't be any messages using the stock kernel.
Jasonhhx said:
lol thanks im a bit weird, really likes a bit of perfection, especially on this expensive phone
thank you for the help :good:
Click to expand...
Click to collapse
Trust me, I know the feeling. I was like this when I first hour my phone no worries mate!
@others who posted - correct. Torxx uses the stock kernel. Stock kernel means no message TWRP recovery means message because it isn't stock.
Sent from my HTC One S using Xparent Blue Tapatalk 2
invasion2 said:
Trust me, I know the feeling. I was like this when I first hour my phone no worries mate!
@others who posted - correct. Torxx uses the stock kernel. Stock kernel means no message TWRP recovery means message because it isn't stock.
Sent from my HTC One S using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
But I'm on trickdroid7.1 (stock kernel ) and I still get that screen even if I reboot normally ( holding down power button and pressing reboot)
CrayzyBoy said:
But I'm on trickdroid7.1 (stock kernel ) and I still get that screen even if I reboot normally ( holding down power button and pressing reboot)
Click to expand...
Click to collapse
Check your kernel version. If it's the same, there is possibly not much you can do about.
Most recent update of my issue
I have flashed the newest ruu (3 uk) downloaded from the ruu collection post and got rid of the message. I also rooted and installed custom recovery on my phone and the message still did not appear
I attached a screen shot of my software info
Btw I tried to flash trick droid 7.1 (without flashing the boot.img)after done this, the message did not appear however my phone is stuck with a boot loop just after the boot sound (and no boot animation). The last time I installed trickdroid I flashed boot.img and everything went fine however I got the development only message, so I suppose the issue is with the the kernel in the boot.IMG I flashed last te when I installed trickdroid
If trick droid is based on stock kernel how come I can't get it to work on my stock phone? (rooted and custom recovery installed)
Sent from my HTC One S using xda app-developers app
Jasonhhx said:
Most recent update of my issue
I have flashed the newest ruu (3 uk) downloaded from the ruu collection post and got rid of the message. I also rooted and installed custom recovery on my phone and the message still did not appear
I attached a screen shot of my software info
Btw I tried to flash trick droid 7.1 (without flashing the boot.img)after done this, the message did not appear however my phone is stuck with a boot loop just after the boot sound (and no boot animation). The last time I installed trickdroid I flashed boot.img and everything went fine however I got the development only message, so I suppose the issue is with the the kernel in the boot.IMG I flashed last te when I installed trickdroid
If trick droid is based on stock kernel how come I can't get it to work on my stock phone? (rooted and custom recovery installed)
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It's based off the 2.21 Euro release. If you installed any other RUU, you need to flash the boot.img either via fastboot or TWRP. This may result in the development message again (not sure what ROM gave me the message, but it was still there on TD 7.1)
I have the same kernel version as in the image rootrider posted in post #13, but I always have the red text on every boot.
What may make the difference, is whether the boot image is signed. The boot image from a RUU is signed. I bet the boot image from torxx is not.
-Jobo
How come so many ROMs have 2-3 stops of flashing and it kinda scares me when I'm not that familiar with flashing images first than this than that, why do some ROMs like JellyBam just come as one flash and done again just asking? :banghead:
Thanks
Sent from my HTC One S using xda premium
TheCrow1372 said:
How come so many ROMs have 2-3 stops of flashing and it kinda scares me when I'm not that familiar with flashing images first than this than that, why do some ROMs like JellyBam just come as one flash and done again just asking? :banghead:
Thanks
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Its not that hard really you flash all roms the same its just some come with installer that does more then flash the rom.
Darknites said:
Its not that hard really you flash all roms the same its just some come with installer that does more then flash the rom.
Click to expand...
Click to collapse
Can u explain a bit more like with Viper2 I flash initial ROM than what is the rest, boot image and stuff and do u flash it all to the sd than which steps come next? (sorry)
Sent from my HTC One S using xda premium
TheCrow1372 said:
Can u explain a bit more like with Viper2 I flash initial ROM than what is the rest, boot image and stuff and do u flash it all to the sd than which steps come next? (sorry)
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I told you how to do it in that PM you sent me. You can use Flash Image GUI to flash the boot.img before flashing the rom.
after i flash a rom and when i get to setup menu it says unfortanately phone has stopped!! doesnt matter which rom i flash it says the same thing!! tried with omni rom official beanstalk rom and bs harmony rom!! please help thx in advance
What steps are you taking when you flash a ROM?
Sent from my Nexus 5 using xda app-developers app
freddienux74 said:
after i flash a rom and when i get to setup menu it says unfortanately phone has stopped!! doesnt matter which rom i flash it says the same thing!! tried with omni rom official beanstalk rom and bs harmony rom!! please help thx in advance
Click to expand...
Click to collapse
Are you wiping data when you flash the rom?
If you don't have any important stuff on your phone, I would just flash the factory images and start over with the rom process.
freddienux74 said:
after i flash a rom and when i get to setup menu it says unfortanately phone has stopped!! doesnt matter which rom i flash it says the same thing!! tried with omni rom official beanstalk rom and bs harmony rom!! please help thx in advance
Click to expand...
Click to collapse
Please tell us also what is your phone's status at the moment. Like is your phone rooted with bootloader unlocked and stuff like that.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Bruce Lee said:
Please tell us also what is your phone's status at the moment. Like is your phone rooted with bootloader unlocked and stuff like that.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well since he's flashing a rom, it would be rooted and the bootloader unlocked.
aooga said:
Well since he's flashing a rom, it would be rooted and the bootloader unlocked.
Click to expand...
Click to collapse
It never hurts to ask though. Maybe he did something different and bypassed something. You never know. You got to have the whole story. :sly:
Sent from my Nexus 5 using XDA Premium 4 mobile app
Kreateablaze said:
What steps are you taking when you flash a ROM?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I did full wipe then dalvik cache
Sent from my Nexus 5 using Tapatalk
I'm rooted! When I flashed Mahdi ROM no issues! Mahdi ROM actually is my backup ROM also
Sent from my Nexus 5 using Tapatalk
freddienux74 said:
I'm rooted! When I flashed Mahdi ROM no issues! Mahdi ROM actually is my backup ROM also
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Wait it's working now?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Bruce Lee said:
Wait it's working now? No its not working! Mahdi ROM is my daily driver and my backup! I'm thinking now it might be kernel issue. Do you think the kernel might be issue?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No its not working now! I meant my daily driver is Mahdi ROM and I use
Sent from my Nexus 5 using Tapatalk
When you flash the ROM it also flashes the kernel that comes with it.
So if you are using Mahdi ROM then everything is ok but if you try a different ROM you get the error constantly?
using the ClockworkMod recovery.
If you receive issues on flashing, double check your download. If nothing, I suggest using the ClockworkMod recovery.
mistahseller said:
When you flash the ROM it also flashes the kernel that comes with it.
So if you are using Mahdi ROM then everything is ok but if you try a different ROM you get the error constantly?
Click to expand...
Click to collapse
Yes
Sent from my Nexus 5 using Tapatalk
storm007 said:
If you receive issues on flashing, double check your download. If nothing, I suggest using the ClockworkMod recovery.
Click to expand...
Click to collapse
I switch to cwm and same issue! Its weird! I mean again today I flash 4 different ROMs and as soon as I get to setup same issue! Unfortunately phone has stopped!
Sent from my Nexus 5 using Tapatalk
freddienux74 said:
I switch to cwm and same issue! Its weird! I mean again today I flash 4 different ROMs and as soon as I get to setup same issue! Unfortunately phone has stopped!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Phone has stopped is related to your gapps
freddienux74 said:
I switch to cwm and same issue! Its weird! I mean again today I flash 4 different ROMs and as soon as I get to setup same issue! Unfortunately phone has stopped!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The type of recovery you use will have no bearing on it, hundreds of people on here use twrp and cwm.
All I can suggest and it was suggested before is to wipe your phone completely and start over again. Something went wrong, clearly.
I just happened to notice my friend using his Galaxy S3 is getting 4G service at MY house and I can't even get it? Is this an issue or what? He is also using Verizon.
ROM: Android Revolution HD
Kernel: Checkm8 2.8GHz
Radio firmware: haven't touched it
Anything else: Can't think of anything else to include atm so ask if im missing any information.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
S1L3nTShaDoWz said:
I just happened to notice my friend using his Galaxy S3 is getting 4G service at MY house and I can't even get it? Is this an issue or what? He is also using Verizon.
ROM: Android Revolution HD
Kernel: Checkm8 2.8GHz
Radio firmware: haven't touched it
Anything else: Can't think of anything else to include atm so ask if im missing any information.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well if you want to troubleshoot it I would start by flashing my ruu that's posted. See if you get 4g on your phone with that.
Sent from my SM-T320 using Tapatalk
dottat said:
Well if you want to troubleshoot it I would start by flashing my ruu that's posted. See if you get 4g on your phone with that.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
I just now am getting familiar with what an RUU is and from my understanding so far there's 2 types? 1. radio upgrade unit & 2. rom upgrade utility. Which is yours? I'm not really looking forward to flashing roms atm, just looking for something quick like flashing some firmware that doesn't overwrite my entire system partition 'IF' possible. If not then am I stuck with flashing what appears to be a new rom? Or do I have another option? Thanks for reply!
Edit: Also I forgot to include that I'm S-OFF with bootloader unlocked & permanent root w TWRP recovery, would this act like one of Samsungs crappy OTA's and re-lock my phone IF it was the ROM thing I mentioned above rather than just Radio Firmware?
Sent from my HTC6525LVW using XDA Premium 4 mobile app
S1L3nTShaDoWz said:
I just now am getting familiar with what an RUU is and from my understanding so far there's 2 types? 1. radio upgrade unit & 2. rom upgrade utility. Which is yours? I'm not really looking forward to flashing roms atm, just looking for something quick like flashing some firmware that doesn't overwrite my entire system partition 'IF' possible. If not then am I stuck with flashing what appears to be a new rom? Or do I have another option? Thanks for reply!
Edit: Also I forgot to include that I'm S-OFF with bootloader unlocked & permanent root w TWRP recovery, would this act like one of Samsungs crappy OTA's and re-lock my phone IF it was the ROM thing I mentioned above rather than just Radio Firmware?
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And ruu is an ruu. It is both the stock rom and firmware included. There are reset parameters that a factory reset on stock recovery can do that twrp etc are not.
This will not affect your lock or s off status and it's pre rooted. Also, there's not really "permanent root" on any phone. More so with s off you have the ability to flash su and root.
Sent from my SM-T320 using Tapatalk
ROM | STOCK | 4.4.4 GPE| HTC ONE M7
htc/m7_google/m7:4.4.4/KTU84P.H1/356549:user/release-keys
About:
OTA Ready.
100% Stock android 4.4.4 KTU84P.H1 for HTC One M7 International, GPE. Not tested with other versions of HTC One M7
Created with adb pull /system partition to PC and packed in installation zip for TWRP recovery
Requirements:
Latest TWRP
Unlocked bootloader
S-Off
S-On users can try flash boot.img inside zip via fastboot.
Installations:
Boot in TWRP
Wipe Data
Install zip ROM
Reboot
Download 4.4.4:
Androidfilehost.com - OTA Ready
Older 4.4.3
Androidfilehost.com - OTA Ready
Thank you for the rom, will try this one. Is the latest Version of TWRP really necessary or is the most common version 2.633 good for installation?
Verstuurd vanaf mijn HTC One met Tapatalk
teejayd said:
Thank you for the rom, will try this one. Is the latest Version of TWRP really necessary or is the most common version 2.633 good for installation?
Verstuurd vanaf mijn HTC One met Tapatalk
Click to expand...
Click to collapse
I think 2.633 ok. You may update twrp with this aroma recovery installer http://www.androidfilehost.com/?fid=23501681358549174
pre-root??
kopeko said:
pre-root??
Click to expand...
Click to collapse
No, it's stock rom without any modifications. You can root it yourself if need.
To better understand. I have an s-on m7. If I extract the boot.img from the zip and flash it via fastboot and then flash the rom via twrp, will I be able to install this rom and not end up in a bootloop?
Sent from my HTC One using XDA Premium 4 mobile app
Vazduh said:
To better understand. I have an s-on m7. If I extract the boot.img from the zip and flash it via fastboot and then flash the rom via twrp, will I be able to install this rom and not end up in a bootloop?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are right. Make a backup always recommended.
artur0588 said:
No, it's stock rom without any modifications. You can root it yourself if need.
Click to expand...
Click to collapse
Just flash the superuser zip to attain root?
Ty
Sent from my HTC One using XDA Premium 4 mobile app
Sheetzie03 said:
Just flash the superuser zip to attain root?
Ty
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes.
Very smooth rom and no issues found, everything works great. And a good battery life ☺
Thanks!
artur0588 said:
You are right. Make a backup always recommended.
Click to expand...
Click to collapse
I did as you advise and it worked. I'm now having a great GPE based Rom on my S-on device. Everything is smooth and works as it should. A very big and appreciative thanks. Great work and kudos!
4.4.4 ready OP
Has anyone tried installing this over ARHD 6.1 (GE 4.4.3)? I am guessing it should work without wiping if I erase dalvik/cache after flashing.
Edit: Tried it myself. Works just fine. Happily using 4.4.4.
Is this build any different from the Skydragon build of @HolyAngel ? I'm using that with the ElementalX 15.1 GPE kernel.
sanderg said:
Is this build any different from the Skydragon build of @HolyAngel ? I'm using that with the ElementalX 15.1 GPE kernel.
Click to expand...
Click to collapse
This looks like a stock ROM with root? Mine has a bunch of tweaks and performance enhancements over stock..
HolyAngel said:
This looks like a stock ROM with root? Mine has a bunch of tweaks and performance enhancements over stock..
Click to expand...
Click to collapse
No root. This is complete stock.
many thanks, I always prefer full stock roms to avoid any weird behavior....
Is anyone having problems flashing this with TWRP 2.7.1.1 ?
It's saying error flashing..
blast1987 said:
Is anyone having problems flashing this with TWRP 2.7.1.1 ?
It's saying error flashing..
Click to expand...
Click to collapse
I always do with this ROM. Use cwm recovery
mrgwap said:
I always do with this ROM. Use cwm recovery
Click to expand...
Click to collapse
I've already tried, it starts flashing then the phone reboot automatically and get stuck on HTC white screen, then it automatic rebot again and go back to recovery....