Hi,
My original Sensation started dieing (backlight issues I think). I successfully returned it to standard with S-ON prior to returning it to Vodafone.
Today the replacement turned up, so S-OFF is the first step ) So a few checks first and......
Anyway, "adb devices" seems not to be able to see the new phone.
i) USB Debugging enabled on the phone;
ii) PC sees it perfectly as a storage device;
iii) "adb devices" sees my Desire perfectly;
iv) Yesterday on the same PC I installed RUU on the old Sensation, then reset CID then finally changed it back to S-ON, the final two rely on adb/fastboot connectivity.
So with the above in mind I believe ADB is installed correctly on the PC.
Anyone have any thoughts what I've missed (screwed up) or why the replacement Sensation is invisible to the PC via ADB ?
gol_n_dal said:
Hi,
My original Sensation started dieing (backlight issues I think). I successfully returned it to standard with S-ON prior to returning it to Vodafone.
Today the replacement turned up, so S-OFF is the first step ) So a few checks first and......
Anyway, "adb devices" seems not to be able to see the new phone.
i) USB Debugging enabled on the phone;
ii) PC sees it perfectly as a storage device;
iii) "adb devices" sees my Desire perfectly;
iv) Yesterday on the same PC I installed RUU on the old Sensation, then reset CID then finally changed it back to S-ON, the final two rely on adb/fastboot connectivity.
So with the above in mind I believe ADB is installed correctly on the PC.
Anyone have any thoughts what I've missed (screwed up) or why the replacement Sensation is invisible to the PC via ADB ?
Click to expand...
Click to collapse
Hi,
Might be worth trying to re-install the HTC DRIVERS
Thanks,
I'd already started downloading the latest version of HTC Sync for its drivers.
Weird though how the old one worked fine and this is invisible.
I'll update if it works.
EDIT: Meant to add that I noticed the Desire was recognised in Hardware/Devices, however, the Sensation wasn't.
How about fastboot?
Did you try fastboot devices
With phone connected to pc from bootloader? (phone should read fastboot usb after this)
Sent from my pyramid.. Through blazing fast sonic waves
Turns out the replacement phone was goosed before I had a chance to screw it up myself
Never appeared in Hardware/Devices properly, HTC Sync didn't work, Vodafone asked me to install latest OTA. Then I discovered WiFi was also screwed, the WiFi icon never turned up in the notification bar...
So, Replacement for the Replacement is on its way.
Thanks folks.
Replacement , replacement phone turned up today and it worked perfectly first time with both ADB and WiFi.
The only slight down side is that it's running 3.32.161.11 so HBOOT 1.27.0000. The first replacement was 1.17.0006 (so easy revolutionary S-OFF). 1.27.0000 seems a little more hassle and looks like I need to go via http://htcdev.com/bootloader to start with, I'd hoped to avoid that. At least this phone is working properly.
Thanks for the suggestions folks, all my issues came down to a broken replacement phone
Colin
P.S.
Talk about consistency, the first replacement turned up with no back and an 8GB uSD card. The latest one came with a back and no uSD card
gol_n_dal said:
1.27.0000 seems a little more hassle and looks like I need to go via http://htcdev.com/bootloader to start with, I'd hoped to avoid that. QUOTE]
Before you go doing that, the HTC unlock method can create other roadblocks for you down the road. Make sure to read up on it first.
I never had to root the 1.27 version so I'm not intimately familiar with the problems the HTC method causes, but I'm constantly seeing issues about things that work quirky later because of it, or other workarounds you need to do to to overcome the HTC unlock.
The short circuit thing is goofy, but it supposedly works well and gives you a truely unlocked bootloader.
Click to expand...
Click to collapse
gol_n_dal said:
Replacement , replacement phone turned up today and it worked perfectly first time with both ADB and WiFi.
The only slight down side is that it's running 3.32.161.11 so HBOOT 1.27.0000. The first replacement was 1.17.0006 (so easy revolutionary S-OFF). 1.27.0000 seems a little more hassle and looks like I need to go via http://htcdev.com/bootloader to start with, I'd hoped to avoid that. At least this phone is working properly.
Thanks for the suggestions folks, all my issues came down to a broken replacement phone
Colin
P.S.
Talk about consistency, the first replacement turned up with no back and an 8GB uSD card. The latest one came with a back and no uSD card
Click to expand...
Click to collapse
you can use my soff guide ( link in my signature ) and avoid htc-dev unlock ..but remember wire trick my way is bit difficult
Thanks,
I found a coltrolbear/JuopunutBear guide, so all sorted now: S-OFF, rooted, custom recovery and SuperCID. The only issue was the timing with the paper clip, it took a few attempts. Still a lot more hassle than just using revolutionary.io....
Just need to have a look around now at the latest ROMs. I see there is a Jelly Bean one floating around.
Related
Hi all again, another noobish question
i am facing some Wi-Fi issues (wifi dont turn on..i tried new roms, kernels, stock ones either, wiping etc...), so i decided go back to stock and i mean STOCK with S-ON, unroot, stock radio, stock hboot etc. > also because of warranty, coz new motherboard cost almost like whole new phone, and thats not acceptable for me but i want restore all the goodies, when phone returns from service!!! (ViperS 1.2.0 is so fraggin awesome!)
So my question is: Can somebody post some tutorial or help me with this? my laptop i so slow right now, word i write appears about 15 seconds later, so i can´t search
Thans in advance!!
Lord5619
http://forum.xda-developers.com/showthread.php?t=1672425
Sent from my HTC Sensation 4G using xda app-developers app
Do a nandroid backup of your current ROM.
Change CID to the one you're meant to have. You'll need to boot into fastboot mode and run the command "fastboot oem writecid xxx" where xxx is your correct cid.
Run the correct RUU for your phone to install the stock ROM. You'll need to run it from a windows PC with the HTC drivers installed but without HTC sync. If it won't work, put the phone into bootloader mode and try it again.
Once the RUU has successfully flashed, boot into fastboot mode and issue the command "fastboot oem writesecureflag 3" to return to S-on. Make sure that step is done last else you'll end up with a brick.
I recently did the above for a friend's phone to return for warranty repair. It was successful
So i flashed complete RUU ICS, get S-ON...and the wi-fi still doesn't work, I tried it for maybe half an hour...So i leaved it on the table and went play with my little son for an hour or so. Than a returned to my damn phone and wi-fi actually works!!! Quite strange, but great
Thx for help guys!
Hey!
About a week ago, after rebooting my device, the softkeys at the bottom of my screen stopped working as they´re supposed to do. When i tried to press a button, nothing happened. However, if i would press slightly above the actual button it worked fine.
But now (after flashing other roms in order to fix it), even that wont work anymore. In addition, when in Recovery(TWRP), a line of about half a centimeter at the bottom of the screen above the Softkeys is unresponsive too, preventing me from navigating back etc.
Don´t know if thats a possible cause but this happened some days after I installed a Rom with Sweep2wake for the first time. Worked fine until the problem appeared.
Things I tried yet: Flashing several different Roms(Cm9,Cm10,IceColdSandwich,FalloutEvolution,Andromadus), Factory Reset, Calibration (didn´t expect it to work but worth a try ^^),Using the Search-Function.
Specs: Unlocked SAGA PVT Ship S-ON Rl
Hboot 2.00.0002
Rom i used when the Problem appeared is Cm10.
If any additional Informations(Logcats,whatever) are required, just ask.
Help of any kind would be really appreciated!
Thank you very much and have a nice Weekend.
As long as you are S-On, you should maybe send it back to HTC if you have the warranty, since it is more of a hardware problem than a software problem (maybe the sensors are not in the right place). But before you do that you should change the hboot version to 0.98, since they can see that you unlocked your bootloader and the warranty would be gone. And you also should backup your data, so that you have a fallback positon,
Thanks for your reply!
I forgot to mention that I unlocked it via htc-dev. I didnt change the Hboot-Version, so why would you advise me to change Hboot?
PS.: Ordered at amazon,so thats where i would send it back to.
The reason you should downgrade hboot version is that they can't see if you unlocked it via htcdev or not. Normally if you would unlock it via htcdev you can see that the bootloader is unlocked and there is no way to put it into previous state (you can only put it into relock, but your warranty would be still gone). So I advise you to downgrade the hboot version to 0.98.00000 and flash a stock Rom, since HTC only accept stock Roms, S-On and locked bootloader.
P.S: You instantly get locked bootloader as soon as you downgrade and lose your S-off, just follow the steps in the Android Development section carefully
P.P.S: Does anyone know where the Desire S gets repaired when you send it back to Amazon?
Sent from my HTC Desire S using xda app-developers app
Is it actually possible that this has something to do with Sweep2wake? Just wondering, because this problem appeared while using a ROM with Sweep2wake for the first time.
EDIT:
I just activated visual touch feedback to see what happens when i touch the softkeys or the screen at the bottom 0,5 cm. The "visual touch response point" always appears centered at the top of the area not working. I made a picture with my old e71, very sorry for the horrible quality and my mad Paintskills . Pink arrows leads to the visual touchfeedbacl, green one to where i actually touched the screen.
EDIT2: Forgot, the picture, but im actually not able to post the link due to my low post count..
Isn´t that a sign that it is not hardware related?
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
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.
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