Database Info

Q about cwm 3.0+ and 2.3.2

Out of sheer curiosity and wonder, I noticed after the OTA was installed, su was not working, duh, I knew that would happen, so I re rooted the device, I made a back up of the rom every single time it was updated, so I noticed when clicking "reboot into recovery" option in rom manager (keep in mind I am on 2.3.2) it boots me into stock android <3e> recovery and not CWM 3.0.x.x. Which is weird because after that I do a battery pull to jump into the bootloader to access recovery there, nope, still takes me to the damn stock recovery, so back to the bootloader and fastboot my way back. After that, I noticed once back booted in android I go into RM and "flash recovery" (3.0.x.x) and voila! I get back into CWM, but I have to flash it every single time.
Has anyone noticed this?
Feel free to hit me up on twitter since I try to stay outta forums, thank you.
I <3 Trolls.

b16a2smith said:
Out of sheer curiosity and wonder, I noticed after the OTA was installed, su was not working, duh, I knew that would happen, so I re rooted the device, I made a back up of the rom every single time it was updated, so I noticed when clicking "reboot into recovery" option in rom manager (keep in mind I am on 2.3.2) it boots me into stock android <3e> recovery and not CWM 3.0.x.x. Which is weird because after that I do a battery pull to jump into the bootloader to access recovery there, nope, still takes me to the damn stock recovery, so back to the bootloader and fastboot my way back. After that, I noticed once back booted in android I go into RM and "flash recovery" (3.0.x.x) and voila! I get back into CWM, but I have to flash it every single time.
Has anyone noticed this?
Feel free to hit me up on twitter since I try to stay outta forums, thank you.
I <3 Trolls.
Click to expand...
Click to collapse
Wow, I'm sorry to be cranky, but this is unreal.
Your question has been asked and answered a hundred times in this forum if you'd bothered to search, and you're not even willing to a monitor the forum for an answer, you want us to come search you out on Twitter?!?!?
Here's a hint to find the answer to your question, use the forum search button and search for the phrase /etc/install-recovery.sh.
You'll find dozens of posts telling you to rename that file, which Google added with the updates to overwrite any custom recoveries with the stock one on each boot of the phone... Rename the file and you won't have to flash cwm every time any more.

Okay, that last post was a bit more harsh than I meant it to be, perhaps, but I'm leaving it intact. Since you "try to stay outta forums" you probably don't know proper etiquette:
1) search before asking; your issue has most likely been asked before. It's annoying to forum regulars when people show up and ask the same thing over and over that's already been answered.
2) read the FAQ thread before asking; your issue has most likely been addressed in it. It's annoying to forum regulars when people show up and ask the same thing over and over that's already been answered in the FAQ.
3) if you're going to come to the forums and ask a question, then come back periodically and see if it's been answered. We're doing you a favor answering your question, at least show some effort by coming back and reading it instead of asking someone else to come find you in another forum and spoon feed it to you. If you're really just too important or time-challenged to do that, then subscribe to the thread you created and get an email notice when posts are made to it.[/I]

You'll need to rename install-recovery.sh to install-recovery.sh.old.
Its located in the /etc system folder. You can use root explorer or any another alternative. Refer to the rooting guides available as they include a more thorough explanation of how to do this. And please, no twitter.
Sent from my Nexus S using XDA App

it's actually enough just to fastboot push the renamed recovery.img
then it will stick without having to rename the install-recovery.sh

Hey huge thanks to @AllGamer.
The other guy, no idea what crawled up your ass and died, but didn't know that one simple question could hurt so badly. Have a nice day.
P.S. I am sure most of the people here know this, the search engine sucks on this site so yes I did use it and its garbage. I was just concerned about it so I could start my builds without any worry. Happy trolling.
Moderator delete this thread,
Thanks.

AllGamer said:
it's actually enough just to fastboot push the renamed recovery.img
then it will stick without having to rename the install-recovery.sh
Click to expand...
Click to collapse
I don't recall that working for me. I'm not even sure why that would work. Every boot up that script is ran unless you delete or rename it, isn't it? I guess I'll have to play with it when I get a chance.
EDIT: Do you mean renaming clockwork-3.0.0.5-crespo.img to just recovery.img when pushing it via fastboot? Never tried that here.
b16a2smith said:
Hey huge thanks to @AllGamer.
The other guy, no idea what crawled up your ass and died, but didn't know that one simple question could hurt so badly. Have a nice day.
Click to expand...
Click to collapse
I think it was the bit about I try to stay out of forums, so come find me on twitter coupled with the <3 trolls.
I was cranky this morning and I apologize, but it was all true, and don't forget that I did tell you how to find the answer (which search term to use) and even how to fix it (rename the file), so I think thanks are in order....You're welcome for that, and have a nice day as well..
Peace

distortedloop said:
EDIT: Do you mean renaming clockwork-3.0.0.5-crespo.img to just recovery.img when pushing it via fastboot? Never tried that here.
Click to expand...
Click to collapse
yes, it is in my guide
yet people always misses to read it
most people reading it either assumes things, or doesn't follow it properly
that's how i do it every time and it works without fail

