Database Info

[Q] ICS ota with half root?

I want to be sure my DS can receive and install the imminent (?) ota ICS from HTC. Still a bit of a noob so read a lot of stuff on here and other forums (mainly non DS) but haven't really found definitive answers for the 'half rooted' device i.e. bootloader unlocked via htcdev, cwm flashed, s-on.
Main concerns are:
losing root
ota will not install because of /system/app and framework mismatch (after a few UOT mods) - boot animation and sound have also been changed in /system/customise/resource, also bloatware removed
ota issues with cwm installed
Originally first thing I did immediately after flashing cwm was a nandroid backup so that's available to me, which really only leaves the cwm and ota compatability question.
Is Rootkeeper an option or should I root from scratch again after ota?
If I receive notification of the ota availability, then restore from original backup (and maybe relock bootloader with htcdev?) will I then have lost the chance to install the ota?
A lot of questions and ifs, I know, I just don't want to screw up the chance to try the official ICS before going for a custom rom. Thanks in advance.
Hboot 2.00.0002
Android 2.3.5
Sense 3.0
Stock rom/kernel/radio

Sorry, I'm pretty sure HTC Dev unlocked devices can't get OTA updates. I'm completely sure devices with CWM can't (you need stock HTC recovery). Since you already have a custom recovery, it would be better to get a custom ROM, much fastr and tweaked

As shrome99 said..
To get the OTA update you will need to have STOCK recovery, and a relocked bootloader to get the OTA.
__________________
This assumes you are 100% stock on the operating side.

foX2delta said:
As shrome99 said..
To get the OTA update you will need to have STOCK recovery, and a relocked bootloader to get the OTA.
__________________
This assumes you are 100% stock on the operating side.
Click to expand...
Click to collapse
I got OTA updates with both an unlocked bootloader and custom recovery. It's true the update won't install till you're back on stock recovery but the locked bootloader isn't necessary. I was however updating from Stock Sense 2.1

Warning: do not install it if you get a OTA message if rooted!
It will lead to the dreaded red triangle screen. Your best bet is to just install CWM/4EXT then when the new update comes, install the ICS prerooted ROM by Adidas.
Sent from my HTC Desire S using xda premium

The "dreaded" triangle screen is just the stock recovery.

Jack_R1 said:
The "dreaded" triangle screen is just the stock recovery.
Click to expand...
Click to collapse
That won't boot back to your ROM therefore you are stuck.
No root/s-off, therefore you can't do much about it. (Unless you get the RUU to run)
And for the average user, this is difficult for them to understand. Hence it has picked up its name as the 'dreaded triangle screen' over several different HTC device threads.
Sent from my HTC Desire S using xda premium

Cheers for the input.. did a bit more snooping and (if and when I get the ota shout).. I think I can go back with original nandroid to pre-root, before superuser went in. Then I'll give Android Recovery Manager (Sensation Android Development forum) a lash, just to see if I can flash back the stock recovery img.
If any nice ota comes my way which won't take then I'll try htcdev to relock the bootloader and give it another lash!
Think (hope) it'll work.. couldn't find a stock img anywhere yet so I'm hoping it's included in the above manager.. was going to try tonight but, typical, my connection went..
'Your best bet is to just install CWM/4EXT then when the new update comes, install the ICS prerooted ROM by Adidas.'
I have cwm, not sure why I would wait for the update then install a custom ics rom..

You must install stock recovery to install OTA update.OTA won't install, if you have custom recovery or S-off.But I recommend to install ROM, using zip or RUU.

From htcdev:
(after unlocking bootloader) Some content on your device may also be invalidated and cannot be accessed any more because of invalid DRM security keys. This includes content that you may have purchased through a 3rd party vendor and through HTC. Furthermore, although you will still be able to receive updates to your device via FOTA (“firmware over the air”), we do not guarantee that updating your device via FOTA will not render your device unusable.
That answers the question re the bootloader but I'm struggling to find the stock recovery img to flash.
I suppose I can extract and then flash it, possibly from this: RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed.exe, even though my device is 2.10.161.3 (161 is Vodafone). The radio is the same as mine which is irrelevant anyway, right?
I know it would be easier to install the RUU but after hours of research I would really like to be able to nail this so I have the option of reverting back to VF stock, as I still have 18 months warranty left.
Can anyone can confirm if I'm on the right track pls?

