Database Develop

ROM Manager Won't Doesn't Work

I have an N1 that I unlocked and rooted and was running CM7 RC1 when I decided to try the stock Gingerbread. This switch went perfectly, but now I don't think I want to stay on the stock GB but I can't seem to get ROM Manager to boot into recovery to allow me to flash another ROM. Do I have to do something differently now? BTW, I do not have root on the 'new' GB.
Thanks.

Unless you flashed a pre-rooted version of Gingerbread, you will have lost root and your custom recovery...
If this is the case, you have two options:
1 - Flash a custom recovery through an unlocked bootloader.
2 - passimg back to an older version of Android and root again...
Sent from my Nexus One using XDA App

tsprks said:
BTW, I do not have root on the 'new' GB.
Click to expand...
Click to collapse
This is your problem. ROM Manager installs a custom recovery, but only when your phone is rooted. You need to re-root GB.

Can I ask them how people flash custom recoveries without having root? I see threads all over the place that say that you don't have to root your phone to run these custom ROM's.

tsprks said:
Can I ask them how people flash custom recoveries without having root? I see threads all over the place that say that you don't have to root your phone to run these custom ROM's.
Click to expand...
Click to collapse
You have to root, but you don't have to unlock your bootloader.

You have to do one of the things:
1) Root.
2) Unlock the bootloader.
Rooting allows you to bypass security mechanisms from within the OS, and flash the custom recovery from there.
Unlocking the bootloader turns off the security mechanisms, and you can flash whatever you want directly from bootloader.
Both achieve the same thing, but in different ways.
Root privileges in OS are lost upon official upgrades.
Unlocked bootloader is never lost.
Unlocked bootloader allows for an easy way to gain root in the first place, regardless of the ROM.

How does an unlocked bootloader allow me to flash whatever ROM I want? ROM Manager won't run without root? Am I missing something? I've read the wiki's and threads about rooting an N1 and they all just seem to stop at unlocking the bootloader, well, my bootloader is unlocked but I can't get it to boot into CWM so that I can select another ROM. Is there another way to do this?

ROM Manager is only one, and not the most successful nor most powerful, way to flash ROMs or recovery. ROM Manager was made for non-understanding people to make the process look and feel easier. The most powerful way is directly from bootloader - which needs to be unlocked to allow it.
If you read all the threads, you'll see that unlocking the bootloader is just a first step - you can look carefully at "installing custom ROM" guide in Wiki. Or, for example, here:
http://forum.xda-developers.com/showthread.php?t=636795
Read the Wiki, look for recovery installation instructions using unlocked bootloader, execute. I suggest Amon_Ra's.

[Q] OTA updates and root

So,
My HTC Incredible S is rooted, and the bootloader is unlocked (what the point of unlocking the bootloader is I still don't know as I can't install custom ROMS... but back to the point at hand...), and the OTA update to 2.3.5 arrived 2 weeks ago.
Needless to say, the update would not install. Despite researching the issue, I'm still confused as to what exactly is preventing the update from working. Is the the fact that my device is rooted? Or is it the unlocked bootloader? I tried relocking the bootloader and that had no effect, so I'm assuming rooted devices for some reason are rejected by the update.
So considering I can't install custom ROMs (I'm HBOOT 1.16 and the downgrade guide didn't work for me, so no s-off), and I now can't upgrade officially, I'm feeling a little stuck.
Is there a way to force an official update to install on a phone in my 'condition'?
Note: My recovery is custom - Revolutionary CWM - and I can't find (and therefore cannot flash) an original recovery image... would this affect the updating process?
Thanks guys/gals,
G

Root won't stop an ota but an unlocked bootloader will. You can check in your boot screen if its still unlocked or if its relocked.

