htc one m8 "variant system version" !!!! - One (M8) Q&A, Help & Troubleshooting

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 ...

Related

[Q] unlock bootloader and OTA

I know some will say its answered somewhere in the forum , but i searched and it didnt give me a clear answer,
if i unlocked the bootloader and installed CWM and rooted my phone wothout flashing a new ROM, will i lose the ability to recive OTAs?
one more thing (sorry im asking alot) unlocking bootloader says that it will erase all phone data , does that include the SD card part of our phone since its internal ? will i lose the photos stored , or its just like flashing an RUU
Thank you so much
ahm09 said:
I know some will say its answered somewhere in the forum , but i searched and it didnt give me a clear answer,
if i unlocked the bootloader and installed CWM and rooted my phone wothout flashing a new ROM, will i lose the ability to recive OTAs?
one more thing (sorry im asking alot) unlocking bootloader says that it will erase all phone data , does that include the SD card part of our phone since its internal ? will i lose the photos stored , or its just like flashing an RUU
Thank you so much
Click to expand...
Click to collapse
Firstly, yes you will lose the ability to receive OTA updates. With regards to the SD Card this will remain untouched.
dr9722 said:
Firstly, yes you will lose the ability to receive OTA updates. With regards to the SD Card this will remain untouched.
Click to expand...
Click to collapse
Thanks for your quick reply , so if i managed to download the OTA from the web can i flash them Manually knowing that i still have the stock ROM
ahm09 said:
Thanks for your quick reply , so if i managed to download the OTA from the web can i flash them Manually knowing that i still have the stock ROM
Click to expand...
Click to collapse
Are you planning on using a stock rom or a custom rom?
EDIT: Sorry didn't read properly. Yes if you are using stock rom then you should be able to download the OTA update from somewhere on XDA. If you are using a custom rom then the chances are the Dev would have already updated there rom to the latest base.
dr9722 said:
Are you planning on using a stock rom or a custom rom?
Click to expand...
Click to collapse
for the time being I'm staying with the stock ROM , my only aim here is to get root access nothing more
EDIT: sorry i replied before seeing the edit , thanks a lot for the help
ahm09 said:
for the time being I'm staying with the stock ROM , my only aim here is to get root access nothing more
EDIT: sorry i replied before seeing the edit , thanks a lot for the help
Click to expand...
Click to collapse
Sorry to ask additional question:
If I intended to use stock ROM only and continue to receive OTA update but with rooted phone. What is the best suggestion?
phonixloo said:
Sorry to ask additional question:
If I intended to use stock ROM only and continue to receive OTA update but with rooted phone. What is the best suggestion?
Click to expand...
Click to collapse
in my understanding , you will have to unlock the bootloader and install a CWM recovery to root your phone and keep the stock ROM, but you will have to download and install the OTAs manually
see this link for more info : http://forum.xda-developers.com/showthread.php?t=1577671
phonixloo said:
Sorry to ask additional question:
If I intended to use stock ROM only and continue to receive OTA update but with rooted phone. What is the best suggestion?
Click to expand...
Click to collapse
Just flash back the stock recovery, relock the bootloader, reboot the phone, receive OTA update and install. Then re-root process again to have root access.
ahm09 said:
in my understanding , you will have to unlock the bootloader and install a CWM recovery to root your phone and keep the stock ROM, but you will have to download and install the OTAs manually
see this link for more info : http://forum.xda-developers.com/showthread.php?t=1577671
Click to expand...
Click to collapse
But I suppose this way you can't update the HBOOT and Radio ....
---------- Post added at 02:03 PM ---------- Previous post was at 01:59 PM ----------
ckpv5 said:
Just flash back the stock recovery, relock the bootloader, reboot the phone, receive OTA update and install. Then re-root process again to have root access.
Click to expand...
Click to collapse
Just wonder where to find the stock recovery? If my ROM is 1.28.xxxx then I must use back the 1.28.xxx stock recovery img file, isn't it? Where should I look for the exact stock recovery img file?
phonixloo said:
Just wonder where to find the stock recovery? If my ROM is 1.28.xxxx then I must use back the 1.28.xxx stock recovery img file, isn't it? Where should I look for the exact stock recovery img file?
Click to expand...
Click to collapse
This is the stock recovery for 1.28.707.10, I believe yours is same as mine.