I suppose, if you haven't GoldCard or SuperCID recovery won't flash(signature verify failed).Download Zip/exe of your ROM , and flash that recovery.After that you might be able to install FOTA.No guarantee it will work.

scandron said:
I suppose, if you haven't GoldCard or SuperCID recovery won't flash(signature verify failed).Download Zip/exe of your ROM , and flash that recovery.After that you might be able to install FOTA.No guarantee it will work.
Click to expand...
Click to collapse
It will flash, because his bootloader is unlocked.
He won't need a goldcard cause he is flashing a voda RUU recover, future I don't think it will even come into play when using fastboot to flash it.
However I suggest EVERYONE who is a little unsure make a goldcard.

Thanks all, trying to get a gold card now just to be sure.. however just intend to extract and flash the recovery img from the ruu, once I can be sure I have the right one.. the stock recovery in HTC devices is generic, no?

i also have a doubt.
what i wanted to know is that will i still be able to update my device OTA if i have unlocked the bootloader, rooted my device but havent installed a custom recovery?my device is rooted nothing more than that. and after relocking my bootloader (i dont mind loosing root) will i be able to update OTA?
sorry for being irrelevant but i didnt want to start a new thread for a doubt of this magnitude.

See post #10

[Q] Help to choose custom ROM for WT19i

Hey everyone,
I just rooted my WT19i and unlocked bootloader. Because I'm absolutely new in custom ROMs I need your advice helping me to decide which of them I should install on my device. Which is the best?
BTW I already tried installing CM9 using ROM manager, but it said "Installing update..." , then the device rebooted ant stuck on "Sony Ericsson" logo... I had to flash firmware and root my phone again...

Maceee said:
Hey everyone,
I just rooted my WT19i and unlocked bootloader. Because I'm absolutely new in custom ROMs I need your advice helping me to decide which of them I should install on my device. Which is the best?
BTW I already tried installing CM9 using ROM manager, but it said "Installing update..." , then the device rebooted ant stuck on "Sony Ericsson" logo... I had to flash firmware and root my phone again...
Click to expand...
Click to collapse
ROMs for this phone are buggy if you want one with all features working even walkman button try Hibroman (just ask for a link to download)
if you have unlocked bootloader you can see kernels like rage kernel with cpu governors this will increase/improve battery !
It's better to use phone-specific methods for flashing than ROM Manager (some got trouble by this way)
when flashing a ROM that requests to change bootloader be sure to flash it using a laptop on battery -it's better to protect from power problems if something is wrong when flashing bootloader your phone is bricked and only service tools can revive it !
never flash ROMs/ kernels not made for your phone -you are to experiment a hardware failure !

ruscan.calin said:
ROMs for this phone are buggy if you want one with all features working even walkman button try Hibroman (just ask for a link to download)
if you have unlocked bootloader you can see kernels like rage kernel with cpu governors this will increase/improve battery !
It's better to use phone-specific methods for flashing than ROM Manager (some got trouble by this way)
when flashing a ROM that requests to change bootloader be sure to flash it using a laptop on battery -it's better to protect from power problems if something is wrong when flashing bootloader your phone is bricked and only service tools can revive it !
never flash ROMs/ kernels not made for your phone -you are to experiment a hardware failure !
Click to expand...
Click to collapse
Thanks! I guess I'll try installing this ROM and kernel when I have enough time. And two more questions: if I flashed another firmware my bootloader will be locked again and which version of Hybroman should I use?

