Hi - I am new in Android as Desire is my first such OS in use, however it is far more interesting as WM and not as boring as iPhone OS
Anyway - I know that there are some ways to get rooted ROM from xda or modaco, but is there a way to root my own?
aren't there two steps to root the phone? 1st to apply modified bootloader to allow recovery via pc (using gold card) and 2nd to apply rooted rom via SD card?
going further - what if I will apply stock rom, meaning i will unroot my device, then apply new bootloader performing the 1st part of the rooting process, then - somehow (this is the question how) - will apply stock rom in zip file and finally apply super user on top of it?
this are just my thoughts, i am not a developer and maybe i am wrong ?
Cheers
hi.im new so please go easy
anyway my question is what the difference between debranded and rooted.i had stock o2 desire and put new rom on it and made the goldcard thing but aint sure if im rooted or what??i cant seem to get the ota update and aint sure what rom to upgrade for the new ota update(if there is one)also my camera goes split screen sometimes(kinda purple and pink)with 2 images sometimes.any help would be greatly appreciated.thanks H
First how did you put a new rom on it? If you made the goldcard and ran a .exe file on your computer you are debranded Explanation to follow:
Debranding: as the word says, this is about removing a certain branding(could be orange or in you case o2 software stuff) In order to do this we flash a stock(non rooted) rom directly from HTC without all the branding. This is normally only possible on unbranded phones, as branded ones should only be able to run a rom from whatever carrier branded it. Here we use the goldcard in order to make the phone accept original software from HTC and not only from the carrier. So the only difference made is, that we get rid of all the carrier stuff and only have original HTC firmware.
Rooting: this is very different, and as the name suggests, this is something we do to gain root access(full system access without limits from the software) to the system. This is done by placing a su-binary in /system/bin and the superuser.apk in /system/app, because then we can grant su-access to apps using the binary.
The actual root process is the hard part, because on stock phones, we cant place those files, so we must use some sort of security hole. On desire we use a hole, which lets us replace the recovery, and then we can use a custom recovery to place the su-files and get root.
thanks morten
would you have info on an easy to do root option for a dummy
i cant get the new update as my phone crashes everytime i try to install it,
plus i would like to get the full benefits of my handset and get some cool themes and stuff.if i root it does it affect the downloading of apps and stuff??many thanks H
Use this link http://forum.xda-developers.com/showthread.php?t=788044. I did it last night and it works perfectly.
However, I now have a question. My phone is successfully rooted and I would like to set it up so that all apps run off the SD. I know this can be done, I have seen reference to apps2SD but I can´t work out what I need to do. Also, I presume I will lose everything on the SD at the moment?
I know it can't be done right now but all I want is the stock rom with superuser installed. When the one-click comes out do you guys think it will have the option?
Sent from my Nexus 7 using Tapatalk 4 Beta
Why not just unlock? You can always lock it again if you want to return to factory.
^^ This, plus if you don't want to replace the recovery you can always use ADB to boot do a different recovery like TWRP to flash the SuperSU :good:
Will an unlocked bootloader still be able to accept OTA updates?
If not, will it accept OTA updates after relocking the bootloader?
Thanks.
Godswrath said:
Will an unlocked bootloader still be able to accept OTA updates?
Click to expand...
Click to collapse
Yes.
Unlocking your tablet doesn't really make changes to your system. It sets a flag that allows you to modify partitions which were previous read-only and also allows you to boot unsigned kernels/recoveries.
Whether you can accept OTAs or not depends on whether you have modified or removed any OS files. Adding files (like you would to add root) will not affect your ability to get OTAs. However with root capabilities, you will sometimes be tempted to modify or remove OS files. That could prevent you from a successful OTA update.
sfhub said:
Whether you can accept OTAs or not depends on whether you have modified or removed any OS files. Adding files (like you would to add root) will not affect your ability to get OTAs. However with root capabilities, you will sometimes be tempted to modify or remove OS files. That could prevent you from a successful OTA update.
Click to expand...
Click to collapse
So I mentioned above that root wouldn't affect your ability to get OTAs.
I actually went through the process of flashing JWR66N, rooting, then applying the JSS15J OTA.
What I found is that SuperSU actually does cause the OTA to fail somewhere near the end when it is setting permissions. All the files are patched successfully but there is a failure when the OTA tries to unpack the new recovery. This is due to SuperSU install marking a file immutable to support its "survive" OTA feature. If you undo this attribute change on the one file, the OTA works fine.
If you do not undo the change, effectively you'll have all the files for the JSS15J ROM, except your build fingerprint will still say JWR66N.
sfhub said:
So I mentioned above that root wouldn't affect your ability to get OTAs.
I actually went through the process of flashing JWR66N, rooting, then applying the JSS15J OTA.
What I found is that SuperSU actually does cause the OTA to fail somewhere near the end when it is setting permissions. All the files are patched successfully but there is a failure when the OTA tries to unpack the new recovery. This is due to SuperSU install marking a file immutable to support its "survive" OTA feature. If you undo this attribute change on the one file, the OTA works fine.
If you do not undo the change, effectively you'll have all the files for the JSS15J ROM, except your build fingerprint will still say JWR66N.
Click to expand...
Click to collapse
Great, thank you so much for the info sfhub! May I ask how you undo the attribute change on the file? I'll really want root, but for the moment I don't want to stick with OTAs, I spend enough time messing around with ROMs on my phone, (EG4T).
Why not just learn android some more? It's a nexus device. It's meant to be easily unlocked / rooted / returned to stock / relocked. If anything, there are tons of resources in this forum to help you return your device to stock if you mess things up so you can return the tablet or get warranty done.
Godswrath said:
Great, thank you so much for the info sfhub! May I ask how you undo the attribute change on the file? I'll really want root, but for the moment I don't want to stick with OTAs, I spend enough time messing around with ROMs on my phone, (EG4T).
Click to expand...
Click to collapse
you just do
chattr -i /system/etc/install-recovery.sh
I attached an UPDATE-SuperSU-ota.zip install file you can run from TWRP to do it for you. You just run it after UPDATE-SuperSU-v1.51.zip and it will set you up to receive OTAs successfully (you'll need to re-install the two files after the OTA to put root back on)
So basically you do this
adb reboot bootloader
fastboot boot twrp.img
within TWRP
install UPDATE-SuperSU-v1.51.zip
install UPDATE-SuperSU-ota.zip
You can even "chain" install them, just select UPDATE-SuperSU-v1.51.zip first.
Aria807 said:
Why not just learn android some more? It's a nexus device. It's meant to be easily unlocked / rooted / returned to stock / relocked. If anything, there are tons of resources in this forum to help you return your device to stock if you mess things up so you can return the tablet or get warranty done.
Click to expand...
Click to collapse
IMO you can actually learn a lot trying to understand out why things fail
Hello everyone.
My good old Note7 N-930F threw a fit recently and rebooted to an FRP lock screen. :crying:
After a bit of panick I managed to restore it to original 6.0.1 firmware with original recovery, etc. Basically everything is stock with the exception of Knox (obviously).
I know how to root it (done it before) and only need it so that I can enable the SHealth (with buildProp edit). But then I'd like to un-root the phone since some of the apps won't work on a rooted device (GooglePay, some banking apps, etc.)
What do I need to do to remove root after editing the buildProp? Can the TWRP stay (and work) after the unroot?
Will the phone boot again or will I have to repeat the full wipe/recovery procedure?
Thanks in advance
I have an S20 Ultra G9880 (Hong Kong model) and I want to install Cerberus, along with other applications, as system applications that will not be deleted when a factory reset occurs. Unfortunately, it appears that only systemless root methods are available for this phone, and that Android 10 disallows writing to the system folder even when rooted in any case. I saw a thread in which someone running a custom ROM was able to write to this folder, so it seems like this is a decent way of bypassing Android's restrictions.
Could someone help me find information on installing a custom ROM on this device in order to be able to install system apps that will survive resets? I have already unlocked the bootloader and rooted with Magisk.
Also, what might break with this, besides the things that break with Magisk root?
Following your thread mate though i have no answer to you.