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.
Related
I'm under the impression this is what I have to do. Please tell me if they're wrong.
Why I want to "root" my Inspire 4G:
Get rid of bloatware.
To increase the usability of the phone, such as better battery life.
To root stock Inspire ROM:
Follow bubby323's guide.
This will downgrade the phone, use an exploit to activate superuser status ("root"), and upgrade back to stock ROM.
Potential Issues with Above:
Superuser force-closing- Update the ROM image.
ClockWorkMod shows blank screen-Update it to 3.0.0.6+.
Phone will not boot past bootloader-Reinstall the stock rooted ROM.
"Model ID Incorrect"-Bad GoldCard.
Done.
Installing custom ROM- (optional)
Replace the stock rooted Inspire ROM to Gingerbread ROM:
Install Rom Manager, and download RCMix. Put the ROM on the microSD card, and install using Rom Manager.
Flash the Radio:
Follow pollux1151's directions.
Done.
To return back to Stock:
Run bubby323's S-On Tool. Afterwards, run the RUU exe file, with the phone NOT in USB debug mode.
Done.
To reiterate, the above steps are what I need to do... correct?
Also, what's the difference between the rooted stock Inspire ROM (e.g. essentially stock with superuser access) and the RCMix Gingerbread? Doesn't really say much in that topic...
Printerscape said:
I'm under the impression this is what I have to do. Please tell me if they're wrong.
Why I want to "root" my Inspire 4G:
Get rid of bloatware.
To increase the usability of the phone, such as better battery life.
To root stock Inspire ROM:
Follow bubby323's guide.
This will downgrade the phone, use an exploit to activate superuser status ("root"), and upgrade back to stock ROM.
Potential Issues with Above:
Superuser force-closing- Update the ROM image.
ClockWorkMod shows blank screen-Update it to 3.0.0.6+.
Phone will not boot past bootloader-Reinstall the stock rooted ROM.
"Model ID Incorrect"-Bad GoldCard.
Done.
Installing custom ROM- (optional)
Replace the stock rooted Inspire ROM to Gingerbread ROM:
Install Rom Manager, and download RCMix. Put the ROM on the microSD card, and install using Rom Manager.
Flash the Radio:
Follow pollux1151's directions.
Done.
To return back to Stock:
Run bubby323's S-On Tool. Afterwards, run the RUU exe file, with the phone NOT in USB debug mode.
Done.
To reiterate, the above steps are what I need to do... correct?
Also, what's the difference between the rooted stock Inspire ROM (e.g. essentially stock with superuser access) and the RCMix Gingerbread? Doesn't really say much in that topic...
Click to expand...
Click to collapse
Go to the second page theme is a guide. To root all you have to do is follow instructions. The stock ROM it installs already has super user and cwm. You don't really install the custom ROM. You wipe that partition and flash a new ROM over it. When it come to s-on you are going to need to have the free file on your SD card from when you rooted the phone. Then just run the ruu from tour computwr. I am not sure what you mean by done.
The s-on doesn't always work, and the guide has a fix for the cwm black screen.
Are you planning on returning to stock right after rooting, that's a lot of work to end up with what you started out with.
The difference is a stock rooted from is just that no kernel mode or anything just stock rooted froyo. The ginger bread roms are ported from the desire hd and desire s. They have been cooked and modded to he zip aligned and deodexed, and to improve on performance.
Sent from Hey... This isn't where I parked my car.
mudknot2005 said:
Go to the second page theme is a guide. To root all you have to do is follow instructions. The stock ROM it installs already has super user and cwm. You don't really install the custom ROM. You wipe that partition and flash a new ROM over it. When it come to s-on you are going to need to have the free file on your SD card from when you rooted the phone. Then just run the ruu from tour computwr. I am not sure what you mean by done.
Click to expand...
Click to collapse
Yes, I stripped from the guide.
By "done", I mean that procedure is done (for example "To root stock Inspire ROM:" blah blah blah, "Done". The Inspire is rooted).
Also, must I flash the radio? What does that even mean...? Can I just not flash the radio...?
The radio isn't required, only recommended. Some people depending on where they live have better reception or battery life. The radio.img is essentially a firmware upgrade for your radio.
Sent from Hey... This isn't where I parked my car.
This is probably is super simple question but, I want to Flash my Thunderbolt with CM7 RC 1.1 (MR2.5 radio version) and flash the MR2.5 radio. Which one do I flash first?
THANK YOU!
I'm not a dev but i have flashed a few different radios when I installed a custom Rom. So far (and maybe it's just me) but I have installed the rom and let it load up and get going and everything. Then skip through all the setup and when it is finished I reboot into recovery and flash the radio afterward.
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.
Several months ago I purchased a NS4G on Craigslist. I wanted to use it as an iPod touch without the data. It came rooted with SuperUser. The phone keeps prompting me to OTA to 2.3.7 (it's currently on 2.3.5) I used Gingerbreak to unroot and it worked, SuperUser is now gone. However, ClockWorkMod Recovery is still present and 2.3.7 won't install. The phone reboots, goes to about 1/3 of the progress bar, and then fails. I just want to get the phone on completely stock 2.3.7, in preparation for the coming 4.0 OTA.
Hopefully the solution doesn't involve flashing a custom ROM, I've never done that before. Thanks!!
No need to get it OTA, you can just flash the stock ICS ROM found in the stickies of the development forum of this phone. Of course follow instructions closely.
Sent from my Nexus S using xda premium
But I'm selling it and need it to be completely 100% original and stock, which is what the buyer requested..
You want to use fastboot to flash a stock recovery. Peter Alfonso has them all listed on his site.
Thanks. I'm really not familiar with fastboot, and is there any way you could give me a link with instructions or the files I need? My build number is GRJ90.
And if there's anyway for me to avoid a rooted stock ROM, that'd be great. Just pure stock 2.3.7.
The stock image on Rom manager has the recovery bootloader included.
Flash a stock gb rom from cwm. You will find a list of them in either general or android development threads, not sure which. Completely stock, unrooted and as far as I remember the stock recovery is included. If not then the person will never know anyway as if someone doesn't want any non stock features then they won't know how to get to recovery anyway.
Actually I don't think they have stock recovery. Just flash the stock rom and then fastboot flash the stock recovery like was mentioned above. All you need to type is:
Fastboot flash recovery xxxxx.img
Xxxxx.img is the name of the image file you download.
Don't cheat the buyer...Tell him exactly what he's buying...And that you returned thedevice back to stock again.It's just not worth it.
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.