Hey guys.
I have an AT&T HTC One that I'd like to convert to T-Mobile version. I'm selling my phone to someone with T-Mobile.
It would just be nice for it to be stock for this person and without AT&T bloat on it.
It's unlocked and s-off and CID is 111111111 and also running HBOOT 1.44
When I run the stock HTC T-Mobile 4.3 Sense RUU, it fails saying CHECK USB CONNECTION.
USB Connection is fine though, it's stilling in fastboot mode and fastboot devices detect it just fine. (I've previously converted to GPE Rom and also Had CM10.2 on it, and currently it's stock AT&T 4.3 Sense ROM).
Any ideas / tips? Should I try a non 4.3 sense ruu? then go to 4.3ruu?
Thanks
Update: I booted the phone up, the RUU detected, and it put the phone to download mode (fastboot oem rebootRUU), but then got same usb 171 error.
Cant really comment much on how to do it but keep in mind the ATT version is different from TMO version.
They will not get the 1700 aws spectrum that most of TMO network is on.
They will get the 1900mhz refarmed spectrum..
You can try to flash a GPe RUU or TMO since you put 1111111 as your super CID.
As far as why its giving you an error sorry im not super experienced with those types of things.
You can do it using fastboot
nxt said:
Hey guys.
I have an AT&T HTC One that I'd like to convert to T-Mobile version. I'm selling my phone to someone with T-Mobile.
It would just be nice for it to be stock for this person and without AT&T bloat on it.
It's unlocked and s-off and CID is 111111111 and also running HBOOT 1.44
When I run the stock HTC T-Mobile 4.3 Sense RUU, it fails saying CHECK USB CONNECTION.
USB Connection is fine though, it's stilling in fastboot mode and fastboot devices detect it just fine. (I've previously converted to GPE Rom and also Had CM10.2 on it, and currently it's stock AT&T 4.3 Sense ROM).
Any ideas / tips? Should I try a non 4.3 sense ruu? then go to 4.3ruu?
Thanks
Update: I booted the phone up, the RUU detected, and it put the phone to download mode (fastboot oem rebootRUU), but then got same usb 171 error.
Click to expand...
Click to collapse
I had similar problem of RUU not detecting my phone but fastboot working. Here's what I did to install the RUU. In fastboot usb mode, I used command "fastboot oem rebootRUU" and then installed the RUU once the phone rebooted(and it detected the phone this time) and put it in the download mode.
Sorry I did not see your update part. But mine worked since I was going back to AT&T stock 4.1 from international rom. I would check if it works with whatever the stock T-Mobile version would be and then upgrading to 4.3
Related
Full disclosure, this isn't my phone and I'm helping a coworker who did some things. The phone was originally purchased without service as she was switching from AT&T to T-mobile and didn't have it setup yet.
Incident: The phone was unlocked and rooted when last night she used a "toolkit" (I have no idea which one and she said she deleted the folder with everything), then locked it with the toolkit and used the fastboot oem unlock to get back in. When the stock rom was installed again the screen wouldn't work and I was able to navigate with a OTG mouse connected. All of the custom roms work fine as far as the screen goes but the stock one is like it's missing a driver. The other issue here is the SIM card doesn't pickup a network, I verified the Access Point is setup correctly and tried with both the LTE (fast) setup and regular. It's entirely possible that the radio was hosed to start with and we didn't find out until the sim card was purchased on Monday. At this point I'd just like to get it back to FULL stock and see if she can do anything with the Warranty (not sure if this is really possible yet). So, on to things I've tried.
1. Display Issue on Stock, I read this could be a kernel issue and attempted to flash several Stockish roms from here. Also the kernel from mugetsu666. That kernel a long with the other 3-4 stock roms from page 1. Nothing resolved.
2. No Signal. While going through the stock and custom roms all I really need is the signal to work. The PA install had the wrong APN settings and I updated them with the Defaults. No change, so I moved on to radios, maybe that's it. Flashed all the radios from here and a couple other random ones from the individual rom I was using. Nothing.
3. Ok, at this point I just want back to stock. This phone is toast and I'm tired of dealing with it for the day. Found the t-mobile ruu file here and attempted to run it as admin on a windows 7 and 8 machines. The bootloader was locked before attempting this and I tried in fastboot or just the phone being on. All I get is error 170 which is the usb connection issue. Fastboot does recognize my device so the RUU should pickup, now i'm really stuck.
Needless to say it's hasn't been a productive day at work. Any assistance is greatly appreciated. THANKS!!
I see you tired the T-Mobile ruu have your tried offival att ruu yet?
Sent from inside the T.A.R.D.I.S
joselv456 said:
I see you tired the T-Mobile ruu have your tried offival att ruu yet?
Sent from inside the T.A.R.D.I.S
Click to expand...
Click to collapse
You should run the revone s-off before you do anything after unlocking the bootloader. The first RUU should have been ATT since it is an ATT phone, like the last poster mentioned. After you unlock the bootloader, run revone to get s-off, then get superCID and run whatever RUU you like ATT,GPE, or T-Mo.
This one?. The link is dead. Can I use another supercid by at or M7?
Thanks for the help. I'm really a Samsung user so this is new
C Murder said:
You should run the revone s-off before you do anything after unlocking the bootloader. The first RUU should have been ATT since it is an ATT phone, like the last poster mentioned. After you unlock the bootloader, run revone to get s-off, then get superCID and run whatever RUU you like ATT,GPE, or T-Mo.
Click to expand...
Click to collapse
Bootloader unlocked
s-off complete
CID-11111111
I'm running the Signed2 from this list.
http://www.androidruu.com/index.php?developer=M7
Error 170, USB issue. Fastboot can see the device but the RUU can't, odd.
Edit: Running the RUU when the phone is booted to PA gets pasted the error 170. Now it's an error 155 and it's stuck on the HTC logo. Powering it off and it's still hosed.
Sooooo, I think there is more wrong here than a simple RUU update. I noticed under the *** UNLOCKED *** that the model is M7_UL, which i'm finding is a Europe model. I'm toast.. warm buttery toast i think.
Side note: Don't offer to help coworkers if you haven't worked on a phone like this before.
I have m7ul which was originally a t-mobile device when I got it used. I flashed the GE ruu no problem. You should be ok with that device.
Sent from my HTC One using Tapatalk 4
kronikwisdom said:
Bootloader unlocked
s-off complete
CID-11111111
I'm running the Signed2 from this list.
http://www.androidruu.com/index.php?developer=M7
Error 170, USB issue. Fastboot can see the device but the RUU can't, odd.
Edit: Running the RUU when the phone is booted to PA gets pasted the error 170. Now it's an error 155 and it's stuck on the HTC logo. Powering it off and it's still hosed.
Click to expand...
Click to collapse
Did you try running the tmobile RUU.exe from your pc. I know it's in the Tmobile HTC One forum. I'm sure it's here somewhere too. The kernels and recovery are there too, with guides to take you back to stock.
C Murder said:
Did you try running the tmobile RUU.exe from your pc. I know it's in the Tmobile HTC One forum. I'm sure it's here somewhere too. The kernels and recovery are there too, with guides to take you back to stock.
Click to expand...
Click to collapse
Yes, I've tried the tmobile RUU from these forums.
I've just made things worse now it seems because I updated the CID back to "T-MOB010" and now the recovery image won't stick. Seems like I'm missing something else from the boot.img but I've tried to flash the original firmware.zip on these forums. So tired of this thing.
Monday and I'm still at this. After relocking my boot loader per the request of the owner I'm unable to unlock it now. Requested a new code and that didn't change anything. The command to unlock from fastboot completes and writes successfully but the screen doesn't popup on my phone to accept the unlock.
Fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 kb)... <--- not sure if that's correct, the file is actually 256b but maybe it's under 1 so it doesn't show.
OKAY [ 0.150s ]
writing 'unlocktoken'...
OKAY [ 0.010s ]
finished. total time: 0.160s
this phone is going further down hill.
last ditch effort and I ran the RUU from Tmobile on an old XP machine, worked. back to stock.. not sure what to say but i'm tired of looking.. haha
I don't know why she needed to do all that soff in the first place ... This device doesn't require soff to flash roms or even soff to flash tmobile roms on the att m7 or vise versa
It's a lot like nexus model the boot.img flashes In roms soff is usually needed to do that on other htc devices not the One
Simple carrier unlock and Bootloader unlock with recovery is all you need to flash any Rom onto any m7 besides sprint and vzw
Soff and supercid doesnt seem like it was necessary in her case
HTC is touchy stuff takes reading 10 times over before attempting anything...
If we had a samsung Odin method we would be golden ..
Glad it's fixed
Sent from my HTC One using xda app-developers app
Hey all,
The title pretty much says it all. I've converted my AT&T HTC One into a Google Edition phone, but I'm tired of multiple issues etc. With that being said, I'd like to convert back to AT&T stock, but I can't seem to find the stock RUU for my device. Can anyone point me to the right direction? I've been able to pretty much get to the RUU stage, but it seems like that's the only thing holding me back at this point.
Thanks all
pacDiesel said:
Hey all,
The title pretty much says it all. I've converted my AT&T HTC One into a Google Edition phone, but I'm tired of multiple issues etc. With that being said, I'd like to convert back to AT&T stock, but I can't seem to find the stock RUU for my device. Can anyone point me to the right direction? I've been able to pretty much get to the RUU stage, but it seems like that's the only thing holding me back at this point.
Thanks all
Click to expand...
Click to collapse
post your fastboot getvar all results minus serial no and IEMI
did you change your MID and CID to GPE?
You need to be S-Off...
Directions an Hboot you'll need are here: http://forum.xda-developers.com/showpost.php?p=43460011&postcount=2
The RUU file is here: http://www.htc1guru.com/downloads/ruu-file-downloads/
You want the Cingular one...
One thing not mentioned in the directions on xda is that affer you flash the hboot in RUU mode, fastboot reboot-bootloader. With the phone connected in bootloader mode, run the RUU. There is no need to change your CID back to the att one to have the RUU run...
pm me if you have any questions...I did it today...I prefer the developer edition RUU...(brightstar) grab the 1.29.1540.16 version, and let it run the OTA's all the way to 4.4.2
Mark
Hi all,
I was hoping for a little help. I got my phone last summer on At&t and immediately converted the Developer's Edition. The phone is currently rooted,
has s-off and is on a KitKat Rom.
The above said, would I be able to get back to stock? I've Googled it and can only find instructions on Stock to Developer's, not the other way around.
TIA
infg3570
infg3570 said:
Hi all,
I was hoping for a little help. I got my phone last summer on At&t and immediately converted the Developer's Edition. The phone is currently rooted,
has s-off and is on a KitKat Rom.
The above said, would I be able to get back to stock? I've Googled it and can only find instructions on Stock to Developer's, not the other way around.
TIA
infg3570
Click to expand...
Click to collapse
did you s-off ? did you change your CID ?
just change your CID back to AT&T
fastboot oem writecid CWS__001
and flash the AT&T RUU
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
clsA said:
did you s-off ? did you change your CID ?
just change your CID back to AT&T
fastboot oem writecid CWS__001
and flash the AT&T RUU
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Click to expand...
Click to collapse
Thank you! All though I have email notification set up for replies, I never received one. Interesting is that my CID remains the At&t and i currently have s-off. When I RUU.exe (I downloaded the same the other night), I get an error and it restarts my phone. I'm wondering if it's because I have a KitKat Rom already installed and the software number is slightly higher than the RUU? The software number is 4.18.502.7 (my phone). I think the RUU is 502.1.
Thanks again,
infg3570
infg3570 said:
Thank you! All though I have email notification set up for replies, I never received one. Interesting is that my CID remains the At&t and i currently have s-off. When I RUU.exe (I downloaded the same the other night), I get an error and it restarts my phone. I'm wondering if it's because I have a KitKat Rom already installed and the software number is slightly higher than the RUU? The software number is 4.18.502.7 (my phone). I think the RUU is 502.1.
Thanks again,
infg3570
Click to expand...
Click to collapse
If your s-off use my decrypted RUU here
http://www.androidfilehost.com/?fid=23329332407580500
instructions are here
http://forum.xda-developers.com/showthread.php?t=2695749
clsA said:
If your s-off use my decrypted RUU here
http://www.androidfilehost.com/?fid=23329332407580500
instructions are here
http://forum.xda-developers.com/showthread.php?t=2695749
Click to expand...
Click to collapse
I tried as you have suggested your decrypted file. Unfortunately, I get an error when trying to run it via ADB in fastboot.
I've rooted when I first got the phone last summer using Revone method/tool. All worked fine and i had continued updating the OS a few times with stock rooted phones.
The last that i updated to was a stock rooted odex kitkat ROM found here http://forum.xda-developers.com/showthread.php?t=2676986
Only thing that seemed wrong was that I couldn't reinstall any of my apps requiring root. The error that would pop up is "Could not install to SD card".
Now, I have to say that I noticed that with some updates, it seems that new ROMS don't clean up the old files/framework even after fully wipes. It seems to back it up in some folders (sdcard0, sdcard00, sdcard000 etc). All though the sdcard folder seems clean and refreshed, the others mentioned had all my old files in there. Since I've updated to kitkat, I can no longer view these folders (I used to use Root Explorer, but now since the kitkat install - I can't). What caused me to notice was the fact that my storage, in the 'Other:' section, shows 20GB out of 32. So, I used ES File Mgr to see if I can create some space by deleting the so-called backup folders. I think that was a bad mistake because now, even after a full data wipe, I still can't:
* Install root-required apps
* flash the zip file you provided
* use the exe version of the zip you provided (still get an error with that as well)
* Clear the 20gb of data I don't need
* get back to the At&t carrier brand from the Developer's Edition that i switched it to back last summer.
Fortunately the phone works fine, but is this hopeless? Anything I can do to get this going again (really thing I messed things up)
Is there anything else I can try?
thank you,
infg3570
Hi
I have At&t HTC One M7 with stock rom on it. Android version is 4.3. S-on. I am outside the US so I can't get the At&t OTA.
I tried to update by RUU. The one for 4.4 and the one for 5.0. It stops after 5%. I also tried by Zip on the device itself and it gives me error of 'invalid operation'.
Any one knows how to get this updates work?
Thanks!
oferpelled said:
Hi
I have At&t HTC One M7 with stock rom on it. Android version is 4.3. S-on. I am outside the US so I can't get the At&t OTA.
I tried to update by RUU. The one for 4.4 and the one for 5.0. It stops after 5%. I also tried by Zip on the device itself and it gives me error of 'invalid operation'.
Any one knows how to get this updates work?
Thanks!
Click to expand...
Click to collapse
You can try this:
Unlock your bootloader
Install TWRP custom recovery
GURU Reset 5.12.502.2
When exiting TWRP select Stock Recovery
Lock your bootloader:
Code:
fastboot oem lock
Run the latest RUU: http://forum.xda-developers.com/htc-one-att/general/capture-3-31-15-lollipop-ota-update-ruu-t3070978
The cell is not rebooting into the system, it stays on the HTC logo until the battery runs out.
I can boot into TWRP with no problem. :good:
I think all system got wiped. :crying:
I downloaded from HTC the: RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
But it is not working because it can't connect, I supposed it needs the system to work.
How can I unbrick my cell? I have never flashed a ROM before from TWRP, so I don't know exactly what is the file I need to download or the commands. The good news is that I do devOps so I'm used to the shell.
Can someone give me some guidance? :fingers-crossed:
Thanks!
That isn't the right RUU for the AT&T version. You would need to have the US Developer's Edition, or else have s-off and change to the Dev Ed CID or SuperCID, to use the "Brightstar" RUU. If you have the AT&T version, and still on the ATT CID, you need to use an AT&T RUU. I have them listed here: https://forum.xda-developers.com/showthread.php?t=2751432
You don't need a working system/OS to use RUU. But you will need to be in bootloader-fastboot mode (in recovery won't work), and relocked bootloader to RUU (unless s-off, in which case unlocked bootloader is okay). IF you meet all the requirements, and still having USB connection issues, you should try to re-install HTC Sync and HTC Drivers, try another USB cable, and try another USB port on the PC.
If you choose to flash a ROM in TWRP, all you need to do is get a ROM from one of the development threads:https://forum.xda-developers.com/htc-one-m8/development
https://forum.xda-developers.com/htc-one-m8/orig-development
Then you can copy the ROM to the phone's storage using TWRP (to browse the storage); or alternately put the ROM on SD card, using a USB card reader. Then go to "Install" in TWRP and flash the ROM. This also assumes you phone is on relatively recent firmware (Lollipop or Marshmallow is okay for the current ROMs).
Thanks!
For some reason my device is S-On but it is rooted and I have installed TWRP
Please watch this image, it is a picture of the radios, data and all that. thanks!
http://prntscr.com/f11z85
I'm currently downloading the official RUU 4.28.502.1 (Android 5.0.2) from the list you sent me. thanks
By the way, I remember I paid for SunShine to s-off my device some time ago. For some reason, I did S-on again. I'm an idiot right!
I download today SunShine but it is an APK, how don't know how to install it with no system. am I screwed?
From the radio number on your screenshot, I believe it's on AT&T firmware (radio numbers for this phone starting "4.0...." are unique to AT&T). So therefore, the AT&T RUU should work.
But if you want me to determine more definitely, do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
You can't use sunshine with no OS. I agree that making the phone s-on was a mistake, as it serves little purpose unless you were returning the phone to HTC for warranty. But s-off is not needed to recover the phone. Simply using the proper RUU should work.
Once the phone is running properly again (can boot into OS) you can use the sunshine app, and should be able to s-off for no extra $, if you like.