Ragazzi ho acquistato un m8 di seconda mano con su la viperone...vorrei tornare a stock.. Mi potere aiutare per favore? Non ho esperienza di modding con htc
Guys I buy a m8 used on the viperone ... I would go back to stock .. can you help me please? I have no experience of modding with htc.. Sorry forma my english
Do you know how to boot to bootloader ? And write here what's written on it ?
ckpv5 said:
Do you know how to boot to bootloader ? And write here what's written on it ?
Click to expand...
Click to collapse
hey ckpv5
I want too to return my htc one m8 to complete factory stock, stock rom with ota updates
I am currently S-OFF and bootloader unlocked
any help to do this please ?
You can read this : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Without info, can't help much. You need to provide your fastboot getvar all details
Being S-Off, I believe it is very much easier to return to stock (unless your stock is a rare version)
ckpv5 said:
You can read this : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Without info, can't help much. You need to provide your fastboot getvar all details
Being S-Off, I believe it is very much easier to return to stock (unless your stock is a rare version)
Click to expand...
Click to collapse
hey again
here are the details :
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 1.22.21331147A1.29G
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.28.401.9
INFOversion-misc: PVT SHIP S-OFF
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B10000
INFOcidnum: HTC__002
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: df77f8b7
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.020s
dave_lp said:
hey again
here are the details :
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 1.22.21331147A1.29G
INFOversion-main: 3.28.401.9
INFOversion-misc: PVT SHIP S-OFF
INFOmodelid: 0P6B10000
INFOcidnum: HTC__002
Click to expand...
Click to collapse
First - delete the serial no. & imei no. on your above post.
Now you have two options:
1. The RUU way - you need a Windows PC with USB2.0, latest HTC USB driver installed.
RUU will wipe everything and make your phone out of the box state, so make backup of your important files like music, photos & etc from your internal storage
Download the RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed.exe
Here : http://androidruu.com/?developer=M8
Connect your device to PC (preferable put it on bootloader/fastboot mode)
Right click the RUU exe and select run as administrator and follow all the instructions until it completes the process.
This will take you directly to lollipop and then do OTA to 4.16.401.13
2. The nandroid backup way - the link that I gave you earlier and read thoroughly the 14 steps on post #1
Install TWRP 2.8.70
Restore the 3.28.401.9 backup
Install the 3.28.401.9 stock recovery
Reboot, then do OTA to 4.16.401.10 then OTA to 4.16.401.13
I will follow all the steps and I will keep you informed.
Thank you very much for your help ckpv5
ckpv5 said:
First - delete the serial no. & imei no. on your above post.
Now you have two options:
1. The RUU way - you need a Windows PC with USB2.0, latest HTC USB driver installed.
RUU will wipe everything and make your phone out of the box state, so make backup of your important files like music, photos & etc from your internal storage
Download the RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed.exe
Here : http://androidruu.com/?developer=M8
Connect your device to PC (preferable put it on bootloader/fastboot mode)
Right click the RUU exe and select run as administrator and follow all the instructions until it completes the process.
This will take you directly to lollipop and then do OTA to 4.16.401.13
2. The nandroid backup way - the link that I gave you earlier and read thoroughly the 14 steps on post #1
Install TWRP 2.8.70
Restore the 3.28.401.9 backup
Install the 3.28.401.9 stock recovery
Reboot, then do OTA to 4.16.401.10 then OTA to 4.16.401.13
Click to expand...
Click to collapse
The RUU way not working, I tried it on 3 PC, an error comes up when I right click and try to run as administrator
An error (-5001 : 0x80070002) has occurred while running the setup.
Please make sure you have finished any previous setup and closed other application.
If the error still occurs, please contact your vendor.
dave_lp said:
The RUU way not working, I tried it on 3 PC, an error comes up when I right click and try to run as administrator
An error (-5001 : 0x80070002) has occurred while running the setup.
Please make sure you have finished any previous setup and closed other application.
If the error still occurs, please contact your vendor.
Click to expand...
Click to collapse
Tried on 3 PC but the same downloaded RUU ?
You may have bad download. Check the md5, it should match
8cb9b5d9091164cd57b6e04459bee3c6
ckpv5 said:
Tried on 3 PC but the same downloaded RUU ?
You may have bad download. Check the md5, it should match
8cb9b5d9091164cd57b6e04459bee3c6
Click to expand...
Click to collapse
Effectively, the MD5 doesn't match, I redownloaded it and everything was fine, the installation done without issue, actually I'm 4.16.401.13.
That's really nice I finally can do OTA updates
I could not have made it without your help.
Thank you so much
I'd like to reinstall a custom rom because this one eats a lot the battery
If it's not too much to ask again, I'd like to know in case I want to reinstall a custom rom, how do I proceed ?
because I saw your custom roms and they made me want to try them, they look awesome
Thanks in advance
dave_lp said:
If it's not too much to ask again, I'd like to know in case I want to reinstall a custom rom, how do I proceed ?
because I saw your custom roms and they made me want to try them, they look awesome
Thanks in advance
Click to expand...
Click to collapse
Give me 1/2 hour to respond.. bit busy, no need to bump again
ckpv5 said:
Tried on 3 PC but the same downloaded RUU ?
You may have bad download. Check the md5, it should match
8cb9b5d9091164cd57b6e04459bee3c6
Click to expand...
Click to collapse
If it's not too much to ask again, I'd like to know in case I want to reinstall a custom rom, how do I proceed ?
because I saw your custom roms and they made me want to try them, they look awesome besides the ota update eats a lot my battery
Thanks in advance
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
ckpv5 said:
Give me 1/2 hour to respond.. bit busy, no need to bump again
Click to expand...
Click to collapse
ok sorry
dave_lp said:
If it's not too much to ask again, I'd like to know in case I want to reinstall a custom rom, how do I proceed ?
because I saw your custom roms and they made me want to try them, they look awesome
Thanks in advance
Click to expand...
Click to collapse
I don't release any personal custom ROM
What you see is the custom ROM that I use to help fixing things here & there.
Your device is S-Off and still bootloader unlocked, right ?
To install custom ROM :
1. Install TWRP 2.8.7.0 - you know where to get it because you've been in my thread before
2. Put the custom ROM.zip to your internal or external storage
3. In TWRP make a backup of your current ROM
4. In TWRP select install menu then select the ROM.zip to install
5. Reboot .. done
For you to read - http://forum.xda-developers.com/showthread.php?t=2744194
ckpv5 said:
I don't release any personal custom ROM
What you see is the custom ROM that I use to help fixing things here & there.
Your device is S-Off and still bootloader unlocked, right ?
To install custom ROM :
1. Install TWRP 2.8.7.0 - you know where to get it because you've been in my thread before
2. Put the custom ROM.zip to your internal or external storage
3. In TWRP make a backup of your current ROM
4. In TWRP select install menu then select the ROM.zip to install
5. Reboot .. done
For you to read - http://forum.xda-developers.com/showthread.php?t=2744194
Click to expand...
Click to collapse
well, so following these steps i can install any custom rom ?
thank you for all and for the link, this gonna answer lot of my questions
dave_lp said:
well, so following these steps i can install any custom rom ?
thank you for all and for the link, this gonna answer lot of my questions
Click to expand...
Click to collapse
Yes .. the basic steps to install any custom ROM. Anything extra you can read the ROM thread instructions
And thanks for that I just received. It is highly appreciated
ckpv5 said:
Yes .. the basic steps to install any custom ROM. Anything extra you can read the ROM thread instructions
And thanks for that I just received. It is highly appreciated
Click to expand...
Click to collapse
Well, I just installed TWRP 2.8.7.0 and made a backup of my current ROM, then I downloaded SkyDragon M8 v1.5.1 Sense 7 Android 6.0 from here : http://forum.xda-developers.com/htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062378
and before attempting the installation I wanted to be sure that I'm not wrong choosing the custom ROM
also after finishing the backup and the device was about rebooting, TWRP asked to swip to install supersu to root the device
so swiping to install supersu will root my device ?
and last question pls if it's not too much asking
In case I want to reinstall the stock ROM again, shall I run the stock ROM I downloaded as you explained me above through RUU way ?
asking too many questions because it's a demo unit device and I want to switch between stock and custom ROM without bricking it
and thanks to you too
dave_lp said:
Well, I just installed TWRP 2.8.7.0 and made a backup of my current ROM, then I downloaded SkyDragon M8 v1.5.1 Sense 7 Android 6.0 from here : http://forum.xda-developers.com/htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062378
and before attempting the installation I wanted to be sure that I'm not wrong choosing the custom ROM
also after finishing the backup and the device was about rebooting, TWRP asked to swip to install supersu to root the device
so swiping to install supersu will root my device ?
and last question pls if it's not too much asking
In case I want to reinstall the stock ROM again, shall I run the stock ROM I downloaded as you explained me above through RUU way ?
asking too many questions because it's a demo unit device and I want to switch between stock and custom ROM without bricking it
and thanks to you too
Click to expand...
Click to collapse
You can ask any question related to the ROM in the ROM thread because this thread is about stock ROM
When you want to reinstall stock ROM, just restore the backup that you made. The RUU was for a lower version, now your firmware/software is at higher version.
TWRP ask about root because you have non-rooted custom ROM. If you want to run a rooted stock ROM, yes just swipe to root.
If you want to install custom ROM, no need to root because custom ROM is pre-rooted.
I have no idea about demo unit, but I believe a clean stock ROM or a custom ROM will remove that. You run the RUU before and updated to the latest, it is no more demo feature running, right ?
ckpv5 said:
You can ask any question related to the ROM in the ROM thread because this thread is about stock ROM
When you want to reinstall stock ROM, just restore the backup that you made. The RUU was for a lower version, now your firmware/software is at higher version.
TWRP ask about root because you have non-rooted custom ROM. If you want to run a rooted stock ROM, yes just swipe to root.
If you want to install custom ROM, no need to root because custom ROM is pre-rooted.
I have no idea about demo unit, but I believe a clean stock ROM or a custom ROM will remove that. You run the RUU before and updated to the latest, it is no more demo feature running, right ?
Click to expand...
Click to collapse
Do I need to wipe everything before to select install in the TWRP menu or no need to wipe ? will I just select the ROM.zip in the TWRP install menu to install ?
I believe a custom rom will remove the demo unit but not the stock rom, after OTA update, an application called demo that I cant uninstall was installed itself and plays a demo video every 2 or so minutes and some others stuff like rebooting the device was removing my installed applications...
I couldn't do a factory reset as the OK button was greyed out, the developer mode can't be touched but USB debugging mode was on when I connect it to the PC so I tried to factory reset from the bootloader, it worked, and when the devide loaded I disabled all automatic updates so till now it works as a normal phone
updating it may mess it up again
I read HERE if I supercid! (11111111) will have a 100% generic device, OTA updates and all... Demo won't even install. Any knowledge about how to supercid ?
Thanks
Related
Hey guys im new to xda and also ROMs in general so any help at all would be much appreciated!
Im trying to flash a ROM so i can use my HTC one M8, im currently stuck on bootloader/recovery.
I have tried to flash 6 different ROM.zip files with no success, i get all prompts as though the file flashed successfully but when i reboot system im still stuck on bootloader.
what i have been doing is
1. move .zip file to SD card
2. open TWRP wipe dalvik/cache
3.install .zip from SD using TWRP
Is there something missing or is it the ROMs i used?
i dunno if this is right but I was told i need a ROM that is specific to Australia, i havent found one
so if anyone has an Australian HTC one M8 ROM, or just one that will definately work on my phone could you please post a link?
Im happy to share more information if you think you could help me
thank you all for reading!
andrewwilba said:
Hey guys im new to xda and also ROMs in general so any help at all would be much appreciated!
Im trying to flash a ROM so i can use my HTC one M8, im currently stuck on bootloader/recovery.
I have tried to flash 6 different ROM.zip files with no success, i get all prompts as though the file flashed successfully but when i reboot system im still stuck on bootloader.
what i have been doing is
1. move .zip file to SD card
2. open TWRP wipe dalvik/cache
3.install .zip from SD using TWRP
Is there something missing or is it the ROMs i used?
i dunno if this is right but I was told i need a ROM that is specific to Australia, i havent found one
so if anyone has an Australian HTC one M8 ROM, or just one that will definately work on my phone could you please post a link?
Im happy to share more information if you think you could help me
thank you all for reading!
Click to expand...
Click to collapse
the way you are flashing sounds fine, which rom's have you tried ? and which version of TWRP ? also could you please post your fastboot getvar all without imei and serial number please.
Seanie280672 said:
the way you are flashing sounds fine, which rom's have you tried ? and which version of TWRP ? also could you please post your fastboot getvar all without imei and serial number please.
Click to expand...
Click to collapse
thank you for the quick response um i've tried the viper 2.0, hdrevolution 1.1, lollipop something, i even tried a couple stock ruu's from the htc website but nothing has worked yet.
my TWRP version is 2.7.0.2
and here is my getvar all
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.2133156.UA15_2G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B11000
cidnum: TELST001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: ab0efa49
hbootpreupdate: 11
gencheckpt: 0
Restore TELSTRA 1.54.841.8 backup and install its stock recovery, reboot then do OTA update to the latest lollipop OTA ...
then you can install any custom Sense based ROM that you like.
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
ckpv5 said:
Restore TELSTRA 1.54.841.8 backup and install its stock recovery, reboot then do OTA update to the latest lollipop OTA ...
then you can install any custom Sense based ROM that you like.
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
where can i find the telstra 1.54.841.8? could you talk me through OTA updates please
andrewwilba said:
where can i find the telstra 1.54.841.8? could you talk me through OTA updates please
Click to expand...
Click to collapse
everything is explained in the link that I gave above.
Post #1 - how-to
Post #2 - where you can find 1.54.841.8 backup
Post #4 - where you can find 1.54.841.8 stock recovery
read that thread thoroughly.
ckpv5 said:
Restore TELSTRA 1.54.841.8 backup and install its stock recovery, reboot then do OTA update to the latest lollipop OTA ...
then you can install any custom Sense based ROM that you like.
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
im on your tutorial right now but im finding it hard to understand as im not fully up to speed with the process, do you mind talking me through each step from where i am now thank you
andrewwilba said:
im on your tutorial right now but im finding it hard to understand as im not fully up to speed with the process, do you mind talking me through each step from where i am now thank you
Click to expand...
Click to collapse
thank you for all your help so far im stuck again i transfered and restored backup and then fastboot recovery image and on reboot i got a triangle picture after htc logo?
ckpv5 said:
everything is explained in the link that I gave above.
Post #1 - how-to
Post #2 - where you can find 1.54.841.8 backup
Post #4 - where you can find 1.54.841.8 stock recovery
read that thread thoroughly.
Click to expand...
Click to collapse
i have followed your steps and after flashing recovery img, then reboot. i get a red triangle in front of a phone screen.
if you could please stay with me until i fix this i promise to donate to you. you have my word. its either that or pay whatever they tell me to
Do you really follow all steps from 1 to 11 (step 11 is when you need to flash stock recovery image)
1. You need to use TWRP 2.8.1.0 as recommended.
2. When you do restore, do you see the progress till it said success ?
From your above post, it seems the restore was not successful or not correctly done.
You can try again .. reflash/install TWRP 2.8.1.0 and follow the steps again.
Note : I don't do this for donations ... so don't worry about that.
ckpv5 said:
Do you really follow all steps from 1 to 11 (step 11 is when you need to flash stock recovery image)
1. You need to use TWRP 2.8.1.0 as recommended.
2. When you do restore, do you see the progress till it said success ?
From your above post, it seems the restore was not successful or not correctly done.
You can try again .. reflash/install TWRP 2.8.1.0 and follow the steps again.
Note : I don't do this for donations ... so don't worry about that.
Click to expand...
Click to collapse
YAY im back up and running after flashing TWRP 2.8.1.0! Just running OTA updates now thank you for your help ckpv5
ill be sure to give SkyDragon sense 7 a try before flashing anything else :good:
andrewwilba said:
YAY im back up and running after flashing TWRP 2.8.1.0! Just running OTA updates now thank you for your help ckpv5
ill be sure to give SkyDragon sense 7 a try before flashing anything else :good:
Click to expand...
Click to collapse
Great :good::good:
You're going to have multiples OTA (at least 3 OTAs) as your current base is too old. After one OTA done, check again for another one until it says no more updates.
After the last OTA which is Lollipop, to install a Sense based custom ROM, you need to flash/install TWRP 2.8.5.0 or 2.8.6.0 (recommended). Don't use any lower than 2.8.4.0
It's not needed .. thanks for the donation .. highly appreciated.
I restored my M8 International Unlocked Dual SIM Version to stock through a nandroid backup and then flashed one of the recoveries I found online but my phone won't update through OTA. I then tried restoring different backups. Some of which worked and some didn't even boot.
I finally came to the conclusion that it was because of the HBOOT version and maybe the version-main.
I want to know:
1- Understand version-main.
2- How can I know which nandroid backup is right for me. (and if possible point me to the right ones for me).
I searched quite some time but couldn't turn up with a complete answer. Forgive me if I missed something.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.30.401.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B64000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 49d38c68
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
GeekOmar said:
1- Understand version-main.
2- How can I know which nandroid backup is right for me. (and if possible point me to the right ones for me).
[/CODE]
Click to expand...
Click to collapse
I don't own the dual SIM, and can't speak that specifically on it. But what I can say:
1) Main version is the firmware number. It won't change when you restore a nandroid.
2) You will want a nandroid that matches your firmware number. If you are trying to flash backups for the "regular" (single SIM) M8, these will never work on your phone. Dual SIM nandroids are probably pretty limited.
GeekOmar said:
....but my phone won't update through OTA.
Click to expand...
Click to collapse
What's the error ?
Is it stuck on red triangle ? If yes, press & hold volume up button and press power button once. This will get you to recovery and read what error that you have there.
redpoint73 said:
I don't own the dual SIM, and can't speak that specifically on it. But what I can say:
1) Main version is the firmware number. It won't change when you restore a nandroid.
2) You will want a nandroid that matches your firmware number. If you are trying to flash backups for the "regular" (single SIM) M8, these will never work on your phone. Dual SIM nandroids are probably pretty limited.
Click to expand...
Click to collapse
Thank you Redpoint,
I bricked my phone before, and was able to fix it using the backups and recovery from the below link and everything was fine, I was able to install two OTAs and get lollipop.
http://forum.xda-developers.com/htc-one-m8/help/rooted-m8-dual-sim-bricked-s-t2979774
But now, when I restore that backup and original recovery, then install any OTA update, the screen becomes black. I know the phone is working fine as I can hear the sound when pressing the volume key or when someone calls. But no screen! The link above is to a thread made by me and the only difference i can see between that time and now is the HBOOT version and the radio/baseband. This is driving me crazy!
ckpv5 said:
What's the error ?
Is it stuck on red triangle ? If yes, press & hold volume up button and press power button once. This will get you to recovery and read what error that you have there.
Click to expand...
Click to collapse
The screen just becomes black. Phone works fine as I can hear incoming calls.
Come on people, is it that hard! There must be something that can be done.
Sent from my HTC One_M8 dual sim using XDA Forums
GeekOmar said:
Come on people, is it that hard! There must be something that can be done.
Click to expand...
Click to collapse
This is sounding really rude. How about asking nicely?
Nobody here is getting paid for their time, or sitting at their computer 24 hours a day to help you. You need some patience.
Plus, the dual SIM version is not terribly common/popular, so getting the specific help and files needed may be a challenge. Folks here are helping as much as they can, when they can.
Its hard enough, that you can't figure it out, right?
---------- Post added at 09:23 AM ---------- Previous post was at 09:16 AM ----------
GeekOmar said:
But now, when I restore that backup and original recovery, then install any OTA update, the screen becomes black.
Click to expand...
Click to collapse
What backup and what OTAs specifically? The statement is to vague for me to see what you did.
List the version of the backup (link to a link to a link doesn't help me) and what version OTAs did you try.
Where did you get the OTA files from (specific post, if applicable)?
GeekOmar said:
the only difference i can see between that time and now is the HBOOT version and the radio/baseband.
Click to expand...
Click to collapse
This means your firmware is different for before. This is not a minor thing, its a huge difference.
GeekOmar said:
The screen just becomes black. Phone works fine as I can hear incoming calls.
Click to expand...
Click to collapse
That's because you restored a very low version of backup when you have a high version firmware installed.
What I understand here, you restored 1.45.401.12 but your firmware is 4.30.401.15
When you restore a backup (when your device is S-On), the lowest version that may work on your device is 3.33.401.6 but not 1.45.401.12.
And the correct version to restore is 4.30.401.15
If you don't have this 4.30.401.15 backup and unable to find it for now, just to have a good running device, you can install custom ROM made for your device.
I believe this is a good one : http://llabtoofer.com/2015/05/08/htc-one-m8-dual-sim-maximushd-3-0-0/
(note : you should have made your own backup when you first fixed your previous problem)
redpoint73 said:
This is sounding really rude. How about asking nicely?
Nobody here is getting paid for their time, or sitting at their computer 24 hours a day to help you. You need some patience.
Plus, the dual SIM version is not terribly common/popular, so getting the specific help and files needed may be a challenge. Folks here are helping as much as they can, when they can.
Its hard enough, that you can't figure it out, right?
Click to expand...
Click to collapse
I didn't mean to sound rude. What I meant by my last post, was to encourage readers as I know it is a challenge and I wanted them to share their thoughts. I assure you that I AM grateful for your help otherwise I wouldn't thank you for your first post which suggested to restore a nandroid backup for a dual SIM which I already did.
Anyway, please accept my apologies for this misunderstanding.
What backup and what OTAs specifically? The statement is to vague for me to see what you did.
Click to expand...
Click to collapse
I restored the same backup that I used to fix my phone the first time. It is currently deleted but it said it was version 1.45.401.12. Which worked flawlessly and I was able to install OTA updates.
The update I'm trying to install currently is version: 3.33.401.6. for Android 4.4.4. It is an over the air update by the phone it self.
ckpv5 said:
That's because you restored a very low version of backup when you have a high version firmware installed.
What I understand here, you restored 1.45.401.12 but your firmware is 4.30.401.15
When you restore a backup (when your device is S-On), the lowest version that may work on your device is 3.33.401.6 but not 1.45.401.12.
And the correct version to restore is 4.30.401.15
If you don't have this 4.30.401.15 backup and unable to find it for now, just to have a good running device, you can install custom ROM made for your device.
I believe this is a good one : http://llabtoofer.com/2015/05/08/htc-one-m8-dual-sim-maximushd-3-0-0/
(note : you should have made your own backup when you first fixed your previous problem)
Click to expand...
Click to collapse
I'm keeping ROMs as a last option
How do you suggest I update my firmware?
Again, all are thanked for their valuable contributions.
This should help you : http://forum.xda-developers.com/htc-one-m8/help/m8-dugl-lollipop-upgrade-unlocking-t3098463
GeekOmar said:
Anyway, please accept my apologies for this misunderstanding.
Click to expand...
Click to collapse
No worries, your apology is accepted. And I gave you your first "Thanks" too!
I look at most all new posts in this section, and respond if I have something to contribute when I have the time (and ckpv5 looks to operate very much the same way). So the lack or response was due to me not being online, and otherwise unable to spend the time on XDA (and nagging won't change that). Therefore, "bumping" a thread to the top is usually not necessary. Or if you choose to do so, try to pose it as a polite appeal for help (in the form of a question, and using the word "please" can work wonders).
The way you posted it, sounded more like you were making a demand or giving orders.
GeekOmar said:
I restored the same backup that I used to fix my phone the first time. It is currently deleted but it said it was version 1.45.401.12. Which worked flawlessly and I was able to install OTA updates.
The update I'm trying to install currently is version: 3.33.401.6. for Android 4.4.4. It is an over the air update by the phone it self.
Click to expand...
Click to collapse
Did you install the 2.xx.401 OTA before trying 3.33.401? Because this is mandatory (OTAs need to be installed in sequence, and you can't skip any).
GeekOmar said:
How do you suggest I update my firmware?
Click to expand...
Click to collapse
Your main version, hboot, and radio numbers given in your top post all indicate you are on the current Lollipop firmware.
The issue is getting a ROM on the phone that matches the firmware, as ckpv5 has given you suggestions on how to do (4.30.401 nandroid is what you want, if you can find it).
You may be confusing "firmware" with "ROM", as they are not the same thing.
He can use one version lower 3.33.401.6 too.
And he can find that 3.33.401.6 backup in the link that I posted above.
Did you install the 2.xx.401 OTA before trying 3.33.401? Because this is mandatory (OTAs need to be installed in sequence, and you can't skip any).
Click to expand...
Click to collapse
I update as the phone asks. I abide by what it is asking.
Your main version, hboot, and radio numbers given in your top post all indicate you are on the current Lollipop firmware.
The issue is getting a ROM on the phone that matches the firmware, as ckpv5 has given you suggestions on how to do (4.30.401 nandroid is what you want, if you can find it).
You may be confusing "firmware" with "ROM", as they are not the same thing.
Click to expand...
Click to collapse
What I understand now, is that I got the firmware of Lollipop but I am still running Kitkat. Couldn't find any 4.30.401 nandroid.
ckpv5 said:
This should help you : http://forum.xda-developers.com/htc-one-m8/help/m8-dugl-lollipop-upgrade-unlocking-t3098463
Click to expand...
Click to collapse
I tried, that method. Flashed the rom, and it asked me to install Lollipop, which is good. But when flash stock recovery lock the bootloader. It boots straight to fastboot!
GeekOmar said:
I tried, that method. Flashed the rom, and it asked me to install Lollipop, which is good. But when flash stock recovery lock the bootloader. It boots straight to fastboot!
Click to expand...
Click to collapse
Why relock bootloader ? It's not needed. Unlock it again as you need to flash correct recovery.
Boot back to fastboot usually happen when you flash wrong recovery especially a recovery meant for other device.
From where you get the recovery ? You only mentioned somewhere on the net.
Use 3.33.401.6 recovery or 4.30.401.15 recovery. Either one should work. You can get them in link in my signature.
ckpv5 said:
Why relock bootloader ? It's not needed. Unlock it again as you need to flash correct recovery.
Boot back to fastboot usually happen when you flash wrong recovery especially a recovery meant for other device.
From where you get the recovery ? You only mentioned somewhere on the net.
Use 3.33.401.6 recovery or 4.30.401.15 recovery. Either one should work. You can get them in link in my signature.
Click to expand...
Click to collapse
I flashed the stock recovery so I locked the bootloader to install the OTA. Don't you need a locked boot loader to install an OTA?
Man, don't make me feel stupid more than I do now. I'll get a Nokia and then kill myself. [emoji30] [emoji379]
I'll try one of your recoveries as soon as I'm home.
ckpv5 said:
Why relock bootloader ? It's not needed. Unlock it again as you need to flash correct recovery.
Boot back to fastboot usually happen when you flash wrong recovery especially a recovery meant for other device.
From where you get the recovery ? You only mentioned somewhere on the net.
Use 3.33.401.6 recovery or 4.30.401.15 recovery. Either one should work. You can get them in link in my signature.
Click to expand...
Click to collapse
Sent from my TF700T using Tapatalk
GeekOmar said:
I flashed the stock recovery so I locked the bootloader to install the OTA. Don't you need a locked boot loader to install an OTA?
Click to expand...
Click to collapse
No .. no need a relocked bootloader for OTA. (doesn't matter your device is S-On or S-Off)
Relocked bootloader only needed when your device is S-On and you want to :
1. Install a HTC RUU
2. Install a HTC signed firmware
ckpv5 said:
No .. no need a relocked bootloader for OTA. (doesn't matter your device is S-On or S-Off)
Relocked bootloader only needed when your device is S-On and you want to :
1. Install a HTC RUU
2. Install a HTC signed firmware
Click to expand...
Click to collapse
Understood.
Ok, so I flashed that stock rom you mentioned earlier and and one of your stock recoveries and Voila! Everything is perfect, except WiFi. When I turn on WiFi, it says "Turning on.." and stays like this indefinitely. Any idea?
Well, I have tried everything to fix the WiFi problem to no avail. Finally I got fed up and decided to use the room you provided. Thanks ckpv for your help. I appreciate it.
Sent from my TF700T using Tapatalk
GeekOmar said:
Well, I have tried everything to fix the WiFi problem to no avail. Finally I got fed up and decided to use the room you provided. Thanks ckpv for your help. I appreciate it.
Sent from my TF700T using Tapatalk
Click to expand...
Click to collapse
I don't have your device version so I can't confirm anything why the wifi won't work on your device.
Anyway .. when you want to try again - see this : http://forum.xda-developers.com/showpost.php?p=56681264&postcount=113
a nandroid backup that you can restore and install the stock recovery and try to OTA again.
ckpv5 said:
I don't have your device version so I can't confirm anything why the wifi won't work on your device.
Anyway .. when you want to try again - see this : http://forum.xda-developers.com/showpost.php?p=56681264&postcount=113
a nandroid backup that you can restore and install the stock recovery and try to OTA again.
Click to expand...
Click to collapse
I'll give it a try.
Thank you for your help, you've done enough.
Sent from my HTC One_M8 dual sim using Tapatalk
As per the headline, I've got an HTC M8 that I rooted shortly after purchasing in 2014. When the Lollipop OTA upgrades came out, I was reading mixed reviews about battery life and system performance, so I used a quarantine app to freeze the auto-update app so that it would stop bothering me to upgrade all the time. Now that Marshmallow has been out for a few months, the reviews seem positive and say that battery life is improved and the device is just as responsive as it used to be, so now I want to upgrade my device to Marshmallow.
I'm more or less an android / phone newbie - I mainly just use my phone for email, web browsing, driving directions, taking photos and the occasional app like banking, I'm not into heavy customisation but would like to retain root for the ability to uninstall shovel-ware, freeze programs and so some minor customizations.
Anyway, since I have 4.4.3 Android rooted, which process should I follow to get Marshmallow rooted, while retaining all the current data on my phone (apps, phone contacts, etc)? Do I need to do an OTA upgrade to Lollipop, and from there do an upgrade to Marshmallow?
My phone is an unlocked HTC M8; it's not a GPE or other branded vendor phone. I live in New Zealand and I bought it parallel imported, I think it was originally from Hong Kong.
I already have some of the bootloader/recovery stuff sorted out from when I rooted it the first time. Going into bootloader this is what prints out for me:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 8 2014,15:18:03.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next time
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Click to expand...
Click to collapse
If I select recovery, then I get a recovery menu, and the version at the top is: Team Win Recovery Project v2.7.0.2
Please upgrade your firmware first through RUU to flash other ROMs.
[Edited]
Would this be the same as stock OTA?
Also wouldn't flashing a ROM destroy all my apps and data?
Lanthanide said:
Would this be the same as stock OTA?
Also wouldn't flashing a ROM destroy all my apps and data?
Click to expand...
Click to collapse
No the ROM won't be same as stock OTA,there are more or less modification in every ROM.The way you can exactly stock update by flashing RUU.
And yes all your apps and data will be wiped.Why don't you try titanium backup?you can backup all apps and app data with it.
Jongla said:
Upgrade TWRP to the latest version.
Flash any MM ROM with S-On support.Though most of the ROMs doesn't require S-On,but but read and read about the ROM before you flash it.
Edit:You can try ViperOne ROM for the first time,i find it more stable.
Click to expand...
Click to collapse
MM ROMs won't work properly with his old firmware. He will lose wifi, among other issues he will face. Updating his firmware is a MUST before he flashes a Marshmallow ROM
xunholyx said:
MM ROMs won't work properly with his old firmware. He will lose wifi, among other issues he will face. Updating his firmware is a MUST before he flashes a Marshmallow ROM
Click to expand...
Click to collapse
Sorry for the wrong infos.
I flashed other mm ROMs over lollipop firmware everything's working fine.
But just got to know about firmware upgrade myself an hour ago.
Sorry again.
Lanthanide said:
As per the headline, I've got an HTC M8 that I rooted shortly after purchasing in 2014. When the Lollipop OTA upgrades came out, I was reading mixed reviews about battery life and system performance, so I used a quarantine app to freeze the auto-update app so that it would stop bothering me to upgrade all the time. Now that Marshmallow has been out for a few months, the reviews seem positive and say that battery life is improved and the device is just as responsive as it used to be, so now I want to upgrade my device to Marshmallow.
I'm more or less an android / phone newbie - I mainly just use my phone for email, web browsing, driving directions, taking photos and the occasional app like banking, I'm not into heavy customisation but would like to retain root for the ability to uninstall shovel-ware, freeze programs and so some minor customizations.
Anyway, since I have 4.4.3 Android rooted, which process should I follow to get Marshmallow rooted, while retaining all the current data on my phone (apps, phone contacts, etc)? Do I need to do an OTA upgrade to Lollipop, and from there do an upgrade to Marshmallow?
My phone is an unlocked HTC M8; it's not a GPE or other branded vendor phone. I live in New Zealand and I bought it parallel imported, I think it was originally from Hong Kong.
I already have some of the bootloader/recovery stuff sorted out from when I rooted it the first time. Going into bootloader this is what prints out for me:
If I select recovery, then I get a recovery menu, and the version at the top is: Team Win Recovery Project v2.7.0.2
Click to expand...
Click to collapse
First off, you need to update your recovery. Go with TWRP 2.8.7.0 or higher.
Secondly, you can update and keep all of your data. Make a nandroid backup with your new recovery, then run the appropriate RUU to update, or go back to complete stock and take the OTAs that will get downloaded to your phone, then restore your nandroid. The new firmware won't get overwritten by restoring your backup. That partition isn't included in the backups.
Hook up your phone to your PC, get into fastboot, and enter the command fastboot getvar all. Post the results here (minus your IMEI & serial# ~ that's private info) and I or someone else here will direct you on the easiest way for you to update.
---------- Post added at 10:58 AM ---------- Previous post was at 10:57 AM ----------
Jongla said:
Sorry for the wrong infos.
I flashed other mm ROMs over lollipop firmware everything's working fine.
But just got to know about firmware upgrade myself an hour ago.
Sorry again.
Click to expand...
Click to collapse
Yeah, MM ROMs will work with Lollipop firmware, but not with KitKat like the OP has.
xunholyx said:
First off, you need to update your recovery. Go with TWRP 2.8.7.0 or higher.
Secondly, you can update and keep all of your data. Make a nandroid backup with your new recovery,
Click to expand...
Click to collapse
Is nandroid part of the recovery?
then run the appropriate RUU to update
Click to expand...
Click to collapse
What is an RUU?
or go back to complete stock and take the OTAs that will get downloaded to your phone
Click to expand...
Click to collapse
This implies that if I unfroze the OTA updater on my current software and let it simply upgrade, that it wouldn't work properly? So either way I have to "run the appropriate RUU", OR re-flash a stock 4.4.3 image and then do OTA upgrades on that?
Here's the getvar all output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.011s
Click to expand...
Click to collapse
Bump.
Lanthanide said:
Is nandroid part of the recovery?
Click to expand...
Click to collapse
No, a nandroid is a backup that is made by recovery (TWRP). It can back up the stock ROM, and user data (which is the goal in the above posted suggestion). After you update, you can restore the user data (but you don't want to restore the old ROM, since the goal is to get to MM - that part wasn't clear in the previous post).
Lanthanide said:
What is an RUU?
Click to expand...
Click to collapse
RUU = ROM Update Utility
Its an official HTC tool that completely updates or restores the stock image.
Lanthanide said:
This implies that if I unfroze the OTA updater on my current software and let it simply upgrade, that it wouldn't work properly? So either way I have to "run the appropriate RUU", OR re-flash a stock 4.4.3 image and then do OTA upgrades on that?
Click to expand...
Click to collapse
Since you rooted, you can't simply unfreeze the updater and OTA.
OTA requires restoring the stock ROM (never rooted, unrooting does not work) and stock recovery (you have TWRP now, which is a custom recovery). RUU is an easy way to restore the whole phone to stock condition.
Ok, so if I'm understanding this correctly:
* To use the OTA updates, I need to have a stock ROM, as well as a stock recovery (not TWRP)
* I can make a nandroid backup of user data in TWRP, and then use RUU to go back to a completely stock phone
* From there I can do OTA upgrades to get up to MM
* Then I can install the TWRP recovery and restore my user data
Another approach might be:
* Backup the user data using TWRP
* Use an appropriate RUU, or series of RUU's, to upgrade to MM, without using any OTA updates at all
* Restore user data
It seems like path 2 would be easier and less risky of making a mistake. So what RUU's do I need? The output of "getvar all" is available a few posts up.
Also is there an easy guide somewhere for how to upgrade to a newer version of TWRP?
Lanthanide said:
It seems like path 2 would be easier and less risky of making a mistake. So what RUU's do I need? The output of "getvar all" is available a few posts up.
Click to expand...
Click to collapse
Yes, path 2 (RUU) would be easier in your case. But unfortunately, I don't think you version has RUU. You'd be looking for an RUU for 6.12.709.4
That being the case, you need to resort to path 1 (return to stock and OTA updates).
Lanthanide said:
Also is there an easy guide somewhere for how to upgrade to a newer version of TWRP?
Click to expand...
Click to collapse
Fastboot install method is simple and reliable. Instructions and TWRP files here: https://twrp.me/devices/htconem8gsm.html
Since you already have fastboot working, just put the TWRP .img file in the same folder as wherever fastboot.exe is located, then connect the phone, and run the command:
fastboot flash recovery twrp.img
Right, I've just sat down to try and do this, and realised that I'm still not clear on what I actually need to do.
It seems there is no RUU for my phone for MM, which would be RUU for 6.12.709.4.
So instead I need any RUU that suits my phone for Kitkat or Lollipop, and then do OTA upgrades from there? So what RUU versions should I be looking for, since 6.12.709.4 does not exist?
Lanthanide said:
Right, I've just sat down to try and do this, and realised that I'm still not clear on what I actually need to do.
It seems there is no RUU for my phone for MM, which would be RUU for 6.12.709.4.
So instead I need any RUU that suits my phone for Kitkat or Lollipop, and then do OTA upgrades from there? So what RUU versions should I be looking for, since 6.12.709.4 does not exist?
Click to expand...
Click to collapse
There is no RUU for your device version. You can only restore to stock ROM and do OTAs up to the latest.
Your main mistake (I remember you have the same problem before) is restore your backup data after OTA done. Restoring old data that removed your apps like calculator & flashlight.
What you need to do (correctly):
1. Don't use that TWRP 2.7.0.2 .. install 2.8.10 or 2.8.3.0
2. Make a TWRP backup of your current data/system/boot
3. Restore non-rooted backup 2.22.709.3 (boot and system only - use your current data)
4. Install 2.22.709.3 stock recovery
5. Do multiple OTAs up to the latest 6.20.709.2
You'll upgrade your ROM and firmware but still have all your data intact.
All files needed are here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
If you happen to wipe all data & system before restore 2.22.709.3 (as per step 3), you can restore data only from your own backup before step 4 ... remember to restore your own data before OTA, not after OTA (if not you'll have your old problem again)
Concerned guys @ckpv5 , @Lanthanide and @redpoint73
I know this is an old thread but just for info, I found RUU for this particular CID HTC__621 on another site
Source: Removed to avoid confusion
RUU Link - Removed | Wrong file, was not an RUU
Though I'm not sure whether it is official or not (signed or not) as the name of the file is really small.
Mayank7795 said:
Concerned guys @ckpv5 , @Lanthanide and @redpoint73
I know this is an old thread but just for info, I found RUU for this particular CID HTC__621 on another site
Though I'm not sure whether it is official or not (signed or not) as the name of the file is really small.
Click to expand...
Click to collapse
That's not RUU ... it's a ROM flashable zip. Maybe you better remove the link so it won't confused others.
Right, I've finally gotten around to doing this, and the process was pretty straighforward. Thanks very much for your excellent help ckpv5.
So I'm now on 6.20.709.2, but I don't have root. How can I root this phone?
Lanthanide said:
Right, I've finally gotten around to doing this, and the process was pretty straighforward. Thanks very much for your excellent help ckpv5.
So I'm now on 6.20.709.2, but I don't have root. How can I root this phone?
Click to expand...
Click to collapse
Install latest TWRP 3.0.2-0 - https://dl.twrp.me/m8/
Install latest stable SuperSU 2.65 in recovery - https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
It's better to install custom kernel as custom kernel has system write protection disabled.
Hi folks, So finally i am ready to update my Supersu rooted,S-OFF, Rogers M8 to the marshmallow OTA update which has been showing as a notification from the last couple of months.I asked same question last year but at that time there was no easy way to update the rooted phone other than finding stock backup.
Any new way came to update without finding stock backup?I would really appreciate if someone can give step by step.Thanks.
C:\>cd adb
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.631.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXX
(bootloader) imei: XXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 4a2bcc8a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.058s
Click to expand...
Click to collapse
ninja_zx11 said:
Hi folks, So finally i am ready to update my Supersu rooted,S-OFF, Rogers M8 to the marshmallow OTA update which has been showing as a notification from the last couple of months.I asked same question last year but at that time there was no easy way to update the rooted phone other than finding stock backup.
Any new way came to update without finding stock backup?I would really appreciate if someone can give step by step.Thanks.
Click to expand...
Click to collapse
hi
you can just flash the RUU which will update your device to official marshmallow ( and it will wipe your internal storage so make sure to backup all your data )
here is the RUU
https://www.androidfilehost.com/?fid=24459283995310669
and here is the guide ( replace the RUU by the one i linked ) and you don't need to relock the bootloader
start from
2. Download htc_fastboot.exe here
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
ahmed.ismael said:
here is the RUU
https://www.androidfilehost.com/?fid=24459283995310669
Click to expand...
Click to collapse
Thanks ahmed for your reply.I got one question.Is it safe to apply RUU downloaded from third party website.I mean is it guaranteed to be 100% stock without any chances of compromised security inside the RUU?
ninja_zx11 said:
Thanks ahmed for your reply.I got one question.Is it safe to apply RUU downloaded from third party website.I mean is it guaranteed to be 100% stock without any chances of compromised security inside the RUU?
Click to expand...
Click to collapse
Depends on the RUU and the provider
You have to decide what you will do
You came here asking for help and when you find your answer you got suspicious
Anyway you choose if you want to download the 3rd party website RUU or not
Sent from my HTC M8 using XDA Labs
ninja_zx11 said:
Is it safe to apply RUU downloaded from third party website.I mean is it guaranteed to be 100% stock without any chances of compromised security inside the RUU?
Click to expand...
Click to collapse
The file says "signed". If that is true, there is virtually no way (at least form a practical/feasible sense) for it to be anything but an official HTC RUU. My understanding, the encryption involved with being a signed file is far too complicated for anyone to bother messing with (never heard of anyone breaking that encryption to make a file "signed"). At least, its not worth it to spend all the time to make it "signed" just for the purpose of malware, etc. Far too many other "lower hanging fruit" possibilities.
That being said, since are s-off, I don't know how you would verify that file is truly signed. With s-off, you can flash unsigned RUU files. With s-on, only signed RUUs will flash. But I don't know its worthwhile to go s-on just for the purpose of making sure the RUU is signed.
You've already flashed custom recovery and a SuperSU file, all from 3rd parties (maybe from reputable sources, or not). There is no more or less reason to believe those files are safe.
ahmed.ismael said:
Depends on the RUU and the provider
You came here asking for help and when you find your answer you got suspicious
Click to expand...
Click to collapse
Hi ahmed, I assure you that i was asking that question about in a constructive way and i really appreciate your help and i think that's what i will be doing.I just put up my genuine fear/concern in a positive way.
redpoint73 said:
The file says "signed". If that is true, there is virtually no way (at least form a practical/feasible sense) for it to be anything but an official HTC RUU. My understanding, the encryption involved with being a signed file is far too complicated for anyone to bother messing with (never heard of anyone breaking that encryption to make a file "signed"). At least, its not worth it to spend all the time to make it "signed" just for the purpose of malware, etc. Far too many other "lower hanging fruit" possibilities.
That being said, since are s-off, I don't know how you would verify that file is truly signed. With s-off, you can flash unsigned RUU files. With s-on, only signed RUUs will flash. But I don't know its worthwhile to go s-on just for the purpose of making sure the RUU is signed.
You've already flashed custom recovery and a SuperSU file, all from 3rd parties (maybe from reputable sources, or not). There is no more or less reason to believe those files are safe.
Click to expand...
Click to collapse
Thanks redpoint for your reply.Yes i agree with you.I am gonna go ahead and flash that RUU as ahmed said.
I have my own full TWRP backup which i made before touching my M8 last year but it was from kitkat.
Can i run that backup to go back to kitkat and start from there?Thanks again ahmed and redpoint!!
ninja_zx11 said:
........I have my own full TWRP backup which i made before touching my M8 last year but it was from kitkat.
Can i run that backup to go back to kitkat and start from there?.......
Click to expand...
Click to collapse
if your backup is non rooted then you can just restore it and flash the stock recovery and do OTA ( multiple until marshmallow ) this way you will be sure that the download from HTC directly to your device
i'm curious to know how do you concern about the downloaded RUU while you have s-off rooted device ?
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
i'm curious to know how do you concern about the downloaded RUU while you have s-off rooted device ?
Click to expand...
Click to collapse
Its because i did rooting and S-off by myself (i am not an expert in any way.Did it by reading and getting help from XDA)on my brand new phone using third-party software (But well known and reputable sources-SuperSu and Sunshine).
I am not saying at all that downloaded RUU is infected or has some problem.It could be 100% stock and i might go that way you had described in your first post.I just expressed my genuine concern.But if that disturbed you then accept my apologies....
ninja_zx11 said:
Its because i did rooting and S-off by myself (i am not an expert in any way.Did it by reading and getting help from XDA)on my brand new phone using third-party software (But well known and reputable sources-SuperSu and Sunshine).
I am not saying at all that downloaded RUU is infected or has some problem.It could be 100% stock and i might go that way you had described in your first post.I just expressed my genuine concern.But if that disturbed you then accept my apologies....
Click to expand...
Click to collapse
no need to an apology that's your own security
but my point is you did unlock your device bootloader,flash custom recovery,flash supersu and used sunshine to s-off ( for what purpose all of this )
you just killed all of this device security
ahmed.ismael said:
no need to an apology that's your own security
but my point is you did unlock your device bootloader,flash custom recovery,flash supersu and used sunshine to s-off ( for what purpose all of this )
you just killed all of this device security
Click to expand...
Click to collapse
Yes i know i did.
But don't you think that downloading RUU from unknown source (If someone has injected something) is more dangerous than doing S-off and unlocking bootloader?I think after s-off and rooting ,It depend on me how i use my phone.Hope you understand my point.
I think there is no end of this security discussion.We can stretch it as much as we want and better...
ninja_zx11 said:
Yes i know i did.
But don't you think that downloading RUU from unknown source (If someone has injected something) is more dangerous than doing S-off and unlocking bootloader?I think after s-off and rooting ,It depend on me how i use my phone.Hope you understand my point.
I think there is no end of this security discussion.We can stretch it as much as we want and better...
Click to expand...
Click to collapse
I can't say anything
But as redpoint73 said earlier the signed RUU is protected by htc sign keys and i don't think that someone will decrypt then encrypt the RUU to push a malware software inside it
at the end it's your device,your own security and your decision
do what you see right
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
if your backup is non rooted then you can just restore it and flash the stock recovery and do OTA ( multiple until marshmallow ) this way you will be sure that the download from HTC directly to your device
Click to expand...
Click to collapse
The stock TWRP non rooted backup from the same phone when it was brand new is from android 4.4.3. Will it go backwards and accept that 4.4.3 old version? Thanks
ninja_zx11 said:
The stock TWRP non rooted backup from the same phone when it was brand new is from android 4.4.3. Will it go backwards and accept that 4.4.3 old version? Thanks
Click to expand...
Click to collapse
yes it will update to the latest but you need the proper recovery version to flash the OTA
ahmed.ismael said:
yes it will update to the latest but you need the proper recovery version to flash the OTA
Click to expand...
Click to collapse
I think my question wasn't clear.
Right now i am android version 5.0.1 and the TWRP backup i have is from 4.4.3.
So my question is that will my phone accept quite old backup (4.4.3) without any problems? and then i can take OTA updates step by step?Is that right?Thanks.
ninja_zx11 said:
I think my question wasn't clear.
Right now i am android version 5.0.1 and the TWRP backup i have is from 4.4.3.
So my question is that will my phone accept quite old backup (4.4.3) without any problems? and then i can take OTA updates step by step?Is that right?Thanks.
Click to expand...
Click to collapse
yes it will work no worry
ahmed.ismael said:
yes it will work no worry
Click to expand...
Click to collapse
Thanks for confirming!! will try this weekend.
ninja_zx11 said:
I think my question wasn't clear.
Right now i am android version 5.0.1 and the TWRP backup i have is from 4.4.3.
So my question is that will my phone accept quite old backup (4.4.3) without any problems? and then i can take OTA updates step by step?Is that right?Thanks.
Click to expand...
Click to collapse
You can use your TWRP backup 2.23.631.2 that you already have and you need to install 2.23.631.2 stock recovery to accept and install OTA but this is not productive. See option 2 below for the reason.
You have 3 options :
Option 1 :
You can install the RUU zip as mentioned in post #2 - http://forum.xda-developers.com/showpost.php?p=70110165&postcount=2
It is a HTC Signed RUU and that's the reason why you need to use htc_fastboot to install the RUU not the generic fastboot
Personally, I don't like to use RUU as it is a hassle to backup all my files from Internal Storage as this RUU will wipe everything on the phone.
Option 2 :
As you have a S-Off device, you can use your TWRP backup 2.23.631.2 that you already have but you need to have stock recovery 2.23.631.2 installed to proceed with OTA.
But this is not productive as you need to accept and install multiple OTAs
2.23.631.2 --> 3.34.631.4 --> 4.20.631.2 --> 4.20.631.3
Also you need to restore all boot, data & system from 2.23.631.2 as your current data on 4.20.631.3 won't work on 2.23.631.2
Option 3 :
As you are running a rooted stock ROM (if not, you won't receive OTA notification) and on 4.20.631.3 firmware, the best for you is restore a stock non-rooted 4.20.631.3 backup.
You only need to restore boot & system, no need to restore data. This way you have all your data intact, no need to re setup after OTA to Marshmallow 6.13.631.7
You can get the non-rooted stock 4.20.631.3 backup and stock recovery 4.20.631.3 from my thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
1. Download the 4.20.631.3 backup
2. Download the 4.20.631.3 stock recovery
3. Restore 4.20.631.3 backup (select only boot & system)
4. Install 4.20.631.3 stock recovery
5. Reboot
6. Check for update
7. Accept, download and install OTA
8. Done.
ckpv5 said:
You can use your TWRP backup 2.23.631.2 that you already have and you need to install 2.23.631.2 stock recovery to accept and install OTA but this is not productive. See option 2 below for the reason.
You have 3 options :
Option 1 :
You can install the RUU zip as mentioned in post #2 - http://forum.xda-developers.com/showpost.php?p=70110165&postcount=2
It is a HTC Signed RUU and that's the reason why you need to use htc_fastboot to install the RUU not the generic fastboot
Personally, I don't like to use RUU as it is a hassle to backup all my files from Internal Storage as this RUU will wipe everything on the phone.
Option 2 :
As you have a S-Off device, you can use your TWRP backup 2.23.631.2 that you already have but you need to have stock recovery 2.23.631.2 installed to proceed with OTA.
But this is not productive as you need to accept and install multiple OTAs
2.23.631.2 --> 3.34.631.4 --> 4.20.631.2 --> 4.20.631.3
Also you need to restore all boot, data & system from 2.23.631.2 as your current data on 4.20.631.3 won't work on 2.23.631.2
Option 3 :
As you are running a rooted stock ROM (if not, you won't receive OTA notification) and on 4.20.631.3 firmware, the best for you is restore a stock non-rooted 4.20.631.3 backup.
You only need to restore boot & system, no need to restore data. This way you have all your data intact, no need to re setup after OTA to Marshmallow 6.13.631.7
You can get the non-rooted stock 4.20.631.3 backup and stock recovery 4.20.631.3 from my thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
1. Download the 4.20.631.3 backup
2. Download the 4.20.631.3 stock recovery
3. Restore 4.20.631.3 backup (select only boot & system)
4. Install 4.20.631.3 stock recovery
5. Reboot
6. Check for update
7. Accept, download and install OTA
8. Done.
Click to expand...
Click to collapse
Thanks a lot ckpv5!!! Will try as you described.I really appreciate your help!
ckpv5 said:
Option 3 :
As you are running a rooted stock ROM (if not, you won't receive OTA notification) and on 4.20.631.3 firmware, the best for you is restore a stock non-rooted 4.20.631.3 backup.
You only need to restore boot & system, no need to restore data. This way you have all your data intact, no need to re setup after OTA to Marshmallow 6.13.631.7
You can get the non-rooted stock 4.20.631.3 backup and stock recovery 4.20.631.3 from my thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
1. Download the 4.20.631.3 backup
2. Download the 4.20.631.3 stock recovery
3. Restore 4.20.631.3 backup (select only boot & system)
4. Install 4.20.631.3 stock recovery
5. Reboot
6. Check for update
7. Accept, download and install OTA
8. Done.
Click to expand...
Click to collapse
Hi ckpv5, Thanks for your help and i finally updated my M8 using your option 3.It really saved my time as i didn't have to delete my data and pics..
One question, Even after updating to marshmallow,the android security patch is still dated to dec 2015? Is it the latest patch and nothing came after?Thanks.
ninja_zx11 said:
........One question, Even after updating to marshmallow,the android security patch is still dated to dec 2015? Is it the latest patch and nothing came after?Thanks.
Click to expand...
Click to collapse
yes it's the latest
no more updates or security patches
I wanted to root my HTC One M8 to uninstall unnecessary applications. I describe the procedure that I survived:
1- I unlock the HTC One M8 bootloader
2- I installed the CWM Recovery: recovery-clockwork-6.0.4.8-m8.img
3- I proceeded to the root with UPDATE-SuperSU-v2.46.zip
And at restart it's where everything gets complicated. It remains stuck on the logo of the boot and can not restart anything. I left for more than an hour to see but nothing moved.
I managed to enter bootloader by associating the volume + and Power key to restart, and when the phone turns off before restarting I do volume- and power.
And the I'm stuck I know more manipulation to make my HTC one M8 work again.
Is the phone ****ing kind unrecoverable?
How to recover my phone?
Help me please
The files (custom recovery and SuperSU) you used are horribly outdated. Unless your current firmware is something like Kitkat, the stuck on boot situation is expected.
Additionally, CWM never officially supported this phone, and that in itself may cause some problems (in addition to being outdated as well).
Correct versions depends on your current firmware number. Most folks (but not all) are on Marshmallow at this point. But you can tell us more by posting what it says for OS number on the bootloader screen. Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
But likely, you should use a TWRP version 2.8.7 or later. And SuperSU 2.79 or later. Or Magisk to root (latest is 13.3, which should work).
redpoint73 said:
The files (custom recovery and SuperSU) you used are horribly outdated. Unless your current firmware is something like Kitkat, the stuck on boot situation is expected.
Additionally, CWM never officially supported this phone, and that in itself may cause some problems (in addition to being outdated as well).
Correct versions depends on your current firmware number. Most folks (but not all) are on Marshmallow at this point. But you can tell us more by posting what it says for OS number on the bootloader screen. Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
But likely, you should use a TWRP version 2.8.7 or later. And SuperSU 2.79 or later. Or Magisk to root (latest is 13.3, which should work).
Click to expand...
Click to collapse
Yes indeed I had chosen the wrong files (custom recovery and SuperSU). The phone was on Marshmallow. I opted for a simple solution: to install a stock rom Android Jelly Bean 4.4.2 and wait for the update Marshmallow. But before I have installed last version of TWRP. After installing my rom stock, I installed stock recovery and I relock the bootloader.
thank you for your help
Koukougnon said:
I opted for a simple solution: to install a stock rom Android Jelly Bean 4.4.2 and wait for the update Marshmallow.
After installing my rom stock, I installed stock recovery and I relock the bootloader.
Click to expand...
Click to collapse
I don't think this will work. Your firmware indicated by OS number (in bootloader, not in OS Settings) will still read as updated (MM) and you won't be prompted to update.
Additionally, just as FYI, it is not necessary to relock the bootloader for an OTA update, only for RUU or flashing stock signed firmware.
Stuck on HTC logo screen due to old version TWRP and SuperSU, can often be fixed simply by using the proper updated files. But in the current condition, you will need to unlock the bootloader again. In light of that, it might make sense to restore by RUU (if you version has one - you haven't provided the info requested) or otherwise restore to MM (so ROM matches your firmware) before trying to root again.
Excuse me for my absence. I need your help.
As I said earlier, I opted to go back to a Stock ROM.
Actually as you said, I can not install the update to Marshmallow. It downloads the update but it crashes at installation.
I am sending you the information you requested:
OS number on the bootloader
*** Software statut: Modified ***
*** UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8674_FO.1015
OS-6.12.401.4
eMMC-boot 2048MB
Dec 17 2015, 14:15:48.0
fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 1.29.214500021.12G
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.12.401.4
INFOversion-misc: PVT SHIP S-ON
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B10000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 76df2b54
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.024s
I still have the TWRP installed and unlock bootloader
Can you help me?
Koukougnon said:
Excuse me for my absence. I need your help.
As I said earlier, I opted to go back to a Stock ROM.
Actually as you said, I can not install the update to Marshmallow. It downloads the update but it crashes at installation.
Click to expand...
Click to collapse
No surprise there. It's best you follow the advice given, instead of making up your own solutions, unless you really know what you are doing. This device has a lot of nuances, and what seems like common sense or a simple solution, often doesn't apply.
OTAs will not install on this device with TWRP, but rather require stock recovery. But it probably doesn't matter, as I stated before, since you are trying to load an update (ROM + firmware), when the firmware is already updated (even if the ROM is not updated), it will likely not install. Basically you have mismatched components, and this will prevent the update from installing. ROM is older, but firmware is updated (version main in getvar indicates firmware is Marshmallow 6.12.401.4).
Koukougnon said:
I still have the TWRP installed and unlock bootloader
Click to expand...
Click to collapse
What version TWRP? You mentioned before the "latest" but did not give a version number. I've had a lot of cases where folks thing they have the "latest" but when prompted for specific version number, it turns out to be an old version.
Just want to be sure before we proceed. After all, the other files you used are going on 3 years old.
redpoint73 said:
No surprise there. It's best you follow the advice given, instead of making up your own solutions, unless you really know what you are doing. This device has a lot of nuances, and what seems like common sense or a simple solution, often doesn't apply.
OTAs will not install on this device with TWRP, but rather require stock recovery. But it probably doesn't matter, as I stated before, since you are trying to load an update (ROM + firmware), when the firmware is already updated (even if the ROM is not updated), it will likely not install. Basically you have mismatched components, and this will prevent the update from installing. ROM is older, but firmware is updated (version main in getvar indicates firmware is Marshmallow 6.12.401.4).
What version TWRP? You mentioned before the "latest" but did not give a version number. I've had a lot of cases where folks thing they have the "latest" but when prompted for specific version number, it turns out to be an old version.
Just want to be sure before we proceed. After all, the other files you used are going on 3 years old.
Click to expand...
Click to collapse
I had installed a stock recovery and relocked the bootloader after installing the rom stock. I received an update for Marshmallow but that crashed at the installation.
After I wanted to install a Rom Custom Nougat for HTC M8, so I unlocked the bootloader, installed TWRP (version twrp-3.1.1-0-m8) then root with SuperSU (the SR1-SuperSU-v2 version. 82-SR1-20170608224931). I installed the rom that no more.
So I reinstalled the rom stock Jelly Bean 4.4.2. That's why I have the TWRP installed and the bootloader unlocked.
Koukougnon said:
.
After I wanted to install a Rom Custom Nougat for HTC M8, so I unlocked the bootloader, installed TWRP (version twrp-3.1.1-0-m8) then root with SuperSU (the SR1-SuperSU-v2 version. 82-SR1-20170608224931). I installed the rom that no more.
Click to expand...
Click to collapse
I'm not sure what that means (what the problem was after flashing the custom ROM). You may have some words missing/wrong in the last sentence.
Flashing the custom ROM should work (seems that it was the real goal here). Did you also flash gapps (Google Apps) which is normally required for AOSP type ROMs? This (or trying a different gapps) is a frequent cause for an AOSP ROM not booting after flashing.
If you still want to return to stock, restore the stock TWRP backup from the collection, using the instructions and files on the following thread. Only need to do through Step 9, and reboot: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, keep in mind best practice is to make a TWRP backup of your stock ROM, before trying to root of flash a custom ROM. If you did that, returning to stock would have been as easy as restoring the backup you made.
redpoint73 said:
I'm not sure what that means (what the problem was after flashing the custom ROM). You may have some words missing/wrong in the last sentence.
Flashing the custom ROM should work (seems that it was the real goal here). Did you also flash gapps (Google Apps) which is normally required for AOSP type ROMs? This (or trying a different gapps) is a frequent cause for an AOSP ROM not booting after flashing.
If you still want to return to stock, restore the stock TWRP backup from the collection, using the instructions and files on the following thread. Only need to do through Step 9, and reboot: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, keep in mind best practice is to make a TWRP backup of your stock ROM, before trying to root of flash a custom ROM. If you did that, returning to stock would have been as easy as restoring the backup you made.
Click to expand...
Click to collapse
The problem I had with the Custom Rom was that I could not see my Sim contacts. It was a Rom Mokee 7.1.2 for HTC M8.
And I did not backup either the Rom Stock or the Custom Rom.
That's why I installed the Rom Stock 4.4.2 again
Can I install a RUU for HTC M8?
I found this zip file : 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
Koukougnon said:
The problem I had with the Custom Rom was that I could not see my Sim contacts. It was a Rom Mokee 7.1.2 for HTC M8.
Click to expand...
Click to collapse
The description of events that got you to the current condition, gets more and more convoluted every time you post.
Not critical in this case (returning to stock is fairly simple, and doesn't rely that much on the history). But for other issues, conveying the information this way could be a real problem for those trying to help you.
Koukougnon said:
Can I install a RUU for HTC M8?
I found this zip file : 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
Click to expand...
Click to collapse
You can. It would require relocking the bootloader. Then if you want TWRP, root or custom ROM, you will need to unlock the bootloader again after RUU. RUU will also wipe all data on the phone.
Must flash with SD card method, or using htc_fastboot
Not gaining much versus what I previously recommended, especially if you want to still have TWRP for root, custom ROM, etc.
redpoint73 said:
The description of events that got you to the current condition, gets more and more convoluted every time you post.
Not critical in this case (returning to stock is fairly simple, and doesn't rely that much on the history). But for other issues, conveying the information this way could be a real problem for those trying to help you.
You can. It would require relocking the bootloader. Then if you want TWRP, root or custom ROM, you will need to unlock the bootloader again after RUU. RUU will also wipe all data on the phone.
Must flash with SD card method, or using htc_fastboot
Not gaining much versus what I previously recommended, especially if you want to still have TWRP for root, custom ROM, etc.
Click to expand...
Click to collapse
I understand I was wrong at first to solve my problem. I got into that. I did not think well before applying the solutions. Thank you for your help.
So, if I understood correctly to flash the RUU,
- relocked the bootloader
- to be S-ON
- flash by SD Card or Fastboot
Should I install a recovery stock before relocking the bootloafer?
My comments/responses below in red font:
Koukougnon said:
So, if I understood correctly to flash the RUU,
- relocked the bootloader yes, using fastboot command: fastboot oem lock
- to be S-ON It's not a requirement to be s-on, but it's your current condition. With s-off, the requirement to lock the bootloader is bypassed (and RUU still works).
- flash by SD Card or Fastboot Either SD card method, or htc_fastboot specifically. Trying to use the "generic" fastboot will fail since the RUU file is too large. IF you need further info, see here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Should I install a recovery stock before relocking the bootloafer? NO. It's not needed when doing RUU.
Click to expand...
Click to collapse
I managed to flash the RUU with your advice. Everything works well.
The only problem is the recovery. When I go into the recovery it shows me a red triangle and nothing happens. But I intend to install the TWRP.
Thank you for your help.
Koukougnon said:
I managed to flash the RUU with your advice. Everything works well.
The only problem is the recovery. When I go into the recovery it shows me a red triangle and nothing happens.
Click to expand...
Click to collapse
That isn't a "problem", it is working as it should. It's the stock recovery. Press vol up and tap the power button to show the recovery menu options (although not much you can do in stock recovery).
Koukougnon said:
Thank you for your help.
Click to expand...
Click to collapse
You're welcome. Please click the "Thanks" button for any post you found helpful.
Some advice and "best practices" as it seems that you've missed a lot of important info when trying to mod the phone:
1) Always research the most up to date info on rooting a device, before you start anything. Files are updated often, and using old methods can (and will) lead to a lot of problems. I know a lot of the info for this device is outdated, or not entirely organized. So feel free to ask questions if you are confused.
2) Always make a TWRP backup of your stock ROM, before doing any mods (root, custom ROM, etc.).
3) Always know how to return to stock, before doing the mods.
4) At least for this device, after installing TWRP, you don't need to root, if you are then going to immediately flash a custom ROM. In other words, you don't need root to flash a ROM. Most ROMs are pre-rooted But the few that are not, you need to flash root (SuperSU or Magisk) after you flash the ROM.
redpoint73 said:
That isn't a "problem", it is working as it should. It's the stock recovery. Press vol up and tap the power button to show the recovery menu options (although not much you can do in stock recovery).
You're welcome. Please click the "Thanks" button for any post you found helpful.
Some advice and "best practices" as it seems that you've missed a lot of important info when trying to mod the phone:
1) Always research the most up to date info on rooting a device, before you start anything. Files are updated often, and using old methods can (and will) lead to a lot of problems. I know a lot of the info for this device is outdated, or not entirely organized. So feel free to ask questions if you are confused.
2) Always make a TWRP backup of your stock ROM, before doing any mods (root, custom ROM, etc.).
3) Always know how to return to stock, before doing the mods.
4) At least for this device, after installing TWRP, you don't need to root, if you are then going to immediately flash a custom ROM. In other words, you don't need root to flash a ROM. Most ROMs are pre-rooted But the few that are not, you need to flash root (SuperSU or Magisk) after you flash the ROM.
Click to expand...
Click to collapse
I understood well. Thank you.