nope_okay said:
So,
My HTC Incredible S is rooted, and the bootloader is unlocked (what the point of unlocking the bootloader is I still don't know as I can't install custom ROMS... but back to the point at hand...), and the OTA update to 2.3.5 arrived 2 weeks ago.
Needless to say, the update would not install. Despite researching the issue, I'm still confused as to what exactly is preventing the update from working. Is the the fact that my device is rooted? Or is it the unlocked bootloader? I tried relocking the bootloader and that had no effect, so I'm assuming rooted devices for some reason are rejected by the update.
So considering I can't install custom ROMs (I'm HBOOT 1.16 and the downgrade guide didn't work for me, so no s-off), and I now can't upgrade officially, I'm feeling a little stuck.
Is there a way to force an official update to install on a phone in my 'condition'?
Note: My recovery is custom - Revolutionary CWM - and I can't find (and therefore cannot flash) an original recovery image... would this affect the updating process?
Thanks guys/gals,
G
Click to expand...
Click to collapse
You need to replace CWM with the standard HTC recovery (you simply need to extract the recovery.img file from a RUU/ROM.zip file) and then relock the bootloader before the OTA will install correctly.

At hboot 1.16 and rooted all you should have to do is install Cwm and than you can flash custom ROM's..... Not sure what your problem is.
Sent from my anus using xda crap

@itsbeertimenow - yeah, unlocking the bootloader never did anything for me in terms of being able to flash custom ROMs... I guess 's-off' is required
@tpbklake, nonverbose
Yeah, I had a feeling the custom recovery had something to do with it. As I mentioned before, even relocking the bootloader had no effect.
Does the recovery have to be a specific version? I'm running Android 2.3.3, so will any 2.3.3 recovery work or does it have to be a recovery for an HTC Incredible S running Android 2.3.3 - that's a little harder to find. Any suggestions for an ruu/zip file to extract a recovery img from?
Thanks again for the helpful responses.
G

nope_okay said:
@itsbeertimenow - yeah, unlocking the bootloader never did anything for me in terms of being able to flash custom ROMs... I guess 's-off' is required
@tpbklake, nonverbose
Yeah, I had a feeling the custom recovery had something to do with it. As I mentioned before, even relocking the bootloader had no effect.
Does the recovery have to be a specific version? I'm running Android 2.3.3, so will any 2.3.3 recovery work or does it have to be a recovery for an HTC Incredible S running Android 2.3.3 - that's a little harder to find. Any suggestions for an ruu/zip file to extract a recovery img from?
Thanks again for the helpful responses.
G
Click to expand...
Click to collapse
Instead of trying to install the OTA update for Sense 3/2.3.5 why don't you flash the stock, rooted version of 2.3.5/Sense 3 ROM that I posted in the Dev section. With the unlocked bootloader and CWM you can flash this ROM and then manually flash the boot.img in that ROM's zip file and you should be good to go.

@tpbklake
I think I'd already tried that and the update process aborted pretty early on. I'll give it another go and check out troubleshooting threads related to the process. thanks again.
G
Update: I'm following the instructions as per this thread: http://forum.xda-developers.com/showthread.php?t=1337105
Update 2: It worked and I managed to install CM7... happy day Thanks guys

nope_okay said:
@tpbklake
I think I'd already tried that and the update process aborted pretty early on. I'll give it another go and check out troubleshooting threads related to the process. thanks again.
G
Update: I'm following the instructions as per this thread: http://forum.xda-developers.com/showthread.php?t=1337105
Update 2: It worked and I managed to install CM7... happy day Thanks guys
Click to expand...
Click to collapse
Here is the 2.3.5/Sense 3.0 stock, rooted ROM built directly from the OTA you were trying to install. You would flash it in CWM just like you did for CM7.
http://forum.xda-developers.com/showthread.php?t=1430535

Thanks for the link, will come in handy when I want to go back to a 'stock' setup... wasn't very impressed with CM7 so I then tried the Virtuous Affinity ROM (2.3.5/S3.5) - fantastic. Thanks again for your help!
G

how to root with stock ICS

I know there are stickies but I am still unsure of where to start.
My phone is stock ICS + Sense 3.6
I want to root it so I can install root only apps. Further down the road I want to install CM9 or another rom.
I rooted my Desire with unrewoked last year, which was really easy, but for the Incredible I can't figure out where to start.
I am not sure if the stickies apply to ICS as well?
Help please

