Related
Hi All,
I need help for the following issue,
today i got notified by my incredible S that a software update is available,
I accepted and downloads starts, finished, choose install and the system checked the downloaded package, then phone rebooted to start the installation, then a blue android logo appear on the screen along with "!" inside a triangle, and phone was stuck on this for more then an hour before i took out the battery and restarted it and it is now back normal but on 2.3.5
anyone faced this matter and found a solution???
the phone is rooted, unlocked bootloader via HTCDEV website, and all the crappy HTC application uninstalled including htc sense and everything.
any help will be very appreciated,
thanks.
Problem solved:
-relock the bootloader:fastboot oem lock
-create a gold card: http://androidforums.com/desire-s-all-things-root/500543-guide-how-create-goldcard.html
-download the ICS RUU suitable for your phone: http://d-h.st/users/Inferi0r/?fld_id=2601#files
-put the gold card in the phone then run the RUU
DONE
20545ZR16 said:
Hi All,
I need help for the following issue,
today i got notified by my incredible S that a software update is available,
I accepted and downloads starts, finished, choose install and the system checked the downloaded package, then phone rebooted to start the installation, then a blue android logo appear on the screen along with "!" inside a triangle, and phone was stuck on this for more then an hour before i took out the battery and restarted it and it is now back normal but on 2.3.5
anyone faced this matter and found a solution???
the phone is rooted, unlocked bootloader via HTCDEV website, and all the crappy HTC application uninstalled including htc sense and everything.
any help will be very appreciated,
thanks.
Click to expand...
Click to collapse
unroot. relock bootloader. thats your problem
naathaanb96 said:
unroot. relock bootloader. thats your problem
Click to expand...
Click to collapse
thanks for the reply, will try to do it later this night
sorry for my noob question, is there a way yet to root after the update to 4.0?
BTW, phone still S ON.
20545ZR16 said:
thanks for the reply, will try to do it later this night
sorry for my noob question, is there a way yet to root after the update to 4.0?
BTW, phone still S ON.
Click to expand...
Click to collapse
if you dont wanna lose it all, go to development, tpbklake posted the stock ics update pre rooted. and you can flash in recovery like a normal custom rom. http://forum.xda-developers.com/showthread.php?t=1756500
HTC Incredible cant update
hi im from malaysia
i've checked my htc incredible s for an ics update manually, but it says "Your phone is up to date". I have android gingerbread now. Can anybidy help? i need an ics update... thanks a lot
KennyAppllez said:
hi im from malaysia
i've checked my htc incredible s for an ics update manually, but it says "Your phone is up to date". I have android gingerbread now. Can anybidy help? i need an ics update... thanks a lot
Click to expand...
Click to collapse
if you can flash custom roms, flash the one from the link above ^
naathaanb96 said:
if you dont wanna lose it all, go to development, tpbklake posted the stock ics update pre rooted. and you can flash in recovery like a normal custom rom. http://forum.xda-developers.com/showthread.php?t=1756500
Click to expand...
Click to collapse
thanks for the link,
do you know if it works for
HBOOT-2.01.001
RADIO-3822.01.0814_M
S-ON
I can flash the image via fastboot as describe in the original thread of the rom
should i perform a factory reset, wipe data and dalvik before flashing?
thanks again
Edit: after searching the ROM thread, it will not work on HBOOT 2.01.001
20545ZR16 said:
thanks for the link,
do you know if it works for
HBOOT-2.01.001
RADIO-3822.01.0814_M
S-ON
I can flash the image via fastboot as describe in the original thread of the rom
should i perform a factory reset, wipe data and dalvik before flashing?
thanks again
Edit: after searching the ROM thread, it will not work on HBOOT 2.01.001
Click to expand...
Click to collapse
Downgrade. Use the all in one noob guide in development
Sent from my Incredible S using xda premium
20545ZR16 said:
Hi All,
I need help for the following issue,
today i got notified by my incredible S that a software update is available,
I accepted and downloads starts, finished, choose install and the system checked the downloaded package, then phone rebooted to start the installation, then a blue android logo appear on the screen along with "!" inside a triangle, and phone was stuck on this for more then an hour before i took out the battery and restarted it and it is now back normal but on 2.3.5
anyone faced this matter and found a solution???
the phone is rooted, unlocked bootloader via HTCDEV website, and all the crappy HTC application uninstalled including htc sense and everything.
any help will be very appreciated,
thanks.
Click to expand...
Click to collapse
OK, so if you have modded the stock ROM by removing HTC applications and Sense, then that is why the OTA update failed.
To accept and install the OTA you must have all the stock components in place, HBOOT, recovery and all the apps.
Download the stock ice ruu exe from the thread listing in the dev section.
Make a goldcard and then install.
Remember this method I think will work with a compleatly stock phone meaning s-on locked bootloader, no root and no custom recovery. Do this at your own risk. I have a inc s with cid 38, It worked for me.
Sent from my HTC Incredible S using xda app-developers app
tpbklake said:
OK, so if you have modded the stock ROM by removing HTC applications and Sense, then that is why the OTA update failed.
To accept and install the OTA you must have all the stock components in place, HBOOT, recovery and all the apps.
Click to expand...
Click to collapse
i have checked your suggested rom but it seems not to work with my S ON hboot version
would it help if i do the following?:
restore all the stock application from titanium backup
and then try to accept the OTA update?
or as naathaanb96 suggested to simply unroot, lock bootloader?
i have tried to unroot using htc tool V3 with no luck: http://forum.xda-developers.com/showthread.php?t=1343114
thanks
abhijay.jagini said:
Download the stock ice ruu exe from the thread listing in the dev section.
Make a goldcard and then install.
Remember this method I think will work with a compleatly stock phone meaning s-on locked bootloader, no root and no custom recovery. Do this at your own risk. I have a inc s with cid 38, It worked for me.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
20545ZR16 said:
i have checked your suggested rom but it seems not to work with my S ON hboot version
would it help if i do the following?:
restore all the stock application from titanium backup
and then try to accept the OTA update?
or as naathaanb96 suggested to simply unroot, lock bootloader?
i have tried to unroot using htc tool V3 with no luck: http://forum.xda-developers.com/showthread.php?t=1343114
thanks
Click to expand...
Click to collapse
As the previous poster suggested, just relock the bootloader and then run the official ICS RUU using a goldcard.
Then since you have unlocked your bootloader before, you can simply use the same unlock_code.bin to unlock the ICS bootloader and then you can add a custom recovery and root the system.
Before you guys jump on me, I would like to apologize for just being dumb. Even though that is the truth, may I have some help?
I didn't read the guide on turning the S-Off on my Vivid, I thought all I had to do was run the hason s-off and it would automatically do everything for me. Yeah, I didn't even know about a wire trick (I've already admitted the obvious). My Vivid just boots to the JoupunutBear screen and reboots after about 3 minutes to the same screen. I guess I've bricked my device!:crying:
Is it possible for HTC to remotely restore my Vivid, or do I have to take it to an authorized dealer that repair phones? If so, how much am I looking at? I wished I had left my phone alone, but doing some of the crazy wild and exciting stuff for phones is so cool! I wish I had read that I needed to pin mod something, or else I would not have tried to do S-Off! I just got my phone a few days ago in a trade for my HTC Shift.
I guess this will be an expensive lesson and hopefully I'll read and not think every procedure for different phones are the same.
I miss my Vivid!:crying:
Use flashtool and flash stock rom .....
Sent from my E15 using Tapatalk 2
bandarigoda123 said:
Use flashtool and flash stock rom .....
Sent from my E15 using Tapatalk 2
Click to expand...
Click to collapse
I thought as long as I had reovery image on my device, I had nothing to worry about. Boy was I wrong!
Any tips on which recovery I should use? Preferably with guide, my nerves are a bit tweaked right now.
OK, I just relocked...now what?
Downloaded AT&T stock ROM, downloaded AT&T PH39img. I guess now I'm suppose to place both files on SD card and use HBOOT?
Follow the guide in my signature titled "back to stock" (I think its step 6). Then if you want to re root or whatever follow the guide in my signature steps 1-4.
Sent from my HTC PH39100 using xda premium
Double post
slapshot30 said:
Follow the guide in my signature titled "back to stock" (I think its step 6). Then if you want to re root or whatever follow the guide in my signature steps 1-4.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Following your guide now, I'll let you know how it goes.
I have to download the RUU and not use the AT&Tzip I've already have downloaded. Seems straight forward, I'll reply back, thanks!
Since I have some time before the RUU finishes downloading, I tried to reflash factory rom using the second method. When I reboot into recovery, it does load the PG file, but it doesn't give me an option to flash anything?
Just a heads up...for me ruu never worked with a unlocked bootloader so if it doesn't work relock your bootloader with the super tool thing in he dev section...just boot into fastboot from hboot and click relock bootloader, then boot back to fastboot and run the ruu
Sent from my HTC PH39100 using xda app-developers app
mg2195 said:
Just a heads up...for me ruu never worked with a unlocked bootloader so if it doesn't work relock your bootloader with the super tool thing in he dev section...just boot into fastboot from hboot and click relock bootloader, then boot back to fastboot and run the ruu
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
thats the easiest way to do it
kobe_24 said:
Since I have some time before the RUU finishes downloading, I tried to reflash factory rom using the second method. When I reboot into recovery, it does load the PG file, but it doesn't give me an option to flash anything?
Click to expand...
Click to collapse
The beginning of step 6 requires you to relock the bootloader. Otherwise, the RUU or PH zip will not work.
Sent from my HTC PH39100 using xda premium
Man this download is taking long, I still have 15 percent to go (6 minutes)!
I guess I have to have the RUU for any of this to work, so I'll stop playing around with it before I render the device useless. So I'll be patient since I have 5 minutes to go, then I should be able to perform any of the two methods found in the guide. I'm so glad there are so many here to help me, I love you guys! Don't be too flattered, I love my Vivid more! Once this is done, I'll thank each and every one of you!
OK all, I have to leave for right now. I started the RRU utility, but it stops at checking signatures.
ERROR (155) Unknown error
The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I have an AT&T Vivid, I thought the one for Holiday Cingular was the correct one? On the phone it says RUU update failed. So I'll look into it when I get back and try then. For some reason I can't update the HBOOT?
Bye for now!
I bet you can't update the bootloader while it is locked, LOL!
As said...I'll look into it when I get back.
kobe_24 said:
OK all, I have to leave for right now. I started the RRU utility, but it stops at checking signatures.
ERROR (155) Unknown error
The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I have an AT&T Vivid, I thought the one for Holiday Cingular was the correct one? On the phone it says RUU update failed. So I'll look into it when I get back and try then. For some reason I can't update the HBOOT?
Bye for now!
I bet you can't update the bootloader while it is locked, LOL!
As said...I'll look into it when I get back.
Click to expand...
Click to collapse
It should work if you re-locked your bootloader... So that isn't the problem. Maybe somewhere during you trying to S-OFF you still managed to change the HBOOT to the unofficial one. If so, then the RUU or PH zip will both probably not work. Somehow you need to get back to the stock HBOOT. You might need to ask in the Juoponut bear thread or contact them directly.
slapshot30 said:
It should work if you re-locked your bootloader... So that isn't the problem. Maybe somewhere during you trying to S-OFF you still managed to change the HBOOT to the unofficial one. If so, then the RUU or PH zip will both probably not work. Somehow you need to get back to the stock HBOOT. You might need to ask in the Juoponut bear thread or contact them directly.
Click to expand...
Click to collapse
It says I have HBOOT-1.85.0025. I'm back now, so I'll just keep trying.
Congratulations!
Your ROM update has been completed. Your Android phone is now ready for use.
Yup guys, just had to get the right RRU which is the htc_vivid_att_RUU_3.26.502.56_US.exe
Phone is back up and running and everyone is thanked!
Big thank you for all who stood by me during my time of sorrow.
All,
I am pulling my hair out, I decided to root my phone today so I could delete the default APN's, I have tried CWM and also TWRP.
All was fine, as soon as I installed Busybox something went horribly wrong, my phone will not boot up and just displays the "HTC Logo" I can get to the boot menu and boot to either CWM or TWRP. However there is nothing I can do within there, I cannot find a RUU for my model (CID is Orange) I have found a nandroid backup but CWM/TWRP refuses to see it via OTG and I have tried lots of USB Sticks.
I really do not know what to do next, I cannot turn S-OFF as HBOOT is 1.54
What can I do, I have read thread after thread.
Is there a default recovery.img or one for my carrier as I cannot find it.
Many thanks,
Dale
Managed to restore a nandroid, but I have no touch screen!
Tried clearing cache etc, have currently got a mouse plugged in to it to control it, there is an OTA available so going to try that.
DaleR said:
Managed to restore a nandroid, but I have no touch screen!
Tried clearing cache etc, have currently got a mouse plugged in to it to control it, there is an OTA available so going to try that.
Click to expand...
Click to collapse
Don't try it with a custom recovery. You'll need to relock your bootloader too.
No touchscreen is a firmware issue. The nandroid you restored will be an old one not compatible with the latest firmware..
Sent from my HTC One using xda premium
redbull123 said:
Don't try it with a custom recovery. You'll need to relock your bootloader too.
No touchscreen is a firmware issue. The nandroid you restored will be an old one not compatible with the latest firmware..
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thank you for the reply
I've re-locked the bootloader.
What do I do next?, I cannot find a later nandroid backup anywhere
DaleR said:
Thank you for the reply
I've re-locked the bootloader.
What do I do next?, I cannot find a later nandroid backup anywhere
Click to expand...
Click to collapse
Just for now for the sake of getting a working phone I would just flash a 4.2.2 stock ROM, or Sense-based Rom. You'll need to unlock your bootloader again obviously.
Sent from my HTC One using xda premium
redbull123 said:
Just for now for the sake of getting a working phone I would just flash a 4.2.2 stock ROM, or Sense-based Rom. You'll need to unlock your bootloader again obviously.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thanks for the reply, was up till 3am trying to get around this and got it going eventually.
That's what I have done for now, I sideloaded a stock Sense ROM which came with a stock recovery.img, guess I have to wait for a S-OFF for 1.54 if it ever happens.
htc one deleted os
DaleR said:
Thanks for the reply, was up till 3am trying to get around this and got it going eventually.
That's what I have done for now, I sideloaded a stock Sense ROM which came with a stock recovery.img, guess I have to wait for a S-OFF for 1.54 if it ever happens.
Click to expand...
Click to collapse
i have done the same deleted the os off my htc one (CID o2 ) and can not find a the same kind of rom I can get into recovery and have twrp but side loader just says loading and my laptop wont see my phone keeps saying htc mtp driver fail any chance u can let me know how you did yours thanks
If you find your PC/laptop is not seeing the phone then ensue you have the latest drivers on the PC
mini sdk
http://goo.gl/T6InE
HTC Driver version 4.2.0.001
Some folks find Hasoon's All in One very useful - a grate bit of kit
http://forum.xda-developers.com/showthread.php?t=2183942
I would like to install the AT&T OTA of 4.4.2 but have a custom recovery and am unable to upgrade. I am rooted with the stock 4.3 ROM and have the twrp recovery installed. I have S-ON. I've searched around trying to find a way to get this to work but can't seem to figure it out. I've tried looking around for an AT&T 4.3 stock recovery to try and flash it but can't seem to find one. The one from the Dev sticky page is not available for download. Can someone detail the steps I have to perform to get the 4.4.2 OTA from AT&T. Thanks in advance.
[SOLVED]
OK, problem fixed and 4.4.2 installed from OTA. I had relocked the bootloader on my phone so... start from scratch. Steps to resolve
1 - Unlock Bootloader
2 - Get S-Off on device (Makes everything easier). I used Firewater (http://firewater-soff.com)
3 - Flash the AT&T 3.17.502.3 (4.3) RUU from here (http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/). You may need a different one if not on AT&T
4 - Start phone, check for update. Let it download. Cake.
Now off to redo all the settings on my phone. Hope this helps someone else.
You can extract recovery.IMG from the ATT 4.4.2 OTA update if you can't find anything else.
sent from my mobile device
SaHiLzZ said:
You can extract recovery.IMG from the ATT 4.4.2 OTA update if you can't find anything else.
sent from my mobile device
Click to expand...
Click to collapse
Awesome, that's what I wanted to hear. I'm going to give that a shot. Thank you
Stock recoveries here: http://d-h.st/users/guich/?fld_id=29380#files
sent from my mobile device
SaHiLzZ said:
Stock recoveries here: http://d-h.st/users/guich/?fld_id=29380#files
sent from my mobile device
Click to expand...
Click to collapse
I flashed my recovery but recovery now just gets a read triangle with the exclamation
Let the phone download OTA and apply it
sent from my mobile device
SaHiLzZ said:
Let the phone download OTA and apply it
sent from my mobile device
Click to expand...
Click to collapse
Doing now.
It downloaded and attempted to install, then failed half way. Anything else I have to do before I update? Do I have to lock my bootloader again or unroot?
Sent from my HTC One using xda app-developers app
Yea lock bootloader
sent from my mobile device
No dice. Same deal.
Sent from my HTC One using xda app-developers app
Text/Photo of the error?
SaHiLzZ said:
Text/Photo of the error?
Click to expand...
Click to collapse
It doesn't give me an error. The OTA downloads, reboots and gets to a triangle with the green arrows inside and starts installing, then about 25% of the way it stops and goes to a red triangle. I'm thinking the MD5 to one of my files may be failing. I installed an edit to the framework sometime ago to get the hotspot working (that's the only change to the stock rom I've made). It doesn't really give me an error message though.
It could be the issue. You will need to choose one of the few options:
1. Restore a stock ATT OS for the same version you have (4.3) and update again
2. S-OFF (Preferred to avoid future messy bricks) and reinstall old ATT RUU and then upgrade all the way without custom rom/rooting/firmware changes
3. Wait for someone to post a custom rom install of the new ATT 4.4 update and install that.
SaHiLzZ said:
It could be the issue. You will need to choose one of the few options:
1. Restore a stock ATT OS for the same version you have (4.3) and update again
2. S-OFF (Preferred to avoid future messy bricks) and reinstall old ATT RUU and then upgrade all the way without custom rom/rooting/firmware changes
3. Wait for someone to post a custom rom install of the new ATT 4.4 update and install that.
Click to expand...
Click to collapse
Thanks, I appreciate your help. I think I'm gonna go with option 2, depending on how much time I have to do this, or 3 if time is an issue. Just one more question for you. Is firewater the best method to get S-Off or do you recommend a different one?
SMaximus7 said:
Thanks, I appreciate your help. I think I'm gonna go with option 2, depending on how much time I have to do this, or 3 if time is an issue. Just one more question for you. Is firewater the best method to get S-Off or do you recommend a different one?
Click to expand...
Click to collapse
If the ota stops on the second half as you discribe I think you have the wrong stock recovery. Different version than your "version-main"
mb_guy said:
If the ota stops on the second half as you discribe I think you have the wrong stock recovery. Different version than your "version-main"
Click to expand...
Click to collapse
I guess it can't hurt to try and reflash the recovery and retry. I'll give it a try.
SMaximus7 said:
I guess it can't hurt to try and reflash the recovery and retry. I'll give it a try.
Click to expand...
Click to collapse
I had the exact same thing occur, had a newer recovery than "fastboot getvar all"
mb_guy said:
I had the exact same thing occur, had a newer recovery than "fastboot getvar all"
Click to expand...
Click to collapse
It could be because I flashed the recovery that came with the OTA with fastboot and then after SaHiLzZ pointed me in the right direction was able to download the 4.3 recovery but flashed that one with flashify. I bet you the one I did with flashify didn't take. Funny thing is I also relocked my bootloader and now must unlock it again and that will probably wipe my device. What a mess, oh well, I hope that's all it is and at least I'm learning as I go.
SMaximus7 said:
It could be because I flashed the recovery that came with the OTA with fastboot and then after SaHiLzZ pointed me in the right direction was able to download the 4.3 recovery but flashed that one with flashify. I bet you the one I did with flashify didn't take. Funny thing is I also relocked my bootloader and now must unlock it again and that will probably wipe my device. What a mess, oh well, I hope that's all it is and at least I'm learning as I go.
Click to expand...
Click to collapse
Ya, I was lucky, had a nandroid . But you are right the recovery in the ota is too new.
Solved
OK, problem fixed and 4.4.2 installed from OTA. I had relocked the bootloader on my phone so... start from scratch. Steps to resolve
1 - Unlock Bootloader
2 - Get S-Off on device (Makes everything easier). I used Firewater (http://firewater-soff.com)
3 - Flash the AT&T 3.17.502.3 (4.3) RUU from here (http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/). You may need a different one if not on AT&T
4 - Start phone, check for update. Let it download. Cake.
Now off to redo all the settings on my phone. Hope this helps someone else. Thanks everybody for chiming in.
Hey Guys,
I got an HTC Vivid a while ago. However, when I got , I looked into the software unlock method to unlock it. Doing so required for the phone to first be rooted. So I followed through some steps to root it. WORST DECISION EVER ! Since then, not only did the unlock not work, but the phone has gotten so slow and dysfunctional it is barely useful. I mean, everything else runs properly, except Calls and Text Message. i.e The phone isn't performing its right function.
Thus, I wanted to look into a way to 'unroot it' or at least just return COMPLETELY to factory settings. I want to be at least able to sell it and buy another. I've looked through and tried a couple of guides to remove the root. One seemed to work really well, until I restarted the phone, where the "Cleanup" window came back on, and the phone returned to its old rooted self.
Thanks in advance for your help !
How did you root it...
What 'unlock' are you trying to accomplish?
Sent from my Vivid 4G using Tapatalk
rignfool said:
How did you root it...
What 'unlock' are you trying to accomplish?
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
I rooted using a method I saw here, which was supposed to be one of the steps to software unlock.
However, it is not already uncooked using the regular IMEI, which is completely different.
So, now I just want to unroot, and bring the phone back to factory, with those "Android is Upgrading...Optimizing applications" message at every boot up.
Anyone ?!
If you revert to stock ROM using ruu, you will be unroofed.
Sent from my Vivid 4G using xda app-developers app
projectisaac said:
If you revert to stock ROM using ruu, you will be unroofed.
Sent from my Vivid 4G using xda app-developers app
Click to expand...
Click to collapse
I tried that once...It didn't seem to work for me. Is there a particular method I need to follow?
Also, it seems the "Deodex' method for my rom was supposed to work?
Thank you in advance.
joellecool said:
I tried that once...It didn't seem to work for me. Is there a particular method I need to follow?
Also, it seems the "Deodex' method for my rom was supposed to work?
Thank you in advance.
Click to expand...
Click to collapse
In not familiar with the "deodex" method, but I did fish out a guide for the ruu:
http://forum.xda-developers.com/showthread.php?p=34617117
In the meantime, I'll look up the deodex method and come back to this post.
Sent from my Vivid 4G using xda app-developers app
I have recently tried to revert my Velocity back to stock but ran into the same problem. Have relocked the device and tried to flash stock RUU but this didn't work. My device was s-on and I read in a post here that to be able to go back to stock RUU you need to be s-off. The part I haven't worked out yet is to be able to get s-off you have to be on stock RUU!
ph0n3n3rd said:
I have recently tried to revert my Velocity back to stock but ran into the same problem. Have relocked the device and tried to flash stock RUU but this didn't work. My device was s-on and I read in a post here that to be able to go back to stock RUU you need to be s-off. The part I haven't worked out yet is to be able to get s-off you have to be on stock RUU!
Click to expand...
Click to collapse
You DO NOT need to be s-off to be on stock ruu. Do you mind going through the steps you followed?
Sent from my Vivid 4G using xda app-developers app
projectisaac said:
You DO NOT need to be s-off to be on stock ruu. Do you mind going through the steps you followed?
Sent from my Vivid 4G using xda app-developers app
Click to expand...
Click to collapse
No, sorry ,I meant to say that you have to be on stock RUU to be able to achieve s-off. The guide that I followed was "The HTC Superguide " in the development section of this device. Firstly, I did a full wipe, as in Dalvic cache, Cache, System, Boot and Factory Data Reset, also SD card, then I relocked the device with "fastboot oem lock", after that I tried to run the stock RUU ( The one the phone was originally on ), which started the initial flash but stopped at about 10% and came up with " ERROR 140 ". I tried 4 or 5 times and even tried another computer with the same result.
ph0n3n3rd said:
No, sorry ,I meant to say that you have to be on stock RUU to be able to achieve s-off. The guide that I followed was "The HTC Superguide " in the development section of this device. Firstly, I did a full wipe, as in Dalvic cache, Cache, System, Boot and Factory Data Reset, also SD card, then I relocked the device with "fastboot oem lock", after that I tried to run the stock RUU ( The one the phone was originally on ), which started the initial flash but stopped at about 10% and came up with " ERROR 140 ". I tried 4 or 5 times and even tried another computer with the same result.
Click to expand...
Click to collapse
I found this thread with people that had the same problem, but I'm not sure if it will help you: http://forum.xda-developers.com/showthread.php?t=1828491&page=3
You could try flashing an old gingerbread ROM and then try the RUU, as it seems to have something to do with the rom on the phone being newer than the RUU or something.
projectisaac said:
I found this thread with people that had the same problem, but I'm not sure if it will help you: http://forum.xda-developers.com/showthread.php?t=1828491&page=3
You could try flashing an old gingerbread ROM and then try the RUU, as it seems to have something to do with the rom on the phone being newer than the RUU or something.
Click to expand...
Click to collapse
I have tried flashing an old gingerbread rom ( 2.27.841.6 ) as well as the latest version I could find ( 3.25.841.4 ) but I keep getting "ERROR 140 WRONG BOOTLOADER" and it also says the current version is 3.44.841.3 which is why I can't upgrade because I'm really trying to downgrade. The update to 3.44.841.3 from 3.25.841.4 was only about 58Mb but I can't find that and I don't think it would be of much use.
I have also tried to s-off the device with a live Ubuntu 12.04 32bit CD using ControlBear instructions but hit a snag because the sudo ./ControlBear command does nothing. I think the permissions or password may be out of date. Any ideas would be greatly appreciated
I made a PH39IMG.zip from the 3.25.841.4 and tried flashing that but got the Wrong Image message too.