Database Info

Verifying my Glacier is Bricked

I have followed all of the procedures to reload my phone stuch on the splash screen, but have had no luck. Before I dispose of the phone, as it is in mint condition, I want to be sure there is no other options to update / reformat the bootloader
1. I have loaded the image for 2.2.1 AND 2.3.4 MULTIPLE TIMES
2. I have cleared the Cache's and no change
3. status on bootloader shows
GLACIAER PVT SHIP S-ON
HBOOT-09.0006
MICROP-0429
RADIO-26.13.04.19_M
eMMC-BOOT
Jul 15 2011, 16:45:17
I guess the last hope since th reloading the original images did not work is to reload / format the bootloader using ADB, but I believe that I have the wrong HBoot.
Is the phone eMMC bad and the phone bricked or is there something else to try?

johnmbailey said:
I have followed all of the procedures to reload my phone stuch on the splash screen, but have had no luck. Before I dispose of the phone, as it is in mint condition, I want to be sure there is no other options to update / reformat the bootloader
1. I have loaded the image for 2.2.1 AND 2.3.4 MULTIPLE TIMES
2. I have cleared the Cache's and no change
3. status on bootloader shows
GLACIAER PVT SHIP S-ON
HBOOT-09.0006
MICROP-0429
RADIO-26.13.04.19_M
eMMC-BOOT
Jul 15 2011, 16:45:17
I guess the last hope since th reloading the original images did not work is to reload / format the bootloader using ADB, but I believe that I have the wrong HBoot.
Is the phone eMMC bad and the phone bricked or is there something else to try?
Click to expand...
Click to collapse
When you try to flash PDwhatever.IMG, what does it tell you?

Glacier locked at Mytouch logo, without image load errors
THEindian said:
When you try to flash PDwhatever.IMG, what does it tell you?
Click to expand...
Click to collapse
It does not give any errors after flashing to 2.3.4, as it loads, verifies, then asks to load. It then successfully loads all pieces of the image, only to reboot to the same Mytouch logo screen.
When I use recovery, it can't mount anything, and when I wipe the Cache, it give arror that Ext3 is not compatible.
I reboot and factory restore in recovery, and gives the Ext3 compatibility message and can't mount anything.
I never receive any image loading errors, but I cannot load the 2.2.1 image, as it never give me a chance to say 'yes' to loading it.

If it doesn't work, care to sell it? I need a back and home button for mine lol
I also think my volume buttons will be gone soon, their starting to stick
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium

siloner said:
If it doesn't work, care to sell it? I need a back and home button for mine lol
I also think my volume buttons will be gone soon, their starting to stick
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
Click to expand...
Click to collapse
The phone is in Mint Condition, so I hoped to resurrect it if at all possible, but if it is not possible I definitely will be selling it whole or in part.

johnmbailey said:
It does not give any errors after flashing to 2.3.4, as it loads, verifies, then asks to load. It then successfully loads all pieces of the image, only to reboot to the same Mytouch logo screen.
When I use recovery, it can't mount anything, and when I wipe the Cache, it give arror that Ext3 is not compatible.
I reboot and factory restore in recovery, and gives the Ext3 compatibility message and can't mount anything.
I never receive any image loading errors, but I cannot load the 2.2.1 image, as it never give me a chance to say 'yes' to loading it.
Click to expand...
Click to collapse
Thats really weird because usually if the emmc is dead, the image doesn't load completely in the bootloader. Have you tried calling tmo and telling them about your predicament? I know you are over warrenty but they might still help.

Glacier Stuck on Splash, now on StraightTalk service
THEindian said:
Thats really weird because usually if the emmc is dead, the image doesn't load completely in the bootloader. Have you tried calling tmo and telling them about your predicament? I know you are over warrenty but they might still help.
Click to expand...
Click to collapse
I am now on Straight Talk, so I no longer have a TMobile account to call about. My PAygo ended on Sunday with them.
Can I load anything from ADB with this version of the HBoot / Bootloader? Does the Ext3 mean it had a newer Rom, so I need to change to a supported type using ADB? IT almost looked like the Ext3 format was causing the problem. This also might be a red flag to support if it was not on a factory format. I inherited the phone, so I do not know the history.
Since it never finished booting, is there any way to use the original HTC.exe programs that install the RUU image?