AllGamer said:
yes, it is in my guide
yet people always misses to read it
most people reading it either assumes things, or doesn't follow it properly
that's how i do it every time and it works without fail
Click to expand...
Click to collapse
Just to be clear, we're talking about having clockwork NOT overwritten by the stock each bootup. I'm a little confused because you say "that's how i do it every time..." If it sticks, why do you need to do it more than once?
Assuming you mean clockwork sticking without renaming the install-recovery.sh file, please read on. If that's not what you meant, skip the rest below...
I don't think people necessarily miss it, they assume things like you say
I didn't follow your guide to root mine (it wasn't out yet, and isn't Mac), but obviously I've read it. I did notice that you rename it, but assumed it's not necessary, since Koush's instructions don't have you do that and you get a successful flash without renaming.
Anyways, I just tested this out on my NS.
I was on stock recovery, and I have not renamed my /etc/install-recovery.sh file.
I booted the phone to fastboot mode, renamed my clockwork recovery to recovery.img.
I then "fastboot flash recovery recovery.img" and after a successful flash message, selected recovery from the fastboot menu.
The phone booted to clockwork recovery, which confirms a successful installation of it.
I then rebooted the phone, and after it was fully booted, rebooted it to fastboot mode. When I selected recovery, I then get the box with an arrow pointing into the android, so I hit the proper keys and I ended up in stock recovery (blue text).
The install-recovery.sh script still reflashed the stock recovery even though I flashed it per your instructions.
If I rename that script and then install clockwork, any attempt to boot recovery goes straight to clockwork recovery (orange text, extra features, etc).
Did I do something different than you're suggesting? Based on my test, I don't think you have any option other than to rename that script (or delete the backup image it uses to flash stock) if you want to remain on Clockwork.
Thoughts?

you should still have the CW recovery, if you pushed it into the phone as recovery.img
after i reboot the phone, i can go back into CW just by selecting Recovery
i just use those reboot software, or manually hold volume up + power
then i get into the fastboot mode
in fastboot mode i select Recovery
and that takes me back to CW recovery
i did not rename the install-recovery.sh, just in case i ever want to restore the phone back to stock
i do know that if i do not rename the recovery-clockwork-3.0.0.5-crespo.img to recovery.img, then i will lose CW right after the reboot

AllGamer said:
you should still have the CW recovery, if you pushed it into the phone as recovery.img
after i reboot the phone, i can go back into CW just by selecting Recovery
i just use those reboot software, or manually hold volume up + power
then i get into the fastboot mode
in fastboot mode i select Recovery
and that takes me back to CW recovery
i did not rename the install-recovery.sh, just in case i ever want to restore the phone back to stock
i do know that if i do not rename the recovery-clockwork-3.0.0.5-crespo.img to recovery.img, then i will lose CW right after the reboot
Click to expand...
Click to collapse
Well, that's a weird one. You didn't say I tested it wrong, but I am getting different results than you.
If I were ambitious I would make a youtube video of it to show my results, not as a challenge, just to see if I'm doing something wrong.
Are you stock ROM? If not, maybe that's a difference that would explain it.

i'm on Bionix 1.3 beta
perhaps that's the difference?

AllGamer said:
i'm on Bionix 1.3 beta
perhaps that's the difference?
Click to expand...
Click to collapse
Almost certainly the difference.
I'll wager that if you go to the /system/etc folder that Bionix has removed that script for you. That would explain why it's not running and restoring the stock.
Check that out and let me know; we may have solved the mystery here.
FYI, I just downloaded the bionix 1.3 files and checked inside, no install-recovery.sh in it...

[Q] Phone not booting.

Right first off, I haven't searched the forum as I'm not exactly sure as to what to search for as I dont know the exact problem.
I want to flash a new ROM on my sensation and this was very easy to do on my old Desire. So what I did was:
1. Followed the tutorial to turn S-OFF - Done.
2. Followed Step 2 to install recovery. Put the file into my SD card but then the instructions weren't clear as I couldn't see any options to click Accept as the guide said.
3. Downloaded the Android Flasher app. Did these options:
- Chose sensation from the menu.
- Downloaded Radio "HTC-RIL 2.2.0169HMQ" and clicked the box.
- Clicked the Recovery box and chose the Recovery file I had put on my SD Card originally.
- Clicked Bootloader and chose "MIUI.us_pyramid_1.11.18_Eng_Deo_ZipA_Signed_TwinDragons"
- Chose my own splash screen.
4. Then I clicked flash and everything was ok. Phone booted into Hboot and the program said complete.
5. I rebooted the phone and the splash screen loads then.....nothing.
I was then unsure what I have done wrong. I tried rebooting several times to no success so I wiped the phone and installed MIUI again via the SD card but to no avail. I can still access ClockworkMod Recovery but thats it. Any help would be mucho apreciated.

I am new to android as well but what i understand from your situation is you flashed the radio wrong . Don't worry your device isn't bricked try re flashing radio VIA ARHD recomended ... I may be wrong but if I helped you out hit the thanx button below

Cheers for the help saddist. Will have a go at this when I'm home as I'm at work the now. I thought that the radio was purely for...well as the name suggests the phone's radio.
Appreciate you taking the time to help as it's a bit of a pain not having access to a phone.

