Database Develop

Straight to Hboot, fastboot broken,

Good evening lads. First of all, let me just say that I'm not an HTC person. My friend gave it to me and asked me to fix it but I am currently stumped.
So, it's a regular Incredible S, European version, that got into a little accident.
The story
My friend somehow... Pee'd on it.
So, I was given a phone that boots straight into Hboot. I start thinking corrupt OS. I start thinking, why don't I just flash a new and fresh rom to it then? Following this thought I start looking up how this is done. Between that thought and now the phone has booted into both regular mode and safemode without a simcard, and only into safemode with a sim. This is done on a random basis, I can not find a pattern in button-presses and success. Also worth noting is that each time this happens you have to redo location, time and other "firstboot" settings. So I start thinking corrupt internal SD. So, I'm still looking at flashing and it says I need to enter fastboot. I select fastboot but I don't get the result I was hoping for.
Short version.
Phone boots to Hboot. Randomly boots to OS in either normal or safemode. With Sim only safemode.
Power and volume down don't work on Hboot. Volume up does Volume down.
Fastboot prints out
SD CHECKING...
Loading... [PG32DIAG.zip]
No image!
Loading... [PG32DIAG.zip]
No image or wrong image!
Loading... [PG32IMG.zip]
No image!
Loading... {PG32IMG.nbh]
No image or wrong image!
Click to expand...
Click to collapse
The phone has stock rom and kernel.
Info from Hboot
***LOCKED***
VIVO PVT SHIP S-ON RL
HBOOT 2.02.0002
RADIO-3831.18.00.11_M
eMMC-boot
May 22 2012,14:22:00
Click to expand...
Click to collapse
Please do ask if you need any more information. The next time the phone boots into OS I'll grab some more details.
And I must say I am terribly sorry if this has already been brought up, but I have not found anything similar. Searches for broken (and similar words) fastboot gives things related to it not being recognized as USB and powerbutton not working. Searches for the files gives me things related to people screwing up flashes. Some pointers or solutions would be great!
Thanks for reading!
F

Ferkswe said:
Good evening lads. First of all, let me just say that I'm not an HTC person. My friend gave it to me and asked me to fix it but I am currently stumped.
So, it's a regular Incredible S, European version, that got into a little accident.
The story
My friend somehow... Pee'd on it.
So, I was given a phone that boots straight into Hboot. I start thinking corrupt OS. I start thinking, why don't I just flash a new and fresh rom to it then? Following this thought I start looking up how this is done. Between that thought and now the phone has booted into both regular mode and safemode without a simcard, and only into safemode with a sim. This is done on a random basis, I can not find a pattern in button-presses and success. Also worth noting is that each time this happens you have to redo location, time and other "firstboot" settings. So I start thinking corrupt internal SD. So, I'm still looking at flashing and it says I need to enter fastboot. I select fastboot but I don't get the result I was hoping for.
Short version.
Phone boots to Hboot. Randomly boots to OS in either normal or safemode. With Sim only safemode.
Power and volume down don't work on Hboot. Volume up does Volume down.
Fastboot prints out
The phone has stock rom and kernel.
Info from Hboot
Please do ask if you need any more information. The next time the phone boots into OS I'll grab some more details.
And I must say I am terribly sorry if this has already been brought up, but I have not found anything similar. Searches for broken (and similar words) fastboot gives things related to it not being recognized as USB and powerbutton not working. Searches for the files gives me things related to people screwing up flashes. Some pointers or solutions would be great!
Thanks for reading!
F
Click to expand...
Click to collapse
1. Make sure you have a HTC USB cable.
2. Make sure you are using a USB 2.0 port on the PC and you have the current HTC drivers installed.
3. You can go to the HTCDEV.com site and get the official IncS RUU (Rom Update Utility). This is a Windows PC app that will flash the Stock ICS Rom to the device. Just follow the instructions on the screen.

tpbklake said:
1. Make sure you have a HTC USB cable.
2. Make sure you are using a USB 2.0 port on the PC and you have the current HTC drivers installed.
3. You can go to the HTCDEV.com site and get the official IncS RUU (Rom Update Utility). This is a Windows PC app that will flash the Stock ICS Rom to the device. Just follow the instructions on the screen.
Click to expand...
Click to collapse
I figured out the problem. It wasn't memory problem. It wasn't anything corrupted. It was the volume down button that was broken. So when I powered the device on, it got power + volume down = hboot.
When it randomly started all random it was when I held the volume up button or when I released power button fast enough.
Took me a while to realise since I didn't know that power and volume down took you to hboot.
Thanks for helping!
F

[Q] Stuck in a reboot loop, can't get into recovery, what to do?

I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!

brasstongue said:
I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!
Click to expand...
Click to collapse
Can u get into bootloader?? Press power + vol down??

