Related
So I am on the fence on this one. Every Android device I have owned has been rooted but not being able to return the device if something should go wrong has me a little skeptical with the View.
Looking at the development section I also don't see anything that would make me jump off stock right now and not sure if that will change in the future.
Anyone else contemplating keeping it stock? I did notice you can always go back to GB from HC and then root but it would require you to use HTC unlocker. My question is, if you use HTC's unlocker can you still achieve S-OFF and load Roms, Radios, and Kernels from CWM or will it be like the EVO 3D fiasco?
[email protected] said:
So I am on the fence on this one. Every Android device I have owned has been rooted but not being able to return the device if something should go wrong has me a little skeptical with the View.
Looking at the development section I also don't see anything that would make me jump off stock right now and not sure if that will change in the future.
Anyone else contemplating keeping it stock? I did notice you can always go back to GB from HC and then root but it would require you to use HTC unlocker. My question is, if you use HTC's unlocker can you still achieve S-OFF and load Roms, Radios, and Kernels from CWM or will it be like the EVO 3D fiasco?
Click to expand...
Click to collapse
Nevermind please ignore. My post below is about Flyer and OP was asking about View. Not sure what to do about view
Not accurate. You do not need to unlock to get to HC or get back from HC to GB.
1) GB to HC: http://forum.xda-developers.com/showthread.php?t=1358758
2) Back to GB: http://forum.xda-developers.com/showthread.php?t=1428104
After following instructions on second link, you are back to GB, but you are S-OFF. To go back to S-ON Follow this guide => http://forum.xda-developers.com/showthread.php?t=1346200
[email protected] said:
So I am on the fence on this one. Every Android device I have owned has been rooted but not being able to return the device if something should go wrong has me a little skeptical with the View.
Looking at the development section I also don't see anything that would make me jump off stock right now and not sure if that will change in the future.
Anyone else contemplating keeping it stock? I did notice you can always go back to GB from HC and then root but it would require you to use HTC unlocker. My question is, if you use HTC's unlocker can you still achieve S-OFF and load Roms, Radios, and Kernels from CWM or will it be like the EVO 3D fiasco?
Click to expand...
Click to collapse
I went about this in just about the wrong-est way possible by getting the OTA Honeycomb update before doing anything. I used the HC to GB downgrade process described in the dev forum (which requires the HTC unlock as a first step), then got S-OFF using globatron's other thread, both of which worked with little drama.
I've had no trouble flashing ROM's through CWM but haven't tried anything else (is the HC kernel source for the View even available yet?). In short, I have no regrets, but I bought the View to play with so YMMV.
I think the main thing I am looking forward to with this purchase is the rooting and the unlockable bootloader. If I decide to keep it, that will be the first thing I'm doing
I am going to stay Stock. It's a very good device as Stock and there is no need to put on a ROM as far as I am concerned.
[email protected] said:
Every Android device I have owned has been rooted but not being able to return the device if something should go wrong has me a little skeptical with the View.
Click to expand...
Click to collapse
You shouldn't return the product because you screwed up trying to modify it... this is the reason why locked bootloaders exist!
Printerscape said:
You shouldn't return the product because you screwed up trying to modify it... this is the reason why locked bootloaders exist!
Click to expand...
Click to collapse
Thanks buddy, I don't need a lesson from you as to why locked bootloaders exist. I have owned over 10 smartphones in my day and have unlocked / rooted all of them with no problems. But you best be sure if I mess something up within my return period it is going back like everyone else here would do including you Mr high almighty.
Also, when Dev's work on an un-root method a lot of times they will brick a device and need to return it for another one. So will you purchase them another device so they can do you a favor and unlock your bootloader for you? I don't think so.
So after doing some research, I am thinking of rooting it but just leaving GB on it. I have seen people complain about some compatibility issues with some apps as well as the on screen buttons taking up to much screen real estate. I don't really see an advantage to going to honeycomb.
Another question, is there a way to re-root the phone back to stock after it is unrooted? If ICS comes to town, I would probably want to grab the official update...
Printerscape said:
You shouldn't return the product because you screwed up trying to modify it... this is the reason why locked bootloaders exist!
Click to expand...
Click to collapse
Excuse me if I do not feel bad for the multi billion dollar corps if a couple busted failed modded devices return, which in most cases they fix in seconds are sell refurbished
Sent from my HTC Flyer P510e using xda premium
[email protected] said:
Another question, is there a way to re-root the phone back to stock after it is unrooted? If ICS comes to town, I would probably want to grab the official update...
Click to expand...
Click to collapse
Why? A rooted version of the official ICS update (if one every happens) would likely show up right after the official OTAs hit the airwaves. If not leaked earlier even.
Hey, guys. I'm having a heating issue with my Rezound. It's on Newt's OneXxX RLS3 right now, 3.14.605.5 and his kernel, S-On, just flashed it this morning in the hopes it would fix my overheating issues, but no luck.
Last night, and from May 30th, I was on BAMF ICS 2.1, 3.11 firmware. I made a 15 minute call to my Mom, and went from 100% to 87%, and up to 123 degrees with alternating amber/green light.
Just a few minutes ago, spent about 10 minutes on the phone and playing on the net, and it was up to 110 degrees, and in 10 more minutes, went from 69% battery to 25%, so looks like Newt's didn't fix it either.
I need to know what I need to do to get it into a returnable condition. Do I need to re-lock the bootloader? If so (I assume so) will that be enough to get past Verizon, or do I need to return it to stock? Do they look at software numbers and stuff? I really don't want to have to S-Off the damn thing just to get it back to GB to return it.
I tried to call Verizon and have them send me a replacement, but the tech lady said I'd need to take it to a brick and mortar store to have them check it out. She said they would want to check out the battery, the charger, and the phone.
Ok, didn't get an answer so I went ahead and S-Off'd. Now where are the directions for reverting to GB....
First, please confirm you didn't run HTCDev Unlock again after S-off, at least tell me you kept stock bootloader or flashed the JB hboot lol. If you did, you'll need to redo the S-off process to get the "Unlocked/Relocked" flag to change back to "Locked". If you are worried about full stock appearance for warranty purposes.
Download the 2.01.605.11 GB RUU, preferably the PC .exe version since it can wipe stuff easier remotely.
http://forum.xda-developers.com/showthread.php?p=19756694
Glad you were able to accomplish S-off quickly, since you don't have much technical trouble you'll probably want to follow this guide to reset the S-on flag too: http://forum.xda-developers.com/showthread.php?p=25165453
Ah, crap. No, I forgot to install the jb_hboot. I've already installed this Rom: http://forum.xda-developers.com/showthread.php?t=1467329 but I still have Amon Ra. I'm locked, but still S-Off. Can I install the 2.01 over top of what I have already? And will it overwrite the recovery?
Danariel said:
Ah, crap. No, I forgot to install the jb_hboot. I've already installed this Rom: http://forum.xda-developers.com/showthread.php?t=1467329 but I still have Amon Ra. I'm locked, but still S-Off. Can I install the 2.01 over top of what I have already? And will it overwrite the recovery?
Click to expand...
Click to collapse
Well the point is actually that once you run HTCDev Unlock on the bootloader, only S-off magic can make the flag a stock "Locked" message. Relocking normally shows "Relocked" which still indicates tampering lol. Sounds like you are good if it is still "Locked" that is what you want.:thumbup:
Yes, run the RUU and it overwrites the ROM, the recovery, bootloader, radios, and factory resets the data. What it does not affect are the flags in the bootloader (i.e. Locked/Unlocked/Relocked and S-on/S-off) That RUU covers all warranty issues except S-off flag. To toggle to S-on, all your accessing past this point will be from the adb commands you have from HTCDev/S-off process if that is what you're wondering.
So yeah, from where you are just run the RUU, do Scotty's guide for the S-on flag. Just remember on Scotty's guide you must boot into the ROM after the RUU to toggle USB debugging in the settings. So go back into the bootloader after the guide and do a factory reset to cover those tracks lol.
Well, I managed to install the jb_hboot, but now there's no Recovery at all. And since I'm already on 2.01, the .exe is failing. I think I need to set Mainversion Low, but since I don't have a recovery...looks like I'll have to use the other file to flash it in the bootloader. I'll let you know how this goes.
Edit: Ok, I am now Locked, and S-On. However, it won't boot. When I go to turn it on, it boots to a black screen with a circle arrow and one in the middle pointing down over the picture of a phone. I managed to brick it, didn't I?
Edit 2: Ok, it's rebooting now...and we have Stock! I rebooted into the bootloader to verify LOCKED, S-ON, but there's still nothing when I try to go to recovery. IDC, that's good enough for me dammit. I'm through with it for the night!
(And thank the gods I remembered to uninstall my Blizzard Authenticator before I did all this crap...)
Danariel said:
Well, I managed to install the jb_hboot, but now there's no Recovery at all. And since I'm already on 2.01, the .exe is failing. I think I need to set Mainversion Low, but since I don't have a recovery...looks like I'll have to use the other file to flash it in the bootloader. I'll let you know how this goes.
Ok, I am now Locked, and S-On. However, it won't boot. When I go to turn it on, it boots to a black screen with a circle arrow and one in the middle pointing down over the picture of a phone. I managed to brick it, didn't I?
Click to expand...
Click to collapse
Soft brick. That is the stock recovery... Did you do S-on with the JB hboot and/or custom ROM? That could cause that per the warnings in Scotty's thread.
Edit 2: haha good deal, congrats. Yes, that is what stock recovery looks like, no alarm needed.
PhantasmRezound said:
Soft brick. That is the stock recovery... Did you do S-on with the JB hboot and/or custom ROM? That could cause that per the warnings in Scotty's thread.
Edit 2: haha good deal, congrats. Yes, that is what stock recovery looks like, no alarm needed.
Click to expand...
Click to collapse
Thank you so much for all your help!
The temp on this ***** is 121 Degrees Fahrenheit right now. She's going BACK tomorrow! Absolutely unbelievable. You know, come to think about it, my Thunderbolt had overheating/rebooting issues until I rooted it and got a custom ROM. I really hope I get a good one, this time, I'd hate to go through all this **** again.
Danariel said:
Thank you so much for all your help!
The temp on this ***** is 121 Degrees Fahrenheit right now. She's going BACK tomorrow! Absolutely unbelievable. You know, come to think about it, my Thunderbolt had overheating/rebooting issues until I rooted it and got a custom ROM. I really hope I get a good one, this time, I'd hate to go through all this **** again.
Click to expand...
Click to collapse
All phones are different, depends on how a person uses it. But the radio, charginig method, running apps, and likely hardware are all factors. http://forum.xda-developers.com/showthread.php?p=20138465 Worth skimming through. Some now have newer XE and unmarked hardware models which may have better temperature performance, time will tell. Could be worse... Just don't know if these hardware revisions address quality issues with heat, or are meant to reduce production cost. Probably both. Perhaps inconsistent from revision to revision; maybe a middle-aged model got cheaper but unexpectedly ran hotter. Need to be an HTC insider or get plenty of feedback to isolate the effect hardware revision has in the overall heat equation.
Edited for TL;DR-ness of anecdotal info. Good luck with the replacement.
PhantasmRezound said:
All phones are different, depends on how a person uses it. But the radio, charginig method, running apps, and likely hardware are all factors. http://forum.xda-developers.com/showthread.php?p=20138465 Worth skimming through. Some now have newer XE and unmarked hardware models which may have better temperature performance, time will tell. Could be worse... Just don't know if these hardware revisions address quality issues with heat, or are meant to reduce production cost. Probably both. Perhaps inconsistent from revision to revision; maybe a middle-aged model got cheaper but unexpectedly ran hotter. Need to be an HTC insider or get plenty of feedback to isolate the effect hardware revision has in the overall heat equation.
Edited for TL;DR-ness of anecdotal info. Good luck with the replacement.
Click to expand...
Click to collapse
LOL, Bacon Mode! Yep, that's my phone to a Tee. However, i'm not going to LET it get to 135 or 152 before I take it back. That's Extra Crispy bacon right there!
I have done my research on this topic, but I am still not confident I will be going about this the correct way.
I am new to the android hacking scene but feel with a little more guidance I will be able to do what I want to do.
I got my EVO on day 1 of release and have not accepted any OTA's. I had the phone rooted right after the first root method was released. I had wanted to flash custom ROM, but was not willing to go the HTCDev route as I was concerned with the warranty.
The Lazypanda S-OFF solution seemed good until I read it was bricking a lot of phones. Now I know there is an unbricking tool, but how effective is this? Simply put, if I follow directions, how likely is it that I would brick my phone with this method? And how likely am I to be able to fix it?
And lastly, I had activated Google Wallet before it stopped working on the phone. I know the OTA will fix this, but for obvious reasons I do not want to do this. Will I have to do the build.prop edit to a Nexus phone to gain access and wipe GW settings before I do lazy panda or is there another way?
Thank you in advance for the help.
All your answers are in the forum.
I'm not sure of the % of bricks from using lazypanda, I think its low if you follow the directions and the unbricker is successful 100% of the time for that brick AFAIK.
forget about clearing wallet. I have my phone since release day and have never reset/cleared wallet and I usually flash new a new ROM every few days. GWallet still works fine.
I would hang around the lazypanda thread for a while and ask the questions you asked here. There are some real helpful ppl there
Good luck with S-OFF
Sent from my EVO using xda premium
Thank you for the reply.
I believe some of my answers probably have been answered, but I have already spent a considerable amount of time reading and do not feel confident. I just do not want to risk bricking my phone. I realize that there will always be some risk, but I would like to have a good idea what that is.
I am not concerned with a soft brick, if the tool will really fix any brick that could have occurred while using the lazy panda method.
Apologies if I should have continued reading more, I just thought I was at the point to request some more personal guidance.
Yup
No worries. I'm almost positive the unbricker works 100 % of the time IF you need it. You should probably have it setup and ready to go just in case. I personally didn't have any problems
Sent from my EVO using xda premium
me either.. just follow the directions and u should be fine.. it went perfect for me.. it was over in 5 mins!!!! s-off is the way to go!!!!!!
evo401 said:
me either.. just follow the directions and u should be fine.. it went perfect for me.. it was over in 5 mins!!!! s-off is the way to go!!!!!!
Click to expand...
Click to collapse
My phone bricked, used the unbricke,r made sure everything was working in the reccomendations from post 2 in LP thread, ran LP no problems
u will be fine
Hey man, s-off is definitely worth it. There are plenty of us here on xda that can help u out if it does manage to brick.
And if for some reason u have a problem and brick run the un brick tool.
Practice makes perfect. And anything worth anythings ng takes a little risk.
Was concerned myself about the gwallet thing. I bricked 2 EVO LTE's w secure element errors just rooting and flashing roms. This was back before the fix though. And it is still unclear whether the fix is in the actual updated app or in the ota, or both. Google won't be clear with that.
If u want to be extra safe then do the build.prop edit to reset. Make sure to re-install old build.prop after resetting gwallet and before the s-off process. Not sure if it matters or not but better safe with stock and s-off then edited build.prop running unbricker.
I wouldn't upgrade now. The devas from lazypanda just hot a phone with hboot 1.15 to work on
Sent from my EVO using xda premium
Man I hope they crack it soon, now that they got a device.
Sent from my EVO using xda app-developers app
Hey all!
I want to send my phone back to HTC for some warranty work (warranty expires within the week so I need to get this done asap). I'm having some call quality issues as well as network issues (limited 4G when my wife's LTEvo is better). Anyway, I'm trying to get it back to stock and unrooted.
I found videos by QBKing77. From his videos, it looks like I'm supposed to lock the bootloader and then unroot the phone. When he shows the bootloader screen, his shows tampered and unlocked. The lock bootloader video is then supposed to make it say relocked and tampered and then the unroot will take away the tampered notice. The thing is, I don't see those on mine. I know my phone is rooted, is it possible I didn't unlock the bootloader? If so, is there a way for me to check?
Basically, I'm looking for the best way for me to relock my phone and have it good enough that nothing looks like I'm violating any warranty. I've seen things about RUUs, but there are different versions it seems. I'm just not sure where to begin or what I need for my phone. I did not unroot via HTC's website or anything like that. But I did it all about a year ago, so I'm not exactly sure what I did.
Any help would be greatly appreciated! Thanks!
Viperboy has a tool that you can use to return your phone to a completely stock, locked state. You must be S-off in order to use it, but if you're concerned about sending in your phone that's obviously been tampered with, it's the best way to go, in my opinion. The link to his tool is below. Also, this type of post would normally go in Q&A.
http://forum.xda-developers.com/showthread.php?t=2197909
Sent from my EVO 4G LTE using xda premium
FinZ28 said:
Viperboy has a tool that you can use to return your phone to a completely stock, locked state. You must be S-off in order to use it, but if you're concerned about sending in your phone that's obviously been tampered with, it's the best way to go, in my opinion. The link to his tool is below. Also, this type of post would normally go in Q&A.
http://forum.xda-developers.com/showthread.php?t=2197909
Sent from my EVO 4G LTE using xda premium
Click to expand...
Click to collapse
Thank you very much. I'll look into this. Does this take my phone from S-off to S-on when it's done? If not, do I need to do that myself or does Sprint and/or HTC not care about that?
If they fix my problem, will I be able to root my phone again after this? Not a necessity, but I'm curious.
Oh, and thanks for being kind when I posted in the wrong section. If a moderator can move it, that'd be great. Sorry.
KB3NRY said:
Thank you very much. I'll look into this. Does this take my phone from S-off to S-on when it's done? If not, do I need to do that myself or does Sprint and/or HTC not care about that?
If they fix my problem, will I be able to root my phone again after this? Not a necessity, but I'm curious.
Oh, and thanks for being kind when I posted in the wrong section. If a moderator can move it, that'd be great. Sorry.
Click to expand...
Click to collapse
Yes, if you use the tool it will revert your phone to S-on.
As far as whether or not Sprint or HTC cares is almost anybody's guess. I've seen people say they don't care, and others say that they do. Just to be safe go back completely stock. You can always root it again once you get it back
Sent from my EVO 4G LTE using xda premium
Yes it will take the s-off flag to s-on, you will be back to stock, updated to 3.16, after that if it gets fixed/repaired you should be able to get s-off with moonshine / facepalm / dirty racun whichever it's easier for you...
Sent from my EVO using xda app-developers app
Thank you both very much! This sounds like exactly what I was looking for. I'll give it a shot and see if I'm still having the issues I'm having. If I am, I'll send it back. We send my wife's phone back to HTC once (never rooted) and they were pretty easy to work with. Just cost us about $8 in shipping or something like that.
I am honest with Sprint employees about my phone being rooted whenever I have an issue. They never seem to mind, they just can't always be as certain if the problem is their problem or something from me messing with it...and I understand that. I usually test with my wife's phone and see if I have the same problem or not. Anyway, for what it's worth, Sprint has always been good to me as far as my phone being rooted, but I wasn't asking for warranty work at those times.
First of all, this is one of my first few posts, so forgive me if this is in the wrong section.
The backstory:
I just recently bought an HTC One M8 (AT&T) and had it unlocked via AT&T to put on T-Mobile. Literally everything works besides MMS. I've tried APN settings every way that I could, and nothing. I've done some research and found that if I'm having this problem, it has something to do with the AT&T service that the phone was on. I did a factory reset on it and then re-did the APN settings again, but still no avail. I did some MORE reading and found that rooted devices don't have this issue, for whatever reason. So, now I'm looking into that. However, I don't want to brick the thing because I just got it.
I have a couple questions before I dive any deeper into the rooting and/or flashing a 5.0.1(I think) GPE, if I'm even going to.
First of all, how easy is it to brick Android phones nowadays? I've got a friend who gets a new device simply to tinker with and he said it's not terribly difficult unless you're really dumb. I've rooted and flashed a new firmware on my Kindle Fire, and it works like a charm, so I'm not completely new to the scene.
Second, I found this tutorial... http://forum.xda-developers.com/showthread.php?t=2799796
And it seems to be the one that I'm going to follow. But do I need to S-Off first?
Second a, If I do, how? Firewater seems to be dead and Sunshine I have to pay for, which I would like to avoid, though I'm not completely opposed.
Second b, is Sunshine any more safe than Firewater?
Third, is there any more info you need from me? If there is, I can post within.
Have you tried changing your messaging app's custom settings? Try fiddling with your messaging app's apn settings, or using a different messaging app.
You can use the directions in your link to unlock your bootloader with htcdev for a custom recovery+root without s-off and paying for sunshine.
You can use one of the all in one toolkits floating around if you're worried about messing up, but it's not too complicated.
I wouldn't worry about bricking your phone, as long as you follow the directions, and have a solid usb connection.
Power+up volume for a hard reset, and Power+volume down to get back to the bootloader will save you if you mess up in the vast majority of cases. Staying S-ON should prevent you from changing the stuff that could truly catastrophically brick your phone.
You would need s-off if you wanted to change your phone to be the same as if you bought it from T-mobile.
http://forum.xda-developers.com/showthread.php?t=2796417 might help you out too.
you should be able to flash a ruu for t mobile provided youre s-off and change CID to match t mobile carrier.
That would likely fix all of your issues.
And again, I wouldn't worry too much about bricking the phone. Just make sure to do a complete backup before you start and follow all the directions to the letter.
http://forum.xda-developers.com/google-nexus-5/help/faq-to-android-read-post-root-t2508292
this is a good article to read to help you get acquainted with your phone and whats going on inside it.
Hope this helps.