Database Users

Does flashing a rom unroot a rooted phone???

So I rooted my phone with one click method, changed rom, also because I wanted an unrooted phone again, but it seems that even though I flash a new room I always stay rooted??? Am I doing something wrong??? I thought that flashing a new rom was supposed to restore factory defaults including an unrooted device. Am I wrong??? I started with a XXJID whent to XWJJ4 to XXJK1 and back to XXJID, but it always stays rooted... I want to unroot my phone can anyone help me out please

yes it does, once the custome roms are created they will generally be released rooted to save you the effort.

retroqwe said:
yes it does, once the custome roms are created they will generally be released rooted to save you the effort.
Click to expand...
Click to collapse
Thanks, so what must I do to unroot my phone?? tried the one click metod and it does not work...

Curious as to why you want to un-root it?

shollywood said:
Curious as to why you want to un-root it?
Click to expand...
Click to collapse
Because i am curios as well and should the need arise I see it is not as simple as all that.

There is no reason whatsoever to unroot. But yes, flashing a new firmware will unroot your tab as it would any other device.

ftgg99 said:
There is no reason whatsoever to unroot. But yes, flashing a new firmware will unroot your tab as it would any other device.
Click to expand...
Click to collapse
Not true, I have flashed many roms and always stays rooted

That, my man, is because the roms you were flashing already included su permissions... a new firmware will completely replace the entire filesystem, all settings included. And there are no customised firmwares for the tab atm.
EDIT: just realised you are attempting to answer your own question lol

ftgg99 said:
That, my man, is because the roms you were flashing already included su permissions... a new firmware will completely replace the entire filesystem, all settings included. And there are no customised firmwares for the tab atm.
EDIT: just realised you are attempting to answer your own question lol
Click to expand...
Click to collapse
Wait a moment, I dont get it???? Are you telling me that whoever flashes a Rom from Samfirmware is in fact installing a firmware with root access already installed??? I didn't realize this, but looking at the results of my flashes I guess you must be right

I had to manually root my JK1 ROM after flashing.

I'm saying this shouldn't be happening. Probably its the recovery you need to replace. I'm not sure if its partition gets wiped with Sammy firmwares. I'm not doing any flashing yet as I see no point.

The rom XWJJ4/XXJK1 uses a different partition schema as XXJID used, where XWJJ4 and its successors uses "P1" .PIT file, and XXJID uses "816" .PIT file. Maybe the issue comes from this.

Zeron.Wong said:
The rom XWJJ4/XXJK1 uses a different partition schema as XXJID used, where XWJJ4 and its successors uses "P1" .PIT file, and XXJID uses "816" .PIT file. Maybe the issue comes from this.
Click to expand...
Click to collapse
Perhaps, but from what I understand the XXJID uses "no repartition" to install, so the pit is actually not used when putting on this firmware... I wonder which firmware actually uses this same repartition. I used JHA before putting on JID, and I would have thought this used the same repartition, but still signs of a rooted phone. From what "ftgg99" said I wonder where the roms from samfirmware come from. I guess other devices from were the roms have been extracted, and to extract a rom from a device I think you need root acess, so that is why I am getting leftovers of rooted phones on these roms, namely the SU file which gives me the rom as rooted when I go and check the firmware. I saw that Kies fortunately sees my device as normal so I hope that when an official update will come along there will be no problems with the official upgrade...

Well, flashing a ROM outside of OTA updates invalidates the warranty, so does rooting, if we believe this article:
MOD EDIT:Wait until further instructions.DO NOT EDIT THE POST W/O MY PERMISSION.
Hack only if you can afford the consequences !

Moddage ftw. Super one click modifies the recovery partition, so to lose root you will have to replace it with the original.
So, can we please get the original recovery?

Superoneclick has a unroot function that we may wish it will "restore the original one". While a root guide posted by "chowdarygm" indicated that after unrooting the device that was rooted by superoneclick before, he can't root it again by using the same tool, and have to reflash the rom to make it under control. Given this, the root tool itself is not as perfect as we wished yet, especially with the "rollback" mechanism.

Thanks for this thread you guys, i have Samsung A9 PRO 2016 and flashed magisk patched rom to it, but i have problem the Magisk don't detect instalation and Banking app don't work cause magisk can't hide no settings to do it. Also my apps starts breaking and stopping.

OTA fail help