brasstongue said:
After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols.
Click to expand...
Click to collapse
that means your firmware is either in a state of limbo, or you corrupted one of your partitions.
so I decided to try to reflash the stock ROM, using the RUU zip found here. Due to some problem
Click to expand...
Click to collapse
which ruu, and what was the problem
But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM.
Click to expand...
Click to collapse
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt

Thanks for the reply.
nkk71 said:
which ruu, and what was the problem
Click to expand...
Click to collapse
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
nkk71 said:
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
Click to expand...
Click to collapse
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
nkk71 said:
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
Click to expand...
Click to collapse
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
nkk71 said:
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
Click to expand...
Click to collapse
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
nkk71 said:
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt
Click to expand...
Click to collapse
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>

brasstongue said:
Thanks for the reply.
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>
Click to expand...
Click to collapse
my bad, thought I read Sprint, not sure if Sprint and Verizon use same recovery, but that doesn't really matter now
unless you can get to bootloader, you're stuck, sorry.
If your pc does see "fastboot devices" then it must be in bootloader and flashing a ruu.zip (if available) could (that's a very big could) get the device working again.

[Q] Semi Soft Bricked Phone

Hello everyone. In my attempt to experiment with custom ROMS yesterday, I seem to have sort of soft bricked my phone. When I install the stock OS, it installs fine, and I can start the phone. However, after it boots up, there are no apps. Just the clock at the top, the background, and the menu button in the bottom center (but pressing this button doesn't do anything). I can pull down the top menu and go to settings, but I don’t have access to anything else. Furthermore, after a couple minutes, the phone restarts itself. After this first restart, when its gets done booting, there is simply an empty black screen. The only way to get to the state mentioned before is to boot into bootloader, turn the phone off, and then turn it back on.
I’m wholly lost and out of ideas on how to go about troubleshooting this. Here is what I did yesterday to get to this point:
1. Unlocked the bootloader.
2. Flashed the latest Viper rom. It didn’t work; after booting up the phone was forever stuck on the Viper splash screen.
3. Flashed the stock Sprint HTC One rom. Again, after booting up the phone was forever stuck on the HTC splash screen.
4. Used TWRP to format all the data.
5. Flashed the stock Sprint HTC One rom again. This time it worked just fine. At this point, I thought I had discovered a valid method for fixing my soft bricked phone, so I decided to experiment with Viper and Android Revolutions roms to see if I could get them to work. I followed the process of installing a custom rom, getting stuck on the splash screen, formatting the data, then reinstalling the stock rom 3 times. On all three times the stock rom worked when I installed it. However, on the 4th iteration of this cycle, I reached the state I described above.
I tried using the RUU utility, but it doesn’t work (I get a signature verification error). I can enter bootloader and recovery without issue.

I've had this happen to me, Make sure that you re-lock your bootloader before the RUU
fastboot oem lock
I believe this will allow the RUU to start up right and repair. Lemme know how that goes.

jclark11 said:
I've had this happen to me, Make sure that you re-lock your bootloader before the RUU
fastboot oem lock
I believe this will allow the RUU to start up right and repair. Lemme know how that goes.
Click to expand...
Click to collapse
Do you mean you have had the same blank screen problam as well? Or RUU wouldn't work for you?
I'm pretty sure i relocked the bootloader when I tried doing the RUU, but I will definitely try again. Unfortunately, I'm on a trip at the moment, so I'm not sure when I'll be able to look at it again (hopefully Saturday or Tuesday).

Desire 510 bootloop, even affects some HBOOT functions

Hello,
I fear my daughters european HTC Desire 510 is bricked. First of all, we have already given up on what is on the phone. So no worries if a solution means wiping EVERYTHING from the phone, as long as we can get it to start again.
For some unknown reason, possibly an update the phone went into an almost constant bootloop a month or so before christmas. It could eventually get to the login screen, after going in circles for anything between 20 mins and hours. So I thought I would try to tamper with it. I know how to get into the bootloader from rooting other phones, so I went there to try to reset the phone to the factory settings. The result was that the phone now wouldn't go there again. If I tried to do a second reset it went straight to boot, without any way to interrupt, same thing when trying to go into recovery, instant reboot in the blink of an eye.
What then happens when the phone reboots? It gets to the first screen, green HTC logo and "Powered by Android", it sits there for maybe 30 seconds, then it goes black, buzz and back to the previous HTC logo. And this goes on until the battery dies, I pull the battery or I quickly push the vol down and power buttons to go into HBOOT.
I usually don't give up this easily. I found another thread here on some european guy having trouble with his Desire 510, and one of the answers linked to a RUU for a european 510. So I thought, why not, I hadn't unlocked the bootloader yet. So I downloaded the RUU and tried to install it. It messed with me a little, aparently as expected, and then ran through the whole installation. Before the upgrade, well downgrade to be specific the OS was ver. 1.51.401.4 but now claims to be 1.51.401.1. Problem though is, absolutely no change in behaviour. I have restarted the phone after pulled the battery and waited for anything between seconds and an hour, and the phone does exactly the same thing. It happily goes into HBOOT but won't allow me to do a factory reset, nor will it allow me to access recovery.
It will allow me to access Fastboot though, so I thought, hmmm if I install ClockWorkMod or TWRP, maybe something will change. Since I'm more used to working with CWM I went down that road, went to htcdev.com, got the unlock code and unlocked the phone. It now says <<< UNLOCKED >>> and I ran the fastboot devices command, that happily returned some "CC4********7 fastboot". So I went ahead and installed CWM, the installation went all the way and in the end it happily stated that CWM was installed. But did that mean any difference, noooo. If I try to access either Recovery, that should start CWM or Factory reset and also Check smartsd, instant reboot. And I mean INSTANT. Fastboot works, as already stated. I can also get into Image CRC and Show barcode, but what good is that.
Any ideas. I'm beginning to think that something is physically broken inside the phone.

Help, I can't get back to stock!!!

Hello my fellow friends in HTC Desire 626s Metro PCs land.
This is Isaiah speaking. I've run into a little misfortune here and I wanted to know if someone would be kind enough to help me out.
I have seemed to get myself in a little snag, were for some reason after I relock my phone, it won't reboot the system. What happens is, it boots right into download mode. So I unlocked it again and guess what. Everything booted normally.
Then I go to unlock it again, it jumps right back to download mode. I'm going bonkers over here, like Willy Wonka bonkers because i can't figure out why I can't relock my phone without it going right back to download mode. I flashed stock recovery through cmd, before I relocked it, that didn't work. All I did was root my phone. No debloated roms or anything. Just simply rooted my phone. I'm on Android 6.0.1. Somebody will you please help me get back to stock. Sigh, momma told there'd be days like this! Lol!!! I had to throw in a little humor.

I had the exact same problem. I found a possible fix. If you are just trying to get back to the recovery area.
Press and hold the power and volume down keys then release the power.
Once on the download mode screen scroll to Reboot to bootloader
Once in the bootloader area select Reboot to recovery mode.
This is the only way I can get to recovery mode.

Ace18o said:
I had the exact same problem. I found a possible fix. If you are just trying to get back to the recovery area.
Press and hold the power and volume down keys then release the power.
Once on the download mode screen scroll to Reboot to bootloader
Once in the bootloader area select Reboot to recovery mode.
This is the only way I can get to recovery mode.
Click to expand...
Click to collapse
What i'm trying to do is actually get back to the stock recovery so that I can re-flash the official ruu file from the official HTC Roms Website because my phone has not been running smoothly on the ota update they sent out in July. I figured since the the sites ruu file is 1.32gb and the actual ota update was 845mb, may-be there's something in the ruu that will fix this issue.
I already tried unrooting it by flashing stock recovery through command prompt then going back and re-locking my device. But after I re-locked my phone, instead of it rebooting normally where it goes to the boot animation, then loads the welcome screen to allow you to go through putting your wifi info and email address etc. It returns to download mode, or boot loader mode. Then every time I restart my phone it does the same thing and it goes back to the same screen. But when I re-unlock it, it boots fine.

s3llz said:
What i'm trying to do is actually get back to the stock recovery so that I can re-flash the official ruu file from the official HTC Roms Website because my phone has not been running smoothly on the ota update they sent out in July. I figured since the the sites ruu file is 1.32gb and the actual ota update was 845mb, may-be there's something in the ruu that will fix this issue.
I already tried unrooting it by flashing stock recovery through command prompt then going back and re-locking my device. But after I re-locked my phone, instead of it rebooting normally where it goes to the boot animation, then loads the welcome screen to allow you to go through putting your wifi info and email address etc. It returns to download mode, or boot loader mode. Then every time I restart my phone it does the same thing and it goes back to the same screen. But when I re-unlock it, it boots fine.
Click to expand...
Click to collapse
Ahh my bad, I was very tired last night.

s3llz said:
What i'm trying to do is actually get back to the stock recovery so that I can re-flash the official ruu file from the official HTC Roms Website because my phone has not been running smoothly on the ota update they sent out in July. I figured since the the sites ruu file is 1.32gb and the actual ota update was 845mb, may-be there's something in the ruu that will fix this issue.
I already tried unrooting it by flashing stock recovery through command prompt then going back and re-locking my device. But after I re-locked my phone, instead of it rebooting normally where it goes to the boot animation, then loads the welcome screen to allow you to go through putting your wifi info and email address etc. It returns to download mode, or boot loader mode. Then every time I restart my phone it does the same thing and it goes back to the same screen. But when I re-unlock it, it boots fine.
Click to expand...
Click to collapse
Just don't lock the boot loader, I didn't lock my boot loader to run the RUU. My phone was running the firmware that if came with and I had unlocked the boot loader, flashed TWRP, and rooted. All I did was flash the stock recovery then ran the RUU(it didn't work turned off so I booted into fastboot) and it updated.

Problem solved
IsaacGuti said:
Just don't lock the boot loader, I didn't lock my boot loader to run the RUU. My phone was running the firmware that if came with and I had unlocked the boot loader, flashed TWRP, and rooted. All I did was flash the stock recovery then ran the RUU(it didn't work turned off so I booted into fastboot) and it updated.
Click to expand...
Click to collapse
Thank you so much for your advice. It worked like a charm. Consider this case closed. I downloaded the official ruu file for my particular carrier and left the boot loader unlocked, but installed the stock recovery through command prompt. Then, I connected my device to my pc via usb as instructed through the ruu. Then, zing.....watched it zap my phone with the stock rom of 6.0.1. Solved my lagging issues as well as my network switching issues as well. For some strange reason, my device kept switching between different carriers which caused me not to be able to sent text messages. I was like "What in the Doc Brown Marty McFly is going on here!!!" Had me like Doc Brown "Great Scott!!!!" LOL!! Thanks buddy for your advice though. Problem Solved.:good::highfive::victory::victory:

s3llz said:
Thank you so much for your advice. It worked like a charm. Consider this case closed. I downloaded the official ruu file for my particular carrier and left the boot loader unlocked, but installed the stock recovery through command prompt. Then, I connected my device to my pc via usb as instructed through the ruu. Then, zing.....watched it zap my phone with the stock rom of 6.0.1. Solved my lagging issues as well as my network switching issues as well. For some strange reason, my device kept switching between different carriers which caused me not to be able to sent text messages. I was like "What in the Doc Brown Marty McFly is going on here!!!" Had me like Doc Brown "Great Scott!!!!" LOL!! Thanks buddy for your advice though. Problem Solved.:good::highfive::victory::victory:
Click to expand...
Click to collapse
By any chance, do you have the stock recovery link? I'm having the same issue :/

Sharkyzz said:
By any chance, do you have the stock recovery link? I'm having the same issue :/
Click to expand...
Click to collapse
I will upload it so that you can dowload it. Make sure when you go in to command prompt that you type exactly what it says "Stock_Recovery.img" without the parenthesis of course. Thats what i had to do. it will look like this when you type it in "fastboot flash recovery Stock_Recovery.img"
Link below.
https://drive.google.com/file/d/0ByVHpaOig07QT1hfUmY4bkZrbGs/view?usp=sharing

s3llz said:
I will upload it so that you can dowload it. Make sure when you go in to command prompt that you type exactly what it says "Stock_Recovery.img" without the parenthesis of course. Thats what i had to do. it will look like this when you type it in "fastboot flash recovery Stock_Recovery.img"
Link below.
https://drive.google.com/file/d/0ByVHpaOig07QT1hfUmY4bkZrbGs/view?usp=sharing
Click to expand...
Click to collapse
PS. Also, when I used the Rom update utility it failed once. But if you look carefully at the picture instructions on the screen, it tells you to unplug your usb cable and pull out the battery. But of course we both know we can't take out the battery. So what you do is, just unplug the usb, but don't restart your phone. Leave it on the screen where it stopped on. When you get to the screen where it tells you to plug your usb back in, then you plug it back in. After that, you just follow the instructions on the screen of the ruu, and it will begin flashing your device with the stock rom. That was the step I kept missing. To unplug the usb and then plug it back in when the ruu says to.

s3llz said:
I will upload it so that you can dowload it. Make sure when you go in to command prompt that you type exactly what it says "Stock_Recovery.img" without the parenthesis of course. Thats what i had to do. it will look like this when you type it in "fastboot flash recovery Stock_Recovery.img"
Link below.
https://drive.google.com/file/d/0ByVHpaOig07QT1hfUmY4bkZrbGs/view?usp=sharing
Click to expand...
Click to collapse
PS. Also, when I used the Rom update utility it failed once. But if you look carefully at the picture instructions on the screen, it tells you to unplug your usb cable and pull out the battery. But of course we both know we can't take out the battery. So what you do is, just unplug the usb, but don't restart your phone. Leave it on the screen where it stopped on. When you get to the screen where it tells you to plug your usb back in, then you plug it back in. After that, you just follow the instructions on the screen of the ruu, and it will begin flashing your device with the stock rom. That was the step I kept missing. To unplug the usb and then plug it back in when the ruu says to.