Hello there,
Preamble:
Since first wave of OTAs came out, I've been wondering about going back to stock to get one. But yesterday I noticed that LeeDroid ROM got an update to Oreo (5.00), so I decided to try that out first.
Well, I failed – the installation process went just fine, however I failed to boot. That's when I thought of going back to LeeDroid 4.00 – wiped everything as instructed and installed the previous version. And now my radio doesn't work.
Question:
Could this radio problem be caused by 8.0 ROM installation even though I had Nougat firmware?
And what should I do to resolve this problem?
Thanks in advance!
The same problem. here
if you find a solution, please tell me, i have exactly the same problem
That's why you are REQUIRED to have Oreo firmware for any Stock or custom Oreo stock based roms.
Upgrading to Oreo will result in loss of baseband upon downgrading back to Nougat.
(new boot.img/ramdisk places firmware bits in places that the old boot.img/ramdisk doesn't see)
There currently is no method to update and then go back.
Your only available solution, is to fully update to Oreo firmware and software to get your baseband back.
There are already several threads which discuss this in pretty great lengths and detail.
santod040 said:
That's why you are REQUIRED to have Oreo firmware for any Stock or custom Oreo stock based roms.
Upgrading to Oreo will result in loss of baseband upon downgrading back to Nougat.
(new boot.img/ramdisk places firmware bits in places that the old boot.img/ramdisk doesn't see)
There currently is no method to update and then go back.
Your only available solution, is to fully update to Oreo firmware and software to get your baseband back.
There are already several threads which discuss this in pretty great lengths and detail.
Click to expand...
Click to collapse
So, essentially I need to flash Taiwanese RUU and 8.0 OTA now to get things work?
(My device is TW as well)
Elegiacal said:
So, essentially I need to flash Taiwanese RUU and OTA now to get things work?
(My device is TW as well)
Click to expand...
Click to collapse
Correct! :good:
Related
Hi everyone!
I recently unlocked my bootloader and rooted my m8.
I tried using firewater to "s-off" my phone and unfortunately, it did not work out. The way I understand it, I cannot install stock ROMs (such as the 5.0.1 GPE) without "s-off." Now, I want to unroot my phone and stick to waiting for the OTAs to roll out instead.
I followed the instructions in the "returning to stock" thread and noticed that I have no version main (see attached image). I looked around the forums and saw that the advice was to flash the latest TWRP version. Since I'm stuck with a phone that I cannot update, I'm trying to be careful now. Can anyone please confirm if flashing the latest TWRP will bring my version main back?
The noob in me also has a few questions/requests as well:
1. Since my phone is rooted, I cannot receive OTA updates and upgrade to lollipop once these updates roll out?
2. Please tell me which files to download to return to stock. Just trying to be really careful this time around.
3. Lastly, is it also true that I can only install custom ROMs once have rooted? As to stock ROMs, I can't install them until I get "s-off"?
Thanks a lot, everyone! Cheers!
panchizzles said:
Hi everyone!
I recently unlocked my bootloader and rooted my m8.
I tried using firewater to "s-off" my phone and unfortunately, it did not work out. The way I understand it, I cannot install stock ROMs (such as the 5.0.1 GPE) without "s-off." Now, I want to unroot my phone and stick to waiting for the OTAs to roll out instead.
I followed the instructions in the "returning to stock" thread and noticed that I have no version main (see attached image). I looked around the forums and saw that the advice was to flash the latest TWRP version. Since I'm stuck with a phone that I cannot update, I'm trying to be careful now. Can anyone please confirm if flashing the latest TWRP will bring my version main back?
The noob in me also has a few questions/requests as well:
1. Since my phone is rooted, I cannot receive OTA updates and upgrade to lollipop once these updates roll out?
2. Please tell me which files to download to return to stock. Just trying to be really careful this time around.
3. Lastly, is it also true that I can only install custom ROMs once have rooted? As to stock ROMs, I can't install them until I get "s-off"?
Thanks a lot, everyone! Cheers!
Click to expand...
Click to collapse
Your firmware version: 3.32.708.4
I got it from your radio (baseband) number.
xunholyx said:
Your firmware version: 3.32.708.4
I got it from your radio (baseband) number.
Click to expand...
Click to collapse
Thanks for the reply!
Do I have to flash the latest TWRP version before proceeding?
Hi,
After doing some reading on here I am a little unsure on the best way to back up my HTC One M9 (GSM) stock recovery/system. My software number is 3.50.710.1 (Android 6.0) and it came from Optus (Australia). I cannot seem to find an RUU file for this firmware anywhere online; only earlier versions are available. My understanding of this is that I need an RUU file for my specific firmware as a fail-safe in case I mess something up and need to return to stock?
My questions are:
1) Can I get my phone back to the current complete stock firmware and be able to receive future OTA updates without turning s-off and without copying anything from my phone before I flash TWRP and a custom ROM?
2) If not is there anyway that I can back up my phone it its current stock state that will allow me to go back to this state if I want to go back to my stock Optus firmware or to install OTA updates? (Including the stock radio/recovery)
3) Reading this post as well as others leads me to believe that I may stop my mobile radio working by flashing a custom ROM (especially as the linked post has the exact same firmware as me). How can I avoid this, or fix it if it happens to everyone?
I am ideally looking for a custom ROM which improves over the stock firmware. My priority is maximum battery life, with customisation and HTC 10 system UI/apps a secondary focus. Any recommendations would be great, as well as tweaks and kernels which help give the maximum battery life.
Cheers!
You can't backup your firmware (and that includes your radio). However if you read my google sheet you'll find instructions for backing up your current boot.img, your system and the stock recovery. If you do it correctly those files will suffice for recovering the ability of installing OTAs. No personal data will be backed up so maybe you want to share your backup with us afterwards.
There is a custom kernel for CM/AOSP roms which is said to repair the signal problems. As far as I read some sense rom users reported that flashing the stock boot.img recovered their signal. However this doesn't seem to work for every user. So you'll need to try by yourself.
Flippy498 said:
You can't backup your firmware (and that includes your radio). However if you read my google sheet you'll find instructions for backing up your current boot.img, your system and the stock recovery. If you do it correctly those files will suffice for recovering the ability of installing OTAs. No personal data will be backed up so maybe you want to share your backup with us afterwards.
Click to expand...
Click to collapse
Thank you so much! I have managed to find the guide you mentioned to backup the stock boot image, system image and recovery. By the looks of it the tab to the right is the guide to return my phone to its original state, which is good. I'm more than happy to share the backup once I do it.
Flippy498 said:
There is a custom kernel for CM/AOSP roms which is said to repair the signal problems. As far as I read some sense rom users reported that flashing the stock boot.img recovered their signal. However this doesn't seem to work for every user. So you'll need to try by yourself.
Click to expand...
Click to collapse
Okay, well I am planning on keeping s-on at this stage, so I'm left with Sense based ROMs I believe? I have read that LeeDroid is the best for battery life, does this sound right? If so I am unsure if I can flash it as it says "Please make sure you have the latest HTC Hima 3.35.XXX.XX Marshmallow firmware installed prior to installing this ROM" because my software number is 3.50.710.1?
Thanks again!
Da Doom Lord said:
Okay, well I am planning on keeping s-on at this stage, so I'm left with Sense based ROMs I believe? I have read that LeeDroid is the best for battery life, does this sound right? If so I am unsure if I can flash it as it says "Please make sure you have the latest HTC Hima 3.35.XXX.XX Marshmallow firmware installed prior to installing this ROM" because my software number is 3.50.710.1?
Click to expand...
Click to collapse
I've read that several times in the near past and I actually don't understand it. You never needed S-OFF for flashing none-sense based roms as long as I started using Android/HTC phones and that was back in 2012. Why do so many people think they need S-OFF for AOSP?
I personally prefer the Viper rom. But taste differs and in the end the best advice I can give is try it out by yourself. Everyone has different needs and is using his/her phone in a different way. The best rom for person a might be an awful choice for person b since he/she has completely different needs.
I can't tell you whether you can use Leedroid. Test it and report back. That's how xda works. You might be able to use it after you flashed your stock boot.img but I don't know whether you really are or not. The warning is written so that people don't start flashing that rom with a lower firmware version. On older HTC phones flashing an "older" rom has never been an issue on newer firmware versions whereas flashing a newer rom on an older firmware never goes well (even on the M9). However many things have changed since the M9. There is no hboot anymore, the Download Mode got introduced, google changed the way OTAs are checking whether your system is modified, and so on. (Just to mention a few changes.) Those issues with the lost signal didn't even exist on pre-3.x firmware versions of the M9. Therefore users like you who use a not so common firmware (in comparison to the user numbers of the most common firmware bases: international, taiwanese and the developer firmware) have no other choice but trying out by themselves or getting S-OFF and changing to a more common firmware.
Flippy498 said:
I can't tell you whether you can use Leedroid. Test it and report back. That's how xda works. You might be able to use it after you flashed your stock boot.img but I don't know whether you really are or not. The warning is written so that people don't start flashing that rom with a lower firmware version. On older HTC phones flashing an "older" rom has never been an issue on newer firmware versions whereas flashing a newer rom on an older firmware never goes well (even on the M9).
Click to expand...
Click to collapse
I have followed your guide and now have the latest stable LeeDroid ROM installed and TWRP. Just as I predicted the radio was not originally working. When I restored my stock boot.img from the original backup I performed it began to work. Thanks so much for your help! I'll upload the backup to cloud storage when I get access to a decent internet connection and then I'll share it to help others out.
Hi all,
I have the EE UK HTC 10.
Managed to get TWRP and SuperSU flashed fine and rebooted into system with no problems.
Copied over the LeeDroid Latest ROM, I forgot to address the firmware issue, so the one I'm running is older than the ROM's one. Causing my fingerprint sensor/home button to stop working...
I've been looking around thee internet for hours now and cannot find the RUU for my UK EE HTC 10 to be able to update the Firmware, and in general cannot find any way to update Firmware now.
Can someone please help? I'm not a complete noob to this, just haven't messed with Root and so on in a few years. (Not had the time, lol.)
corydor13 said:
Hi all,
I have the EE UK HTC 10.
Managed to get TWRP and SuperSU flashed fine and rebooted into system with no problems.
Copied over the LeeDroid Latest ROM, I forgot to address the firmware issue, so the one I'm running is older than the ROM's one. Causing my fingerprint sensor/home button to stop working...
I've been looking around thee internet for hours now and cannot find the RUU for my UK EE HTC 10 to be able to update the Firmware, and in general cannot find any way to update Firmware now.
Can someone please help? I'm not a complete noob to this, just haven't messed with Root and so on in a few years. (Not had the time, lol.)
Click to expand...
Click to collapse
Do you have a backup of your stock rom? If so flash that and see if you can upgrade using the official OTA.
Else, check out this thread for firmwares, on the last couple pages there are a bunch of versions posted.
https://forum.xda-developers.com/ht...-collection-recovery-ruu-ota-t3359297/page183
Also, from a couple threads below yours:
https://forum.xda-developers.com/htc-10/help/home-button-fingerprint-doesnt-nougat-t3558961
corydor13 said:
Hi all,
I have the EE UK HTC 10.
Managed to get TWRP and SuperSU flashed fine and rebooted into system with no problems.
Copied over the LeeDroid Latest ROM, I forgot to address the firmware issue, so the one I'm running is older than the ROM's one. Causing my fingerprint sensor/home button to stop working...
I've been looking around thee internet for hours now and cannot find the RUU for my UK EE HTC 10 to be able to update the Firmware, and in general cannot find any way to update Firmware now.
Can someone please help? I'm not a complete noob to this, just haven't messed with Root and so on in a few years. (Not had the time, lol.)
Click to expand...
Click to collapse
Read the aroma installer. Install the rom again and when you get the question on what firmware you are, select marshmallow firmware. The fingerprint and home button will work again.
Mr Hofs said:
Read the aroma installer. Install the rom again and when you get the question on what firmware you are, select marshmallow firmware. The fingerprint and home button will work again.
Click to expand...
Click to collapse
Yeah, sorry mate. I thought it was asking which version of the OS I want to install. LOL.
Thanks for that though! :good:
Hey everyone,
Apologize if this is something that has been asked before, haven't been able to find much information on it using search. Also still a relative newbie to android, so hope you folks will bear with me. I'm seeing the OS version in download mode showing as OS-3.36.709.3, while the software number in software information shows 4.30.617.12. Is this considered normal, or did I mess something up?
I previously had Marshmallow on my phone, and used TWRP to install the developer edition of Nougat. Was trying to do OTA, which unsurprisingly didn't work with TWRP installed. My plan is to reflash the recovery.img, but I'm unsure whether I should be using the recovery.img for 4.30.617.12, or the one for 3.36.709.3? Is there something I should do to get the versions aligned properly? Trying to make sure I avoid bricking the phone
The easiest solution would be downloading the latest version of the rom that you installed in the past and flashing it via TWRP.
Some advices: Please read the ReadMe thread. It explains why the version numbers differ (e.g. in the RUU section). In addition it will explain to you, that installing OTAs with TWRP actually is possible (c.f. the OTA section) but not in your case. Even with the correct stock recovery for your phone (the 709 one) you wouldn't be able to achieve your goal. You're trying to install an update for a completely different firmware than the current one of your phone. That's not possible. OTAs are incremental. That means you need to be using the firmware that the OTA is supposed to update (4.30.617.12) and not 3.36.709.3. You would need to convert your phone if you want to install that update.
You might want to read the article that I called "the difference between rom and firmware" in the further reading section of the ReadMe thread, as well, after you finished reading the ReadMe thread itself.
Be aware that it's always best to use a system that has the same version (or at least the same mayor version - e.g. 3.x for marshmallow or 4.x for nougat) as your phone. This way you can be sure that system and firmware are optimized for each other. Mismatches can cause unforseen side effects like battery drainage, lags or bugs.
I read the ROM vs. firmware article, and also based on your last comment, I think it would be best to align the firmware and ROM versions. If I'm understanding things correctly, I either need to flash the firmware to a version matching my ROM (4.30.617.12) by following the steps in the 's-off firmware flashing thread', or else I need to go back to a 3.36.709.3 rom and use OTA to update the firmware/ROM. If I use TWRP to update the ROM, I'll still be stuck with an older firmware. Is my understanding on this correct?
I originally go the phone second hand, and am not sure what ROM was on it to begin with. Had previously tried to get it back to stock to update to Nougat via OTA, but kept getting the your device software has been modified regardless of what I did, so ended up using TWRP.
P.S. will make sure to put questions in the right forum in the future.
e1rond said:
I read the ROM vs. firmware article, and also based on your last comment, I think it would be best to align the firmware and ROM versions. If I'm understanding things correctly, I either need to flash the firmware to a version matching my ROM (4.30.617.12) by following the steps in the 's-off firmware flashing thread', or else I need to go back to a 3.36.709.3 rom and use OTA to update the firmware/ROM. If I use TWRP to update the ROM, I'll still be stuck with an older firmware. Is my understanding on this correct?
Click to expand...
Click to collapse
Correct.
e1rond said:
I originally go the phone second hand, and am not sure what ROM was on it to begin with. Had previously tried to get it back to stock to update to Nougat via OTA, but kept getting the your device software has been modified regardless of what I did, so ended up using TWRP.
Click to expand...
Click to collapse
Then the phone had been modified before you got it. Since android 5 google is using block-based OTAs. That means re-flashing the stock recovery isn't sufficent if you want to update your phone and modified it, beforehand. You need to restore a completely untouched system image.
Check the ReadMe thread. The RUU section as well as the TWRP section II should contain the files and instructions that you need for restoring the OTA function of your phone. It's up to you which of the methods you prefer to use.
Appreciate the information and the advice. Decided to RUU back to a 3.x version, and use OTA to upgrade to Nougat. Took a lot of updates to get it to the latest version, but everything is working well now
Hi, I've got this one Note 4 that's had loads of trouble presumably since the last security update.
Baseband Version: N910AUCS2EQD1
Android: 6.0.1
Have seen the instructions and all as to how to go about downgrading BUT one site I came across with the original stock firmware downloads outright state how:
""DO not ever try to downgrade from any newest Android 6.0.1 Marshmallow updates back to an older 6.0.1 build version""
'and so I'm lost. Should trying to then reinstall the same Baseband version atop what's already there a good first alternative? ...that is, just in case it was never upgraded properly in the first place? Or is that not even possible?
Is trying to downgrade at all a futile pursuit?
Would truly appreciate any suggestions, help, direction...heck, anything! Thanks in advance.
I downgraded from 6.0.1 epk5 to 5.1.1 with no problem.
Not sure about qd1.
As long as you have the odin firmware, I see no problem.
Can i downgrade note 4 n910a from marshmallow to lollilop,please help me i am in great trouble because marsmallow update is very bad with a lot of reboot issue ,battery drain.
Once you are on QD1 you will not be able to go back to anything lower than that firmware. The bootloader is now at the latest version and has blown one of those imaginary "e-fuses" so that you can not go back in time to any other vulnerable OS. I just tried today to go from EQD1 to EPK5 and It would not flash and would fail every time whilst using the latest Odin. So good luck on finding anything on getting you back to another firmware version but at this time I do not believe there is anything that will move you back to the firmware you want. If you do happen to find something or make your own exploit do tell @sanaullahkhan371 If you are on QD1 you are not going to be able to downgrade if you are on PK5 you can try the Odin downgrade method that will5 presumably used but if you are not in this firmware use case you are SOL.
will5 said:
I downgraded from 6.0.1 epk5 to 5.1.1 with no problem.
Not sure about qd1.
As long as you have the odin firmware, I see no problem.
Click to expand...
Click to collapse
Hi,
Can you please let me know how did you downgrade? Is it straight away flash to 5.1.1 or did you follow any steps?
I am also planning to downgrade. Anyways, I stopped using Note 4 after update to 6.0.1 as it was switching off every now and then due to update. Might as well make this phone usable to take photos and as a video player for my kid
Thanks
roxster said:
Hi,
Can you please let me know how did you downgrade? Is it straight away flash to 5.1.1 or did you follow any steps?
I am also planning to downgrade. Anyways, I stopped using Note 4 after update to 6.0.1 as it was switching off every now and then due to update. Might as well make this phone usable to take photos and as a video player for my kid
Thanks
Click to expand...
Click to collapse
I just odin to this firmware N910AUCU2DOI2-5.1.1 It s available somewhere on this forum.
Read how to odin if you never used it. In this case you need to unzip the file and load AP, BL, CP and CSC files on odin and flash.
Was running 6.0.1 epk5 previously.
will5 said:
I just odin to this firmware N910AUCU2DOI2-5.1.1 It s available somewhere on this forum.
Read how to odin if you never used it. In this case you need to unzip the file and load AP, BL, CP and CSC files on odin and flash.
Was running 6.0.1 epk5 previously.
Click to expand...
Click to collapse
Thanks a lot buddy! :good:
My note 4 was also running on 6.0.1 EPK5. Found the 5.1.1 firmware and followed your instructions to downgrade. My phone came back to life and is usable now.:victory:
No more switching off abruptly! I wont update anymore since all the apps which I use are working fine with current version of Android.
braindead444 said:
Once you are on QD1 you will not be able to go back to anything lower than that firmware. The bootloader is now at the latest version and has blown one of those imaginary "e-fuses" so that you can not go back in time to any other vulnerable OS. I just tried today to go from EQD1 to EPK5 and It would not flash and would fail every time whilst using the latest Odin.
Click to expand...
Click to collapse
Were you ever able to flash back to an older version from QD1? Others have said that the bootloader was not incremented in QD1.
spocko said:
Were you ever able to flash back to an older version from QD1? Others have said that the bootloader was not incremented in QD1.
Click to expand...
Click to collapse
Were you able to downgrade from EQD1 to 5.1.1? I am on EQH1 and I am not able to downgrade
somani09 said:
Were you able to downgrade from EQD1 to 5.1.1? I am on EQH1 and I am not able to downgrade
Click to expand...
Click to collapse
I'm also on EQH1. I have never tried to downgrade. I was just curious if it was possible, in case a root method was discovered that only worked on older versions. But I've just learned to live without root. EQH1 works fine for me.
I had the infamous freeze/reboot/shutdown issue with 6.0.1 and I wasn't sure if that was the issue but I downgraded to 5.1 and have fewer issues now. The phone runs just fine, except it does not reboot. You have to do a soft reset every time. But with the Wakelock app, at least it runs.
roxster said:
Thanks a lot buddy! :good:
My note 4 was also running on 6.0.1 EPK5. Found the 5.1.1 firmware and followed your instructions to downgrade. My phone came back to life and is usable now.:victory:
No more switching off abruptly! I wont update anymore since all the apps which I use are working fine with current version of Android.
Click to expand...
Click to collapse
Hi can i ask if u still have that firmware file