So I've read the other threads about this and tried pretty much everything what am I doing wrong?
1: type in "/k cd c:\" to switch from C:\Users\johan> to C:
2:C:\>adb\fastboot flash unlocktoken Unlock_code.bin (which gives error cannot open "Unlock_code.bin")
file is in C:adb along with:
adb.exe
adbwinapi.dll
adbwinusbapi.dll
fastboot
fastboot.exe
additional info:
the unlock file is only 1kb is this normal?
"adb devices" shows no devices but fastboot works don't know why
any of the above causing the problem?
I assume you're simply trying to unlock the bootloader? Could you post more details please about your device, e.g. manufacturer, exact model, then I'll be able to help you. Also can you show me what guide you're following and exactly what you're trying to accomplish?
(I'm assuming you're missing drivers which is why I'm asking you for this info).
HTCDreamOn said:
I assume you're simply trying to unlock the bootloader? Could you post more details please about your device, e.g. manufacturer, exact model, then I'll be able to help you. Also can you show me what guide you're following and exactly what you're trying to accomplish?
(I'm assuming you're missing drivers which is why I'm asking you for this info).
Click to expand...
Click to collapse
It's a HTC ONE S that I got and since I hadn't used android b4 I instead of doing a system update I updated some kind of CID that was on the phone which locked the phone in to "this build is for developers only..."
trying to bring it back to stock installing an RUU failed for some reason(the RUU being the one already in use since the phone is S-ON)
fastboot and adb drivers are installed, I can find my device in fastboot but not adb. enabling USB debugging should fix this but I can't enter the phone while it's looping and I've found no way of enabling it via cmd
this is what the phone shows while in boot:
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28 (RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1. 11.50.05.28_10.27.50.08L_release_301814_signed_2_4 is the RUU I tried running)
OpenDPS-v31.1.0.45.0815
eMMC-boot
Dec 14 2012. 17:10:57:-1
and correct I'm trying to unlock bootloader through htcdev then repeating the process and locking the loader, running the RUU again... if this doesn't work I guess I can go S-OFF (but then I need USB debugging) and picking any RUU see if that works
and prior to getting this phone I had never touched an android so I have 0 experience
I have downloaded the SDK and htc sync
tried following these guides:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
http://forum.xda-developers.com/showthread.php?t=1315947
and this is my original asking thread trying to get my phone back to stock:
http://forum.xda-developers.com/htc-one-s/help/help-purchased-dev-phone-accidently-t2813586
I am retarded
since I got this phone second hand I didn't know what had been done with it other than what I installed to cause my problems...
one of the things that had been done previously was unlocking bootloader.. hence the very obvious "Unlocked" in the boot menu.... sooo unlocking an unlocked bootloader was kinda redundant
tried oem locking the boot b4 but missed to specify where the files where (C:adb), lock worked and RUU installed without a hing!
thanks for your help!
Related
Aplogies if this is not the best starting point but have been reading for 10 hours and am reluctant to take a next step after failure of s-off that has stuck phone in bootloader.
Details
Copied all SD card data to PC
Rooted phone as described by HTCdev
Used SKG utility to attempt s-off
Controlbear got stuck in some strage loop waiting for device after process had started. Never even got prompted to try the wire trick :-( 30 mins later I had to pull the pin
rebooting phone gave me the Controlbear black screen with Green arrow but could now not connect to the device using controlbear just said waiting for device then press any key to exit
Phone will not boot to android OS
when USB connected to phone in bootloader it says FASTBOOT USB and
fastboot devices lists my connected device so USB is OK
Followed instructions at unlimited.io/troubleshooting to try to recover controlbear -f seemed to do somthing so then did
fastboot flash boot recovery_backup.img
which failed could not find image !!!!! der
downloaded 4ext recovery.img
fastboot flash boot recovery.img
worked
Now have
Details of boot
*** UNLOCKED ***
Pyramid PVT SHIP S-ON RL
HBOOT 1.27.0000
Radio 11.24.3504.10_M
OpenADSP-v)2.6.0.2226.00.0131
cMMC-boot
CID reported by fastboot getvar cid is BM__001
Just tried everything from bootloader but always got back bootloader screen no Controlbear screen with arrow as before
At a whim I ran the controlbear -f again and whammo it came up with the 4ext recovery which I was happy to see. Despite doing a backup before starting anything 4ext says no backup present :-(
How can I recover device? I have downloaded the Bell stock RUU which should be correct for this device. Running it says device image version is 3.32.666.13Hesitant to try anything without some good advice. Hopefully I can recover and try the s-off agin but it's been a painful ride. Is it just as simple as clicking update on the RUU exe?
thanks
The backups are not present its saying when you are doing controlbear -f
That means you have no backup present in that controlbear folder
This can be either because of
1.you have another copy of controlbear folder where you done the soff process and where the controlbear saved the backups
(there will be boot_backup.img, recovery_ backup.img)
2.you deleted those images from the controlbear folder
Now what you can do is
1.just find the boot_backup.img and flash it via bootloader
fastboot flash boot boot_backup.img
That will get you out of the Juopunutbear screen..
No need to run the ruu in this case
Edit: and with regards to the 4EXT backup.. The backup will be stored in sdcard and during soff process the sdcard will be wiped.. That's why 4EXT said no backup present.. Just format your sdcard again.. Copy the sdcard backup from your pc (at least copy the Clockworkmod/backup folder to sdcard with the same path in sdcard... It holds your rom backup if you did any)
Then try the 4EXT backup
Sent from my pyramid.. Through blazing fast sonic waves
If your problem was solved, it's a good idea to add [SOLVED] to the topic.
Still in trouble
HI thanks for the advice. Went to the io help and they said relock boot and reflash RUU. Now I have not RUU'd at all as have not been able to find a suitable one. But did fastboot oem lock as suggested. Can I now unlock it again as your post made way more sense and I found the recovery stuff you are speaking of. Just need to unlock and I should be able to recover. is there an unlock command?
markwatson said:
HI thanks for the advice. Went to the io help and they said relock boot and reflash RUU. Now I have not RUU'd at all as have not been able to find a suitable one. But did fastboot oem lock as suggested. Can I now unlock it again as your post made way more sense and I found the recovery stuff you are speaking of. Just need to unlock and I should be able to recover. is there an unlock command?
Click to expand...
Click to collapse
Copy the unlock_code.bin to the folder with adb & fastboot.
Then
Code:
fastboot flash unlocktoken unlock_code.bin
Also, please come down to this channel for support. (I'm only going to help there because you used the tool)
SOLVED
Solved Problem
Hi All Thanks to some sterling efforts by KGS1992 my problem was solved. Take care ye all to ensure that you ensure you get the correct version of controlbear there are many and you need the correct one for your android version. I'll post a detailed summary tomorrow I'm bushed.
I don't like starting new threads especially but I have searched and searched and not come up with an answer/problem quite the same as mine. I am not a TOTAL noob and do understand s-on, s-off, htcdev unlock etc. Here goes
I got a Sensation from a friend who acuired it from God knows when but he asked me if it can be fixed. Its currently stuck in fastboot mode. Its Locked S-OFF however NOTHING I try works. Here is some info
BOOTLOADER
*** Locked ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012,17:33:34
CID
Is already Super CID = 11111111
RECOVERY
There is no custom recovery flashed and trying to flash recovery via fastboot fails saying "remote: not allowed"
FASTBOOT COMMANDS
Fastboot commands work to get cid etc but get a "remote: not allowed" to erase or flash boot,img, any rom or any hboot or ANYTHING
BOOTLOADER FLASHING
If I try to flash a firmware file through Bootloader, it parses the P58IMG.zip but fails on Bootload saying Fail-PU Partition update failed
FLASH SHIPPED RUU
Trying a shipped ROM also fails. Goes smoothly, reads current image on phone as 1.45.401.3 but once it starts updating, it sticks in waiting for boatloader and gives ERROR[171] while phone has restarted in FASTBOOT mode
HTCDEV Unlock
I thought I would give the HTCDEV method a go even though I know this is redundant since I am already supposedly s-off but even that fails cuz no lock, unlock screen comes up. Flashing of Unlock_boot.bin goes fine
I am at a TOTAL loss now cuz since I am already S-OFF, I should have been able to flash recover or flash a rom or boot image to get phone working again. NOTHING works!!
Any ideas anyone? Apologies if this has been covered before and I couldnt find it.
tabi13 said:
I don't like starting new threads especially but I have searched and searched and not come up with an answer/problem quite the same as mine. I am not a TOTAL noob and do understand s-on, s-off, htcdev unlock etc. Here goes
I got a Sensation from a friend who acuired it from God knows when but he asked me if it can be fixed. Its currently stuck in fastboot mode. Its Locked S-OFF however NOTHING I try works. Here is some info
BOOTLOADER
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012,17:33:34
CID
Is already Super CID = 11111111
RECOVERY
There is no custom recovery flashed and trying to flash recovery via fastboot fails saying "remote: not allowed"
FASTBOOT COMMANDS
Fastboot commands work to get cid etc but get a "remote: not allowed" to erase or flash boot,img, any rom or any hboot or ANYTHING
BOOTLOADER FLASHING
If I try to flash a firmware file through Bootloader, it parses the P58IMG.zip but fails on Bootload saying Fail-PU Partition update failed
FLASH SHIPPED RUU
Trying a shipped ROM also fails. Goes smoothly, reads current image on phone as 1.45.401.3 but once it starts updating, it sticks in waiting for boatloader and gives ERROR[171] while phone has restarted in FASTBOOT mode
HTCDEV Unlock
I thought I would give the HTCDEV method a go even though I know this is redundant since I am already supposedly s-off but even that fails cuz no lock, unlock screen comes up. Flashing of Unlock_boot.bin goes fine
I am at a TOTAL loss now cuz since I am already S-OFF, I should have been able to flash recover or flash a rom or boot image to get phone working again. NOTHING works!!
Any ideas anyone? Apologies if this has been covered before and I couldnt find it.
Click to expand...
Click to collapse
Have you tried playing with fastboot commander? Mabe try formatting all partitions, then installing RUU or PG58IMG ?Or try with different RUUs? The last thing I can think of is to lock the bootloader back, and try to send it to HTC with warranty.
Even fastboot commander, the same as entering commands manually can not flash anything or erase any partition. Dead end there.
tabi13 said:
Even fastboot commander, the same as entering commands manually can not flash anything or erase any partition. Dead end there.
Click to expand...
Click to collapse
what about locking it back to s-on? did you tried it? does it "run" a custom rom ?
First off to use all the fastboot commands you need to have a eng Hboot on the device. You can not use all fastboot commands with a stock Hboot which is what the Hboot 1.27.0000 that you have is. Click on this link to download the JuopunutBear eng Hboot and follow the below instructions to flash it via fastboot.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
If you still can not get the device up and going using fastboot after flashing the eng Hboot, or if the Hboot will not flash you may have screwed up partitions on the the device. There is a fastboot or a adb command you can use to get a read out of the partitions but I can not remember it right now, just google it you will find it. I mention this because of the "Fail-PU Partition update failed" message you mentioned.
If it does flash the eng Hboot then you should be able to flash a custom recovery or anything else you want to flash via fastboot. If all else fails though do as gallardo5 sayed and flash the stock ROM via RUU while in fastboot and connected to your computer via USB. Then you can try to start from scratch rooting and installing a custom recovery.
T-Macgnolia said:
First off to use all the fastboot commands you need to have a eng Hboot on the device. You can not use all fastboot commands with a stock Hboot which is what the Hboot 1.27.0000 that you have is. Click on this link to download the JuopunutBear eng Hboot and follow the below instructions to flash it via fastboot.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
If you still can not get the device up and going using fastboot after flashing the eng Hboot, or if the Hboot will not flash you may have screwed up partitions on the the device. There is a fastboot or a adb command you can use to get a read out of the partitions but I can not remember it right now, just google it you will find it. I mention this because of the "Fail-PU Partition update failed" message you mentioned.
If it does flash the eng Hboot then you should be able to flash a custom recovery or anything else you want to flash via fastboot. If all else fails though do as gallardo5 sayed and flash the stock ROM via RUU while in fastboot and connected to your computer via USB. Then you can try to start from scratch rooting and installing a custom recovery.
Click to expand...
Click to collapse
Oh yes, I should have mentioned it. I did even try flashing the JB-hboots, both GB and ICS versions. Neither worked.
It gives error on erase cache, oem rebootRUU reboots back to fastboot and then flashing fails
I think you are spot on about the partitions about being mssed up. Even if they can be read out (i saw the commands somewhere myself) can they be repaired at all?
p.s. Thanks for your help
One more thing I should have mentioned and dont know how I missed, the FASTBOOT page says *** Locked *** not *** Unlocked ***. I dont know if this can/should be changed.
I am sorry in advance if I am being silly
tabi13 said:
One more thing I should have mentioned and dont know how I missed, the FASTBOOT page says *** Locked *** not *** Unlocked ***. I dont know if this can/should be changed.
I am sorry in advance if I am being silly
Click to expand...
Click to collapse
If you have a messed up partition you can not fix it without replacing the whole board. And about the locked in fastboot that is why your fastboot commands are not working. But the fact that you can not flash the eng Hboot sorta tells me you got a bad partition and it will not take the flash. Blackwing had the same issue with his Sensation and all the best guys I know that are over on the IRC Help Now channel could not come up with a fix and finally diagnosed it as bad partitions. Hid was the exact same it would give aerroron erase cache. Find the command to get a read out on the partitions and post the read out here.
T-Macgnolia said:
If you have a messed up partition you can not fix it without replacing the whole board. And about the locked in fastboot that is why your fastboot commands are not working. But the fact that you can not flash the eng Hboot sorta tells me you got a bad partition and it will not take the flash. Blackwing had the same issue with his Sensation and all the best guys I know that are over on the IRC Help Now channel could not come up with a fix and finally diagnosed it as bad partitions. Hid was the exact same it would give aerroron erase cache. Find the command to get a read out on the partitions and post the read out here.
Click to expand...
Click to collapse
Tmac.. I solved one guys FAIL-PU errors.. If the op can boot to recovery.. Maybe we can fix it.. Remember I said we CAN so there's a possibility
Edit: but not now.. Or at least until 20th August.. I'm out of station (as I need to do remotely everything)
Sent from my HTC Sensation 4G using xda premium
gameshp, let me know when you can help me out. IF my friend hasnt given up by then. Thank you
I have the same situation, so I'm really hoping for a solution.
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
eMMC-boot
Jan 13 2012,17:33:34
hey ppl im ready ..check your PM's ..and let me know
Did you try to navigate back to "HBOOT" and do a "Factory reset"?
If it does not work, maybe you should flash firmware using JTAG.
marcusgolden said:
I have the same situation, so I'm really hoping for a solution.
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
eMMC-boot
Jan 13 2012,17:33:34
Click to expand...
Click to collapse
No you don't have the same problem, cause your bootloader is unlocked
Flash the firmware again and try to flash recovery
Hi,
I'm having a lot of problems after rooting my device.
I can get into the Bootloader and Recovery, so I'm certain it's not bricked.
Here is my screen in bootloader:
*** UNLOCKED ***
DOUBLESHOT PVT SHIP S-ON RL
HBOOT-1. 45 .0013
MICROP-0353
eMMC-boot
Nov 21 2011.20:20:47
Now, when I load fastboot and connect it to the USB, it says "fastboot usb" but "adb devices" doesn't show it in the list.
I had it working when I booted it into CM10, but I needed to get it to s-off in order to SIM unlock it, but "adb devices" would NOT pick it up, in bootloader OR CM10.1 (Yes I checked all settings from within CM10, allowing debugging and root etc).
I then decided to pay $14.99 for an unlock code to save the hassle of going through the s-off problems as I couldn't detect it using revolution or adb. Turns out only stock rom will allow SIM Unlock so I tried to flash a stock rom, several different ones now and for some reason it didn't get past the splash screen on any of them. So I tried flashing PD59IMG.zip which looked like it worked, but then: Splash screen.
I'm now completely stuck. Please help.
Fixed: http://forum.xda-developers.com/showthread.php?t=2100182&highlight=stock+rom
Use "Fastboot Devices" when in fastboot and see if it recognizes it then. Also from your hboot it looks like you have a mytouch 4g slide instead of a mytouch 4g. If you are unlocked but have s-on you have to flash the kernal before flashing the rom. Its frustrating but pretty easy if you follow these instructions http://forum.xda-developers.com/showthread.php?t=1508556
Please go to the mytouch 4g slide forums, you have a doubleshot, these are the glacier forums.
THEindian said:
Please go to the mytouch 4g slide forums, you have a doubleshot, these are the glacier forums.
Click to expand...
Click to collapse
...uhh no. These are the MT4GS forums, not the MT4G forums.
HappyKhicken said:
...uhh no. These are the MT4GS forums, not the MT4G forums.
Click to expand...
Click to collapse
This was originally put in the wrong forum. A mod moved it!
Sent from my Nexus 4 using Tapatalk 2
Spudguy said:
Hi,
I can get into the Bootloader and Recovery, so I'm certain it's not bricked.
Now, when I load fastboot and connect it to the USB, it says "fastboot usb" but "adb devices" doesn't show it in the list.
I had it working when I booted it into CM10, but I needed to get it to s-off in order to SIM unlock it, but "adb devices" would NOT pick it up, in bootloader OR CM10.1 (Yes I checked all settings from within CM10, allowing debugging and root etc).
Click to expand...
Click to collapse
So did you install CWR already, or are you still on stock recovery? Reinstalling drivers for your phone sounds like what might help out.
Limewirelord said:
So did you install CWR already, or are you still on stock recovery? Reinstalling drivers for your phone sounds like what might help out.
Click to expand...
Click to collapse
He needs to use fastboot commands while in fastboot mode like 'fastboot devices' adb commands don't work while in fastboot
Sent from my Nexus 4 using Tapatalk 2
you installed the correct mt4gs fastboot drivers cause that happened to me when i DLed the tether version of htc fastboot and didnt work maybe...thats the problem
Spudguy said:
Hi,
I'm having a lot of problems after rooting my device.
I can get into the Bootloader and Recovery, so I'm certain it's not bricked.
Here is my screen in bootloader:
*** UNLOCKED ***
DOUBLESHOT PVT SHIP S-ON RL
HBOOT-1. 45 .0013
MICROP-0353
eMMC-boot
Nov 21 2011.20:20:47
Now, when I load fastboot and connect it to the USB, it says "fastboot usb" but "adb devices" doesn't show it in the list.
I had it working when I booted it into CM10, but I needed to get it to s-off in order to SIM unlock it, but "adb devices" would NOT pick it up, in bootloader OR CM10.1 (Yes I checked all settings from within CM10, allowing debugging and root etc).
I then decided to pay $14.99 for an unlock code to save the hassle of going through the s-off problems as I couldn't detect it using revolution or adb. Turns out only stock rom will allow SIM Unlock so I tried to flash a stock rom, several different ones now and for some reason it didn't get past the splash screen on any of them. So I tried flashing PD59IMG.zip which looked like it worked, but then: Splash screen.
I'm now completely stuck. Please help.
Fixed: http://forum.xda-developers.com/showthread.php?t=2100182&highlight=stock+rom
Click to expand...
Click to collapse
strapped365 said:
He needs to use fastboot commands while in fastboot mode like 'fastboot devices' adb commands don't work while in fastboot
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
You need the proper drivers installed for the device in fastboot mode also. They are each their own device, you would need to install the proper drivers for the phone in both adb and fastboot modes. I did this a few days ago when setting up the phone and Android SDK on Windows 8 and I had to install the HTC driver for them separately.
Hello,
I cannot recover my Sensation anymore, so the experts in this forum are my last hope:
I suffered from "eMMC corruption" described in
http://forum.xda-developers.com/showthread.php?t=2542506
That meant that a RUU got stuck in the middle and after a reset the phone remains in "RUU mode". In order to fix the partition table I tried a lot of things. Among others, I reinstated S-ON (via fastboot writesecureflag 3) and lock (via fastboot oem lock) because I had read that RUU needs a locked bootloader.
In hindsight that was a very stupid thing to do, as RUU still fails. But now I cannot flash any recovery anymore.
I tried unlocking the phone again using the HTCDev method (fastboot flash unlocktoken Unlock_code.bin) but this seems to fail now - I supposed because I'm in RUU mode, not in the normal bootloader.
As a consequence, my phone is still in RUU mode but doesn't respond to fastboot commands anymore.
I've searched this forum but couldn't find a workable solution for my problem.
I could imagine the following ways out of it:
- somehow get out of RUU mode and back into the normal bootloader; I imagine the HTCDev unlock process works there
- find a different method of unlocking that doesn't require adb but only fastboot (I only know of Revolutionary, Juopunutbear and rumrunner S-OFF, all of which need working adb)
- somehow try to compose a RUU that has a shorter (not working) image for the partition that fails in order to complete RUU and get into the bootloader this way
Has anyone else any other idea for me how to proceed?
Thanks a lot in advance.
lotan_rm said:
Hello,
I cannot recover my Sensation anymore, so the experts in this forum are my last hope:
I suffered from "eMMC corruption" described in
http://forum.xda-developers.com/showthread.php?t=2542506
That meant that a RUU got stuck in the middle and after a reset the phone remains in "RUU mode". In order to fix the partition table I tried a lot of things. Among others, I reinstated S-ON (via fastboot writesecureflag 3) and lock (via fastboot oem lock) because I had read that RUU needs a locked bootloader.
In hindsight that was a very stupid thing to do, as RUU still fails. But now I cannot flash any recovery anymore.
I tried unlocking the phone again using the HTCDev method (fastboot flash unlocktoken Unlock_code.bin) but this seems to fail now - I supposed because I'm in RUU mode, not in the normal bootloader.
As a consequence, my phone is still in RUU mode but doesn't respond to fastboot commands anymore.
I've searched this forum but couldn't find a workable solution for my problem.
I could imagine the following ways out of it:
- somehow get out of RUU mode and back into the normal bootloader; I imagine the HTCDev unlock process works there
- find a different method of unlocking that doesn't require adb but only fastboot (I only know of Revolutionary, Juopunutbear and rumrunner S-OFF, all of which need working adb)
- somehow try to compose a RUU that has a shorter (not working) image for the partition that fails in order to complete RUU and get into the bootloader this way
Has anyone else any other idea for me how to proceed?
Thanks a lot in advance.
Click to expand...
Click to collapse
Hi this is for another device but u can have a look, the thread title is "how to flash a rom in ruu mode" i dunno tho.
http://forum.xda-developers.com/showthread.php?t=1087164
jmcclue said:
Hi this is for another device but u can have a look, the thread title is "how to flash a rom in ruu mode" i dunno tho.
http://forum.xda-developers.com/showthread.php?t=1087164
Click to expand...
Click to collapse
jmcclue: Thank you for the link to the thread. Unfortunately, that doesn't help me because the eMMC bug causes an RUU to never finish. It always get stuck somewhere in the middle. As a consequence, it always stays in RUU mode.
lotan_rm said:
jmcclue: Thank you for the link to the thread. Unfortunately, that doesn't help me because the eMMC bug causes an RUU to never finish. It always get stuck somewhere in the middle. As a consequence, it always stays in RUU mode.
Click to expand...
Click to collapse
I'm afraid that even if you find a way to gain S-Off again or an unlocked bootloader, you won't find a way to fix the eMMC.
I think it's like a broken flash drive, you won't ever be able to fix it.
Sajito said:
I'm afraid that even if you find a way to gain S-Off again or an unlocked bootloader, you won't find a way to fix the eMMC.
I think it's like a broken flash drive, you won't ever be able to fix it.
Click to expand...
Click to collapse
Are you sure repartitioning wouldn't help. I've found a friend who has a Sensation as well (working of course) and I would've tried remodelling the partition table after his'.
lotan_rm said:
Are you sure repartitioning wouldn't help. I've found a friend who has a Sensation as well (working of course) and I would've tried remodelling the partition table after his'.
Click to expand...
Click to collapse
I'm not 100% sure, you can always try.
I'm not even 50% sure it would work but I'd hate giving up on an otherwise good phone.
Hello All
I have been getting a lot of dropped calls and calls don't come through sometimes
I think it"s a software firmware problem right?
I can't update my phone which is running on a ROM I downloaded from this website
When I try to update the phone gives me this message ,,,,,,, I paraphrase
(Can"t update your phone because you have modified software
restore HTC software)
Here are my phone vitals
HTC ONE XL
First lines of my boot loader
ATT phone
UNLOCKED (using Tmobile)
EVITA PUT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OPEN DSP-34.1.0.45.1219
eMMC-boot
Nov 26 2012
running Android 4.2.2
Kernel is [email protected]#1SMP PREEMPT
Recovery
Team win recovery project 2.7.1.0
My questions are
How do I fix this?
Do have to do a factory reset ?
If I do a factory reset will my phone be locked again?
Thanks
HTCuser3 said:
Hello All
I have been getting a lot of dropped calls and calls don't come through sometimes
I think it"s a software firmware problem right?
I can't update my phone which is running on a ROM I downloaded from this website
When I try to update the phone gives me this message ,,,,,,, I paraphrase
(Can"t update your phone because you have modified software
restore HTC software)
Here are my phone vitals
HTC ONE XL
First lines of my boot loader
ATT phone
UNLOCKED (using Tmobile)
EVITA PUT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OPEN DSP-34.1.0.45.1219
eMMC-boot
Nov 26 2012
running Android 4.2.2
Kernel is [email protected]#1SMP PREEMPT
Recovery
Team win recovery project 2.7.1.0
My questions are
How do I fix this?
Do have to do a factory reset ?
If I do a factory reset will my phone be locked again?
Thanks
Click to expand...
Click to collapse
Since your phone is S-OFF it should be easy to bring it back to stock using a RUU or a stock rom to troubleshoot if your issue is software or hardware related. I'll ask a moderator to move your thread in the correct section (you have posted in the One X9 forum) and ppl there should be able to help you. Meanwhile you might want to post the output of "fastboot getvar all" so the ppl there will already have all the info to help you.
Btw your phone will not be relocked after a factory reset.
Thanks
I will do that
HTC said they could help me with the factory Reset but I wanted to come here first
Never heard of Fastboot Getvar All
Can anyone explain that and how to do that?
Thanlks
HTCuser3 said:
I will do that
HTC said they could help me with the factory Reset but I wanted to come here first
Never heard of Fastboot Getvar All
Can anyone explain that and how to do that?
Thanlks
Click to expand...
Click to collapse
You need to use fastboot from a pc to enter that command. Adb and fastboot need to be installed first (if you don't already have it) then type.
Adb devices ( this makes sure your connected) should respond back with numbers.
Now you enter the*fastboot*main command with the command*getvar*(get variable) and “all” as parament for that
fastboot getvar all
Which will get you a list of various variables on the phone with model and such useful things.
And, if you want to output this to a textfile, you can’t use the standard dos output since fastboot.exe doesn’t support that. So you have to use the 2nd output.
fastboot getvar all 2> filename.txt
That will create a text-file called “filename.txt” in the folder where you stand when you enter that command.
Sent from my Nexus 6 using XDA Free mobile app
31ken31 said:
You need to use fastboot from a pc to enter that command. Adb and fastboot need to be installed first (if you don't already have it) then type.
Adb devices ( this makes sure your connected) should respond back with numbers.
Now you enter the*fastboot*main command with the command*getvar*(get variable) and “all” as parament for that
fastboot getvar all
Which will get you a list of various variables on the phone with model and such useful things.
And, if you want to output this to a textfile, you can’t use the standard dos output since fastboot.exe doesn’t support that. So you have to use the 2nd output.
fastboot getvar all 2> filename.txt
That will create a text-file called “filename.txt” in the folder where you stand when you enter that command.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Can I do that with a Mac?
Thanks
HTCuser3 said:
Can I do that with a Mac?
Thanks
Click to expand...
Click to collapse
Yes, I'm not 100% of the steps on a Mac. Search Mac adb fastboot on the forums here. Should be a easy find. If ya get stuck I'll see what I can find in the am. It's 1:30 am here and too lazy to search yet.
Sent from my Nexus 6 using XDA Free mobile app
Hello
Sorry It's been awhile but I am getting around to following your instructions
I found the thread for setting up adb and fastboot on a mac
http://forum.xda-developers.com/showthread.php?t=1917237
(I had to download android studio go to configure>SDK manager>Launch Standalone ADK manager from there I downloaded the files I needed . I found adb and fastboot this way adtbundle for mac> sdk>platformtools> (That was hard)
But now I don't know how to follow the following instructions
"Paste ADK and Fastboot in the root of your android folder"
And
I opened a terminal but when I try to type the path to my android folder
cd /Users/<myusername>/Desktop/android
I get "no such file or directory "
So now I am stuck
Please help if you can
Thanks
HTCuser3 said:
Hello
Sorry It's been awhile but I am getting around to following your instructions
I found the thread for setting up adb and fastboot on a mac
http://forum.xda-developers.com/showthread.php?t=1917237
(I had to download android studio go to configure>SDK manager>Launch Standalone ADK manager from there I downloaded the files I needed . I found adb and fastboot this way adtbundle for mac> sdk>platformtools> (That was hard)
But now I don't know how to follow the following instructions
"Paste ADK and Fastboot in the root of your android folder"
And
I opened a terminal but when I try to type the path to my android folder
cd /Users/<myusername>/Desktop/android
I get "no such file or directory "
So now I am stuck
Please help if you can
Thanks
Click to expand...
Click to collapse
Post some screen shots of the error with as much previous text as possible
Sent from my Nexus 6 using XDA Free mobile app