completely stock (never tampered) Mini won't boot past hboot into OS - HTC One Mini

Hello XDA members,
My wife's HTC One Mini's battery drained yesterday and when we charged it up, it will not boot into the OS. I'm quite familiar with rooting, loading ROMs, and stuff like that for my HTC One, but it's really odd that the stock AT&T ROM and everything is getting this behavior. I would ideally not have to wipe everything right away because she took pictures of our new born daughter (3 months) and she unfortunately did not setup G+ to backup her photos. I'm a little hesitant to bring it to AT&T right away (we have insurance on this phone) because I feel like they might not explore all the options as we would here on XDA.
here is what the boot screen says.
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
OS-1.32.502.3
eMMC-boot 1024MB
Sep 3 2013,11:06:59.0
FASTBOOT
usual volume button commands
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I can get into BOOTLOADER which lists, recover, factory reset, clear storage, simlock, image CRC, and show boarcode.. but nothing happens when I select them with the power button.
I'm at a loss here. I'm going through the process of getting my Windows 8.1 drivers to connect to fastboot to see if I can access the card to pull down the images but I'm not sure if I can do that since I didn't have any opportunity to unlock it in ADB prior to booting into hboot.

iceterminal said:
Hello XDA members,
My wife's HTC One Mini's battery drained yesterday and when we charged it up, it will not boot into the OS. I'm quite familiar with rooting, loading ROMs, and stuff like that for my HTC One, but it's really odd that the stock AT&T ROM and everything is getting this behavior. I would ideally not have to wipe everything right away because she took pictures of our new born daughter (3 months) and she unfortunately did not setup G+ to backup her photos. I'm a little hesitant to bring it to AT&T right away (we have insurance on this phone) because I feel like they might not explore all the options as we would here on XDA.
here is what the boot screen says.
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
OS-1.32.502.3
eMMC-boot 1024MB
Sep 3 2013,11:06:59.0
FASTBOOT
usual volume button commands
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I can get into BOOTLOADER which lists, recover, factory reset, clear storage, simlock, image CRC, and show boarcode.. but nothing happens when I select them with the power button.
I'm at a loss here. I'm going through the process of getting my Windows 8.1 drivers to connect to fastboot to see if I can access the card to pull down the images but I'm not sure if I can do that since I didn't have any opportunity to unlock it in ADB prior to booting into hboot.
Click to expand...
Click to collapse
I gotchu my friend ;D http://www.htc.com/us/support/htc-one-mini-att/news/ That is the ruu for the htc one mini

abzboi said:
I gotchu my friend ;D That is the ruu for the htc one mini
Click to expand...
Click to collapse
Thanks! Unfortunately the executable requires the phone to boot into the OS to be recognized and the phone isn't booting into it. Trying to find the RUU stock ROM now to see if maybe I can push it over via fastboot. Crossing fingers!

iceterminal said:
Thanks! Unfortunately the executable requires the phone to boot into the OS to be recognized and the phone isn't booting into it. Trying to find the RUU stock ROM now to see if maybe I can push it over via fastboot. Crossing fingers!
Click to expand...
Click to collapse
Ah I read that it will work too if it is fastboot which is why you were suggesting it. I'm wrestling with fastboot drivers and windows 8.1 so it is recognized so I dualbooted into ubuntu which can communicate via fastboot so I'm hoping WINE will run and flash the RUU .exe

So I ended up rebuilding an older laptop to Windows 7 and ran the RUU executable and it looked promising at first with the updater recognizing the device and displaying what software version and stuff.... but then when it rebooted into hboot with it's process, the update failed.. not sure if it matters but it was "updating" from the same version as the current version. I was hoping this would be a fresh install. So now I'm looking into maybe doing a fastboot oem unlock and flashing a rom myself. Not sure if this will help me get the phone back from the dead, but going to do some more reading and exploring. If anyone has some shots-in-the-dark they would like to offer, I'm up for trying them.

I hope you would be able to fix it.

