Go Back   Android Forums > Android Phones > HTC One > (AT&T) One - All Things Root

test: Reply
 
LinkBack Thread Tools
Old February 7th, 2014, 05:04 PM   #1 (permalink)
Member
Thread Author (OP)
 
Savage Shadows's Avatar
 
Join Date: Jun 2012
Location: Phoenix, AZ
Gender: Male
Posts: 354
 
Device(s): TMobile Nexus 4 16GB, Samsung Galaxy SII, Samsung Galaxy Prevail, HTC EVO Design 4g
Carrier: TMobile

Thanks: 25
Thanked 139 Times in 72 Posts
Sad No idea where to turn

So, I used to be an avid tinkerer, could get my way around most devices. That was about a year and a half ago. Then I got a Nexus 4, found Paranoid Android, and never had anything to worry about again. Recently, I switched to the HTC One. I got it used, clean numbers and all, nothing to worry about. What I didn't know until I picked it up, is that it was an unlocked AT&T model. It worked great, and then I started to change some things. I have no idea about the kernel, but it had TWRP installed, as well as CM 10.x (I just know that it was still on a Jelly Bean build). I went to flash CWM because that is what I'm used to and comfortable with, then proceeded to flash Paranoid Android 3.99 RC2. After that, it would no longer recognize my sim card, among other problems like not being able to communicate with the camera. I first noticed the sim problem when I went to input the proper APN settings for TMobile.

Where I'm at now.
I'm trying to reinstall TWRP because of course I made a backup before doing anything at all. However, I cannot get adb to push it. When the phone is fully booted up, through the command "adb devices" I get,
Code:
C:\fastboot>adb devices
List of devices attached
HT3A9W904144    offline
However, when I run "adb devices" while the phone is in fastboot, I get an empty list of devices. Also, when I run "fastboot flash recovery recovery.img", I get
Code:
C:\fastboot>fastboot flash recovery recovery.img
target reported max download size of 1526722560 bytes
error: cannot load 'recovery.img': No error
Now, I'm not really as versed in coding languages as I'd like to be, but that makes no sense to me at all since the recovery file is only just over 9MB and it said the max download size is near 1.5GB. Not to mention the "No error" error.

If it helps anything, here is the information displayed in my bootloader/fastboot pages:
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4T.20.3218.13
OpenDEP-v31.120.274.0617
OS-3.17.502.3
eMMC-boot 2048MB
Oct  4 2013,00:49:44.0

Now, I need to be able to install TWRP again so I can restore my device to working order. Is there anybody with advice?




ps: I'm running windows 7 home premium 64bit. For anybody I deem trustworthy, you're welcome to help out through remote desktop by means of teamviewer if that helps. Just ask me first.

Advertisements
__________________
Want to share something? Do it for free! http://db.tt/TZm94Al2
Have I helped you? Hit thanks!
Savage Shadows is offline  
Reply With Quote
sponsored links
Old February 7th, 2014, 08:34 PM   #2 (permalink)
Senior Member
 
Join Date: Apr 2013
Location: FLA. USA
Posts: 621
 
Device(s): iPhone 4S,HTC One
Carrier: AT&T

Thanks: 65
Thanked 532 Times in 382 Posts
Default

Quote:
Originally Posted by Savage Shadows View Post
So, I used to be an avid tinkerer, could get my way around most devices. That was about a year and a half ago. Then I got a Nexus 4, found Paranoid Android, and never had anything to worry about again. Recently, I switched to the HTC One. I got it used, clean numbers and all, nothing to worry about. What I didn't know until I picked it up, is that it was an unlocked AT&T model. It worked great, and then I started to change some things. I have no idea about the kernel, but it had TWRP installed, as well as CM 10.x (I just know that it was still on a Jelly Bean build). I went to flash CWM because that is what I'm used to and comfortable with, then proceeded to flash Paranoid Android 3.99 RC2. After that, it would no longer recognize my sim card, among other problems like not being able to communicate with the camera. I first noticed the sim problem when I went to input the proper APN settings for TMobile.

Where I'm at now.
I'm trying to reinstall TWRP because of course I made a backup before doing anything at all. However, I cannot get adb to push it. When the phone is fully booted up, through the command "adb devices" I get,
Code:
C:\fastboot>adb devices
List of devices attached
HT3**********    offline
However, when I run "adb devices" while the phone is in fastboot, I get an empty list of devices. Also, when I run "fastboot flash recovery recovery.img", I get
Code:
C:\fastboot>fastboot flash recovery recovery.img
target reported max download size of 1526722560 bytes
error: cannot load 'recovery.img': No error
Now, I'm not really as versed in coding languages as I'd like to be, but that makes no sense to me at all since the recovery file is only just over 9MB and it said the max download size is near 1.5GB. Not to mention the "No error" error.

