Hello Everyone,
When i was in USA i ordered htc one m8 and it is AT&T phone i guess. Since i hate the AT&T apps in the phone i tried to flash a custom rom and i sort of succeeded. Yet i still have problem about it. Whenever i flash a custom rom form( http://forum.xda-developers.com/htc-...opment#romList ) here its smooth and perfect first 1-2 weeks. No lagging no annoying problems. But after 2 weeks i am having lags (like slow app opening, late reactions, even freezing) It happens all the time, doesn't matter whichever rom i tried. And another problem is I can kill my battery in 2-3 hours just playing a game (lower than 500mb games). How can i make my phone stable smooth fast and longer battery life? (I love the room that i am using at the moment http://forum.xda-developers.com/htc-...pload-t3064838) And i also started to consider that am i flashing the roms wrong??!
Please can somebody help me
I am in begginer stage about these rom and root stuff
tugratolunay said:
Hello Everyone,
When i was in USA i ordered htc one m8 and it is AT&T phone i guess. Since i hate the AT&T apps in the phone i tried to flash a custom rom and i sort of succeeded. Yet i still have problem about it. Whenever i flash a custom rom form( http://forum.xda-developers.com/htc-...opment#romList ) here its smooth and perfect first 1-2 weeks. No lagging no annoying problems. But after 2 weeks i am having lags (like slow app opening, late reactions, even freezing) It happens all the time, doesn't matter whichever rom i tried. And another problem is I can kill my battery in 2-3 hours just playing a game (lower than 500mb games). How can i make my phone stable smooth fast and longer battery life? (I love the room that i am using at the moment http://forum.xda-developers.com/htc-...pload-t3064838) And i also started to consider that am i flashing the roms wrong??!
Please can somebody help me
I am in begginer stage about these rom and root stuff
Click to expand...
Click to collapse
Can you check your firmware version? It's in the bootloader menu(to enter it: restart phone then right after screen turns black hold volume down). Mine for example is 6.14.401.4. Also can you tell the name of the rom you use as the links you posted are not full and can't see it?
high_voltage said:
Can you check your firmware version? It's in the bootloader menu(to enter it: restart phone then right after screen turns black hold volume down). Mine for example is 6.14.401.4. Also can you tell the name of the rom you use as the links you posted are not full and can't see it?
Click to expand...
Click to collapse
[ROM] S.ROM-S3-10.0-A(A9) B(B2) | MMB29M Sense7g/7 | HK/JBL/BS | A9 1.56.617.1
But i didnt updated the lates version yet. But i have same problems in every roms.
HBoot 3.19.0.000
Os- 4.28.502.1
tugratolunay said:
[ROM] S.ROM-S3-10.0-A(A9) B(B2) | MMB29M Sense7g/7 | HK/JBL/BS | A9 1.56.617.1
But i didnt updated the lates version yet. But i have same problems in every roms.
HBoot 3.19.0.000
Os- 4.28.502.1
Click to expand...
Click to collapse
Your OS firmware is lollipop one, not MM. The best way is to search for RUU(MM one) and flash it. There is thread in the forum how to flash ruu and section for your variant. Beware: RUU will erase ALL your data(yes, including the internal memory) except the Sdcard!
high_voltage said:
Your OS firmware is lollipop one, not MM. The best way is to search for RUU(MM one) and flash it. There is thread in the forum how to flash ruu and section for your variant. Beware: RUU will erase ALL your data(yes, including the internal memory) except the Sdcard!
Click to expand...
Click to collapse
What if I want to use current custom or similar one?
tugratolunay said:
What if I want to use current custom or similar one?
Click to expand...
Click to collapse
Then you unlock the bootloader as you did before(should be locked to flash ruu it's easy done with fastboot relock command you will see in the instructions) and flash the custom rom. I did that. Was on lollipop firmware(4.16.401.10 in my case) and MM rom, locked the bootloader, flashed stock recovery(before locking the bootloader), flashed the ruu, unlocked the bootloader, flashed custom recovery twrp, flashed the desired new custom MM rom.
Check the instruction, I am not sure if it's needed to flash the stock recovery as the RUU flash that too.
high_voltage said:
Then you unlock the bootloader as you did before(should be locked to flash ruu it's easy done with fastboot relock command you will see in the instructions) and flash the custom rom. I did that. Was on lollipop firmware(4.16.401.10 in my case) and MM rom, locked the bootloader, flashed stock recovery(before locking the bootloader), flashed the ruu, unlocked the bootloader, flashed custom recovery twrp, flashed the desired new custom MM rom.
Check the instruction, I am not sure if it's needed to flash the stock recovery as the RUU flash that too.
Click to expand...
Click to collapse
Would you be angry if i said i didnt get it?
high_voltage said:
Then you unlock the bootloader as you did before(should be locked to flash ruu it's easy done with fastboot relock command you will see in the instructions) and flash the custom rom. I did that. Was on lollipop firmware(4.16.401.10 in my case) and MM rom, locked the bootloader, flashed stock recovery(before locking the bootloader), flashed the ruu, unlocked the bootloader, flashed custom recovery twrp, flashed the desired new custom MM rom.
Check the instruction, I am not sure if it's needed to flash the stock recovery as the RUU flash that too.
Click to expand...
Click to collapse
I started to download http://www.htc.com/us/support/htc-one-m8-att/news/ this ruu for my phone. I will install this ruu and then unlock bootloader and flash recovery twrp and flash the custom rom again ? and it will help my phone to stabilize?
tugratolunay said:
I started to download http://www.htc.com/us/support/htc-one-m8-att/news/ this ruu for my phone. I will install this ruu and then unlock bootloader and flash recovery twrp and flash the custom rom again ? and it will help my phone to stabilize?
Click to expand...
Click to collapse
Sadly, I checked, there is no MM update for at&t at that point of time. You are.1 this is .2 version with only SF fix that is not relevant for your problem. Still, I would advice you to try for a weak developer edition stock rooted rom.
Link: http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Try this rom. Keep in mind that internal memory files will be moved to folder with name "0", but won't be deleted.
high_voltage said:
Sadly, I checked, there is no MM update for at&t at that point of time. You are.1 this is .2 version with only SF fix that is not relevant for your problem. Still, I would advice you to try for a weak developer edition stock rooted rom.
Click to expand...
Click to collapse
Can you help me to find the correct rom to flash please?
high_voltage said:
Sadly, I checked, there is no MM update for at&t at that point of time. You are.1 this is .2 version with only SF fix that is not relevant for your problem. Still, I would advice you to try for a weak developer edition stock rooted rom.
Link: http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Try this rom. Keep in mind that internal memory files will be moved to folder with name "0", but won't be deleted.
Click to expand...
Click to collapse
This one requires S-off mine is s-on
Ryokan said:
Can you help me to find the correct rom to flash please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/devdb/project/dl/?id=15489&task=get
I use it currently, in the aroma installer I choose root(normal root method that it's default one, I don't like systemless), swipe2sleep ON and write protection disabler ON. Hope it runs smooth, but give it a few days to settle. This is stock MM rom and I run it with lollipop firmware without problems, tho I have europe unlocked edition and just don't know how at&t copes with it's lollipop firmware and new MM roms. Give it a shot.
---------- Post added at 03:56 PM ---------- Previous post was at 03:55 PM ----------
Ryokan said:
This one requires S-off mine is s-on
Click to expand...
Click to collapse
Only flashing the firmware requires s-off, relax, I am s-on too. Check the direct link, this is the rom itself and all you need.
high_voltage said:
http://forum.xda-developers.com/devdb/project/dl/?id=15489&task=get
I use it currently, in the aroma installer I choose root(normal root method that it's default one, I don't like systemless), swipe2sleep ON and write protection disabler ON. Hope it runs smooth, but give it a few days to settle. This is stock MM rom and I run it with lollipop firmware without problems, tho I have europe unlocked edition and just don't know how at&t copes with it's lollipop firmware and new MM roms. Give it a shot.
---------- Post added at 03:56 PM ---------- Previous post was at 03:55 PM ----------
Only flashing the firmware requires s-off, relax, I am s-on too. Check the direct link, this is the rom itself and all you need.
Click to expand...
Click to collapse
Thank you so much sir I will try it and how can i know that at&t release the ruu that i need ? where can i follow it?
Ryokan said:
Thank you so much sir I will try it and how can i know that at&t release the ruu that i need ? where can i follow it?
Click to expand...
Click to collapse
There is at&t android development section in the M8 forum, I am sure there will be noticed if MM is released.
Also in general thread in the sticky thread updates. Cheers!
Ryokan said:
This one requires S-off mine is s-on
Click to expand...
Click to collapse
You only need s-off to flash the recommended firmware for this ROM. If you have the right firmware, you never NEED s-off to flash a ROM. This ROM comes with a guide on how to bypass S-ON Write Protection-- a hack by Flar2. This isn't the same as a hard S-OFF
You should give it a try
Edit looks like somebody else beat me to the punch, sorry about that
Anonaru said:
You only need s-off to flash the recommended firmware for this ROM. If you have the right firmware, you never NEED s-off to flash a ROM. This ROM comes with a guide on how to bypass S-ON Write Protection-- a hack by Flar2. This isn't the same as a hard S-OFF
You should give it a try
Edit looks like somebody else beat me to the punch, sorry about that
Click to expand...
Click to collapse
How can i know if my firmware matches?
Ryokan said:
How can i know if my firmware matches?
Click to expand...
Click to collapse
By asking you what firmware version you have. So, which version do you have? I put the big "If you have the right firmware" in there for a reason :laugh:
Ryokan said:
How can i know if my firmware matches?
Click to expand...
Click to collapse
I think you are confusing "firmware" with "ROM". While true on some devices, these terms are used interchangeably, its better to not treat them so on the M8.
On this device, "firmware" usually refers to a number of modules (hboot, radio, WiFi, Bluetooth, and others) not included in the ROM, but included in official OTA updates and RUUs.
Your firmware is Lollipop, as shown by your OS number (on hboot screen) or main version (getvar all). This doesn't change when you flash a ROM.
LP firmware should run fine with MM ROMs. Technically, its best to run MM firmware. But you can't update the firmware until AT&T MM is released, or alternately if you get s-off. And the changes in the firmware seem minimal. I'm running LP firmware with the 6.12.1540 stock ROM linked by another user in this thread, with no glitches whatsoever.
redpoint73 said:
I think you are confusing "firmware" with "ROM". While true on some devices, these terms are used interchangeably, its better to not treat them so on the M8.
On this device, "firmware" usually refers to a number of modules (hboot, radio, WiFi, Bluetooth, and others) not included in the ROM, but included in official OTA updates and RUUs.
Your firmware is Lollipop, as shown by your OS number (on hboot screen) or main version (getvar all). This doesn't change when you flash a ROM.
LP firmware should run fine with MM ROMs. Technically, its best to run MM firmware. But you can't update the firmware until AT&T MM is released, or alternately if you get s-off. And the changes in the firmware seem minimal. I'm running LP firmware with the 6.12.1540 stock ROM linked by another user in this thread, with no glitches whatsoever.
Click to expand...
Click to collapse
Big thank you inbound!
I wanted to suggest that it might be safe to try running a MM ROM with the LP firmware, but had no precedent to do so. Sounds like it is generally safe to do so, then :laugh:
Anonaru said:
Big thank you inbound!
I wanted to suggest that it might be safe to try running a MM ROM with the LP firmware, but had no precedent to do so. Sounds like it is generally safe to do so, then :laugh:
Click to expand...
Click to collapse
You are correct, in that general rule of thumb is to update firmware to match the ROM. Especially having KitKat firmware with a LP ROM, which caused major problems (no WiFi, audio issues, no boot or extreme long boot times).
But MM ROMs in general seem to work fine with LP firmware. It seems minimal changes to the firmware this time around. I haven't seen any issues (at least not anything major or significant) reported running MM ROMs with LP firmware.
And for the OP's AT&T version, he can't update firmware unless he does s-off. So at least for the time being, I don't see a compelling reason to do that; and look at other options to help his performance issues.
Related
Hi there
I have been a M7 user for nearly two years and I decided to jump to the M8 a couple of days ago. I have already tried stock ROM, VenomROM, and InsertCoin. I realized that custom ROMs have a fairly long boot-up time (nearly 5 minutes) and there is no bootup animation whereas stock ROM boots up almost immediately. Why is that? And can it be fixed?
Thank you.
TarekElsakka said:
Hi there
I have been a M7 user for nearly two years and I decided to jump to the M8 a couple of days ago. I have already tried stock ROM, VenomROM, and InsertCoin. I realized that custom ROMs have a fairly long boot-up time (nearly 5 minutes) and there is no bootup animation whereas stock ROM boots up almost immediately. Why is that? And can it be fixed?
Thank you.
Click to expand...
Click to collapse
I believe it's something to due with Android 4.4.3, from what I've read everyone who went to the new ViperROM's has experienced this along with some other ROM's too.
Ah that must be it, because the stock ROM was 4.4.2. Thanks for the information.
TarekElsakka said:
Ah that must be it, because the stock ROM was 4.4.2. Thanks for the information.
Click to expand...
Click to collapse
It's the firmware version I think. Venom 1.8.0 worked like a charm for me and the firmware for it was 1.*.**.* once I tried installing viperone 4.4.3, the firmware on it was 2.*.***.*.* while my phone was still on the previous firmware. I say the two are just not compatible
Sent from my HTC One_M8 using XDA Free mobile app
queen112 said:
saadww
Click to expand...
Click to collapse
Genuine spammer.....reported you.
TarekElsakka said:
Hi there
I have been a M7 user for nearly two years and I decided to jump to the M8 a couple of days ago. I have already tried stock ROM, VenomROM, and InsertCoin. I realized that custom ROMs have a fairly long boot-up time (nearly 5 minutes) and there is no bootup animation whereas stock ROM boots up almost immediately. Why is that? And can it be fixed?
Thank you.
Click to expand...
Click to collapse
I'm willing to bet you flash a 4.4.3 rom without flashing an updated firmware...mine boot up right away
some user who have old firmware reported slow boot up and broken BT and wifi.
I am going to see if I can flash an older firmware just to try.
TarekElsakka said:
I am going to see if I can flash an older firmware just to try.
Click to expand...
Click to collapse
Don't add confusion by interchanging the terms "ROM" and "firmware". I think you mean "flash an older (Android 4.4.2 or software 1.xx) based ROM". Which yes, will resolve the long boot time (but also put you on what is becoming an obsolete ROM base).
When firmware is mentioned on this thread, it specifically means the modules not flashed when you install a ROM (hboot, radio, WiFi, Bluetooth, etc.).
Long boot time is a known issue, and the solution is S-off and flash 2.22 based firmware. Details here: http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
Post is in regards to the ARHD custom ROM, but it applies to any 2.xx Sense based custsom ROM.
Thank you so much it worked brilliantly.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
redpoint73 said:
Don't add confusion by interchanging the terms "ROM" and "firmware". I think you mean "flash an older (Android 4.4.2 or software 1.xx) based ROM". Which yes, will resolve the long boot time (but also put you on what is becoming an obsolete ROM base).
When firmware is mentioned on this thread, it specifically means the modules not flashed when you install a ROM (hboot, radio, WiFi, Bluetooth, etc.).
Long boot time is a known issue, and the solution is S-off and flash 2.22 based firmware. Details here: http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
Post is in regards to the ARHD custom ROM, but it applies to any 2.xx Sense based custsom ROM.
Click to expand...
Click to collapse
Thanks for the useful post. I m running the stock HTC ROM (4.4.3, just got it today, rooted it and updated OTA), do you know if that FW will work with HTC's ROM as well?
krakout said:
Thanks for the useful post. I m running the stock HTC ROM (4.4.3, just got it today, rooted it and updated OTA), do you know if that FW will work with HTC's ROM as well?
Click to expand...
Click to collapse
The firmware on your device should work well with any 2.xx Sense ROM (as well as GPE or AOSP).
redpoint73 said:
The firmware on your device should work well with any 2.xx Sense ROM (as well as GPE or AOSP).
Click to expand...
Click to collapse
Apologies, not sure exactly what you mean... you mean I can flash that FW on my HTC-ROM device as well with no problem?
Apologies again
krakout said:
Apologies, not sure exactly what you mean... you mean I can flash that FW on my HTC-ROM device as well with no problem?
Apologies again
Click to expand...
Click to collapse
If you updated by OTA to 4.4.3, the latest firmware is already on your device, and you need not take any further action to run 2.xx based Sense ROMs.
You can verify by looking at hboot and baseband on the bootloader screen. Hboot should be 3.18, and radio baseband should be 1.19. If so, you are on the latest firmware.
Also, in general OTA will include the firmware what matches the OS software contained in the OTA.
redpoint73 said:
If you updated by OTA to 4.4.3, the latest firmware is already on your device, and you need not take any further action to run 2.xx based Sense ROMs.
You can verify by looking at hboot and baseband on the bootloader screen. Hboot should be 3.18, and radio baseband should be 1.19. If so, you are on the latest firmware.
Also, in general OTA will include the firmware what matches the OS software contained in the OTA.
Click to expand...
Click to collapse
Ah, thanks for the clarification!
Versions on mine are as you stated them, which is too bad because I still have the slow boot issue. Like waaaay too slow!
krakout said:
Versions on mine are as you stated them, which is too bad because I still have the slow boot issue. Like waaaay too slow!
Click to expand...
Click to collapse
Odd, slow boot times associated with the outdated firmware were something like 5-10 minutes. Is yours that slow?
I haven't run a truly stock ROM for a while. But mine boots up in a minute or so from a full restart.
redpoint73 said:
Odd, slow boot times associated with the outdated firmware were something like 5-10 minutes. Is yours that slow?
I haven't run a truly stock ROM for a while. But mine boots up in a minute or so from a full restart.
Click to expand...
Click to collapse
Er.... wtf. I just rebooted after checking the HBoot version and it booted right away (25 secs or so) for the first time Before that it would get stuck at the first white HTC screen for minutes on end. Only thing I changed was that I installed the HandleExternalStorage module of Xposed, but I don't think this is relevant...
i have htc one m8 unbranded ... i bought it with nocturnal software !! it weird but i go back to stock using ruu "t-mobile" version cause i didn't find the unbranded version ... now after download the new ota update 4.4.4 eye ... i got message
"variant system version" >> you are running a modified version,.. for protection cannot update, plz revert to htc software system
the screenshot attach.
my current info:
locked bootloader
S-OFF
CID:11111111
plz help me XDA :fingers-crossed:
If you a custom recovery, or xposed, or have altered/removed any system apps, the Ota will fail.
You are s-off and super CID. Why not just flash the new firmware manually?
See the "flashing firmware without the panic attacks" guide in development section. ?
thank you sir .. flash firmware will get me to stock and update ota with no problem or what ??
btw which firmware to download ... or my super cid will accept any firmware number !!!
my now software no. 2.22.531.6 not in the "flashing firmware without the panic attacks" ??
am sry just changed from iphone, and i barely understand you
hossamkhalil89 said:
thank you sir .. flash firmware will get me to stock and update ota with no problem or what ??
btw which firmware to download ... or my super cid will accept any firmware number !!!
my now software no. 2.22.531.6 not in the "flashing firmware without the panic attacks" ??
am sry just changed from iphone, and i barely understand you
Click to expand...
Click to collapse
Don't do it!
Seriously, do not go stock. Just unlock your bootloader (can you be s off and supercid without? I never knew).
Once you do that, you can flash firmware from any carrier, then flash any updated ROM for that version.
You will never have to wait for carrier updates.
If you go stock, you will always be playing catch-up.
yes am sure of that am "locked" "S-oFF" and "CID:11111111" but i don't understand what a firmware will do to me !!!!!
but i understand this: unlock the bootloader ,,, then i will download any firmware with any number ?? really ? .. then download any custom rom ? like viper one...
and then if i do that i will recive 4.4.4 updates without any problems ? i think NO, custom roms prevent ota updates, so i have to check the sites of the rom from time to time to update ??
thank you
ex *i can't get viper one 3 rom untill updated to 4.4.4
Flashing firmware will not return you to stock But flashing the latest firmware will allow you to flash the latest version of roms that require the new firmware.
---------- Post added at 07:59 AM ---------- Previous post was at 07:55 AM ----------
But how can you have a custom recovery (to flash roms) if you didn't unlock user bootloader?
I'm confused. Lol
If you can find a stock backup, you can restore that to get back to stock, then flash your stock recovery.
Again, Need the custom recovery to use the backup tho.
KJ said:
Flashing firmware will not return you to stock But flashing the latest firmware will allow you to flash the latest version of roms that require the new firmware.
---------- Post added at 07:59 AM ---------- Previous post was at 07:55 AM ----------
But how can you have a custom recovery (to flash roms) if you didn't unlock user bootloader?
I'm confused. Lol
If you can find a stock backup, you can restore that to get back to stock, then flash your stock recovery.
Again, Need the custom recovery to use the backup tho.
Click to expand...
Click to collapse
no its locked bootloader with stock recovery, s-off and super cid !!!
i tried to get back to stock using backup recovery but i failed,, and no ruu for the international unlocked yet ... i just want any custom rom with 4.4.4 and be able to upgrade to android L when it release .... thank you mate
hossamkhalil89 said:
no its locked bootloader with stock recovery, s-off and super cid !!!
i tried to get back to stock using backup recovery but i failed,, and no ruu for the international unlocked yet ... i just want any custom rom with 4.4.4 and be able to upgrade to android L when it release .... thank you mate
Click to expand...
Click to collapse
Well it looks like to me that you'll be in the same situation as me. And that is that the easiest and probably quickest way we'll get L, is to flash a custom L Sense Rom. Or Aosp if you prefer that. And we'll be able to do that, cause we're s-off and Super CID. ?
Will likely need to update firmware for L too. Which again is simple with Super CID.
So, for right now, you do need to unlock your bootloader to flash a custom recovery. My vote is twrp. You need to do this to flash a 4.4.4 rom.
Also, you need to be on the latest firmware for the 4.4.4 roms.
All that said, if you want to wait and get the L OTA... You need to be stock and I believe you need your original CID to receive the Ota. I could be wrong on that. I've never done an ota on my M8...any device actually. I've always manually flashed new versions or used Roms. ?
So for now unlock bootloader and get the latest firmware then flash 4.4.4 rom ?? Where did i find that 4.4.4 rom ??
hossamkhalil89 said:
So for now unlock bootloader and get the latest firmware then flash 4.4.4 rom ?? Where did i find that 4.4.4 rom ??
Click to expand...
Click to collapse
Depends on your model/carrier which roms you use.... But in the development sections.
And firmware needs to be current or there will be issues on 4.4.4 roms.
The "flashing firmware without the panic attacks" thread in the general m8 development section will help you update. ?
Am unbranded international single sim .. give ne any link to the roms 4.4.4 and be greatful
Lots of roms here... I never recommend particular roms...
http://forum.xda-developers.com/htc-one-m8/development
Read the first post to see about it, and decide what you like.
Backup what you have in recovery first... Then follow the rom install instructions. That's it.
---------- Post added at 12:58 PM ---------- Previous post was at 12:54 PM ----------
This thread has some good info..
http://forum.xda-developers.com/showthread.php?t=2694600
---------- Post added at 12:58 PM ---------- Previous post was at 12:58 PM ----------
And this one...
http://forum.xda-developers.com/showthread.php?t=2711073
sry but last question sir can i update my android version from 4.4.2 to 4.4.4 with a custom rom ???
hossamkhalil89 said:
yes am sure of that am "locked" "S-oFF" and "CID:11111111" but i don't understand what a firmware will do to me !!!!!
but i understand this: unlock the bootloader ,,, then i will download any firmware with any number ?? really ? .. then download any custom rom ? like viper one...
and then if i do that i will recive 4.4.4 updates without any problems ? i think NO, custom roms prevent ota updates, so i have to check the sites of the rom from time to time to update ??
thank you
ex *i can't get viper one 3 rom untill updated to 4.4.4
Click to expand...
Click to collapse
You need the firmware, that's all. Then you can install Viperone's 4.4.4. That's what I'm running.
And you don't have to unlock the bootloader. Just flash the new firmware and then flash the ROM.
You can get firmware downloads, and instructions on how to flash them here.
This method is the safest.
EDIT: Looks like I'm a little late with my reply.
thank you "xunholyx" ... i will do a firmware update and hope that's will work, but how do i flash a viperone custom rom with a locked bootloader !!!
i thought i have to unlock, then twrp then flash it !!!! little confused
hossamkhalil89 said:
thank you "xunholyx" ... i will do a firmware update and hope that's will work, but how do i flash a viperone custom rom with a locked bootloader !!!
i thought i have to unlock, then twrp then flash it !!!! little confused
Click to expand...
Click to collapse
It was me who was confused. Sorry. You can flash the firmware, but not the ROM. You'll have to unlock for that.
thanks man i appreciate your help ... i might get the viperone or google play edtion rom with the latest updates ... i just so afraid to unlock my bootloader but i wil do it anyway
hossamkhalil89 said:
thanks man i appreciate your help ... i might get the viperone or google play edtion rom with the latest updates ... i just so afraid to unlock my bootloader but i wil do it anyway
Click to expand...
Click to collapse
There's nothing to be afraid of. As long as you follow instructions well, you will never have a problem.
Have fun flashing! You're going to love it. And ViperOne is a real good choice if you want to keep Sense. I'm running it, and it is great!
man plz help me ,,, i do firmware update after successful i reboot, then stuck on htc green logo but all buttons working and someone call me ,, i cant see but i can answer ... i make another reboot then the phone on black screen while everything still working !!!! am gonna be crazy ...
I'm wondering if anyone has attempted to install a Marshmallow custom ROM or stock RUU over the Nougat firmware with any success.
I'm doubtful, but perhaps it's possible with S-On. Thanks!
the nougat firmware is not downcompatible with marshmallow roms.
only way would be to s-off, downgrade firmware then, flash the marshmallow rom.
be aware to pick a full firmware though and no incremental one...we've seen a handful people doing this and that ends in a hardbrick.
j to the 4n said:
the nougat firmware is not downcompatible with marshmallow roms.
only way would be to s-off, downgrade firmware then, flash the marshmallow rom.
be aware to pick a full firmware though and no incremental one...we've seen a handful people doing this and that ends in a hardbrick.
Click to expand...
Click to collapse
When I then eventually update ViperROM from Marshmallow to Nougat, will I have to perform a full wipe - or can the update be directly applied?
Trying to plan ahead, thanks a bunch j4n.
fullydeveloped said:
When I then eventually update ViperROM from Marshmallow to Nougat, will I have to perform a full wipe - or can the update be directly applied?
Trying to plan ahead, thanks a bunch j4n.
Click to expand...
Click to collapse
well, that sounds like that you are still on marshmallow firmware + rom.
That would mean, you could flash the nougat rom and revert back to the marshmallow one anytime. Just ensure you flash latets TWRP before and backup your data, including sdcard..in case something goes wrong with encryption.
the nougat rom can be dirty flashed.
you know what the difference between firmware and rom is, right?
j to the 4n said:
well, that sounds like that you are still on marshmallow firmware + rom.
That would mean, you could flash the nougat rom and revert back to the marshmallow one anytime. Just ensure you flash latets TWRP before and backup your data, including sdcard..in case something goes wrong with encryption.
the nougat rom can be dirty flashed.
you know what the difference between firmware and rom is, right?
Click to expand...
Click to collapse
Thanks, apologies for the confusion. I'm on Nougat, but am planning to downgrade for xposed - then eventually update back up to Nougat once there's a stable release. I asked about dirty flashing since I'm less likely to full wipe for 7.0 after many months of customizing
j to the 4n said:
the nougat firmware is not downcompatible with marshmallow roms.
only way would be to s-off, downgrade firmware then, flash the marshmallow rom.
be aware to pick a full firmware though and no incremental one...we've seen a handful people doing this and that ends in a hardbrick.
Click to expand...
Click to collapse
Has anyone downgraded the Firmware and succeeded? I hard bricked mine twice, first was trying to downgrade it with a full stock firmware from OTA and 2nd time it died when i accidentally picked and flashed a wrong Marshmallow aboot trying to get rid of Hidden Red text which made me believe flashing a Marshmallow aboot while on Nougat hardbricks the Phone. It died at the stage where it should restart so we can run fastboot flash zip Firmware_xx.zip command the 2nd time. It goes black, doesn't turn on, a PC doesn't recognize it, doesn't show if charging. Was lucky HTC took care of the problem.
emrug said:
Has anyone downgraded the Firmware and succeeded? I hard bricked mine twice, first was trying to downgrade it with a full stock firmware from OTA and 2nd time it died when i accidentally picked and flashed a wrong Marshmallow aboot trying to get rid of Hidden Red text which made me believe flashing a Marshmallow aboot while on Nougat hardbricks the Phone. It died at the stage where it should restart so we can run fastboot flash zip Firmware_xx.zip command the 2nd time. It goes black, doesn't turn on, a PC doesn't recognize it, doesn't show if charging. Was lucky HTC took care of the problem.
Click to expand...
Click to collapse
thats what I said. The firmware in an ota is NOT a full firmware, its a incremental one.
You need a full firmware package like its provided in @Sneakyghost 's threads, with those lots of downgraded already.
j to the 4n said:
thats what I said. The firmware in an ota is NOT a full firmware, its a incremental one.
You need a full firmware package like its provided in @Sneakyghost 's threads, with those lots of downgraded already.
Click to expand...
Click to collapse
Great!! Now i get it, well explained. Thanks :highfive:
Does anyone have the latest retail version of the G5S rom stock?
Version latest is NPP26.102-49-1
this firmware will not come out, it will have to wait for the next one.
lohanbarth said:
this firmware will not come out, it will have to wait for the next one.
Click to expand...
Click to collapse
But mine version is on NPPS26.102-63-1
Will this version be released?
And if I try to flash .49 version will I get error?
Thanks a lot
I think I found one place where it's suposed to host the "MONTANA_NPP26.102-63_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" file, but it's a paid download site.
i'm not going to pay to download because money in Brazil is something very scarce especially for something charged in dollar :silly:
if you wanna try, here is: https://www.top-firmware.com/index.php?a=browse&b=file-info&id=26032
and if in any case you get this file, please share with us
bycabraljr said:
I think I found one place where it's suposed to host the "MONTANA_NPP26.102-63_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" file, but it's a paid download site.
i'm not going to pay to download because money in Brazil is something very scarce especially for something charged in dollar :silly:
if you wanna try, here is: https://www.top-firmware.com/index.php?a=browse&b=file-info&id=26032
and if in any case you get this file, please share with us
Click to expand...
Click to collapse
So my guess is, we can still flash .49 version rom even we're on higher version. (just simply not to flash gpt.bin, this cause error when your version is newer than .49)
And after installed .49 version, we will receive OTA update then we update it?
Not sure if this is the correct way to get back to stock rom and relock the bootloader...
michael50310 said:
So my guess is, we can still flash .49 version rom even we're on higher version. (just simply not to flash gpt.bin, this cause error when your version is newer than .49)
And after installed .49 version, we will receive OTA update then we update it?
Not sure if this is the correct way to get back to stock rom and relock the bootloader...
Click to expand...
Click to collapse
To relock the bootloader you'll need a firmware more recent than the previous one you installed. If you had the .49-1 installed, you'll may need to wait for one more recent firmware popout as this .49 will give errors while installing (the "oem lock begin" command only locks the bootloader if you install every single file from the firmware, which will fail because an lower version of the firmware was installed).
In short: you can get back to stock but can't relock bootloader unless you didn't installed the OTA .49-1 or have an more recent firmware available
bycabraljr said:
To relock the bootloader you'll need a firmware more recent than the previous one you installed. If you had the .49-1 installed, you'll may need to wait for one more recent firmware popout as this .49 will give errors while installing (the "oem lock begin" command only locks the bootloader if you install every single file from the firmware, which will fail because an lower version of the firmware was installed).
In short: you can get back to stock but can't relock bootloader unless you didn't installed the OTA .49-1 or have an more recent firmware available
Click to expand...
Click to collapse
Gotcha. So after reverted to .49 form higher version, will I be able to get OTA update to higher version? Tks a lot!
michael50310 said:
Gotcha. So after reverted to .49 form higher version, will I be able to get OTA update to higher version? Tks a lot!
Click to expand...
Click to collapse
Yes, you can update without worries. Just remember to maintain your system untouched before any update. If you root or install custom recovery, the update will fail and may get into a boot loop
bycabraljr said:
Yes, you can update without worries. Just remember to maintain your system untouched before any update. If you root or install custom recovery, the update will fail and may get into a boot loop
Click to expand...
Click to collapse
So I'm currently running NPPS26.102-63-1 , and my bootloader is unlocked. Am I still capable for OTA update? And if I decided to install custom recovery and rom, can I flash .49 version stock rom?
michael50310 said:
So I'm currently running NPPS26.102-63-1 , and my bootloader is unlocked. Am I still capable for OTA update? And if I decided to install custom recovery and rom, can I flash .49 version stock rom?
Click to expand...
Click to collapse
You can upgrade through OTA with unlocked bootloader, you only can't if you modify your system. But if you are running .63-1 I'm not certain about reinstalling the .49 ROM as they may be different, like different modem or other resources like NFC resulting in bricking. Test at your own risk. I'd like to test .63 ROM, but I can't find any free places to download it.
(Or if you want you can also try the ZUI ROM, it's a stock rom from a chinese moto g5s with ZUI interface)
bycabraljr said:
You can upgrade through OTA with unlocked bootloader, you only can't if you modify your system. But if you are running .63-1 I'm not certain about reinstalling the .49 ROM as they may be different, like different modem or other resources like NFC resulting in bricking. Test at your own risk. I'd like to test .63 ROM, but I can't find any free places to download it.
(Or if you want you can also try the ZUI ROM, it's a stock rom from a chinese moto g5s with ZUI interface)
Click to expand...
Click to collapse
So the reason is the latest firmware for locking bootloader
Untill now I have thought that the problem is with only my device can we ask for Motorola for the latest firmware releases so that we can relock our bootloader
Talwar sridhar said:
So the reason is the latest firmware for locking bootloader
Untill now I have thought that the problem is with only my device can we ask for Motorola for the latest firmware releases so that we can relock our bootloader
Click to expand...
Click to collapse
They used to have a site for you to download firmware, but it hasn't been updated like 3years... Even Moto support doesn't know where to get it..
no matter what i do with my htc 10, i always lose radio on flashing rom, i looked and it say only flash oreo roms if you are on oreo firmware, which is what i am doing. i am formatting data like it says to do to rid the encrypyion. because of this i have to restore from RUU everytime to fix radio, restoring from a twrp backup does not fix the radio. home button stops working aswell but it doesnt work in twrp either. is there any way i can fix these problems?
Thank you for your help
twosaltyy said:
no matter what i do with my htc 10, i always lose radio on flashing rom, i looked and it say only flash oreo roms if you are on oreo firmware, which is what i am doing. i am formatting data like it says to do to rid the encrypyion. because of this i have to restore from RUU everytime to fix radio, restoring from a twrp backup does not fix the radio. home button stops working aswell but it doesnt work in twrp either. is there any way i can fix these problems?
Thank you for your help
Click to expand...
Click to collapse
It lacks all the important info
1: what is your current firmware
2: what is your current OS
3: what ruu did you flash
Mr Hofs said:
It lacks all the important info
1: what is your current firmware
2: what is your current OS
3: what ruu did you flash
Click to expand...
Click to collapse
1. Oreo
2. 3.16.401.2
3. The Oreo RUU for 3.16.401.2
twosaltyy said:
1. Oreo
2. 3.16.401.2
3. The Oreo RUU for 3.16.401.2
Click to expand...
Click to collapse
Alright that setup is fine, using the ruu gives you radio so all is working fine at that point. What roms did you try to flash ?
Mr Hofs said:
Alright that setup is fine, using the ruu gives you radio so all is working fine at that point. What roms did you try to flash ?
Click to expand...
Click to collapse
I tried PureFusion and AOSiP
My radio works fine on fully stock (which is what i am running right now) but when i goto flash a rom i lose radio and home button, i just wanted to clarify because i didnt know how good my initial explanation was.
twosaltyy said:
I tried PureFusion and AOSiP
My radio works fine on fully stock (which is what i am running right now) but when i goto flash a rom i lose radio and home button, i just wanted to clarify because i didnt know how good my initial explanation was.
Click to expand...
Click to collapse
Yeah, ï believe purefusion is based on the nougat firmware so that explains the loss of radio. Check the specs before flashing.......maximus, leedroid or viper should work fine.
You have to read more mate, just checked the OP of the AOSP rom.......
It says it needs N or MM firmware so no O (oreo) firmware.
Mr Hofs said:
You have to read more mate, just checked the OP of the AOSP rom.......
It says it needs N or MM firmware so no O (oreo) firmware.
Click to expand...
Click to collapse
Hmm... what about purefusion though, i cant see anything on that page about what firmware i have to be on but i read somewhere you have to be on O firmware for any O roms to work and you cant flash N roms if you are on O firmware.
Mr Hofs said:
Yeah, ï believe purefusion is based on the nougat firmware so that explains the loss of radio. Check the specs before flashing.......maximus, leedroid or viper should work fine.
Click to expand...
Click to collapse
i dont want to use those because i wanted the fully stock android experience, like i did on my other phones. Should the lineageos 15.1 rom work?
twosaltyy said:
i dont want to use those because i wanted the fully stock android experience, like i did on my other phones. Should the lineageos 15.1 rom work?
Click to expand...
Click to collapse
Read the specs ?
Look all the info is there. Take your time and take all info in, don't be hasty, read it a second time if needed.
Mr Hofs said:
Read the specs
Click to expand...
Click to collapse
Yeah it says O firmware required. is there a specific way i need to erase the device in TWRP other than formatting data to rid the encryption? just want to be sure. it only says to erase /system and /data if coming from another ROM, im not sure if this includes stock sense also?
twosaltyy said:
Yeah it says O firmware required. is there a specific way i need to erase the device in TWRP other than formatting data to rid the encryption? just want to be sure. it only says to erase /system and /data if coming from another ROM, im not sure if this includes stock sense also?
Click to expand...
Click to collapse
Especially going from stock sense to an AOSP style rom it's wise to wipe the whole thing because you don't want to mix two roms, strange behavior may occur.
Follow the instructions in the specific thread, if you want to run the phone unencrypted then you need to format data indeed.
Hey sorry to hijack thread but I'm having a similar issue, any sort of flashing I do results in the airplane mode getting stuck to "turning off" and I can't use my mobile network. I can flash my official T-Mobile RUU zip and things will work fine, but if I flash twrp on official it breaks. I switched over to the unlocked Dev rom and it breaks. I can only get my official zip working. Any help?
My specs are:
Android 7.0
2.51.617.32
S-off locked
1.0.U010241a 6117.76.02_f radio
Switched cid to bs_us01 or whatever the Dev cid is. For the rom. Other than lineageOS which didn't work, I haven't tried any other rom except dev.
kazuki1 said:
Hey sorry to hijack thread but I'm having a similar issue, any sort of flashing I do results in the airplane mode getting stuck to "turning off" and I can't use my mobile network. I can flash my official T-Mobile RUU zip and things will work fine, but if I flash twrp on official it breaks. I switched over to the unlocked Dev rom and it breaks. I can only get my official zip working. Any help?
My specs are:
Android 7.0
2.51.617.32
S-off locked
1.0.U010241a 6117.76.02_f radio
Switched cid to bs_us01 or whatever the Dev cid is. For the rom. Other than lineageOS which didn't work, I haven't tried any other rom except dev.
Click to expand...
Click to collapse
That's odd, flashing twrp works fine for me. maybe you need to unlock to be able to use twrp?
Mr Hofs said:
Especially going from stock sense to an AOSP style rom it's wise to wipe the whole thing because you don't want to mix two roms, strange behavior may occur.
Follow the instructions in the specific thread, if you want to run the phone unencrypted then you need to format data indeed.
Click to expand...
Click to collapse
Just an update, i flashed the Unofficial LineageOS 15.1 ROM and it works perfectly, thank you so much for your help it is greatly appreciated!
Mr Hofs said:
Especially going from stock sense to an AOSP style rom it's wise to wipe the whole thing because you don't want to mix two roms, strange behavior may occur.
Follow the instructions in the specific thread, if you want to run the phone unencrypted then you need to format data indeed.
Click to expand...
Click to collapse
Just an update, i flashed the Unofficial LineageOS 15.1 ROM and it works perfectly, thank you so much for your help it is greatly appreciated!
UPDATE 2: The rom flash didnt go as well as i thought, the camera and flashlight didnt work nomatter what i did so i went back to RUU Stock and it worked fine
twosaltyy said:
That's odd, flashing twrp works fine for me. maybe you need to unlock to be able to use twrp?
Click to expand...
Click to collapse
Twrp works and flashes normal, it just breaks my airplane mode making the network unusable when I try to do any sort of modding to stock.
kazuki1 said:
Twrp works and flashes normal, it just breaks my airplane mode making the network unusable when I try to do any sort of modding to stock.
Click to expand...
Click to collapse
Just as all the other comments, read what you are flashing and which roms.
Nougat firmware - nougat roms
Oreo firmware - oreo roms
You have NOUGAT firmware so ONLY nougat roms work.
G
Mr Hofs said:
Just as all the other comments, read what you are flashing and which roms.
Nougat firmware - nougat roms
Oreo firmware - oreo roms
You have NOUGAT firmware so ONLY nougat roms work.
Click to expand...
Click to collapse
I am flashing nougat roms, the wwe/dev rom I have running atm(which is giving me airplane issues) is the same as the official T-Mobile ruu I have that works, only difference is that it's the dev edition instead of t-mobile, same firmware and both are Android 7.0. Flashing full RUU and not any of these custom roms on here. I had only flashed lineage to see what it was like But got rid of it and put on my working T-Mobile ruu.
Both T-Mobile and dev edition RUU is taken from the official HTC website, they're the exact same thing.