I tried to flash non-ruu roms, but it bricked my one x, saying "this build is for development purposes only" on both system boot screen and recovery. Then i flashed RUU and fixed this problem. So is there any chance that i can flash unofficial ROMs? My one x is rogers version, thanks!
aspirinmatt said:
I tried to flash non-ruu roms, but it bricked my one x, saying "this build is for development purposes only" on both system boot screen and recovery. Then i flashed RUU and fixed this problem. So is there any chance that i can flash unofficial ROMs? My one x is rogers version, thanks!
Click to expand...
Click to collapse
That message you are getting on the splash screen is normal (not bricked). There is no avoiding that notice right now. That has nothing to do with being able to flash ROMs. You need to unlock your bootloader and a custom recovery to flash roms
How do you know that your phone is bricked?
mikelebz said:
That message you are getting on the splash screen is normal (not bricked). There is no avoiding that notice right now. That has nothing to do with being able to flash ROMs. You need to unlock your bootloader and a custom recovery to flash roms
How do you know that your phone is bricked?
Click to expand...
Click to collapse
Yeah, I heard that message is "normal", but it's not normal for me XD cuz i can't get in to system and recovery. My phone just freeze there, so i thought that message is the problem, and my one x is bricked. (I already unlocked bootloader following the process provided by HTCdev )
aspirinmatt said:
I tried to flash non-ruu roms, but it bricked my one x, saying "this build is for development purposes only" on both system boot screen and recovery. Then i flashed RUU and fixed this problem. So is there any chance that i can flash unofficial ROMs? My one x is rogers version, thanks!
Click to expand...
Click to collapse
As pointed out that is not a brick notice. That will show up when you unlock your bootloader. Noting you can do about it. Just wait a moment for the ROM to load after you get that screen. If the ROMs aren't loading, make sure you are not flashing international One X ROMs which can actually hard brick your phone.
Edit: Did you just say you can't get into recovery? How about bootloader?
Edit 2: If you can run the RUU then you should be able to get in to bootloader. Are you using TWRP for recovery?
What ROM did you try to flash?
Butters619 said:
As pointed out that is not a brick notice. That will show up when you unlock your bootloader. Noting you can do about it. Just wait a moment for the ROM to load after you get that screen. If the ROMs aren't loading, make sure you are not flashing international One X ROMs which can actually hard brick your phone.
Edit: Did you just say you can't get into recovery? How about bootloader?
Edit 2: If you can run the RUU then you should be able to get in to bootloader. Are you using TWRP for recovery?
Click to expand...
Click to collapse
Yes i can get in to bootloader, as well as fastboot, just not recovery. I tried to flash in ClockworkMod, and recovery(just this name, the official one i guess?). Get confused by how to flash in 4EXT so i didn't try this one and the one you just told me. What do you mean by international One X ROMs? Like the ROMs made based on Taiwan kernel? I'm getting confused that which model my One is now cuz i notice that there is another twin model called "XL" XD, so i think the reason is that i flashed the wrong version of system, as well as recovery? And is there any way to recognize which model my One is? Thanks!
aspirinmatt said:
Yes i can get in to bootloader, as well as fastboot, just not recovery. I tried to flash in ClockworkMod, and recovery(just this name, the official one i guess?). Get confused by how to flash in 4EXT so i didn't try this one and the one you just told me. What do you mean by international One X ROMs? Like the ROMs made based on Taiwan kernel? I'm getting confused that which model my One is now cuz i notice that there is another twin model called "XL" XD, so i think the reason is that i flashed the wrong version of system, as well as recovery? And is there any way to recognize which model my One is? Thanks!
Click to expand...
Click to collapse
You said you had a Rogers One X, so you need to stay in this sub forum. This is for the Snapdragon/LTE version of the One X. The other forum is for the quad core One X. Stay away from that one.
For your phone you need to use TWRP recovery. Do a search in this forum for it and there are tons of threads on how to install it.
aspirinmatt said:
I tried to flash in ClockworkMod, and recovery(just this name, the official one i guess?).
Click to expand...
Click to collapse
You can't flash custom ROMs for recovery. Stock recovery is a picture of the phone with a green circle or red triangle. I think you're confusing ClockworkMod with the stock recovery.
aspirinmatt said:
Get confused by how to flash in 4EXT so i didn't try this one
Click to expand...
Click to collapse
That's good. Because there is no 4EXT recovery for our phone.
aspirinmatt said:
What do you mean by international One X ROMs? Like the ROMs made based on Taiwan kernel?
Click to expand...
Click to collapse
No, what is often called the "international" version of our phone is the Tegra3 quad core version of the One X, which has completely different hardware from our Snapdragon S4 dual core, called the One X in US and Canada, but the One XL elsewhere.
If you flashed a ROM for the "international" One X, you may have really screwed up your phone, as the memory partitions are different, and recovery may have been overwritten by the ROM flash. Although the fact you can get to bootloader and fastboot is a good sign.
Tell us EXACTLY what ROM you tried to flash and where you got it from.
---------- Post added at 03:24 PM ---------- Previous post was at 03:17 PM ----------
Agree that TWRP is the only recovery that should be used with our device. Clockworkmod does not really support our device, its just a port, and it has some known issues due to that.
Try installing TWRP using fastboot: http://www.teamw.in/project/twrp2/99
redpoint73 said:
You can't flash custom ROMs for recovery. Stock recovery is a picture of the phone with a green circle or red triangle. I think you're confusing ClockworkMod with the stock recovery.
That's good. Because there is no 4EXT recovery for our phone.
No, what is often called the "international" version of our phone is the Tegra3 quad core version of the One X, which has completely different hardware from our Snapdragon S4 dual core, called the One X in US and Canada, but the One XL elsewhere.
If you flashed a ROM for the "international" One X, you may have really screwed up your phone, as the memory partitions are different, and recovery may have been overwritten by the ROM flash. Although the fact you can get to bootloader and fastboot is a good sign.
Tell us EXACTLY what ROM you tried to flash and where you got it from.
Click to expand...
Click to collapse
Tnaks, you solved a lot of questions for me I got the roms from a Chinese website, they are all probably for international model! I saw a rom called Revolution HD, is this rom good on my One x? I think i mess up with recovery (i got recovery on that website as well).
Revolution HD is not for our phone. Flashing things for the international One X will not work, and may brick or otherwise damage your phone.
Where did you get Clockworkmod from?
Don't install things from random websites. It makes it really easy to flash the ROM for the "other" One X. Stick to our Development forum, everything here is meant for our phone: http://forum.xda-developers.com/forumdisplay.php?f=1538
If you want to see everything in an organized list, you will enjoy my index: http://forum.xda-developers.com/showthread.php?t=1671237
be nice for him to be able to remove the battery and read his model number =)
aspirinmatt, could you list your bootloader information?
DvineLord said:
be nice for him to be able to remove the battery and read his model number =)
Click to expand...
Click to collapse
He already said its the Rogers version.
Related
I would not post unless i was absolutely stuck so here goes:
I have the AT&T One X and managed to unlock the bootloader with no problem. I want to flash CWM, root, and ultimately install the latest cyanmod.
Im stuck trying to get a functional recovery mod working. I have tried a few different methods of flashing the recovery and a few different versions as well, mostly newer ones ie recovery-clockwork-touch-5.8.3.1-endeavoru and 5.8.4.0. I tried the automatic flash and i have done the commands myself. In the end my phone will not boot recovery, i just get the HTC screen that says something about development purposes only.
I could really use some help as i believe i just bricked my phone as well.
Thank you much
Endeavour is the tegra version of the One X and that's the cwm version you flashed. I have no idea what the consequences of doing that are but you may have bricked your phone. I also suggest using TWRP instead of CWM if you do get your phone working again.
Sent from my One XL using xda-developers app
The fact that you are seeing the HTC screen is promising. You definitely want to be using TWRP instead of CWM if you have the North American HTC One XL (ie. "evita", NOT "endeavor" ). I think you need to download an evita version of TWRP, boot into the bootloader (by holding volume down during boot) and then flash it using fastboot.
OigMan said:
I would not post unless i was absolutely stuck so here goes:
I have the AT&T One X and managed to unlock the bootloader with no problem. I want to flash CWM, root, and ultimately install the latest cyanmod.
Im stuck trying to get a functional recovery mod working. I have tried a few different methods of flashing the recovery and a few different versions as well, mostly newer ones ie recovery-clockwork-touch-5.8.3.1-endeavoru and 5.8.4.0. I tried the automatic flash and i have done the commands myself. In the end my phone will not boot recovery, i just get the HTC screen that says something about development purposes only.
I could really use some help as i believe i just bricked my phone as well.
Thank you much
Click to expand...
Click to collapse
As he said your lucky u Can still get the white screen with a phone as fragile with flashing as this I would of done a bibit more research if I were you...but ultimately your going to hhave to use fastboot commands to get your thing back running I believe go check out many of ththe million " I bricked my phone by flashing a tegra thing " you'll see many trust me best of luck to you and once u get everything settled out don't flash cwm. Its unofficial and bad go with twrp. Great recovery but do your research with a device like this
I managed to unbrick my phone by reinstalling the stock RUU but im still stuck trying to instal CWM. What is the correct version i should be using with my AT&T One x?
OigMan said:
I managed to unbrick my phone by reinstalling the stock RUU but im still stuck trying to instal CWM. What is the correct version i should be using with my AT&T One x?
Click to expand...
Click to collapse
Do not use CWM. Install TWRP by downloading GooManager from the market, opening it, hitting menu and choosing "install openrecovery". That will install TWRP for you.
Sent from my One X using xda premium
OigMan said:
I managed to unbrick my phone by reinstalling the stock RUU but im still stuck trying to instal CWM. What is the correct version i should be using with my AT&T One x?
Click to expand...
Click to collapse
Facepalm downloadgoo manager and install from there
Hey folks,
I successfull instaled CM 10 nightlies but wanted to install Android Revolution HD 12 but I couldn't, it didn't boot. Even my backups didn't boot up. To make it worse, the clockworkmod stop working. I've instaled it again and WHEN I GO TO CLOCKWORDMOD TO INSTALL FROM ZIP, THERE ISN'T ANY FILES IN VIRTUAL SDCARD ANYMORE! I can't boot and I don't have rooms to flash in.
What do I do? I tried to push using adb with no success.
Thanks.
Do you have an International OneX or a ATT OneX?
Android Revolution is NOT for our phone, and CWM is NOT supported for our phone.
Flashing either could brick your phone.
If you can get into bootloader, install TWRP and ONLY flash Roms from this forum
What you could do is download your phones specific RUU and run it. That will completely reset your phone back to the stock ROM/kernel. You'll have to re-lock your bootloader before you run it. from the fastboot cmd prompt type"fastboot oem lock" that will re-lock it.
then, unlock your BL again and flash TWRP over. Than only use ROM/kernel rom this forum, if it's not the international version.
Myrder said:
What you could do is download your phones specific RUU and run it. That will completely reset your phone back to the stock ROM/kernel. You'll have to re-lock your bootloader before you run it. from the fastboot cmd prompt type"fastboot oem lock" that will re-lock it.
then, unlock your BL again and flash TWRP over. Than only use ROM/kernel rom this forum, if it's not the international version.
Click to expand...
Click to collapse
he wont need to relock the bootloader if he can get into hboot.
from there just flash twrp and boot into recovery and flash a ROM
absolutelygrim said:
he wont need to relock the bootloader if he can get into hboot.
from there just flash twrp and boot into recovery and flash a ROM
Click to expand...
Click to collapse
That makes sense.
Every time I was being dumb and nearly bricked my phone from trying to flash over ViperX 2.6 it would get stuck at bootloop. So I just relocked bootloader and ran my RUU and unlocked BL again and flashed over the version for our phone, ViperXL 2.1.
Guys, just solve.
I updated the clockworkmode from 5.8.3.1 to 5.8.4 and now the USB MOUNT works. Now I can copy files without boot and I can install the ROM.
Thanks!
celosouzap said:
Guys, just solve.
I updated the clockworkmode from 5.8.3.1 to 5.8.4 and now the USB MOUNT works. Now I can copy files without boot and I can install the ROM.
Thanks!
Click to expand...
Click to collapse
I don't think you understand.. you shouldn't be using clockwork mod on this phone...
Unless you are in the wrong section..
Seriously, do you have the tegra 3 version or the snapdragon s4? If you have the tegra you are in the wrong section.
If you are in the s4 you better switch to twrp before you get a booboo
Sent from my One X using xda app-developers app
absolutelygrim said:
I don't think you understand.. you shouldn't be using clockwork mod on this phone...
Unless you are in the wrong section..
Seriously, do you have the tegra 3 version or the snapdragon s4? If you have the tegra you are in the wrong section.
If you are in the s4 you better switch to twrp before you get a booboo
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
LOL. I'ts the first time that I heard that ONE X Tegra 3 (I'm using tegra version) it's not compatible with clockworkmod. I Follow 2 different tutorials to install (one on my language pt-br) and other in english and both teaches installing clockwork. About ARHD I was following this page http://forum.xda-developers.com/showthread.php?t=1562603 but it didn't worked. The phone never boots. I quit and installed this stock ROM from this page http://forum.xda-developers.com/showthread.php?t=1546970
celosouzap said:
LOL. I'ts the first time that I heard that ONE X Tegra 3 (I'm using tegra version) it's not compatible with clockworkmod. I Follow 2 different tutorials to install (one on my language pt-br) and other in english and both teaches installing clockwork. About ARHD I was following this page http://forum.xda-developers.com/showthread.php?t=1562603 but it didn't worked. The phone never boots. I quit and installed this stock ROM from this page http://forum.xda-developers.com/showthread.php?t=1546970
Click to expand...
Click to collapse
Wrong. Tegra is compatible. Snapdragon isn't. Wrong forum. Go to the international forum
Sent from my One X using xda app-developers app
celosouzap said:
I'm using tegra version
Click to expand...
Click to collapse
There are 2 different forums. The one you want (Tegra3) is simply "HTC One X". You will see that the title of this (Snapdragon S4) forum is quite different ("AT&T, Rogers HTC One X, Telstra One XL"). Completely different hardware. Be sure to stay within the proper forum for your device, to make sure you don't get the improper advice or download the wrong ROMs, etc.
redpoint73 said:
There are 2 different forums. The one you want (Tegra3) is simply "HTC One X". You will see that the title of this (Snapdragon S4) forum is quite different ("AT&T, Rogers HTC One X, Telstra One XL"). Completely different hardware. Be sure to stay within the proper forum for your device, to make sure you don't get the improper advice or download the wrong ROMs, etc.
Click to expand...
Click to collapse
This.
I ended up doing the same thing he did, but I was in the "HTC One X" with my AT&T HOX..
Almost had a very nice and expensive paperweight but, thanks to Absolutelygrim and a few others I'm working perfectly.
redpoint73 said:
There are 2 different forums. The one you want (Tegra3) is simply "HTC One X". You will see that the title of this (Snapdragon S4) forum is quite different ("AT&T, Rogers HTC One X, Telstra One XL"). Completely different hardware. Be sure to stay within the proper forum for your device, to make sure you don't get the improper advice or download the wrong ROMs, etc.
Click to expand...
Click to collapse
Sorry guys!!! I use the forum just for reading, this was my first time. I appreciate the patience!
I have HTC One X. unlocked bootloader, rooted. Stock version 2.20. Tried to flash CM10 nightly build 01042013 through TWRP. First copied the roms into internal storage. Then used fastboot flash boot boot.img, then entered TWRP to wipe everything, factory reset, then try to flash rom, says error and failed. Tried several times, didn't work. I tried to reboot, the phone enters endless bootloop. Tried to use power+vol to enter fastboot again. Select recovery, phone bootloop, never enters recovery. Then I tried to flash CWM touch to phone. Still cannot enter recovery.
What's worse is that when the phone is on, it cannot charge. When usb is not connected, I can turn the phone off by keep holding power. But once the usb is connected the phone will turn on by itself, and the charging stops -- this way the remaining battery is kept being drained.
Please help! Thanks!!!
Try installing TWRP again via adb.
There is no CWM Touch for our version of the One X (only the non-touch version of CWM, and its not recommended). So you may have flashed a recovery for the wrong device. It doesn't sound like that was the initial cause of your woes, but it may have made the issue worse.
You can also try to relock the bootloader, RUU and start over again (re-unlock, install TWRP and flash).
You sure you downloaded CM10 for our (Snapdragon S4) version, and not the Tegra3 version of the One X? There is no reason that flashing a ROM would mess with recovery, unless you flashed the wrong version.
redpoint73 said:
Try installing TWRP again via adb.
There is no CWM Touch for our version of the One X (only the non-touch version of CWM, and its not recommended). So you may have flashed a recovery for the wrong device. It doesn't sound like that was the initial cause of your woes, but it may have made the issue worse.
You can also try to relock the bootloader, RUU and start over again (re-unlock, install TWRP and flash).
You sure you downloaded CM10 for our (Snapdragon S4) version, and not the Tegra3 version of the One X? There is no reason that flashing a ROM would mess with recovery, unless you flashed the wrong version.
Click to expand...
Click to collapse
I downloaded the ROM through this link
http://forum.xda-developers.com/showthread.php?t=1786696
which brought me to the download site:
http://get.cm/?device=endeavoru
I guess my battery is well below 30% now. I saw people said if I relock it with such low battery, I may end up not able to do anything after. Will that happen? I'll try to flash TWRP first. Thanks
Also, I cannot do adb at this time since I cannot enter system and if I use adb command in cmd on my PC, it says cannot find device.
Do you have a AT&T one x or international? How many cores does it have?
Sent from my HTC One XL using xda app-developers app
HTC One X = International
area51avenger said:
Do you have a AT&T one x or international? How many cores does it have?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
The one is AT&T HTC one x. I think that's the most standard ATT version, I don't know how many cores it has though ..
qb200210 said:
The one is AT&T HTC one x. I think that's the most standard ATT version, I don't know how many cores it has though ..
Click to expand...
Click to collapse
Well if it says AT&T on the top of the phone it's most definitely a dual-core version, instead of the quad-core. But you downloaded a CM-endeavoru ROM which is the international. We here have the device codenamed "evita". It sounds to me that you've bricked your phone, unfortunately. However if it's still booting to the white HTC Screen there might be some hope.
I don't have the link handy, but if you wanna find the unbricking thread, it may help if you have knowledge of Linux
HTC_Phone said:
Well if it says AT&T on the top of the phone it's most definitely a dual-core version, instead of the quad-core. But you downloaded a CM-endeavoru ROM which is the international. We here have the device codenamed "evita". It sounds to me that you've bricked your phone, unfortunately. However if it's still booting to the white HTC Screen there might be some hope.
I don't have the link handy, but if you wanna find the unbricking thread, it may help if you have knowledge of Linux
Click to expand...
Click to collapse
I can still enter fastboot and can flash things into it using cmd from PC usb connection. It's just nothing worked: not able to boot pass htc white screen, keeps rebooting, turns on when usb connected, not able to charge, cannot enter recovery. Tried to re-flash TWRP, didn't work, still cannot enter recovery.
If you can get to fastboot, you're not bricked. Be sure you're pushing the right (Evita) version of TWRP; so far you've loaded your phone up with endeavour stuff.
Does adb devices show your phone? What are you seeing in Device Manager when it's plugged in? Are you sure you have all the HTC drivers installed? You might try switching USB ports and using a different cable.
HTC_Phone said:
Well if it says AT&T on the top of the phone it's most definitely a dual-core version, instead of the quad-core. But you downloaded a CM-endeavoru ROM which is the international. We here have the device codenamed "evita". It sounds to me that you've bricked your phone, unfortunately. However if it's still booting to the white HTC Screen there might be some hope.
I don't have the link handy, but if you wanna find the unbricking thread, it may help if you have knowledge of Linux
Click to expand...
Click to collapse
Thanks for pointing it out. Now I flashed boot.img from evita version and it enters recovery. Now the only question is that how can I download the correct rom into my phone since I don't think I can enter the system? Thanks!
iElvis said:
If you can get to fastboot, you're not bricked. Be sure you're pushing the right (Evita) version of TWRP; so far you've loaded your phone up with endeavour stuff.
Does adb devices show your phone? What are you seeing in Device Manager when it's plugged in? Are you sure you have all the HTC drivers installed? You might try switching USB ports and using a different cable.
Click to expand...
Click to collapse
Now I can enter TWRP, which I used to root this phone before without problems. Now I just need to push the right rom. However, if I choose Mount USB storage, my PC is asking me to format the disk. Should I do that or is there other ways I can push ROM into my phone? Thanks!
qb200210 said:
Now I can enter TWRP, which I used to root this phone before without problems. Now I just need to push the right rom. However, if I choose Mount USB storage, my PC is asking me to format the disk. Should I do that or is there other ways I can push ROM into my phone? Thanks!
Click to expand...
Click to collapse
Now in TWRP, I'm able to use adb push update.zip / to push the CM10 evita ROM into the phone. But when I tried to install, it still reports error:
Updating partition details ...
E: Unable to mount '/sdcard'
E: Unable to mount storage.
E: Mount: Unable to find partition for path '/update.zip'
Error flashing zip '/update.zip'
Updating partition details...
E: Unable to mount '/sdcard'
E: Unable to mount storage.
This happens with or without USB cable connected to PC. Thanks!
Format the sdcard to fat32
Sent from my HTC One XL using xda app-developers app
qb200210 said:
Should I do that or is there other ways I can push ROM into my phone? Thanks!
Click to expand...
Click to collapse
As stated, go ahead and format. It's quite common when having these problems to corrupt your sdcard, esp. when using CWM on this phone.
iElvis said:
As stated, go ahead and format. It's quite common when having these problems to corrupt your sdcard, esp. when using CWM on this phone.
Click to expand...
Click to collapse
Thanks for the tips! Now I formatted it into fat32, reboot into recovery, and I'm able to successfully install the CM10 evita ROM. However, after the reboot, the phone keeps the bootloop. The battery is 50% +. Is there something else I did wrong? Thanks!
qb200210 said:
Thanks for the tips! Now I formatted it into fat32, reboot into recovery, and I'm able to successfully install the CM10 evita ROM. However, after the reboot, the phone keeps the bootloop. The battery is 50% +. Is there something else I did wrong? Thanks!
Click to expand...
Click to collapse
Did you remember to flash the boot.img separately?
iElvis said:
Did you remember to flash the boot.img separately?
Click to expand...
Click to collapse
Yes, I did that. But CM10 didn't work whatever I tried. Then I flashed boot.img of CleanROM and installed CleanROM. Finally it works! Thanks a lot for all the help!
dan6677 said:
HTC One X = International
Click to expand...
Click to collapse
What??? Incorrect, and how can an AT&T user be saying this? The dual core S4 version is called the One X in US (AT&T) and Canada (Rogers), and called the One XL elsewhere.
Outside Canada and US, its true that One X refers to the quad core Tegra3 version. But the term "international" is a bit obsolete at this point, now that the S4 version has been released in some 6 or 7 countries.
The OP said he was on stock 2.20 firmware, which is AT&T. So I knew he had the AT&T version from the start.
To the OP, stick with ROMs and mods from this forum section to avoid the same mistake in the future: http://forum.xda-developers.com/forumdisplay.php?f=1538
---------- Post added at 10:17 PM ---------- Previous post was at 10:14 PM ----------
qb200210 said:
Yes, I did that. But CM10 didn't work whatever I tried. Then I flashed boot.img of CleanROM and installed CleanROM. Finally it works! Thanks a lot for all the help!
Click to expand...
Click to collapse
I know in the past, at least one nightly build of CM10 had a faulty kernel that caused the phone to be stuck on the boot splash. Flashing an older kernel made the ROM boot right up. Maybe that is the case with the one you tried. Or maybe just a bad download.
qb200210 said:
I have HTC One X. unlocked bootloader, rooted. Stock version 2.20. Tried to flash CM10 nightly build 01042013 through TWRP. First copied the roms into internal storage. Then used fastboot flash boot boot.img, then entered TWRP to wipe everything, factory reset, then try to flash rom, says error and failed. Tried several times, didn't work. I tried to reboot, the phone enters endless bootloop. Tried to use power+vol to enter fastboot again. Select recovery, phone bootloop, never enters recovery. Then I tried to flash CWM touch to phone. Still cannot enter recovery.
What's worse is that when the phone is on, it cannot charge. When usb is not connected, I can turn the phone off by keep holding power. But once the usb is connected the phone will turn on by itself, and the charging stops -- this way the remaining battery is kept being drained.
Please help! Thanks!!!
Click to expand...
Click to collapse
I had the same issue today, was trying to flash jellybam. I fastboot flash boot boot.img then entered TWRP and wiped then flashed the ROM and when I tried booting up I was in a boot loop. What I did is entered boot loader mode and factory reset ( which wiped my internal storage) and then I was able to enter recovery.
Sent from my HTC One XL using Tapatalk 2
qb200210 said:
Yes, I did that. But CM10 didn't work whatever I tried. Then I flashed boot.img of CleanROM and installed CleanROM. Finally it works! Thanks a lot for all the help!
Click to expand...
Click to collapse
Glad to hear you got it working. Too many damn bricks around these parts for my taste.
Hi- i'm tyring to root my HTC Inspire 4G. I've downloaded alot of the programs aahk, oneclick, root rescue, etc. not having any luck. one click program gets to #7 and hangs. my rom recovery might be corrupt b/c i cant get into recovery. even when i do a factory reset in settings it hangs on the white htc screen on boot up forever. than need to take battery out. i did manage to unlock the bootloader fine with htcdev.i tried the PD98IMG in my sdcard. but i guess i need to have S-Off which i still have S-On b/c my phone isnt rooted yet, any ideas what i can try.? thanks
mikk65 said:
Hi- i'm tyring to root my HTC Inspire 4G. I've downloaded alot of the programs aahk, oneclick, root rescue, etc. not having any luck. one click program gets to #7 and hangs. my rom recovery might be corrupt b/c i cant get into recovery. even when i do a factory reset in settings it hangs on the white htc screen on boot up forever. than need to take battery out. i did manage to unlock the bootloader fine with htcdev.i tried the PD98IMG in my sdcard. but i guess i need to have S-Off which i still have S-On b/c my phone isnt rooted yet, any ideas what i can try.? thanks
Click to expand...
Click to collapse
If you've unlocked the bootloader you can't do any of that other stuff. You need to fastboot flash a recovery.img. Then flash a ROM from there. Instructions in the Ace Think Tank in the Desire HD General section. Note that the DHD and the I4G are essentially the same phone and have the same rooting instructions, and they can use each others' ROMs.
bananagranola said:
If you've unlocked the bootloader you can't do any of that other stuff. You need to fastboot flash a recovery.img. Then flash a ROM from there. Instructions in the Ace Think Tank in the Desire HD General section. Note that the DHD and the I4G are essentially the same phone and have the same rooting instructions, and they can use each others' ROMs.
Click to expand...
Click to collapse
oh really? I thought i had to first unlock the bootloader to root the phone or is that to jus use a custom rom? i can relock like i did earlier. is that what i need to do? Yes i realize the Desire HD/Inspire 4G same phone. was waiting for ICS and than HTC said too bad.So do you recommend i lock the bootloader back up? I'm new today here. wondering if i posted in right category after i posted. i see a development one to..
There are two ways to root and flash a custom ROM. One is S-Off. The other is unlocking the bootloader. S-off's tool has been retired, so you can only do it manually. You can still root and flash custom ROMs with an unlocked bootloader, though.
bananagranola said:
There are two ways to root and flash a custom ROM. One is S-Off. The other is unlocking the bootloader. S-off's tool has been retired, so you can only do it manually. You can still root and flash custom ROMs with an unlocked bootloader, though.
Click to expand...
Click to collapse
I went to this think tank link below like you mentioned and flashed the recovery. i even flashed a XGS Rom from sdcard.phone is booting up or its stuck on the white screen still but it installed.On #6 i got an error but the install went thru.might have to pull battery and restart it i think.this procedure didnt root my phone right? My phone stuck on the white screen.Might have to redo but like the 4ext recovery. Thanks for the great info!
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
What's an XGS ROM? You're hanging on the boot splash because #6 had an error. Fastboot flashing the ROM zip's boot.img is essential because you are S-On.
mikk65 said:
I went to this think tank link below like you mentioned and flashed the recovery. i even flashed a XGS Rom from sdcard.phone is booting up or its stuck on the white screen still but it installed.On #6 i got an error but the install went thru.might have to pull battery and restart it i think.this procedure didnt root my phone right? My phone stuck on the white screen.Might have to redo but like the 4ext recovery. Thanks for the great info!
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
Click to expand...
Click to collapse
I dont understand #6 theres no boot.img file in that folder. do i have to put one in or rename a file to flash?
Unzip the ROM zip. It'sinside the folders. If the ROM is missing one you need to find a new ROM zip.
bananagranola said:
Unzip the ROM zip. It'sinside the folders. If the ROM is missing one you need to find a new ROM zip.
Click to expand...
Click to collapse
That was the missing link. boot up fine. Thanks again!!. dont know if i need to root my phone or not now.yours rooted? XGS Rom link below. Cool Rom check it out if you like.
http://forum.xda-developers.com/showthread.php?t=1829764
I respect existz too much to use a downstream ROM. Yes, my phone is rooted. But all custom ROMs are rooted, so with XGS you probably are rooted as well.
bananagranola said:
I respect existz too much to use a downstream ROM. Yes, my phone is rooted. But all custom ROMs are rooted, so with XGS you probably are rooted as well.
Click to expand...
Click to collapse
I'll have to check out others avail with my phone. Root checker shows rooted phone. bootloader menu shows S-On still thought it would be S-Off. might run superoneclick root program on it. noticed the music files didnt play. battery drain about the same. Wondering if i can flash a Rom with LTE? unless that is a hardware issue.
mikk65 said:
I'll have to check out others avail with my phone. Root checker shows rooted phone. bootloader menu shows S-On still thought it would be S-Off. might run superoneclick root program on it. noticed the music files didnt play. battery drain about the same. Wondering if i can flash a Rom with LTE? unless that is a hardware issue.
Click to expand...
Click to collapse
Like I said earlier, there are two ways you can root and flash custom ROMs, S-On with unlocked bootloader and S-Off, and you can't have both. If you want S-Off, you would need to relock. And since AAHK (the S-Off tool) is retired, you can only manually S-Off now (which is something I would only recommend for advanced users). Using outdated tools, like AAHK and SuperOneClick, can get you in very bad predicaments very quickly (and I should note that you will probably not find support for those cases). You can look into other ROMs though, and note that the Inspire 4G and the Desire HD are basically the same phone and can use each others' ROMs. Since you are now rooted and can flash custom ROMs through recovery anyway, I would strongly advise that you stick to flashing ROMs now and not try to get S-Off.
LTE is a hardware issue. I4G and DHD don't support it.
bananagranola said:
Like I said earlier, there are two ways you can root and flash custom ROMs, S-On with unlocked bootloader and S-Off, and you can't have both. If you want S-Off, you would need to relock. And since AAHK (the S-Off tool) is retired, you can only manually S-Off now (which is something I would only recommend for advanced users). Using outdated tools, like AAHK and SuperOneClick, can get you in very bad predicaments very quickly (and I should note that you will probably not find support for those cases). You can look into other ROMs though, and note that the Inspire 4G and the Desire HD are basically the same phone and can use each others' ROMs. Since you are now rooted and can flash custom ROMs through recovery anyway, I would strongly advise that you stick to flashing ROMs now and not try to get S-Off.
LTE is a hardware issue. I4G and DHD don't support it.
Click to expand...
Click to collapse
Yeah just want to be able to flash Roms really. dont really need to have phone in S-Off. I'm looking at the Jellybean Rom think by codefirex i want to use. i want the latest ver. think its the 4.2.2 version. do know where can download it? Guess no LTE for awhile then or til my contracts up.
mikk65 said:
Yeah just want to be able to flash Roms really. dont really need to have phone in S-Off. I'm looking at the Jellybean Rom think by codefirex i want to use. i want the latest ver. think its the 4.2.2 version. do know where can download it? Guess no LTE for awhile then or til my contracts up.
Click to expand...
Click to collapse
The OP should have a link.
bananagranola said:
The OP should have a link.
Click to expand...
Click to collapse
Well i found it and flashed it on there. flashed fine and installed. but i dont see but i dont see google store.?
mikk65 said:
Well i found it and flashed it on there. flashed fine and installed. but i dont see but i dont see google store.?
Click to expand...
Click to collapse
When you flash ROMs and/or do anything else with your phone, make sure you read thoroughly. In the case of ROMs, read the OP carefully. It will tell you that you need to flash gapps.
bananagranola said:
When you flash ROMs and/or do anything else with your phone, make sure you read thoroughly. In the case of ROMs, read the OP carefully. It will tell you that you need to flash gapps.
Click to expand...
Click to collapse
Whats "OP"? i found a google play 3.10.14.apk latest ver. i guess and installed it on sdcard but it doesnt stay open. closes right up. probably need to flash it on there.right?
mikk65 said:
Whats "OP"? i found a google play 3.10.14.apk latest ver. i guess and installed it on sdcard but it doesnt stay open. closes right up. probably need to flash it on there.right?
Click to expand...
Click to collapse
I need to start over wipe it out b/c followed below instructions now phone not booting up...keep getting setup wizard has stopped ok button than comes back on.
http://yagyagaire.blogspot.com/2011/12/how-to-flash-google-apps-on-your.html#.UVziMEqmVuQ
.
mikk65 said:
I need to start over wipe it out b/c followed below instructions now phone not booting up...keep getting setup wizard has stopped ok button than comes back on.
http://yagyagaire.blogspot.com/2011/12/how-to-flash-google-apps-on-your.html#.UVziMEqmVuQ
.
Click to expand...
Click to collapse
Found the gapps file i need to flash just dont know when to do it. after i flash the jellybean rom?
OP is the original post in a thread, so post #1. Yes, just flash the gapps zip after the ROM.
Before I get flamed, let me say that I have done ALOT of research on the questions I am about to ask, and the fact of the matter that there is a lot of conflicting information out there. So please bear with me.
I am on a rooted phone, Android 4.1.1, Sense 4+, 3.18.502.6 radio, kernal version 3.4.10
Rooted with S-on
So here's my questions:
1. Can I install a custom rom with S-on?
2. If the answer is yes, can someone give me the quick run-down, or at the very least point me in the direction of another thread that I can refer to?
3. I have read conflicting threads that claim that with S-on, I need to flash the boot.img first, other threads say just go ahead and flash the ROM
Some of these threads are 30+ pages long and go back to 2012. If you miss one post in the thread then you're screwed. Any help is appreciated. For the record these forums have been extremely helpful. Successfully rooted two phones in the past year. I understand the rooting very, flashing custom roms gives me the willies.
First thing, why not just s-off and solve your problems? It's super simple. http://forum.xda-developers.com/showthread.php?t=2155071
But the answer is... Sometimes. Sometimes you need to flash the boot.img. If you're unsure, just do it anyways. This can be done by
1. Extracting the boot.img from the ROM zip archive you wish to flash.
2. Placing it in your adb working directory.
3. Enter fastboot on your phone.
4. fastboot flash boot boot.img
Sent from my HTC One X using Tapatalk 4
RollTribe said:
First thing, why not just s-off and solve your problems? It's super simple. http://forum.xda-developers.com/showthread.php?t=2155071
But the answer is... Sometimes. Sometimes you need to flash the boot.img. If you're unsure, just do it anyways. This can be done by
1. Extracting the boot.img from the ROM zip archive you wish to flash.
2. Placing it in your adb working directory.
3. Enter fastboot on your phone.
4. fastboot flash boot boot.img
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
Thanks Man! I'll give the S-off a shot. I'll take your advice and just flasht he boot.img, just to be on the safe side
I am thinking about flashing the CleanRom, unless anyone has any other suggestions
Fivetenfrank said:
Thanks Man! I'll give the S-off a shot. I'll take your advice and just flasht he boot.img, just to be on the safe side
I am thinking about flashing the CleanRom, unless anyone has any other suggestions
Click to expand...
Click to collapse
If you're s-off there's no need to flash boot.img.
Sent from my HTC One X using Tapatalk 4
RollTribe said:
If you're s-off there's no need to flash boot.img.
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
Thanks. One last question. Ok maybe not the last one but one more question regardless.
With custom roms, does the rom need to be based on the same firmware that's on my stock phone? I other words, right now my phone has build 3.18.502.6. I found a rom that I really like that's based on 3.8.402.1. Is that custom rom compatible with my phone?
Fivetenfrank said:
3. I have read conflicting threads that claim that with S-on, I need to flash the boot.img first, other threads say just go ahead and flash the ROM
Click to expand...
Click to collapse
The short (and incomplete) answer is that "it depends".
If you are s-on and hboot 1.14 or higher, you need to flash boot.img separately using fastboot. A few ROMs (ViperXL, some versions of CleanROM) will flash boot.img in the AROMA installer. But most will not.
Failure to do so will mean the kernel for the custom ROM is not flashed, and you will likely bootloop or be stuck on the boot screen.
Another option, as already mentioned, is to get S-off. But be aware that S-off means that all security checks are bypassed. Meaning you can flash lots of things, with security checks bypassed. Sometimes this is good, sometimes it can be really bad.
---------- Post added at 09:35 AM ---------- Previous post was at 09:29 AM ----------
Fivetenfrank said:
With custom roms, does the rom need to be based on the same firmware that's on my stock phone?
Click to expand...
Click to collapse
Typically no.
There are some exceptions. For instance, if you did OTA or RUU to get on the 3.18 stock ROM, the touch panel firmware was upgraded, and AOSP ROMs will not work right (no touch functions). The solution is to have S-off and downgrade the touch panel firmware.
Fivetenfrank said:
right now my phone has build 3.18.502.6. I found a rom that I really like that's based on 3.8.402.1. Is that custom rom compatible with my phone?
Click to expand...
Click to collapse
Link the ROM, and I can probably answer that for you pretty easily.
Notills his
redpoint73 said:
The short (and incomplete) answer is that "it depends".
If you are s-on and hboot 1.14 or higher, you need to flash boot.img separately using fastboot. A few ROMs (ViperXL, some versions of CleanROM) will flash boot.img in the AROMA installer. But most will not.
Failure to do so will mean the kernel for the custom ROM is not flashed, and you will likely bootloop or be stuck on the boot screen.
Another option, as already mentioned, is to get S-off. But be aware that S-off means that all security checks are bypassed. Meaning you can flash lots of things, with security checks bypassed. Sometimes this is good, sometimes it can be really bad.
---------- Post added at 09:35 AM ---------- Previous post was at 09:29 AM ----------
Typically no.
There are some exceptions. For instance, if you did OTA or RUU to get on the 3.18 stock ROM, the touch panel firmware was upgraded, and AOSP ROMs will not work right (no touch functions). The solution is to have S-off and downgrade the touch panel firmware.
Link the ROM, and I can probably answer that for you pretty easily.
Click to expand...
Click to collapse
It won't link to the rom because XDA won't let me because I am a new user. It's Scott's CleanRom version 6.5. It says its built on the 3.17 OTA build
My phone is a week old. It stock with 4.1.1 and 3.18.502.6. No OTA updates happening here. So can I assume the touchpanel firmware will NOT be an issue since 3.18 is stock?
And I'm not going to mess with S-off. Ill stick with S-on for now.
You should be fine to flash it. Like redpoint said, you may have to flash the boot.img. I can't remember whether CR6.5 flashes the boot.img for you or not. To be on the safe side, go ahead and flash it.
Fivetenfrank said:
It won't link to the rom because XDA won't let me because I am a new user. It's Scott's CleanRom version 6.5. It says its built on the 3.17 OTA build
Click to expand...
Click to collapse
Fair enough. CR6.5 will work great. One thing to note however, recent versions of TWRP (2.4 and 2.5) are known to be problematic and will not work with CR6.5. Either use an older TWRP (2.3) or use the official CWM.
Fivetenfrank said:
My phone is a week old. It stock with 4.1.1 and 3.18.502.6. No OTA updates happening here. So can I assume the touchpanel firmware will NOT be an issue since 3.18 is stock?
.
Click to expand...
Click to collapse
That would be the incorrect assumption. Since the phone came out of the box with 3.18, it will have the upgraded touch panel firmware. Meaning AOSP ROMs will not have a functional touch screen, unless you S-off and downgrade the touch panel firmware.
For Sense ROMs, its doesn't matter, you are fine with the upgraded touch panel firmware.
BTW, please hit the "Thanks" button for any posts that you found helpful!
redpoint73 said:
Fair enough. CR6.5 will work great. One thing to note however, recent versions of TWRP (2.4 and 2.5) are known to be problematic and will not work with CR6.5. Either use an older TWRP (2.3) or use the official CWM.
That would be the incorrect assumption. Since the phone came out of the box with 3.18, it will have the upgraded touch panel firmware. Meaning AOSP ROMs will not have a functional touch screen, unless you S-off and downgrade the touch panel firmware.
For Sense ROMs, its doesn't matter, you are fine with the upgraded touch panel firmware.
BTW, please hit the "Thanks" button for any posts that you found helpful!
Click to expand...
Click to collapse
I think I am in good shape. CleanRom is built on Sense. Ill flash the boot.img first to be on the safe side. Btw according to Scott's website for this Rom, with respect to TWRP vs CWM, this is what he says:
"Must have TWRP Recovery installed with unlocked bootloader! CWM Recovery not supported!" Can I get a clarification?
Once this is all done ill post and let everyone know how I made out. Going back now and "thanking" all who have replied
Fivetenfrank said:
I think I am in good shape. CleanRom is built on Sense. Ill flash the boot.img first to be on the safe side.
Click to expand...
Click to collapse
Since your phone is on 3.18, and CleanROM is 3.17 base, I don't know if you can be completely sure there haven't been kernel changes. You're right, it might be the same (or same enough) kernel, but to be on the safe side, it won't hurt to flash the boot.img.
Fivetenfrank said:
Btw according to Scott's website for this Rom, with respect to TWRP vs CWM, this is what he says:
"Must have TWRP Recovery installed with unlocked bootloader! CWM Recovery not supported!" Can I get a clarification?
Click to expand...
Click to collapse
Its an outdated statement. There was a time where CWM was only a unofficial (somewhat hacked) port, and caused some serious issues for some people, that then wrongly blamed scrosler and his ROM.
None of this is very relevant any longer. CWM is officially supported for our device. It works great with CleanROM 6.5 (its what I'm currently using); when I will guarantee you that the latest TWRP 2.5.0.0 will not work with CleanROM 6.5. And anything after TWRP 2.3.1.1 is known to be problematic for our device. So its really up to you, which recovery is the best to use.
If you pick CWM, this is the thread you want:
http://forum.xda-developers.com/showthread.php?t=2148909
redpoint73 said:
Since your phone is on 3.18, and CleanROM is 3.17 base, I don't know if you can be completely sure there haven't been kernel changes. You're right, it might be the same (or same enough) kernel, but to be on the safe side, it won't hurt to flash the boot.img.
Its an outdated statement. There was a time where CWM was only a unofficial (somewhat hacked) port, and caused some serious issues for some people, that then wrongly blamed scrosler and his ROM.
None of this is very relevant any longer. CWM is officially supported for our device. It works great with CleanROM 6.5 (its what I'm currently using); when I will guarantee you that the latest TWRP 2.5.0.0 will not work with CleanROM 6.5. And anything after TWRP 2.3.1.1 is known to be problematic for our device. So its really up to you, which recovery is the best to use.
If you pick CWM, this is the thread you want:
http://forum.xda-developers.com/showthread.php?t=2148909
Click to expand...
Click to collapse
Ok so noted. CWM is the way to go. So next question. How complicated is the process to remove TWRP before I flash CWM?
Fivetenfrank said:
Ok so noted. CWM is the way to go. So next question. How complicated is the process to remove TWRP before I flash CWM?
Click to expand...
Click to collapse
You don't have to remove TWRP. Just flash over the top of it with CWM.
Egrier said:
You don't have to remove TWRP. Just flash over the top of it with CWM.
Click to expand...
Click to collapse
Got it. Wish me me luck fellas. I am going to give this a whirl tonight
Hey while I have everyone's attention, are there any other roms out there worth checking out for someone like me? That's probably a loaded question given the fact that theres a boat load of Roms out there... but all opinions welcomed!
Fivetenfrank said:
Ok so noted. CWM is the way to go. So next question. How complicated is the process to remove TWRP before I flash CWM?
Click to expand...
Click to collapse
Just for the record, I'm not saying that CWM is necessarily better. Either CWM, or TWRP 2.3.1.1. Your choice. But TWRP 2.5 definitely does not work with CleanROM 6.5, and TWRP 2.4 has issues, also.
As already mentioned, no need to remove TWRP. Just flash CWM, and TWRP will be removed.
---------- Post added at 01:01 PM ---------- Previous post was at 12:58 PM ----------
Fivetenfrank said:
Hey while I have everyone's attention, are there any other roms out there worth checking out for someone like me? That's probably a loaded question given the fact that theres a boat load of Roms out there... but all opinions welcomed!
Click to expand...
Click to collapse
Yes, that is a loaded question. They are all worth checking out! To suggest one (or a few), would suggest the others are somehow "not worth" checking out. Which is really not fair to the devs that have worked so hard to give us these ROMs.
Look through the ROMs, and if any look interesting, try them. This is what most of us do. You already mentioned you aren't going to s-off yet, so the AOSP ROMs are out (due to the touch panel firmware issue).
redpoint73 said:
Just for the record, I'm not saying that CWM is necessarily better. Either CWM, or TWRP 2.3.1.1. Your choice. But TWRP 2.5 definitely does not work with CleanROM 6.5, and TWRP 2.4 has issues, also.
As already mentioned, no need to remove TWRP. Just flash CWM, and TWRP will be removed.
---------- Post added at 01:01 PM ---------- Previous post was at 12:58 PM ----------
Yes, that is a loaded question. They are all worth checking out! To suggest one (or a few), would suggest the others are somehow "not worth" checking out. Which is really not fair to the devs that have worked so hard to give us these ROMs.
Look through the ROMs, and if any look interesting, try them. This is what most of us do. You already mentioned you aren't going to s-off yet, so the AOSP ROMs are out (due to the touch panel firmware issue).
Click to expand...
Click to collapse
Yep, AOSPs are out. Thanks for all of your help everyone. Going to try this tonight. Hopefully I wont have a paperweight by this time tomorrow
Fivetenfrank said:
Yep, AOSPs are out. Thanks for all of your help everyone. Going to try this tonight. Hopefully I wont have a paperweight by this time tomorrow
Click to expand...
Click to collapse
Go slow follow directions and your phone will be fine. Don't skip steps or shortcut anything. That's where problems arise.
Sent from my HTC One XL using xda premium
also inpensi
31ken31 said:
Go slow follow directions and your phone will be fine. Don't skip steps or shortcut anything. That's where problems arise.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Thanks for the heads up. I am good on the instructions. I have found a multitude of posts outlining the steps. My biggest fear is/was the compatibility issue - flashing a rom that's not compatible with my phone. I tried flashing a Rom a couple of months ago on an HTC One X on 2.20, and I bricked it. I flashed the wrong Rom. Luckily AT&T didnt catch it and they gave me a new phone. I had to get another new phone this week past because my old HTC One X died for some unknown reason. AT&T gave me another one on warranty. This new one has the 3.18
Sounds like you flashed a ROM for the quad core "international" version (ENDEAVORU). Stick to this forum (says "AT&T" at the top) and any ROM you flash will be fine.
Or use my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
redpoint73 said:
Sounds like you flashed a ROM for the quad core "international" version (ENDEAVORU). Stick to this forum (says "AT&T" at the top) and any ROM you flash will be fine.
Or use my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
If my memory serves me correctly, that's exactly what I did.