dumbmayhem said:
Right first off, I haven't searched the forum as I'm not exactly sure as to what to search for as I dont know the exact problem.
I want to flash a new ROM on my sensation and this was very easy to do on my old Desire. So what I did was:
1. Followed the tutorial to turn S-OFF - Done.
2. Followed Step 2 to install recovery. Put the file into my SD card but then the instructions weren't clear as I couldn't see any options to click Accept as the guide said.
3. Downloaded the Android Flasher app. Did these options:
- Chose sensation from the menu.
- Downloaded Radio "HTC-RIL 2.2.0169HMQ" and clicked the box.
- Clicked the Recovery box and chose the Recovery file I had put on my SD Card originally.
- Clicked Bootloader and chose "MIUI.us_pyramid_1.11.18_Eng_Deo_ZipA_Signed_TwinDragons"
- Chose my own splash screen.
4. Then I clicked flash and everything was ok. Phone booted into Hboot and the program said complete.
5. I rebooted the phone and the splash screen loads then.....nothing.
I was then unsure what I have done wrong. I tried rebooting several times to no success so I wiped the phone and installed MIUI again via the SD card but to no avail. I can still access ClockworkMod Recovery but thats it. Any help would be mucho apreciated.
Click to expand...
Click to collapse
I don't quite get what you've done. Did you try and flash a ROM using Android Flasher? If so you need to walk away and do some serious reading as you WILL brick your phone if you continue

horrorschow1986 said:
why you don't flash the rom via cwm??
its easier i think...
Click to expand...
Click to collapse
I would have done this at first but, before using the Anroid Flasher app, I did not have access to cwm. I have since tried formatting the phone in cwm and installing from sd card but again, it just hangs after the splash screen. I also downloaded Bulletproof 1.4 to see if applying a Sense ROM had any effect - but again it stalled after the splash.
EddyOS said:
I don't quite get what you've done. Did you try and flash a ROM using Android Flasher? If so you need to walk away and do some serious reading as you WILL brick your phone if you continue
Click to expand...
Click to collapse
Yeah your correct Eddy, as my post above states, I turned S-OFF - got a bit stuck and then seen the ANdroid Flasher programme. I thought, smashing problem solved.
You are correct, I do need to do some more reading with the looks of it. On the desire, a programme did all the stuff for you. It seemed to me that the Android flasher was the same.
Where to start reading, I'm a bit unsure as I have a phone which is not booting. I'm not looking for everyone to do all the work for me, but if someone could give me a gentle push where to start in order to get this working again that would be great.
Meanwhile I'll do as you say Eddy and do some more reading.

Thanks everyone for your help. I got it sorted by flashing CWM manually this time and it flashed the ROMS so that they would work. Must have been flashing them wrong somehow but still managing it without errors.
Anyway, again I appreciate you taking the time to help.

[TUTORIAL] Prepare Your AT&T HTC One X for Custom ROMs