If it helps anything, here is the information displayed in my bootloader/fastboot pages:
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4T.20.3218.13
OpenDEP-v31.120.274.0617
OS-3.17.502.3
eMMC-boot 2048MB
Oct  4 2013,00:49:44.0
Now, I need to be able to install TWRP again so I can restore my device to working order. Is there anybody with advice?




ps: I'm running windows 7 home premium 64bit. For anybody I deem trustworthy, you're welcome to help out through remote desktop by means of teamviewer if that helps. Just ask me first.
what version of TWRP ?
and did you try and clear the cache ?

boot to bootloader (power + vol down)
plug phone into PC
you should be in fastboot USB
from your fastboot/adb folder open command prompt and type fastboot devices
if your s/n shows proceed to
fastboot getvar all
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader

paste the results in your reply

you can download TWRP here Techerrata Downloads - Browsing m7
clsA is offline  
Reply With Quote
The Following User Says Thank You to clsA For This Useful Post:
scotty85 (February 8th, 2014)
Old February 8th, 2014, 03:44 PM   #3 (permalink)
Member
Thread Author (OP)
 
Savage Shadows's Avatar
 
Join Date: Jun 2012
Location: Phoenix, AZ
Gender: Male
Posts: 354
 
Device(s): TMobile Nexus 4 16GB, Samsung Galaxy SII, Samsung Galaxy Prevail, HTC EVO Design 4g
Carrier: TMobile

Thanks: 25
Thanked 139 Times in 72 Posts
Default

Ugh. Complete (and very extended) derp moment on my part. Rebooted the laptop, and communication issues went away. Successfully restored, no issues I can find yet and it's been nearly twenty four hours.

I can supply any information later (on my way to work right now), but any tips on how to prevent such issues when I try again? I usually take all the regular precautions by habit, so other than mistakes due to lack of experience with carrier unlocked devices, I'm not sure where I went wrong.
Savage Shadows is offline  
Reply With Quote
The Following User Says Thank You to Savage Shadows For This Useful Post:
scotty85 (February 8th, 2014)
Old February 8th, 2014, 04:33 PM   #4 (permalink)
AF Addict
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 11,014
 
Device(s):
Carrier: Not Provided

Thanks: 7,893
Thanked 7,228 Times in 4,485 Posts
Default

Quote:
Originally Posted by Savage Shadows View Post
but any tips on how to prevent such issues when I try again?
wich issues? the comunications errors are part of using windows,wich require prollematic drivers and are sensitive to other programs that attempt to comunicate with the device,espeically with newer versions.

usb hubs and usb 3.0 are also notoriously prollematic.

best tip i can think of is dont use windows

other than that, small errors are just part of it. this is a general windows checklist i throw out whenever folks have connectivity issues(windows 8 and usb 3.0 specific fixes not included):






having said all that,i have had pretty good luck with windows 7 32 bit,but after having some issues with newer phone tools and firwewall/antivirus conflicts,i use ubuntu for any "delicate" phone work.

if youre refering to the issues you had with your paranoid android install,thats a little tougher. biggest thing is to check the integrity of your downloads by comparing md5 sums,and make sure you do a "full wipe" whenever you install a new rom. even when the new rom uses a similar or same base, you never know what issues can arise from not doing a factory reset.
__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers.
donate to my device fund
scotty85 is online now  
Reply With Quote
Old February 10th, 2014, 06:35 AM   #5 (permalink)
Senior Member
 
dibblebill's Avatar
 
Join Date: Feb 2012
Location: Raleigh, NC
Gender: Male
Posts: 2,028
 
Device(s): Active Devices: Asus Padfone X, HTC One (m7att), Ouya
Carrier: AT&T

Thanks: 214
Thanked 344 Times in 280 Posts
Send a message via AIM to dibblebill Send a message via Yahoo to dibblebill
Default

If possible, get yourself a Ubuntu hard drive or partition and use that- much more reliable for ADB/fastboot than Windows.
__________________
Lord of the Snarkô
ROM's:
Tempest [OmniROM] 4.4 (Manta) (m7att)
dibblebill is online now  
Reply With Quote
The Following User Says Thank You to dibblebill For This Useful Post:
scotty85 (February 10th, 2014)
Reply


Go Back   Android Forums > Android Phones > HTC One > (AT&T) One - All Things Root
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 05:43 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.