Related
Dear xda-community,
as said in the title i dont know if i bricked my device by trying to get s-on again.
At first i read some threads here about getting s-on again and revert to stock.
I was s-off by revelutionary and flashed the ENG-hboot a few days ago (0.98.2000). After that i flashed the stock 1.47 rom and was trying to get s-on and stock again with the 1.47 RUU. I read that if i have the ENG-hboot i can run the RUU and then i get back to stock and s-on. But after i was running the RUU, i get to the bootloader again (on the phone). In the header stands now "*** Security Warning ***" and i'm s-on again like i want it with hboot 0.98.0002.
But the problem is that i cant get out of the bootloader, i can only acsses fastboot and the bootloader. If i click 'recovery', 'reboot' or anything else it only restarts the bootloader. I cant even turn the phone off, only with pulling the battery :/
So i'm stucked in the hboot 0.98.0002 with s-on and i dont know what i can do now or if i bricked my desire s permanently
Can anyone help me please?
are you sure that you have used the right RUU?
amidabuddha said:
are you sure that you have used the right RUU?
Click to expand...
Click to collapse
yes, i used the htc_saga_europe... 1.47 and im on a unbranded phone, so this is the right, isnt it?
Jahai said:
yes, i used the htc_saga_europe... 1.47 and im on a unbranded phone, so this is the right, isnt it?
Click to expand...
Click to collapse
It should be if you bought it in Europe. What happens when you try the RUU again? You should do this when "FASTBOOT USB" is written on your phone screen.
amidabuddha said:
It should be if you bought it in Europe. What happens when you try the RUU again?
Click to expand...
Click to collapse
yes, i bought and use it in germany. if i try it again it get aborted after receiving the information from the phone and tells me something about a error 140: bootloader error and in the manuel isnt an entry for error 140 :S
Jahai said:
yes, i bought and use it in germany. if i try it again it get aborted after receiving the information from the phone and tells me something about a error 140: bootloader error and in the manuel isnt an entry for error 140 :S
Click to expand...
Click to collapse
Ok there is what you can do:
run RUU without a connected phone. Let the screen open. Go to WIndows Explorer, C drive and type in the search box : rom.zip. When you find it copy it to another place and close the RUU window.
Then extract from the rom.zip these images: system.img, boot_signed.img, recovery_signed.img
If you do not have fastboot command use the Guide in my signature. Then in cmd on your PC with phone in "fastboot usb" mode type:
Code:
fastboot flash system {path to the file}\system.img
fastboot flash boot {path to the file}\boot_signed.img
fastboot flash recovery {path to the file}\recovery_signed.img
where {patho to the file}\ should be replaced with the the actual path to the file from your Windows Explorer (like C:\android\images)
then, if the flashing is successful try to reboot to OS (wait several minutes on the white screen it can take some time to load)
This solution is taken from here, credits to degit
amidabuddha said:
Ok there is what you can do:
run RUU without a connected phone. Let the screen open. Go to WIndows Explorer, C drive and type in the search box : rom.zip. When you find it copy it to another place and close the RUU window.
Then extract from the rom.zip these images: system.img, boot_signed.img, recovery_signed.img
If you do not have fastboot command use the Guide in my signature. Then in cmd on your PC with phone in "fastboot usb" mode type:
Code:
fastboot flash system {path to the file}\system.img
fastboot flash boot {path to the file}\boot_signed.img
fastboot flash recovery {path to the file}\recovery_signed.img
where {patho to the file}\ should be replaced with the the actual path to the file from your Windows Explorer (like C:\android\images)
then, if the flashing is successful try to reboot to OS (wait several minutes on the white screen it can take some time to load)
This solution is taken from here, credits to degit
Click to expand...
Click to collapse
thank you for your help!
i will try that and report back in a few minutes
hm
i cant get it to work in this way :/
if i write fastboot flash system C:\android-tools\system.img
it tells me:
"sending 'system' (571388 KB)...
OKAY [93.130s]
writing 'system'...
(bootloader) signature cheking...
FAILED (remote: signature verify fail)
finished. total time: 166.095s"
its the same with boot_signed.img and recovery_signed.img
if i try fastboot getvar version-main i get : 11.10.401.4
think there is a typo, shouldnt it be 2.10.401.4? could it be this and if yes how could i change it?
So you problem maybe sounds the same, but it is not.
Try
Code:
fastboot oem rebootRUU
Your phone will reboot to a black screen with silver HTC logo. Then run the RUU.
Other options is to go to the repair centre and tell them that this happened during OTA update.
Sent from my HTC Desire S using Tapatalk
Jahai said:
if i try fastboot getvar version-main i get : 11.10.401.4
think there is a typo, shouldnt it be 2.10.401.4? could it be this and if yes how could i change it?
Click to expand...
Click to collapse
Hmm that's new. Have you flashed a new radio recently? Anyway try the latest RUU 2.10.401.8.
Sent from my HTC Desire S using Tapatalk
amidabuddha said:
Hmm that's new. Have you flashed a new radio recently? Anyway try the latest RUU 2.10.401.8.
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
will try it with that. since now i tried it until 2.10.401.4
Edit: it took me ages to download that ruu from filefacrtory :/
i got the same error 140 with the last 2.10.401.8 RUU
looks like it is stucked in that bootloader for ever
Jahai said:
i got the same error 140 with the last 2.10.401.8 RUU
looks like it is stucked in that bootloader for ever
Click to expand...
Click to collapse
Go to repair center and say that the OTA update did this (it is the same as RUU) They should repair it for free
Sent from my HTC Desire S using Tapatalk
maybe there is any way to get s-off from fastboot or bootloader?
got to new hboot with this instruction: http://forum.xda-developers.com/showpost.php?p=20850548&postcount=22
managed to get the unlocktoken from htcdev but if i flash it everything themes fine, but i cant choose the option yes (unlock bootloader).
if i choose "no" and press the power button it reboots like it should but if i choose "yes" and press the power button nothing happens. i can still choose between the options but nothing happens :/
anyone know how i can get it working to unlock this bootloader and flash a custom recovery?
I attempted to place a ROM on the phone using CWM recovery and something messed up. Now, I can boot into screen that says fastboot, recovery, etc. However, when I select recovery, nothing happens. Anyone point me in the right direction...im back to using my Blackberry!
From fastboot try and reflash recovery I would highly suggest twrp over cwm since twrp officially supports the one x.
Sent from my Nocturnalized Beast
E.Cadro said:
From fastboot try and reflash recovery I would highly suggest twrp over cwm since twrp officially supports the one x.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
This is where I am stuck. Unfortunately, I'm not all that familiar with Fastboot. When connecting the phone to the PC with a USB, I see that the phone says Fatboot USB. From there I'm lost. I've not been able to find a guide that describes how to install a ROM using fastboot. Lots of posts says that it can be done, but none describing how its done. Anyone pointing me in the right direction?
http://forum.xda-developers.com/showthread.php?t=1754018
gunnyman said:
http://forum.xda-developers.com/showthread.php?t=1754018
Click to expand...
Click to collapse
Im still having difficulty loading a recovery via fastboot...
I get to the point where I enter the following line in command prompt...fastboot flash recovery twrp.img and the response I get is "error: cannot load 'twrp.img"
Any suggestions?
rpritch said:
Im still having difficulty loading a recovery via fastboot...
I get to the point where I enter the following line in command prompt...fastboot flash recovery twrp.img and the response I get is "error: cannot load 'twrp.img"
Any suggestions?
Click to expand...
Click to collapse
My Bad...didnt have the img file in the platform-tools folder.
So I've tried flashing the TRWP img and when I reboot into recover, I get the blue and black Teamwin splash screen. then it reboots and stays permanently on the HTC splash screen.
After I flash the clockwork img file and reboot into recovery, it reboots and stays permanetly on the HTC splash screen.
Any suggestions?
rpritch said:
My Bad...didnt have the img file in the platform-tools folder.
So I've tried flashing the TRWP img and when I reboot into recover, I get the blue and black Teamwin splash screen. then it reboots and stays permanently on the HTC splash screen.
After I flash the clockwork img file and reboot into recovery, it reboots and stays permanetly on the HTC splash screen.
Any suggestions?
Click to expand...
Click to collapse
I am having this same exact issue! Did you figure it out? I installed TWRP as well and now get the Teamwin screen before it reboots the the HTC screen with the legal disclaimer. Please help1
veritas2884 said:
I am having this same exact issue! Did you figure it out? I installed TWRP as well and now get the Teamwin screen before it reboots the the HTC screen with the legal disclaimer. Please help1
Click to expand...
Click to collapse
Sounds like a bad flash or corrupt recovery inage. Go to the play store and download goo manager and install twrp from goo manager instead. See if that fixes the problem.
Sent from my Nocturnalized Beast
E.Cadro said:
Sounds like a bad flash or corrupt recovery inage. Go to the play store and download goo manager and install twrp from goo manager instead. See if that fixes the problem.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
Our devices will not boot. All we can get is either the white HTC Screen or get into the menu that allows fastboot/recover/ect...
Relock bootloader, run real stock ruu for your carrier, reunlock, reroot, reflash recovery. Flash your desired Rom. You will lose all data on phone!
Sent from my HTC One XL using xda app-developers app
c5satellite2 said:
Relock bootloader, run real stock ruu for your carrier, reunlock, reroot, reflash recovery. Flash your desired Rom. You will lose all data on phone!
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
That is what I am doing now. I did not relock the boot loader first it is in the process of running the RUU. Did I just fry my phone even more?
---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------
Thanks c5satellite2 ,
For my AT&T One X I fixed it as you stated
Booted into fastboot
Used command window to relock bootloader:
fastboot devices <enter>
fastboot oem lock <enter>
Restarted and rebooted into fastboot again
Ran Stock Rom RUU Program from http://forum.xda-developers.com/showthread.php?t=1649658
Put me back to a working stock phone.
Re-rooted and re-unlocked bootloader
Installed TWRP this time! Thanks for the help! :good:
Recommended process for fixing strange issues like what you were experiencing. Glad it helped you guys out!
Sent from my HTC One XL using xda app-developers app
veritas2884 said:
That is what I am doing now. I did not relock the boot loader first it is in the process of running the RUU. Did I just fry my phone even more?
---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------
Thanks c5satellite2 ,
For my AT&T One X I fixed it as you stated
Booted into fastboot
Used command window to relock bootloader:
fastboot devices <enter>
fastboot oem lock <enter>
Restarted and rebooted into fastboot again
Ran Stock Rom RUU Program from http://forum.xda-developers.com/showthread.php?t=1649658
Put me back to a working stock phone.
Re-rooted and re-unlocked bootloader
Installed TWRP this time! Thanks for the help! :good:
Click to expand...
Click to collapse
How exactly did you do this part "Ran Stock Rom RUU Program from http://forum.xda-developers.com/show....php?t=1649658"? What command did you use?
rpritch said:
How exactly did you do this part "Ran Stock Rom RUU Program from http://forum.xda-developers.com/show....php?t=1649658"? What command did you use?
Click to expand...
Click to collapse
It's just an exe. Boot your phone into fastboot mode. Your computer will recognize that it is plugged in in fast boot mode if you have the HTC driver installed. Then open the exe on your computer and follow the instructions on the screen. It will take about 15 mins for the whole process and your phone will reboot several times.
Also make sure you use twrp recovery instead of clockwork if you re-root!
veritas2884 said:
It's just an exe. Boot your phone into fastboot mode. Your computer will recognize that it is plugged in in fast boot mode if you have the HTC driver installed. Then open the exe on your computer and follow the instructions on the screen. It will take about 15 mins for the whole process and your phone will reboot several times.
Also make sure you use twrp recovery instead of clockwork if you re-root!
Click to expand...
Click to collapse
I cant seem to find a stock Rogers Ruu...will continue searching. Anyone out there have it?
http://http://forum.xda-developers.com/showthread.php?p=27882810#post27882810
Finally got it working...the above link is what worked. Here is the summary...
I was having this same problem and it took a while before I could get it to work. Try opening a command window in the same location of your adb tools.
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
Hopefully this helps you out!
Berserk87 said:
I'm stock right now (rooted) , but the updates keep failing, so i want to reflash stock rom.
I'm lost as to how to do this.
I downloaded ARUwizard and the stock rogers rom (PJ83IMG) but its still failing. I dont get all this adb tools stuff.
Click to expand...
Click to collapse
do this:
1.Put Rogers stock zip (keep it in zip form) in your platform-tools folder (you need to download Android SDK). This is the rogers file I downloaded...http://rapidlibrary.com/files/pj83i...elease-254934-signed-zip_ulc8eyefx8i89on.html
2. Boot phone into fastboot (hold power button and volume down key)
3. Used command window to relock bootloader by doing the following:
use command window to get to location on your computer where you have saved SDK stuff, continue with command window to the platform-tools folder then enter the following commands:
fastboot devices <enter>
fastboot oem lock <enter>
Phone will restart and reboot into fastboot again
4. type 'fastboot oem rebootRUU'.
5. Next, make sure you have the .zip RUU file in the same folder (see step 1) and type 'fastboot flash zip XXX.zip' (replace XXX with whatever the rogers stock zip is called, I changed it to "rogersstock.zip")
Phone will reboot to a HTC screen. If you see "re-flush image immediately", repeat fastboot flash zip XXX.zip command. You may have to do this 2 or 3 times.
After doing this, I was able to download and install the Rogers firmware update
BTW...I didn't discover any of this stuff on my own...I researched a bunch of different posts and put it together. Hopefully, someone else finds have all this in one post useful.
Hey guys, AT&T One X unlocked
I'm having a similar problem, been following the wiki exactly and when I flashed CWM recovery and it says it was successful:
F:\Users\Ryan\AppData\Local\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.890s]
writing 'recovery'...
OKAY [ 1.480s]
finished. total time: 2.380s
When I select recovery it brings up the HTC logo and says in red text "This build is for development purposes only. Do not distribute without HTCs written permission... etc" after about 10 seconds the device boots up as normal.
Not sure what I'm doing wrong.
slash178 said:
Hey guys, AT&T One X unlocked
I'm having a similar problem, been following the wiki exactly and when I flashed CWM recovery and it says it was successful:
F:\Users\Ryan\AppData\Local\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.890s]
writing 'recovery'...
OKAY [ 1.480s]
finished. total time: 2.380s
When I select recovery it brings up the HTC logo and says in red text "This build is for development purposes only. Do not distribute without HTCs written permission... etc" after about 10 seconds the device boots up as normal.
Not sure what I'm doing wrong.
Click to expand...
Click to collapse
What you are doing wrong is flashing the recovery for the wrong phone. Any file with "enveavoru" in it is for the international (Tegra3) version. Our phone is "evita".
Only install things in our Dev forum:
http://forum.xda-developers.com/forumdisplay.php?f=1541
To see everything in an organized list, go to my index: http://forum.xda-developers.com/showthread.php?t=1671237
Also, TWRP is recommended. CWM does not officially support our device, and therefore is just a port, and buggy. TWRP officially supports our device.
im getting the same error and im using the recovery ending on evita
Hi !
I have been trying to fix my htc one s (s4) for several days now, and i'm stuck.
I tried to update my HBOOT and get back to stock rom by flashing a RUU but I got the wrong one (signature verification fail) but I'm not sure that's what caused the problem.
When I plug my phone in in recovery (TWRP or CWM) an empty disk is detected on my computer but no sd card so i can't format it or load another ROM to be flashed.
I did a factory reset to see if it would fix it but it did not.
I have no ROM left on my phone, no backup available, adb does not work ( each adb command gets me a error:device not found ) and adb devices can't see my phone.
My HTC Drivers are updated.
Fastboot and bootloader, however, still work.
I have tried changing cable.
When I wipe dalvik in TWRP, I get this line among the other ones in the log:
/sd-ext not present, skipping
when i do a factory reset one of the line is
E: unknowv olume for path [/sd-ext]
And sometimes, although I'm not sure what triggers it, I get a bunch of
Unable to open ums lunfile (No such file or directory)
My phone is S-ON, H-BOOT is 1.14.0002
I don't know what to try anymore I hope I'm not the owner of a shiny little brick.
Does anyone have any ideas what my fix it ?
I apologize for my english if my grammar is poor, I'm French.
Any help would be appreciated. Thanks.
dominolapin said:
Hi !
I have been trying to fix my htc one s (s4) for several days now, and i'm stuck.
I tried to update my HBOOT and get back to stock rom by flashing a RUU but I got the wrong one (signature verification fail) but I'm not sure that's what caused the problem.
When I plug my phone in in recovery (TWRP or CWM) an empty disk is detected on my computer but no sd card so i can't format it or load another ROM to be flashed.
I did a factory reset to see if it would fix it but it did not.
I have no ROM left on my phone, no backup available, adb does not work ( each adb command gets me a error:device not found ) and adb devices can't see my phone.
My HTC Drivers are updated.
Fastboot and bootloader, however, still work.
I have tried changing cable.
When I wipe dalvik in TWRP, I get this line among the other ones in the log:
/sd-ext not present, skipping
when i do a factory reset one of the line is
E: unknowv olume for path [/sd-ext]
And sometimes, although I'm not sure what triggers it, I get a bunch of
Unable to open ums lunfile (No such file or directory)
My phone is S-ON, H-BOOT is 1.14.0002
I don't know what to try anymore I hope I'm not the owner of a shiny little brick.
Does anyone have any ideas what my fix it ?
I apologize for my english if my grammar is poor, I'm French.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Well the good thing is you don't have a bricked device your just in a bad spot atm so
Wipe the sd card in twrp from wipe menu
Download the newist ruu before you do that flash stock recovery and relock bootloader then flash the ruu
Sent from my HTC One S using Tapatalk 4
Flashalot said:
Well the good thing is you don't have a bricked device your just in a bad spot atm so
Wipe the sd card in twrp from wipe menu
Download the newist ruu before you do that flash stock recovery and relock bootloader then flash the ruu
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
I tried nevertheless to lock and run the ruu.
upon lock:
c:\fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Unknown error))
finished. total time: 0.944s
upon ruu:
it starts normally and then ERROR 131 error id client
and that's it.
my ruu is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
I tried nevertheless to lock and run the ruu.
upon lock:
c:\fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Unknown error))
finished. total time: 0.944s
upon ruu:
it starts normally and then ERROR 131 error id client
and that's it.
my ruu is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
"STOCK" recovery. I think you have tried with CUSTOM recovery.
Here is the link for stock recovery. The second download link is the stock recovery image
Flash stock recovery, then relock boot loader and then follow the above procedure :good:
Actually I did flash the stock recovery I just typed custom by mistake. Sorry about that. The one I flashed even came from the same link .
I searched on the forums and I might not have flashed the right ruu.
But i can't seam to find the right one, because strangely "fastboot getvar version-main" gives a blank result.
Hboot 1.14.0002
radio 1.08es.50.02.16
CID HTC_247
I have been trying to unbrick my phone for 2 days now. So right now when I boot it goes through the boot screens then it goes black and just says
"process system ins't responding" , so if i press wait that error will just pop up again. Otherwise all I get is a black screen and have to force reboot.
So here is what I have done so far:
When bought phone I did S-OFF and have it unlocked "I believe it was with firewater, but that was months ago",
Installed CWM 6.0.4.8 <--im pretty sure thats the one.
Created nandroid
Then I installed SKYFALL and used that ever since.
Decided I wanted ViperOne.
Read many post and here is where the fun started.
Restored my origional nandroid.
fastboot flashed stock recovery then erase cache
booted nandroid. and installed downloaded 4.4.3 OTA
phone rebooted just fine.
fastboot flashed twrp recovery (openrecovery-twrp-2.8.0.3-m8_wlv.img) then erase cache
booted recovery and installed ViperOne.
then error process system isn't responding.
Since then I have repeated those steps. I have also tried CleanRom and RKDN and those get stuck in loading loops. I have tried the RUU options, and tried RUU and fastboot to get back to the 1.55.605.2 completely stock as it can be with a stock image or the nandroid and nothing seems to work. Just get the same errors. Now I am stuck and unsure what to do or how to go about fixing this....
Not sure if you've already tried this, but might help.
Load the RUU from here http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144
After that, go into the stock recovery and do a factory reset.
dab1414 said:
I have been trying to unbrick my phone for 2 days now. So right now when I boot it goes through the boot screens then it goes black and just says
"process system ins't responding" , so if i press wait that error will just pop up again. Otherwise all I get is a black screen and have to force reboot.
So here is what I have done so far:
When bought phone I did S-OFF and have it unlocked "I believe it was with firewater, but that was months ago",
Installed CWM 6.0.4.8 <--im pretty sure thats the one.
Created nandroid
Then I installed SKYFALL and used that ever since.
Decided I wanted ViperOne.
Read many post and here is where the fun started.
Restored my origional nandroid.
fastboot flashed stock recovery then erase cache
booted nandroid. and installed downloaded 4.4.3 OTA
phone rebooted just fine.
fastboot flashed twrp recovery (openrecovery-twrp-2.8.0.3-m8_wlv.img) then erase cache
booted recovery and installed ViperOne.
then error process system isn't responding.
Since then I have repeated those steps. I have also tried CleanRom and RKDN and those get stuck in loading loops. I have tried the RUU options, and tried RUU and fastboot to get back to the 1.55.605.2 completely stock as it can be with a stock image or the nandroid and nothing seems to work. Just get the same errors. Now I am stuck and unsure what to do or how to go about fixing this....
Click to expand...
Click to collapse
I can team viewer with you and checkout what's up. What error do you get on RUU flashing?
jsaxon2 said:
Not sure if you've already tried this, but might help.
Load the RUU from here http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144
After that, go into the stock recovery and do a factory reset.
Click to expand...
Click to collapse
I had this ruu already, and the MD5 matched up. So I downloaded a new copy anyways, However I am unable to flash it. On another note I did try other non 443 rru's that did flash but factory reset did not work.
dottat said:
I can team viewer with you and checkout what's up. What error do you get on RUU flashing?
Click to expand...
Click to collapse
when trying to flash
Code:
C:\Users\balddav\My Documents\M8\ruu\443>fastboot oem rebootRUU
C:\Users\balddav\My Documents\M8\ruu\443>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
error: cannot load '0P6BIMG.zip'
Then I push file to root of external sd card:
once boot to HBOOT
Loading...[0P6BIMG.zip]
and after 1 hour still loading. then I tried to load 442 ruu and this:
Code:
C:\Users\balddav\My Documents\M8\ruu\442>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
sending 'zip' (825739 KB)...
OKAY [ 35.882s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 36.033s
I can ruu the 443 firmware from this post http://forum.xda-developers.com/showthread.php?t=2723159with no issues.
dab1414 said:
I had this ruu already, and the MD5 matched up. So I downloaded a new copy anyways, However I am unable to flash it. On another note I did try other non 443 rru's that did flash but factory reset did not work.
when trying to flash
Code:
C:\Users\balddav\My Documents\M8\ruu\443>fastboot oem rebootRUU
C:\Users\balddav\My Documents\M8\ruu\443>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
error: cannot load '0P6BIMG.zip'
Then I push file to root of external sd card:
once boot to HBOOT
Loading...[0P6BIMG.zip]
and after 1 hour still loading. then I tried to load 442 ruu and this:
Code:
C:\Users\balddav\My Documents\M8\ruu\442>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
sending 'zip' (825739 KB)...
OKAY [ 35.882s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 36.033s
I can ruu the 443 firmware from this post http://forum.xda-developers.com/showthread.php?t=2723159with no issues.
Click to expand...
Click to collapse
Flash the firmware and then go right to RUU flashing via sd.
dottat said:
Flash the firmware and then go right to RUU flashing via sd.
Click to expand...
Click to collapse
I have tried that and it hangs on loading. But I will try it again.
When I woke up I noticed my phone actually booted up normally. I think what I did different was reformat external drive. Copy the 442 RUU to it. I flashed the 442 firmware, then reboot to hboot it loaded the RUU, went to sleep and it worked.
So when I get a chance today I will make sure I have a good copy of the 443 firmware and try it the same way I just did 442, and post my steps.
Thanks for your help so far.
removed
So I was just trying something out and downloaded the OTA update and installed it. Everything looked like it updated fine so I just rebooted and the error process system isn't responding came back when rebooting. So I am trying the 443 firmware and RUU.
One thing I noticed from this post http://forum.xda-developers.com/showthread.php?t=2723159 is there is no boot or recovery, so after flashing the 443 firmware, I flashed the boot and recovery images found on the same thread. then I inserted the sd card with the RUU from here http://forum.xda-developers.com/verizon-htc-one-m8/development/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144 and this time HBOOT loaded the file and installed with no errors.
Now on booting up it still says Process system isn't responding.
dab1414 said:
So I was just trying something out and downloaded the OTA update and installed it. Everything looked like it updated fine so I just rebooted and the error process system isn't responding came back when rebooting. So I am trying the 443 firmware and RUU.
One thing I noticed from this post http://forum.xda-developers.com/showthread.php?t=2723159 is there is no boot or recovery, so after flashing the 443 firmware, I flashed the boot and recovery images found on the same thread. then I inserted the sd card with the RUU from here http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144 and this time HBOOT loaded the file and installed with no errors.
Now on booting up it still says Process system isn't responding.
Click to expand...
Click to collapse
You did not need to flash boot and recovery. In fact, the ruu will do that automatically for you.
Did your phone calm down? Sometimes on boot if blinkfeed and other apps try to update it can crash. . Reboot once more after that and see what happens.
dottat said:
You did not need to flash boot and recovery. In fact, the ruu will do that automatically for you.
Click to expand...
Click to collapse
I realized that shortly after I typed it, I looked in the zip files.
dottat said:
Did your phone calm down? Sometimes on boot if blinkfeed and other apps try to update it can crash. . Reboot once more after that and see what happens.
Click to expand...
Click to collapse
No my M8 is nothing but issues apparently. I have been rooting, unlocking, updating and installing ROMS for years now and I haven't had so many issues. Usually just my own mistakes, which this is probably one of them. I have done so much before I asked for help I couldn't tell you exactly what I did. If I would have read more then I wouldn't have gone the OTA route.
Right now I have not been able to get 442 or 443 to work. Here is a link to the picture right after I flashed firmware through RUU then hboot loaded 0P6BIMG.zip
https://www.dropbox.com/s/feu0tkkfkzyso67/Photo%20Oct%2016%2C%2023%2039%2048.jpg?dl=0
Then when it boots up it goes from verizon logo to the error. Here is a link to video I made of that boot process.
https://www.dropbox.com/s/wfnd0bxh6zz2bwh/Video%20Oct%2016%2C%2023%2042%2033.mov?dl=0
I have tried rebooting several times with the same results.
dab1414 said:
I realized that shortly after I typed it, I looked in the zip files.
No my M8 is nothing but issues apparently. I have been rooting, unlocking, updating and installing ROMS for years now and I haven't had so many issues. Usually just my own mistakes, which this is probably one of them. I have done so much before I asked for help I couldn't tell you exactly what I did. If I would have read more then I wouldn't have gone the OTA route.
Right now I have not been able to get 442 or 443 to work. Here is a link to the picture right after I flashed firmware through RUU then hboot loaded 0P6BIMG.zip
https://www.dropbox.com/s/feu0tkkfkzyso67/Photo Oct 16, 23 39 48.jpg?dl=0
Then when it boots up it goes from verizon logo to the error. Here is a link to video I made of that boot process.
https://www.dropbox.com/s/wfnd0bxh6zz2bwh/Video Oct 16, 23 42 33.mov?dl=0
I have tried rebooting several times with the same results.
Click to expand...
Click to collapse
I'm at a loss, the only other thing I could tell you to try would be to remove the sdcard and try rebooting.
I have a few comments. Go back and flash the 4.4.3 RUU from fastboot. Make sure your SDK is up to date with the latest and greatest. Your firmware is ok. In looking through your log from the fastboot attempt, you got error - Failed (remote: 32 header error). This means the zip couldn’t be read and unzipped properly. Something is borked. Make sure you have lots of room on your internal SD card too.
dab1414 said:
I realized that shortly after I typed it, I looked in the zip files.
No my M8 is nothing but issues apparently. I have been rooting, unlocking, updating and installing ROMS for years now and I haven't had so many issues. Usually just my own mistakes, which this is probably one of them. I have done so much before I asked for help I couldn't tell you exactly what I did. If I would have read more then I wouldn't have gone the OTA route.
Right now I have not been able to get 442 or 443 to work. Here is a link to the picture right after I flashed firmware through RUU then hboot loaded 0P6BIMG.zip
https://www.dropbox.com/s/feu0tkkfkzyso67/Photo Oct 16, 23 39 48.jpg?dl=0
Then when it boots up it goes from verizon logo to the error. Here is a link to video I made of that boot process.
https://www.dropbox.com/s/wfnd0bxh6zz2bwh/Video Oct 16, 23 42 33.mov?dl=0
I have tried rebooting several times with the same results.
Click to expand...
Click to collapse
You could have hosed partitions. I can team viewer and try a couple things to see if we can get it fixed.
jsaxon2 said:
I'm at a loss, the only other thing I could tell you to try would be to remove the sdcard and try rebooting.
Click to expand...
Click to collapse
Irieone said:
I have a few comments. Go back and flash the 4.4.3 RUU from fastboot. Make sure your SDK is up to date with the latest and greatest. Your firmware is ok. In looking through your log from the fastboot attempt, you got error - Failed (remote: 32 header error). This means the zip couldn’t be read and unzipped properly. Something is borked. Make sure you have lots of room on your internal SD card too.
Click to expand...
Click to collapse
dottat said:
You could have hosed partitions. I can team viewer and try a couple things to see if we can get it fixed.
Click to expand...
Click to collapse
Finally!!! Thank you all for the help.
So I removed my sdcard, then installed twrp, then went and advanced wipe and selected every box ( all i did before was factory resets). Then flashed firmware through ruu mode. Then reinserted sdcard with the 0P6BIMG file. rebooted to bootloader selected hboot, then when done rebooted and it was working fine. then reinstalled twrp and installed viperone, and rolling through just fine. Guess there was something floating around the factory reset didnt wipe.
Again thank you all for your time and help to resolve my screwup!!
dab1414 said:
Finally!!! Thank you all for the help.
So I removed my sdcard, then installed twrp, then went and advanced wipe and selected every box ( all i did before was factory resets). Then flashed firmware through ruu mode. Then reinserted sdcard with the 0P6BIMG file. rebooted to bootloader selected hboot, then when done rebooted and it was working fine. then reinstalled twrp and installed viperone, and rolling through just fine. Guess there was something floating around the factory reset didnt wipe.
Again thank you all for your time and help to resolve my screwup!!
Click to expand...
Click to collapse
Yeah....I think your partition was wonked. Twrp even has a repair option built in now for ext4 partitions under advanced wipe.
Hi all,
I have(had) a AT&T HTC One X (evita) that was running CM10.2.1, hboot 2.14, S-OFF, CID 11111111
My story: I wanted to update to CM11 so according to the CyanogenMod website (sorry can't post a link as a new user) I updated from my previous hboot 2.14 to 2.18 by updating to firmware 5.18.502.1, so far so good all went fine. Then I noticed that I should have at least TWRP 2.7.0.8 but I had 2.6.something so I went ahead and wanted to update the twrp recovery. That's were I made the stupid mistake. I went to the TWRP manager app, selected recovery update and by mistake (now as I'm tinking back about that) I selected HTC One X+ ATT i.e. the "evitareul" instead of "evita" and flashed that. Now the phone is dead, the screen is black, when put on charger the red LED doesn't come on, power+volume down doesn't do anything (no flashing, vibration, nothing). When I connect it to windows machine it recognizes some android device. Under linux, ADB doesn't see any device, though fastboot does, but instead of serial number there are just some non sense characters. I can run some bastboot commands like "fastboot oem readcid" and that works, but I can't flash (now correct) twrp recovery, all flash attempts end with FAILED (remote: not allowed). I tried applying RUU from windows but the phone can't boot into bootloader so it fails.
Please, is there any way I can fix this on my own? Or is it permanently bricked and I should start looking into getting a new phone :crying:
Many thanks for any advise!!
Does fastboot reboot bootloader do anything?
Hi, I tried to reboot to bootloader, the command was sent but the phone didn't do a thing, no visible reaction
Code:
$ sudo fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.113s]
finished. total time: 0.113s
You've borked your partition table. You can either have the motherboard replaced by HTC (~$200) or have a jtag repair done (~$50).
Thanks, I'll try to find somebody to get the jtag repair done.