[Q] RUU stuck on "sending" - HTC Incredible S

Hi,
I just got my phone back from repairs and I'm trying to get S-OFF. Naturally, the repair centre updated it to 4.0.4 and hboot 2.02, so I have to downgrade to HBOOT 1.13 in order to S-OFF using revolutionary.
I've followed the main downgrading guide stickied, (unlock bootloader, change main version number and run downgrade RUU) and everything is fine up to the point of running the RUU - it just stays at the "Sending..." screen (screenshot). I've waited up to an hour and it still seems to be stuck at "Sending...".
I googled around and searched xda and I found people saying I needed to have a locked bootloader with fastboot oem lock, didn't change anything and still stuck at sending (it's not frozen, the little dots are moving but it's not doing anything).
Help!

Bump?

Solved, I just let it sit for 3 hours in a row. Not sure why, but it must have just taken a long time to send.

anonymousthing said:
Solved, I just let it sit for 3 hours in a row. Not sure why, but it must have just taken a long time to send.
Click to expand...
Click to collapse
same thing is happening to me now. it's been 1 hour i'm stuck in sending. so should i wait more ?

Related

[Q] phone stuck after update :/ need help

after i got the OTA update, the phone finished downloading and started the installation process, the phone rebooted into that screen with the 3 green arrows (2 circling and 1 down). i left the phone on that screen for more than an hour or some and that's it it's stuck on that screen.
i tried the pull out the battery and put it in again and when i boot the phone it goes back to that screen.
plus i'm not able to boot into hboot nor doing anything and when i plug the usb to a pc it wont detect it.
i have tried everything i know so far :s and still no luck .... i would be glad if anyone can help me.
not a single reply !!??
i should throw the phone from my window then
Is it HTC dev unlocked? You can't do an ota if its not completely stock.
e-zee said:
after i got the OTA update, the phone finished downloading and started the installation process, the phone rebooted into that screen with the 3 green arrows (2 circling and 1 down). i left the phone on that screen for more than an hour or some and that's it it's stuck on that screen.
i tried the pull out the battery and put it in again and when i boot the phone it goes back to that screen.
plus i'm not able to boot into hboot nor doing anything and when i plug the usb to a pc it wont detect it.
i have tried everything i know so far :s and still no luck .... i would be glad if anyone can help me.
Click to expand...
Click to collapse
e-zee said:
not a single reply !!??
i should throw the phone from my window then
Click to expand...
Click to collapse
You did not give enough information to even try to help you. As markj338 suggested, if you have modified your phone by unlocking the bootloader, flashing a custom recovery or rooted the phone, it will not apply the OTA successfully.
So what was the state of your phone before you attempted to run the OTA?
tpbklake said:
You did not give enough information to even try to help you. As markj338 suggested, if you have modified your phone by unlocking the bootloader, flashing a custom recovery or rooted the phone, it will not apply the OTA successfully.
So what was the state of your phone before you attempted to run the OTA?
Click to expand...
Click to collapse
it's perfectly stock. i have locked the bootloader and installed a stock RUU before checking any updates, and i told you how my story ended
e-zee said:
it's perfectly stock. i have locked the bootloader and installed a stock RUU before checking any updates, and i told you how my story ended
Click to expand...
Click to collapse
So we are clear, your phone was completely stock? Or was your bootloader unlocked and you locked it before checking for updates?
acme anvil said:
So we are clear, your phone was completely stock? Or was your bootloader unlocked and you locked it before checking for updates?
Click to expand...
Click to collapse
the bootloader was unlocked, i relocked it then installed an original RUU after that everything was working normal, i checked for updates so i got the OTA update, then installed it and then my phone stuck on that screen.
What method did you use to lock your bootloader?
thanks guys for everything, i found a store to fix my phone, and they fixed it with jtag box and now it's brand new.

[Q] [UPDATE WITH SOLUTION] RUU 155 Error with HTC ONE Developer Edition

