Database Users

cant restore phone with ruu 1.29

it gets to writing signiture and says it cant update this rom. is there a newer ruu from sprint. it used to work till i got my replacement phone in.

I had same issue..
what I did was (and this only worked cuz I had this already done) Rooted the phone with RA 1.5.2 recovery and flashed Fresh 1.0
once I got it to successfully load into fresh.. then I ran the RUU 1.29 and it worked..

still cant get it to let me un root it. it says that it is the wrong rom to do it. is there a new ruu

Have you tried flashing while in quick boot?

sorry to be such a newb. but what is quick boot and how do i get to it

Power your phone off. Hold the volume down button and power it on. You will get a menu and one of the options is quick boot (I think it's volume up but I'm not positive).
With it hooked up to your computer, check device manager in windows and make sure you don't have any missing phone drivers. If you don't then run the RUU.

ok trying that now. and no errors with drivers

still doesnt work as soon as it gets to updating signature it stops. i dont get it. i have done it a million times with no problems. now it wont work

do you have "usb debugging" turn OFF?

I can confirm testing it with debugging off it still doesn't work. I've tried a million times as well, same problem. I'm not sure if we have to flash the stock rom image before doing so, but in flashrec it only gives me the option of backing up image before actually flashing one and I get an error "Backup Failed: Could not run command" not sure if that has anything to do with it

RUU 1.29 CDMA Sprint
Here's how I got it to work. I reflashed mine couple weeks ago with stock sprint rom (orginal factory state). You need to have HTC sync connected first. Once you establish connection than run RUU 1.29. The hero will drp connection than automatically re-install drivers than it will continue to load the original rom from sprint.

mulcahyd said:
Here's how I got it to work. I reflashed mine couple weeks ago with stock sprint rom (orginal factory state). You need to have HTC sync connected first. Once you establish connection than run RUU 1.29. The hero will drp connection than automatically re-install drivers than it will continue to load the original rom from sprint.
Click to expand...
Click to collapse
I was working with someone who was having an issue flashing the RUU (failing at checking license). I took him in to fastboot and we literally tried manually running the restore step by step. Basically what the RUU does but manually. And it would still fail at the license. It wasn't a driver issue.
But your fix will work for people whose RUU says it can't find the phone after it reboots it.

flipzmode said:
I was working with someone who was having an issue flashing the RUU (failing at checking license). I took him in to fastboot and we literally tried manually running the restore step by step. Basically what the RUU does but manually. And it would still fail at the license. It wasn't a driver issue.
But your fix will work for people whose RUU says it can't find the phone after it reboots it.
Click to expand...
Click to collapse
So how do we get it to work? I get the same error, unfortunately. I was thinking about trying your hero ruu update that you put out...

obannvi said:
So how do we get it to work? I get the same error, unfortunately. I was thinking about trying your hero ruu update that you put out...
Click to expand...
Click to collapse
The one on ppcgeeks? Heh I need to pull that. I used it earlier and found that after using it I had no access to the /data folder. Not huge deal if you are using it to take your phone back to Sprint or something, but no good if you are wanting to use it. I need to fix the script but am swamped right now.
What's your reason for wanting to RUU? Is your phone "with google" branded?

flipzmode said:
The one on ppcgeeks? Heh I need to pull that. I used it earlier and found that after using it I had no access to the /data folder. Not huge deal if you are using it to take your phone back to Sprint or something, but no good if you are wanting to use it. I need to fix the script but am swamped right now.
What's your reason for wanting to RUU? Is your phone "with google" branded?
Click to expand...
Click to collapse
I have the "With Google" branding. I wanted too revert back and get it swapped out. I also wanted to reflash Fresh to it...

obannvi said:
I have the "With Google" branding. I wanted too revert back and get it swapped out. I also wanted to reflash Fresh to it...
Click to expand...
Click to collapse
So of the people that have been having the issue where it fails at the licensing issue and gives you: Error[140]: Bootloader Version Error, all the ones I've talked to (only a couple of you) have had "with google" phones. Although all have said that they were able to RUU before and can't anymore.
If you strictly want to return to stock so that you can return the phone then I can help you. PM me.

