Hello, is this how you supposed to root and flash it?
1. Unlock bootloader
2. Install SuperSu through Recovery
3. Flash Stock Sony Rom
4. Flash CM12
Drevas said:
Hello, is this how you supposed to root and flash it?
1. Unlock bootloader
2. Install SuperSu through Recovery
3. Flash Stock Sony Rom
4. Flash CM12
Click to expand...
Click to collapse
No. Or yes if you are stupid and don't read the forums.
Sent from my D6603 using Tapatalk
---------- Post added at 15:32 ---------- Previous post was at 15:26 ----------
ondrejvaroscak said:
No. Or yes if you are stupid and don't read the forums.
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
Sorry for being rude, just woke up in bad mood...
The Safe way to root Z3 is to downgrade to KitKat, root it and use PRFCreator to make prerooted FW. You can find all the info here if you spend like 10 minutes of your life.
Sent from my D6603 using Tapatalk
ondrejvaroscak said:
No. Or yes if you are stupid and don't read the forums.
Sent from my D6603 using Tapatalk
---------- Post added at 15:32 ---------- Previous post was at 15:26 ----------
Sorry for being rude, just woke up in bad mood...
The Safe way to root Z3 is to downgrade to KitKat, root it and use PRFCreator to make prerooted FW. You can find all the info here if you spend like 10 minutes of your life.
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
Not sure how do i downgrade to kitkat from lolipop
Drevas said:
Not sure how do i downgrade to kitkat from lolipop
Click to expand...
Click to collapse
Using FlashTool
Sent from my D6603 using Tapatalk
Why not just unlock the bootloader the official way, flash a custom recovery (Cyanogen, TWRP, etc.), and then flash SuperSU Update ZIP from there? It takes maybe 10 minutes, and apart from obtaining the unlocking code, it is pretty straightforward.
fonix232 said:
Why not just unlock the bootloader the official way, flash a custom recovery (Cyanogen, TWRP, etc.), and then flash SuperSU Update ZIP from there? It takes maybe 10 minutes, and apart from obtaining the unlocking code, it is pretty straightforward.
Click to expand...
Click to collapse
So i dont need to downgrade to nothing?
Also which ROM is the most stable and which custom recovery you reccomend on installing?
fonix232 said:
Why not just unlock the bootloader the official way, flash a custom recovery (Cyanogen, TWRP, etc.), and then flash SuperSU Update ZIP from there? It takes maybe 10 minutes, and apart from obtaining the unlocking code, it is pretty straightforward.
Click to expand...
Click to collapse
Because unlocking phone without having TA backup is irreversible process leading to loss of low light pictures quality and couple other DRM related issues. Downgrade to KitKat is safe way to keep your bootloader locked and possibility to backup TA.
Sent from my D6603 using Tapatalk
ondrejvaroscak said:
Because unlocking phone without having TA backup is irreversible process leading to loss of low light pictures quality and couple other DRM related issues. Downgrade to KitKat is safe way to keep your bootloader locked and possibility to backup TA.
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
AFAIK if you re-lock your bootloader then flash a stock FTF with FlashTool, TA is replaced with a working copy. I might be wrong though.
fonix232 said:
AFAIK if you re-lock your bootloader then flash a stock FTF with FlashTool, TA is replaced with a working copy. I might be wrong though.
Click to expand...
Click to collapse
Problem of TA is that it is device specific, unique on each phone.
Sent from my D6603 using Tapatalk
Related
Good morning!
So, yesterday evening I rooted my N5 with Towelroot, installed TWRP and then flashed the latest SuperSU! Everything went fine and now I want to install PA (4.4 RC1). But I'm not quite sure if I need to unlock the bootloader for that... I think that only needs to be done for a kernel. So what should I do? Leave it locked and flash PA, or unlock it and flash PA?
Also, if someone could set me up with the 4.4.3 gapps, that would be nice. I downloaded a file, but its not a mini version and only has 97MB. The full versions are a lot bigger if I remember correctly, aren't they?
Anyway thanks!
*edit: I'm currently on the 4.4.3 stock ROM. That means that I don't need to update my radio, because it should already be the latest version from the OTA... Correct me if In wrong though!
Sent from my Nexus 5 using Tapatalk
Please can you ensure you ask questions in the questions section ?
The bootloader only needs to be unlocked to flash recovery which you need for rooting. This isn't an issue for you because you used the new exploit that means you can root without having to unlock the bootloader
Even though you've rooted already, I strongly urge you to read the pre root section in the thread shown in my signature to bump up your basic knowledge
Sent from my Nexus 5 using Tapatalk
rootSU said:
Please can you ensure you ask questions in the questions section ?
The bootloader only needs to be unlocked to flash recovery which you need for rooting. This isn't an issue for you because you used the new exploit that means you can root without having to unlock the bootloader
Even though you've rooted already, I strongly urge you to read the pre root section in the thread shown in my signature to bump up your basic knowledge
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I do have basic knowledge (rooted my Nexus Phones before, every time with fastboot). I'm just asking if it is important to unlock the hootloader before flashing a ROM, as I'm not sure. Sorry for posting in the false section...
Sent from my Nexus 5 using Tapatalk
julbra18 said:
I do have basic knowledge (rooted my Nexus Phones before, every time with fastboot). I'm just asking if it is important to unlock the hootloader before flashing a ROM, as I'm not sure. Sorry for posting in the false section...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You can install custom ROMs, but only ROMs based on stock firmware and using stock kernel. ROMs like CyanogenMod, you can't install at all because you cannot flash the custom kernel that comes with it. Unlocked bootloader allows you to install unsigned kernels onto your phone.
fxdil said:
You can install custom ROMs, but only ROMs based on stock firmware and using stock kernel. ROMs like CyanogenMod, you can't install at all because you cannot flash the custom kernel that comes with it. Unlocked bootloader allows you to install unsigned kernels onto your phone.
Click to expand...
Click to collapse
Where did you get this information? My bootloader is locked and I can flash all kernels via recovery
Sent from my Nexus 5 using Tapatalk
rootSU said:
Where did you get this information? My bootloader is locked and I can flash all kernels via recovery
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Isn't that the case, or have I been misinformed? I left my boot loader unlocked since the day I was rooted, mostly because of that fact (I remembered reading it somewhere) and also because I can't do a RMA.
Sent using Etch-a-Sketch
fxdil said:
Isn't that the case, or have I been misinformed? I left my boot loader unlocked since the day I was rooted, mostly because of that fact (I remembered reading it somewhere) and also because I can't do a RMA.
Sent using Etch-a-Sketch
Click to expand...
Click to collapse
You unlock the bootloader to flash a custom recovery. You flash kernels/ROMs in a custom recovery, not in bootloader.
Also this thread is in the wrong section.
So, if I just unlock my bootloader with bootunlock I won't have any problems?
Sent from my Nexus 5 using Tapatalk
julbra18 said:
So, if I just unlock my bootloader with bootunlock I won't have any problems?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sure. Also you wont have any problems if you DON'T unlock your bootloader
Sent from my Nexus 5 using Tapatalk
Lethargy said:
You unlock the bootloader to flash a custom recovery. You flash kernels/ROMs in a custom recovery, not in bootloader.
Also this thread is in the wrong section.
Click to expand...
Click to collapse
That was where I was getting at, since I learnt to root using the manual way and not using a toolkit, I had to unlock my bootloader first before flashing a custom recovery. Never occurred to me to relock it.
(if I made a mistake somewhere, I apologized. I'm still learning, and learnt something new today!)
rootSU said:
Sure. Also you wont have any problems if you DON'T unlock your bootloader
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'll try it with the locked one first, I can change it later on anyways! Thanks for your help!
Sent from my Nexus 5 using Tapatalk
fxdil said:
That was where I was getting at, since I learnt to root using the manual way and not using a toolkit, I had to unlock my bootloader first before flashing a custom recovery. Never occurred to me to relock it.
(if I made a mistake somewhere, I apologized. I'm still learning, and learnt something new today!)
Click to expand...
Click to collapse
You can flash a kernel/ROM in a custom recovery regardless bootloader state, but the bootloader needs to be unlocked to use fastboot (i.e. flash the custom recovery in the first place). A bunch of people relock their bootloader with an app (and unlock when necessary, doesn't delete internal storage through this method) for extra security (internal storage wipes if bootloader is unlocked via fastboot).
Wondering what version of twrp to use to flash recovery for root or am I not able with new version 4.4.4
Droid Maxx
Sent from my XT1080 using XDA Free mobile app
boffster99 said:
Wondering what version of twrp to use to flash recovery for root or am I not able with new version 4.4.4
Droid Maxx
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Well, you can downgrade to 4.4, take the 4.4.4 OTA, and then flash the latest TWRP and install the apropiate root for the phone.
I was already at 4.4 then took the ota to 4.4.4 seems to be several versions of twrp. Just wondering what works for the maxx and does root change with the new ota?
Sent from my XT1080 using XDA Free mobile app
boffster99 said:
I was already at 4.4 then took the ota to 4.4.4 seems to be several versions of twrp. Just wondering what works for the maxx and does root change with the new ota?
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Use whatever version you want, 2.7 works though. The update didn't require stock recovery or removing of root though. Not sure what you mean by does root change but same process as it has always been.
akellar said:
Use whatever version you want, 2.7 works though. The update didn't require stock recovery or removing of root though. Not sure what you mean by does root change but same process as it has always been.
Click to expand...
Click to collapse
So your saying you took the OTA with twrp? Or you manually flashed the update in twrp?
an21281 said:
So your saying you took the OTA with twrp? Or you manually flashed the update in twrp?
Click to expand...
Click to collapse
Flashed in TWRP. Same end result with half the headache.
I thought I had to go back to stock to take the update so I did. Sorry I didn't keep twrp and do it that way. Oh well. Thanks for the replies I really appreciate it.
Sent from my XT1080 using XDA Free mobile app
joel_sinbad said:
Well, you can downgrade to 4.4, take the 4.4.4 OTA, and then flash the latest TWRP and install the apropiate root for the phone.
Click to expand...
Click to collapse
Once on 4.4.4 - you cant downgrade, the bootloader wont allow you.
CrazyRussianXDA said:
Once on 4.4.4 - you cant downgrade, the bootloader wont allow you.
Click to expand...
Click to collapse
Don't flash the motoboot.img, that's the bootloader, skip this line...
Im on the same boat.
Currently im on 4.4, unlocked bootloader and thats all.
In order to get root, should i flash first twrp, root and then take the ota?
And other question.. ¿Its possible to lock again the bootloader? Im afraid to unlock it again, i spend $25
conquesoextra said:
Im on the same boat.
Currently im on 4.4, unlocked bootloader and thats all.
In order to get root, should i flash first twrp, root and then take the ota?
And other question.. ¿Its possible to lock again the bootloader? Im afraid to unlock it again, i spend $25
Click to expand...
Click to collapse
If your unlocked there is no way to lock the phone, flash twrp and boot into it, it will ask you to root on exiting.
Thank you ¿even if i try whit fastboot oem lock?
This process is important? I was deleting SuperSU and in says that if I delete SuperSU I will delete this file too...
If you're unrooting, you don't need to keep it.
Ok, thanks.
There is a way to see if there is any modifications to the system's file?
Sent from my Nexus 5 using XDA Free mobile app
There's an OTA checker flashable zip in general I think.
No, not in the ota, I say in general, if I want just to control of there is any modifications without flash anything
Sent from my Nexus 5 using XDA Free mobile app
Giolte_ said:
No, not in the ota, I say in general, if I want just to control of there is any modifications without flash anything
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I don't understand. Please rephrase
If I want to check if the system's file are modified, how can I do?
Sent from my Nexus 5 using XDA Free mobile app
Giolte_ said:
If I want to check if the system's file are modified, how can I do?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
There is only one way. By flash the OTA checker zip in custom recovery. It can be found in the general forum I believe.
---------- Post added at 10:15 AM ---------- Previous post was at 10:12 AM ----------
Here it is
http://forum.xda-developers.com/showthread.php?t=2927865
Ok, so I have to flash this with flashify (rooted with towelroot)
After the flash I'll have to unroot the phone and just install Lollipop with the ota?
Sent from my Nexus 5 using XDA Free mobile app
Giolte_ said:
Ok, so I have to flash this with flashify
Click to expand...
Click to collapse
Flash what with Flashify?
I think the best bet for you is to read the thread about root / update in my signature. OTA is proving too troublesome. I can't hand hold you through the whole process.
I mean the zip checker
Sent from my Nexus 5 using XDA Free mobile app
Giolte_ said:
I mean the zip checker
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I already told you.
Ok, I've read your thread about how to upgrade to Lollipop the Nexus.
The fact is that my main pc have no working USB ports, so if I want to unlock the bootloader and stuff like this I have to use my second pc, and it is very slow (the last time to just fastboot a factory image it tooks me one hour of suffering).
I think that the method 2b is the one that is closest to my situation:
1. Unlock bootloader if necessary (This wipes data)
2. Accept OTA update
3. Fastboot flash a custom recovery image (of your choice)
4. Fastboot flash a custom boot.img (@Chainfire for basic root, @sykopompos for full permissive mode)
5. Flash from recovery, SuperSU
Click to expand...
Click to collapse
I don't want root, so:
2. Accept OTA update
Click to expand...
Click to collapse
If I have understood, the only thing that I have to do is use flashify to flash the OTA checker zip. file and than proceed with the OTA, right?
If there is another way to do this without use the PC, it will be great, but I don't know.
Is what I said right or I forgot something?
Thank you with your help anyway!
Giolte_ said:
If I have understood, the only thing that I have to do is use flashify to flash the OTA checker zip
Click to expand...
Click to collapse
You haven't understood. I told you how to flash it. I did NOT say flash via flashify please try to read properly
There is only one way. By flash the OTA checker zip in custom recovery.
Click to expand...
Click to collapse
This is what you mean?
If yes, I can't flash with a custom recovery because I have the stock recovery (because I'm rooted with only Towelroot, so stock recovery and locked bootloader)
Giolte_ said:
This is what you mean?
If yes, I can't flash with a custom recovery because I have the stock recovery (because I'm rooted with only Towelroot, so stock recovery and locked bootloader)
Click to expand...
Click to collapse
Then you can't use it! Wait for the OTA and install it.
I already have the OTA, but I think that there could be some issues, this is why I want to check if everything it's good, I don't want to brick/bootloop the device
Giolte_ said:
I already have the OTA, but I think that there could be some issues, this is why I want to check if everything it's good, I don't want to brick/bootloop the device
Click to expand...
Click to collapse
You wont brick it. If you're not stock, it wont install.
Thank you, it works
Please help i am trying to flash stock rom but i am getting remote failure error
anujdevrani said:
Please help i am trying to flash stock rom but i am getting remote failure error
Click to expand...
Click to collapse
Bootloader unlocked?
acejavelin said:
Bootloader unlocked?
Click to expand...
Click to collapse
is unlocking the bootloader required for flashing stock rom???
anujdevrani said:
is unlocking the bootloader required for flashing stock rom???
Click to expand...
Click to collapse
Not if it's the identical version... Although the error your receiving is common when this is the case.
Can you give a screenshot of the flash attempt from start to finish?
Sent from my MotoG3 using Tapatalk
acejavelin said:
Not if it's the identical version... Although the error your receiving is common when this is the case.
Can you give a screenshot of the flash attempt from start to finish?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
It came with the lollipop version.. Now i am trying to flash the mm one...currently i have the mm one installed on the device but its not booting up
But mm has two builds available 6.0 and 6.0.1... I am not sure which one is currently installed... However the one i am trying to flash is 6.0.1
anujdevrani said:
It came with the lollipop version.. Now i am trying to flash the mm one...currently i have the mm one installed on the device but its not booting up
Click to expand...
Click to collapse
The version it shipped with not relevant, you must use the same version that is currently installed.
Were you able to successfully flash? Did you do the factory reset before starting the process (boot will fail if you don't)?
Sent from my MotoG3 using Tapatalk
acejavelin said:
The version it shipped with not relevant, you must use the same version that is currently installed.
Were you able to successfully flash? Did you do the factory reset before starting the process (boot will fail if you don't)?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
How do i reset the phone.... I am unable to boot to recovery
..
anujdevrani said:
How do i reset the phone.... I am unable to boot to recovery
..
Click to expand...
Click to collapse
If the bootloader is locked (and oem unlocking was not previously enabled), you can't start recovery, and you can't flash the identical version via fastboot... Your device is bricked and needs to be repaired/replaced by Moto. You should contact their customer service.
Sent from my MotoG3 using Tapatalk
acejavelin said:
If the bootloader is locked (and oem unlocking was not previously enabled), you can't start recovery, and you can't flash the identical version via fastboot... Your device is bricked and needs to be repaired/replaced by Moto. You should contact their customer service.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Okk... I guess i have to now.
Make sure you don't update to 7.1.1 on a locked bootloader for the Verizon model otherwise, the depixel8 exploit will no longer work. It was confirmed by the developers of it already as you can check at their site and see as well. Now me personally I enjoy stock so I don't care but I figured for people with the Verizon model like me would care to see this.
Do not attempt to downgrade or any other methods of rooting until you see a tested and working method by one of the XDA devs in the Android Development forums for the Pixel.
learned this the hard way by updating my Verizon Pixel XL 128 installing twrp, then boot-to-root then bootloop. it appears it breaks twrp & root. i could be wrong. anybody else have a similar experience?
macboss said:
learned this the hard way by updating my Verizon Pixel XL 128 installing twrp, then boot-to-root then bootloop. it appears it breaks twrp & root. i could be wrong. anybody else have a similar experience?
Click to expand...
Click to collapse
If you're unlocked it shouldn't have re-locked it?
Sent from my Pixel using Tapatalk
macboss said:
learned this the hard way by updating my Verizon Pixel XL 128 installing twrp, then boot-to-root then bootloop. it appears it breaks twrp & root. i could be wrong. anybody else have a similar experience?
Click to expand...
Click to collapse
I'm pretty sure the boot to root doesn't work with TWRP. Use a factory image if possible and try to install TWRP and use the SuperSU zip instead.
If we are unlocked BL, rooted, stock recovery with SR5, will root break if we adb sideload?
joshw0000 said:
If you're unlocked it shouldn't have re-locked it?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
I was thinking the same thing... The update in general wouldn't have gone through if it was rooted.
so how do I update if I'm unlocked and have twrp installed? I'm assuming I shouldn't take the OTA update?
Bought my pixel from the Google store. Pixels from the Google store, are the bootloader's locked or unlocked?
Sent from my Pixel XL using Tapatalk
They are locked upon purchasing however, you can easily unlock them.
jreink01 said:
Bought my pixel from the Google store. Pixels from the Google store, are the bootloader's locked or unlocked?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Archangel said:
They are locked upon purchasing however, you can easily unlock them.
Click to expand...
Click to collapse
Might be interested in rooting at some point, is it my understanding to not take the 7.1.1 update then. Or wouldn't it matter since my bootloader is still locked? I guess what I'm asking if root would still be possible if i took the update?
Sent from my Pixel XL using Tapatalk
jreink01 said:
Might be interested in rooting at some point, is it my understanding to not take the 7.1.1 update then. Or wouldn't it matter since my bootloader is still locked? I guess what I'm asking if root would still be possible if i took the update?
Click to expand...
Click to collapse
If you are have a phone from Verizon it is required to have unlocked bootloader to obtain root.
So if it is a Verizon phone and you take 7.1.1 update - you won't be able to get root
km8j said:
If we are unlocked BL, rooted, stock recovery with SR5, will root break if we adb sideload?
Click to expand...
Click to collapse
Yes
Sent from my Pixel using Tapatalk
---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------
mrj0087 said:
so how do I update if I'm unlocked and have twrp installed? I'm assuming I shouldn't take the OTA update?
Click to expand...
Click to collapse
I side loaded the OTA and went through the process again have twrp and root
Sent from my Pixel using Tapatalk
I bought my device from UK, i got it unlocked and rooted but without TWRP recovery, what is the best option for me to install the update ?
And does it erase my device ?
Thanks in advace ...
I'm running Build : NDE63V
guandms said:
I bought my device from UK, i got it unlocked and rooted but without TWRP recovery, what is the best option for me to install the update ?
And does it erase my device ?
Thanks in advace ...
I'm running Build : NDE63V
Click to expand...
Click to collapse
With an unlocked BL, you're pretty free to do whatever you want. I've done it multiple ways; to me, the most straightforward steps are:
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Enjoy!
km8j said:
If we are unlocked BL, rooted, stock recovery with SR5, will root break if we adb sideload?
Click to expand...
Click to collapse
Yes, but just reroot. Works fine.
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
jreink01 said:
Might be interested in rooting at some point, is it my understanding to not take the 7.1.1 update then. Or wouldn't it matter since my bootloader is still locked? I guess what I'm asking if root would still be possible if i took the update?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
On a Google Store pixel, you can always unlock your bootloader. You are posting in a vzw pixel revelent thread, depixel8 and any talk on the subject doesn't apply. Don't get confused.
Sorry, didn't know i was in a Verizon thread.
Sent from my Pixel XL using Tapatalk
epic4grooted said:
Yes
Sent from my Pixel using Tapatalk
---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------
I side loaded the OTA and went through the process again have twrp and root
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Sorry I'm confused. So use adb side load in twrp? So I'm doing adb reboot recovery then adb side load OTA.zip once in twrp? Then I have to reflash twrp and root?
Download the OTA zip from Google run flash all it then go through the steps to reroot and install twrp
Sent from my Pixel using Tapatalk
I unlocked the BL using dePixel8 last Wed. when I picked up my Pixel. It updated to NDE63X via OTA after I unlocked BL. Received OTA update to NMF260, downloaded and installed it last night via normal OTA process. BL unlock is unchanged: unlocked status.
It helps if the phone is plugged in and on WiFi since it is a 260MB download.
So far 7.1.1 works great.
epic4grooted said:
Download the OTA zip from Google run flash all it then go through the steps to reroot and install twrp
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
got it