esbenm said:
I know there are stickies but I am still unsure of where to start.
My phone is stock ICS + Sense 3.6
I want to root it so I can install root only apps. Further down the road I want to install CM9 or another rom.
I rooted my Desire with unrewoked last year, which was really easy, but for the Incredible I can't figure out where to start.
I am not sure if the stickies apply to ICS as well?
Help please
Click to expand...
Click to collapse
You are in uncharted waters my friend. ICS/Sense 3.6 introduced a new HBOOT 2.02.0002. Your only hope is that the Downgrade script that uses 'tacoroot' exploit stills works. Here is the link if you want to give it a shot and then report back on your success or failure.
http://forum.xda-developers.com/showthread.php?t=1373697

The way I rooted mine was firstly unlock the bootloader via HTCdev, then flashed 4ext recovery via fastboot. I was then able to flash Superuser via recovery and finally installed Busybox from the market

mr nick said:
The way I rooted mine was firstly unlock the bootloader via HTCdev, then flashed 4ext recovery via fastboot. I was then able to flash Superuser via recovery and finally installed Busybox from the market
Click to expand...
Click to collapse
Thanks for this post. I forgot that this was an option because so many people dismiss this option because they don't want HTC knowing that they unlocked their phone.

[Q] Rooting and OTA

Hi,
I know this has been discussed in several ocassions, and I have read several threads but none of them answer my question.
I am wondering if I root my HTC One and keep the device with the stock rom (I only want to root for some apps that needs su) will I be able to get OTA updates?
If not, if I also do S-OFF will I be able to? Please keep in mind that I do not want to flash a custom rom, where then the answer I believe would be to unroot and apply the OTA.
Thank you

buzmay said:
Hi,
I know this has been discussed in several ocassions, and I have read several threads but none of them answer my question.
I am wondering if I root my HTC One and keep the device with the stock rom (I only want to root for some apps that needs su) will I be able to get OTA updates?
If not, if I also do S-OFF will I be able to? Please keep in mind that I do not want to flash a custom rom, where then the answer I believe would be to unroot and apply the OTA.
Thank you
Click to expand...
Click to collapse
No, and youll need a custom kernel with disabled write protection for the root to stick, which will not allow OTA's to work. if you really want root, download a custom stock rom

IINexusII said:
No, and youll need a custom kernel with disabled write protection for the root to stick, which will not allow OTA's to work. if you really want root, download a custom stock rom
Click to expand...
Click to collapse
But what about S-OFF not even with it it would work? I am confuse because I saw a guide here in XDA saying the following:
Rooting stock ROM
What you need to know before rooting stock ROM:
You can "un-root" it easily.
As long as you won't change any files on system partition, you still will be able to download and install official OTA updates.
Download Rooting Tools
Boot your device in recovery mode (power off the device and turn it on using power + vol down buttons and select "RECOVERY")
In main menu, select "install zip from sdcard" and "choose zip from sdcard".
Navigate to the location of Rooting Tools (zip) package and confirm flashing procedure.
After flashing process is complete, reboot the device. Your device has now SuperUser.apk, su binary and busybox installed.
So is this not true?
Link to this guide:
http://forum.xda-developers.com/showthread.php?t=2265618

buzmay said:
But what about S-OFF not even with it it would work? I am confuse because I saw a guide here in XDA saying the following:
Rooting stock ROM
What you need to know before rooting stock ROM:
You can "un-root" it easily.
As long as you won't change any files on system partition, you still will be able to download and install official OTA updates.
Download Rooting Tools
Boot your device in recovery mode (power off the device and turn it on using power + vol down buttons and select "RECOVERY")
In main menu, select "install zip from sdcard" and "choose zip from sdcard".
Navigate to the location of Rooting Tools (zip) package and confirm flashing procedure.
After flashing process is complete, reboot the device. Your device has now SuperUser.apk, su binary and busybox installed.
So is this not true?
Link to this guide:
http://forum.xda-developers.com/showthread.php?t=2265618
Click to expand...
Click to collapse
Having S-off won't effect OTAs but having a custom recovery will. Best to go all stock, rom and recovery to receive the OTA updates. You can root after.
Note: Do the S-off procedure before you update. If your hboot gets updated, you're outta luck.