Ok so here is the latest and hopefully someone can confirm what I'm thinking for next steps.. I attempted to unlock the bootloader from HTC Dev. I was able to extract the keys, and I loaded the BIN with the new keys that will unlock the bootloader. Interestingly enough, I was expecting the HTC dev splash screen warning to come up where I would have to Accept the new terms and stuff, but that did not come up at all. So it was like I could go through the process and communicate to the device to unlock the bootloader, but something must be corrupt about it because it is just not responding the way it should on certain commands/tasks.. My bootloader is still locked (S-ON)
SO.. I stumbled upon someone mentioning that we are able to load CWM recovery even on a locked bootloader. Is this true and available for the HTC One Mini as well?? Couldn't find a definite answer on that for this device.

iceterminal said:
Ok so here is the latest and hopefully someone can confirm what I'm thinking for next steps.. I attempted to unlock the bootloader from HTC Dev. I was able to extract the keys, and I loaded the BIN with the new keys that will unlock the bootloader. Interestingly enough, I was expecting the HTC dev splash screen warning to come up where I would have to Accept the new terms and stuff, but that did not come up at all. So it was like I could go through the process and communicate to the device to unlock the bootloader, but something must be corrupt about it because it is just not responding the way it should on certain commands/tasks.. My bootloader is still locked (S-ON)
SO.. I stumbled upon someone mentioning that we are able to load CWM recovery even on a locked bootloader. Is this true and available for the HTC One Mini as well?? Couldn't find a definite answer on that for this device.
Click to expand...
Click to collapse
Have sent you a PM re your issue.....
Re flashing recovery without fastboot (locked bootloader), it can be done, but only, as far as I know, via the phone os using CWM manager or Flashify (which is a cool app!)

wanted to close the loop on this thread that nelvinchi and I literally tried everything we could think of to bring the phone back to life with no avail. Much respect out to nelvinchi for taking his time to help me out! We've determined that the device has a faulty memory chip and cannot be recovered...

Mine just did the same thing and I can't get through to anything I need help also if you have found a solution

Help my
provided you solve a problem with one htv mini.my I have the same problem, please help me

Related

Help needed please.... got into a dead end with my One X

Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster
sunster00 said:
Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster
Click to expand...
Click to collapse
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout
jags_the1 said:
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout
Click to expand...
Click to collapse
Hi mate thanks for offering advice and help. I have not had to use your method as I decided to give the HTC bootloader unlock code one final try before proceeding to your rescue plan and all of a sudden it was successful again. I got into recovery and did a nandroid restore so am back online again, but have nevertheless made note of your method in case I become stuck again in the future. Thanks anyway for your reply! :good:

[Q] VM HTC One V CDMA Sooooo Messed Up!

