Related
Just noticed this when I was browsing through an old Desire ROM, I know we can't downgrade HBOOT but if we do manage to be able to find a way to do it, maybe this HBOOT will have R/W access, I really do not know, just throwing it in to the wild.
AdamG said:
Just noticed this when I was browsing through an old Desire ROM, I know we can't downgrade HBOOT but if we do manage to be able to find a way to do it, maybe this HBOOT will have R/W access, I really do not know, just throwing it in to the wild.
Click to expand...
Click to collapse
We can now http://android.modaco.com/content/htc-desire-desire-modaco-com/310970/how-to-downgrade-hboot/
Didn't realise someone found it already, thanks for the update.
I understand the downgrade method, but does this SPL have to be put into an RUU for it to be flashable? Or is there another method I can use to flash it?
Just tweeted Paul about this, i hope this is a good development
Guys its not S-OFF or less protected, its simply from a usedebug RUU released a long time ago. As described in my rom I already have it and tested all the different things to see if its less protected, which it was not.
Yeah Paul just confirmed it on twitter, dead end im afraid;(
i have installed the gingerbread keyboard file on my sd card and have rooted my phone using the visonary method but now i cant seem to get into recovery mode. I have rom manager installed and have flashed clockwork recovery mode. it said that it had sucsessfully installed.
I then flashed it again as i read somewhere that i might need to do it twice as sometimes it dosent work.
when i now click on the recovery option in rom manager all i get is the red triange with the ! in the middle.
any ideas what im doing wrong?
Have tried reading the threads but with 30 plus pages i am now completley confused
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this
just done the hboot hing and at the top of screen it says
vision pvt ship s-on
hpsauce37 said:
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this
Click to expand...
Click to collapse
It's a bit confusing because there is more than one way to do this. But by far the safest way is to follow the guide at http://forum.xda-developers.com/showthread.php?t=857390
Have a good read, then if you're not sure, ask questions in that thread on the process.
steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Click to expand...
Click to collapse
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?
steviewevie said:
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?
Click to expand...
Click to collapse
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Click to expand...
Click to collapse
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.
steviewevie said:
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.
Click to expand...
Click to collapse
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro
Click to expand...
Click to collapse
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.
im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems
hpsauce37 said:
im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems
Click to expand...
Click to collapse
Have you tried my guide on adb ? http://forum.xda-developers.com/showthread.php?t=865685
OK, I can use some help too
I have a DZ with stock ROM, root and s-off and CWR.
In my enthusiasm that I knew how to flash rom updates with clockwork (I am running the Godspeed 1Ghz) I downloaded the Gingerbread keyboard rom update from the G2 forum. I think I jumped off a bit too fast...
And now I am stuck in an infinite boot loop. I can get into Clockwork recovery but it just loops the "HTC Quietly Brilliant" forever including the annoying boot sound...
I tried some suggestions to download and reflash a second time, no effect.
I tried to mount /system before flashing, no effect.
Am I forced to go back to factory now?
Also, I found 2 gingerbread keyboards, one in the G2 forum and one over here.
Anyone know what the difference is? They have a different filesize..
Any help is welcome...
*edit*
OK so now I read that it is only to be flashed on a non-stock ROM... so I am now flashing Cyanogen 6.1
try wiping all the caches...
Lennyuk said:
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.
Click to expand...
Click to collapse
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Click to expand...
Click to collapse
S'alright.
HTC really ramped up the security on these new phones, as Lenny said, with this hardware write-protection on certain partitions. But even given that, I was amazed by just how quickly the guys on the #G2ROOT IRC channel, especially Scotty2, managed to crack it !
It also looks like they've opened the phone even wider than many others before, with the "true" radio S-OFF that they achieved.
You can read up all about it in the Wiki - http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
Good evening.
I'm new to the forum, so I hope it's ok that I ask a question as the first thing?
(Oh and bear over with my english as it is not my main language)
I'm quite sure you guys get this question quite alot, but it is a bit hard for me to collect the necessary information needed for me to start working on my "problem".
My plan is too root my newly aqquired HTC Desire HD.
As an added information: I already temporary rooted it using the VISIONary+ application and that seems to work as it should. I can get root rights and everything. So far so good - I havn't tried using the permanent root option that this program allows as I want to know exactly what I am doing before doing anything (I heard all the scary stories of bricking and stuff)
So let's start out with the questions:
- How do I check what firmware, kernel, ect ect ect I've got so that I can get the necessary information?
- How do I know if it is branded or not? (Not sure what that even means... I live in Denmark and bought it at the shop, and it is not simlocked. Phone company is Telmore)
- Where the hell should I start?
I looked up this guide: wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Full_Update_Guide#Flashing_Radio
Would that help me?
Also looked at this: androidpolice.com/2010/04/16/complete-guide-how-to-fully-back-up-and-restore-your-android-phone-using-nandroid-backup-and-clockworkmod-rom-manager/
Could I just perma root with VISIONary+ without worrying and then using rom manager to get the recovery image on and stuff or is it better doing a manual root somehow?
Oh and by the way, I already got adb access to my phone through the pc!
(And please tell me if this is the wrong section of the forum.)
Thanks in advance!
I guess the first question is, did you purchase the telus desire hd in canada per chance?
The firmware /kernel info can be found in the about phone section of the settings menu.
As for rooting I personally favour the manual root specified by the good folks over at CyanogenMod here if you find that a bit daunting there are some automated one click tools over in the Development forums here on XDA, although most require that you have access to a computer running windows.
equlizer said:
I guess the first question is, did you purchase the telus desire hd in canada per chance?
Click to expand...
Click to collapse
Nope. It was bought in denmark.
Dunno if it's a telus model or anything (As I have no idea what a telus is lol)
Some Information about my device: (Btw I'm trying to translate from danish. So ask if something sounds wrong)
- Android Version
2.2
- Basebandversion
12.28b.60.140eU_26.03.02.26_M
- Kernelsystem
2.6.32.21-gf3f553d
[email protected] #1
Thu Oct 28 13:24:11 CST 2010
- VersionNumber
1.32.405.6 CL278359 release-keys
- SoftwareNumber
1.32.405.6
- Browser version
WebKit3.1
As far as I can see my VersionNumber (I guess that is my firmware??) matches the one that the cyanogenmod guide (As In I dont need to downgrade yay!):
wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Full_Update_Guide
Asks for.
Is there anything else I should check for before I begin, or would that be the guide I should follow?
Plus I forgot to say:
I'm pretty good with computers in general. So I don't care using an "advance" manual method as long as it is descriped well so I don't end up saying "Wait what? Where the hell should I go now?"
So no need to doing some noobish way (Not saying One click methods are noobish) I just need to know what to do and how it should be done.
ok for starters, dont worry about bricking, it's impossible to brick your device trying to root, infact there are only 2 ways you can brick your device, and thats flashing a radio or hboot you have the 1.32 software version and that can be easly permrooted using visionary, after you root, you may want to s-off aswell
AndroHero said:
ok for starters, dont worry about bricking, it's impossible to brick your device trying to root, infact there are only 2 ways you can brick your device, and thats flashing a radio or hboot you have the 1.32 software version and that can be easly permrooted using visionary, after you root, you may want to s-off aswell
Click to expand...
Click to collapse
First off, thanks for the quick help! *thumps up*
So I don't have to use the CyanogenMod guide? (would it be better if I did it that way?)
Or is it enough with a perm root with VISIONary?
Then after that I'm thinking of doing a backup (It's called Nandroid as far as I've read?)
Doing a perm root with VISIONary, followed up by flashing the recovery image using the one click option that ClockWork ROM manager allows.
Would I have to worry about doing that, or does my information say that my model should work perfectly fine with that?
I think it's quite important to say that I'm thinking of doing a Custom Rom later, but my first job is to get it rooted and backed up incase anything happens.
Oh and, how would I manage to do a s-off after I've got it rooted? Would that have to be done BEFORE doing the flashing of the recovery image and doing a backup?
you can use the Cyanogen method, thats just a manual way, i used visionary, and have had no problems at all, just click the permroot option and wait after you root, before you flash a custom recovery you need to s-off, this is because the nand chip has write protection, check out this thread http://forum.xda-developers.com/showthread.php?t=855403 jkoljo tool is awsome and although flashing a hboot is dangerous, no1 has bricked there device using his tool yet, thats how safe it is once you are s-off, you can download rom manager and flash a custom recovery
I can see that the tool is called "One click ENG s-off" as in ENGLISH.
Does it matter that my phone is bought in denmark and is in danish?? (Does the language matter at all? :O)
virtual-aidz said:
I can see that the tool is called "One click ENG s-off" as in ENGLISH.
Does it matter that my phone is bought in denmark and is in danish?? (Does the language matter at all? :O)
Click to expand...
Click to collapse
the ENG means engineering, there are two types of s-off, engineering s-off and Radio s-off, the engineering one allows you to issue fasboot commands though and the radio one dosent, either one will security unlock your bootloader though
Ah I see
I just noticed in the s-off guide: "tick "I have Radio S-OFF" in the tool"
Why do I have to tick that? I don't have Radio S-OFF? :O
And right now I can't even test out what we are talking about *sadface* I just noticed a dead pixel right in the center of the screen, so before I start messing around, I'm gonna take it to the shop and see what they say (God I hate dead pixels)
I know it's a bit (well alot) besides the subject, but I was just crossing my fingers that you were a dead pixel specialist and could answer a simple question: Would a dead pixel on a 1 month old phone (I think the pixel is red, but it could be black as in completly dead) have any chance of spreading or something?
Cause I could live with a single dot.. but if it has a chance of spreading, I would really wanna get it fixed before it's too late (And sorry for the off-topic in my own thread xD)
Notice the big OR in the requirements part? As you are not using a custom ROM, and you do not have Radio S-OFF, you should not tick it.
Dead pixels do not spread, and there are apps in market to revive dead pixels, you should try one of them.
jkoljo said:
Notice the big OR in the requirements part? As you are not using a custom ROM, and you do not have Radio S-OFF, you should not tick it.
Dead pixels do not spread, and there are apps in market to revive dead pixels, you should try one of them.
Click to expand...
Click to collapse
Haha... My bad.
As I mentioned in my first post, my main language is not english. So I misunderstood what it said
I think I'm ready now.
Just need to talk with the shop before I void the warranty for good.
Thanks for the help guys, and I will return when I get it working (or **** it all up.. who knows)
By the way, root, S-OFF and custom ROMs do not void warranty. It says nothing about software in the warranty terms, check it out yourself if you want to
Odd. There has been multiple cases where they did not fix phones that were just rooted.
jkoljo said:
By the way, root, S-OFF and custom ROMs do not void warranty. It says nothing about software in the warranty terms, check it out yourself if you want to
Click to expand...
Click to collapse
Oh and by the way. I see you're the creator of the s-off and radio s-off tools?
Is it true that you recommend Radio S-off (forum.xda-developers.com/showthread.php?t=857537)?
And how do I check if I meet all the requirements?
jkoljo said:
By the way, root, S-OFF and custom ROMs do not void warranty. It says nothing about software in the warranty terms, check it out yourself if you want to
Click to expand...
Click to collapse
actually it does............. "use of products, equipment, systems, utilities, services, parts supplies, accessories, applications, installations, repairs, external wiring or connectors not supplied or authorized by HTC" ........ custom bootloader, and software can come under the systems, applications and installations
Ah yay. I thought so
As far as I can see on the Radio S-Off (Again, is it recommended over s-off?)
System requirements:
Windows XP SP2 or higher
.NET Framework 4.0
HTC Sync (or ADB drivers)
Desire HD with stock kernel (or Apache14's 1.0.7 / 1.1.4 Sense)
It will not work on 1.72.405.3 or higher build, or new radio. Downgrade first!!
I got the 3 first ones covered.
But I'm not sure about the two last.
My Phone has HTC sense, but I dunno what version to be honest.
And I guess I got the last one covered too as I got the 1.32.405.6
You meet all the requirements
AndroHero said:
actually it does............. "use of products, equipment, systems, utilities, services, parts supplies, accessories, applications, installations, repairs, external wiring or connectors not supplied or authorized by HTC"
Click to expand...
Click to collapse
Please take a picture for me, that is not included in the warranty statement that came with my phone. I rang HTC about it, and they said that unless the hardware is modified, software does not matter. Also mike1986 sent his phone to be repaired with ENG S-OFF and everything, and nobody complained.
jkoljo said:
You meet all the requirements
Please take a picture for me, that is not included in the warranty statement that came with my phone. I rang HTC about it, and they said that unless the hardware is modified, software does not matter. Also mike1986 sent his phone to be repaired with ENG S-OFF and everything, and nobody complained.
Click to expand...
Click to collapse
How did you know I met the requirements with the HTC sense?
(I need to learn too)
Ok guys might need a bit of help..
Not too familiar with this handset really but flashed my phones a million times without problems...till I set about the missus's phone yesterday.
Its a 3 UK branded desire..was HBoot 0.83
Went through the S-Off/root/Recovery/Hboot upgrade procedures...and all looked good.
Till I came to actually flashing ROMs.. and tried a couple. Just bootlooped on the AlphaRev screen for all.
So decided to drop back to stock through HBoot... the stock ROM flashes with apparently no errors reported, but again fails to boot. And AlphaRev HBoot doesn't get overwritten..although Recovery's gone.
Anyone know how to proceed?
First of all by reading the tutorials carefully before proceed, to avoid any trouble
Get the latest RUU for your Desire (3UK) and save it somewhere.
Before you flash it, download the HBOOT Downgrader from Alpharev.nl.
Flash the Downgrader first, then the RUU.
And what do you mean the recovery is gone? Are you still S-OFF? You can flash a recovery with the Android Flasher tool in the Development secton.
And What ROMs did you try that all failed you?
You probably forget one ot two steps when flashing.
Ain't no noob buddy so need to cut and paste the standard response guys!
Did all them things so that's why I'm asking..and yes despite being over flashed with the RUU s-off is still there. That's what I meant by the alphrev hboot not being overwritten.
However..the downgradues worth a try....
DJW6927 said:
Ain't no noob buddy so need to cut and paste the standard response guys!
Click to expand...
Click to collapse
And that's how being rude will cut the number of replies you get...
No rudeness intended..but RTFM is no help either under the circumstances.
I've been doing this for years since my tytn.
I really appreciate the help I really do..the downgrade suggestion ain't in the guide...and seems a good idea. Will try soon as I'm home.
Ha. It ain't going well... worse in fact.
Downgraded HBoot and flashed RUU...screen won't turn on. But RUU can still just talk to it. Flashing again. But still the same.
Vol down makes it vibrate now...but not much else!!
Edit: Hum...my first brick I think! Think the wife might be gettin an upgrade.
Edit again: Screen blank but the RUU program still sees the phone. Fails to revive it mind you. Only outward sign of life is a pulse vibrate on the power button being depressed after a battery pull. Anyone seen this?
Slcd brick?
Swyped from my CM7.1 Desire using XDA Premium App
timmaaa said:
Slcd brick?
Swyped from my CM7.1 Desire using XDA Premium App
Click to expand...
Click to collapse
Elaborate my friend? The 0.83 bootloader might indicate it has a sLCD... but only might I understand. Is there a history of issues with SLCD screens?
I gotta go to work..in Holland..but I'll still be checking in here for any information. It may very well be bricked but I'm still interested from a technical aspect.
DJW6927 said:
Elaborate my friend? The 0.83 bootloader might indicate it has a sLCD... but only might I understand. Is there a history of issues with SLCD screens?
I gotta go to work..in Holland..but I'll still be checking in here for any information. It may very well be bricked but I'm still interested from a technical aspect.
Click to expand...
Click to collapse
Which RUU did you flash? If your phone has a SLCD screen, it might be a possibility that you've flashed an AMOLED RUU to your SLCD. Thus you will get a SLCD brick which makes you unable to view anything on the screen but the phone is working normally. It's reversible by following a SLCD unbrick guide.
Sent from my HTC Original Desire using Tapatalk
DJW6927 said:
Elaborate my friend? The 0.83 bootloader might indicate it has a sLCD... but only might I understand. Is there a history of issues with SLCD screens?
Click to expand...
Click to collapse
This is all basic, well documented stuff you seem to be completely unaware of. Perhaps RTFM is exactly what's needed here.
Thankyou very much indeed to those who who pointed me in the direction of slcd. Now I know what to search on finding the information I need is straight forward. Really good stuff.
Thanks very much too to those who provided the ex-wife service too. Unfortunately I always know where to get advice like that
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