...then again, I might just be being a complete moron and absolutely wasting a lot of people's time. I'm going to try anyway because everytime I Google my multiple problems I seem to get back to this website. Yes, I watched your noob video - I laughed a lot, and unfortunately and unintentionally I feel like I'm going to tick a few of the boxes at the end of it... If you can rescue me from my situation, I'll definitely make a donation towards the upkeep of your site (As long as you have a donation link.)
I have a HTC Sensation XE (with Beats Audio) and it being a Sunday afternoon I thought I would have a crack at rooting and applying custom firmware to me phone for the first ever time. I bet you can see where this is going. I downloaded the SDK Manager, HTC ONE X All In One tool, and the latest Cyanogen for my handset. I DID NOT S-OFF MY PHONE BEFORE JUMPING RIGHT IN FOR I AM AN IDIOT. So I rooted the phone, and all seemed to be going well, I had the Stock ROM, I believe they call it? But it was rooted as confirmed by Root Checker. AT THIS POINT I BACKED UP USING CLOCKWORK. I then got ahead of myself and tried to download the new Custom ROM. After getting aggrieved that the ROM was stuck on 86% consistently with ROM Manager I downloaded it to my PC. Put it onto my SD card. Went into recovery mode. Installed .zip via SD card.
This is where problems began. Once the installation was done I restarted my phone and got caught out by the little blue man, and I believe my screen was stuck in bootloop, where it just continually showed me his image - and the movements around him kept occurring, it didn't freeze. I tried to put the boot.img on from the .zip where I had downloaded it but it came to no avail, it still didn't boot past that point.
I was aggrieved and so restored my phone to the point I said I had backed up. Just after the root of the stock ROM. Then when I tried to boot this up, it got stuck at the Beats Audio symbol in similar vein to how it was stuck on the little blue man.
I turned my phone off, tried to wipe everything using 4ext recovery that I placed on the phone at this point. My All In One tool also stopped recognising my phone, constantly saying "error: device not found" when I tried to do something which it was not doing before the root. Furthermore, when I plug my phone into my PC, it doesn't offer me Removable Drive storage, but it does make the pinging noise which notifies me that the device is recognised. Now after all this, when I boot the phone it is stuck at the HTC screen with a white background and I don't know why it is now halting here as opposed to what it was earlier, could it be something to do with when I was trying to get the all-in-one tool to recognise my phone I tried to reflash recovery of 'Stock'? I really am upset about this and regret even attempting it as I am in love with my phone and can't really live without it. Please help and if I get a successfully, rooted phone I will be very happy and PROMISE to make a donation towards the site of what I can afford.
So please do me and your own site a favour and help me
BRIEF POINTS OF NOTE
ROOT SEEMED TO WORK FINE UNTIL ATTEMPTING TO PUT CUSTOM ROM ON
CUSTOM ROM WOULDN'T BOOT PAST BLUE MAN SCREEN AT FIRST, THEN BEATS AUDIO SCREEN AND THEN HTC SCREEN.
MY PHONE IS S-ON, UNLOCKED, PYRAMID PUT SHIP S-ON RL, HBOOT-1.29.0000,eMMC-boot,Mar 2 2012, 18.14.34
PC IS NOT CURRENTLY RECOGNISING MY PHONE AS A REMOVABLE DEVICE IN THE SENSE THAT IT WON'T ALLOW ME TO PUT ON ANY ITEMS.
I DO HAVE A SPARE, ACCESSIBLE SD CARD AND DO NOT CARE WHAT HAPPENS TO THE CONTENTS OF IT. IF THIS IS USEFUL.
Please. Help me. Thank you
don't panic.many as you had that issue.it is easy
from 4ext recovery enable smartflash and then immediately flash the rom
you should be fine
If it still fails to boot after reflashed with smartflash on, get boot.img from zip, place it in your fastboot/adb folder and flash it manually from fastboot: fastboot flash boot boot.img
Look for Asskicker's guide in General section. "flashing rom with s-on and Hboot 1.27+"
Sent from my HTC Sensation Z710e using xda app-developers app
rzr86 said:
don't panic.many as you had that issue.it is easy
from 4ext recovery enable smartflash and then immediately flash the rom
you should be fine
Click to expand...
Click to collapse
Unfortunately, this hasn't worked for me. I did this...
- Went onto 4EXT recovery.
- Went to tools.
- Clicked on 'Enable Smartflash'.
- Ensured it was on.
- Went to 'install .zip from SD Card'
- Found the Cynagon MOD.
- "Finding update package... Opening update package... Installing update... Install from SD Card complete."
- Rebooted phone.
- A pending update to your boot partition has been detected. Your ROM will reboot once [and then it reboots]. The first time it came up with this though. It said something about how there had been an error.
- Got stuck at the HTC screen again.
I'd just like to reaffirm that before something happened (I believe it was when I tried to flash to stock recovery), my phone was getting to the Beats Audio/Little Blue Man Screen. Now it's getting to the HTC screen.
That donation to the site is still in promise!
matekaneve said:
If it still fails to boot after reflashed with smartflash on, get boot.img from zip, place it in your fastboot/adb folder and flash it manually from fastboot: fastboot flash boot boot.img
Look for Asskicker's guide in General section. "flashing rom with s-on and Hboot 1.27+"
Sent from my HTC Sensation Z710e using xda app-developers app
Click to expand...
Click to collapse
This also didn't work for me. It appeared to run entirely successfully. I rebooted the phone using 'fastboot reboot' and it still got stuck at the same screen.
ElliotHorne32 said:
Unfortunately, this hasn't worked for me. I did this...
- Went onto 4EXT recovery.
- Went to tools.
- Clicked on 'Enable Smartflash'.
- Ensured it was on.
- Went to 'install .zip from SD Card'
- Found the Cynagon MOD.
- "Finding update package... Opening update package... Installing update... Install from SD Card complete."
- Rebooted phone.
- A pending update to your boot partition has been detected. Your ROM will reboot once [and then it reboots]. The first time it came up with this though. It said something about how there had been an error.
- Got stuck at the HTC screen again.
I'd just like to reaffirm that before something happened (I believe it was when I tried to flash to stock recovery), my phone was getting to the Beats Audio/Little Blue Man Screen. Now it's getting to the HTC screen.
That donation to the site is still in promise!
Click to expand...
Click to collapse
did you flash gapps and then the CM rom?
if no then:
flash gapps
flash the rom again
(don't forget to enable smartflash again)
rzr86 said:
did you flash gapps and then the CM rom?
if no then:
flash gapps
flash the rom again
(don't forget to enable smartflash again)
Click to expand...
Click to collapse
Sorry to be a pain, but could you run me through a step-by-step on how to do that? *Noob Klaxon*
ElliotHorne32 said:
Sorry to be a pain, but could you run me through a step-by-step on how to do that? *Noob Klaxon*
Click to expand...
Click to collapse
gapps is google apps.is a zip file
if i remember well maybe is in the thread where you downloaded the rom
simply put it in the root of sdcard and flash it from recovery
after that flash the rom(don't forget smartflash)
rzr86 said:
gapps is google apps.is a zip file
if i remember well maybe is in the thread where you downloaded the rom
simply put it in the root of sdcard and flash it from recovery
after that flash the rom(don't forget smartflash)
Click to expand...
Click to collapse
I downloaded it from here [can't post link, but it's the official Cynagon MOD Website] - I then clicked on the 'Stable Mod'.?
If you straight quick responses go on this forum here I have through similar issues before and they so helpful..I'm S-ON
http://forum.xda-developers.com/showthread.php?t=163186
Sent from from my HTC Sensation XE with Beats Audio Z715e using xda app-developers app
Hi there mate!
What I would recommend you to do is running an appropriate RUU for your device, ( i would recommend GB, because then you can S-off very easy), and then re-run the whole process. If you run a GB RUU, you can gain s-off with revolutionary. And the best part, the RUU can be run in bootloader, so it doesn't matter if your ROM does not boot. I can send you a link once my internet gets faster (im using all my bandwidth for source-building lol)
Please keep me posted and feel free to ask any questions
Best of luck !
InfinityFTW said:
Hi there mate!
What I would recommend you to do is running an appropriate RUU for your device, ( i would recommend GB, because then you can S-off very easy), and then re-run the whole process. If you run a GB RUU, you can gain s-off with revolutionary. And the best part, the RUU can be run in bootloader, so it doesn't matter if your ROM does not boot. I can send you a link once my internet gets faster (im using all my bandwidth for source-building lol)
Please keep me posted and feel free to ask any questions
Best of luck !
Click to expand...
Click to collapse
if i remember well he can't downgrade using a GB ruu because he is S-ON
i think he can only upgrade
you have to be already S-OFF in order to downgrade with ruu
InfinityFTW said:
Hi there mate!
What I would recommend you to do is running an appropriate RUU for your device, ( i would recommend GB, because then you can S-off very easy), and then re-run the whole process. If you run a GB RUU, you can gain s-off with revolutionary. And the best part, the RUU can be run in bootloader, so it doesn't matter if your ROM does not boot. I can send you a link once my internet gets faster (im using all my bandwidth for source-building lol)
Please keep me posted and feel free to ask any questions
Best of luck !
Click to expand...
Click to collapse
Thank you for your helpful paragraph If you could send me the link for that RUU, that would be great, but I do have a couple of other questions. What is an RUU? I assume GB is Gingerbread, but is that the OS that I am on? What will the RUU do? I really stepped out of my depth trying this haha!
Elliot,
ElliotHorne32 said:
Thank you for your helpful paragraph If you could send me the link for that RUU, that would be great, but I do have a couple of other questions. What is an RUU? I assume GB is Gingerbread, but is that the OS that I am on? What will the RUU do? I really stepped out of my depth trying this haha!
Elliot,
Click to expand...
Click to collapse
RUU returns your device into completely stock situation as you bought it
now depending your hboot version you are running ics android
ElliotHorne32 said:
Thank you for your helpful paragraph If you could send me the link for that RUU, that would be great, but I do have a couple of other questions. What is an RUU? I assume GB is Gingerbread, but is that the OS that I am on? What will the RUU do? I really stepped out of my depth trying this haha!
Elliot,
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=1074559
RUU stands for Rom Update Utility, and it is an executable (.exe) file wich is ran from a pc with a phone connected in fastboot. The RUU is meant to restore all partitions on your phone
Sent from a muffin inside a muffin using muffintalk.
OK try this.
1. Reboot into 4ext recovery.
2. Wipe everything except sdcard.
3.enable 4ext smart flash
4. Reflash Cyanogenmod.
5. Flash gapps add-on from Cyanogenmod thread.
6. Reboot and wait up to 10 minutes.
If this does not work take your Cyanogenmod rom and on your pc extract the boot.IMG file and move it to your adb folder then repeat but add
8. Fastboot flash boot.IMG using adb while in recovery.
Open your cmd and CD to your ad folder.
Issue the command " fastboot flash boot boot.img " with the phone connected.
9. Reboot and wait up to 10 minutes
Thank you all for your responses, I haven't forgotten about this thread at all haha - I've just been very busy lately but will be doing all of your suggestions over the weekend, so thank you. Will keep you posted. Elliot
ElliotHorne32 said:
Thank you all for your responses, I haven't forgotten about this thread at all haha - I've just been very busy lately but will be doing all of your suggestions over the weekend, so thank you. Will keep you posted. Elliot
Click to expand...
Click to collapse
Btw the only RUU that will work on hboot 1.29.0000 devices is the 3.33.401.153 one IIRC. It's also available to download from my FTP - here
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Jonny said:
Btw the only RUU that will work on hboot 1.29.0000 devices is the 3.33.401.153 one IIRC. It's also available to download from my FTP - here
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Just when I have everything ready to try this, I am getting '403 Forbidden' on that link you just sent me. What do I do to get that link working?
Also, is it as simple as plugging the phone into Fastboot USB mode and clicking the .exe file?
Elliot,
Any help possible with this one, guys and girls? The last post I made about the 403?
Elliot
Related
I wanted to flash to ARHD 6.3
This is my first time.. I managed to S off.. But then the bootloop began after I flashed PG58IMG.zip via fastboot.
Step 1. To S-OFF your Sensation - (You do not need to do this if you have S-off already or done this before) - WORKING NOW for TMOUS users
Visit
download the application for your operating System. AND EXTRACT IT TO A FOLDER
YOU MAY NEED TO DISABLE YOUR ANTIVIRUS PROGRAM- Norton is flagging up Revolutionary as a Virus when it isn't
IMPORTANT
Fill out the form under the download links with your OS, Device, Hboot Version and Serial number. This will give your beta key to enable you to S - OFF. Make a note of this.
How To get your Hboot Version - 3 methods below
1. [/url] and if it has found your device it should read
"Found your Device: HTC Sensation Z710* Applications -> Development)
4. With the phone switched on (not in HBOOT, just the regular home screen), plug in your USB cable and select HTC sync mode.(IGNORE any warning messages on your phone telling you it cannot find HTC Sync )
5. Launch revolutionary.exe. It should detect the phone and ask for your beta key. Type it (BE CAREFUL, as its case sensitive) or copy and paste it in.
If Revolutionary fails to find your phone verify you have all the drivers installed, try disk drive mode or charging mode (Linux users can use disk drive mode. Confirmed to be working by others)
6. Once you have entered your beta key correctly, follow any on screen prompts or actions from revolutionary and wait for it to S-Off,
7. You're done. Your Device will Successfully have S-OFF....if it hangs on method 3 and doesn't S-Off. See post 2 below for solutions.
IF REVOLUTIONARY SAYS FAILED YOUR PHONE IS NOT SUPPORTED. Go back and check hboot using the methods above. some users are told its failed and they still have S off now. If you have S-off your hboot will now be 1.17.1011 and revolutionary will tell you now your device is not supported
8. Revolutionary will now ask you to Install clockwork recovery mod after S OFF. Type N and install it manually below (the recovery provided is v4.0.1.4 doesn't charge when device is switched off, the one below v5.0.0.1 does charge)
9. Your Device now is S-off.
To install clockwork recovery for the sensation. Follow step 2!
STEP 2. To INSTALL Recovery - v5.0.0.8
1. Download recovery v5.0.0.8 for the Sensation HERE: or Multiupload
2. Copy the PG58IMG file into the Root folder of your SD card (The main Folder of your Memory Card)
3. Turn off your phone FUlly and reboot into the Bootloader/HBOOT screen (see post above on how to get to hboot screen)
4. Press Volume up to Accept when it asks" Do you want to start the update"
5. Press Power Off to Reboot back to android after installation is successful (normal screen with homescreen)
Click to expand...
Click to collapse
I got stuck at step 2.5.. Pls help me out. Actually I used to flash ROM for i9000 a couple of times but for sensation this is my first time. I'm using sensation unlocked. I lived in Malaysia so most probably its asians version.
ethanmars said:
I wanted to flash to ARHD 6.3
This is my first time.. I managed to S off.. But then the bootloop began after I flashed PG58IMG.zip via fastboot.
I got stuck at step 2.5.. Pls help me out. Actually I used to flash ROM for i9000 a couple of times but for sensation this is my first time. I'm using sensation unlocked. I lived in Malaysia so most probably its asians version.
Click to expand...
Click to collapse
Hi,
Try loading 5.0.2.0 HERE
Then follow THIS GUIDE to install 6.3.0
thank you so much for your reply!
i've downloaded that. Now how do i install it? fastboot only accept .zip files right? or is the instruction is in the 2nd link you gave me?
ethanmars said:
thank you so much for your reply!
i've downloaded that. Now how do i install it? fastboot only accept .zip files right? or is the instruction is in the 2nd link you gave me?
Click to expand...
Click to collapse
Hi,
Just rename 5.0.2.0 to PG58IMG.zip
Power off
Power on holding volume- and power button.
When it has finished,delete PG58IMG.zip
malybru said:
Hi,
Just rename 5.0.2.0 to PG58IMG.zip
Power off
Power on holding volume- and power button.
When it has finished,delete PG58IMG.zip
Click to expand...
Click to collapse
just pressed thanks, hehe..
i was wandering alone while waiting for your reply n managed to install ext4 touch recovery.. lol.. but still bootloop when pressed reboot.
now I wanna know will the 5.0.2.0 help me to access android again coz i haven't backup my contacts n sms yet..
let's say the answer is no, will it help if i make a nandroid backup now? or is it too late considering i cant access android anymore?
ethanmars said:
just pressed thanks, hehe..
i was wandering alone while waiting for your reply n managed to install ext4 touch recovery.. lol.. but still bootloop when pressed reboot.
now I wanna know will the 5.0.2.0 help me to access android again coz i haven't backup my contacts n sms yet..
let's say the answer is no, will it help if i make a nandroid backup now? or is it too late considering i cant access android anymore?
Click to expand...
Click to collapse
Hi,
Lesson for the future...
Always backup(nandroid,Titanium Backup,google) BEFORE starting anything major.
If you have 4EXT installed,then follow THIS GUIDE to install 6.3.0
malybru said:
Hi,
Lesson for the future...
Always backup(nandroid,Titanium Backup,google) BEFORE starting anything major.
If you have 4EXT installed,then follow THIS GUIDE to install 6.3.0
Click to expand...
Click to collapse
thanks again ..
so that means there's no way to access my phone like it was before eh?
btw, i thought it wasnt anything major coz it was just gaining an s off n then installing recovery.. then this happened.. i dont know what went wrong.. hmm
so i shall proceed with installing 6.3.0 since its like the only option i have left i believe?
ethanmars said:
thanks again ..
so that means there's no way to access my phone like it was before eh?
btw, i thought it wasnt anything major coz it was just gaining an s off n then installing recovery.. then this happened.. i dont know what went wrong.. hmm
so i shall proceed with installing 6.3.0 since its like the only option i have left i believe?
Click to expand...
Click to collapse
Hi,
Just as a matter of interest.
Do you still have a PG58IMG.zip on your sd card?
If so ,delete it.
Then it may boot into your ROM...
malybru said:
Hi,
Just as a matter of interest.
Do you still have a PG58IMG.zip on your sd card?
If so ,delete it.
Then it may boot into your ROM...
Click to expand...
Click to collapse
oh i've read that as well so i have deleted it manually by using sd adapter.. then reinserted it back n tried to boot normally.. but to no avail.. what's the root cause of this eh?
when i gained s off, i still can boot into my ROM.. however disaster happens when i flashed the .zip files obtained as per instructions..
oh but directly after i've flashed it, i didn't remove the .zip files n tried to immediately reboot into ROM.. does this make a difference?
ethanmars said:
oh i've read that as well so i have deleted it manually by using sd adapter.. then reinserted it back n tried to boot normally.. but to no avail.. what's the root cause of this eh?
when i gained s off, i still can boot into my ROM.. however disaster happens when i flashed the .zip files obtained as per instructions..
Click to expand...
Click to collapse
Hi,
Did you complete the s-off thread by rooting and getting SuperCID?
malybru said:
Hi,
Did you complete the s-off thread by rooting and getting SuperCID?
Click to expand...
Click to collapse
good question..
immediately after s off, i boot into my ROM and tried to install busybox and other apps that requires superuser or root but failed and stating that my device was still not rooted..
so i proceed to install a recovery (in this case its ext4 recovery) but failed to find a .zip installer (but managed to find the .apk and .img version but afraid to proceed considering the extension wasn't the same as per guide's PG5...ZIP). so i tried to simply install cwm as per stated in the guide. coz i know after recovery is installed, only then i would be able to install the su zip files.
then it boot looped.. n here we are trying to shoot all of these troubles.. XD
and if my understanding was wrong, pls correct me. thanks!
only after you sent me the links i managed to install ext4 recovery via a much easier method using cmd.exe..
n that also means that i wasn't even able to follow through the supercid part of the guide..
ethanmars said:
good question..
immediately after s off, i boot into my ROM and tried to install busybox and other apps that requires superuser or root but failed and stating that my device was still not rooted..
so i proceed to install a recovery (in this case its ext4 recovery) but failed to find a .zip installer (but managed to find the .apk and .img version but afraid to proceed considering the extension wasn't the same as per guide's PG5...ZIP). so i tried to simply install cwm as per stated in the guide. coz i know after recovery is installed, only then i would be able to install the su zip files.
then it boot looped.. n here we are trying to shoot all of these troubles.. XD
and if my understanding was wrong, pls correct me. thanks!
only after you sent me the links i managed to install ext4 recovery via a much easier method using cmd.exe..
Click to expand...
Click to collapse
Hi,
I follow THIS GUIDE
If you have 4EXT installed ,then you should be able to boot into recovery and make a nandroid,then root,then supercid...
malybru said:
Hi,
I follow THIS GUIDE
If you have 4EXT installed ,then you should be able to boot into recovery and make a nandroid,then root,then supercid...
Click to expand...
Click to collapse
wait a moment, i dont know if things are making more sense to me but, is it possible that this was caused by a wrong firmware? i just figured out my cid and its htc_044 and there are 4 different version of firmware for this cid, so should i try each of it until my phone boots to my original ROM?
Update: Oh God, I'm in such a relief! Thank God it works now. I flashed the firmware 1.17 n now am able to boot back into my ROM. Now i'm gonna get things backed up n will proceed. phew thanks so much for helping me out. The cause was maybe the zip files werent compatible with mine. So i check my cid n mid, n downloaded what might be the original one. so now its fixed..
Hi guys, my sensation ce keep stuck and auto reboot for many times after ics update, I tried darkforest Rom but still the same thing happen. I tried the method pull battery and restart phone but no idea. So any ways to fix this. Pls help!!!
wesker5131 said:
Hi guys, my sensation ce keep stuck and auto reboot for many times after ics update, I tried darkforest Rom but still the same thing happen. I tried the method pull battery and restart phone but no idea. So any ways to fix this. Pls help!!!
Click to expand...
Click to collapse
what did you do ???
ICS OTA update ?
or flashed ICS ROM directly via recovery from GB rom?
can you post the details of bootloader (HBOOT)
random stuck and reboot
Alright, here is how it goes... I bought this used sensation xe from a guy, the time I check the phone, it is already ota update. While that time the phone keep stuck and reboot.for few times. Maybe 30 minutes once. The whole phone suddenly freeze and then restart. So I decide to root it and install custom Rom, I thought that maybe custom Rom will works better, but not. I read some guides out there mention that in order to flash custom Rom, we need to unlock the phone first. So I unlock by using the HTC dev method. After that I flash dark forest ics Rom, but the stuck and reboot problem still remains there. So here is my bootloader. UNLOCKED , PYRAMID PVT SHIP S - ON RL. HBOOT 1.27.0000. any idea how to fix this? Please provide me step by step guide if yes. I have been confusing searching the forum.
wesker5131 said:
Alright, here is how it goes... I bought this used sensation xe from a guy, the time I check the phone, it is already ota update. While that time the phone keep stuck and reboot.for few times. Maybe 30 minutes once. The whole phone suddenly freeze and then restart. So I decide to root it and install custom Rom, I thought that maybe custom Rom will works better, but not. I read some guides out there mention that in order to flash custom Rom, we need to unlock the phone first. So I unlock by using the HTC dev method. After that I flash dark forest ics Rom, but the stuck and reboot problem still remains there. So here is my bootloader. UNLOCKED , PYRAMID PVT SHIP S - ON RL. HBOOT 1.27.0000. any idea how to fix this? Please provide me step by step guide if yes. I have been confusing searching the forum.
Click to expand...
Click to collapse
ohh you got ics ota previusly...good things are easy now for you
now
1.you got rom on your sdcard or on pc ?..then extract the boot.img file from rom's zip file (usually present in kernels folder... if it has more than one boot.img choosethe one of your choice)
2.keep the boot.img in adb folder (assuming you got adb/factboot setup)
3.keep the device in fastboot mode and connect it to pc (bootloader then fastboot)
3.flash the boot.img via fastboot
command : "fastboot flash boot boot.img"
(you need to do this every time you install custom rom via custom recovery---to prevent this you can install latest 4EXT custom recovery 1.0.0.5 RC3 )
4.reboot ---then voila it should work
The Rom you mean is custom Rom? But I discover that after I flash the dark forest Rom, I can't flash any other custom Rom or kernel. It says (bad). Installation aborted . Later will try the method that you stated. The adb folder is on pc? You mean c: Android on my computer?
wesker5131 said:
The Rom you mean is custom Rom? But I discover that after I flash the dark forest Rom, I can't flash any other custom Rom or kernel. It says (bad). Installation aborted . Later will try the method that you stated. The adb folder is on pc? You mean c: Android on my computer?
Click to expand...
Click to collapse
yep...ROM ->what ROM you've flashed and had bootloop
adb folder...is where your adb is...yeah it is C: Android in your case
So about the Rom installation aborted? How to fix that. Btw my phone is not s off. How should I s off with the phone condition now.
wesker5131 said:
So about the Rom installation aborted? How to fix that. Btw my phone is not s off. How should I s off with the phone condition now.
Click to expand...
Click to collapse
To do soff we need to use jb soff
First get your device out of bootloop using above steps
then we'll deal with soff
Sent from my HTC Sensation XE with Beats Audio using xda premium
lol. my phone is not stuck at bootloop. it go until home screen. and can online or gaming whatever. but, like what i say, i surfing the net for few minutes or 30 minutes so on, the phone freeze, i press lock key also dont work. and then it restart.
wesker5131 said:
lol. my phone is not stuck at bootloop. it go until home screen. and can online or gaming whatever. but, like what i say, i surfing the net for few minutes or 30 minutes so on, the phone freeze, i press lock key also dont work. and then it restart.
Click to expand...
Click to collapse
Lol.. I thought you are stuck at bootloop..
The above method I mentioned helps too as these random boots might happen due to kernel/module mismatch... So first do that and see the random reboots are gone.
If that didn't solve the issue
Then this random boots might be due to improper flash of rom... First if you got custom recovery installed.. Do a full wipe (use ARHD super wipe too if you want to) from recovery and then flash the rom again... See that solves the issue.. If still not then once again extract the boot.img and repeat the above process again
Sent from my HTC Sensation XE with Beats Audio using xda premium
trying now, will leave the feedback later or soon. so what is the next step to get it S-OFF? is there easier methods?
i have done what you said on top, the boot.img method. so lets hope the phone goes well and doesnt stuck anytime. whats next?
wesker5131 said:
i have done what you said on top, the boot.img method. so lets hope the phone goes well and doesnt stuck anytime. whats next?
Click to expand...
Click to collapse
Check guide to Juopunutbear soff in sensation general thread its by auggie.. Good guide follow it to soff
Sent from my HTC Sensation XE with Beats Audio using xda premium
When I was on a stock rom on my sensation the phone was all kinds of bad, it would restart randomly like you mention and it would always force close and reload sense...once I flashed a custom rom everything is perfect. So good I am scared to flash something else and get problems..sounds like you need to to superwipe and start all over. with s-off and everything.
use this guide. this is what i used and did everything exactly and it worked.
http://forum.xda-developers.com/showthread.php?t=1192300
done s-off with the JupoBear. but now get BLANK SD CARD message. How do I format it while I dont had a card reader??
wesker5131 said:
done s-off with the JupoBear. but now get BLANK SD CARD message. How do I format it while I dont had a card reader??
Click to expand...
Click to collapse
well that was fast
got custom recovery? ...there might be an option to format sdcard
if you got 4EXT recovery...you'll have that option..dont know about cwm
if i cant format through CWM , then what else should I do. Its too late to flash 4EXT while the Install from zip option cant mount SD card. I tried on CWM Format / sdcard, but it says Error mounting SD CARD Skipping format...
wesker5131 said:
if i cant format through CWM , then what else should I do. Its too late to flash 4EXT while the Install from zip option cant mount SD card. I tried on CWM Format / sdcard, but it says Error mounting SD CARD Skipping format...
Click to expand...
Click to collapse
lot of ppl got their sdcard fried while trying JB SOFF....the only option left for you is to try card reader...
also you can flash 4EXT via fastboot as i mentioned in my earlier posts...that method doesnt require sdcard
but worry not...now that you are SOFF...you can completely control your device
if i get a new sd card will this solve the problem? i'm afraid that after getting new sd card and the blank sd appear again.
wesker5131 said:
if i get a new sd card will this solve the problem? i'm afraid that after getting new sd card and the blank sd appear again.
Click to expand...
Click to collapse
yeah it will suffice
why dont you join the irc by clicking IRC HELP CHANNEL in my signature ...with a nick name...we can talk directly there...its like a group chat
Good evening/morning all
Just grabbed this new OTA from my One S so i thought i would make an appearance... And before anyone asks, yes - I am working on a ROM
OTA_Ville_U_HTC_Europe_1.78.401.2-1.53.401.2
Please note: This OTA takes you from 1.53.401.2 to 1.78.401.2
Change log from the updater service (rather vague):
System enhancment
Enjoy
P.S > Had no time to analyse the actual content but the OTA contains full firmware updates including HBoot & Radio.
Edit: Just noticed paul has done a repack of the base already.. may still come in handy for you devs out there
I knew you would come just like I asked for and others.
Thanks Lee.
If you can work on a T-Mobile ROM/EU ROM.
Very excited about the LeeDroid
Excellent rum were at Desire
On the one s worth the wait?
Can't wait for some goodness from you!
Sent from my US HTC One S using Tapatalk 2
Dimson75 said:
Very excited about the LeeDroid
Excellent rum were at Desire
On the one s worth the wait?
Click to expand...
Click to collapse
Certainly will be
Sent from my LeeDrOiD One Xtreme loaded HTC One X
woohoo !! about time you made an appearance !! I knew you was hanging around here somewhere
missed you since i left the sensation forums
I know this is probably a really stupid question but I'm going to ask anyway...
Can you actually install an OTA package on the phone somehow or is it just useful to take files out of it?
And the other question, my phone doesn't find any OTA updates anymore since I've 'tampered' with it so is there a way to make it find and install the OTA updates again?
Thanks
As long as you are using the correct stock ruu you can apply it via cwm recovery(unlock needed )... to restore full functionality its best to flash the stock RUU
Sent from my LeeDrOiD One Xtreme loaded HTC One X
LeeDroid said:
As long as you are using the correct stock ruu you can apply it via cwm recovery(unlock needed )... to restore full functionality its best to flash the stock RUU
Sent from my LeeDrOiD One Xtreme loaded HTC One X
Click to expand...
Click to collapse
The other thing is that when I try installing the stock RUU it's telling me it's for the wrong device or something like that, although it's definitelly the correct RUU.
Also, my phone is HTCDev unlocked but is still S-ON so if I install the OTA package usign CWM is it going to update the radio and the hboot (I thought it can't do that if you're S-ON)?
Thanks
you dont install it via CWM, you install it via the stock recovery.. of which you will first need to flash..
Did'nt work for me, wrong CID...
edit the info.txt to match your CID
azzledazzle said:
you dont install it via CWM, you install it via the stock recovery.. of which you will first need to flash..
Click to expand...
Click to collapse
Ok, maybe I'm not getting this right but I'm talking about two separate things:
Issue 1. My understanding is that I can install the OTA zip package using ClockworkMod, is that correct?
Issue 2. The RUU package won't install on my phone:
i) I have restored via ClockworkMod the nandroid image of the stock ROM (image that I've taken straight after I unlocked the boot loader and flashed a custom recovery, but before I rooted the phone). Then, I flashed the stock recovery image using fastboot. So now my phone should be back to stock.
ii) I then tried to install RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
When I do this, the RUU goes through right up to the step where it says 'Updating signatures' and then it stops saying 'unknown error' and it leaves my phone on that screen with black background and white HTC logo. Then, I have to hard boot and the phone starts up fine but in the state it was before the RUU - not even the user data is missing. To me this means that for some reason it doesn't even try to flash the RUU onto the phone but it stops when checking the signatures - I just can't understand why this is happening...
Can you help?
Thanks
1. No you cannot flash anything official from HTC using CWM, you MUST use stock recovery. You can find stock recovery in the OTA zip file, It will be named recovery.img OR recovery_signed.img
2. Unknown error is hard to diagnose, Normally we get error codes which we can identify as to what the problem is.. Are you running the RUU in fastboot ?
azzledazzle said:
1. No you cannot flash anything official from HTC using CWM, you MUST use stock recovery. You can find stock recovery in the OTA zip file, It will be named recovery.img OR recovery_signed.img
Click to expand...
Click to collapse
Sorry for my ignorance, but how do I initiate the installation of the OTA zip package using the stock recovery? As I said, I can't actually get it 'over the air' but I've just downloaded the zip package from this thread...
ok put the package on your sd card.
boot into fastboot, flash the stock recovery using the command ''fastboot flash recovery recovery.img'' (or recovery_signed.img) (also no quotes)
when thats done, select recovery from fastboot using volume button..
When you get a red ! press volume UP and power button, That will take you into stock recovery
Then look for the option, install from sd card or something like that
select your OTA package and BOOM !!! job done
Reflash CWM and away you go
Damn... I had no idea that you can actually get into the menu of the stock recovery... It all makes sense now...
me neither till about 3 days ago
I might not seem like a noob,,,,,but deep down i am
azzledazzle said:
2. Unknown error is hard to diagnose, Normally we get error codes which we can identify as to what the problem is.. Are you running the RUU in fastboot ?
Click to expand...
Click to collapse
I've tried that again and it actually breaks down when it gets to 'Checking Header...' and it exits with 'ERROR [155]: UNKNOWN ERROR". Maybe this is a bit more specific...
this is what i found for error 155
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
Alternatively (in some cases) right click on the file and choose "Run as Administrator".
Or use the rom.zip -> PGXXIMG.zip flashing method.
Click to expand...
Click to collapse
I dont know if it will fail when flashing the rom.zip in CWM - usually you have to rename it to the model number and flash in fastboot, however you cant do this with S-ON
Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Problem Fixed
DrOfLife said:
Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
fsustrength said:
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
Click to expand...
Click to collapse
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
TheAdictsPunk said:
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
Click to expand...
Click to collapse
I have also tried the steps and have run into the same problem. All is well when I flash into recovery, but when the phone starts updating about quarter or half-way through it also gives me the same red error message and the phone restarts soon after with no update. I have tried several times with the same problem.
However, thanks fsustrength for the instructions, before I was getting no where, but now I almost got it
Sent from my HTC VLE_U using xda app-developers app
ckpv5 said:
As there are many questions on how to do OTA update & to revert to stock after a device is rooted and bootloader unlocked; I made this simple guide which I hope will help the newbies especially.
NOTE : always do a backup and a nandroid backup before trying any of these.
OTA update:
A) ROM is stock, bootloader unlocked, stock recovery and not rooted.
- just run the OTA update, there is no need to relock the bootloader
B) ROM is stock, bootloader unlocked, CWM recovery and not rooted.
- flash the stock recovery that comes with your RUU, extract the RUU for the stock recovery.
* boot to bootloader
* fastboot flash recovery recovery_signed.img
* fastboot reboot-bootloader
* fastboot erase cache
* fastboot reboot
- run the OTA update
C) ROM is stock, bootloader unlocked, stock recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- run the OTA update, there is no need to relock bootloader
- Once done, run OTA Rootkeeper and click restore root
D) ROM is stock, bootloader unlocked, CWM recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- no need to relock bootloader
- boot to bootloader and fastboot flash the stock recovery
- run the OTA update
- Once done, run OTA Rootkeeper and click restore root
E) ROM is custom, bootloader unlocked, CWM recovery and rooted and you have a stock nandroid backup
- flash the stock boot.img if after nandroid restore, you have a bootloop
- flash the stock recovery.img
- relock the bootloader - fastboot oem lock
- boot your device and run the OTA update
F) ROM is custom, bootloader unlocked, CWM recovery and rooted and you don't have a stock nandroid backup
- if you dont have the stock nandroid backup, you need to run RUU
- before you can run the RUU you need to:
* flash the stock recovery.img
* flash the stock boot.img (maybe no need)
* relock the bootloader - fastboot oem lock
* run RUU
- run device setup
- run the OTA update
Flashing RUU to revert to stock or to update your One V after you have a custom ROM installed.
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
Note : for people with ERROR 155 UNKNOWN ERROR they need to go into HBOOT and select FASTBOOT and run the RUU to revert to stock (thanks Lloir)
And usually:
Error 155 - usually wrong recovery.img /wrong boot.img
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
Credit to all XDA members that posted all the guides in various forum thread and some from own experience which I compiled here for easy reference.
Click to expand...
Click to collapse
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did). I did in fact have and used the root keeper app, put it on temporary unroot, and flashed the stock rom and ran the update. Yet, I still run into the problem of the red error sign. I'm sure there is a factor that maybe could cause it to stop, but I cannot put a finger on it.
However, I did notice something while following the procedures of the guide on my phone. When I flash the stock rom on my phone, I have to re-download the system update. While downloading the system update I notice that some of my apps get root permissions from SuperSu in the background, even though in root keeper I temporarily took off root. Rootkeeper also states that my phone is unrooted. Could this problem cause the red error message? If so, any way to fix it?
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did).
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
I did! Last night I even tried flashing the recovery image through fastboot instead of the all-in-one kit. Then, even, the recovery image wouldn't flash all the way through... maybe our phones are having a problem with the recovery being reflashed and not the update at all.
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
mmceorange said:
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
Click to expand...
Click to collapse
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
mmceorange said:
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
Click to expand...
Click to collapse
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Click to expand...
Click to collapse
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Rerooting
DrOfLife said:
So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I'm still running stock 1.84, but I'm rooted and unlocked. I do not have any kind recovery like CWM or TWRP. You may have to flash a stock recovery image in order to re-install the recovery of your choice. If you want to get rooted again try this method: http://forum.xda-developers.com/showthread.php?t=1577831 It's what I used to gain root. It's a rather easy to follow guide. I used this instead of the AIO kit.
I'm going to try and revert to locked and unroot in order to get the update. Wish me luck.
DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Oh lol sorry about that.
DrOfLife said:
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
Click to expand...
Click to collapse
Awesome!
DrOfLife said:
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I personally have never encountered that before, so I am of little help here. The suggestion above me sounds like the right direction though.
Red triangle error
dc211 said:
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Click to expand...
Click to collapse
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
lonegunman0 said:
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
Click to expand...
Click to collapse
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Stock rom
mylegiscramped said:
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Click to expand...
Click to collapse
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
Yes i agree about the file detection. I'm running stock rom but i think i've just realised my problem. Although i have a stock rom my problem is that the stock rom i'm running is deodexed. I read somewhere that if the stock rom is tweaked in any way or if any bloatware is deleted you can't get OTA updates.
Hope this helped
Wouldn't an RUU fix any of those problems?
Yes it would
Sent from my HTC One S using xda app-developers app
Hey Everyone!
I've been trying to fix this problem for hours with no luck, and while I've found solutions that have worked for others I can't find one that is specific enough to my situation.
So I just got an HTC One X that is locked to Rogers today from Kijiji, and I love it - great phone. The thing I didn't like was the hoard of stock apps that took up about four pages on the app drawer, so I thought hey, I'll root it and delete them. I didn't have any intention of using any custom ROMs, just wanted superuser permission to delete stock apps. Unlocking went fine (finding the token and what not using the app I found on here), and the rooting seemed to go alright until it turned off and didn't start again. I pulled out the cable from the computer and now things are weird..
I can sometimes get into the hboot, but when I try to just start the phone normally it goes to the HTC splash screen and has red writing telling me "this build is for development purposes only", etc etc. I really wanted to get rid of those stock apps but at this point I just want my phone working again. Am I screwed?
I CANNOT find the RUU that I need ANYWHERE. I've tried flashing both Clockwork Recovery and TWRP, and both are apparently successfully installed, but neither will open for me. This is seriously pushing me towards an iPhone
Thanks in advance.
oot-n-aboot said:
Hey Everyone!
I've been trying to fix this problem for hours with no luck, and while I've found solutions that have worked for others I can't find one that is specific enough to my situation.
So I just got an HTC One X that is locked to Rogers today from Kijiji, and I love it - great phone. The thing I didn't like was the hoard of stock apps that took up about four pages on the app drawer, so I thought hey, I'll root it and delete them. I didn't have any intention of using any custom ROMs, just wanted superuser permission to delete stock apps. Unlocking went fine (finding the token and what not using the app I found on here), and the rooting seemed to go alright until it turned off and didn't start again. I pulled out the cable from the computer and now things are weird..
I can sometimes get into the hboot, but when I try to just start the phone normally it goes to the HTC splash screen and has red writing telling me "this build is for development purposes only", etc etc. I really wanted to get rid of those stock apps but at this point I just want my phone working again. Am I screwed?
I CANNOT find the RUU that I need ANYWHERE. I've tried flashing both Clockwork Recovery and TWRP, and both are apparently successfully installed, but neither will open for me. This is seriously pushing me towards an iPhone
Thanks in advance.
Click to expand...
Click to collapse
Yes, please get an iphone! Redpoint73 resource compilation thread, linked in my signature, has all the RUUs and OTAs you would ever need. Good luck.
Sweet, I found the right RUU but it's a zip file and I'm not able to get into recovery mode on my phone. I can get into hboot but rebooting to recovery from there just shows the HTC splash screen with the "developer only" message" then shuts off again. I've tried installing both Clockwork and TWRP with no luck. Any ideas?
exad said:
Yes, please get an iphone! Redpoint73 resource compilation thread, linked in my signature, has all the RUUs and OTAs you would ever need. Good luck.
Click to expand...
Click to collapse
oot-n-aboot said:
Sweet, I found the right RUU but it's a zip file and I'm not able to get into recovery mode on my phone. I can get into hboot but rebooting to recovery from there just shows the HTC splash screen with the "developer only" message" then shuts off again. I've tried installing both Clockwork and TWRP with no luck. Any ideas?
Click to expand...
Click to collapse
The zip file is an OTA and not an RUU. You would need to extract the recovery from that zip file (may be burried deep). Will be called recovery.img or recovery_signed.img or something to that effect. Fastboot flash recovery recoveryfilename.img then boot to that recovery then install the zip through the phone's stock recovery.
I really appreciate the help but I still can't seem to find the proper RUU. I've tried a few and they all fail. If it helps, the number I get when I typed getvar version-main is: 3.17.631.2
Would someone be able to link me to a download for this particular RUU? Thanks
Edit: Thought I'd update a bit of what I've done. Ive found the one I should need in the list you've provided, but there is no link for download. There is the OTA file but not the RUU. I've been using ARUWizard to try to install the RUU, but any one I've tried so far just says it's not the right one. No other error messages, it just tells me to find the appropriate ROM. I can't understand why this is so difficult to find the right one! It seems like all the other models are readily available. Thanks again!
(This looks like the one, but no download link:
3.17.631.2
File Timestamp: 04/12/12
Publically Seen: 08/01/13
Android: 4.1.1
Kernel: 3.4.10-g240d4d5
hboot: 2.14.0000
radio: 0.23a.32.09.29_10.128.32.34
adsp: 31.1.0.45.0815
wcnss: 1031145
tp_syn3202: 3.2_PR1293981
tz: 001.138.010
sbl1: 001.138.003
sbl2: 001.138.004
sbl3: 001.138.005
OTA: OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.3 2.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl 6j.zip (full)
RUU: N/A
Source: evitaul-jb-crc-3.4.10-240d4d5.zip
exad said:
The zip file is an OTA and not an RUU. You would need to extract the recovery from that zip file (may be burried deep). Will be called recovery.img or recovery_signed.img or something to that effect. Fastboot flash recovery recoveryfilename.img then boot to that recovery then install the zip through the phone's stock recovery.
Click to expand...
Click to collapse
Rogers did not release an ruu for that software version. Proceed with the ota the way I explained in my last post or s-off if you want to run the ruu for the older software version.
Sent from my One X using xda app-developers app
For some reason flashing stock recovery doesn't work for me. It says it is successful but when I try to boot to recovery it just goes right back to hboot or sits on the HTC splash screen. I can install TWRP though. Do you know of a nandroid backup for my phone? cid is Roger001
exad said:
Rogers did not release an ruu for that software version. Proceed with the ota the way I explained in my last post or s-off if you want to run the ruu for the older software version.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
oot-n-aboot said:
For some reason flashing stock recovery doesn't work for me. It says it is successful but when I try to boot to recovery it just goes right back to hboot or sits on the HTC splash screen. I can install TWRP though. Do you know of a nandroid backup for my phone? cid is Roger001
Click to expand...
Click to collapse
Fastboot erase cache
Sent from my HTC One X using xda premium
31ken31 said:
Fastboot erase cache
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Try that. Nandroid will not restore your recovery. Only the ROM/kernel/radio files and settings.
I have tried that but unfortunately still can't get into stock recovery. It just goes to the HTC splash and shuts off after a couple of seconds. I know I have the right OTA so if I can get into stock recovery I shouldn't have a problem. Any other suggestions? Am I downloading the wrong version of the recovery?
exad said:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Try that. Nandroid will not restore your recovery. Only the ROM/kernel/radio files and settings.
Click to expand...
Click to collapse
oot-n-aboot said:
I have tried that but unfortunately still can't get into stock recovery. It just goes to the HTC splash and shuts off after a couple of seconds. I know I have the right OTA so if I can get into stock recovery I shouldn't have a problem. Any other suggestions? Am I downloading the wrong version of the recovery?
Click to expand...
Click to collapse
Extract the recovery from the OTA Zip file. It will be in there somewhere. I have done this myself so I know it works.
exad said:
Extract the recovery from the OTA Zip file. It will be in there somewhere. I have done this myself so I know it works.
Click to expand...
Click to collapse
I have as well and worked like a charm
Sent from my HTC One X using xda premium
Sorry, I forgot to mention, if you are not S-OFF, you need to relock after flashing stock recovery and doing fastboot erase cache.
Hey guys, sorry for the late reply, it was a busy long weekend. Here's where I'm at now. I've managed to install cyanogenmod, which booted up fine and everything looked great, but the touch screen didn't work. After some searching I found it it is because the firmware is too new or something, and to downgrade the touch firmware I would have to S-OFF, which would require me to superCID... and I don't know what any of that is and I'd really just like to get back to stock anyway, so..
I've done what you said. Taken the "recovery.img" out of the OTA file for my phone. I've flashed the recovery, relocked the bootloader and erased the cache. Upon booting to recovery it will either splash the HTC screen then go to a black screen (I used to think it was powering off but it looks like it is on but just not displaying anything). Sometimes it will show a image of a phone with a red exclamation mark with a triangle around it.
I feel like I've royally screwed up this phone and I'd just like to get it back to stock.
Thanks!
Edit: The internet is telling me hold volume up + power to get to recovery from the red triangle, but it just reboots me into the bootloader.
exad said:
Sorry, I forgot to mention, if you are not S-OFF, you need to relock after flashing stock recovery and doing fastboot erase cache.
Click to expand...
Click to collapse
You just need to get into stock recovery. Then you can install that ota zip file. I remember having a hard time getting into it too. I would reflash stock recovery to try to remember how I got to the flash screen but my motherboard is out on rma.
Sent from my Sony Tablet S using xda app-developers app
Just posting in case other people have my problem:
I didn't fix it myself, but a friend did for me. He said it wasn't rooted properly so he basically started from scratch and redid that part of it. There is no RUU file for my phone, but he used to AT&T version and it seems to have worked perfectly. Nothing I've noticed so far has any problems.
Anyway, thanks for all the help guys!
exad said:
You just need to get into stock recovery. Then you can install that ota zip file. I remember having a hard time getting into it too. I would reflash stock recovery to try to remember how I got to the flash screen but my motherboard is out on rma.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
oot-n-aboot said:
Just posting in case other people have my problem:
I didn't fix it myself, but a friend did for me. He said it wasn't rooted properly so he basically started from scratch and redid that part of it. There is no RUU file for my phone, but he used to AT&T version and it seems to have worked perfectly. Nothing I've noticed so far has any problems.
Anyway, thanks for all the help guys!
Click to expand...
Click to collapse
Since your friend fixed the issue for you what firmware are you now now. Is it still rooted?
Looks like I have Android version 4.1.1, HTC Sense 4+, and using CleanROM 6.5.0. Is that what you were wondering?
Also, SuperUser is enabled in SuperSU, so that means I'm rooted right?
takylo said:
Since your friend fixed the issue for you what firmware are you now now. Is it still rooted?
Click to expand...
Click to collapse