OUT OF DATE USE THE ONE CLICK 1.85 ROOT TOOL IN THE FORUMS
As the ROM chefs go to work, we want to be sure that we are ready to flash the ROMs when they come to be available! This guide will help you set up your phone so that you can flash custom ROMs.
After this process you will have a phone on the latest firmware (1.85 at the moment) with bootloader unlock, rooted, and busybox installed.
This guide assumes you are on a root friendly firmware (as of now, it is firmwares 1.82.502.3 and below).
This is really going to be done in a four step process. First we need to root the device in order to access the place where the CID is stored so that we can change it and get unlocked. After changing the CID, we can unlock via htcdev.com. Then we can go on to installing a custom recovery and finally rooting!
From there I will give you some tips on installing ROMs.
NOTE: THIS PROCESS IS EXTREMELY DANGEROUS. IT MAY BE A BIT CONFUSING. READ OVER THE STEPS BEFORE STARTING. IF YOU DO NOT THINK YOU WANT TO RISK YOUR DEVICE BECOMING A BRICK THEN DO NOT ATTEMPT THIS. THIS VERY EASILY COULD RUIN YOUR DEVICE.
BACKUP EVERYTHING BEFORE STARTING AS EVERYTHING ON YOUR DEVICE WILL PROBABLY BE WIPED.
I, XDA, AND THE ORIGINAL TOOL CREATORS DO NOT TAKE RESPONSIBILITY FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. IT IS SOLELY YOUR RESPONSIBILITY FOR WHAT YOU DO TO YOUR DEVICE.
Click to expand...
Click to collapse
Your warranty will be void if you unlock the bootloader. If you just root though then you can return to 100% stock by running the RUU.
This guide is for Windows only at the moment though I will try to post Mac and Linux guides at some point.
ORIGINAL TOOL THREADS:
One Click Root for 1.82 and below: http://forum.xda-developers.com/showthread.php?t=1644167
Spoof CID Script: http://forum.xda-developers.com/showthread.php?t=1672284
I will try to keep this as up to date as possible! Taking a visit to the index of the development forums (http://forum.xda-developers.com/showthread.php?t=1671237) is also a good idea!
Last Updated: 5/28/12

0. Getting the prerequisites:
Download the package at the bottom of the first post to get started.
Extract the package somewhere you will remember (like on your desktop).
Connect your device via USB and make sure you have USB Debugging enabled under settings.
Click to expand...
Click to collapse
1. Root your device
1. Open the folder you downloaded and navigate to the "root" directory.
2. Double click on the root-windows.bat file
3. Let the root run and do not touch your device. It will reboot several times- do not touch it or you may brick your device. Just let it do its thing and eventually after around 3 minutes you will have a rooted device in your hand.
Click to expand...
Click to collapse
2. Get the unlock token
In order to unlock the bootloader we will need to change a value called the CID. This will allow the htcdev.com site to unlock our phones.
1. Go to the downloaded folder and go to the "change_cid" folder.
2. Click on the "Spoof-CID.bat" file. Follow the instructions. Your CID will change from CWS__001 (stock AT&T CID) to 11111111 (called "SuperCID," will allow you to flash anything)
3. Log in to htcdev and go here: http://www.htcdev.com/bootloader/unlock-instructions (NOTE: This skips the agreements you need to click through as some of the buttons on their website are wonky. Doing this assumes you agree to their policies that are listed there)
4. Follow the instructions very carefully (they are written very well) untill the point where you get the file "Unlock_code.bin" via email. Stop there.
5. You should now have the file for bootloader unlock. MAKE SURE TO SAVE THAT FILE "Unlock_code.bin" TO THE "generic" FOLDER IN THE PACKAGE YOU DOWNLOADED! YOU WILL NEED IT LATER.
Click to expand...
Click to collapse
3. Run the RUU to update to latest firmware
1. Download the latest RUU from the xda forums (should be an .exe file)
Currently it is version 1.85.502.3 and you can download it here:
http://briefmobile.com/download-htc-one-x-att-1-85-update
2. Follow its instructions very carefully. It will take approximately 20 minutes to complete. BE PATIENT. IF YOU UNPLUG YOUR PHONE HERE YOU WILL GET A BRICK.
3. Let your phone reboot and go through initial setup again
Click to expand...
Click to collapse
4. Unlock your bootloader using Unlock Token
1. Navigate to the "generic" folder in cmd (you should have added the Unlock_code.bin file to this folder already) and plug your phone in in fastboot mode. To do this, first shut off your phone. Wait for it to turn off. Then hold the volume down button. Press the power button for 3 seconds while still holding the volume down key. Let go of the power button but keep holding the volume down button untill you see a white screen with a bunch of small text on it. Use the volume up and down keys and the power button to select the FASTBOOT option. Plug your phone into your computer. Then wait for the FASTBOOT text to turn into FASTBOOT USB.
2. Type the following into cmd on your computer:
fastboot flash unlocktoken Unlock_code.bin
NOTE: This step might take quite a few tries. For some it works on the first time. For others, it may take around 20 times. Just keep typing in the command until you get a sucessful flash. We aren't sure why it does this at the moment but just keep trying and don't give up.
3. Use the volume keys to say that you do want to unlock your bootloader and wait for reboot
4. Bootloader should be unlocked! Congrats, most of the grunt work is done! Go to Settings - Developer Options - Enable USB Debugging. This will allow us to continue
5. Re-set up phone and enable USB debugging again
Click to expand...
Click to collapse
5. Install a custom recovery so that we can gain root access
1. Currently there are two recovery options: ClockWorkMod Touch and TWRP (TeamWinRecoveryProject). Both are pretty much the same as they both use touch input but TWRP does have some other nice features like a built in file browser and more. It is also more touch optimized. ClockWorkMod is more "old school" and I personally feel more comfortable using it, but using TWRP is fine as well. It doesn't really matter which recovery your choose, both are good choices. Download whichever one you want below:
CWM Touch: http://forum.xda-developers.com/showthread.php?t=1677304
TWRP: http://forum.xda-developers.com/showthread.php?t=1677447
2. Drag the .img recovery file you just downloaded into the "generic" folder
3. Connect your phone via fastboot
4. Type the following:
fastboot flash recovery <insert name of recovery .img file here>
Replace the stuff between the <> with the name of the file you just downloaded
5. Wait for your device to reboot. Then type into cmd which is cd'ed to the "generic" folder:
adb reboot recovery
6. Make sure your recovery works as soon as it is done loading and then press "reboot system"
7. Follow its instructions
Click to expand...
Click to collapse
6. Root your system
1. Connect your phone as a "Disk Drive" and drag the "root.zip" file in the "root" folder to your phone's memory
2. Reboot into recovery with the adb command (adb reboot recovery)
3. Go to install zip from sdcard and navigate to the zip file you downloaded. Say "yes" and watch it flash
4. Reboot system now
5. Go to the play store and download any app that has "Busybox installer" in its name (the one by JRummy16 works good I believe)
Click to expand...
Click to collapse
If all goes well, you should be sitting at an AT&T HTC One X which is on the latest RUU leaked firmware (1.85.502.3 at this moment), rooted, busyboxed, and unlocked.
Congrats!
If you want to flash any ROMs, download the .zip file of the ROM, place it on your phones memory, and then install the zip like you did to the root.zip file.
Enjoy your AT&T HTC One X!

CREDITS:
kennethpenn: For initial root, getting all the RUUs from the "source" and for giving the HTC One X's situation prime press appearance on his website, BriefMobile.com
grankin01: For finding out how to edit the CID originally
designgears: For creating the One Click Super CID tool for bootloader unlock
paulobrien: For porting CWM Touch to our device
sk08: For leading the way in terms of MODs and organizing an S-OFF thread to get this thing fully ours
JSLEnterprises: For initially being there to help organize a bootloader unlock
Team Nocturnal: For their awesome ROM
Click to expand...
Click to collapse
If you want to thank or donate to someone, please do not do so to me. The people above are the ones that deserve the thanks and the donations to encourage them to keep doing the fantastic work they have been doing! I'm just a high school student
Some common terminology:
Deoxdexed: OEMs package their apps with .odex files because they are more optimized for your device. However, this makes the file uneditable by developers and things like mods cannot be used with odexed ROMs. A ROM with "deodexed" as a feature means it is easier to use mods with that ROM
Busybox: A collection of linux tools that are helpful for flashing ROMs and doing other basic Android tasks
RUU: ROM Update Utility, made by HTC, completely reflashes device firmware, useful if you get bricks. Only for Windows.
Root: Allows you to edit system level files
S-OFF: (currently unattainable) Security-OFF, it is a "feature" in HTC phones that allows us to modify almost any part of your system.
Unlocked Bootloader: Allows us to flash custom images to the device.
Click to expand...
Click to collapse

As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.

HydroSkillet said:
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
Click to expand...
Click to collapse
Wasnt sure, there are still a few people asking how to do it since it is a bit complicated with the 1.85 update breaking root so I just compiled everything into a master one.
And yeah, I use a lot of the scripts in the package I put for download.
Anyway, mods do what you think with this thread! And this might be in the wrong section, wasnt sure if it goes in general or development.

Please keep this up. As it is the most aggregated list of instructions, I'm sure it will help many who have just gotten their phone. Great work by the way.

HydroSkillet said:
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
Click to expand...
Click to collapse
As I agree with you, a "one stop shop" that can be pointed out to for the noobs who got their mommy's to buy them their cool phone should at least keep the redundant questions to a minimum.

you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG

squishy5 said:
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
Click to expand...
Click to collapse
Locked boot loader yes.
Root for cwm no.
Sent from my HTC One X using xda premium

squishy5 said:
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
Click to expand...
Click to collapse
Why don't you read before you comment on things like this?
I never "Unlock the bootloader"
I simply get the Unlock token from HTC.
So stop acting like you know everything, because you dont
Don't ever use caps with me and expect me to come back with a nice response. I put this out for the community, not for some kid who thinks he knows it all to come back and say that I did it wrong when he didn't even read the post properly.
And you don't need root to install CWM, just an unlocked bootloader.
Stop calling my stuff wrong if you yourself don't even know what is right

rohan32 said:
Why don't you read before you comment on things like this?
I never "Unlock the bootloader"
I simply get the Unlock token from HTC.
So stop acting like you know everything, because you dont
Don't ever use caps with me and expect me to come back with a nice response. I put this out for the community, not for some kid who thinks he knows it all to come back and say that I did it wrong when he didn't even read the post properly.
And you don't need root to install CWM, just an unlocked bootloader.
Stop calling my stuff wrong if you yourself don't even know what is right
Click to expand...
Click to collapse
He put his foot in his mouth, apology should be coming oh and Good job man, Good job. Thanks for the work, this should be a sticky.

This is a great write up and would have been extremely helpful last night. I will admit I have done a lot of reading before I unlocked the bootloader and updated to 1.85, but it was still very confusing at some points. The htcdev site actually gave me the most trouble because I didn't realize most of the steps were completed and I could skip all the way to entering the token and the site was simply used for entering the token and getting the unlock file.
And yes, I almost said the same thing about the relock step. I had to read it twice to realize you didn't unlock yet. That's another thing that confused me last night was unlocking/relocking immediately.
I think this should be a sticky and all the other tutorials and such should be deleted. This is a perfect summary IMO and will use it when I unlock my friends one x
Sent from my HTC One X

My problem with this is that you packaged it all up while the individual threads for each thing are updating and you are severing up potentially outdated scripts.

designgears said:
My problem with this is that you packaged it all up while the individual threads for each thing are updating and you are severing up potentially outdated scripts.
Click to expand...
Click to collapse
I agree. While it is nice to have a all-in-one, you should be linking to the threads since they are updating them on a daily basis instead of linking to their scripts. Ive already had to change JeepFreaks script this morning as he updated it. It would make your world a lot easier if you did it that way, and also not risk giving some new user outdated scripts.
I think this should go in the General section as the first few pages should redirect to the original threads anyway.

Red5 said:
I agree. While it is nice to have a all-in-one, you should be linking to the threads since they are updating them on a daily basis instead of linking to their scripts. Ive already had to change JeepFreaks script this morning as he updated it. It would make your world a lot easier if you did it that way, and also not risk giving some new user outdated scripts.
I think this should go in the General section as the first few pages should redirect to the original threads anyway.
Click to expand...
Click to collapse
Sure thing, I will add to the original post for the links.
Also I will try to keep this updated, but yeah I might not catch all the updates

Thank you so much Rohan! Really appreciate it! Took me about 4 hours to get this done but it was worth it. Now to install cleanrom. Thanks again. This is my first time doing something like this.

Duse ijuat saw this and I'm going to do this and flash clean from when I get home and I read through this I honestly love you for doing this it helps more than you think thanks a lot
Deffinitlet should be stickied
Sent from my HTC One X using XDA

These are the best instructions! Wish i had them when all this shenanigans started. Thx

ethantarheels123 said:
Please keep this up. As it is the most aggregated list of instructions, I'm sure it will help many who have just gotten their phone. Great work by the way.
Click to expand...
Click to collapse
I agree. This guide is very helpful for me. I consider myself to be fairly computer literate and have flashed ROMs on previous phones, but I am a complete n00b to android and linux. Looking around some of the other threads -- it appears to me that there are many people who could have much confusion resolved by reading this. Thanks for the thread.
-- Jon

Not quite sure what's going on with my update...
I'm using the exe that updates the RUU and it gets stuck on the "sending to phone" step. Reboots the bootloader once, gets stuck again (as far as I can tell , nothing is ever sent) and then gives me an error telling me "The ROM Update Utility cannot update your Android Phone. Please get the correct ROM Update Utility and try again"
i've got the correct drivers installed (was having some trouble related to that a couple days ago but have since figured it all out ) would it be better to just do the update manually? (On my evo you just change the update file to Update.zip and it automatically installs it for you when you boot into bootloader)
maybe I'll have to look into it further, but just curious if anyone's run into this issue or figured out how to get past it as of yet...
Edit: Just an update- I'm betting its because I forgot to relock my bootloader before updating. So anyone who's already completed SOME of the steps in the second post here, make sure you relock your bootloader if you haven't already done so.
Edit1.5: This assumption was correct and the bootloader is now unlocked.
Edit 2- Almost done here... Busybox wont install. Tried two different apps, neither one worked. No indication as to why (got very vague error messages to the effect of "busybox was not installed")
Edit 3- FIXED- Ok, figured it out. As far as I can tell, the process should be Root first, THEN install busybox. It doesn't work without root privelages (at least that was my experience here)

[Q] HTC One S(ville) black screen, thats it... just a black screen, what can i do???

I was working fine, enjoying my new HTC One S with CM9 rom installed. Well the battery life wasnt the best on it, and i didnt install the custom kernel. So I looked for the custom kernel download(on my phone, not on my computer) and i found a .zip file. Well I thought that you could just download the kernel straight to my phone and open it up with "Rom Manager" which i did, it than said i needed to reboot the phone in recovery to continue the installation, so I did... it took me to recovery "to continue the installation" well than I looked away, looked backed down and it was black.... and i have tried powering up, booting into boot loader, booting into recover, and nothing... its just BLACK! nothing works, its literally useless ATM. I really messed up, is there anyway to fix this? Thanks in advanced!
----EDIT----
I think I accidentally flashed the kernel like i would normally flash a rom.... cause i downloaded the .zip file(directly to my phone, not using a computer), than i tapped the download and it asked me if i wanted to open it up with rom manager, so i did. and i think rom manager thought i was flashing a rom, when i wasnt, it was a kernel.... am i screwed? or is there anyway out of this?

Do you know the exact kernel you flashed--where did it come from
Some you need to extract and push
Assume you just tried to boot into bootloader thru phone buttons
Does your pc recognize your phone when plugged in, if so can you open a command window and try to access phone as in adb devices then adb reboot bootloader
assuming you are familiar with sdk adb/fastboot comands
otherwise i don't know what else to say--may be bad--sorry

Came from an XDA thread
Here is where it came from: http://forum.xda-developers.com/showthread.php?t=1708676 from "sun90" (half way down the page "CM9 KERNEL remix edition.zip - [Click for QR Code] (5.53 MB, 9 views) ")
i downloaded that straight to my phone and opened it up with Rom Manager, which i think the app took it as a rom, and installed it like a rom even though it was not a rom. I just tried to access it through adb, it comes up with no devices my PC does recognize it when i plug it in though...
Ive tried to get into bootloader tons of times, it just stays black... :'(
Thanks for your answer!

You flashed a galaxy s2 kernel on your one s? why would you ever think that was a smart thing to do?
Looking at the updater script in that zip it seems it wipes some partitions, the partitions on a SGS2 and the ONE S are different, so if that script accidentally wiped say the hboot partition, or some other critical-for-boot partition, you have a fully bricked phone.
For any devs that may know what partitions are what on the One S, the script wiped
mmcblk0p7, and wrote a zimage to mmcblk0p5
---EDIT---
Normally this is a cwm flashable zip on the Samsung Galaxy S II, which is why rom manager flashed it, as it met all the requirements, the only issue is, it was not made for the ONE S and probably overwrote some important things.

I tried for hours and hours to fix the same issue on a friend's One S (same symptoms, not same cause) to no avail. I tried QPST and telnet and a ridiculous amount of things. Had to bring it to the store and get a new one.
Good luck, but I don't believe there's anything you can do to fix it.

Just answered your question in the help thread, Didnt see this thread too !
Im afraid its not looking good, I think your best bet would be to call your provider and blame it on an OTA update.
And hope for the best

Alright, thanks for the help!
Well it looks like i bricked my phone than.... I thought that CM9 was only on the One S, so I just looked for the CM9 kernel, which obviously was for the sg2, i feel like such a dumb ass now! haha well thanks for all the help guys! ill be heading to the t-mobile store today to blame it on a OTA:]