Maceee said:
Thanks! I guess I'll try installing this ROM and kernel when I have enough time. And two more questions: if I flashed another firmware my bootloader will be locked again and which version of Hybroman should I use?
Click to expand...
Click to collapse
nope your bootloader is not touched by flashing a custom ROM
indeed in some cases you have to flash separately a different bootloader so you can use that custom rom (in fact the problem is that bootloader will not give a chance to that kernel to load into memory -it's about a kind of protection)
wich version ? well as you see that thread is a very long one (and that's a sign of a good one ..) but no links in first post but just ask them your question and you get a link surely

try real ics 5.1 with krsh kernel... its really nice on my wt19i

Did u wipe custom data and cache....???
Did u flash the .img file???
If u didn't then ur phone gets stuck at SE logo...
CM9 is ICS based so first
1. flash ICS
2. flash boot.img file (instde cm-9.0.0-coconut.zip)
3. Enter recovery (turn off ur phone and turn it on by pressing volume down key.)
4. wipe custom data and device cache
5. install cm-9.0.0-coconut.zip
6. reboot...
Ur CM9 will work

[Q]so what happens to k-exec when you do new unlock

I'm as happy as anyone else with this new method of unlocking the bootloader. I'm rooted the ODIN way and then have bean's stock rom with imosey's custom rom installed (via the k-exec). I've read that people are doing this with all different kinds of rom and recovery.
My question: what happens to the k-exec? All gets re-written? we don't need to go to stock to get this to work? It seems to me that it would be safer if we re stock, no?
I know there is a one click now but I prefer manual stuff.

I was wondering the same thing. I want to flash an kexec kernel but idk what might happen now that I'm unlocked
Sent from my SCH-I535 using xda app-developers app

vx2ko said:
I was wondering the same thing. I want to flash an kexec kernel but idk what might happen now that I'm unlocked
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You should be fine assuming you still have a kexec compatible recovery. Eventually all roms will move to full unlocked so kexec will pretty much be a thing of the past.

PJnc284 said:
You should be fine assuming you still have a kexec compatible recovery. Eventually all roms will move to full unlocked so kexec will pretty much be a thing of the past.
Click to expand...
Click to collapse
So running this new unlock method can be accomplished with K-exec on the phone? I've always thought that k-exec was a bott=strap kind of a method. Wouldn't this get messed up with this new method?

loveubuntu said:
So running this new unlock method can be accomplished with K-exec on the phone? I've always thought that k-exec was a bott=strap kind of a method. Wouldn't this get messed up with this new method?
Click to expand...
Click to collapse
I'm on Synergy 1.7 (non-nightly) and it's running fine. Still using the stock kernel and not Imo's lean kernel but it apparently still worked for others.

PJnc284 said:
You should be fine assuming you still have a kexec compatible recovery. Eventually all roms will move to full unlocked so kexec will pretty much be a thing of the past.
Click to expand...
Click to collapse
We need a list of non kexec and kexec recoveries and kernels. I've been in the Rom flashing and troubleshooting game for a while but never had to use a locked otloader so this kexec stuff is new. If someone could clarify what's kexec and what's not that would be great
Sent from my SCH-I535 using xda app-developers app

loveubuntu said:
I've always thought that k-exec was a bott=strap kind of a method. Wouldn't this get messed up with this new method?
Click to expand...
Click to collapse
To the best of my knowledge, when the bootchain gets to the boot partition, it loads the kernel on boot.img. It then proceeds to start up the system partition. If you're using kexec, the ROM you're using checks whether the kernel is the expected one or stock. If it isn't the right one, it reboots to recovery, passing instructions to CWR on what to do when it gets there (please feel free to correct me on that part, my knowledge there is vague). That's the first reboot. Once in recovery, those instructions tell recovery to load the right kernel into memory and uses kecex to perform a hardware restart and boot from the kernel it just put in memory. That's the second reboot you see. Once that kernel is loaded up, it starts up the system partition and finishes booting into your ROM.
Before, if the image on boot did not match what the bootloader would permit, it would throw an error and refuse to boot. Unlocking the bootloader allows us to put whatever we want on boot. What got overwritten when you unlocked your bootloader was aboot, the part of the boot sequence that's loaded before the boot partition. If you install a rom that includes a boot.image, now it will just boot from that with whatever kernel. It boots normally, the rom no longer needs to reboot into recovery to load the correct kernel, and all of that kexec infrastructure, which is still there goes unused.
So as long as you don't switch to a recovery without kexec support, you can flash whatever you want, kexec, stock, or using the unlocked bootloader. You can't get yourself into any trouble restoring a backup can't fix.
Of course, if you were to switch to TWRP or another recovery not supporting kexec and then try to boot a kexec rom, you're asking for a bootloop. So stick with the recovery you're using now until every rom or kernel you'd possibly try no longer uses kexec.

lazarus2405 said:
To the best of my knowledge, when the bootchain gets to the boot partition, it loads the kernel on boot.img. It then proceeds to start up the system partition. If you're using kexec, the ROM you're using checks whether the kernel is the expected one or stock. If it isn't the right one, it reboots to recovery, passing instructions to CWR on what to do when it gets there (please feel free to correct me on that part, my knowledge there is vague). That's the first reboot. Once in recovery, those instructions tell recovery to load the right kernel into memory and uses kecex to perform a hardware restart and boot from the kernel it just put in memory. That's the second reboot you see. Once that kernel is loaded up, it starts up the system partition and finishes booting into your ROM.
Before, if the image on boot did not match what the bootloader would permit, it would throw an error and refuse to boot. Unlocking the bootloader allows us to put whatever we want on boot. What got overwritten when you unlocked your bootloader was aboot, the part of the boot sequence that's loaded before the boot partition. If you install a rom that includes a boot.image, now it will just boot from that with whatever kernel. It boots normally, the rom no longer needs to reboot into recovery to load the correct kernel, and all of that kexec infrastructure, which is still there goes unused.
So as long as you don't switch to a recovery without kexec support, you can flash whatever you want, kexec, stock, or using the unlocked bootloader. You can't get yourself into any trouble restoring a backup can't fix.
Of course, if you were to switch to TWRP or another recovery not supporting kexec and then try to boot a kexec rom, you're asking for a bootloop. So stick with the recovery you're using now until every rom or kernel you'd possibly try no longer uses kexec.
Click to expand...
Click to collapse
Thank you, great explanation. To clarify: If you have k-exec and rot before the bootloader unlock leak and now unlock your bootloader with the new leak, you have the best of both worlds. If you use a ROM that uses K-exec, the k-exec part kicks in and if you use the new CM10 alpha without k-exec, the k-exec is unused and the new unlock bootloader is utilized.
Is that right?

Folks...listen up! You can unlock your device on any rom. That being said now that your unlocked, kexec or non kexec kernels will work on a unlocked device. Just make sure your unlocked and using cwm 6.0.1 and everything thats currently available to flash on our device will work. Kexec is not some majical program where we need to worry about bricking our device. Its simply a script that hijacks the boot process after the stock kernel passes verification and then it side loads the custom kexec kernel off of the recovery partition. Unlocking the bootloader has no effect on any of this. Im still using imoseyons 12-2 kexec kernel with beans 8 and the only difference is the device boots up alot quicker. Reason being the bootloader is no longer checking for signed software. Its really no big deal folks..everything still works the same.

droidstyle said:
Folks...listen up! You can unlock your device on any rom. That being said now that your unlocked, kexec or non kexec kernels will work on a unlocked device. Just make sure your unlocked and using cwm 6.0.1 and everything thats currently available to flash on our device will work. Kexec is not some majical program where we need to worry about bricking our device. Its simply a script that hijacks the boot process after the stock kernel passes verification and then it side loads the custom kexec kernel off of the recovery partition. Unlocking the bootloader has no effect on any of this. Im still using imoseyons 12-2 kexec kernel with beans 8 and the only difference is the device boots up alot quicker. Reason being the bootloader is no longer checking for signed software. Its really no big deal folks..everything still works the same.
Click to expand...
Click to collapse
Quick noob question. I rooted and flashed synergy v1.7 using ROM Manager from the app store. When I open the app is says rom manage v5.0.1.5 at the top. Everything is running perfect and do not want to flash a new rom until synergy does a jellybean rom. Should I use the unlock app to unlock my phone now or is there no need? Also is rom manager ok to continue using or should I use something else? Thanks for the help

I got lazy and unlocked using the market app. Running Bean building 8 that is using kexec. I'm still getting three reboots. Is this right?
Sent from my SCH-I535 using xda premium

Custom Rom After Jellybean?

Sorry if this has already been answered, but I couldn't find anything
I have rooted my tf300t, but not unlocked. I know that I can still unlock after the JB update, but is it still possible to install custom recoveries and roms? I don't want to update if there's a risk that I'll be stuck with it.

There is Hydro which is a stock based rom and it just basically makes it feel faster.

adrhodes said:
There is Hydro which is a stock based rom and it just basically makes it feel faster.
Click to expand...
Click to collapse
I realise that custom roms are available, but does the install process still work after updating to jellybean?

you have to flash the old stockrom first. This will install the old bootloader and Recovery. Than flash the ICS Recovery and you are good to go on all the old Customs.

pukeboy said:
Sorry if this has already been answered, but I couldn't find anything
I have rooted my tf300t, but not unlocked. I know that I can still unlock after the JB update, but is it still possible to install custom recoveries and roms? I don't want to update if there's a risk that I'll be stuck with it.
Click to expand...
Click to collapse
If you have upgraded to jb then yes you can install recoveries and Roms but you want to be sure to install those that match jb. For example, if you want to flash cwm recovery, be sure to flash v6.0.1.2, not v5. If you try to install v5, you might brick your tablet. When you access a ROM or recovery post in the Dev section, it should say which it was designed for.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

[Q] help with installation

Hi there!
This is my first post, ive ben around quite a while and never had to post this question.
But ive tried everything with the razr maxx hd to install cm11 because stock kk its really buggy reboots randomely
and terrible battery life, i have root, bootloader unlocked and custom recovery ive tried this:
1:
Stock jb, rooted bl unlocked, twrp 2.6.3.0 flashed a cm11(epinter build, the one that doesnt require kernel 3.4 ) and also slimbuild, aosp etc, and it doesnt boot
2:
Stock kk,rooted, bl unlocked, tried all recoverys to see if theres the issue (cwm 6.0.4.4, twrp) the .zip flashes correctly (unified cm11with kernel 3.4)
And no luck, it never boots
To get the phone back to life, i flash a stock sbf and boots back everything normal. I cant figure out whats missing or whats my error.

wurlJAM00 said:
Hi there!
This is my first post, ive ben around quite a while and never had to post this question.
But ive tried everything with the razr maxx hd to install cm11 because stock kk its really buggy reboots randomely
and terrible battery life, i have root, bootloader unlocked and custom recovery ive tried this:
1:
Stock jb, rooted bl unlocked, twrp 2.6.3.0 flashed a cm11(epinter build, the one that doesnt require kernel 3.4 ) and also slimbuild, aosp etc, and it doesnt boot
2:
Stock kk,rooted, bl unlocked, tried all recoverys to see if theres the issue (cwm 6.0.4.4, twrp) the .zip flashes correctly (unified cm11with kernel 3.4)
And no luck, it never boots
To get the phone back to life, i flash a stock sbf and boots back everything normal. I cant figure out whats missing or whats my error.
Click to expand...
Click to collapse
if your on stock kitkat you need to flash a rom with the 3.4 kernel

billycar11 said:
if your on stock kitkat you need to flash a rom with the 3.4 kernel
Click to expand...
Click to collapse
How is that going to help? Can you point us in the right direction for the ROMs that can work?
Sent from my SM-N900V using Tapatalk

Its because the kernel needs to be the same tipe as :kk bl=kk kernel ive tried and nothing