Why are you s-on? Shouldn't you be s-off if you want to install a rom??
Have you tried rooting method again? As far as i know using the gfree method should not give you this issue,
Sent from my Arrows Z using xda app-developers app

Mytouuch 4g - stuck at splash screee
I bought phone from CL. As I suspected previous owner tried to mod the phone. It loads to splash screen. I can get into bootloader but can not select RECOVERY or FACTORY RESET. I tried the PD15IMG.ZIP but when i extracted hboot is 0.89 (and the following happens):
***LOCKED***
GLACIER PVT SHIP S-ON
HBOOT-0.90.0000
MICROP-0429
RADIO-26.13.04.19_M
eMMC-boot
PD15DIAG.ZIP
no image
PD15DIAG.nbh
no image
Main Version is older!
Update Fail!
Press<power> to reboot
I think i need the IMG that pertains to the HBOOT.
HELP PLEASE
Thank you all

Glacier is Stuch at Splash, so what are options after reloading img?
NeuroticallyYou said:
Why are you s-on? Shouldn't you be s-off if you want to install a rom??
Have you tried rooting method again? As far as i know using the gfree method should not give you this issue,
Sent from my Arrows Z using xda app-developers app
Click to expand...
Click to collapse
The phone is stuck at the splash, so what options do I have that load from SD or USB at the 'Stuck' splash or 'Bootloader'? Can I use the HTC EXE programs to reload the phone or do they require a 'fully booted' phone? Is there any way to load the engineered hboot / bootloader so that I can have ADB options?

johnmbailey said:
The phone is stuck at the splash, so what options do I have that load from SD or USB at the 'Stuck' splash or 'Bootloader'? Can I use the HTC EXE programs to reload the phone or do they require a 'fully booted' phone? Is there any way to load the engineered hboot / bootloader so that I can have ADB options?
Click to expand...
Click to collapse
ok let's calm down and not panic, something similar happened to me when i started rooting my first MT4G, did you try to root the phone? if not i will suggest you to do that with the cyanogenmod guide HERE but before you follow the guide try to boot into bootloader by shutting the phone down, leave it off for like 10 seconds then turn it on by pressing the power button+volume down key, you will enter into bootloader usually you will see 3 androis at the bottom of the screen on skateboards if you don't see that but instead the phone keeps booting into splash screen then try again until you enter bootloader, wihle in bootloader you need to tell me what options you get and what options are enabled, since you can't mount the SD card you will have to get an adapter to download all software needed on the SD card(remember you have to remove the sd card from the phone since you can't mount it). Proceed with the guide until you install a custom rom like CyanogenMod 7.
this type of errors can be reproduced easily for example on a rooted phone wipe the phone completely and reboot, the phone will do exactly the same your phone is doing another thing is i don't know what is this HTC.exe program you are talking about everything is done with the android SDK so before doing everything in the guide you need to download and isntall the android SDK.
it seems like the previous person tried to root but instead messed up the phone system, probably corrupted? like i said i have reproduced the same behaviour on my MT4G many times and by now i don't freak out like it was the first time, the thing that have saved me is the rooting guide, i know by experience that you CAN'T install a rom or anything if you are S-ON.