yeah, others wont agree with what your about to do but........
just act like a complete noob, dont mention anything about software / firmware / ROMs / bootloader etc ect
just say your phone made a noise, you selected update and it died lol

good luck--I know it is heartbreaking
not sure of your situation with carrier, but you could go thru Retention if needed

Hi peeps.
i'm very new to all this but sort of know the basics
i'm running on Axiom now but tried to flash cm10 but after install i got a black screen so had to do a restore.
Today i just flashed venom and after the instal process is done, i hear the start up music but nothing on the screen.
I have had 3 other roms on my phone and never had a problem!
these are the steps i do
download rom - place on sd
put phone in recovery
reset factory
reset cache
install from sd
when it finish's reboot
blank screen.
Am i missing something?
Any help would be great and i can't post on the thread because i'm a noob with less than 10 and dont want to spam my way to the 10 :silly:

you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe

rugmankc said:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
Click to expand...
Click to collapse
Thanks but i think that is now the least of my problems!
I used Goomanager and installed CM10, When I did it i installed teamwin recovery. It started to do a lot of strange things, when it finally rebooted i got a load of errors "phone is not working" nearly every 10 seconds?
it will not connect via usb, i discovered the the SD was not mounted.
I tried to mount the SD but it doesnt work, so i rebooted to recovery and tried to mount there but its coming up with - error unable to mount? ive tried everything but no joy
please please help
Thanks:crying:

