I was wondering if it would be possible to flash a ROM without an S-OFF hboot. The logic is as follows:
The NAND lock is performed by the hboot.
Flashing is performed by the recovery OS.
We can now disable the NAND lock using a kernel module regardless of the hboot.
Could the recovery OS disable the NAND lock and flash a ROM without using an S-OFF hboot?
There are a few reasons against flashing the S-OFF hboot, namely, it's less risky, and easier to revert to factory if a warranty claim needs to be made.
Simple answer NO.
Long answer, you can't flash a custom rom without a custom recovery.
You can't flash a custom recovery without and unlock hboot.
So what ur saying will not work because u will not be able to flash the recovery.
Also no risk if u follow the steps. And reverting is as easy as running pc10img
Also this needs to be move to gen thread
Sent from my T-Mobile G2 using XDA App
Technically, you can probably use dd to reflash the recovery partition instead of hboot, which would allow you to install custom ROMs because the NAND is always unlocked in recovery.
But nobody is going to do that, and there are catches: even then you still can't write to /system without Android without the hack S-OFF is best.
I agree that S-OFF is best, but there might be people who are reluctant to flash an hboot. I figured ROMs can include the kernel module that disables the lock, so they would be able to write to /system.
If it's easy to restore to factory though, I guess there isn't much point in working around the lock all the time like that. S-OFF it is then.
If I missed it, would it be possible to go S-OFF, flash a custom ROM, then go S-ON again?
ok this is a debate i had going on in dz forum. you can flash clockwork recovery via rom manager and prob dd cmd after running the wpthis.ko. you can also perm root it as we know. it has been done in dz forum.
now i agree with you. at this point you should be able to boot into recovery and flash whatever you want and have perm root. however WP will still be on when booted into andriod which can be good and bad depending on how you look at it. (noobs vs pain in ass). this leaves u 2 options. reboot to recovery for any changes, or run the wpthis.ko make changes, reboot.
that being said. heres the prob with having s-on. if you screw up your phone you have less of a chance fixing it. (currently helping someone in this position).
ot anyone know of stock rom in update.zip format?
xile6 said:
You can't flash a custom recovery without and unlock hboot.
Click to expand...
Click to collapse
That's not true......i'm proof
Would need atleast a recovery which uses test keys or simply ignores them.
With the wpthis.ko u could dd other imgs but not enough for a rom as you can not access the system while you are on it.
If you had an S-off hboot u can atleast fastboot the images without the recovery.
Right?
Sent from my T-Mobile G2 using XDA App
Related
Is there a way to confirm NAND unlock? I was initially rooted with unrevoked and then in order to attempt to flash a custom ROM used simple root. As far as I can tell the simple root worked -- the problem is now I have tried 2 custom ROMs (baked snack AND fresh) and both just continue to loop on boot up (I did clear cache etc a few times and reloaded).
My thought is now that I wasnt rooted properly, any ideas/suggestions?
Boot into bootloader and look at your HBOOT. If it's 76 you're NAND is unlocked
oh that was easy, thanks. Now I just have to figure out why it keeps looping. annoying the hell out of me
Would I be correct to say that your hboot version is not 0.76.2000? If so, then that might explain your bootlooping problem. Most custom ROMs need nand unlocked in order to flash properly.
Sent from my PC36100 using XDA App
Also above the version it will say S=OFF if your nand is unlocked, S=ON is locked.
What recovery are you using? I think some people have been having trouble with Clockwork
samrat123 said:
Is there a way to confirm NAND unlock? I was initially rooted with unrevoked and then in order to attempt to flash a custom ROM used simple root. As far as I can tell the simple root worked -- the problem is now I have tried 2 custom ROMs (baked snack AND fresh) and both just continue to loop on boot up (I did clear cache etc a few times and reloaded).
My thought is now that I wasnt rooted properly, any ideas/suggestions?
Click to expand...
Click to collapse
what happens if you do a: "adb remount" (from a loaded ROM)
I have htc legend rooted
and my HBOOT 0.43.0001
what does it mean?and what is it s-on\s-off?
The HTC Legend, when rooted using the usual methods doesn't really have access to the System partition.
In order to have access to this, you have to have a "S-OFF" or "Security-Off" Phone.
S-on means that there is the default protection that prevents you to write to /system and /recovery partitions. If you want more information you can visit alpharev site: http://alpharev.nl
What are the benefits?
You can alter the files from the protected partitions as if they were on a sdcard for ex. No more "read only" rights, and so on.
Sent from my Legend using XDA App
Meocene said:
What are the benefits?
Click to expand...
Click to collapse
Rapier said:
You can alter the files from the protected partitions as if they were on a sdcard for ex. No more "read only" rights, and so on.
Sent from my Legend using XDA App
Click to expand...
Click to collapse
With great power, comes great responsibility. It's a great tool (I'm S-OFF, myself) but just be careful.
I understand what turning the security off enables.
But what are the benefits?
Personally, I haven't found any benefits to being S-OFF.
I've found that using the Clockwork Recovery doesn't work sometimes and it's handy to have a PC handy just in case...
With s-off you can edit files in the /system partition without the need of switching to recovery, but i don't think that it is a functionality needed by many people.
If you have s-off you can also flash a recovery, therefore you won't need anymore to use fake-flash for booting in clockworkmod.
On some rooting guides for phones like the DHD it says you need to be S-OFF to flash a custom ROM. How come we've been doing this on our S-ON Legends? I don't understand how being S-OFF is any different than S-ON for a Legend user?
I've probably got the wrong end of the stick here...
EDIT: Something to do with ROMs having to be signed by HTC, but none of the custom roms for Legend have to be used on an S-OFF phone despite not being signed by HTC?
S-OFF unlocks the bootloader, you can install basically anything on any partition on the phone. This lets us install a custom recovery in the recovery partition. It also allows to boot custom kernels without flashing them (I believe)
Rooting with S-ON just allows you to boot a custom ROM with root access and no read/write capabilities in the /system partition (unless you have aufs)
S-OFF unlocks the bootloader, you can install basically anything on any partition on the phone. This lets us install a custom recovery in the recovery partition. It also allows to boot custom kernels without flashing them (I believe)
Rooting with S-ON just allows you to boot a custom ROM with root access and no read/write capabilities in the /system partition (unless you have aufs)
Click to expand...
Click to collapse
You can flash custom Kernels without being S-OFF. Done it myself many, many times. You don't need to be S-OFF to flash kernels.
S-ON as you said, gives read/write access to the /system partition while the phone is running. Unless you're looking at theming the phone yourself, or you want to access the /system and /recovery partitions it's not really required.
As I mentioned previously, I can get into recovery via Clockwork, but it's spotty, and I don't really like the idea of flashing a new ROM if I'm not near a PC that can drop me into Recovery. Rambo, I am not!
S-on means that there is the default protection that prevents you to write to /system and /recovery partitions. If you want more information you can visit alpharev site: http://alpharev.nl
Click to expand...
Click to collapse
Hats off to entropicamente for posting the above - it's THE best place to go. I would warn that if you're a Bell Legend user, the download there will not work. There's a download on this forum for the .iso to S-OFF your phone.
Ultimately, with the number of "What benefits does this give me?" questions, it should probably be avoided for now.
entropicamente said:
With s-off you can edit files in the /system partition without the need of switching to recovery, but i don't think that it is a functionality needed by many people.
If you have s-off you can also flash a recovery, therefore you won't need anymore to use fake-flash for booting in clockworkmod.
Click to expand...
Click to collapse
probably wrong, but i don't think i am using fake flash...
my legend's s-on, but to get to clockworkmod i just boot in through rom manager...
(guessing someone's about to tell me that that is fake flash...)
EDIT: missed marclh1992's post.
so in other words i'd be able to replace the stock htc recovery (accessed holding back+power) with clockworkmod, for example?
Yes, you can install clockwork mod into your recovery partition if you are S-OFF.
Sent from my S-OFF Bell Canada HTC Legend.
would I flash the CWM recovery image with fastboot? Where can I find the .img. I can only find the CWM recovery as a zip
joggerman said:
would I flash the CWM recovery image with fastboot? Where can I find the .img. I can only find the CWM recovery as a zip
Click to expand...
Click to collapse
Look in the development section. There is a thread called "Recovery 3" .. there you will find the .img file..
Sent from my Legend using XDA App
many thanks
is this why the busybox installer from the market cant do its work on installing busybox? i'm s-on tho....
does having superuser mean you phone is S-OFF ?
vip333 said:
does having superuser mean you phone is S-OFF ?
Click to expand...
Click to collapse
No, superuser just lets you "log in" to the root user account. S-OFF allows you to write to any part of the phone essentially. Among other things.
hi!
i found a shop in my area (slo) to unlock my phone. but i'm a bit confused. if i get my phone s-off-ed, as i understand this means full system root, which should men i should be somehow able to flash clockwork mod and then custom roms. this should be done by downgrading to 2.1 and hboot 0.8x.
i found a video tutorial on downgrading here:
http://forum.xda-developers.com/showthread.php?t=981765
and my question: shouldn't i be able to flash clockworkmod directly (without downgrading), since i will have my phone fully unlocked? if possible, how?
I think the best is after the s-off, install and older RUU, then use unrevoked 3.14 thats the most easy and i think the safest way
Most efficient way
hans3103 said:
I think the best is after the s-off, install and older RUU, then use unrevoked 3.14 thats the most easy and i think the safest way
Click to expand...
Click to collapse
May I suggest more efficient way: http://forum.xda-developers.com/showpost.php?p=12188132&postcount=15
Can you please tell me which shop. I'm from Slovenia too... Maybe you just see my private message.
Tnx
<edit>
never mind got me a xtc clip and found out the hard way
using the search function has help me more than making noob questions, sorry
dailor said:
May I suggest more efficient way: http://forum.xda-developers.com/showpost.php?p=12188132&postcount=15
Click to expand...
Click to collapse
Hi
I have rooted wildfire with s-off (xtc clip) and Hboot - 1.01.0002 . I tried the above method but fastboot wont detect the zip file and says not found. I am unable to install clockworkmod using rom manager, whenever i do, i get the red traingle of death.
What to do now ?
Please help...
u donot need to downgrade with an RUU. and further doing so may make ur phone S-ON again (im not sure about this).
u have a simple process.
u can flash any "recovery image" via fastboot mode.
and that's all, after doing that u can flash any rooted custom rom from that recovery.
getting to S-OFF is an expensive task yaar (as far as now). try to keep it in S-OFF permanently.
dailor said:
May I suggest more efficient way: http://forum.xda-developers.com/showpost.php?p=12188132&postcount=15
Click to expand...
Click to collapse
rishabhd said:
Hi
I have rooted wildfire with s-off (xtc clip) and Hboot - 1.01.0002 . I tried the above method but fastboot wont detect the zip file and says not found. I am unable to install clockworkmod using rom manager, whenever i do, i get the red traingle of death.
What to do now ?
Please help...
Click to expand...
Click to collapse
have u done the "PC49IMG.zip" process with the file in the above link. it is the process for flashing clockwork mod "recovery image". once this is successful, then u can install any custom roms from the CWM recovery.
note: donot do the PC49IMG.ZIP process with any outside file (excluding the link above). if u do that, u might loose the S-OFF
Alternatively, u can flash other recoveries also (i dont know any others)
I got it eventually, I downgraded using ruu rom to hboot. 80 rooted it again and now have 2.3.3 over it
Thanks anyways ..
Sent from my HTC Wildfire using XDA App
bharatgaddameedi said:
have u done the "PC49IMG.zip" process with the file in the above link. it is the process for flashing clockwork mod "recovery image". once this is successful, then u can install any custom roms from the CWM recovery.
note: donot do the PC49IMG.ZIP process with any outside file (excluding the link above). if u do that, u might loose the S-OFF
Alternatively, u can flash other recoveries also (i dont know any others)
Click to expand...
Click to collapse
How will you lose s-off by flashing a PC49IMG.zip? XTC Clip wipes the secuflag in radio NVRAM, no way of getting it back via a normal update.
edit: never mind........
edit: never mind...........................
Rooted with the "check this out even if" thread. Worked fine, found out that gfree doesn't root, but that visionary is what actually roots you when using it for teh second time after gfree turns radio security off. (had su denied in terminal a few times after gfree until I ran visionary and rebooted twice- it finally took)
So a big thanks to everyone.
The question is- at the end of the above thread, it says 0.85 bootloader is not necessary to flash a rom (i'm on royal ginger now so i know that), but that it would help avoid bricks in the future. Meanwhile, on the CM wiki for MT4G, it goes thru the abd rooting method, and it says that bootloader is not recommended.
Now, which is it? I don't want one of these
http://forum.xda-developers.com/showthread.php?t=1028615
where I read that there's people who flash one rom a single time like royalginger 1.6, then want to goto CM7.02 or vice versa, and that's all it takes to get in some boot loop. Now it might be that they're not wiping everything they should wipe, or wipe once instead of twice (which shouldnt be necessary), but it still makes you wonder.
Should I flash the 085 bootloader? Running fine on RG1.6, but may try CM 7.02 or RG2.0 when it's out of testing...
Thanks
acsi007 said:
The question is- at the end of the above thread, it says 0.85 bootloader is not necessary to flash a rom (i'm on royal ginger now so i know that), but that it would help avoid bricks in the future. Meanwhile, on the CM wiki for MT4G, it goes thru the abd rooting method, and it says that bootloader is not recommended
Click to expand...
Click to collapse
The engineering bootloader is not required, but some of us do recommend it. IF you should have something go south you can flash recovery images, sections of the ROM, erase sections of the ROM, clear stuff. It helps if you should run into a problem. Their have been a few threads that people would of bricked their devices if they didn't have it.
The final choice is up to you. But if it were my phone i'd do it. If you are worried about the code you have to punch in to unlock it, just double and triple check it.
hmm... what is it specifically that i cant do if i don't flash the engineering bootloader?
my partial answer to my own question is that i cant use fastboot commands thru adb, right? but i dont fully know what the heck fastboot is anyway.
also, what about the pdimg15 thing? is that not possible to flash back to stock with pdimg15 if i dont have the 085 bootloader?
anything else i cant do without H085?
acsi007 said:
hmm... what is it specifically that i cant do if i don't flash the engineering bootloader?
Click to expand...
Click to collapse
You cannot flash specific sections of the ROM if something should go south. You cannot flash recovery images via the HBoot, and you cannot flash splash images.
acsi007 said:
my partial answer to my own question is that i cant use fastboot commands thru adb, right? but i dont fully know what the heck fastboot is anyway.
Click to expand...
Click to collapse
fastboot = hBoot = Engineering Screen.
Basically it what allows you to flash items via the Engineering screen. You cannot mount sections of the ROMs, nor can you clear stuff out if you should so choose.
acsi007 said:
also, what about the pdimg15 thing? is that not possible to flash back to stock with pdimg15 if i dont have the 085 bootloader?
Click to expand...
Click to collapse
You can flash the PD15IMG via either recovery image. but it appears that if you use the 3.0.0.5, 3.0.0.6, or the 3.0.2.4 recovery image while trying to flash the PD15IMG (via the HBoot) it will brick your device. So that is not always a fail safe method.
basically the .85 HBoot a BIG tool to help you not brick your device.
thanks so far.. ok, im getting convinced. here's my reference for an eventuality where i'd need to rescue myself from some boot loop and reflash stock
http://forum.xda-developers.com/showthread.php?t=924923
so, in continuing to try to understand recoveries and boot screens here, i saw that after step three in the above thread, it says
"Some times at the end it will boot into fastboot rather then hboot. If this happens just scroll to bootloader and boot into it."
but then you wrote "fastboot = hBoot = Engineering Screen."
so why does the guide say "rather"? (indcating "does not equal")
second, you wrote
"You can flash the PD15IMG via either recovery image. but it appears that if you use the 3.0.0.5, 3.0.0.6, or the 3.0.2.4 recovery image while trying to flash the PD15IMG (via the HBoot) it will brick your device. So that is not always a fail safe method."
"either recovery image" -- you're referring to Clockwork Mod recovery and hboot?
And if you've seen that 3005 - 3024 may brick a PD15IMG flash, then what-- you dont go through Clockwork mod screen at all, you boot into hboot instead?
thanks for slogging thru this so i can get to my "aha!" moment....
acsi007 said:
thanks so far.. ok, im getting convinced. here's my reference for an eventuality where i'd need to rescue myself from some boot loop and reflash stock
http://forum.xda-developers.com/showthread.php?t=924923
so, in continuing to try to understand recoveries and boot screens here, i saw that after step three in the above thread, it says
"Some times at the end it will boot into fastboot rather then hboot. If this happens just scroll to bootloader and boot into it."
but then you wrote "fastboot = hBoot = Engineering Screen."
so why does the guide say "rather"? (indcating "does not equal")
Click to expand...
Click to collapse
when we are talking about booting into Recovery, or the Engineering screen. Fastboot, hBoot, and Engineering screen are all pretty much one in the same. Just like some people call softdrinks, "pop", "soda", or "coke". It's terminology. the reason for the "Some times at the end it will boot into fastboot rather then hboot. If this happens just scroll to bootloader and boot into it." Is even though are in a "bootloader" screen the phone must pick up and recognize that you want to use fastboot. so sometimes, not typical though, you must select the "fastboot option".
acsi007 said:
second, you wrote
"You can flash the PD15IMG via either recovery image. but it appears that if you use the 3.0.0.5, 3.0.0.6, or the 3.0.2.4 recovery image while trying to flash the PD15IMG (via the HBoot) it will brick your device. So that is not always a fail safe method."
"either recovery image" -- you're referring to Clockwork Mod recovery and hboot?
Click to expand...
Click to collapse
Correct there have been several threads popping up that are pointing to people have bricked their devices by flashing the PD15IMG in the Engineering screen but they are using the wrong recovery image. It always said something to the degree of "fail -PU". One guy was able to fix his by flashing the 2.5 recovery image from the Engineering screen then flashing the PD15IMG.
acsi007 said:
And if you've seen that 3005 - 3024 may brick a PD15IMG flash, then what-- you dont go through Clockwork mod screen at all, you boot into hboot instead?
thanks for slogging thru this so i can get to my "aha!" moment....
Click to expand...
Click to collapse
Yes to flash the PD15IMG you need to be in the Engineering Screen. but from reading that other thread you need the 2.5 recovery image to do it.
neidlinger said:
Yes to flash the PD15IMG you need to be in the Engineering Screen. but from reading that other thread you need the 2.5 recovery image to do it.
Click to expand...
Click to collapse
Wow- so I have to get rid of 3024 and flash cwm2545 (or whatever that exact number is) to use the pd15img that's so important to regaining control over a hypothetical borked flash?
acsi007 said:
Wow- so I have to get rid of 3024 and flash cwm2545 (or whatever that exact number is) to use the pd15img that's so important to regaining control over a hypothetical borked flash?
Click to expand...
Click to collapse
i think we are on two different wave lengths.
one of the first Clockwork recoverys that came out where for 2.2 style ROMs, where store information in an EXT3 format. When Google released 2.3 we needed a new recovery image to flash the EXT4 design that the 2.3 ROMs bring. 3.0.0.5 will only handle 2.2 ROMs 3.0.0.6 and 3.0.2.4 will do both.
The problem lies in the fact that EXT3 and EXT4 ROMs store and handle information differently.
using the recovery image while trying to load the PD15IMG will cause the load to fail.
Now if you have the engineering screen loaded you can manually load the 2.5.1.4 recovery image via the Engineering screen then flash the PD15IMG and all should be good.
But this is only if you need to revert back to 100% stock.
we're not on 2 wavelengths, i'm just talking like an inebriated baby on no sleep!
thanks for the patience you display toward everyone, all the while having a guide which spells all this stuff out...
so the file system rules, and since 2.3's obvious big upgrade was the F/S, it borked previous recoveries.
so i'm on CWM3024, the latest, which i installed via rommanager, and it flashed it, and i nandroid backed up.
so im set for ext3 and ext4 incl pd15img, (which is ext3). right?
also, flashing pd15img- that reverts the bootloader from 085 to 086 again?
Um...neidlinger, fastboot and hboot are two totally different things. Keep in mind, I am not picking on you...
Appreciate your enthusiasm, but you are wrong a lot.
kmdub said:
Um...neidlinger, fastboot and hboot are two totally different things. Keep in mind, I am not picking on you...
Appreciate your enthusiasm, but you are wrong a lot.
Click to expand...
Click to collapse
then i'm out....
Didn't see this in General so thought it would be worth adding, especially since there have been many threads lately with new users wanting to root their phone and then getting scared of the guides.
Now there is also the option to go the official way to unlock the bootloader.
http://htcdev.com/bootloader/
noob here with a question... rooting is the same as unlocked bootloader??
coldsun15 said:
noob here with a question... rooting is the same as unlocked bootloader??
Click to expand...
Click to collapse
Not quite. It can probably explained more accurately but the gist of it is this:
An unlocked bootloader is what allows you to flash custom roms to your phone.
Root access simply grants you the rights to mess with your phones rom whichever way you want.
thomas_wlc said:
Not quite. It can probably explained more accurately but the gist of it is this:
An unlocked bootloader is what allows you to flash custom roms to your phone.
Root access simply grants you the rights to mess with your phones rom whichever way you want.
Click to expand...
Click to collapse
so, basically whats this means is, now i dont need to root and s-off and stuff to be able to put CM7 (for example)?
coldsun15 said:
so, basically whats this means is, now i dont need to root and s-off and stuff to be able to put CM7 (for example)?
Click to expand...
Click to collapse
I thinks that's pretty much it, once you have unlocked your bootloader you'll be able to flash any custom rom you like. Though it'll probably a bit tricky on the first go since you don't have a custom recovery yet, so I believe you'd have to flash some pc10img.
Still it's commonly to believed to be the better choice to stick with the more exhausting solutions posted around here, since HTC will register your phone if you use their tool. At least for the time being they claim that by using their way, your warranty will be void.
I've unlocked my desire z through the htcdev.com website.
Bootloader is unlocked, S-on..
But I can't get a rom installed, it gave me an error while trying to update from the recovery mode (apply update zip) using a stock rom with root.
Akward..
So now I've unlocked my bootloader, but still can't change my rom..
Anyone know how to do it after you've unlocked the bootloader?
flash custom recovery first, from there flash the rom
if you're s-on, bootloader is still locked....
artov said:
flash custom recovery first, from there flash the rom
Click to expand...
Click to collapse
I'm working on it
Gaining temp root using this guide worked.
http://forum.xda-developers.com/showthread.php?t=1178912
But when I press start clockwordmod, it says that my phone is not rooted..
While I press "flashcockwork" clockword mod recovery, I get an error.
än error occurred while attempting to run privileged commands!
I'm doing something wrong..
pretty annoying
I get unlock my bootloader today, and YES there is S-ON, but on the top is written in hboot menu big letters UNLOCKED (How you thinks, htcdev joke?).
I've installed clockworkmod using fastboot:
Code:
fastboot flash recovery clockwork_mod_for_vision.img
Then put off battery and turn on phone with volume down + power, I pressed 'recovery' menu option. Clockworkmod runs correctly. Then tried last stable CyanogenMod 7.1.0, flash was done without errors, I wiped out what's need (cache, data). Next I tried run phone, but freezes at splash (green htc letters on white background).
I tried also miui mod, but Ive got only MIUI splash screen nothing else.
Then I restored my htc from backup (done before flashing using clockworkmod) and Im still on the stock htc android 2.3.3.
Regards,
Mariusz
p.s Sorry for my poor english.
how can I install CM7 or other roms after unlocking the bootloader
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
rskainth82 said:
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
Click to expand...
Click to collapse
1. boot to fastboot mode, flash a custom recovery (recommand ClockWorkMod), power down the phone.
2. put your downloaded update_cm7.xxx.zip into sdcard, boot phone into recovery
3. choose in the recovery, first "wipe data", then "install update from sdcard", choose the zip file you just put in.
4. choose "reboot system"
that's all to go.
pentie said:
1. boot to fastboot mode, flash a custom recovery (recommand ClockWorkMod), power down the phone.
2. put your downloaded update_cm7.xxx.zip into sdcard, boot phone into recovery
3. choose in the recovery, first "wipe data", then "install update from sdcard", choose the zip file you just put in.
4. choose "reboot system"
that's all to go.
Click to expand...
Click to collapse
I did it, but CM7 doesnt boot.
rskainth82 said:
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
Click to expand...
Click to collapse
flak999 said:
I did it, but CM7 doesnt boot.
Click to expand...
Click to collapse
Booting problem is mostly kernel related, do you have logcat output? (run "adb logcat" and boot the phone)
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
EDIT:
That was a EVO3D with UNLOCKED HBOOT, I believe you're having the same situation, try my method or may others make out a better perfect solution ? (not my own phone, I just helped with its owner, no time to dig the details)
pentie said:
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
EDIT:
That was a EVO3D with UNLOCKED HBOOT, I believe you're having the same situation, try my method or may others make out a better perfect solution ? (not my own phone, I just helped with its owner, no time to dig the details)
Click to expand...
Click to collapse
Thanks men thats worked for me. First flash the boot.img from CM7.0.1 then run recovery and run update_cm7.0.1.zip. After reboot everything run corectly.
Once more thanks!
flak999 said:
Thanks men thats worked for me. First flash the boot.img from CM7.0.1 then run recovery and run update_cm7.0.1.zip. After reboot everything run corectly.
Once more thanks!
Click to expand...
Click to collapse
now I confirmed the UNBLOCKED HBOOT somehow blocks the CWM to flash boot.img
My Phone have a S-OFF HBOOT and i was considering flash it to the UNLOCK the last night, now it seems not worth the try ~
pentie said:
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
Click to expand...
Click to collapse
My friend has an officially unlocked Desire Z as well and I gave him these instructions to try it out, he has the same boot problem (stuck at splash screen). Maybe this information should either be stickied or added to a faq until there is a real solution to the problem (unlike this workaround), updated cwm or something like that.
Anyway thanks for sharing this information.
HTC bootloader unlock tool is quite restrictive. It still leaves you S-ON, so you won't be able to flash a new hboot or radios.
I recommend avoiding it and using the current well-proven methods from the XDA Wiki.
Sent from my Desire Z running CM7.
Its working now...
Steps I followed:
1. flash recovery using fastboot
2. Do a nandroid backup using recovery
3. flash boot.img using fastboot
4. reboot into recovery
5. wipe data/cache
5. install update for CM7, and gapps
Also make sure before doing any of these steps you have copied CM7 and gapps update onto sdcard.
Thanks everyone for helping out.
I am experimenting with this myself and I don't seem to be having the same issues flashing a boot.img from an update.zip in ClockworkMod recovery with the official HTC unlocked bootloader that others are having. Maybe it is the version of the recovery that is the issue? Which version is everyone trying to use? I am using the 3.xxxx version that is linked from the wiki. I have had other problems with the 5.xxx version and tend to stick with the older version for that reason anyways.