farang4u said:
Having S-off won't effect OTAs but having a custom recovery will. Best to go all stock, rom and recovery to receive the OTA updates. You can root after.
Note: Do the S-off procedure before you update. If your hboot gets updated, you're outta luck.
Click to expand...
Click to collapse
Ok, but now for instance I do have 4.2.2 so if I root and then there is an update 4.3 then what? I am interested in being only root and being able to get the updates. So every time an OTA comes I shall unroot and then root? This option is not as optimal as I would have though it would be.
Thanks

buzmay said:
Ok, but now for instance I do have 4.2.2 so if I root and then there is an update 4.3 then what? I am interested in being only root and being able to get the updates. So every time an OTA comes I shall unroot and then root? This option is not as optimal as I would have though it would be.
Thanks
Click to expand...
Click to collapse
As long as you have a stock recovery and rom, you should be able to receive OTAs on a rooted phone. Not %100 certain though.
Note: An OTA update could break the root and other mods you made to the rom and cause some other issues.

farang4u said:
As long as you have a stock recovery and rom, you should be able to receive OTAs on a rooted phone. Not %100 certain though.
Note: An OTA update could break the root and other mods you made to the rom and cause some other issues.
Click to expand...
Click to collapse
But how can I have a stock recovery and be root? Dont I need a custome recovery to root?

buzmay said:
But how can I have a stock recovery and be root? Dont I need a custome recovery to root?
Click to expand...
Click to collapse
You need custom recovery to run the rooting process. After your system is rooted you can then flash back to the stock recovery. You should still have root access but I could be wrong. Download "Root Checker" from the play store, run it to see if your device is still rooted. You still need a stock recovery to receive OTA updates though.

The reason you need stock recovery is that you can't install an official update with custom recovery. The type of recovery you have doesn't affect root access.
The reason you have to keep your system files perfectly stock is that an OTA is a patch, meaning it doesn't necessarily replace entire files but mainly snippets of code. If the system files are not stock, it can't do this properly. So it checks /system before running and stops if things are not perfectly stock.
You can get OTAs being rooted, you just can't install them unless you have stock recovery and a fully stock rom.
If you're stock on 4.2.2 right now, you can't s-off, so don't worry about that.

You don't have to flash a custom rom, but you can flash a stock rooted rom. With OTAs, you play the cat-and-mouse game. Can I root it? Did the HBOOT update and kill current S-OFF procedures?
If 4.3 does come out, all you would have to do is wait for a few days for a dev to cook a stock rooted 4.3 rom. AT&T always lags with updates, yet I have a fully functioning 4.2.2 M7 with LTE and no AT&T bloat all thanks to the devs who cook stock rooted roms.

Couple questions about rooting and s-off

Sprint User
1. I just bought the M8 tried to get s-off using the firewater method and it said it wouldn't work at this time.
Is there another method to get s-off?
2. The phone is rooted but I do not want a custom rom. I want to keep the rom stock but get updates. Is this possible or would I have to flash in recovery to work around it?

If firewater won't work for you you will have to do the sunshine method, it's $25 though.

As stated above, you will need to use the SunShine exploit to gain S-off. To answer your second question, once rooted you cannot take OTA updates without reinstalling the stock Android system recovery. Otherwise you'll have to wait for the RUU for the update to be released.

Magnum_Enforcer said:
As stated above, you will need to use the SunShine exploit to gain S-off. To answer your second question, once rooted you cannot take OTA updates without reinstalling the stock Android system recovery. Otherwise you'll have to wait for the RUU for the update to be released.
Click to expand...
Click to collapse
So it would besomething like this
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery

Stride2 said:
So it would besomething like this
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
Click to expand...
Click to collapse
Correct:thumbup: