Hi..just wanted some help with clarification on a few things. I upgraded the firmware to the one needed to install the ICS ROMs, but have reverted back to my original stock ROM using a NAND restore.
However, I noticed the radio and the HBOOT is still with the newer firmware one. So does NAND restore not restore them to the original? (the NAND was done before upgraded to the newer firmware).
Also, if I want to go back to the previous radio that was already on the phone. How can I do that? Do I use the RUU file? Will that restore everything back? And will I lose root?
Thanks for your help.
newr said:
Hi..just wanted some help with clarification on a few things. I upgraded the firmware to the one needed to install the ICS ROMs, but have reverted back to my original stock ROM using a NAND restore.
However, I noticed the radio and the HBOOT is still with the newer firmware one. So does NAND restore not restore them to the original? (the NAND was done before upgraded to the newer firmware).
Also, if I want to go back to the previous radio that was already on the phone. How can I do that? Do I use the RUU file? Will that restore everything back? And will I lose root?
Thanks for your help.
Click to expand...
Click to collapse
Why do you want previous FW, if current one most likely work perfectly?
Nandroid only restores/backsup /system, /cache, /data, /boot (kernel), and /recovery. It doesn't touch radio, boot, or any other firmware stuff.
Sent from my HTC Sensation
I am not sure if it's the problem with it, but it seems the battery is draining very fast after I upgraded to this new firmware for the ICS and not back on gingerbread. That's why I want to restore a previous radio etc..
Actually, I mainly want the firmware that was released for the lastest gingerbread (i.e. t-mobile update in Dec). I had flashed the firmware before...after that flashed the other one for the ICS. Can I just reflashed the previous version of it?
Does RUU restore the radio back? and does it keep root?
I am not sure if it's the problem with it, but it seems the battery is draining very fast after I upgraded to this new firmware for the ICS and not back on gingerbread. That's why I want to restore a previous radio etc..
Actually, I mainly want the firmware that was released for the lastest gingerbread (i.e. t-mobile update in Dec). I had flashed the firmware before...after that flashed the other one for the ICS. Can I just reflashed the previous version of it?
Does RUU restore the radio back? and does it keep root?
RUU restores everything back, and i mean everything. And root, it'll be gone, but easy to gain again. You might need to superCID to be able to downgrade hboot (to flash earlier version which is in the latest t-mobile ruu)
tinky1 said:
RUU restores everything back, and i mean everything. And root, it'll be gone, but easy to gain again. You might need to superCID to be able to downgrade hboot (to flash earlier version which is in the latest t-mobile ruu)
Click to expand...
Click to collapse
Oh I see..so RUU files brings restores back to original.
I have super CID and everything root etc.. how about just flashing the PMG file that was for the update back in Dec for TMOUS? I just want to see getting rid of this new radio will make a difference.
Related
At the end of the "effen manual" in ace's hack kit, it shows you how to reflash the stock radio and rom, probably in case you ever need to send the phone back for insurance purposes. My question is...do I need to reflash the stock radio if I intend to use the stock radio with a custom rom or will the stock radio still be in tact after rooting, downgrading the rom, etc...
In other words, does ace's hack kit affect the stock radio?
Yes. As part of the downgrade step, the radio is also replaced by the one in the downgrade package.
Thank you.
I will reflash the stock radio and then flash a custom rom. It doesn't matter which order I perform those two steps in...or does it?
if your going to flash a custom rom, go ahead and wait to flash the radio, until you flash the custom rom, then you can flash the recommended radio for the rom.
Like said above because sometimes the roms will run just as good with one radio as they do with another. I did though when I used the kit.... can't really go wrong with either one you can always change it later.
Sent from my Inspire 4G using XDA App
The first rom I flashed after I rooted with the Hack-Kit was the rooted stock rom with the OTA update in PD98IMG.zip form (http://forum.xda-developers.com/showthread.php?t=1058042). Because it has the OTAed stock radio with the rooted stock rom in it so everything is done in one step (installed from HBoot). After that you can flash any rom of your choice from recovery and you get to keep the OTAed stock radio.
Is there a guide to getting back to GB from the ICS roms?
I would like to try ICS, but want a way to get back!
I just did a revert back to GB.
Just superwipe and install the GB rom
Worked just fine on Coredroid. Should work on others. Did not change and firmware
Does the 3.24 firmware work with GB then?
GavChap said:
Does the 3.24 firmware work with GB then?
Click to expand...
Click to collapse
I read somewhere, that it does not....thats why i myself have not upgraded the FW
GavChap said:
Does the 3.24 firmware work with GB then?
Click to expand...
Click to collapse
It does not, it will cause bootloops. To flash a gingerbread ROM, first transfer the 3.12 firmware and ROM to your SD-card. Then reboot directly into recovery and flash the room, then reboot into the bootloader and flash the firmware.
also not that for most current ics roms you need the current 3.24 firmware so if you want gb you just have to downgrade your firmward i believe
I was on the latest ARHD and whatever FW that required and just wiped and installed Coredroid 3.2
The 3.12... firmware works with both ICS and GB roms. I switch between Nandroid backups of both with this firmware, because I have found that while ICS roms have made great strides they still have issues (freezes, reboots), while GB is problem free.
LBN1 said:
The 3.12... firmware works with both ICS and GB roms. I switch between Nandroid backups of both with this firmware, because I have found that while ICS roms have made great strides they still have issues (freezes, reboots), while GB is problem free.
Click to expand...
Click to collapse
I get md5 mismatch when restoring a backup. any ideas?
I just installed 1.17 bootloader back without changing the radio and it did well.
dmcb123 said:
I get md5 mismatch when restoring a backup. any ideas?
Click to expand...
Click to collapse
did you rename the backup? if so take out whatever spaces you have in there. that will cause the mismatch
Hey guys,
I searched around and only found some old posts for this topic.
I just bought this phone, I rooted it, simunlocked it, and added two day old CWM recovery. Its a S4 Canadian (Bell) version in case that helps..
Is there a way to apply the OTA update WITHOUT having to wipe my data and settings and reflashing a rom?
Hlep will be greatly appreciated!
THANKS :good:
I got the same thing going on. I have a TMOUS HTC One S stock with CWM Rooted and such. I just changed it back to the Stock recovery, but doesn't seem to help. Is there something else I need to do? Maybe I need to flash a newer recovery version?
I have the stock recovery from a MoDaCo topic I can't list because I don't have 10 posts yet.
its topic/353006-interim-clockworkmod-touch-recovery-for-the-htc-one-s-stock-download/ though.
Are you sure your Rom is absolutely stock. For example if the rom is tweaked in any way or if bloatware has been deleted then you won't recieve the update
Ok so I got the update to work. This is what I did: in CWM I backed up a nandroid. I flashed a stock BACKUP for the HTC One S (I moved the zip to the clockwork > backups folder on the sd card). Rebooted into bootloader, flashed a stock recovery from modaco, rebooted, ran the update (I had to update twice, from 1.53 to 1.84 to 2.35). Then I restored my original nandroid. Problem is, the update didn't stick. And now I'm getting an error when I try to turn on wifi. Any ideas? I feel like I got so close...
Tough to see what went wrong.
I had a brand new stock rom with no modifications.
Then I flashed stock recovery,
Did a root keeper (play store app)
Then did the update
And restored root.
Worked out fine for me!
I think you should flash a stock rom and not a backup..
I tried out the NOX sense 5 rom and then reverted back to stock , but my wifi doesn't work at all. During the first NOX release I upgraded the radio image and I'm guessing I need to downgrade it back to the stock x920d radio to get wifi working again.
I don't suppose anyone has the stock radio image for the x920d?
Cheers in advance.
digitalmonkey said:
I tried out the NOX sense 5 rom and then reverted back to stock , but my wifi doesn't work at all. During the first NOX release I upgraded the radio image and I'm guessing I need to downgrade it back to the stock x920d radio to get wifi working again.
I don't suppose anyone has the stock radio image for the x920d?
Cheers in advance.
Click to expand...
Click to collapse
I have the same problem just now. It's because we need the stock boot.img file before we can return to stock. The problem I encountered was I restored my original ROM from TWRP backup. I tried flashing the stock boot that another user gave but it doesn't work, then I remember the KillX kernel which comes with its own boot.img file and Flashed that. Now my wifi is work but the kernel is no longer stock.
Since I can't post on the original android development thread. I'll ask here.
I'm a noob on all of these rooting and custom roming however I did manage to unlock my bootloader, flash TWRP 2.6.0.0, have root access via Superuser, S-OFF and finally flash Android 4.2.2 Sense 5-5.08.111.2 stock ROM by Turge on my ATT device running JB 3.18 (HBOOT 2.14).
I love the stock rom however I'm having problems such as signal drops throughout the day, random reboots and no signal when I wake up everyday for the past 3 days.
I know the solution is to flash Kernel and update firmware - which is explicitly stated on Turge's thread, which leads me to my questions:
1) What does firmware updating do to my device? I'm pretty clear on what happens when you flash Kernel.
2) Assuming I was able to update firmware (including HBOOT to 2.15?) and Kernel, Would I still be able to revert back before messing with them? Would creating a nandroid backup before updating and restoring that nandroid backup be able to revert them back pre update w/o issues (or bricking)?
3) Lastly, I made an original nandroid backup while still Android 3.18 w/ Sense 4 (my very first nandroid backup) before flashing Sense 5. Assuming I updated firmware and Kernel while on Sense 5, Would restoring the original nandroid backup allow me to restore back to Sense 4 w/o issues (or bricking)?
Hope someone would take time to respond! Thanks!
+1 i have same questions
You might get more responses if this was in the question thread. Mod please move this to the correct area.
Sent from my HTC One XL using xda premium
watswidme said:
Since I can't post on the original android development thread. I'll ask here.
I'm a noob on all of these rooting and custom roming however I did manage to unlock my bootloader, flash TWRP 2.6.0.0, have root access via Superuser, S-OFF and finally flash Android 4.2.2 Sense 5-5.08.111.2 stock ROM by Turge on my ATT device running JB 3.18 (HBOOT 2.14).
I love the stock rom however I'm having problems such as signal drops throughout the day, random reboots and no signal when I wake up everyday for the past 3 days.
I know the solution is to flash Kernel and update firmware - which is explicitly stated on Turge's thread, which leads me to my questions:
1) What does firmware updating do to my device? I'm pretty clear on what happens when you flash Kernel.
2) Assuming I was able to update firmware (including HBOOT to 2.15?) and Kernel, Would I still be able to revert back before messing with them? Would creating a nandroid backup before updating and restoring that nandroid backup be able to revert them back pre update w/o issues (or bricking)?
3) Lastly, I made an original nandroid backup while still Android 3.18 w/ Sense 4 (my very first nandroid backup) before flashing Sense 5. Assuming I updated firmware and Kernel while on Sense 5, Would restoring the original nandroid backup allow me to restore back to Sense 4 w/o issues (or bricking)?
Hope someone would take time to respond! Thanks!
Click to expand...
Click to collapse
1. The firmware update will update the hboot, radio, and some WiFi and media modules.
2. You can revert using the 3.18 RUU, this will return you to the 2.14 hboot, stock recovery, and stock Sense 4 ROM.
2b. A nandroid backup doesn't backup the partition that is updated by a firmware package. It only backs up the OS/data/boot partitions, so restoring a backup won't change your firmware, use the RUU as suggested above if you need to revert.
3. Restoring your backup will return you to the Sense 4 ROM. Like I mentioned above though it will not change your firmware.
You are s-off so the chance of bricking while running an RUU is minimal. There is always a small chance of bricking no matter what you're doing, whether it be flashing a ROM/kernel, changing hboot (higher risk), flashing a radio, running an RUU. With your current setup, you have no greater risk than anyone else though.
PS. Questions go in the q&a section (for future reference).
Sent from my Evita
I had the same exact issue. I did the easiest thing first - flashed the Beastmode 3.5 kernel, and thankfully that has completely fixed the issues for me. Been running with it for 4 days now and the signal has not dropped once nor have I had random reboots. I did not have to upgrade firmware.
Just a personal note... the stock settings flash did not work for me; I had to choose the custom flash and enter the stock settings. He mentions this in the install notes.
Here's the Beastmode 3.5 thread:
http://forum.xda-developers.com/showthread.php?t=2165880
Here's his post with what the stock settings should be if you need to choose the custom flash:
http://forum.xda-developers.com/showpost.php?p=45195808&postcount=251
timmaaa said:
2. You can revert using the 3.18 RUU, this will return you to the 2.14 hboot, stock recovery, and stock Sense 4 ROM.
Click to expand...
Click to collapse
This^ I was gonna ask about it in Q&A thank goodness I read this thread first. Thank you!
Sent from my HTC One X using Tapatalk 4
Timmaa - Great stuff buddy! One additional question, It sounds like I can restore my backup (made on 2.14) while my firmware is 2.15? Wouldn't this cause any trouble?
rwalterk - I will err on the side of safety and flash my Kernel first, like how you did it. My phones getting more reboots and dead signals after a week of use. If problems still continue I will update my firmware.
pjacanales - noted, questions on the questions thread.
watswidme said:
Timmaa - Great stuff buddy! One additional question, It sounds like I can restore my backup (made on 2.14) while my firmware is 2.15? Wouldn't this cause any trouble?
rwalterk - I will err on the side of safety and flash my Kernel first, like how you did it. My phones getting more reboots and dead signals after a week of use. If problems still continue I will update my firmware.
pjacanales - noted, questions on the questions thread.
Click to expand...
Click to collapse
I can't see any reason why reverting to Sense 4 wouldn't be ok on the newer firmware.
Sent from my Evita
Newbie Question.
rwalterk said:
I had the same exact issue. I did the easiest thing first - flashed the Beastmode 3.5 kernel, and thankfully that has completely fixed the issues for me. Been running with it for 4 days now and the signal has not dropped once nor have I had random reboots. I did not have to upgrade firmware.
Just a personal note... the stock settings flash did not work for me; I had to choose the custom flash and enter the stock settings. He mentions this in the install notes.
Here's the Beastmode 3.5 thread:
http://forum.xda-developers.com/showthread.php?t=2165880
Here's his post with what the stock settings should be if you need to choose the custom flash:
http://forum.xda-developers.com/showpost.php?p=45195808&postcount=251
Click to expand...
Click to collapse
Hey bro
I'm from Venezuela and I'm having the exact same problem as you guys have.
I readed your post and downloaded Beastmode 3.5 and flash it, but i got caught in a bootloop.
I'm using the VIPER 4.2.2 Rom.
Since this is not a solution for me, i was wondering which Rom are you using exactly?
Did you select custom from the Beastmode installer? He's using Turge's stock Sense 5 ROM which can be found in the development section.
Sent from my Evita
rwalterk said:
I had the same exact issue. I did the easiest thing first - flashed the Beastmode 3.5 kernel, and thankfully that has completely fixed the issues for me. Been running with it for 4 days now and the signal has not dropped once nor have I had random reboots. I did not have to upgrade firmware.
Just a personal note... the stock settings flash did not work for me; I had to choose the custom flash and enter the stock settings. He mentions this in the install notes.
Here's the Beastmode 3.5 thread:
http://forum.xda-developers.com/showthread.php?t=2165880
Here's his post with what the stock settings should be if you need to choose the custom flash:
http://forum.xda-developers.com/showpost.php?p=45195808&postcount=251
Click to expand...
Click to collapse
timmaaa said:
Did you select custom from the Beastmode installer? He's using Turge's stock Sense 5 ROM which can be found in the development section.
Sent from my Evita
Click to expand...
Click to collapse
Thank you my friend!
I downloaded Turge's ROM and install it, and actually didnt have to flash the New kernel; i used the one in the Package and it Worked! i almost sold my phone because i couldnt find a ROm taht works but, so far, its been passed one day only and i havent had any signal drop, nor battery fast draining!
Sorry for my english BTW.
Thank you once again!
PS: If u find a way to fix VIPER ROM let me know, cause i've read a lot and cant find a way to fix it, but im to shy to ask in a new post hahahahahhahahahahahahaha.
Let me know if you need my phone specs. (as bootloader version, software version etc.)
The best way to overcome the problems is to get s-off, then you're able to upgrade to the 2.15 firmware which is the best solution to signal loss and reboots on Sense 5 ROMs. In order to get s-off you'd most likely need to flash a different ROM though, I don't think a single person has had the process succeed while running a 4.2.2 ROM.
Sent from my Evita
timmaaa said:
The best way to overcome the problems is to get s-off, then you're able to upgrade to the 2.15 firmware which is the best solution to signal loss and reboots on Sense 5 ROMs. In order to get s-off you'd most likely need to flash a different ROM though, I don't think a single person has had the process succeed while running a 4.2.2 ROM.
Sent from my Evita
Click to expand...
Click to collapse
Yeah, i'm already S-OFF.
Actually, all this problems came out when i was 1.14 FW, but when i checked for the first time this post, i decided to change the FW and now i'm @ 2.15 FW, S-OFF and CID-11111111.
I haven't checked what is gonna happen if i install VIPER ROM, but in the meanwhile, i'm gonna try this ROM which runs smooth.