Bootloader options on Glacier Stuck at bootloader
NeuroticallyYou said:
ok let's calm down and not panic, something similar happened to me when i started rooting my first MT4G, did you try to root the phone? if not i will suggest you to do that with the cyanogenmod guide HERE but before you follow the guide try to boot into bootloader by shutting the phone down, leave it off for like 10 seconds then turn it on by pressing the power button+volume down key, you will enter into bootloader usually you will see 3 androis at the bottom of the screen on skateboards if you don't see that but instead the phone keeps booting into splash screen then try again until you enter bootloader, wihle in bootloader you need to tell me what options you get and what options are enabled, since you can't mount the SD card you will have to get an adapter to download all software needed on the SD card(remember you have to remove the sd card from the phone since you can't mount it). Proceed with the guide until you install a custom rom like CyanogenMod 7.
this type of errors can be reproduced easily for example on a rooted phone wipe the phone completely and reboot, the phone will do exactly the same your phone is doing another thing is i don't know what is this HTC.exe program you are talking about everything is done with the android SDK so before doing everything in the guide you need to download and isntall the android SDK.
it seems like the previous person tried to root but instead messed up the phone system, probably corrupted? like i said i have reproduced the same behaviour on my MT4G many times and by now i don't freak out like it was the first time, the thing that have saved me is the rooting guide, i know by experience that you CAN'T install a rom or anything if you are S-ON.
Click to expand...
Click to collapse
The 2.2.1 image does not load due to 'older version' error in the bootloader, so I renamed it so that it would stop at bootloader to test working options.
Glacier pvt ship s-on
HBOOT-0.89.0006
MICROCROP-0429
RADIO-26.13.04.19_M
cMMC-boot
Jul 15 2011, 16:45:17
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Fastboot of course works, as I am able to run the image load from SD card
REcovery works, but give the various mounting errors mentioned earlier
factory reset can be selected but does not change anything and it returns to the splash screen
I did not try simlock, as it looks irrelevant
image crc works and seems to check an image somewhere
When I select RECOVERY, Press UP Volume and Power to get past Triangle, it enters the recovery with all of the mount errors, and then the menu pops up
Androic System Recovery <3e>
Use volume .....
Select w Power....
Reboot System Now
Apply Update from SD card
Wipe data / Factory Reset
Wipe Cache Partition
Wiping DAta completes with Ext3 error, unable to mount anything, and unable to open errors, and returns to Recovery menu
Wiping Cache completes wipe with Ext3 error, unable to mount, unable to open and then reboots
Apply Update from SD Card also appears to fail
Rebooting by reason OEM
Cant mount
Count open
then it reboots
From what screens can you mount the 'drive' to use with ADB? When trying to run the ADB commands, I get the error device not found, so I either am not in the correct mode on the phone or I do not have the correct drivers. When coinnectd at the splash screen, my device manafer shows a Portable Device with Drive f:\ and the details show an Android Phone, but the drive is not visible or accessible by ADB.
When I start bootloader with Hboot at USB PLUG mode, the device manage on my computer changes to Android Bootloader device, but I still get 'Device Not Found' after executing the first ADB command. I then followed the info (I think) at http://forum.xda-developers.com/showthread.php?t=881324 with no success for ADB to work, so I something must be wrong.

It seems the S-ON option is not letting you go further, if it gave you a ext3 format error most likely is because the phone can't erase or rewrite the partition needed. Now I'm no expert on the hardware part but I put my small knowledge on that it have to do with the S-ON part of the phone.
Was the phone booting up properly before? If the phone can't boot to android then you can't use adb commands(for what I know) also the fact you don't have a custom recovery image will make it hard for you reinstall android.
I can probably make some time to help you but nothing is better than having the phone so I can troubleshoot. If you want we can chat on gmail to set up a remote session? Other than that I don't see how I can help you.
Sent from my Arrrows Z using xda app-developers app

FINAL Questions on Recovering Glacier MyTouch 4g stuck at Splash
NeuroticallyYou said:
It seems the S-ON option is not letting you go further, if it gave you a ext3 format error most likely is because the phone can't erase or rewrite the partition needed. Now I'm no expert on the hardware part but I put my small knowledge on that it have to do with the S-ON part of the phone.
Was the phone booting up properly before? If the phone can't boot to android then you can't use adb commands(for what I know) also the fact you don't have a custom recovery image will make it hard for you reinstall android.
I can probably make some time to help you but nothing is better than having the phone so I can troubleshoot. If you want we can chat on gmail to set up a remote session? Other than that I don't see how I can help you.
Sent from my Arrrows Z using xda app-developers app
Click to expand...
Click to collapse
Since the phone will not go pase the splash or bootloader / hboot.....
Questions:
1. Can the original manufacturer RUU - Rom Update Utility be downloaded somewhere and if so wouldn't it just need the phone in Bootloader mode?
2. For the ADB method, will it work with thge phone at the Bootloader screen, and if so what drivers arfe needed as the Android Bootloader ones do not work that are showing. Is these another setting beyond just the driver that needs to be set to use ADB?
3. Will a program like Odin that I used to recover my samsung image from bootloader work for these phones?
4. Does anyone have any ideas or should I just part out this Mint phone?
Please refer to previous posts for the details on what has already been tried....and what it is still doing.

