Hello Everyone.
Yesterday, I updated my "Global" Z1 firmware to Android 4.3 and then {Of course} I had no root. I already had a TA backup from 4.2 (534) and already un/relocked the bootloader so I am not worried about warranty. So I tried something to get Full root on Locked bootloader.
What I basically did is that I unlocked the bootloader, turned on USB debugging, downloaded doomkernel (Made by @DooMLoRD) and then in fastboot I wrote the command:
Code:
fastboot boot boot.img
Then it restarted and booted doomkernel once (fast boot filename.img makes the phone boot that kernel once) and then flashed the latest SuperSU zip using TWRP recovery (VOL Down) and then went to Advanced → Fix Permissions. Then tried mounting /system as R/W but with no success. So I then flashed doomkernel using the following fastboot command:
Code:
fastboot flash boot boot.img
and then installed the latest XZDualRecovery by @[NUT] and then I had 4 recoveries So I flashed stock kernel and XZDualRecovery wasn't uninstalled, So what I did is that I flashed the SuperSU zip again (using TWRP) and then booted up.
In the first boot, I couldn't mount /system as R/W but I restarted for some reason. and tried to mount as R/W and it worked!
So I relocked my bootloader (by restoring the TA) and now I have full root on TOTALLY STOCK 4.3 Locked bootloader :victory:
Now, when I go to /system/etc/init.d I find a file named "99SuperSUDaemon" and I remember reading somewhere that init.d has something to do with what should work on boot (other than system booting things, cuz I only see that file). So maybe that fixed the "Partial root" problem. Don't know where it came from, but it works :highfive:
Just thought that it might be good to share some info with others, might be useful for people who doesn't want to use ftf's of other places like someone in MEA (me) doesn't want to use UK or US or any other ftf cuz of more bloatware.
Regards,
~J2C
May I ask you how you can verified if you have a Full Root or Semi Root?
Well, I have been removing system apps and I can mount /system as R/W.
If there's a way I can check, please tell me how.
Edit: I actually don't know what does "Semi Root" mean.
Regards,
~J2C
That was allready told here, with links to the description.
http://forum.xda-developers.com/showthread.php?t=2588331
Just2Cause said:
Edit: I actually don't know what does "Semi Root" mean.
Click to expand...
Click to collapse
Not Full Root. Half and Half.
eclyptos said:
Not Full Root. Half and Half.
Click to expand...
Click to collapse
Yes, I have full root.
In case if you're on 4.2 and you can OTA to 4.3 (and you have root) try to copy the file 99SuperSUDaemon to /system/etc/init.d and then reboot, uninstall dual recovery, update to 4.3 OTA and check if you have full root. If you DO have full root, then you can install XZDualRecovery again and enjoy android.
Edit: uploaded the file, unzip (NOTE: it's NOT a flashable zip!) and copy it to /system/etc/init.d and give it permissions rwsr-xr-x
Regards,
~J2C
Just2Cause said:
Yes, I have full root.
In case if you're on 4.2 and you can OTA to 4.3 (and you have root) try to copy the file 99SuperSUDaemon to /system/etc/init.d and then reboot, uninstall dual recovery, update to 4.3 OTA and check if you have full root. If you DO have full root, then you can install XZDualRecovery again and enjoy android.
Edit: uploaded the file, unzip (NOTE: it's NOT a flashable zip!) and copy it to /system/etc/init.d and give it permissions rwsr-xr-x
Regards,
~J2C
Click to expand...
Click to collapse
Could you please explain step by step? I mean for example when fid you install dual recovery?
Sent from my C6903 using Tapatalk
Just2Cause said:
In case if you're on 4.2 and you can OTA to 4.3 (and you have root) try to copy the file 99SuperSUDaemon to /system/etc/init.d and then reboot, uninstall dual recovery, update to 4.3 OTA and check if you have full root. If you DO have full root, then you can install XZDualRecovery again and enjoy android.
Click to expand...
Click to collapse
I do not use OTA, I don't have it. So I have to find a different way. I can only update to 4.3 from recovery or flashtool.
ArashMiniStar said:
Could you please explain step by step? I mean for example when fid you install dual recovery?
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
I installed dual recovery after flashing doomkernel
eclyptos said:
I do not use OTA, I don't have it. So I have to find a different way. I can only update to 4.3 from recovery or flashtool.
Click to expand...
Click to collapse
I can go to cwm and create a flashable zip from there and give it to you if you want
@eclyptos
I know you didn't ask for a 4.3 flashable zip but here it is:
Update.zip
I don't know if something needs to be removed from the zip, but all I did is that I wen to cwm and clicked on "Clone ROM to update.zip" and then uploaded it to google drive.
Regards,
~J2C
Which rom it's exactly in the zip file? Stock?
eclyptos said:
Which rom it's exactly in the zip file? Stock?
Click to expand...
Click to collapse
Yes, Global stock.
But I removed some apps that I don't want/use (most of them are extensions for twitter and flickr and such things) and I added some apps.
Regards,
~J2C
Root for locked bootloader but need to be unlock-able?!
If the BL is unlockable then it is useless to say it is for locked bootloader, if it's lock it's lock.
Once it is unlocked user can flash a pre rooted rom or kernel...
babylonbwoy said:
Root for locked bootloader but need to be unlock-able?!
If the BL is unlockable then it is useless to say it is for locked bootloader, if it's lock it's lock.
Once it is unlocked user can flash a pre rooted rom or kernel...
Click to expand...
Click to collapse
Can you try this for me? You'll find attached zip containing the file in the original post in page 1.
Just2Cause said:
In case if you're on 4.2 and you can OTA to 4.3 (and you have root) try to copy the file 99SuperSUDaemon to /system/etc/init.d and then reboot, uninstall dual recovery, update to 4.3 OTA and check if you have full root. If you DO have full root, then you can install XZDualRecovery again and enjoy android.
Edit: uploaded the file, unzip (NOTE: it's NOT a flashable zip!) and copy it to /system/etc/init.d and give it permissions rwsr-xr-x
Regards,
~J2C
Click to expand...
Click to collapse
Works!
I don't have init.d folder but I gained full root as well as my bionz is intact....
Related
Hello,
I just wanted to share how I have rooted my device today, and it was way easier than the methods I have been reading about so far.
My device: Xperia Z2 , C6543.
How I did it:
1- I updated my flashtool to the latest version, downloaded the 7.1.2.A.0.314 ftf for my region and flashed like instructed in the post. (Note that If you don't have flashtool installed, you have to go inside it's drivers folder and install the Z2 driver so it can communicate to the phone).
http://forum.xda-developers.com/showthread.php?t=2759934
2- After the downgrade to the 7.1.2.A.0.314 version mentioned above, I went to the flashtool menu (My 65XX -> Root -> Force towelroot)
When prompted to, I have choosen the SuperSU option.
Then the towelroot app showed in the phone's screen, I've tapped on "make it rain" and let it run.
After that the phone restarted and it was rooted.
3. Okay, now that the 7.1.2.A.0.314 is rooted, an OTA update notification showed up to update to the same version (lol). Well, I just let it update, and the root was there (I confirmed by restoring some data in titanium backup).
4. After that, another OTA update showed up to update to 23.0.1.A.0.167. Again, I let it download and install.
Well, that's what it took for me to root my z2 in it's latest version with only one downgrade and no manual adb commands, no manual rootkit downloads, pretty similar to the way I've always rooted my ZQ (R.I.P - it drowned lol).
The credits are due to the hard-working people who made all the mentioned tools, I am only doing my part by sharing an easier method than what i've seen around. Feel free to share your toughts.
Laters!
Sorry to be noob! Will it break anything like camera x reality or anything? And for warranty, can I claim it by just unrooting it(it's in the su) ?
Did not break anything for me. Now I can use foldermount and transfer heavy apps to the external sd. Wonderful. As for the warranty, since there is no recovery installed and no bootloader unlocked, it is as easy as doing the step 1 in the procedure described. It will flash the unrooted system back.
But ist same method, if u use this or this tool.
This post doesnt deserve an original development section!
thanks. I will follow this guide as i had root, upgraded and lost it. But i've have been itching to flash stuff lol.
But ist same method, if u use this or this tool.
Click to expand...
Click to collapse
I am not sure I understand what you mean, but if you are talking about the xperiarootkit compared to the "force towelroot" from flashtool, I checked the scripts in advance and they seem to be the same thing yes. The only shortcut to what I did was not having to flash recovery, and creating customized ftf, etc.
This post doesnt deserve an original development section!
Click to expand...
Click to collapse
I am sorry you feel that way man, that comment was a great way to add value to the conversation, thank you.
remydlc said:
thanks. I will follow this guide as i had root, upgraded and lost it. But i've have been itching to flash stuff lol.
Click to expand...
Click to collapse
Did you tried ota survival in Supersu?
rjshrjndrn said:
Did you tried ota survival in Supersu?
Click to expand...
Click to collapse
not before applying the OTA. Perhaps that would have helped. I have the app installed, but it says the binaries are not installed, to consult the forums for re-rooting
remydlc said:
not before applying the OTA. Perhaps that would have helped. I have the app installed, but it says the binaries are not installed, to consult the forums for re-rooting
Click to expand...
Click to collapse
I think you have to do all the stuff one again and root device. Then check the option for its root survival and do ota updates. I think you'll be fine with the updates.
Question, /System RW? (don't confuse it with a TA Restore, as it could only be restoring to the /Data partition).
Moscow Desire said:
Question, /System RW? (don't confuse it with a TA Restore, as it could only be restoring to the /Data partition).
Click to expand...
Click to collapse
I doubt you'll have system RW access as sony ric should still be running, but if root is working fine flashing nut's recovery should fix this easily.
root achieved and kept
Nice one thanks for the info worked well and updated to .167 ota and kept root.
Going to give this a try. Thanks
Thanks for the info, OP.
I used flashtool to downgrade my D6503 to .55, tried to use towelroot, no luck. used the CVE root exploit and got root, but after that update center failed the verification to .314.
Your method works, so cheers!
Will the Phone be wiped during this root method
ecolupo said:
Will the Phone be wiped during this root method
Click to expand...
Click to collapse
flashtool will wipe your phone unless you unselect data partition (not recommended). The rooting part is non-destructive so no that part won't your phone.
ptmaniac said:
I doubt you'll have system RW access as sony ric should still be running, but if root is working fine flashing nut's recovery should fix this easily.
Click to expand...
Click to collapse
Tried to install nut's recovery with supersu option but all the apks in the script could not be written into system folder. Also could not install xposed installer. May have to downgrade again and avoid this method
update: no need to downgrade again. sony_ric prevents r/w to system folder even with root, so I just used ric killer by forty two: http://forum.xda-developers.com/xperia-z2/general/4-4-4-sony-ric-killer-t2953141
afterward I was able to install xposed installer via normal method.
Thank you for the tutorial. It worked fine for me.
What will happen if I do a factory reset via settings-menu? Will root be gone? Do I have to downgrade again or can I install SuperSU to get root back?
Sent from my D6503 using XDA Free mobile app
Step0 Extract These https://www.dropbox.com/s/3w4s95zonkzstfp/Guide.zip?dl=0
https://www.dropbox.com/s/i2zewkiles047jb/Guide2.rar?dl=0 Files To A Folder
Step1 Place The SuperSu zip to your SD card
Step2 Boot To Fastboot Mode And Click On The Batch File(It Will Install The Kernel With Recovery)Or Flash Kernel In Flashtool
Step3 Reboot Phone Press Volume down While Booting you will boot into twrp Flash SuperSu zip and go to advanced Tab and reboot to bootloader(Warning Your Phone Wont Boot Into System)
Step4 Open Flashtool And Flash The FTF Attached
Step5 Your Rooted
PS:All Files Provided Are Not Mine They Are The Work Of The Respective Developers
Also I Am Not Responsible For Bricked Devices
i had unlockd BL, I flashed lollipop ftf by flashtool. my BL still unlockd or is it Locked now?
CLINTZ9 said:
Step0 Extract These https://www.dropbox.com/s/3w4s95zonkzstfp/Guide.zip?dl=0
https://www.dropbox.com/s/i2zewkiles047jb/Guide2.rar?dl=0 Files To A Folder
Step1 Place The SuperSu zip to your SD card
Step2 Boot To Fastboot Mode And Click On The Batch File(It Will Install The Kernel With Recovery)Or Flash Kernel In Flashtool
Step3 Reboot Phone Press Volume down While Booting you will boot into twrp Flash SuperSu zip and go to advanced Tab and reboot to bootloader(Warning Your Phone Wont Boot Into System)
Step4 Open Flashtool And Flash The FTF Attached
Step5 Your Rooted
PS:All Files Provided Are Not Mine They Are The Work Of The Respective Developers
Also I Am Not Responsible For Bricked Devices
Click to expand...
Click to collapse
Can i relock my bootloader after?
Can i restore my TA partion after?
where is the batch file???
I think you can find the batch file in the guide2.rar file.
Is this an unlocked 5.0.2 boot loader or is it from a previous version?
What about rooting the phone, is it enough to have supersu installed?
Unlocked
Yes you can re lock
yes you can restore TA
CLINTZ9 said:
Yes you can re lock
yes you can restore TA
Click to expand...
Click to collapse
Thx
are you testing? no brick?
The FTF is 5.0.2 stock kernel
m!k3 said:
Thx
are you testing? no brick?
Click to expand...
Click to collapse
Yes I Am
TA Restore is also possible
CLINTZ9 said:
Unlocked
Click to expand...
Click to collapse
Ok, and what about root, supersu or more to install?
Device Will be rooted with super su installed
CLINTZ9 said:
Device Will be rooted with super su installed
Click to expand...
Click to collapse
My phone stuck in sony logo after flash kernel ftf
restore phone by flashtool... no root, no ta, sony compagnion
I have playing for about 3 hours to root lolipop without any luck on locked bootloader, selinux seems very restrictive on this Supersu unable to loc su binary, wft?
munjeni said:
I have playing for about 3 hours to root lolipop without any luck on locked bootloader, selinux seems very restrictive on this Supersu unable to loc su binary, wft?
Click to expand...
Click to collapse
So why not give it try to unlock before rooting?
munjeni said:
I have playing for about 3 hours to root lolipop without any luck on locked bootloader, selinux seems very restrictive on this Supersu unable to loc su binary, wft?
Click to expand...
Click to collapse
Yes It is . For now the only solution is a pre rooted fw
m!k3 said:
My phone stuck in sony logo after flash kernel ftf
restore phone by flashtool... no root, no ta, sony compagnion
Click to expand...
Click to collapse
I did it again seems to work fine
Make sure you put the ftf in the firmware folder of flashtool
CLINTZ9 said:
I did it again seems to work fine
Make sure you put the ftf in the firmware folder of flashtool
Click to expand...
Click to collapse
Backup TA partition
Unlock bootloader
flash last lollipop by flashtool
Flash kernel kitkat via flashtool in hotboot mode (fastboot option for flash) (provide by you)
when phone reboot, push volume - when led flash
flash superuser (or nut's dual recovery) by recovery after choose fix su before reboot
hard reboot phone (power + vol +)
clean your phone
relock bootloader
reflash TA partition
all file for root or dual recovery here : https://mega.co.nz/#!ZdARCSIB!p1bSDiYls1cwIve-qC4qdxuXYU0Ilt9pMJPL_z7-qhA
all work fine but not flash boot.img by fastboot directly
you can provide this in your first thread
CLINTZ9 said:
Step0 Extract These https://www.dropbox.com/s/3w4s95zonkzstfp/Guide.zip?dl=0
https://www.dropbox.com/s/i2zewkiles047jb/Guide2.rar?dl=0 Files To A Folder
Step1 Place The SuperSu zip to your SD card
Step2 Boot To Fastboot Mode And Click On The Batch File(It Will Install The Kernel With Recovery)Or Flash Kernel In Flashtool
Step3 Reboot Phone Press Volume down While Booting you will boot into twrp Flash SuperSu zip and go to advanced Tab and reboot to bootloader(Warning Your Phone Wont Boot Into System)
Step4 Open Flashtool And Flash The FTF Attached
Step5 Your Rooted
PS:All Files Provided Are Not Mine They Are The Work Of The Respective Developers
Also I Am Not Responsible For Bricked Devices
Click to expand...
Click to collapse
I thought you could only flash
.ftf with flash mode. I'm stuck at final step,because it says reboot to bootloader, then flash .ftf. Sorry if I'm missing something. Thanks
munjeni said:
I have playing for about 3 hours to root lolipop without any luck on locked bootloader, selinux seems very restrictive on this Supersu unable to loc su binary, wft?
Click to expand...
Click to collapse
dear master, I'm not a developer maybe this will help you to bypass SELinux
http://forum.xda-developers.com/showpost.php?p=59879026&postcount=3837
There are quite a few threads that have all the information but for new Z3TC owners, it can be challenging to know where to start and to understand the process.
How I started here is recently purchasing a Rogers Z3TC and to my surprise, the bootloader cannot be unlocked. I shouldn't have been surprised since carriers do tend to lock the bootloaders and if I did my research, I would have found out that Sony offers unlockable and non-unlockable versions of the same hardware. I have never had to worry about having a recovery to root the device or install custom ROMs with root. For anyone new to Android, the recovery is probably the single most important mode to setting up your device the way you want. A prerequisite for that is of course an unlocked bootloader so you can install the recovery of your choice - ClockworkMod (CWM) or TeamWin Recovery Project (TWRP).
So what makes the process confusing for some new Z3TC owners, such as myself, is that the process is somewhat backward. For most of my previous devices, it is:
1. Unlock bootloader
2. Install recovery
3. Gain root through flashing SuperSU or a rooted custom ROM
Because for my Rogers Z3TC cannot be bootloader unlocked, the process now looks like this:
1. Obtain root
2. Install recovery
3. Flash a pre-rooted Lollipop ROM
The only way we can get root on Lollipop is on a pre-rooted ROM because there is no exploit yet to do it directly. The only way we can install a pre-rooted ROM is through a custom recovery. The only way we can get a custom recovery is to be rooted. For unlocked bootloaders, they can get recovery through flashing the img of the recovery. The only way we can obtain root is through an exploit on a Z3 ROM, which thankfully works on the Z3TC due to the similar hardware.
So without quoting all the instructions of each step, I will provide the links and you just have to follow the instructions for each part.
Before you begin, you will need Flashtool and install the drivers for Flashmode and your device. You will not need Fastboot because unfortunately, you wont be doing anything with it on a locked bootloader. You may install it if you want.
If you are on Windows 8.1/10, you will need to to disable driver signature.
1. Obtain root by first flashing SGP621_23.0.1.A.0.167_CE.ftf and the system partition of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf. Then use giefroot to root.
2. Prepare prerooted flashable zip of 23.1.A.0.690 NOBA on your internal storage or external SD.
3. Install XZDualRecovery and now you will have TWRP to install 23.1.A.0.690 NOBA on your SD card.
I would finish off by running SGP621-RICDefeat.zip to get R/W system access.
This is the simple template that I would imagine be the way those of us with locked bootloaders will install custom ROMs, obtain root or upgrade Android.
Thank you @lowtraxx for the root instructions and @[NUT] for the XZDualRecovery.
I am running stock Lollipop now.
If I take above mentioned steps,
do I lose the data with apps and settings I am using now?
ux50jp said:
I am running stock Lollipop now.
If I take above mentioned steps,
do I lose the data with apps and settings I am using now?
Click to expand...
Click to collapse
I have tried downgrading from Lollipop back to step one without wipe in Flashtool but I think the system data are incompatible and caused bootloop.
Once I flashed a fresh SGP621_23.0.1.A.0.167_CE.ftf, I did not bother setting up any apps until I did a fresh install of the pre-rooted Lollipop ROM. If you can back up everything first, that would be best. If you cannot, try Flashtool without wipe and worst case scenario if you bootloop, there is a shut off button beside the SIM card tray and you can still get back into Flashmode.
hellocng said:
I have tried downgrading from Lollipop back to step one without wipe in Flashtool but I think the system data are incompatible and caused bootloop.
Once I flashed a fresh SGP621_23.0.1.A.0.167_CE.ftf, I did not bother setting up any apps until I did a fresh install of the pre-rooted Lollipop ROM. If you can back up everything first, that would be best. If you cannot, try Flashtool without wipe and worst case scenario if you bootloop, there is a shut off button beside the SIM card tray and you can still get back into Flashmode.
Click to expand...
Click to collapse
If someone could do a tutorial video, I think a lot of people along with myself would highly appreciate it. I tried doing root on locked bootloader prior to Lollipop, but it just wasn't happening for me. So I decided to give up and just update it since it was too much of a hassle.
Thanks for the post.
Has anyone else tried this?
I am wondering why the root method previously need to unlock the bootloader to get the 621 firmware back on an rooted.
What has changed for this to work without unlocking the bootloader?
Thanks in advance
hellocng said:
1. Obtain root by first flashing SGP621_23.0.1.A.0.167_CE.ftf and the system partition of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf. Then use giefroot to root.
2. Prepare prerooted flashable zip of 23.1.A.0.690 NOBA on your internal storage or external SD.
3. Install XZDualRecovery and now you will have TWRP to install 23.1.A.0.690 NOBA on your SD card.
I would finish off by running SGP621-RICDefeat.zip to get R/W system access.
This is the simple template that I would imagine be the way those of us with locked bootloaders will install custom ROMs, obtain root or upgrade Android.
Thank you @lowtraxx for the root instructions and @[NUT] for the XZDualRecovery.
Click to expand...
Click to collapse
Will I lose my drm keys by doing this? I want to get root but dont wanna unlock my bootloader
Jiyeon90 said:
Will I lose my drm keys by doing this? I want to get root but dont wanna unlock my bootloader
Click to expand...
Click to collapse
yes if you don't follow this steps
1- flash stock 4.4.4 with flashtool
2-flash the 4.4.4 Z3 system only" with flastool
3-factory reset in settings enable usb debuging etc,etc
4-obtain root with giefroot
5-backup TA partition
6-unlock boot loader
7-install dual recovery
8-flash prerooted 5.0.2 with custom recovery
9- gain get system R/W access with ricdefeat
10-relock boot loader restoring TA
good luck
Jiyeon90 said:
Will I lose my drm keys by doing this? I want to get root but dont wanna unlock my bootloader
Click to expand...
Click to collapse
No, we cannot unlock our bootloader so we will not lose DRM.
Speedy Gonzalez said:
yes if you don't follow this steps
1- flash stock 4.4.4 with flashtool
2-flash the 4.4.4 Z3 system only" with flastool
3-factory reset in settings enable usb debuging etc,etc
4-obtain root with giefroot
5-backup TA partition
6-unlock boot loader
7-install dual recovery
8-flash prerooted 5.0.2 with custom recovery
9- gain get system R/W access with ricdefeat
10-relock boot loader restoring TA
good luck
Click to expand...
Click to collapse
Step 3 and 5 is not necessary because we cant do step 6.
hellocng said:
No, we cannot unlock our bootloader so we will not lose DRM.
Step 3 and 5 is not necessary because we cant do step 6.
Click to expand...
Click to collapse
what do you mean with we can't ? you don't want to ?
Never mind I didn't knew you CAN'T unlock the bootloader at all
1. Obtain root by first flashing SGP621_23.0.1.A.0.167_CE.ftf and the system partition of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf. Then use giefroot to root.
2. Prepare prerooted flashable zip of 23.1.A.0.690 NOBA on your internal storage or external SD.
3. Install XZDualRecovery and now you will have TWRP to install 23.1.A.0.690 NOBA on your SD card.
I would finish off by running SGP621-RICDefeat.zip to get R/W system access.
Click to expand...
Click to collapse
These steps don't unlock bootloader. So DRM stays intact. No need to backup/restore TA!!!
hellocng said:
No, we cannot unlock our bootloader so we will not lose DRM.
Step 3 and 5 is not necessary because we cant do step 6.
Click to expand...
Click to collapse
So I can get root even if I skip step 3, 5, and 6?
Jiyeon90 said:
So I can get root even if I skip step 3, 5, and 6?
Click to expand...
Click to collapse
Yes.
Thank you, its working now, yeah no need to backup TA, unlock bootloader, etc.
It was a bit tricky but not as hard as in the other threads.
I did one mistake, I flashed the SGP621 pre-rooted zip on my SGP611, it wouldnt turn on obviously, so I created a pre-rooted file for the SGP611 and now I'm on lollipop with root and dual recovery
Flashing the ricdefeat file fails everytime though but thats a very minor issue.
Here's the pre-rooted file for the SGP611 users
https://drive.google.com/file/d/0Bz4ANHmLVuVTR2FqWHEzemxORjg/view?usp=sharing
It seems really hard to brick the device too, I ran out of space on my pc while flashing 4.4.4 with flashtool so the processes was aborted at about 50% but I was still able to get into flash mode again.
Jiyeon90 said:
Thank you, its working now, yeah no need to backup TA, unlock bootloader, etc.
It was a bit tricky but not as hard as in the other threads.
I did one mistake, I flashed the SGP621 pre-rooted zip on my SGP611, it wouldnt turn on obviously, so I created a pre-rooted file for the SGP611 and now I'm on lollipop with root and dual recovery
Flashing the ricdefeat file fails everytime though but thats a very minor issue.
Here's the pre-rooted file for the SGP611 users
https://drive.google.com/file/d/0Bz4ANHmLVuVTR2FqWHEzemxORjg/view?usp=sharing
It seems really hard to brick the device too, I ran out of space on my pc while flashing 4.4.4 with flashtool so the processes was aborted at about 50% but I was still able to get into flash mode again.
Click to expand...
Click to collapse
Could that prerooted 611 file work on my lollipop 612? Or would it need 612 specifically to work?
Thanks
GigaSPX said:
Could that prerooted 611 file work on my lollipop 612? Or would it need 612 specifically to work?
Thanks
Click to expand...
Click to collapse
I'm not sure, you could give it a try.
Or just make a pre-rooted file yourself, it's quite easy, just remember to use the right lollipop .FTF file for your 612 device.
Jiyeon90 said:
I'm not sure, you could give it a try.
Or just make a pre-rooted file yourself, it's quite easy, just remember to use the right lollipop .FTF file for your 612 device.
Click to expand...
Click to collapse
Just follow the same instructions from the first post?
GigaSPX said:
Just follow the same instructions from the first post?
Click to expand...
Click to collapse
Yes, what I did was.
Downgrade to 4.4.4 using flashtool, if you are on 611 or 612 dont use the ftf file in the first post as your device wont turn on, use the correct ftf file for your device.
Flash z3 compact system using flashtool (dont wipe anything and exclude everything but system, you will end up with with the z3 system and you will get error messages when you turn it on, thats fine)
Root using giefrrot (it took me 3 tries to get it rooted)
Install double recovery.
Put the pre-rooted file in your phone memory or sd card.
Flash the pre-rooted lollipop file and reboot, thats all.
But as you have the 612 device I would recommend you to make your own pre-rooted file, just follow these instructions
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
Jiyeon90 said:
Flashing the ricdefeat file fails everytime though but thats a very minor issue.
It seems really hard to brick the device too, I ran out of space on my pc while flashing 4.4.4 with flashtool so the processes was aborted at about 50% but I was still able to get into flash mode again.
Click to expand...
Click to collapse
The RICDefeat is quite important if you want to remove bloatware or alter the system in anyway, which is one of my prime reasons for rooting. What was the error or message?
Flash mode is intact as long as the bootloader is locked as we cannot modify any of the kernel or boot partitions.
Jiyeon90 said:
Yes, what I did was.
Downgrade to 4.4.4 using flashtool, if you are on 611 or 612 dont use the ftf file in the first post as your device wont turn on, use the correct ftf file for your device.
Flash z3 compact system using flashtool (dont wipe anything and exclude everything but system, you will end up with with the z3 system and you will get error messages when you turn it on, thats fine)
Root using giefrrot (it took me 3 tries to get it rooted)
Install double recovery.
Put the pre-rooted file in your phone memory or sd card.
Flash the pre-rooted lollipop file and reboot, thats all.
But as you have the 612 device I would recommend you to make your own pre-rooted file, just follow these instructions
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
Click to expand...
Click to collapse
I want to personally thank you for the instructions. I'm now running perfectly as is prerooted Lollipop SGP612. It took me several tries too with the rooting with giefroot because each time I run it, I can't get it connected to USB anymore, which I had to constantly restart to get.
hellocng said:
The RICDefeat is quite important if you want to remove bloatware or alter the system in anyway, which is one of my prime reasons for rooting. What was the error or message?
Flash mode is intact as long as the bootloader is locked as we cannot modify any of the kernel or boot partitions.
Click to expand...
Click to collapse
I don't remember what error message I got, all I remember is seeing the word 'aborted' with the green Android guy laying down.
I have removed several apps that came pre-installed using titanium backup, I also installed the SD card fix so I can use the SD card freely. I haven't had a single issue so far.
---------- Post added at 12:03 AM ---------- Previous post was at 12:03 AM ----------
GigaSPX said:
I want to personally thank you for the instructions. I'm now running perfectly as is prerooted Lollipop SGP612. It took me several tries too with the rooting with giefroot because each time I run it, I can't get it connected to USB anymore, which I had to constantly restart to get.
Click to expand...
Click to collapse
No problem, glad I could help [emoji2]
The hot new security update is live, and you maybe want some root love without flashing custom kernel.
(Stock Image here : https://developers.google.com/android/nexus/images#volantis)
Handy modified root compatible boot image for the latest stock image MRA58N. Pure stock kernel modified from the stock images.
You have two choices:
The traditional root in system, which breaks OTA functionality.
(It's more stable now)
New "systemless" approach, which means the root stuffs are only in DATA and BOOT, the system will stay intact and it will accept OTAs.
(Note that this method is still in beta stage according to CF)
Instructions:
System:
Unzip system-root.zip, flash the boot.img through fastboot
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the one above), if you've rooted with other methods, please re-flash your system back to pure stock
Unzip systemless-root.zip, flash the boot.img through fastboot
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
When a new OTA appears I can just apply it and it will work? Do I keep root or do I have to reroot it again?
Are the attached zip files for the wifi model only?
I have this Kernel:
3.10.40-g909db78
[email protected] #1
Fri Aug 28 21:16:30 UTC 2015
Is this a stock one?
And with method shall I use to get rooted MRA58N?
Jeltel said:
When a new OTA appears I can just apply it and it will work? Do I keep root or do I have to reroot it again?
Click to expand...
Click to collapse
You can revert to stock boot and stock recovery to apply OTA
corkiejp said:
Are the attached zip files for the wifi model only?
Click to expand...
Click to collapse
Yes, I can make a LTE compatible version though.
sejmand said:
I have this Kernel:
3.10.40-g909db78
[email protected] #1
Fri Aug 28 21:16:30 UTC 2015
Is this a stock one?
And with method shall I use to get rooted MRA58N?
Click to expand...
Click to collapse
Yes, and yes
topjohnwu said:
You can revert to stock boot and stock recovery to apply OTA
Yes, I can make a LTE compatible version though.
Yes, and yes
Click to expand...
Click to collapse
A LTE compatible version would be great!!!
topjohnwu said:
You can revert to stock boot and stock recovery to apply OTA
Click to expand...
Click to collapse
So that's a no
I flashed factory image MRA58N (system gets encrypted, because it wasn't under MRA58K)
then twrp
then systemless-root (boot.img)
then superuser 2.56.....
EVERYTHING WORKS FINE:
encrypted with root!
how to flash boot.img (command for flashing)
topjohnwu said:
The hot new security update is live, and you maybe want some root love without flashing custom kernel.
(Stock Image here : https://developers.google.com/android/nexus/images#volantis)
Handy modified root compatible boot image for the latest stock image MRA58N. Pure stock kernel modified from the stock images.
You have two choices:
The traditional root in system, which breaks OTA functionality.
(It's more stable now)
New "systemless" approach, which means the root stuffs are only in DATA and BOOT, the system will stay intact and it will accept OTAs.
(Note that this method is still in beta stage according to CF)
Instructions:
System:
Unzip system-root.zip, flash the boot.img through fastboot
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the one above), if you've rooted with other methods, please re-flash your system back to pure stock
Unzip systemless-root.zip, flash the boot.img through fastboot
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
Click to expand...
Click to collapse
how to flash boot.img for system less (partition ?)
Lightnyboy said:
how to flash boot.img for system less (partition ?)
Click to expand...
Click to collapse
Unzip systemless-root.zip which will give you a "boot.img" file.
Then while in fastboot
"fastboot flash boot boot.img"
Anyone have the boot files for LTE yet?
Nice. Could you add the link to CF original post in systemless root.
thebrainkafka said:
Nice. Could you add the link to CF original post in systemless root.
Click to expand...
Click to collapse
topjohnwu said:
[*]Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
[*]Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
Click to expand...
Click to collapse
Already linked? Click on "this thread" above!
Updated for LTE... Sorry for the late update.
Also looks like rovo89 just put up xposed for marshmallow in his xposed for lollipop thread. Yes!
xposed marshmallow
topjohnwu said:
Updated for LTE... Sorry for the late update.
Click to expand...
Click to collapse
Thanks for the modified boot images for LTE, I linked back here from my thread in Q&A forum.
have problems getting it to work...
am on MRA58N stock.
My exact steps.
adb reboot bootloader
Device reboots to bootloader.
fastboot flash boot boot.img (extracted from volantisg-mra58n-boot-systemless.zip)
fastboot boot twrp.img (extracted from https://dl.twrp.me/flounder/twrp-2.8.7.1-flounder.img)
From here, I manage to get into TWRP but they are asking for a PIN. I had to cancel and mounted an external USB storage and manage to flash SuperSU-v2.56-20151030013730.zip successfully. Rebooting after and not installing the the SuperSU that TWRP prompts.
After rebooting, I still don't have root. What did I do wrong?
madbat99 said:
Also looks like rovo89 just put up xposed for marshmallow in his xposed for lollipop thread. Yes!
xposed marshmallow
Click to expand...
Click to collapse
I haven't run N version yet as my N9 is finally working without lags/reboots. But, the lure of the close all recent apps button (and very successful experience with xposed/gravity box on N5 after a year) in GB was too great. It works beautifully!
This may seem off-topic, but since root is required, maybe readers can allow exception.
Sent from my Nexus 9 using Tapatalk
chesterchen said:
have problems getting it to work...
am on MRA58N stock.
My exact steps.
adb reboot bootloader
Device reboots to bootloader.
fastboot flash boot boot.img (extracted from volantisg-mra58n-boot-systemless.zip)
fastboot boot twrp.img (extracted from https://dl.twrp.me/flounder/twrp-2.8.7.1-flounder.img)
From here, I manage to get into TWRP but they are asking for a PIN. I had to cancel and mounted an external USB storage and manage to flash SuperSU-v2.56-20151030013730.zip successfully. Rebooting after and not installing the the SuperSU that TWRP prompts.
After rebooting, I still don't have root. What did I do wrong?
Click to expand...
Click to collapse
You don't need to extract twrp.img, you should flash the full image "twrp-2.8.7.1-flounder.img".
That version should not ask for PIN anymore.
Note: system-less is still experimental
If I want to switch from the systemless root to regular system modified root, are there specific cleanup actions to take?
Thanks!
maximumentropy said:
If I want to switch from the systemless root to regular system modified root, are there specific cleanup actions to take?
Thanks!
Click to expand...
Click to collapse
Reflash the stock image then you're good
Follow at your own risk, I take no responsibility. This guide is for any stock(seems to work with mods) rom. I used TWRP RC1, but could possibly work with alpha 2(for adb sideload only). Not sure if this method is "better" than using flash-all.bat without -w, but the file download was smaller.
Required Files and Locations they should be placed:
TWRP RC1 Image placed in the same folder as your FASTBOOT executable
TWRP RC1 zip installer placed on phones internal storage
SuperSU 2.79 SR3 zip installer placed on phones internal storage
NOF27B or NOF27C - Rogers OTA placed in the same folder as your ADB executable
Ensure the TWRP and SuperSU zip installers are loaded onto the phones internal storage and the OTA zip and TWRP image are in the ADB/FASTBOOT executables folder.
Boot into current TWRP recovery
Make a full backup in TWRP
Connect the phone to the computer
In TWRP select the Advanced menu, click ADB sideload option
On the computer open a command window and navigate to the location of your ADB executable/OTA zip
Only execute one adb sideload command for your specific device
Execute the following command(Non-Rogers): adb sideload sailfish-ota-nof27b-8130b5a8.zip
Execute the following command(Rogers): adb sideload sailfish-ota-nof27c-fb487658.zip
Only execute one adb sideload command for your specific device
The command window should be displaying a percentage and the TWRP should be displaying the standard OTA step 1 and 2 - Let this complete
Click Reboot System and let the OTA finish installing
At this point TWRP and Root are gone, but can be restored
With the device powered off, hold volume down and turn on the device. Your device should now be in the bootloader.
With the device connected to the computer run the following command from the previous step's command window: fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
Install twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip in TWRP
Install SR3-SuperSU-v2.79-SR3-20170114223742.zip in TWRP
Click Reboot System
Install Kernel/Mods
Remember to restore any /system specific edits such as the tether build.prop edit, host file edits, or custom boot animations.
This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed
bush911 said:
This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed
Click to expand...
Click to collapse
Just remove the -w argument from the flash-all.bat and flash the factory image...
Thank you dude, so what's the difference between full factory image and full ota zip, and ota automatically downloaded to phone.
the factory image is around 1.8 G and full ota zip is around 800 M, but the ota automatically downloaded to phone is only 47 M
Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse
I had good luck with this method getting to NMF26O. Just a couple of things to note. Make sure you have the latest ADB files, and while it probably is assumed that you are using TWRP RC1 I'm pretty sure this did not work in Alpha2. Also, when the OP mentions losing TWRP it actually completely removes recovery so don't freak out if you try to boot into it expecting stock recovery and get a no data (or something like that if I remember correctly) error. There is no reason to check, but last time I was curious to see if it would leave TWRP in place. All is fine as long as you can get to bootloader. One other thing is the fact that this is an OTA. I would not do this unless coming from NMF26O but that is just me.
I am in no hurry to do this update since by all accounts it adds no functionality, but I was going to try it this way again. I wonder if anyone has any reason other than habit to continue to use the flash all method.
Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse
so should we sideload the OTA over Q or download the factory image and remove the -w flag and run flash all.bat?
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
This is only for updating stock. If you want of weta then use the full image and remove the -w from the flashall bat file.
thank you! worked great!
quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
Because I'm groovy like that... (And had a nandroid backup) I went ahead and took the jump of sideloading the OTA update over weta 2.2.1. Personally, I wasn't too concerned about botching up the system, as the weta ROM is going away. Instead the author is now compiling his mod(s) to layer over this stock build. I'm assuming that the OTA sideload went without a hitch because weta is designed around the stock image. Of course, I had to install some of my mod's again that were lost in the "update"
**DISCLAIMER**
I'm not claiming or declaring the OTA update is safe to install over weta 2.2.1. I'm only giving my experience so others can weigh out the risks for themselves, if they decide to roll the dice. :silly:
I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay
rohitece06 said:
I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay
Click to expand...
Click to collapse
I don't use Pay, but did you update to the latest Elemental kernel 1.03?
spiller37 said:
I don't use Pay, but did you update to the latest Elemental kernel 1.03?
Click to expand...
Click to collapse
Yes I did.
rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
Try Franco's, his is patched for pay. Just to try and narrow it down here.
rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
You might also try the patched stock kernel that was just updated.
spiller37 said:
You might also try the patched stock kernel that was just updated.
Click to expand...
Click to collapse
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.
Is something up with the OP or is it just my XDA app causing it to show like this..
aholeinthewor1d said:
Is something up with the OP or is it just my XDA app causing it to show like this..
Click to expand...
Click to collapse
Not sure why it displays this way in the two XDA apps. If anyone knows how to fix the formatting I would be grateful for the solution.
rohitece06 said:
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.
Click to expand...
Click to collapse
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.
spiller37 said:
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.
Click to expand...
Click to collapse
it was working before this January pixel update