hi everyone,
I could really need a quick solution.
I just received my phone from a screen repair and was going to root it.
I unlocked it first with htcdev and now it says juopunutBear and it's S OFF.
but when I'm booting it, it just stayson the HTC screen and when I select recovery or factory reset it goes into the reset screen for a little while and after that it returns to the boot screen.
If you can get to the hboot scrren it should be fixable.
You might be able to flash a new copy of a recovery from fastboot on your computer. That should let you reinstalled a saved rom.
You may also be able to flasha rom through a pm58img file in the bootloader.
If all else fails you should be able to run an ruu to reset it entirely and start over.
Sent from my HTC Sensation using xda app-developeras app
Thanks! I'm running the RUU right now, everything will probably go as planned!
i recently started another thread asking for help with my soft bricked stock htc one s.
i was basically playing a game, exited then rebooted and got stuck in a boot loop. tried to install various ruus but was unable to find the proper version/cid to install.
today i got the bright idea of unlocking the bootloader and installing recovery to avoid the issue of my apparent o/s corruption and just installing a custom rom.
unlocked the bootloader successfully, installed cwm successfully then try and boot into recovery, screen goes white with the htc warning about being for developers for 30seconds or so then it restarts into the boot loop at the htc quietly brilliant screen. though maybe there was a problem with the cwm so i tried twrp with the same problem.
does this mean im looking at a hardware fault or does anyone think it could still be software related? im kind of worried now as i probably just voided any chance of getting warranty from htc...
A recovery and unlocked bootloader will not help you get out. Now flash a custom ROM. Don't forget to flash the boot.img
Sent from my locked, tampered ville
---------- Post added at 07:20 AM ---------- Previous post was at 07:18 AM ----------
Oh and don't start two threads!!
Sent from my locked, tampered ville
Is there a way to flash a rom from Fastboot? I've tried fastboot flash system romname.zip and fastboot flash boot boot.img without any luck, appears I've made it worse as the bootloop loads to fastboot now...
I can't get adb to recognize the device, only fastboot commands work. It's weird though, I checked the log of the failed ruu installs and it seems to recognize the phone with adb during the install attempt. I've also tried mirroring the commands from the ruu log but I can't replicate the ability to access adb. I was able to get that black htc screen that pops up during the ruu install though, I dunno if that's a special mode for running adb commands or what it's for but I wasn't able to connect then either...
fastboot flash zip rom.zip
then
fastboot flash boot boot.img
i broke down and spent $20 on a official ruu for my phone. it installed successfully but the phone is still stuck looping the white htc screen.
hoping htc honors my warranty, i unlocked my bootloader trying to fix this problem but its starting to look hardware related... unless there is another partition of software on the phone that could have become corrupted...
mikeinaus said:
i was basically playing a game, exited then rebooted and got stuck in a boot loop.
Click to expand...
Click to collapse
It happens sometimes, you should have just gone into the stock recovery and did a factory reset. But it's too late lets move on...
unlocked the bootloader successfully, installed cwm successfully then try and boot into recovery, screen goes white with the htc warning about being for developers for 30seconds or so then it restarts into the boot loop at the htc quietly brilliant screen. though maybe there was a problem with the cwm so i tried twrp with the same problem.
Click to expand...
Click to collapse
Sounds like the kernel didn't get put, you know the part where you are supposed to do fastboot flash boot boot.img. But it's too late lets move on...
does this mean im looking at a hardware fault or does anyone think it could still be software related? im kind of worried now as i probably just voided any chance of getting warranty from htc...
Click to expand...
Click to collapse
As long as you can get to bootloader you can recovery the phone (as least that's my experience)
mikeinaus said:
Is there a way to flash a rom from Fastboot? I've tried fastboot flash system romname.zip and fastboot flash boot boot.img without any luck, appears I've made it worse as the bootloop loads to fastboot now...
Click to expand...
Click to collapse
Yeah you made it worse, since it only loads to fastboot now, most likley you caused a problem with your recovery. But that's real easy to fix.
I can't get adb to recognize the device, only fastboot commands work. It's weird though, I checked the log of the failed ruu installs and it seems to recognize the phone with adb during the install attempt. I've also tried mirroring the commands from the ruu log but I can't replicate the ability to access adb. I was able to get that black htc screen that pops up during the ruu install though, I dunno if that's a special mode for running adb commands or what it's for but I wasn't able to connect then either...
Click to expand...
Click to collapse
That's a real mess, just stop whatever you're trying to do there.
mikeinaus said:
i broke down and spent $20 on a official ruu for my phone. it installed successfully but the phone is still stuck looping the white htc screen.
Click to expand...
Click to collapse
Where did you spend the $20? File Factory? An RUU shouldn't fail to the fix the problem. I would suggest you just unlock it, install a recovery and then your rom of choice. Even if it's just a rooted stock ROM.
If I was in your spot, I would do this.
1. Unlock Bootloader
2. Install TWRP - Do a factory reset, then wipe system.
3. Flash a custom rom
4. Boot into bootloader - fastboot flash boot boot.img.
5. Reboot
If I was in your spot, I would do this.
1. Unlock Bootloader
2. Install TWRP - Do a factory reset, then wipe system.
3. Flash a custom rom
4. Boot into bootloader - fastboot flash boot boot.img.
5. Reboot
Click to expand...
Click to collapse
1. have done so
2. tried it as well as cwm, phone will not boot into a recovery, doing so just loads into the loop
3. tried without luck
4. tried this as well after flashing rom and still same problem
running the ruu removed the "tampered" message from bootloader as well as stopping the loop from loading into fast boot, it also removed the red developer text from popping up when booting. however the phone is back to its original problem of looping the htc quietly brilliant screen. ive run the ruu twice now without any change.
if the ruu cant fix the problem im doubtful messing around with custom roms will. there is clearly some kind of problem with the phone causing the loop. as far as i understand a ruu completely wipes all the data on the phone and reinstalls all the partitions from scratch.
ive just sent htc an email seeing if theyll cover it for warranty, hopefully they will stand behind their product, as i was not the cause of this problem...
i got the ruu from football, he is the one who posted the thread with all the stock ruu's and he was able to track down the proper one for my phone...
mikeinaus said:
1. have done so
2. tried it as well as cwm, phone will not boot into a recovery, doing so just loads into the loop
3. tried without luck
4. tried this as well after flashing rom and still same problem
running the ruu removed the "tampered" message from bootloader as well as stopping the loop from loading into fast boot, it also removed the red developer text from popping up when booting. however the phone is back to its original problem of looping the htc quietly brilliant screen. ive run the ruu twice now without any change.
if the ruu cant fix the problem im doubtful messing around with custom roms will. there is clearly some kind of problem with the phone causing the loop. as far as i understand a ruu completely wipes all the data on the phone and reinstalls all the partitions from scratch.
ive just sent htc an email seeing if theyll cover it for warranty, hopefully they will stand behind their product, as i was not the cause of this problem...
i got the ruu from football, he is the one who posted the thread with all the stock ruu's and he was able to track down the proper one for my phone...
Click to expand...
Click to collapse
You're in a ****ty spot then. There might be one or two ways to still recover but it sounds like your chances are getting slimmer. I've seen a few other reports of completly stock One S's taking a ****. I hope HTC fixes it for you.
htc said this regarding unlocking the boot loader when i asked about coverage with my problem. looks like they may still cover it. im betting there gonna take the easy way out and just say its not covered when its all said and done though. ive read horrible things about htc customer service...
Not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty. There are several possibilities of what may have caused this issue, that are covered by the warranty, in which the unlocking of the bootloader would not be a problem. We advise you to contact our tech specialists as they will let you know if this procedure will be covered by the warranty.
Click to expand...
Click to collapse
I tried to do the OTA update to ICS for my T-Mobile Sensation 4G and all seemed to be going well till the phone restarted. The phone now gets stuck with the message "Process system is not responding. Would you like to close it?" I have the option to Wait or OK but the phone will not allow me to select an option.
I tried a hard factory reset but I still get the same message when the phone tries to boot.
Can anyone help me get my phone working again?
did you tried reset from bootloader ?
can you got to recovery (once you enter recovery ..pres vol down + vol up + power together ..you will get some options there ..select factory reset) do factory reset then reboot and see ...otherwise RUU is the best way
I ended up having to do an RUU to get the phone to work again but for some reason I can't get it rooted again.
I managed to get the phone to be S-OFF and the bootloader is unlocked but can't figure out how to root it at this point.
Can someone walk me though how to root my phone?
Winia said:
I ended up having to do an RUU to get the phone to work again but for some reason I can't get it rooted again.
I managed to get the phone to be S-OFF and the bootloader is unlocked but can't figure out how to root it at this point.
Can someone walk me though how to root my phone?
Click to expand...
Click to collapse
flash a recovery
then flash this from recovery
http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
I've got an AT&T HTC One X. It keeps rebooting over and over, it gets stuck at the bootloader screen most of the time. It never makes it to the home screen and factory reset does nothing. Is it bricked? Bootloader is still locked and S-on. I thought about trying a RUU but with the one I downloaded the image versions don't match up. Help, I'm running out of ideas.
More information required. What are your bootloader details? Was the bootloader ever unlocked? Exactly which RUU did you try?
Transmitted via Bacon
Hello
I´m going crazy here.. So I wanted to try Android 5 and long story short my phone is without a rom and apparently won´t install one.
I got the "sdcard wont mount" error but got that fixed by flashing stock recovery and reflash TWRP 2.8.4.0.
But now I cant get any rom to boot. It seem to install just fine but then ether stops at the "white" screen or at the black that comes after.
I tried "Candy5" with "gapps nano" and all seems fine but it wont boot up. Then I tried a CM10.2.0 witch is 4.4.3 but I cant get gapps to install on that one.
Info:
HTC One S s4
Old rom that I had before = Unknown Blackbean version
Hboot = 2.15
Radio = 1.11.50.05.28
Might be because I don´t know how it works but I cant get ADB Sideload to work ether.
Says "Starting ADB sideload feature. . ." in console. And then adb can´t find the device when i run a "adb devices" command.
Hope someone can help me
Edit:
Found a RUU that worked So the phone should not be completely broken.
So I unlocked the bootloader again and flashed the latest TWRP. Things still work at this point!
Then I tried the CM11 rom again and it´s still the same.. White HTC screen (whitout the red text for some reason) then the screen goes black and nothing happens.
Am I doing something wrong when I install the roms? Did it the same way with my old Galaxy s plus yesterday and it worked first try. From 2.x straight to 5.0.2.
How I´m doing it:
Wipe - Data, Cache and Dalvik
Install rom
Reboot phone
Edit 2:
Restored the backup I did after I got the phone running with the RUU. And that also worked as i should.
So why can´t i get any custom rom to work :crying:
Edit3:
I somehow got it to work and is now running LiquidSmooth on 5.0.2
This thread can be locked or deleted now I think.
I have the same probable but I can't even get RUU to work.
Do you have T Mobile phone? Where did you download RUU from?
No I´m not on T-mobile.
I got the RUU from:
androidruu.com/?developer=Ville
twiifm said:
I have the same probable but I can't even get RUU to work.
Do you have T Mobile phone? Where did you download RUU from?
Click to expand...
Click to collapse
I'm in the same boat, I got my recovery to work fine but I can not get any roms to install. I can not find a ruu, my software ver is 3.16.661.5 Telus. I have tried about 4 diff roms. I get stuck on the white HTC screen. boot is unlock but s is on, can not turn it off because adb debug is not on. have no os to load in to, so I can get adb
1st edit
looked around abit if you flash the boot img your rom will load if you have s on.
Dklcp said:
I'm in the same boat, I got my recovery to work fine but I can not get any roms to install. I can not find a ruu, my software ver is 3.16.661.5 Telus. I have tried about 4 diff roms. I get stuck on the white HTC screen. boot is unlock but s is on, can not turn it off because adb debug is not on. have no os to load in to, so I can get adb
1st edit
looked around abit if you flash the boot img your rom will load if you have s on.
Click to expand...
Click to collapse
I had to relock and flash stock recovery in order to get RUU to work. Now my phone is at least working but I still cant flash any roms. I also used rumrunner to get s-off
If you're S-On, have you separately flashed the boot.img via fastboot?