see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands

rugmankc said:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
Click to expand...
Click to collapse
I've got a mac
not sure what fastboot is.
I'll check out the link, and thank you very much for trying to help:good:
sorry i do know what fastboot is, yes can get in to it. but ive gone from CWM to teamwin recovery if i go in to the recovery section but that wont let me do anything because the mount. cant even load the phone up

I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track

rugmankc said:
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
Click to expand...
Click to collapse
im going to use someone elses alp top with windows. i'll ytry the all in one thing because thats how i rooted it in the first place. thanks for helping it means alot

good luck on it

[Q] Lg Ls620 (realm) custom recovery

I was trying to find a custom recovery, or any recovery that will work on my lg realm. I boot recovery and it gives me a error message so im guessing its either wiped out or blocked...any ideas out there on how to correct or replace it

twtoned said:
I was trying to find a custom recovery, or any recovery that will work on my lg realm. I boot recovery and it gives me a error message so im guessing its either wiped out or blocked...any ideas out there on how to correct or replace it
Click to expand...
Click to collapse
Looking for one as well. I have not found one.

Recovery is actually preinstalled
I found this just tooling around. Use your favorite file browser, I used
Total commander. /system/vender/itson
The zip file is there. Hope this helps. (Rooted LG ls620)

Could you explain in a little better detail on what you mean Enigmatic177... I'm pulling my hair out Hehe