I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
UPDATE
Ok, I figured out how to avoid the RUU 155 error. It seems that HTC for some dumb reason, although for a unlocked developer edition, we still have to lock the bootloader to utilize the RUU. Here are the steps I have done.
Although it is straight forward and easy to do, issues could always arise. I do not take any responsibility if things go wrong. Educate yourself first before attempting anything. If you do not know what you are doing, then don't do it.
Before Starting.
Make sure you have the latest HTC Drivers. You can use hasoon2000 HTC All-In-One Toolkit to complete that. That can be found at HTC One All-In-One Toolkit
Get the appropriate RUU from HTC Dev
1. Lock your bootloader through by booting into hoot and then going into fastboot and issuing the command fasboot oem lock.
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Notice, this will delete all of the files on the system so do this on your own cognition
4. Let the RUU do its thing. If you get an error during the process, such as 152, simply try again. I had it happen once. The phone was stuck on the black HTC screen with four triangles with exclamation points in each corner. If this happens you will not be able to reboot your phone. Simply relaunch RUU and it should reinstall it. If you get error 155 again, then you have not re-locked your bootloader.
3.Once you have successfully reinstalled the rom, you have to register with the HTC Dev to re-unlock your bootloader if that is what you want. The easiest to do this I found was by using the HTC One All-In-One Toolkit. It is a great tool and will help you with majority of things that I have mentioned above, including locking your bootloader. Follow the steps on the toolkit and you'll be all set. The Toolkit can be found here HTC One All-In-One Toolkit
If you found this helpful, click thanks. Also hit thanks to hasoon2000 for creating the toolkit.
Gotta re lock your bootloader
fastboot oem lock
I got relock it even though it came unlocked? How would I unlock it again since I don't have the tokens from HTC development, or is the ruu gonna do that by itself.
Sent from my HTC One using Tapatalk 2
I was having same issues as OP. After using the lock command, the update got longer. The black HTC screen even got as far as a progress bar. Well I now got ERROR 152 saying I should get the correct RUU. I am sure I have the right one, because there is only ONE developer edition RUU file from htcdev.com
Problem now is, I have the black HTC screen with warning signs on each corner.
One thing I saw on a video is you are supposed to restore to the same version? I had updated OTA Z(1.29.1540.16) to the latest which I cant get an RUU for. The RUU available is 1.29.1540.3 no other available. What do I do now? HTC One Dev Edition stuck on black screen with warning signs on all corners.
All I can see now is a scren that says:
***TAMPERED***
***RELOCKED***
bunch of numbers and letters in green and
RUU in orange
schn1tt3r said:
I was having same issues as OP. After using the lock command, the update got longer. The black HTC screen even got as far as a progress bar. Well I now got ERROR 152 saying I should get the correct RUU. I am sure I have the right one, because there is only ONE developer edition RUU file from htcdev.com
Problem now is, I have the black HTC screen with warning signs on each corner.
One thing I saw on a video is you are supposed to restore to the same version? I had updated OTA to the latest which I cant get an RUU for. What do I do now? HTC One Dev Edition stuck on black screen with warning signs on all corners.
Click to expand...
Click to collapse
When I was doing it, the first time I got the 152 error. I simply just redid it and it accepted it on the second try. Trying relaunching RUU that you have and try the install again. That's at least how it worked with me.
Bosnazmaj said:
When I was doing it, the first time I got the 152 error. I simply just redid it and it accepted it on the second try. Trying relaunching RUU that you have and try the install again. That's at least how it worked with me.
Click to expand...
Click to collapse
Did you get that black HTC screen with warning signs on each corner? I am re-running the RUU, hope it works or I just lost $650.
EDIT: You used RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe right? Were you already OTA updated? I wonder why htcdev web says BrightstarUS for the dev edition instead of something else...
EDIT2: Its on that black screen with loading thing again... still exclamation marks on every corner... hope this works or else it won't be a nice first experience with Android coming from iOS lol and I've jailbroken and tinkered on those devices for so long.
---------- Post added at 08:31 PM ---------- Previous post was at 08:21 PM ----------
Yeah 2nd attempt the same error 152. I just lost $650 right?
The green bar goes all the way to the end, it sends it all, but it doesnt reboot. It just gets error. What else can I try? Device isnt even 3 days old.
Did it a third time, after Updating Radio, thats where the error appears.
schn1tt3r said:
Did you get that black HTC screen with warning signs on each corner? I am re-running the RUU, hope it works or I just lost $650.
EDIT: You used RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe right? Were you already OTA updated? I wonder why htcdev web says BrightstarUS for the dev edition instead of something else...
EDIT2: Its on that black screen with loading thing again... still exclamation marks on every corner... hope this works or else it won't be a nice first experience with Android coming from iOS lol and I've jailbroken and tinkered on those devices for so long.
---------- Post added at 08:31 PM ---------- Previous post was at 08:21 PM ----------
Yeah 2nd attempt the same error 152. I just lost $650 right?
The green bar goes all the way to the end, it sends it all, but it doesnt reboot. It just gets error. What else can I try? Device isnt even 3 days old.
Did it a third time, after Updating Radio, thats where the error appears.
Click to expand...
Click to collapse
What was the software version that it came with. Was it with the most recent one? I think 1.29.401.16 one?
Bosnazmaj said:
What was the software version that it came with. Was it with the most recent one? I think 1.29.401.16 one?
Click to expand...
Click to collapse
It came with the .3 and I did OTA to .16
The RUU you can get online from their web is only .3
===============================
Ok so... that black HTC screen accepts "fastboot" commands.
I downloaded the .ZIP version of the Developer Edition OS.
I went in command prompt, I typed
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
****GOT AN ERROR*****
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
.... so again:
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
10 minutes later
fastboot reboot
Oh my was I happy to see the white HTC Startup.
I also have same phone de it shouldnt be tamperd relocked it should be only relocked
Sent from my HTC One using xda app-developers app
I find it funny now far Computer OS's have come and yet we always have to go back to good old DOS Command Prompt to fix things.
BTW, my phone now has bootloader RELOCKED due to the fastboot oem lock command, should I send the phone back just like that or unlock bootloader before sending it back?
I guess to Unlock bootloader again, I have to follow same instructions as if it were an AT&T version right? Did you UNLOCK yours again OP?
U sending it back to HTC?
Sent from my HTC One using Tapatalk 2
Bosnazmaj said:
U sending it back to HTC?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yes, that is the reason I was doing all this restoring. I had ROOTed it to install AdAway. Ads is the only major drawback when compared to iOS (this is my first Android). When you see a gray image on my phone, there are 3 sort of water drops. Like between the touch screen and LCD.
Well, I am exchanging it actually. I like the HTC One a lot. It has a tiny gap, but I dont care about that much, the weird discoloration on the sceen, though, I do mind.
That makes sense.
Sent from my HTC One using Tapatalk 2
Bosnazmaj said:
I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
UPDATE
Ok, I figured out how to avoid the RUU 155 error. It seems that HTC for some dumb reason, although for a unlocked developer edition, we still have to lock the bootloader to utilize the RUU. Here are the steps I have done.
Although it is straight forward and easy to do, issues could always arise. I do not take any responsibility if things go wrong. Educate yourself first before attempting anything. If you do not know what you are doing, then don't do it.
Before Starting.
Make sure you have the latest HTC Drivers. You can use hasoon2000 HTC All-In-One Toolkit to complete that. That can be found at HTC One All-In-One Toolkit
Get the appropriate RUU from HTC Dev
1. Lock your bootloader through by booting into hoot and then going into fastboot and issuing the command fasboot oem lock.
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Notice, this will delete all of the files on the system so do this on your own cognition
4. Let the RUU do its thing. If you get an error during the process, such as 152, simply try again. I had it happen once. The phone was stuck on the black HTC screen with four triangles with exclamation points in each corner. If this happens you will not be able to reboot your phone. Simply relaunch RUU and it should reinstall it. If you get error 155 again, then you have not re-locked your bootloader.
3.Once you have successfully reinstalled the rom, you have to register with the HTC Dev to re-unlock your bootloader if that is what you want. The easiest to do this I found was by using the HTC One All-In-One Toolkit. It is a great tool and will help you with majority of things that I have mentioned above, including locking your bootloader. Follow the steps on the toolkit and you'll be all set. The Toolkit can be found here HTC One All-In-One Toolkit
If you found this helpful, click thanks. Also hit thanks to hasoon2000 for creating the toolkit.
Click to expand...
Click to collapse
Thank you. This was very helpful.
Glad I could help
Sent from my HTC One using Tapatalk 2
schn1tt3r said:
It came with the .3 and I did OTA to .16
The RUU you can get online from their web is only .3
===============================
Ok so... that black HTC screen accepts "fastboot" commands.
I downloaded the .ZIP version of the Developer Edition OS.
I went in command prompt, I typed
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
****GOT AN ERROR*****
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
.... so again:
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
10 minutes later
fastboot reboot
Oh my was I happy to see the white HTC Startup.
Click to expand...
Click to collapse
THANK YOU MAN!!!!!!!! You just saved me. I had the same problem except I had OTA .17 and trying to flash .16. My device was all jacked up but it's back to original.
Bosnazmaj said:
I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
.........
Click to expand...
Click to collapse
Bosnazmaj - thank you for this wonderful write-up & knowledge. I have a Dev edition myself. Sometime ago, I got into charging issues. Initially, assuming it to be software issues, I thought I'd run the RUU. So, like you, I too figured out that I have to lock my bootloader. Ran the RUU....long story short, found out that I have to give my phone for repairs (turned out to be a hardware issue).
So, the point I am trying to make is that, if we unlock the bootloader, certain apps (like flashlight, sound recorder etc) seems to get deleted. While this, on it's own, might not sound too alarming....the problem is, if these apps are not present, then the OTA does not & will not get applied as the OTA says that these apps have to be present. I am not sure how to unlock the bootloader without losing any apps.
Any knowledge / information on this is MOST appreciated.
Actually I used titanium backup to back those apps that disappear during root before I unlocked anything. Then once I rooted and unlocked I just restored them back with titanium and all was fine. But in reality you don't want to so an ota when you are rooted as you might loose root.
Sent from my HTC One using Tapatalk 2
Can't you re-unlock the phone using following command without going through the HTCDev website mess?
Code:
fastboot oem unlock
Just a heads up. I was able to return to stock using the RUU without locking the bootloader. It took a while to figure it out.
I went from ARHD 31 to A stock rom (m7_stock_dev_1.29.1540.16_signed_052313.zip) found on an old thread, also had to find a stock recovery that would work (i think it was the one liked in the ARHD thread) and used the revone S-off method, then applied the latest RUU from the htc dev site .and it installed and the bootloader remained unlocked.
I had to get this thing ready for someone who bought it. They asked if i could return it to stock with S-off. It was a pain in the but, but got it working

