I relocked my phone to update to the ICS firmware (fastboot oem lock), but I got an error in the terminal. INFOTZ_HTC_SVC_DISABLE ret = 134086000 (0x7FDFD70)
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
My phone rebooted to fastboot, and it says:
Relocked
Security Warning
S-On RL
I haven't rebooted, and I haven't booted into the bootloader to let the PH98IMG.zip flash.
Any advice on what to do next?
Edit--is the security warning normal? The error in the terminal scared the **** out of me, and coming from a Thunderbolt security warnings are bad news.
tekhna said:
I relocked my phone to update to the ICS firmware (fastboot oem lock), but I got an error in the terminal. INFOTZ_HTC_SVC_DISABLE ret = 134086000 (0x7FDFD70)
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
My phone rebooted to fastboot, and it says:
Relocked
Security Warning
S-On RL
I haven't rebooted, and I haven't booted into the bootloader to let the PH98IMG.zip flash.
Any advice on what to do next?
Edit--is the security warning normal? The error in the terminal scared the **** out of me, and coming from a Thunderbolt security warnings are bad news.
Click to expand...
Click to collapse
I saw this once too when flashing the OTA firmware over the original firmware via a PH98IMG.zip file. I just repeated the install process and it disappeared. Honestly, I don't think its a worry.
I'm like 80% positive I get this error message too when running that command.
andybones said:
I'm like 80% positive I get this error message too when running that command.
Click to expand...
Click to collapse
Cool, thanks guys. So just flash the zip and be on my way?
tekhna said:
Cool, thanks guys. So just flash the zip and be on my way?
Click to expand...
Click to collapse
yup, pretty much what I did. Mine's fine
a.mcdear said:
yup, pretty much what I did. Mine's fine
Click to expand...
Click to collapse
So uh.. my phone seems to have turned off while updating. It checked the package, was going through the update process, and now it just looks like it's shut off. I haven't touched it since it seems to have shut itself off.
Bricked?
Yeah that security warning comes up often and has meant nothing on every other phone I've seen or helped with.
Sent from my ADR6425LVW using xda premium
tekhna said:
So uh.. my phone seems to have turned off while updating. It checked the package, was going through the update process, and now it just looks like it's shut off. I haven't touched it since it seems to have shut itself off.
Bricked?
Click to expand...
Click to collapse
****, I seriously hope not!! I know for a fact I had the same security warning after re-locking to update firmware, and mine works just fine now. I would definitely power it back on, and hope to heaven that the hboot screen comes up ok...
What the hell is going on with my phone? The screen went totally black for a couple minutes during the update process, on its own it just rebooted to fastboot without me touching it, and now I have
Tampered
Relocked
Security Warning
What is going on? Reflash the package?
Edit--it seems to have at least updated Hboot, it's 2.21 now, not 2.11. Radios are .1118r and .12223r
tekhna said:
What the hell is going on with my phone? The screen went totally black for a couple minutes during the update process, on its own it just rebooted to fastboot without me touching it, and now I have
Tampered
Relocked
Security Warning
What is going on? Reflash the package?
Edit--it seems to have at least updated Hboot, it's 2.21 now, not 2.11.
Click to expand...
Click to collapse
OK, you had me scared I had you break your phone for a sec. Things are sounding better now.
On mine, going from 2.10 to 2.11, I got to that same point.. and then flashed the PH98IMG.zip file AGAIN, and security warning went away after the second time.
**edit**
looks like it updated Hboot, but not the radios. You're still on the GB OTA radios..
a.mcdear said:
OK, you had me scared I had you break your phone for a sec. Things are sounding better now.
On mine, going from 2.10 to 2.11, I got to that same point.. and then flashed the PH98IMG.zip file AGAIN, and security warning went away after the second time.
**edit**
looks like it updated Hboot, but not the radios. You're still on the GB OTA radios..
Click to expand...
Click to collapse
Yeah, things are sounding better, getting to fastboot is a darn good thing. It seems like the package didn't flash properly, but I'm afraid if I flash it again it's just going to fail again. I checked the md5, it checked out.
I'm no expert, but I've been doing this a while and I haven't seen my phone do anything like this before.
Edit-heh, nothing you did, would have been on me!
tekhna said:
Yeah, things are sounding better, getting to fastboot is a darn good thing. It seems like the package didn't flash properly, but I'm afraid if I flash it again it's just going to fail again. I checked the md5, it checked out.
I'm no expert, but I've been doing this a while and I haven't seen my phone do anything like this before.
Edit-heh, nothing you did, would have been on me!
Click to expand...
Click to collapse
No its been noted before that the leaked ICS build doesn't always install correctly the first time around and should be run a second time. Even if it does fail again, in exactly the same way, at least you know what to do about now...
a.mcdear said:
No its been noted before that the leaked ICS build doesn't always install correctly the first time around and should be run a second time. Even if it does fail again, in exactly the same way, at least you know what to do about now...
Click to expand...
Click to collapse
Trying again now... fingers crossed.
Edit: Crap, it keep unzipping and then updating and then updating and then unzipping system. Is that supposed to happen over and over again?
Edit 2: Phew, moved past system. I can't remember being this anxious even when I first rooted my very first phone! Gah.
Edit 3: ****. It shut down again. What the hell? I think it was towards the end of the update. My radios updated, but I have no idea if the whole package took or not. And I'm back in fastboot. Flash a third time?
tekhna said:
Trying again now... fingers crossed.
Edit: Crap, it keep unzipping and then updating and then updating and then unzipping system. Is that supposed to happen over and over again?
Click to expand...
Click to collapse
From what I remember reading after the most recent ICS leak came out was that the first time, basically only HBOOT got updated. When you run it again, it runs successfully and updates everything. It sounds to me like you're ok, but hopefully one of the people who actually ran the latest leak RUU will chime in with their experience.
It has ~10 items to update in the package. Let it sit and DO NOT touch it for the next 10-15mins.
Snuzzo said:
It has ~10 items to update in the package. Let it sit and DO NOT touch it for the next 10-15mins.
Click to expand...
Click to collapse
Yeah, I did. And then when I looked away it rebooted itself again. Dunno what to do. Is it possible it's a bad package despite the md5s checking out?
Edit--Tampered and security warnings are gone from fastboot.
Even 1 change in removing 1 of the updates will change the MD5. You are fine. All you have to do is run it twice and you're cooking.
EDIT:
Oh btw, that error you got. Perfectly normal.
Snuzzo said:
Even 1 change in removing 1 of the updates will change the MD5. You are fine. All you have to do is run it twice and you're cooking.
Click to expand...
Click to collapse
I ran it twice. It rebooted itself again during the second install.
tekhna said:
I ran it twice. It rebooted itself again during the second install.
Click to expand...
Click to collapse
Rebooted to hboot or normally to splash screen?
Snuzzo said:
Rebooted to hboot or normally to splash screen?
Click to expand...
Click to collapse
hboot
Related
So i was running MeanROM 3.4 and i'm on S-ON. I have decided that S-OFF for HBOOT 1.15 will probably never happen and i'm going to relock and run the RUU. Problem is that i relocked via fastboot oem lock and now the phone will not get past the bootloader screen so i can run the RUU. I was told that i didn't have to unroot, just relock and then run the RUU. I'm thinking i need to flash a stock ROM and that's why it won't boot? Does this seem right or is there something else i should be doing?
Thanks
Edit: Just realized i can't get into my recovery now. So whatever i need to do to fix this will have to be done via fastboot/ABD it appears.
Just run the RUU with the phone in bootloader
Rxpert said:
Just run the RUU with the phone in bootloader
Click to expand...
Click to collapse
Thought you had to boot the phone to do that? Now i feel like an idiot.
I'll try that, thanks!
CBRRider said:
Thought you had to boot the phone to do that? Now i feel like an idiot.
I'll try that, thanks!
Click to expand...
Click to collapse
Nope, first thing the RUU does is restart the phone into bootloader anyway
Rxpert said:
Nope, first thing the RUU does is restart the phone into bootloader anyway
Click to expand...
Click to collapse
Thanks so much. I didn't originally plan relocking and updating my phone but i downloaded WifiKill last night to try it out. But when i when to exit the app, my phone freaked out, restarted, every app seem to reset, and i kept getting constant force close errors on almost every app as well. Was able to run my backup pro and back up everything though. But since i figured i'm going to have to completely reset my phone, might as well update it since i really don't think S-OFF will come to HBOOT 1.15.
Oh well, Thanks again!
Next time something like that happens you should try fix permissions, anytime I've had apps suddenly misbehave like that fix permissions sets them straight
om4 said:
Next time something like that happens you should try fix permissions, anytime I've had apps suddenly misbehave like that fix permissions sets them straight
Click to expand...
Click to collapse
I completely forgot about that feature. Damn...oh well.
Sent from my EVO using xda premium
I rooted using this method: http://forum.xda-developers.com/showthread.php?p=36976137#post36976137 (I think it's referred to as CID 222222, though I think when I did it the first time it was 111111). I locked it, updated to 2.04.605.2, then was able to reroot it using the same method.
I want to get the OTA to 2.06 because I keep getting the PUK lock and no SIM found errors and the update popup is really starting to get annoying with how much it pops up.
I think I can get root and s-off using moonbeam if I upgrade to 2.06, but I'm not sure how to get it to that point.
andyd273 said:
I rooted using this method: http://forum.xda-developers.com/showthread.php?p=36976137#post36976137 (I think it's referred to as CID 222222, though I think when I did it the first time it was 111111). I locked it, updated to 2.04.605.2, then was able to reroot it using the same method.
I want to get the OTA to 2.06 because I keep getting the PUK lock and no SIM found errors and the update popup is really starting to get annoying with how much it pops up.
I think I can get root and s-off using moonbeam if I upgrade to 2.06, but I'm not sure how to get it to that point.
Click to expand...
Click to collapse
I'm on a custom rom right now, so I don't remember exactly. But it should be under Settings>About Phone> and somewhere in there there should be the option to "check for software update."
kxs783kms said:
I'm on a custom rom right now, so I don't remember exactly. But it should be under Settings>About Phone> and somewhere in there there should be the option to "check for software update."
Click to expand...
Click to collapse
Unfortunately because it's rooted it fails to update that way. Last time I think I had to restore a factory Rom or ruu or something then do the update and then restore from backup, but I'm not sure which room to use this time, or if there is a better way now.
andyd273 said:
Unfortunately because it's rooted it fails to update that way. Last time I think I had to restore a factory Rom or ruu or something then do the update and then restore from backup, but I'm not sure which room to use this time, or if there is a better way now.
Click to expand...
Click to collapse
I think you're going to have to RUU the 1.15 stock rom with directions from here
http://forum.xda-developers.com/showthread.php?t=2017525 and just let it accept all of the the updates up to the 2.06 update before you root it. That way you'll have the stock recovery, so you should definitely be able to accept the OTA's. There might be an easier, quicker way, but I couldn't find one.
kxs783kms said:
I think you're going to have to RUU the 1.15 stock rom with directions from here
http://forum.xda-developers.com/showthread.php?t=2017525 and just let it accept all of the the updates up to the 2.06 update before you root it. That way you'll have the stock recovery, so you should definitely be able to accept the OTA's. There might be an easier, quicker way, but I couldn't find one.
Click to expand...
Click to collapse
All right, that's fine at least.
So, once I take it down to 1.15, then back up to 2.06, I can do the moonbeam method to root and s-off instead of CID 222222, right?
Also, is there a better way to handle updates, so I don't have to keep going down to 1.15?
Thanks for the help.
I used the Revone method to root 2.06. I never used that one you mentioned because when I bought my DNA 2 weeks ago, it was on 2.06 and Revone and Moonshine were the only options I saw that worked for 2.06. It's in the development section.
Sent from my HTC6435LVW using Tapatalk 4
Check the moonshine thread op it has how to update to 2.06
Sent from my HTC6435LVW using XDA Premium HD app
.torrented said:
Check the moonshine thread op it has how to update to 2.06
Click to expand...
Click to collapse
Sorry, I read that whole thread and didn't see it. I see where he says to search the forum, but the only one I have seen is the one kxs783kms suggested: http://forum.xda-developers.com/showthread.php?t=2017525
I'm currently trying that one, but the RUU part failed the first time I tried... will try it again.
andyd273 said:
Sorry, I read that whole thread and didn't see it. I see where he says to search the forum, but the only one I have seen is the one kxs783kms suggested: http://forum.xda-developers.com/showthread.php?t=2017525
I'm currently trying that one, but the RUU part failed the first time I tried... will try it again.
Click to expand...
Click to collapse
Here you go. http://forum.xda-developers.com/showthread.php?t=2314771&nocache=1 Scroll down in the first post and it will tell you how to upgrade it to 2.06.
kxs783kms said:
Here you go. http://forum.xda-developers.com/showthread.php?t=2314771&nocache=1 Scroll down in the first post and it will tell you how to upgrade it to 2.06.
Click to expand...
Click to collapse
Gaa. I think I may have messed something up.
Phone is stuck on white HTC start screen. no other messages.
I started to do the downgrade to 1.15, it didn't work, but it did wipe everything out.
So then I saw how to just do the upgrade to 2.06, so I figured I would first do a restore through clockwork mod.
It got part way, and something happened, and when I looked at it next the white screen was up.
I can restart it by holding down the power button, but then it starts back up again.
Any way to save it?
Edit: ok, was able to get into fastboot/bootloader
Figuring out where to go from here...
andyd273 said:
Gaa. I think I may have messed something up.
Phone is stuck on white HTC start screen. no other messages.
I started to do the downgrade to 1.15, it didn't work, but it did wipe everything out.
So then I saw how to just do the upgrade to 2.06, so I figured I would first do a restore through clockwork mod.
It got part way, and something happened, and when I looked at it next the white screen was up.
I can restart it by holding down the power button, but then it starts back up again.
Any way to save it?
Edit: ok, was able to get into fastboot/bootloader
Figuring out where to go from here...
Click to expand...
Click to collapse
Need a little more info, are you unlocked? s-off'd? rooted? custom recovery? I mean what are these set to currently btw, not what you have done in the past.
jake.corey.jacobs said:
Need a little more info, are you unlocked? s-off'd? rooted? custom recovery?
Click to expand...
Click to collapse
I might have figured it out...
unlocked, rooted, not s-off'd, CWM recovery.
I had a NANDROID backup, but it wasn't letting me restore from it, said it couldn't restore system.
Thats when it failed out.
I did some reading and figured out that I needed to hold down the down volume button when the screen flickered black for a half second and that got me back into fastboot.
Back in CWM I factory reset, wiped the cache and davlik cache, formatted system, and tried restore and so far it looks like it's working. It was able to restore system, and is currently restoring data.
So hopefully I'm on my way back, though it was a scary couple minutes there.
I'm a noob, but slowly learning
andyd273 said:
I might have figured it out...
unlocked, rooted, not s-off'd, CWM recovery.
I had a NANDROID backup, but it wasn't letting me restore from it, said it couldn't restore system.
Thats when it failed out.
I did some reading and figured out that I needed to hold down the down volume button when the screen flickered black for a half second and that got me back into fastboot.
Back in CWM I factory reset, wiped the cache and davlik cache, formatted system, and tried restore and so far it looks like it's working. It was able to restore system, and is currently restoring data.
So hopefully I'm on my way back, though it was a scary couple minutes there.
I'm a noob, but slowly learning
Click to expand...
Click to collapse
Trust me you keep around these parts and you will learn a lot from just reading random threads. Glad you got it back working so far, let us know how it turns out sir.
jake.corey.jacobs said:
Trust me you keep around these parts and you will learn a lot from just reading random threads. Glad you got it back working so far, let us know how it turns out sir.
Click to expand...
Click to collapse
Will do.
I don't like that Verizon makes it so hard to do this stuff, locking things down, but I do feel some satisfaction when I am able to make it work despite them.
andyd273 said:
Will do.
I don't like that Verizon makes it so hard to do this stuff, locking things down, but I do feel some satisfaction when I am able to make it work despite them.
Click to expand...
Click to collapse
Yeah vzw is horrible on a lot of fronts, but I like my consistent bill every month, something I never had on att. My bill would be anywhere from 120-300 dollars for no reason, as I had 2 grandfathered unlimited plans. my bill should of been around 150 dollars, and never was.
jake.corey.jacobs said:
Yeah vzw is horrible on a lot of fronts, but I like my consistent bill every month, something I never had on att. My bill would be anywhere from 120-300 dollars for no reason, as I had 2 grandfathered unlimited plans. my bill should of been around 150 dollars, and never was.
Click to expand...
Click to collapse
Ok, restore worked successfully!
Trying to flash 2.06 firmware, but it's not working quite right:
C:\DeveloperAndroid\android-sdk-windows\platform-tools>adb reboot bootloader
C:\DeveloperAndroid\android-sdk-windows\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.045s]
finished. total time: 0.047s
C:\DeveloperAndroid\android-sdk-windows\platform-tools>fastboot flash zip dna2.06firmware.zip
sending 'zip' (33119 KB)...
OKAY [ 2.616s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.688s
Click to expand...
Click to collapse
I Am hopefully missing something really simple?
A few days ago I flashed Zarboz's 4.2.2 kernel over NOS 3.0.6 and found trickstermod would crash on launch or crash the entire phone. A complete wipe of system and internal fixed that.
With all the current issues I forgot why I wiped again but after flashing NOS the phone stays on the slash screen.
At this point I figure a ruu is needed. I relocked, an trying to use the utility but it stops after I click "update" no warnings or messages out just goes away.
I'm pretty sure it's dead but am looking for help before headed to Verizon for a new device.
Thanks.
Trying flashing the nos kernel separately
Phaded said:
Trying flashing the nos kernel separately
Click to expand...
Click to collapse
Thanks. I'm going to have to. I'm stuck S-On with HTVDEV not accepting a SuperCID.
Phaded said:
Trying flashing the nos kernel separately
Click to expand...
Click to collapse
No go. I'm stuck at the initial splash screen not the bootanimation.
fr4nk1yn said:
No go. I'm stuck at the initial splash screen not the bootanimation.
Click to expand...
Click to collapse
Are you able to get into fastboot or recovery while holding down the volume buttons?
durgis said:
Are you able to get into fastboot or recovery while holding down the volume buttons?
Click to expand...
Click to collapse
Yes, both.
What's really odd is when I run the fastboost Command to get the unlock code it's different Evey time. None of which htcdev will accept. I am supercid.
fr4nk1yn said:
Yes, both.
What's really odd is when I run the fastboost Command to get the unlock code it's different Evey time. None of which htcdev will accept. I am supercid.
Click to expand...
Click to collapse
Usually only your original code will work. Do you have the email still?
Phaded said:
Usually only your original code will work. Do you have the email still?
Click to expand...
Click to collapse
I fixed that by superciding with 2s, got the code after that. I'm trying to get rid of the custom splash screen but am getting a failed: remote not allowed error. The eng Hboot won't go away either. from what I'm reading it all needs to be changed to RUU(?).
Looked at the LG G2 and it "did nothing for me" so I'm back to trying to get this fixed. Feels like some progress although not really in actuality.
-Edit: I'm still unlocked S-Off trying to flash.
-Edit2: I thought 1.33 was the eng Hboot. DOH!
fr4nk1yn said:
I fixed that by superciding with 2s, got the code after that. I'm trying to get rid of the custom splash screen but am getting a failed: remote not allowed error. The eng Hboot won't go away either. from what I'm reading it all needs to be changed to RUU(?).
Looked at the LG G2 and it "did nothing for me" so I'm back to trying to get this fixed. Feels like some progress although not really in actuality.
-Edit: I'm still unlocked S-Off trying to flash.
Click to expand...
Click to collapse
You have a custom splash screen installed?
Phaded said:
You have a custom splash screen installed?
Click to expand...
Click to collapse
I did. It's now stock splash screen, 1.33.001 HBOOT, *** RELOCKED ***, I even flashed the 2.06 OTA so recovery is stock.
The RUU still disappears after clicking "Update", I'm DL'ing from a different source. I can only figure there's a problem with it.
-Edit: And that was it! Update is going.
Yea it shouldn't just disappear...
After clicking update, do ctrl+atl+ delete
Is the ruu still a running process? If so, give it some time... It might just be "loading"
If you need a new source still tomorrow I'll host it on my Dropbox
Phaded said:
Yea it shouldn't just disappear...
After clicking update, do ctrl+atl+ delete
Is the ruu still a running process? If so, give it some time... It might just be "loading"
If you need a new source still tomorrow I'll host it on my Dropbox
Click to expand...
Click to collapse
It was closing. I let it run while taking a nap earlier.
But now I have the 158 image error! Motherpussbucket!
fr4nk1yn said:
It was closing. I let it run while taking a nap earlier.
But now I have the 158 image error! Motherpussbucket!
Click to expand...
Click to collapse
That is usually hboot related. Flash stock hboot from my rts thread
Phaded said:
That is usually hboot related. Flash stock hboot from my rts thread
Click to expand...
Click to collapse
Thanks the 2.06 for messed me up. I thought supercid allowed downgrading. It apparently does not.
So much for that. I now have a 152 update error!
I'm back to thinking the hardware is messed up. That would explain my weird kernel problem.
TWO bad downloads! Before I gave up, which I was close I decided to download from the Hotfile link.
It too hours but... I'm now booted! MD5s probably would've saved me some time.
@Phaded I extracted the rom.zip just in case. I'm going to upload it later if you want to link to it.
flashing it through fastboot would probably be easier and it shows errors unlike the RUU updater.
Thanks for the help.
I have a question...
The RUU... Were you flashing it? Or running it on the computer? I only ask because of your attached pic.
Anyways, RUU.exe usually shows errors. I wonder if the one link is bad... I'll download from it tonight and run it on my throw away DNA...
Phaded said:
I have a question...
The RUU... Were you flashing it? Or running it on the computer? I only ask because of your attached pic.
Anyways, RUU.exe usually shows errors. I wonder if the one link is bad... I'll download from it tonight and run it on my throw away DNA...
Click to expand...
Click to collapse
I did everything possible is every combination.
While flashing after in "recovery", (black screen, HTC, and 4 exclamation points), I founda thread saying to try flashingthe rom.zip, so I did that too.
The photo is after unplugging the phone on that screen. It showed the error.
The HTC RUU shows the error afterwards but not that it was having a problem with /system.
Flashing through fastboot showed the error in realtime. Besides it skips that dreaded programand could be done in Linux or Mac
This is Odd...
I appear to be soft bricked again after flashing NOS and Zarboz kernel.
Going to try CM.
fr4nk1yn said:
I did everything possible is every combination.
While flashing after in "recovery", (black screen, HTC, and 4 exclamation points), I founda thread saying to try flashingthe rom.zip, so I did that too.
The photo is after unplugging the phone on that screen. It showed the error.
The HTC RUU shows the error afterwards but not that it was having a problem with /system.
Flashing through fastboot showed the error in realtime. Besides it skips that dreaded programand could be done in Linux or Mac
Click to expand...
Click to collapse
Could always do fastboot oem rebootRUU and then fastboot flash zip ruu.zip instead of running the .exe
Sent from my HTC6435LVW using XDA Premium 4 mobile app
times_infinity said:
Could always do fastboot oem rebootRUU and then fastboot flash zip ruu.zip instead of running the .exe
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did that again tonight. It's much quicker and easier than the exe.
I flashed the wrong splash image and it still took. I'm interested in if it runs any checks at all. That would be aewsome for restoring to stock.
Side note: my phone will boot CM-20130913, but not 20130914. this is so weird I checked my computers' memory with MemTest.
I recently bought a replacement Rezound, which has Hboot 2.25/Radios 1.22.10 0421r &0424r. I have unlocked the bootloader and installed TWERP 2.6.3.0 and Infection 2.9.1. I am sure I should have thought of this before installing Infection, but my battery life is worse than my original phone and it runs hot. No reboots or other problems.
I have searched for instructions and recommendations for upgrading Hboot, but haven't found anything clear enough to overcome my nervousness about this process. I have one bricked phone on the desk in front of me and I don't want another. I will be grateful to anyone who can recommend what Hboot to flash (I'm thinking 2.27 or 2.28?) and guide me through the process.
Thanks,
geronimo48 said:
I recently bought a replacement Rezound, which has Hboot 2.25/Radios 1.22.10 0421r &0424r. I have unlocked the bootloader and installed TWERP 2.6.3.0 and Infection 2.9.1. I am sure I should have thought of this before installing Infection, but my battery life is worse than my original phone and it runs hot. No reboots or other problems.
I have searched for instructions and recommendations for upgrading Hboot, but haven't found anything clear enough to overcome my nervousness about this process. I have one bricked phone on the desk in front of me and I don't want another. I will be grateful to anyone who can recommend what Hboot to flash (I'm thinking 2.27 or 2.28?) and guide me through the process.
Thanks,
Click to expand...
Click to collapse
look at my downgrade/upgrade guide here in the rezound q&a.....the 3 ph98img ota files are the updates you want
REV3NT3CH said:
look at my downgrade/upgrade guide here in the rezound q&a.....the 3 ph98img ota files are the updates you want
Click to expand...
Click to collapse
Your initial comment, "For this you MUST BE S-OFF FOR DOWNGRADING with a relocked bootloader and make sure you are not on a custom or hex edited hboot or you can brick your device." stopped me. My phone is S-on and Hboot is unlocked. Do I have to be S-off and unlocked to flash the three OTAs?
geronimo48 said:
Your initial comment, "For this you MUST BE S-OFF FOR DOWNGRADING with a relocked bootloader and make sure you are not on a custom or hex edited hboot or you can brick your device." stopped me. My phone is S-on and Hboot is unlocked. Do I have to be S-off and unlocked to flash the three OTAs?
Click to expand...
Click to collapse
yes thats for downgrading with the ruu.exe's not for updating...to update just follow the OTA part with the ph98img.zips
REV3NT3CH said:
yes thats for downgrading with the ruu.exe's not for updating...to update just follow the OTA part with the ph98img.zips
Click to expand...
Click to collapse
I downloaded all three files and checked md5 - all checked out. I then put the 1st file on the root directory of my ex sd card, renamed it PH98IMG.zip and rebooted into the unlocked bootloader. Bootloader recognized the zip, the progress bar appeared and the file transferred. Then the progress bar disappeared and nothing else happened. There was no instruction to press Volume up. I repeated everything and got the same result. I can still boot into TWERP and my phone still starts up with Infection 2.9.1.
Let me say at this point, THANK GOD NOTHING BAD HAPPENED!
Any suggestions?
geronimo48 said:
I downloaded all three files and checked md5 - all checked out. I then put the 1st file on the root directory of my ex sd card, renamed it PH98IMG.zip and rebooted into the unlocked bootloader. Bootloader recognized the zip, the progress bar appeared and the file transferred. Then the progress bar disappeared and nothing else happened. There was no instruction to press Volume up. I repeated everything and got the same result. I can still boot into TWERP and my phone still starts up with Infection 2.9.1.
Let me say at this point, THANK GOD NOTHING BAD HAPPENED!
Any suggestions?
Click to expand...
Click to collapse
hmmm for s and g's relock the bootloader....are you absolutely sure you are on 2.25...the first ph98img is hboot 2.27 with the firmware....also just rename it to just PH98IMG if you type the zip with it the phone will read it as PH98IMG.zip.zip and wont work
REV3NT3CH said:
hmmm for s and g's relock the bootloader....are you absolutely sure you are on 2.25...the first ph98img is hboot 2.27 with the firmware....also just rename it to just PH98IMG if you type the zip with it the phone will read it as PH98IMG.zip.zip and wont work
Click to expand...
Click to collapse
I am looking at my Hboot screen. It says:
VIGOR PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012, 16:47:46
I transferred the 1st file to my SD card and deleted "this 1st " from the name. I watched it reading in Hboot and saw "PH98IMG.ZIP".
I'll try relocking the bootloader.
Thanks.
EDIT - Looks like the bootloader needs to be locked. The first file is finished, starting on the second.
EDIT 2 - OK. I can't get the 2nd file to flash with the bootloader locked or unlocked.
BUT, I now have:
HBOOT-2.27.000
RADIO-2.22.20.0801r/2.22.10.0803r
geronimo48 said:
I am looking at my Hboot screen. It says:
VIGOR PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012, 16:47:46
I transferred the 1st file to my SD card and deleted "this 1st " from the name. I watched it reading in Hboot and saw "PH98IMG.ZIP".
I'll try relocking the bootloader.
Thanks.
EDIT - Looks like the bootloader needs to be locked. The first file is finished, starting on the second.
Click to expand...
Click to collapse
ah thanks for the info bud much appreciated....glad relocking it worked for you
REV3NT3CH said:
ah thanks for the info bud much appreciated....glad relocking it worked for you
Click to expand...
Click to collapse
Please see EDIT 2. I can't flash the 2nd file with the bootloader locked or unlocked.
I can boot into Hboot, but when I try to open Recovery I first get the green arrows (circle and down), then I get the red triangle with exclamation mark. When I booted the phone I got the setup wizard and a notice that my phone was just activated. Of course it was already activated. I suppose this just means everything has been wiped and I'm starting fresh with the firmware from the 1st downloaded zip. I didn't go through setup.
Any ideas?
geronimo48 said:
Please see EDIT 2. I can't flash the 2nd file with the bootloader locked or unlocked.
I can boot into Hboot, but when I try to open Recovery I first get the green arrows (circle and down), then I get the red triangle with exclamation mark. When I booted the phone I got the setup wizard and a notice that my phone was just activated. Of course it was already activated. I suppose this just means everything has been wiped and I'm starting fresh with the firmware from the 1st downloaded zip. I didn't go through setup.
Any ideas?
Click to expand...
Click to collapse
yes....after 1st ota phone is suppose to activate through verizon
REV3NT3CH said:
yes....after 1st ota phone is suppose to activate through verizon
Click to expand...
Click to collapse
Any ideas on how to install the other two OTAs?
geronimo48 said:
Any ideas on how to install the other two OTAs?
Click to expand...
Click to collapse
all 3 install through bootloader....must have a relocked bootloader...the other 2 ph98img.zip's are not firmware or rom....just radios, hboot, and required system files for them
REV3NT3CH said:
all 3 install through bootloader....must have a relocked bootloader...the other 2 ph98img.zip's are not firmware or rom....just radios, hboot, and required system files for them
Click to expand...
Click to collapse
I noticed they were smaller. I installed the 1st OTA with the bootloader relocked. The 2nd OTA wouldn't complete installation locked or unlocked. I reflashed the first OTA just to make sure and the process worked flawlessly. The 2nd OTA acts like it is loading, but I don't get the notice to press Vol Up.
If you think of a way that might work to get the other OTAs installed, let me know.
Thanks again for all your help.
geronimo48 said:
I noticed they were smaller. I installed the 1st OTA with the bootloader relocked. The 2nd OTA wouldn't complete installation locked or unlocked. I reflashed the first OTA just to make sure and the process worked flawlessly. The 2nd OTA acts like it is loading, but I don't get the notice to press Vol Up.
If you think of a way that might work to get the other OTAs installed, let me know.
Thanks again for all your help.
Click to expand...
Click to collapse
Same issue here thanks for addressing it.
drhile said:
Same issue here thanks for addressing it.
Click to expand...
Click to collapse
hmm strange....works for some doesnt for others...i know flyhalf posted a method of this somewhere for s-on users...required extra step i think
geronimo48 said:
Any ideas on how to install the other two OTAs?
Click to expand...
Click to collapse
I guess you haven't thought of anything.
I am thinking of having another go at installing all three OTAs. I have installed CWM and TACHYON. I don't have FCs or bootloops, but my battery life is poor, the camera doesn't work and the phone runs hot (>110). I have tried SetCPU with limited success.
You and others have stated that outdated HBOOT/radios can cause overheating, so I want to try.
Question: Do I need to do a factory reset and start over with the 1st OTA?
Thanks again for all of your help.
geronimo48 said:
I guess you haven't thought of anything.
I am thinking of having another go at installing all three OTAs. I have installed CWM and TACHYON. I don't have FCs or bootloops, but my battery life is poor, the camera doesn't work and the phone runs hot (>110). I have tried SetCPU with limited success.
You and others have stated that outdated HBOOT/radios can cause overheating, so I want to try.
Question: Do I need to do a factory reset and start over with the 1st OTA?
Thanks again for all of your help.
Click to expand...
Click to collapse
If you're at hboot 2.27, that's not your problem, you have other issues, being you're s-on, how did you flash the kernel for Tachyon?
geronimo48 said:
I guess you haven't thought of anything.
I am thinking of having another go at installing all three OTAs. I have installed CWM and TACHYON. I don't have FCs or bootloops, but my battery life is poor, the camera doesn't work and the phone runs hot (>110). I have tried SetCPU with limited success.
You and others have stated that outdated HBOOT/radios can cause overheating, so I want to try.
Question: Do I need to do a factory reset and start over with the 1st OTA?
Thanks again for all of your help.
Click to expand...
Click to collapse
as stated there is a method with the last two foe s-on users...having to use fastboot i believe
REV3NT3CH said:
as stated there is a method with the last two foe s-on users...having to use fastboot i believe
Click to expand...
Click to collapse
Thanks. I'll post if I figure it out.
geronimo48 said:
Thanks. I'll post if I figure it out.
Click to expand...
Click to collapse
according to flyhalf as the this 3rd was uploaded by him you just need a relocked bootloader for s-on....im s-off though but can guarantee links work as i just used them...but in all seriouness if your not really using stock i highly suggest gaining s-off as it will make life easier....plus it has less of a chance on fully and permanently bricking your rez...with s-on there isnt really much you can do in a brick
moonshine doesn't like xposed
fastboot oem lock
device modified
s-on
relocked
security warning
used 0PJAIMG.zip on sd card cuz ruu failed, and fastboot flash unlock token gave "no such partition" (or something) and flashing the clean system.emmc.win gave same error
it did it's thing with flashing opjaimg.zip and when finished it said press power button to complete and it now wont come back on.
plugged into charger i get no led
effen fantastic
i want my m7 back...........
moonshine was for the M7. They have no m9 varient. why would you do that?
94tbird said:
moonshine was for the M7. They have no m9 varient. why would you do that?
Click to expand...
Click to collapse
i ment sunshine. i was tired. the apk ran fine before i had exposed, got paid yesterday and was going to drop the $25 for s-off.
and all i did was relock bootloader and run ruu from sd card and it broke device
ahh ok makes more sense now, sorry.
jpwhre said:
i ment sunshine. i was tired. the apk ran fine before i had exposed, got paid yesterday and was going to drop the $25 for s-off.
and all i did was relock bootloader and run ruu from sd card and it broke device
Click to expand...
Click to collapse
was it the original .17 ruu zip?
Unlock your bootloader again by running the unlock file in download mode. *I had to do this twice, as it failed the first time after relocking*
Flash back to stock rooted.
Run RUU
I locked my bootloader thinking I would need to when running the RUU. Turned out that I couldn't do anything without unlocking again. I thought I was stuck too, but then the unlocked worked (luckily)
He said he couldn't power up. But I suspect he can.
Hold Vol Up & Down and Power all at once for a while.
mswlogo said:
He said he couldn't power up. But I suspect he can.
Hold Vol Up & Down and Power all at once for a while.
Click to expand...
Click to collapse
same thing happened to me when i was on .30 and accidentally flashed the .17 RUU... its bricked, sorry :/ it wont even power on. Mine didnt I just took it back to sprint and told them it was DOA when i got it.. they wont be able to power it on either so just take it back to them and play dumb. They will get you a new one.
OMJ said:
was it the original .17 ruu zip?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95916177934554226
Harfainx said:
Unlock your bootloader again by running the unlock file in download mode. *I had to do this twice, as it failed the first time after relocking*
Flash back to stock rooted.
Run RUU
I locked my bootloader thinking I would need to when running the RUU. Turned out that I couldn't do anything without unlocking again. I thought I was stuck too, but then the unlocked worked (luckily)
Click to expand...
Click to collapse
Nope
mswlogo said:
He said he couldn't power up. But I suspect he can.
Hold Vol Up & Down and Power all at once for a while.
Click to expand...
Click to collapse
My fingers hurt
deakelem said:
same thing happened to me when i was on .30 and accidentally flashed the .17 RUU... its bricked, sorry :/ it wont even power on. Mine didnt I just took it back to sprint and told them it was DOA when i got it.. they wont be able to power it on either so just take it back to them and play dumb. They will get you a new one.
Click to expand...
Click to collapse
My girlfriend told me to do the same thing, after looking at me and asking what i did (and tells me to quit doing this sh!t, again)
When I fastboot oem lock, it rebooted into bootloader (not download) and gave me security warning and refuse to reboot to system.
I tried to flash unlock token back and it kept giving me errors of partition doesn't exist. Ran RUU and it put device into fastboot oem rebootRUU mode and then sat for 5 minutes waiting on bootloader. So i put above zip on sd and flashed in download mode. Finished successfully and then gave option to reboot, and it never came back on.
14 days to the day today. No questions asked, they just exchanged it.
Girlfriend asked me the dumbest question afterwords.. "You going to eff with this one too?" of course i am, duh
jpwhre said:
14 days to the day today. No questions asked, they just exchanged it.
Girlfriend asked me the dumbest question afterwords.. "You going to eff with this one too?" of course i am, duh
Click to expand...
Click to collapse
Boy, are you in the dog house lol
Congrats on getting a new one. Think twice, flash once.
I'm always Leary of EVER going backwards on firmware.
mswlogo said:
Boy, are you in the dog house lol
Congrats on getting a new one. Think twice, flash once.
I'm always Leary of EVER going backwards on firmware.
Click to expand...
Click to collapse
Well we've been together for 4.5 years and i've been doing this crap since 2007 so there is no way she'll get me to stop.
I didn't go backwards. I was on bone stock rooted .30 with xposed, and instead of going the the bizzilian files in recovery to delete, rename and uninstall the hard way, i figured oem lock and flashing stock sprint .30 and rooting again would be easier.
Found culprit though. Just settling down from school and store run, time to start over with new phone and do s-off before i do anything else, low and behold the usb port on laptop is failing. I keep all files/tools on 2 tb external hard drive connected to 3.0 port. One 2.0 usb port i knew failed last year, only left with 1 and it died. couldn't get phone to reboot with adb, or get adb to find device. Getting unlock token froze half way thru.
Copying fold to desktop to plug phone into 3.0 and go from there.
Thank you, thank you!
mswlogo said:
He said he couldn't power up. But I suspect he can.
Hold Vol Up & Down and Power all at once for a while.
Click to expand...
Click to collapse
I had bricked my phone for a couple of days before finding this little nugget of gold. So pleased to find that everything was as I had left it and no need to format. I'll NEVER format an SD card as internal again.
So very grateful that you posted this. :victory: