Hello, to start of im sorry if there is a thread I am unaware of but I was unable to find it in the countless hours i have worked on this. My main problem is my phone wont load to the OS. the issue started when i attempted to run a custom ROM for the first time, the ROM made the WiFi unavailable. So i did some research and found out i needed to update the firmware.zip, so i did so. Thats where things went south, the rom would not load at all and the internal storage will not show up on my pc.
So the things i have tried include....
Trying to reinstall the rom
Using the ruu update utility
using a backup (not sure if i did that right)
Plz if you could help me get my phone working that would be great! Let me know if you need more info.
Are you S-OFF and what Rom did you try flashing ?
What firmware and how did you try and flash it?
jball said:
Are you S-OFF and what Rom did you try flashing ?
What firmware and how did you try and flash it?
Click to expand...
Click to collapse
Yeah, there isn't nearly enough info posted by the OP.
In addition:
What hboot and radio number?
What thread did you get the firmware zip?
What RUU(s) did you try?
Did you relock the bootloader to RUU (required if s-on).
I know you don't have enough posts yet to provide links to what you tried to flash. But try to describe as best you can, and specifically as possible in words.
---------- Post added at 09:45 AM ---------- Previous post was at 09:43 AM ----------
Thorin_Stone said:
using a backup (not sure if i did that right)
Click to expand...
Click to collapse
Which backup did you try, and how did you try to restore it (list out the exact steps, file location you saved to, etc.)? You say you're not sure if you did it right, but then you don't say how you did it. So how is that info supposed to help us help you?
Always provide as much detail as possible when asking for help. Leaving out all these details makes it impossible to provide the proper help.
redpoint73 said:
Yeah, there isn't nearly enough info posted by the OP.
In addition:
What hboot and radio number?
What thread did you get the firmware zip?
What RUU(s) did you try?
Did you relock the bootloader to RUU (required if s-on).
I know you don't have enough posts yet to provide links to what you tried to flash. But try to describe as best you can, and specifically as possible in words.
---------- Post added at 09:45 AM ---------- Previous post was at 09:43 AM ----------
Which backup did you try, and how did you try to restore it (list out the exact steps, file location you saved to, etc.)? You say you're not sure if you did it right, but then you don't say how you did it. So how is that info supposed to help us help you?
Always provide as much detail as possible when asking for help. Leaving out all these details makes it impossible to provide the proper help.
Click to expand...
Click to collapse
Sorry for the lack of info...
-Hboot #= 3.19.0.0000
-Radio#= 1.21.213311491.A04G
-The place i got the firmware from is= forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
-And i got the recovery from here =forum.xda-developers.com/showthread.php?t=2701376
-Lastly the ruu from this tutorial (yes i relocked)= droidviews.com/restore-att-htc-one-m8-stock-firmware/
When i tried to restore I
-Pushed the restore to my phone
-placed them in the proper TWRP recovery location
-Then attempted to restore
-First error I got was "E: Unable to locate partition by backup name 'recovery'
-Then failed with no error
Can I plz get some advice
Thorin_Stone said:
Can I plz get some advice
Click to expand...
Click to collapse
You didn't answer the questions whether you are s-off; and what ROM you are trying to flash.
---------- Post added at 11:05 AM ---------- Previous post was at 10:57 AM ----------
Thorin_Stone said:
When i tried to restore I
-Pushed the restore to my phone
-placed them in the proper TWRP recovery location
-Then attempted to restore
-First error I got was "E: Unable to locate partition by backup name 'recovery'
-Then failed with no error
Click to expand...
Click to collapse
I think you downloaded the wrong file. The stock recovery is what you would flash over TWRP to go "back to stock". If you are trying to restore the stock ROM, you want the stock nandroid, not recovery. What file exactly did you try to restore from the stock nandroid thread?
You are also still doing a horrible job of providing the specific details I asked. I asked for the file location, and your response is the "proper location". This seriously is not helpful. I want you to tell me the exact file path/location so I can verify its the "proper" location.
But I also don't think that restoring a nandroid is the right way to go. Assuming you are s-off (you need to be, to manually flash firmware), its just a matter of properly installing the firmware and flashing the desired ROM.
Did you try to flash the firmware twice (often required to get everything to install)?
If so, I would then fastboot erase cache, install TWRP again (get updated version, if not so already). Then try to flash the ROM again.
fastboot getvar all if you want folks to help...If you do not know how to run fastboot adb commands research. Cannot help with this limited information.
Thorin_Stone said:
Sorry for the lack of info...
-Hboot #= 3.19.0.0000
-Radio#= 1.21.213311491.A04G
-The place i got the firmware from is= forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
-And i got the recovery from here =forum.xda-developers.com/showthread.php?t=2701376
-Lastly the ruu from this tutorial (yes i relocked)= droidviews.com/restore-att-htc-one-m8-stock-firmware/
When i tried to restore I
-Pushed the restore to my phone
-placed them in the proper TWRP recovery location
-Then attempted to restore
-First error I got was "E: Unable to locate partition by backup name 'recovery'
-Then failed with no error
Click to expand...
Click to collapse
redpoint73 said:
You didn't answer the questions whether you are s-off; and what ROM you are trying to flash.
---------- Post added at 11:05 AM ---------- Previous post was at 10:57 AM ----------
I think you downloaded the wrong file. The stock recovery is what you would flash over TWRP to go "back to stock". If you are trying to restore the stock ROM, you want the stock nandroid, not recovery. What file exactly did you try to restore from the stock nandroid thread?
You are also still doing a horrible job of providing the specific details I asked. I asked for the file location, and your response is the "proper location". This seriously is not helpful. I want you to tell me the exact file path/location so I can verify its the "proper" location.
But I also don't think that restoring a nandroid is the right way to go. Assuming you are s-off (you need to be, to manually flash firmware), its just a matter of properly installing the firmware and flashing the desired ROM.
Did you try to flash the firmware twice (often required to get everything to install)?
If so, I would then fastboot erase cache, install TWRP again (get updated version, if not so already). Then try to flash the ROM again.
Click to expand...
Click to collapse
Wonders_Never_Cease said:
fastboot getvar all if you want folks to help...If you do not know how to run fastboot adb commands research. Cannot help with this limited information.
Click to expand...
Click to collapse
One again im sorry.
Code:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.21.213311491.
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: RUU
commitno-bootloader: c88f4560
hbootpreupdate: 11
gencheckpt: 0
Im s-on and cant get to s-off seeing how my phone is loading into os and SU is not installing.
I placed the recovery in the same location TWRP makes them, which is /data/media/TWRP. The recovery i got was a nandroid for CID CWS__00, 1.12.502.18 - TWRP 2.6.3.3.
From what im seeing every time im trying to install any rom (currently tried both InsertCoin and Android Revolution HD 22.10 im getting this
Code:
-> creating symlinks
simlink: some symlinks failed
Id suggest flashing the exe ruu for 1.58.502 and then flashing the 2.23.502 ruu that will at least puy you up to a 4.4.3 base until the update in about two weeks to 4.4.4
Wonders_Never_Cease said:
Id suggest flashing the exe ruu for 1.58.502 and then flashing the 2.23.502 ruu that will at least puy you up to a 4.4.3 base until the update in about two weeks to 4.4.4
Click to expand...
Click to collapse
****BREAKTHROUGH*****
I was able to get the phone on with cyanogenmod. Can you help guide me back to stock?
****BREAKTHROUGH*****
Can you plz help me find those because i have tried those(of which i found) and i get an error with those to and the error occurs when it checks the signature but gives no specific error. But mabey you know something i don't..
Connect them via fastbootusb optionin bootloader and try,info you provided,they should run. Search google for htc one m8 att 2.23.502.5(i think) and it should find link to it same with 1.58.502,that one should be available right from the htc support page
Thorin_Stone said:
From what im seeing every time im trying to install any rom (currently tried both InsertCoin and Android Revolution HD 22.10 im getting this
Code:
-> creating symlinks
simlink: some symlinks failed
Click to expand...
Click to collapse
Failure to flash various ROMs (as long as its not something obvious, like bootloader locked) can often be fixed by following the last sentence of my previous post (#6).
---------- Post added at 09:59 AM ---------- Previous post was at 09:55 AM ----------
Thorin_Stone said:
One again im sorry.
Code:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.21.213311491.
Click to expand...
Click to collapse
Something here is very screwy. Those hboot and radio numbers don't exist for the AT&T version (and don't correspond to the US Dev Ed version either, AFAIK). And they can't be modified (to non-AT&T hboot and radio) with s-on.
Did you buy the phone 2nd hand?
---------- Post added at 10:00 AM ---------- Previous post was at 09:59 AM ----------
Thorin_Stone said:
Can you plz help me find those because i have tried those(of which i found) and i get an error with those to and the error occurs when it checks the signature but gives no specific error. But mabey you know something i don't..
Click to expand...
Click to collapse
Did you relock the bootloader before trying to RUU (as I've already indicated)?
redpoint73 said:
Failure to flash various ROMs (as long as its not something obvious, like bootloader locked) can often be fixed by following the last sentence of my previous post (#6).
---------- Post added at 09:59 AM ---------- Previous post was at 09:55 AM ----------
Something here is very screwy. Those hboot and radio numbers don't exist for the AT&T version (and don't correspond to the US Dev Ed version either, AFAIK). And they can't be modified (to non-AT&T hboot and radio) with s-on.
Did you buy the phone 2nd hand?
---------- Post added at 10:00 AM ---------- Previous post was at 09:59 AM ----------
Did you relock the bootloader before trying to RUU (as I've already indicated)?
Click to expand...
Click to collapse
No the phone is not second hand i did apply a firmware... i don't remember were i got it from but i flashed it with s-on so i don't know why i can reflash an old one with s-on. and i did relock the bootloader to ruu it.
Thorin_Stone said:
No the phone is not second hand i did apply a firmware... i don't remember were i got it from but i flashed it with s-on so i don't know why i can reflash an old one with s-on. and i did relock the bootloader to ruu it.
Click to expand...
Click to collapse
Something strange is going on. You can't flash firmware with s-on. And if you can't remember what you did (what firmware you flashed), I can't really help much more.
You won't be able to run any AT&T RUU. Reason being, you can't run an RUU that has a lower (older) hboot than what is presently on the phone. And the hboot number you reported is higher than what is contained on all AT&T RUUs (until AT&T releases Android 4.4.4). You might try the Dev Ed 3.28 RUU.
Otherwise, fastboot erase cache, re-install TWRP, and see if that allows you to flash ROMs. Flashing a ROM is most you can do, if no RUUs work.
redpoint73 said:
Something strange is going on. You can't flash firmware with s-on. And if you can't remember what you did (what firmware you flashed), I can't really help much more.
You won't be able to run any AT&T RUU. Reason being, you can't run an RUU that has a lower (older) hboot than what is presently on the phone. And the hboot number you reported is higher than what is contained on all AT&T RUUs (until AT&T releases Android 4.4.4). You might try the Dev Ed 3.28 RUU.
Otherwise, fastboot erase cache, re-install TWRP, and see if that allows you to flash ROMs. Flashing a ROM is most you can do, if no RUUs work.
Click to expand...
Click to collapse
Ok i thank you for your help! How do you think all this will effect my return policy? Do you think a repair company will be able to help?
Thorin_Stone said:
Ok i thank you for your help! How do you think all this will effect my return policy? Do you think a repair company will be able to help?
Click to expand...
Click to collapse
Warranty is for manufacturing defects, not for damage you did to the phone when modding.
Did you try to wipe cache, and re-install TWRP like I suggested? I think your failure to flash ROMs is not that major an issue, probably recoverable, and certainly not a reason to return the phone.
The firmware issue is a weird one. But once the phone is up and running, can be fixed with s-off.
redpoint73 said:
Warranty is for manufacturing defects, not for damage you did to the phone when modding.
Did you try to wipe cache, and re-install TWRP like I suggested? I think your failure to flash ROMs is not that major an issue, probably recoverable, and certainly not a reason to return the phone.
The firmware issue is a weird one. But once the phone is up and running, can be fixed with s-off.
Click to expand...
Click to collapse
Well I just had a breakthrough and got it running with cyanogen mod. If im correct I can S-OFF now and flash an ruu right?
Thorin_Stone said:
Well I just had a breakthrough and got it running with cyanogen mod. If im correct I can S-OFF now and flash an ruu right?
Click to expand...
Click to collapse
You need to be completely stock.
If you can download the right stock backup or a stock ROM than try that out.
Thorin_Stone said:
If im correct I can S-OFF now and flash an ruu right?
Click to expand...
Click to collapse
I don't know if you will be able to s-off with the hboot number you supplied, even with sunshine. You can try, but stock ROM is best for sunshine, as mentioned. I'm not even sure which stock ROM goes with the hboot and radio you listed.
Something odd has happened to your phone, and I really don't know what.
Related
It has come to a lot of peoples furious attention that there is an issue with the latest RUU from HTC. I firsthand had to deal with it an it is documented in this thread http://forum.xda-developers.com/showthread.php?t=2074643 in which i attempted to restore my htcdev unlocked phone back to stock.
THE ISSUE
The problem is the ruu is updating hboot and seemingly nothing else. Radios, recovery, rom, etc all have remained the same after running the ruu. Attempts at re running the ruu do nothing and various ways of flashing/applying the ruu are ineffective. This creates a stable but malfunctioning phone with mismatched hboot, radios, rom, and seems unable to take you back to fully stock.
Pre-RUU:
s-on
hboot: 1.19
radio: 1.05.11.0606
rom: stock rooted jb with superuser
Post-RUU: (after multiple flashings/applications)
hboot: 2.09
radio: 1.05.11.0606
rom: stock rooted jb with superuser (i'm assuming that this should have been completely stock instead its the same rom i had previous to ruu application)
In the mean time, I've been running the latest stock jb rom and its stable enough for a functioning phone but things like cellular data (streaming music from google music doesn't work or sending sexy pics to the ladies on snap chat) and lte is completely absent. If you experience the same issue post in here with what happened, solutions, fixes, etc.
GOING BACK TO STOCK
If you need to get back to stock or semi bricked your phone use the ruu for your current software not the latest (for example if your hboot is 1.19 use the ruu with hboot 1.19 not the jb ruu with 2.09 hboot)
For now it seems the best thing to do is aware htc of the problem, wait for a new ota update/ruu fix, and/or wait for new s-off method for 2.09,
tankerevo has been working on various attempts/fixes and i've forwarded this thread along with some other information to htc.
RESPONSE FROM HTC
Dear rollerpig,
Thank you for contacting the HTC Technical Support Center in regards to your issue suggestion.
We are glad to know there are customers like you committed with our brand to improve our service and customer satisfaction. We understand there could be a lot of users and fans waiting for a fix on this RUU. We think it is amazing to have a good support in our users to enhance our products and releases. Right now we will share this concern with the Develop Team to look forward on a solution. We expect this issue will be fixed as soon as possible.
Rollerpig, we want to thank you once again for working with us, and for caring about our brand.
If you require further assistance in the near future please contact us through http://www.htc.com/us/support/email-support or call us at +1-866-449-8358 from 6AM to 1AM EST, 7 days a week.
Have a nice day,
Let me know if I have successfully answered your question, please click here to complete this.
To send a reply to this message, please click here.
Sincerely,
Julian
HTC
Want to see what others are saying? Have a question to ask other HTC fans?
Become a fan of HTC facebook.com/htc
Follow us on Twitter twitter.com/htc
Subscribe to our YouTube Channel youtube.com/htc
Explore our development resources developer.htc.com
Please visit us at htc.com if you have any questions or need further assistance.
Click to expand...
Click to collapse
THE FIX
Here's a possible fix complements of user Fuses. I have not tried this yet because i'm on vacation but it looks very promising and most likely works. http://forum.xda-developers.com/showthread.php?t=2097150
Fix
- Download JB OTA firmware from http://unlimited.io/jewel.htm
- Download fastboot executable (google)
- Put all files in one directory
- Reboot phone into fastboot mode
- Make sure that bootloader is Locked or Relocked. If bootloader is Unlocked, relock it with command fastboot oem lock
- Enter commands
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip
NOTE:
If you see FAILED (remote: 90 hboot pre-update! please flush image again immediately) text after running fastboot flash zip command you have to run fastboot flash zip command again.
After this flash stock RUU again.
Permanent fix
- S-OFF your phone. With S-OFF phone you can always flash decrypted, unsigned and/or older RUU and get phone working again easily.
Click to expand...
Click to collapse
Obviously, depending on the firmware version you are frozen at there will likely be variance in stability and function between ROMs and other users with the issue stuck at a different firmware version.
For me the last ICS stock ROM is working the best including LTE. But WiFi, Cell, and Data do restart rather incessantly.
MeanBean 2.0 works alright considering... But LTE doesn't work at all and the radios get very weak signals to the point that I start to enter roaming often.
It might help to post before and after info of the radio versions, hboot, pri, all that stuff so if someone were to have used the RUU and it worked they can compare what the old stuff is to the new stuff.
does gps work well on the ics stock?
sickied for a little while until issue is resolved
Papa Smurf151 said:
sickied for a little while until issue is resolved
Click to expand...
Click to collapse
good deal... And also , Thanks OP for the heads up
I've got my lte back, but had to nandroid back to superlte. I went to ##3282# and set profile to 1, and changed scan timer to 2 and max timer 30. It has been the longest I've had constant lte in a month.
Sent from my EVO using Tapatalk 2
Mine was hosed too. If I ran the 2.13 RUU, it said you have a 2.13 image, would you like to update it to 2.13. If I ran the 3.15 RUU, it would say you have a 3.15 image on your phone, would you like to update it to 3.15?
Needless to say, none of that worked. I even tried the P75 image of JB direct from Sprint through recovery. No workie. I gave up and took it to Sprint. Explained that after RUU just aint going to work and this phone is stuck in ICS/JB hybrid limbo.
Sprint replaced the phone and I am now good to go. If you want to wait for a hack fix, then wait. Otherwise, you can try getting Sprint to replace it with a new one.
So back to my original question, can someone post what the 3.15.651.16 official numbers should be.
PRI, Radio, All those magical numbers were talking about..
Id like to check mine and see. I do remember downloading the RUU and installing it..
IAmSixNine said:
So back to my original question, can someone post what the 3.15.651.16 official numbers should be.
PRI, Radio, All those magical numbers were talking about..
Id like to check mine and see. I do remember downloading the RUU and installing it..
Click to expand...
Click to collapse
PRI - 2.87_003
Baseband - 1.12.11.1119
bigdaddy619 said:
PRI - 2.87_003
Baseband - 1.12.11.1119
Click to expand...
Click to collapse
OK those numbers match my device so i guess im OK..
The file i used to upgrade was downloaded 12/24/2012
RUU_JEWEL_CL_BJ_45_S_SPRINT_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe
This is the RUU i used on mine because i was impatient and didnt want to wait for the OTA to hit my phone.
From what i can tell it did the upgrade just fine.
IAmSixNine said:
The file i used to upgrade was downloaded 12/24/2012
RUU_JEWEL_CL_BJ_45_S_SPRINT_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe
This is the RUU i used on mine because i was impatient and didnt want to wait for the OTA to hit my phone.
From what i can tell it did the upgrade just fine.
Click to expand...
Click to collapse
IAmSixNine, could you give us a bit more detail on your setup. OS (windows etc), where you downloaded the RUU, and what software version were you running before you upgraded.
Windows 7 home, i was on the latest stock, unlocked device prior to that update coming out.
Where did i DL it at, http://www.htcruu.com/?dir=Jewel
Try this one, please report on that thread if fix works for you also
http://forum.xda-developers.com/showthread.php?t=2097150
I installed the 3.15 RUU from CM10 to try to bring my phone back to stock.
The RUU took, but now my phone is incredibly slow, freezes, screen goes unresponsive, camera wont work...All kinds of issues]
I even reapplied the same RUU from the stock 3.15 ROM.
Are my issues symptoms of this problem outlined in this thread?
Possibly. What's you baseband version?
If its less than 1.12 then yes.
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
Also if it is less then fllow fuses thread link above.
update baseband
is there a way to update the baseband version mine is less then 1.12, I am s-off and am running the latest meanrom because meanbean was super unstable for me.
do I need to download the latest ruu to update it, then flash it with the latest meanbean?
frey482 said:
is there a way to update the baseband version mine is less then 1.12, I am s-off and am running the latest meanrom because meanbean was super unstable for me.
do I need to download the latest ruu to update it, then flash it with the latest meanbean?
Click to expand...
Click to collapse
Here is the full firmware minus hboot-recovery-kernel
http://d-h.st/4Y0
MD5 2a9b2c8f6a969fe0163df5738e8f4b5
Rename it PJ75IMG and place it on your ext sdcard/boot into bootloader/ it should ask you if you want to update follow the on screen instructions once you are rebooted remove the file from your sdcard if you don't you will be asked to update every time you enter bootloader
I rooted my phone this morning, and attempted to install cm10. the screen became inop. so I tried a recovery and it put it into boot loop. I have relocked the phone and tried some RUUs but all come back with bootloader, or signature errors, I have tried this method as well to no avail all i end up getting is this:
C:\Users\Downloads>fastboot flash zip RUU.zip
sending 'zip' (659905 KB)...
OKAY [ 27.926s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 106.089s
Boot Screen:
*tampered
*relocked
s on
hboot 2.09
radio 1.12.11.1210
opendsp-v31.1.45.0815
eMMC-boot
Any help would be appreciated
Hello all,
I'm Beginner with htc, i have problem with boot loop, i have done lot of search in the internet and i applied many procedures but i couldn't resolve the problem.
My phone is :
HTC EVO 3D GSM
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
RADIO-11.25.3504.06_M
OpenDSP-v02.6.0.2226.00.02.02
eMMC-boot
Can i have your helps please?
Thank you very much
Best regards,
Dear beginner, this is HTC One (2013) forum
Sent from my Desire HD using Tapatalk 2
Which rom are you trying to boot? Because you are s-on you need to flash boot.img seperately in fastboot. OR you could use 4EXT recovery with smartflash turned on.
EM|NEM said:
Which rom are you trying to boot? Because you are s-on you need to flash boot.img seperately in fastboot. OR you could use 4EXT recovery with smartflash turned on.
Click to expand...
Click to collapse
Thank you very much for your replay,
Sorry for this late response, i was late because i have post my problem in oder thread at this link ( http://forum.xda-developers.com/showthread.php?p=38896827#post38896827 )
i have use all ruu.exe available in this site ( http://androidfiles.org/ruu/?dir=Shooter ) that have the same radios like my phone but it doesn't completed, the ruu.exe show me the error that my phone is non-compatible with this ruu,
The ruu that i have used from the ()are:
RUU_SHOOTER_U_ICS_35_S_hTC_Asia_WWE_3.28.707.1_Rad io_11.77.3504.00U_11.25.3504.06_M_release_264110_s igned.exe
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio _11.77.3504.00U_11.25.3504.06_M_release_262714_sig ned.exe
RUU_SHOOTER_U_ICS_35_S_Rogers_WWE_3.28.631.1_Radio _11.77.3504.00U_11.25.3504.06_M_release_262715_sig ned.exe
Please, can you send me a link for any ruu or rom works with my phone described above,?
Thank you very much for your all collaborations and helps,
Best regards,
aagrou said:
Thank you very much for your replay,
Sorry for this late response, i was late because i have post my problem in oder thread at this link ( http://forum.xda-developers.com/showthread.php?p=38896827#post38896827 )
i have use all ruu.exe available in this site ( http://androidfiles.org/ruu/?dir=Shooter ) that have the same radios like my phone but it doesn't completed, the ruu.exe show me the error that my phone is non-compatible with this ruu,
The ruu that i have used from the ()are:
RUU_SHOOTER_U_ICS_35_S_hTC_Asia_WWE_3.28.707.1_Rad io_11.77.3504.00U_11.25.3504.06_M_release_264110_s igned.exe
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio _11.77.3504.00U_11.25.3504.06_M_release_262714_sig ned.exe
RUU_SHOOTER_U_ICS_35_S_Rogers_WWE_3.28.631.1_Radio _11.77.3504.00U_11.25.3504.06_M_release_262715_sig ned.exe
Please, can you send me a link for any ruu or rom works with my phone described above,?
Thank you very much for your all collaborations and helps,
Best regards,
Click to expand...
Click to collapse
First of all, since you are using a smarphone, you should try and be a bit smart yourself. From a logical standpoint, those ruu have something different: on one says ASIA, on one EUROPE, and on one Rogers (which I can only assume it is linked to the us version, probably CDMA Evo 3D). If you live and bought the phone from Europe, it seems to me you should try the Europe RUU, right? If from Asia, the Asia one and so forth. Simple logic.
Secondly, if you would have read the vast quantity of threads and tutorials about this, you should have started your phone in hboot (Power button+Volume Down), select Fastboot by pressing the Power button, connect your phone to your pc, and in cmd write "fastboot oem lock". Also preferably a full wipe to be done in recovery. Once those steps were performed, the logically chosen RUU would work without any errors
posedatull said:
First of all, since you are using a smarphone, you should try and be a bit smart yourself. From a logical standpoint, those ruu have something different: on one says ASIA, on one EUROPE, and on one Rogers (which I can only assume it is linked to the us version, probably CDMA Evo 3D). If you live and bought the phone from Europe, it seems to me you should try the Europe RUU, right? If from Asia, the Asia one and so forth. Simple logic.
Secondly, if you would have read the vast quantity of threads and tutorials about this, you should have started your phone in hboot (Power button+Volume Down), select Fastboot by pressing the Power button, connect your phone to your pc, and in cmd write "fastboot oem lock". Also preferably a full wipe to be done in recovery. Once those steps were performed, the logically chosen RUU would work without any errors
Click to expand...
Click to collapse
thank you for your replay,
I have done all of that (wip all in recovery, lock my phone, install the ruu.exe). i did that for all the ruu.exe described above but it doesn't work :cryingerror ruu no compatible).
do you know any ruu work on my phone please?
my phone is HTC EVO 3D GSM(described above)
thank you a lot,
best regards
What usb cable are you using, and what usb itself? The ruu will not work on usb 1.1 or 3.0, only on usb 2.0 . If you use a pc, plug it in the back, directly in a usb from a mainboard, not in the front usb or through a hub
Which carrier was your phone on before? Make sure you use the correct RUU for your phone
EDIT: I see its already been explained
EM|NEM said:
Which carrier was your phone on before? Make sure you use the correct RUU for your phone
EDIT: I see its already been explained
Click to expand...
Click to collapse
thank you for your replay.
i don't know which is the first ruu of my phone, because i have got it with a bootloop problem.
do you know the original ruu for my phoene described above?
thank you for you collaborations.
best regards.
Boot into bootloader and run this command in cmd: "fastboot getvar cid"
this should give you your CID. might help in figuring out what your original rom was
---------- Post added at 12:32 AM ---------- Previous post was at 12:16 AM ----------
been googling your prob for a while and there is a possibility you had an arabic rom/firmware.
If you have HTC__J15 cid then run this RUU (the ics one): http://forum.xda-developers.com/showthread.php?t=1282840
EM|NEM said:
Boot into bootloader and run this command in cmd: "fastboot getvar cid"
this should give you your CID. might help in figuring out what your original rom was
---------- Post added at 12:32 AM ---------- Previous post was at 12:16 AM ----------
been googling your prob for a while and there is a possibility you had an arabic rom/firmware.
If you have HTC__J15 cid then run this RUU (the ics one): http://forum.xda-developers.com/showthread.php?t=1282840
Click to expand...
Click to collapse
thank you. i will test that thid night and i inform you tomorow
Best regards,
EM|NEM said:
Boot into bootloader and run this command in cmd: "fastboot getvar cid"
this should give you your CID. might help in figuring out what your original rom was
---------- Post added at 12:32 AM ---------- Previous post was at 12:16 AM ----------
been googling your prob for a while and there is a possibility you had an arabic rom/firmware.
If you have HTC__J15 cid then run this RUU (the ics one): http://forum.xda-developers.com/showthread.php?t=1282840
Click to expand...
Click to collapse
the cid that i got with the command "fastboot getvar cid" is "cid: VODAP304".
Where can i find the the original rom,
thank you a lot,
best regards,
aagrou said:
the cid that i got with the command "fastboot getvar cid" is "cid: VODAP304".
Where can i find the the original rom,
thank you a lot,
best regards,
Click to expand...
Click to collapse
The Europe ruu should work for that cid... Nonetheless, I will look a bit more into it later when I get home, to see if I can find any more details
You probably need a vodafone ruu but i can't seem to find an ICS one
posedatull said:
The Europe ruu should work for that cid... Nonetheless, I will look a bit more into it later when I get home, to see if I can find any more details
Click to expand...
Click to collapse
thank you for your collaboration,
Just for information, i have tested the europe ruu.exe but doesn't work.
Best regards,
Be sure to plug the phone in a usb 2.0 in the computer (one in the back, NOT in the front) to be sure it works properly. Ruus have problems on usb 1.1 and even on 3.0. Also try replacing your data cable, it might be faulty.
If you wiped everything in recovery and then oem locked hboot through adb, the europe ruu should have worked. Since it didnt, i must assume the problem is either with the cable used or with the usb port.
Also an idea might be to try and download the ruu again, maybe there was an error during the download
Theres something else you can try too. download the zip RUU. place this on your sd card and flash in bootloader
EM|NEM said:
Theres something else you can try too. download the zip RUU. place this on your sd card and flash in bootloader
Click to expand...
Click to collapse
thank all for your collaborations,
I have done this but it doesn't work, sorry for all and thank you.
do you know other ruu?
best regards
Well if you cant RUU you should try to get a custom rom to boot. First do these steps:
Unlock your bootloader.
Flash 4EXT recovery in fastboot. Then boot into recovery and turn on smartflash in tools menu.
Download Viper3D rom (the latest one) and transfer it to your sdcard.
Boot into recovery
wipe data/factory reset, wipe cache+dalvik
install viper3d rom. It will take a while, around 10 mins on synergy 4EXT alignment.
reboot and hope it boots
EM|NEM said:
Well if you cant RUU you should try to get a custom rom to boot. First do these steps:
Unlock your bootloader.
Flash 4EXT recovery in fastboot. Then boot into recovery and turn on smartflash in tools menu.
Download Viper3D rom (the latest one) and transfer it to your sdcard.
Boot into recovery
wipe data/factory reset, wipe cache+dalvik
install viper3d rom. It will take a while, around 10 mins on synergy 4EXT alignment.
reboot and hope it boots
Click to expand...
Click to collapse
Thank you,
I have boot loop after installation,
regards,
Hi,
I have a Sprint CDMA HTC EVO 3D. I tried root and get S-OFF for it. Unfortunately I failed and now the phone fail to boot.
Below is what I did from which you might be able to diagnose it and give me suggestions.
(1) The original status of mu phone is:
Stock rom, I never root it before.
HBOOT-1.58.0000
Android Version: 4.03
HTC Sense version: 3.6
Software version: 2.95.651.6.710RD
(2) My root procedures:
I followed this post: http://forum.xda-developers.com/showthread.php?t=1813818
I successfully unlocked phone with HTCDev, successfully Flashed 4EXT recovery, and successfully installed Superuser-3.1.3-arm-signed.zip. I also booted into sytem, everything worked well.
However I failed in next step of JuopunutBear's Wire Trick (S-OFF). When I ran ControlBear.exe, it finally hanged there.
Current status of my phone:
Unfortunately I did not make a backup to my original ROM, so there is no way to revert back by restoring backup.
Now the phone is in unlocked status, I was able to boot to HBOOT and also enter 4Ext recovery, however I am not able to boot into Android. If I try to boot into Android, it always hang at black screen.
I am able to boot to fastboot (USB) mode, I tried to flash some stock ROM (listed at http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209), but I failed. For example, I ran a RUU of 2.89.exe, it detected my phone version is 2.95, and further update RUU failed.
Looks like my partition is ruined, but I might be wrong.
ANyone can help me to restore my phone to working status? At least I need the phone to be able to boo to Android.
Here are also some tries that I ever did:
(1) I ever put the PG86IMG.zip file (downloaded from http://forum.xda-developers.com/showpost.php?p=21593454&postcount=564) to my sdcard, still failed.
(2) I ever formatted all partition from 4EXT recovery
lsdyna said:
Here are also some tries that I ever did:
(1) I ever put the PG86IMG.zip file (downloaded from http://forum.xda-developers.com/showpost.php?p=21593454&postcount=564) to my sdcard, still failed.
(2) I ever formatted all partition from 4EXT recovery
Click to expand...
Click to collapse
EDIT:
Okay. I've got some questions.
1. You're stuck on some black screen as you said. It boots past the white HTC splash and then it's stuck on that black screen, right. Do you mean the juopunutbear "arrow screen" - juopunutbears boot.img?
2. I think if you had flashed the original boot img everything would have been fine.
3. The easiest way is to flash to stock, so lets try to figure out why it doesn't flash.
MrJyrks said:
Okay. So from what I understood, you are stuck on the black juopunutbear screen, right?
Click to expand...
Click to collapse
Yes, after I was stuck with black juopunutbear screen, I took battery out, reboot again, never was able to root to Android. I am only able to boot to HBoot.
lsdyna said:
Yes, after I was stuck with black juopunutbear screen, I took battery out, reboot again, never was able to root to Android. I am only able to boot to HBoot.
Click to expand...
Click to collapse
And you can boot to recovery, right?
EDIT:
One more thing. Which ruu were you trying to run
Edit2:
What's your CID? Use "fastboot getvar cid" or "fastboot oem readcid" (without quotes).
Edit3:
BTW, this was on the wire trick page... http://unlimited.io/jbtroubleshooting.htm - TROUBLESHOOTING There was everything you needed to know when you failed at something. Remember that page. You may need it the next time you try to do the wiretrick.
Q: Were you using a linux distro for the wire trick and did you use the appropriate files for wire trick since GB and ICS have separate tools?
If you want I may assist you in gaining s-off if we get this thing functional again.
Yes, I am able to boot to recovery.
I tried ROM's here
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
and
http://forum.xda-developers.com/showthread.php?p=22519105#post22519105
I tried 2.17, 2.89, unfortunately none of them worked
My CID is SPCS_001
MrJyrks said:
And you can boot to recovery, right?
EDIT: One more thing. Which ruu were you trying to run
Edit2: What's your CID? Use "fastboot getvar cid" or "fastboot oem readcid" (without quotes).
Click to expand...
Click to collapse
lsdyna said:
Yes, I am able to boot to recovery.
I tried ROM's here
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
and
http://forum.xda-developers.com/showthread.php?p=22519105#post22519105
I tried 2.17, 2.89, unfortunately none of them worked
My CID is SPCS_001
Click to expand...
Click to collapse
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Edit: This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Now I only want to revert my phone to stock, not considering root at present time.
I searched 2.95 ROM, unfortunately the highest version that I can find is 2.89. Does this mean I have no way to revert my phone to live? Thanks a lot.
MrJyrks said:
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Click to expand...
Click to collapse
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
MrJyrks said:
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Click to expand...
Click to collapse
lsdyna said:
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
Click to expand...
Click to collapse
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
My HBoot screen shows below:
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.000
RADIO-1.09.00.0108
OpenADSP-v02.6.0.2226.00.0217
DO you think I still have chance to save my device? Thanks a lot.
lsdyna said:
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
Click to expand...
Click to collapse
lsdyna said:
My HBoot screen shows below:
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.000
RADIO-1.09.00.0108
OpenADSP-v02.6.0.2226.00.0217
DO you think I still have chance to save my device? Thanks a lot.
Click to expand...
Click to collapse
If you have access to the recovery, most likely, yes.
Hello MrJyrks,
Thank you so much for the link! I am eager to try that. Before I do that I think I shall ask two questions to avoid further mess up the device:
Question #1: To install the deodexed rom, which is the correct way:
(1) Rename the ZIP file to PG86IMG.ZIP, put to root of sdcard, then boot, letting the Bootloader to do the update.
(2) In 4EXT recovery, enable smartflash, enable script asserts, then install the zip from the root of sdcard.
Question #2: You said I shall flash boot image, can you tell me how to do this? I mean, where shall I get the boot image file? Flash it with 4EXT? SHall I do it before or after install ROM zip file?
Thank you very much for your helps!!!
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
I tried install the stock ROM from your link (using 4EXT with smartflash enabled and script asserts enabled.) . Amazing that installation completed successfully (indeed this is the first ROM zip that I was able to install successfully since I mess up the device). When I exit After that, it did some further update which I guess is the boot.img that you mentioned.
4EXT it said 'a pending update for your boot partition is detected' and I think it was doing the boot image flash that you mentioned, right?
Unfortunately when I boo the device, I still got black screen.
Now I am unlocked and also rooted (since I successfully installed superuser in 4EXT). DO you think I shall lock the devioce before installing the stock ROM? If so, one possible issue is that if I relock the device, I found 4EXT is not available. In that case, how shall I install the ROM zip file?
Thanks.
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
Further update:
I flashed boot image by: fastboot flash boot boot.img which is included in the stock ROM zip file.
The flash went successfully. However, I am still not able to boot to Android. WHat I have is the device hang there, alternatively displaying logo with white background, and black screen.
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
I wiped cache and Dalvic, then re-flash the ROM, now I am able to boot as normal.
MrJyrks, you are my life save!!!
Your helps are sincerely appreciated !
lsdyna said:
I wiped cache and Dalvic, then re-flash the ROM, now I am able to boot as normal.
MrJyrks, you are my life save!!!
Your helps are sincerely appreciated !
Click to expand...
Click to collapse
You're welcome! I'm glad I could help!
---------- Post added at 12:02 PM ---------- Previous post was at 11:16 AM ----------
Oh, and if, in the future, you do try the wire trick and get stuck at some point you can revert the changes with ControlBear -r or ControlBear -f from command line. And you may also PM me if you need any help. Cheers!
MrJyrks, thank you so much!!!
MrJyrks said:
You're welcome! I'm glad I could help!
---------- Post added at 12:02 PM ---------- Previous post was at 11:16 AM ----------
Oh, and if, in the future, you do try the wire trick and get stuck at some point you can revert the changes with ControlBear -r or ControlBear -f from command line. And you may also PM me if you need any help. Cheers!
Click to expand...
Click to collapse
Similar problem, can't return to stock
I have a problem similar to lsdyna's, and am hoping that even though this post is old, MrJyrks or someone might be able to help me.
I am unsuccessfully trying to return my phone to stock. First a bit of history.
I had 2.95.651.6.710RD s-on hboot 1.58 Android Version: 4.03 HTC Sense version: 3.6 on my phone, and wanted root. I didn't need s-off, just wanted to root so could do some tweaking (stop some apps from autostarting, stop some form getting network access, etc.) so loaded 4EXT Recovery Touch, and got root (fastboot oem get_identifier_token method), got superuser in there, and happily began tweaking. Famous last words... I didn't make a backup right away (learned my lesson!) and suddenly found a 'overtweaked' sluggish phone on my hands.
Thought best thing would be to lose the root & return to stock & start over, carefully, making backups.
So I used Fastboot (fastboot oem lock) to lock it (worked) and proceeded to try to load RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe into it [via my computer], but didn't realize until reading MrJyrks post that a lower RUU couldn't be used.
I now am relocked (phone does boot up, but can tell the system tweaks are still slogging it), lost the recovery, and wondering what to do... do I try putting recovery back in & using the Negalite 2.95 stock deodex ROM MrJyrks mentioned? If so, how do I use that zip file method verses the exe one I tried thru my computer?
Thanks for the help
You had issues with the RUU because your main version is higher than that contained in the RUU.
Unlock, flash recovery again. Boot into recovery and flash this zip: https://copy.com/wlVvwssXXNN00Pe
That will lower your main version. Relock the bootloader, put the phone into fastboot USB mode, then run the RUU while in fastboot USB mode.
Should be back to stock after that.
I'm somewhat of a noob at this - this is my first HTC, so I had no idea what S-Off or unlocked bootloader meant. With my Samsung, rooting and installing a custom recovery involved a one-click method, so I never had to learn all the ins and outs of this stuff. With this DNA, I used the revone method (since the phone was purchased with 2.06 firmware already installed), so I still didn't need to learn much.
Anyway, I recently tried to go back to stock. I figured that would involve an RUU, going back to S-On, and locking the bootloader. So I first (yes, before performing the RUU like a dodo) used revone to go back to S-On, then found something saying I needed to execute "fastboot oem writesecureflag 3", so I did that, and now I am stuck at fastboot. I don't have access to CWM recovery, and if I try to boot beyond fastboot it hangs on the initial HTC screen.
Without being able to use ADB since it doesn't boot that far, I can't go back to S-Off via revone. I can't flash anything that I have been able to find so far via fastboot because it fails at signature verification. And I can't use the RUU that I found because it is firmware 1.15 and it won't allow me to install on top of 2.06.
Does anyone have any ideas on how to fix this? Is there a way to get to S-Off through fastboot? Is there an RUU for the 2.06 firmware? I have spent a few days searching and the answer to both seems to be no...
UPDATE: I grabbed the Rom.zip out of the 1.15 RUU and tried flashing that via fastboot (in RUU mode). I got the following message:
sending 'zip' (913111 KB)...
OKAY [ 35.667s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 118.073s
Click to expand...
Click to collapse
I assume this has something to do with the firmware version difference (1.15 vs. 2.06). But I was very excited to see a signature check be successful for once.
I should note that the ROM I was running when doing this was Newt's NOS m7 v 3.0.6
When selecting recovery from the fastboot menu, it does nothing?
If that's a yes... You need s-off again.
Phaded said:
When selecting recovery from the fastboot menu, it does nothing?
If that's a yes... You need s-off again.
Click to expand...
Click to collapse
It doesn't do nothing per se, it shows a screen that I'm not used to with a red triangle and exclamation point on top of a picture of a phone with a blue background. I assume this is the recovery screen from the factory, not the CWM recovery I had installed previously.
Is there a way to get s-off without ADB (only using fastboot)?
Flash firmware zip located on the moonshine thread, then use moonshine
Phaded said:
Flash firmware zip located on the moonshine thread, then use moonshine
Click to expand...
Click to collapse
I successfully flashed the firmware zip from the moonshine thread, but the phone still will not boot past fastboot. I assume since the instructions for moonshine require the phone to be booted to android, this option will not work for me.
jdpalmer2k13 said:
I successfully flashed the firmware zip from the moonshine thread, but the phone still will not boot past fastboot. I assume since the instructions for moonshine require the phone to be booted to android, this option will not work for me.
Click to expand...
Click to collapse
I've been thinking about this. Why did the firmware zip from Moonshine pass signature inspection? Was it signed? Could that same signature be placed on a rom or some other zip that installs a recovery or even somehow performs s-off? I know I am not very well experienced with android development, so I'm probably talking out of my ass.
I recently flashed the RUU from fastboot.
http://forum.xda-developers.com/showthread.php?t=2115987 post#4
I believe what you are looking for is in this thread.
To get back to stock on my phone I needed to flash the stock hboot first before I could use the stock RUU
bwhxeon said:
I believe what you are looking for is in this thread.
To get back to stock on my phone I needed to flash the stock hboot first before I could use the stock RUU
Click to expand...
Click to collapse
I can't flash the stock hboot because I'm s-on and the file fails signature verification.
jdpalmer2k13 said:
I can't flash the stock hboot because I'm s-on and the file fails signature verification.
Click to expand...
Click to collapse
Then your pretty much out of luck. Need to exchange it or possibly do a jtag. Does your phone say tampered/relocked? If so then I'd guess Jtag is the only solution.
Unfortunately the guide you used to go back to stock was pretty dumb in telling you make your phone s-on again. It isn't needed especially if it was just so you could do a clean install and flash other roms.
I was in your situation, but I was lucky enough to have unlocked my phone using htcdev when Jcase released his original unlock method. If the super cid method still works. I would unlock my bootloader the super cid method and not even bother with moonshine. That way you end up with a unlock token and wouldn't get stuck in this situation.
bwhxeon said:
Then your pretty much out of luck. Need to exchange it or possibly do a jtag. Does your phone say tampered/relocked? If so then I'd guess Jtag is the only solution.
Unfortunately the guide you used to go back to stock was pretty dumb in telling you make your phone s-on again. It isn't needed especially if it was just so you could do a clean install and flash other roms.
I was in your situation, but I was lucky enough to have unlocked my phone using htcdev when Jcase released his original unlock method. If the super cid method still works. I would unlock my bootloader the super cid method and not even bother with moonshine. That way you end up with a unlock token and wouldn't get stuck in this situation.
Click to expand...
Click to collapse
Nothing was wrong with the guide. He didn't follow it correctly as he did s-on using revone.
Flashing the firmware zip should allow you to boot up and run moonshine. Are you sure it flashed correctly.
Phaded said:
Nothing was wrong with the guide. He didn't follow it correctly as he did s-on using revone.
Flashing the firmware zip should allow you to boot up and run moonshine. Are you sure it flashed correctly.
Click to expand...
Click to collapse
Correct, the guide was not at fault here, I am just an idiot. Here are the results of flashing the dna2.06firmware.zip file from the moonshine thread: http://pastebin.com/GkgdGt19
Following what is shown at this link, I executed "fastboot reboot-bootloader", selected "Power Down", and then tried to turn the phone on again. I got the same result as always (stuck on the initial HTC quietly brilliant screen - not the bootanimation screen).
Spoke with beaups on IRC. I was running a 4.2 rom that will not run on the stock kernel. Since the only thing I can flash is the signed stock kernel because I am s-on, the only remaining option is to run a 2.06 RUU. However, the 2.06 RUU has not been leaked to anyone's knowledge. So I will have to send off for jtag in order to get s-off, then flash whatever - RUU, custom ROM, what-have-you.
Thanks all for trying to help. I will hang on to it for a while if anyone has any other thoughts or suggestions.
jdpalmer2k13 said:
Spoke with beaups on IRC. I was running a 4.2 rom that will not run on the stock kernel. Since the only thing I can flash is the signed stock kernel because I am s-on, the only remaining option is to run a 2.06 RUU. However, the 2.06 RUU has not been leaked to anyone's knowledge. So I will have to send off for jtag in order to get s-off, then flash whatever - RUU, custom ROM, what-have-you.
Thanks all for trying to help. I will hang on to it for a while if anyone has any other thoughts or suggestions.
Click to expand...
Click to collapse
I talked to beaups last night about the same thing... Hes a good guy. I'm in the exact same boat. I hope there is a break through on this but if not I guess JTAG is our only option. Let me know if you figure anything out jdpalmer, i'd really appreciate it.
Try this please
fastboot oem readcid
What's it say?
Phaded said:
Try this please
fastboot oem readcid
What's it say?
Click to expand...
Click to collapse
VZW_001 for me. Not trying to jack your thread jd, it just seems we have screwed up in the exact same manner.
PiperBen85 said:
VZW_001 for me. Not trying to jack your thread jd, it just seems we have screwed up in the exact same manner.
Click to expand...
Click to collapse
Yep same here
jdpalmer2k13 said:
Yep same here
Click to expand...
Click to collapse
You are s-on... Are you also locked?
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
It's possible you might have supercid, although I doubt it
You could try
Fastboot oem writecid 22222222
Reboot
Fastboot oem readcid
Did it change?
Phaded said:
You are s-on... Are you also locked?
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
It's possible you might have supercid, although I doubt it
You could try
Fastboot oem writecid 22222222
Reboot
Fastboot oem readcid
Did it change?
Click to expand...
Click to collapse
Yes, I am locked. Here is the result of trying to writecid:
Code:
C:\Android>fastboot oem writecid 22222222
...
(bootloader) [SD_ERR] The project does not support SD card
(bootloader) E0902910 E0902E20
FAILED (status read failed (Too many links))
finished. total time: 0.005s
Hello there.
I have been trying at this for a while now but simply cannot figure out how to get around this issue. I have successfully rooted my M8 but now I am trying to install OTA updates. I looked up a guide on how to do this and came to this video:
Everything was going swimmingly until about minute 7 in the video where the step is to and go ahead with the OTA updates. When my phone restarts to install the updates the progress bar loads to about 1/5 and then stops for a few moments before giving me the triangle red exclamation mark icon.
How do I get around this? I'm fairly certain I have the right stock recovery. All I want to do is install the OTA updates without losing any of my current apps/settings. If an easier process is to unroot my phone and leave it that way then so be it.
Phone INFO:
CID: T-MOB010
version 4.4.4
HTC sense v. 6.0
software #: 3.32.531.2
SDK API level: 6.25
Any help pointing me in the right direction would be swell. I apologize in advance for the tall order. Thanks.
blinkdagger said:
Hello there.
I have been trying at this for a while now but simply cannot figure out how to get around this issue. I have successfully rooted my M8 but now I am trying to install OTA updates. I looked up a guide on how to do this and came to this video:
Everything was going swimmingly until about minute 7 in the video where the step is to and go ahead with the OTA updates. When my phone restarts to install the updates the progress bar loads to about 1/5 and then stops for a few moments before giving me the triangle red exclamation mark icon.
How do I get around this? I'm fairly certain I have the right stock recovery. All I want to do is install the OTA updates without losing any of my current apps/settings. If an easier process is to unroot my phone and leave it that way then so be it.
Phone INFO:
CID: T-MOB010
version 4.4.4
HTC sense v. 6.0
software #: 3.32.531.2
SDK API level: 6.25
Any help pointing me in the right direction would be swell. I apologize in advance for the tall order. Thanks.
Click to expand...
Click to collapse
If I remember correctly, you can't be rooted doing official ota updates. Finish updates, then root
BR7fan said:
If I remember correctly, you can't be rooted doing official ota updates.
Click to expand...
Click to collapse
Ok, do you think it's worthwhile to manually do the updates?
blinkdagger said:
Ok, do you think it's worthwhile to manually do the updates?
Click to expand...
Click to collapse
Yeah I found them to be those guys get the latest up very quick. Make sure your s-off
BR7fan said:
Yeah I found them to be those guys get the latest up very quick. Make sure your s-off
Click to expand...
Click to collapse
Ok thanks a lot. I will try to manually install the updates.
BR7fan said:
If I remember correctly, you can't be rooted doing official ota updates. Finish updates, then root
Click to expand...
Click to collapse
You would be remembering incorrectly. Root has no impact itself on whether an OTA will install. As long as no system files have been altered by the user (using root permissions), and stock recovery is installed. Root and unlocked bootloader are both okay. Although you will most likely lose root after the update.
---------- Post added at 09:52 AM ---------- Previous post was at 09:50 AM ----------
blinkdagger said:
Phone INFO:
CID: T-MOB010
version 4.4.4
HTC sense v. 6.0
software #: 3.32.531.2
SDK API level: 6.25
Click to expand...
Click to collapse
Is your phone the T-Mob version, or an AT&T version converted to T-Mob? Because this is the AT&T version specific forum section.
Another option to update would be to just run the T-Mobile Lollipop RUU. Relock the bootloader if you are s-on. Biggest downside, is that RUU will wipe the phone; and keeping user data may be your reason for seeking the OTA route.
redpoint73 said:
You would be remembering incorrectly. Root has no impact itself on whether an OTA will install. As long as no system files have been altered by the user (using root permissions), and stock recovery is installed. Root and unlocked bootloader are both okay. Although you will most likely lose root after the update.
---------- Post added at 09:52 AM ---------- Previous post was at 09:50 AM ----------
Is your phone the T-Mob version, or an AT&T version converted to T-Mob? Because this is the AT&T version specific forum section.
Another option to update would be to just run the T-Mobile Lollipop RUU. Relock the bootloader if you are s-on. Biggest downside, is that RUU will wipe the phone; and keeping user data may be your reason for seeking the OTA route.
Click to expand...
Click to collapse
I think I may have posted in the wrong forum. My phone is simply the T-Mobile version as far as I know. I think I may have changed some system files around. Do you know of a way to reset them to default that way I can proceed with the OTA updates? I do want to keep all the apps and user settings. My plan was to re root the phone after the OTA updates were done. Thanks for your help.
blinkdagger said:
I think I may have posted in the wrong forum. My phone is simply the T-Mobile version as far as I know.
Click to expand...
Click to collapse
T-Mobile has its own section, so yes this is the wrong forum section. But I'll try to help anyway, as your issues aren't that carrier specific.
blinkdagger said:
I think I may have changed some system files around. Do you know of a way to reset them to default that way I can proceed with the OTA updates?
Click to expand...
Click to collapse
Few different options.
1) Just restore the nandroid backup you made before messing with system files. And you did this, like you should before making any such mods, RIGHT? Well if not:
2) You can manually change them all back. Probably the most tedious method, especially since you don't seem sure of what you changed.
3) Find the right stock nandroid and flash it. Find corresponding stock recovery, and flash it.
4) Relock the bootloader and RUU to stock, and since you can just RUU to the current OS version, no need to OTA. After that, just unlock the bootloader again via HTCDev.com (of if you want to avoid that, sunshine) in preparation for installing custom recovery (and root) again. Yes, RUU will wipe that phone, but that brings us to the next point:
blinkdagger said:
I do want to keep all the apps and user settings. My plan was to re root the phone after the OTA updates were done. .
Click to expand...
Click to collapse
You are rooted, so back up your apps and app data with Titanium Backup (or similar root app). Then you can just restore all the apps and app data after you RUU. You should be backing them up anyway. Saying you want to keep your app data; then not having them backed up is a contradiction. If you data is important to you, back it up. And that advice goes for whether you decide to RUU or not.
Backing up setting with Titanium across ROM versions is not recommended. But unless you have a really large amount of settings customizations, it usually doesn't take that much time to set these up again manually, anyway (as long as your apps and app data are already restorable).
Option 4 above is what I would consider. Its really up to you whether options 3 or 4 are best for you. But the reason I like RUU, even though it has the extra steps of relocking/unlocking the bootloader, and backing up your data; what it saves you is from finding the right stock nandroid and stock recovery, and putting them to the correct location on the phone to then Restore with TWRP. And these steps are ones with potential for mistakes that can make them exhaust a lot more time than you would think. RUU is a complete factory image, so everything is sure to play well together, no guesswork or potential for mistakes.
redpoint73 said:
T-Mobile has its own section, so yes this is the wrong forum section. But I'll try to help anyway, as your issues aren't that carrier specific.
Few different options.
1) Just restore the nandroid backup you made before messing with system files. And you did this, like you should before making any such mods, RIGHT? Well if not:
2) You can manually change them all back. Probably the most tedious method, especially since you don't seem sure of what you changed.
3) Find the right stock nandroid and flash it. Find corresponding stock recovery, and flash it.
4) Relock the bootloader and RUU to stock, and since you can just RUU to the current OS version, no need to OTA. After that, just unlock the bootloader again via HTCDev.com (of if you want to avoid that, sunshine) in preparation for installing custom recovery (and root) again. Yes, RUU will wipe that phone, but that brings us to the next point:
You are rooted, so back up your apps and app data with Titanium Backup (or similar root app). Then you can just restore all the apps and app data after you RUU. You should be backing them up anyway. Saying you want to keep your app data; then not having them backed up is a contradiction. If you data is important to you, back it up. And that advice goes for whether you decide to RUU or not.
Backing up setting with Titanium across ROM versions is not recommended. But unless you have a really large amount of settings customizations, it usually doesn't take that much time to set these up again manually, anyway (as long as your apps and app data are already restorable).
Option 4 above is what I would consider. Its really up to you whether options 3 or 4 are best for you. But the reason I like RUU, even though it has the extra steps of relocking/unlocking the bootloader, and backing up your data; what it saves you is from finding the right stock nandroid and stock recovery, and putting them to the correct location on the phone to then Restore with TWRP. And these steps are ones with potential for mistakes that can make them exhaust a lot more time than you would think. RUU is a complete factory image, so everything is sure to play well together, no guesswork or potential for mistakes.
Click to expand...
Click to collapse
Hey thanks for all the help. I have decided to use Option 4 but I have discovered that my phone is still S-ON. I found this thread which seems to be able to provide me with the right RUU file.
http://forum.xda-developers.com/showthread.php?t=2754063
The only issue is that at the top of the thread it says that these RUUs are meant for S-OFF users. After searching a bit I learned that supposedly http://theroot.ninja/ is the only way to change my phone from S-ON to S-OFF. I just don't want to pay 25 bucks if I don't have to. Is this the only way?
blinkdagger said:
Hey thanks for all the help. I have decided to use Option 4 but I have discovered that my phone is still S-ON. I found this thread which seems to be able to provide me with the right RUU file.
http://forum.xda-developers.com/showthread.php?t=2754063
The only issue is that at the top of the thread it says that these RUUs are meant for S-OFF users. After searching a bit I learned that supposedly http://theroot.ninja/ is the only way to change my phone from S-ON to S-OFF. I just don't want to pay 25 bucks if I don't have to. Is this the only way?
Click to expand...
Click to collapse
Yes. As of this date, Sunshine is the only way to gain S-Off for the M8. Firewater is discontinued.
blinkdagger said:
Hey thanks for all the help. I have decided to use Option 4 but I have discovered that my phone is still S-ON. I found this thread which seems to be able to provide me with the right RUU file.
http://forum.xda-developers.com/showthread.php?t=2754063
The only issue is that at the top of the thread it says that these RUUs are meant for S-OFF users. After searching a bit I learned that supposedly http://theroot.ninja/ is the only way to change my phone from S-ON to S-OFF. I just don't want to pay 25 bucks if I don't have to. Is this the only way?
Click to expand...
Click to collapse
The s-off statement in the thread you linked was specific to firmware packages. S-off is required to flash a firmware.zip, not an RUU. Those are 2 very different things.
RUU will run fine with s-on, as long as you relock the bootloader; and also you can only run an RUU that is equal or greater than the software version you rooted (looks like Android 4.4.4). So what you want is a T-Mobiel RUU for either Android 4.4.4 (software 3.xx) than OTA to Android 5.0; or RUU right to Android 5.0 (software 4.xx).
redpoint73 said:
The s-off statement in the thread you linked was specific to firmware packages. S-off is required to flash a firmware.zip, not an RUU. Those are 2 very different things.
RUU will run fine with s-on, as long as you relock the bootloader; and also you can only run an RUU that is equal or greater than the software version you rooted (looks like Android 4.4.4). So what you want is a T-Mobiel RUU for either Android 4.4.4 (software 3.xx) than OTA to Android 5.0; or RUU right to Android 5.0 (software 4.xx).
Click to expand...
Click to collapse
Hey I know it has been a while but I just got around to taking care of this. I want to use an RUU to reset everything like you mentioned. The trouble I am now having is with the re-locking procedure.
I am trying to to relock the bootloader using the "fastboot oem lock" command. When I enter the command I get this message.
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.194s
I have done this about 5 times now and the lock status remains "UNLOCKED". Thank you for all your help thus far. I will continue to try to search for a solution.