Hey im tryinna OTA update my One S its at Android Version 4.0.4 Sense 4.1 and i have an OTA ive had it for a while now. How could i update it and keep my root? Or if i install a higher version custom rom will it brick my phone?
Sent from my HTC VLE_U
Br00talBean said:
Hey im tryinna OTA update my One S its at Android Version 4.0.4 Sense 4.1 and i have an OTA ive had it for a while now. How could i update it and keep my root? Or if i install a higher version custom rom will it brick my phone?
Sent from my HTC VLE_U
Click to expand...
Click to collapse
not sure what you mean with your last sentence... but:
in my case the ota deleted my root. but I also recommend to do a factory reset after updating to 4.1 sense 4+, just to be sure that you have a clean jb rom (do titanium backups of your apps you wanna keep).
but you have to be on stock recovery if you want to apply the ota.
after your update you can root your phone again.
applying the ota wont have any effect on flashing a higher / newer custom rom.
you only have to be unlocked and on custom recovery. but you alawys have to flash the boot.img of the custom rom after flashing the custom rom zip.
NQNH said:
not sure what you mean with your last sentence... but:
in my case the ota deleted my root. but I also recommend to do a factory reset after updating to 4.1 sense 4+, just to be sure that you have a clean jb rom (do titanium backups of your apps you wanna keep).
but you have to be on stock recovery if you want to apply the ota.
after your update you can root your phone again.
applying the ota wont have any effect on flashing a higher / newer custom rom.
you only have to be unlocked and on custom recovery. but you alawys have to flash the boot.img of the custom rom after flashing the custom rom zip.
Click to expand...
Click to collapse
My bad i wasnt even payin attention to what i was typing and im still pretty much a noob at Root stuff so please bear with me lmao
Lets say i try to flash a 4.2.2. Rom even though im originally at 4.0.4. Would it brick my phone?
So would stock recovery be the stock rom i still hqve after rooting? I havent applied any custom roms at all since ive rooted
Sent from my HTC VLE_U
Br00talBean said:
My bad i wasnt even payin attention to what i was typing and im still pretty much a noob at Root stuff so please bear with me lmao
Lets say i try to flash a 4.2.2. Rom even though im originally at 4.0.4. Would it brick my phone?
So would stock recovery be the stock rom i still hqve after rooting? I havent applied any custom roms at all since ive rooted
Sent from my HTC VLE_U
Click to expand...
Click to collapse
the rom you want to flash doesnt care about your previous rom, because you wiped your previous rom.
so it really doesnt matter which rom you have before if you want to flash a new rom.
its like.. you have installed windows xp, then format your hdd and install windows 7, windows 7 doesnt take a --- about the old os
recovery and rom are two different parts.
you can stock recovery and custom rom, you can have custom recovery and custom rom, you can have stock recovery and stock rom.. blaaa
NQNH said:
the rom you want to flash doesnt care about your previous rom, because you wiped your previous rom.
so it really doesnt matter which rom you have before if you want to flash a new rom.
its like.. you have installed windows xp, then format your hdd and install windows 7, windows 7 doesnt take a --- about the old os
recovery and rom are two different parts.
you can stock recovery and custom rom, you can have custom recovery and custom rom, you can have stock recovery and stock rom.. blaaa
Click to expand...
Click to collapse
Oooh okay i get what youre saying. Soo recovery and the rom are two different things. I can upgrade to whatever gigher version i want. What about the OTA? If i upgrade to higher version custom rom will the OTA icon go away?
Sent from my HTC VLE_U
Br00talBean said:
Oooh okay i get what youre saying. Soo recovery and the rom are two different things. I can upgrade to whatever gigher version i want. What about the OTA? If i upgrade to higher version custom rom will the OTA icon go away?
Sent from my HTC VLE_U
Click to expand...
Click to collapse
after u have flashed a custom ROM, you wont get any OTA updates
Well, not from HTC anyways
Seraz007 said:
after u have flashed a custom ROM, you wont get any OTA updates
Well, not from HTC anyways
Click to expand...
Click to collapse
Oooooooh okay i get it now wow haha so custom rom updates are the OTA pretty much once its flashed on there?
Sent from my HTC VLE_U
Br00talBean said:
Oooooooh okay i get it now wow haha so custom rom updates are the OTA pretty much once its flashed on there?
Sent from my HTC VLE_U
Click to expand...
Click to collapse
well no
but u can update and then Root
That way you'll have the OTA radio and hboot and the custom ROM
Related
My sensation is s-off. I want stock recovery. Can I get root without cwm? If I just download the su app from market?
Thanks.
Oops please move to q/a
Nope, but if you don't like CWM you can restore back by doing this: http://forum.xda-developers.com/showthread.php?t=1228648&highlight=OTA+stock
So I can flash cwm apply su/root then flash back stock recovery and I will get Ota updates with no problems?
Afaik, chances are good, that you'll get OTA updates, but I think you'll also lose root then.
hg3atintin said:
So I can flash cwm apply su/root then flash back stock recovery and I will get Ota updates with no problems?
Click to expand...
Click to collapse
Yes, worked for me ALSO: Read it through the guide, and insure that you got everything ready, if something should go the other way
bubuthebear said:
Afaik, chances are good, that you'll get OTA updates, but I think you'll also lose root then.
Click to expand...
Click to collapse
Nope, only if it is a brand new version, like the ICS, then you will loose it. But not if you change from gingerbread 2.3.4 to 2.3.5
TheStigx said:
Nope, only if it is a brand new version, like the ICS, then you will loose it. But not if you change from gingerbread 2.3.4 to 2.3.5
Click to expand...
Click to collapse
My experience is, that one will have to reapply root, if he installs something from stock.
But maybe I did something wrong in the past
My experience with CWM has been nothing but good. You should just install that recovery. I think, in my opinion you would like it. I've had it on my HTC sensation for several months now. No issues
100% agree guys here have latest updates in there roms before any ota updates - you can be running ics now if u want . U can always go back to stock s-on later. I'm no techie but I would never go back unless I needed to for warrenty
Sent from my HTC Sensation Z710e using XDA App
Hi all,
I'm sorry about my stupid question but I really don't know nothing about that . I had rooted and flashed my NS and installed the matr1x kernel (very good btw), and now I knew that JB will be available to NS. My question is, need I back to stock kernel to receive the update?
Thanks
Sent from my Nexus S using xda app-developers app
Gnng
You have to understand that installing an OTA (official update) on a rooted device regardless of what kernel can cause problems, as it did with my Nexus S before. I suggest you make a NANDroid backup at all times before you install any ROMs, official or Custom. You can also use Titanium backup and others.
There's still a slight while until the new JB 4.1 comes out. It's suggested that you install a Custom JB 4.1 ROM for your Nexus S as though you don't cause any problems. I think it's OK if you do it with the kernel pre-installed. But people always install the Custom ROM THEN they install the Kernel, I think installing a new ROM always overwrites the kernel, if it comes with it.
EDIT:
In short, wait for the JB Custom ROM and you don't have to revert back to stock kernel, when you do the update it will automatically overwrite. Most Custom ROMs come with Stock/ordinary kernels. So then the user can flash whatever kernel they like in your case, matr1x.
Wish you the best of luck, and I am waiting for the Nexus S JB to come out as soon as possible
Ota binary patches the boot image iirc. So it can get all messed up.
Sent from my Samsung Epic 4G using Tapatalk 2
Yeah, what he said!
MДЯCЦSДИT said:
Ota binary patches the boot image iirc. So it can get all messed up.
Click to expand...
Click to collapse
andezzat,
Thank you very much for the help.
andezzat said:
Gnng
You have to understand that installing an OTA (official update) on a rooted device regardless of what kernel can cause problems, as it did with my Nexus S before. I suggest you make a NANDroid backup at all times before you install any ROMs, official or Custom. You can also use Titanium backup and others.
Click to expand...
Click to collapse
I didn't any backup before flashing a new kernel :crying:, so what can I do now if I want my stock kernel back?? What's a NANDroid (I know that is a tool but how can I do it?) ? Is Titanium bkp easily?
There's still a slight while until the new JB 4.1 comes out. It's suggested that you install a Custom JB 4.1 ROM for your Nexus S as though you don't cause any problems. I think it's OK if you do it with the kernel pre-installed. But people always install the Custom ROM THEN they install the Kernel, I think installing a new ROM always overwrites the kernel, if it comes with it.
Click to expand...
Click to collapse
I prefer wait for stock JB Rom and probaby I'll , but, can I already find some JB ROM?
In short, wait for the JB Custom ROM and you don't have to revert back to stock kernel, when you do the update it will automatically overwrite. Most Custom ROMs come with Stock/ordinary kernels. So then the user can flash whatever kernel they like in your case, matr1x.
Click to expand...
Click to collapse
I don't need to remove the kernel even unroot my cell, alright?
Thank you!!
Gnng said:
I didn't any backup before flashing a new kernel :crying:, so what can I do now if I want my stock kernel back?? What's a NANDroid (I know that is a tool but how can I do it?) ? Is Titanium bkp easily?
Click to expand...
Click to collapse
A NANDroid backup is a internal memory backup. You can create one by booting into Recovery (Power off your phone and Hold Power and Down on your volume buttons.) If you rooted your phone and unlocked your bootloader (that's what you had to do to flash a new kernel), you should be able to load ClockworkMod or TeamWin Recovery and do a backup of your phone.
Gnng said:
I prefer wait for stock JB Rom and probaby I'll , but, can I already find some JB ROM?
Click to expand...
Click to collapse
There's one rom but it's a port from the SDK and the amount of major bugs is high so it's not recommended but you could try another custom rom meanwhile, I can't go back to stock after trying custom roms, like AOKP and Cyanogenmod 9. Make sure you backup your apps and some settings (not everything will be compatible between stock and custom so pay close attention to which system setting you'll backup) with Titanium Backup.
To sum it all up for you
There's a Jelly Bean release which is unstable and has no sound, and will not be fixed until the REAL version comes out.
NANDroid backs up the whole internal memory on the phone including the system, it can be done from clockworkmod recovery.
Titanium backup, backs up specific settings and information that you choose, available from the playstore.
You don't need to unroot or go back to a STOCK kernel in order to flash a CUSTOM ROM. DO not however flash a STOCK rom after rooting, as at times that can cause problems.
If you want to go back to a STOCK ROM after rooting a device, there's a way, check this guide
http://forum.xda-developers.com/showthread.php?t=1063664
and choose your Nexus S model: To acquire model, go to Settings - About - Baseband version. if it says I9023 at the start that's your Nexus S's model
Choose one of the Fastboot Stock ROMs and use the Fastboot method to flash the ROM. That is a good way to go back to STOCK ROM if anything bad happens
By the way you should expect the new OTA official 4.1 update for the Nexus S to be on your model's page.
NOTE: Using Fastboot to flash a ROM is very clean. However this will delete all your data and if you do everything correctly will lock your bootloader and unroot your phone. So use Fastboot only when you really feel the need to.
Cheers
and stay tuned for Jelly Bean :victory:
andezzat said:
To sum it all up for you
You don't need to unroot or go back to a STOCK kernel in order to flash a CUSTOM ROM. DO not however flash a STOCK rom after rooting, as at times that can cause problems.
Click to expand...
Click to collapse
That means, when I receive the official 4.1 update notification, I should unroot my phone first and just install it after?
Gnng said:
That means, when I receive the official 4.1 update notification, I should unroot my phone first and just install it after?
Click to expand...
Click to collapse
OK first off, do not install the update using the system update method from about, as that is a 100% stuff up if you're still rooted or on a Custom ROM.
However to update I think flashing a stock ROM but USING Clockworkmod works fine!
Someone please confirm, as I am not 100% sure
However what I am sure about is that if you run into any troubles installing your STOCK ROM using Fastboot is very very good and clean, however there are 2 things:
1. You will wipe everything COMPLETELY
2. You need the ROM to be in a fastboot format kind of way for you to flash it
There's a guide and everything for fastboot.
---------- Post added at 12:35 AM ---------- Previous post was at 12:33 AM ----------
Personally I will wait for a custom ROM for 4.1 if it doesn't take too long as that's guaranteed and will obviously be faster and safer to install on a ROOTED device.
Someone still confirm if installing Stock ROM while over Custom ROM while ROOTED through CWM is OK or not!?
Hummm, ok...
I'm already using the Stock ROM, I just flashed a new kernel, and I prefer install the stock kernel and unroot my phone. Just to let it clean.
After I install the JB official update, maybe I flash and root again, depends of Google :laugh:
Do you know where can I download a trust official 4.0.4 kernel from the forums? My phone is a Nexus S I9020AUCKJ1, Version Number: IMM76D
Thanks!!!
I have h-boot 1.14 withe twrp recovery, I backed up my phone with a previous rom i had and my question is would I have to install the image again after i restore the phone or should the phone restore without any problems.
cal4877 said:
I have h-boot 1.14 withe twrp recovery, I backed up my phone with a previous rom i had and my question is would I have to install the image again after i restore the phone or should the phone restore without any problems.
Click to expand...
Click to collapse
Most of the time yes you will have to install the boot .img manually coming from a different base or Rom... But say if you're on viper and your back up is the same base sense Rom you probably wouldn't have to reflash it... But if coming from cm10 or anything else yes
a box of kittens said:
Most of the time yes you will have to install the boot .img manually coming from a different base or Rom... But say if you're on viper and your back up is the same base sense Rom you probably wouldn't have to reflash it... But if coming from cm10 or anything else yes
Click to expand...
Click to collapse
Awesome thanks man, also im currently running nocturnals dirty rom I believe this is a AOKP rom, now if i want to flash another AOKP or any other CM10 base rom wouldnt the image be the same? or the i have to flash another image of the rom aswell?
cal4877 said:
Awesome thanks man, also im currently running nocturnals dirty rom I believe this is a AOKP rom, now if i want to flash another AOKP or any other CM10 base rom wouldnt the image be the same? or the i have to flash another image of the rom aswell?
Click to expand...
Click to collapse
Be safe and flash it
Is it necessary to reflash rom before restore or can you just fastboot flash boot.IMG and just restore backup?
Sent from my One X using xda premium
I believe you have to flash boot. IMG and than restore according to the comments up there
I just wish we had to option to downgrade the software/hboot without going thru all those steps listed, I remeber i had the htc inspire and you will be able to downgrade hboot by choosing a downgraded version of Ruuu files.
cal4877 said:
I just wish we had to option to downgrade the software/hboot without going thru all those steps listed, I remeber i had the htc inspire and you will be able to downgrade hboot by choosing a downgraded version of Ruuu files.
Click to expand...
Click to collapse
Yeah I loved the inspire that's what got me into android... But I got my phone on hboot 1.09 I've never done the downgrade process but I heard it can be pretty simple
Trying to solve a lag/crash issue with any ROM I install on my or my wifes phone. Reading the forums I've seen references to needing to install the official Jelly Bean RUU before flashing a Jelly Bean ROM like Viper XL, etc.
To do this, do I need to be S-OFF first?
Both our phones are already rooted (never took the 2.20? update, so never any issues with root).
Would it be something like this?
S-OFF the phone.
Install Jelly Bean RUU
Re-root
Install Jelly Bean ROM
Thanks!
that would work fine, you would need to s-off to run the jb update. as far as lag from jb sense roms, are you doing a full wipe before flashing?
Instead of "re-root", just push twrp 3.xxx to the phone. Then you can flash whatever rooted Rom you want. Has to be v3 or higher since the touchscreen drivers were updated. Personally I downgraded my touchscreen drivers to use 2.2.2.0 instead cause I'm partial to that version.
Sent from my HTC One X
ECEXCURSION said:
Instead of "re-root", just push twrp 3.xxx to the phone. Then you can flash whatever rooted Rom you want. Has to be v3 or higher since the touchscreen drivers were updated. Personally I downgraded my touchscreen drivers to use 2.2.2.0 instead cause I'm partial to that version.
Sent from my HTC One X
Click to expand...
Click to collapse
cwm ftw!!!
do the touchscreen driver downgrade like ECEXCURSION said though.
DvineLord said:
that would work fine, you would need to s-off to run the jb update. as far as lag from jb sense roms, are you doing a full wipe before flashing?
Click to expand...
Click to collapse
Yeah I completely wipe everything including storage. Still get lag after a while, still get freezes and reboots.
Just trying to figure out the best way to do this, step by step.
jburkco said:
Yeah I completely wipe everything including storage. Still get lag after a while, still get freezes and reboots.
Just trying to figure out the best way to do this, step by step.
Click to expand...
Click to collapse
You'll want to:
s-off
run ruu
update if your ruu doesnt include the latest update.
ruu will not relock your bootloader nor do you need to relock so no need to unlock or reroot.
fastboot flash recovery. i suggest twrp 2.3.x
then you can downgrade your touchscreen if you intend to use an older recovery or an aosp rom but i like to think the updates made improve things so i wouldnt downgrade unless you need to for an aosp rom or older twrp version.
flash whatever rom you like! if you just want stock rooted boot to recovery after flashing and it will prompt to root your rom when you go to reboot from within recovery.
good luck and have fun!
Okay, whats the reason behind downgrading the touchscreen drivers and using TWRP 2.3 vs 3.0
jburkco said:
Okay, whats the reason behind downgrading the touchscreen drivers and using TWRP 2.3 vs 3.0
Click to expand...
Click to collapse
-JB touchscreen firmware does not work with AOSP roms. Your touchscreen won't function.
-TWRP 2.4.x seems to cause problems with flashing for a lot of people.
jburkco said:
Okay, whats the reason behind downgrading the touchscreen drivers and using TWRP 2.3 vs 3.0
Click to expand...
Click to collapse
you need to downgrade touchscreen driver so you can use non-jb sense roms such as aosp roms and ics sense roms. he meant to say twrp 2.3 vs 2.4, twrp 2.4 can give many users random issues. i personally haven't had a single issue with official cwm.
Okay but since I'll be using ViperXL, the touchscreen wont be an issue. Thanks for all the help everyone.
2.4 doesnt properly wipe partitions and remnants are left behind causing issues.
Hey guys its been a really long time sense ive updated my phone im running the google play 4.4.4 rom right now and I want the latest normal stock htc rom rooted of course would someone mind telling me what i need in terms of radios and roms to flash
Bierce22 said:
Hey guys its been a really long time sense ive updated my phone im running the google play 4.4.4 rom right now and I want the latest normal stock htc rom rooted of course would someone mind telling me what i need in terms of radios and roms to flash
Click to expand...
Click to collapse
Check out Dotta's thread in general. Youre looking for the ruu. Im assuming your s-off, so look for the latest (5.0.1) this comes with computer run program or load from sd card via hotboot. This comes pre rooted, so after that youll have to set up your recovery again, and after that youre good to flash any rom youd like. Digital high's GPE rom has an update to 5.1 support, so look there.
Link to ruu - http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
okay i followed the instructions flashed the ruu from hboot and rebooted back to my normal google play rom so can i just download a normal 5.1 rom now?
also is there a decent stock 5.1 sense rom thats debloated I kind of want to go back to that or cyanogen
Bierce22 said:
also is there a decent stock 5.1 sense rom thats debloated I kind of want to go back to that or cyanogen
Click to expand...
Click to collapse
100% stock ROM
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
also mine based off this base pretty much stock with some tweaks
http://forum.xda-developers.com/ver...rom-fluent-rom-v1-0-rls1-4-16-1540-8-t3007173
(if you want to debloat more than what the ROM has, just download something like root explorer and remove what you don't want. Takes all of 5 minutes at most and a reboot)
andybones said:
100% stock ROM
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
also mine based off this base pretty much stock with some tweaks
http://forum.xda-developers.com/ver...rom-fluent-rom-v1-0-rls1-4-16-1540-8-t3007173
(if you want to debloat more than what the ROM has, just download something like root explorer and remove what you don't want. Takes all of 5 minutes at most and a reboot)
Click to expand...
Click to collapse
I think im just going to stick with digitalhighs gpe roms ive been running the 4.4.4 version for months now and use the aroma installer to install sense
Bierce22 said:
I think im just going to stick with digitalhighs gpe roms ive been running the 4.4.4 version for months now and use the aroma installer to install sense
Click to expand...
Click to collapse
Your phone my friend, run what makes you happy.
Was just answering the question you asked. :good:
andybones said:
Your phone my friend, run what makes you happy.
Was just answering the question you asked. :good:
Click to expand...
Click to collapse
hey i flashed that ruu but my wifi isnt working in the gpe rom did i miss something?
Bierce22 said:
hey i flashed that ruu but my wifi isnt working in the gpe rom did i miss something?
Click to expand...
Click to collapse
May get better luck asking in said ROM thread.
Should be working from what I've read.
andybones said:
May get better luck asking in said ROM thread.
Should be working from what I've read.
Click to expand...
Click to collapse
well my phone is in a bootloop now and i cant get into hboot because it sees the ruu and wants to flash it and i cant get my sd card out
Bierce22 said:
well my phone is in a bootloop now and i cant get into hboot because it sees the ruu and wants to flash it and i cant get my sd card out
Click to expand...
Click to collapse
You need to remove sd card, or boot to a ROM and change the name of file on sdcard....
Delete
If youre using twrp flashify doesnt have the latest update the latest is 2.8.7.0, youll have to install 2.8.5.0 and then and flash the upgraded img. In recovery. I had raido problems going to 5.1 update and the way i fixed it was by updating twrp before flashing rom. Let your phone read hboot, hit power down, eject sd card and then reboot. You can flash ruu again to start clean and fix bootloop, if that doesnt work the exe version does work. Advise is to remove sd card powered down, so when in hboot you can select and load into fastboot.
Best of luck,