I am new to all of this, and dumb as a rock. That being said, I have soft-bricked this phone. I loaded PACman v15.3 primoc inyourface09.zip first
Went to boot loop. In trying to fix that, I did a bunch of other stuff that didn't work and I don't really remember what all I did-been a week of this chaos. Last thing I did was load Cyanogen Mod 9, which boot looped. Still shows this when I go to fastboot:
*** UNLOCKED ***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0928
eMMC-boot
May 14 2012.20:27:30
Here is other possibly useful info.
MWID: Hex:A10000023E805EE
SN: FA2AJX40824
MB: 31B15AD04215
MEID Dec: 270113181115205870
SD Checking
LOADING
wRONG OR NO ZIPPED IMAGE [PK76IMG.ZIP]
lOADING
NO IMAGE [PK76IMG.NBH]
same for .TAR, .AES, .ENC
I then loaded gapps-jb-20120726-signed.zip, JmzStockDeodex-VirginMobile.zip and JmzStockodex-VirginMobile.zip
I still get the HTC white screen with red disclaimer. Then goes to buzz, lightning, Red Virgin Mobile splash screen with sound, and reboots to HTC white screen-boot loop.
When I got a PK76IMG.ZIP and tried to flash it, it says it can't open the zip file.
But I can still get to the Hboot, Fastboot screen and recovery. Backup was empty :s
Tried to load a different recovery, but just like pacman, twrp won't go away.
And just so you know, I did factory reset a gazillion times.
Help! What have I done, and what can I do to fix it? I am comfortable with command lines, poking around in code, etc., but not with a totally new device like this...obviously, too much to mess up.
.
..
Still need serious help! found a possible reason for problem
Seems my HBoot 1.53.00.00 is for GSM; my phone is CDMA. Do how do I install/where do I download the correct hboot for vmt120 (the model number for this One V)?
I have been researching the phone and the problem, not just posting for help ad nauseum. I really need some help, please.
Thanks in advance, folks.
goofed again said:
Seems my HBoot 1.53.00.00 is for GSM; my phone is CDMA. Do how do I install/where do I download the correct hboot for vmt120 (the model number for this One V)?
I have been researching the phone and the problem, not just posting for help ad nauseum. I really need some help, please.
Thanks in advance, folks.
Click to expand...
Click to collapse
Were you able to get a backup of the original config, (before you first rooted it?)
(I have the same phone, same radio, (hboot 1.57), for NTelos, and am able to boot, but just no wifi/mobile data).. So, if you have a good backup, I might be able to trade a stock kernel that works for my phone.
I'm desperate also, so I know how it feels to have a machine that doesn't work,...
goofed again said:
I am new to all of this, and dumb as a rock. That being said, I have soft-bricked this phone. I loaded PACman v15.3 primoc inyourface09.zip first
Went to boot loop. In trying to fix that, I did a bunch of other stuff that didn't work and I don't really remember what all I did-been a week of this chaos. Last thing I did was load Cyanogen Mod 9, which boot looped. Still shows this when I go to fastboot:
*** UNLOCKED ***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0928
eMMC-boot
May 14 2012.20:27:30
Here is other possibly useful info.
MWID: Hex:A10000023E805EE
SN: FA2AJX40824
MB: 31B15AD04215
MEID Dec: 270113181115205870
SD Checking
LOADING
wRONG OR NO ZIPPED IMAGE [PK76IMG.ZIP]
lOADING
NO IMAGE [PK76IMG.NBH]
same for .TAR, .AES, .ENC
I then loaded gapps-jb-20120726-signed.zip, JmzStockDeodex-VirginMobile.zip and JmzStockodex-VirginMobile.zip
I still get the HTC white screen with red disclaimer. Then goes to buzz, lightning, Red Virgin Mobile splash screen with sound, and reboots to HTC white screen-boot loop.
When I got a PK76IMG.ZIP and tried to flash it, it says it can't open the zip file.
But I can still get to the Hboot, Fastboot screen and recovery. Backup was empty :s
Tried to load a different recovery, but just like pacman, twrp won't go away.
And just so you know, I did factory reset a gazillion times.
Help! What have I done, and what can I do to fix it? I am comfortable with command lines, poking around in code, etc., but not with a totally new device like this...obviously, too much to mess up.
Click to expand...
Click to collapse
Hey! Just restore your Radio back to stock. Google "RUU Stock for HTC ONE V VM" and there are some articles that could help you. Basically, you just run the RUU and extract some files in it.
---------- Post added at 11:23 PM ---------- Previous post was at 11:17 PM ----------
plebevt said:
Were you able to get a backup of the original config, (before you first rooted it?)
(I have the same phone, same radio, (hboot 1.57), for NTelos, and am able to boot, but just no wifi/mobile data).. So, if you have a good backup, I might be able to trade a stock kernel that works for my phone.
I'm desperate also, so I know how it feels to have a machine that doesn't work,...
Click to expand...
Click to collapse
So guys, if you still have this problem here' what you'll need to do.
Originally Posted by CafeKampuchia
Before you start, you will need to set up your computer to properly recognize the phone. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync.
About HTC Sync: The only reason you need HTC Sync installed is for the USB drivers that come with it. But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
Here we go:
First of all, google "RUU of HTC ONE V CDMA" or sumthing. then you'll find alot of things. Choose the SPRINT/VM Then:
1. Download the correct RUU for your device from Football's Primo Shipped ROM Collection.
2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up. While the RUU wizard is open,(LET IT OPEN UP, DONT DO ANYTHING!) find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT/B] using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery recovery_signed.img
6. Relock the bootloader using the following command:
Code:
fastboot oem lock
7. Re-run the RUU. It will restore the device to it's original condition, locked (though *** RELOCKED ***) and unrooted.
Once the install is done you'll have unlock the bootloader again using the token you already have from the first time, reflash CWM Recovery and re-root. All this will be 10x easier than the first time.
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!

[Q] HTC One X (At&t, evita) believed bricked after ruu update