flipzmode said:
So of the people that have been having the issue where it fails at the licensing issue and gives you: Error[140]: Bootloader Version Error, all the ones I've talked to (only a couple of you) have had "with google" phones. Although all have said that they were able to RUU before and can't anymore.
If you strictly want to return to stock so that you can return the phone then I can help you. PM me.
Click to expand...
Click to collapse
I just dont understand why its sluggish. It was never sluggish before. I figure by reverting back to stock and then re-freshing it, it should be ok.

You can try just clearing your cache (my app installer in my sig can help you do that) and then flashing fresh on top of itself to see if that helps the speed issue.

flipzmode said:
You can try just clearing your cache (my app installer in my sig can help you do that) and then flashing fresh on top of itself to see if that helps the speed issue.
Click to expand...
Click to collapse
I'll give it a shot. I do have a nand backup of my original install before I installed Fresh...I did that prior and then I installed Fresh again...

Didnt work, still sluggish. I did a wipe through the recovery menu so we'll see what happens.

[Q]Mango on rev 1.4

Has anyone been able to update to mango on rev 1.4? I'm on 7392, unlocked and provisioned to receive the 7401 update but my phone stalls at step 6 of 9, rebooting the phone. Zune says I have an update, but can't complete the update.
Sent from my SGH-i917. using XDA Windows Phone 7 App

I don't really think you can
Did you manage to make a backup ?
I can't even do that

I can make a backup for 7004 and 7008 then it stalls on 7392
Sent from my SGH-i917. using XDA Windows Phone 7 App

draino623 said:
I can make a backup for 7004 and 7008 then it stalls on 7392
Sent from my SGH-i917. using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Yeah same here

http://forum.xda-developers.com/showthread.php?t=1224139 Look here for the instruction of moving to 7720 for Samsung devices. It took around 2 hours on my Samsung focus, and yes, it's rev 1.4. But now that everyone and the rev 1.3 owners are rolling to official Mango, I feel like we're being left out (Until "late-October" AT&T says)

try killing the zune autolauncher service, it was stalling the update process (would hang at rebooting) on my 1.3 device, after killing it, it went through fine

adiliyo said:
try killing the zune autolauncher service, it was stalling the update process (would hang at rebooting) on my 1.3 device, after killing it, it went through fine
Click to expand...
Click to collapse
But we all are on rev 1.4, which at the moment can only use 7720 RTM, not official. All 1.4 devices will not get update notification until late October (Quote AT&T). Official Mango update is pushed to 1.3 devices today, though. Have fun, adiliyo~

adiliyo said:
try killing the zune autolauncher service, it was stalling the update process (would hang at rebooting) on my 1.3 device, after killing it, it went through fine
Click to expand...
Click to collapse
Hi, forgive my ignorance but what do you mean by "killing the Zune Autolauncher service"?
I have the Samsung Focus v1.4 on 7390-Walshed. I haven't been able to successfully unWalsh my phone and when I received the 7392 update, I got stuck on step 6 (Rebooting phone) stage where the phone would get stuck on reboot for hours. (Yes, I let it run for 2+ hours but no luck and a very warm phone.)
So, I'm trying to get to Mango anyway possible.
Thanks.

Could somebody please explain to me how to check what revision I'm using? I can't seem to find that anywhere online.
Thanks

remove the battery and check the white sticker behind it.

kimck99 said:
Hi, forgive my ignorance but what do you mean by "killing the Zune Autolauncher service"?
I have the Samsung Focus v1.4 on 7390-Walshed. I haven't been able to successfully unWalsh my phone and when I received the 7392 update, I got stuck on step 6 (Rebooting phone) stage where the phone would get stuck on reboot for hours. (Yes, I let it run for 2+ hours but no luck and a very warm phone.)
So, I'm trying to get to Mango anyway possible.
Thanks.
Click to expand...
Click to collapse
open task manager and end the "ZuneLauncher.exe" process, after killing that the rebooting steps worked without any hitches for me.
this was during my update to the leaked 7720.68 RTM, so if you're having those issues with a 1.4 device regardless of what you're trying to flash, it's something to try, as it won't hurt anything even if it doesn't help.
i only had to do it once, and now i leave it running and the phone just got the "samsung update" today and it flashed just fine.

