Related
Hi, I have been flashing many ROMs and trying different tweaks with my evo since I got it. However I have decided to flash the new radio which I have not done before. What are the critical steps involved in insuring I do not brick my phone?
Also, is there an advantage with installing updated radios through Hboot with the pc361 file over recovery? I know there is none currently for the newest, but was wondering if there is any advantages. Thanks for the replies.
Sent from my PC36100
If you're going to flash a radio through recovery just make sure your getting it from someone who knows what they are doing. Also make sure you have plenty of charge on your battery and make sure not to remove your battery during the flash.
The only advantage of running a PC36IMG is you get a fesh clean system. I don't think it matters that much but like formatting c: and reinstalling some people like to run an RUU every few months. As long as you get your radio_update.zip from a reputable source then there is no advantage, regarding the radio, to running a whole PC36IMG just to get a radio out of the deal. Flashing a radio from recovery will not affect anything else you have set up already.
nebenezer said:
If you're going to flash a radio through recovery just make sure your getting it from someone who knows what they are doing. Also make sure you have plenty of charge on your battery and make sure not to remove your battery during the flash.
The only advantage of running a PC36IMG is you get a fesh clean system. I don't think it matters that much but like formatting c: and reinstalling some people like to run an RUU every few months. As long as you get your radio_update.zip from a reputable source then there is no advantage, regarding the radio, to running a whole PC36IMG just to get a radio out of the deal. Flashing a radio from recovery will not affect anything else you have set up already.
Click to expand...
Click to collapse
Can you also answer this question. Why is the only Hboot we can use for root the .76 version? Is there something inherent with it or is it that no one has altered the .79 version yet? Thanks for taking the time.
rafroehlich2 said:
Can you also answer this question. Why is the only Hboot we can use for root the .76 version? Is there something inherent with it or is it that no one has altered the .79 version yet? Thanks for taking the time.
Click to expand...
Click to collapse
the .76 version is the engineer build. .79 is the consumer build
I was Flashing the OTA 2.2 Froyo Leak a while ago and it just didnt finish for some reason. Now when I try to turn it on it Vibrates 5 times and has a green blinking light.
Also it is S-ON now for some reason as well.
I have looked everywhere and cannot find a solotion.
Any help is appreciated.
Edit* I have tried flashing other roms and still nothing, (I can access HBOOT but not Recovery) and I cannot flash recovery either. Everything but Hboot is gone. And i tried flashin Ruu and it says main system too old.
5 Vibrates is usually some kind of hardware issue, where-as 3 vibrates is usually a software issue.
BTW, if you're S-On, how are you going to flash any recovery or ROMs? You need to be S-Off before you can flash anything.
carngeX said:
5 Vibrates is usually some kind of hardware issue, where-as 3 vibrates is usually a software issue.
BTW, if you're S-On, how are you going to flash any recovery or ROMs? You need to be S-Off before you can flash anything.
Click to expand...
Click to collapse
How can I get S-OFF then? I can access Recovery but it doesnt do me any good it wont read my sd card.
I have no idea what I did, but it rebooted itself and its working
this is EXTREMELY weird. I had the phone plugged in because I wanted to root, but i was first getting the SD Card files off and when I unplugged the phone the same thing happened already....
So then I plugged the phone on again, went into HBOOT and ran the image until it told me it cant be read, and rebooted and back to normal....
Any idea what happened? I just wanna get opinions out of curiosity.
cvbcbcmv said:
cool. But no you don't want to be s-off for flashing the RUU back to stock, then you actually flash a s-on image first.
Click to expand...
Click to collapse
He said he was trying to flash recovery and other ROMs to try and get it to work though too... You can't flash custom recovery without being S-Off.
If you want to flash back the RUU, and go back to complete unrooted stock... then yeah, you want S-On.
carngeX said:
BTW, if you're S-On, how are you going to flash any recovery or ROMs? You need to be S-Off before you can flash anything.
Click to expand...
Click to collapse
Untrue, you can flash ROMs without being S-OFF. I was rooted and flashing ROMs before unrevoked released "forever."
Sent from my Droid Incredible running a random CM7 nightly.
it seems the problem is more serious then i imagined... I cant seem to use my phone.. when i connect it to the computer its unrecognizable and I cant do anything with it
SteveG12543 said:
Untrue, you can flash ROMs without being S-OFF. I was rooted and flashing ROMs before unrevoked released "forever."
Sent from my Droid Incredible running a random CM7 nightly.
Click to expand...
Click to collapse
So were the images previous to Unrevoked's S-Off patch just signed properly? I didn't get a DINC and root it until after Unrevoked had released their patch.
eljean said:
it seems the problem is more serious then i imagined... I cant seem to use my phone.. when i connect it to the computer its unrecognizable and I cant do anything with it
Click to expand...
Click to collapse
Like I said previously, 5 vibrates is usually a hardware issue, meaning you're most likely going to have to send it in for replacement. There's been a few people to recover from a 5-vibrate brick, but they had gotten lucky. You can search the forums and try to find how they fixed it (can't remember the thread off hand, just do a search for 5 vibrates and you'll get lots of results).
carngeX said:
So were the images previous to Unrevoked's S-Off patch just signed properly? I didn't get a DINC and root it until after Unrevoked had released their patch.
Click to expand...
Click to collapse
I guess so, idk tbh lol. I've had my Inc since day one, and rooted it rather early.
Sent from my Droid Incredible running a random CM7 nightly.
yeah except i bought off ebay so i cud flash to boost. and i did but then i got too curious and ended up with bad nv items on the phone fixed it, then my meid came as <not available> (which still remains and i believe is the problem) and now this... i cant unplug my fone or it will die on me...
i need to get S-OFF and i might be able to fix it... any ideas on how to do this through HBOOT
i need to flash a rom thats what i need to do, because ihave no drivers.., thats the hardware issue and my meid but thats not importatn
Try using unrevoked while the phone is plugged in and in fastboot/hboot?
k_nivesout said:
Try using unrevoked while the phone is plugged in and in fastboot/hboot?
Click to expand...
Click to collapse
How can this be possible? Can you just show me a quick summary and show me links to this method of rooting
Sent from my ADR6300 using XDA App
Just google unrevoked and download the unrevoked tool. I thought it did its thing in fastboot, but I could be wrong. Its worth a shot.
And BTW, its not really necessary to be posting multiple threads in multiple forums, it would be easier for you to just check one thread.
fixed it
http://forum.xda-developers.com/showthread.php?p=14440621
k_nivesout said:
Just google unrevoked and download the unrevoked tool. I thought it did its thing in fastboot, but I could be wrong. Its worth a shot.
And BTW, its not really necessary to be posting multiple threads in multiple forums, it would be easier for you to just check one thread.
Click to expand...
Click to collapse
Oh no is I bought 2 bricked phones from ebay as a wholesale and im trying to fix both of them which have different issues.
eljean said:
fixed it
http://forum.xda-developers.com/showthread.php?p=14440621
Click to expand...
Click to collapse
oh **** theres a fix for this lol i never knew
JoelZ9614 said:
oh **** theres a fix for this lol i never knew
Click to expand...
Click to collapse
Yeah the guide was released last month
Sent from my ADR6300 using XDA App
So I was reading a post about someone who was potentially able to downgrade hboot 2.16 hw4 2.3.3 to hboot 2.10 via bootloader and a PC63IMG.zip that had 3.70 in it. So I tried on my 2.3.3 s-On evo and sure enough it failed. It wouldnt work because it was an older version. So, I extracted the PC63IMG.zip and replaced the hboot 2.10 with hboot 2.16 (renaming hboot 2.16 to hboot 2.10) from the post in the dev section. I used winrar and with normal compression rezipped the files and signed in android kitchen. it actually loaded the files and went through checking them, but once check it kicked me back to the main menu of the bootloader with no error or messages. I tried the same with the file with no compression when zipped and signed and i got an error stating that it was a wrong file. and didnt even pass the check. So have I stumbled upon something simple and useful? Can someone help me look into this further and maybe it will get us somewhere. Or am I a dumb?
Sweet. I'm sure you are the first one to get this ROM ported, I know others have tried but they haven't had much success.
androidsupra said:
Sweet. I'm sure you are the first one to get this ROM ported, I know others have tried but they haven't had much success.
Click to expand...
Click to collapse
What? I never said anything about porting. I was trying to find a simple way to Root my Evo running 2.3.3. Still no luck but I was hoping what I found may be something someone has not yet tried. Its simple but I was suprised that it looked like it passed the bootloader check. I did not receive any errors, but at the same time could not downgrade.
Once you got back to the hboot menu, what version did it say you have?
If 2.10, I would think your next bet is try and run unrevoked
androidsupra said:
Sweet. I'm sure you are the first one to get this ROM ported, I know others have tried but they haven't had much success.
Click to expand...
Click to collapse
You do know the dev section is for more than ROM's. Moron. This is a post from someone attempting to find root and you show your true intelligence level.
Sent from my PC36100 using Tapatalk
spotopolis said:
What? I never said anything about porting. I was trying to find a simple way to Root my Evo running 2.3.3. Still no luck but I was hoping what I found may be something someone has not yet tried. Its simple but I was suprised that it looked like it passed the bootloader check. I did not receive any errors, but at the same time could not downgrade.
Click to expand...
Click to collapse
He wasn't serious about porting anything, common thing to do when someone posts in the wrong section (especially in development).
On my main note, any modification of an "official" PC36IMG.zip would break HTC'S signature and the bootloader would not accept the update.
Sent from my PC36100 using XDA Premium App
He's attempting to Flame I believe. Due to a lot of mis placed posts. However, I do not find this to be mis placed. It is valid, and just the fact that it tried to run is great. farther then most have gotten, and the way I see it, any good inputs/thoughts should be welcomed warmly.
Sent from my Xoom using XDA Premium App
So now what I am trying to do is download, extract, and replace the hboot from http://www.megaupload.com/?d=VSFLE9CD with the 0.76 hboot, repack, resign, and test in the bootloader. This is all really simple stuff and thats why I am wondering if it will work. Because its so simple something like this was overlooked.
HipKat said:
Once you got back to the hboot menu, what version did it say you have?
If 2.10, I would think your next bet is try and run unrevoked
Click to expand...
Click to collapse
as far has my bootloader says for now it has the latest everything unfortunately. hboot 2.16 hw4 and all that. I was surprised that I was able to get passed the check without an error doing this though and its why I posted. I have 4 minutes left on the new PC63IMG.zip downloading before I can try to mess with it.
I tried this exact same thing just last night. It did the same thing to me as well, with it returning to the bootloader menu with no error msgs. If somehow we are able to edit the PC36IMG.zip file to match the hboot version 2.16 with the 3.70 update to pass security check then we may be on to something. But I'm not sure how to resign an IMG zip with HTC's signature to pass security. Thoughts?
sivarticus85 said:
I tried this exact same thing just last night. It did the same thing to me as well, with it returning to the bootloader menu with no error msgs. If somehow we are able to edit the PC36IMG.zip file to match the hboot version 2.16 with the 3.70 update to pass security check then we may be on to something. But I'm not sure how to resign an IMG zip with HTC's signature to pass security. Thoughts?
Click to expand...
Click to collapse
I am about to attempt now after signing the zip with kitchen.
spotopolis said:
I am about to attempt now after signing the zip with kitchen.
Click to expand...
Click to collapse
You will be my hero if this works.
Damn! Same thing. I loaded up the latest update with the older hboot renamed to match the new one it replaced. rezipped with normal compression, signed PC63IMG.zip with latest kitchen, it loaded the modded PC63IMG all the way in the bootloader and passed that, then started checking the file and then just went to the main menu again with no errors.
Is it possible that it is not doing anything because it thinks im loading up the same version it is running? Could I simply change another file to make the bootloader think Im uploading a newer version so it would take the update?
I guess you guys haven't heard the news, but you can't resign the damn thing with HTC's key because we don't have HTC's keys. As many have stated the focus should be temp root, then the bootloader shall fall. Cart before the horse kids.
That sucks. Oh well can't hurt that you tried.
Otta way to think out of the box. I hope u get somewhere with this buddy. I would love to help but I know nothing. Lol. I can make lock rings. That's bout it. Good luck
Sent from my PC36100 using Tapatalk
androidsupra said:
I guess you guys haven't heard the news, but you can't resign the damn thing with HTC's key because we don't have HTC's keys. As many have stated the focus should be temp root, then the bootloader shall fall. Cart before the horse kids.
Click to expand...
Click to collapse
I know that but if you don't sign with the kitchen it wouldn't have even gotten this far correct? So its something right? Even if it doesn't work, its another thing on the list that has been tried and maybe it will lead to something else. You never know with electronics. A single random chip could be made slightly different from others and it changes everything. No way to know until you try.
Do I really need to link every post where someone has tried to mod these files, I mean really...
There is a post about every three days on this same subject, it goes on for two days and then gets locked like this one will. And on the next day somebody else posts their marvelous idea of tricking the bootloader. And the cycle continues.
androidsupra said:
Do I really need to link every post where someone has tried to mod these files, I mean really...
There is a post about every three days on this same subject, it goes on for two days and then gets locked like this one will. And on the next day somebody else posts their marvelous idea of pricking the bootloader. And the cycle continues.
Click to expand...
Click to collapse
Is that not the point of this community? Someone trying to use some other persons idea and expand on it? Who cares if it ultimately doesn't work? Its information.
I have hw 003 hboot 2.10. I can enter hboot but not recovery. during normal boot phone just shows evo boot screen and boot loops. same thing when I try to enter recovery. I was s-off but after trying some methods in other brick threads I ended up with s-on.
I was using miui 2.2.3 when I turned it rebooted into recovery to make a nand and that is when the loops started. I have tried several ruu's with no luck on getting it to boot. was going to try the lastest ruu but not sure if I should.
I am flashed for cricket so there is not the option of bricking and returning to sprint for a replacement.
Edit: was not using twrp. Ar 2.3 was my recovery. As stated earlier I tried several ruu's in pc36img.zip.
If you can get to hboot you are not bricked. Have you tried using a pc36img of a stock rom in the hboot? This should boot you to a stock rom, thus allowing you to re-root and get your recovery back.
sitlet said:
If you can get to hboot you are not bricked. Have you tried using a pc36img of a stock rom in the hboot? This should boot you to a stock rom, thus allowing you to re-root and get your recovery back.
Click to expand...
Click to collapse
You can be bricked and still get in hboot Twrp2.0 did it to a few phones, the partitions end up screwed up and you can boot to hboot but no recovery or system not sure which partition gets borked but I think its the misc partition
We are legion, for we are many
Where is Captain_Throwback to save the day and another evo once again
Oh I am sure Captain will save the day soon as he always does.
That does not sound like fun man, sometimes the evos get crazy and there is nothing you can do about it. Did you do anything different before you had this issue? flash any files, adjust any system settings or mess with the hardware in anyway?
stevovanburen said:
Oh I am sure Captain will save the day soon as he always does.
That does not sound like fun man, sometimes the evos get crazy and there is nothing you can do about it. Did you do anything different before you had this issue? flash any files, adjust any system settings or mess with the hardware in anyway?
Click to expand...
Click to collapse
No i had been running miui for a few days and was getting prepared for the next update by doing a nand. I rebooted to recovery with the reboot option in the rom. Then bang boot loop city here i am. Just tried the newest ruu pc36img.zip and still nothing. Going to get it unlocked later and see if I can reflash .img files through fastboot.
Sent from my M865 using XDA App
You weren't using twrp2.0 were u? If you were more than likely SOL that's one of the main reasons twrp for the evo is no longer supported even tho it works great on other devices like the kindle fire and 3vo I use it on the KF which I have running cm9 which I just got running on the evo as well now I gotta get my kernel fixed for this thing, have you tried reflashing your recovery? Or using adb to push a boot.img
Sent from my PC36100 using xda premium
evo4gnoob said:
Where is Captain_Throwback to save the day and another evo once again
Click to expand...
Click to collapse
I know. Captain has become the shaman of the Evo. He needs a special title, like Honorary Genius, or something.
sent from AOKP heaven
You guys flatter me .
I don't have any experience with MIUI, though. It's the one ROM I've never tried, but if it's an AOSP ROM, then the bootloop of death is always a possibility.
We haven't had any success rescuing anyone in that scenario, unfortunately. Flashing the ENG HBOOT will allow you to run fastboot commands, though, so that's probably the first step if you want to flash stuff through fastboot.
If you can't get adb working, then there probably isn't much hope. Since you ended up S-ON, and now without a custom recovery, I don't think there's much you can do. Perhaps others with a similar issue can chime in, but as far as I know, there's no current solution. The only way I'd know for sure is having the phone in my hands personally, but I doubt that's a possibility. I haven't personally experienced this bootloop thing, but it sounds scary .
jlmancuso said:
No i had been running miui for a few days and was getting prepared for the next update by doing a nand. I rebooted to recovery with the reboot option in the rom. Then bang boot loop city here i am. Just tried the newest ruu pc36img.zip and still nothing. Going to get it unlocked later and see if I can reflash .img files through fastboot.
Sent from my M865 using XDA App
Click to expand...
Click to collapse
Ok so I have unlocked the bootloader from the htcdevelopers site and i can now use fastboot commands and have tried flashing the recovery. I see it load and write to the phone only thing is that it makes no difference. I still just get the boot loop.
Hate to say it, my friend, but I think it's the end of the road for that phone
HipKat said:
Hate to say it, my friend, but I think it's the end of the road for that phone
Click to expand...
Click to collapse
maybe but i will keep trying till the phone catches fire in my hands. I dont know the meaning of "quit". I read last night in a xda thread about a possible fix by this guy and some people said it would just brick the phone and others say it works. only thing is i have been unable to find that thread again. it had a link to some evo.docx file.
jlmancuso said:
maybe but i will keep trying till the phone catches fire in my hands. I dont know the meaning of "quit". I read last night in a xda thread about a possible fix by this guy and some people said it would just brick the phone and others say it works. only thing is i have been unable to find that thread again. it had a link to some evo.docx file.
Click to expand...
Click to collapse
I assume you're referring to this thread: http://forum.xda-developers.com/showthread.php?t=1480630
Have fun trying! Many have tried, and I think only 1 ever succeeded.
thanks captain.
capn, thanks for the link! I've had that README_EVO.docx file on my SD for god-knows-how-long and have always wondered where in the hell I got it lol (and 'why').
@jlmancuso
Good luck, but condolences as well. My $ says, if Cap'n can't fix it, it likely can't be fixed (on Evo). Seems that guy has explored every RUU, Hboot, recovery, NV, Radio, kernel etc. He could probably BUILD an Evo, HW and SW lol.
sent from AOKP heaven
Captain throwback just the person i want to see lol i have a evo with 2.18 hboot
with s-on the phone keeps boot looping wrote the wrong nv to the phone now its boot looping also used the latest ruu top no avail still boot loops now is there a way i can repair the nv please help me with your guiding light and also this phone is not rooted or no roms its all stock also says in purple at the top ***LOCKED (00w) *** what ever that means ??
fatalfury said:
Captain throwback just the person i want to see lol i have a evo with 2.18 hboot
with s-on the phone keeps boot looping wrote the wrong nv to the phone now its boot looping also used the latest ruu top no avail still boot loops now is there a way i can repair the nv please help me with your guiding light and also this phone is not rooted or no roms its all stock also says in purple at the top ***LOCKED (00w) *** what ever that means ??
Click to expand...
Click to collapse
I think someone else was able to fix this problem . . . there's a thread around here somewhere. I'll try and find it.
EDIT: This is the thread - you'll probably want to read the whole thing, and if you have issues, maybe you can PM the guy that got it working.
The potential problem I see for you is that you're S-ON and bootloader is locked. You're probably going to have to unlock your device with HTCDev.com before you can make any headway. How were you able to write NV items to the phone? Don't you have to be S-OFF to do that?
Captain_Throwback said:
I think someone else was able to fix this problem . . . there's a thread around here somewhere. I'll try and find it.
Click to expand...
Click to collapse
i remember you had them downgrade to the ENG hboot and they were able to use fastboot to change the NV ?
evo4gnoob said:
i remember you had them downgrade to the ENG hboot and they were able to use fastboot to change the NV ?
Click to expand...
Click to collapse
Yup. I updated my post above with the thread, but that guy was S-OFF, so it was actually possible. Not much you can do with S-ON and locked bootloader.
Captain_Throwback said:
Yup. I updated my post above with the thread, but that guy was S-OFF, so it was actually possible. Not much you can do with S-ON and locked bootloader.
Click to expand...
Click to collapse
use HTC dev to unlock then use your guide to downgrade then root with revolutionary then downgrade hboot ?
Howdy! Lemme preface all of this by saying that I'm less than a noob here....really inexperienced. Here's the background......
I rooted my DInc and I can't even remember which unrevoked tool I used. I was just reading along and punching commands and when the process was done I was rooted. I installed CWM successfully and flashed to CM7.2 which I've been running for quite some time. Lately I got an itch to try a JB ROM like infected, so when I looked into it, it clearly says I need S-off to accomplish that flash so I checked and realized I was S-on still.
At this point, I added the unrevoked-forever.zip to my sdcard root and tried to flash that ZIP by way CWM and i get these error messages:
E: unsupported radio version
E: update failed. Check/sdcard/soff.log
E: error in /sdcard/unrevoked-forever.zip (Status 42)
I am running Android version 2.3.7 and radio baseband version 2.15.10.12.20
Is this one of those things that I shouldn't be trying from CM7.2 and I should've dealt with before my initial flash to CM7.2?? Basically I'm totally freakin lost and in WAAAAY over my element, so any guidance would be duly appreciated. Thanks in advance!
Scott
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
PonsAsinorem said:
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
Click to expand...
Click to collapse
Sorry....i guess it pays to be extra thorough in the description of the problem. The link you left me is the one that I followed. I researched achieving S-Off on the DInc first and found this same page in my research. I followed the process and all went smooth right up until i started to flash the unrevoked-forever.zip from my sdcard via CWM. The aforementioned error messages came up on my phone and it said the process failed.
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
smvogel73 said:
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
Click to expand...
Click to collapse
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
PonsAsinorem said:
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
Click to expand...
Click to collapse
Yes thx....I'm gathering that! So this is where terminology gets so dang confusing for me. I didn't think unlocking my bootloader meant the same thing as achieving S-Off?? I already thought my bootloader was unlcoked, as I was able to flash CM7.2, which I didnt think I would be able to do if I had a locked bootloader. So wicked confused!!! And try as I miught to educate myself in these forums, I haven't located a sticky or guide that really thoroughly explains all the vernacular regarding android dev/modding/rooting/flashing/etc
So this other method will work with any radio baseband version then?? Or is it important to check compatibility there too??
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
PonsAsinorem said:
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
Click to expand...
Click to collapse
It says "UNLOCKED" and below that it says "S-ON
Thank u for the materials too!
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run. I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.
The ROM I'm looking to flash is Infection JB 4.2.2. The instructions say that if you're coming from. A non-AOSP ROM and are S-On that you've gotta extract boot.img and fastboot it after the ROM flash......whatever the heck that means???
smvogel73 said:
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run.???
Click to expand...
Click to collapse
Correct. Staying S-ON minimizes the danger. It locks your radio, and HBOOT, which are the main dangers.
smvogel73 said:
I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.???
Click to expand...
Click to collapse
Not really ROM flashing, but radio and HBOOT flashing, which is what unrevoked-forever tweaks.
I'd try to flash it one more time. When you do, what, if anything, are you wiping? You should be doing a factory reset, system, and boot wipe/format, then flash the ROM.
If that doesn't work (it might not, it's been awhile since I've worked with S-ON devices), then we'll move on to S-OFF (if you want).
Oh no.....I didn't even attempt to flash the Infection JB ROM specifically because I was not able to achieve S-Off. Whether it was intended or not, yea.....u sufficiently scared me about bricking the phone if I'm not to spec per the developer.
Are u saying I should wipe and then try to flash this ROM despite still being S-On?
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
PonsAsinorem said:
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
Click to expand...
Click to collapse
Well there you have it....I will trust your wisdom (as it is far supperior to my own) and I shall flash this ROM tonight!! I already have a nandroid backup of CM7.2 that Im running, as well as a Titanium backup of all my user apps/files.
Sincerest thanks for all your help!!
Hello. Im no expert but i think Cyanogenmod is aosp so you should be good.
I was where you were 2 yrs ago when I rooted my 1st phone: a friends froyo Dinc (ahhh...froyo). A few months ago I aquired my own and went to research how to root GB and everything has changed and is now vastly more complicated. Also I think every phone has a locked bootloader but not encrypted and I think Soff is extra security since I've only encountered it on htc phones. Anyway I've managed to get my inc to Soff but its still locked, idk how lol
Sent from my ADR6300 using Tapatalk 2