Hello everyone! I'm new to HTC and Android phones in general. I have a problem with my Rogers HTC Evo 3D, but I unlocked it.
The problem is that it won't turn on. All I see is the HTC logo with a white background and then a black screen. Then it repeats. This began happening after I updated through Wifi to 4.0.3. It powers down and will no longer start up again. I've researched on this topic but am unable to find a fix for this issue.
So on the HBOOT screen I see
UNLOCKED
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.49.0008
eMMC-boot
Jul 15 2011, 14:39:25
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
So I can't go into recovery or factory reset at all. In the recovery I just get an android phone with a red exclamation mark. For the Factory Reset, the phone just switches off.
I've tried to change the S-ON to S-OFF but revolutionary has the 'waiting for device' issue which I saw many people were having.
I wasn't even able to get a backup when the update happened. -_-
Any help?
RUU
have access to the bootloader? Rogers operates on a CDMA network? ok so look for the correct network packets RUU, I have GSM and packet looks like this PG86IMG.zip, throw it on the card and then turn on the phone in bootloader "white background and android at the bottom of fellows" package should she run, search for your network, see here http://forum.xda-developers.com/showthread.php?t=1447839
Or install recovery.img via fastboot if you boodloader is UNLOCKED, download CWM recovery or 4ext ,rename to recovery.img ,put in android fastboot and adb folder ,next go to folder in windows CMD ,"cd c:/android" and connect phone in fastboot mode
HBOOT
FASTBOOT <--------------------------
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
and in WIN cmd flash recovery from folder , "fastboot flash recovery recovery.img" and download system in zip and install in recovery ,
Rogers runs on GSM.
So basically I download a RUU file and rename it to PG86IMG.zip?
Does the RUU file stuff apart from the Carrier matter? There are like 5 or 6 rogers ones on the androidfiles.org website.
I tried the second method and tried using the wipe all data option. All I could see was a hat(?) with an arrow. No loading bar or anything. Is this how it's supposed to be? Does the phone have to be connected to my PC?
Sorry about the double post, but I didn't know that I could use the camera button as well. Now I'm in the process of wiping everything and doing a factory reset.
EDIT
Nope doesn't work. Still stuck in the boot loop. -_-
Thanks for the help!
Anyone able to help? Can't I just wipe everything off of my phone, including operating system, then reinstall it through my computer? Is there a backup available online?
I helped a person out earlier with the same exact issue. Find a stock rooted rom.Than put it on the sd card.Keep a copy on the desktop as well.
Boot into recovery. Cd c:\adb or android, you can name it spongebob as long as the right files are in it.So cd c:\adb than adb reboot recovery.Or pull the battery and hold volume down and power until your in the bootloader.
Next install the zip file with the stock rooted rom.Than once installed pull the battery and put it back in.go back to the bootloader, plug the phone back in.Than select fastboot and press power.
Next go back to the rom on the desktop open the rom look for the boot.img, put it in the adb folder thats in the c drive.Than in cmd type cd c:\adb
Than type
fastboot flash boot boot.img
Next go back to recovery wipe the cache, davilk cache and do the factory data/reset.
Than reboot normally the bootloop should end and it should boot up normally after a few minutes.
Back to business after becoming softbricked.Hit the thanks button if i helped!
Sent from my SPH-D710VMUB using XDA Premium HD app
worldwidehustling said:
I helped a person out earlier with the same exact issue. Find a stock rooted rom.Than put it on the sd card.Keep a copy on the desktop as well.
Boot into recovery. Cd c:\adb or android, you can name it spongebob as long as the right files are in it.So cd c:\adb than adb reboot recovery.Or pull the battery and hold volume down and power until your in the bootloader.
Next install the zip file with the stock rooted rom.Than once installed pull the battery and put it back in.go back to the bootloader, plug the phone back in.Than select fastboot and press power.
Next go back to the rom on the desktop open the rom look for the boot.img, put it in the adb folder thats in the c drive.Than in cmd type cd c:\adb
Than type
fastboot flash boot boot.img
Next go back to recovery wipe the cache, davilk cache and do the factory data/reset.
Than reboot normally the bootloop should end and it should boot up normally after a few minutes.
Back to business after becoming softbricked.Hit the thanks button if i helped!
Sent from my SPH-D710VMUB using XDA Premium HD app
Click to expand...
Click to collapse
Thank you! I followed the instructions and got through everything but my phone is still stuck in a bootloop though.
Could it be the fact that I have S-ON? I tried to obtain S-OFF but Revolutionary keeps on giving me the waiting for device.
EDIT
Ok so now I was able to use Revolutionary to 'connect' with my phone. Now I end up with an error like this.
Found your device: /sbin/sh: getprop: not found (/sbin/sh: getprop: not-/sbin/sh: getprop: not, Android: /sbin/sh: getprop: not, ROM version: /sbin/sh: )
Your device: /sbin/sh: getprop: not, with HBOOT /sbin/sh: getprop: not is not supported at this time. Press <almost> any key to exit.
I do know my HTC Evo 3D is supported though. -_-
Honestly it would be easier if you
p.m. me.I can answer and ask questions faster.If needed i can remote into your pc.
Sent from my SPH-D710VMUB using XDA Premium HD app
Related
I got the s-off files from xda and had no problems with turning it off. i then used the superoneclick method to root my HTC Aria running the OTA 2.2.2 att update. my phone is rooted, i have superuser and all is good..... except that when i try to go into recovery mode to install a custom rom it just gives me a failure screen of a phone and a red triangle with a red exclamation point in it. i have to take the battery out to reset the phone.
why wont it let me into recovery?
if anyone has some insight for me it would be greatly appreciated.
thank u
AlphaRevX doesn't install recovery automatically for you, but once you have S-OFF you can do it yourself. This post tells you what to do:
http://forum.xda-developers.com/showthread.php?t=1122694
thanks for the quick response.
i downloaded all the files (to windows computer) then extracted files. then i went and put my phone into fastboot usb.
i guess im getting confused on the next step. it says to fastboot flash recovery <recovery.img> from a command line <----- (not sure what the command line is)
i know about phones and apps but am just getting into roms and rooting.
sorry for having a blonde moment
Start > Run > Type "cmd"
Then from command prompt do:
Code:
cd C:\path\to\folder
fastboot flash recovery recovery.img
(replace C:\path\to\folder with the place you extracted the files)
I was unlocking the bootloader and at the last step my little son unplugged it.
So now when I power it on i see HTC logo for couple of second and then black screen.
Holding power +vol down takes my to hboot, but I am a total noob how to fix it.
BTW it sais unlocked and s -on
It is a best buy wifi only version
ADB doesnt recognize my flyer actually my computer doesn't recognize it at all
Any help please????
A little more info from holding power+vol down:
Unlocked
FLYER PVT SHIP S-ON RL
HBOOT-1.11.0011
MICROP-0950
RADIO-3822.10.08.07_M
eMMC-boot
Oct 25 2011, 16:55
Two threads in different sections?
You are not bricked. What were you looking to accomplish
Flyer
I was unlocking a friend's bootloader the other day via HTCDev for another phone. I unplugged during the process as well however this didn't affect it. Your bootloader is telling you that you're also unlocked. How long have you waited on the black screen after the HTC logo?
If you hold power and volume down to enter the bootloader then go into fastboot mode, can you connect the Flyer to your PC and enter the following command into a terminal;
Code:
fastboot devices
A serial number will come up if your Flyer is being recognised. If this is the case it would be possible for you to flash a custom recovery enabling you to then flash a custom rom.
What he said
Flyer
pravus_nephilim said:
I was unlocking a friend's bootloader the other day via HTCDev for another phone. I unplugged during the process as well however this didn't affect it. Your bootloader is telling you that you're also unlocked. How long have you waited on the black screen after the HTC logo?
If you hold power and volume down to enter the bootloader then go into fastboot mode, can you connect the Flyer to your PC and enter the following command into a terminal;
Code:
fastboot devices
A serial number will come up if your Flyer is being recognised. If this is the case it would be possible for you to flash a custom recovery enabling you to then flash a custom rom.
Click to expand...
Click to collapse
Nothing happens
It doesnt show anything
mcord11758 said:
Two threads in different sections?
You are not bricked. What were you looking to accomplish
Flyer
Click to expand...
Click to collapse
I just want my flyer back
pravus_nephilim said:
I was unlocking a friend's bootloader the other day via HTCDev for another phone. I unplugged during the process as well however this didn't affect it. Your bootloader is telling you that you're also unlocked. How long have you waited on the black screen after the HTC logo?
If you hold power and volume down to enter the bootloader then go into fastboot mode, can you connect the Flyer to your PC and enter the following command into a terminal;
Code:
fastboot devices
A serial number will come up if your Flyer is being recognised. If this is the case it would be possible for you to flash a custom recovery enabling you to then flash a custom rom.
Click to expand...
Click to collapse
Sorry actually I get this:
HT15SJN00622 fastboot
I would think, as mentioned, your best route is to flash a recovery then a rom. Has to be a rom with a stock kernel so I suggest either virtuous or iodriod. Assuming your on hc which I believe is the case. Download a rom to your pc then download this and place it in the same directory as your Fastboot commands
https://m.box.com/view_shared/9bb9ba944ea6f301afe8
Then with flyer in Fastboot and connected
Fastboot flash recovery "name of file here"
Then go back to hboot and select recovery should now have it. Under options in recovery mount to pc and place rom you downloaded on your external sd. Then go back and select install zip from sd find the rom and flash it
mcord11758 said:
I would think, as mentioned, your best route is to flash a recovery then a rom. Has to be a rom with a stock kernel so I suggest either virtuous or iodriod. Assuming your on hc which I believe is the case. Download a rom to your pc then download this and place it in the same directory as your Fastboot commands
https://m.box.com/view_shared/9bb9ba944ea6f301afe8
Then with flyer in Fastboot and connected
Fastboot flash recovery "name of file here"
Then go back to hboot and select recovery should now have it. Under options in recovery mount to pc and place rom you downloaded on your external sd. Then go back and select install zip from sd find the rom and flash it
Click to expand...
Click to collapse
Yes I was on HC
Sorry for noob question
How do I flash recovery??
Is this Rom ok?
RUU_Flyer_BrightstarUS_WWE_1.36.1540.32_R_Radio_20.3501.30.089BU_3809.05.04.10_M_release_191425_signed
Why were you unlocking your flyer, what is your end goal?
Flyer
mcord11758 said:
Why were you unlocking your flyer, what is your end goal?
Flyer
Click to expand...
Click to collapse
I wanted to go back to gingerbread
but now i regret it
question:
by putting those two files to the same directory can I put them in my folder adb with adb.exe, fastboot.exe ?
I have a problem with this, I am not sure ..
So you have a best buy flyer and wanted to roll back to gb. Your hboot says unlocked and you have not yet flashed a recovery. First thing I want to do is get you booted then if you still have the stomach you can go back to gingerbread.
If you have not already, download the recovery.img I linked. Place it in the same folder as the Fastboot.exe. Put your flyer in Fastboot mode.
Open a command prompt on your pc. Change to the directory that has your adb/Fastboot commands. Type
Fastboot flash recovery "name of downloaded recovery file.img"
No quotations just file name then hit enter
Should flash recovery. Download a hc rom to your pc, I suggest iodriod which is a smaller file. Then place it on ext sd and flash like you would any rom.
mcord11758 said:
So you have a best buy flyer and wanted to roll back to gb. Your hboot says unlocked and you have not yet flashed a recovery. First thing I want to do is get you booted then if you still have the stomach you can go back to gingerbread.
If you have not already, download the recovery.img I linked. Place it in the same folder as the Fastboot.exe. Put your flyer in Fastboot mode.
Open a command prompt on your pc. Change to the directory that has your adb/Fastboot commands. Type
Fastboot flash recovery "name of downloaded recovery file.img"
No quotations just file name then hit enter
Should flash recovery. Download a hc rom to your pc, I suggest iodriod which is a smaller file. Then place it on ext sd and flash like you would any rom.
Click to expand...
Click to collapse
when I do that (if I put the file name correctly) I get this:
error cannot load hc recovery
The file name was hc recovery right?
Btw I want to thank you for hepling me.
Also I do not have the stomach to downgrade anymore, I just want my flyer to work again
Did you put the .img at the end of the name?
maciejkoziol said:
when I do that (if I put the file name correctly) I get this:
error cannot load hc recovery
The file name was hc recovery right?
Btw I want to thank you for hepling me.
Also I do not have the stomach to downgrade anymore, I just want my flyer to work again
Click to expand...
Click to collapse
I am trying to locate the rom you suggeted but I cannot find it.
Btw breathe a little I do not believe you are that bad off, correcting your issue should not be that hard
---------- Post added at 09:46 AM ---------- Previous post was at 09:45 AM ----------
Rom
http://forum.xda-developers.com/showthread.php?t=1580395
mcord11758 said:
Did you put the .img at the end of the name?
Click to expand...
Click to collapse
I typed fastboot flash recovery hc recovery.img
got error cannot load hc
Can you confirm that you flyer is in Fastboot and that the recovery is in the same folder as your adb files and that you are in that directory in your command prompt
mcord11758 said:
Can you confirm that you flyer is in Fastboot and that the recovery is in the same folder as your adb files and that you are in that directory in your command prompt
Click to expand...
Click to collapse
yes all should be correct
Remove any space in file name. So just hcrecovery.img
Before I get into the gist of my current problem I think it might be relevant to provide some backstory. I decided I wanted to try and root my phone so I could install a new custom ROM. I had done some jailbreaking back when the iPod touches came out, back when jailbreaking was extremely ghetto and unreliable, so I figured I could teach myself this fairly easily. I unlocked bootloader using the htcdev method without an issue, and, following a guide, downloaded something called Rootboot to flash the phone. There was only one step to this portion, so I assumed it would be easy. Running the rootboot started rooting my phone, however after a couple of lines in the command prompt it said something about the adb, failed, and the phone was stuck in a boot loop with no roms on it at all. I stayed up all night with the damn thing attempting to fix it, and at one point, actually got it to load up the stock ROM from the computer using some combination of RUU's and fastboot commands. I have no clue how I did it, all I know is that it was not through adb sideload because the recovery I had at the time wouldn't work with adb sideload for whatever reason. It was the recovery that came with the All-In-One toolkit, for the AT&T / TELUS version. At this point I figured since the phone was working I would just install the VenomROM, and after a few hours of playing around with fastboot and the bootloader trying to get a ROM loaded, I figured I was familiar enough with all of them to load the ROM.
Which is what brings me to my current issue. I KNOW the boot.img is flashed to the device because I used the All-In-One Toolkit to do it, erased the cache, did it again using fastboot commands in the command prompt, erased the cache, and continued to use recovery to install the ROM. I got it to load and install, cleared the darvik cache, data, and cache, but when booting, the phone would get to the lock screen, upon which sliding to unlock, presented me with a white screen that says "htc" on it instead of a launcher. After a couple of seconds of waiting, it says, "setup has quit responding" and gives me the option to close or to wait. Either option results in the phone rebooting wherein I only see a black screen with the notification bar at the top displaying my battery and no internet/network connection. I have gone back and flashed the boot.img again and cleared cache, darvik cache, and data several times and just have no clue what I'm doing wrong to not get this phone to boot with the ROM. I can reflash at any point from my sideload.zip file and the installation process has an option to flash the kernel (boot.img) because it is included in the zip. Any help would be much appreciated. I highly doubt theres anything wrong with the ROM or boot.img, it is probably me just not doing it right.
I am using (or attempting to use) the 1.2.7 version of VenomXL+ on the HTC One X+ along with TWRP 2.5 as the recovery.
Hi patarrfwifwi,
This should help you getting your phone back, make sure your SDK/ADB tool is perfectly installed (see in my signature if you need a guide) on your computer, this is the manual procedure to achieved a custom recovery, installing root and transferring a ROM via sideload to your phone to allow an installation.
Download this recovery HERE
Move this file in your platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
In the command window with your phone in FASTBOOT USB mode
Type>fastboot flash recovery TWRP2500.img
(Success)
Type again>fastboot erase cache
(Success)
Unplug your USB cable
Hit one time Power
Select Recovery (Volume down)
Hit Power to Reboot in Recovery
Your phone should reboot in Recovery
(!! The following instruction are with TWRP Recovery installed !!)
Select Advanced -> ADB Sideload -> swipe to activate
Download this file SuperSU and transfer this file again in platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
Type>adb sideload SuperSU.zip (Enter)
(Success)
Once done select Install menu of the Recovery
Locate sideload.zip and select it.
Swipe to confirm.
You are done rooting your phone.
Stay in Recovery and delete the sideload.zip file
Select Advanced -> ADB Sideload -> swipe to activate
Download this file ViperXL+ 1.2.7 JB and transfer this file again in platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
Double click on the ViperXL+-1.2.7.zip file and locate the boot.img and drag it to the platform-tools folder.
Type>adb sideload ViperXL+-1.2.7.zip (Enter)
(Success)
Once done select Wipe menu and wipe (factory reset and format system)
Select Install menu of the Recovery
Locate sideload.zip and select it.
Swipe to confirm.
Aroma installer will start leave everything by default and install the ROM.
Once done select Reboot-> Bootloader
Make sure FASTBOOT USB is highlighted
In bootloader via the command window type>fastboot flash boot boot.img (Enter)
(Success)
At the prompt type>fastboot erase cache (Enter)
(Success)
Finally at the prompt>fastboot reboot (Enter)
Rebooting
Give your phone ~5-10 minutes to complete the installation.
Tell me how that went please.
Thank you very much for the extensive reply. I am going to start on this right away. Quick update: I tried installing a different ROM named elegancia and got the same problem at the lock screen with it saying system process not responding. Might be irrelevant at this point, but I thought I'd throw up the update.
Starting this now, I'll get back to you when I'm done.
Unfortunately, this ended in the same problem. White screen with htc, system process stopped running. boot loop.
The only differences between this and what I was doing is that I never had that SuperSU step before and I was running everything from the data folder of the All-In-One toolkit instead of the sdk.
Try fixing permissions in recovery.
sixcarnage said:
Try fixing permissions in recovery.
Click to expand...
Click to collapse
Ok, did that. It just enters a black screen with the notification bar at top, then goes black. The keys respond to hitting the lock/power button, but the notification bar goes away permanently, then phone goes back and reboots again.
What boot.img are you flashing? Is it the one inside the .zip?
sixcarnage said:
What boot.img are you flashing? Is it the one inside the .zip?
Click to expand...
Click to collapse
Yes
Try the one in the forum under the downloads. I know it's the stock but give it a shot.
Where would I find that?
If that doesn't work try the Beast Mode Kernel.
Download: http://db.tt/aGV3WhR2
Extract the boot.img from .zip and then flash the .zip in recovery.
Does this work?
---------- Post added at 10:39 PM ---------- Previous post was at 10:37 PM ----------
patarrfwifwi said:
Where would I find that?
Click to expand...
Click to collapse
Don't get cocky that was an accidental thanks
Here is the stock boot.img from the Viper thread
Download: http://www.androidfilehost.com/?fid=9390248398092764372
I don't really need a custom ROM, if I could just get the phone back to stock that would be good too. Basically, I don't care what I do to get it to work again, I just want to be able to use my phone. I've been out a cell since Sunday night and if going back to stock is easy and simple I'll just do that. If custom ROMs are the easiest option at this point I'll stick with that too; whatever gets my phone working the fastest.
Any luck with the above?
I flashed the boot.img from the beastmode, adb sideloaded the zip, installed the zip, did a wipe (darvik cache and whatnot) and after the Viper startup screen, it brought me to a screen that said upgrading apps (260 of them) and my hopes were up so much, but then it just started with the black screen. went into recovery and wiped the cache and darvik cache again, restarted, same problem with the htc screen.
I flashed the stock boot onto it and restarted. No luck,
I'm going to bed for the night. I'll be back on around 3 PM EST tomorrow.
patarrfwifwi said:
I'm going to bed for the night. I'll be back on around 3 PM EST tomorrow.
Click to expand...
Click to collapse
I'd go back to stock for now.
What I would do is get the att latest ruu and adb it to the phone to install. This happened to me and all I got was a black screen with the noti bar on top and nothing else. And then i send the latest ruu zip through adb and installed it. And now I have a working phone
Seems like we can't downgrade right now..
Sent from my SoftBank AQUOS PHONE Xx 203SH using XDA Premium
can you give me a link to this? i found the latest ruu, but its an exe file instead of a zip
RUU is always under an *.exe type file. It must be flash in bootloader mode (fastboot) via your computer with your phone plugged in.
Can you tell which HBOOT version you have (you can check this in bootloader mode)?
This is long, but it's nice for noobs because it's detailed. It's honestly kind of fun, I promise. I'm assuming you have WINDOWS. This is based off of the guide by torxx!. It's modified because some of the info is outdated (you don't have to flash the boot.mg separately, for example). If you are NOT a noob you can just look at the "overview" for each step.
UNLOCKING YOUR DEVICE WILL WIPE YOUR DEVICE. THIS IS A SECURITY FEATURE. BACKUP FIRST.
Part 1- gaining unlock token
Overview: go to htcdev.com and unlock bootloader
Be sure you've turned off fast boot option in power menu; usb debugging should be on (settings -> developer options).
Go to http://www.htc.com/www/software/htc-sync-manager/[1] and install HTC SYNC. Alternatively, if you know what you're doing, you can install these drivers:
x86 http://www.mediafire.com/?qabo1tue2v1ky75 x64 http://www.mediafire.com/?8dl8s3l9mr6ggr9
Go on http://www.htcdev.com[4] and create yourself an account on HTCDEV.
Download these adb/fastboot files: http://d-h.st/RvD
Make a new folder anywhere. We'll use C:/fastboot as an example.
Extract the zip downloaded to the new folder
Go Here http://www.htcdev.com/bootloader/[6] and select "All Other Supported Models" and "then begin unlock bootloader" (check the boxes, click proceed, all that good stuff). YOU CAN IGNORE THE DIRECTIONS THAT THEY TELL YOU (and follow this guide instead).
Power off your phone. Power your phone on by holding power and volume down.
Highlight 'Fastboot' the volume buttons then press power to "select".
Plug your phone into your PC and open a Command Prompt. (windows XP - Click Start > Run > type CMD in box then press OK; Windows 7 - Click Start > type CMD in search box then press Enter) Change directory to your folder where we put fastboot files by typing cd c:\fastboot for example.*
*Alternatively, you can just hold down shift and right click in the folder and select "open command window here". Neat huh?
Type this into your command prompt window: fastboot oem get_identifier_token
Select & copy the text as per step 9 on the HTCDev website
Paste your identifier token into the box at the bottom and submit
You Will Very Shortly Receive an email from HTCDev with a link to the second part of the instructions and your "Unlock_code.bin" attached
Download the "Unlock_code.bin" from the email and save it to the same folder that we extracted fastboot files
Type this into your command prompt window: fastboot flash unlocktoken Unlock_code.bin
The Display Will change on your phone, press Vol+ to accept and power to confirm.
Part 2
Overview: flash your recovery. Boot into recovery. Turn phone off if it boots into OS. Boot into back into recovery. You're done!
Download a recovery:
TWRP (the one I use): http://forum.xda-developers.com/showthread.php?t=2173870
CWM 2: http://forum.xda-developers.com/showthread.php?t=2172979
CWM: http://forum.xda-developers.com/showthread.php?t=2173863
Place the Recovery file to the folder where the fastboot.exe is.
Same thing as above- boot (volume down + power) into the bootloader and highlight 'Fastboot' the volume buttons then press power to "select".
Do the same thing as with the command prompt above. This time, however, you'll be typing:
fastboot flash recovery "name_of_the_recovery.img"
For example:
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.img
then type:
fastboot erase cache
From the menu, boot into recovery (use volume to move up and down, power to select). The phone might boot to the OS instead of recovery, don't worry!
Turn off phone then turn on (while holding volume down) to boot back into the bootloader.
TAMPERED shows up, boot into recovery and now your recovery should be working!
Part 3- obtaining root
Overview: flash a super tool
Download a super user tool for root:
SuperSU (I use this one): http://forum.xda-developers.com/showthread.php?t=1538053
SuperUser: http://download.clockworkmod.com/superuser/superuser.zip
Alternatively, download this: http://forum.xda-developers.com/showthread.php?t=2252959. This is a stock rooted rom for ATT. If you download and flash this instead of the super user tool, you're done. (This rom includes super user) Or you can download a custom rom such as this one: http://forum.xda-developers.com/showthread.php?t=2183023
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip super user tool to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead.
I recommend these kernels: http://forum.xda-developers.com/showthread.php?t=2255900 or http://forum.xda-developers.com/showthread.php?t=2233665&highlight=menu
Download it.
Installing custom rom/kernel ("flashing a rom")
Overview: Download Rom, boot into recovery and wipe and then flash.
According to Shenye, even though your device is s-on, you can still flash boot now. So just do this:
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip kernel/cutom rom to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
I feel like this title should be changed to clarify that it's unlocking the bootloader, not the SIM lock.
Just wanted to say this tutorial was 100% dead on and what I used to unlock bootloader and root/rom my One.
Oddity - Did everything, I've got root but I -AM- out of the woods. Was installing bulletproof mod through recovery but it kept failing due to missing a MD5 file or something -- Trying to work that out through that thread atm but anyway, rebooted the phone a couple of times now and I still have root, Tit back up works OR are we talking about things like CPU clocking won't work since it can't rewrite?
Sticking this.
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Does anyone know if this will work on the Rogers HTC One?
Thank you. Followed this last night. Worked flawlessly. The only thing that threw me was rebooting into recovery. It took maybe 3 or 4 reboots for it to say "TAMPERED" at the top. When it didn't say tampered, it would not boot to recovery.
TELUS?
DannySmurf said:
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Click to expand...
Click to collapse
Did you happen do run this tutorial on a TELUS device?
Viceroy_N said:
Does anyone know if this will work on the Rogers HTC One?
Click to expand...
Click to collapse
Yes it does. I have a Rogers phone, and it worked perfectly.
richnanaimo said:
Did you happen do run this tutorial on a TELUS device?
Click to expand...
Click to collapse
No, I have a Rogers device. But the procedure should not be any different.
followed step by step and got an error that says submitted token wrong length
I'm on ubuntu 13.04 and I get stuck at getting the token. I type in fastboot oem get unlock_identifier_token and it says waiting for device. Tried it with sudo and it says error and sudo ./fastboot and it says no such command.
Sent from my HTC One using xda app-developers app
Having a really odd problem. I flash the twrp recovery per instructions. I try to reboot to recovery and it seems to try and then, blam, the att boot.
I have tried this from the bootloader, selecting Recovery, as well as from a booted stated using "adb reboot recovery".
Any hints for me? I originally had a silver One and today got my Black One replacement,. Had no issues on the original one. Hmm. Guess I will try CWM.
FYI: Yes I unlocked the bootloader and it says Unlocked in there
-I also notice that I seem to go right into fastboot, when I boot the bootloader. Now, I believe that is normal if you have the usb cable attached, but this happens regardless.
-flashed stock recovery back and can get into it. trying twrp again, renaming the file to "recovery.img" just because...and it worked on that stock recovery file
-Also, very hard to get into bootloader from powered off state. I may flash RUU_M7_UL_JB_50_Cingular and see if it helps me.
OK, maybe it is the phone or ATT has done something screwy on the latest. I can not even get the RUU install to pass inspection. Wants me to check the connection. I know all my stuff is in order, as I did this all on the previous one. grrr
-Just noticed mine does say Unlocked but it does not say Tampered.
-Crazy. I decided to get a new Unlock token and redo the unlock with it. Now, the bootloader finally says Tampered and I got into TWRP. I have no idea why, since I would think that if the original Unlock token was incorrect, it would not have unlocked the phone.
So, rather than providing worthwhile information for anyone else having problems, I think this post is probably deletable and that is fine by me should the powers so decide.
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
tacotino said:
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
fastboot oem lock
but, it will say relocked. nobody cares or seems to check. also, it will say tampered until you restore a stock ruu to flash. I used RUU_M7_UL_JB_50_Cingular.exe for mine when switching from silver to black. it is the right one for att. sorry, don't have the link to the download anymore.
great writeup! quick comment though, just helped my brother unlock his phone. i had a similar issue to @Barsky above so I decided to try to reflash the recovery. The first time I used the line fastboot erase cache after flashing the recovery and I think that's what caused it to not boot into recovery. The second time I flashed TWRP, I didn't enter that line and voila it worked on the first try!
can anyone post a mirror of the dev host files? devhost seems to be down.
nice...
help please
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
mbroch89 said:
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
Click to expand...
Click to collapse
I think the last bit was your problem. You can't factory reset from bootloader. Try to push twrp again in fastboot then load/flash clean romantic, then boot up. It already has root so you don't need to push su.
Sent from my HTC One X using xda app-developers app
I'm pretty inexperienced with rooting.. I think I may have messed my brother's phone up. I rooted his rezound and got cwm recovery working. I tried to flash a "TACHYON-1.2.zip" rom I found here and now it won't boot past the white background with green htc screen when I try to boot the phone. Please help me try to fix this! I can still boot into cwm recovery.
[EDIT] When I wipe data/factory rest it says error mounting /sdcard/.android_secure!
This was probably a mistake but I'm freaking out. I put CleanROM Standard 4.5.zip from here https://www.copy.com/s/uYOSaNCntCvx/CleanROM on another sd card and installed it after tying to wipe again. Now it boots past the htc screen and the CleanROM screen boots for a minute, then sticks..
Cap'n Jazz said:
I'm pretty inexperienced with rooting.. I think I may have messed my brother's phone up. I rooted his rezound and got cwm recovery working. I tried to flash a "TACHYON-1.2.zip" rom I found here and now it won't boot past the white background with green htc screen when I try to boot the phone. Please help me try to fix this! I can still boot into cwm recovery.
[EDIT] When I wipe data/factory rest it says error mounting /sdcard/.android_secure!
This was probably a mistake but I'm freaking out. I put CleanROM Standard 4.5.zip from here https://www.copy.com/s/uYOSaNCntCvx/CleanROM on another sd card and installed it after tying to wipe again. Now it boots past the htc screen and the CleanROM screen boots for a minute, then sticks..
Click to expand...
Click to collapse
You need to extract and flash the boot.img file from the ROM zip separately via fastboot. Extract the file and place it in an easy to access place on the drive (like same place as fastboot/adb) , then after flashing the ROM reboot into hboot and start fastboot, and use:
fastboot flash boot boot.img
Then reboot and be patient, sometimes the first boot seems to take forever.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
You need to extract and flash the boot.img file from the ROM zip separately via fastboot. Extract the file and place it in an easy to access place on the drive (like same place as fastboot/adb) , then after flashing the ROM reboot into hboot and start fastboot, and use:
fastboot flash boot boot.img
Then reboot and be patient, sometimes the first boot seems to take forever.
Click to expand...
Click to collapse
Thank you for the reply, and sorry if I ask too many questions, but how exactly do I flash the boot.img file? In CMD? There isn't a flash option in my fastboot section of the phone, just BOOTLOADER, REBOOT, REBOOT BOOTLOADER and POWER DOWN.
http://img854.imageshack.us/img854/6248/ismh.png
This is how far I got in cmd if I'm headed in the right direction at all..
Cap'n Jazz said:
Thank you for the reply, and sorry if I ask too many questions, but how exactly do I flash the boot.img file? In CMD? There isn't a flash option in my fastboot section of the phone, just BOOTLOADER, REBOOT, REBOOT BOOTLOADER and POWER DOWN.
This is how far I got in cmd if I'm headed in the right direction at all..
Click to expand...
Click to collapse
You start fastboot in the phone, that puts it in a mode to enter fastboot commands from a PC... You Don't do anything in the phone in fastboot, you use the fastboot command that is part of the ADB package. The same way you would have unlocked the phone on HTCdev.com to allow root or CWM to be installed.
Sent from my Nexus 4 using Tapatalk
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom.
mjones73 said:
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom.
Click to expand...
Click to collapse
Thank both of you so much! I'm sorry I had to have you completely spell it out for me, but I appreciate the help and this forum in general so much!
I hate to bring this thread back, but it's the best place to ask about my problem. I'm trying to switch from Clean Rom on an HTC Rezound to Venasaur Rom v3.2.0 because I read that it will work with a Straight Talk sim. I tried installing with ClockWork and I get the new rom's boot screen, but it won't boot past that. I don't know what I'm doing wrong. I would really appreciate it if somebody could help me out again!
Did you flash the boot.img this time? I would suggest after you get booted, trying rumrunner to go S-off... It saves sooo much time... I'm always switching between multiple ROMs because I'm s-off....
Sent from my HTC EVO 4G Running AOKP 4.2.2
Cap'n Jazz said:
I hate to bring this thread back, but it's the best place to ask about my problem. I'm trying to switch from Clean Rom on an HTC Rezound to Venasaur Rom v3.2.0 because I read that it will work with a Straight Talk sim. I tried installing with ClockWork and I get the new rom's boot screen, but it won't boot past that. I don't know what I'm doing wrong. I would really appreciate it if somebody could help me out again!
Click to expand...
Click to collapse
... you should remember one thing for sure. Because you are s-on whenever you flash any custom rom, you have to flash its corresponding boot.img file in fastboot separately otherwise you are gonna get bootloop ...
---------- Post added at 11:50 AM ---------- Previous post was at 11:49 AM ----------
... and yeah. you should try to get s-off as you are already been suggested above ...