I was on HBOOT 1.58 which has problems with most roms so I wanted to downgrade my HBOOT. I used JuopunutBear to gain S-OFF and then downgraded my HBOOT to 1.50 and my radio is 1.06.00.1216. I then installed CM10. I could not get any data. I checked APNs and the APN is there. I then ran the retail RUU to see if it fixed the issue and it did not. I tried installing several different HBOOTS with no change. I tried a PRL update on the official OTA and the issue still exists. Any ideas?
hanzohittori said:
I was on HBOOT 1.58 which has problems with most roms so I wanted to downgrade my HBOOT. I used JuopunutBear to gain S-OFF and then downgraded my HBOOT to 1.50 and my radio is 1.06.00.1216. I then installed CM10. I could not get any data. I checked APNs and the APN is there. I then ran the retail RUU to see if it fixed the issue and it did not. I tried installing several different HBOOTS with no change. I tried a PRL update on the official OTA and the issue still exists. Any ideas?
Click to expand...
Click to collapse
If you flashed the RUU before doing the wire trick per the instructions on the unlimited.io website you should be on firmware (baseband level) 1.09.00.0706. My phone automatically reactivated after doing the wire trick and gaining S-OFF. If yours hasn't done that you should probably call Sprint and ask them to reactivate it for you.
ramjet73
Related
Hey everyone I ran into a bit of an issue here. I was getting my defective rezound ready to send back to verizon and ran the latest ota ruu or so I thought..... I actually ran the ICS .10 leak I had downloaded also which upgraded my hboot to 2.25. I am s-on so from all my research I need to be s-off to downgrade the hboot so I can reinstall factory GB which I'm sure I can handle but on the Unlimited.io, website 3.14.605.5 is the newest they have.
Is it possible the use the .5 or does someone have another way to help me get s-off? I just don't want to screw it up since I'm sending it back:silly:
Thank everyone!!
.5 and .10 are the same h boots
snow580 said:
Hey everyone I ran into a bit of an issue here. I was getting my defective rezound ready to send back to verizon and ran the latest ota ruu or so I thought..... I actually ran the ICS .10 leak I had downloaded also which upgraded my hboot to 2.25. I am s-on so from all my research I need to be s-off to downgrade the hboot so I can reinstall factory GB which I'm sure I can handle but on the Unlimited.io, website 3.14.605.5 is the newest they have.
Is it possible the use the .5 or does someone have another way to help me get s-off? I just don't want to screw it up since I'm sending it back:silly:
Thank everyone!!
Click to expand...
Click to collapse
I wouldn't worry about it. Wait a couple days see if the OTA drops like they're saying. IF it does, you'll be close to, if not stock.
However, the s-off will work with the .10 leak, too.
Thanks you two! I have to send it back in the next couple days so I couldn't wait to see IF we actually get the ICS ota. I got the .5 juopunutbear and ran that and after a few failed attempts at that wire trick I was able to finally achieve s-off! I then flashed the latest gb ruu in the bootloader which worked good and then used Scottys get back to s-on guide http://http://forum.xda-developers.com/showthread.php?t=1612937which worked flawlessly and now the bootloader says LOCKED and s-on with the proper hboot!!
Now since I got all that practice with s-off I'm going to get my new rezound s-off'd!:good:
Thanks again!!
Current: JBear, S-off, HBoot 2.21.2121, Radio 1.22.10.0310r, Running 3.14.605.12 71ORD.
I don't want to brick. What are the steps needed from this starting point to get to a global rom? Came from Moto phones where we didn't seem to have so many options. Will being JBear cause issues? Will I lose s-off?
cawaller said:
Current: JBear, S-off, HBoot 2.21.2121, Radio 1.22.10.0310r, Running 3.14.605.12 71ORD.
I don't want to brick. What are the steps needed from this starting point to get to a global rom? Came from Moto phones where we didn't seem to have so many options. Will being JBear cause issues? Will I lose s-off?
Click to expand...
Click to collapse
I was in your same state two days ago I just downloaded and ran the global ruu twice and everything went fine. Just make sure after you run the ruu twice before the first boot of the phone make a factory reset from within hboot
No you wont get s on after the global ruu. You stay s off but locked but all you have to do is flash the jbear hboot and you are unlocked and s off.
I'm on hboot 1.12. I've seen some talk about updating my hboot//firmware to the most recent version. it seems like a bit of a process. Can someone tell me the benefit of doing this? Also, if someone could explain how i can do this? thank you so much!
Im on Mean Rom 4.1
thank you
Most important question: are you S-OFF?
Sent from my Transformer using xda premium
Never update your hboot. Updating firmware is a good idea. Definitely get s-off if you haven't already.
Its not a "process" at all.... you just flash it either from recovery or from H-boot depending on if you are S-ON or S-OFF
And you want to update radio and firmware, no tthe Hboot
I think what you may be referring to is relocking and running the RUU to update your firmware. Sure that can be a bit involved, but if you're S-OFF updating firmware is really easy and you don't have to mess with any of that stuff. Like the others have said, since you're 1.12 you should go get S-OFF and then flash the firmware (minus the hboot).
Definitely get s-off, s-on unlocked is a guilded cage
Even if he is S-ON it doesnt matter. Hboot 1.12 can update through recovery
Yea but soff is better
I thought with 1.12 s-on you could only update the radio but the other firmware bits were off limits?
Sent from my EVO LTE
The security is different on 1.12, its practically non existent (compared to hboots 1.15 and 1.19) when you unlock but to have full write access to nand you need soff
Considering there's a tool out now to give you S-OFF with Hboot 1.19 (http://forum.xda-developers.com/showthread.php?t=1964309)
Is there any advantage to updating the Hboot?
If not i will just keep what i got since developers on here don't find it necessary to take the time to mention which hboot their rom is developed and tested with.
Neipas09 said:
Considering there's a tool out now to give you S-OFF with Hboot 1.19 (http://forum.xda-developers.com/showthread.php?t=1964309)
Is there any advantage to updating the Hboot?
If not i will just keep what i got since developers on here don't find it necessary to take the time to mention which hboot their rom is developed and tested with.
Click to expand...
Click to collapse
It doesn't matter what hboot you have, 1.12, 1.15, or 1.19. You can s-off all 3. There is no point in upgrading at all.
roids87 said:
It doesn't matter what hboot you have, 1.12, 1.15, or 1.19. You can s-off all 3. There is no point in upgrading at all.
Click to expand...
Click to collapse
you sure about that bro?
cause on my gf's evo 3d is sure as **** mattered what hboot is on her phone when i tried installing the Venom rom and it kept stalling and crashing because i didn't have the latest hboot on there.
Neipas09 said:
you sure about that bro?
cause on my gf's evo 3d is sure as **** mattered what hboot is on her phone when i tried installing the Venom rom and it kept stalling and crashing because i didn't have the latest hboot on there.
Click to expand...
Click to collapse
i doesn't matter what Hboot you have on the evo lte... with the 3d it was a little different because of the bootloader
HTC EVO LTE
It does not matter what hboot, I'm running outdated hboot and firmware and run viper, mean, stock w/goodies, cm10, pa just fine. The difference in hboot is 1.12 allows direct access to boot partition, 1.15 and 1.19 do not. It's not an issue now that you can either soff or downgrade and soff all current hboot software
I recently bought my new Evo 3D from eBay. As far as I can tell, it is in perfect shape. I was hoping to flash it to Page Plus and was dismayed when I realized how impossible the rooting process looked. I began with downgrading my 1.58 HBOOT to 1.40. Now I am attempting to flash the 1.13 RUU so I can finally move on in this process, but every time I attempt to flash it (or any other RUU), I get the error, "Error [131]: CUSTOMER ID ERROR." Now most fastboot commands do not work, and my phone bootloops with the stock ROM. Any idea how to fix it?
I used the juopunut bear wire trick for s-off so excuse me if I'm a little ignorant here with the downgrade method. Once you are down to hboot 1.40 (which sounds like you were successful with) can't you use the revolutionary s-off tool?
Once s-off you can easily run any ruu but I guess I don't understand why you need to downgrade even further to s-off, when revolutionary (I thought) works with hboot 1.40 and 1.30
Brian706 said:
I used the juopunut bear wire trick for s-off so excuse me if I'm a little ignorant here with the downgrade method. Once you are down to hboot 1.40 (which sounds like you were successful with) can't you use the revolutionary s-off tool?
Once s-off you can easily run any ruu but I guess I don't understand why you need to downgrade even further to s-off, when revolutionary (I thought) works with hboot 1.40 and 1.30
Click to expand...
Click to collapse
As I understand I can't use Revolutionary without booting into Android (since it needs ADB), which is currently impossible because of the bootloop.
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Macadamia Daze said:
As I understand I can't use Revolutionary without booting into Android (since it needs ADB), which is currently impossible because of the bootloop.
Click to expand...
Click to collapse
Oh, I see now!
Macadamia Daze said:
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Click to expand...
Click to collapse
So far, in every case I've seen, running the latest RUU has solved the bootloader unlock issue for people. I would run the 1.58 RUU and see if you can unlock the bootloader. Then go from there.
Or as I saw mentioned in the other thread, use the PG86IMG version of the RUU or extract it yourself from the exe. Flashing through the bootloader does not perform a cid check.
Brian706 said:
Oh, I see now!
So far, in every case I've seen, running the latest RUU has solved the bootloader unlock issue for people. I would run the 1.58 RUU and see if you can unlock the bootloader. Then go from there.
Or as I saw mentioned in the other thread, use the PG86IMG version of the RUU or extract it yourself from the exe. Flashing through the bootloader does not perform a cid check.
Click to expand...
Click to collapse
So far, I have yet to have any success despite flashing many RUUs. I took a break for quite a while, but decided I may try again. I am downloading now the 2.08 RUU, which one thread suggested.
Macadamia Daze said:
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Click to expand...
Click to collapse
If I remember correctly, the HTCDev unlock doesnt work for the earlier bootloaders. It says so on the very first page when its walking you through the steps. I could be wrong but you may wanna keep that in mind