Related
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
Hey everybody! I went to stock from CyanogenMod Nightlyes, and flashed stock 2.3.2 nandroid.
Then I flashed the 2.3.3, it works just fine! But my bootloader is still unlocked!
First thing that i thank was just to install Superuser, but it doesen't work.
I connected it to Pc in fastboot mod, and ran install-superboot-windows.bat (one click root)
But now, it just stuck in Google logo, and I don't know what to do next... I tryed to pull out the battery, nothing...
Update: just reflashed recovery via fastboot flash recovery recovery.img, and got the CWM. Now restoring to 2.3.2.
I think that we can just flash CWM after update, and then install superuser. I'll try and will ask you about any changes.
Update 2:: So, it ran just fine, first installed 2.3.2, then updated it to 2.3.3, and then flashed CWM. It boots up just fine, but in CWM I tried to install superuser.zip, it says: invalid to install
maybe reinstall your backup from CWM?
also the one click root you need to be in a rom and using adb
I did the same thing and ended up in the same situation...ive fixed like this...downloaded odin got back to stock 2.3.1 then downloaded the update,flashed it through stock recovery then flashed recovery.img....flashed su and everything is back on normal now
Hope it helps
Sent from my Nexus S using XDA App
If you unlock already, it is very easy to root again
1. fastboot boot recovery.img
2. flash su.zip
3. reboot
all done
Yeah, but it says, that it can't install superuser.zip (bad) I don't know what it means..
2.3.3 root question
Ok so currently I'm rooted on stock 2.3.2
How do I update to 2.3.3 and
1. not lose root
2. not have to reinstall all user apps
3. not have to redo all my settings
Is there a way to do this?
This does not belong in development.
Sent from my MattedBlues CM7 Google Nexus S!
I have a question is there a way to make the phone as if it was never messed about with, just incase it was ever needed to get repaired under the warrenty
Trinitronik said:
Yeah, but it says, that it can't install superuser.zip (bad) I don't know what it means..
Click to expand...
Click to collapse
mount /system inside of clockwork then try.
Sent from my Nexus S using XDA App
Jnowak1981 said:
Ok so currently I'm rooted on stock 2.3.2
How do I update to 2.3.3 and
1. not lose root
2. not have to reinstall all user apps
3. not have to redo all my settings
Is there a way to do this?
Click to expand...
Click to collapse
Try this..
From Android 2.3.2 /rooted/locked bootloader
1) Fastboot boot recovery.img..to boot into recovery CW recovery screen
2) Apply 2.3.3 update.zip ..
=>Do not reboot ,as this 2.3.3 has Bootloader change that disable fastboot boot for locked bootloader.
3) Without rebooting , mount system, apply su.zip
4) Reboot..
Click to expand...
Click to collapse
I am just posting the concept..you need to find out the details steps
Ill keep 2.3.2 until than
Sent from my Nexus S using XDA App
Follow the link, i managed to retain root after 2.3.3 update.
http://forum.xda-developers.com/showpost.php?p=11626567&postcount=70
Code:
I manage to keep the root for 2.3.3 with the flashing sequence listed below.
From Android 2.3.2 /rooted/locked bootloader
1) Fastboot boot recovery.img..to boot into recovery CW recovery screen
2) Apply 2.3.3 update.zip ..
=>After applying update DO NOT REBOOT ,as this 2.3.3 has Bootloader change that disable fastboot boot for locked bootloader.
3) Without rebooting , mount system, apply su.zip
=> This step is to reapply Superuser.apk permission setting
4) Reboot..
I am highlighting the concept, for details inter steps..please refer to the first post on the link.
2.3.3 root
is there a method to root 2.3.3 or is it to early i tried allgamer way but it failed
Or you can simply restore 2.3.3 its in the development forum. It had root already on it
Sent from my Nexus S using XDA App
There is a 2.3.3 rooted nandroid backup in development section.
Sent from my Nexus S using XDA App
well tryind to do from 2.3.3
Based on this change from 2.3.2 to 2.3.3, does it make sense just to unlock the bootloader?
Yes, I know it'll wipe my device, but is that the only thing? I can just use Titanium Backup and restore everything anyway right?
Are there advantages/disadvantages to the locked bootloader? I never bothered just because I was just learning how to root and picked a method almost at random.
kaimyn said:
Based on this change from 2.3.2 to 2.3.3, does it make sense just to unlock the bootloader?
Yes, I know it'll wipe my device, but is that the only thing? I can just use Titanium Backup and restore everything anyway right?
Are there advantages/disadvantages to the locked bootloader? I never bothered just because I was just learning how to root and picked a method almost at random.
Click to expand...
Click to collapse
If I were currently locked bootloader, I would run a full titanium backup of apps+data, and copy over your entire sdcard contents to your pc, along with the titanium backups (remember, the oem unlock wipes the sdcard also, not just internal space).
Then unlock the bootloader. Easiest way to deal with custom recovery in the future.
There are steps in the 2.3.3 link thread here describing how you can update and get root back even with the locked bootloader; which might be less of a hassle then going through a wipe.
squattingb said:
I tried to do this in clockwork but the installation kept failing, I was getting some messages about "assert failed", wasn't quite clear so I couldn't really make out what the problem was, does anyone have any insights into this? I downloaded the update from http://forum.xda-developers.com/showthread.php?p=11566707 for Nexus S.
Click to expand...
Click to collapse
I'm having the same issue. Any idea how to fix this?
Just load the Nandroid as charlieb620 said. If your already on 2.3.3 you won't lose nowt, just backup your data first.
I'm with GCI/Alaska Digitel and I used Universal Androot it said my phone was successfully rooted. Is it rooted to the point where I can flash custom ROMs?
If not, is it possible to root via another method?
And if so, is it possible to back my radio up then flash a ROM, then recover my radio?
Thanks all,
Angel
Download Rom Manager from the market. You need to install a custom recovery to flash ROMs. If it allows you to flash clockworkmod recovery, you are rooted and ready to flash.
Sent from my HERO200 using XDA App
Angel34 said:
I'm with GCI/Alaska Digitel and I used Universal Androot it said my phone was successfully rooted. Is it rooted to the point where I can flash custom ROMs?
If not, is it possible to root via another method?
And if so, is it possible to back my radio up then flash a ROM, then recover my radio?
Thanks all,
Angel
Click to expand...
Click to collapse
You won't change the radio when you flash roms and such,unless you flash a radio zip. NEVER FLASH A RADIO THAT IS FOR A GSM PHONE!(not yelling just don't want you to brick your phone)
Okay so it is rooted, downloaded and did the Rootcheck or whatever. I got a couple CM7 roms but they won't boot. It just sits at the boot screen spinning, stops for a second, and then starts the CM7 boot screen over.
Ideas? Thanks all,
Angel
Well you need to wipe and format the appropriate things first. Read the readme on AOSP's mod thread.
Hey thanks, will do.
First, you need to wipe data, cache, boot and system. Do this twice and then flash the rom.
So, he's running a custom ROM right now, the latest desire hd port, GB, etc.
Well, most everything else needs CWM 3.006 or whatever. So, I'm trying to flash that. BUT, his phone acts as if he doesn't have root. I't S-offed and has "su" (the app) but it just doesn't work.
Tried flashing cwm with fastboot, "permission denied"
Idk what else to do
Regards
Smith
smithisize said:
So, he's running a custom ROM right now, the latest desire hd port, GB, etc.
Well, most everything else needs CWM 3.006 or whatever. So, I'm trying to flash that. BUT, his phone acts as if he doesn't have root. I't S-offed and has "su" (the app) but it just doesn't work.
Tried flashing cwm with fastboot, "permission denied"
Idk what else to do
Regards
Smith
Click to expand...
Click to collapse
doubt its bricked...(its not bricked if you can get to the bootloader
what h-boot version do you have?
use the PD15IMG.zip to restore your phone
VibrantOwnr said:
what h-boot version do you have?
Click to expand...
Click to collapse
86.0.0.0 i believe... I followed the perm root tut before flashing this custom ROM, then he messed it up..
smithisize said:
86.0.0.0 i believe... I followed the perm root tut before flashing this custom ROM, then he messed it up..
Click to expand...
Click to collapse
i dont think you can flash using fastboot in .86.
if it wont boot to the rom try the PD15IMG.zip file to restore
if it boots to the rom, go back to the true s-off/permroot guide in the development section and flash your bootloader (there is directions at the bottom of the first post (the post with the instructions))
After that it should work for fastboot
You can alternatively flash recovery through rom manager (off of the market..the free version will do)
VibrantOwnr said:
i dont think you can flash using fastboot in .86.
if it wont boot to the rom try the PD15IMG.zip file to restore
if it boots to the rom, go back to the true s-off/permroot guide in the development section and flash your bootloader (there is directions at the bottom of the first post (the post with the instructions))
After that it should work for fastboot
You can alternatively flash recovery through rom manager (off of the market..the free version will do)
Click to expand...
Click to collapse
ROM Manager didn't work (again, couldn't obtain permissions).
So, I'm going to flash the ROM, hope for the best, then if $*&^ hits the fan, I'll result to flashing a diff bootloader.
Thanks for your advice, didn't think about flashing a diff booloader... used to my Cappy xD
Regards
Smith
have you tried using TrueBlue's recovery .zip it was the only way I could get either of my phones to take 3.0.0.6
HERE is the thread for it
Well, I flashed regardless of the 3006 req, and it went fine... Whatever lol.
thanks for the help and suggestions
Regards
Smith
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.