Related
As a quick FYI, I spent a lot of time yesterday trying to get the stock RUU update to flash my HTC Raider. I played around with a custom ROM and wasn't too happy with it, but stupidly I didn't backup my stock rom with CWM... Lesson learned!
Anyways, if you are trying to go back to stock and are hitting Error 155 during the RUU Update, try re-locking the bootload with "fastboot eom lock". I tried this today and the stock firmware flashed on first try and I'm back to the good old Bell bloat!
Hope this helps anyone!
Hi I was trying to make a rom and ended up in a bootloop, so i made a mistake and flashed the boot.img from the android sdk folder to my raider and now I can't get into hboot, but with adb can get into cwm. i did have a backup and can restore the backup.
now when the restore is complete i try to restart and the phone hangs at the htc logo, then the screen turns black. phone never boots.
any ideas on what might fix this?
Thanks
abray1978 said:
As a quick FYI, I spent a lot of time yesterday trying to get the stock RUU update to flash my HTC Raider. I played around with a custom ROM and wasn't too happy with it, but stupidly I didn't backup my stock rom with CWM... Lesson learned!
Anyways, if you are trying to go back to stock and are hitting Error 155 during the RUU Update, try re-locking the bootload with "fastboot eom lock". I tried this today and the stock firmware flashed on first try and I'm back to the good old Bell bloat!
Hope this helps anyone!
Click to expand...
Click to collapse
Can you get back into HBOOT now that you did the restore?
I'm by far no expert but I'm curious if you can get back to HBOOT if you can put it into fastboot, re-lock the bootloader (fastboot oem lock) and then use the RUU to restore back to stock. That should fix the boot image and I you then can start the process over again by unlocking and playing.
That's what I did and I'm back to a non-bricked phone. You can get the Holiday (aka Raider) RUUs by searching these forums. Just download the one for your carrier.
Good luck
abray1978 said:
As a quick FYI, I spent a lot of time yesterday trying to get the stock RUU update to flash my HTC Raider. I played around with a custom ROM and wasn't too happy with it, but stupidly I didn't backup my stock rom with CWM... Lesson learned!
Anyways, if you are trying to go back to stock and are hitting Error 155 during the RUU Update, try re-locking the bootload with "fastboot eom lock". I tried this today and the stock firmware flashed on first try and I'm back to the good old Bell bloat!
Hope this helps anyone!
Click to expand...
Click to collapse
Where did you find an RUU for the HTC Raider?
I need RUU. I am in japan,but there is some thing wrong with my vivid, factory reset did not work....I can just see htc logo and then att logo, and then...though there is a setup but when i click that it shut down directly.....can any one help me ?
http://forum.xda-developers.com/showthread.php?t=1416836
2nd post has the links for stock ruu for all carriers
Sent from my HTC PH39100 using XDA App
thank you sooooo much.
Sent from my HTC PH39100 using XDA App
abray1978 said:
As a quick FYI, I spent a lot of time yesterday trying to get the stock RUU update to flash my HTC Raider. I played around with a custom ROM and wasn't too happy with it, but stupidly I didn't backup my stock rom with CWM... Lesson learned!
Anyways, if you are trying to go back to stock and are hitting Error 155 during the RUU Update, try re-locking the bootload with "fastboot eom lock". I tried this today and the stock firmware flashed on first try and I'm back to the good old Bell bloat!
Hope this helps anyone!
Click to expand...
Click to collapse
Many thanks! I thought that mine Raider was completly dead. Didn't want get into CWM only 2 lines for less than 0.25sec with messsage that is unable to get acces to cache then reboot and stuck with htc logo forever. Then i read this post and my Raider is get back to live.
Many thanks once again.
Thank you so much!
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
mikhailov1 said:
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
Click to expand...
Click to collapse
try this http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
it worked for some users
Thanks. Will try when I get home. I was able to use my Win 7 computer at work to unlock the boot loader again, but I cannot get S Off. I ran rumrunner and it looked like it was working, but then said FATAL: download update. Is there no rumrunner for GPE?
Sent from my HTC One using Tapatalk
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Prash8429 said:
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Click to expand...
Click to collapse
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
mikhailov1 said:
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
Click to expand...
Click to collapse
you can still get OTA with a rooted phone, as long as you have stock recovery and flashed stock ruu.... tip if your having trouble with flashing ruu change the zip file name to something simple like ruu.zip worked for me.:good:
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Can you tell me if your bootloader was 1.54 or 1.55? I have been unable to get Windows 8.1 to recognize the 1.54 bootloader. It always says "device not recognized" If yours was 1.54.0000 I will try this fix. Thanks.
I am 1.54.
Sent from my Nexus 5 using Tapatalk
Thanks for this, helped me out alot
Sent from my HTC One using XDA Premium 4 mobile app
Hi all! First of all I'm sorry if this has been asked previously but after 3 hours of searching I was unable to find a straight answer and I have tenths of bookmarks opened...
Right so, just got my "new" (used) phone delivered today. 6 months old, currently running stock 4.4.2 with Sense 6.0 under the GiffGaff network. Straight away I went and tried to flash a new ROM onto it (flashed a few roms previously to my HTC Sensation with no problems). So just the usual routine: fastboot > HTCdev > get token ... and here where the first problem occurred. I couldn't get the token as I was getting the following error:
(bootloader) [ERR] Command error !!!
OKAY [ 0.010s]
finished. total time: 0.010sRestarting the phone/PC didn't help, changing USB debug on/off also didn't help. Fastboot unlock oem command didn't work either as it gave me the same error. So I went and downloaded the Hasoon2000's AIO tool to see if that will work but again no luck. When hitting the "Get Token ID" I get an error that the phone is offline - . - . So I had a little search on the net and found out that maybe it's due to my HBOOT version which is 1.57 and is S-ON . However I have no idea how to change that nor if it'll actually solve my problem and I don't want to do anything outside the box so that I don't get my phone bricked.
Any ideas what might be wrong/what am I doing wrong/solutions? I'm clueless at the moment and about to run out of patience... Any help is more then welcome
bboybtek said:
(bootloader) [ERR] Command error !!!
OKAY [ 0.010s]
finished. total time: 0.010sWhat was the exact command?
Click to expand...
Click to collapse
changing USB debug on/off also didn't help.
Click to expand...
Click to collapse
usb debug doesn't matters in bootloader, only in the OS or in recovery for adb commands.
Fastboot unlock oem command didn't work either
Click to expand...
Click to collapse
this command is blocked, so it will not work.
So I went and downloaded the Hasoon2000's AIO tool
Click to expand...
Click to collapse
Hasoon2000 did a great job with his toolkit, but I recommend (and many others) not using toolkits. use fasboot and adb directly from the command window, much better when you are trying to find what doesnt work. Be sure to have the latest sdk on your computer, and latest htc drivers. Also make sure to use 2.0 usb ports, not 3.0
I get an error that the phone is offline
Click to expand...
Click to collapse
What is the output of "fastboot devices" ?
So I had a little search on the net and found out that maybe it's due to my HBOOT version which is 1.57 and is S-ON
Click to expand...
Click to collapse
not sure about that, I really doubt you can't unlock bootloader because of hboot 1.57.
Any ideas what might be wrong/what am I doing wrong/solutions?
Click to expand...
Click to collapse
follow this guide:
Thanks for the reply mate. I watched the video again but I had no luck. However, thanks to that video I went and downloaded the huge SDK archive from HTC site. Instead of using the small archive with "essential" files for the adb, I used the one from HTC site (it has many more files in adb folder) and guess what, it worked! Now, I'm very happy that I finally unlocked it but my question now is, why didn't it work with just the "essential" files? All tutorials videos/forum posts etc. mentioned just the 4 files and not the big HTC package so if it wasn't for the fact that I was desperate I don't think I would of ever unlock this biatch...
Right, instead of creating a new thread I'm just going to ask here. So I successfully unlocked the device and using this video I tried to root the phone. Everything went smoothly, all successful and so on. However when I downloaded the root checker it gives me a message saying the the device is not properly rooted . I then tried with firewater s-off but no luck here either. I've attached the image of how my cmd looks when trying the firewater method. I really thought it's going to be a bit easier to flash this phone... Any advice here guys?
Edit: I just realised that the phone is still S-ON...how did this happen even tho I successfully installed everything that's required...?
Edit2: Tried the temp-root method with firewater but even this doesn't work. I'm getting an error and fail messages (image attached). I think I've run out of ideas here :/
bboybtek said:
Right, instead of creating a new thread I'm just going to ask here. So I successfully unlocked the device and using this video I tried to root the phone. Everything went smoothly, all successful and so on. However when I downloaded the root checker it gives me a message saying the the device is not properly rooted . I then tried with firewater s-off but no luck here either. I've attached the image of how my cmd looks when trying the firewater method. I really thought it's going to be a bit easier to flash this phone... Any advice here guys?
Edit: I just realised that the phone is still S-ON...how did this happen even tho I successfully installed everything that's required...?
Edit2: Tried the temp-root method with firewater but even this doesn't work. I'm getting an error and fail messages (image attached). I think I've run out of ideas here :/
Click to expand...
Click to collapse
first, why are you trying to s-off? s-off is not required to flash custom roms (except for GPE roms), only an unlocked bootloader and a custom recovery (twrp 2.6.3.3) are needed. You definitively need a fully rooted phone to use firewater and an unsecured kernel would also help. Btw almost all custom roms out here are pre-rooted, so just flash a rom and you'll be fine.
and that video you have linked is very outdated, twrp 2.5.0.0 lol. just flash twrp 2.6.3.3 and then boot in recovery. Quit the recovery and you'll be prompted to install root.
but anyway, is your goal is to flash a custom rom, you don't need to root before, they are all (almost) pre-rooted.
alray said:
first, why are you trying to s-off? s-off is not required to flash custom roms (except for GPE roms), only an unlocked bootloader and a custom recovery (twrp 2.6.3.3) are needed. You definitively need a fully rooted phone to use firewater and an unsecured kernel would also help. Btw almost all custom roms out here are pre-rooted, so just flash a rom and you'll be fine.
and that video you have linked is very outdated, twrp 2.5.0.0 lol. just flash twrp 2.6.3.3 and then boot in recovery. Quit the recovery and you'll be prompted to install root.
but anyway, is your goal is to flash a custom rom, you don't need to root before, they are all (almost) pre-rooted.
Click to expand...
Click to collapse
I got lost a little bit with all the tutorials I found, that's why I thought I need s-off lol. I know the video is a bit old that's why I used twrp 2.7.1.1 with SU 3.2 . I'm planning on installing ViperOne rom so I'm just going to go ahead and try that and hopefully everything will be working. Thanks again for the reply mate
bboybtek said:
I got lost a little bit with all the tutorials I found, that's why I thought I need s-off lol. I know the video is a bit old that's why I used twrp 2.7.1.1 with SU 3.2 . I'm planning on installing ViperOne rom so I'm just going to go ahead and try that and hopefully everything will be working. Thanks again for the reply mate
Click to expand...
Click to collapse
Make a backup using TWRP first..
Also the file you should have used should be SuperSU-2.02.. but if you are going to flash a new rom, point is moot.
SaHiLzZ said:
but if you are going to flash a new rom, point is moot.
Click to expand...
Click to collapse
yeah I've installed a new rom and everything is running perfectly fine! Thanks for the tips chaps!
So... I'm embarrased to say, I am stuck. I usually figure this stuff out, but this one's got me stuck.
While trying to S-0ff (1.57) I somehow have erased something important . I've rooted probably 25 phones. Every HTC I've had I rooted, and S-Off. But I have NO idea how I did this.
It all started when I re-locked my bootloader so I could RUU in order to try one method for S-off (I've tried about 10 times to s-off with no luck - firewater, moonshine, rumrunner, etc.)
Every time I tried to flash RUU to fix it via fastboot I got a verification error. Not only that but after I tried, my phone would only boot to bootloader. I then tried unlocking the bootloader again, and suddenly it booted back to my origional (ViperRom) Rom. I thought everything was good, but I tried flashing CM11, and ran firewater again on a last ditch effort. It was then that I noticed I had no cell signal. When I booted into bootloader again is says "OS- " - nothing. I have no "OS" under the bootloader. It had been the 5.x
I've tried RUU the same firmware. - errors. I tried reflashing VenumRom - boots to lock screen, but when I swipe up, HTC logo with white screen appears and stays. It eventually reboots.
So the only thing I can boot is CM11, but I don't have cell signal.
The kicker is I was in such a hurry (wife's phone) that I didn't nandroid.... :crying:
SO does anyone have a nandroid (of m7wls) I can have a copy of? I can change to any recovery. I have no problem with that, but I have NO idea how I even got here and I've tried everything I can find on it. I've been trying for hours.
I can't find a stock rom that I can flash in recovery - I've looked all over - other versions galore, but no m7wls.
Or any other suggestions...
boytoreckonwith said:
So... I'm embarrased to say, I am stuck. I usually figure this stuff out, but this one's got me stuck.
While trying to S-0ff (1.57) I somehow have erased something important . I've rooted probably 25 phones. Every HTC I've had I rooted, and S-Off. But I have NO idea how I did this.
It all started when I re-locked my bootloader so I could RUU in order to try one method for S-off (I've tried about 10 times to s-off with no luck - firewater, moonshine, rumrunner, etc.)
Every time I tried to flash RUU to fix it via fastboot I got a verification error. Not only that but after I tried, my phone would only boot to bootloader. I then tried unlocking the bootloader again, and suddenly it booted back to my origional (ViperRom) Rom. I thought everything was good, but I tried flashing CM11, and ran firewater again on a last ditch effort. It was then that I noticed I had no cell signal. When I booted into bootloader again is says "OS- " - nothing. I have no "OS" under the bootloader. It had been the 5.x
I've tried RUU the same firmware. - errors. I tried reflashing VenumRom - boots to lock screen, but when I swipe up, HTC logo with white screen appears and stays. It eventually reboots.
So the only thing I can boot is CM11, but I don't have cell signal.
The kicker is I was in such a hurry (wife's phone) that I didn't nandroid.... :crying:
SO does anyone have a nandroid (of m7wls) I can have a copy of? I can change to any recovery. I have no problem with that, but I have NO idea how I even got here and I've tried everything I can find on it. I've been trying for hours.
I can't find a stock rom that I can flash in recovery - I've looked all over - other versions galore, but no m7wls.
Or any other suggestions...
Click to expand...
Click to collapse
I don't know which RUU you tried but this site has the latest RUU and firmware. Since you are S-ON you will need to relock your bootloader.
boytoreckonwith said:
So... I'm embarrased to say, I am stuck. I usually figure this stuff out, but this one's got me stuck.
While trying to S-0ff (1.57) I somehow have erased something important . I've rooted probably 25 phones. Every HTC I've had I rooted, and S-Off. But I have NO idea how I did this.
It all started when I re-locked my bootloader so I could RUU in order to try one method for S-off (I've tried about 10 times to s-off with no luck - firewater, moonshine, rumrunner, etc.)
Every time I tried to flash RUU to fix it via fastboot I got a verification error. Not only that but after I tried, my phone would only boot to bootloader. I then tried unlocking the bootloader again, and suddenly it booted back to my origional (ViperRom) Rom. I thought everything was good, but I tried flashing CM11, and ran firewater again on a last ditch effort. It was then that I noticed I had no cell signal. When I booted into bootloader again is says "OS- " - nothing. I have no "OS" under the bootloader. It had been the 5.x
I've tried RUU the same firmware. - errors. I tried reflashing VenumRom - boots to lock screen, but when I swipe up, HTC logo with white screen appears and stays. It eventually reboots.
So the only thing I can boot is CM11, but I don't have cell signal.
The kicker is I was in such a hurry (wife's phone) that I didn't nandroid.... :crying:
SO does anyone have a nandroid (of m7wls) I can have a copy of? I can change to any recovery. I have no problem with that, but I have NO idea how I even got here and I've tried everything I can find on it. I've been trying for hours.
I can't find a stock rom that I can flash in recovery - I've looked all over - other versions galore, but no m7wls.
Or any other suggestions...
Click to expand...
Click to collapse
Your os version is missing because you used a version of twrp recovery that has the misc partition bug. But it is only cosmetic. Your os (firmware) is still there it just doesn't show the version number. Flashing firmware or an ruu will fix it.
Now on to the more serious problem, which sounds like you have Unknown imei and Baseband. Check under settings to see if your Imei and baseband are correctly displayed.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
Your os version is missing because you used a version of twrp recovery that has the misc partition bug. But it is only cosmetic. Your os (firmware) is still there it just doesn't show the version number. Flashing firmware or an ruu will fix it.
Now on to the more serious problem, which sounds like you have Unknown imei and Baseband. Check under settings to see if your Imei and baseband are correctly displayed.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Well, you are correct about baseband missing. I don't even see imei anywhere - didn't think sprint had that... anyways. I tried both locked AND unlocked bootloader to flash firmware versions 5.05.651.2 and 5.11.401.10.zip. When the bootloader is unlocked I get an error 99 and when it's locked I get signature verification fails.... any ideas?
boytoreckonwith said:
Well, you are correct about baseband missing. I don't even see imei anywhere - didn't think sprint had that... anyways. I tried both locked AND unlocked bootloader to flash firmware versions 5.05.651.2 and 5.11.401.10.zip. When the bootloader is unlocked I get an error 99 and when it's locked I get signature verification fails.... any ideas?
Click to expand...
Click to collapse
I've known many cases of Unknown Imei and Baseband, unfortunately it's not good news. Especially if your s-on. But I only know of one case where the problem was repaired and it was a hardware repair (antenna pin connector)
You can post your getvar all and maybe find some firmware to try but I doubt there's an ruu that you can use with s-on, Since your already on the latest hboot. And downgrading requires s-off.
See one such case here http://forum.xda-developers.com/showthread.php?t=2885235
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
I have this phone i have downloaded the RUU from Sprint and also From T-mobile, and i trying a lot of time with each ones, also put the phone in bootloader and download mode, and in all times the error 155 comes appearing.
is there a way to install marshmallow on this variation?
I Concur!
I'm also wondering about this. Is there any way to successfully flash Marshmallow on this device? Us Cricket users are feeling awfully lonely back here.
luis052593 said:
I have this phone i have downloaded the RUU from Sprint and also From T-mobile, and i trying a lot of time with each ones, also put the phone in bootloader and download mode, and in all times the error 155 comes appearing.
is there a way to install marshmallow on this variation?
Click to expand...
Click to collapse
Alright, man. I doubt you care at this point, but here it is:
I've figured out how to get Marshmallow onto this thing. Follow the instructions in this thread: https://forum.xda-developers.com/desire-626/help/flashable-mm-update-zip-626s-t3615689
I've been using my phone like this and not encountered any real issues related to the ROM. Give it a go.