johnmbailey said:
Since the phone will not go pase the splash or bootloader / hboot.....
Questions:
1. Can the original manufacturer RUU - Rom Update Utility be downloaded somewhere and if so wouldn't it just need the phone in Bootloader mode?
2. For the ADB method, will it work with thge phone at the Bootloader screen, and if so what drivers arfe needed as the Android Bootloader ones do not work that are showing. Is these another setting beyond just the driver that needs to be set to use ADB?
3. Will a program like Odin that I used to recover my samsung image from bootloader work for these phones?
4. Does anyone have any ideas or should I just part out this Mint phone?
Please refer to previous posts for the details on what has already been tried....and what it is still doing.
Click to expand...
Click to collapse
I don't know of an external app like odin that works for our phone. Also, there are no RUU's for the Glacier, only PD15IMG.zip files.

Since Mint MyTouch 4g Phone is Bricked, how much will work for Slide Version?
I saw an old post with a broken link for an RUU that was supposed to work on the Glacier called the panache. I finally found a working link and downloaded the RUU for Gingerbread, but when I ran it it gave and error that the battery was below 30%, even though fully charged and verified with my wall charger, and 2 usb chargers and 2 different batteries. I might try a powered USB hub, but this data on battery condition might have been stored on the phone somehow? If it could get the phone to work again, then a I could always reflash with a different ROM later.
If there is no hope of recovering this Mint MyTouch 4g Stuck on the splash screen, so can parts be used on the shift / slide version such as LCD / Digitizer, push buttons, or ????
It makes me sick to tear it apart.....

Any other thoughts?

Ran into similar problem
I ran into a similar problem with a message about the version number of the recovery image being wrong. This was a few weeks ago and I didn't keep a log of exactly how I fixed it but this is what I remember:
It turned out that during an attempt to root before I knew what I was doing I had changed the version number using the guide at the link below.
http://www.androidauthority.com/mytouch-4g-t-mobile-root-custom-recovery-74465/
That error message was misleading and the problem was instead due to the fact the phone was unlocked (although mine did say so on the bootloader screen.) HTC images have apparently been created to require a locked phone to successfully load. I relocked it in Fastboot USB mode with the command "fastboot oem relock" and was able to successfully load any version number after that.
Good luck.

Hello, have you tried using a different SD card?
Sent from my HTC Sensation 4G using xda app-developers app

[Q] One S Brick? HELP!

Novice here.
Ran the All-in-One utility today and after the CWM installed I hit "Perm root" without reading the thing below telling me to boot to recovery first. It's now stuck in boot loop. Everything went off fine up until the Perm root. Even that said successful and then restarted. Only after the process was completed did the recovery loop begin. No HTC logo loop. Just reboots into CWM over and over no matter what technique I use (except for opening the case).
I've read this: http://forum.xda-developers.com/showthread.php?t=1599363
And am trying to install ADB to push ANY possible ROM over to the SD card. My recovery allows the toggle of /mount sdcard and /mount system, however adb fastboot push doesn't work. "error: device not found"
And I can't do this: http://forum.xda-developers.com/showthread.php?t=1644730 because my phone is stuck in the recovery loop. If I try volume down + power, it just comes back to recovery screen. I've tried factory reset, I've tried wiping cache, I've tried wiping Dalvik, and still nothing. I did flash the SuperSu.zip after I had used the Perm Root button on Haroon2000's app.
I'm incredibly flustered as I've rooted devices for years and this is my first problem. I've seen similar complaints all with ideas of breaking into the phone and unplugging it's battery so I can get to the bootloader etc, but I'm so very confused. So many posts telling me to do so many things.
Can someone please help break down a tangible solution here? I'm freaking out.
Cheers
EDIT: If someone can get my phone fixed, I'll Paypal them $50 USD. I really need my phone back ASAP :\

I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium

beats4x said:
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.

