Hey guys. A while ago I was trying to use the gfree method to unlock my sim (I had S-OFF) but I realized I had to downgrade my radio. Stupidly, I tried to flash the official RUU (RADIO-26.03.02.18_M3).
Half way through, I got an error (forgot what cause I wasn't paying much attention -_- ) and had to abort. After that, the phone would not go past the HTC screen. I go into bootloader and the phone was now S-ON and had the radio version 26.03.02.18_M3.
No matter which rom I flash the same thing happens. On another note, I can get into Bootloader and clockwork recovery and ADB works as well.
Anyone know what to do from here? Sorry for being stupid but i`m not the brightest at this
Sounds like you may wiped your boot and system partitions doing this. Did you have a nandroid backup to restore? You can try flashing the PC10IMG again to see if it works this time (risk of losing recovery) or try flashing a custom kernel in addition to the rom.
Kind Regards,
Kevin
Related
Recently my phone was working fine until today. I was on mikfroyo 4.4 everything was fine until i decided to flash an unimportant file, when i reboot it my phone was doing boot loops, so i decided to wipe everything and flash a clean mikfroyo 4.4 again. it worked for a couple hours, later my phone started to freeze, i took the battery out and i got stuck on the white screen logo.. i tried to take battery out for a couple times and nothing.. i tired to go into recovery mode(amon-ra 2.2.1) and i could not get into recovery, it kept on freezing i was like WTF!! then i tried to go into bootloader and that worked fine, but when i choose to boot into recovery via bootloader it did boot into recovery but then it froze again in recovery.. So at the end nothing worked but bootloader.. then i decided to flash a ROM via bootloader (PC36IMG.zip) and that fixed all the problems temporarily (it did not freeze).. but then I notice that that was a stock unrooted PC36IMG file so i lost root and it put back the HTC stock recovery (NOT AMON-RA nor CLOCKWORK).. then the problems started again (the same from above).. but since i rooted my phone via unrevoked forever i had S-OFF.. so i flashed AMON_RA recovery via bootloader to see if I could flash unrevoked-forever-son (that way i could have S-ON and send it to sprint for a replacement) but again it kept on freezing on recovery mode.... so my question is is there anyway i can flash unrevoked-forever-son via bootloader.... that way i can send it to sprint and tell them that my phone keeps on freezing.
Nothing works but bootloader, everything else freezes (recovery mode and while trying to boot the phone)
I will apreciate your time and help.
Did you try running unrevoked son as PC36img.zip?, then the stock RUU. (doesn't sound like it could hurt, lol)
but what kind of files would i put inside pc36img?
You don't put anything inside the PC36IMG.zip file. It comes ready to go from the unrevoked team:
How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update
Click to expand...
Click to collapse
- So go here: http://unrevoked.com/rootwiki/doku.php/public/forever
- Find the section I quoted above
- Download the PC36IMG.zip file
- Put it on the root of your SD card
- Power off
- Hold vol down + power
- Once in HBOOT it will automatically find/ask to run the PC36IMG.zip file
- volia! s-on
I know, i understand that process but my problem is that i cant go into recovery AT ALL it frezzes each time neither to boot my phone normally... the only thing that works fine is bootloader.. so what i am trying to look for is a way to flash the s-on tool via botloader bc i can not go into recovery.
the pc36img contains the stock unrooted ROM - supposed to be flashed via bootloader (i have already done this process so i lost root)
and when you download the S-on tool it comes in a zip file that is suppose to be flash thru recovery not bootloader (and this will be my final step which is not done yet)
yoboii23 said:
I know, i understand that process but my problem is that i cant go into recovery AT ALL it frezzes each time neither to boot my phone normally... the only thing that works fine is bootloader.. so what i am trying to look for is a way to flash the s-on tool via botloader bc i can not go into recovery.
Click to expand...
Click to collapse
Edit: one sec -- I am looking for a PC36IMG.zip that did s-on.
spiicytuna said:
I am looking for a PC36IMG.zip that did s-on; I've used it recently on a friends evo
Click to expand...
Click to collapse
This is what i was looking for i hope you can find it!! !!!
I was looking for a way to have the s-on tool inside a PC36IMG.zip.. i didnt think it was possible
But isn't that process (PC36IMG.zip) only for things that suppose to be flash thru bootloader? like slpash screens, recoverys, boot.img? so in what category does the s-on tool fits?
I'm sorry for all this questions but i dont wanna make my phone worse then what already is.
I think your best bet is to hop on freenode and join channel #unrevokedtest
Easiest way to do this is here: http://webchat.freenode.net/
They'll be able to help you for sure. LazyDog and joshua_ are two good people to look for.
thank you man.. but nope is confirmed you can not put put the S-on tool into a PC36IMG.zip ima have to tell sprint that i lost it.
yoboii23 said:
thank you man.. but nope is confirmed you can not put put the S-on tool into a PC36IMG.zip ima have to tell sprint that i lost it.
Click to expand...
Click to collapse
Did you talk to the guys on irc? Seriously, I've seen them preform some miracles.
PS. The chances of Sprint checking s-on/off is highly unlikely.
You can use the pc36img from amon ra's thread to flash the recovery and then use it to lock your nand. Afterward all you have to do is run the ruu one more time and you will be good to go
I agree with what was said before. The likelihood that they'll look at S-On is VERY small. I would just take it in, tell them its freezing all the time, and ask for a replacement. If by some crazy chance they do look at S-On, just play dumb and pretend you don't even know what it is. If you've got a cute lookin girl to help you that'd be willing to take it in, all the better
Otherwise, try running the RUU for your build number. We'll go from there if you still have problems.
I fixed it, it was all due to a ripped cable inside my evo I don't knw how that happened but it happened lol all I had to do was replace my screen.
And yea I did talk to guys from unrevoked.. they r pretty smart and understood my problem quick but were unable to help me.
I was rooting my Desire following the newbie guide found here:
http://forum.xda-developers.com/showthread.php?t=1016084
When doing the S-OFF with Alpharev, phone got stuck on step 3:
Flashing new bootblock: OK. Read Alpharez instructions and it would be safe to remove battery. Did so, then fastboot, recovery mode, back-up & here, it says it cannot find any files, even though I made a back-up when I rooted with unrevoked... Am I screwed?
Edit: it does say I'm on S-OFF now, but still can't get into stock ROM.
As you mentioned, you see that your are S-OFF, so you can go into alpharev HBOOT I guess?
That means, you might be able to go into recovery via HBOOT.
From there you might be able to flash a custom rom. (Backup stock rom just to be sure)
Appreciate the comment.
I can get into HBOOT and from there into clockworkmod recovery, but as I said, there appears do be no recovery file. You're saying I should do back-up in clockworkmod and proceed with flashing a custom ROM? I'd still need to partition my SD-card but I suppose this can be done with my card reader as well. I followed the guide completely so I'm clueless as to what went wrong.
Hmm, so if you made a backup in clockworkmod it should be in /sdcard/clockworkmod/backup. There's no files there? Are you able to access other files on your sd as you were before?
Just got home. Popped the cd-card in adapter. There's no recovery file on it. Only a 'backup' map, but that might just be the standard android backup one...
Edit: I made a new nandroid back-up now, but I noticed I didn't get the typical alpharev - why so serious - screen. Is this something to worry about? Next step would be flashing new ROM.
jens1987 said:
Just got home. Popped the cd-card in adapter. There's no recovery file on it. Only a 'backup' map, but that might just be the standard android backup one...
Edit: I made a new nandroid back-up now, but I noticed I didn't get the typical alpharev - why so serious - screen. Is this something to worry about? Next step would be flashing new ROM.
Click to expand...
Click to collapse
Ok so you've got a working recovery and backup - good!
Now check you still have s-off, look in bootloader, top line. You should normally have the joker screen so maybe you have to rerun alpharev?
It does still say AlphaRev, same options as in the guide, but not the - why so serious - screen (HTC one instead). I could rerun Alpharev, but it might get stuck again I definetely need the S-OFF before flashing new ROM?
Odd. Well, you don't need s-off to flash a rom, but you do need it if you want to change your partition table (gives you more internal memory in /data), and it allows you write access to any part of your phone while booted (e.g. you can permanently delete any app by removing its .apk file from /system). You definitely see "bravo pvt1 s-off" or something similar at the fist line of bootloader?
I do. You can check the images I added It's all there, but when going into recovery, I get clockworkmod and not alpharev and as said, not the splashscreen.
I think I found out why as well. Phone got stuck at 3rd step in Alpharev (flashing new bootblock: ok). After this, you would normally get the following:
Flashing splash1: ok
Flashing CWM-Alpharev recovery: ok
Procedure completed succesfully!
So I take it I'm S-OFF but without these last 2 features. Question is now whether I can proceed or need to do it again.
Edit: tried a restore, but I still can't get into stock rom :/
Edit2: proceeded with flashing leedroid 2.2 and it seems to have worked
I've messed up big time now guys.
The background to the issue is that i wanted to upgrade my DZ to android 2.3 but when I tried to install the update Clockwork recovery wouldn't install it, so I figured that I need to install the original bootloader.
So I went into hboot and install what I tought was the original, it was, but it was for the G2.
So I tried in all kind of ways to get back to the DZ hboot but nothing works.
And after doing to many things, the latest thing I did was flashing a nandroidbackup from my DZ, and now I am stuck at boot screen.
However I can get into hboot and Clockwork recovery, so I don't think I am totally screwed, right?
But is there a way to get back to my old DZ at all?
Edit: I have the DZ bootloader now, but when in hboot trying to update to DZ it just fails.
Edit 2: Just wanted to say that I solved the problem, found an older nandroidbackup and flashing that one did the trick, sorry for posting..
Okay, so I flashed the 1.32 RUU to be able to upgrade my DHD up to 3.12.405. so that I could install the unlockable HBOOT.
According to HTC this unlocked HBOOT should let you flash custom ROMs.
I went to to htcdev.com and followed their steps to unlock my bootloader, which worked flawlessly..
Except when i flash custom ROMs the phone hangs on splashscreen. I've tried full wipe and clean install, I've even tried restoring backed up ROMs.
Any one else have simlar problems? or a solution?
anything that may help?
Since I don't read anything about it, I'm gonna ask you: Did you flash a recovery?
Yes sorry for not managing to provide that info before :-/
I have ClockworkMod 5.0.2.0
And do you also know that after flashing a custom ROM the first boot might take a loooong time?
OFC. I've waited over 20 minutes for the thing to boot but nothing happens.
Only thing i can think of is that it might be that it is S-ON and not S-OFF.
also i can recover the backed up stock ROM.
_____________________________________________________________________________
I got Advanced ACE Hack Kit to degrade it so now I'm able to S-OFF, super CID and everything again
All I had to do was to relock the bootloader and run the AAHK
Thank for the responses.
Moderators may close this now.
Incrediblec XD ship S-On
Hboot-0.92.0000
microp-0417
touch panel-atmelc03_16ac
Radio-2.15.10.07.07
Jul 23 2010, 18:06:51
Hello, first thank you for an amazing and current forum, I'd been researching my issue for a while, but most things are dated around 2010. I've experience rooting and ROMing a Droid X with multiple ROMS, but I use the original Incredible as my main phone because I still love it. Well, I originally rooted my Inc with Unrevoked3 I believe. I left the ROM as stock up until a couple months ago when I put CM7.2.0 on it.
About a week ago, the phone would always have working mobile data. Yet, if I received or tried to make a call, I couldn't and then I would lose texting ability. Then, a couple days ago, I was using the Inc for wifi tethering when suddenly it went into an Incredible bootloop. I tried booting to the cyanogen recovery, but it will quickly loop out of it as well.
I went to pvillecomp.com/ and downloaded all the stock Inc software. I individually renamed files to PB31IMG.zip and tried to have HBoot pick up on them. Hboot will see the files, but then do nothing. Except, the originally ROM will get checked and come back and say that the current version is older and can't be flashed.
I've always tried the RUU software for hboot and the original ROM. I either get a usb error or a low battery error even if the battery is charged. Granted, I'm trying the RUU from the phone's bootloader screen.
Does anyone have some support they could throw this way? I use my phone for internet and everything. Thank you all.
-Nevin
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
did you flash any radios? Flashing radios always ends up bad.
NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
123421342 said:
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
Click to expand...
Click to collapse
Btw, no I didn't flash the radio. That was the only thing I didn't attempt to flash. Yet, when attempting to flash anything else, nothing worked. Still wondering about getting S-off before using TWRP, but hopeful to still get it working. Thank you again.
NevinInc said:
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
Click to expand...
Click to collapse
BUMP/UPDATE:
Yes, I'm still at it trying to get my Dinc out of it's bootloop and up/running. It's difficult at this point to say what all I've tried. At one point I wanted to use htcdev.com to ensure the bootloader was unlocked/etc. I've had much trouble trying to get fastboot to work correctly on my pc. I've seem to get stuck on "waiting for device" which appears to be a driver error.
I gave up on that and started focusing on the RUU process. I've tried to install the entire Gingerbread 605.3 file. I fixed the error usb 170 by updated or changing htc sync software. Now I'm left with error 140 bootloader error.
I've also updated hboot using the ruu process for version 605.2. This worked on my pc and got me partially excited. Now my hboot shows up as "Locked" now at the top. I also downloaded a different Stock.img file. Hboot detected this and begun the install process. Everything came up as complete and upon reboot went right back into the white screen/incredible bootloop.
So since posting before I've updated htc sync on my pc and have officially relocked my bootloader. I don't mind RUU'ing things to stock, but now gotta get past the Error 140. Any ideas?
So I'm not sure how many are looking at this or have had ideas, but I was able to use htcdev to unlock the bootloader.
Before unlocking the bootloader I was able to RUU to image .15. After this is when I unlocked the booloader. The RUU said it was complete, but I still only bootloop on the incredible white screen. Now, some of the pb31img.zip files I've come across don't even try to install. This includes signed and unsigned .15 img files. Currently these are the new settings to the phone:
Bootloader: unlocked, s-on
hboot 1.07.0000
radio - 2.15.10.12.20
Image version: 4.08.605.15
The last option I can think of is to try using fastboot, but won't that essentially do the same thing? If you think fastboot is the way to go, can u link me or give me some basics on using it. Obviously I used it for unlocking the bootloader so it can't be that complicated.
Are there any other ideas or should I give up on my Dinc? Looking forward to hear what you think. Thanx.
-Nevin
somebody recommended you install TWRP and install a stable Jellybean ROM. Did you try that?