Related
Hi there geniuses of XDA! (somewhat of a noob here)
Need some help. I want to update my VZW HTC One (m7) to the Android L version (I think its out now, maybe not though, if not 4.4.3). I currently have Android 4.2.2. I am rooted, unlocked, and S-Off. I am running ClockworkMod Recovery and have a nandroid backup in that, that I would like to maintain in case things go wrong. It is my understanding that if I were to switch to TWRP my backup would not work, so I would like to stay with CWM. So can anyone provide a suggestion of a good ROM to get that will bring me up to current version and will still work with CWM?
Thanks, your help is greatly appreciated.
Steve
Also let me point out that I am still on Firmware 1.10.605.8. How do I get this updated? Looks like most of the current ROMs require later firmware. Basically I rooted last year, day one when I got the phone and have not updated anything since then. So I really need some help on getting current. Step by step instructions would be most helpful.
Thanks
lostnsound said:
Also let me point out that I am still on Firmware 1.10.605.8. How do I get this updated? Looks like most of the current ROMs require later firmware. Basically I rooted last year, day one when I got the phone and have not updated anything since then. So I really need some help on getting current. Step by step instructions would be most helpful.
Thanks
Click to expand...
Click to collapse
See people's response in your other question thread. Furthermore, I would like to add that after you update your firmware from santod's thread - you will want to update to the latest ROM. We do not have L as you have requested. There is a preview floating around in the international forum, but it is not for daily use and not for VZW. I suggest - if you want stock to either use Santod's stock rom's as they are stock completely or Andybone's which are stock with minor tweaks. Outside of that there are stock based ROM's that have an abundance of tweaks - NuSense, Ecliptic, Viper, etc.
If you run into recovery issues (due to potentially outdated CWM) - I suggest trying Philz. It is CWM based but easier to use. You should be able to access your backup. You can also pull the backup off your phone and save it on a computer. It will be saved in clockworkmod/backups or something.
brymaster5000 said:
See people's response in your other question thread. Furthermore, I would like to add that after you update your firmware from santod's thread - you will want to update to the latest ROM. We do not have L as you have requested. There is a preview floating around in the international forum, but it is not for daily use and not for VZW. I suggest - if you want stock to either use Santod's stock rom's as they are stock completely or Andybone's which are stock with minor tweaks. Outside of that there are stock based ROM's that have an abundance of tweaks - NuSense, Ecliptic, Viper, etc.
If you run into recovery issues (due to potentially outdated CWM) - I suggest trying Philz. It is CWM based but easier to use. You should be able to access your backup. You can also pull the backup off your phone and save it on a computer. It will be saved in clockworkmod/backups or something.
Click to expand...
Click to collapse
Thanks for the assistance brymaster5000. This is all very helpful information.
lostnsound said:
Hi there geniuses of XDA! (somewhat of a noob here)
Need some help. I want to update my VZW HTC One (m7) to the Android L version (I think its out now, maybe not though, if not 4.4.3). I currently have Android 4.2.2. I am rooted, unlocked, and S-Off. I am running ClockworkMod Recovery and have a nandroid backup in that, that I would like to maintain in case things go wrong. It is my understanding that if I were to switch to TWRP my backup would not work, so I would like to stay with CWM. So can anyone provide a suggestion of a good ROM to get that will bring me up to current version and will still work with CWM?
Thanks, your help is greatly appreciated.
Steve
Click to expand...
Click to collapse
I would recommend Viper for sense 6 / 4.4.2, Santod's GPE 4.4.4 for gpe, or CM11 4.4.4 for a great aosp experience.
Just one thing to point out - if you move away from sense roms, you will lose some camera function. Only the sense camera(which only works on sense roms) really works well. If you go GPE or AOSP you will see a noticable drop in camera boot times, focus times and flash timing.
Good evening everyone -
I'm running into some issues with my LRA version of the M8. I am/was rooted and running TWRP fine until I decided to revert back to the stock recovery so I could install the latest OTA that was released to me. Like an idiot I never backed up my stock OTA before flashing TWRP so I extracted the firmware.zip from the OTA download, relocked my bootloader, then used fastboot to flash firmware.zip. All seemed to go well until I rebooted, I'm now stuck at the HTC splash screen and can get no further. Things I've done:
- tried booting into recovery, got red triangle w/red exclamation mark
- unlocked bootloader and installed TWRP, can get into recovery now at least
- tried factory reset
- wiped cache, no luck
Unfortunately the LRA M8 isn't very common it appears so I'm unable to find a stock ROM to try and reinstall. I'm hoping someone might be able to help me get started back up without the need for my stock RUU or nandroid backup. Any assistance would be greatly appreciated, please let me know what other info I could provide to help out. Thanks in advance.
promsos said:
Good evening everyone -
I'm running into some issues with my LRA version of the M8. I am/was rooted and running TWRP fine until I decided to revert back to the stock recovery so I could install the latest OTA that was released to me. Like an idiot I never backed up my stock OTA before flashing TWRP so I extracted the firmware.zip from the OTA download, relocked my bootloader, then used fastboot to flash firmware.zip. All seemed to go well until I rebooted, I'm now stuck at the HTC splash screen and can get no further. Things I've done:
- tried booting into recovery, got red triangle w/red exclamation mark
- unlocked bootloader and installed TWRP, can get into recovery now at least
- tried factory reset
- wiped cache, no luck
Unfortunately the LRA M8 isn't very common it appears so I'm unable to find a stock ROM to try and reinstall. I'm hoping someone might be able to help me get started back up without the need for my stock RUU or nandroid backup. Any assistance would be greatly appreciated, please let me know what other info I could provide to help out. Thanks in advance.
Click to expand...
Click to collapse
Did your firmware.zip have a boot*.img in it? You probably need the old version of the boot.img to match the old software. You might want to find on of the old Verizon RUUs and extract the boot.img from there and try flashing that in fastboot. Message me if the Verizon boot doesn't work for you, I might have some other ideas. I'd say be careful, but you're already in trouble.
Edit: You could also do a nandroid backup and try a custom ROM to get it functional in the short term.
I did eventually grab a nandroid backup and loaded Viper Rom on it, although it's a bit quirky - probably because the LRA version of the phone is slightly different than the stock Verizon version. That being said, the firmware.zip that I loaded did have a boot.img file in it so I'm guessing that's the issue. Do you think the boot.img from a Verizon RUU would work considering my phone is not the same exact version as the Verizon one? Or another way to ask it I guess is if there's really any harm in me restoring my nandroid and loading a standard Verizon boot.img? I'd think it can't render my phone any more useless than it was previously, just wasn't sure how locked in the boot.img file was to the specific model\OS that's on the phone. The whole LRA phone thing is really a kick in the pants.
promsos said:
I did eventually grab a nandroid backup and loaded Viper Rom on it, although it's a bit quirky - probably because the LRA version of the phone is slightly different than the stock Verizon version. That being said, the firmware.zip that I loaded did have a boot.img file in it so I'm guessing that's the issue. Do you think the boot.img from a Verizon RUU would work considering my phone is not the same exact version as the Verizon one? Or another way to ask it I guess is if there's really any harm in me restoring my nandroid and loading a standard Verizon boot.img? I'd think it can't render my phone any more useless than it was previously, just wasn't sure how locked in the boot.img file was to the specific model\OS that's on the phone. The whole LRA phone thing is really a kick in the pants.
Click to expand...
Click to collapse
The boot.img from an older Verizon RUU would probably work, but you might have to try a couple to get the right one. The boot.img is directly tied to the ROM version that is installed, and is often called the kernel and tells the system how to boot the ROM.
Make sure you do a backup of your working Viper before restoring the stock one and trying to flash a boot.img.
I don't understand why you re locked the boot loader and flashed a firmware zip just to revert to stock recovery? All you had to do was pull the stock recovery from the firmware.zip in the OTA then flash it via fast boot. Then go ahead and flash the OTA.
You need to now find and flash a compatible boot.img. Just keep trying different ones until it boots.
I'm making a little progress here, thanks for the help. I downloaded a 4.4.3 Verizon kernel, loaded that (after restoring the old nandroid backup) and I'm able to boot, whew... I'm having two issues now, 1) my wireless won't turn on for some reason and 2) I tried installing the 4.4.4 OTA update my carrier released (downloaded via 4G) and it won't apply - I was hoping successfully applying this OTA would fix the wireless issue. Looking at my software version it looks like I'm actually running 4.4.2, could that cause both of these issues? I'm trying to locate a 4.4.2 kernel to load but figured I'd toss out the question in the meantime.
Ashyx - I wish I had a better answer to why I temporarily relocked the boot loader and flashed firmware.zip other than desperation (trying to get that darn OTA). It was a while ago I flashed the firmware.zip file but I thought that when I initially extracted the recovery from the zip file and flashed it I could no longer boot into a recovery, maybe I'm making that up though - I can hardly remember last week lol. I'm an IT guy, so I'm not completely clueless, but I'm far from proficient with mobile technologies, as I'm sure you gathered already.
Anyways, I'd appreciate any insight, in the mean time I'm going to keep hunting for a 4.4.2 kernel to try on this thing. Thanks again to all.
http://forum.xda-developers.com/showthread.php?t=2723159
Try the zips from here, they should have a boot.img for 4.4.2.
Sent from my One M8 using XDA Free mobile app
Ok, I think I'm back up and running. I was able to find a 4.4.2 boot.img that allowed me to once again use my wireless. After getting the wireless working I had to find valid versions of flashlight.apk and calculator.apk to put in data/preload and the OTA finally took....success at last. I really appreciate the help durgis, I'll be grabbing a nandroid of my now working phone right away so I don't run into issues in the future. Again, thank you for the help, very much appreciated.
I suspect that we are on the same carrier, LRA__001. I've been fighting a similar problem to yours. The only custom rom I've been able to install is Cyanogenmod. It's good, but the battery life is horrible for me. Also, I can't get MMS or 4G to work. Everything other rom I've tried won't boot up for me. Any chance that you could provide a link to your nandroid backup? I'm looking to get back to a more stock rom that I can get OTA updates on. Thanks.
rook79 said:
I suspect that we are on the same carrier, LRA__001. I've been fighting a similar problem to yours. The only custom rom I've been able to install is Cyanogenmod. It's good, but the battery life is horrible for me. Also, I can't get MMS or 4G to work. Everything other rom I've tried won't boot up for me. Any chance that you could provide a link to your nandroid backup? I'm looking to get back to a more stock rom that I can get OTA updates on. Thanks.
Click to expand...
Click to collapse
Hey rook, I do have the same CID, are you on Cellcom out of Wisconsin? I didn't grab a bare bones nandroid, but i can do a backup, uninstall my apps and do one, or rebuild mine from my unbootable one now that I have everything i need. If you want to try a different ROM you could try Viper, it worked decent for me, just a few quirks when i bounced from wireless to 3G for some reason.
I am with Cellcom. My problems started with the recent OTA update. The update wouldn't take, because of the flashlight.apk. I decided it was time to root this phone anyway and try some custom roms. I've done it with my other HTC phones in the past with no problems. Unlocked the bootloader, loaded TWRP and did a backup. Didn't check where the backup was being put and ended up saving it to internal. Put on a new ROM and wiped my backup. Cyanogenmod 11 is the only ROM that I've had success with. Every other rom that I have tried so far will not complete the initial boot. I suspect that I'm missing something stupid, or it has something to do with the OTA update not completing. Are you running Viper, or did you get the Cellcom OTA update to work?
I was running Viper for a while but now have my phone reverted to stock with the 4.4.4 OTA applied. If you want a nandroid of stock Cellcom 4.4.4 I can work on one for you, it may take a couple days to get it but I should be able to get one.
That would be awesome. I've been looking for a stock Rom for a while now. As you know those are nearly impossible to find. Not having a stock nandroid backup or the OTA update zip kind of put me in a SOL position. Thanks for your help.
Finally got around to this, try the download below, it's the stock 4.4.4 ROM and also the stock recovery (for future OTA updates). Let me know if it works out for you. I also have the 4.4.4 OTA updated if needed.
https://www.dropbox.com/s/thd0z8l2zlprt3r/One M8 LRA 4.4.4 Stock.zip?dl=0
That worked awesome. Thanks!!!
Hi Guys, (@rook79 , @promsos)
i have the same model and running into similar problem, i was also not able to flash any other rom than SkyDragon, wanted to be able to flash other roms but no luck, i thought its the firmware that wont let me install so i went for S-Off and flashed one of the firmware from verizon, since there was not much help for this specific model and everyone was referring it as a variant from verizon, i did flash one and my problem started, my phone had no signals after flashing the firmware and was still not able to flash any other ROM, i flashed couple of more firmwares and radios to get my network working but no luck, and i got a new problem that the phone keeps rebooting after a couple of minutes it loads into system.
then somebody helped me with the stock firmware 4.4.4 from here and nandroid from this thread, firmware was still verizon, i managed to restore it but still the same reboot issue and no signals, but i was able to download OTA which wont install, everytime i try to install it, it goes to stock recovery with a progress bar 1% filled and then stuck into boot loop and after n number of attempts it boots into system, where again it reboots after a couple of minutes.
extracted the firmware from OTA and manually flashed it and tried to install OTA but still same, i tried to reboot into stock recovery but every time i do that, it goes to black screen and then keep rebooting, i am not able to get to that red triangle screen.
help less clueless trying to find complete RUU for it (not sure if thats going to help)
my partition table has 2 vzw partitions as well because i flashed dottat's RUU for verizon.
can you guys help me with that?
my phone is m8_wlv CID: LRA_001 MID: 0P6B20000
s-off, and i am on a GSM network (not US).
promsos said:
Finally got around to this, try the download below, it's the stock 4.4.4 ROM and also the stock recovery (for future OTA updates). Let me know if it works out for you. I also have the 4.4.4 OTA updated if needed.
https://www.dropbox.com/s/thd0z8l2zlprt3r/One M8 LRA 4.4.4 Stock.zip?dl=0
Click to expand...
Click to collapse
I'll appreciate if you share the 4.4.4 OTA, I really need it now.
hoang555 said:
I'll appreciate if you share the 4.4.4 OTA, I really need it now.
Click to expand...
Click to collapse
is this what you are looking for? https://www.dropbox.com/s/2oozc291kwe5l9r/OTA_M8_WL_L50_SENSE60_MR_LRA_US_4.21.512.4-3.31.512.2_release_426215.zip?dl=0
hoang555 said:
I'll appreciate if you share the 4.4.4 OTA, I really need it now.
Click to expand...
Click to collapse
Hi
Do you still have that LRA version?? I need some help
Hi,
I have 855 (generic European version), V10L, rooted (using towel rooter), no TWRP, all OTA (since July 2014) installed automatically and seamlessly so far (keeping the root).
Today I got a prompt about V20E available upgrade.
I have LG PC Suite up-to-date backups of this device, and anyhow don't have anything that can't be restored, but in general prefer to not reconfigure everything manually.
Did nothing so far.
Questions:
Is it worth to move to V20E, is the version stable enough, worth to wait for V20F or whatever comes next ?
If I decide to proceed now, I want to be able to return to my current state (I do not need to fast switch between multiple roms, just way to get back V10L with my current configuration).
I prefer the way that allows me to keep receiving OTAs, and not to flush next updates manually.
After looking on the forums I though about the following workflows
First (without TWRP):
1. Create one more backup using LG PC Suite.
2. Unroot (just to be safe).
3. Accept OTA.
If I understand correctly I will loose root here, and it can not be restored (for now).
In case of need to restore:
1. Follow LG G3 Stock Firmware (Go Back to Stock) to flash D855 V10A. I hope after flushing it will receive 10L OTA ? Am I right, or I will be stuck with 10A ?
2. Restore my existing backup using LG PC Suite. If I do restore on V10A, will it bring me back to 10L ?
3. Reroot if needed.
Second, with TWRP:
1. Install TWRP.
2. Create full backup from inside TWRP.
3. Get prebumped Lollypop image (I see only V20C here. Where can I get more recent versions ?)
4. Install it and reroot if needed.
In this case I must reject upcoming OTA prompts and flash future prebumped images manually.
To restore
1. Restore full TWRP backup, and I'll get V10L with all my stuff preconfigured.
2. If at this step I want to get rid off TWRP, can I remove it somehow ? Will it restore the phone to the current state (rooted, V10L, able to get OTAs) ?
Sorry for multiple questions but currently the whole process looks a bit unclear for me.
Q: Is it worth to move to V20E, is the version stable enough, worth to wait for V20F or whatever comes next ?
A: No V20H got released today and its probably gonna be available in your region really soon
Note: If you do ever want to install stock lollipop please be aware LG backup cannot save the appdata of any system applications such as chrome etc etc
Q: Follow LG G3 Stock Firmware (Go Back to Stock) to flash D855 V10A. I hope after flushing it will receive 10L OTA ? Am I right, or I will be stuck with 10A ?
A: Check (http://lg-phone-firmware.com/index.php?id_mod=41) and download the v10 firmware the corrosponds with your country. If the firmware has a 6 in front of it its for the 16GB variant
Q: Where can I get more recent versions?
A: http://forum.xda-developers.com/lg-g3/development/stock-t2961073
Q: If at this step I want to get rid off TWRP, can I remove it somehow ? Will it restore the phone to the current state (rooted, V10L, able to get OTAs) ?
A: Yes, by flashing stock recovery.img. Restoring your TWRP backup will restore the phone to the current state
itsbighead said:
A: Yes, by flashing stock recovery.img. Restoring your TWRP backup will restore the phone to the current state
Click to expand...
Click to collapse
Thanks, but I am not sure about this one. What is the process ?
If I flash stock kdz it will remove TWRP, but I will not be able to restore TWRP backup (without TWRP), right ?
Is it possible to first restore TWRP backup, then flash "something" that will replace only TWRP, leaving android OS intact ?
Before saying anything, I would just like to give you a thank you for your post, it's very clear and pleasant to read. Looks like you also did a bit of research before asking so that is also very good :good:
So, I'm not gonna be able to help you a lot about the backup thing because I like to always start fresh when I change Rom or if I want to go back to stock. I backup my data manually and restore what I want to. Using a Google account it will automatically reinstall your apps, but you'll have to reconfigure them manually.
Anyway, I also got a D855, French variant A6FR. (A6 means 16GB) You can check what is the latest version that LG offers you by checking the link bellow. You just put your IMEI at the end and it will give you an XML with information about your phone, like your specific variant (German, UK, ... don't know where you are from) and the latest firmware available for your and a link to download it. For me it says D85520F_00 so it's LL version F.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=IMEI
So, you can go back to stock using the KDZ method and with the firmware LG offers you (removing root, revovery, ...), but as you probably now, LL is not rootable. To summarize, that is not really interesting unless you want a STOCK STOCK LL.
But you guessed right with the V10A. If you go back to stock with this version, it will remove the root, custom recovery and anything else you have, you will also end up with a completely stock G3, but KitKat G3. There is no obligation to use V10A, if you find a KDZ of a later version you can use it too. Of course we are talking here about V10something not V20 that is LL. Just make sure to use a version suitable to your phone (16/32GB).
Flashing that, LG will be happy and will let you do OTAs. So if you flash V10A, it will give you all the OTAs untill the latest available. So you can go V10A --> V10B --> V10C --> ...... --> V10L --> ..... --> Lollipop
You won't be stuck with V10A.
Now if you want a rooted LL, you will need to use a custom Rom. In the Dev section you can find for example GloudyG3 that is based on the stock LG rom with a few enhancements. It is currently based on V20F and will probably move to V20H which is a brand new version that went up like 2 days ago.
To summarize
KDZ with V10something allows you to go completely stock and give you official OTAs. It can be rooted.
KDZ with V20something works too and will give you OTAs, but is not rootable, so if you want a custom rom, you will have to downgrade to V10, root and install TWRP.
Flashing a KDZ always erase everything on your phone.
If you flash a custom rom, you won't have LG's OTAs so you won't have to worry about rejecting them.
Before doing anything crazy, backup your EFS (basically your IMEI partion) with TWRP and manually. Always nice to have several ways to do it.
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.
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