If I am sending my eris back to get a replacement, what software should be on it? Should I put a vzw radio on (i have a sprint radio flashed), and more importantly, what ROM should I flash, because kaosfroyo is currently installed. Is ivan's official the one to flash, or when the device is returned, should it not have root permissions. Also, on a side note, would you guys rather have a devour or ally over the eris?
-Thanks, eriscentro
Be best to just get another eris, both of them phones arnt very well at all. And there's a thread how to downgrade from root to stock in xda threads search and that will put the phone back to where you can send it back
to get phone back to original.
radio here: http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=7232088
then flash PB00IMG-21-official.zip from here: http://android.grdlock.net/index.php?&direction=0&order=&directory=PB00IMG Roms
should reset and unroot your phone
Will the unroot image prevent future rooting.
eriscentro said:
Will the unroot image prevent future rooting.
Click to expand...
Click to collapse
no sir, EVERY ERIS IS ROOTABLE via jcase's app so dont worry
eriscentro said:
If I am sending my eris back to get a replacement, what software should be on it? Should I put a vzw radio on (i have a sprint radio flashed), and more importantly, what ROM should I flash, because kaosfroyo is currently installed. Is ivan's official the one to flash, or when the device is returned, should it not have root permissions. Also, on a side note, would you guys rather have a devour or ally over the eris?
-Thanks, eriscentro
Click to expand...
Click to collapse
Do not send your phone in rooted, if you are savvy with ADB shell i can send you directions and files to push 1.5 official unrooted just like out of the box. Pm me if you need it! I found a way to push root to ANY eris, even with hboot 1.49 s-on, and how to unroot any eris.
mjb413 said:
to get phone back to original.
radio here: http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=7232088
then flash PB00IMG-21-official.zip from here: http://android.grdlock.net/index.php?&direction=0&order=&directory=PB00IMG Roms
should reset and unroot your phone
Click to expand...
Click to collapse
Good intent, but bad information.
Both of those ROMs on Grdlock's site contain kernels and other build tags which were never publicly released - note that one of them is the Root ROM (which installs an Engineering bootloader!), and the other is Leak-V2. They are easily spotted as not being "official" HTC/VZW software
The Official VZW/HTC 2.1 OTA for the Eris was essentially identical to the Leak-V3 PB00IMG.ZIP ROM
If you are going to try applying a PB00IMG.ZIP ROM, use Leak V3. As of today, if you install the Leak-V3 ROM using the HBOOT+PB00IMG.ZIP method, it will immediately update to the July 2010 (2.1 patch OTA) almost as soon as it boots up.
If a VZW sales agent or tech looks a a phone which is updated this way (Leak-V3) at
Settings -> About phone -> Software information
he/she will see information which is identical to virginal Eris'es that are up to date; if he/she looks at the bootloader, he/she will see 1.49.0000 S-ON, which is the bootloader currently shipped on most refurbs and new replacements.
Do not use the Leak-V2 ROM (or the Root ROM, but I think that should be obvious).
bftb0
By the way, would you guys rather have an ally or devour than an eris? Also, isn't the general "give em' a new device" time after three replacements, because getting a replacement now will become my 4th phone.
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
Okay, so I ordered a USED Thunderbolt on ebay last week and it should be here tomorrow. I'm not entirely new to rooting and such as I have a droid 2 global now, but that's motorola which seems to be fairly different from HTC. Anyway I've been reading threads and have come up with a few questions.
For instance if my phone is rooted when I get it, how can I get back to stock. I won't know how it was rooted, and some guides say it matters, while others don't. Plus many guides say not to just flash an RUU over a rooted phone, but if it replaces the bootloader, radio, and system, why not. Isn't that basically like an SBF on a motorola phone? Can I then also do a data wipe from the hboot bootloader thing on my phone and end up with a perfect stock device without any risk? From what I understand some roots block this entirely on the phone though so maybe I can't. I'm not really sure how to know what is safe to do on a phone that I didn't previously own and would love a guide to how to check these things and what to do so I don't brick the phone.
Also I can't seem to find a functional link to any of the latest radios, does anyone have a working link, and do people recommend the leaked radio from the most recent leaked build, or an official radio? and if so what radio is official? the one ending in 906 seems to be the most recent that I think is official but I'm not sure, though I am almost certain the 916 one isn't official, it appears to have been released in january on rootzwiki, while the most recent leaked build was less than a week ago from what I understand, but I don't know if it has a new radio or not.
Aside from that I think I've got it all down. figure out how to get phone to most recent stock OTA update. get 4g lte sim card, activate, root using this method.
http://rootzwiki.com/topic/20864-tool-root-2116059-and-19-no-downgrade-or-data-wipe/
then if I don't have the most recent radio I can flash it in the hboot thing, and can use cwm to flash any rom I want and a recommended kernel (I'm thinking thundershed 1.5 for starters though wouldn't mind some recommendations. I love Cyanogenmod)
Does this sound about right?
Also I'm not sure how hboot on htc phones works aside from booting on power+vol down button, but does the hboot allow for clearing data and cache as well as flashing things? On my droid 2 global there is a bootloader than can only be used to flash sbf files to get back to stock ota, and then there is a motorola stock recovery on the phone that is used for flashing updated ota updates that are signed or wiping data/cache. Are these the same on htc or are there a 2 different ones on that phone as well? I do understand that no PC is required for the htc as the tool to flash an ruu is built into the phone even if it is an older one than what the phone is currently on right?
Ok everyone. I like to think I am efficient enough to figure things out and such but I will honestly say I am having a major n00b moment with this one.
In the past, with my older Android phones (Droid 1 and Droid Razr) I was able to root and unroot the phones by following the instructions and ensure if I ever returned my device to Verizon, it gets unrooted and such.
however, now that I have the HTC Rezound from Verizon, I feel pretty stupid when it comes to the instructions I've found.
I gotten as far as unlocking the bootloader which appeared to be fairly simple, but there are just so many instructions out there on how to root the phone I cant make heads over heals on what to do.
Essentially I just want to be able to root and unroot the phone in the event I ever were to return it to Verizon for replacement. Can someone direct me to the proper way in doing this? I'd truly appreciate the help. Thank you all
storo1975 said:
Ok everyone. I like to think I am efficient enough to figure things out and such but I will honestly say I am having a major n00b moment with this one.
In the past, with my older Android phones (Droid 1 and Droid Razr) I was able to root and unroot the phones by following the instructions and ensure if I ever returned my device to Verizon, it gets unrooted and such.
however, now that I have the HTC Rezound from Verizon, I feel pretty stupid when it comes to the instructions I've found.
I gotten as far as unlocking the bootloader which appeared to be fairly simple, but there are just so many instructions out there on how to root the phone I cant make heads over heals on what to do.
Essentially I just want to be able to root and unroot the phone in the event I ever were to return it to Verizon for replacement. Can someone direct me to the proper way in doing this? I'd truly appreciate the help. Thank you all
Click to expand...
Click to collapse
Once you have unlocked the bootloader or gotten s-off, you just need to flash a recovery (Amon ra is linked in my sig) then flash a rom. All of the ROMS are pre-rooted. To revert to uprooted, all you need to do is run the GB RUU which can be found in the development section (or google)
AshtonTS said:
Once you have unlocked the bootloader or gotten s-off, you just need to flash a recovery (Amon ra is linked in my sig) then flash a rom. All of the ROMS are pre-rooted. To revert to uprooted, all you need to do is run the GB RUU which can be found in the development section (or google)
Click to expand...
Click to collapse
am not sure if i ever had the change to thank you but thank you!
I recently unlocked my bootloader and rooted my phone. I installed TWRP and flashed a couple of custom roms ( GPE & Revolution HD ) I decided i want to go back to stock. I understand so far i gotta unroot, flash stock rom and re lock bootloader. I read something about RUU files. Any one have suggestion or help how i go about this? Again, i have AT&T varient, currently on Revolution HD Rom
Famous22 said:
I recently unlocked my bootloader and rooted my phone. I installed TWRP and flashed a couple of custom roms ( GPE & Revolution HD ) I decided i want to go back to stock. I understand so far i gotta unroot, flash stock rom and re lock bootloader. I read something about RUU files. Any one have suggestion or help how i go about this? Again, i have AT&T varient, currently on Revolution HD Rom
Click to expand...
Click to collapse
There is currently no RUU available as of right now. I think the best you can do for now is to a TWRP restore. There is a stock rooted TWRP in the Android Dev forum. Although this won't un-root you, its closest to stock that you will get. For the future, always make a backup before you root and then you won't have to worry
TheEmpyre said:
There is currently no RUU available as of right now. I think the best you can do for now is to a TWRP restore. There is a stock rooted TWRP in the Android Dev forum. Although this won't un-root you, its closest to stock that you will get. For the future, always make a backup before you root and then you won't have to worry
Click to expand...
Click to collapse
I just ordered my device and still waiting on it to be delivered. I'm already debating on whether or not to root as I've never owned an android phone that i didn't root. From what i understand, the bootloader needs to be unlocked, then s-off, flash recovery and then root. Now, if i'm to do a nandroid of the stock ROM before I root, will I be able to lock the bootloader again, nandroid and s-on in case I need to utilize the warranty? Also, will any warranty bits show up or a tampered flag or any other problem arise that'll indicate it's been farked with? Is there a way to undo those flags? Thanks in advance to TheEmpyre or whomever else can shed some light on this.
EDIT: If the s-off is the only step that will trip the flag, is it possible to leave S, er, ON?
brianray14 said:
I just ordered my device and still waiting on it to be delivered. I'm already debating on whether or not to root as I've never owned an android phone that i didn't root. From what i understand, the bootloader needs to be unlocked, then s-off, flash recovery and then root. Now, if i'm to do a nandroid of the stock ROM before I root, will I be able to lock the bootloader again, nandroid and s-on in case I need to utilize the warranty? Also, will any warranty bits show up or a tampered flag or any other problem arise that'll indicate it's been farked with? Is there a way to undo those flags? Thanks in advance to TheEmpyre or whomever else can shed some light on this.
EDIT: If the s-off is the only step that will trip the flag, is it possible to leave S, er, ON?
Click to expand...
Click to collapse
Unlocking the bootloader trips a flag. When you relock it gets rid of one flag but trips the relocked flag. Soff can get rid of all flags but you have to leave it soff. Turning it back on throws a security flag.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
If you are current AT&T customer, and can go through them for warranty, they do not care in the least whether you are bootloader unlocked, rooted, s-off, etc.
I know AT&T written policy says otherwise (they have the right refuse warranty on modded phones) but in reality they cherish you paying that nice monthly bill every month over the modest cost of a refurb phone.
I've come over from the One X (EVITA) forum, and there were many (possibly dozens) of report from XDA users successfully returning their devices for warranty with bootloader RELOCKED, UNLOCKED, and in some cases even with custom ROMs installed! And I haven't seen any reports otherwise (AT&T denying warranty due to modded phone).
If you are not a current AT&T customer, and have to go through HTC, that is a different story.
But if you are an AT&T customer, my personal opinion is that you do not need to care about being able to return to stock, tripping flags, etc. Just mod away.
redpoint73 said:
If you are current AT&T customer, and can go through them for warranty, they do not care in the least whether you are bootloader unlocked, rooted, s-off, etc.
I know AT&T written policy says otherwise (they have the right refuse warranty on modded phones) but in reality they cherish you paying that nice monthly bill every month over the modest cost of a refurb phone.
I've come over from the One X (EVITA) forum, and there were many (possibly dozens) of report from XDA users successfully returning their devices for warranty with bootloader RELOCKED, UNLOCKED, and in some cases even with custom ROMs installed! And I haven't seen any reports otherwise (AT&T denying warranty due to modded phone).
If you are not a current AT&T customer, and have to go through HTC, that is a different story.
But if you are an AT&T customer, my personal opinion is that you do not need to care about being able to return to stock, tripping flags, etc. Just mod away.
Click to expand...
Click to collapse
I can second this. I just had to replace my m8 because the speakers were crackling like crazy, my bootloader showed relocked and they told me straight up that they didn't care about that as long as it was a hardware problem and not a software problem and replaced it on the spot.
I was under the impression that if you were in your first year of owning the device that faulty hardware would be covered under HTC's factory warranty and not AT&T?
brianray14 said:
I was under the impression that if you were in your first year of owning the device that faulty hardware would be covered under HTC's factory warranty and not AT&T?
Click to expand...
Click to collapse
Looking at the return info, I can see where the confusion might come from. It says "Return directly to manufacturer" for 15 days or more:
http://www.att.com/shop/wireless/returnpolicy.html#fbid=KMGdewZyG_f
But AFAIK, all warranty returns go to AT&T when you work through their warranty department. You send them your defective phone, and they send you a refurb. I haven't had to go through this process myself, but this is what has been reported many times on XDA and other forums.
Any update on this how to lock bootloader for HTC M8 AT&T with 4.4.3 InsertCoin 4.1.1 Rom S-On of course.
How do I lock the bootloader in order to upgrade to stock 4.4.4?
im2c0ol said:
Any update on this how to lock bootloader for HTC M8 AT&T with 4.4.3 InsertCoin 4.1.1 Rom S-On of course.
How do I lock the bootloader in order to upgrade to stock 4.4.4?
Click to expand...
Click to collapse
No "update" on this issue is required. The process has been the same for a couple years or more. Further, you've posted the same/similar question to multiple places, and its been answered already in multiple places.
Connect phone to computer in fastboot mode.
Open command prompt, and type: fastboot OEM lock
From there, you can run the RUU.
if HTC allows downgrading the bootloader so I can install a custom rom after I make the mistake of taking an OTA update from ATT. With the S4 this wasn't possible. but since this is my first android phone, I was wondering if it was Samsung trying to keep the device "secure" or ATT forcing these companies to keep their bootloaders locked.
some_douchebag said:
if HTC allows downgrading the bootloader so I can install a custom rom after I make the mistake of taking an OTA update from ATT. With the S4 this wasn't possible. but since this is my first android phone, I was wondering if it was Samsung trying to keep the device "secure" or ATT forcing these companies to keep their bootloaders locked.
Click to expand...
Click to collapse
Once you unlock the boot loader no update can relock it. HTC offers a lot more freedom than samsung, but at the price of no warranty. So if you unlock it and shatter your screen, don't be upset like other people when htc will not warranty it. As long as you have a custom recovery, your phone cannot even physically take an ota update so nothing to worry about either way.
The Magnuson–Moss Warranty Act is in place for us consumers for this reason. The company has to prove that any modification you did, is the cause of the trouble. So if you unlock your bootloader, root, etc, then crack your screen, as the poster above mentioned, the company can not void your warranty since what you did has nothing to do with cracking your screen.
This was huge for me when I modified my car and I found this here on XDA after doing more searching
http://www.xda-developers.com/xda-tv-2/your-warranty-is-not-void-xda-tv/
Oh and yeah,,if you are outside the US, it wont work lol
some_douchebag said:
if HTC allows downgrading the bootloader
Click to expand...
Click to collapse
That depends on what you mean by "allow". You cannot downgrade the bootloader by any "official" means. You will fail version check when you try to install, as you can "normally" only flash a equal or great version number hboot.
But if you are s-off, version check is bypassed, and any hboot version can be flashed.
Similar to a previous response, my advice would be to unlock the bootloader (required if you want to flash custom ROMs anyway) and S-off the phone soon after you get it. Neither of those can be changed by any OTA.
Also, accepting OTA is not recommended on a modded phone, anyway. Whatever came in the update will usually get posted in a stock rooted form in the Development forum, and/or incorporated into custom ROMs, often within days of the OTA rolling out. And OTA will not install on a modded phone (stock recovery needs to be present). OTAs also may plug existing s-off or other exploit; preventing you from doing them if you haven't already (but as mentioned, can't make the phone s-on again). Moral of the story, I strongly recommend against OTA on any modded phone.
Some of these terms/concepts are HTC specific, so may be a bit confusing for you. I would suggest reading up on these forums, if you aren't familiar with s-off, HTC's bootloader unlock process, etc.