nik.the said:
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
Click to expand...
Click to collapse
Okay, update.
I was able to get ADB working and detect my phone.
Next, I was able to push Venom Rom to phone. I factory reset, wiped cache, wiped Dalvik, and was able to install Venom.zip. It then asked to reboot (per Venom screen) and I said okay. It then returned to CWM Recovery. I was confused but left everything as is. I have now reset the phone by holding the power button for around 10 seconds. It then restarted to the HTC Quietly Brilliant screen. I have been looking at that screen for about 5 minutes.
Also pertinent: I did try to run the RUU, but it didn't connect through USB. (I forget what it said verbatim). So that didn't work. I also was able prior to this entire process get into the bootloader via dumb luck.
Any suggestions? I am staring at the HTC boot screen still. Do I try to restart and enter bootloader? If so, then what? It seems there is something wrong with CWM. Can I switch recoveries? Can I uninstall it?

Calm down we have all been there,
When you flashed venom did you flash the boot image? Also i use twrp instead of cwm i find twrp better .
To enter bootloader hold power button and down vol together .

As gazknight said, this seems like proper kernel not being flashed or having an issue. If you flashed the boot.img with fastboot, try again erasing cache from fastboot first. The commands are as follow:
fastboot erase cache
fastboot flash boot boot.img (where this boot.img is the one inside the zip from the rom you choose and must be left in the same folder than fastboot)
It happened to me a couple times when i was on hboot 1.14 that I had to flash the boot.img a second time sometimes, somehow it was not working the first time, randomly, even though the flash had completed ok on fastboot.
If still doesn't work try doing a factory reset from TWRP and flashing ViperOneS again.
If that still doesn't work, you might want to try another rom, like TrickDroid, you would then have to flash the boot.img from this other room with fastboot, remember that.
Try and let us know

Hold down volume down while you're trying to boot, that will get you in boot loader, go to fast boot by pressing the power key, connect your phone to your computer, run the flash viper boot img thingy and you're set!
Envoyé depuis mon HTC One S avec Tapatalk

Same issue with HTC One S bricked but in European version, Stock ROM
hello,
I did't want to start a new topic, as I'm experiencing a similar issue with my HOS. Briefly, yesterday morning I plug the phone from charger at 06.00 am. Play with it for a while and then go to work. Used it at work for a few phone calls until 10.00 am (so 4 hours on fully charge battery). Then at 10.00 am I went into a meeting and left the phone out of my sight for 20-30 minutes. When I came back from the meeting I realize that the phone was closed. I try to open it (power button) but nothing. Press power for 10-30 seconds with volume down - still no effect.
Then I took the charger (the original one that I always use to cherge it) and plug it, left it for 2-3 minutes and press power. The phone starts but all I have is the white screen with HTC logo and if I press the power button + volume down the phone goes into bootloader. That's all I can do with it for now.
I have stock rom, bootloader is locked and I never try to root the phone. Is it any chance to repair it by myself or I have to sent it to the repair shop.
many thanks in advance.

Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.

nik.the said:
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
Click to expand...
Click to collapse
You might need to do it as administrator.

I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).

nik.the said:
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
Click to expand...
Click to collapse
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.

Darknites said:
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Click to expand...
Click to collapse
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.

Yeah! Fixed!
After enough toggling, I changed the recovery to the T one and relocked my bootloader. It turns out detecting the device wasn't necessary somehow. Then I ran the RUU and voila!

nik.the said:
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Click to expand...
Click to collapse
Not sure whats up with that, never had any issue on win7.

Windows 8 fastboot works on my laptop for some reason. I installed the drivers from the HTC Sync folder.
Sent from my HTC One S using Tapatalk 2

[Q] So many issues....just so many!