[Q] JB OTA update fails on rooted Vodafone One X

Hello guys,
I have a HTC One X from Vodafone, rooted, unlocked, stock rom, custom recovery, and today (FINALLY ) I received the OTA update to Jelly Bean.
I downloaded it and tried to install it using the custom recovery but it was failing on some assert. I guessed that it was because of the recovery so I flashed back the stock recovery and tried to install; fail again.
Went online and found the directory for the update log and saw an entry saying that there was a problem trying to verify the stock Dropbox apk that comes with the phone and that is placed on /system/apps. I read somewhere that if you modify something on the stock apks the OTA would fail, and unfortunatelly I did, I flashed the Galaxy S3 Dropbox apk on my phone, but that's not the problem, the problem is that I deleted the flashed Dropbox and the stock Dropbox from /system/apps without knowing it and the OTA is still failing.
My guess is that if I can flash the stock Dropbox apk to /system/apps, the OTA will try to verify it and will succeed, and therefore I'll have finally Jelly Bean on my branded device (as I said, is just a guess) so if someone could please send me the stock Dropbox apk, the one located in /system/apps as well as any other file located there that could possibly be related to Dropbox app, it will be very very appreciated.
If you guys think that I'm missing something here and even after flashing the stock Dropbox apk the OTA will still fail for some karma related reasons, please let me know and help me out.
If you need any other info from my phone let me know too.
If you need the .zip file with the official update from Vodafone I have it too.
Thanks in advance.
TO update OTA you SHOULD HAVE ONLY stock recovery and STOCK boot.img(kernel) ..and this way everything will be ok.
nemer12 said:
TO update OTA you SHOULD HAVE ONLY stock recovery and STOCK boot.img(kernel) ..and this way everything will be ok.
Click to expand...
Click to collapse
Well yes I have stock recovery (replaced the custom recovery yesterday) and stock kernel, I haven't changed the kernel yet, and according to the log the problem is with Dropbox. I'll try to find it and paste it here so you guys can see it.
Thanks.
Just flash the RUU, update OTA and reroot.
Alright, will do and I'll let you know how it goes. Thanks
Netrunner16 said:
Alright, will do and I'll let you know how it goes. Thanks
Click to expand...
Click to collapse
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
prankstarr said:
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
Click to expand...
Click to collapse
If you only unlocked the bootloader the update should run fine !!! If it fails you did change some more !
prankstarr said:
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
Click to expand...
Click to collapse
I think they're right, if I hadn't touched the system apps then I think the update would work, having only unlocked and rooted. Right after you try to install the update, go to /cache/recovery/ and check the logs for any clues on why the update is failing.
I'll try flashing the RUU for my phone, then applying the OTA and the rerooting as suggested, maybe you should try the same.
And rule number 1 after flashing cwm custom recovery is
always do a nandroid backup from the stock rom ! Now you know why its important.so when you go to JB and start rooting and running custom roms.....do the nandroid backup to avoid these situations !
Netrunner16 said:
I think they're right, if I hadn't touched the system apps then I think the update would work, having only unlocked and rooted. Right after you try to install the update, go to /cache/recovery/ and check the logs for any clues on why the update is failing.
I'll try flashing the RUU for my phone, then applying the OTA and the rerooting as suggested, maybe you should try the same.
Click to expand...
Click to collapse
I unlocked the bootloader (HTCDev)
I flashed CWR...
That was it (I am running a different launcher but that makes no different right??)
How do I get the RUU for Vodafone UK? Is that the stock ROM? Sorry, I am not very good with this stuff...I was okay at rooting my Desire HD but this is another level
prankstarr said:
I unlocked the bootloader (HTCDev)
I flashed CWR...
That was it (I am running a different launcher but that makes no different right??)
How do I get the RUU for Vodafone UK? Is that the stock ROM? Sorry, I am not very good with this stuff...I was okay at rooting my Desire HD but this is another level
Click to expand...
Click to collapse
You need to flash the stock recovery !
Do this command
Fastboot getvar version-main
If a number pops up starting with 2.17 you need to flash back this recovery
http://db.tt/U5CK4noo
And yes you did more than just unlock the bootloader, be specific .... it's necessary for this phone otherwise it gets confusing !
MarcelHofs said:
And rule number 1 after flashing cwm custom recovery is
always do a nandroid backup from the stock rom ! Now you know why its important.so when you go to JB and start rooting and running custom roms.....do the nandroid backup to avoid these situations !
Click to expand...
Click to collapse
But I still have the stock ROM. I never flashed a custom ROM. I wanted to flash a JB rom, thats why i rooted...then I discovered that my CID was not capable of getting a JB ROM so I just left it rooted but on stock voda ROM...
Doesn't matter .... Did u read my post above yours ....
Last time .....
You need stock rom,stock kernel, STOCK RECOVERY....not the custom cwm recovery. That's why the update fails. :thumbup:
prankstarr said:
But I still have the stock ROM. I never flashed a custom ROM. I wanted to flash a JB rom, thats why i rooted...then I discovered that my CID was not capable of getting a JB ROM so I just left it rooted but on stock voda ROM...
Click to expand...
Click to collapse
But you said you had CWR, you need to flash the stock recovery back and then try the update.
MarcelHofs said:
You need to flash the stock recovery !
Do this command
Fastboot getvar version-main
If a number pops up starting with 2.17 you need to flash back this recovery
http://db.tt/U5CK4noo
And yes you did more than just unlock the bootloader, be specific .... it's necessary for this phone otherwise it gets confusing !
Click to expand...
Click to collapse
Okay cool - will try although I thought I flashed stock recovery. I got rid of CMR when I got in from work today ... recovery img was in the fastboot folder i used when unlocking bootloader.
---------- Post added at 12:20 AM ---------- Previous post was at 12:14 AM ----------
Netrunner16 said:
But you said you had CWR, you need to flash the stock recovery back and then try the update.
Click to expand...
Click to collapse
Yes, I thought i flashed stock before but am about to confirm
The goal after unlocking the bootloader is to flash a custom recovery to flash different roms.....therefore i doubt u flashed the stock recovery.....unlocking the bootloader and flashing a stock recovery doesn't make sense
MarcelHofs said:
Doesn't matter .... Did u read my post above yours ....
Last time .....
You need stock rom,stock kernel, STOCK RECOVERY....not the custom cwm recovery. That's why the update fails. :thumbup:
Click to expand...
Click to collapse
Yes, sorry - i did read it and it did say 2.17xxx...I downloaded the recovery you pointed me to but expect i need to re-unlock the bootloader. (I re-locked it before thinking that was causing the issue...)
Anyway, soon I should know if this works
By the way, I really appreciate you helping me - i've been trying to sort this out all evening!
---------- Post added at 12:34 AM ---------- Previous post was at 12:29 AM ----------
MarcelHofs said:
The goal after unlocking the bootloader is to flash a custom recovery to flash different roms.....therefore i doubt u flashed the stock recovery.....unlocking the bootloader and flashing a stock recovery doesn't make sense
Click to expand...
Click to collapse
There is a good chance you are correct. The file in my fastboot folder said recovery and I assumed it was what I was after but it may have been connected to something that I was told to download in the unlocking process (I followed a guide on Youtube by a chap called cursed4eva)
I'm reunlocking the bootloader now because I got an error wh3n i tried to flash that recovery img. "writing 'recovery'... FAILED (remote: not allowed)"
---------- Post added at 01:24 AM ---------- Previous post was at 12:34 AM ----------
Okay - so I
1/ reunlocked the bootloader which basically wiped the phone back to its initialt state all be it with an unlocked bootloader.
2/ once again completed the OTA download of Vodafone Jellybean for the One X
3/ flashed the 2.17 recovery img that Marcel provided
4/ tried to update
5/ am currently looking at a download / progress bar! (YESSSS!)
6/ am hoping this works!
Thanks a lot Marcel. I very much appreciate your patience!
dr9722 said:
Just flash the RUU, update OTA and reroot.
Click to expand...
Click to collapse
I already have the RUU for my phone, and I was planning to follow this tutorial: http://forum.xda-developers.com/showthread.php?t=1660807
But I was thinking, what if I flash only the system.img instead of all the 3 files? I already have the stock recovery (the one you provided) and I've never changed the boot.img so I still have the stock one.
What about if I flash the system.img only, and then try the OTA update? Do you think that would work?
Thanks for the help.
Yes you can try that, the phone is already wiped with unlocking the bootloader, i never tried it. But in logical terms it is possible yes. If doesn't work you can always run the complete ruu !
That's weird, I'm getting error 00000006 when trying to flash the system.img.
Reading on other posts that's related to the size of the file, which is around 1 GB. If I can't flash the system.img I think I wont be able to run the entire RUU either.
Do you know a way to bypass this error?