adiliyo said:
open task manager and end the "ZuneLauncher.exe" process, after killing that the rebooting steps worked without any hitches for me.
this was during my update to the leaked 7720.68 RTM, so if you're having those issues with a 1.4 device regardless of what you're trying to flash, it's something to try, as it won't hurt anything even if it doesn't help.
i only had to do it once, and now i leave it running and the phone just got the "samsung update" today and it flashed just fine.
Click to expand...
Click to collapse
Well, I gave this a try but didn't work. A few comments.
1. In Task Manager, the only process that I have for ZUNE is the Zune.exe. I don't see a ZuneLauncher.exe process.
2. As before, the phone gets stuck on reboot at step 6 of 10. Essentially, the phone has the Samsung logo on the screen and just stays there.
3. When I power down the phone and reboot, I get an 801812C1 error code. (The usual stopping point for me.)
So, not sure what to try next. I've been reading as much as I could on this forum and one thing I haven't tried is the UCKJ2 AT&T i917 (I think) ROM install. But I've read a few people who have a "Walshed" phone not being about to get that ROM installed. Stuck at the same point. (Or they could also have the rev1.4 version as well like me. A double whammy for me, Walshed and Rev 1.4 ....sigh).
Thanks for the tip though.

[Q] Tried to restore and failed. Now phone isnt booting anymore. Help please!

Hi,
I was running 7712 and tried to restore a NoDo Restore Point I had. It failed. Now, it shows the samsung screen and eventually gets to the connect to PC screen but it doesnt fully bootup anymore. It can still connect to my PC and retries using the restore point but never works. Help is MUCH appreciated. Thanks

wilcoholic5 said:
Hi,
I was running 7712 and tried to restore a NoDo Restore Point I had. It failed. Now, it shows the samsung screen and eventually gets to the connect to PC screen but it doesnt fully bootup anymore. It can still connect to my PC and retries using the restore point but never works. Help is MUCH appreciated. Thanks
Click to expand...
Click to collapse
Had this problem too, and didn't manage to restore.
I suppose it happened because I filled more than half of the available capacity (or so I think).
I even tried downgrading to 7004 and retry the backup then, that didn't work either.
You can try that, if that doesn't work... you'd be out of luck, like I was.
Try again and again different scenarios, be imaginative, maybe you can find a solution that works in your case.

I tried flashing 7004 to it with the WP7 USB Image tool and that did not work either. I keep getting an error..something about the phone not matching? The error descriptions cuts off and I cant see all of it..and I did use the correct one for my hardware rev. Help?

wilcoholic5 said:
I tried flashing 7004 to it with the WP7 USB Image tool and that did not work either. I keep getting an error..something about the phone not matching? The error descriptions cuts off and I cant see all of it..and I did use the correct one for my hardware rev. Help?
Click to expand...
Click to collapse
Can you detail a bit more about your phone?
Revision (1.3/1.4), card installed (type/size)
When the error started to appear etc. Anything you think might be useful/relevant.

I have hardware rev 1.3. I do not have any SD card in my phone at the moment, nor have I ever. I can get to the download menu and restoration menu in zune, but it all fails. I think what messed things up was I tried to format while on 7712 to try to get back to factory default. This took me to a "new" 7712 with the default settings. I even tried formatting by holding PWR + Vol DWN + camera to no avail. When i was stuck with 7712, I tried to use my restore point to get back to NoDo. Thats when it all came crashing down. I think I need to wait until newer roms become available. Help?