So last night I tried to install CM11 and unfortunately forgot to make sure it was a clean install. Got stuck on boot animation and after remembering what I did wrong, tried to get back into recovery, however this is my first time trying to install CM on this device so was confused when the power button wasn't the "select" button to get me into recovery...so I ended up messing around for a bit and now I'm screwed.
My phone doesn't show up as a storage device on my computer and only recognises it as an "Android" device or "Fastboot Falcon S". I have tried reinstalling the Motorola drivers and I'm just at a loss. :crying:
I can access recovery on my phone but when I attempt to install a zip from sdcard it says "E: Can't mount /sdcard". Which means I can't install any Roms. I did some research and apparently I can push a stock rom to my phone, but this leads me to my next problem.
I can't seem to get adb to recognise my phone. I feel like I have tried everything but I have reached the extent of my knowledge on this matter and It's starting to hurt my brain. I saw mention of using "Eclipse" but when I try to run it I get an error message about Java.
Edit: When I say adb doesn't recognise my phone, it doesn't show up when I type the command "adb devices" and whenever I attempt an adb command such as "adb push" or "adb shell" I get an error message. I can however use all fastboot commands, which were a big help.
I honestly am completely and totally baffled on how to recover from this total f*ck up, so if any of you geniuses could help me save my device I would be forever grateful. I'm not sure what information I should supply you with as this is my first post. So please tell me what you need and I'll try me best to get you the info.
Thank you!

If you can boot into fastboot mode, just flash stock firmware of your region. There are many guides in the general and q/a sections. Just read them properly and remember to use mfastboot.
Sent from my Moto G using Tapatalk

You don't need adb, but mfastboot, which are two different things.
Let your brain rest few hours and then read the guides how to flash stock firmware.

You are fantastic. Thank you so much!
I can finally use it again.....and attempt to flash CM11 again, hopefully this time without screwing it up.
I owe you!

[Q] Locked Bootloader with TWRP, Won't unlock anymore

Ok, I'm an idiot. A big one.
I was looking to flash back to stock after using some lollipop roms. I was using TK's toolbox which was an extremely handy utility but in the peak of my madness, I hit lock bootloader with TWRP still installed.
Since hitting lock bootloader i'm not stuck with TWRP and it's crippled my phone since the current ROM no longer seems to be fully functional...I can't seem to download anything else from the web. Everything seems to fail.
I've tried fastboot oem unlock and it goes through the process that appears to be successful but it just boots back into TWRP and it's not unlocked. Does anyone have any suggestions or do I have a $300 paper weight. haha

Tonymhoffman said:
Ok, I'm an idiot. A big one.
I was looking to flash back to stock after using some lollipop roms. I was using TK's toolbox which was an extremely handy utility but in the peak of my madness, I hit lock bootloader with TWRP still installed.
Since hitting lock bootloader i'm not stuck with TWRP and it's crippled my phone since the current ROM no longer seems to be fully functional...I can't seem to download anything else from the web. Everything seems to fail.
I've tried fastboot oem unlock and it goes through the process that appears to be successful but it just boots back into TWRP and it's not unlocked. Does anyone have any suggestions or do I have a $300 paper weight. haha
Click to expand...
Click to collapse
Believe it or not, I have the same problem since yesterday. Its driving me mad since I'm no expert on rooting/unlocking
Phone gets detected by PC and by the toolbox but I can not unlock my phone again.
I am now stuck with TWRP and the only rom I can flash is Slimkat, all the others fail. If I hit unlock bootloader in the toolbox it goes through the process (fast) and it gives no error, boots back up to TWRP and thats it, but it is still locked
I just want it back locked and stocl CM11

Firstly, don't use toolkits. They are often the cause of issues.
Follow this thread to solve your problem: http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390

Fixed it!
Solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912

PewLaserBeam said:
Fixed it!
Solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Click to expand...
Click to collapse
Damn you're lucky!
I'm having more issues because my phone won't let me download anything. It's like there is no SD card detected. I can't get that file onto my phone to flash it. Any ideas how I can do it?
I have ADB enabled and it shows up in my devices but it won't respond to adb sideload oneplusone-bootunlocker.zip
It responds to fastboot commands.. it just won't let me download anything off the net onto the device. IT will however update phone apps.. It's so damn frustrating.

