i just want to start by saying my phone is stock, non rooted and hasnt been tampered with in any way.
i was playing a game the other night and everything was working fine. exited the game and my phone froze, held the power button to reboot and now my phone is stuck in a boot loop at the htc quietly briliiant screen.
booting to fastboot and trying recovery, factory reset and clear data do nothing other then load back into the boot loop.
before sending the phone in for warranty and loosing my new screen protector i was going to try and fix it myself.
ive been doing a tun of reading and trial and error and im needing a little help.
ive installed the phone drivers and can boot into the bootloader and access fastboot.
my computer sees the phone and i can access fastboot and recognize the phone threw the pc
my first attempt was to install a ruu file 2.35 from t-mobile, i got an error about incompatible device id or something
second attempt i downloaded a ruu file 1.70 from fido, this one passed the device id but gave me another error related to my bootloader being too high of a version 1.13.0000
from my understanding to make this work i need a ruu file from fido/rogers version 1.84 or higher, or i need to change the device cid to tmobile to install that ruu.
when i tried to change the cid from a guide i found my problem i was entering is adb doesnt recognize my device when in fastboot and i cant access recovery or make any changes to the device.
im basically asking if anyone knows of anywhere i can downloader a higher version ruu for fido or rogers? ive been searching for hours but im coming up empty. or an easier way of fixing the phone by changing the cid?
Related
Hi guys, this is a friends Nexus S he bricked during an ICS update (official one). I can't get it to work at all. It boots up an android guy with a red triangle and a (!) coming out of his chest. The bootloader is locked (version I9020XXKL1). He's never tried to root beforee
Things I've tried:
Got ADB drivers working
'ADB factory reset oem unlock' gets me a dialog screen on the phone confirming the unlock, then when I confirm, I get: 'FAILED. remote erase: fail'. Tried with serial number (saw a random post mentioning that), but same result.
I tried flashing an IMG file through fastboot with a similar error. the device shows up in getstate and devices, but you can't write to it it seems.
Mentioned to someone at work and he said I should be able to get a stock RUU exe file and you just run the RUU. Similar to a 1 click odin fix, but...not. Cause I can't get into download mode. If I try to go into recovery mode from fast boot, that's when you see the dead android guy with the (!). If I just try and let it boot on its own..it just boot loops. Doesn't turn off/on, but never passes the 'Google' splash screen.
I've searched for the RUU files and can't find them anywhere, at least for a Nexus S. Am I missing something here? Not sure what else to try.
Thanks!
b0vine said:
Hi guys, this is a friends Nexus S he bricked during an ICS update (official one). I can't get it to work at all. It boots up an android guy with a red triangle and a (!) coming out of his chest. The bootloader is locked (version I9020XXKL1). He's never tried to root beforee
Things I've tried:
Got ADB drivers working
'ADB factory reset oem unlock' gets me a dialog screen on the phone confirming the unlock, then when I confirm, I get: 'FAILED. remote erase: fail'. Tried with serial number (saw a random post mentioning that), but same result.
I tried flashing an IMG file through fastboot with a similar error. the device shows up in getstate and devices, but you can't write to it it seems.
Mentioned to someone at work and he said I should be able to get a stock RUU exe file and you just run the RUU. Similar to a 1 click odin fix, but...not. Cause I can't get into download mode. If I try to go into recovery mode from fast boot, that's when you see the dead android guy with the (!). If I just try and let it boot on its own..it just boot loops. Doesn't turn off/on, but never passes the 'Google' splash screen.
I've searched for the RUU files and can't find them anywhere, at least for a Nexus S. Am I missing something here? Not sure what else to try.
Thanks!
Click to expand...
Click to collapse
Firstly is this still under warranty? Since its the offical ICS update. Just tell him to go to his provider and ask for a replacement since it was not the user's fault.
A few questions. Why is he receiving the ICS update now? If this was ages ago when ICS was first released, Google stopped ICS update for a weeks or so since there was some problems.
And if the warranty doesnt work. Id say root it and flash a Recovery.
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
It's a few months out of warranty, and no, TELUS won't replace it, he's already tried.
I also can't root it as mentioned. I get to this point in the guide
For Windows:
fastboot oem unlock
And get the ERASE:FAILED error once confirming the unloock.
i've been trying for the past two days to get my one s back to stock because after flashing cm10.1 the touch screen stopped working. nandroid backups don't work and for some reason, the ruu wont boot up. there are no errors, it just stops after preparing the install wizard screen. sometimes it'll say install failed, reinstall with recommended settings, but it still never makes it the the actual htc updating part. i've deleted temp folders and cache and whatever else i could get my hands on and no luck. anyone else have this problem? i cant find a solution anywhere.
thanks in advance
HomieOneKinobi said:
i've been trying for the past two days to get my one s back to stock because after flashing cm10.1 the touch screen stopped working. nandroid backups don't work and for some reason, the ruu wont boot up. there are no errors, it just stops after preparing the install wizard screen. sometimes it'll say install failed, reinstall with recommended settings, but it still never makes it the the actual htc updating part. i've deleted temp folders and cache and whatever else i could get my hands on and no luck. anyone else have this problem? i cant find a solution anywhere.
thanks in advance
Click to expand...
Click to collapse
Your going to have to re lock you phone and from fastboot your will have to run your factory RUU
Are you S-off ? have you changed your CID ?
dave1970 said:
Your going to have to re lock you phone and from fastboot your will have to run your factory RUU
Are you S-off ? have you changed your CID ?
Click to expand...
Click to collapse
still s-on and did change my cid. i've been trying to find a way to change those over fastboot, but no luck. and i know i have to relock it and run the ruu thru fastboot, i did that a few days ago when i first started tinkering. the problem is that the ruu.exe wont run and i cant figure out why. like i said, it'll launch and run the preparing installwizard, but when that parts done it just completely stops. no errors, no next screen, nothing.
/edit - i meant i didn't change my cid. every article i read about modding and flashing new roms, not one said that s-off was all but necessary or you're gonna be super screwed if you slip up a little bit. shoulda checked that a little more thoroughly.
/update - so it's all back to stock rom thanks to a nandroid dump i found. the only issue now is i'm trying to flash an ruu to completely restock the device and i'm coming thru with error after problem after nonsense.
starting with fastboot. when i got to lock the bootloader back up to run the hboot it gets an error - FAILED (status read failed (Too many links)). boot back into fastboot to run the ruu and the program doesnt recognize my phone and doesn't even get past the preparing install screen. so i relock the bootloader and go into a bootloop. backup from cwm and start over, quite possible with a reversed x axis touch screen.
when i connect to the pc, ruu doesn't run when connected in charge only mode. when connected as mass storage i get a disk read error and windows checks for errors (never finds anything, but each time i connect, it asks). just ran ruu and it recognized the phone, went all the way to the sending part of updater and then stopped responding, leaving my phone on the black htc update screen (that was the most successful ive been so far)
many other times i'll get multiple different errors that i haven't been able to recreate now that im trying to type them out, but they're all errors involving my data or sdcard. i belive one was unable to write to ruu_log. i'll try to recreate and be more specific.
Here is how I always got the RUU runnin:
- Flash stock recovery
- Relock bootloader
- Boot into bootloader (NOT fastboot mode, just bootloader)
- Connect device to the PC
- Run the RUU as an admin
jay-em-ass said:
Here is how I always got the RUU runnin:
- Flash stock recovery
- Relock bootloader
- Boot into bootloader (NOT fastboot mode, just bootloader)
- Connect device to the PC
- Run the RUU as an admin
Click to expand...
Click to collapse
can u give resumable link to TMOUS htc one s RUU...m unable to find one
Here are all RUUs for Ville c1 (s4 cpu):
http://www.androidruu.com/index.php?developer=Ville
I think the latest TMOUS one is version 3.14.531.11
Hi everyone,
I am trying to help a buddy out and getting his phone working. The phone is not rooted in any way shape or form.
Here are my issues
The phone will not boot into the stock rom. I can get it into the bootloader. Which I went to htcdev. To unlock the bootloader. Followed the steps and was able to get the phone screen to show unlock bootloader. But when I hit yes it reboots and stays on the white htc screen. Then it will keep rebooting. When I go back into bootloader. It still shows the bootloader as being locked? Any suggestions. I haven't flashed anything in about 3 years. But only Samsung things.
This is my set up
Your best bet is to try latest RUU: http://www.htc.com/us/support/htc-one-sv-boost/news/
I tryed that as well. Thinking it is kinda like Odin for samsungs. But as soon as it try to reboot into bootloader. It stays on the white htc screen
The RUU was running completely through and it still not booting?
I will take a picture of the screen. It does not go all the way through. Also I tryed the Ota. Zip. And changed it to PL80IMG and placed it in my SD card. It looked as if it went through and it told me to reboot. But still nothing.
This is what's happening.
Forget the OTA. It won't solve anything for you.
I also think, your bootloader must be locked to run the RUU.
And i think it is your only chance to get the phone back running, because there is no stock rom or backup for boost (as far as i know).
I am OK with rooting it. But in order for me to do it I have to get the bootloader to unlock which I can't seem to do. It does all the motions to unlock. Until the phone reboots
What i have found in this few minutes, Error 171 should be a driver issue.
So, you should make sure that the correct drivers are running (HTC Sync). Maybe another PC could be also a good try.
And you can't root a phone which is not booting into OS. You need a OS.
Is there different drivers I could try besides tc sync. I have tried both computers that I have one has windows 8. The other has windows vista.both have htc sync on them. Also tried a different cable.
If I type in cmd fast boot devices it shows my device being connected. The error shows up while it is waiting for the boot loader to reconnect
Latest should be this.
I will give it a try thank you for helping me. I'm banging my head against the wall for 2 days trying to figure out why nothing is working on this.
Its really kinda strange, that bootloader should belocked again after reboot.
But your focus must be the RUU.
old.splatterhand said:
Its really kinda strange, that bootloader should belocked again after reboot.
But your focus must be the RUU.
Click to expand...
Click to collapse
Yea, my main goal is to get it to boot up. I was hoping it was an easy fix. Like with the Samsung epic I had. Just slap it in with odin and boom. after I couldn't get the RUU to work I figured I would try to root it. but since I can't even get the bootloader to unlock. I am stuck and that's the biggest reason I posted. normally I wouldn't I try to read other post and/or youtube it to find someone with a similar problem.
Quick question. When I go into the RUU can/should be in fastboot?
Yes, you should be in fastboot (USB) mode.
Ok so I downloaded the drivers you recommend. It was different then the ones I had. I also downloaded the RUU from the htc site as well just in case. Will try when I get back home. Thanks again.
So here is what I have. I downloaded driver v4.11.0.001. And installed. Downloaded ruu k2_cl_jb_45_s_sprint_wwe_boost_3.05.653.4......
I went into cmd and type fastboot devices. My device showed up. Ran the ruu. Samething happened. The ruu stops because when the phone reboots. It doesn't reboot to the bootloader.
Also I tried in cmd to get the phone to reboot to bootloader with no luck. Is there any thing else I can try?
Just as a quick intro, hello everyone. I'm new to the forum, but I've been reading from this site for a couple years now. Now that that's out of the way...to the real question.
So, my DNA committed suicide the other day and I received an HTC One M7 from a friend of mine who switched to apple. Yeah...he's stupid. But it's my gain. ANYHOW! It's a sprint HTC One m7 with the 1.57 hboot. I've come across an issue with trying to break this system open. Unlock went great along with TWRP recovery flash and superSU. No issues with any of that. HOWEVER! Somewhere down the line I believe my baseband and IMEI has been lost internally. I only come to this conclusion through research and finding a somewhat similar situation.
Currently, this is what's happening. I can enter bootloader and recovery just fine. The phone boots up just fine. But, once the phone is booted and I unlock the screen, all I get is a white screen with an HTC logo. Touch works, vibration works, it registers everything I do including the pull down (just to display header. it never actually pulls down), usb debugging icon, sounds, screenshot, PC recognizes device and everything. But it stays like this for about a minute or two and then restarts. It does this over and over.
I've been trying to s-off using rumrunner just to see if by chance it'd have success, but the phone won't recognize ADB. It will recognize fastboot commands perfectly, but not ADB. And yes...I use ADB commands in recovery I've tried every driver I could think of and every version of recovery and adb.exe I could find compatible. Because the computer won't recognize the phone in ADB, I can't get anywhere in rumrunner and because I can't access the main screen after unlocking the screen, I can't even use sunshine.
I'm at a total loss and I don't have any money for another phone. I really need some advice to get this fixed so I can flash a baseband and/or RUU and get this thing working with ViperONE. Please halp!
- Charles
You need to flash a stock ruu with fastboot and the imei will restore .
To see if the imei is still in the partition but the software doesn´t recognize it go in fastboot mode and type fastboot getvar all and the imei should be there.
Hi everyone. Thanks for your attention
I have a HTC Mini. Today I wasn't able to connect my phone into the wifi. Then, I restarted and afterwards the phone didn't boot at all. It goes only to the bootloader menu. Last two days I was looking for the solution. In the HBOOT menu when I tried to the factory reset it only jumps into the fastboot menu, same thing for the recovery. When I am in the fastboot menu, if I click on reboot, or reboot bootloader it just reboot and the HBOOT menu comes again.
However, my HBOOT menu is locked and when I wanted to try unlock it. following problem happen :
- when I connect the phone to a Mac, Fastboot Devices detect (but only fastboot, ADB devices return nothing) the phone and I could get the token for unlocking procedure, but when I load the the unlock token which sent to me by mail from HTCDEV, nothing happen. it just say everything was successful on Terminal, but nothing shows up on the phone to Confirm unlocking procedure and sometimes it hangs and if I try pushing the token again (the bin file), I receive an error, fail to splash the screen (something like this). However, I already installed the HTC Sync Manager and every other possible driver I could find on the internet.
When I use windows, after installing HTC Sync and all of the drivers several time, still the command for Fastboot devices or ADB Devices return nothing. I don't care about the phone data or anything. I just want to like Flash the whole operating system and everything . thats fine. But nothing is working properly.
Please guide me if you have any idea about this problem.:crying::crying:
It happened to me too. Same sh1t. Camera didn't worked so i decided to restart the phone...from that time same story like yours.
same here, but i have an idea
when i do fastboot getvar all my baseband says N/A indicating corrupt or missing radio rom
the correct radio should be Radio_1.29.40g on mine based on the RUU i have on hand (used before)
RUU attempts to get into different mode and fails
i have been unable to extract the files from the RUU