Related
When trying to upgrade to the sprint stock system update 2.31.651 my phone just goes off comes on and just sits the four hours on the htc white screen...What should I do?
1. Ask Sprint, because this is something to do with the "official" software release
2. Learn to read
3. Remember - this is not your helpdesk
4. Most important - Read (again) and post in the right forum
Mont.21 said:
When trying to upgrade to the sprint stock system update 2.31.651 my phone just goes off comes on and just sits the four hours on the htc white screen...What should I do?
Click to expand...
Click to collapse
Try To Turn Off Your Phone, Pull The Battery Out, Put It Back In...
Then.... Power Your Phone
Back On....
"Holding The Volume-Down-Button"
Once On....
You Should See The "Hboot-Menu" Where You "SHOULD"?? Be Able To Use the "Volume-Up-Button"
To Select The "Fastboot-Menu"
Where You Can "TRY" To Perform A "Hard-Reset/Factory-Reset" By Pressing The "Menu-Button"!!
*NOTE*
Everything Will Be Erased,
Except For What On The SDCard!!
Hopefully This'll Work??
Good-Luck!!
Sent from my HERO200 using XDA App
Did you have your phone rooted?
If all else fails you're most likely going to have to run the ruu which will restore your phone to factory.
Sent from my HERO200 using XDA App
Nate14 said:
Did you have your phone rooted?
If all else fails you're most likely going to have to run the ruu which will restore your phone to factory.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
No its not rooted its everything factory
Mont.21 said:
No its not rooted its everything factory
Click to expand...
Click to collapse
There is the problem.
Mont.21 said:
No its not rooted its everything factory
Click to expand...
Click to collapse
I don't see any other solution. I believe you are going to need to run the latest ruu.
This is the latest build, http://forum.xda-developers.com/showthread.php?t=800586
Run that from you computer.
Sent from my HERO200 using XDA App
I searched and didnt find anything sorry if there something like this somewhere around here feel free to delete
Okay so i decided to go back to stock i used hansoons all in one toolkit to lock bootloader then i saved the tmobile us ruu on the phone went to bootloader and tried to flash ruu nothing happens what am i doing wrong?
blah_blah_blah_blah said:
I searched and didnt find anything sorry if there something like this somewhere around here feel free to delete
Okay so i decided to go back to stock i used hansoons all in one toolkit to lock bootloader then i saved the tmobile us ruu on the phone went to bootloader and tried to flash ruu nothing happens what am i doing wrong?
Click to expand...
Click to collapse
The RUU are not meant to be flash on your phone.
It's an .exe file which mean you run it on your Windows PC.
Connect phone to PC and go into bootloader, click on RUU_xxxx.exe <<(not exact name but you knowwhat I mean)
Follow instructions on PC screen.
baseballfanz said:
The RUU are not meant to be flash on your phone.
It's an .exe file which mean you run it on your Windows PC.
Connect phone to PC and go into bootloader, click on RUU_xxxx.exe <<(not exact name but you knowwhat I mean)
Follow instructions on PC screen.
Click to expand...
Click to collapse
Thanks for the fast respond
Im sorry would u mind walking me trough the steps im not new to rooting iv rooted befor but seems to me that htc way of unrooting is a little bit more hard :crying:
Instead of putting the RUU on your phone just put it on your PC.
Relock your bootloader if you haven't done so.
Code:
fastboot oem lock
Connect your phone to the PC using the USB cord.
Put phone in fastboot mode
Click on RUU on PC and a screen will pop up
Just follow instructions what it say to do.
baseballfanz said:
Instead of putting the RUU on your phone just put it on your PC.
Relock your bootloader if you haven't done so.
Code:
fastboot oem lock
Connect your phone to the PC using the USB cord.
Put phone in fastboot mode
Click on RUU on PC and a screen will pop up
Just follow instructions what it say to do.[/QUOT]
Makes more sence now thank you for your help :good:
Click to expand...
Click to collapse
Can you post the ruu file. And the stock recovery image. I've been looking on and off for almost a day.
Sent from my HTC One S using xda premium
mike102871 said:
Can you post the ruu file. And the stock recovery image. I've been looking on and off for almost a day.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Try here
http://forum.xda-developers.com/showthread.php?p=23542379
Can't download there without premium acct.
Sent from my HTC VLE_U using xda premium
mike102871 said:
Can't download there without premium acct.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
That's weird, that's where i got mine from and I don't have premium account.
If it under 500mb you download free . T-Mobile ruu is .like 563 or so.
Sent from my HTC VLE_U using xda premium
mike102871 said:
If it under 500mb you download free . T-Mobile ruu is .like 563 or so.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Do U need the tmobile ruu? If u do ill be uploading to my dropbox and ill post the link
Here is the link for the tmobile ruu
http://d-h.st/yAg
Sent from my HTC One S using xda premium
I looked around and didn't see a solution to my problem. I might have missed it because I'm kind of panicked right now.
My HOXL was dying really fast. Within a few hours, it falls from 80% to 0%. I wanted to factory reset because I heard that it helps the battery life.
So I followed the process I always have (I'm unlocked, rooted, and had pacman's evita ROM installed) and did a factory reset, wiped cache and dalvik cache. Then I re-flashed pacman's ROM and the gapps. When I rebooted though, it went to the HTC screen and in a few seconds it just went black. I think it might have still been on or something, but nothing was happening for like 30 minutes. I tried it over and over again, flashing new ROMs and kernels, but now all that's happening is that it's stuck on that very first HTC screen.
I downloaded the latest JB RUU for evita to try it out. But if I can't get past that first screen, is there a way to connect it? I can still get into TWRP's recovery. My HBoot is 1.09. I'm really starting to feel nervous about having to buy a new phone, yet I feel like there should be a way to fix this. Could flashing the stock kernel be all I need? I tried to download from Viper's hub, but the download just stops at 99% and doesn't finish.
Please, I would really, really appreciate any help!
I would run the 3.18 RUU (which you can do in fastboot).
Try a complete wipe: Factory reset, system, cache and dalvik cache in twrp or if it is not wiping correctly due to twrp version " 2.3......" is best fro our phones, try downloading and installing twrp again or use adb commands to wipe and flash rom again.
I've tried a complete wipe, but I just noticed that my TWRP version is 2.2.0. I tried the wipe like five or more times and it didn't work. My PC isn't reading the HOXL in the adb command window. I rooted a Sero Pro 7 this way, so I think I should have the drivers installed for it... I'm going to try installing the HTC Sync drivers and seeing if I can send adb commands to my HOXL. If this doesn't work, I'm going to try the 3.18 RUU. I heard that some people have bricked their HOXL completely doing this, but I didn't change my SuperCID and s-on (?), so would I be fine? Or would it be safer to just use the latest ICS one (RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radio _0.19as.32.09.11_2_10.105.32.25L_release_271865_si gned.exe)?
So you have no way to flash boot image separately? I would definitely try to get device recognition so adb can be used before running ruu.
Sent from my HTC One X using xda premium
Yeah, I went through the noob way of unlocking and rooting this phone, so there was no need to use adb commands. I would have liked to try that first before running RUU, but I just want to have a working phone again, even if I have to go through the whole process of unlocking and rooting.
Sent from my Nexus 7 using XDA Premium HD app
I would still try to get a good adb environment. Sometimes panic is not a good thing. Just be careful and make sure you get the proper ruu and do not let the battery die while running it. Let me know if it works.
Sent from my HTC One X using xda premium
Venomtester said:
I would still try to get a good adb environment. Sometimes panic is not a good thing. Just be careful and make sure you get the proper ruu and do not let the battery die while running it. Let me know if it works.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is what I'm worried about:
SERooted wrote: Note to OP: You really should add to the 1st post that it is not wise to flash the 3.18 firmware over super cid and s-on.. its not a good thing for most people to have a qhsb_dload turn their phone into a paper weight before finding out that they shouldn't have used that file to begin with. i had to find out the hard way. i would have flashed the ics firmware on my phone but decided to go with the big JB only to find out that it turns it into a paperweight. I understand this is no fault but my own, however this would greatly help people when choosing which ruu to run.
http://forum.xda-developers.com/showthread.php?t=2191477
I know what you mean lol. I would only do that as a last resort. I would try and get adb working since the phone is not bricked. It just seems to have no Rom or boot image. Have you tried one with an aroma installer?
Sent from my HTC One X using xda premium
Venomtester said:
I know what you mean lol. I would only do that as a last resort. I would try and get adb working since the phone is not bricked. It just seems to have no Rom or boot image. Have you tried one with an aroma installer?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Huh...I just tried flashing the UrDroid ROM because of its aroma installer, but it didn't happen in recovery, like I thought it would. It said it was successful, so I rebooted the system. It got past the initial screen with an AT&T boot img and htc one img. Now I'll have to see if it actually loads past this.
EDIT: It worked! I'm going to have to try to see if I can load boot img some other way than just an aroma installer.
You can use Flash GUI from the market to install boot images or get Goo Manager to install a 2.3..... Version of twrp. That may solve your problems.
Sent from my HTC One X using xda premium
Venomtester said:
You can use Flash GUI from the market to install boot images or get Goo Manager to install a 2.3..... Version of twrp. That may solve your problems.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Second Flash GUI....works like a charm
i was going to s-off the this morning and flash illusion 2.0 but instead i am beating my head off the keyboard. i have been reading all day. i have like 12 tabs open and my main problem is that adb isn't working. not sure what i'm doing wrong. i need to get to supercid. instructions seem easy enough. i go to command prompt, change my directory, everything good here just as usual. when i type "adb shell" i get "error: device offline" don't know what i'm doing wrong. thanks in advance.
I had the same problem. First make sure ADB debugging in advanced options is checked. Next try booting into fastboot. If your on stock try putting it into charge only mode. Try the multiple different ways
Sent from my One S using xda app-developers app
skinzy98 said:
I had the same problem. First make sure ADB debugging in advanced options is checked. Next try booting into fastboot. If your on stock try putting it into charge only mode. Try the multiple different ways
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
i'm on a custom rom. where is adb debugging? advanced options in the phone or on computer? really appreciate the response.
Its under developers option on the phone
Sent from my One S using xda app-developers app
skinzy98 said:
Its under developers option on the phone
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
do you mean usb debugging? or is adb debugging different? because i don't see adb debugging anywhere.
Check these things right here in the picture. Have USB debugging enabled and select root access and choose apps and adb
Sent from my One S using xda app-developers app
only1penny said:
do you mean usb debugging? or is adb debugging different? because i don't see adb debugging anywhere.
Click to expand...
Click to collapse
It's usb debugging that you need to check. You mentioned that you are on a custom rom ... Is it sense based or aosp? I was still on the stock ics rom when I changed to super cid. Everything went just fine, although I didn't proceed to do Facepalm s-off immediately. I did flash cm10, and came back to finish s-off a couple of weeks later. Nearly drove myself crazy, until I realized it works best when done on a sense rom. Flashed a stock rooted rom, and it literally took about 10 minutes to finish s-off. Restored my cm10 backup, and all is well.
I really appreciate the info. I'm on bb8, which isn't sense. I have USB debugging on. Should I be on a stock rpm to get supercid or just for s-off? My problem is adb won't my phone.
Sent from my HTC One S using xda app-developers app
ok so, back on task...i can not get adb to work. i'm trying to get supercid. i can't find anything on adb. i get "error: device offline"
And you've tried putting it into fast boot? Also have you set up android SDK?
Sent from my One S using xda app-developers app
skinzy98 said:
And you've tried putting it into fast boot? Also have you set up android SDK?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
what do you mean by tried putting it into fast boot? & by that i mean i thought it had to be in fastboot. also, i believe i have sdk set up but that's maybe where i'm going wrong. in cmd i actually got it to say "daemon started successfully" which it's suppose to, but then it said "error: device not found" not sure what i'm doing wrong.
only1penny said:
what do you mean by tried putting it into fast boot? & by that i mean i thought it had to be in fastboot. also, i believe i have sdk set up but that's maybe where i'm going wrong. in cmd i actually got it to say "daemon started successfully" which it's suppose to, but then it said "error: device not found" not sure what i'm doing wrong.
Click to expand...
Click to collapse
Fast boot is when you boot into boot loader using power + volume down. Once you get to boot loader there's an option for fast boot use you power button to select it
Sent from my One S using xda app-developers app
skinzy98 said:
Fast boot is when you boot into boot loader using power + volume down. Once you get to boot loader there's an option for fast boot use you power button to select it
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
yes, i'm familiar with fastboot. no luck.
Dir you install android SDK with the guide here on xda
Sent from my One S using xda app-developers app
skinzy98 said:
Dir you install android SDK with the guide here on xda
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
yes, i'm not that familiar with it, but i did install it. & it just won't read my device.
Neither was I. Their is one more thing I wanna try. Download a galaxy nexus toolkit. And tell use it to install ADV drivers onto your computer
Sent from my One S using xda app-developers app
skinzy98 said:
Neither was I. Their is one more thing I wanna try. Download a galaxy nexus toolkit. And tell use it to install ADV drivers onto your computer
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
i serched the android sdk guide and it looks like i have everything in order. i will dl the gn toolkit. also, i've heard that some things work better with a sense rom. i did switch to trickdroid, which has wifi issues and will not be a daily driver, but i can't remember if it was with scid or s-off or something else.
only1penny said:
i serched the android sdk guide and it looks like i have everything in order. i will dl the gn toolkit. also, i've heard that some things work better with a sense rom. i did switch to trickdroid, which has wifi issues and will not be a daily driver, but i can't remember if it was with scid or s-off or something else.
Click to expand...
Click to collapse
Wheni cid I was on stock and was able to choose charge only mode
Sent from my One S using xda app-developers app
skinzy98 said:
Wheni cid I was on stock and was able to choose charge only mode
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
if the gn toolkit doesn't work i'll have to give that a try. i'm tmobile us. which is the correct ruu i should flash if i want to try that? i read about don't get the ota updates. your help is greatly appreciated.
i fired up the toolkit and it says there is an update. but it wants version. i'll put a gsm version but should i put 4.2.2 or 4.1.2 or something different?
only1penny said:
if the gn toolkit doesn't work i'll have to give that a try. i'm tmobile us. which is the correct ruu i should flash if i want to try that? i read about don't get the ota updates. your help is greatly appreciated.
i fired up the toolkit and it says there is an update. but it wants version. i'll put a gsm version but should i put 4.2.2 or 4.1.2 or something different?
Click to expand...
Click to collapse
It doesn't matter. Don't hook your phone up with the toolkit. Also what's your hbootM
Sent from my One S using xda app-developers app
I am currently stuck in the bootloader. To make matters worse, I relocked to RUU and am stuck at Sending with that. I am Super CID which I think is the problem. To make matters even worse, I no longer have my unlock_code.bin file.
Is there any hope for my phone? Also, the RUU process has completely wiped my phone. Thanks for any input in advance. I have searched and searched for an answer but haven't found anything useful.
Sent from my HTC One XL using XDA Premium 4 mobile app
You haven't given enough information, what are you trying to do? You could just unlock your bootloader again.
Sent from my Evita
timmaaa said:
You haven't given enough information, what are you trying to do? You could just unlock your bootloader again.
Sent from my Evita
Click to expand...
Click to collapse
How can I unlock my bootloader without the unlock_code.bin file? Update. I reverted back to original CID CWS__001 and am going to try and run the RUU again.
I tried to s-off my wife's phone and it screwed it up somehow (rather I screwed it up). I simply wanted to take it back to stock to start fresh and now I am stuck in the bootloader with no Rom and a locked phone.
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
How can I unlock my bootloader without the unlock_code.bin file? Update. I reverted back to original CID CWS__001 and am going to try and run the RUU again.
I tried to s-off my wife's phone and it screwed it up somehow (rather I screwed it up). I simply wanted to take it back to stock to start fresh and now I am stuck in the bootloader with no Rom and a locked phone.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You would just go to htcdev like you did in the first place and go through the unlock process again. But, you can't do that now because you just changed the CID back to CWS__001 which is blocked by htcdev. And I'm guessing you didn't succeed in getting s-off? If so, you've just used the one and only time you can change the CID without s-off to change it to a CID which is blocked, which means you have no way to unlock the bootloader again, ever. I hope your original plan was to stay stock because that's your only option now. Maybe that's for the best though, you seem to be doing things without fully comprehending what you're doing or the potential catastrophic results.
Sent from my Evita
timmaaa said:
You would just go to htcdev like you did in the first place and go through the unlock process again. But, you can't do that now because you just changed the CID back to CWS__001 which is blocked by htcdev. And I'm guessing you didn't succeed in getting s-off? If so, you've just used the one and only time you can change the CID without s-off to change it to a CID which is blocked, which means you have no way to unlock the bootloader again, ever. I hope your original plan was to stay stock because that's your only option now. Maybe that's for the best though, you seem to be doing things without fully comprehending what you're doing or the potential catastrophic results.
Thanks for your input. I appreciate it. Can I at least ruu the 3.18 now and get back to stock... That's better than bootloader I suppose. By the way, how could I have unlocked in the state I was in?
Ruu is stuck at sending for some time now.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
//JavaJ said:
timmaaa said:
You would just go to htcdev like you did in the first place and go through the unlock process again. But, you can't do that now because you just changed the CID back to CWS__001 which is blocked by htcdev. And I'm guessing you didn't succeed in getting s-off? If so, you've just used the one and only time you can change the CID without s-off to change it to a CID which is blocked, which means you have no way to unlock the bootloader again, ever. I hope your original plan was to stay stock because that's your only option now. Maybe that's for the best though, you seem to be doing things without fully comprehending what you're doing or the potential catastrophic results.
Thanks for your input. I appreciate it. Can I at least ruu the 3.18 now and get back to stock... That's better than bootloader I suppose. By the way, how could I have unlocked in the state I was in?
Ruu is stuck at sending for some time now.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you have a locked bootloader and the correct CID there should be no harm in running the RUU. The unlock process (from memory, I could be wrong) doesn't require the phone to be booted into an os, it's all taken care of while the phone is in bootloader. That's kinda irrelevant now anyway as it isn't possible anymore.
Are you using the usb cable that came with the phone? You can try using a different usb port, usually the ones on the back of the pc tower are the best.
May I ask, how exactly do you think the s-off process screwed up the phone? It either succeeds or fails, and there should be no serious repercussions from either.
Sent from my Evita
Click to expand...
Click to collapse
Ever since I ran the s off process I couldn't copy anything to the sd card, I.e. to flash a new Rom. I feel like an idiot for changing the cid back now. I ran the zip for s off and I waited an hour or so and it never went throufh
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
Ever since I ran the s off process I couldn't copy anything to the sd card, I.e. to flash a new Rom. I feel like an idiot for changing the cid back now. I ran the zip for s off and I waited an hour or so and it never went throufh
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It sounds to me like you might have actually done a factory reset from bootloader which corrupts the sd card. The s-off process has no ability to change the sd card. Did you have HTC drivers and adb/fastboot all installed when you tried the s-off process? That's probably why it didn't work.
The corrupted sd card might be why the RUU won't work, can you still get into TWRP recovery? If so, you can use the mount menu to mount it to your pc and format it. If not, you might seriously be in trouble. The combination of these things you've done have possibly rendered the device completely useless. If this if the case, I hope this has been a learning experience. It's really important to have a firm understanding of what you're doing (and the results and potential risks) when modifying your device. It looks like you've rushed into all this without understanding it all properly.
In any case, let me know about what I asked about above and I'll do my best to see if there's a way out of this.
Sent from my Evita
timmaaa said:
It sounds to me like you might have actually done a factory reset from bootloader which corrupts the sd card. The s-off process has no ability to change the sd card. Did you have HTC drivers and adb/fastboot all installed when you tried the s-off process? That's probably why it didn't work.
The corrupted sd card might be why the RUU won't work, can you still get into TWRP recovery? If so, you can use the mount menu to mount it to your pc and format it. If not, you might seriously be in trouble. The combination of these things you've done have possibly rendered the device completely useless. If this if the case, I hope this has been a learning experience. It's really important to have a firm understanding of what you're doing (and the results and potential risks) when modifying your device. It looks like you've rushed into all this without understanding it all properly.
In any case, let me know about what I asked about above and I'll do my best to see if there's a way out of this.
Sent from my Evita
Click to expand...
Click to collapse
Took your advice about the usb port. Switched it to the back and the ruu worked. Will I be able to run the root exploit again? Yes, this definitely has been a learning experience. Coupled with my lack of sleep and overall frustration I made some bad moves. Thanks for your patience and help though. Much appreciated.
And no, I could not get back into recovery after I relocked it. It would send me right back to the bootloader. Also, I did do a factory reset from the bootloader. Believe me, taking mental notes all the way here.
Sent from my HTC One XL using XDA Premium 4 mobile app
Now that you have a working os, you could be able to use the exploit again to unlock the bootloader etc. Just take it slowly though, do some reading so you gain a bit of knowledge. And if you have any questions, don't be afraid to ask.
Sent from my Evita
Unlocked and rooted. Again. Thanks for your help. Leary of trying to s off again though
Sent from my HTC One XL using XDA Premium 4 mobile app
Very glad to see you got it all working again. S-off might seem daunting now, but it's a pretty straight forward process as long as you follow the instructions exactly.
Sent from my Evita
timmaaa said:
Very glad to see you got it all working again. S-off might seem daunting now, but it's a pretty straight forward process as long as you follow the instructions exactly.
Sent from my Evita
Click to expand...
Click to collapse
Yes, I have done it before, on my One X. Not quite sure what went wrong. Maybe the issue with my wife's phone was preexisting and reared it's ugly head in the process. I have been rooting and nodding phones for years. I am not a complete noob. I am experienced in java programming and have created many interesting applications for my phone. Perhaps I should take my java knowledge and automate my s off experience.
Sent from my HTC One XL using XDA Premium 4 mobile app
If you're looking for an automated method, I saw this just before. It's brand new but it looks to have some great tools incorporated. I prefer the manual method myself but many people will love this.
Sent from my Evita
timmaaa said:
If you're looking for an automated method, I saw this just before. It's brand new but it looks to have some great tools incorporated. I prefer the manual method myself but many people will love this.
Sent from my Evita
Click to expand...
Click to collapse
Very nice found Tim.....:thumbup:
Swyped From BlueICESense_JBE
timmaaa said:
If you're looking for an automated method, I saw this just before. It's brand new but it looks to have some great tools incorporated. I prefer the manual method myself but many people will love this.
Sent from my Evita
Click to expand...
Click to collapse
Appreciate it. I don't mind working from the command line either. Could my trouble have had anything to do with being plugged into the front of the cpu, for s off that is? Was getting stuck at sending with the flash zip command.
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
Appreciate it. I don't mind working from the command line either. Could my trouble have had anything to do with being plugged into the front of the cpu, for s off that is? Was getting stuck at sending with the flash zip command.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah that was probably it, try again using the rear port and it'll probably be fine.
Sent from my Evita
timmaaa said:
Yeah that was probably it, try again using the rear port and it'll probably be fine.
Sent from my Evita
Click to expand...
Click to collapse
Just wanted to let you know that I went through s off and all went well. Only thing I can think was the problem was that either there was a pre existing corruption on the phone, or the usb port I was using.
Sent from my HTC One XL using XDA Premium 4 mobile app
It could have been anything. It's becoming more and more apparent that different things halt the process for different users. It makes it really difficult to troubleshoot when helping someone through the process. In the end you got it though which is great.
Sent from my Evita