If anyone makes or finds a working recovery please post it.

Itson is a zip file that was installed after last update it has the basics to unlock the boot loader. I unpacked it used Rom toolbox pro rebooted to RECOVERY did regular reboot system upgraded.
A couple if bit mapp errors 11111. Then I basically flashed CWM.
Before you do this the partitions change from ext2-ext4. I'd advise
Backing them up.

LG Realm & exceed 2 TWRP recovery/fastboot files
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw

TWRP recovery help L620 LG Realm
hello I followed the steps in the read me file and i succeeded in installing twrp although im having troubles booting up to my system os. when i power on my device it takes me straight to twrp. i have a feeling i might of missed a step. i tried creating a backup but i cant because i noticed my screen turns off fast. do you think you might know what might be the problem why i cant boot up to my os? thanks!

I think i know what seems to be the problem. I think i might have accidentally replaced the boot img with the twrp recovery img. i did not make a backup before this happened. is there anything i can do to make my phone boot up to its normal image? thanks

Nope. It is officially a paperweight and no one I know of has access to the stock ROM either.
Sent from my LGLS620 using XDA Premium 4 mobile app

Hey
Has anybody found a custom rom?

Finally. Easy as pie
Ok, I downloaded an image (w5c_twrp_bumped.img)
put that img on the root of my sd card
downloaded Rashr from the google play store
opened rashr and tapped 'recovery from storage', navigated to external sd and tapped the image and tapped
ýes please'
flashed it. after the flash the phone rebooted into the twrp recovery.
then just rebooted back into the system
worked perfectly.
im new here im not allowed to post outside links yet, just google "w5c_twrp_bumped.img" should take you to a link for a download of that recovery
i got twrp now as a custom recovery. on my lg realm.

That_One_Person760 said:
hello I followed the steps in the read me file and i succeeded in installing twrp although im having troubles booting up to my system os. when i power on my device it takes me straight to twrp. i have a feeling i might of missed a step. i tried creating a backup but i cant because i noticed my screen turns off fast. do you think you might know what might be the problem why i cant boot up to my os? thanks!
Click to expand...
Click to collapse
You have the bumped recovery so all i can say if u messed up is to flash a stock rom u can find on google i had to re flash mine a few times messing with root

