Does anyone know if it is at all possible to inject root into the updates that are available from Asus's website? Like to download the full update from Asus website, extract the system image and put the SU binary in there and repack then run the update on the tablet? I know the SU binary for ICS works with the latest OTA update so logically i would think it to be possible... especially since there are root injected stock roms available for various phones that i own (ie. SGS III).
I just would think it would be easier to inject root into the stock downloaded updates and install them instead of having to always go back to ICS and re-root and stuff if the latest OTA fails like mine did, causing me to manually update which also wiped out my SU backup that Rootkeeper made...
If it is possible to make root injected updates, any tips on how to go about doing it and where the SU binary and other files need to be located in the image?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
hansonmi said:
Does anyone know if it is at all possible to inject root into the updates that are available from Asus's website?
Click to expand...
Click to collapse
It is possible, but you can't sign the modified package with the correct key, so you could only apply them to unlocked devices.
_that said:
It is possible, but you can't sign the modified package with the correct key, so you could only apply them to unlocked devices.
Click to expand...
Click to collapse
Yup, that whole signing thing is a ***** Great that it validates the Firmware you are installing... sucks for modders
_that said:
It is possible, but you can't sign the modified package with the correct key, so you could only apply them to unlocked devices.
Click to expand...
Click to collapse
Can you kindly elaborate ? Are you referring to Unlocked Bootloaders or Network Unlocked phones ? Either way, won't APK Multi Tool be able to Sign the file ?
What I have is a device with Locked Bootloader and no Network lock (to my knowledge). I have its Stock update.zip that I'd like to inject Root into.
Perseus71 said:
Can you kindly elaborate ? Are you referring to Unlocked Bootloaders or Network Unlocked phones ? Either way, won't APK Multi Tool be able to Sign the file ?
What I have is a device with Locked Bootloader and no Network lock (to my knowledge). I have its Stock update.zip that I'd like to inject Root into.
Click to expand...
Click to collapse
You need an unlocked bootloader. The locked bootloader checks for the Asus digital signature - so any signing tool would help you only if you somehow obtain Asus' private key.
_that said:
You need an unlocked bootloader. The locked bootloader checks for the Asus digital signature - so any signing tool would help you only if you somehow obtain Asus' private key.
Click to expand...
Click to collapse
Ah! I see. In my Case I don't have ASUS Transformer. Rather I have Smartstick. I believe Its bootloader does not do this Check. So I should be ok inserting su binary into /system/bin with correct compression.
Question though, other than Inserting SU Binary and SuperSU in /System/app, is there anything else I need to be doing in order to Root my Stock Rom ?
Perseus71 said:
Ah! I see. In my Case I don't have ASUS Transformer.
Click to expand...
Click to collapse
This is the TF700 forum.
Perseus71 said:
So I should be ok inserting su binary into /system/bin with correct compression.
Question though, other than Inserting SU Binary and SuperSU in /System/app, is there anything else I need to be doing in order to Root my Stock Rom ?
Click to expand...
Click to collapse
If your device supports flashing of unsigned ROM images, then that's it - you only need the su binary with the correct permissions (with the SUID bit set) and SuperSU - in whatever format your device accepts ROM images. But that's off topic here.
_that said:
This is the TF700 forum.
Click to expand...
Click to collapse
Yes I know. My device is Orphan! There's no forum for it....
_that said:
If your device supports flashing of unsigned ROM images, then that's it - you only need the su binary with the correct permissions (with the SUID bit set) and SuperSU - in whatever format your device accepts ROM images. But that's off topic here.
Click to expand...
Click to collapse
What is
"SUID Bit Set"
Please ?
Perseus71 said:
Yes I know. My device is Orphan! There's no forum for it....
Click to expand...
Click to collapse
http://forum.xda-developers.com/forumdisplay.php?f=2070
Perseus71 said:
What is
"SUID Bit Set"
Please ?
Click to expand...
Click to collapse
http://lmgtfy.com/?q=suid+bit
_that said:
http://forum.xda-developers.com/forumdisplay.php?f=2070
Click to expand...
Click to collapse
Thanks for pointing that out. Although I knew about it, IMHO its a Zoo of Noob Central.
I am trying to Build a ROM on my own for a device launched in November Last Year. So my question on that forum will most likely not get Developer's attention.
_that said:
http://lmgtfy.com/?q=suid+bit
Click to expand...
Click to collapse
Yeah I guess I deserved that. My apologies.
Related
After my thread for the TF101, here are my first repackaged OTA updates for the TF700:
First of all let me make this clear:
If you have root and want to keep it, use OTA Rootkeeper.
The original recovery is removed from the blob, so you won't lose your current recovery.
If after flashing one of these zips you still have the OTA update notification, do this:
Go to Settings -> Apps -> All and clear data from DMClient.
Current OTA 9.4.5.26:
US version:
us-9.4.5.22-to-9.4.5.26-TF700-CWM-v1.0.zip MD5: 2C6C763D0A7618E4AB4CB530D714F833
WW version:
ww-9.4.5.22-to-9.4.5.26-TF700-CWM-v1.0.zip MD5: E9597AD7C18483445A1F006D91A44C1B
IMPORTANT! If you deleted/changed some files, these updates will NOT work. These updates are meant for people on a stock rooted rom.
Sweet I know a few people were looking for a flashable OTA update.
...for CWM that hasn't been ported yet
tweeklulz said:
...for CWM that hasn't been ported yet
Click to expand...
Click to collapse
AFAIK cwm zips are compatible with TWRP.
It's a generic name which is supported by most recoveries.
(TWRP or CWM) As far as we are able to unlock our TF700... That not my case...
But it's a good news for those who can
Lizard, a better title would be "[ROM][FLASHABLE]" or something. People tend to get very confused when you say "CWM" because they think no other recovery can flash it .
eyeballer said:
Lizard, a better title would be "[ROM][FLASHABLE]" or something. People tend to get very confused when you say "CWM" because they think no other recovery can flash it .
Click to expand...
Click to collapse
I've changed the title to flashable, since I don't consider the update zips to be roms. I hope this will take away some of the confusion.
Lizard said:
I've changed the title to flashable, since I don't consider the update zips to be roms. I hope this will take away some of the confusion.
Click to expand...
Click to collapse
Thanks! Will reduce our support requests for TWRP
Bad Link To zip File
Oops! This page appears broken. DNS Error - Server cannot be found.
This is the message I get when I click the link to download your OTA update, need that update, can you help. Please.
TECHNOLLIC said:
Oops! This page appears broken. DNS Error - Server cannot be found.
This is the message I get when I click the link to download your OTA update, need that update, can you help. Please.
Click to expand...
Click to collapse
Look at the date of the OP - 9.4.5.26 is very old. Why do you need this old update?
_that said:
Look at the date of the OP - 9.4.5.26 is very old. Why do you need this old update?
Click to expand...
Click to collapse
To install NvFlash. I have 9.4.5.30, NvFlash will not install with this Rom version, it has to be before that.
TECHNOLLIC said:
To install NvFlash. I have 9.4.5.30, NvFlash will not install with this Rom version, it has to be before that.
Click to expand...
Click to collapse
You cannot downgrade from 9.4.5.30 to 9.4.5.26; the 9.4.5.30 bootloader and above accepts only signed bootloaders and the older ones are not signed.
_that said:
You cannot downgrade from 9.4.5.30 to 9.4.5.26; the 9.4.5.30 bootloader and above accepts only signed bootloaders and the older ones are not signed.
Click to expand...
Click to collapse
So how will I be able to install the NvFlash Tool? I want to flash custom roms but I want to protect my tablet from getting bricked.
TECHNOLLIC said:
So how will I be able to install the NvFlash Tool? I want to flash custom roms but I want to protect my tablet from getting bricked.
Click to expand...
Click to collapse
You can no longer able to install nvflash once you already flashed above .26 version, like .30 and up. You're out of luck.
buhohitr said:
You can no longer able to install nvflash once you already flashed above .26 version, like .30 and up. You're out of luck.
Click to expand...
Click to collapse
That sucks, I didn't flash .30, it came with it already installed. I'm used to flashing my phones, so it should be no problem flashing my tablet. Thank you very much for your help.
If you've flashed roms on other phones or tablets in the past then you should be fine. Just don't do anything crazy and you shouldn't brick it. I don't have NV Flash capabilities on mine, though I had the chance to but updated my bootloader anyway. Doesn't bother me as I'm not a dev and won't be doing anything crazy on mine. I've done plenty of flashing on many phones and the Asus Prime in the past, so I'm not worried about it
Sent from my Evo LTE using XDA Premium
TECHNOLLIC said:
That sucks, I didn't flash .30, it came with it already installed. I'm used to flashing my phones, so it should be no problem flashing my tablet.
Click to expand...
Click to collapse
Just be careful to never choose "wipe data" in the bootloader menu without a working (compatible to bootloader) recovery, that is the #1 reason for hard bricks:
http://forum.xda-developers.com/showthread.php?t=1917304
_that said:
Just be careful to never choose "wipe data" in the bootloader menu without a working (compatible to bootloader) recovery, that is the #1 reason for hard bricks:
http://forum.xda-developers.com/showthread.php?t=1917304
Click to expand...
Click to collapse
Thanks again for your help and support.
I just received my TF700T for Christmas and it has JB. Can I flash this to go back and get root without unlocking?
rocketjr said:
I just received my TF700T for Christmas and it has JB. Can I flash this to go back and get root without unlocking?
Click to expand...
Click to collapse
Yes. see http://forum.xda-developers.com/showthread.php?t=1925230
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk HD
I'm running 4.1.1 on my I9020A rooted. Stock Rom and Kernel. I searched the forums and the web, and every article I find gives instructions on going back to 2.3.X, THEN removing root. I don't want to go back, in fact I only want to un-root shortly, then go back to a rooted phone.
So my question is, Can I go through the locking steps of un-rooting, but leave the current ROM (4.1.1) installed?
Christopher_M said:
I'm running 4.1.1 on my I9020A rooted. Stock Rom and Kernel. I searched the forums and the web, and every article I find gives instructions on going back to 2.3.X, THEN removing root. I don't want to go back, in fact I only want to un-root shortly, then go back to a rooted phone.
So my question is, Can I go through the locking steps of un-rooting, but leave the current ROM (4.1.1) installed?
Click to expand...
Click to collapse
Delete, IN THIS ORDER:
/system/Superuser.apk
/system/xbin/su
/system/bin/su
Reboot your phone.
Root gone. If you want to root again, go to Androidsu.com, download the appropriate zip file, flash it, and you have root again.
oldblue910 said:
Delete, IN THIS ORDER:
/system/Superuser.apk
/system/xbin/su
/system/bin/su
Reboot your phone.
Root gone. If you want to root again, go to Androidsu.com, download the appropriate zip file, flash it, and you have root again.
Click to expand...
Click to collapse
Thanks for the quick reply! Should I additionally go through the fastboot steps of locking the bootloader as well?
Christopher_M said:
Thanks for the quick reply! Should I additionally go through the fastboot steps of locking the bootloader as well?
Click to expand...
Click to collapse
No. Unlocked bootloader and root are 2 different things.
polobunny said:
No. Unlocked bootloader and root are 2 different things.
Click to expand...
Click to collapse
What he said. Unless you're returning your phone for warranty repair or you're worried about security (like me), there's no reason to lock your bootloader.
I see. Thank you guys!
I have no Superuser.apk in the System/ folder.
I can only find com.noshufou.android.su-1.apk in data/app/
The other two files you listed I have found.
Christopher_M said:
I have no Superuser.apk in the System/ folder.
I can only find com.noshufou.android.su-1.apk in data/app/
The other two files you listed I have found.
Click to expand...
Click to collapse
That's the one. Delete it, it's the app to manage the su rights. su in xbin/bin is the binary for SuperUser
Ok, so I attempted to unroot. I opened es file explorer (Which launched with SU rights) and I was able to delete com.noshufou.android.su-1.apk in data/app/.
Then when I tried to delete su in /xbin, I was denied. Tried deleting su in /bin as same results. Denied.
Any thoughts?
Just flash stock. Now unrooted. To go back flash CWM and SU. This sounds a lot easier if oldblue's suggestion isn't working for you.
Use this for step by step.
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium
jayjay3333 said:
Just flash stock. Now unrooted. To go back flash CWM and SU. This sounds a lot easier if oldblue's suggestion isn't working for you.
Use this for step by step.
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Yea, that was the conclusion I was coming too. Thanks for the help guys. :good:
You need to delete su binary via adb. Don't believe you can delete it while phone is under Android...
polobunny said:
You need to delete su binary via adb. Don't believe you can delete it while phone is under Android...
Click to expand...
Click to collapse
I'm new to android / linux. Been a Windows admin for 15+ years. I thought it not possible to delete SU while using SU, but I figured I'd try anyway. So ADB requires phone in FASTBOOT mode, correct?
Christopher_M said:
I'm new to android / linux. Been a Windows admin for 15+ years. I thought it not possible to delete SU while using SU, but I figured I'd try anyway. So ADB requires phone in FASTBOOT mode, correct?
Click to expand...
Click to collapse
No, just debugging mode.
MercilessLTD said:
No, just debugging mode.
Click to expand...
Click to collapse
In this case I think he would need to be in fastboot though.
Hi all!
I got my transformer infinity and the first of all connected to wifi and upgraded to JB.(it was a doltish action)
then realized that it was a deadend too root and development:crying::crying:
the only way I was able to move on was Unlocking bootloader and void warranty
now I have a costom bootloader: http://forum.xda-developers.com/showthread.php?t=1797692
what can I do now for rooting & nvflash, dualboot for UBUNTU(Ithing it is very suitable for the infinity because of the dock and touchpad )
now im hanged totaly
plz help me
best regards!
You cannot use NVFlash as you have upgraded the bootloader. It only works on .26 or earlier. Not on .30 or JB. You can load several of the custom Roms, just check your MD5 sums before installing them, and be wary of Alpha builds or TF300 based ones. If you don't get too crazy, you should be OK without NVFlash. Having it is like car insurance, you don't plan on using it, but when you do crash it's nice to have.
tbtaf said:
You cannot use NVFlash as you have upgraded the bootloader. It only works on .26 or earlier. Not on .30 or JB. You can load several of the custom Roms, just check your MD5 sums before installing them, and be wary of Alpha builds or TF300 based ones. If you don't get too crazy, you should be OK without NVFlash. Having it is like car insurance, you don't plan on using it, but when you do crash it's nice to have.
Click to expand...
Click to collapse
Thanks a lot!
what about root and dualboot?
No such dual boot available and doubt there will be for some time.
If you want a fast rom install clean rom.
sbdags said:
No such dual boot available and doubt there will be for some time.
If you want a fast rom install clean rom.
Click to expand...
Click to collapse
+1 CleanROM v1.3 is rooted and flies like the wind. If you are not rooted, you will need to fastboot flash the TWRP custom recovery in order to be able to flash a custom ROM. Look for TWRP (Team Win Recovery Project ) thread in Development section.
okantomi said:
+1 CleanROM v1.3 is rooted and flies like the wind. If you are not rooted, you will need to fastboot flash the TWRP custom recovery in order to be able to flash a custom ROM. Look for TWRP (Team Win Recovery Project ) thread in Development section.
Click to expand...
Click to collapse
Sorry for asking, but should i understand your answer as this:
For installing a custom rom as CleanRom i haven't got to be rooted or unlocked?
Im on JB now and i haven't rooted or unlocked my device yet.
Best regards
Mackis
Mackis said:
Sorry for asking, but should i understand your answer as this:
For installing a custom rom as CleanRom i haven't got to be rooted or unlocked?
Im on JB now and i haven't rooted or unlocked my device yet.
Best regards
Mackis
Click to expand...
Click to collapse
I believe cleanrom is prerooted rom, but you need to unlock in order to flash the rom.
Mackis said:
Sorry for asking, but should i understand your answer as this:
For installing a custom rom as CleanRom i haven't got to be rooted or unlocked?
Im on JB now and i haven't rooted or unlocked my device yet.
Best regards
Mackis
Click to expand...
Click to collapse
You need to be unlocked.
sbdags said:
You need to be unlocked.
Click to expand...
Click to collapse
ok thanks for the answer but i don't want to void my warranty.
//Mackis
Mackis said:
ok thanks for the answer but i don't want to void my warranty.
//Mackis
Click to expand...
Click to collapse
Then it is only ASUS custom ROMs for you -- there's no other way than unlocking.
tbtaf said:
You cannot use NVFlash as you have upgraded the bootloader. It only works on .26 or earlier. Not on .30 or JB. You can load several of the custom Roms, just check your MD5 sums before installing them, and be wary of Alpha builds or TF300 based ones. If you don't get too crazy, you should be OK without NVFlash. Having it is like car insurance, you don't plan on using it, but when you do crash it's nice to have.
Click to expand...
Click to collapse
I want to try new ROM's. I have searched, but can't find out how to check md5 sums. Any info would be appreciated
redheadplantguy said:
I want to try new ROM's. I have searched, but can't find out how to check md5 sums. Any info would be appreciated
Click to expand...
Click to collapse
Under Windo2s I very much like HashTab -- once installed, right-click on a file and under the Properties window, you get a new tab called "File Hashes" or something like that. If you transfer the file under Windows (e.g., using a card reader), you check it again just to be sure.
Under Android I use MD5 Hash Checker because it provides Send-to functionality: you can browse to the file using you preferred file app (mine is Total Commander) and just send it MD5HC.
Under both programs, you can just paste in the MD5 checksum the developer gives out and see if the file downloaded correctly.
Just to make sure, there's only 1 way to unlock as of now, correct? The ASUS unlocking app?
redheadplantguy said:
I want to try new ROM's. I have searched, but can't find out how to check md5 sums. Any info would be appreciated
Click to expand...
Click to collapse
I use ES FIle Explorer - it can check the MD5's itself...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
incarceration said:
Just to make sure, there's only 1 way to unlock as of now, correct? The ASUS unlocking app?
Click to expand...
Click to collapse
Right, and alternatives are unlikely to appear in the near future.
Hi guys, as I cant stand the ads I'm thinking of rooting the device but I wonder if I can have OTA updates after this and if yes, do I have to re-root the phone after the updates?
thxxx
epivitor said:
Hi guys, as I cant stand the ads I'm thinking of rooting the device but I wonder if I can have OTA updates after this and if yes, do I have to re-root the phone after the updates?
thxxx
Click to expand...
Click to collapse
If you have non gpe device then yes root will deny ota.
No my device isnt the gpe.
How can I update my phone then ?
epivitor said:
No my device isnt the gpe.
How can I update my phone then ?
Click to expand...
Click to collapse
flash stock rom
update via OTA
again root..
solved...
reversegear said:
flash stock rom
update via OTA
again root..
solved...
Click to expand...
Click to collapse
There is no other easier way to do this?
I had in mind something like download the update to the pc and apply it to the phone with usb connection. Isnt that possible. Could this method I thought brick the phone?
epivitor said:
There is no other easier way to do this?
I had in mind something like download the update to the pc and apply it to the phone with usb connection. Isnt that possible. Could this method I thought brick the phone?
Click to expand...
Click to collapse
afaik OTAs cannot be installed via PC
name itself says Over The Air
reversegear said:
afaik OTAs cannot be installed via PC
name itself says Over The Air
Click to expand...
Click to collapse
I wanted to say if I get the OTA update from another source not over the air of course, could I flash it without porblem through usb cable?
epivitor said:
I wanted to say if I get the OTA update from another source not over the air of course, could I flash it without porblem through usb cable?
Click to expand...
Click to collapse
no you cannot flash OTAs via PC
S0bes said:
If you have non gpe device then yes root will deny ota.
Click to expand...
Click to collapse
Really? My XT1032 is rooted since i bought it and I was still able to apply the February OTA. Didn't wait for it to reach my phone though - I've downloaded it here on XDA, then checked for updates.
epivitor said:
There is no other easier way to do this?
I had in mind something like download the update to the pc and apply it to the phone with usb connection. Isnt that possible. Could this method I thought brick the phone?
Click to expand...
Click to collapse
you can install CWM.
Then make a full backup. You can move it on your pc or let it take space on your phone.
After that you can apply any patches via CWM or install root or whatsoever
When your phone will show the next update you should:
1) Boot into CWM and recover your backup. BUT! You should recover only part of it. The system part.
backup and restore -> advanced restore from /sdcard -> choose your backup -> restore system
2) wait till it complete.
Now you can delete your backup.
Reboot your phone (reboot system now)
After that you will see 2 messages and if you wanna be able to apply ota you have to make the right choises
Q: ROM may flash stock recovery on boot. Fix?
A: NO
Q: Root access is missing. Root device?
A:NO
After all that steps you'll get:
1) clear system part (which means no root, modified files etc)
2) default recovery
I've read "mixed" opinions about this; some say rooted devices lose updates and some say otherwise. I've also heard that if you flash ROM A on top of ROM B that's your original ROM, and you get signature errors you no more receive OTA updates. By the way, I was able to receive OTA updates on my Asia Retail XT1033 that was flashed to Retail UK XT1032. It would be cool if some senior member here shed some light on this subject.
knizmi said:
Really? My XT1032 is rooted since i bought it and I was still able to apply the February OTA. Didn't wait for it to reach my phone though - I've downloaded it here on XDA, then checked for updates.
Click to expand...
Click to collapse
yes, it can be so. I heard about the same situation from few people. But other still can not apply ota with root
S0bes said:
yes, it can be so. I heard about the same situation from few people. But other still can not apply ota with root
Click to expand...
Click to collapse
I think that people who have reported that they can't apply the OTA update had messed their /system partition in other ways than just rooting.
I've studied the update package and all it does is that it first checks if the files (and only those files) that are going to be updated are untampered with and if everything is allright, they are patched.
To sum it up - you can have extra files on your /system folder (like the su binary), but all of the updated files must be stock. The updater really doesn't care if su, xposed or other mods are present.
knizmi said:
I think that people who have reported that they can't apply the OTA update had messed their /system partition in other ways than just rooting.
I've studied the update package and all it does is that it first checks if the files (and only those files) that are going to be updated are untampered with and if everything is allright, they are patched.
To sum it up - you can have extra files on your /system folder (like the su binary), but all of the updated files must be stock. The updater really doesn't care if su, xposed or other mods are present.
Click to expand...
Click to collapse
Is there a problem if some of the apps are disabled ? (not with titanium backup but through settings->apps->select the app ->disable)
epivitor said:
Is there a problem if some of the apps are disabled ? (not with titanium backup but through settings->apps->select the app ->disable)
Click to expand...
Click to collapse
No, disabled apps are still where they are supposed to be. The OTA updater checks if the file is there (it is), if the fingerprint matches (it does) and then it patches the app even when it's disabled.
Hi, i have a Nexus 5 (as you may have guessed) and was sent the L OTA update last night. After downloadong, i thought I'd check online to see if there was any issues with the update and the L OTA update. I only found one blog/post anywhere that answered my question and it said that it would fail, so I didn't install it.
I have just used the 'full unroot' in SuperSU, and it appears to have worked (root checker says 'Sorry, this device does not have proper root access') but I dont know if this is enough to return my device to stock in a big enough degree to allow the OTA update to work (I have no custom ROM or Recovery, just a stock image which i rooted) So I'd basically like some advice And hopefully solve my problem without much issue...
Should be OK. Root itself doesn't cause the fail. Just modified system files. Root gives new system files, not modified existing ones.
rootSU said:
Should be OK. Root itself doesn't cause the fail. Just modified system files. Root gives new system files, not modified existing ones.
Click to expand...
Click to collapse
So if i had installed a custom ROM/ recovery, would that mess with the OTA update?
If so, then that is a relief, as I thought I would have to flash a stock image and relock the bootloader
SamuelGTeague said:
So if i had installed a custom ROM/ recovery, would that mess with the OTA update?
If so, then that is a relief, as I thought I would have to flash a stock image and relock the bootloader
Click to expand...
Click to collapse
Custom ROM or Recovery cannot accept OTA. if any existing apk or file is missing or different, you also cannot accept an OTA as the OTA checks the "fingerprint" of those files. Adding new files aren't an issue as the OTA doesn't know about them so cannot check the fingerprint.
rootSU said:
Custom ROM or Recovery cannot accept OTA. if any existing apk or file is missing or different, you also cannot accept an OTA as the OTA checks the "fingerprint" of those files. Adding new files aren't an issue as the OTA doesn't know about them so cannot check the fingerprint.
Click to expand...
Click to collapse
So as I understand it, with my current set up, the OTA should run and complete. (Sorry if it sounds stupid and repetative, i just cant afford to brick my phone)
SamuelGTeague said:
So as I understand it, with my current set up, the OTA should run and complete. (Sorry if it sounds stupid and repetative, i just cant afford to brick my phone)
Click to expand...
Click to collapse
It wont brick for modified system files. It will just fail verification. if it's going to brick, it wont be for this reason.
rootSU said:
It wont brick for modified system files. It will just fail verification. if it's going to brick, it wont be for this reason.
Click to expand...
Click to collapse
Thanks for all your help, its all installed and is running perfectly!