Related
I apologize if there is already a thread like this, but the search wasnt working.. I know what i can do with my phone once it is rooted, I am just interested in what happens tot he actual phone. I could be wrong, but once i root it isnt it always possible to tell that i rooted it even if i unroot it so therefor all warantees are voided? sorry if im being unclear, i cant think of another way to explain it haha.
The K-Zoo Kid said:
I apologize if there is already a thread like this, but the search wasnt working.. I know what i can do with my phone once it is rooted, I am just interested in what happens tot he actual phone. I could be wrong, but once i root it isnt it always possible to tell that i rooted it even if i unroot it so therefor all warantees are voided? sorry if im being unclear, i cant think of another way to explain it haha.
Click to expand...
Click to collapse
The language on the "warranty void" screen says that unlocking the bootloader "may" void your warranty. On the Nexus One, HTC usually honored the warranty if the issue was with anything hardware related and could not have been the result of software tampering. Granted, that's them and this is Samsung.
Further, unless there is something hidden in the system files that counts the number of times you unlock the bootloader, you can always relock it prior to sending it in for repair with fastboot oem lock.
unremarked said:
The language on the "warranty void" screen says that unlocking the bootloader "may" void your warranty. On the Nexus One, HTC usually honored the warranty if the issue was with anything hardware related and could not have been the result of software tampering. Granted, that's them and this is Samsung.
Further, unless there is something hidden in the system files that counts the number of times you unlock the bootloader, you can always relock it prior to sending it in for repair with fastboot oem lock.
Click to expand...
Click to collapse
So there is a way to kind of undo the root without them knowing? THanks a lot btw. I figured it was something like this.
The K-Zoo Kid said:
So there is a way to kind of undo the root without them knowing? THanks a lot btw. I figured it was something like this.
Click to expand...
Click to collapse
unlocking the bootloader and rooting are two different things
jblade1000 said:
unlocking the bootloader and rooting are two different things
Click to expand...
Click to collapse
Ahh i have no idea what unlocking the bootloader does then.
The K-Zoo Kid said:
Ahh i have no idea what unlocking the bootloader does then.
Click to expand...
Click to collapse
In a nutshell, unlocking the bootloader means you will be allowed to flash non-Google/custom files to the system partition and more or less enables superuser access(aka root). Once thats done, then you "root" the device, push the Superuser.apk which will enable the rooted apps. Please check out the rooted section of my stickied FAQ for more detail on how to do this if you decide to. There are two great threads I link to.
Once you lock the bootloader, you lose access to the system partition and superuser I believe which effectively unroots it.
unremarked said:
In a nutshell, unlocking the bootloader means you will be allowed to flash non-Google/custom files to the system partition and more or less enables superuser access(aka root). Once thats done, then you "root" the device, push the Superuser.apk which will enable the rooted apps. Please check out the rooted section of my stickied FAQ for more detail on how to do this if you decide to. There are two great threads I link to.
Once you lock the bootloader, you lose access to the system partition and superuser I believe which effectively unroots it.
Click to expand...
Click to collapse
So basically if you want to do any sort of mods, flash roms, etc. you need to unlock the bootload and root. Thanks a lot for explaining that. I think i understand it now, but just to clarify, if i unlock the bootloader and root will i be able to get the phone back to stock without samsung knowing that i rooted/unlock the bootloader?
The K-Zoo Kid said:
So basically if you want to do any sort of mods, flash roms, etc. you need to unlock the bootload and root. Thanks a lot for explaining that. I think i understand it now, but just to clarify, if i unlock the bootloader and root will i be able to get the phone back to stock without samsung knowing that i rooted/unlock the bootloader?
Click to expand...
Click to collapse
Yes, to mod/flash roms you need to unlock the bootloader. It's possible that sometime down the road someone may develop a method of gaining root access on the phone without touching it, but it's unlikely given the fact that we can both unlock and lock the bootloader very easily.
Right now, the answer is... more or less. If you make a NAND backup in Clockwork Recovery/Rom manager of your stock ROM, you can restore back to that, fastboot flash the closest thing we have currently to the stock recovery(check development section for this), then relock the bootloader. This will give the phone all appearances of being stock. Unless Samsung has something deep in the system files tracking the number of times you've unlocked/locked(which I doubt, since I'm sure such a system would have been found by now), you should be good to go.
Most people who have returned the phone to Best Buy have noted that they don't even power on the device or check to see if the bootloader is unlocked or if there's a custom recovery on there. But your mileage may vary.
Interesting stuff. I was under the impression that once clockworkmod is flashed there is no way to remove it at this time.
Reading this thread I'm guessing and hoping this is not the case?
I had clockworkmod installed but used rom manager to flash the 2.3.1 update and i've now got the stock bootloader back. I guess the ota update does the same? It would seem that getting back to stock is pretty easy.
Sent from my Nexus S using XDA App
xspyda said:
Interesting stuff. I was under the impression that once clockworkmod is flashed there is no way to remove it at this time.
Reading this thread I'm guessing and hoping this is not the case?
Click to expand...
Click to collapse
My apologies, I posted that before I came to the same understanding regarding the stock recovery.
Like the poster above me mentioned there is a NAND backup of stock 2.3.1 you could restore to which has the stock recovery.
Sent from my Nexus S using XDA App
Thanks for the clarification. I'll do some more reading in the dev section
Thanks a lot, this really helped me out a lot. I will proceed to rooting
So, just want to make sure I have this straight... You unlock the bootloader, load custom recovery, SU, and now phone is rooted. If you lock the bootloader, you lose root?
For me, I'm not big on custom roms since I just don't have time to keep things up to date or participate in the bug process, but I do like to maintain backups with Titanium (my primary reason for rooting). So by locking the bootloader down I will not be able to use Titanium. Furthermore, unlocking the bootloader wipes the device. So is there a reason one would not want to keep the bootloader unlocked? Have I completely misunderstood the system?
Hi All,
I think I am screwed here, but here goes...I have CM7 nightly 161 on my phone, but the USB port is broken, so can't use adb. Got the warranty replacement and now I need to put my broken phone back to stock.
I tried to load the stock rom from Football's thread, and it took my s-off to s-on, but said "Main version is older"
any ideas on what I can do to revert back? or am I screwed? been trying for hours, and I am just
Since you have root privileges in CM7, you can execute the downgrading guide without the need for temp-root through ADB.
Read the Wiki, "Root" section, "Downgrade MT4G to 2.2.1" guide, execute it all from inside Terminal Emulator on the phone. Don't run fre3vo, you don't need it. Just overwrite the MISC partition as directed, and then you'll be able to flash PD15IMG.ZIP. Link to Wiki in my signature.
thanks for the quick reply, but it says permission denied for both the "root" section and the fre3vo section
Please read my post again. Didn't I write clearly - skip the rooting / fre3vo part?
Execute ONLY the downgrade part.
Specifically, execute the following part:
Changing Version Number to Allow Downgrade
Get an SD Card adapter and use Footballs Gingerbread RUU in the development section. It will give you the gingerbread update, you will lose root, and you will have s=on. Easiest fool proof way.
scrapin240 said:
thanks for the quick reply, but it says permission denied for both the "root" section and the fre3vo section
Click to expand...
Click to collapse
Here the method i did to downgrade my phone http://forum.xda-developers.com/showthread.php?t=1178912 I know it works. went to that wiki and the link posted there is the same as the one i posted.
Thanks for the help! my issue was that I was trying to make the version file executable from the sdcard not realizing that it needs to be local.
once i did that, smooth sailing. THANKS!!
Congrats Glad it worked.
lowandbehold said:
Get an SD Card adapter and use Footballs Gingerbread RUU in the development section. It will give you the gingerbread update, you will lose root, and you will have s=on. Easiest fool proof way.
Click to expand...
Click to collapse
He couldn't use RUU. He wrote - "Main version is older" showed up when he attempted. That's why me and Wolf pointed him to downgrading guide.
I don't need help with this, my phone is S-OFF, SuperCID and the lot, however, I'd still like to know why we can't install OTA's manually, from the stock recovery while S-ON.
Over at a Swedish forum, a lot of people have reported that installing the latest OTA manually does not work, period. They enter the stock recovery, press and hold power and volume up, and choose to install the OTA. However, the phone reboots. CID is matching, so no issue there.
Why do you need to be S-OFF when installing an OTA manually, with the stock recovery?
Theshawty said:
I don't need help with this, my phone is S-OFF, SuperCID and the lot, however, I'd still like to know why we can't install OTA's manually, from the stock recovery while S-ON.
Over at a Swedish forum, a lot of people have reported that installing the latest OTA manually does not work, period. They enter the stock recovery, press and hold power and volume up, and choose to install the OTA. However, the phone reboots. CID is matching, so no issue there.
Why do you need to be S-OFF when installing an OTA manually, with the stock recovery?
Click to expand...
Click to collapse
Interested, subscribed. @Sneakyghost any ideas?
Sent from my iPod touch using Tapatalk
Could be security needs to actually be on to flash the OTA. Seen that before.
signatures are for girls
Sneakyghost said:
Could be security needs to actually be on to flash the OTA. Seen that before.
signatures are for girls
Click to expand...
Click to collapse
But as @Theshawty said, and I have seen once, when my phone was new, one can't flash an OTA manually on a completely stock phone which is s-on. So, security needs to be off. For HTC signed stuff. Now, the question is why..
n1234d said:
But as @Theshawty said, and I have seen once, when my phone was new, one can't flash an OTA manually on a completely stock phone which is s-on. So, security needs to be off. For HTC signed stuff. Now, the question is why..
Click to expand...
Click to collapse
Exactly. My little brother even tested on his completely unmodified phone.
Sent from my HTC One using Tapatalk
Theshawty said:
I don't need help with this, my phone is S-OFF, SuperCID and the lot, however, I'd still like to know why we can't install OTA's manually, from the stock recovery while S-ON.
Over at a Swedish forum, a lot of people have reported that installing the latest OTA manually does not work, period. They enter the stock recovery, press and hold power and volume up, and choose to install the OTA. However, the phone reboots. CID is matching, so no issue there.
Why do you need to be S-OFF when installing an OTA manually, with the stock recovery?
Click to expand...
Click to collapse
I faced this annoying problem and tried every thing but finally i found that this is due to ( preload ) folder and its content was deleted from data
So u can put them back and apply right permissions and it will work without any problem
If u don't have backup of preload folder, tell me and i will upload it to you when go home
Sent from my HTC One using Tapatalk
mido.fayad said:
I faced this annoying problem and tried every thing but finally i found that this is due to ( preload ) folder and its content was deleted from data
So u can put them back and apply right permissions and it will work without any problem
If u don't have backup of preload folder, tell me and i will upload it to you when go home
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Preload folder? What do you mean exactly?
I don't need it as I don't run stock and worry about OTA's. I'm a custom ROM kind of guy. I want to know for everyone else. Like I said, my little brother tried this with his phone and he hasn't rooted or unlocked or anything, yet he can't apply the OTA. It either says "wrong CID" or just reboots. His CID is correct, though.
Hmm, are there any HTC experts who could answer this?
@beaups @jcase @EddyOS
Theshawty said:
Preload folder? What do you mean exactly?
I don't need it as I don't run stock and worry about OTA's. I'm a custom ROM kind of guy. I want to know for everyone else. Like I said, my little brother tried this with his phone and he hasn't rooted or unlocked or anything, yet he can't apply the OTA. It either says "wrong CID" or just reboots. His CID is correct, though.
Click to expand...
Click to collapse
/data/preload gets deleted when you unlock using HTCdev, the 1.xx can be found here: http://forum.xda-developers.com/showthread.php?t=2200628
this used to interfere with 1.xx and 2.xx OTA updates, but shouldn't be a problem in 3.xx+ OTAs as they are no longer checked.
But still, I don't understand why the OTA can't be applied.... i'm not sure, but i do think people were able to manually install OTAs even with S-On (I could very well be wrong), but the fact that it says "wrong CID" would lead me to believe it's the wrong OTA file.
do you have his "fastboot getvar all" and which OTA he's trying to apply?
nkk71 said:
/data/preload gets deleted when you unlock using HTCdev, the 1.xx can be found here: http://forum.xda-developers.com/showthread.php?t=2200628
this used to interfere with 1.xx and 2.xx OTA updates, but shouldn't be a problem in 3.xx+ OTAs as they are no longer checked.
But still, I don't understand why the OTA can't be applied.... i'm not sure, but i do think people were able to manually install OTAs even with S-On (I could very well be wrong), but the fact that it says "wrong CID" would lead me to believe it's the wrong OTA file.
do you have his "fastboot getvar all" and which OTA he's trying to apply?
Click to expand...
Click to collapse
Believe me when I say this, mate, it IS the right OTA. I opened the OTA myself using winRAR and confirmed that the CID HTC__Y13 is supported (the android-info.txt in the OTA contains all SuperCID's (11111111, 22222222 etc) and all standard EU CID's and the Nordic HTC__Y13 CID).
The OTA is right, it's for the correct base. Everyone who tried to apply it over at Swedroid who were S-ON got the "check CID failed" and they all had unmodified phones (i.e. never been unlocked using HTCdev, never S-OFF'd, etc). Only the ones who had S-OFF could apply it without issues.
Theshawty said:
Believe me when I say this, mate, it IS the right OTA. I opened the OTA myself using winRAR and confirmed that the CID HTC__Y13 is supported (the android-info.txt in the OTA contains all SuperCID's (11111111, 22222222 etc) and all standard EU CID's and the Nordic HTC__Y13 CID).
The OTA is right, it's for the correct base. Everyone who tried to apply it over at Swedroid who were S-ON got the "check CID failed" and they all had unmodified phones (i.e. never been unlocked using HTCdev, never S-OFF'd, etc). Only the ones who had S-OFF could apply it without issues.
Click to expand...
Click to collapse
I do believe you
But strange indeed
nkk71 said:
I do believe you
But strange indeed
Click to expand...
Click to collapse
Yes, strange indeed. It's doesn't make any sense at all.
Theshawty said:
Yes, strange indeed. It's doesn't make any sense at all.
Click to expand...
Click to collapse
mixed results here too: http://android-revolution-hd.blogspot.com/2013/12/how-to-manually-install-ota-update.html
I'm gonna look back a bit, cause I remember people manually installing OTAs but can't remember if they were all S-Off. If I find something I'll let you know
cheers
---------- Post added at 05:27 PM ---------- Previous post was at 04:35 PM ----------
Well makes no sense whatsoever , but you are correct S-Off seems necessary to manually apply, here are a couple of threads:
http://forum.xda-developers.com/showthread.php?t=2500424
http://forum.xda-developers.com/showthread.php?t=2637699
summary: S-Off works fine, S-On -> CID mismatch and reboot
hmm, wondering what getprop("ro.cid") returns when in stock recovery, and selecting "apply ..."
maybe try an updater-script which outputs
getprop("ro.bootloader")
getprop("ro.cid")
getprop("ro.product.device")
getprop("ro.build.product")
Basically, I'm thinking that during a normal OTA update, the system reboots with a "proper" default.prop, whereas when you manually apply that info is not there (or incorrect/incomplete somehow), and the default.prop checks don't pass... just a thought
nkk71 said:
mixed results here too: http://android-revolution-hd.blogspot.com/2013/12/how-to-manually-install-ota-update.html
I'm gonna look back a bit, cause I remember people manually installing OTAs but can't remember if they were all S-Off. If I find something I'll let you know
cheers
---------- Post added at 05:27 PM ---------- Previous post was at 04:35 PM ----------
Well makes no sense whatsoever , but you are correct S-Off seems necessary to manually apply, here are a couple of threads:
http://forum.xda-developers.com/showthread.php?t=2500424
http://forum.xda-developers.com/showthread.php?t=2637699
summary: S-Off works fine, S-On -> CID mismatch and reboot
hmm, wondering what getprop("ro.cid") returns when in stock recovery, and selecting "apply ..."
maybe try an updater-script which outputs
getprop("ro.bootloader")
getprop("ro.cid")
getprop("ro.product.device")
getprop("ro.build.product")
Basically, I'm thinking that during a normal OTA update, the system reboots with a "proper" default.prop, whereas when you manually apply that info is not there (or incorrect/incomplete somehow), and the default.prop checks don't pass... just a thought
Click to expand...
Click to collapse
My first thought as to why the OTA might fail when S-ON is because there is a write protection on the system when security is on, but that shouldn't matter when you're in the recovery, right?
Theshawty said:
My first thought as to why the OTA might fail when S-ON is because there is a write protection on the system when security is on, but that shouldn't matter when you're in the recovery, right?
Click to expand...
Click to collapse
yeah i don't think that matters in recovery, and the OTA isn't even getting to that part (writing system)... you've obviously already taken a look at the updater-script and the CID check is like the 2nd or 3rd thing it checks, so the "/system/build.prop" fingerprint checks out, but CID fails.
i think ro.cid is just returning "" (nothing ), and due to S-On fails
i guess you could edit the OTA to include cid == "" and it could work... lemme check something....
nkk71 said:
yeah i don't think that matters in recovery, and the OTA isn't even getting to that part (writing system)... you've obviously already taken a look at the updater-script and the CID check is like the 2nd or 3rd thing it checks, so the "/system/build.prop" fingerprint checks out, but CID fails.
i think ro.cid is just returning "" (nothing ), and due to S-On fails
i guess you could edit the OTA to include cid == "" and it could work... lemme check something....
Click to expand...
Click to collapse
but if you edit the zip, you break the integrity of the zip, right?
Theshawty said:
but if you edit the zip, you break the integrity of the zip, right?
Click to expand...
Click to collapse
as far as i can tell, only the firmware.zip inside the OTA is encrypted and HTC signed; the OTA.zip itself, doesn't look encrypted (but possibly apk signed).
i can't test this code on the M7 at the moment (due to phone calls), but I did test it on the HTC Sensation (in custom recovery) and worked fine.
Code:
# output OTA check info
ui_print("Mounting /system");
mount("ext4", "EMMC", "system", "/system");
ui_print("ro.build.fingerprint=" + file_getprop("/system/build.prop", "ro.build.fingerprint") + "\n");
ui_print("ro.bootloader=" + getprop("ro.bootloader") + "\n");
ui_print("ro.cid=" + getprop("ro.cid") + "\n");
ui_print("ro.product.device=" + getprop("ro.product.device") + "\n");
ui_print("ro.build.product=" + getprop("ro.build.product") + "\n");
ui_print("-----------------------");
ui_print("bootloader check: " + is_ship_bootloader(getprop("ro.bootloader")) + "\n");
ui_print("cid check: " + check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" , "HTC__001" , "HTC__E11" ,
"HTC__102" , "HTC__203" , "HTC__405" , "HTC__Y13" , "HTC__304" ,
"HTC__032" , "HTC__A07" , "HTC__J15" , "HTC__016") + "\n");
ui_print("mid1 check: " + check_mid("full", "PN0710000") + "\n");
ui_print("mid2 check: " + check_mid("simple", "PN0710000") + "\n");
ui_print("device check: " + getprop("ro.product.device") + "\n");
ui_print("product check: " + getprop("ro.build.product") + "\n");
ui_print("Unmounting /system");
unmount("/system");
it should be run on a stock recovery to see what kind of output you get... if i get a chance later, i'll flash back a stock recovery and run it.
then it would have to be run on an S-On device, ...... if it doesn't allow it to run, then we'd need to apk sign it (or whatever the appropriate term is ), and see which check fails. that would at least narrow it down
well that did NOT go as expected
not only was i not able to to run that file using stock recovery (yeah, can't be that simple)... i also managed to wipe everything off my phone (before even attempting to apply that file.... i really don't get it, why does installing stock recovery sometimes wipe the phone completely???)
nkk71 said:
well that did NOT go as expected
not only was i not able to to run that file using stock recovery (yeah, can't be that simple)... i also managed to wipe everything off my phone (before even attempting to apply that file.... i really don't get it, why does installing stock recovery sometimes wipe the phone completely???)
Click to expand...
Click to collapse
Hmmm, really weird! What is up with this? Haha.
Theshawty said:
Hmmm, really weird! What is up with this? Haha.
Click to expand...
Click to collapse
not funny :silly:
once it happened to me... (hence i had a nandroid backup made just before and pulled it off the phone, cause the internal storage got wiped too)... and another time i flashed enough stock recoveries and messed with them, and nothing got erased. go figure
oh well, a couple of wasted hours, but i've never had so much free space on my internal storage
I'm new to xda and obviously I'm not a dev. I just want to root my Axon 7 so I can download root apps. I'm not tech savvy at all and I've created this thread because I have no idea what to do with this page : http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 . Can anyone give a step by step tutorial on how to root my phone?
I feel so so out of place here... please don't scold me :x
inb4 banned cuz didn't read the rules or stickies
I'm running B29.
What version are you running? B20/B27/B29
If you are not tech savvy, do not attempt the root method. It's for advance user and too many people have bricked their phone already. Just read the threads and you will know what I mean.
S8ntsHaz3 said:
What version are you running? B20/B27/B29
Click to expand...
Click to collapse
I'm running B29.
And yes I can probably guess the amount of people who bricked their phones. But what if everything were to be laid out simple and I follow the directions in every respect? I'm not going to start rooting until I know what I'm doing. So don't worry. I'm stupid but I'm not THAT stupid.
No your fine lmao I started with this phone so we're pretty much same level. As to my understanding it is possible but I would wait just a bit for the b29 stuff to come out.
Don't worry, you're not the only one. I've been reading these tutorials and it's all gibberish, lol.... Every phone I have has been rooted within the first day, this phone I've had over 2 months, and I still can't get it. So you're not alone, lol...
There definitely needs to be some cleaning done on this forum, with far too many threads covering the same topics and many OPs being out of date.
Best rooting guide I found was buried in a thread, but is now also out of date if you're running B29.
http://forum.xda-developers.com/showpost.php?p=68302434&postcount=157
It might help if you're still on B27. I used it, had root and bootloader still locked, updated to B29 for the security patch, and was able to keep TWRP but lost root. Having TWRP still allows me to flash all the Google pixel stuff though, which is nice
Bolandk said:
There definitely needs to be some cleaning done on this forum, with far too many threads covering the same topics and many OPs being out of date.
Best rooting guide I found was buried in a thread, but is now also out of date if you're running B29.
http://forum.xda-developers.com/showpost.php?p=68302434&postcount=157
It might help if you're still on B27. I used it, had root and bootloader still locked, updated to B29 for the security patch, and was able to keep TWRP but lost root. Having TWRP still allows me to flash all the Google pixel stuff though, which is nice
Click to expand...
Click to collapse
I'm looking closely at this phone now myself...
I've seen the bootloader thread: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
I'm only interest in this if I can successfully unlock the bootloader and stock root is possible...from what I've read, BOTH can be done. According to the root thread, the model I need (A2017G) is listed as unlockable, correct? What's the difference between a2017g B02 and B03??
RoOSTA
totalFX said:
I'm new to xda and obviously I'm not a dev. I just want to root my Axon 7 so I can download root apps. I'm not tech savvy at all and I've created this thread because I have no idea what to do with this page : http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 . Can anyone give a step by step tutorial on how to root my phone?
I feel so so out of place here... please don't scold me :x
inb4 banned cuz didn't read the rules or stickies
I'm running B29.
Click to expand...
Click to collapse
OK I have read far too many of these questions here about root on B29 - so here goes.
1. Go to the ZTE website, download the stock B20, and install it.
2. http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204 use this to get TWRP installed on your phone - don't worry about root.
3. http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 UNLOCK the bootloader
4. http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2 flash boot file, system file, and SuperSU 2.65
Now please relax - anyone here with any dev skills whatsoever are neck deep in other projects (like CM13). B29 hasn't been out long and the only stock image we have from ZTE is B20, which doesn't give us a ton to work with
I also very new to android smartphone and I also feel so so out of place too.
I wish someone make a video how to root this axon 7 phone.
search around youtube jailbrake iPhone is so easy root samsung phone is so easy.... but root axon 7 nothing
I love axon 7 so much now but if I know it's so hard to root i'm just gonna buy samsung phone .
so F..... tired of this youtube ads
ads block is the only reason why I want to root
and that is the only reason why I jailbrake all my ideviese
For me, also with B29, the best and easy way was this from rczrider (thanx a lot). http://forum.xda-developers.com/showpost.php?p=69507226&postcount=766
But one issue after root: I have no access to system, i noticed that, as i install Gsam Battery Monitor root companion, that will install in priv-app but i was write protect. Also RootExplorer was not possible to copy/delete files in system, because write protect. How to change that?
tasar said:
For me, also with B29, the best and easy way was this from rczrider (thanx a lot). http://forum.xda-developers.com/showpost.php?p=69507226&postcount=766
But one issue after root: I have no access to system, i noticed that, as i install Gsam Battery Monitor root companion, that will install in priv-app but i was write protect. Also RootExplorer was not possible to copy/delete files in system, because write protect. How to change that?
Click to expand...
Click to collapse
I forgot to add a final step to that list. I've updated it and here's the new one:
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Flash TWRP (recovery) using the method in the OP (B27 file is fine). You don't need to flash the boot image.
Unlock the bootloader (B27 is fine): http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Boot phone, set it up, whatever
*Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, a fully functioning TWRP (no data encryption issue), and rooted B29. You will not be able to receive OTAs.
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
---------- Post added at 08:45 ---------- Previous post was at 08:02 ----------
In case anyone stumbles across this thread, here's a "Newbie's Guide to Unlocking and Rooting the Axon 7": http://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234
It will be updated as necessary and contains a step-by-step process with links to the appropriate threads.
So are they still releasing a new bootloader unlock tool? Or should I just go ahead and do these steps?
Sent from my ZTE A2017U using Tapatalk
polar2792 said:
So are they still releasing a new bootloader unlock tool? Or should I just go ahead and do these steps?
Click to expand...
Click to collapse
Yes, ZTE still supports bootloader unlocking on the Axon 7. It is currently on hold, but yes, our understanding is that they will be releasing a new process (likely with Nougat).
I can't think of any reason not to unlock now because you can always re-lock if you want to. Who knows what the new process will entail.
rczrider said:
[*] *Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
Click to expand...
Click to collapse
Thanks, reboot disemmcwp fixed my write access to /system
rczrider said:
Yes, ZTE still supports bootloader unlocking on the Axon 7. It is currently on hold, but yes, our understanding is that they will be releasing a new process (likely with Nougat).
I can't think of any reason not to unlock now because you can always re-lock if you want to. Who knows what the new process will entail.
Click to expand...
Click to collapse
Yea well I was hoping the new tool wouldn't kill the warranty but that's wishful thinking, and after some thought I highly doubt that will happen. So time to unlock the bootloader,l and flash TWRP.....soon as I get off work in 9 hours.
Sent from my ZTE A2017U using Tapatalk
polar2792 said:
Yea well I was hoping the new tool wouldn't kill the warranty but that's wishful thinking, and after some thought I highly doubt that will happen. So time to unlock the bootloader,l and flash TWRP.....soon as I get off work in 9 hours.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I think ZTE will eventually put out a bootloader unlock without killing the warranty. But, yeah, either way it's easy enough to do it on your own now.
rczrider said:
I forgot to add a final step to that list. I've updated it and here's the new one:
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Flash TWRP (recovery) using the method in the OP (B27 file is fine). You don't need to flash the boot image.
Unlock the bootloader (B27 is fine): http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Boot phone, set it up, whatever
*Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, a fully functioning TWRP (no data encryption issue), and rooted B29. You will not be able to receive OTAs.
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
---------- Post added at 08:45 ---------- Previous post was at 08:02 ----------
In case anyone stumbles across this thread, here's a "Newbie's Guide to Unlocking and Rooting the Axon 7": http://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234
It will be updated as necessary and contains a step-by-step process with links to the appropriate threads.
Click to expand...
Click to collapse
Thank you; thank you, THANK YOU!!!!! I tried for an hour or two, using both ADB and Terminal Emulator to apply this "reboot disemmcwp" fix, and I just couldn't get it to work (I'm on B29). Then, I saw your instructions to use TWRP and followed them, and it worked first time, like a charm!
Thanks again - I'm a very happy camper. You da' man, LOL!
Dennis
It is valid for Oneplus 5 also
https://forum.xda-developers.com/oneplus-5t/help/remove-unlocked-bootloader-warning-t3841712
Post #12
You argued in the topic that you are mentioning, why do you make a new topic?
Remove unlocked bootloader message, by locking the bootloader
yusuo said:
Remove unlocked bootloader message, by locking the bootloader
Click to expand...
Click to collapse
Go lock your bootloader with a custom ROM installed, I beg you. And please don't forget to let me know how that turns out for you and your device.
This was posted in 6T too and pissed off a lot there as well.
Mods CLOSE THIS THREAD!
[GUIDE] Remove unlocked bootloader warning
^- We are talking about this annoying warning Someone asked for that on this forum, someone told this is impossible - so I did that. It replaces aboot with the one that doesn't display this annoying warning, enjoy :) Download flashable zip...
forum.xda-developers.com
could this work for op6
-- accidental post, wrong forum --