HTC One problems after repair

Hey guys,
A couple of days ago I recieved my One after I sent it for repairs.
They fixed my camera issue but changed my phone back to s-on. So now i'm left with a relocked phone with s-on.
I can't seem to re-unlock my phone by using htc's unlocking guide. After flashing the token it doesn't go into unlocking mode.
So i need some help with that. I'm on hboot 1.56 and 4.4 stock sense
Next problem:
I've been having this problem for a couple of days now. My phone charges unusually slowly. I always charge it overnight.
Last night it was 40% when i put it on the charger. About 8 hours later i woke up and it reached 95%. Already did a fresh install with no luck.
I'm thinking about sending it back and demand a new one but i need my phone for work. So if you guys know a way to fix it by using software that would be awesome.
Helping me out means beer ^^
bamidrol said:
Hey guys,
A couple of days ago I recieved my One after I sent it for repairs.
They fixed my camera issue but changed my phone back to s-on. So now i'm left with a relocked phone with s-on.
I can't seem to re-unlock my phone by using htc's unlocking guide. After flashing the token it doesn't go into unlocking mode.
So i need some help with that. I'm on hboot 1.56 and 4.4 stock sense
Next problem:
I've been having this problem for a couple of days now. My phone charges unusually slowly. I always charge it overnight.
Last night it was 40% when i put it on the charger. About 8 hours later i woke up and it reached 95%. Already did a fresh install with no luck.
I'm thinking about sending it back and demand a new one but i need my phone for work. So if you guys know a way to fix it by using software that would be awesome.
Helping me out means beer ^^
Click to expand...
Click to collapse
They didn't "fix" your phone, they never simply fix ones phone. They send you a new "refurbished phone" which would be why the Token ID doesn't work for unlocking the bootloader. Go through the steps to get a new Token ID then unlock your phone.
As for the problem with the charger, perhaps that's the reason the phone got sent in to be fixed in the first place, that would be something you want to work out before going through all the work to unlock and s-off first.
.Ryker said:
They didn't "fix" your phone, they never simply fix ones phone. They send you a new "refurbished phone" which would be why the Token ID doesn't work for unlocking the bootloader. Go through the steps to get a new Token ID then unlock your phone.
As for the problem with the charger, perhaps that's the reason the phone got sent in to be fixed in the first place, that would be something you want to work out before going through all the work to unlock and s-off first.
Click to expand...
Click to collapse
Thanks for the reply. But they actually did fix it. I had some "marks" on my device. Some small scratches that helped me identify my phone. So this truly is my phone. I really do wanna go back to ARHD. I need my xposed
bamidrol said:
Thanks for the reply. But they actually did fix it. I had some "marks" on my device. Some small scratches that helped me identify my phone. So this truly is my phone. I really do wanna go back to ARHD. I need my xposed
Click to expand...
Click to collapse
Hmm maybe then they reflashed the device with stock every thing. I've never heard of them actually fixing it before! So if they did reflash it then they could be having the same issues.
Sent from my One using Tapatalk
.Ryker said:
Hmm maybe then they reflashed the device with stock every thing. I've never heard of them actually fixing it before! So if they did reflash it then they could be having the same issues.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Yeah they reflashed a RUU. Not sure what kind of RUU. Only thing i find peculiar is that i can flash the token but it wont work.
Never had or heard about this problem before. If you know how to fix it you can earn yourself a beer ^^
I'm on hboot 1.56.0000. Maybe that is causing all the trouble
bamidrol said:
Yeah they reflashed a RUU. Not sure what kind of RUU. Only thing i find peculiar is that i can flash the token but it wont work.
Never had or heard about this problem before. If you know how to fix it you can earn yourself a beer ^^
I'm on hboot 1.56.0000. Maybe that is causing all the trouble
Click to expand...
Click to collapse
Have you tried getting a different token ID on it?? Or tried running rumrunner to s-off?
Sent from my One using Tapatalk
.Ryker said:
Have you tried getting a different token ID on it?? Or tried running rumrunner to s-off?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I tried rumrunner but it needs root-acces. I'm not rooted yet. And what exactly do you mean by a different token ID?
Flashing a RUU doesnt work. Signature fail error 12

