Hi guys!
First of all, I did a lot of research on the dev forums, and surely I've learned a lot, but somethings are still not clear for me.
My Defy runs a stock branded Eclair, but I'd like to try Froyo ROMs and also the CM7 port. I don't want to lose the ability of coming back to the stock firmware, though. As far as I understand, I have to make a nandroid backup of my phone and then Flash the Froyo ROM without CG31 and CG39, so that I can go back to the original firmware. I've understood that CG31 is something related to phone signature, and CG39 related to system partition. But will the Froyo ROM work without the CG39 flashed? Is there any resultant difference of flashing a full ROM and a "fixed" ROM besides losing the downgrade ability?
I couldn't find any description of what each CG is responsible for, do you guys have any link?
Also, on every ROM thread, someone asks for a nandroid backup of it. Why? Is it easier to flash ou flashing through a nandroid backup preserves the downgrade possibility too?
My phone infos:
System Version:
Blur_Version.6.36.1.MB525.Vivo.en.BR
Firmware Version:
2.1-update1
Version Number:
JORLA_U3_6.36.1
Thanks very much for the attention!
Daniel
The Korean Froyo will let you downgrade back to Eclair.
Its the only sbf (atm) you can flash directly and still go back.
Otherwise you need to use a nandroid and fixed sbf of the Froyo version you want to use.
People want a nandroid because the way around not being able to downgrade is to make up a 'full' rom using the nandroid + a fixed sbf.
So a nandroid gives you CG39 and the fixed sbf makes up the rest of the CG's; thus a 'full' rom.
Rather then flash a full sbf and lose the means to downgrade.
Fixed sbf's exist already: http://forum.xda-developers.com/showthread.php?t=966537
Codegroups: http://forum.xda-developers.com/showthread.php?p=11195544
Btw should also mention Daniel here is smarter than the average bear; he reads before trying . . . . P
Fritolays, thank you for the ultra-fast response!
In fact I've been reading threads here for more than one week... Obviously it's possible to learn a lot from intuition and observing things, but there are moments in which pieces of the puzzle start to miss, because a lot of informations are implicit on the threads or treated like already known by people who are discussing it, what's pretty normal methinks, but makes it a little difficult for the new ones to understand things.
For instance, before reading your reply I was thinking that one should flash the fixed sbf OR the nandroid backup, because I believed they had similar purposes...
So, this also means that when going back from Froyo to original Eclair I'll also need a Eclair sbf besides my nandroid backup, right? Does it have to be a specific one to match my nandroid backup or not?
Also, do you recommend flashing the full Korean Froyo ROM or another ROM with fixed sbf plus nandroid backup?
To receive the official Motorola Froyo upgrade whenever (if ever) ready I'll have to have my stock firmware, right?
Thanks and cheers from Brazil!
To go back to Eclair, yes you will need an Eclair sbf. Though is does not need to be the exact same version (just dont use 2.51, prevents downgrade); as your nandroid will overwrite the system partition with your Eclair version. Just need the sbf to restore the other codegroups.
Personally I just use the Korean Froyo as a starting point. Saves on headaches because you can just flash the sbf. Dont need to install recovery then restore nandroid then flash fixed sbf. Less rebooting P
Ya to get the official moto Froyo, if they ever decide to release it, you will most likely need to be on an Eclair build. But to be honest who cares; with Quarx working on Gingerbread, motorola can shove it. Why have 2.2.2 when he's working on 2.3.3 ? hehe
Hope this help !
fritolays said:
To go back to Eclair, yes you will need an Eclair sbf. Though is does not need to be the exact same version (just dont use 2.51, prevents downgrade);
Click to expand...
Click to collapse
When flashing Eclair back from Froyo should I flash the whole sbf and then restore nandroid backup or should I left CG31 and CG39 out like if I were upgrading with a fixed rom?
fritolays said:
as your nandroid will overwrite the system partition with your Eclair version. Just need the sbf to restore the other codegroups.
Click to expand...
Click to collapse
Do you know what CGs are present in a Nandroid backup?
fritolays said:
Personally I just use the Korean Froyo as a starting point. Saves on headaches because you can just flash the sbf. Dont need to install recovery then restore nandroid then flash fixed sbf. Less rebooting P
Click to expand...
Click to collapse
It saves on headaches but if I don't install recovery, although I'll be able to flash Korean Froyo directly, there will be no way to backup my firmware and so even if I am able to downgrade I won't have my backup to do so. Right?
fritolays said:
Ya to get the official moto Froyo, if they ever decide to release it, you will most likely need to be on an Eclair build. But to be honest who cares; with Quarx working on Gingerbread, motorola can shove it. Why have 2.2.2 when he's working on 2.3.3 ? hehe
Click to expand...
Click to collapse
You are right but don't forget about warranty! Say my camera or touchscreen stop working, they will put the blame on the modded firmware, so I have to be able to go forth and back to keep things official if needed.
fritolays said:
Hope this help !
Click to expand...
Click to collapse
Sure you're helping! Thank you very much!
danimagrin said:
When flashing Eclair back from Froyo should I flash the whole sbf and then restore nandroid backup or should I left CG31 and CG39 out like if I were upgrading with a fixed rom?
Do you know what CGs are present in a Nandroid backup?
It saves on headaches but if I don't install recovery, although I'll be able to flash Korean Froyo directly, there will be no way to backup my firmware and so even if I am able to downgrade I won't have my backup to do so. Right?
You are right but don't forget about warranty! Say my camera or touchscreen stop working, they will put the blame on the modded firmware, so I have to be able to go forth and back to keep things official if needed.
Sure you're helping! Thank you very much!
Click to expand...
Click to collapse
Yup to downgrade flash the full sbf, then your nandroid - fixed sbf's are for going up in versions.
Doesnt really work that way. It backs up your data, cache and system partitions.
Make a backup before you flash the sbf. The backup gets saved to your sdcard card so you can copy it to your computer. That way even if recovery gets deleted from flashing a full sbf you can just re-install recovery, copy your nandroid back to your sdcard, restore it and be on your merry way.
I void warranties. ) At this point its your call. Just to note though officially moto will not fix your phone if it has a leaked version on it. Official ones are ok, and the Korean one is the only official Froyo one out there.
When one sends something for repair here in Brazil they ask for the proof of purchase/invoice (don't know what's the best word for that in English). So, you know... It's a little strange... A phone bought in Brazil running Korean software. They will complain immediately But I won't worry about that.
I've read the CGs thread. Unfortunately there isn't a long explanation about what each CG is responsible for, but only a short description for some of them, and no description for 32, 35, 42, 45, 53, 61, 64 and 65.
However, as far as I understood, some CGs stay the same but some change between different ROM versions. So, if I reflash Eclair after Froyo and restore my Nandroid Backup, despite having the same data, cache and system partitions, some CGs will be different from the firmware I'm running now. Any issues about that, if I choose to stay with Eclair after all?
I've sucessfully made the nandroid backup of my phone.
But just to make sure I understand things, I would like to make one last question. I couldn't find the exact sbf of my firmware on the internet (JORLA_U3_6.36.1).
So, if I need to reflash 2.1, it won't be JORLA_U3_6.36.1.
Will my nandroid backup work together with any other 2.1 sbf than the JORLA_U3_6.36.1? For instance, will it work if I flash JRDNEM_U3_2.21.0, that I can find on the internet?
Thank you...
danimagrin said:
When one sends something for repair here in Brazil they ask for the proof of purchase/invoice (don't know what's the best word for that in English). So, you know... It's a little strange... A phone bought in Brazil running Korean software. They will complain immediately But I won't worry about that.
I've read the CGs thread. Unfortunately there isn't a long explanation about what each CG is responsible for, but only a short description for some of them, and no description for 32, 35, 42, 45, 53, 61, 64 and 65.
However, as far as I understood, some CGs stay the same but some change between different ROM versions. So, if I reflash Eclair after Froyo and restore my Nandroid Backup, despite having the same data, cache and system partitions, some CGs will be different from the firmware I'm running now. Any issues about that, if I choose to stay with Eclair after all?
Click to expand...
Click to collapse
I don't think some CG's stay the same when you flash an sbf, I believe its the CG version that changes. For instance if a particular CG is at version 2 on your phone, some froyo full flashes may update that CG to version 3, and thus you cannot flash back down to a version 2, you can only flash CGs that are the same version or higher.
kashavsehra said:
I don't think some CG's stay the same when you flash an sbf, I believe its the CG version that changes. For instance if a particular CG is at version 2 on your phone, some froyo full flashes may update that CG to version 3, and thus you cannot flash back down to a version 2, you can only flash CGs that are the same version or higher.
Click to expand...
Click to collapse
You're right indeed, but as far as i know some CGs do stay the same between different sbf versions, as you can see, for example, in this comparison taken from CM7 thread:
sunoldman said:
If you depack a full sbf, you will find several CG??.smg files. Here's a comparison between 3.4.3_11 and 3.4.2_177.
Code:
CG31 cdt Codegroup Description Table same
CG32 bploader Baseband Processor Bootloader same
CG33 cdrom CDROM diff
CG34 lbl Linux Bootloader same
CG35 boot Android Boot Image diff
CG39 system Android System diff
CG42 logo boot logo diff
CG45 bpsw Baseband Processor Firmware diff
CG47 recovery Android Recovery Image diff
CG53 kpanic Kernel Panic Console same
CG61 devtree Device Tree same
CG64 mbr eMMC Master Boot Record same
CG65 ebr eMMC Extended Boot Record same
Click to expand...
Click to collapse
Just forgot to mention that this also means, obviously, that CGs having same version can binarly differ...
Very useful information for Android beginners like me, but the most important question still remains - is full sbf of the stock ROM is required in case of downgrade to the stock version? Or can I use nandroid backup of my stock ROM together with different version of Eclair sbf?
The problem is that I cannot find full sbf of my stock ROM, but I want to be able to get back to it if needed.
Agreed, some code groups can stay the same. I wonder what the procedure is to work out what version a CG is?
Actually a database/table of s/w versions along with the CG numbers and version would be a good resourse to help people understand what downgradability options they have by knowing what versions they are flashing to their phones.
mindugo said:
Very useful information for Android beginners like me, but the most important question still remains - is full sbf of the stock ROM is required in case of downgrade to the stock version? Or can I use nandroid backup of my stock ROM together with different version of Eclair sbf?
The problem is that I cannot find full sbf of my stock ROM, but I want to be able to get back to it if needed.
Click to expand...
Click to collapse
Have you tried to plug your device to your PC and seeing if the Motorola Software Update tool detects any software versions for it? If so it will download the complete sbf from motorola servers to your Hard Drive.
kashavsehra said:
Agreed, some code groups can stay the same. I wonder what the procedure is to work out what version a CG is?
Actually a database/table of s/w versions along with the CG numbers and version would be a good resourse to help people understand what downgradability options they have by knowing what versions they are flashing to their phones.
Click to expand...
Click to collapse
Used MotoAndroidDepacker (also used to fix SBFs) to extract individual CGs, than the app from http://forum.xda-developers.com/showthread.php?t=945035 to tell each CGs' version. To compare CGs you can use good old linux diff command.
mindugo said:
Very useful information for Android beginners like me, but the most important question still remains - is full sbf of the stock ROM is required in case of downgrade to the stock version? Or can I use nandroid backup of my stock ROM together with different version of Eclair sbf?
The problem is that I cannot find full sbf of my stock ROM, but I want to be able to get back to it if needed.
Click to expand...
Click to collapse
I had the same doubt as yours because I couldn't find the exact sbf of my stock ROM also, but I've tested my stock ROM Nandroid backup (Eclair) and it worked together with every different Eclair SBF I tried, independently whether the "helper" sbf was full or fixed or the CG version it had. Just be aware that even a Eclair ROM may have greater CG version than the one installed on your phone so if you flash one of these you won't be able to come back using a full sbf (if you had it...). However if you lock your phone you can always downgrade using fixed sbf + nandroid backup.
Don't know if I was clear enough, I know this is confuse to explain.
It's easier if you tell your stock rom version and what you want to do exactly.
Feel free to ask if you have any doubts...
Question about update and downgrade
Hello android people!
I'm new to android world, and i have done some things, differente from daniel.........i didn't read sufficiently before, and i already have make some upgrades.
I installed a sbf file - 3.4.2-117 002 blur usa
I wanna know if i can go back to Eclair sbf, just like daniel asked, cause i'm from Brazil and i have the same thing he sayed, about lose the warranty.
Another question, i get the 3.4.3-11 blur usa, the one Quarz from CM7 recomend to install.
If i install that sbf, can i downgrade to the one that i'm already using, or to the Eclair sbf??
Thanks everybody, i starting to like very much this forum, and the android world.
Cheers
Related
Just a quick one.
Ive come from the desire which ive installed just about every rom on and modified the partition table dozens of times so im no stranger to rooting... however this defy has me confused.
I need 2.2 to access lotus traveller for my work emails so im looking to install a custom rom until T-mobile uk finally release the official one but im reading all sorts of things like not being able to downgrade if you flash certain roms which arent "fixed".
Can someone give me a brief overview so i can get my head round what all this is about and can anyone point me in the direction of a good solid 2.2 rom which is as close to the official rom as possible?
cheers
edit : forgive the title, its meant to say FROYO!!
Here you go fella http://forum.xda-developers.com/showthread.php?t=993402
I've just recently flashed this 3.4.3-11 http://depositfiles.com/en/files/tjnmh6d98 onto my Defy & it's running great. There's no T-Mobile branding on this one & I doubt that you would be able to downgrade to an older version either.
You'll need RSD Lite V4.9, Motorola Drivers (I used V4.9 for these).
I followed Higgsy's great guide http://forum.xda-developers.com/showthread.php?t=853674 about flashing a sbf & it worked a treat - in fact this current sbf is the 2nd froyo that I've flashed.
Hope this helps.
thanks for that. Ive actually managed to get a version of 3.4.2 on now which can be downgraded. Im starting to get the hang of this, it certainly a different process than what im used to thanks to motorola!
Im trying to keep it to stock roms now as I found with my desire there was always some bug that "bugged" me with custom roms so with this I think when the official 2.2 comes out for the UK I will flash it and keep the phone unrooted ( I only ever initially got into rooting for apps2sd anyway)
The reason for needing to keep it downgradeable is purely for the warranty with t-mobile otherwise I would just go with the rom you suggested.
Do you know of any version of 3.4.3-11 that is out there that is downgradeable that is still close to stock in terms of apps and features?
edit :its worth noting that higgsys procedure doesnt work with the eclair 2.51, you end up with the black screen issue. ( I imagine most are shipping with this now) although the general guidelines still apply, just different files are needed.
I'm not clued up on anything other than flashing a sbf via RSD Lite but if you have a look at the SBF Service File sticky in the Defy Dev forum the last post or two links to a fixed sbf & a nandroid of 3.4.3-11.
Sent from my MotoDefy.
Ive been looking through some of the posts on the Android development board, but im relativly new to the idea of flashing different roms.
At the moment my phone is running the standard Froyo 2.2.2 firmware, from Motorola,
system version 34.164.3.MB525.Retail.en.FR
Is it a simple process to change this?
can i go back to the default Rom/version( listed above)? or would i be stuck with, say, cyanogenmod 2.3.4?
would i still be able to use the Motorola phone portal to send texts via my p.c?
http://forum.xda-developers.com/showthread.php?t=1065798
Follow this tutorial..everything is given in this..
The process is simple..u may face few problems flashing a ROM,just search in this forum for the solution.
Well yes u can go back to your stock ROM if you have the sbf file or an nandroid backup.
Yes phone portal is present in CM7 also..so not a problem.
All the best
Thanks for the link, although im still non the wiser.
You said
Well yes u can go back to your stock ROM if you have the sbf file or an nandroid backup.
Click to expand...
Click to collapse
How can i get hold of that file? my phone updated via motorola sfotware update to this:
Version.34.164.3.MB525.Retail.en.FR
and its running Firmware version 2.2.2
whats this nordic firmware?, and if thats 2.1 would that cause probelms as my phone is curently 2.2.2??
you already have the right firmware. start to flash cm7. should be fine.
klickig said:
you already have the right firmware. start to flash cm7. should be fine.
Click to expand...
Click to collapse
How can i get hold of a revocery file, if i decide to go back to the standard motorola 2.2.2?
http://forum.xda-developers.com/showthread.php?t=1126907
Here is the link to the official 2.2.2 UK sbf(as u r from UK)
you can use this to get back to 2.2.2 anytime you want
http://www.multiup.org/fichiers/dow...06b1_Motorola_Defy_Nu___Android_2.2_FroYo.rar
or go to above link to download you present official ROM..
Both should work fine..
All the best
Hey guys, I was thinking of installing cm7 on my motorola defy but the problem is that its a t-mobile uk version that has been unlocked using an unlock code. Right now I can use any sim with this phone but after installing cm7 will the phone lock itself back to t-mo? I don't have the unlock code for this phone so it would be really disastrous for me if it were to lock itself. should I be worried?
I found a tutorial here that un brands the motorola defy, does that mean the phone would be unlocked? My phone is currently running android 2.2.2 official uk build with baseband epu_93_00.59.02 kernel version 2.6.32.9 and build number jorem_u3_3.4.2_179-6.1.
Any help would be appreciated. Thanks!
Sent from my MB525 using XDA
Yes it should be safe.
I haven't done it myself, but here's why I say so:
1- during the process of updating to a custom rom, everyone should create a full nandroid backup of their current stock rom right after installing 2nd-Init. That way, if things don't work out with custom rom [or for warranty purposes] one can easily return to that original setup with a nand restore [and un-rooting];
2- there is a thread regarding sim unlocking the Defy here: http://forum.xda-developers.com/showthread.php?p=22227859 but I bet you will not even have to deal with it...But if you do, it's there for you and you'll find help from others users I'm sure.
Don't waste anymore time and give a shot at CM7; I'm sure that you'll never go back to stock rom afterwards ;-)
Cheers
Ok one last question. My baseband is greater than the version listed on that thread. It is .02 and I have heard that downgrading your baseband is usually not safe?
Sent from my MB525 using XDA
that shouldn't be a problem either.
In fact, Maniac103 just recently changed the way we set baseband on cm7; no more dedicated apk.. it's now all done through Device Settings.
If you're still worried [and To be on the safe side, in addition the the nand backup before installing a custom rom], also make a copy of this whole folder (current radio files) from your stock rom:
system/etc/motorola/bp_mvn_default
so that you can revert to them (make a flashable zip w them) if needed.
Anyhow, no big risk involved if you do it that way.
Good luck and have fun.
Thank You for your help!
as far as I know unlock is retained no matter what rom u are on...
not 100% sure...
let us know how this works out...
Sent from my MB526 using xda premium
SBFs on Motorola Defy
I read the Motorola Defy beginners guide but I don't understand some stuff. I am already on the latest SBF deployed by T-Mobile UK i.e JOREM_U3_3.4.2_179-6.1 as shown in settings Build Number. When we install Custom ROMs lets say CM7, do these ROMs change the SBF? If yes, then how do I know if it is a Fixed SBF or a Full SBF? If I want to come back to the official build of which I would be making a backup in case I need to get warranty (I still have 6 months of warranty) then do I need to again install the Full SBF taken from the link Zephyrot posted?
If CM7 does not modify or change the SBF then I think I would be pretty much safe in just restoring the official 2.2.2 froyo build without worrying much about SBFs, unroot the phone using SuperOneClick and taking it back to the service center. Right?
And lastly I have the SOC Defy, checked it using CatLog. Does the stable build downloaded from the CynaogenMod website of CM7 work OOB? Zephyrot suggested that sometimes you need to do additional stuff for everything to work correctly.
To go back to stock state, there are two options: 1) you restore a nand backup and like you said, you have to remove SU and unroot. This ain't so easy to do, but is sometimes the only option for people not having their stock sbf available. 2) access STOCK recovery and wipe everything and then flash their stock sbf.
Once rooted and 2nd init installed, I still recommend to create a nand backup of your stock/current state before using a custom rom anyway.
Could be useful if you ever need to go back (outside warranty) to stock rom with all your apps still installed...
Sbf is stock firmware; custom rom replace and build upon that software. I think you meant kernel? But anyhow, I suggest you to first go with ghe latest Maniac103 latest build as it includes boot.img and devtree; no need for anything else and it is rock solid and lightning fast.
Get it here: https://github.com/maniac103/android_device_motorola_jordan/downloads#download_187690
It works superbly
Thanks guys, everything works superbly. The phone didn't lock and it feels like a dead man has been given a life back again!
Hello,
I would like to create a full stock backup, I do not care for applications or settings, the only thing I want is full non-rooter, current Gingerbread with ability to install possible upcoming OTA updates.
The reason for this is simple, I want to try out different ICS roms just for fun and then go back to original, HTC Sense 2.1 powered rom.
The question is: How do I do that? I know I can handle rooting the device and installing various things but how do I get back?
Thanks!
PS A link with instructions on how to do that would be nice, I tried searching the forums and Google but nothing legit came out.
If you have already rooted your phone and installed a recovery such as ClockworkMod or 4EXT, reboot into recovery and go to the "Backup" menu and make a full backup.
In the event of problems, you can do a full wipe or factory reset, and then go to the same backup/restore menu to restore your backup from the SD card.
But if the phone is Gingerbread (it is) I have to downgrade first, correct? To Froyo 2.2. So Basically that leaves me with a copy of 2.2 while my phone came with Gingerbread in the first place.
It basically shows that I've changed (downgraded) the software, doesn't it?
stranded.eu said:
But if the phone is Gingerbread (it is) I have to downgrade first, correct? To Froyo 2.2. So Basically that leaves me with a copy of 2.2 while my phone came with Gingerbread in the first place.
It basically shows that I've changed (downgraded) the software, doesn't it?
Click to expand...
Click to collapse
If you have ALREADY rooted it, then there is no need to be downgrading back to an exploitable firmware when you've already exploited the phone. If all you're doing is installing a custom rom on an already rooted/unlocked phone then you need only flash the roms via recovery.
You would only have to downgrade the firmware if you for some reason decided to flash the original stock firmware, hboot, etc onto the phone.
But that's least as far as the backups go.
In terms of how to get the phone back to non-root/locked state there's a sticky/wiki for that, though I would find it to be a pain in the butt to have the phone rooted and unlocked and then have to go thru the process of locking it back up only to possibly risk bricking it. The more times you mess with the firmware/radio/hboot the more likely you are to brick it.
Just to make it all clear my phone is kinda new, was never rooted, that's why I'm asking. I still can't believe that HTC doesn't have an app like Xperia has, SEUS to be exact, you can fix any phone with one click. By saying fix I mean install the latest, official rom.
That's too bad there is no other way to root Desire Z.
stranded.eu said:
Just to make it all clear my phone is kinda new, was never rooted, that's why I'm asking. I still can't believe that HTC doesn't have an app like Xperia has, SEUS to be exact, you can fix any phone with one click. By saying fix I mean install the latest, official rom.
Click to expand...
Click to collapse
If never rooted there's not much of a way to make a full backup first (since most backup tools like Titanium Backup requires root).
That's too bad there is no other way to root Desire Z.
Click to expand...
Click to collapse
Well there is the HTCDev unlocker from HTC themselves, but you actually have better luck following something like cyanogenmod's wiki entry.
Something like this works quite well : http://wiki.cyanogenmod.com/wiki/HTC_Vision
You just need to make sure to triple-check all the numbers and messages, someone accidentally skipping 2 or 3 steps multiple times is just asking for problems.
But once rooted (like for my G2 I followed the cyanogenmod steps, and then went another step by upgrading my radio to the latest, I just went with a different rom after being rooted) it's usually best to keep it that way even if you decide to just flash the stock rom (i.e.: still rooted and unlocked, but simply using the original software they provide you, which can be rooted simply by having the su binary and superuser app).
The voiding of warranty usually applies to software, i.e.: you bricked the phone as a result of flashing the wrong hboot. Where as if the screen or eMMC dies, it's a hardware failure and shouldn't be voided simply because the phone was rooted (unless of course they determined you fried your CPU by running the phone at 1.9Ghz constantly).
You could just download a full version of the G2 gingerbread rom from shipped-roms.com and flash that if you ever want/need to go back to stock gingerbread.
-Nipqer
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.