When I started this project I guess I thought I knew more than I did. I had installed Cyanogen on multiple other devices, but this one got me. I apologize profusely, I'm not usually one to ask for help but I promise I've been scouring these forums and the web for about 8 hours straight now to no avail. (In all likelyhood I'm just an idiot). Anyway, I'll spell out my problem as best I can.
Basically what I want as a final result is CM 10.1 RC2 Jelly Bean 4.2.2 on my HTC One X at&t. Right now, I'd just like to be able to install any rom at all. I currently don't have anything working and I believe accidentally wiping "system" did that.
When I try to flash it from CWM it just stops and says (Status 7). It seems every rom I try to install comes up with some error there.
Could rooting be a problem? I tried installing several superuser.zip files I could find online. One seemed to work, though I think it's an old one. The latest one I tried came up with error (status 0).
Do I need s-off? I've been trying the "All in one" tool for that but with no luck. I also tried installing SuperUser with the same tool, but it said "Device not found", even though I could reach it via adb fast boot.
Finally, when I try to boot normally it bootloops between the "HTC quietly brilliant" screen, and the same one with the red text that says "this build is for development purposes only. Do not distribute..."
It's 3 in the morning and I should probably get a little sleep before work tomorow. Thanks a ton for reading!
I have the same problem! My phone doesnt have a rom on it at all after this.. When i go to cmd and try to flash a rom, it says something like "cannot open filename.img"
First things first. What firmware and hboot versions are you on?
Secondly, try using TWRP recovery instead of CWM. It can be found here. Flash it using fastboot with the following command:
fastboot flash recovery recoveryfilename.img (whatever the exact recovery filename is)
Then do:
fastboot erase cache
fastboot reboot-bootloader
Thirdly, where are you downloading cm from? You should only get it from here.
Sent from my Evita
---------- Post added at 07:17 PM ---------- Previous post was at 06:54 PM ----------
PS. flashing a superuser.zip while you have no OS installed will do absolutely nothing.
Sent from my Evita
I think everyone with the evita should be s-off. it helps get rid of many annoyances with this phone. also nothing is being done that uses s-off that is really that dangerous.
You should be supercid,s-off,latest ruu 3.17 or 3.18(at&t) then flash recovery and then flash supersu zip to get stock rooted, or you can just wipe the phone and flash a custom rom. i currently use cwm and havent had trouble with it. you can get latest unofficial cwm builds here http://goo.im/devs/mdmower
Related
Now first off I'd like to start saying that I've seen a few threads from a search with this issue but none of them matched my case perfectly or solved the issue.
I have an AT&T HTC One X and was running CleanRom DE 1.0
I saw there was an upgrade out and tried installing the upgrade. I tried running the RUU but it gave me an error 155 (Unknown error). Thinking that it did not matter to much, I tried to install the new version anyway. This got me stuck in a boot loop of the boot animation for about 1 second, then rebooting. I have CWM recovery installed and can adb/fastboot but I cannot do much else. I pushed a 1.7 rom to my sdcard but CWM gives me the message, "Error: Cannot mount /sdcard/"
My phone is unlocked but locking it did not change anything, still could not load anything or use the RUU.
I've seen other threads saying to Lock the phone, then flash the ruu and I guess I'm a little confused on that. By saying "flash the ruu" do you mean just running the .exe file or doing something with fastboot flash? I'm stuck without a phone right now and any help would be appreciated.
In my situation, I deleted the user memory and dalvik cache. I then did some research on my phone's exact stock ROM. I flashed the ROM and basically started off fresh. It may not be the most convenient. But, it may be what is needed. It sounds as if your phone is 'soft-bricked' so this should work as the last ditch effort.
Best of luck!
Sent from my MB865 using xda premium
Thankyou for your reply, I'm new to android and I'm wondering what exact steps went into flashing the stock rom onto your phone? Let's assume I already have that stock rom. Are you just using fastboot flash boot rom.zip ? or using CWM?
EDIT: My phone is now booting! I kept launching the RUU and after about four times it decided to work. Back to the stock AT&T rom, and right now I'm great with that.
was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.
What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.
first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off
No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?
I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.
i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.
i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.
well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.
Hey all, been a member here for years but dont post offten. Normally able to get the info i need from other posts but this time i am stuck Just wondering if anyone has had the same issue flashing a One S C2 with the S3 CPU that im having now. It was stuck with 4.0.3 with hboot 2.09.001, raido 16.05.2.24_M and CID OPTUS001...
Last night i dev unlocked it via the HTC site and flashed TWRP 2.4.4.0 recovery. Tried to put on luxandroidROM v4 but it failed part way through ROM install. The progess bar just got to a point and stopped?? I noticed i had a hboot that was too old for the JB ROM so tried BackToBasics v3 (ICS) ROM but that did the same thing...
Thinking it was maybe just a issue with the ROMs, i tried TrickDroid 6 and CM10 Unofficial build but that was doing the exact same thing... Tried redownloading all the ROMs and looking into SupoerCID but as other with the S3 CPU have reported, it all appears to have worked but does not change the CID Oddly enough when i was in ADB Shell while the phone was sitting on the TWRP recovery mode the SU command was not working. Relevent?
I'm now thinking the issue is the phone is not getting permissions to write the ROMs but have no idea how to correct this. I made sure TWRP has all sections mounted (not sure if this is needed as i normally use CWM) but didn't help.
TWRP keeps saying device isnt rooted when i go to reboot it but fails to root when i tell it to on exit. I have manually flashed SuperSU through TWRP and tried fixing permissions. Tried full factory wipe, Bulletproof-S3-1.3 Kernal and SuperSU again. Still nothing.
Not able to find a RUU for the OPTUS001 CID. Tried extracted version of RUU_VILLEC2_U_ICS_40_hTC_Asia_WWE_1.11.707.112_Radio_16.12.20.02U_16.05.20.16_M2 with CID changed in texts files but it still saied with carrier ID issue
This would be the first time i think i have bricked a phone Does anyone have any suggestions? At this point i would be happy for a nandroid backup to go back to sock and just like with 4.0.3
$40 reward to whoever provides me the info i need to fix this
On the s4 versions of TWRP newer than 2.4.0.0 have issues. I'm not sure if they affect the c2 version but I shouldn't hurt to try an older version.
Sent from my HTC One S using xda app-developers app
TWRP 2.4.4.0 has known bugs. Downgrade to 2.3.3.0 or 2.3.3.7.
And remember to open (BUT NOT EXTRACT) the .zip and to copy and paste the boot.img into your fastboot working environment and manually flash it with this command:
fastboot flash boot boot.img
Then try to flash the ROM that you got the boot.img from. This should work.
Sent from my One S using xda premium
Managed to get this working, figured i would post in case anyone else runs in this issue.
Tried multiple versions of TWRP and no matter what one i tried the roms were unable to write to the stoage. Had to format the phone storage using boot cd - I used GParted through a virtual to do so.
Once that was done TWRP 2.4.4.0 worked fine to flash rom. Still stuck with 4.0.3 with hboot 2.09.001 due to the optus CID but phone is atleast alive. Thanks all for the input
I had been needing to update my phone for a few months now, but because I'm super lazy and I have to flash the boot.img with a pc first, I avoided it... until tonight.
First, I had CM10.1 flashed, did my usual thing: dled the latest nightly, extract zip file, wipe, flash boot.img... went to flash nightly (which I noticed only after was 10.2 nightly) and it failed.
I had done a backup before all of this, but restoring the backup does nothing. Stuck at the HTC splash screen with red text.
When I noticed I was trying to update from 4.2.2 to 4.3, I found the thread on here and noticed that to do so, I had to attain S-Off first. I followed the instructions to do so and at the very last step ( adb shell su -c "/data/local/tmp/soffbin3" ), there's an (unwanted) error. It says su directory not found. In the last successful boot I had before all of this, I know debugging was enabled, and I had flashed superuser.zip in TWRP successfully, and I know I had SuperCID. There was also an issue where, when the instructions state the system should boot to android, my phone just turns off. I booted into TWRP and continued the steps...
I got fed up with all of this and just tried to flash CM10.1. Went through all my normal steps, but now the install fails (Error 7). (I tried the trick where you remove some lines of code, but when I try to flash the altered zip, it just fails. No error listed.) I think it's because of the S-Off attempt. (MID is PJ8312000 I THINK... I recognized it from the S-Off process.)
I've tried everything: updated TWRP, switched to CWM, restored backup AGAIN... still stuck. I need help
When you made your backup did you backup boot? And when you restored did you flash that boot?
What ROM were you on when you attempted the s-off process? You said you couldn't get anything to boot, so if you didn't have a bootable ROM installed that's why it failed.
You should really never removed lines of code from an updater script if a ROM won't install, it's stopping it for a reason. Every time I've seen someone do this and the ROM flashed "successfully" it's bricked their phone.
Lastly, cm10.2 doesn't require s-off. It does require you to run the 3.18 RUU first though, and that requires s-off.
Sent from my Evita
timmaaa said:
When you made your backup did you backup boot? And when you restored did you flash that boot?
What ROM were you on when you attempted the s-off process? You said you couldn't get anything to boot, so if you didn't have a bootable ROM installed that's why it failed.
You should really never removed lines of code from an updater script if a ROM won't install, it's stopping it for a reason. Every time I've seen someone do this and the ROM flashed "successfully" it's bricked their phone.
Lastly, cm10.2 doesn't require s-off. It does require you to run the 3.18 RUU first though, and that requires s-off.
Sent from my Evita
Click to expand...
Click to collapse
Hey, thanks for responding!
I can't remember the nightly I was on exactly, but it was definitely CM10.1 (Android 4.2.2). I don't think it's hard bricked. (I can still access bootloader and recovery.)
Do you have any advice on what I could/should do (besides hang myself... :crying...?
vowelsounds said:
Hey, thanks for responding!
I can't remember the nightly I was on exactly, but it was definitely CM10.1 (Android 4.2.2). I don't think it's hard bricked. (I can still access bootloader and recovery.)
Do you have any advice on what I could/should do (besides hang myself... :crying...?
Click to expand...
Click to collapse
Hey, I flashed the boot.img from the nandroid backup then restored. Finally got it working again!
Thanks for the help; please close thread!
Good news. Time to get s-off? If so, I'd suggest temporarily flashing a 4.1 ROM purely for s-off process, many folks have had trouble with it working 4.2 ROMs.
Sent from my Evita
vowelsounds said:
I don't think it's hard bricked. (I can still access bootloader and recovery.)
Click to expand...
Click to collapse
Just for future reference: If the screen comes on for this device, its almost certainly not bricked, and you can recover.
---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
vowelsounds said:
Thanks for the help; please close thread!
Click to expand...
Click to collapse
Why do folks always ask for their threads to be closed the second they resolve their problem? Its not your decision to make. Threads stay open, in case others want to make further comments or ask their own questions.
The only time threads on XDA get closed typically, is if there is some kind of excessive fighting/conflict, or rules have been broken.
HI! Today I got an HTC Sensation from a friend and it was laggy due to it's stock rom with preinstalled apps and stuff, so I decided to move to a custom ROM, the first one which caught my eye was 5.0 CM12 from the development section, so I copied it to sdcard.
I have managed to unlock the bootloader through the htcdev site and then flashed the lasted CWM Recovery available, 5.8.0 and then formatted cache, data, system, dalvik, because that's what I've always been doing on my Galaxy S2, it was very straight forward.
But now, I can't install a custom rom, tried that one and the slim pyramid one, even a cyanogenmod rom but still no luck. It would abort the installation and output an error about filesystems which can't be found or it woudn't say nothing but will restart the phone straight to recovery mode.
Also, tried 4ext recovery and still no luck. At this point I started panicking and tried to resolve this by installing the stock rom, RUU.
Downloaded RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed , which is the perfect match for my phone but also fails to finish installation, telling me something about failed/unknown mounts/filesystem... If it will help, I will tell you exactly what the error is.
At this moment I have S-On in bootloader, and can't see any radio serial metioned at the top. Tried some instructions flashing PG58IMG.zip , but it doesn't seem to do anything.
Please, help me out because at this point my phone won't go anywhere but bootloader and recovery.
AKAndrew41 said:
HI! Today I got an HTC Sensation from a friend and it was laggy due to it's stock rom with preinstalled apps and stuff, so I decided to move to a custom ROM, the first one which caught my eye was 5.0 CM12 from the development section, so I copied it to sdcard.
I have managed to unlock the bootloader through the htcdev site and then flashed the lasted CWM Recovery available, 5.8.0 and then formatted cache, data, system, dalvik, because that's what I've always been doing on my Galaxy S2, it was very straight forward.
But now, I can't install a custom rom, tried that one and the slim pyramid one, even a cyanogenmod rom but still no luck. It would abort the installation and output an error about filesystems which can't be found or it woudn't say nothing but will restart the phone straight to recovery mode.
Also, tried 4ext recovery and still no luck. At this point I started panicking and tried to resolve this by installing the stock rom, RUU.
Downloaded RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed , which is the perfect match for my phone but also fails to finish installation, telling me something about failed/unknown mounts/filesystem... If it will help, I will tell you exactly what the error is.
At this moment I have S-On in bootloader, and can't see any radio serial metioned at the top. Tried some instructions flashing PG58IMG.zip , but it doesn't seem to do anything.
Please, help me out because at this point my phone won't go anywhere but bootloader and recovery.
Click to expand...
Click to collapse
install latest 4ext from here
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot command
the command is fastboot flash recovery recovery.img
then from 4ext format all partitions except sdcard
enable smartflash( because you are on S-ON)
flash the custom rom
note: enable smartflash exactly before flashing the rom
Thank you very much! I've managed to install SKimKAT now. But how can I get S-Off permanent? Also, I can't install the stock RUU firmware.
RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed
It freezes on the "sending" stage for hours.
AKAndrew41 said:
Thank you very much! I've managed to install SKimKAT now. But how can I get S-Off permanent? Also, I can't install the stock RUU firmware.
RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed
It freezes on the "sending" stage for hours.
Click to expand...
Click to collapse
see this guide
http://forum.xda-developers.com/showthread.php?t=2751187