wilcoholic5 said:
I have hardware rev 1.3. I do not have any SD card in my phone at the moment, nor have I ever. I can get to the download menu and restoration menu in zune, but it all fails. I think what messed things up was I tried to format while on 7712 to try to get back to factory default. This took me to a "new" 7712 with the default settings. I even tried formatting by holding PWR + Vol DWN + camera to no avail. When i was stuck with 7712, I tried to use my restore point to get back to NoDo. Thats when it all came crashing down. I think I need to wait until newer roms become available. Help?
Click to expand...
Click to collapse
Not being able to hard reset suggests some kind of problem, which either points to the hardware or the flash. Let's leave the hw for now, so you can easily assume it's a flashing problem.
I would go with a 7004 ROM and start from scratch. If everything works well, you might be able to use your restore.
However, if something's really wrong with your phone, flashing might actually do more damage and possibly brick your phone. Not to scare you, but to make you aware of alternatives.

I have already tried flashing with the 7004 rom and it did not work. I kept getting an error about the devices not matching. I am thinking that I need to flash with at least a 7712 rom, since it seems that is now the phones default version. weird.

Bump. I think that if i were to have a restore point that was 7712 or above, I can get the phone back in operating condition. I'd be willing to pay if anyone is interested. However, it has to have no windows live account attached to it. I.E. restore, and skip entering in account info.

samfirmware.com has couple firmware for Focus. If you can get your phone into download mode (connect to PC screen), you can flash the firmware to it. Not sure which tool to use (ODIN or else) for flashing firmware. Check the dev forum for help.

Thanks for the reply. I checked out samfirmware.com and didnt see any specifically for the focus..any chance i can get a link to them?
Edit: Nevermind, I found them. Ill try them out.

I tried flashing with the roms on samfirmware.com, I got the same results with those roms as the ones posted in the forums here. I assume I need at least a 7712 rom to flash to, as my phone has essentially "forgotten" that anything before that exists and doesnt know how to go back to it. I can still use a fresh restore point from 7712 or beyond please. I am stuck using some horrible old phone while i fix this lol.
Edit: Grammar

Happy to report that after various configurations of my process, I finally got it work. I used the roms that are up on these forums. If anyone has the same issue i had here... try different computers. try different cables. try different ports. That's how I got it to work. Thanks to those that gave me suggestions.

I sense that when official Mango finally hits, we will see a lot ppl hitting the same issue as you because you must roll back to NoDo firmware before you can apply official Mango updates if you're on 7712 Mango beta, IIRC.

