Hello all, I'm new to this site and I've never rooted a phone. Actually, the Eris is my first smartphone. I've read a lot of forums about rooting the Eris and from what I understand I shouldn't have installed the 2.1 ota update. I bought this phone soon after they were released so maybe I have a 1.47 hboot? I'm unsure how to check this, but if so does this mean I can root using the 1.5 method?
I just bought a class 6 8GB microsd card with the hopes of installing a custom rom, overclocking, and installing apps2sd. Now I'm getting very discouraged because it seems 2.1 can't currently be rooted.
Hopefully a senior user can help me out. Please put your response in lamens terms. I've seen some other forums where junior users are getting bashed for asking stupid questions so I'm putting it out there....please don't bash me for this one.
http://forum.xda-developers.com/showthread.php?t=684049
everything you need and more. To answer your next question. As long as your phone was never updated with leak, the process for root of 1.5 and 2.1 are the same.
happy rooting!
Thanks Spencer! If I root using the method at that page will I be able to flash other roms or will I be stuck with this 2.1 ROM? I'd like to install the evileris rom and (again I'm a newbie) I don't want to end up stuck like the people who installed the leaked 2.1.
you should be able to flash a custom rom to the phone as i believe you have to first load a custom recovery image to it. i could be wrong though just a guess.
SDK Not Working?
HELP!! I just rooted my phone, installed java, installed SDK and I can't get the command prompts to work. I followed the steps exactly (or so I think) and I'm opening sdksetup.exe. When I try to type I get nothing. Am I opening the wrong file or doing something wrong. I've not been able to install the recovery or custom rom to my phone yet, so I'm very vulnerable right now. Any ideas anyone?
Ok, maybe this is my problem...
Before the root, I could go into device manager from my computer and I got a yellow exclamation mark. After the root, I cannot find it. I can click on portable devices and it shows an Android Phone so I'm guessing my computer doesn't recognize it anymore. If that's the case I probably need to update the driver for SDK to work, but I need to find the device for that to work. I have USB debugging on. Any help is appreciated.
If it says android phone with no exclamation point that means it is recognized. Its when there is an exclamation point that means it is not recognized. I probably won't be able to help you further because I'm a rooting noob (I've only rooted my Eris and I had no problems) but I am a computer expert and I would suggest rebooting your computer and then trying it again... unless you already have.
-------------------------------------
Sent via the XDA Tapatalk App
joshw0000 said:
HELP!! I just rooted my phone, installed java, installed SDK and I can't get the command prompts to work. I followed the steps exactly (or so I think) and I'm opening sdksetup.exe. When I try to type I get nothing. Am I opening the wrong file or doing something wrong. I've not been able to install the recovery or custom rom to my phone yet, so I'm very vulnerable right now. Any ideas anyone?
Click to expand...
Click to collapse
What exactly do you mean when you say "I can't get the command prompts to work"?
joshw0000 said:
HELP!! I just rooted my phone, installed java, installed SDK and I can't get the command prompts to work. I followed the steps exactly (or so I think) and I'm opening sdksetup.exe. When I try to type I get nothing. Am I opening the wrong file or doing something wrong. I've not been able to install the recovery or custom rom to my phone yet, so I'm very vulnerable right now. Any ideas anyone?
Click to expand...
Click to collapse
Ok, calm down its not the end of the world, i ran into the same problem. What we need for us to help you, is at what point are you in trying to root your phone. Do you have SDK installed and updated?
I'm following the how to root instructions. I've completed I: Gaining Root and made it to 9. In II: Prerequisites. Java and SDK are both saved and extracted on my c: drive. I downloaded the USB drivers package in #6 of II. USB debugging was enabled and the phone was set to charge only. When I opened device manager on my pc, their was no yellow exclamation like the instructions indicated. I clicked on "Android Phone" and attempted to update the drivers found in SDK but Windows said they were up to date. I moved on to step III. Flashing a Custom Recovery and saved the zip file to my SD (should I save that to my c: drive?). I extracted it to tools in Android SDK and attempted to use the command prompt in SDK. It was unresponsive. It did not recognize my phone. I'm unsure if it does that automatically, if I need to take action, or if I should use the pc command prompt.
I went back to #9 of II and tried to troubleshoot. I tried every way I could think of to get the exclamation mark to show up in device manager so I could update the USB drivers. I hooked up my wife's unrooted Eris and it had the exclamation. I restarted my phone, restarted my computer, reflashed PB00IMG.zip and still had no luck.
Anybody had this probem? Any suggestions?
Related
I recently returned my phone to Gingerbread EH03 and am wanting to root and install a new custom ROM.
I have rooted before but as you can tell am currently unrooted, I have tried both the one-click and the usual command prompt rooting process but neither works.
After I type "./rage.bin" and it restarts adb my phone is no longer recognized when I type "adb devices". I've tried unplugging it and plugging it back in but then it wont be recognized and I have to pull my battery out but this happens each time and I can't find a way around it. Debugging was on, current drivers, etc.
And help?
if your flashing a custom rom there is no need to root. But if you insist on rooting, try this method in section5 of my guide.
http://forum.xda-developers.com/showthread.php?t=1238070
codylicious9 said:
I recently returned my phone to Gingerbread EH03 and am wanting to root and install a new custom ROM.
I have rooted before but as you can tell am currently unrooted, I have tried both the one-click and the usual command prompt rooting process but neither works.
After I type "./rage.bin" and it restarts adb my phone is no longer recognized when I type "adb devices". I've tried unplugging it and plugging it back in but then it wont be recognized and I have to pull my battery out but this happens each time and I can't find a way around it. Debugging was on, current drivers, etc.
And help?
Click to expand...
Click to collapse
Why are you trying to eat pizza with chop sticks?
superclean eh03, TKSGB1118
laureanop said:
Why are you trying to eat pizza with chop sticks?
superclean eh03, TKSGB1118
Click to expand...
Click to collapse
it look like he might be trying to demonstrate chop stick skills.
You only need root on stock roms if you are keeping them OR if you are trying to install recovery via Clockworkmod app. Other than that, most ROMs come with superuser already enabled. The MIUI is the only one I know that you have to actually enable the superuser ability in the settings.
But with these phone's it looks like all you need is a good recovery .tar file and odin. Now, i'm kinda new with this phone, but I have been through at least 10 droids. So I'm not quite sure. I keep asking everyone but I will get a new answer for each person I ask.
So the basic message I'm trying to convey is USE ODIN TO FLASH A RECOVERY and then you can load any rom you want which will have superuser. But recovery is what u want bro, i just dont know how to go about it.
I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
The best guide ever is in the development section, it works for your device.
http://forum.xda-developers.com/showthread.php?t=1239185
follow the guide its very easy and worked fine for me
I Return triumphant, and gentlemen, i must say you were incorrect.
The I/O edition does not give you the option to access recovery at any point, even with the Pwr+VOL DN boot.
You can put it into download mode, and certianly use ODIN to install the recovery rom, but you will have no method to actually access recovery to push zip files.
thanks to some quick self education on using fastboot, i was able to root successfully.
To those of you in a similar situation who stumble upon this thread, i invite you to visit:
http://droidbasement.com/db-blog/?p=2439
There you can download CWM in a .img format for use with fastboot.
This link is where you can download fastboot:
http://forum.xda-developers.com/attachment.php?attachmentid=596615&d=1305443483
and you'll need to install PDANet for Android to get the fastboot drivers:
http://junefabrics.com/android/
I belive you'll also need ADB installed from the Android SDK. i do have it installed on this computer, but did not use the ADB command at any point, just fastboot.
Instructions:
1. Download fastboot, PDANet for android, and the recovery image. You'll also need "Samsung_Galaxy_Tab_10.1_root.zip" found in Root.zip from the retail version instructions.
2. Copy the "Samsung_Galaxy_Tab_10.1_root.zip" to the tablet, and and power it off. Disconnect the USB connection
3. Unzip fastboot zip into it's own folder, and then copy your recovery.img file into the same folder.
4. Start the install of PDANet. It will ask you if you want to install drivers about half way through. say yes, and select "Samsung" when the time comes. it will install some drivers and then ask you to try and connect. windows may flare up and say they're unsigned. accept anyway.
5. watch this friendly video on how to start fastboot on your tablet:
http://www.youtube.com/watch?v=sR7vE4IueaU
"fastboot!"
Basically the same as the steps outlined for the retail version, but you will go to the usb icon instead of the box.
6. once the tablet is in fastboot, connect the USB cable. PDA net will recognize it as an ADB connection and try and load itself. it will fail, that's fine. Let the installer exit completely.
7. Open a command line in windows, and get it to the directory fastboot.exe and your recovery image are in.
8. run your fastboot command. i only used it temporarlily, so my command was:
"fastboot boot recovery-cwm_5.0.2.7-sam-tab-10.1.img"
9. the tablet should now boot into the recovery image presented. hooray! follow the remaining instructions from the retail version root, using recovery to load the "Samsung_Galaxy_Tab_10.1_root.zip" and reboot.
10. Once you've done all that, select to reboot. The tablet will reboot. i took the opportunity to disconnect the cable.
11. "Superuser" should now be in your apps, and you're rooted!
Extra Step: Download "Rom Manager" by clockwork from the android market, and install it. from here, opt to flash recovery. Once that's complete, you can now access recovery by launching that program and simply hitting "Reboot into Recovery"
I have no use for this myself but it's not often someone comes back and posts a complete howto on solving their own initial issue. I wish more people would do this. Thanks button clicked.
I just ran into this exact problem and only found this thread after figuring it out on my own. I figured my IO tab just didn't like having clockwork mod installed, but it certainly booted it. I nearly ruined it by accidentally wiping my rom trying to get it to boot at all. I had to repush my install files to the insternal memory using adb after I was able to boot into recovery with fastboot.
I haven't looked around too much (seeing as I only JUST got the damn thing to boot a rom) but is there a fix to that, perhaps installing the retail bootloader?
I'd hate to have to use fastboot everytime my rom doesn't boot. I've gotten used to wiping and installing roms from wherever I am on my other android devices.
I'm not familiar enough with the device to be able to give you a definite answer, but i imagine adding a bootloader from the retail version would give you the recovery option instead of fastboot.
personally, i'm a little more fond of having fastboot around right now, as it's easy enough to get into recovery when flashing things with it, and the bootloader for the I/O is unlocked... i can think of a few fun things to do in the future if i can load any ROM i want into memory, test it, and move on if it's no good... i may even give some of the ICS dailies a try thanks to this.
Always several ways of doing things... glad you got it worked out.
http://forum.xda-developers.com/showpost.php?p=15735928&postcount=2
RootzFan,
that method is flashing an entirely new rom, down to 3.0, just to gain root access and open recovery so you can then return to 3.1.. it has the added byproduct of installing touchwiz.
IMHO, my way is a little cleaner as there is actually zero flashing needed, and you get to keep everything active and installed.
i recommend just going for custom roms - it comes already rooted - yBoot into recovery and flash a custom ROM
I have the IO tab myseldf and have been flawlessly running GalaxyTask custom ROM - http://forum.xda-developers.com/showthread.php?t=1340064
shane86 said:
I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
Click to expand...
Click to collapse
oh, def not the best method... just saying it is nice that there are alternatives.
self delete
Fun Stuff.
(i made sure to do a backup)
Let me sum up what I have done:
I've managed to follow a guide on a wiki(I lost the link however, since I ATTEMPTED to give up on this) that involved me downgrading my firmware, then do some steps to install cyanogen 1.4. Afterwards, I got to step that required me to rename some file to update.zip. I followed that step and noticed my computer didn't convert the file to a zip file(it remained as a img file) but continued anyway while finding that odd.
Afterwards, cyanogen tells me that it cannot find the zip file. I've search most of google and a bit of this site, and i've seen various solutions that failed me such as:
-renaming the update.zip to update
-using android sdk(which i have no clue on how to use)
Anyways, finding out that I was foolish to do all of this without prior knowledge, I decided to go back to my original firmware. However, on the phone's reboot, cyanogen came up again for some reason, and didn't let the update be applied.(I don't recall the error)
Anyways, I selected reboot and got to my phone's main menu then some music started playing automatically. I should note, before I did the update, I placed all of my backed up data(while still having the original copy on my pc) on my phone so it might've been some music that the original owner had. Now, on the menu, i'm getting this error "The process android.process.acore has stopped unexpectedly. Please try again." all the time. Since this error constantly pops up, I can't do anything.
So if you managed to read my long and boring story, let me ask one question:
How do I get my phone back to normal if rooting is impossible at this point?
First question is what firmware is your htc magic currently on? And by reading everything I guess your phone isnt rooted...
Dataslycer said:
First question is what firmware is your htc magic currently on? And by reading everything I guess your phone isnt rooted...
Click to expand...
Click to collapse
It's on 1.5 currently. Also as a little update:
I fixed the "not being able to do anything on the menu" problem by doing a factory reset. Afterwards, I learned the SDK a little bit more and have the tools, pc driver, and fastboot on my pc. However, i'm getting the error:
FAILED (remote: not allow)
Just a bump. I need all the help I can get on this one. Even a premade update.zip would help me GREATLY.
One last bump. I promise.
I'm new to this whole Android scene, been an Apple user my whole life. I know the ins and outs of iOS and jailbreaking, but i can't figure out how to root my device for the life of me!
I've looked through Google and found this (bin4ry's recovery), which picks up my device, and I get the screen on my phone saying restore, which I click. Then it comes up with "Starting restore", before coming up with "Restore ended" a few moments later. After that the program just sits there, obviously failing to root the device.
I've also read through this thread but didn't understand any of it, and attempts to follow instructions given were all dead ends
Any help would be much appreciated.
Cheers
What type of phone, and what android version..?
Miniricho said:
What type of phone, and what android version..?
Click to expand...
Click to collapse
Alcatel OT-993
Running Android ICS 4.0.4
Ultim8um said:
Alcatel OT-993
Running Android ICS 4.0.4
Click to expand...
Click to collapse
Have you tried cd (change directory) into the folder where your bin4ry restore is located?
Commonly happens to most phones, there's a video on the site where you download it from.
Also that russian page is for installing CWM (clockworkmod recovery) And you need to be rooted in order to do that.
Miniricho said:
Have you tried cd (change directory) into the folder where your bin4ry restore is located?
Commonly happens to most phones, there's a video on the site where you download it from.
Also that russian page is for installing CWM (clockworkmod recovery) And you need to be rooted in order to do that.
Click to expand...
Click to collapse
Ah that explains why I couldn't follow it. Cheers
Also I presume you mean in the command prompt?
puu(dot)sh/2EfaU(dot)png
Would that be correct? Because that is how I have done it every time
EDIT: This is the step it stops on. puu(dot)sh/2EfpJ.png I click restore on my phone and as stated in the OP it starts and ends the restore instantly
Are you sure your phone is rootable via this method?
Miniricho said:
Are you sure your phone is rootable via this method?
Click to expand...
Click to collapse
Its the only method that comes up when searching for my phone, but no I'm not sure. If you know any other methods that work that would be wonderful
Maybe just try some of the most popular methods like unlockroot, or superoneclick,
if all else fails, make sure your drivers are installed correctly, and keep trying and searching around. Good luck.
Same problem
-Ran the latest version of Bin4ry on my Alcatel OT-993 running unrooted Android 4.0.4.
-The script seems to run correctly and I'm able to click the Restore button but it wont reboot the the phone.
-When I manually switch of the phone it displays that the script was successful and says its waiting for the device to reappear.
-When the phone is switched on again the script finishes but says im not rooted
Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Update: I've finally figured out how to get the TWRP recovery booted. Now working on trying to get my phone to boot up an OS of some sort. Very slowly but surely.
bullmurf said:
Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Click to expand...
Click to collapse
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Addicted2xda said:
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Click to expand...
Click to collapse
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
bullmurf said:
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
Click to expand...
Click to collapse
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Addicted2xda said:
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Click to expand...
Click to collapse
"use sideload to copy / install a custom ROM..." OK I don't know anything about this but it will point me in the right direction. I have the phone unlocked. The HBOOT version is 1.40.0000. I'll see if I can do what you suggested, thanks.
Update: Atempting an adb sideload using TWRP which seems to be the only option for me.
ADB Sideload
What is ADB sideload?
--------------------------------------------------------------------------------
ADB sideload is a new feature that was added to AOSP recovery in Jelly Bean. As of version 2.3, TWRP now supports ADB sideload mode. ADB sideload is a different ADB mode that you can use to push and install a zip using one command from your computer. Most likely ADB sideload won't be very useful for your average recovery user, but ADB sideload can be a huge time-saver for a ROM developer.
How do I use ADB sideload?
--------------------------------------------------------------------------------
1.Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher
2.Have newer ADB binaries installed on your computer. If it's been a while since you installed ADB on your computer, you may need to get the latest ADB binaries in platform-tools from the Android SDK. You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line.
3.Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
4.From the command line, type adb sideload /path/to/rom.zip
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Note that sideload mode is a separate ADB mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.
Click to expand...
Click to collapse
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
bullmurf said:
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
Click to expand...
Click to collapse
Update: after trying the same thing 100 times it decided to send "sideload". command line was adb sideload name.zip. Installing Viper ROM for HOX+ atm. I'll see if it fixes all of my problems. Thanks for all of the help to this point. I'll type up a guide of what went wrong with my root and how we managed to get it fixed.
Update: Phone is booting to HTC white screen and then shutting off. Now trying to figure that one one out.
Update" Phone is booting to HTC white screen now and staying there. In TWRP under reboot is says "no os installed, do you still wish to reboot". Still digging in the forums to figure this one out and how to fix it. I installed the Viper ROM fine but when it asked to reboot now it just rebooted to HTC white screen. Missing something here? The phone is S-ON, does that make a difference in using the TWRP?
Is there an RUU exe file I can run from my computer? I relocked the phone but the links you gave me are for installing the ap through google play. Not sure how you do that with a phone that wont boot past htc screen.
Update: I've found an RUU application from these boards that is supposed to work for HOX+ so i'm downloading it. It really is taking forever to find the information I need along the way from this board but it's here....somewhere...I think...Will keep plugging away but feel free to throw me a bone ever once in a while! =)
Update: The version that worked for others isn't the same version I have. Going to dig again for 1.19.502.1 version.
Update: Found the version in the last place I thought it would be...HTC website...Downloading it and just hoping its and application I can run on my computer.
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
I would suggest you to use hasoon's all in one toolkit
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
bullmurf said:
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
Click to expand...
Click to collapse
There is a great lockscreen called CLocker
Addicted2xda said:
There is a great lockscreen called CLocker
Click to expand...
Click to collapse
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
bullmurf said:
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
Click to expand...
Click to collapse
You will find it in the playstore itself
You need to set lockscreen to None
Addicted2xda said:
You will find it in the playstore itself
You need to set lockscreen to None
Click to expand...
Click to collapse
Thanks again man. I got it and the ring is gone \0/ Phone looks freakin amazing now with that lock screen and Elegancia rom. Glad you stopped by to help :good: Still learning my way around the forums and my rooted phone. It's great to not be stressed about bricking it ^^
suppils soars
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
mrmagoogt said:
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
Click to expand...
Click to collapse
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Addicted2xda said:
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Click to expand...
Click to collapse
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
mrmagoogt said:
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
Click to expand...
Click to collapse
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Addicted2xda said:
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Click to expand...
Click to collapse
Thanks, I used a script to charge my battery, relock bootloader and installed ruu file to get back to stock, rooted again using Hasoon2000's all in one kit...