Is there a way to root without the change hboot and cwm?
If not is they a way to restore the stock hboot and recovery so as to be able to accept updates from HTC?
story to whom intersted
I previously used revelotionary to s-off and changed HBoot from 1.18.000 to 1.17.000 and installed cwm 4.x and installed su as the guide it was ok.
Later I needed to have an OTA update for the stock rom, so I used a stock rom rru and installed them updated everything ok, but I have problem with battery.
So either the stock rom is bad in power (radio 10.56.9035.00U_10.14.9035.01M, build 1.50.415.1) or need to clear the stats for the battery so need root.
If I use the make the default , I will lose ability to have updates unless go back to the old stock and so on....the problem that I need arabic native which have very few leaked roms so I have to go to a very old version.
Related
Ok.. I bought my Nexus S with 2.3.1 installed. I rooted it shortly after deciding I would keep the phone for awhile. According to all the guides I looked through, Clockwork Recovery won't stick unless that one file is renamed..
Well, come to find out, when I tried accepting the OTA update for 2.3.4, I somehow lost stock recovery and have Clockwork still installed. I've been running the stock software, stock kernel, with the bootloader unlocked and superuser installed. I never renamed the file in order to keep my stock recovery, just in case, but somehow still lost it.
I want to update my phone from 2.3.1 to 2.3.4 but I don't want to lose my app data and whatnot so I want to know if it is possible to install the OTA updates via Clockwork.. I managed to find the zip file for the update that will bring my phone from 2.3.1 to 2.3.3 and then the zip file for 2.3.3 to 2.3.4 from Google.
I don't want to flash a ROM, just looking to keep everything mostly stock but with root. I've searched for an answer but must be looking up the wrong terms, as I can't seem to find any info on doing this under the circumstances
Any help would be appreciated, thanks in advance!!
Phone: i9020t
Android: 2.3.1
Baseband: I9020XXJK8
Kernel: 2.6.35.7-g7f1638a / [email protected] #1
Build: GRH78
hkt03 said:
Ok.. I bought my Nexus S with 2.3.1 installed. I rooted it shortly after deciding I would keep the phone for awhile. According to all the guides I looked through, Clockwork Recovery won't stick unless that one file is renamed..
Well, come to find out, when I tried accepting the OTA update for 2.3.4, I somehow lost stock recovery and have Clockwork still installed. I've been running the stock software, stock kernel, with the bootloader unlocked and superuser installed. I never renamed the file in order to keep my stock recovery, just in case, but somehow still lost it.
I want to update my phone from 2.3.1 to 2.3.4 but I don't want to lose my app data and whatnot so I want to know if it is possible to install the OTA updates via Clockwork.. I managed to find the zip file for the update that will bring my phone from 2.3.1 to 2.3.3 and then the zip file for 2.3.3 to 2.3.4 from Google.
I don't want to flash a ROM, just looking to keep everything mostly stock but with root. I've searched for an answer but must be looking up the wrong terms, as I can't seem to find any info on doing this under the circumstances
Any help would be appreciated, thanks in advance!!
Phone: i9020t
Android: 2.3.1
Baseband: I9020XXJK8
Kernel: 2.6.35.7-g7f1638a / [email protected] #1
Build: GRH78
Click to expand...
Click to collapse
Yes, you can install the OTA with CWM.
Why don't you just install a stock, rooted rom.
It is just the stock rom, rooted and packed in zip ready to be flashed in clockwork rec.
Sent from my Nexus S using Tapatalk
deeren said:
Why don't you just install a stock, rooted rom.
It is just the stock rom, rooted and packed in zip ready to be flashed in clockwork rec.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Don't really feel like setting up my phone again and losing my app data.. I didn't mind too much with my G1, but I've got so much junk on my NS that I don't want to lose. Just want to update like normal..
i guess you have two options update:
1 - you could flash original ota from cwm, but you will lose the root and cwm recovery, then you will need to root again, but to root in 2.3.4, you will need to unlock booloader, and that gonna make you lose everything...
2 - you also could try to flash stock, deodexed and rooted zip, but i really don't know if it gonna work (although i don't see why it wouldn't)...
thiagodark said:
i guess you have two options update:
1 - you could flash original ota from cwm, but you will lose the root and cwm recovery, then you will need to root again, but to root in 2.3.4, you will need to unlock booloader, and that gonna make you lose everything...
2 - you also could try to flash stock, deodexed and rooted zip, but i really don't know if it gonna work (although i don't see why it wouldn't)...
Click to expand...
Click to collapse
My bootloader has been unlocked, flashing the ota doesn't lock it back up does it? I always thought I only lost root access, but not lock up the bootloader
hkt03 said:
My bootloader has been unlocked, flashing the ota doesn't lock it back up does it? I always thought I only lost root access, but not lock up the bootloader
Click to expand...
Click to collapse
well, if your bootloader is unlocked you don't have any problem at all! =o)
since you said that you rooted in 2.3.1, i thought you followed the guide to make it without unlocking bootloder.
with unlocked bootloader, that's what i would do:
- reboot in recovery (cwm recovery)
- nandroid backup
- wipe cache / dalvik-cache
- flash official zip OTA for your specific model. you can find it here: http://forum.xda-developers.com/showthread.php?t=1056062
- boot and see if everything is okay
after that, you will lose root and cwm recovery! now you have to root just like you had done before (flashing cwm from bootload and applying su file).
hope it can helps!
Is it possible to run stock rom with S-OFF, rooted device and CWR (with OTA available)?
bibihtc said:
Is it possible to run stock rom with S-OFF, rooted device and CWR (with OTA available)?
Click to expand...
Click to collapse
Yes you can run stock rom with s-off and root access however I am not sure if OTA updates will still work. Even if they did work I would imagine you would lose root access once the OTA update has been applied.
So when I flash stock ruu.exe nothing happens with S-OFF neither root?
You will need the stock recovery to get OTA updates to install, they won't work with CWM
and with stock recovery I'll be able to create backups of installed roms? And how do I reinstall stock recovery?
thx
You can't backup with the stock recovery, no
Got it, thx.
And how do I install stock recovery?
Get it from an RUU, then flash it using fastboot commands
Android Recovery Manager
There is a much easier solution: Android Recovery Manager
Hey,
I'm a little confused right now, and just want some clarification on a few things since I know if I do this wrong, my phone might get bricked in the process.
Right now I'm running stock HTC Sense 3.0 (went to my stock backup from my last ROM) rooted and s-off, with ClockworkMod Recovery
HBOOT 1.17
My end goal is to end up with a device where I can flash CM9, and have it work properly. And I believe I need the android 4.0/sense 3.6 update. Which I cannot get since I got my phone s-off
From what I understand I need to flash the stock recovery to be able to install the ICS OTA update, so my device will actually run CM9.
Where I am stuck here is what file do I need, and do I flash it just like a ROM?
Any help would be hugely appreciated!
Thank you
You need to update the firmware to run any ICS ROM.
Once you update the firmware you can flash CM9 like any other ROM.
Hi am having a problem after going back to telstra stock after being on rohans JB build 3. It was really bad at connecting on LTE so I wanted to go back to stock where I have less problems. So now the 4.0.4 OTA update is available which fixes the one of the main reasons I found a ROM, that stupid settings bar.
However when I reboot to install the OTA it just boots into TWRP (v 2.2.2). I cant manually apply update from within recovery. It just gives an error. If I reboot from recovery nothing is applied.
Android v 4.0.3, software version 1.89.841.9
Do I have to get rid off TWRP or find a RUU and and apply that image? Was there some boot locking thing I need to do through abd to get the OTA to work?
piscario said:
Hi am having a problem after going back to telstra stock after being on rohans JB build 3. It was really bad at connecting on LTE so I wanted to go back to stock where I have less problems. So now the 4.0.4 OTA update is available which fixes the one of the main reasons I found a ROM, that stupid settings bar.
However when I reboot to install the OTA it just boots into TWRP (v 2.2.2). I cant manually apply update from within recovery. It just gives an error. If I reboot from recovery nothing is applied.
Android v 4.0.3, software version 1.89.841.9
Do I have to get rid off TWRP or find a RUU and and apply that image? Was there some boot locking thing I need to do through abd to get the OTA to work?
Click to expand...
Click to collapse
Pretty sure you have to relock your bootloader and run an RUU to get your phone to true stock. Then OTA. Although, if the RUU was based off 4.0.4 you wouldn't have to OTA. You can always re-ulock your phone after an RUU as long as you have your unlock token and/or super CID.
Did you just flash a stock ROM?
Also, pretty sure there are 4.0.4 stock ROMs out there that you could flash so you wouldn't have to relock your phone.
Butters619 said:
Pretty sure you have to relock your bootloader and run an RUU to get your phone to true stock. Then OTA. Although, if the RUU was based off 4.0.4 you wouldn't have to OTA. You can always re-ulock your phone after an RUU as long as you have your unlock token and/or super CID.
Did you just flash a stock ROM?
Also, pretty sure there are 4.0.4 stock ROMs out there that you could flash so you wouldn't have to relock your phone.
Click to expand...
Click to collapse
Thanks I restored a backup I made before flashing the ROM. Might try and find another ROM to see how 4G goes.
Fixing a connectivity issue on one custom ROM is not a good reason to go stock. I think the OTA needs stock recovery, so that is why you are getting stuck at recovery. Even if it works, you lose root. Its a step backwards, so why would you want to do that?
Just flash a ROM based on 4.0.4 from Development. You can pick a custom ROM, or a stock rooted one (safe to flash from TWRP), if you want stock.
If you are rooted, don't install a OTA or run RUU (unless you are trying to fix a soft brick). Good rule for any Android device.
Hi there !
I have U11 2.31.400 version
-Bootloader Unlocked
-TWRP installed
- Root with Masgik
Now i want get OTA update
-First, NO RUU, i tried Restore NANDoid backup and Flash stock recovery (same version)
(https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=1564536856)
-> Not work
-I tried flash stock Firmware ( got 35_RU_Partition_not_support firmware error)
Anyone can tell me how to got OTA with out RUU??
Hi there
I think we're in the same situation.
I also unlocked my phone, installed TWRP and Magisk on stock system and did a NANDroid Backup before doing so.
In order to get the OTA I restored stock recovery (which i had to extract from OTA, since i forgot to back it up) and started OTA.
--> Red Triangle!
Even after restoring stock NANDroid the OTA wouldn't install.
My mistake i think was that i didn't kept the stock system read only when i did the backup in twrp and swiped to allow modifications.
According to some threads here, even mounting the system r/w would break OTA functionality.
So since i also have no RUU for my device, i don't have the chance either to go back to stock. Maybe you did that mistake too.
The only way i can think of now, is to go temporary S-OFF, change CID and MID (to 401 international for example), flash Firmware and run the RUU for it.
But i'm not sure it'll still work after flashing the firmware.
Can anyone maybe confirm this way would work?
Thanks
Edit: Hi, in case you're still having this problem, here's a solution:
Reverting to stock