• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Need Newest RUU NOW!!

So even with the update that is the only ruu to use. And the cause is my phone is stuck in boot loop whenever I flash or restore a rom
 
richking34 said:
So even with the update that is the only ruu to use. And the cause is my phone is stuck in boot loop whenever I flash or restore a rom
Click to expand...

Ahh...You're using 4EXT?

Sometimes it doesn't work right...


Fastboot the kernel, and it should be fine after that.
 
Just out of curiosity how did you get hboot 1.58 (per your sig in the OP) if you are stock Virgin Mobile with S-ON? You should have hboot 1.57.

ramjet73
 
richking34 said:
Anyone?
Click to expand...
Here's what I would suggest. Fastboot your recovery using the following command from a PC:

fastboot boot recovery.img (where recovery.img is the name of the recovery you flashed)

That will put you into recovery in a mode that will allow you to flash the entire ROM, including the boot.img (kernel). If you are using 4EXT make sure SmartFlash (S-ON) is disabled in the tools menu, then "format all partitions except SD card" in the wipe/format menu and flash the ROM.

I've been S-OFF for a while but that method always worked for me when I was S-ON. However, if you want to run anything other than Sense based ICS ROM's you are going to have to get S-OFF and downgrade your bootloader (hboot).

ramjet73
 
ramjet73 said:
Here's what I would suggest. Fastboot your recovery using the following command from a PC:

fastboot boot recovery.img (where recovery.img is the name of the recovery you flashed)

That will put you into recovery in a mode that will allow you to flash the entire ROM, including the boot.img (kernel). If you are using 4EXT make sure SmartFlash (S-ON) is disabled in the tools menu, then "format all partitions except SD card" in the wipe/format menu and flash the ROM.

I've been S-OFF for a while but that method always worked for me when I was S-ON. However, if you want to run anything other than Sense based ICS ROM's you are going to have to get S-OFF and downgrade your bootloader (hboot).

ramjet73
Click to expand...

i fixed using this method thank you
 
I download the file I see its not a zip file soo how do I installed
 

Attachments

  • uploadfromtaptalk1355573103405.jpg
    uploadfromtaptalk1355573103405.jpg
    17.9 KB · Views: 110
pancho32392 said:
My hboot is 1.58 and s-off
How do I exactly install or flash the RUU
Click to expand...

This just my 2 cents, but unless you are having a MAJOR problem or wanting to return phone. There isn't really a reason to run the RUU. It will put you back to stock ROM, S-ON, and 1.57 HBoot. Also before you run the RUU .exe file from your PC, I believe you have to re-lock the phone.
 
BoomBoom53 said:
This just my 2 cents, but unless you are having a MAJOR problem or wanting to return phone. There isn't really a reason to run the RUU. It will put you back to stock ROM, S-ON, and 1.57 HBoot. Also before you run the RUU .exe file from your PC, I believe you have to re-lock the phone.
Click to expand...
Rxpert83 said:
Ruu should NOT make you s-on
Click to expand...
That's correct. If you are already S-OFF, flashing the RUU does not set you back to S-ON and you don't have to relock the bootloader before running it. The only way to set S-ON is via the "fastboot oem writesecureflag" command which should not be issued unless you are sure that you have a signed stock bootloader installed.

For S-OFF users, as long as a nandroid is done before the RUU is flashed, the only things that are required afterwards are to flash a custom bootloader and recovery, then restore the nandroid and you will lose no settings. I agree that if everything is running fine and you are S-OFF there is probably no need to flash the RUU, but if you are having problems the whole process including taking the OTA (if you can see it) shouldn't take more than an hour.

For S-ON users, I think it's a good way to make sure everything is fully stock and in sync before doing the wire trick, but many have done it successfully with custom ROM's and recoveries installed.

ramjet73
 
ramjet73 said:
That's correct. If you are already S-OFF, flashing the RUU does not set you back to S-ON and you don't have to relock the bootloader before running it. The only way to set S-ON is via the "fastboot oem writesecureflag" command which should not be issued unless you are sure that you have a signed stock bootloader installed.

For S-OFF users, as long as a nandroid is done before the RUU is flashed, the only things that are required afterwards are to flash a custom bootloader and recovery, then restore the nandroid and you will lose no settings. I agree that if everything is running fine and you are S-OFF there is probably no need to flash the RUU, but if you are having problems the whole process including taking the OTA (if you can see it) shouldn't take more than an hour.

For S-ON users, I think it's a good way to make sure everything is fully stock and in sync before doing the wire trick, but many have done it successfully with custom ROM's and recoveries installed.

ramjet73
Click to expand...
i need a ruu for hboot 1.58 htc evo v 4g like asap !!!
 
master odysues said:
i need a ruu for hboot 1.58 htc evo v 4g like asap !!!
Click to expand...
You and a lot of other people.

If you find one please let us know since AFAIK there aren't any available yet for the Evo V or Evo 3D March OTA's.

The best you can do at this point is to either flash the stock ROM or go for S-OFF if you don't have it already, then flash the original RUU and the two updates which should be close to the equivalent of a 2.95 (hboot 1.58) RUU.

ramjet73
 
ramjet73 said:
You and a lot of other people.

If you find one please let us know since AFAIK there aren't any available yet for the Evo V or Evo 3D March OTA's.

The best you can do at this point is to either flash the stock ROM or go for S-OFF if you don't have it already, then flash the original RUU and the two updates which should be close to the equivalent of a 2.95 (hboot 1.58) RUU.

ramjet73
Click to expand...

Do we know that the ruu won't work or is it assumed? The November ota put the 3d on 1.58. Have we compared the sprint 1.58 to the vm 1.58? Did the ruu work on Sprint 1.58? Is firmware also scrutinized bytheruu prior to working?
 
Palmetto Fellow said:
Do we know that the ruu won't work or is it assumed? The November ota put the 3d on 1.58. Have we compared the sprint 1.58 to the vm 1.58? Did the ruu work on Sprint 1.58? Is firmware also scrutinized bytheruu prior to working?
Click to expand...
There was no November OTA for the Evo 3D. The original Sprint ICS RUU from July came with the 1.58 bootloader and that's still the most current for the Evo 3D so S-ON users of that model that have taken the March OTA can still flash the RUU if they downgrade their main version (mainver).

The Sprint and VM versions of the 1.58 hboot are identical but that has nothing to do with why the RUU won't flash. The problem is that the Evo V RUU and November OTA have the 1.57 hboot and the March OTA has the 1.58 hboot and the RUU process won't downgrade the hboot for S-ON users.

ramjet73
 
ramjet73 said:
There was no November OTA for the Evo 3D. The original Sprint ICS RUU from July came with the 1.58 bootloader and that's still the most current for the Evo 3D so S-ON users of that model that have taken the March OTA can still flash the RUU if they downgrade their main version (mainver).

The Sprint and VM versions of the 1.58 hboot are identical but that has nothing to do with why the RUU won't flash. The problem is that the Evo V RUU and November OTA have the 1.57 hboot and the March OTA has the 1.58 hboot and the RUU process won't downgrade the hboot for S-ON users.

ramjet73
Click to expand...

I think I am starting to see what you're saying. So even IF we could run the Sprint RUU, that's going to put Sprint firmware on there, and the HBOOT will still be at 1.58. That would then probably affect how the OTAs were applied. Again, I said "if" above...

Doesn't seem like any workaround is feasible. But I wonder...S-ON prevents unsigned stuff from being applied. Isn't the RUU signed?
 
You must log in or register to reply here.
Back
Top Bottom