[Q] Updating Bootloader for CM12?

Trying to flash CM12 Rom and it fails cause it needs 3.19.0.00 Bootloader? I am currently on bootloader 3.16.0.00. Any way to update for this ROM
Sent from my HTC6525LVW using XDA Free mobile app
Update your FW
I'm on 4.4.2 after restoring from being hard bricked. Would 4.4.4 Ota update from Verizon have the new bootloader?
kenferrari13 said:
I'm on 4.4.2 after restoring from being hard bricked. Would 4.4.4 Ota update from Verizon have the new bootloader?
Click to expand...
Click to collapse
Short answer, yes
Long answer, do the research. Learn what you're doing. Open an OTA and have a look inside
And read my signature regarding DMs...
I tried installing a 4.4.4 ota from Verizon and it fails. Does it need stock recovery? I have clockwork on there currently
kenferrari13 said:
I tried installing a 4.4.4 ota from Verizon and it fails. Does it need stock recovery? I have clockwork on there currently
Click to expand...
Click to collapse
Yes. Also, if there is a 4.4.3 OTA for Verizon, you need to install that first before going to 4.4.4.
yes you need the stock recovery. I am having the same issue, although I have CM11 and TWRP and I can not seem to find the telus nandoid or recovery for 3.16
Sorry I meant to say 4.4.3 update and it failed on me.
kenferrari13 said:
I'm on 4.4.2 after restoring from being hard bricked.
Click to expand...
Click to collapse
"Hard brick" or "brick" means you had to open the phone to recovery (JTAG, replace motherboard, etc.). Is this what happened to you?
---------- Post added at 01:26 PM ---------- Previous post was at 01:25 PM ----------
kenferrari13 said:
Sorry I meant to say 4.4.3 update and it failed on me.
Click to expand...
Click to collapse
Failed how? Did it give you an error message about the phone being modified?
You need to be on the stock ROM (no system files altered by root) in order to OTA.
I didn't have to replace any hardware. I guess it was more of a soft brick cause it would show splash screen and then freeze.
Well if I install a 4.4.4 Rom from the forums instead of ota Verizon will it have hboot files included?
kenferrari13 said:
Well if I install a 4.4.4 Rom from the forums instead of ota Verizon will it have hboot files included?
Click to expand...
Click to collapse
Nope. Hboot is not included in a ROM.
But it would be included in a firmware package (s-off required to flash).
I do have s off but when I go to flash an hboot update 3.19.0.00 it starts then says installation aborted in CWM! What gives?
Have a thread for HTC One M8 Verizon HBoot downloads that will flash in Clockwork? Maybe my file is corrupt.
You don't flash FW via CWM, you flash it through fastboot. Have you actually read anything?
Well I have read a ton on this I just don't know my terminology that well. I have been trying to flash hboot.zip which i read can be flashed in cw and it fails. I have also tried fastboot install with platform tools/RUU as well and can't get it. I'll try again tonight and report back. Just trying to learn a little here sorry if I'm not up to your standards EddyOS haha.
Well if you can't even spell my name right there's no hope...If you don't get the terminology then don't even start until you do! I didn't do anything until I learnt what I was doing and how to revert the changes I was making before I first rooted my Desire back in 2010 (and it was a lot more technical back then too!)
Okay bud thanks for that! I was only kidding, learn by doing.