foxbat121 said:
I sense that when official Mango finally hits, we will see a lot ppl hitting the same issue as you because you must roll back to NoDo firmware before you can apply official Mango updates if you're on 7712 Mango beta, IIRC.
Click to expand...
Click to collapse
If I read this (http://forum.xda-developers.com/showthread.php?t=1215501) correctly, you should be able to start with 7712... just jump to step 16 as indicated by step 5a.

schahr01 said:
If I read this (http://forum.xda-developers.com/showthread.php?t=1215501) correctly, you should be able to start with 7712... just jump to step 16 as indicated by step 5a.
Click to expand...
Click to collapse
I'm not so sure about that. Just ask those who walshed their Focuse try to get to NoDo faster(which is actually also from Microsoft). There are likely firmware updates accompanied by the official release for Focus. Anything that's not running official NoDo updates will probably have a tough time getting that official update, or anything after that.

[Q] stuck at system update.

It's my friends phone,and during the system update from LG,the phone rebooted to the lockscreen,but the screen is not responsive to any touch,so I then was able to enter into the recovery and I noticed that the android symbol was still there and underneath it still is saying that it's still performing the system update,but it never finishes.
I'm thinking it was probably a bad download,but he cancelled his insurance from Sprint and the are telling him that he needs to pay for a news phone.
My question is there a way to recover from this?
Like running a ruu?
Any ideas would be appreciated.

REVREN said:
It's my friends phone,and during the system update from LG,the phone rebooted to the lockscreen,but the screen is not responsive to any touch,so I then was able to enter into the recovery and I noticed that the android symbol was still there and underneath it still is saying that it's still performing the system update,but it never finishes.
I'm thinking it was probably a bad download,but he cancelled his insurance from Sprint and the are telling him that he needs to pay for a news phone.
My question is there a way to recover from this?
Like running a ruu?
Any ideas would be appreciated.
Click to expand...
Click to collapse
see if you can get into download by plugging phone into computer and as soon as you plug it in hold the volume up as soon as you plug it in it should go into download mode then look for a forum with the restore files and flashtool and all that cant help you much i dont have the sprint variant oh was your friend rooted when he took the ota

dont know really what to do, bring it in as its now and let lg sort it.
not happy with that, risk permanently bricking it by reboot into download mode. I wager you had custom recovery on phone whilst trying ota
send from the jungle

Nope the phone is stock. never been rooted.

spinninbsod said:
see if you can get into download by plugging phone into computer and as soon as you plug it in hold the volume up as soon as you plug it in it should go into download mode then look for a forum with the restore files and flashtool and all that cant help you much i dont have the sprint variant oh was your friend rooted when he took the ota
Click to expand...
Click to collapse
Do you have the link for the restore files and flashtool?
,I've looked everywhere in the forum with no luck.

HTC 10 bricked during RUU

I decided I was going move back to stock verizon software from 2.41.617.3 and try out ViperROM. I would use the software I had on hand, execute the 1.85.605.8 RUU, and then OTA to nougat. During the RUU process, I seen on the device screen it was updating the hboot, then acted like it restarted but never powered back on. After letting the device lay dead still connected to the USB for a day, I've removed the SD/SIM, plugged it into a wall charger, tried to power on and hard reset, and getting nowhere.
My question is there a way resurrect this phone using Qualcomm HS-USB QDLoader or similar tools? or did I just brick with no return?

ricanbeans said:
I decided I was going move back to stock verizon software from 2.41.617.3 and try out ViperROM. I would use the software I had on hand, execute the 1.85.605.8 RUU, and then OTA to nougat. During the RUU process, I seen on the device screen it was updating the hboot, then acted like it restarted but never powered back on. After letting the device lay dead still connected to the USB for a day, I've removed the SD/SIM, plugged it into a wall charger, tried to power on and hard reset, and getting nowhere.
My question is there a way resurrect this phone using Qualcomm HS-USB QDLoader or similar tools? or did I just brick with no return?
Click to expand...
Click to collapse
what firmware was on the the phone prior to trying to RUU?

ricanbeans said:
I decided I was going move back to stock verizon software from 2.41.617.3 and try out ViperROM. I would use the software I had on hand, execute the 1.85.605.8 RUU, and then OTA to nougat. During the RUU process, I seen on the device screen it was updating the hboot, then acted like it restarted but never powered back on. After letting the device lay dead still connected to the USB for a day, I've removed the SD/SIM, plugged it into a wall charger, tried to power on and hard reset, and getting nowhere.
My question is there a way resurrect this phone using Qualcomm HS-USB QDLoader or similar tools? or did I just brick with no return?
Click to expand...
Click to collapse
To confirm, you basically went from the US unlocked N 2.41.617.3 firmware to the VzW MM RUU, correct?
Quick question.
Why did you flash the VzW MM RUU instead of the N RUU?

aer0zer0 said:
what firmware was on the the phone prior to trying to RUU?
Click to expand...
Click to collapse
BS_US001 2.41.617.3
andybones said:
To confirm, you basically went from the US unlocked N 2.41.617.3 firmware to the VzW MM RUU, correct?
Click to expand...
Click to collapse
Yes you're correct.
andybones said:
Quick question.
Why did you flash the VzW MM RUU instead of the N RUU?
Click to expand...
Click to collapse
I wasn't aware at the time that someone had posted the nougat RUU zip yet and HTC Sync Manager didn't have the nougat RUU available. I had the 1.85.605.8 RUU exe downloaded already from when I S-OFF'd. I've downgraded this phone before from 2.41.605.12 to 1.85.605.8 before no problems using the same RUU exe file. I let the RUU start, went and made breakfast, came back the software was stuck and the phone was dark.

ricanbeans said:
BS_US001 2.41.617.3
Yes you're correct.
I wasn't aware at the time that someone had posted the nougat RUU zip yet and HTC Sync Manager didn't have the nougat RUU available. I had the 1.85.605.8 RUU exe downloaded already from when I S-OFF'd. I've downgraded this phone before from 2.41.605.12 to 1.85.605.8 before no problems using the same RUU exe file. I let the RUU start, went and made breakfast, came back the software was stuck and the phone was dark.
Click to expand...
Click to collapse
Very sorry, my friend. Quite unfortunate.
I stick to the sd-card method usually.
But there's no reason I see why this happened to you.
:-/

So you had The US unlocked firmware? Did you complete converting it back to vzw cod and mid prior to trying to RUU?

aer0zer0 said:
So you had The US unlocked firmware? Did you complete converting it back to vzw cod and mid prior to trying to RUU?
Click to expand...
Click to collapse
yes, right before I applied the RUU. The MID was the same @ 2PS65000 and I switched the CID back @ VZW__001.

ricanbeans said:
yes, right before I applied the RUU. The MID was the same @ 2PS65000 and I switched the CID back @ VZW__001.
Click to expand...
Click to collapse
Just sounds like bad luck then. I've done that same thing before with no repercussions.

Verizon will replace it if they don't know.
I hard bricked mine due to a firmware downgrade. The phone completely died.
But I got Verizon to replace it for free, since they didn't know what I did. And several months later no charge. So yeah, just call them and get a warranty replacement.

Spinkness said:
Verizon will replace it if they don't know.
I hard bricked mine due to a firmware downgrade. The phone completely died.
But I got Verizon to replace it for free, since they didn't know what I did. And several months later no charge. So yeah, just call them and get a warranty replacement.
Click to expand...
Click to collapse
I called HTC since I bought the phone off Swappa and it's still under warranty. Hopefully they don't get it working and realize what I was doing :fingers-crossed:

Doing a little bit of morning internet browsing and seen this intresting tidbit. I knew HTC Sync caused an ADB server mismatch sometimes in command prompt, but this lil piece of info would have been nice before running an RUU exe. I suppose installing an RUU via SD card is sounds like the safer bet from now on.

ricanbeans said:
Doing a little bit of morning internet browsing and seen this intresting tidbit. I knew HTC Sync caused an ADB server mismatch sometimes in command prompt, but this lil piece of info would have been nice before running an RUU exe. I suppose installing an RUU via SD card is sounds like the safer bet from now on.
Click to expand...
Click to collapse
This has been known information for quite sometime.. Nothing new to the 10. Usually one will install hTC Syncvto get the drivers, then uninstall hTC Sync as the drivers stay.
I always run RUU on SD-Card myself because I feel it's the safest way. I'm always afraid of losing power or something and my PC shuts off mid RUU.

andybones said:
This has been known information for quite sometime.. Nothing new to the 10. Usually one will install hTC Syncvto get the drivers, then uninstall hTC Sync as the drivers stay.
I always run RUU on SD-Card myself because I feel it's the safest way. I'm always afraid of losing power or something and my PC shuts off mid RUU.
Click to expand...
Click to collapse
Exactly, as OCD as I am, I have all ruu's on separate 4GB microsd's, labeled and such. I only use fastboot or exe on rare occasions

ricanbeans said:
I called HTC since I bought the phone off Swappa and it's still under warranty. Hopefully they don't get it working and realize what I was doing :fingers-crossed:
Click to expand...
Click to collapse
I doubt they will. Most likely they'll part it out or toss it. Not really worth the fuss for them.
I can't even count how many rooted/s-off/bootloader unlocked devices I've replaced, and never had any problems. Sure they say your warranty is now void, but if it's hard bricked that bad, it's not coming back, and they'll never know!

aer0zer0 said:
Exactly, as OCD as I am, I have all ruu's on separate 4GB microsd's, labeled and such. I only use fastboot or exe on rare occasions
Click to expand...
Click to collapse
That is a little OCD, but probably should be considered "best practices." A good use for those old too-small 4g microsd cards, too. Good suggestion. Thanks.

hgoldner said:
That is a little OCD, but probably should be considered "best practices." A good use for those old too-small 4g microsd cards, too. Good suggestion. Thanks.
Click to expand...
Click to collapse
My travel kit... I still have all my 7, 8 ,9 ruu's the same exact way