Related
Hi
Does anybody know where i can find One S (S4) odex stock roms for tmobile. Basically i can't get ota updates and i think my problem is that my current stock rom is deodex.
none of the develops in the One S community wants to make it.. dont know why....
the closest u get is the nandroid in the dev section.. thats what im running now...
Why not run a RUU from the Shipped ROMs thread in development section
I'd like it too actually. I tried flashing stock recovery and relocking my bootloader, but out still said tampered and still couldn't flash an ruu... I'm hoping getting all stock could help with that.
There are no RUU's for tmobile uk sadly, so i need to super cid my phone to get the international version. Also i dont know how to super cid
I found another version of the RUU for TMOUS so I'll try that in the near future and see what happens.
Because the cramp just won't go away!
Does anybody have a stock nandroid for tmobile UK?
Sent from my HTC One S using xda app-developers app
If you read the posts it says there isn't one. Just to verify I looked and I didn't see one either.
Also, after going into fastboot and flashing stock recovery I did
Code:
fastboot OEM lock
My phone rebooted I did it again and flashed the latest RUU for my phone which was TMOUS 1.84 or something like that.
That seemed to work. Now running android 4.0.4.
_______________________________________
Because the cramp just won't go away!
mylegiscramped said:
If you read the posts it says there isn't one. Just to verify I looked and I didn't see one either.
Also, after going into fastboot and flashing stock recovery I did
Code:
fastboot OEM lock
My phone rebooted I did it again and flashed the latest RUU for my phone which was TMOUS 1.84 or something like that.
That seemed to work. Now running android 4.0.4.
_______________________________________
Because the cramp just won't go away!
Click to expand...
Click to collapse
I'm just curious are you from UK or USA. I supercid my phone yesterday and tried flashing three different ruu's but none of them worked. But then again my bootloader is unlocked so I'm not sure whether locking it will help.
Sent from my HTC One S using xda app-developers app
I'm from us, but please don't hate me i didn't decide to be birthed here
I'm assuming your a tmobile UK user due to your post. I'm not really familiar as to what to do with your situation as I've never dealt with UK RUU Issues. I would assume you probably can't use any of the RUUs from anywhere else. You would think T-Mobile would have an international one out. I would probably not risk damaging your device using other carriers unless someone tells you it works. I don't see why trying a tmous RUU would harm you though. There are two versions of it out a 1.54 and 1.84 I believe. I don't know what effect itll have on your phone though so don't blame me if it bricks if you try.
Ive got a huge problem I supercid my phone last night and after that I couldn't call or text anyone as well as recieve. I even unsupercid my phone and back to the original HTC__001 cid. So can anyone give me a solution. Btw I relocked my bootloader and ran the European RUU and it worked
Sent from my HTC One S using xda app-developers app
Maybe try to run the RUU again? Or a factory reset.
_______________________________________
Because the cramp just won't go away!
No no this happened due to me trying to super cid. I just did the ruu right now. I think I need to flash a radio but not sure how to
Sent from my HTC One S using xda app-developers app
That's possible I suppose. Here is how.
After flashing your device properly, start it up and let everything run a few minutes so the ROM can get settled in, I assume you've done that already.
Next you download the radio image you need, I'm not sure which it is I don't know what your running.
Then reboot to fast boot.
Enter
Code:
fastboot flash radio radio.IMG
Then reboot your phone with
Code:
fastboot reboot
Or you can do it through a menu on the device.
Then you should have your radio set.
Someone please correct if anything is wrong.
_______________________________________
Because the cramp just won't go away!
My hboot version is 1.14.002
Radio-1.06s.50.02.27_2
I'm not sure which radio to flash, so could you please tell me?
P:S I'm on the S4 processor
Sent from my HTC One S using xda app-developers app
I'm not sure which radio you need. This is what I have.
HBOOT-1.14.004
RADIO-1.08ts.50.02.16
I googled quick, but haven't been able to find anything as of yet. Maybe check the wiki?
lonegunman0 said:
My hboot version is 1.14.002
Radio-1.06s.50.02.27_2
I'm not sure which radio to flash, so could you please tell me?
P:S I'm on the S4 processor
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Your not flashing any radio with that HBOOT.
HTC One S
Flash radio
fmedrano1977 said:
Your not flashing any radio with that HBOOT.
HTC One S
Click to expand...
Click to collapse
Are you saying there aren't any radios that i can flash? I'm actually considering sending this back to htc to see if they can fix it but im not sure if they will
lonegunman0 said:
Are you saying there aren't any radios that i can flash? I'm actually considering sending this back to htc to see if they can fix it but im not sure if they will
Click to expand...
Click to collapse
He is saying you CAN'T flash radios, new, old, it doesn't matter. Your hboot does not support it. You are SOL.
Hey Guys!
Bought a HTX One X from At&T and I'm trying to make it work here.
The problem is that the unlocking code I bought from ebay doesn't work. Neither worked the unlocking box used in a local smartphone store.
Will this actually work? What are my options?
http://forum.xda-developers.com/showpost.php?p=25251622&postcount=26
Forgot to mention the bootloader is unlocked and the phone is rooted!
Running King kang's rom, if that's matters for the case...
I saw someone saying earlier that you need to be on a Sense based ROM in order for a sim unlock to work.
Sent from my One XL using XDA Premium
Ok. That applies as well to the method I posted?
Then if I go back to a Sense based rom I'll be able to unlock it, right? Do I have to change back to the same kernel as well?
I'll search for a method to do so...
I'm not sure to be honest man, I vaguely remember seeing a thread somewhere here.
Sent from my One XL using XDA Premium
brunomcf said:
Hey Guys!
Bought a HTX One X from At&T and I'm trying to make it work here.
The problem is that the unlocking code I bought from ebay doesn't work. Neither worked the unlocking box used in a local smartphone store.
Will this actually work? What are my options?
http://forum.xda-developers.com/showpost.php?p=25251622&postcount=26
Click to expand...
Click to collapse
the thread you mentioned is for tegra 3 version. It may or may not work ( may result in other issues ) when you use on ATT version
---------- Post added at 07:37 PM ---------- Previous post was at 07:36 PM ----------
have you ever entered your unlock code?
brunomcf said:
Ok. That applies as well to the method I posted?
Then if I go back to a Sense based rom I'll be able to unlock it, right? Do I have to change back to the same kernel as well?
I'll search for a method to do so...
Click to expand...
Click to collapse
what you posted is for international one x and partitioning is different. so no it will not work. if you want to sim unlock your htc one xl you'll need to cough up a couple of bucks
Crappyvate said:
what you posted is for international one x and partitioning is different. so no it will not work. if you want to sim unlock your htc one xl you'll need to cough up a couple of bucks
Click to expand...
Click to collapse
I did pay for the unlock code on ebay, and it did not work.
probably because as the other user said, it has to be on Sense based rom.
I'm trying to find the topic to get back to it, but haven't suceeded yet.
Where can I find it?
Hey Guys!
I was trying to get my AT&T one X back to stock rom, using the RUU.
I've relocked first, but it won't get out of fastboot, and the RUU tool does not recognize my phone when usb connected.
I need to have it back at it's original rom, so I can sim unlock it...
ps: when trying to run the RUU I get error 170
brunomcf said:
Hey Guys!
I was trying to get my AT&T one X back to stock rom, using the RUU.
I've relocked first, but it won't get out of fastboot, and the RUU tool does not recognize my phone when usb connected.
I need to have it back at it's original rom, so I can sim unlock it...
ps: when trying to run the RUU I get error 170
Click to expand...
Click to collapse
Um ok ...... Did you grab the right ruu.....you need to be in bootloader for ruu not fastboot
I've tried in bootloader and still doesn't work.
I've also relocked it...
Checked several times the RUU and I have the right one. Unless it's damaged and I need another one...
brunomcf said:
I've tried in bootloader and still doesn't work.
I've also relocked it...
Checked several times the RUU and I have the right one. Unless it's damaged and I need another one...
Click to expand...
Click to collapse
make sure you have the right drivers installed...
Crappyvate said:
make sure you have the right drivers installed...
Click to expand...
Click to collapse
How do I know I have them? if not, where do I get them?
ps: just checked and instaled again. Seems not to be the problem
This is the RUU I'm using, and it matches with the phone's. Have no idea why it's not working and I'm freaking out...
RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7
MD5: A40CD830E8C57109D140E1E68E2D1328
https://www.dropbox.com/s/pq569ez3dteksp9/2012-11-12 12.42.34.jpg
As you can see from that image, it says "tampered" abd "security warning".
Is that preventing the RUU to update? How do I fix it?
everything it says is correct. the 2.20 ruu is the correct ruu also. your md5 for the ruu is also correct.
be in fastboot instead of hboot.
Check your drivers. What is it listed as in device manager?
What does "adb devices" return when the phone is connected?
Sent from my HTC One X using xda app-developers app
I've been running ViperXL (Bulletprrof 1.3 kernel) just fine fine for a few weeks. It's been nearly flawless. Just now, though, the backlight went out and nothing I do seems to bring it back on. I've rebooted, plugged into AC, and tried booting into recovery. In the sunlight I can see just enough to know the device is on. I've managed to get into settings, which thankfully has a white background, and verified that brightness is at max.
There is no backlight even through the reboot process.
ctennenh said:
I've been running ViperXL (Bulletprrof 1.3 kernel) just fine fine for a few weeks. It's been nearly flawless. Just now, though, the backlight went out and nothing I do seems to bring it back on. I've rebooted, plugged into AC, and tried booting into recovery. In the sunlight I can see just enough to know the device is on. I've managed to get into settings, which thankfully has a white background, and verified that brightness is at max.
There is no backlight even through the reboot process.
Click to expand...
Click to collapse
When you reboot the phone, does the boot image (Default HTC Screen) also have no backlight? Or in recovery is there a backlight? If not, it's a hardware failure. Screen would need to be replaced. If the backlight comes on when in recovery or during first boot image, then it's something software related which is easier to fix.
There's no backlight anywhere. I know it's not kernel since I was able to fastboot flash the default kernel for ViperXL over USB.
If I bought this through AT&T less than a year ago does anyone know if it's under warranty? I'd hate to pay to get the screen replaced. I'd rather try to get it back to stock and take it in.
That's assuming, of course, someone can point me to instructions for getting back to stock! I've looked but haven't seen any in the forum.
It's hardware. You need a new screen. You would need to s-off if you're not already and then run the appropriate ruu for your carrier. I believe at&t will warrant it np.
S-off directions are stickied in original android dev section and ruu's can be found in the resource compilation thread linked in my signature.
Make sure to download an executable Ile and not a zip. Easier to return to stock with exe
Sent from my HTC One X using xda app-developers app
exad said:
It's hardware. You need a new screen. You would need to s-off if you're not already and then run the appropriate ruu for your carrier. I believe at&t will warrant it np.
S-off directions are stickied in original android dev section and ruu's can be found in the resource compilation thread linked in my signature.
Make sure to download an executable Ile and not a zip. Easier to return to stock with exe
Click to expand...
Click to collapse
Thanks a ton. I'm already S-Off. I spoke with customer service and they're going to send me a replacement device (same model, though I asked if it was possible to change). Should I be using the one labeled [ruu] [stock] att 2.20 ota? There are a few whose names look like what I might want.
No you'll want one that is ruu and not ota. Doesn't matter what version so long as it's at&t. The filename will end with exe
Sent from my HTC One X using xda app-developers app
exad said:
No you'll want one that is ruu and not ota. Doesn't matter what version so long as it's at&t. The filename will end with exe
Click to expand...
Click to collapse
Ok, so like [STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502 ? And the RUU will wipe anything that's not stock, right? Thanks.
It will return your phone to stock but your bootloader will still be unlocked and you will still have s-off. You can spoof it like it's never been unlocked and return it to s-on though I doubt that would be worth the trouble.
Sent from my HTC One X using xda app-developers app
exad said:
It will return your phone to stock but your bootloader will still be unlocked and you will still have s-off. You can spoof it like it's never been unlocked and return it to s-on though I doubt that would be worth the trouble.
Click to expand...
Click to collapse
I see. So you don't think they'd bother digging too deeply to notice it's s-off and unlocked? I'll run the RUU tonight and check in later.
I really appreciate your help this evening.
Since it's a hardware issue, I doubt they'll care to dig That far into it. From what I see on here AT&T is pretty lenient about unlocked phones, especially when it's a hardware issue.
Sent from my Sony Tablet S using xda app-developers app
I'm having difficulty running the RUU. I've rebooted and connected my device to my computer and run the RUU utility. It says it can't find the device and to check the connection. I can't see the screen well enough to turn debug mode on or off on the device. What can I do to run the RUU?
Try running while in bootloader/fastboot?
Sent from my Sony Tablet S using xda app-developers app
That did it, thanks. Now to wait until the sun is bright enough out today to wipe the SD card through settings.
I'm going to miss being rooted.
Ok, I have never been more tempted to throw a phone in all my life. This has me VERY irritated.
I got this htc one x on a hunch, was a good deal, seen great roms on here, thought it was a good idea. I've had nothing but trouble. Heres my deal:
I went to the htcdev site to get the boot loader unlocked. Im no dummy, I've gotten into LOTS of phones. This thing is crazy. I've watched 20 videos, used 3 different computers, NOTHING works. ALWAYS says Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
Now this isn't my first rodeo, I read, searched, paused videos made sure I was getting the same info selected, spaces, EVERYTHING that were showing between my screen and the youtube screens. This phone has taken the latest att update. Is this the problem? Has getting into the phone been cut out? Is there another way to get in and load roms? Should I ditch it for a galaxy?
You have supercid, right? The One XL can't have bootloader unlock without it. AT&T Doesn't like for people to use phones the way they're intended to be used
There is a new method for unlocking on the latest update over in general.
Sent from my HTC One XL using xda premium
I've never owned a phone so hard to deal with... Everything I read says I need to be rooted, I need to have bootloader unlocked to root, different direction loops I cant seem to break... The noobproof all require bootloader unlocked... there is SO much info, it all points in different directions, and I cant make heads or tails out of it to be honest. I've been reading for 2 days and am about to pitch this thing as far as I can.
I cant find the directions for supercid, just what it does. I normally don't require hand holding... I have an upgrade coming in September.....
Part of my issues is I don't have a charge only mode...
what carrier did the phone come from and what software version are you on?
klloyd said:
Part of my issues is I don't have a charge only mode...
Click to expand...
Click to collapse
Newest update doesn't have this option. There's a root method in dev section, however you need linux to run the script. But that's easy to make a bootable CD just to run the script. After you root then dev unlock. Then you can proceed to either fastboot a recovery or use goo manager to install the latest. Then flash away...
I recommend you follow the S-off thread too... That way you don't need fastboot to flash boot.img. then if it came with 3.18 firmware, you'll also need to follow the touchscreen downgrade thread if you plan on using Aosp roms.
It's really not hard to do the last 2 steps, but I have to agree you need to go through an a$$load of steps to get the desired effect. But this phone is great with custom roms. Some call me crazy, but if I run carbon Rom tweaked it'll rival my buddies S4 no problem
Sent from my HTC One XL using Tapatalk 2
Its a true blue att phone. Running 4.1.1, software 3.18.
I actually run Linux on about everything... I am using my wifes computer to do all this, cause it seemed windows was easier. (insert shame here)
Im just use to the one clicks, the easy additions of clockwork in a single flash on the galaxy phones. Im not giving up, but believe you me, there is an note2 or and s4 in my future.
klloyd said:
Its a true blue att phone. Running 4.1.1, software 3.18.
I actually run Linux on about everything... I am using my wifes computer to do all this, cause it seemed windows was easier. (insert shame here)
Im just use to the one clicks, the easy additions of clockwork in a single flash on the galaxy phones. Im not giving up, but believe you me, there is an note2 or and s4 in my future.
Click to expand...
Click to collapse
*Gags a little* lol. Good luck man
Sent from my HTC One XL using Tapatalk 2
The reason info conflicts is AT&T phones cant use htcdev unlock by AT&T request.
All other evita's can use htcdev fine.
So AT&T phones need root to change cid to pretend to not be an AT&T phone before they can unlock.
Sent from my HTC One XL using xda app-developers app
As normal, wonderful help! Im on the right track this time! Thanks!
klloyd said:
Its a true blue att phone. Running 4.1.1, software 3.18.
Click to expand...
Click to collapse
If that's the case, you need to go here:
http://forum.xda-developers.com/showthread.php?t=2283760
That will change you Cid so it no longer identifies your phone as an AT&T model. Then, and only then will you be able to use htcdev to unlock your phone.
Sent from my HTC One X 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