Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?
ruubs said:
Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?
Click to expand...
Click to collapse
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.
computerslayer said:
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.
Click to expand...
Click to collapse
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out
ruubs said:
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out
Click to expand...
Click to collapse
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.
computerslayer said:
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.
Click to expand...
Click to collapse
The phone status is indeed unlocked.
I didn't know I could flash TWRP or a ROM. I thought I needed S-OFF for that.
I want my phone to be as stock as possible. Can I flash a stock ROM or does it have to be a custom one.
And do i need to flash TWRP in order to flash a ROM?
So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.
ruubs said:
So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.
Click to expand...
Click to collapse
That's the route I would take too. The readme thread has a section dedicated to changing your SKU in order to use other RUUs.
Related
Update: Well, I took the plunge on my own, and everything worked fine. Flashed firmware.zip, went to stock recovery and flashed OTA, and voila, all good.
So I've bought an HTC device for the first time. I did S-Off and unlocked bootloader and rooted as well. Now, there's an OTA available (I have the Asia_India variant), and I wanted to ask just how would I go about updating.
Here's what I've surmised till now:
1. Revert changes to system partition or it will fail to update (I moved some system APKs, but I saved them for such a scenario.)
2. Flash Firmware.zip to get stock recovery back.
3. Install OTA normally from the notification.
However, I'm still not sure what else I'd need to do (unroot, using the option in SuperSU?), so was wondering if someone could help me out. I've made backups in Philz and TWRP recovery both just to be sure.
P.S.: I extracted the firmware.zip file from the OTA, and tried to open it, but it doesn't open in apps like WinRAR. Is that normal, with the file only flashable via fastboot?
Personally, I'd say remove root just incase it stops the OTA but others will say it doesn't matter so long as the rest of the system is 100% stock as HTC intended it
For OTA updates after having a custom recovery, just flash your ROM stock recovery (search XDA all are available) then run OTA as you normally would and then flash your custom recovery again (if you like to get root again). However personally I would not do this with S-ON device, probably it's better if you're S-OFF while doing this to avoid any problem.
I am also interested in this. What would be the risk if I do this with S-ON? Assume I flash the wrong stock recovery or do some other mistake, won't I still be able to flash my custom recovery back from fastboot and get everything back up and running?
Thanks to whom will answer. :good:
Black Antitoon said:
I am also interested in this. What would be the risk if I do this with S-ON? Assume I flash the wrong stock recovery or do some other mistake, won't I still be able to flash my custom recovery back from fastboot and get everything back up and running?
Thanks to whom will answer. :good:
Click to expand...
Click to collapse
So long as the phone still boots to fastboot, yes (although unlocking the boot loader will delete any backups so make sure you backup the backup to your PC before doing anything else!)
Thank you for your answer. As far as you know, being S-ON, is there really any kind of mistake one can do to brick the phone so that it doesn't even boot to fastboot?
Also, if my bootloader is already unlocked, no data wipe is going to happen again flashing a firmware/OTA in any predictable case, right?
Once again, thank you or anybody else who knows the answer.
By the way, are there any FAQs answering these questions? There are some FAQs here and there, but none seems to be very clear on these matters.
Black Antitoon said:
Thank you for your answer. As far as you know, being S-ON, is there really any kind of mistake one can do to brick the phone so that it doesn't even boot to fastboot?
Also, if my bootloader is already unlocked, no data wipe is going to happen again flashing a firmware/OTA in any predictable case, right?
Once again, thank you or anybody else who knows the answer.
By the way, are there any FAQs answering these questions? There are some FAQs here and there, but none seems to be very clear on these matters.
Click to expand...
Click to collapse
If you're S-ON there's not a lot you can do to brick the phone. You could wipe the ROM and have it not boot but you should always be able to get back to fastboot. This is where S-OFF is only handy to have if RUUs are about (it's the ONLY reason I am S-OFF, it's purely for a 'going back to stock' standpoint)
Yes, if the bootloader is already unlocked then you're good to go
Hello there!
I know there are many threads and questions about unrooting, but I haven't found anything useful to me (or I just don't understand them) and also I'm new to the whole root/unroot thing.
Here is the story. I rooted my device via TWRP Recovery. Then I tried to get S-OFF using Firewater. When I wasted like a few days trying to get this done I discovered that my device is "Patched by HTC" so I cannot use Firewater anymore to get this S-OFF.
The whole thing was to convert my M8 into a GPE version. Now I'm trying to revert my phone back to stock ver. because I have no need in root.
So is it possible to unroot my phone?
My CID is HTC_622
Software number is 1.60.708.2
Thanks in advance!
Funky_Noises said:
Hello there!
I know there are many threads and questions about unrooting, but I haven't found anything useful to me (or I just don't understand them) and also I'm new to the whole root/unroot thing.
Here is the story. I rooted my device via TWRP Recovery. Then I tried to get S-OFF using Firewater. When I wasted like a few days trying to get this done I discovered that my device is "Patched by HTC" so I cannot use Firewater anymore to get this S-OFF.
The whole thing was to convert my M8 into a GPE version. Now I'm trying to revert my phone back to stock ver. because I have no need in root.
So is it possible to unroot my phone?
My CID is HTC_622
Software number is 1.60.708.2
Thanks in advance!
Click to expand...
Click to collapse
just flash stock then flash stock recovery and your done
but bootloader will still say tampered
jaythenut said:
just flash stock then flash stock recovery and your done
but bootloader will still say tampered
Click to expand...
Click to collapse
Thanks for the reply.
I wish there was more detail in your post: like what software should I use to flash stock?
Should I download some rom for that?
As I said, I'm really new to the whole thing.
1. Flash your backup in TWRP
2. Once restored and confirmed working, flash the stock recovery image for your software version in fastboot the same way you flashed TWRP (fastboot flash recovery <nameofrecovery>.img
3419
EddyOS said:
1. Flash your backup in TWRP
2. Once restored and confirmed working, flash the stock recovery image for your software version in fastboot the same way you flashed TWRP (fastboot flash recovery <nameofrecovery>.img
Click to expand...
Click to collapse
I see! Thanks a lot!
Will try that.
Damn, I wish I could do S-OFF and convert my phone into GPE ;|
stock recovery
EddyOS said:
1. Flash your backup in TWRP
2. Once restored and confirmed working, flash the stock recovery image for your software version in fastboot the same way you flashed TWRP (fastboot flash recovery <nameofrecovery>.img
Click to expand...
Click to collapse
Hey I've been googling for hours for this too.I know this is an old post.
I am one of the unfortunate people do get a 1.60 up
Update on CID HTC__622
I have surfed the page with the list of nandroids, however there is no stock recovery that begins with 1.60. From other research it states that the first two numbers are the most important whilst flashing recoveries.
Any information would be really helpful
Thanks
I originally had a stock sense M8 (bought it first day) but since October, I changed my phone to GPE (GPE Firmware and everything) and have been using 5.0 eversince using SkyDragon rom. Ran into issues a few weeks ago, and i've been waiting hard to go back to sense and use the newer 5.0 sense version.
However, today I ran into multiple issues, I thought installing the latest Sense Lollipop firmware and installing the latest ARHD 5.0 rom would do the trick, sadly that did not work.
I flashed the latest sense firmware and the ROM only for it to boot saying my Data is corrupt and i have to reset my phone, i say okay(was going to do that anyway) but then I access my recovery (TWRP) and my Internal storage/Cache/Data will not mount. I tried going back to GPE (atleast so my phone would work) but I cant do that either because even with the GPE firmware, the data partition wont mount and my internal storage shows 0 MB in TWRP, now im just stick in a bootloop/bricked device for hours. Any help would really be appreciated...thanks a lot.
Dev Edition RUU is what I would recommend. Partitioning is different on GPE versus Sense. So I'm guessing running the firmware only, since its not a complete image, did not change the partitioning back to the Sense partition scheme.
Converting from GPE back to Sense is not trivial, and not to be taken lightly. It seems like you tried to make up your own process instead of following any definitive guide or advice, which I do not recommend.
redpoint73 said:
Dev Edition RUU is what I would recommend. Partitioning is different on GPE versus Sense. So I'm guessing running the firmware only, since its not a complete image, did not change the partitioning back to the Sense partition scheme.
Converting from GPE back to Sense is not trivial, and not to be taken lightly. It seems like you tried to make up your own process instead of following any definitive guide or advice, which I do not recommend.
Click to expand...
Click to collapse
Thanks for your reply, to get this clear:
I should flash the Dev Edition RUU from (http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777) (3.28.1540.5) and then update the firmware to 4.16.1540.8 by just flashing that separate zip. However, if I flash the RUU wouldn't it relock my bootloader and put me on S-On and lose root and the custom recovery(Im terribly sorry if this sounds dumb, but my phone is soft bricked and I really need to get everything right this time), Is that the case if I flash the dev edition RUU? Thanks again.
Austin3161337 said:
However, if I flash the RUU wouldn't it relock my bootloader and put me on S-On and lose root and the custom recovery
Click to expand...
Click to collapse
No, RUU will not relock the bootloader. The only way the bootloader gets locked/unlocked is if you do so yourself.
Same with s-off, there is nothing that can change that aside from you making it s-on yourself.
Yes, you will lose custom recovery, as RUU will install stock recovery. So just flash stock recovery by fastboot after RUU. Then flash the ROM you want, which should already be rooted (so losing root is a moot point).
Official firmware.zip will also write stock recovery. So doing so would have caused the loss of TWRP anyway (unless it was a user modified firmware zip).
redpoint73 said:
No, RUU will not relock the bootloader. The only way the bootloader gets locked/unlocked is if you do so yourself.
Same with s-off, there is nothing that can change that aside from you making it s-on yourself.
Yes, you will lose custom recovery, as RUU will install stock recovery. So just flash stock recovery by fastboot after RUU. Then flash the ROM you want, which should already be rooted (so losing root is a moot point).
Official firmware.zip will also write stock recovery. So doing so would have caused the loss of TWRP anyway (unless it was a user modified firmware zip).
Click to expand...
Click to collapse
So I downloaded the RUU from (http://www.htc.com/us/support/htc-one-m8/news/) but its an .exe which requires me to plug my phone in which my computer cannot recognize because the phone won't boot at all, is there anyway I can install the RUU by not really needing to connect the phone to the computer? (Put the file in the external SD and install it via the bootloader maybe?) Any tips on that? Thanks
Austin3161337 said:
So I downloaded the RUU from (http://www.htc.com/us/support/htc-one-m8/news/) but its an .exe which requires me to plug my phone in which my computer cannot recognize because the phone won't boot at all
Click to expand...
Click to collapse
The phone doesn't need to boot into OS to run the RUU. It just needs to be able to get into bootloader/fastboot mode, which it can if the screen comes on.
If the device doesn't show on your PC, its a different issue. USB connectivity issue is almost always a driver issue. Install HTC Sync and HTC drivers, if you haven't already. Or uninstall and install them again.
I have a similiar issue. I had a tombile ruu.zip that a flashed as a 0P6Bimg.zip a kitkiat sense version for tmobile. Everything is cool and it runs fine. When I change cid and mid then flashed the sense lollipop firmware I lost my internal memory and twrp read storage as 0mb.
So idk
I flashed the Dev RUU as recommended by redpoint73, booted up and now it says that its updating to the latest firmware android 5.0 (OTA Update) However, I am going to install a custom recovery (TWRP) and put on ARHD instead, thanks for the help, and pretty much unbricking my device, lol.
Austin3161337 said:
I flashed the Dev RUU as recommended by redpoint73, booted up and now it says that its updating to the latest firmware android 5.0 (OTA Update) However, I am going to install a custom recovery (TWRP) and put on ARHD instead, thanks for the help, and pretty much unbricking my device, lol.
Click to expand...
Click to collapse
You're very welcome. Happy to help.
Did you have to do anything to get the RUU to run (like install drivers), or did you just end up running the RUU exe, and it worked?
redpoint73 said:
You're very welcome. Happy to help.
Did you have to do anything to get the RUU to run (like install drivers), or did you just end up running the RUU exe, and it worked?
Click to expand...
Click to collapse
I already had HTC Sync installed, had to boot into Fastboot USB for the thing to get recognized.
Is it possible to have a working phone without a recovery installed ?
Unlocked bootloader, flashed twrp 3.0.1.0, phone wouldn't boot into recovery.
Relocked bootloader cause phone is s-on, ran 401 ruu but can't get into stock recovery but otherwise phone works ok
:banghead:
There is always a recovery installed. Either the stock one or the custom one. What does it do when you go to the recovery?
10rdan said:
Is it possible to have a working phone without a recovery installed ?
Unlocked bootloader, flashed twrp 3.0.1.0, phone wouldn't boot into recovery.
Relocked bootloader cause phone is s-on, ran 401 ruu but can't get into stock recovery but otherwise phone works ok
:banghead:
Click to expand...
Click to collapse
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
jollywhitefoot said:
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
Click to expand...
Click to collapse
With s-on you need to relock the bootloader to use official signed ruu files. When he flashed the ruu he could be seeing the exclamation mark that is normal as a warning before entering the stock recovery for which you need to push a volume and power button combo (don't know them heads up)
A possibility is to clear the cache and try to enter again (as this was a thingy on older HTC devices) or indeed as suggested at least to use the latest twrp available
Mr Hofs said:
With s-on you need to relock the bootloader to use official signed ruu files. When he flashed the ruu he could be seeing the exclamation mark that is normal as a warning before entering the stock recovery for which you need to push a volume and power button combo (don't know them heads up)
A possibility is to clear the cache and try to enter again (as this was a thingy on older HTC devices) or indeed as suggested at least to use the latest twrp available
Click to expand...
Click to collapse
It doesn't get as far as red exclamation mark, that's what I was waiting for. I'll try the newer version of twrp tomorrow after I've unlocked bootloader again. Do you think the same unlock code will work again?
10rdan said:
It doesn't get as far as red exclamation mark, that's what I was waiting for. I'll try the newer version of twrp tomorrow after I've unlocked bootloader again. Do you think the same unlock code will work again?
Click to expand...
Click to collapse
Yes i think it does work again. But that's a try and find out. There is always the possibility i could be wrong.
Edit :
This is why i love s-off....no more relocking / unlocking the BL with also an increased chance of bricks. The BL isn't made to be relocked and unlocked over and over.
Mr Hofs said:
With s-on you need to relock the bootloader to use official signed ruu files.
Click to expand...
Click to collapse
Sorry, but I believe this is misinformation, possibly residual to older HTC devices. I've heard this going back to the M7.
You need to be s-off to flash in download mode, but s-on can flash signed firmware and ruu's in RUU mode. I'm s-off so I can't test at the moment, but I'm about 99% that my information is correct.
S-on, you can only flash same or newer, though. You can't flash older firmware.
See post 19 here:
http://forum.xda-developers.com/htc-10/how-to/unlocked-official-ruu-t3378540/page2
I'm 100% that you can flash signed firmware package in ruu mode with bootloader unlocked and s-on.
jollywhitefoot said:
Sorry, but I believe this is misinformation, possibly residual to older HTC devices. I've heard this going back to the M7.
You need to be s-off to flash in download mode, but s-on can flash signed firmware and ruu's in RUU mode. I'm s-off so I can't test at the moment, but I'm about 99% that my information is correct.
S-on, you can only flash same or newer, though. You can't flash older firmware.
See post 19 here:
http://forum.xda-developers.com/htc-10/how-to/unlocked-official-ruu-t3378540/page2
I'm 100% that you can flash signed firmware package in ruu mode with bootloader unlocked and s-on.
Click to expand...
Click to collapse
That's new to me. Hopefully it isn't just tied to the developers edition then.
Thanks for the information
Mr Hofs said:
This is why i love s-off....no more relocking / unlocking the BL with also an increased chance of bricks. The BL isn't made to be relocked and unlocked over and over.
Click to expand...
Click to collapse
I'll bare that in mind, will unlock tomorrow again and try newer twrp. Only reason I relocked was to run ruu to get phone running again.
jollywhitefoot said:
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
Click to expand...
Click to collapse
Where can I find 3.0.2.2, can only see 3.0.2.0 on twrp site?
Cheers
Edit.... Found it. ?
@jollywhitefoot
I've got stock recovery back on phone. Can you think of any reason, other than old version, as to why twrp wouldn't boot after flashing it ?
Will try again tomorrow.
10rdan said:
@jollywhitefoot
I've got stock recovery back on phone. Can you think of any reason, other than old version, as to why twrp wouldn't boot after flashing it ?
Will try again tomorrow.
Click to expand...
Click to collapse
I'm not exactly sure, but up until 3.0.2.2 Captain Throwback didn't even have the device and was working blind. I know he was trying different things to make it compatible with different variants, too, so in my mind that was a test build. I'm not sure why they have it on the downloads page. For me, I always download it from the download section of the twrp thread.
Hi people, this is my first time posting on a forum. I've always fixed my problem by googling them but now i failed.
I fixed the problem mentioned in the title and now i'm back to the original problem.
I followed a guide on the web to root my HTC 10. What i did was unlocking the bootloader and then flashing TWRP and till then things went good.
Then i tried to root it by flashing superSU and after that my phone went in bootloop and i found out i didnt have a system image anymore.
I tried to flash the RUU with my cid but i got the following error "RU_MAIN_VER_FAIL...".
This is my situation:
-i can access download, recovery and bootloader
-I've TWRP installed and my internal storage is blank, it only has an empty TWRP folder.
-My external memory has the following folders: Android, TWRP, .android_secure, LOST.DIR
What is my problem? I even tried to restore a TWRP backup without succeeding from https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Please help me!!
rorou said:
Hi people, this is my first time posting on a forum. I've always fixed my problem by googling them but now i failed.
I fixed the problem mentioned in the title and now i'm back to the original problem.
I followed a guide on the web to root my HTC 10. What i did was unlocking the bootloader and then flashing TWRP and till then things went good.
Then i tried to root it by flashing superSU and after that my phone went in bootloop and i found out i didnt have a system image anymore.
I tried to flash the RUU with my cid but i got the following error "RU_MAIN_VER_FAIL...".
This is my situation:
-i can access download, recovery and bootloader
-I've TWRP installed and my internal storage is blank, it only has an empty TWRP folder.
-My external memory has the following folders: Android, TWRP, .android_secure, LOST.DIR
What is my problem? I even tried to restore a TWRP backup without succeeding from https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Please help me!!
Click to expand...
Click to collapse
Grab an ruu that is at least at the same version you are, or flash a custom rom from twrp
Tarima said:
Grab an ruu that is at least at the same version you are, or flash a custom rom from twrp
Click to expand...
Click to collapse
thank you for your reply! i tried already a ruu solution with the version of my cid but it didnt workout. You're saying i need to install a custom rom and then revert back to stock?
rorou said:
thank you for your reply! i tried already a ruu solution with the version of my cid but it didnt workout. You're saying i need to install a custom rom and then revert back to stock?
Click to expand...
Click to collapse
No I meant you can flash a custom rom instead of stock. If you want stock you'll have to run a stock ruu. What's your current software number and which ruu are you trying to run?
Tarima said:
No I meant you can flash a custom rom instead of stock. If you want stock you'll have to run a stock ruu. What's your current software number and which ruu are you trying to run?
Click to expand...
Click to collapse
I've used this ruu 1.90.401.5 that has same mid and cid as my phone. And before wiping my internaL storage i had nougat, 7.0 i think. This ruu thing is really twisting my mind, never heard about it before today... maybe that's because i got in trouble. I've installed viper and the phone seems to work now but i have my doubts on whether to keep it or not. I'll try this so rom for a week, i want to see if it has battery or overheating issues.
But in case i wanted to go back to stock, i dont know what went wrong and why the ruu i've picked failed to install even if it had the same cid and mid.
rorou said:
I've used this ruu 1.90.401.5 that has same mid and cid as my phone. And before wiping my internaL storage i had nougat, 7.0 i think. This ruu thing is really twisting my mind, never heard about it before today... maybe that's because i got in trouble. I've installed viper and the phone seems to work now but i have my doubts on whether to keep it or not. I'll try this so rom for a week, i want to see if it has battery or overheating issues.
But in case i wanted to go back to stock, i dont know what went wrong and why the ruu i've picked failed to install even if it had the same cid and mid.
Click to expand...
Click to collapse
If you had Nougat before, that means your firmware version is 2.x.x.x. This is newer than the ruu you're trying to flash. You can only run an ruu that is at the same version as or above your current firmware version, and you cannot downgrade. That's what I mean by "run an ruu that's the same version as your phone."
Get your software info by doing fastboot getvar all from download mode. Then find an ruu that is for your CID/mid and at the same or higher version that you have. That'll take you to stock.
Tarima said:
If you had Nougat before, that means your firmware version is 2.x.x.x. This is newer than the ruu you're trying to flash. You can only run an ruu that is at the same version as or above your current firmware version, and you cannot downgrade. That's what I mean by "run an ruu that's the same version as your phone."
Get your software info by doing fastboot getvar all from download mode. Then find an ruu that is for your CID/mid and at the same or higher version that you have. That'll take you to stock.
Click to expand...
Click to collapse
That explains everything! thank you so much!!!