Earlier today I tried to update my HTC One X's firmware to 3.18 in order to install the latest cyanogenmod nightlies. First, I was confused at why the latest cyanogenmod nightly would not flash so after looking it up and figured out I needed to update the firmware but to do that I would have to relock the bootloader. Second, I had issues trying to relock the bootloader, eventually got that (did not know adb was updated). Third, after believing my nightmare was over, I quickly decided I would try to flash the latest evita ruu, which completed without any errors and I clicked finish. (RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed) straight from HTC's website. Finally, after a few minutes I noticed that my phone did not have a notification led, nor was it booted into the lovely (opinions may differ) HTC sense 4.1.
That is the story of how my phone got to the state it is in. The state being no lcd in any way, no notification led, but I can still hear the phone being plugged into windows and can hear it shut down and turn on (with the windows usb sounds) when holding the power button and pressing it as if it worked and I was doing a hard reboot(about a 10 second press to shut down and get the usb disconnected noise). (Tried both adb devices and fastboot devices neither showed a device). Never have I seen this before and if I can get it working hopefully I will never see it again. Hopefully XDA's member's genius can make up for my stupidity. (most likely my fault being too hasty and skipping a step :silly.
Any questions about what I did or how I did it. Please ask!
Hey bud,
sorry about your troubles. I myself have just updated to ruu 3.18 and hboot 2.14 in order to flash the xylon rom. I'm not an expert at this: I'm just another person trying to get the best (vanilla) experience from his phone! Here's a couple things I noticed in my 9 hour trial & tribulation in going from 3.17 ruu + 1.09 hboot to the latest updates:
my pc also did not read my phone on a couple of occasions. Some parts of the process, I believe you have to be on your regular screen and the phone will reset into fastboot on its own. Later on, I had relocked my bootloader before I was supposed to, and was unable to write much. I just went back to step 1 and re-did everything (had to dig up a thread on unlocking my bootloader via htcdev).
my best friend helping through this was the hold power + vol down button. i kept going to stock recovery & rebooting my phone OR into fastboot and see which place I was supposed to be at.
as for your LCD being completely dead...I haven't come across that issue. The closest thing was when I was in RUU mode and there was only an HTC logo on the screen.
if you'd like, pm me and I can msg you the xda threads I used to get through it. I'm not sure how to approach the dead LCD, but I hope it all pans out for you.
I just wanted to share my experience, as a non-dev nor extremely savvy techie, I feel your pain brother.
Its not that the lcd is dead (unless it died after the ruu flash finished along with the notification led), more like it just wont turn on, along with the notification led, Where it would usually be on when plugged in, it just no longer turns on. Anyway thanks for your sympathy, I managed to jam the nano sim into my HTC arias micro sim slot without an adaptor (cyanogenmod 7 is its latest), so yeah at least I have a phone for the time being XD.
You flashed 3.18 with supercid and s-on. If you have supercid you need s-off before ruu to 3.18.
Sent from my HTC One XL using xda app-developers app
In other words, if you RUU'd with SuperCID and s-on, you're probably bricked.
Sent from my Evita
So far, from what you guys have posted, i'm out of luck on fixing the brick by myself. I do not know if either of these are an option so, again, fix my stupidity. First, I found a hard brick repair (mobiletechvideos, can't post link yet :/) which I have seen mentioned on the website a few times so I want to know if it can fix my brick and if the repair is worth trying. Second, is replacement from at&t/ HTC an option? Of course if anyone wants to comment a fix on my first post please do .
Starfrog6 said:
So far, from what you guys have posted, i'm out of luck on fixing the brick by myself. I do not know if either of these are an option so, again, fix my stupidity. First, I found a hard brick repair (mobiletechvideos, can't post link yet :/) which I have seen mentioned on the website a few times so I want to know if it can fix my brick and if the repair is worth trying. Second, is replacement from at&t/ HTC an option? Of course if anyone wants to comment a fix on my first post please do .
Click to expand...
Click to collapse
Jtagg is probably the best option, if you're within a year you can try sending it to HTC, if they figure out how you bricked, which is possible, they will charge you ~$200USD to replace the board.
Good luck.
If you ran the RUU with SuperCID and S-on, its bricked. JTAG is likely your only option to get the phone running again. You can look into the unbricking thread in General, and the JET tool in Development. But to my knowledge, nobody has been able to unbrick from this condition (SuperCID + S-on + RUU or OTA), short of JTAG. Yes, Mobiletechvideos has been mentioned on here as on JTAG option. Can't vouch for them personally, but others on here might be able to.
If you phone is less than a year old, you can likely get a warranty replacement from AT&T. Ethically, its a bit of a gray area IMO. I'm usually not crazy about people making warranty claims for failure to read, and as a result of you having modded the phone (which SuperCID is). But in reality, it shouldn't typically be expected for RUU plus SuperCID to brick the phone (past RUUs have run fine with SuperCID).
HTC is typically less forgiving about warranty issues. So no reason to try with them over AT&T. AT&T will pretty much honor the warranty for anything but obvious physical damage. They don't care if the phone has been modded, or bootloader unlocked (not that they would even be able to tell in your phone's current condition).
http://forum.xda-developers.com/showthread.php?t=2181929
I was bricked too.
I tried to relocking my bootloader and flashing the offficial jellybean without doing S-OFF first and bricked mine. I tried everything here at XDA with no luck. I gave up and sent it back to HTC and they had it back to me running the official jellybean update in 2 weeks. and without any charge. I even got it back on my birthday. It is running smooth and fast with no lag at all.
HTC One X+ AT&T Version
Hello there,
I tried updating my phone from Android Version 4.1.1 to the latest Android 4.2.2
But after installing my phone has stuck in the HTC logo and its bricked.
Please advice me for further proceedings.
My phone details :
Updated ROM image from 1.15.502.1 to 2.15.502.1
***RELOCKED***
EVITARE_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.73.0000
CPLD-None
RADIO-SSD:2.21.5517.15
eMMC-bootmode: disabled
CPU-BOOTMODE: disabled
HW Secure boot: enabled
MODEM TYPE: MDM9215M
Sep 30 2013,17:16:15
I have installed the RUU file which you have shared in the link above.
Please help me I need my phone in the working condition.
You're in the wrong forum. This is the HTC One XL forum, you want the HTC One X+ forum.
But, have you actually attempted to run an RUU from this section? Any RUU you find in this section is not for your device.
Sent from my Evita

