My cwm cannot find my sd card so that means I can't flash zip files. Can anyone help me get cwm 4.0.0.9? Currently I have cwm 5.0.2.7
Sent from my myTouch 4G Slide using xda premium
What's the error? Is it that weird Lum thing?
Sent from my Bulletproof_Doubleshot using xda app-developers app
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
Also the one your on is the most stable, have you tried messing with your SD? This happens to me every once in a while. I just reboot.
Sent from my Bulletproof_Doubleshot using xda app-developers app
AgentCherryColla said:
What's the error? Is it that weird Lum thing?
Sent from my Bulletproof_Doubleshot using xda app-developers app
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
Also the one your on is the most stable, have you tried messing with your SD? This happens to me every once in a while. I just reboot.
Sent from my Bulletproof_Doubleshot using xda app-developers app
Click to expand...
Click to collapse
I think its the lum thing when using terminal emulator but some told me to flash 5.0.2.7 and I did and it's messed up
Sent from my myTouch 4G Slide using xda premium
Is there a problem with the true official CWM release or are you just wanting to change? And at this point, unless you are trying to apply an "update.zip" file you don't need access to your external card.....unless I am just misunderstanding your issue. ADB will flash your new recovery directly to the correct partition on your internal system memory. Won't it??
BTW Agent.....what is that weird "Lum" thing? I've not run across that term.
its the error with opening sdcards on cwm 6.x
xmc wildchild22 said:
its the error with opening sdcards on cwm 6.x
Click to expand...
Click to collapse
Thank you XMC....I'm always anxious to learn. :good:
Do you have any idea why that type of error would pop up out of the clear blue like that?
WeekendsR2Short said:
Is there a problem with the true official CWM release or are you just wanting to change? And at this point, unless you are trying to apply an "update.zip" file you don't need access to your external card.....unless I am just misunderstanding your issue. ADB will flash your new recovery directly to the correct partition on your internal system memory. Won't it??
BTW Agent.....what is that weird "Lum" thing? I've not run across that term.
Click to expand...
Click to collapse
Can you help me with this step by step
Sent from my myTouch 4G Slide using xda premium
K7Cobb said:
Can you help me with this step by step
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
You really won't have any problems. I promise. It flashes just like any other version of CWM thru adb. Just download it from my "Tools" thread, place it where you normally flash a file from, rename the file to boot.img. Then from your command window on your computer you just do the following string of commands:
reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Remember? :good:
flash boot?
WeekendsR2Short said:
You really won't have any problems. I promise. It flashes just like any other version of CWM thru adb. Just download it from my "Tools" thread, place it where you normally flash a file from, rename the file to boot.img. Then from your command window on your computer you just do the following string of commands:
reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Remember? :good:
Click to expand...
Click to collapse
Hang on, isn't he trying to flash his recovery? I've never done it through fastboot, but I can't help but think that flashing a recovery image to the boot partition won't turn out well... There is an option in fastboot to flash recovery, but again, I've never used it.
The way I've always flash recovery images is (in terminal emulator or ADB)
flash_image recovery /sdcard/name-of-recovery.img
As I was looking up this command, I saw someone (well, not just anyone, kornyone) suggest using ROM Manager... Although you would, of course, have to flash an older version of CWM.
My guess could be stupid but try redownloading cwm and reflash cwm recovery ...
Sent from my myTouch_4G_Slide using xda app-developers app
@Weekend um says something about reboot is not recognized as an external command,operable program or batch file. Have any idea as to why this shows and could you help with this problem
K7Cobb said:
@Weekend um says something about reboot is not recognized as an external command,operable program or batch file. Have any idea as to why this shows and could you help with this problem
Click to expand...
Click to collapse
It's an Android command, you need to either run it through ADB Shell or through the Terminal Emulator (You ran it directly in the Windows command line)
Do you have ADB and fastboot setup? If not, go download Android SDK from Google and get it installed. (Be sure to install Platform Tools as well as Tools)
If you haven't setup the Android SDK before, you'll need to install the Java SDK too.
The second two commands he provided are not ADB commands, they should be run directly from the directory where fastboot is installed, which is the Android SDK Install location\platform-tools.
The default Android SDK install location (as of the new version I downloaded yesterday) is C:\Users\(Your Name)\AppData\Local\Android\android-sdk . The old default location was C:\Program Files (x86)\Android\android-sdk . I like that one better. You can use whichever you wish, just be sure you remember where it is.
I can't post links, otherwise I'd link you to a guide. Sorry :/
Nvm thank you all
Sent from my myTouch 4G Slide using xda premium
Sompom said:
Hang on, isn't he trying to flash his recovery? I've never done it through fastboot, but I can't help but think that flashing a recovery image to the boot partition won't turn out well... There is an option in fastboot to flash recovery, but again, I've never used it.
The way I've always flash recovery images is (in terminal emulator or ADB)
flash_image recovery /sdcard/name-of-recovery.img
As I was looking up this command, I saw someone (well, not just anyone, kornyone) suggest using ROM Manager... Although you would, of course, have to flash an older version of CWM.
Click to expand...
Click to collapse
Your way will work but I promise the ADB fastboot flash sequence will too. It's the only way I've ever flashed my recoveries. Always more than one way to skin a cat.
---------- Post added at 10:49 PM ---------- Previous post was at 10:37 PM ----------
K7Cobb said:
@Weekend um says something about reboot is not recognized as an external command,operable program or batch file. Have any idea as to why this shows and could you help with this problem
Click to expand...
Click to collapse
Sorry......I just kinda took something for granted. (as usual)
Before you can run that string I told you about you have to tell your system it is an ADB command. ACTUALLY it's like this:
ADB reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Sorry for my oversight. I hope it didn't cause you much grief.
I do the stuff correct. But when I go to clock work it still says 5027
Sent from my myTouch 4G Slide using xda premium
So when you enter the command it tells you "sending image" and then the time?
After that it tells you "writing image" then the time and then something to the effect of "transfer complete"? If it does then somehow you've gotten the images confused and renamed the 5.0.2.7 image and put that one in your flashing folder and not the 4.0.0.9 image.
It's always your choice what you run on your phone but I still don't understand your opposition to the official CWM release. ANYway....Good Luck in your attempt.
WeekendsR2Short said:
So when you enter the command it tells you "sending image" and then the time?
After that it tells you "writing image" then the time and then something to the effect of "transfer complete"? If it does then somehow you've gotten the images confused and renamed the 5.0.2.7 image and put that one in your flashing folder and not the 4.0.0.9 image.
It's always your choice what you run on your phone but I still don't understand your opposition to the official CWM release. ANYway....Good Luck in your attempt.
Click to expand...
Click to collapse
Omg it does not work Clearly if I'm having problems. Not meant to be taken in a mean way but I keep telling people the same thing
Sent from my myTouch 4G Slide using xda premium
Omg. What is wrong with this???!?!?!?!?!? I need MAJOR HELP!!!
Sent from my myTouch 4G Slide using xda premium
What I'm trying to find out is how in the crap you got 5.0.2.7 on your phone to start with. If you flashed it thru terminal emulator you can put 4.0.0.9 on there the very same way. If you flashed it thru ADB you can put 4.0.0.9 on there the very same way. See what I'm saying? Have you ever flashed anything or did you get it on there thru maybe Rom Manager. I'm just looking for a clue. SEE? I know you're having a problem but we need to more than "it's not working".
K7Cobb said:
I do the stuff correct. But when I go to clock work it still says 5027
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I am running 5.5.0.4 and ROM manager reports the version as 5.0.2.7. Seems to work fine here.
Hastily spouted for your befuddlement
Related
How do I flash cwm image without using fastboot (from within my NS)?
Thanks
Heeter
Sent from my Nexus S using XDA Premium App
ROM manager if you are rooted...
Hi NYYFan325
ROM Manager will install my CWM image?
I know it has an older builtin version (3.0.2.4), but I would like to install the new 4.0.0.2
How would it do that? I can see a flash alternate recovery, but it is not picking up my image on the sdcard.
Is there a specific folder that it has to go into?
Thanks
Heeter
Heeter said:
Hi NYYFan325
ROM Manager will install my CWM image?
I know it has an older builtin version (3.0.2.4), but I would like to install the new 4.0.0.2
How would it do that? I can see a flash alternate recovery, but it is not picking up my image on the sdcard.
Is there a specific folder that it has to go into?
Thanks
Heeter
Click to expand...
Click to collapse
Someone smarter then me will have to chime in if I'm wrong but if you want the newest one (4.0.0.2) you'll have to use fastboot. Any reason your looking to avoid it?
I just like to waaaaay more simpler menus and wipe menus.
The confirmations are gone too, as well as all the "no" down the screen, with one "yes" in the middle.
Like the different color too.
Heeter
I meant why are you avoiding fastboot? Using it will get you 4.0.0.2 in the blink of an eye...
Fastboot refuses to work on my Windows7 machine. Even using the PDAnet drivers and Android SDK drivers, and everything in between.
Been trying to get fastboot to work for months, but just gave up on it. The are several of my posts in here concerning my fastboot issues.
It did work when I switched to Debian, but, because of work issues, I had to switch back to Windows.
Heeter
are you sure? i'm running win7 x64 and everything works just fine.
if you are rooted, you can put any cwm in your device, it's not easy, but can be done, the trick is that you need fastboot to root your device (you could search a exploit to achieve it without fastboot, but...)
Alright, so what you need to to is this:
1. Download the img file somewhere.
2. cd into the directory
3. fastboot erase recovery to erase the current recovery
4. fastboot flash recovery ____.img and voila!
Good luck!
-As NYYFan325 said, you need fastboot in order to do this quick
Oh yeah, make sure ur in the bootloader while doing all this
Heeter said:
How do I flash cwm image without using fastboot (from within my NS)?
Thanks
Heeter
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
You can flash it through ROM Manager with a little tweaking.
Thanks Maximilian Mary,
That is exactly what I was looking for. I renamed it *.img.bak instead of *.img.real. Still worked like a charm, flashed the hotness, LOLOL.
As in previous posts, fastboot is not an option for me.
Thanks again,
Heeter
Put newest recovery on internal usb storage
Rename it recovery.img
Download flash_image gui by Joeykrim
Select recovery and browse to recovery.img
snandlal said:
Put newest recovery on internal usb storage
Rename it recovery.img
Download flash_image gui by Joeykrim
Select recovery and browse to recovery.img
Click to expand...
Click to collapse
I actually purchased that application.
But It says it is only good NS4G, not my NS3G. Unless you can confirm it works on my 3G.
Thanks
Heeter
It works on yours also
Heeter said:
I actually purchased that application.
But It says it is only good NS4G, not my NS3G. Unless you can confirm it works on my 3G.
Thanks
Heeter
Click to expand...
Click to collapse
it works 100%
Sent from my Nexus S using XDA Premium App
mathkid95 said:
Alright, so what you need to to is this:
1. Download the img file somewhere.
2. cd into the directory
3. fastboot erase recovery to erase the current recovery
4. fastboot flash recovery ____.img and voila!
Good luck!
-As NYYFan325 said, you need fastboot in order to do this quick
Click to expand...
Click to collapse
fastboot doesn't work so your instructions are useless.
Try using the app flash image gui
Sent from my Nexus S 4G using Tapatalk 2
You should try with "nexus toolkit".Search google how to use it.
I flashed latest clockwork mod after installing brainmasters ics tweaked. When i noticed my mms wasnt working i decided to re flash another rom but when i booted into recovery it got back into fastboot mode and tells me "no boot or recovery img"
I have re flashed all versions through rom manager but they wont stick. I tried to push it with fastboot and my computer but my Ubuntu 11.10 wont recognize my Ns4g. I installed all the android sdk, adb, and fastboot files but when I type ./adb devices its doesn't come up with my device. ./fastboot flash boot recovery3101.img doesnt work either. Juat says <waiting on device>
flash image by GUI
search market for this app and use it to flash kernel image.
I'm on mobile
Sent from my Nexus S 4G using xda premium
1st. post in the correct section. This way you can get your answer quicker and you're not annoying everyone.
2nd. Find yourself a WINDOWS PC and install android SDK and all drivers for your phone to be recognizable. Then follow one of the posts in here to flash recovery.
You could also install ROM manager from the market and use it to flash recovery through it but its always good to have a proper SDK setup for this type of emergency.
This has happened to me before and I have fixed it by flashing the latest cwmr multiple times.
Try using a different USB cable if your com still doesn't recongize it.
PS now I use twrp and i like it a lot better
Sent from my Nexus S 4G using xda premium
I didnt see any other NS4g section. Sorry bud.
Would flash image gui work well to flash twrp?
When i use rom manager it says successfully flashes rom but then i reboot and get the sane no boot or recovery img. I dont have access to a windows pc...
Can a mod please move this to the nexus help section?
As stated, reboot from and get rom Manager from market. Try reinstalling recovery or scroll down and there is an option to use older versions and flash an older version.
Sent from my Nexus S 4G using xda premium
toddlmr said:
As stated, reboot from and get rom Manager from market. Try reinstalling recovery or scroll down and there is an option to use older versions and flash an older version.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Okay todd,
As stated before, back in my FIRST post i have rom manager and I havr flashed all versions of cwm available. 3.0.0.0 to 5.0.2.0 but none of them stick.
I just got flash image gui and tried to flash twrp and it said it was successful but when i rebooted i got the same no boot or recovery img
Make sure you have debug turned on.
Sent from my Nexus S 4G using xda premium
I had this happen to me when I first flashed a ICS port. the only thing that worked for me was to dl the Flash Image GUI from the market & flash your cwm file.
courtesy of my Nexus S 4G using Tapatalk
bnitty said:
I had this happen to me when I first flashed a ICS port. the only thing that worked for me was to dl the Flash Image GUI from the market & flash your cwm file.
courtesy of my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
+1 agreed it works like a lucky charm.
Sent from my BB GPA19x Linux S 4G using xda premium
might not be what you want to hear, but... maybe start from scratch again. find a guide that lets you revert to the stock image and then reroot. sometimes... you just have to start with a clean slate. good luck man. sounds like a stressful / annoying issue to have.
ehac1680 said:
Make sure you have debug turned on.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I never turn it off
bnitty said:
I had this happen to me when I first flashed a ICS port. the only thing that worked for me was to dl the Flash Image GUI from the market & flash your cwm file.
courtesy of my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
info[]box1 said:
+1 agreed it works like a lucky charm.
Sent from my BB GPA19x Linux S 4G using xda premium
Click to expand...
Click to collapse
I just tried to flash twrp and then cwmr 5.0.2.0 with Flash Image GUI and neither of them stuck...
Is it my only option to ask my friends if I can use their computer? I hate loading things on peoples computer. I feel bad...
mercado79 said:
might not be what you want to hear, but... maybe start from scratch again. find a guide that lets you revert to the stock image and then reroot. sometimes... you just have to start with a clean slate. good luck man. sounds like a stressful / annoying issue to have.
Click to expand...
Click to collapse
Im okay with starting over but I cant even get my computer to recognize my NS4G. I'm using Ubuntu 11.10 and I have Android sdk and fastboot on my computer but when I boot my phone into fastboot it isn't recognized by my computer. All "./adb devices" or "./fastboot devices" brings up is nothing!
If I can get my Linux machine to recognize my phone I would gladly return to stock unrooted and start over.
Flash twice in rom manager. See if that changes anything. Don't reboot between just one after another. Also, in rom manager hit menu and clear download cache before you try flashing.
info[]box1 said:
flash image by GUI
search market for this app and use it to flash kernel image.
I'm on mobile
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Its flash image GUI by joeykrim......
Sent from my Nexus S 4G using xda premium
Ochochinko said:
Im okay with starting over but I cant even get my computer to recognize my NS4G. I'm using Ubuntu 11.10 and I have Android sdk and fastboot on my computer but when I boot my phone into fastboot it isn't recognized by my computer. All "./adb devices" or "./fastboot devices" brings up is nothing!
If I can get my Linux machine to recognize my phone I would gladly return to stock unrooted and start over.
Click to expand...
Click to collapse
No ./ its just fastboot
So it should look like
# fastboot devices
# fastboot flash recovery recovery.img
Etc.
Sent from my Nexus S 4G using xda premium
This happened to me and I was freaking out until I updated super users binary then flashed clockworkmod and it worked fine.
Sent from my Nexus S 4G using xda premium
Oops didn't read both pages
I've had this happen to me several times. The problem happens any time I use an app (i.e. Rom Manager or Flash Image GUI) to flash a new recovery.
The only way I've been able to resolve it is to
1. Flash cwm 3.1.0.1 with fastboot
2. Go into recovery and flash cwm 5.0.2.0.
3. DO NOT update CWM when relaunching Rom Manager or like app.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
No ./ its just fastboot
So it should look like
# fastboot devices
# fastboot flash recovery recovery.img
Etc.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Either work if he is in the right directory.
@OP: Did you follow the Ubuntu guide to have it recognize your device? I'm on Ubuntu and everything works fine for me.
http://forum.xda-developers.com/showthread.php?t=883032
Greetz
Hi all, I have an s-on unlocked htc sensation. Last night I went to bed and woke up to a phone that was dead (forgot to plug in) so I charged it a little bit and then turned it on..only to find that it just stays at the white HTC screen. I then went into recovery and tried to reinstall a clockwork mod recovery(which has worked plenty of times) but this time it said "the folder does not contain any zip files, so I thought, Oh well time to do a fresh install anyway, so I went into the 4ext recovery/wiped everything, then turned on the smart ext..ran super wipe, then installed the elegancia 4.0 2.7, everything went fine...until it finished, EXT4 recovery then says something like creating backup..blah blah blah..then says backup failedthere was an error processing the command (not the exact terminology)..so then i let it restart and again it is stuck at the white htc screen. I then reboot into recovery again, and it says smart 4ext has been disabled, go to tools etc to re-enable..report your error blah blah blah..I just dont get it, i have done this many times, but I am clueless on why it wont boot..i have the latest files etc too 1.27.00 bootloader as well, I am unable to do anything with adb right now..I am at work, but really need a phone today..can someone help possibly?..Thanks a million....Larry
There are lot of blahs in the post
Anyways coming to your post.. Flash the boot.img of the rom you have flashed from bootloader/fastboot
(extra 1 step in flashing roms with SON guide)
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
There are lot of blahs in the post
Anyways coming to your post.. Flash the boot.img of the rom you have flashed from bootloader/fastboot
(extra 1 step in flashing roms with SON guide)
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
I forgot about having to do it that way since I dont have s-off..I cant get to a computer that has adb right now..is there any way I can do this from the phone?..maybe extract the boot.img from the zip file or something like that?Thanks for your help.
dirtylarry10 said:
I forgot about having to do it that way since I dont have s-off..I cant get to a computer that has adb right now..is there any way I can do this from the phone?..maybe extract the boot.img from the zip file or something like that?Thanks for your help.
Click to expand...
Click to collapse
Not possible as you would be using the kernel when you are booting the phone (just like how formatting c drive (where windows is normally installed) is not possible when using windows)
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
Not possible as you would be using the kernel when you are booting the phone (just like how formatting c drive (where windows is normally installed) is not possible when using windows)
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
eah...makes sense...ok cool...thanks for your help..ill get it done this afternoon....
It'll be easier to help if you can provide exact errors you are getting and exactly what you did. Try installing an AOSP ROM and let us know the error you are getting. I've never used smart EXT so maybe let it be disabled and try.
dirtylarry10 said:
I forgot about having to do it that way since I dont have s-off..I cant get to a computer that has adb right now..is there any way I can do this from the phone?..maybe extract the boot.img from the zip file or something like that?Thanks for your help.
Click to expand...
Click to collapse
you can't do it through the phone casue to flash the boot.img you need to be in fastboot mode...
Hello,
I just want to say that please don't say "you should have read instructions more carefully...etc" its too late for that. I'm just trying to see if its possible to get my HOX working again so its not a brick. So please, if you can help me, I will gladly donate to you.
I have a HTC ONE XL (AT&T). I saw a thread today on XDA saying 2.2 was able to be rooted, so I decide to root my HOX. It took a lot of courage, but I was able to root it and unlock the bootloader.
Everything was going great, I decided to flash CM10, the newest one: cm-10-20121025-EXPERIMENTAL-evita.zip. along with gapps-jb-20121011-signed.
First mistake: I did not backup
Recovery is TWRP v2.3.1.0
I wiped cache, dalvik cache, and system, then flashed CM10
Then i flashed GAPPS
I thought I had everything in the bag, rebooted it and let it do its thing. People say the first boot took long time (~5 mins) I gave it 10 mins. Nothing, its stuck on the boot loop.
Then I retried this 2 other times, same thing.
I panicked and accidentally hit factory reset, and managed to clear everything, both of the flashable files (CM10 and GAPPS) from my HOX, now all i can do is go into TWRP recovery. If i try to reboot into bootloader system or recovery it says "NO OS installed! Are you sure you wish to reboot?"
So please, can anyone help me, this was a very costly mistake, but I'm trying to fix it.
CLIFFS:
-Made mistake of not backing up
-Now only boots to TWRP, no flashable files.
First of all bro, you did everything right in the first place except flash the boot.img seperate using fastboot. That's why you bootlooped bc you had no kernel.
Second, don't worry lol. plug in phone to your computer and enter twrp, choose "mount". Get on your computer and download Rom of choice. Once downloaded, extract Rom and seperate the boot.img. rezip Rom. Transfer Rom onto phone.
fastboot boot.img, then flash the Rom through twrp. Then your golden
Sent from my HTC One XL using xda premium
InflatedTitan said:
First of all bro, you did everything right in the first place except flash the boot.img seperate using fastboot. That's why you bootlooped bc you had no kernel.
Second, don't worry lol. plug in phone to your computer and enter twrp, choose "mount". Get on your computer and download Rom of choice. Once downloaded, extract Rom and seperate the boot.img. rezip Rom. Transfer Rom onto phone.
fastboot boot.img, then flash the Rom through twrp. Then your golden
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Hi inflatedtitan,
Thanks for replying, you are a lifesaver, i almost bought another phone... because i thought i was done for.
However, im not sure what you mean exactly as i have not done this flashing before. so i downloaded the rom cm10.
1. so i unizip the rom on my computer
2. copy rom onto phone
3. flash??
thanks please clarify thanks again.
ur a lifesaver.
EDIT: when i hit mount, there are 4 boxes, what do i check (i cant select SD card)? and when i hit mount, it shows up on my computer but asks me to format disk. should i do it?!
As you already factory reseted and lost everything, you should format as the damage is already done lol, it'll get your sdcard back right. But when you extract cm10 on your computer you'll see the boot.img in the folder. Move it to where you have adb and fastboot. THEN rezip Rom and transfer to your phone.
Sent from my HTC One XL using xda premium
---------- Post added at 02:00 AM ---------- Previous post was at 01:59 AM ----------
Do you have fastboot and adb? If so, the boot.img goes here. Fire up command prompt, type this---> fastboot flash boot boot.img
Then proceed to flash the Rom via twrp
Sent from my HTC One XL using xda premium
InflatedTitan said:
As you already factory reseted and lost everything, you should format as the damage is already done lol, it'll get your sdcard back right. But when you extract cm10 on your computer you'll see the boot.img in the folder. Move it to where you have adb and fastboot. THEN rezip Rom and transfer to your phone.
Sent from my HTC One XL using xda premium
---------- Post added at 02:00 AM ---------- Previous post was at 01:59 AM ----------
Do you have fastboot and adb? If so, the boot.img goes here. Fire up command prompt, type this---> fastboot flash boot boot.img
Then proceed to flash the Rom via twrp
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I took a screenshot
http://imgur.com/qcClC
so i copy the boot to the folder with adb and fastboot? and copy cm-10-2012... to my HOX (unchanged)?
Yes exactly, then run fastboot flash boot boot.img
After that is done, open TWRP and run the zip file
Rom will have excluded boot.img . Try it out and see what happens as you recapped. I'm not so sure as your running fastboot through the xfactor program.. but try it out, worst case is you bootloop like last time. If that happens again, you know to download android SDK tools, adb and fastboot and reinstall HTC drivers and start over
Sent from my HTC One XL using xda premium
They are many simple tutorials for rooting but do not know why you guys having hard time. Ok here is
1) You got Android SDK from google + Platform-tools + Google USB Driver -
2) Only for windows - Download htc sync ( It will install necessary htc drivers) - Link
3) Just to check if htc drivers installed properly , open "C:\android-sdk\platform-tools" ( Or folder where adb and fastboot exists) then "Press shift + right click and select "Open command window here" ( open command prompt and cd "folder where adb and fastboot exists).
4) In command window type " adb devices" and see output - If you get output then htc drivers installed properly.
You can skip step 3 and step 4 - These steps are only for verification
5) Goto [ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit and follow the instructions there.
6) Once you successfully root your device using above exploit then goto - [How To] Flash Custom recovery and ROMS after 2.20 root complete the steps to flash custom recovery and if you want to flash ROMS
7) To unlock BOOT LOADER use this link - [INDEX] AT&T/ROGERS One X Resources Compilation Roll-Up , follow the instructions under " BOOTLOADER UNLOCK, SUPER CID, AND S-OFF"
You can also goto this link - [ROOT][2.20] One XL Bootloader unlock & Root guide By XsMagical - Very nice tutorial, if you find above links difficult to follow
Note* : During exploit or flashing recovery they talk about using fastboot commands, In order to execute them you need goto C:\android-sdk\platform-tools" ( Or folder where adb and fastboot exists) then "Press shift + right click and select "Open command window here" ( open command prompt and cd "folder where adb and fastboot exists) and then execute the commands ..
Advice - Do not flash any roms apart from xda
Sent from my HTC One XL using xda premium
uhh guys so i did the whole fastboot thing, everything looked great. but when i try to go back to recovery, im stuck at the htc quietly brilliant
"this build is for development purpose only
do not distribute..." screen. I cant get back to recovery!?
Sorry for being such a noob, i really appreciate your guyses help.
Try it a couple times, if that doesn't work reflash recovery.
donkeybat64 said:
uhh guys so i did the whole fastboot thing, everything looked great. but when i try to go back to recovery, im stuck at the htc quietly brilliant
"this build is for development purpose only
do not distribute..." screen. I cant get back to recovery!?
Sorry for being such a noob, i really appreciate your guyses help.
Click to expand...
Click to collapse
How long did you stay on that screen? Did you see the cyanogenmod boot animation at all?
Sent from my HTC One XL using xda premium
---------- Post added at 02:42 AM ---------- Previous post was at 02:31 AM ----------
Have you tried holding power and volume down? When phone flashes and goes off, release power button and keep holding volume down till you get to hboot. White screen that says fastboot, recovery, facto reset, etc
Sent from my HTC One XL using xda premium
Any progress bro?
Sent from my HTC One XL using xda premium
you don't delete boot.img from the rom, leave the original zip untouched. just make sure you flash boot.img in fastboot though. whenever i flash something in fastboot i like to run "fastboot erase cache".
NEVER factory reset in bootloader, it will mess up your sdcard.
you should rewipe and reflash everything in twrp. also verify the md5 checksums of cm10 and gapps both the md5 sums are listed at their download locations.
Fixed an gone like a teenager an his car?
WR
Sent from my HTC One X
WarRaven said:
Fixed an gone like a teenager an his car?
WR
Sent from my HTC One X
Click to expand...
Click to collapse
yep that's another thing i've asked all the querying noobs to do, changing the op to [SOLVED] when it is but to no avail :crying:
sry guys it took very long, i followed all your instructions and finally fixed it last night. I went straight to sleep because of work. Thanks again for your help, sorry for late restponse:
my solution: I followed INFLATEDTITAN's instructions. double click the cm10 rom, then take out the boot.img, copy that to where your fastboot files are, SHIFT right click, select CMD (or open cmd and use cd to change directory to folder), then type what he said w/ fastboot, make sure your connected. Then i flashed the cm10 rom, the gapps, reboot, took a couple tries.
Anyways, it works great, so smooth.... on wifi.
I have stragiht talk, and I've been getting really crappy speeds for data, from 5Mbps to 0.16.... down, interestingly, upload has not changed ~1.2 mbps. does anyone have any insight? Why DL is so slow but UL is still the same?
Crappyvate said:
yep that's another thing i've asked all the querying noobs to do, changing the op to [SOLVED] when it is but to no avail :crying:
Click to expand...
Click to collapse
Can you tell me how to edit my post? i can only edit the content, not the title.
Also I have a question on radios. From this thread: (click "this")
I have the latest cm10 nightly build, as I said in my previous post, I am on straight talk. While the radio is showing HSPA+, I'm getting edge speeds (0.16mbps) but good upload speed ~1.2mbps.
Can I use the AT&T 2.2 radio from this list? (near the bottom)
Radios for Latest CM10 versions (with radio in /system/etc/firmware)
I just rooted my phone from 2.2, and want to make sure I'm using the right one.
Thanks.
Sorry bro, can't flash radios and RILs being you have the newer hboot
Sounds like you're into aosp roms. But usually the newer sense Roms are just as amazing and usually are updated with the newer radio. However I'm using old hboot, so I can't confirm that if you flash a Rom, the included radio will also automatically flash. Can anyone reading help with the correct answer?
Sent from my HTC One XL using xda premium
InflatedTitan said:
Sorry bro, can't flash radios and RILs being you have the newer hboot
Sounds like you're into aosp roms. But usually the newer sense Roms are just as amazing and usually are updated with the newer radio. However I'm using old hboot, so I can't confirm that if you flash a Rom, the included radio will also automatically flash. Can anyone reading help with the correct answer?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Thanks, so the only thing i can do at this point is to flash a original HTC ICS rom (basically where i started before root)?
Well like I say, I'm not even sure it'll install the new radio lol. So I'd sit tight till someone replies with the correct advice.
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
---------- Post added at 03:29 PM ---------- Previous post was at 03:27 PM ----------
I'm in hpsa and that's about what I get too. I'll get a few tests that'll nail about 6 on download speed, sometimes I can't even get 1 lol. I wouldnt worry too much unless it gets super sluggish when you have full service
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Ok, I've looked through the help sections, I've Googled my issue [a few times now], so now time to ask for help. [which may or may not be well recieved.]
I was running Viper 3.2.6 fine for about a month, I loved the rom, however I started getting repeated FCs and errors, so I decided to recover my nandroid backup. That didn't work very well, and my phone started to bootloop... I then decided to re-flash viper, re-install twrp [first 2.4.4.0, then when that version wouldn't work, 2.4.1.0] Now when flashing Viper [any JB version I've tried] all my phone does is hang on the HTC startup screen, then reboot back to TWRP. Not to mention that Viper is the only sense ROM that my phone will accept. I've tried fastboot flashing the boot.img, fastboot erasing cache, and running the Nocturnal SD fix to give myself a clean slate to work with.
I'm S-on and HBoot 2.14. Any help that can be provided would be appreciated.
I would post a logcat, but when I tried it would not output anything since the phone is not getting to the rom boot animation.
Try flashing the boot image separately. Or going s-off. I have had troubles with twrp higher than 2.4 before I went s-off.
I always stayed on 2.3
Sent from my HTC One X using xda premium
---------- Post added at 04:53 PM ---------- Previous post was at 04:49 PM ----------
May sound silly but are you typing the word "boot" in twice when flashing?
Sent from my HTC One X using xda premium
Venomtester said:
Try flashing the boot image separately. Or going s-off. I have had troubles with twrp higher than 2.4 before I went s-off.
I always stayed on 2.3
Sent from my HTC One X using xda premium
---------- Post added at 04:53 PM ---------- Previous post was at 04:49 PM ----------
May sound silly but are you typing the word "boot" in twice when flashing?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
As far as flashing the boot image, I type fastboot flash boot boot.img.
And with the S-Off situation, I looked into that, but most of the tools for that seemingly require a working ROM, as usually they require you to have "usb debugging enabled" Like I stated previously, I've tried to solve the issue myself, to no avail thus far.
Also being hboot 2.14 twrp 2.3.x seems to not have touchscreen.
So you have no working Rom? Or can you flash viper again?
Sent from my HTC One X using xda premium
Magickalhack said:
As far as flashing the boot image, I type fastboot flash boot boot.img.
And with the S-Off situation, I looked into that, but most of the tools for that seemingly require a working ROM, as usually they require you to have "usb debugging enabled" Like I stated previously, I've tried to solve the issue myself, to no avail thus far.
Also being hboot 2.14 twrp 2.3.x seems to not have touchscreen.
Click to expand...
Click to collapse
Pretty sure you can s-off purely from boot loader.
2.3.x has working touchscreen for 2.14 and would solve all your issues. You'd have to wipe everything and reflash viper though
Sent from my One X using xda app-developers app
Also check fastboot device too make sure adb is reading your phone.
Sent from my HTC One X using xda premium
exad said:
Pretty sure you can s-off purely from boot loader.
2.3.x has working touchscreen for 2.14 and would solve all your issues. You'd have to wipe everything and reflash viper though
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Just tried 2.3.1 and no, the touchscreen didn't work, I was looking for a d/l for 2.3.3.x but haven't been able to find one. all of the ones I have found have been removed, or changed to 2.4.4.0
I would be quite greatful if you could point me in the direction of a 2.3.3.x twrp that works.
With S-Off, all the guides I've found by searching XDA [and google, which usually points me back to XDA] state that I need to start with USB debugging enabled, I even tried to start the process in fastboot... still no-go.
So you have no working Rom? Or can you flash viper again?
Click to expand...
Click to collapse
None, Every time I try venom it looks like it flashes just fine, says it's successful, however I just end up looking at twrp again.
Venomtester said:
Also check fastboot device too make sure adb is reading your phone.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
When I did fastboot devices I got:
HT26PW300712 fastboot
Click to expand...
Click to collapse
https://dl.dropbox.com/u/19685555/openrecovery-twrp-2.3.3.1-evita.img
MD5: D903047E6E871ACB8F99834C30EB8307
As for the USB debugging. It's just so you can use ADB to boot to fastboot. You can go into bootloader and go to fastboot and then skip step 3. -_-
http://forum.xda-developers.com/showthread.php?t=2155071
Just trust me, Install TWRP 2.3.3.1, reflash viper (wipe everything first, cache, dalvik, system, factory reset) and your fine, or S-OFF and then do it or vice versa, whatever you want.
---------- Post added at 06:17 PM ---------- Previous post was at 06:02 PM ----------
I forgot to add, and I am so sorry, to do fastboot erase cache after flashing twrp 2.3.3.1, just in case.
exad said:
https://dl.dropbox.com/u/19685555/openrecovery-twrp-2.3.3.1-evita.img
MD5: D903047E6E871ACB8F99834C30EB8307
As for the USB debugging. It's just so you can use ADB to boot to fastboot. You can go into bootloader and go to fastboot and then skip step 3. -_-
http://forum.xda-developers.com/showthread.php?t=2155071
Just trust me, Install TWRP 2.3.3.1, reflash viper (wipe everything first, cache, dalvik, system, factory reset) and your fine, or S-OFF and then do it or vice versa, whatever you want.
---------- Post added at 06:17 PM ---------- Previous post was at 06:02 PM ----------
I forgot to add, and I am so sorry, to do fastboot erase cache after flashing twrp 2.3.3.1, just in case.
Click to expand...
Click to collapse
For s-off, if you don't use supercid, it doesn't seem to work, I did not use super cid, since I didn't need to to unlock my bootloader. I tried that method already.
Though, 2.3.3.1 is working; but viper XL 3.2.6 is still fighting with me... Now it's just hanging at the HTC boot screen with the annoying red script.
Magickalhack said:
For s-off, if you don't use supercid, it doesn't seem to work, I did not use super cid, since I didn't need to to unlock my bootloader. I tried that method already.
Though, 2.3.3.1 is working; but viper XL 3.2.6 is still fighting with me... Now it's just hanging at the HTC boot screen with the annoying red script.
Click to expand...
Click to collapse
Did you fastboot erase cache then wipe everything and reinstall viper after installing twrp 2.3.3.1? If so:
http://forum.xda-developers.com/showthread.php?t=2212737
Do this. Then soff then ruu with your bootloader kept unlocked then reinstall twrp 2.3.3.1 then flash viper
Sent from my One X using xda app-developers app
exad said:
Did you fastboot erase cache then wipe everything and reinstall viper after installing twrp 2.3.3.1? If so:
http://forum.xda-developers.com/showthread.php?t=2212737
Do this. Then soff then ruu with your bootloader kept unlocked then reinstall twrp 2.3.3.1 then flash viper
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Followed your instructions to the letter[I actually wiped everything twice before installing Viper.], same result, still hanging at the white HTC screen. I'm going to keep trying though. Thank you for the help thus far.
Magickalhack said:
Followed your instructions to the letter[I actually wiped everything twice before installing Viper.], same result, still hanging at the white HTC screen. I'm going to keep trying though. Thank you for the help thus far.
Click to expand...
Click to collapse
I've seen this before. You will have to s-off and ruu so follow my last post.
Sent from my One X using xda app-developers app
exad said:
I've seen this before. You will have to s-off and ruu so follow my last post.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
The only issue, is that it requires adb; since I cannot get a rom to load; when I adb, it just outputs device not found. I was able to find the file to hex edit using twrp file manager, and edited the right part, but it won't let me over-write the original file... any suggestions?
Magickalhack said:
The only issue, is that it requires adb; since I cannot get a rom to load; when I adb, it just outputs device not found. I was able to find the file to hex edit using twrp file manager, and edited the right part, but it won't let me over-write the original file... any suggestions?
Click to expand...
Click to collapse
You should be able to adb from recovery no?
Sent from my One X using xda app-developers app
exad said:
You should be able to adb from recovery no?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I can adb sideload; but when I try to run the commands it just keeps saying "error: closed" I'll try again though.
Magickalhack said:
I can adb sideload; but when I try to run the commands it just keeps saying "error: closed" I'll try again though.
Click to expand...
Click to collapse
Sorry I hadnt had to do this till now. OK here's what you need to do. In recovery advanced. Go to terminal command select root dir "/". And then do the "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4" on your phone. This will pull the file. Mount your SD card in twrp and hex edit the mmcblk0p4 file on your sdcard like in my guide then save it in the same spot, make sure file size matches then go back to terminal command and select the root "/" directory again and type
"dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4" from your phone. This will push the edited file back.
This is a bit more advanced but will work since you cannot adb. Adb just allows you to use the phones terminal remotely. Instead were actually using it on the phone.
Sent from my One X using xda app-developers app
exad said:
Sorry I hadnt had to do this till now. OK here's what you need to do. In recovery advanced. Go to terminal command select root dir "/". And then do the "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4" on your phone. This will pull the file. Mount your SD card in twrp and hex edit the mmcblk0p4 file on your sdcard like in my guide then save it in the same spot, make sure file size matches then go back to terminal command and select the root "/" directory again and type
"dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4" from your phone. This will push the edited file back.
This is a bit more advanced but will work since you cannot adb. Adb just allows you to use the phones terminal remotely. Instead were actually using it on the phone.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
actually, I had considered something similar, I just didn't know what directory I would have needed. I'll try this out and let you know.
Magickalhack said:
actually, I had considered something similar, I just didn't know what directory I would have needed. I'll try this out and let you know.
Click to expand...
Click to collapse
I tested it before telling you so it will work. then you can s-off.
Sent from my One X using xda app-developers app
exad said:
I tested it before telling you so it will work. then you can s-off.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
It's not liking the: adb shell su -c "/data/local/tmp/soffbin3" command. It's outputting: /sbin/sh: su: not found
I flashed SuperSU and I'm getting the same error.
Magickalhack said:
It's not liking the: adb shell su -c "/data/local/tmp/soffbin3" command. It's outputting: /sbin/sh: su: not found
I flashed SuperSU and I'm getting the same error.
Click to expand...
Click to collapse
Sorry man, I fell asleep. You still stuck at this part?
Sent from my One X using xda app-developers app