[Q] HELP!!! HTC one stuck in bootloop

So I've had my htc one since september I bought it brand new and rooted it and put custom rom and unlocked bootloader. After a month I wanted to relock the bootloader and unroot it so I used the RUU. It worked for about a month then one day it just turned off and keeps rebooting itself. Sometimes when its off and i plug it in it starts to flash a red light on top then it just turned off. I have reinstalled the RUU many times but never worked. Its been like this since october sometimes it keeps rebooting and it actually turns on but its in safe mode. no music playin, no microphone, really fast battery drain. If someone can please help me it is the at&t version. I have also tried to factory reset it many times from the fastboot menu. thank you for reading
I've had that problem before on previous HTC devices. Unlock the boot loader and root eveeythinf/soff again. Forgot exactly how I fixed it but I know I had to root, soff, unlock boot loader again. Think it's whenever u relock the boot loader it messes things up.
Sent from the one and only HTC One
thanks ill try that out

Relock question

ALright, my previous m7 is sitting dead in forever bootloops... it's on the back burner until further notice.
so i got another one. stock all around. used. took the OTA for latest firmware and radios, exactly the same revision as the previous m7....
unlocked bootloader, flashed twrp, flashed good old cm11. worked good for a few weeks.
then i decided to try lineage 14/15. cm13, back and forth, over and a bout...
then running stabile in lineage14.1, i noticed i couldnt' make phone calls.
so i flashed back to cm11, LTE/4g shows up, data is good, but cannot make calls, cannot receive calls, same with text messages.
flashed back to the stock nandroid that the phone came with, same thing! only data, no voice/text.
so, in attempt to bring it back in for repair, i needed to relock the bootloader.
that's where it went ugly. it said relocked, tampered, and security warning, and i was unable to boot into anything else.
luckily i kept the unlock token ,and reissued an unlock, and it would let me boot into the rom again and the recovery, but i don't want to attempt to continue the RUU until i know exactly what steps are required.
i read the bootloader must be relocked before RUU, i also read if i was stuck where i was, in fastboot mode the RUU would still work, which it didnt..
help please!
thanks
Well, no one replied in time.
Asurion said it was covered under manufactures warranty. Zero deductible and a new HTC 10. And the old m7 was accepted tampered /unlocked.
Sent from my 2PS64 using Tapatalk
Wow, nice. I tried to help, but you got outside of my knowledge level. I'm really glad you got a 10. It's a really nice device.

Categories

Resources