Related
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.
Hello. So I've tried multiple times flashing ROMs to my device, and have always had problems somewhere along the line. The furthest I got was successfully flashing this ROM, but it ended up in a boot loop. I believed it was due to my device being S-ON, even though I've successfully rooted and unlocked my bootloader via HTCdev and thus I've been attempting to get S-OFF. I tried JuopunutBear but got an error message related to checking my adb and fastboot drivers (Which I'm fairly sure are up to date and working) and I think the problem is I am on HBOOT 1.57. I've been attempting to downgrade using this guide (Which uses Revolutionary to get S-OFF in which case I wouldn't need JuopunutBear). I only got a bit of the way in, however, before I got stuck. After relocking my device it tells you to put the RUU zip on your device, but my computer isn't detecting my device and I'm stuck in the bootloader. I've tried shutting it off, trying all the options in the bootloader, taking out the battery, entering commands into adb, and probably some other things I've forgot, but I'm still stuck on the bootloader and my device isn't detected at all on my computer (Either in command prompt or in the explorer window).
Essentially what I'm asking here is:
How do I get my phone unstuck from bootloader?
Do I need S-OFF to be able to flash ROMs?
If I don't need S-OFF, what was I doing wrong? Should I try a different ROM?
And I suppose I may as well ask if that's a worthwhile ROM. I want something that optimizes my device and allows for custom themes, but otherwise I'm not too picky.
Specs:
Windows Vista (With ADB and fastboot, as well as HTC Sync and other phone drivers. Essentially I think I have all the software I'd need installed.)
HTC EVO 3D CDMA with Virgin Mobile as the carrier.
HTCdev unlocked bootloader
S-ON
HBOOT 1.57
Stock ROM
4ext recovery
Any and all help would be greatly appreciated!
(Also I apologize if I didn't give all the information needed or if I posted this in the incorrect spot. I figured this would be the most appropriate spot since although I have issues with specific processes it's also a fairly general request for help.)
UPDATE: I tried re-unlocking my phone using HTCdev so I'm no longer stuck in bootloader. I'm going to be trying the HBOOT Downgrade Toolkit guide again sometime today or tomorrow to see if I can get it working. I think one of the problems before was that I didn't put the RUU on the sdcard beforehand and then my device wasn't being recognized so i couldn't put it there then. If I put it on beforehand I should be able to update successfully and get past the step I was stuck on before.
If you're son u can only flash sence ROMs.
Sent from my PG86100 using xda app-developers app
cj_302 said:
If you're son u can only flash sence ROMs.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Er, I'm not quite sure what you're saying here.
UPDATE: I tried re-unlocking my phone using HTCdev so I'm no longer stuck in bootloader. I'm going to be trying the HBOOT Downgrade Toolkit guide again sometime today or tomorrow to see if I can get it working. I think one of the problems before was that I didn't put the RUU on the sdcard beforehand and then my device wasn't being recognized so i couldn't put it there then. If I put it on beforehand I should be able to update successfully and get past the step I was stuck on before.
It will be your hboot causing the problems.
Most recoveries allow you to mount usb storage so you can use that option to connect to your pc and move the ruu across without removing your sdcard etc.
Download G Cloud Backup for Android, up to 8 GB Free.Use this code: [KWLYRO] at signup and we'll both earn space: https://play.google.com/store/apps/details?id=com.genie9.gcloudbackup
Hey guys I've been trying to get my phone reset back to stock, I was coming from a rooted stock 3.15 and did what this thread said http://forum.xda-developers.com/showthread.php?t=1706070 to get the RUU to run, after running it. My phone was restored to normal except my sdcard still had everything on it (I think this is expected) and the main issue is that SuperSU was still installed. While my phone was at this state my girlfriend changed the theme of the phone to something else, the only reason I'm saying this is because after running VipeRUU the theme was still the one that was set.
So after that I booted up my phone and ran VipeRUU http://forum.xda-developers.com/showthread.php?t=2197909 and still it worked but again SuperSU was still installed.
Going into my bootloader at this point reveals Tampered and Relocked and S-On, hitting recovery takes my phone to the htc boot logo then a black screen with a red exclaimation mark over a phone. Hopefully someone can help me getting my phone back to 100% stock.
I am currently trying the fix in the sticky with the 3.15 ruu.
After flashing the zip like it says to, the htc sign has a green bar under it that looks nearly full. I tried to run the RUU at this point and it went a fair amount through and stopped eventually due to a usb connection error (I think when the phone switched into fastboot). So I did the fix again and when it got to the green bar I rebooted the phone and am now running the RUU.
Blowdryer said:
Hey guys I've been trying to get my phone reset back to stock, I was coming from a rooted stock 3.15 and did what this thread said http://forum.xda-developers.com/showthread.php?t=1706070 to get the RUU to run, after running it. My phone was restored to normal except my sdcard still had everything on it (I think this is expected) and the main issue is that SuperSU was still installed. While my phone was at this state my girlfriend changed the theme of the phone to something else, the only reason I'm saying this is because after running VipeRUU the theme was still the one that was set.
So after that I booted up my phone and ran VipeRUU http://forum.xda-developers.com/showthread.php?t=2197909 and still it worked but again SuperSU was still installed.
Going into my bootloader at this point reveals Tampered and Relocked and S-On, hitting recovery takes my phone to the htc boot logo then a black screen with a red exclaimation mark over a phone. Hopefully someone can help me getting my phone back to 100% stock.
I am currently trying the fix in the sticky with the 3.15 ruu.
After flashing the zip like it says to, the htc sign has a green bar under it that looks nearly full. I tried to run the RUU at this point and it went a fair amount through and stopped eventually due to a usb connection error (I think when the phone switched into fastboot). So I did the fix again and when it got to the green bar I rebooted the phone and am now running the RUU.
Click to expand...
Click to collapse
You will need to get s-off again and then use VipeRuu to remove s-off and the tampered message... I know it doesn't make sense but that's the only way to do it since there is no official ruu for 3.16...
Sent from my EVO using xda app-developers app
Anybody here successful in using RumRunner on T-MOBILE HTC-ONE? (with 1.55 HBOOT and 3.24 firmware)?
Steps I performed..
1) Unlocked Bootloader (with HTC DEV)
2) Installed Team Win Recovery
3) Installed SUPER SU from Recovery
4) Using T-Mobile 4.3 ROM (from HTC T-MOBILE RUU)
6) Disabled Firewall (Windows 7)
7) Uninstalled Anti-Virus (Microsoft Security Essentials)
8) Installed HTC Sync (for Drivers only - uninstalled right after)
9) Rebooted PC
10) Disabled Lock Screen (no lock screen on HTC ONE)
11) Made sure fastboot was disabled
12) Made sure usb debugging was enabled
13) Made sure "Verify Apps" was unchecked
14) Made sure "Unknown Sources" was checked
15) Told Super SU to automatically grant super user privileges WITHOUT prompting
16) Ran soju in "administrator" console
It does it's thing and reboots several times but it fails with the following
"FATAL: Download updated package at www.rumrunner.us"
I also tried the same thing with the Android HD Revolution ROM (4.3 - ver 31.6) - fails at the same spot (installed via Recovery). I am able to get to www.rumrunner.us without issues and i'm using ver 0.5..
Note: adb Commands Work, fastboot commands all work..
Same sh*t...cant proceed above this point.
Just did it earlier this week. It ran fine for me.
All I did was unlock, root, done. I was on stock T-Mobile 4.3
Successfully done with the international one :highfive: tough i had some problems on the adb connection. maybe just try to reinstall the drivers..
000zui said:
Successfully done with the international one :highfive: tough i had some problems on the adb connection. maybe just try to reinstall the drivers..
Click to expand...
Click to collapse
Just did one just now actually
1) download the universal option
2) unlock bootloader, twrp and root
3) ran on Linux went through perfectly
FWIW, I had no issues doing it with Windows. T-Mobile (PN07130) [previously] bone stock.
any updates on your side @funks?
@ownmart , @850csi , @omgar , @000zui ??? are you running with hboot 1.55 when you did it?
i have an hboot 1.55 with 3.24 firmware too... same problem.
still cant get past that FATAL error.
tried also all the steps on different PCs.
finding to S-Off this very frustrating. haha.
-SS-
@SilverSamurai have you tried using Linux? That's what @funks did and it worked for him. See my thread about GPE conversion for a link to his post. I was hboot 1.55 and it worked perfectly for me on Windows 7. Are you sure your antivirus/firewall is disabled completely?
Perhaps there's some kind of firewall built into your router or modem that's messing with rumrunner? If you're using different PCs on the same network with that result, this could be what's going on.
Not an expert at all on this, just throwing stuff out there.
SilverSamurai said:
any updates on your side @funks?
@ownmart , @850csi , @omgar , @000zui ??? are you running with hboot 1.55 when you did it?
i have an hboot 1.55 with 3.24 firmware too... same problem.
still cant get past that FATAL error.
tried also all the steps on different PCs.
finding to S-Off this very frustrating. haha.
-SS-
Click to expand...
Click to collapse
Yeah, worked on the international one, hboot 1.55 & win7, don't remember on which fw. Though i had some problems until i uninstalled some Samsung USB drivers..
So yesterday I had my Aria in my pocket and I guess the power button got nudged and the screen turned on, lo and behold I pull my phone out of my pocket to find the lovely words written on the screen that too many pattern attempts have been attempted and that the device is locked. Only problem is I use this phone for everything but the phone function, I don't even have a sim in there. So with WiFi off, and no mobile network I was stuck for a bit. But then I finally sat down with it and luckily I had kept USB debugging on so I used adb to hack it. And that is where my urgent problem starts. After finally unlocking it I decided to might as well upgrade it, it was running 2.0.2 I believe Liberated ROM with CWM. So I started browsing around because I haven't really worked with this phone before all that much, I ended up reflashing to stock rom and then was going to use a nifty tool to get my hboot to 1.02, well it worked, the nifty tool flashed my hboot alright, along with my ROM and everything else there was. I am now stuck with a brick, the phone goes to the boot logo and then reboots... over and over and over until I pull the battery. I was charging the phone the whole time while working on it and after the tool was done flashing the hboot I unplugged the phone and a long list of errors ran down the screen of files that the OS was missing. I can get into fastboot, haven't had luck with any reflashs, adb is dud (while in recovery computer recognizes the adb connection but adb only lists the device as inactive. Ever since I lost my Inspire 4G this was my only working mobile device. If you have any tips tricks or clues as to how or if it is possible to come back from this destruction I am all ears.
Thank you in advance :fingers-crossed:
To clarify a bit further, the part that screwed me was the Upgrade HTC Gratia HBOOT for AlpharevX S-OFF tool. It was chugging along just fine up until the very end. The original sites listed for making a gold card are all dead but I managed to find a working one. Now I am trying to figure out what went wrong and why.
LIBERTY PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-031b
TOUCH PANEL-STN21_03
RADIO-7.13.35.13
Nov 4 2010,23:12:58
The time and date are frozen
First you should S-OFF your phone with revolutionary. Then you need to flash a working recovery image and reflash ROM from there. Should work. If this still doesn't work, flash a modified hboot from the Development forum and see if you have any luck with that...
dansou901 said:
First you should S-OFF your phone with revolutionary. Then you need to flash a working recovery image and reflash ROM from there. Should work. If this still doesn't work, flash a modified hboot from the Development forum and see if you have any luck with that...
Click to expand...
Click to collapse
I cannot get revolutionary to find the device, the system version is 2.37.709.11 and I cannot do anything, if I try flashing anything the sig verification always fails.
(EDIT: Well I got lucky, found an asian RUU with same version, reflashed phone, S-Off, flashed unofficial CWM recovery and unofficial cyanogen 11.)
The problem I was having with revolutionary not recognizing the device was because my hboot version was too old (0.57). I used this AT&T Update package to get back to stock 2.2 and revolutionary worked straight away.
HTC_Aria_for_ATT_Android_2.2_ROM_Update.exe
http://www.mediafire.com/download/mch2657rdy8aqct/HTC_Aria_for_ATT_Android_2.2_ROM_Update.exe