Related
So heres the story:
When I was rooting my Amaze using xboarder's Guide, I got a "Status 0" error, then rooted it using the Easy Perm Root One Click, got some mistakes in the cmd, and rerooted it but this time the guide was working flawlessly.
So yesterday the same thing happened to my girl's Amaze, but on my way to rerooting it, i did a sloppy mistake and applied the unlock_code.bin for my phone instead of her. The phone froze for a few seconds, then a "Security Warning" message showed up under ***Relocked*** and restarted back to hboot by itself. By then I already had realized what ive done and changed the cmd directory to her bin, unlocked the bootloader, installed Clockwork and rooted it. The problem is that since then, everytime I try to flash QuickSense or relock and unroot, her phone begins bootlooping even though ph85img.zip seems to flash correctly (i think there were some errors while flashing QuickSense). Also, before i screwed up, i nandroid backed up her rom but then couldnt restore it, shows that android_secure.img is missing and bootloops too.
The only rom which works flawlessly right now on her phone is mike1986's Revolution.
Does anyone know what may be broken and a way to fix it. Thanks in advance!
relock then do the whole unlock over again
xboarder56 said:
relock then do the whole unlock over again
Click to expand...
Click to collapse
That is my first thought as well.
xboarder56 said:
relock then do the whole unlock over again
Click to expand...
Click to collapse
I tried this a couple of times, with 531.5 and 531.6 RUUs, its a no go... I just saw your kernel flashing guide, should i try that?
I relocked/unlocked the phone 2 more times, the official RUUs and xboarder ROMs keep bootlooping, cannot do proper nandroid backup, but Revolution HD works fine. Any idea why is that, and how I can restore phone's normal settings, so it works with all roms? I really need some help here.
That just seems....weird.
There has to be something in that rom that is allowing interface, and that something is not allowing it elsewhere. (Kernal/etc.)?
Hi Everybody,
I have seen the recent posts and guides regarding unrooting especially the guide from Twolazyg. Only problem is, I am already running the stock Sprint 651.3 rom. I always backed up my stock rom and would switch back to update it and I did just that this time to get 651.5 without the pesky CIQ software. I am aware of how to relock the bootloader as per htc instructions but then again I'm not sure of what to do. When I rooted I installed cwm 4.0.1.4 through the method at htcevohacks.com then TWRP came out and I flashed twrp 2.0.0RC0 over cwm. Never had a problem with TWRP so I know it isn't the recovery. I didn't get Flashimage GUI so I was always using fastboot to install roms. Also, I never used the android sdk (at least I think I didn't because its not on my computer) so not too sure when someone says use adb in the instructions. Oh yea, I'm also a noob so take it easy if you can lol.
Initially, I installed a custom rom after rooting and unlocking my bootloader via htc method. Then I wasn't too happy with the roms and just decided to stay rooted but keep my stock rom. I installed app quarantine to freeze some of the unused system apps like friendstream, peep, stocks, etc.. Before I did the update I brought all the apps out of quarantine incase anything screwy happened with app updates.
Fast forward to today, and now after 651.5 update my phone is literally restarting. It keeps booting up to my lock screen and it holds for 1 minute then it just restarts. It's sitting in front of me right now and as I type it has restarted at least 10 times as I have been watching it. It actually started acting up after I let out all the apps from app quarantine yesterday so 651.3 was already screwy with system apps unquarantined.
So I'm trying to unroot and relock so I can send this baby back to Sprint and get a replacement. Already did a master a reset three times and nothing works in terms of stopping the constant rebooting.
I'm just wondering where do I start with any of the steps. Should I just follow the guide exactly or do I have to take different steps???
Thanks
Hiya Buddy said:
Hi Everybody,
I have seen the recent posts and guides regarding unrooting especially the guide from Twolazyg. Only problem is, I am already running the stock Sprint 651.3 rom. I always backed up my stock rom and would switch back to update it and I did just that this time to get 651.5 without the pesky CIQ software. I am aware of how to relock the bootloader as per htc instructions but then again I'm not sure of what to do. When I rooted I installed cwm 4.0.1.4 through the method at htcevohacks.com then TWRP came out and I flashed twrp 2.0.0RC0 over cwm. Never had a problem with TWRP so I know it isn't the recovery. I didn't get Flashimage GUI so I was always using fastboot to install roms. Also, I never used the android sdk (at least I think I didn't because its not on my computer) so not too sure when someone says use adb in the instructions. Oh yea, I'm also a noob so take it easy if you can lol.
Initially, I installed a custom rom after rooting and unlocking my bootloader via htc method. Then I wasn't too happy with the roms and just decided to stay rooted but keep my stock rom. I installed app quarantine to freeze some of the unused system apps like friendstream, peep, stocks, etc.. Before I did the update I brought all the apps out of quarantine incase anything screwy happened with app updates.
Fast forward to today, and now after 651.5 update my phone is literally restarting. It keeps booting up to my lock screen and it holds for 1 minute then it just restarts. It's sitting in front of me right now and as I type it has restarted at least 10 times as I have been watching it. It actually started acting up after I let out all the apps from app quarantine yesterday so 651.3 was already screwy with system apps unquarantined.
So I'm trying to unroot and relock so I can send this baby back to Sprint and get a replacement. Already did a master a reset three times and nothing works in terms of stopping the constant rebooting.
I'm just wondering where do I start with any of the steps. Should I just follow the guide exactly or do I have to take different steps???
Thanks
Click to expand...
Click to collapse
Well first off, Flash Image GUI is a great program, so I want to provided my biased opinion as the author!
Off the top of my head, I am really temped to say your currently rebooting issue could very well be software related and not hardware related.
Moving around system applications, "freezing" and "unfreezing", I personally don't view as the most reliable method.
I view returning the device as the last ditch effort and giving up because everything else has failed and the issue is most likely hardware related.
If you're interested in troubleshooting the issue further, running the RUU, should return the system partition and the kernel back to a completely stock state at which point the rebooting should stop.
If the rebooting stops, then you'll know the issue was trigger by something software related and not hardware related.
Many of the RUU files for the EVO 3D are located at http://www.goo-inside.me/shooter/ruu . The directions/guides are posted all over the place on how to properly process an RUU but they are really fairly simple and bring the device back to 100% stock state.
Hope that helps and good luck!
Thanks for your input joey but weird thing is, when I have my evo 3d plugged in to my pc it does not continuously reboot. For the hour or so I've had it plugged in, it hasn't rebooted at all. It is completely usable. After unplugging it, the reboot cycle begins and it is unusable.
I wanted ask for some help because I never installed android sdk or did anything through adb at all. So if someone says "do it via ADB" I will have no clue as to what to do to fix my phone. I have installed sdk and platform tools to try and relock my bootloader but I'm not sure what to do. I mean, I went back to htc dev step 14, which is to relock I just have to type in fastboot oem lock but because I never did it via sdk method. So I guess I should follow the same method in my TWRP 2.0 folder then? Because I see a file called adb.exe
So, based on Twolazyg's instructions, would I have to put my phone in recovery via fastboot. Then type in the command prompt adb reboot bootloader. Then go to Hboot to flash the RUU and finally type in fastboot oem lock. Is this right???
I tried the instructions provided by Twolazyg but I can't get the first step to work...
So, I hold power + volume down and select fastboot.
Connect to pc with usb cable.
Open up cmd.exe and type in:
cd Desktop\Evo3DTwrp
Then follow instructions.
I type in adb reboot bootloader and then nothing happens.
I get this message on my computer:
* daemon not running. starting it now *
* daemon started sucessfully *
error: device not found
What am I doing wrong???
All I wanna do is unroot so I can return this phone for a new one...
Nevermind people, figured it out lol
Was about to Rage Quit but it works.
Got the RUU working and no longer have superuser and bootloader says relocked
Will now try the update to 651.5 then contemplate a return...
You da man joeykrim! My problem has been resolved
Hiya Buddy said:
Thanks for your input joey but weird thing is, when I have my evo 3d plugged in to my pc it does not continuously reboot. For the hour or so I've had it plugged in, it hasn't rebooted at all. It is completely usable. After unplugging it, the reboot cycle begins and it is unusable.
I wanted ask for some help because I never installed android sdk or did anything through adb at all. So if someone says "do it via ADB" I will have no clue as to what to do to fix my phone. I have installed sdk and platform tools to try and relock my bootloader but I'm not sure what to do. I mean, I went back to htc dev step 14, which is to relock I just have to type in fastboot oem lock but because I never did it via sdk method. So I guess I should follow the same method in my TWRP 2.0 folder then? Because I see a file called adb.exe
So, based on Twolazyg's instructions, would I have to put my phone in recovery via fastboot. Then type in the command prompt adb reboot bootloader. Then go to Hboot to flash the RUU and finally type in fastboot oem lock. Is this right???
Click to expand...
Click to collapse
regarding "adb", this binary is kept inside the android-sdk directory and under the subdirectory platform-tools.
many times ppl extract the adb.exe and the accompanying .dll file, package these two up into their "one click" tools and distribute.
personally, i prefer to grab the official android-sdk from google and their associate adb.exe instead of using copies distributed by other users.
hopefully that helps clarify some of the details around adb!
Hiya Buddy said:
You da man joeykrim! My problem has been resolved
Click to expand...
Click to collapse
always good to hear. another evo 3d saved!
glad it worked out. if any guides/posts were specifically helpful to you, feel free to post back your solution in case anybody else comes across this thread with the same issue.
never stops amazing me how many ppl end up with the exact same issue and these posts can be helpful!
glad to hear the issue was resolved!
@joeykrim
Everything works, but back to rooting for me until Sprint gets their **** together with 651.5 update. I took my phone in for service today after unrooting and relocking the bootloader. I was curious as to why my 3g speeds hover around 100kbps when they're usually at 800-1000kbps. According to the tech, who was running a custom rom on his Epic 4G Touch, he told me the update contained a prl that was screwy and it caused speed issues. I can confirm this with the other two evo 3ds on my account that have never been rooted/modded because they're just as slow with loading up web pages and working with apps. It was prl 21083 that is just not working out with data speed.
On Speed Test, I would put up a screen shot but I'm currently working on rooting lol, the latency would always be around 800ms and the fastest speed I got was 121kbps. There are no outages in my area because I called CS yesterday to set up my appointment and they said the towers are working normally. So it seems the 651.5 update is adds a snappyness to the UI but instead of speeding up the internet, it makes for a rather unpleasant internet experience and makes one question their "truly unlimited data and premium data fee."
So I'm gonna put TWRP back on my phone and pick a new rom based on 651.3 because of the screwed up prl unless I can keep my 651.5 and change the prl.
@Hiya buddy
I have a Sprint evo 3d flashed to reliance (carrier in india). I was on a sense 3.5 rom. I heard about this update and i restored my nandroid of stock ROM. Then i relocked it and flashed RUU (2.08.651.3). And accepted the OTA. Everything is working fine for me. No PRL's / Settings changed. My phone still works on reliance........
I did the same thing, restoring my nandroid backup of OTA 651.3 and did the update. After update 3g speeds are atrocious on Sprint, as for the software the phone is a bit snappier and more fluid than before.
hboot 1.5 s-off. Is this a true s-off or whats the deal
This past weekend I rooted my 3D evo and my girlfriends 3D evo. I had a bunch of problems during the process with mine. receiving 4g on the blackened rom, had to go into the msl settings a couple times, ect.... then when all was said and done, at the boot menu it said s-off.
On the other hand, when i rooted my girlfriends evo 3D, I had no issues at all went through really easily then at the end her's said s-on! I was baffled, I had used the same process, and both of our phones have hboot 1.5?
Does this mean I can install roms from recovery? I have a the full (I think it's revolutionary) recovery on it. Options to install from zip and all.
However I did try and install a custom kernal from kernal manager and had to reinstall the blackened rom (Which is awsome btw) because I couldn't get 4G or wifi. (RCMIX Kernal). When i tried to flash a new kernal over the rcmix, it went through the process rebooted...then nothing still had the RCMIX kernal? So I reinstalled blackened. Totally fine, everything working 100%.
Any explainations, I haven't been able to find anyone with 1.5 hboot s-off doing a google search, only people who say it's coming soon. I also figured this would be the best place to post this considering there is no hboot 1.5 general section. if there is please move this there.
Thanks in advance
sag04463 said:
This past weekend I rooted my 3D evo and my girlfriends 3D evo. I had a bunch of problems during the process with mine. receiving 4g on the blackened rom, had to go into the msl settings a couple times, ect.... then when all was said and done, at the boot menu it said s-off.
On the other hand, when i rooted my girlfriends evo 3D, I had no issues at all went through really easily then at the end her's said s-on! I was baffled, I had used the same process, and both of our phones have hboot 1.5?
Does this mean I can install roms from recovery? I have a the full (I think it's revolutionary) recovery on it. Options to install from zip and all.
However I did try and install a custom kernal from kernal manager and had to reinstall the blackened rom (Which is awsome btw) because I couldn't get 4G or wifi. (RCMIX Kernal). When i tried to flash a new kernal over the rcmix, it went through the process rebooted...then nothing still had the RCMIX kernal? So I reinstalled blackened. Totally fine, everything working 100%.
Any explainations, I haven't been able to find anyone with 1.5 hboot s-off doing a google search, only people who say it's coming soon. I also figured this would be the best place to post this considering there is no hboot 1.5 general section. if there is please move this there.
Thanks in advance
Click to expand...
Click to collapse
Hboot 1.5 s-off is not possible at the moment. Probably wouldn't be worth it to the devs at this point in time with ICS around the corner. That OTA update will most likely change the bootloader.
sent from America....F__k yeah!
@sag04463 Jabawockee is right, that doesn't seem possible. And your issue is a common problem with Hboot 1.5. You gotta get the Flashimage GUI from joeykrim or you could do it via fastboot and remember a few simple commands. That 4G/Wifi issue seems to only be problematic with Hboot 1.5 because HTC didn't fully unlock the bootloader or something (Experts, take it easy on me I'm not sure about this) and it doesn't allow for the installation of custom kernels.
I'm posting this because I know there have to be people out there in my same situation. I don't have much desire to install custom roms, but I want to be rooted and have a custom recovvery. That said, I went with the HTC Dev unlock (well aware of the kernel flashing limitation), rooted and flashed TWRP. This was around the release of the device so I never attempted to update until a few days ago. This is the process I went through to keep my root, still get the OTA updates.
Verified that my root was protected with OTA Rootkeeper, and SuperSU(paid)
Tried running the OTA; failure (nice little red triangle with the !) due to custom recovery and edited build.prop (source)
Flashed the stock recovery per the instructions in the clockwork mod post
Reverted my build.prop back to stock, thankfully I had the unedited saved in the system folder
Downloaded and installed the two updates successfully.
Checked with OTA and root was sill good.
Used Rom Toolbox Pro to install the latest TWRP
Great Success. Hopefully this little guide helps those in a situation similar to mine. Thanks to everyone who actually did the work figuring this stuff out, all I did was bring the pieces together. Also tried to keep it really really simple.
You had H-boot 1.12 and took an OTA??
A moment of silence please to mourn the loss of your 1.12 hboot.
:crying:
I wish you would've said something before attempting this. You could have just flashed everything from recovery and not lost your superior H-boot
You mean flashed a stock ROM based off the ota?
Sent from my EVO
ghostknyght said:
You mean flashed a stock ROM based off the ota?
Sent from my EVO
Click to expand...
Click to collapse
Flashed everything in the OTA (except for the 1.19 h-boot) from recovery so you still keep your unrestricted H-boot
I was under the impression that it was impossible to install everything but a specific hboot. In any case I just posted this because out took me a bit to bring all the different parts to accomplish specifically what I wanted. I figure someone else will get some use out of it. I knew what I was sacrificing, and risking and I'm cool with that.
Sent from my EVO
Hi guys i just switched over from the charge and got my self a rezound. i bought the phone used off of amazon (turned out to be quite the mistake) and was on gb 2.3.4 when it came. so first thing i went to do was to update to ics. I tried the ota update from the phone and most of the time i got "server unavailable" or it would show up in my notifications and would just never start to download. so now im stuck i am guessing the previous owner had to phone rooted and modded or something? i boot my phone into recovery and this is what it says
***** LOCKED *******
VIGOR PVT SHIP SL-ON RL
HBOOT-2.11.0000
eMMC-boot
oct 6 2011,15:4322
HBOOT
VOL UP
VOL DOWN
POWER
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
What happens is that the owner did root and did an unroot and now you cant root again happened to me when i bought and inc 2 off amazon and was stuck with the gb 2.3.4 so i think the same happened to you try looking around and trying every root solution and maybe it will work
Is that a typo or does it actually say SL-ON? Should say S-ON. If it really says SL-ON then it was def messed with.
Since it has GB on it it's very likely it was never unlocked and rooted. If it had been rooted I would think the previous owner would have updated it.
If it was s-on and had been unlocked and rooted it would say ***RELOCKED***. Since yours says ***LOCKED*** I think it wasn't rooted before. It's possible that they did the s-off wire trick and then went back to s-on, I think, I'm not sure what the phone would show in bootloader if they did that, but I think it looks like it has never been unlocked.
Regardless, if you want to update to the latest official OTA you can run the 3.14.605.12 RUU from here:
http://androidfiles.org/ruu/?dir=Vigor
That will get you up to date as of a month ago and fully stock. (sorry if you know this, I don't know what your experience is)
Make sure you let it run through a couple times on its own, when it's done it will leave you back in bootloader. The screen will go black for a bit, don't do anything, just leave it, it will go through updating a second time, just make sure you don't interrupt it.
Then you can try to take the OTA from about a month ago which will take you to 3.14.605.13. From what I've read there's not much to that OTA so if you can't take that for whatever reason it's no big loss.
Then if you want to root you'll need to unlock the phone via HTCDev, flash a recovery then root.
feralicious said:
Is that a typo or does it actually say SL-ON? Should say S-ON. If it really says SL-ON then it was def messed with.
Since it has GB on it it's very likely it was never unlocked and rooted. If it had been rooted I would think the previous owner would have updated it.
If it was s-on and had been unlocked and rooted it would say ***RELOCKED***. Since yours says ***LOCKED*** I think it wasn't rooted before. It's possible that they did the s-off wire trick and then went back to s-on, I think, I'm not sure what the phone would show in bootloader if they did that, but I think it looks like it has never been unlocked.
Regardless, if you want to update to the latest official OTA you can run the 3.14.605.12 RUU from here:
That will get you up to date as of a month ago and fully stock. (sorry if you know this, I don't know what your experience is)
Make sure you let it run through a couple times on its own, when it's done it will leave you back in bootloader. The screen will go black for a bit, don't do anything, just leave it, it will go through updating a second time, just make sure you don't interrupt it.
Then you can try to take the OTA from about a month ago which will take you to 3.14.605.13. From what I've read there's not much to that OTA so if you can't take that for whatever reason it's no big loss.
Then if you want to root you'll need to unlock the phone via HTCDev, flash a recovery then root.
Click to expand...
Click to collapse
thanks for the quick responses and it was a type o. i flashed the ruu and am now running 4.0.3 thank you very much
i have the tools to unlock and know how to do it but im not sure about the recovery or s-on/s-off i know what it is im just not sure if i wanna take it off and with the recovery is there a certain one i have to use or is there one that works better than all others? id like to find a rom that is s-on compatible and looking through some of the threads and some have 300+ pages so anything to lightin up my reading load would be greatly appreciated
Hi guys, I just bought my DNA last week and its running 1.15 (keep deferring update) and I had a few questions about rooting and s-off.. I'm coming from a droid X which was my first and only android phone for the past 3 years and it was a lot different. Lots of this is new to me..
I am interested in unlocking and getting s-off as well as flashing a custom kernel and rom with root. I see that 2.04/06 have no s-off yet. If i get s-ff and unlock on 1.15, and then update to 2.xx will the unlock be retained or is there a method by which i can re-unlock it?
So far from my current searching and reading, I *think* the correct procedure I'm supposed to go through is to unlock, install a custom recovery, s-off, and then custom kernel, and custom ROM flash. I suppose in this case the OTA 2.xx update would be irrelevant because I would be running a custom ROM anyway? Would I need to flash any radios or anything like that or would that be up to date with a ROM?
Thanks!
If you go through with the s-off and do an official update, you should be able to re-root the phone. ive seen alot of that been said around the forums. i'm curious why u would go with the official update after rooting though?
I guess I wouldn't really use OTA. I was thinking maybe I would keep the phone stock a while longer since I've only been using it about a day or two. I wanted to stay "up to date" in the sense that I'd be using a 2.04 based ROM rather than a 1.15 based one. I don't really know much about the changes between the versions though so maybe that doesn't really matter. I guess since I am on 1.15 I can root and unlock the phone as normal then with the various instructions around here. I should do that quickly cause Htc_dm keeps trying to push updates to my phone literally every time i turn on the screen and the phone is not gong to sleep at ALL.
I've come to see my question was kind of pointless after deciding to use a new ROM. Wasn't very well thought out at 3 in the morning
saa1993 said:
I guess I wouldn't really use OTA. I was thinking maybe I would keep the phone stock a while longer since I've only been using it about a day or two. I wanted to stay "up to date" in the sense that I'd be using a 2.04 based ROM rather than a 1.15 based one. I don't really know much about the changes between the versions though so maybe that doesn't really matter. I guess since I am on 1.15 I can root and unlock the phone as normal then with the various instructions around here. I should do that quickly cause Htc_dm keeps trying to push updates to my phone literally every time i turn on the screen and the phone is not gong to sleep at ALL.
I've come to see my question was kind of pointless after deciding to use a new ROM. Wasn't very well thought out at 3 in the morning
Click to expand...
Click to collapse
Soff immediately. If you like sense try newts or viper Rom, if you like a real Android experience I recommend cm or pac.
Sent from my HTC6435LVW using xda app-developers app
I unlocked the phone with supercid today and confirmed thats working. Tried doing soff with the facepalm method but am having no luck. The first time I got error 92, but after completing the process the bootloader still shows S-ON. on following tries, i always got error 99. Cleared cache did system wipe, never got error 92 again.
since some people had some luck with custom kernels and roms, I flashed NOS M7 rom and the LK kernel and still never got error 92. cleared cache/etc again and still cant get error 92. after i do boot dna-rescue.zip it hangs at the black htc screen a long time and eventually reboots. I was in the IRC channel a while but I don't think anyone else was there haha.
I'm at a loss of what to do, I've tried many times... I do not have a nandroid backup- of stock but i do have a clean backup of after i installed the new rom and kernel. I have unlock and root... no S-OFF which I would like...
according aygnsl
saa1993 said:
I unlocked the phone with supercid today and confirmed thats working. Tried doing soff with the facepalm method but am having no luck. The first time I got error 92, but after completing the process the bootloader still shows S-ON. on following tries, i always got error 99. Cleared cache did system wipe, never got error 92 again.
since some people had some luck with custom kernels and roms, I flashed NOS M7 rom and the LK kernel and still never got error 92. cleared cache/etc again and still cant get error 92. after i do boot dna-rescue.zip it hangs at the black htc screen a long time and eventually reboots. I was in the IRC channel a while but I don't think anyone else was there haha.
I'm at a loss of what to do, I've tried many times... I do not have a nandroid backup- of stock but i do have a clean backup of after i installed the new rom and kernel. I have unlock and root... no S-OFF which I would like...
Click to expand...
Click to collapse
edit for anyone who reads this in the future: make sure fastboot is off thats what worked for me.
If you woukdnt mind since you kinda fixed/answered your own question... Click edit on the first post and then go into advanced edit and put solved in the title so people know that you are no longer asking anything thanks
Sent from my HTC6435LVW using XDA Premium HD app