[Q] [ Help! ] One S - soft bricked, S-ON, can't manage to get S-OFF, wont load ROM

Hello guys, this is the 5th day since im messing my mind on this particular device, im out of ideas now, and thats why im creating this thread hoping someone will solve this puzzle out.
I was reading a lot of tutorials, tryed many diffrend ways to get S-off, or trying to get back to stock..
GOAL: make this One S work, being rooted and have s-off, and have custom rom with sense 5 on it.
Story: i bought this HTC ONE S as a used device on cheap price, it was looking terrible, damaged case, cracked glass, outdated rom.
but i got idea i have to buy this one, because i think HTC ONE S IS MOST PRETTY DEVICE I HAVE SEEN , i will do restoration and make this baby beautiful as new! I polished glass, put glass protection on, repainted whole case with new white car paint. (it was black color version) now i have beautiful WHITE edition of HTC ONE S. its not for resell or anything, just personal use. ( i will do photos later on, when i will finish this project).
I noticed this phone have custom rom on it, but it was kinda buggy and slow, and outdated, it was some modded ICS rom. i was thinking like: no problem, i just read some tutorials here and flash new fancy rom, it will take just a hour or so at most,
i though this will be easy cake... since i have samsung galaxy s3 and i flashed it many times without problems.
ohhh how wrong i was... i almost bricked this phone...
THE STAGE THIS PHONE IS NOW AT:
ITS AN S4 DEVICE,
it can boot in to HBOOT with no problems and it can be controlled from windows 7 with fastboot commands.
TAMPERED
UNLOCKED
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.12.50.05.05
OpenDSP-v31.1.0.45.0815
eMMC-boot
(date and clock)
Recovery also works
TWRP v2.6.3.0
it have sweet feature to mount internal sdcard as usb flash for windows, also file browser and so on.. really like this recovery.
last installed rom: cm-10-2.0.-ville.zip
(but it wont load of course)
but after it hangs on HTC logo, red lines about developer rom, ADB DEVICES command shows this device serial number and phone listens to ADB commands with windows cmd from SDK platform tools.
This device original CID was: ORANG001
i was trying to get supercid, and somehow i managed to make it 11111111, but i cant managed to install any original RUU, so later i tryed to change cid to O2___001, and install O2 RUU, but it still wont install.
now i cant change CID to 11111111, just wont work, i have no idea how i changed in first place. but i edited hex and now i cant push this file with supercid againt to phone, gives error. also fastboot write cid wont work to, ends up in error and flastboot frozes, need to reset by holding power key.
so now im stuck with CID: O2___001
soo... can somebody give me some instructions how to get out of this crazyness and make this sweet phone work again by having Maximus HD on it? thank you
Saiyaru said:
Hello guys, this is the 5th day since im messing my mind on this particular device, im out of ideas now, and thats why im creating this thread hoping someone will solve this puzzle out.
I was reading a lot of tutorials, tryed many diffrend ways to get S-off, or trying to get back to stock..
GOAL: make this One S work, being rooted and have s-off, and have custom rom with sense 5 on it.
Story: i bought this HTC ONE S as a used device on cheap price, it was looking terrible, damaged case, cracked glass, outdated rom.
but i got idea i have to buy this one, because i think HTC ONE S IS MOST PRETTY DEVICE I HAVE SEEN , i will do restoration and make this baby beautiful as new! I polished glass, put glass protection on, repainted whole case with new white car paint. (it was black color version) now i have beautiful WHITE edition of HTC ONE S. its not for resell or anything, just personal use. ( i will do photos later on, when i will finish this project).
I noticed this phone have custom rom on it, but it was kinda buggy and slow, and outdated, it was some modded ICS rom. i was thinking like: no problem, i just read some tutorials here and flash new fancy rom, it will take just a hour or so at most,
i though this will be easy cake... since i have samsung galaxy s3 and i flashed it many times without problems.
ohhh how wrong i was... i almost bricked this phone...
THE STAGE THIS PHONE IS NOW AT:
ITS AN S4 DEVICE,
it can boot in to HBOOT with no problems and it can be controlled from windows 7 with fastboot commands.
TAMPERED
UNLOCKED
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.12.50.05.05
OpenDSP-v31.1.0.45.0815
eMMC-boot
(date and clock)
Recovery also works
TWRP v2.6.3.0
it have sweet feature to mount internal sdcard as usb flash for windows, also file browser and so on.. really like this recovery.
last installed rom: cm-10-2.0.-ville.zip
(but it wont load of course)
but after it hangs on HTC logo, red lines about developer rom, ADB DEVICES command shows this device serial number and phone listens to ADB commands with windows cmd from SDK platform tools.
This device original CID was: ORANG001
i was trying to get supercid, and somehow i managed to make it 11111111, but i cant managed to install any original RUU, so later i tryed to change cid to O2___001, and install O2 RUU, but it still wont install.
now i cant change CID to 11111111, just wont work, i have no idea how i changed in first place. but i edited hex and now i cant push this file with supercid againt to phone, gives error. also fastboot write cid wont work to, ends up in error and flastboot frozes, need to reset by holding power key.
so now im stuck with CID: O2___001
i would like to get step instructions what i should try do now, like guiding me trough steps on actions, and i will report how phone responds, and making this phone alive again ?
Click to expand...
Click to collapse
Saiyaru said:
Hello guys, this is the 5th day since im messing my mind on this particular device, im out of ideas now, and thats why im creating this thread hoping someone will solve this puzzle out.
I was reading a lot of tutorials, tryed many diffrend ways to get S-off, or trying to get back to stock..
GOAL: make this One S work, being rooted and have s-off, and have custom rom with sense 5 on it.
Story: i bought this HTC ONE S as a used device on cheap price, it was looking terrible, damaged case, cracked glass, outdated rom.
but i got idea i have to buy this one, because i think HTC ONE S IS MOST PRETTY DEVICE I HAVE SEEN , i will do restoration and make this baby beautiful as new! I polished glass, put glass protection on, repainted whole case with new white car paint. (it was black color version) now i have beautiful WHITE edition of HTC ONE S. its not for resell or anything, just personal use. ( i will do photos later on, when i will finish this project).
I noticed this phone have custom rom on it, but it was kinda buggy and slow, and outdated, it was some modded ICS rom. i was thinking like: no problem, i just read some tutorials here and flash new fancy rom, it will take just a hour or so at most,
i though this will be easy cake... since i have samsung galaxy s3 and i flashed it many times without problems.
ohhh how wrong i was... i almost bricked this phone...
THE STAGE THIS PHONE IS NOW AT:
ITS AN S4 DEVICE,
it can boot in to HBOOT with no problems and it can be controlled from windows 7 with fastboot commands.
TAMPERED
UNLOCKED
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.12.50.05.05
OpenDSP-v31.1.0.45.0815
eMMC-boot
(date and clock)
Recovery also works
TWRP v2.6.3.0
it have sweet feature to mount internal sdcard as usb flash for windows, also file browser and so on.. really like this recovery.
last installed rom: cm-10-2.0.-ville.zip
(but it wont load of course)
but after it hangs on HTC logo, red lines about developer rom, ADB DEVICES command shows this device serial number and phone listens to ADB commands with windows cmd from SDK platform tools.
This device original CID was: ORANG001
i was trying to get supercid, and somehow i managed to make it 11111111, but i cant managed to install any original RUU, so later i tryed to change cid to O2___001, and install O2 RUU, but it still wont install.
now i cant change CID to 11111111, just wont work, i have no idea how i changed in first place. but i edited hex and now i cant push this file with supercid againt to phone, gives error. also fastboot write cid wont work to, ends up in error and flastboot frozes, need to reset by holding power key.
so now im stuck with CID: O2___001
soo... can somebody give me some instructions how to get out of this crazyness and make this sweet phone work again by having Maximus HD on it? thank you
Click to expand...
Click to collapse
Well lest start shall we...
First find stock or close to stock ROM like sourcE
Then find the tool rumrunner and s-off
once your s-off your going to flash the ROM first then update firmware in maximus But before that back up your SD your going to have to wipe it
Now if you get a bootloop your going to have to adb push the ROM to your phone I hope this helps you
Sent from my Nexus 7 using Xparent Red Tapatalk 2
Flashalot said:
Well lest start shall we...
First find stock or close to stock ROM like sourcE
Then find the tool rumrunner and s-off
once your s-off your going to flash the ROM first then update firmware in maximus But before that back up your SD your going to have to wipe it
Now if you get a bootloop your going to have to adb push the ROM to your phone I hope this helps you
Sent from my Nexus 7 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
ty for helping ;D
ok, i installed SourcE 1.4 zip trough recovery, and did cache, dalvic wipe, but after system reboot, i got boot loop. also ADB wont show device number, so its even less wants to boot as with Cyanogen mod roms. they also get boot loop but atleast ADB shows device number after sending command adb devices.
ok, i will simply try now do s-off like i would do by tutorial, and tell u where i get stuck.