right on, thanks for the info. I had no problems at all. it all fell in place like i was hoping. The Realm is the easiest device Iv ever rooted, flashed, and messed with. Well, as far as rooting and flashing a custom recovery. dunno bout roms though. Im sure its simple?

The_android_Modder said:
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
Click to expand...
Click to collapse
OK, I grabbed and extracted this. I used Flashify to simply flash the recovery (w5c_twrp_bumped.img) and it works like a dream on my LG Realm.
OTOH, trying the same on an Exceed 2 gets me TWRP, but it cannot mount much of anything and the backup fails. After failing, it tells me "No OS found, continue?" I continue and get the message "Appears your device has no Root, install now?' I am absolutely certain I have root, or wouldn't even be able to run Flashify, so I continue and it simply boots into the OS just fine. Perhaps the readme isn't complete, as I see the following file in the extracted folder (resources.zip) with no explanation of why it's there. It "appears" to be a flash-able zip that installs "itson" (whatever THAT is). Note that the Realm has this in the /system/vendor/itson, yet the Exceed 2 doesn't.
Have you actually used this on an Exceed 2? And if so, what am I missing here?

The_android_Modder said:
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
Click to expand...
Click to collapse
Link is DEAD. Any chance you can reupload this file? I can't make heads or tails of some of this thread and I don't want to destroy this phone. Thanks!!!

petermg said:
Link is DEAD. Any chance you can reupload this file? I can't make heads or tails of some of this thread and I don't want to destroy this phone. Thanks!!!
Click to expand...
Click to collapse
I'll do you one better. Just forget about the post you replied to, as it's convoluted as hell. Install TWRP 2.8.6 from here. Ignore the big red warning about the Realm, as he evidently hasn't updated the OP. You can view my notes regarding the Realm in this reply. Tested several times and verified working better than anything else available. Easiest recovery to install I've ever dealt with (all done with an .apk). The option to access via cold boot (battery pull procedure) is something to behold
Be sure to thank the developer, even if you need to create an account to do so. Very VERY nice work!

fathergweedo said:
I'll do you one better. Just forget about the post you replied to, as it's convoluted as hell. Install TWRP 2.8.6 from here. Ignore the big red warning about the Realm, as he evidently hasn't updated the OP. You can view my notes regarding the Realm in this reply. Tested several times and verified working better than anything else available. Easiest recovery to install I've ever dealt with (all done with an .apk). The option to access via cold boot (battery pull procedure) is something to behold
Be sure to thank the developer, even if you need to create an account to do so. Very VERY nice work!
Click to expand...
Click to collapse
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Before you replied I installed the version 2.8.5 from here:
http://androidforums.com/threads/twrp-2-8-5-0-for-realm-ls620-and-exceed-2-vs450pp.908704/
Is 2.8.6 better? Looks like the 2.8.5 can't be booted into via key combo from power off? Are there any other differences? I just used the Rashr flash tool from the market to flash 2.8.5. Worked flawlessly. This is actually my mom's phone and it wanted to do a system upgrade but I wanted to back it up first so that's the reason I wanted a recovery.
Pretty cool though, this recovery installs just via an APK!!!? That's amazing!
I'm tempted to install this on her phone next time she comes over... it should be fine right?
Thanks again!!!!!!!!!!

petermg said:
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Before you replied I installed the version 2.8.5 from here:
http://androidforums.com/threads/twrp-2-8-5-0-for-realm-ls620-and-exceed-2-vs450pp.908704/
Is 2.8.6 better? Looks like the 2.8.5 can't be booted into via key combo from power off? Are there any other differences? I just used the Rashr flash tool from the market to flash 2.8.5. Worked flawlessly. This is actually my mom's phone and it wanted to do a system upgrade but I wanted to back it up first so that's the reason I wanted a recovery.
Pretty cool though, this recovery installs just via an APK!!!? That's amazing!
I'm tempted to install this on her phone next time she comes over... it should be fine right?
Thanks again!!!!!!!!!!
Click to expand...
Click to collapse
That one will cold boot with the battery pull procedure too. A little further down that thread you'll see I modded it to work correctly with the Exceed 2 in addition to the Realm. I like the 2.8.6 better if only that the dates of the backup are correct now. The 286.apk will work fine and overwrite your current recovery. If you leave it installed, you can always open it and reboot to recovery from within the app. If I have more time I'll post a screenshot, but running late for work. I think the screen dimming/timeout issue was fixed as well, but I haven't verified that. I normally disable that in TWRP anyway, as I like to monitor what it's doing during a backup/restore in case of errors.

fathergweedo said:
That one will cold boot with the battery pull procedure too. A little further down that thread you'll see I modded it to work correctly with the Exceed 2 in addition to the Realm. I like the 2.8.6 better if only that the dates of the backup are correct now. The 286.apk will work fine and overwrite your current recovery. If you leave it installed, you can always open it and reboot to recovery from within the app. If I have more time I'll post a screenshot, but running late for work. I think the screen dimming/timeout issue was fixed as well, but I haven't verified that. I normally disable that in TWRP anyway, as I like to monitor what it's doing during a backup/restore in case of errors.
Click to expand...
Click to collapse
THANKS!!!! I'll make it a point to flash that to my mom's phone next time I get the chance!