Tonymhoffman said:
Damn you're lucky!
I'm having more issues because my phone won't let me download anything. It's like there is no SD card detected. I can't get that file onto my phone to flash it. Any ideas how I can do it?
I have ADB enabled and it shows up in my devices but it won't respond to adb sideload oneplusone-bootunlocker.zip
It responds to fastboot commands.. it just won't let me download anything off the net onto the device. IT will however update phone apps.. It's so damn frustrating.
Click to expand...
Click to collapse
I had this yesterday + I kept getting the message 'No OS installed'. Since it was already half 'broken', out of frustration I clicked everything and used all sorts of commands I could find (not the best idea I know :angel untill my PC detected the internal memory and then I downloaded 6-7 roms just to be sure. Slimkat was the only one without a fail.

How did you get the files over to your phone then if it wouldn't let you send them to it?
I finally got my internal memory to show up by mounting the system in the TWRP recovery.. But still getting an error that the device stopped responding or is disconnected.. However, it will let me open and view any file on the system, it just won't let me write to it.

Adb sideload did the fix for me after a while.
But it looks loke you have another problem.

Tonymhoffman said:
How did you get the files over to your phone then if it wouldn't let you send them to it?
I finally got my internal memory to show up by mounting the system in the TWRP recovery.. But still getting an error that the device stopped responding or is disconnected.. However, it will let me open and view any file on the system, it just won't let me write to it.
Click to expand...
Click to collapse
Instead of trying to sideload the unlocker zip have you tried using the adb push command?

Timma
Thanks for the reply. The solution for me was to mount the phone in TWRP. This allowed my SD card to be explored in Windows. However, it still would not allow me to copy files to the main directory and just out of frustration I quickly drag and dropped a PDF file that landed on a folder in the SD directory and it worked. Haha. So I then tried to copy the file inside another folder instead of the main directory. Success. What a headache and big ass mistake I'll never make again.
Note to self. Do not lock the bootloader with a custom recovery still installed. Ever.

Retard in need of Help. Weird problem with recovery of my OPO

Alright have read the first 30 pages of comments on http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 and I starting to feel like I'm dumber then a brick.
Okay here is my problem: Just bought a used OPO with the classic boot logo loop error. I have tried to just simply Factory reset it (both Full and wipe cache) and it gives me E: failed to mount /cache (invalid argument) error. Then I googled it and most of the results said that I need to simply reinstall the software with adb. Okay got adb up and running and installed my phones drivers and booted into fastboot.
Then when I try to install it gave me "device not unlocked" error... Fine googled it tried "fastboot oem unlock" and it was still not unlocked.
Googled that and read the posts about tampered bits and after running the "fastboot oem device-info" It gives me "Device tampering: true" "Device unlocked: false" so damn.
Then I read the posts and tried to sideload OnePlusOne-BootUnlocker.zip (used the "apply update" in cyanogen recovery to get the ADB sideload) but it comes up with E: failed to mount /cache (invalid argument) and fails all the other things.
Have tried "fastboot boot recovery recovery.img" but that have the have a unlocked bootloader.
I'm abit lost ATM because I discovered that wile I can get fastboot and Sideload (from update) to show my device the normal adb can't see it when just being in the menu.
So if one of you could point me in the right way or if you got time guide me then I would be greatfull.
Regards Magnus/Mjallo
PS. Please don't burn me for asking

Can post pictures of the screen if it is needed

@Mjallo google "Bacon Toolkit."
Does literally all the things you are trying to do in a matter of a few clicks. Walks you through everything step by step.

h11wiscan said:
@Mjallo google "Bacon Toolkit."
Does literally all the things you are trying to do in a matter of a few clicks. Walks you through everything step by step.
Click to expand...
Click to collapse
Okay have played around with the program abit more and all it does is that same as me doing it in CMD.
I still have the problem with Device tampering and device unlock state. Where is the tools for fixing that?
Have tried to fix the cache but it still make the invalid argument.

might could fastboot flash official images to get the phone back to normal. you dont have to have bootloader unlocked to flash official boot images. you can go here https://cyngn.com/support and download the cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip (scroll down to opo section) and/or go to http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and get the download and follow directions in that post to flash phone

Mjallo said:
Okay have played around with the program abit more and all it does is that same as me doing it in CMD.
I still have the problem with Device tampering and device unlock state. Where is the tools for fixing that?
Have tried to fix the cache but it still make the invalid argument.
Click to expand...
Click to collapse
Yeah idk then. Need more screenshots or info to help. Could be a million things.
-Are you using OEM USB cable?
-Did you install ALL drivers properly?
-Have you rebooted since installing ALL drivers?
-Have you tried using bacon toolkit on another computer? Sometimes simply switching computers can help.
-Did you try resetting phone to factory state using ABD/Bacon Toolkit?
-In Bacon Toolkit did you select the proper firmware and software version before attempting to use the program?
A few questions to ask yourself before we go further.

kenboyles72 said:
might could fastboot flash official images to get the phone back to normal. you dont have to have bootloader unlocked to flash official boot images. you can go here https://cyngn.com/support and download the cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip (scroll down to opo section) and/or go to http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and get the download and follow directions in that post to flash phone
Click to expand...
Click to collapse
Have tried with both Normal Cyanogen and CyanogenMOD (that is what the bootlogo says on this phone) and both of them give the Device not unlocked error both on screen and in CMD

h11wiscan said:
Yeah idk then. Need more screenshots or info to help. Could be a million things.
-Are you using OEM USB cable?
-Did you install ALL drivers properly?
-Have you rebooted since installing ALL drivers?
-Have you tried using bacon toolkit on another computer? Sometimes simply switching computers can help.
-Did you try resetting phone to factory state using ABD/Bacon Toolkit?
-In Bacon Toolkit did you select the proper firmware and software version before attempting to use the program?
A few questions to ask yourself before we go further.
Click to expand...
Click to collapse
Okay I'm using the OEM cable (have tried both the one I got with this phone and the one I got with my Orginal OPO)
Have gone through the steps checking my drivers and they should be working and A OKAY, reboot and all.
Don't have access to another pc ATM but will look after the option.
Have tried all the option in Bacon toolkit to reset the phone to factory setting and non is working, tried to then use the recovery option to maybe get it to work that way but no dice. Have also tried sideloading both with Toolkit and with CMD and no luck their either. Took a picture of the screen when the sideload tries to work.
http://imgur.com/6L74N6J
The Firmware question is up in the air because I have never got it booted so I have no clue what firmware it has only hint that the boot screen is Cyanogen MOD READY and not just Cyanogen like on my other OPO
Hope it helps finding the problem

I super hard bricked my phone a while back, even lost a partition. I was finally able to get it back by flashing colorOS. took a few tries to get the program to recognize my phone, but finally got it flashed. The phone never booted all the way up with colorOs, but it fixed what needed fixed and I was then able to fastboot flash CM13, unlock bootloader and go from there. don't have that thread bookmarked, but it's here in the forums.
Edit: found thread http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

kenboyles72 said:
I super hard bricked my phone a while back, even lost a partition. I was finally able to get it back by flashing colorOS. took a few tries to get the program to recognize my phone, but finally got it flashed. The phone never booted all the way up with colorOs, but it fixed what needed fixed and I was then able to fastboot flash CM13, unlock bootloader and go from there. don't have that thread bookmarked, but it's here in the forums.
Edit: found thread http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
It sadly did not fix the problem it gives this problem and just stops working (need to close it in taskmanger) http://imgur.com/w1zOQFU.
Well the quest goes on

Mjallo said:
It sadly did not fix the problem it gives this problem and just stops working (need to close it in taskmanger) http://imgur.com/w1zOQFU.
Well the quest goes on
Click to expand...
Click to collapse
when you run the program, one of the columns should have a few random characters and "com" in it. if you dont see com in any of the columns, then the program is not seeing you phone. if you do see com, the click on that row and press start and it will show files being written in green showing progress. if phone is not being seen, follow that guide to the letter, specially if this is on a win7/8 machine. i will get my lappy out in a bit and give a few screenies on what it should look like, i wont actually flash my phone though.

kenboyles72 said:
when you run the program, one of the columns should have a few random characters and "com" in it. if you dont see com in any of the columns, then the program is not seeing you phone. if you do see com, the click on that row and press start and it will show files being written in green showing progress. if phone is not being seen, follow that guide to the letter, specially if this is on a win7/8 machine. i will get my lappy out in a bit and give a few screenies on what it should look like, i wont actually flash my phone though.
Click to expand...
Click to collapse
It sees it (you can see it in COM5 in the picture) and when the progress bar shows it just make a little green tip then just stops showing

are you running the program as administrator? right click on exe and select run as administrator? other than that, don't see why it's not flashing and I'm out of ideas, sorry.