I'm on Supercharged HATKA, Unlocked, Rooted, etc. I know the new update has a new radio. I have my original unlock .binn token backed up. What is the verified, safe way to flash the new radio and still be unlocked, etc? Or should just take a wait and see approach for now?
Thanks
keever25 said:
I'm on Supercharged HATKA, Unlocked, Rooted, etc. I know the new update has a new radio. I have my original unlock .binn token backed up. What is the verified, safe way to flash the new radio and still be unlocked, etc? Or should just take a wait and see approach for now?
Thanks
Click to expand...
Click to collapse
as far as flashing radio goes you cant5 unless your s-off and to obtain this you have to spent a great deal of money and send your phone off for a week or so just flash the stock rooted update
Here's the new Stock OTA 2.04.605.2 710RD rooted ROM.
Flash from recovery to install.
Devs can use also, just credit.
If wifi don't work, or won't boot, flash boot.img.
http://www.androidfilehost.com/?fid=9390288116658474610
Click to expand...
Click to collapse
Related
So I started with an official 2.2.2 firmware from Bell. I think this thread might serve 2 purposes, because I had a really hard time figure out all the steps from start to finish as they were in separate threads. So if someone starts off with stock 2.2.2 and wants to get a custom rom, that's the way I manged to do it. Second purpose of this post is for me to find out how I could return my Bell Atrix to stock OTA and what it would imply. Thanks a lot in advance for your inputs.
-I rooted with SuperOneClick
-Unlocked BL with
http://forum.xda-developers.com/showthread.php?t=1136261
-Installed Tenfar's CWM
http://forum.xda-developers.com/showthread.php?t=1138541
-Verified which kernel to use D00 or 1100 and dled it:
http://forum.xda-developers.com/showthread.php?t=1169409
-Then I flashed Alien Rom Build #2 with Tenfar's CWM:
http://forum.xda-developers.com/showthread.php?t=1186537&highlight=bell
-Then tried to do the D00 Intl kernel in CWM without rebooting, that didn't work ... so I rebooted and went directly to fastboot and installed the kernel as the instructions say in the link:
http://forum.xda-developers.com/showthread.php?t=1169409
-Then booted for the first time, rebooted, and flashed the ninja theme in CWM
What I want to know is if ever I wanted to go back to stock with the new GB OTA from Bell 0.37.23 what would it imply:
-Rooting is still available, but is unlocking ? and could I still unlock the APN menu.
-My BL would get relocked? What would that imply for future updates.
Also if I decided to take that route; I would
1) http://forum.xda-developers.com/showthread.php?p=15975211#post15975211
2) Download the new OTA and install
3) Root and unlock...
Thank you for you input,
NiK
You just install the gobstopper. There is no new bell gb OTA from my understanding. Only the new ATT gb ota.
The gobstopper puts you on full 2.2.2.
Thought the latest OTA was for GB .. oh well ... what you be the implications of going back to stock ... would that affect the unlocked BL, would it relock it, would it make future mods more difficult of impossible .... I come from iPhone world so updating a firmware would have a lot of future implications ...
yes gobstopper would put you back to stock 2.2.2 and re-lock the bootloader...so yes you would have a boring ass atrix again...the only time (personal opinion) i would ever revert back is for warranty purposes. This way they can't tell you f'ed with your phone.
and yes it would make future mods impossible....basically all the mods and stuff out there right now would be useless to you...in fact if you did want to mod your phone you would only be able to deodex and theme..with a few other tiny modifications...that aren't even supported by the dev' who made them anymore because everyone is using GB now lol...i'm not sure why anyone would want to go back except for warranty purposes or they are selling to someone who is new to android and doesn't want to hack their phone...
/rant
cheers bro =)
J-Roc said:
yes gobstopper would put you back to stock 2.2.2 and re-lock the bootloader...so yes you would have a boring ass atrix again...the only time (personal opinion) i would ever revert back is for warranty purposes. This way they can't tell you f'ed with your phone.
and yes it would make future mods impossible....basically all the mods and stuff out there right now would be useless to you...in fact if you did want to mod your phone you would only be able to deodex and theme..with a few other tiny modifications...that aren't even supported by the dev' who made them anymore because everyone is using GB now lol...i'm not sure why anyone would want to go back except for warranty purposes or they are selling to someone who is new to android and doesn't want to hack their phone...
/rant
cheers bro =)
Click to expand...
Click to collapse
Hi,
That is incorrect. Once you are unlocked, you are always unlocked. You either have a bootloader that knows what unlocked means or you don't.
In this case you can always go back to IHOP to be unlocked. There is no permanent relock.
The point in going back to stock is to get OTA updates from Bell, not warranty claims because if you can get back to stock you don't need a warranty. It's when your phone is locked up that you want to use your warranty and by then it's too late.
Cheers!
Ok so once the bootloader has been unlocked, whatever happens I can't relock it even when applying an OTA upgrade that upgrades the bootloader ? That sounds like the exact opposite of what happened with iPhones or PS3s or whatever electronics that needed to be jailbroken, unlocked of whatever.
NiKTaMeR said:
Ok so once the bootloader has been unlocked, whatever happens I can't relock it even when applying an OTA upgrade that upgrades the bootloader ? That sounds like the exact opposite of what happened with iPhones or PS3s or whatever electronics that needed to be jailbroken, unlocked of whatever.
Click to expand...
Click to collapse
A fuse gets blown in this case. oem lock does nothing.
What you can do is install a bootloader that doesn't know about unlocking or that that paticular fuse means it's supposed to be unlocked, So the unlocked message doesn't show up on the main screen during boot and fastboot no longer works for signed partitions. However, restoring the unlocked bootloader restores the unlock by checking the blown fuse, and oem unlock no longer has to be done.
Cheers!
Thanks a lot to everyone for your replies.
P.S NF I'm waiting to try your gobstopper 2.3.4 stupid slow upload speeds
NiKTaMeR said:
Thanks a lot to everyone for your replies.
P.S NF I'm waiting to try your gobstopper 2.3.4 stupid slow upload speeds
Click to expand...
Click to collapse
It's done if you were waiting.
Sent from my MB860 using XDA Premium App
I need a little help. I unlocked the bootloader, rooted my phone, made TWRP my recovery, and got s-off. I did not flash a custom ROM. Now though, there is an update for my phone. I want to update it to the latest via OTA and remain on the stock ROM until 4.2.2 comes out. It is my understanding that I may need to run an RUU since I have TWRP as my recovery. This is where I'm a little confused.
1) Which RUU do I select? (I currently have the stock T-Mobile US build version 1.27.531.7 CL170484 release-keys if that helps)
2) Afterr I flash the RUU, do I need to perform s -on and re-lock the bootloader prior to performing the OTA update?
3) Am I missing any major steps?
4) Would it be better to just use a custom ROM like Android Revolution rather than trying to revert back to stock, etc?
Thanks for any and all input.
bloodbath said:
I need a little help. I unlocked the bootloader, rooted my phone, made TWRP my recovery, and got s-off. I did not flash a custom ROM. Now though, there is an update for my phone. I want to update it to the latest via OTA and remain on the stock ROM until 4.2.2 comes out. It is my understanding that I may need to run an RUU since I have TWRP as my recovery. This is where I'm a little confused.
1) Which RUU do I select? (I currently have the stock T-Mobile US build version 1.27.531.7 CL170484 release-keys if that helps)
2) Afterr I flash the RUU, do I need to perform s -on and re-lock the bootloader prior to performing the OTA update?
3) Am I missing any major steps?
4) Would it be better to just use a custom ROM like Android Revolution rather than trying to revert back to stock, etc?
Thanks for any and all input.
Click to expand...
Click to collapse
you need to flash the original recovery to install ota updates,, you will lose root access doing so
Or wait until some package it into a ZIP file and flash using TWRP.
Right?
Just wait a week.
All you need to do is put the stock Tmo recovery on your one. Then go update with ota and you will still be unlocked but you do lose root.
So it seems like there is disagreement to whether the stock ROM causes you to lose root or not. Either way, I would need to "lock" the bootloader again right?
Does the update add anything really worth having? I'm thinking that ARHD would be the best bet until an RUU comes out.
bloodbath said:
So it seems like there is disagreement to whether the stock ROM causes you to lose root or not. Either way, I would need to "lock" the bootloader again right?
Does the update add anything really worth having? I'm thinking that ARHD would be the best bet until an RUU comes out.
Click to expand...
Click to collapse
I'm sorry I was wrong you will lose root after you update ota. But you can do ota while being unlocked so no need to relock bootloader just flash the stock Tmo recovery and update.
chong67 said:
Or wait until some package it into a ZIP file and flash using TWRP.
Right?
Just wait a week.
Click to expand...
Click to collapse
U mean something like this!? https://copy.com/aSLnP
Team-Noctural.com/androidtechy.com/droidnow.com
I'm aware of the OTA update next week that'll update me to Sense 6.
Currently displays in recovery:
Tampered
Unlocked
S-OFF
Currently on stock 4.4.2 rooted, no other kernel changes, etc. but the ROM I'm using has custom black boot screens added (literally just black instead of default white boot background).
Rooting is nice and all but getting tired and would just like to revert to pretty much locked bootloader, unrooted, factory condition, etc. and be able to also do OTA for future updates.
Any help is appreciated. Baby steps please.
Anyone?
First, relock your bootloader. To do that, start your phone in bootloader mode, connect your phone to pc via usb cable and type "fastboot oem lock" on command prompt. Next, download the proper ruu exe file from htc1guru.com. By proper,I mean the one that matches your phones actual model number and custom id. Execute the ruu while connecting your phone to pc in fastboot mode. Follow the on screen instructions and when finished, you will have s phone that says re locked and s-off. You will get ota in this condition and will be able to install ota and upgrade to Sense 6.0 without any problems.
http://forum.xda-developers.com/showthread.php?t=2695749
Can I just flash that RUU in the link above? It should take me back to stock 4.4.2 with no modifications, stock recovery, and since I have an unlocked bootloader + S-OFF I should be able to get OTA's.
I'm just getting replies and finding info in other threads with different methods so I just don't want to screw up anything.
SaHiLzZ said:
If you are only rooted with stock ATT software, unroot using the SuperSU app, make sure you have stock recovery, and you are golden. DO NOT turn S-ON, and also no need to lock bootloader, as with S-OFF, you will get updates with unlocked bootloader
Click to expand...
Click to collapse
I'm running stock AT&T 4.4.2 but the person who uploaded the ROM used a custom black boot screen (black HTC background instead of white when the phone boots) and so I was worried that might affect things. Hence I thought I could just flash an RUU to go back to 100% stock AT&T 4.4.2 (+ unroot) and maintaining unlocked bootloader + S-OFF so I can OTA.
EDIT: Could I just convert it to a Developer Edition using the link in your signature? Will there be any problems with my AT&T SIM card? All I have to do is relock bootloader and flash the Dev. Edition ROM.
Yes you can flash the decrypted ruu. It is the same as using the ruu exe.
If you haven't changed your mid and/cid,then what you need to is just lock the bootloader and flash the ruu (zip or exe). You will be on stock with s-off which is fine for getting ota.
Yes you can convert to developer edition. The DE and the at&t version are the same hardware-wise (except DE have 64gb storage instead of 32gb on at&t version) and have the same radio bands. You will get faster Android upgrades with no at&t bloats.
mch277 said:
http://forum.xda-developers.com/showthread.php?t=2695749
Can I just flash that RUU in the link above? It should take me back to stock 4.4.2 with no modifications, stock recovery, and since I have an unlocked bootloader + S-OFF I should be able to get OTA's.
I'm just getting replies and finding info in other threads with different methods so I just don't want to screw up anything.
I'm running stock AT&T 4.4.2 but the person who uploaded the ROM used a custom black boot screen (black HTC background instead of white when the phone boots) and so I was worried that might affect things. Hence I thought I could just flash an RUU to go back to 100% stock AT&T 4.4.2 (+ unroot) and maintaining unlocked bootloader + S-OFF so I can OTA.
EDIT: Could I just convert it to a Developer Edition using the link in your signature? Will there be any problems with my AT&T SIM card? All I have to do is relock bootloader and flash the Dev. Edition ROM.
Click to expand...
Click to collapse
You may want to just try and apply the OTA when released. I'm not aware that S-OFF is a problem, I know an unlocked bootloader nor rooted isn't an issue. I got the Rogers OTA with an unlocked bootloader a rooted (by the way was still rooted after the OTA)
Just my 0.02
mb_guy said:
You may want to just try and apply the OTA when released. I'm not aware that S-OFF is a problem, I know an unlocked bootloader nor rooted isn't an issue. I got the Rogers OTA with an unlocked bootloader a rooted (by the way was still rooted after the OTA)
Just my 0.02
Click to expand...
Click to collapse
My understanding is that, if there's any modification in system files, applying OTA may result in a bootloop/brick. I agree that rooted devices remain rooted after OTA. As the OP said that s/he us using a rom with modified boot animation, I suggested him/her to return to stock first.
(SOLVED)
Im in stock 4.1.2 whit S-OFF, unlocked bootloader (1.55) and then RELOCKED.
¿Can i take the last OTA?
Im not rooted, and i dont have custom recoverys (i recently flashed a RUU.zip to return to stock, but i could not remove the S-OFF and RELOCKED status because the hboot 1.55).
I have economic (health) problems and I'll really need to sell my phone, but I'm afraid that the new owner will come out error when trying to update.
conquesoextra said:
Im in stock 4.1.2 whit S-OFF, unlocked bootloader (1.55) and then RELOCKED.
¿Can i take the last OTA?
Im not rooted, and i dont have custom recoverys (i recently flashed a RUU.zip to return to stock, but i could not remove the S-OFF and RELOCKED status because the hboot 1.55).
I have economic (health) problems and I'll really need to sell my phone, but I'm afraid that the new owner will come out error when trying to update.
Click to expand...
Click to collapse
Yes. You can get OTAs while S-OFF. And assuming you haven't unlocked the bootloader since flashing the RUU, all the system files it verifies should be in place to accept OTAs. However, considering you are currently on 4.1.2, you'll need to run through a progression of OTAs to get up to the latest version, 4.4.2 w/ Sense 6. Might be better to just run the latest RUU to bring it up to 4.4.2 w/ Sense 5.5 then OTA to Sense 6. Be aware that you'll need to be on the AT&T network in order to get the updates OTA. If you're not on AT&T, you'll need to flash the updates manually, in which case you'll need to be S_OFF.
Also, once the phone is S-OFF there is no good reason to change that back to S-ON. There's the potential of bricking the phone by doing so. And even if it doesn't brick, the updates in firmware may make it more difficult to obtain S-OFF again.
Thank you very much.
At the begining i did this:
1- Unlocked bootloader and flashed TWRP.
2- Root
3- Gained S-Off
When i decide to sell it i did this:
1- Removed xposed and root.
2 - Relocked bootloader.
3 - Flashed RUU.zip (4.1.2)
¿What do you mean whit AT&T network? I unlocked the phone vía imei (using it in mexico whit Telcel) and still have the update appearing.
Sorry for my terrible english
conquesoextra said:
Thank you very much.
At the begining i did this:
1- Unlocked bootloader and flashed TWRP.
2- Root
3- Gained S-Off
When i decide to sell it i did this:
1- Removed xposed and root.
2 - Relocked bootloader.
3 - Flashed RUU.zip (4.1.2)
¿What do you mean whit AT&T network? I unlocked the phone vía imei (using it in mexico whit Telcel) and still have the update appearing.
Sorry for my terrible english
Click to expand...
Click to collapse
First off, since you are S-OFF there is no need to relock the bootloader in order to flash an RUU. It will run just fine with an unlocked bootloader. Also when you flash an RUU, all the partitions get wiped so there is no need to do anything within the ROM such as remove xposed & root prior to flashing. The RUU will set the device essentially in a factory state.
As far as I understand it, the OTAs for carrier specific devices are served up by the carrier. So if the phone has been SIM unlocked and is being used on another network, if you go into Settings>AT&T software update, it will not receive any available OTA update. You will need to flash the update file manually using the information in this thread, http://forum.xda-developers.com/showthread.php?t=2659374.
Since you are still on 4.1.2, you will need to run one of the recent RUUs in order to manually flash the OTA updates in that thread. The latest RUU available for AT&T devices is KK4.4.2 w/Sense 5.5.
http://androidruu.com/getdownload.p...09_10.26.1718.01L_release_356565_signed_2.exe
Flash that then you can manually flash the OTA update to get Sense 6.
You are the man.
THANK YOU SO MUCH!
Ok, i am on ATT 4.4.2 with unlocked bootloader/S-OFF/Rooted/TWRP
i am still on stock rom, if i do the update, will my phone still be S-OFF (firewatered) and will i be able to unlock the bootloader?
Youll need stock recovery regardless to accept an OTA,unlocked and s-off is fine,to be safe I would unroot before taking any OTA, some say its not necessary but I dont leave things up to chance
Bradl79 said:
Ok, i am on ATT 4.4.2 with unlocked bootloader/S-OFF/Rooted/TWRP
i am still on stock rom, if i do the update, will my phone still be S-OFF (firewatered) and will i be able to unlock the bootloader?
Click to expand...
Click to collapse