Hello all
Have searched this forum, but im not really sure what to do.
I've used titanium backup to perm remove a few stock apps, the exchange stock app and amazon app
Now i can't recive any updates OTA, and i get this message..:
assert failed: apply_patch_check("/system/app/Stock.apk"....
E:Error in /sdcard/download/OTA_Ace_HTC_WWE_172_405_3_r2_1_32_405_6_release_1632939lowfu0y78jktpp2.zip
(status 7)
using 2.2 android version number 1.32.405.6
please help
//Cham

You can't accept OTA updates when you are rooted.

I see, but only used temp root with visionary
is that going to affect something?

Or what are my options to get a hold of updates in the future, a costum rom instead? I do kinda like the stock rom, just without stock apps

anyone?

Once again, if you are rooted, it doesnt matter how, you CANNOT accept ota update.
If you deleted something you shouldnt have, then restore the backup to that, or do a factory reset and re-root.

Ok i just figures since it was TEMProot that it didn't matter. Tnx for the reply, tried the factory default option (no luck), is there any place where I can get the Stock firmware to re-flash the phone?
Or would anyone in here recommend another rom ? Tons of custom roms, as I can tell.

Thread moved in Desire HD General.

go here and youll find your rom that you need,
you need the ones that are "RUU_Ace_HTC_WWE" in the file name, as these are what we call World Wide Editions

Thank you very much.
Just to make sure I do not **** something up, what are the steps i should follow, to install the rom?

This is what I did: http://forum.xda-developers.com/showthread.php?t=888109

Got the same problem -- some time ago I removed some "useless" apps from my /system/app folder, and when 1.72 update was released I wasn't able to install it in any way (I was trying to follow this guide). I restored the missing apps, and then everything went fine using the guide mentioned above!
Hope this helps.
sitlet said:
You can't accept OTA updates when you are rooted.
Click to expand...
Click to collapse
Sorry but that ain't correct... You *can* update your phone if you're rooted, the main problem is that root will be gone after update. The best solution is to *always* reject OTA updates provided by HTC and wait until devs here have found a safe way to update your device without losing root privileges.

Thank you
Thank you all, it gave perfectly sense since I'm quite happy with the stock firmware, i'll stick with this. The root is not so necessary for me at least for now
I'm glad it was corrected that visionary did not remove the ability for OTA, that was also what I've read before used it.

Gingerbread OTA back to Froyo

Has anyone tried going back to froyo from the new gingerbread OTA using the sbf file for froyo..... ?

No, why would you want to do that?
I would imagine the RSD Lite method via pc would do it.

If I root it i want to know if i can get back to stock to be able to take back for repairs if i need too....

Should be able to. I can't guarantee as I'm not going to attempt it myself (new phone in 3 days anyway).

I thought you should be able too also but not sure I wanna try without knowing for sure.....

Well to put it in perspective, I ran the leaked GB before SBFing back to stock Froyo. Then ran the OTA. The ability should be there, dunno why I didn't think to mention this before.

Guess maybe a better question would be can you unroot the gingerbread OTA if you root it using the oneclick method ?

This appears to be the blog of the creator, perhaps contact him. I don't have plans to unroot, if I happened to need to bring it in and not void the warranty, I'd just SBF froyo then OTA again. That will surely remove the root.

Yes you can
I have just fixed my phone via the RSDLite method, i got stuck in a bootloop i couldnt get out of and just flashed back to stock froyo without an issue, ran the OTA update and am good to go, so its extremely easy to do

Root, OTA, Market update

Hi guys, after a 6 months period with HTC Wildfire S, i decided it was time to upgrade my device, so here i am, a newbie Nexus S user.
The first things i did with my new toy were unlocking the bootloader, gaining root permissions and installing CWM.
But i noticed that Market isn't updating, it's stuck to THIS version (i think it's 2.13)
Has this anything to do with root and cwm? Or it's just a matter of time and i'll eventually get the update?
Same thing with firmware: at the moment i'm running 2.3.3: looking for updates, and even using the *#*#checkin#*#* code, provided the same result: no FOTA available. Is this due to the root+cwm or i just need to wait?
I know this has already be discussed in the faq, but i find them quite confusing.
I mean, i know i could do a manual update, but i'd like to know whether if i'll ever receive a fota update or if i've lost this chance after root.
Q: I'm rooted with Clockwork and can't install the OTA! I updated to 2.3.1 and lost root! What gives?
most of the time, official OTAs will not install through custom recoveries because of their tendency to break root or restore things like the stock recovery. Also if you've made any modifications to the system files such as replacing the default Mms.apk(messaging) with the custom Black Mms.apk found in the Themes & Apps section, or deleted any .odex files from the system partition, it will not install. The easiest way to update to 2.3.1 is to flash a custom rom such as one of the custom ROMs or use the 2.3.1 Stock NANDROID backup found in the development section. And yes, 2.3.1 "broke root." To regain it, simply follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=884499 (All credit goes to the original author(s) of the linked thread!). The aforementioned procedure is only needed on the Stock Nandroid Backup, not any of the custom ROMs.
Click to expand...
Click to collapse
Thanks in advance for the answers!

There is no update due to the root, i advice you to manually update your phone to the latest version 4.0.3 using cwm, after that root again. finally you will have rooted ics on your nexus s.

uhm, you say i won't receive updates.
FAQ says most of the time i won't receive them.
THIS thread says i will receive them.
I am confused.

from what I can make sense of, it sounds like you should be getting updates. The FAQ you posted says that if you try to install one of the official OTA updates through CWM, it will fail most of the time.
i don't know how reliable that "checkin" trick is, and it may depend on your carrier as well.
if you've already rooted your device, then i would just flash one of the custom roms, you won't want to go back to the OTA after...

Root/cwm recovery/unlocked boot loader etc has nothing at all to do with your device receiving the ota update notification

albundy2010 said:
Root/cwm recovery/unlocked boot loader etc has nothing at all to do with your device receiving the ota update notification
Click to expand...
Click to collapse
Thats correct. It has only to do with the install. (It will fail).. if you dont get the notification for an ota i dont know whats wrong...
Sent from my Nexus S using xda premium

Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?

SavageButcher said:
Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?
Click to expand...
Click to collapse
If you had 2.3.3 the update was probably the 2.3.6 and after that you would have received the 4.0.3 update....anyway from what I remember the version of the ota update is showed in the notification bar...isn't it?!
Sent from my Nexus S using XDA

SavageButcher said:
Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?
Click to expand...
Click to collapse
1. I assume it was the a step up from 2.3.3 to a max of 2.3.6 as OTA updates to 4.0.3 are currently on hold due to battery drain issue
2. your OTA install is failing because you have custom recovery (CWM) but the OTA updates require the stock recovery (3e)
if you really really want to install OTA updates, you gonna have to go back to stock recovery (do a nand restore, hope you have one) then flash the OTA updates for your device

Wanting to unlock and root but also want Marshmallow asap

Should I wait to unlock and root if I want to get Marshmallow or is there a way to get it unlocked and rooted?

I would think as long as you do not stray from the stock software you would still get the OTA update. I do not think unlocking the bootloader and simply rooting the phone would prevent the OTA but I could be wrong.

campbellc1052 said:
I would think as long as you do not stray from the stock software you would still get the OTA update. I do not think unlocking the bootloader and simply rooting the phone would prevent the OTA but I could be wrong.
Click to expand...
Click to collapse
Would rooting and then updating break something though? I thought I may have read that somewhere on here.

I just looked into it a little bit more and I think as long as you do not flash a non-stock recovery image you should just be able to disable any system modifications such as xposed and unroot and the update would come through. You can probably find more information on this on google or the moto forums.

Im sure the devs will capture the OTA and make a flashable version, that's usually what happens. It usually doesnt take more than a day after the OTA to do it.

My plan is to wait until after Marshmallow is out before unlocking the bootloader if rooting. Since we have a unlock available we don't have to worry about updates breaking exploits so I am in no rush. The phone is pretty amazing even without root. Once Marsh is out I will test drive a bit and go from there. It could take a week before a dev drops the update or it could take hours... you never know.

Hmmmmm well I'm unlocked and rooted with TWRP..
But there is a Back to Stock zip..
So once Marshmallow comes out ,I'll just go back to Stock and take the OTA...

ttkyles said:
Hmmmmm well I'm unlocked and rooted with TWRP..
But there is a Back to Stock zip..
So once Marshmallow comes out ,I'll just go back to Stock and take the OTA...
Click to expand...
Click to collapse
Yeah, if you have already done it I'm sure someone can assist in getting you the files needed. Even if a dev can walk me through I don't mind pulling it for you. Maybe there will be a back to stock using the marshmallow image then just reroot after installing twrp and you are good to go

campbellc1052 said:
I just looked into it a little bit more and I think as long as you do not flash a non-stock recovery image you should just be able to disable any system modifications such as xposed and unroot and the update would come through. You can probably find more information on this on google or the moto forums.
Click to expand...
Click to collapse
Root breaks the ability to take an OTA, even using the supersu unroot feature the OTA will fail. The only way to take an OTA is to flash a fully stock system and recovery.

BladeRunner said:
Root breaks the ability to take an OTA, even using the supersu unroot feature the OTA will fail. The only way to take an OTA is to flash a fully stock system and recovery.
Click to expand...
Click to collapse
From what I understand it's not so much root that affects the ability to take an OTA it is the bootloader flag and recovery image. Also I think that while a new OTA would completely overwrite the system directory, since we can unlock bootloader, you can just re-flash SuperSU without issue.

I have to say that I'm a bit confused because Motorola have stated that unlocking the bootloader won't affect OTA updates here - https://motorola-global-portal.cust...tail/a_id/91999/p/1449,8620/kw/bootloader OTA
Can anyone clear this up for sure? I'd say a custom recovery would definitely affect them but not just unlocking the bootloader.

skttrbrain said:
I have to say that I'm a bit confused because Motorola have stated that unlocking the bootloader won't affect OTA updates here - https://motorola-global-portal.cust...tail/a_id/91999/p/1449,8620/kw/bootloader OTA
Can anyone clear this up for sure? I'd say a custom recovery would definitely affect them but not just unlocking the bootloader.
Click to expand...
Click to collapse
That's right...unlocking the bootloader alone won't stop an OTA. The custom recovery will be the issue. Basically if you're rooted and running TWRP all you have to do is follow the instructions in the Return To Stock thread and you're good to go for an OTA. Its a pretty simple process.