Related
#CASE SOLVED#
Hi,
I was using CWM7 and then i tried to flash my phone with shipped custom ROM that was listed on this link http://forum.xda-developers.com/showthread.php?t=1002506&page=37
I chose this version "RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed"
I followed all the procedure and all the process was going right. However, when the phone start to rebooting, it stuck at HTC logo screen for almost half an hour.
I tried the (up) (down) (power) procedure and "adb reboot recovery" but none worked. So i pulled off the battery and try to restart it. However, it stopped again at HTC log screen.
I can still access my recovery, so is there anything that I can still try to do?
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3882.10.08.04_M
NB: this info might useful; when i went to the recovery and connect the usb it mention "HBOOT USB PLUG"
Any help or hint will be really appreciated...
zul.zulkarnaen said:
Hi,
I was using CWM7 and then i tried to flash my phone with shipped custom ROM that was listed on this link http://forum.xda-developers.com/showthread.php?t=1002506&page=37
I chose this version "RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed"
I followed all the procedure and all the process was going right. However, when the phone start to rebooting, it stuck at HTC logo screen for almost half an hour.
I tried the (up) (down) (power) procedure and "adb reboot recovery" but none worked. So i pulled off the battery and try to restart it. Alas, it stopped again at HTC log screen.
I can still access my recovery, so is there anything that I can still try to do?
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3882.10.08.04_M
NB: this info might useful; when i went to the recovery and connect the usb it mention "HBOOT USB PLUG"
Any help or hint will be really appreciated...
Click to expand...
Click to collapse
With the latest Sense 3.0 RUU, the ROM requires that the corresponding HBOOT 2.00.0002 get flashed too in order to boot properly. Since you have S-OFF via Revolutionary, the Revolutionary HBOOT 6.98.1002 is preventing the RUU from overwriting the it, therefore you have ended up with a ROM / HBOOT mismatch and that is why the ROM hangs at the HTC screen.
IMO you would be better off sticking with custom ROMs that have implemented Sense 3.0/3.5 and keeping S-OFF.
From this point you probably need to reinstall ClockworkMod recovery from FASTBOOT mode and then you can restore you nandroid backup (you did make a backup before you attempted this, right?) to get back to CM 7
I did make a backup. But right now, when I choose recovery I can only goes to the stocked recovery. My CWM recovery is lost after the flashing. And when I navigate through the stocked recovery, I can't find a way to restore my last ROM.
zul.zulkarnaen said:
I did make a backup. But right now, when I choose recovery I can only goes to the stocked recovery. My CWM recovery is lost after the flashing. And when I navigate through the stocked recovery, I can't find a way to restore my last ROM.
Click to expand...
Click to collapse
Yes I understand that CWM is no longer there. I said you need to reinstall it using Fastboot.
Look at this thread
http://forum.xda-developers.com/showthread.php?p=14693680
Oh, I didnt know that there's manual process, I only knew the one that use the web. OK, I'll try it
SOLVED. Thanks a lot..
zul.zulkarnaen said:
SOLVED. Thanks a lot..
Click to expand...
Click to collapse
NP. Glad to help. I noticed you updated your first post with SOLVED. It would also help if you modified the Title of your first post and "SOLVED" to it also. That way when others are browsing the threads, they know that a solution is in the discussion.
Hello all
As you can tell Im new to this and thought i would be able to root my device..
Here what I have done I unlocked my device with HTCDev installed CWM 6.0.2.7 treid to boot to recovery no go just stays on a black screen. So then install TWRP 2.4.1.0 Booted to recovery and still the back screen.. so I re-locked the phone and now for some reason all my phone will boot up to is
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
So I would like to know before I go buy a new device If this one can be fix and if it can would some one be able to inform me of the steps ? I can still unlock the device but cant boot to any recovery....
I also Tried to Reload the rogers Ruu and keep getting errors.
Please help
Tookie.
Some one please Help I have been working on this for like 20 hours now and I dont have a phone that can be used :S
tookie69 said:
Hello all
As you can tell Im new to this and thought i would be able to root my device..
Here what I have done I unlocked my device with HTCDev installed CWM 6.0.2.7 treid to boot to recovery no go just stays on a black screen. So then install TWRP 2.4.1.0 Booted to recovery and still the back screen.. so I re-locked the phone and now for some reason all my phone will boot up to is
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
So I would like to know before I go buy a new device If this one can be fix and if it can would some one be able to inform me of the steps ? I can still unlock the device but cant boot to any recovery....
I also Tried to Reload the rogers Ruu and keep getting errors.
Please help
Tookie.
Some one please Help I have been working on this for like 20 hours now and I dont have a phone that can be used :S
Click to expand...
Click to collapse
Just reflash your unlock code from HTC dev install twrp then flash away
Sent from my HTC One X using Tapatalk 2
Don't panic, this should be an easy fix.
Once you relock, you have to run a ruu or unlock again. But you're trying to run a ruu for older firmware, which is why it's failing.
Just push the unlock token again, and you should be able to boot to recovery. If not, push the recovery image again. I don't recommend CWM, even though it's been ported to this phone. That version of TWRP should work, just confirm that you've got the Evita version.
OK i have unlocked again and re pushed recovery TWRP 2.4.1.0
But I still cant boot into the recovery option..
PLease tell me what im doing wrong..
iElvis said:
Don't panic, this should be an easy fix.
Once you relock, you have to run a ruu or unlock again. But you're trying to run a ruu for older firmware, which is why it's failing.
Just push the unlock token again, and you should be able to boot to recovery. If not, push the recovery image again. I don't recommend CWM, even though it's been ported to this phone. That version of TWRP should work, just confirm that you've got the Evita version.
Click to expand...
Click to collapse
I reflashed the unlcok code I reinstall TWRP but i cant boot into recovery..
is there another way to flash away ?
Kole_Ackerson said:
Just reflash your unlock code from HTC dev install twrp then flash away
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
tookie69 said:
I reflashed the unlcok code I reinstall TWRP but i cant boot into recovery..
is there another way to flash away ?
Click to expand...
Click to collapse
I believe through adv but is way simpler to do it through recovery. Try a earlier version of twrp
Sent from my HTC One X using Tapatalk 2
did you verify you are unlocked now, or did you just assume since you pushed the token again?
Also, are you certain you're using the right version of TWRP and not one for another phone (like the endeavour/Tegra One X)?
I pushed the same token and rebooted the device at the top its now says unlocked
DvineLord said:
did you verify you are unlocked now, or did you just assume since you pushed the token again?
Click to expand...
Click to collapse
make sure to run "fastboot erase cache" after changing recovery
IM pretty sure.. I also tried and older TWRP still same issue would you happen to have a link ? I have been using the all in one for HTC one X Tool
iElvis said:
Also, are you certain you're using the right version of TWRP and not one for another phone (like the endeavour/Tegra One X)?
Click to expand...
Click to collapse
bah, all-in-one don't learn anything without doing it yourself. evita is a pretty easy phone once you learn the basics. the op link for twrp in the dev section lists every twrp version officially released for our phone. http://techerrata.com/browse/twrp2/evita
ok i loaded that last night before i went to bed I went this morning to look at the phone and now it just goes to a black screen no madder what I do i put it in the computer the computer goes beep now when its plugged in my computer only the red light at the top flashes and then it disconnects from my computer because i can here the beep of adding and removing hard ware.
is my phone now bricked ?
DvineLord said:
bah, all-in-one don't learn anything without doing it yourself. evita is a pretty easy phone once you learn the basics. the op link for twrp in the dev section lists every twrp version officially released for our phone. http://techerrata.com/browse/twrp2/evita
Click to expand...
Click to collapse
Just relock and boot into boot loader the tampered screen then run a ruu am you should be back to stock
Although I had a EVO before that I flashed the wroung bootloader an bricked it an it wouldn't go anywhere but the bootloader
Sent from my HTC One X using xda premium
If I were you I'd reinstall drivers and manually push the recovery via adb. Use this command- fastboot flash recovery (filename).img
Sent from my HTC One X using Tapatalk 2
Thanks
Thanks for all the help maybe a little late but the issue was the main board on the phone was messed up sent it to HTC and they replaced the board and the battery.. but now i dont need the phone got the HTC one
Rom installation fails on Rogers HTC One X, S-ON, EVITA, HBOOT 2.14.0000
tookie69 said:
Thanks for all the help maybe a little late but the issue was the main board on the phone was messed up sent it to HTC and they replaced the board and the battery.. but now i dont need the phone got the HTC one
Click to expand...
Click to collapse
Hi Guys,
I have the same phone as the specs mentioned below. This is my first android phone and my first time playing around with it.
Here are the specs for "Rogers HTC One X":
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
Here is my accomplishments so far:
- Unlocked with HTC Dec, therefore it says unlocked as mentioned above
- Installed TWRP v2.5.0.0, and can successfully boot into recovery
Yet to be done and do not know how to:
- S-OFF
- Super CID
- Permanent Root
Problems installing ROM:
- unable to install. Various errors with different roms, such as:
1) unable to mount sdcard
2) assert failed: getprop("ro.product.device")
3) error executing updater binary in zip
Please advise. Thank you for your time.
Note: the device is locked to Rogers. It is currently in bootloop. I do not know what I did but before installing TWRP, the device went in bootloop after unlocking bootloader and it would simply not start. Although, as mentioned I can successfully boot into the recovery and mount the sdcard from there to transfer files to the phone.
iccrcmember said:
Hi Guys,
I have the same phone as the specs mentioned below. This is my first android phone and my first time playing around with it.
Here are the specs for "Rogers HTC One X":
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
Here is my accomplishments so far:
- Unlocked with HTC Dec, therefore it says unlocked as mentioned above
- Installed TWRP v2.5.0.0, and can successfully boot into recovery
Yet to be done and do not know how to:
- S-OFF
- Super CID
- Permanent Root
Problems installing ROM:
- unable to install. Various errors with different roms, such as:
1) unable to mount sdcard
2) assert failed: getprop("ro.product.device")
3) error executing updater binary in zip
Please advise. Thank you for your time.
Note: the device is locked to Rogers. It is currently in bootloop. I do not know what I did but before installing TWRP, the device went in bootloop after unlocking bootloader and it would simply not start. Although, as mentioned I can successfully boot into the recovery and mount the sdcard from there to transfer files to the phone.
Click to expand...
Click to collapse
Why are you relocked?
Unlock again and update TWRP, then try to flash a ROM again. What ROM(s) are you trying to flash.
Be aware that since you are s-off, you will need to extract boot.img from the ROM you are trying to flash, and manually flash with fastboot. You will need to do this every time you flash a ROM, unless you get s-off.
Also, I don't know why you posted to this old thread. Aside from the OP also having the Rogers version, it has nothing to do with your issue. Should have started your own thread.
I'll just clarify that when Redpoint said you need to update TWRP you should update it to TWRP 2.6, your current version (2.5) is very buggy. Also, he means since you are s-on you need to flash the boot.img, when you get s-off this will no longer be required.
Sent from my Evita
Thank you redpoint73
redpoint73 said:
Why are you relocked?
Unlock again and update TWRP, then try to flash a ROM again. What ROM(s) are you trying to flash.
Be aware that since you are s-off, you will need to extract boot.img from the ROM you are trying to flash, and manually flash with fastboot. You will need to do this every time you flash a ROM, unless you get s-off.
Also, I don't know why you posted to this old thread. Aside from the OP also having the Rogers version, it has nothing to do with your issue. Should have started your own thread.
Click to expand...
Click to collapse
I made an error. my bootloader was already unlocked. Any how flashing the boot.img of the Rom before installing the Rom worked. Thank you for your insight. My phone is up and running.
For others: below is the rom i flashed:
[ROM] 10/10 Team Venom ViperX 4.0.4 - Sense 5 JellyBean | orig. OTA | Tweaks
http://forum.xda-developers.com/showthread.php?t=2087443
Hi all,
My sensation has been shutting down for no reason for a long time now. No matter what ROM, what kernel, even I have changed the battery twice. It just sometimes turns off, and when I reboot (if it does) it either has very low battery or it will keep shutting down until I plug it in.
To me, it seems like there is something misleading the power level or something. I have super wiped the phone, even reformatted my SD, changed recovery and did the same, flashed thousands of roms (4.1 and 4.2)... and it still does the same.
Funny enough, it doesnt happen when I am in recovery mode (for example, after it shuts down, I reboot into recovery, spend some time there, then reboot and as soon as it boots, bam it shuts down).
This makes me think there is something in a partition that is not touched by the wiping scripts that is bugged and therefore is not fixed after flashing roms etc.
I recently manually wiped and formatted all of my Asus Transformer's partitions (even the recovery) using my PC and it works great, that fixed a problem that also was carried on from ROM to ROM. Hopefully there is a way to do the same for my sensation to give it a 100% clean start.
Thank you very much in advance!
Sent from my Transformer TF101 using Tapatalk 4 Beta
TheKaser said:
Hi all,
My sensation has been shutting down for no reason for a long time now. No matter what ROM, what kernel, even I have changed the battery twice. It just sometimes turns off, and when I reboot (if it does) it either has very low battery or it will keep shutting down until I plug it in.
To me, it seems like there is something misleading the power level or something. I have super wiped the phone, even reformatted my SD, changed recovery and did the same, flashed thousands of roms (4.1 and 4.2)... and it still does the same.
Funny enough, it doesnt happen when I am in recovery mode (for example, after it shuts down, I reboot into recovery, spend some time there, then reboot and as soon as it boots, bam it shuts down).
This makes me think there is something in a partition that is not touched by the wiping scripts that is bugged and therefore is not fixed after flashing roms etc.
I recently manually wiped and formatted all of my Asus Transformer's partitions (even the recovery) using my PC and it works great, that fixed a problem that also was carried on from ROM to ROM. Hopefully there is a way to do the same for my sensation to give it a 100% clean start.
Thank you very much in advance!
Sent from my Transformer TF101 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hi,
The recovery 4EXT has a "Format all partitions except sd card" option.
Look HERE for an installation guide.
Alternatively,you could run a RUU ,which will return all your partitions to stock.
Look HERE
Have you tried the trick of jamming some card to improve the contact of your battery?
It may just be loose,and the card keeps it firmly in place.
malybru said:
Hi,
The recovery 4EXT has a "Format all partitions except sd card" option.
Look HERE for an installation guide.
Alternatively,you could run a RUU ,which will return all your partitions to stock.
Look HERE
Have you tried the trick of jamming some card to improve the contact of your battery?
It may just be loose,and the card keeps it firmly in place.
Click to expand...
Click to collapse
Hi, thank you for your reply.
I used to have 4ext and I have used many times the format all option. I recently switched to TWRP recovery to try their formatting options too. Neither solved the problem.
Also, I have two anker batteries, I have made sure they are not loose. Nevertheless, this happens even when the phone resting on the table, so I am sure that is not the issue. I have switched them wth my gf's sensation, and hers works fine and mine doesn't.
I will try the RUU option to see if going back to stock will remove any kind of bricking that may have occured after so many flashes..
do you think there is anything that is not touched by rom flashing, recovery changing, and partition formatting that may be the cause of the problem? I also updated the firmware too 3.32 I believe it was (the latest) for JB 4.2.2... I dont know what else I can flash or change or format to try to eliminate this powering-off issue...
thanks a lot once more
TheKaser said:
Hi, thank you for your reply.
I used to have 4ext and I have used many times the format all option. I recently switched to TWRP recovery to try their formatting options too. Neither solved the problem.
Also, I have two anker batteries, I have made sure they are not loose. Nevertheless, this happens even when the phone resting on the table, so I am sure that is not the issue. I have switched them wth my gf's sensation, and hers works fine and mine doesn't.
I will try the RUU option to see if going back to stock will remove any kind of bricking that may have occured after so many flashes..
do you think there is anything that is not touched by rom flashing, recovery changing, and partition formatting that may be the cause of the problem? I also updated the firmware too 3.32 I believe it was (the latest) for JB 4.2.2... I dont know what else I can flash or change or format to try to eliminate this powering-off issue...
thanks a lot once more
Click to expand...
Click to collapse
Hi,
The RUU option seems all that is left.
Backup everything before you start.
Are you supercid?
malybru said:
Hi,
The RUU option seems all that is left.
Backup everything before you start.
Are you supercid?
Click to expand...
Click to collapse
Yes, back in the day I used revolutionary, got supercid, and recently I updated the firmware to 3.33 (hboot 1.27.1100), and I am S-OFF.
my bootloader:
-Firmware 3.33 .
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24A.3504.31_M
OpenADSP-V05.6.0.2226.00.0418
eMMC-boot
Might this be caused by the radio? it's the only thing I havent changed recently.
Also, being supercid, and S-OFF, do I have to lock the bootloader and S-ON? I quickly looked at the RUU thread and that is what I understood...
thanks man!
TheKaser said:
Yes, back in the day I used revolutionary, got supercid, and recently I updated the firmware to 3.33 (hboot 1.27.1100), and I am S-OFF.
my bootloader:
-Firmware 3.33 .
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24A.3504.31_M
OpenADSP-V05.6.0.2226.00.0418
eMMC-boot
Might this be caused by the radio? it's the only thing I havent changed recently.
Also, being supercid, and S-OFF, do I have to lock the bootloader and S-ON? I quickly looked at the RUU thread and that is what I understood...
thanks man!
Click to expand...
Click to collapse
Hi,
Noooooooooooooooooooooooooooooooooo!!!!!!!!!!!!!
DO NOT GO TO HTCDEV if you are s-off.
The reason I asked is because you can flash any RUU being s-off and super cid.
Just choose a 3.33 European RUU to run.
EDIT:
Look HERE
Just use the guide to show you how to run it.
malybru said:
Hi,
Noooooooooooooooooooooooooooooooooo!!!!!!!!!!!!!
DO NOT GO TO HTCDEV if you are s-off.
The reason I asked is because you can flash any RUU being s-off and super cid.
Just choose a 3.33 European RUU to run.
EDIT:
Look HERE
Just use the guide to show you how to run it.
Click to expand...
Click to collapse
thanks man, I will run the RUU. I believe I have already done this in the past, but my memory is terrible xDD
3.2 Using RUU to restore partitions
Find your right RUU using 2 in this guide.
Flash your RUU as you normally would by double clicking the executable & following the instructions, you phone must be connected to PC via fastboot USB (in the bootloader).
If you get a Hboot Pre-update message, re-run the RUU once again with your phone connected in fastboot USB.
If the previous step fails, follow points listed under 4. Flashing RUU manually.
Reboot your device to bootloader, your bootloader should now say *Locked* or *Relocked*
Click to expand...
Click to collapse
From the tutorial on RUU in the link you provided, the last point on bootloader being locked or relocked... will I need to do revolutionary again or the other method to unlock it again? Will this be drawback flashing a new ROM?
thanks!
TheKaser said:
thanks man, I will run the RUU. I believe I have already done this in the past, but my memory is terrible xDD
From the tutorial on RUU in the link you provided, the last point on bootloader being locked or relocked... will I need to do revolutionary again or the other method to unlock it again? Will this be drawback flashing a new ROM?
thanks!
Click to expand...
Click to collapse
Hi,
Bootloader will not be affected because you are s-off.
You will not lose s=off either.
YOU WILL LOSE EVERYTHING else.
So,backup first.
You will end up with stock recovery,ROM and kernel.
You will need to re-install a custom recovery,before you install a new ROM.
See how it all works before you do anything.
malybru said:
Hi,
Bootloader will not be affected because you are s-off.
You will not lose s=off either.
YOU WILL LOSE EVERYTHING else.
So,backup first.
You will end up with stock recovery,ROM and kernel.
You will need to re-install a custom recovery,before you install a new ROM.
See how it all works before you do anything.
Click to expand...
Click to collapse
well, the RUU went fine, but now I have a locked bootloader, and can't flash a recovery via fastboot. (still S-OFF).
TheKaser said:
well, the RUU went fine, but now I have a locked bootloader, and can't flash a recovery via fastboot. (still S-OFF).
Click to expand...
Click to collapse
Hi,
Look HERE
Post 2:
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
Should unlock your phone again.
Run the phone for a while.
Does it still reboot?
malybru said:
Hi,
Look HERE
Post 2:
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
Should unlock your phone again.
Run the phone for a while.
Does it still reboot?
Click to expand...
Click to collapse
sweet, that did the trick
I flashed a dark splash screen and the cwm recovery. All went well and I could flash my 4.2.2 rom. I will restore my titanium backup apps and hope for the best. Cant tell now if the sudden turning off still happens because my phone has been plugged in all the time while I was doing this.
I will report probably tomorrow once the battery is bit used.
Sir, I must say, you are a legend. Thank you very very much for your help!!! your rock!:good: :laugh:
TheKaser said:
sweet, that did the trick
I flashed a dark splash screen and the cwm recovery. All went well and I could flash my 4.2.2 rom. I will restore my titanium backup apps and hope for the best. Cant tell now if the sudden turning off still happens because my phone has been plugged in all the time while I was doing this.
I will report probably tomorrow once the battery is bit used.
Sir, I must say, you are a legend. Thank you very very much for your help!!! your rock!:good: :laugh:
Click to expand...
Click to collapse
Hi,
Hope it all works out.
Okay, so the other day I flashed CM10.2, everything was working fine until I turned off the phone, but after about the 3rd time. I rebooted and the bootanimation started to skip and stuff, then the phone rebooted before bootup
It did it again about 3 more times, then it started to boot. When it reached the lockscreen I tried to unlock, but phone was frozen! Then it rebooted and kept doing this!
I read somewhere that if you keep letting it do so it would correct itself
I did so, no correction. Finally I tried to boot into the bootloader to boot cwm. The phone started to boot into bootloader then it rebooted. This time the rom was acting fine But just to test, I rebooted and the process started all over...
So I thought it was a issue with the nightly, but also had this issue with beanstalk rom. What is this and how do I fix!!
I'm rooted with S-ON, this is how my bootloader looks:
*** TAMPERED ***
*** UNLOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.13.50.05.31
OpenDSP-v31.1.0.45.0815
eMMC-boot
Hi,
I am fighting with this for 3 days. I have S-OFF, hboot 2.15.0000. Everytime I flash ROM with android 4.3 it boots for first time fine, but rebooting or flashing updates brings same problem you're having. Boot frozen or multiple reboots on bootanimation. Try flashing some ROM with android 4.2.2. This works for me oldo I am sad I cannot have night builds.
My bootloader says same information as yours, except tampered which dissapeared after flashing stock RUU.
skiller21 said:
Hi,
I am fighting with this for 3 days. I have S-OFF, hboot 2.15.0000. Everytime I flash ROM with android 4.3 it boots for first time fine, but rebooting or flashing updates brings same problem you're having. Boot frozen or multiple reboots on bootanimation. Try flashing some ROM with android 4.2.2. This works for me oldo I am sad I cannot have night builds.
My bootloader says same information as yours, except tampered which dissapeared after flashing stock RUU.
Click to expand...
Click to collapse
Tried flashing cm10.1, same issue Its not a 4.3 issue...
Did you guys flash boot.IMG?
Sent from my HTC One S using xda app-developers app
abracadabra11 said:
Did you guys flash boot.IMG?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
yeah, fastbooting the boot.img solved everything. I still get issue where bootanimation sometimes doesn't fully boot and the phone reboots, but thats a issue that everyone has with S-on and S-off.
I followed the instructions to the letter for Maximus 10.0 ROM. My bootloader shows:
TAMPERED
UNLOCKED
VLE PVT SHIP S-OFF RL
CID-T-MOB010
HBOOT-2.16.0000
RADIO-1.20.50.06.16
OpenDSP-v33.1.0.45.1128
eMMC-boot
I even tried going back to stock with relocking and flashing 3 of the TMOUS RUUs with no luck.
Each time the phone boots it loops or gets stuck on a splash screen. Oddly, even after I try to return to stock I get the splash screen from the Maximus 10.0 rom.
Is there a way to completely ERASE everything on this phone and start from scratch using fastboot and adb?
You can wipe everything from recovery, firmware installation also wipes everything.
If you want more help please try to be more specific. For example what happened with maximus or RUUs? Did you get any errors or bootloops? Do you still want to install maximus or want to turn back to stock? etc.
Sent from my HTC One S
ka_55 said:
You can wipe everything from recovery, firmware installation also wipes everything.
If you want more help please try to be more specific. For example what happened with maximus or RUUs? Did you get any errors or bootloops? Do you still want to install maximus or want to turn back to stock? etc.
Sent from my HTC One S
Click to expand...
Click to collapse
Maximus loads up to a black screen with just the time, battery, and signal icons, then eventually goes into a bootloop. The RUUs did the same thing. Blows me away what is going on now.
I would like ANY rom to work.
My CID is TOM010 or whatever the TMOUS is. Does that matter?
Even tried to install an older unknown jb rom and it still boot loops!!!
there must be a way to make this device complete NEW STOCK!!!!! my god!
f10a said:
Even tried to install an older unknown jb rom and it still boot loops!!!
there must be a way to make this device complete NEW STOCK!!!!! my god!
Click to expand...
Click to collapse
First of all did u try flashing the boot.img that is in the Rom zip file??
If yes did u try superCid or s-off ????
f10a said:
Maximus loads up to a black screen with just the time, battery, and signal icons, then eventually goes into a bootloop. The RUUs did the same thing. Blows me away what is going on now.
I would like ANY rom to work.
My CID is TOM010 or whatever the TMOUS is. Does that matter?
Click to expand...
Click to collapse
I'm in the same boat... maximus messed up my partitions, leaving me with only 48mb of sdcard space... I managed to reclaim that, but now Maximus wont boot EVEN after doing a complete wipe, downgrading to hboot 2.15, and re-installing maximus with his step by step process.
I dunno what to do now
f10a said:
I followed the instructions to the letter for Maximus 10.0 ROM. My bootloader shows:
TAMPERED
UNLOCKED
VLE PVT SHIP S-OFF RL
CID-T-MOB010
HBOOT-2.16.0000
RADIO-1.20.50.06.16
OpenDSP-v33.1.0.45.1128
eMMC-boot
I even tried going back to stock with relocking and flashing 3 of the TMOUS RUUs with no luck.
Each time the phone boots it loops or gets stuck on a splash screen. Oddly, even after I try to return to stock I get the splash screen from the Maximus 10.0 rom.
Is there a way to completely ERASE everything on this phone and start from scratch using fastboot and adb?
Click to expand...
Click to collapse
I JUST did this... I RELOCKED, went back to S-ON, and put my CID back to T-MOB010, and then RUU'd my device. Now I'm able to USE my phone. The only problem at the moment is that my radio doesn't work. I'm gonna see how to fix that and follow up with that later.
Hope that helps.
EDIT: Radio works, it just needed to be manually connected to my network