HTC One boot loop, S-ON

Hi, I need help FAST!
I have an AT&T (sim unlocked - done so because I live in Europe, not US) HTC One.
So, a few days ago I was playing smart and decided to install custom ROM to my device.
I've done everything as said until the S-ON procces. I ran the Rumrunner but I obviously messed up something
without knowing so it was left S-ON. So I went on to the install of dustom ROM wich I did, but I 've got stuck in a boot loop and I could only enter my recovery and bootloader. And to make matters worse I somehow succeded to delete al my files from "sd card", HTC One doesn't have SD card slot, as you know, (it has internal storage) so I deleted all my personal files ( I backed up photos, and other personal stuff to my PC in case something like this happens )
and my SuperSU and custom ROM zip files. Then I found out about flashing stock ROM, so I relocked my device to do so but the proper RUU has prooved very hard to find, I 've tried 4-5 RUUs from htc1guru.com for Cingular (AT&T) bot none worked. Maybe I should look for SIM unlocked RUU because I 've SIM unlocked it from AT&T. Now I am really annoyed and angry because of being so stupid and trying something I obviously couldn't achieve so please don't write down trere " Oh you are a noob for doing that " because I know that and I don't need any extra comments for playing smart and bricking my device. SO PLEASE IF ANYONE ON THIS FORUM CAN HELP ME, DO SO!! If i don't manage to finally fix this somehow I'm going to pay someone to fix this.
Torcidas1950 said:
Hi, I need help FAST!
I have an AT&T (sim unlocked - done so because I live in Europe, not US) HTC One.
So, a few days ago I was playing smart and decided to install custom ROM to my device.
I've done everything as said until the S-ON procces. I ran the Rumrunner but I obviously messed up something
without knowing so it was left S-ON. So I went on to the install of dustom ROM wich I did, but I 've got stuck in a boot loop and I could only enter my recovery and bootloader. And to make matters worse I somehow succeded to delete al my files from "sd card", HTC One doesn't have SD card slot, as you know, (it has internal storage) so I deleted all my personal files ( I backed up photos, and other personal stuff to my PC in case something like this happens )
and my SuperSU and custom ROM zip files. Then I found out about flashing stock ROM, so I relocked my device to do so but the proper RUU has prooved very hard to find, I 've tried 4-5 RUUs from htc1guru.com for Cingular (AT&T) bot none worked. Maybe I should look for SIM unlocked RUU because I 've SIM unlocked it from AT&T. Now I am really annoyed and angry because of being so stupid and trying something I obviously couldn't achieve so please don't write down trere " Oh you are a noob for doing that " because I know that and I don't need any extra comments for playing smart and bricking my device. SO PLEASE IF ANYONE ON THIS FORUM CAN HELP ME, DO SO!! If i don't manage to finally fix this somehow I'm going to pay someone to fix this.
Click to expand...
Click to collapse
What is your phone's image version?
---------- Post added at 04:28 PM ---------- Previous post was at 04:18 PM ----------
Torcidas1950 said:
Hi, I need help FAST!
I have an AT&T (sim unlocked - done so because I live in Europe, not US) HTC One.
So, a few days ago I was playing smart and decided to install custom ROM to my device.
I've done everything as said until the S-ON procces. I ran the Rumrunner but I obviously messed up something
without knowing so it was left S-ON. So I went on to the install of dustom ROM wich I did, but I 've got stuck in a boot loop and I could only enter my recovery and bootloader. And to make matters worse I somehow succeded to delete al my files from "sd card", HTC One doesn't have SD card slot, as you know, (it has internal storage) so I deleted all my personal files ( I backed up photos, and other personal stuff to my PC in case something like this happens )
and my SuperSU and custom ROM zip files. Then I found out about flashing stock ROM, so I relocked my device to do so but the proper RUU has prooved very hard to find, I 've tried 4-5 RUUs from htc1guru.com for Cingular (AT&T) bot none worked. Maybe I should look for SIM unlocked RUU because I 've SIM unlocked it from AT&T. Now I am really annoyed and angry because of being so stupid and trying something I obviously couldn't achieve so please don't write down trere " Oh you are a noob for doing that " because I know that and I don't need any extra comments for playing smart and bricking my device. SO PLEASE IF ANYONE ON THIS FORUM CAN HELP ME, DO SO!! If i don't manage to finally fix this somehow I'm going to pay someone to fix this.
Click to expand...
Click to collapse
Also, see if this All-in-One Toolkit that @hasoon2000 has developed helps you. It could help you get S-Off from the bootloader or recovery or help you find the proper RUU image version of your HTC One:
http://forum.xda-developers.com/showthread.php?t=2183942
Also, can you get into recovery? Like TWRP or Clockwork? Have you tried installing a rom.zip image version for your phone instead? I understand the HTC One M7 doesn't have an external SD slot, so chances are that you don't already have a rom.zip file in your phones directory but you could always sideload one through TWRP or Clockwork from ADB on your computer.
I would search the forums for an HTC One M7 rom.zip image and sideload it.
T-Mobile HTC ONE M7 bricked?
So I did something pretty dumb yesterday. Installed the HTC Sense 6 update on my HTC ONE M7, hated it so decided to root my phone to revert back to Sense 5.0 or 5.5 or potentially try a custom ROM. Downloaded a Tmobile 4.3 JB RUU, downloaded android SDK, HTC sync manager, Fastboot. I unlocked boot loader, installed Wheaton recovery by Koush, installed SU, figured phone was rooted but it wasn't. Now I've somehow succeeded in deleting EVERYTHING. Phone continues booting into recovery. Commands using Fastboot aren't recognized because it cannot find any device. When plugged in via USB, PC recognizes that something is plugged in but that's about it. I tried using a tool that was guaranteed to help me revert back by helping me re-lock bootloader but of-course that didn't work because of the error code stating "device not found". Below are the information that is currently displaying on my screen.
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
Open DSP-v32.120.274.0909
OS-5.14.531.1
eMMC-boot 2048MB
May 9 2014, 15:00:26.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Any help will be greatly appreciated

Categories

Resources