Help, back to stock from lollipop

Hi, first of all:sorry my english. I have a 820n from Orange spain. Im S-On. Twrp and Tomal's Discovery rom. When i got the smartphone, it was on kitkat, i updated via wifi to lollipop, then i rooted it and install tomal rom. I have a Ruu oficial from Orange, but its kitkat Ruu, when i try to install it stuck on 4%. I relock bootloader and install stock recovery when i try to flash the Kitkat Ruu, but always stuck on 4%. Anyone can help me? Its because im on lollipop firmware now? What i can do? Only wait for another official lollipop Ruu from orange? Thanks
Unlock BL, flash newest TWRP from fergy, wipe, and flash this http://forum.xda-developers.com/desire-820/development/recovery-htc-desire-d820n-stock-t3104448
Then you go back to stock. Remember, don't relock BL when you have custom kernel like in tomal rom
Thanks a lot Skorupa123 tomorrow i will test. Only last question: if i am on tomals 2.0 (lollipop) and i flash that dump i will be able to flash kitkat ruu?
After test, didnt work. Unable to flash stock ruu.
TyrellCorporation said:
Thanks a lot Skorupa123 tomorrow i will test. Only last question: if i am on tomals 2.0 (lollipop) and i flash that dump i will be able to flash kitkat ruu?
Click to expand...
Click to collapse
No
---------- Post added at 06:45 AM ---------- Previous post was at 06:37 AM ----------
TyrellCorporation said:
After test, didnt work. Unable to flash stock ruu.
Click to expand...
Click to collapse
5.0.2 Europe HTC Desire d820n,процессор Qualcomm Factory https://yadi.sk/d/dEwiblxjmieVS 4.4.4 Factory https://yadi.sk/d/OrB3smMAmiGoy
Thanks a lot vuk1963. Will test today.
Downloading 5.0.2 Europe file, but im S-On . If CID doesnt match, then i go to crash again. I will test anyway.
vuk1963 said:
No
---------- Post added at 06:45 AM ---------- Previous post was at 06:37 AM ----------
5.0.2 Europe HTC Desire d820n,процессор Qualcomm Factory https://yadi.sk/d/dEwiblxjmieVS 4.4.4 Factory https://yadi.sk/d/OrB3smMAmiGoy
Click to expand...
Click to collapse
Its that 5.0.2 from ORANGE SPAIN?
This Europe,stock
vuk1963 said:
This Europe,stock
Click to expand...
Click to collapse
I was able to flash that backup but i think its no-secure (preinstalled external russian email and recover data..) and i can't get updates from my operator to upgrade.
I can't restore default settings, when i try to "set devide to defaults" the devide stucks on recovery.
TyrellCorporation said:
I was able to flash that backup but i think its no-secure (preinstalled external russian email and recover data..) and i can't get updates from my operator to upgrade.
I can't restore default settings, when i try to "set devide to defaults" the devide stucks on recovery.
Click to expand...
Click to collapse
It is necessary to establish the stock rekaveri and reset the default settings
vuk1963 said:
It is necessary to establish the stock rekaveri and reset the default settings
Click to expand...
Click to collapse
Just make it work now
1- I flash the russian stock backup
2- I reboot into recovery and wipe all, then i re-start the system and it was totally stock (no russian languaje, no preconfigured system)
3- i get the OTA from orange and i rename it to 0PFJIMG.zip and i put on sdcard (Ext), then i install it.
4- i flash stock recovery from firmware.zip inside the OTA
5- i re-lock the bootloader
6- done, all stock. No orange apps, but better keep away that bloatware.
7 - Thanks friend

Slow performance, lagging, low battery

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.

Categories

Resources