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!
Related
I have tried to unlock and root my Nexus S. I achieved unlock, but I am having problems with ClockworkMod Recovery v4.0.0.2 When I reboot, all I get is "Google" in the middle of the screen, with an "unlocked" lock image at the bottom of the screen. I am a new to this, and may have done something wrong.
Paul
Nexus S (Rogers)
Barlaw604 said:
I have tried to unlock and root my Nexus S. I achieved unlock, but I am having problems with ClockworkMod Recovery v4.0.0.2 When I reboot, all I get is "Google" in the middle of the screen, with an "unlocked" lock image at the bottom of the screen. I am a new to this, and may have done something wrong.
Paul
Nexus S (Rogers)
Click to expand...
Click to collapse
You have to be more specific on what you did.
Did you flash a ROM?
.. What did you do?
The "unlocked" image is supposed to be there.
Hold Volume up + Power then go into recovery. Upon there, you should be able to do something. Perform a nandroid restore, flash a ROM, etc.
Remember when you flash a ROM you must wipe: factory settings, cache, dalvik
I'm here thinking you flashed a ROM and didn't wipe so it's not loading the ROM.
If this is the case, just wipe the 3 things I said above and reflash the ROM and then reboot and you'll be on your way.
And please stop using the term 'brick' it is not bricked.
Brick doesn't mean your phone doesn't start and it seems like its broken. Brick means to the state where you CANT turn on the phone AT ALL.
You need to flash the recovery image correctly.
Fastboot flash recovery cwmfilename.img
Then turn off phone and boot. Up by volume up and power to get to bootloader then select recovery.
Sent from my HTC Sensation 4G using XDA Premium App
Thanks for your help. You were right. I have everything working now. Thanks.
Hi, im new to rooting and stuff and i could use some help. after i flashed twrp and did a backup followed by a reboot i lost access to to everything except hboot. No i cant use my phone or twrp but i still have hboot unlocked. can anyone lead in me in the right direction? thanks
shadyboy039 said:
Hi, im new to rooting and stuff and i could use some help. after i flashed twrp and did a backup followed by a reboot i lost access to to everything except hboot. No i cant use my phone or twrp but i still have hboot unlocked. can anyone lead in me in the right direction? thanks
Click to expand...
Click to collapse
Reboot the phone holding power and volume down until you're into the bootloader screen and then select recovery. Try restoring the backup you made. If that doesn't work go back into recovery, put a rom on the sdcard, and flash it. Then reboot.
i cant get to my sdcard because i cant get to twrp anymore. everytime i have it reboot from bootloader it just goes the htc screen and turns off. :crying:
Reinstall twrp from fast boot.
Sent from my HTC One XL using xda premium
Yea, try that. After that select reboot recovery from the bootloader not reboot.
omg i got twrp back. wow that scared me thanks.
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
Hi everyone
I have a desire S that gets stuck on the HTC logo in startup and won't boot.
When i try to get to the bootloader- it works, but if i try to do anything, it just gets stuck.
Trying to get to recovery- it turns off and vibrates 7 times.
I try to do a factory reset- the moment i press the power button it gets stuck and won't respond
Same for everything else.
Anyone knows what can i do with this?
The device is unrooted, but S-off.
Did you even look before you made this thread? The most recent thread was from a user with what sounds like the same problem as you. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2241721
Sent from my Desire S using xda app-developers app
Yes, i looked. a LOT.
This is not the same problem at all- he can get to recovery properly and do a factory reset, while i can't.
Well, perhaps you have done already, some things i 'll mention but..
Simpliest:
1. Remove battery and wait at least a minute before putting it back
( preferably switch the phone off- if you can )
2. Boot it again, connect to pc, check whether fastboot sees your device...
( you said you're not able to boot the system on it- so no ADB )
Try to reboot via fastboot issuing command
fastboot reboot
In case it didn't work
1.flash recovery again ( clockworkmod or 4ext )
and see what happens-when you'll have succeded,
try again to get to recovery from bootloader,
Optional:
when you get there , flash superuser zip
( If you'll still not be able to boot in to system , you may attempt to flash
some other rom- as .zip via recovery )
2. May also attempt to restore factory image on the phone ( RUU )
which proceeds from fastboot...
If all the above fails, there is an article you may be interested in reading,
that hopefully is not your case but....your call
http://forum.xda-developers.com/showthread.php?t=1284196
Edit: if it is unrooted, it may even still have stock recovery -
nothing you may easily interact with, on the level given by custom...
Friend was flashing some roms, something bad happened, and we are now installing RUU through the fastboot. About halfway into it, we get an error that it is out of memory. How can I delete files off the phone if the only phone menu that is woworkings the oem HTC logo screen? Or any other way around it?
Here is a link to a picture that I took. http://imgur.com/7mmVGcR
I'm the friend. This was resolved using the following.
Found this link to HTC One M8 Stock Recovery
allowed me to download the verizon version of HTC One M8 Stock recovery...
Using command prompt and the command
fastboot flash recovery vzw_m8_stock_recovery.img
The phone then rebooted back to stock while keeping s-off and root..
This is my first time having a rooted phone and I believe I installed a GSM rom and threw my phone for a loop causing all the data to delete and format the whole device. All that was left was TWRP.
Anyway this is now resovled.
BygSii said:
Friend was flashing some roms, something bad happened, and we are now installing RUU through the fastboot. About halfway into it, we get an error that it is out of memory. How can I delete files off the phone if the only phone menu that is woworkings the oem HTC logo screen? Or any other way around it?
Here is a link to a picture that I took. http://imgur.com/7mmVGcR
Click to expand...
Click to collapse
That's your pc out of memory. Can you try ruu via SD card? Option two on my page