Related
I bought a Sony Xperia Z1 (C6903) on eBay, and it came installed with Kitkat.
I decided I wanted to root the device and install a custom ROM before I used it much, so I followed a guide on XDA and flashed it with the 14.1.G.1.534 build using Flashtool. (I had to install several drivers to get Flashtool to work.)
After that, I attempted to root it using Vroot, but the program didn't work (the error message was in Chinese, and when I clicked the supplied link, it was something about enabling USB debugging, which I had already done.) I then tried Kingo Android ROOT, which tried to download drivers for the phone, but always failed, so I downloaded and installed them manually as suggested. Kingo Android ROOT then did the same thing as Vroot, and told me to enable USB debugging, even though it was already enabled.
I tried reflashing it using Flashtool and trying again, but same issue.
I finally got fed up and tried to just upgrade to Kitkat again using the Software Updates feature in Phone info, but now the phone fails every time I try to update! It starts, enters the Android update screen, and then reboots a few seconds in. When the phone loads again, it says the update failed and asks me to redownload the file. I tried this several times, including leaving the phone off for a while before upgrading, and making sure it was at full charge AND on AC power, but still nothing.
So, to sum up, I can't root my phone, I can't upgrade my phone and I'm stuck on an outdated version of stock Android. I'm really frustrated with this and am hoping someone can help me.
YamiWheeler said:
So, to sum up, I can't root my phone, I can't upgrade my phone and I'm stuck on an outdated version of stock Android. I'm really frustrated with this and am hoping someone can help me.
Click to expand...
Click to collapse
Try rooting with this to see if it works
https://www.youtube.com/watch?v=1aq9YTlfCgc
Ahki767 said:
Try rooting with this to see if it works
Click to expand...
Click to collapse
MrMurphysLaw said:
https://www.youtube.com/watch?v=1aq9YTlfCgc
Click to expand...
Click to collapse
I tried this, but still nothing. :/
http://i.imgur.com/JboJ9VF.png
I'm beginning to think this is a driver issue, because I installed several drivers in an attempt to get Flashtool to work, but I don't know how to fix this. I used USBDeview to remove several drivers from my computer. After doing this, I plugged in my Xperia Z1 and it installed "C6903" on my computer, but it also prompted me to install software on the phone screen, but each time I click Install, it doesn't do anything...
I'm about ready to just chuck this phone out the window.
Windows doesn't even pick it up properly anymore, MTP doesn't install, I don't know how to fix this.
Does anyone know how to manually uninstall all of the drivers that Flashtool installs?
YamiWheeler said:
I'm about ready to just chuck this phone out the window.
Windows doesn't even pick it up properly anymore, MTP doesn't install, I don't know how to fix this.
Does anyone know how to manually uninstall all of the drivers that Flashtool installs?
Click to expand...
Click to collapse
Don't know how to uninstall the drivers (maybe in device manager?) but make sure you installed the correct ones from the flashtool drivers folder. The first time you plugged your phone in with usb debugging on, did the phone show anything about rsa keys?
Ahki767 said:
Don't know how to uninstall the drivers (maybe in device manager?) but make sure you installed the correct ones from the flashtool drivers folder. The first time you plugged your phone in with usb debugging on, did the phone show anything about rsa keys?
Click to expand...
Click to collapse
Not to my knowledge, no. :/
I suggest you need those drivers.
Firstly you need to read more. Vroot is NOT a trusted way to root your phone. It send your IMEI address to an ip address in chice for no known reason.
Secondly, there is no need to root on .534 FW, that's the point of downgrading to it. Just install the dual recovery whilst on that FW and then flash SuperSU.zip from chainfires website.
Then just flash a 4.4 rom of your choice.
YamiWheeler said:
Not to my knowledge, no. :/
Click to expand...
Click to collapse
Well i'm sure if the drivers ain't installed correctly you wouldn't be able to flash anyways so i don't think its a driver problem. try flashing .534 again and turn on usb debugging and plug your phone in with the screen on and see if there's any pop up
Edit: Just saw gregs reply, totally forgot this method but yes try installing nuts dualrecovery
gregbradley said:
I suggest you need those drivers.
Firstly you need to read more. Vroot is NOT a trusted way to root your phone. It send your IMEI address to an ip address in chice for no known reason.
Secondly, there is no need to root on .534 FW, that's the point of downgrading to it. Just install the dual recovery whilst on that FW and then flash SuperSU.zip from chainfires website.
Then just flash a 4.4 rom of your choice.
Click to expand...
Click to collapse
Wow, after all of the various options I tried, the Dual Recovery worked, even when nothing else on my system was recognizing the phone. Thank you so much. I managed to install Superuser too, but how do I flash a ROM at this point? By starting the dual recovery again?
Forgive my lack of knowledge of this, the only thing I've ever rooted was a Samsung Galaxy S3 Mini, and that process seemed a lot simpler than this. :/ At least, before your method.
YamiWheeler said:
Wow, after all of the various options I tried, the Dual Recovery worked, even when nothing else on my system was recognizing the phone. Thank you so much. I managed to install Superuser too, but how do I flash a ROM at this point? By starting the dual recovery again?
Click to expand...
Click to collapse
Press up button while booting (Sony logo) to get into TWRP to flash roms. ROM threads always have guides on how to flash their roms so just check there for any flashing guide.
Ahki767 said:
Press up button while booting (Sony logo) to get into TWRP to flash roms. ROM threads always have guides on how to flash their roms so just check there for any flashing guide.
Click to expand...
Click to collapse
But don't I have to unlock the bootloader first?
no
Thanks for all your help, it's working and all is well.
I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?
Seriously?
There aren't enough threads and guides for you to read already? Everything you need is already out there on this forum so why start another thread just because you are too lazy to search and read for yourself?
I have read around and have tried a number of guides a number of times. They haven't worked for me and I'm just wondering what i'm doing wrong. Even though all the information is out there, I don't have the experience to understand it apparently. I've spent hours trying to figure things out but i keep reading conflicting info and half-explained steps and now I'm just confused and would like a clear point in the right direction.
So, do i need to reflash the latest firmware, wait a few hours, then try again on a full charge? Or do i need a euro firmware? Which guide should i follow?
I've downloaded a few applications and driver packages and whatnot but if those could possibly conflict with each other and cause problems i could work with a fresh OS. I'm running OS X but i have linux VMs and friends with clean windows installs (mine is all sorts of messed up)
eatfoodnow said:
I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?
Click to expand...
Click to collapse
It isn't a question of firmware, the phone needs to have an unlockable bootloader to be able to be, well, unlocked. Here is a list http://forum.xda-developers.com/showthread.php?t=2181581 of P880 bootloader versions. Follow the guide to check which BL your phone has.
Thats obsolete, all versions can be unlocked afaik, either with official method or by fuse editing. No need to keep sim card in,you just need proper drivers
Oh, OK, I didn't know that. But, even better, OP should not have any trouble, provided he follows the BL unlock guide here http://forum.xda-developers.com/showthread.php?t=2224020
Maybe his BL is already unlocked OR is relocked (meaning can't be unlocked anymore).
Its more likely that his drivers are messed up imo.
The fuse editing method should work for everyone, i recommend you give it a try
So the fuse method would be the "BL-unlock.bat" method on that bootloader unlock forum post? I've tried it before, but I'll try it again. The directions only say to run it, is there anything else I need? Now, since it's a .bat file I absolutely have to run it on Windows, right? Because if so I'll use a friend's computer instead of my windows installation.
What are the necessary installations before I run the file? How should I configure settings on my phone? (like what type of usb connection should it be)
There are a lot of things that people expect readers to know but I'm really not very knowledgeable about standard practices for phone stuff so I really need every step. Thanks for helping!
Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.
Flying_Bear said:
Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.
Click to expand...
Click to collapse
Also, correct me if i'm wrong I only had stock for 2hours, but also stock needs usb debugging to be enabled or adb won't work?
Yep, afaik usb debugging needs to be enabled
When you are fast enough, it is possible in charging mode wihle the carger animation is shown. But you have install adb driver very fast...
So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!
eatfoodnow said:
So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!
Click to expand...
Click to collapse
you can check your bl status by entering sw mode (phone off, hold vol+ and insert charger) or reeboting into bl (adb reboot oem-unlock)
to install cm steps are:
-install recovery (you can choose either cwm or twrp, it's more about looks than functions)
-download rom zip onto sd card
-install said zip from said recovery, there's no adb involved
Now my personal opinion, I really don't see the point in flashing 10.1, i would go staright for cm11 if i were you
Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.
eatfoodnow said:
Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.
Click to expand...
Click to collapse
Factory reset then get nandroid manager app and see if you can restore your stuff with that
CM11 is bugless atm and performance (imo) is way superior
So after a factory reset/data wipe, my phone just booted into CM10.1 and now that's working. And it looks like all of my stuff on the phone is still there (though of course apps aren't installed and whatnot, that wouldn't make sense). Thanks for all the help!
I tried to find a feature list or something to see what exactly is better about CM11, and found out that "stable" doesn't exactly mean stable for CM, and that it looks like a good idea to update, so I think I will try to update to that. Do you know anywhere that has an actual feature list to show me what CM11 does that CM10.1 doesn't?
I'll admit, I didn't fully understand the root process back when I did this. I don't even remember all the steps I took. I got a locked Verizon (black 16GB) for an upgrade back in March. I always wanted this phone but never had an upgrade available. Well I forgot they had a Dev model out and stupidly got the free one with a new contract renewal.
I am running android 4.4 KK and am currently rooted with Xposed installed. I'm pretty sure the only way I can have write protection disabled is by booting into recovery, correct? Even though I select recovery at the fastboot screen, it just boots like normal. I guess my question is, is there any reason for me to be booting into recovery every time? Is there a way to tell if I have WP disabled on /system and root after a normal boot process? I swear I've had Xposed stop working after a normal boot.
EDIT: I'm seriously considering swapping this out for a new Dev model if they go on sale. I could use the extra storage and can easily just unlock the bootloarder and have root when L comes out for the first gen X.
IEcansuckit said:
I'll admit, I didn't fully understand the root process back when I did this. I don't even remember all the steps I took. I got a locked Verizon (black 16GB) for an upgrade back in March. I always wanted this phone but never had an upgrade available. Well I forgot they had a Dev model out and stupidly got the free one with a new contract renewal.
I am running android 4.4 KK and am currently rooted with Xposed installed. I'm pretty sure the only way I can have write protection disabled is by booting into recovery, correct? Even though I select recovery at the fastboot screen, it just boots like normal. I guess my question is, is there any reason for me to be booting into recovery every time? Is there a way to tell if I have WP disabled on /system and root after a normal boot process? I swear I've had Xposed stop working after a normal boot.
EDIT: I'm seriously considering swapping this out for a new Dev model if they go on sale. I could use the extra storage and can easily just unlock the bootloarder and have root when L comes out for the first gen X.
Click to expand...
Click to collapse
You can try installing something as a system app (App Ops for Root comes to mind https://play.google.com/store/apps/details?id=droidmate.appopsinstaller&hl=en) and see if it works. If it does, than write protection is off. The app on Play store is actually an installer that will put App Ops into your /system folder. If you have Xposed working properly, it might be OK already.
I remember when I rooted my VZW Moto Maker Edition on 4.2.2 (I think) I used SlapMyMoto and MotoWPNoMo (or something weird like that). I ran both and then installed Xposed and the framework failed to install properly (the version numbers in the app were red). I tried a few times and it didn't work. I ran the WP script a second time then Xposed worked fine. I must have missed a step in the WP off procedure.
If you boot normally and Xposed doesn't work, or you can't install to /system then I'd say you don't have WP off when booting normally.
fury683 said:
You can try installing something as a system app (App Ops for Root comes to mind https://play.google.com/store/apps/details?id=droidmate.appopsinstaller&hl=en) and see if it works. If it does, than write protection is off. The app on Play store is actually an installer that will put App Ops into your /system folder. If you have Xposed working properly, it might be OK already.
I remember when I rooted my VZW Moto Maker Edition on 4.2.2 (I think) I used SlapMyMoto and MotoWPNoMo (or something weird like that). I ran both and then installed Xposed and the framework failed to install properly (the version numbers in the app were red). I tried a few times and it didn't work. I ran the WP script a second time then Xposed worked fine. I must have missed a step in the WP off procedure.
If you boot normally and Xposed doesn't work, or you can't install to /system then I'd say you don't have WP off when booting normally.
Click to expand...
Click to collapse
Ok, I installed what you suggested, went into the app and tapped the "Install AppOps Root" button. It asked for root access and then rebooted my phone. So I guess this means that by default on a normal reboot, I have WP disabled and root access? Thanks for help clearing this up! I guess the phone was just acting weird that one time when the Xposed modules wouldn't work.
One last question, is there a reason why I can't get to recovery? Whenever I reboot into Recovery, it just starts up like normal? Is that because the normal recovery has been overwritten by a custom one in the root process?
IEcansuckit said:
Ok, I installed what you suggested, went into the app and tapped the "Install AppOps Root" button. It asked for root access and then rebooted my phone. So I guess this means that by default on a normal reboot, I have WP disabled and root access? Thanks for help clearing this up! I guess the phone was just acting weird that one time when the Xposed modules wouldn't work.
One last question, is there a reason why I can't get to recovery? Whenever I reboot into Recovery, it just starts up like normal? Is that because the normal recovery has been overwritten by a custom one in the root process?
Click to expand...
Click to collapse
If your bootloader isn't unlocked I don't think you can change recovery. You may be able to reflash the stock recovery from fastboot/mfastboot for your proper version, but don't quote me on that.
Someone with more experience can chime in. How are you rebooting to recovery? With an app/button, or via fastboot?
fury683 said:
If your bootloader isn't unlocked I don't think you can change recovery. You may be able to reflash the stock recovery from fastboot/mfastboot for your proper version, but don't quote me on that.
Someone with more experience can chime in. How are you rebooting to recovery? With an app/button, or via fastboot?
Click to expand...
Click to collapse
Correct. No unlock - no custom recovery.
It also depends on which method you used to achieve wp-off. Is rather not get into the finer details because it's really not important...
Are you using VOL+ to select recovery in the bootloader?
Edit: yes, when you rooted your phone, the stock recovery was overwritten to give you Android with write protection off. Looks like normal Android, but you have write access to system.
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
shabydog said:
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
Click to expand...
Click to collapse
AFAIK you will need a pc to 1)unlock your bootloader and 2)flash TWRP. After that the rest can be done locally. I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Droidphilev said:
I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Click to expand...
Click to collapse
Second that.
shabydog said:
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Click to expand...
Click to collapse
So at least once you need to connect your phone to a desktop computer. It can be practically running anything, within reason of course: Wiindows. Mac OSX, Linux (almost any distro).
You need to unlock your bootloader with one command, but a warning here: Unlocking the bootloader will erase everything from your phone..
Then you need to install a custom recovery, preferably TWRP. After that everything can be done from the phone itself. Well at least until you soft brick it somehow, then you'll might have to use the PC again.
Also two things:
1. No OTAs for rooted phones
2. Don't lock your bootloader if you want to mess with it, because with a locked bootloader, and Enable OEM Unlocking set to off, and without TWRP, if you soft brick it accidentally, you are boned.
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use?
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
And i really prefer to do it on the device and not by ADB commands.
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
shabydog said:
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
Click to expand...
Click to collapse
Well, you still will have to unlock it, if you want root, or want to flash a custom recovery.
Sent from my Nexus 6 running cyosp using Tapatalk
shabydog said:
......I really don't like the issue of trying to set the drivers of fastboot/google and so on!
Click to expand...
Click to collapse
Than do not 'root' your phone.
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
simms22 said:
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
Click to expand...
Click to collapse
Ha ha, or I don't want my birthday to be on the day I was born every year ?
I can recommend the NTRT, the Nexus Telepathic Rooting Tools.
OK.
I want to do that with a toolkit, only bcs it install the drivers.
What Is the most recommended and easiest to use?
I do looking for the 1 click do all.
Does NTRT do that?
Thank you all.
we are eventually goung to have a "my n6 is bricked, how do i fix it with one click" thread here. seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Sent from my Nexus 6 using Tapatalk
shabydog said:
Could anybody guide me through the steps, if needed?
Click to expand...
Click to collapse
<prev> step <next>
simms22 said:
seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Click to expand...
Click to collapse
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
wtherrell said:
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Click to expand...
Click to collapse
It is fairly enough to read directions and slowly-slowly.
NLBeev said:
<prev> step <next>
Click to expand...
Click to collapse
Thanks!
==========================================================
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
Click to expand...
Click to collapse
i agree with you. if there is somebody who knows the ins and outs already, a one click root would be great. and there will be. problem is that marshmallow just came out, and a few things have changed, like like yoe also need a custom kernel to have root on marshmallow.
shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
It is fairly enough to read directions and slowly-slowly.
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
Click to expand...
Click to collapse
There is a reason you're pushing this topic, and I'm quite sure it's because you would feel safer, if there was a tool that did the scary things instead of you. Well, there's no such tool. If you were willing to search XDA, you would find out that the first two weeks after Marshmallow came out were about people bricking their Nexus 6s with toolkits. Then the toolkit got updated and suddenly it knew that is has to flash a modified boot.img too for the root not to brick the phone. But for two weeks it didn't know, because it wasn't necessary for Lollipop. And it will only work until the next security update comes out. And that's once a month.
Meanwhile those who were willing to use the search function, and learned the five minute procedure, were able to update their rooted phones to the next security update and were able to root it as soon as the new modified boot image came out.
And this above is not something somebody will put in a help, or instructions for future updates.
Actually, this is my first time and I was able to do it pretty easily.
fastboot devices
fastboot oem unlock
my bootloader was unlocked within 30 seconds of turning it on.
then, you can easily root via CF Auto root. Just put it into fastboot then doubleclick on the windows, then root, etc....
or.............go into fastboot flash recovery twrpxxxx.img, then it always offers to run SuperSU, and you get custom recovery and root at the same time, etc......
actually the biggest pain is unlocking the bootloader. My Galaxy S4 already was unlocked, so all I did was use goomanager, flash TWRP which always offers to run SuperSU if you don't have it.
Pretty easy, I did unlock bootloader, root, and custom recovery in 10 min.
---------- Post added at 01:48 AM ---------- Previous post was at 01:44 AM ----------
............................Then I got sick of stock Google's ROM in 15 min and wiped it and put a custom ROM instead.
Thank you all so much...
@mikeprius
Thank you so much for the info'!
But, could you plz write more details? such as:
1. How did you installed the drivers? (from my expirience, many times the pc dosent install this easily).
I just need the Google oem driver and that's it?
2. When drivers was set - did you made anything in your phones settings? Which?
3. What did you had to do before pushing the files? (Like...put all the files in the same folder? *which files?)
4. And then entered to fastboot mode and typed in these commands in pc:
fastboot devices
fastboot oem unlock
Regarding your last sentence ("or...."):
If i just flash the recovery via fastbot mode I can enter to twrp recovery and it offers to flash the SuperSU?
Sounds to me the best option.
Thanks!
1. The drivers were set from a previous device, so I didn't have to set them, but they can be downloaded and set though.
2. You need to enable developer options and select OEM unlock and USB debugging.
3. I didn't push the files, I just had them on my computer and ran fastboot commands.
4. Those commands are to unlock the bootloader.
There are a lot of different ways to do the same thing (Root, custom recovery, unlock bootloader)
1. Run CF Auto Root on a locked bootloader. It will unlock it automatically (Chainfire has it set that way), root, then download Flashify app and flash the latest img of TWRP.
2. Run fastboot commands to manually unlock the bootloader, flash TWRP, then use TWRP's SuperSU which will root it.
3. Run fastboot commands to unlock bootloader, run CF Autoroot which will root and load SuperSU, then flash TWRP via Flashify or fastboot.
There are many different ways to do the same thing. I actually just googled youtube videos and watched them.
TWRP has SuperSU and root built in. TWRP knows if you don't have it and offers to load it for you.
I went the scenic route just because, but presumably you can achieve all (3) using Option #1 without having to deal with fastboot, adb, etc.....Chainfire's script runs automatically.
I realy try to help people but users that run into problems because of the usage of tookits (and innability to solve problems and/or even lack the most basic knowledge needed) should ask the toolkit dev. for support imo, and not boughter users that have invested time and effort to gain that knowledge to clean up their mess. Period
Hi all,
I am trying to relock the bootloader on 3T, with no success. I want to do it because of too many apps nagging me or not working with unlocked bootloader
here's what I did to unlock in the past and relock:
unlocking:
- enable dev options, enable oem unlocking & usb debugging
- flashed TWRP & fastboot oem unlock from command line (don't remember which I did first)
- got my phone wiped which was an an unexpected surprise!
- bootloader unlocked, the fist of those lovely warning screens telling me so
- tried to root without success, so no custom ROMs for me
- lived with it like this for a while, too many apps telling me they won't work, decided to relock
- got latest stock ROM, flashed it via TWRP, wiped, tried to fastboot oem lock ==> success reported by CLI, BUT device still unlocked
- flashed just the 3t recovery img, wiped, fastboot oem lock ==> success reported by CLI, BUT device still unlocked
- tried the qualcomm unbrick tool after installing the recommended drivers, can't have it see my device maybe because it's not bricked or maybe some other reason, I don't know. it doesn't show up in the app. Will uninstall and reactivate driver signature checks soon unless someone explains me how to make the bloody phone show up ...
So at this moment I have a many times-wiped phone with latest 9.0.4 stock ROM whose bootloader won't lock back. I am quite at a loss. I haven't tried any magisk or similat, SuperSU at the time told me I am not rooted.
I am tearing out the few hairs I have left. Any help for this poor family man so that he may not be allowed to walk in darkness? (quote from Uninvited). Thanks
Why don't you use Magisk hide to hide root/unlock status to those apps instead of loosing root/adaway and more?
pitrus- said:
Why don't you use Magisk hide to hide root/unlock status to those apps instead of loosing root/adaway and more?
Click to expand...
Click to collapse
I have never investigated Magisk, I think I installed it at the tima but there was some problem with it so I uninstalled it and didn't think much more about it. The problem is, my phone is not rooted (even though I tried it failed, I unlocked the bootloader to root it in the first place but was not successful), only OEM unblocked. So, so to say, I'm stuck in the worst of the possible worlds except for a bricked device. unlocked with no apparent way to relock it, and not rooted.
I feel like my phone is in some strange state where the normal procedures do not work. If I could at least figure out what's wrong with the rooting, I could go the full way AND then, in case use Magisk. but at the moment I feel like there is a need to put the phone in a known definite state whichever it is and work from there. I'd be happy to revert to stock and locked and then redo everything when needed in the future.
How could I troubleshoot further or get to such a "known state"? many thanks
The thing you did wrong was using the outdated SuperSU method of rooting which is not supported anymore. You should just flash the latest Magisk zip of their github page and then you will have root with the possibility of hiding it for bank apps and others.
https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
pitrus- said:
The thing you did wrong was using the outdated SuperSU method of rooting which is not supported anymore. You should just flash the latest Magisk zip of their github page and then you will have root with the possibility of hiding it for bank apps and others.
https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
Click to expand...
Click to collapse
Thanks pitrus, I'll have a look at it tomorrow and will update with what happened
MassiB said:
Thanks pitrus, I'll have a look at it tomorrow and will update with what happened
Click to expand...
Click to collapse
Hi, update. I installed Magisk but, seeing that it had a way to put the phone in EDL mode, instead of going full root I decided to go the other way around and try to make my phone as stock as possible and reserve the experiments to an unit other than my primary. So I used the Qualcomm "unbrick" tool, and was able to flash the OxygenOS version that came with it - a rather old Android 6 whose networking (wifi, mobile...) wasn't working. But an adb sideload of the latest version after having put the phone in recovery mode allowed me to restore the networking and to update to the last supported version.
Magisk made the difference in getting me out of the spot. Thanks for bringing it to my attention!