So I decided I would finally S-Off my device today, having been too busy recently due to school and life. I got past the point where you do the wire trick and I thought all was going well, but then it said something along the lines of Error: Still Sober. I exited ControlBear and figured I would just try again. At first, it was stuck at the black Juopunutbear screen, and after trying to turn it off via the power button, I decided to pull the battery and turn it back on. When I did this, it just booted up into the bootloader. I searched the forum and found it was possible to attempt it from the bootloader, so I did. It appeared to be working fine, but then my phone rebooted, and ControlBear just said "Connecting to device..." for a while, then said "Connect device and install drivers." Now, my phone only boots into bootloader, my laptop doesn't recognize that it's plugged in (though it will say fastboot USB on the phone), and ControlBear just tells me to "Connect device and install drivers." I don't know where to go from here. Help? Has anyone else had this issue?
Never mind that problem! I rebooted my computer, then it detected my phone just fine. I got the wire trick this time, but now I'm stuck at a point where it keeps rebooting my phone into amonra and ControlBear doesn't detect it?
and again...nevermind! simply powered down, then powered back up, and all was well. What's weird, though, is that it didn't wipe my SD card....all the information is still on it. I would think something went wrong, but when I go to my bootloader, it says S-Off...oh well! Not about to complain about a functional SD card!
Sorry, just read your posts. I experienced each of the same problems along the way But with trying and trying, finally got it. Congrats and welcome to the s-off club!
pmterp said:
Sorry, just read your posts. I experienced each of the same problems along the way But with trying and trying, finally got it. Congrats and welcome to the s-off club!
Click to expand...
Click to collapse
Yeah, I was a little freaked out at first. But I figured, it still does something, so at least I'm not bricked! haha. Thanks! It's good to be part of the club!
i to am stuck in the bootloader. i f-ed my phone up so i decided to relock and run the ruu and that failed.now it says relocked security warning none of my computers see my rezound, adb wont see it ether. i have tried a lot of stuff but no go.
anyone have any advice?
neckbonest said:
i to am stuck in the bootloader. i f-ed my phone up so i decided to relock and run the ruu and that failed.now it says relocked security warning none of my computers see my rezound, adb wont see it ether. i have tried a lot of stuff but no go.
anyone have any advice?
Click to expand...
Click to collapse
When you say it failed. What was the nature of the failure? What did the screen say?
Did you rename the RUU to PH98IMG? Hopefully you have a card reader. Take the SD card out and make sure the RUU is renamed properly. Put it back into your phone and reboot. When the phone goes into HBOOT does it look for and find the card? It should find the PH98IMG file for you to flash. Its been said that you should flash this twice.
topgun1953 said:
When you say it failed. What was the nature of the failure? What did the screen say?
Did you rename the RUU to PH98IMG? Hopefully you have a card reader. Take the SD card out and make sure the RUU is renamed properly. Put it back into your phone and reboot. When the phone goes into HBOOT does it look for and find the card? It should find the PH98IMG file for you to flash. Its been said that you should flash this twice.
Click to expand...
Click to collapse
i did rename it to ph98img and it found it but said checking ph98img and then nothing. i got it up and going anyway. i used the all in one toolkit and started from the beginning and did everything and it worked
Related
I managed to get s-off, but my phone would not boot. I was stuck on a screen that said "JuopunutBear" with an arrow. I did the internal storage fix, now the phone is really screwed. I'm stuck on a white screen with "HTC". I can't boot to recovery and the PC won't recognize phone so ADB commands don't work. Any help would be appreciated.
lithium630 said:
I managed to get s-off, but my phone would not boot. I was stuck on a screen that said "JuopunutBear" with an arrow. I did the internal storage fix, now the phone is really screwed. I'm stuck on a white screen with "HTC". I can't boot to recovery and the PC won't recognize phone so ADB commands don't work. Any help would be appreciated.
Click to expand...
Click to collapse
Get one of the old GB RUU's and run it on your phone. Start again. If your phone was truly bricked, it wouldn't power on and you wouldn't get an LED light when it was plugged in.
lithium630 said:
I managed to get s-off, but my phone would not boot. I was stuck on a screen that said "JuopunutBear" with an arrow. I did the internal storage fix, now the phone is really screwed. I'm stuck on a white screen with "HTC". I can't boot to recovery and the PC won't recognize phone so ADB commands don't work. Any help would be appreciated.
Click to expand...
Click to collapse
This is an easy one, or would have been when you were on the black screen. Well the internal storage fix scares me, but hopefully that wont matter. Typically all you need to do is get the PH file from your rom and place on sd card, boot into hboot, and run the update I believe, then reboot.
This title needs to be edited as it's misleading.
lithium630 said:
I managed to get s-off, but my phone would not boot. I was stuck on a screen that said "JuopunutBear" with an arrow. I did the internal storage fix, now the phone is really screwed. I'm stuck on a white screen with "HTC". I can't boot to recovery and the PC won't recognize phone so ADB commands don't work. Any help would be appreciated.
Click to expand...
Click to collapse
Relax. The S-off process blows out your recovery. You didn't brick your phone.
Put a recovery image on your SD card, go into hboot (from a powered down state, power button and volume down) and let 'er reload recovery. If you can't get the file on your SD card through your phone, pop the SD card into a card reader attached to your PC and stick it on there that way.
Once that's done, remove the image file from your SD card, put your fav ROM on it, and install it from recovery.
You may need to fix your SD card's mount points. Within the thread on S-off, there's a link to the process.
None of the commands work because the phone is not recognized. I cannot boot to hboot. Uh oh.
I had the same screen. Pull the battery and reboot into hboot, volume down+power and run the s-off program again. Something didn't finish and it will pick up where it left off in my experience.
lithium630 said:
None of the commands work because the phone is not recognized. I cannot boot to hboot. Uh oh.
Click to expand...
Click to collapse
What happens when you press power+volume down?
Edit: Also, if you're phone turns on, you're not bricked. It's pretty hard to brick this phone.
tekhna said:
What happens when you press power+volume down?
Edit: Also, if you're phone turns on, you're not bricked. It's pretty hard to brick this phone.
Click to expand...
Click to collapse
Yeap just pull the battery and power on with power and volume down.
This kinda stuff you'll be fine with. Just don't get too creative with "repairs" that aren't posted in here.
tekhna said:
What happens when you press power+volume down?
Edit: Also, if you're phone turns on, you're not bricked. It's pretty hard to brick this phone.
Click to expand...
Click to collapse
As I understand it, the only way to brick a phone is to bork a radio installation.
Dude...pull your battery, put it back in, then power and volume down at the same time. If you can get to hboot, life is good.
After about 30 battery pulls I was able to get to hboot. I have no idea what the issue was. Finally got the phone booting now. I appreciate the replies.
lithium630 said:
After about 30 battery pulls I was able to get to hboot. I have no idea what the issue was. Finally got the phone booting now. I appreciate the replies.
Click to expand...
Click to collapse
Awesome, glad to hear. Did the s-off work?
tekhna said:
Awesome, glad to hear. Did the s-off work?
Click to expand...
Click to collapse
Sure did. Took me a little while to get the wire trick right. I just noticed the sd card is not recognized. I see the fix on the thread. That will be tomorrows project.
Constant reboots
I am able to install roms, but I get constant reboots, every few minutes at best. I tried a few different ICS ROMS. I am running the latest firmware. I BELIEVE with s-off I shouldn't have to flash PH98IMG.zip. I tried fixing permissions also but it has not helped.
How did you get the latest firmware and radios without running the PH98IMG.zip? The ics roms you are installing won't update your firmware.
Sent from my ADR6425LVW using Tapatalk 2
Chillerman said:
How did you get the latest firmware and radios without running the PH98IMG.zip? The ics roms you are installing won't update your firmware.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I relocked the phone and updated it a couple weeks ago. Maybe I need to try it again.
lithium630 said:
I relocked the phone and updated it a couple weeks ago. Maybe I need to try it again.
Click to expand...
Click to collapse
Well the newest leak came out 5/7 and the one before that 5/2 so only a week ago. I would download the newest from Android Police and follow the instructions they give to install, then flash a recovery and install a rooted Rom for this firmware like Scott's.
Sent from my ADR6425LVW using Tapatalk 2
lithium630 said:
I relocked the phone and updated it a couple weeks ago. Maybe I need to try it again.
Click to expand...
Click to collapse
I don't know why you relocked...I think there's a thread about not so good things happening to those who relock after S-off. I downloaded and installed the 5/5 leak as PH98IMG after I S-off'd and reflashed the recovery.
I'm pretty sure my hboot said "locked" straight out of the gate after I did the S-off deed.
douger1957 said:
I don't know why you relocked...I think there's a thread about not so good things happening to those who relock after S-off. I downloaded and installed the 5/5 leak as PH98IMG after I S-off'd and reflashed the recovery.
I'm pretty sure my hboot said "locked" straight out of the gate after I did the S-off deed.
Click to expand...
Click to collapse
Nothing bad happens, you just don't ever get back to "locked" without doing S-off again. You're just at "relocked" like the old days. S-on with an eng hboot on the other hand will brick your device.
That aside, there's no need to unlock if you're S-off. Either flash a patched hboot or just flash a PH98IMG.zip of AmonRa if you don't need fastboot commands (I did the latter).
I flashed the last firmware before S-off. I followed the instructions given. I flashed the latest firmware today and this damn thing still reboots constantly. I flashed the 5-7 firmware then the Venasaur Rom.
lithium630 said:
I flashed the last firmware before S-off. I followed the instructions given. I flashed the latest firmware today and this damn thing still reboots constantly. I flashed the 5-7 firmware then the Venasaur Rom.
Click to expand...
Click to collapse
You need to try installing the radio firmware or just install the complete RUU again. And install a clean copy of the rom, not a nandroid backup. Wipe data, cache, dalvic cache, and system before flashing the rom.
Send me a private message if you would like and I'll help you get it figured out on gtalk.
So I decided I needed to update my phone. I installed the new firmware and everything went perfect. I decided on this rom (I am S-ON). After installing the rom I ran the other zip for S-On users. It then told me my Main Version was too old. I remember doing a fix for this months ago and saying I won't have this issue again. Now I am sitting at a white HTC screen thinking my phone is completely done for. With the firmware leak and all that all my backups seem to have been deleted. Any suggestions?... I am in dire need.
-Still sitting staring at this white htc screen. I literally am out of ideas. I did everything perfect and this happened, I'm so sad. I specifically remember doing something regarding MainVer's awhile back so I would never have this problem and now I am here with a broken phone. This blows ... Suggestions?!
SHIDOOBY said:
So I decided I needed to update my phone. I installed the new firmware and everything went perfect. I decided on this rom (I am S-ON). After installing the rom I ran the other zip for S-On users. It then told me my Main Version was too old. I remember doing a fix for this months ago and saying I won't have this issue again. Now I am sitting at a white HTC screen thinking my phone is completely done for. With the firmware leak and all that all my backups seem to have been deleted. Any suggestions?... I am in dire need.
-Still sitting staring at this white htc screen. I literally am out of ideas. I did everything perfect and this happened, I'm so sad. I specifically remember doing something regarding MainVer's awhile back so I would never have this problem and now I am here with a broken phone. This blows ... Suggestions?!
Click to expand...
Click to collapse
If you are s-on, it is nearly impossible to be "done for". Probably user error (no offense) but you probably had a file named incorrectly or it didn't flash properly. I just got to work and can't really help you right now, but i know someone can. Just don't worry, you'll be fine. Like i said, it's far from "done for".
tCizler said:
So I decided I needed to update my phone. I installed the new firmware and everything went perfect. I decided on this rom (I am S-ON). After installing the rom I ran the other zip for S-On users. It then told me my Main Version was too old. I remember doing a fix for this months ago and saying I won't have this issue again. Now I am sitting at a white HTC screen thinking my phone is completely done for. With the firmware leak and all that all my backups seem to have been deleted. Any suggestions?... I am in dire need.
Click to expand...
Click to collapse
Easy fix.
If you don't have the ROM on your computer anymore, download it again. Extract it and copy the boot.img to your ADB directory (if you don't have ADB, you need to get it lol.) Plug your phone into your computer, then just boot your phone into your bootloader, go into recovery, wipe everything 3X to be safe. Install the ROM, reboot into bootloader (make sure you're in fastboot USB mode.) Open up command prompt, CD to your ADB directory and type in fastboot flash boot boot.img. Reboot, and enjoy. If you have any issues, let me know.
In addition to Chyrux's useful post, I'd recommend keeping backups of your phone's storage on PC and possibly cloud storage.
If you got the time, or a spare SD card to get phone running in the meantime, might want to try a recovery program to get those nandroid backups and files off the SD card. I'd suggest Piriform Recuva for Windows, use the Deep Scan option.
I used to have ADB but don't anymore and downloaded the "noob proof" thing that allows you to do everything. Although you can't really use it without your phone turning on. When I press the volume down button it tries to install a kernel and said "Main Version Old" and makes me press the power button to reboot. I do have Amon Ra installed. I haven't really messed with the whole phone thing in awhile and have tried to educate myself by reading and reading and am a bit of a perfectionist. I don't know where I went wrong.
-I do know that I am on the new firmware w/ ICS
-I do know that Amon Ra is installed.
-I don't have a backup because everything seems to have been deleted.
-I suppose something went wrong during the installation process with RezRom S4 2.5
-I currently have no idea what I am doing. I am not stupid, nor do I expect handouts. I am fully capable of reading threads and usually fixing all my problems on my own. But, without a backup and me not being completely familiar with adb and my phone stuck on a white htc screen it makes me a bit timid to do anything else without some direction.
SHIDOOBY said:
I used to have ADB but don't anymore and downloaded the "noob proof" thing that allows you to do everything. Although you can't really use it without your phone turning on. When I press the volume down button it tries to install a kernel and said "Main Version Old" and makes me press the power button to reboot. I do have Amon Ra installed. I haven't really messed with the whole phone thing in awhile and have tried to educate myself by reading and reading and am a bit of a perfectionist. I don't know where I went wrong.
-I do know that I am on the new firmware w/ ICS
-I do know that Amon Ra is installed.
-I don't have a backup because everything seems to have been deleted.
-I suppose something went wrong during the installation process with RezRom S4 2.5
-I currently have no idea what I am doing. I am not stupid, nor do I expect handouts. I am fully capable of reading threads and usually fixing all my problems on my own. But, without a backup and me not being completely familiar with adb and my phone stuck on a white htc screen it makes me a bit timid to do anything else without some direction.
Click to expand...
Click to collapse
Lol I feel your pain. I don't have an SD card reader, so situations like this usually blew. But, there's a bright side: you have an internal storage unit. Let's try something basic. Take out your SD card and plug your phone into your computer. Reboot into your recovery and mount your USB storage. Tell me if you can see your internal and can access it.
So this is where I get stuck at; I appreciate that idea and will try it shortly (at work at the moment). I basically have no access with my computer and phone via usb because i am unable to get past hboot.
2 things happen as of right now:
-I press the power button and it sits at the HTC white screen forever
-I hold volume down and the power button and it tries to flash a kernel and says my Main Version is old. (When in fact, I know I did the MainVer fix while back; frustrating)
So with those 2 things only happening, is your suggestion still to yank out the external? I wish I had a microSD reader to wipe it and put a new rom on there and then figure out how to access amon ra and get passed this mess.
I took 2 min off work to yank the card out(the external, that is) -- I was able to reach recovery. I went into the mounting section of Amon Ra where I was able to see /sd-ext and /sdcard, both of which I got the message. "E: Can't mount /dev/block/mmcblk1p1) (No such file or directory)
Chyrux said:
Lol I feel your pain. I don't have an SD card reader, so situations like this usually blew. But, there's a bright side: you have an internal storage unit. Let's try something basic. Take out your SD card and plug your phone into your computer. Reboot into your recovery and mount your USB storage. Tell me if you can see your internal and can access it.
Click to expand...
Click to collapse
And for that matter, I have gotten in the habit of lifting my battery out at an angle, pressed into the contacts still to remove and insert my SD card on the fly for when I get these lingering PH98IMG.zip files. Pop out, go to recovery with a ninja grip on phone, and pop SD in lol.
I know Amon Ra Revamped 3.15 recovery has an option to delete those zips.
http://forum.xda-developers.com/showthread.php?p=23169557
Need to try reflashing that zip again in recovery perhaps, maybe RUU undid your Misc partition Mainver fix.
In any case... What your white bootloader screen says would help troubleshoot.
(Sorry for constant edits)
When you flash a new kernel the mainver is changed to what that kernel's is. I'd it's a newer number then when you try to flash something with a older number it won't flash. So every time you flash a kernel it is a good idea to go ahead and redo the main version fix
Sent from my ADR6425LVW using Tapatalk 2
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT 2.21. 0000
RADIO-1.2.22.10. 0310r/1.22.10.0308r
OpenDSP-v13.6.0.7611.00.0104
eMMC-Boot
Mar 11 2012,22:16:16
HBOOT
<VOL UP> to previous menu
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
- How would I flash the Mainver fix when I can't even communicate with my computer through usb?
- Would adb help(I haven't used in a LONG time)
- I'm sitting at the screen I just took about 20 min to type out up above.
The white screen text I showed you was without the external sd card in. I feel like the only solution right now is to buy another external SD card.. put a rom on it, and then flash it... maybe that's the solution since I can't access this SD card and it seems to be ****ed with a mainver problem? Although, even with a new SD card I don't know how I would flash the mainver fix?
SHIDOOBY said:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT 2.21. 0000
RADIO-1.2.22.10. 0310r/1.22.10.0308r
OpenDSP-v13.6.0.7611.00.0104
eMMC-Boot
Mar 11 2012,22:16:16
HBOOT
<VOL UP> to previous menu
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
- How would I flash the Mainver fix when I can't even communicate with my computer through usb?
- Would adb help(I haven't used in a LONG time)
- I'm sitting at the screen I just took about 20 min to type out up above.
Click to expand...
Click to collapse
Okay, you are following the guide of the RezROM to a tee I take it. Have to ask which AmonRa version did you install? I got the same mounting errors once and had to re-flash the recovery to AmonRa 3.14 to detect the mount points properly.
And yes, should be able to use fastboot commands with ADB to push the recovery, the Mainver fix, etc. That is the key communication tool you have barring any other access in your situation.
I'm am not anywhere remotely close to a PC and a bit rusty too, will try and find the ADB commands for that.
PhantasmRezound said:
Okay, you are following the guide of the RezROM to a tee I take it. Have to ask which AmonRa version did you install? I got the same mounting errors once and had to re-flash the recovery to AmonRa 3.14 to detect the mount points properly.
And yes, should be able to use fastboot commands with ADB to push the recovery, the Mainver fix, etc. That is the key communication tool you have barring any other access in your situation.
I'm am not anywhere remotely close to a PC and a bit rusty too, will try and find the ADB commands for that.
Click to expand...
Click to collapse
Those lines I typed were without the SD card in the actual phone. I did install the newer version of AmonRa (3.15 for ICS and GB) In the actual recovery with the External SDcard out I did some scoping around where you're able to delete the kernel install, but that would leave me still with a broken phone. I need to be able to access my SD card and put a new rom on it i'm guessing? I don't even know what the **** I'm doing anymore.
wow.
put THIS file on your sd card. then do the update in HBOOT. once your are back up and running flash the main version fix. then get s-off
*EDIT* just saw where you can go into recovery. Okay. Here comes the fun part. I'm not well-versed in the mainver issue and this method can brick your phone, so be careful. Just what I have for now.
Start by having your SD card out (but on your desk, just make sure you have it lol.) Boot up your phone into the bootloader and go to where you can access your recovery, but don't. Here's where you can brick your phone. Pop out your battery and leave the cable plugged in (you'll have power still going to your phone.) Now, put your SD card back in and put your battery back in as well. Boot into your recovery and mount USB storage. From there, delete the update file using My Computer.
SHIDOOBY said:
So I decided I needed to update my phone. I installed the new firmware and everything went perfect. I decided on this rom (I am S-ON). After installing the rom I ran the other zip for S-On users. It then told me my Main Version was too old. I remember doing a fix for this months ago and saying I won't have this issue again. Now I am sitting at a white HTC screen thinking my phone is completely done for. With the firmware leak and all that all my backups seem to have been deleted. Any suggestions?... I am in dire need.
-Still sitting staring at this white htc screen. I literally am out of ideas. I did everything perfect and this happened, I'm so sad. I specifically remember doing something regarding MainVer's awhile back so I would never have this problem and now I am here with a broken phone. This blows ... Suggestions?!
Click to expand...
Click to collapse
Delete the PH98IMG.zip off your sdcard, download and flash THIS and then try flashing the rom and kernel again. should work. Worked for me.
try this link: http://forum.xda-developers.com/show...57&postcount=4
tmettler5 said:
Delete the PH98IMG.zip off your sdcard, download and flash THIS and then try flashing the rom and kernel again. should work. Worked for me.
try this link: http://forum.xda-developers.com/show...57&postcount=4
Click to expand...
Click to collapse
I think his issue is that he can't access his SD card because he doesn't have a reader/other device to use.
Ah... That makes sense. Maybe another sdcard, then? I'll put the set mainver low file in the dropbox later today and send a link. If you can use a second sd card and put it on that he can fix it. I think.
Sent from my ADR6425LVW using XDA
tmettler5 said:
Ah... That makes sense. Maybe another sdcard, then? I'll put the set mainver low file in the dropbox later today and send a link. If you can use a second sd card and put it on that he can fix it. I think.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Nah, he won't have to. Granted, my method is a bit...unsafe lol, but it worked fine for me. he just has to be careful and he'll be able to take the file off. Glad you have the fix cause I don't, though. So hopefully my trick will work and then he can use the fix.
If you get to the point where you can get into recovery, flash this: http://dl.dropbox.com/u/79523435/SetMainVersionLOW.zip
Then flash your rom and kernel as per normal.
Okay. So, I unlocked my bootloader, rooted my phone and then went to do the S-Off with the "wire trick." Well, during the Control Bear program it got to the 5th beer and rebooted my phone to the black screen with the phone and green arrows in a circle on it. It then couldn't find the device after 5 attempts of doing so. Yes, I had the drivers installed properly for the phone and ADB - so I don't believe that was the issue. Anyways, I closed Control Bear and unplugged my phone. Restarted my phone and Control Bear and it got stuck on the same screen, but now it can't find the device. I put the phone in fastboot, Control Bear detected it and then it booted up to the green arrow screen again.
At this point, I figure I just need to do a factory reset and everything should be fine. WRONG!
So far I have flashed 4EXT touch recovery so that I can attempt to flash a custom ROM. I tried flashing two different ROMs and after a successful installation it reboots and then gets to the same green arrow screen. I've also attempted to flash a stock RUU by putting it on the external SD card, renaming it PH85IMG.zip and it only gets through the blue status bar in the upper right corner and then goes back to the fast boot screen. Rebooting it afterward takes me to the same green arrow screen.
Suggestions on resurrecting my phone? I'd really like to not have to go through the unbricking BS in this thread: http://forum.xda-developers.com/showthread.php?t=1627882
Carrier
OS version
etc.
Info then problem solving after.
Most likely you can just restore a stock ruu, the one you used is probably older since you dug up a hard brick recovery thread though you have a softbrick, tells me you read a far way back than you needed to, so shoot some info, start solving from there.
TMOUS
Was running Stock ICS 4.0.3
HBOOT 1.93.0002
Dark Nightmare said:
Carrier
OS version
etc.
Info then problem solving after.
Most likely you can just restore a stock ruu, the one you used is probably older since you dug up a hard brick recovery thread though you have a softbrick, tells me you read a far way back than you needed to, so shoot some info, start solving from there.
Click to expand...
Click to collapse
Here: http://d-h.st/3VD
I don't know if that's the one you downloaded, but that's the latest image we have, you already know the process of renaming the file and placing it on your external sd card, also before you attempt to reload the stock RUU, don't forget to lock your bootloader, since you're s-on. It will say relocked, but that's fine, then put your sd card in and reboot into bootloader after relocking, watch the magic happen, hit volume up to update.
Ah! That's the step I was forgetting: relocking my bootloader! Thanks. I'm gonna get on that now. I'll let you know how it goes.
Dark Nightmare said:
Here: http://d-h.st/3VD
I don't know if that's the one you downloaded, but that's the latest image we have, you already know the process of renaming the file and placing it on your external sd card, also before you attempt to reload the stock RUU, don't forget to lock your bootloader, since you're s-on. It will say relocked, but that's fine, then put your sd card in and reboot into bootloader after relocking, watch the magic happen, hit volume up to update.
Click to expand...
Click to collapse
I figured, but I could've been wrong, yup let me know when you boot.
YEAH! That worked! Thanks so much! I think I'm gonna skip doing S-Off for now. LOL
DJ_Caibel said:
YEAH! That worked! Thanks so much! I think I'm gonna skip doing S-Off for now. LOL
Click to expand...
Click to collapse
:highfive:
Lol it's not exactly needed unless you wanna mess with things on an advanced level or go back to GB, which I doubt you do, so no worries.
I was looking to SuperCID, but I'm gonna leave that be and be happy with it as is. Thanks again for your help.
Dark Nightmare said:
:highfive:
Lol it's not exactly needed unless you wanna mess with things on an advanced level or go back to GB, which I doubt you do, so no worries.
Click to expand...
Click to collapse
I replaced my digitizer and screen a few days ago and all was working well. After turning the phone off and on a few times over a couple of days it was still working great. Then I tried to start it and got the htc splash screen and then black. I pulled the battery and booted into bootloader. It gave me several error messages looking for (I think) PH98DIAG.ZIP and not finding it. I have tried to reinstall TWERP 2.6.3.0 using fastboot usb and get a message that installation was successful, but I cant access TWERP in bootloader. I have tried FACTORY RESET with no improvement. If I start the phone and get past the htc screen, it gets warm and the battery eventually runs down, so SOMETHING is running.
I also tried to install TWERP using the adb flash_image method and my phone is not recognized. Of course both methods require usb debugging mode to be switched on and I can't get there.
I was running Infection 8.2.1 and TWERP 2.6.3.0. Rooted, S-on, bootloader unlocked (of course).
Any suggestions?
This is our most desperate hour. Help me, Obi-Wan Kenobi. You're my only hope.
geronimo48 said:
I replaced my digitizer and screen a few days ago and all was working well. After turning the phone off and on a few times over a couple of days it was still working great. Then I tried to start it and got the htc splash screen and then black. I pulled the battery and booted into bootloader. It gave me several error messages looking for (I think) PH98DIAG.ZIP and not finding it. I have tried to reinstall TWERP 2.6.3.0 using fastboot usb and get a message that installation was successful, but I cant access TWERP in bootloader. I have tried FACTORY RESET with no improvement. If I start the phone and get past the htc screen, it gets warm and the battery eventually runs down, so SOMETHING is running.
I also tried to install TWERP using the adb flash_image method and my phone is not recognized. Of course both methods require usb debugging mode to be switched on and I can't get there.
I was running Infection 8.2.1 and TWERP 2.6.3.0. Rooted, S-on, bootloader unlocked (of course).
Any suggestions?
This is our most desperate hour. Help me, Obi-Wan Kenobi. You're my only hope.
Click to expand...
Click to collapse
1) The looking for files and not finding any is normal.
2) What's it doing when you try to go into recovery? Just a blank screen? You may want to try installing the recovery using the PH98IMG.zip method if you have access to a card reader to get the file on your SD Card. - http://forum.xda-developers.com/showthread.php?t=1902381
Download the attached file in that thread, rename it to just PH98IMG.zip, place it on the root of your SD card and go into the bootloader, it should find the file and ask you to press volume up to install it. If it goes successful, remove the zip file then try to get into recovery from the bootloader again.
mjones73 said:
1) The looking for files and not finding any is normal.
2) What's it doing when you try to go into recovery? Just a blank screen? You may want to try installing the recovery using the PH98IMG.zip method if you have access to a card reader to get the file on your SD Card. - http://forum.xda-developers.com/showthread.php?t=1902381
Download the attached file in that thread, rename it to just PH98IMG.zip, place it on the root of your SD card and go into the bootloader, it should find the file and ask you to press volume up to install it. If it goes successful, remove the zip file then try to get into recovery from the bootloader again.
Click to expand...
Click to collapse
I tried that. Bootloader only searches for PH98DIAG.ZIP, doesn't find it and goes black.
@geronimo48 Are you S-Off...if so when you boot into bootloader and can access the fastboot usb from there i can give you the RUU.exe files you run in windows that factory restores your phone from the pc
My phone is S-ON. I kept it that way to make sure I wouldn't brick it .
Thanks for trying.
My phone is S-ON. I kept it that way to make sure I wouldn't brick it .
Thanks for trying.
geronimo48 said:
My phone is S-ON. I kept it that way to make sure I wouldn't brick it .
Thanks for trying.
Click to expand...
Click to collapse
s-off allows you to unbrick though...ill search for the diag files as your on a tough boat
Edit: what hboot you on....i may have a fix for you if on hboot 2.25 or 2.27
Hboot is 2.27
I am thinking there is no way to S-Off with my phone the way it is, correct?
geronimo48 said:
I am thinking there is no way to S-Off with my phone the way it is, correct?
Click to expand...
Click to collapse
nope...your soft bricked and need access to rom to change a few settings in that and have it running before starting the process...i may have a fix for you..PM me if you can
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: