Database Develop

HOW TO : Flash 4.3 on rooted stock 4.2.2

If you have a stock 4.2.2 with root and clockwork mod recovery, it can be updated to 4.3, you will keep CWM recovery but lose root so here's what I did.
You need :
- Nexus 4
- 4.2.2 firmware (JDQ39)
- root with superSU
- Clockwork Mod Recovery
Download update JWR66V from JDQ39
Copy the zip file in the folder of your choice.
Shut down the Nexus 4
Boot into CWM Recovery : hold Volume Down and press Power, in the menu with the green "Start" choose "Recovery mode" with the volume and select with power, it will reboot in CWM Recovery
Then in CWM Recovery :
- Install Zip
- Choose zip from sdcard
- 0/
- go in the folder you copied the update and select it
- select Yes and wait
- go back and reboot
- on reboot it will ask to keep recovery and root, say Yes both. But saying no to keep root won't keep root...
So after a long reboot, the Nexus 4 is updated to 4.3, CWM recovery still here but no root binary.
Download the file on this link from SuperSU creator : Chainfire.
Flash it the same way as the update but when it will ask for keeping recovery, say No.
After reboot, you now have a Nexus 4 with 4.3 (JWR66V), root and CWM recovery.
On Google Play, SuperSU is updated, currently version 1.44. When launching SuperSU, it will ask to update SU Binary, choose to update normally.
This should work with TWRP but I don't have it.
I hope this will help.

I want to do a fresh install using the factory images for 4.3 (bootloader, radio, recovery etc)
Once I do that, can I just reinstall CWM then SuperSu to root just like I did using 4.2?

ohhdavid said:
I want to do a fresh install using the factory images for 4.3 (bootloader, radio, recovery etc)
Once I do that, can I just reinstall CWM then SuperSu to root just like I did using 4.2?
Click to expand...
Click to collapse
just use the nexus4 tool kit and use the factory images. Simple and quick

jboogie3 said:
just use the nexus4 tool kit and use the factory images. Simple and quick
Click to expand...
Click to collapse
I'll look into it, however, I usually prefer to do as close to stock install as possible with bare minimum 3rd party modification which is why I usually install factory images and then flash Su through cwm
Sent from my Nexus 4

ohhdavid said:
I'll look into it, however, I usually prefer to do as close to stock install as possible with bare minimum 3rd party modification which is why I usually install factory images and then flash Su through cwm
Sent from my Nexus 4
Click to expand...
Click to collapse
the toolkit just fastboot flashes the images for you... thats complete stock. then you can flash a custom recovery, then install su.

Thanks to the OP :thumbup: works a treat
Sent from my Nexus 4 using xda app-developers app

Le_Zouave said:
If you have a stock 4.2.2 with root and clockwork mod recovery, it can be updated to 4.3, you will keep CWM recovery but lose root so here's what I did.
You need :
- Nexus 4
- 4.2.2 firmware (JDQ39)
- root with superSU
- Clockwork Mod Recovery
Download update JWR66V from JDQ39
Copy the zip file in the folder of your choice.
Shut down the Nexus 4
Boot into CWM Recovery : hold Volume Down and press Power, in the menu with the green "Start" choose "Recovery mode" with the volume and select with power, it will reboot in CWM Recovery
Then in CWM Recovery :
- Install Zip
- Choose zip from sdcard
- 0/
- go in the folder you copied the update and select it
- select Yes and wait
- go back and reboot
- on reboot it will ask to keep recovery and root, say Yes both. But saying no to keep root won't keep root...
So after a long reboot, the Nexus 4 is updated to 4.3, CWM recovery still here but no root binary.
Download the file on this link from SuperSU creator : Chainfire.
Flash it the same way as the update but when it will ask for keeping recovery, say No.
After reboot, you now have a Nexus 4 with 4.3 (JWR66V), root and CWM recovery.
This should work with TWRP but I don't have it.
I hope this will help.
Click to expand...
Click to collapse
Awesome thanks, will try this later.

does this method erase everything on your phone?

clusterchuck said:
does this method erase everything on your phone?
Click to expand...
Click to collapse
No, nothing is erased and it even keep the custom recovery.
The first part is what I used to update to 4.2.2 and keep root and custom recovery. But with 4.3 update, root method seems to have changed, that's why I wrote this post.

Le_Zouave said:
If you have a stock 4.2.2 with root and clockwork mod recovery, it can be updated to 4.3, you will keep CWM recovery but lose root so here's what I did.
You need :
- Nexus 4
- 4.2.2 firmware (JDQ39)
- root with superSU
- Clockwork Mod Recovery
Download update JWR66V from JDQ39
Copy the zip file in the folder of your choice.
Shut down the Nexus 4
Boot into CWM Recovery : hold Volume Down and press Power, in the menu with the green "Start" choose "Recovery mode" with the volume and select with power, it will reboot in CWM Recovery
Then in CWM Recovery :
- Install Zip
- Choose zip from sdcard
- 0/
- go in the folder you copied the update and select it
- select Yes and wait
- go back and reboot
- on reboot it will ask to keep recovery and root, say Yes both. But saying no to keep root won't keep root...
So after a long reboot, the Nexus 4 is updated to 4.3, CWM recovery still here but no root binary.
Download the file on this link from SuperSU creator : Chainfire.
Flash it the same way as the update but when it will ask for keeping recovery, say No.
After reboot, you now have a Nexus 4 with 4.3 (JWR66V), root and CWM recovery.
This should work with TWRP but I don't have it.
I hope this will help.
Click to expand...
Click to collapse
There's a new su zip v1.43 it had just been released
From my BLACKED OUT N4

i got an error when attempting to install in cwm, something regarding a no file_context.
edit: it says error /sdcard/0/ ebc... (status 7)

Worked fine for me
Thanks! This worked perfectly for me. Haven't run into any trouble yet.

I missed "Flash it the same way as the update but when it will ask for keeping recovery, say No" before, now it works fine on my N4

Works fine on TWRP. Updater asks if we want to save root. I said, No. Nothing is asked or said about recovery but recovery (TWRP) is retained. After the update, I went back to recovery and flashed the recent 1.43 update from Chainfire. All went well. Soon thereafter, I was notified that SuperSU is now at version 1.44.
Everything is smooth so far.... One app that works with root is goofy now, but other than that, all is well.

Can someone tell me if using the first part of my method to keep the recovery (so not flashing Chainfire file) and updating to SuperSU 1.44 on google play is enough to get back root?
In my case I updated to SuperSU 1.44 and when I launched it, that asked me to update SU binary and choose between normal or CWM/TRWP method, I choose normal and it worked.
clusterchuck, I get that error too but it didn't blocked and all went fine. Is it a blocking error?

Le_Zouave said:
Can someone tell me if using the first part of my method to keep the recovery (so not flashing Chainfire file) and updating to SuperSU 1.44 on google play is enough to get back root?
In my case I updated to SuperSU 1.44 and when I launched it, that asked me to update SU binary and choose between normal or CWM/TRWP method, I choose normal and it worked.
clusterchuck, I get that error too but it didn't blocked and all went fine. Is it a blocking error?
Click to expand...
Click to collapse
as far as the "no context", i dont think its a blocking error, because once I got the update working, it still has that error message on there. But it turned out my problem was that I deleted some google apps (google plus, earth, etc), and i had completely forget about that. So i ended up having to flash the stock 4.2.2 again then installing 4.3 for it to all go smoothly.

Great , thanks for the post, I will check that this weekend.

Update error
I did some previous flashing with Google Edition camera apk's and whatnot but I believe I should have the stock camera/GoogleGallery.apk.
I perform the steps and it gives me a Status 7 error, with "GoogleGallery.apk" somewhere in there. So I flash the stock 4.2.2 google apps and try again, this time it gives me a BrowserProviderProxy.apk error, Status 7 as well.
Any help on this?

Perhaps your system apps have been modified before or your kernel have been flashed before. Safest method will be to use fastboot to upgrade.
clusterchuck said:
i got an error when attempting to install in cwm, something regarding a no file_context.
edit: it says error /sdcard/0/ ebc... (status 7)
Click to expand...
Click to collapse

Is it also working when coming from a custom kernel (e.g. franco)?

[Q] Can Root Sony Xperia Z1 on 4.4.2(Kitkat)

Can I root z1 on kitkat??anyone can help me?

Yes,
First, ask QUESTIONS in the Question and answer section.
Now, read the several guides in the general and/or development section on how to root.
In brief
Either, unlock your bootloader and flash an insecure kernel
or
flash stock 4.2, root, install recovery and flash a prerooted 4.4 rom.
Alll instructions are in their relevant threads so I will not reproduce them here.
Eigth time and counting I have written this today

Anyone can explain why there is not an straight forward method to root Z1 directly on kitKat and we need to downgrade to do it ?

SrMoure said:
Anyone can explain why there is not an straight forward method to root Z1 directly on kitKat and we need to downgrade to do it ?
Click to expand...
Click to collapse
Because sony has patched the known exploits and made it hard for the devs to find any expoit.

avveMeetU said:
Can I root z1 on kitkat??anyone can help me?
Click to expand...
Click to collapse
Best way to do is it to downgrade to 534 using flashtool, grab the FTF file needed from the mega collection thread.
Use vroot to root the device, install a custom recovery, flash the rom that you want to install (Monx, ihacker, romaur) then don't reboot, but re-enter flashmode and flash everything (without wipe) from an FTF of the same base, do not flash TA and System.
Reboot and youre done.
I wrote a more in depth tutorial which can be found in this thread, second post.
http://forum.xda-developers.com/showthread.php?t=2709585

dladz said:
Best way to do is it to downgrade to 534 using flashtool, grab the FTF file needed from the mega collection thread.
Use vroot to root the device, install a custom recovery, flash the rom that you want to install (Monx, ihacker, romaur) then don't reboot, but re-enter flashmode and flash everything (without wipe) from an FTF of the same base, do not flash TA and System.
Reboot and youre done.
I wrote a more in depth tutorial which can be found in this thread, second post.
http://forum.xda-developers.com/showthread.php?t=2709585
Click to expand...
Click to collapse
No that's not the best way
1) Vroot sends your IMEI number to china for no known reason. They have been asked to change this but gave no response to XDA about it.
2) The point of downgrading to a .534 FTF is that you can install recovery without rooting first. So install dualrecovery, then flash SuperSU.zip from chainfire, then flash a 4.4 rom of your choice.

avveMeetU said:
Can I root z1 on kitkat??anyone can help me?
Click to expand...
Click to collapse
It's real easy to relock the bootloader using Flashtool, so don't sweat unlocking it to root.

KarimSalloum said:
It's real easy to relock the bootloader using Flashtool, so don't sweat unlocking it to root.
Click to expand...
Click to collapse
But how do you backup your TA that way.
You need to root first then backup TA. Relocking with flashtool does not restore your TA.
Once you have your backup then that is always possible, but not for a first time root.

gregbradley said:
No that's not the best way
1) Vroot sends your IMEI number to china for no known reason. They have been asked to change this but gave no response to XDA about it.
2) The point of downgrading to a .534 FTF is that you can install recovery without rooting first. So install dualrecovery, then flash SuperSU.zip from chainfire, then flash a 4.4 rom of your choice.
Click to expand...
Click to collapse
I didn't know you could do it that way, the way that i've mentioned is what was written on all the tutorials that i've seen so i'm literally going from what other people have said, including monx.
The IMEI thing is a bit creepy but I wasn't aware of that either.

another one bricked...sigh how to fix?
Hey all,
Successfully unlocked my c9603 with latest kitkat and installed cwm 6 with these instructions
How to Install CWM 6 Recovery on Xperia Z1:
Download Doomlord’s Advanced Stock Kernel with CWM Recovery
Copy the downloaded.zip file to your phone’s sd card.
Extract the downloaded .zip folder on your PC, you will get a Boot.img file.
Place the extracted Boot.img file in the Minimal ADB & Fastboot folder that you created using our ADB & Fastboot Quick Setup Guide.
If you are using Android ADB & Fastboot full package, you can place the downloaded Recovery.img file in the Fastboot folder or in the Platform-tools folder.
Open the folder where you placed the Boot.img file. E.g Minimal ADB & Fastbootor Fastboot or Platform Tools.
Press and hold the shift key and right click on an empty area within the folder, and click on “Open Command Window Here”.
Turn off your Xperia Z1 completely.
Now press the Volume Up Key and while keeping it pressed plug in the USB cable.
You should see a blue light in the notification light of your phone, that means your device is now connected in Fastboot mode.
Now type the following command: Fastboot Flash boot Boot.img
Hit Enter and it will quickly flash CWM 6.0.4.6 recovery in your Xperia Z1
Once recovery is flashed, now issue this command “Fastboot Reboot”
Your device will reboot now, as soon as you see the Sony logo, and the pink LED, press Volume Up key to enter recovery.
Congrats! You should now see the custom recovery.
Once in CWM recovery, flash the zip file you copied to your phone in step 2. To do so, select “install zip > choose zip from sd card > doomlord advanced stock kernel.zip > yes” and flash it.
Once flashed the zip file, reboot your device.
That’s all.
ok so I did all of the with success now when I turn my phone on I get what I think is a bootloop mode...it gives me the sony logo and the pink led to boot in cwm then re loops over and over.
I can get into cwm but thats it.
So how do I go about fixing my bricked phone now? Kinda need it lol
appreciated guys

WOW, I misread that...
If you flash doomkernel you already have recovery.
Please link to where you found those instructions, they seem way out of date.
and have you unlocked your bootloader?

96329992 144
gregbradley said:
WOW, I misread that...
If you flash doomkernel you already have recovery.
Please link to where you found those instructions, they seem way out of date.
and have you unlocked your bootloader?
Click to expand...
Click to collapse
http://techbeasts.com/2014/02/19/in...ng-latest-14-2-a-1-136-firmware-how-to-guide/
thats the link I used.
and yes I unlocked the bootloader via adb and fastboot using this guide
http://techbeasts.com/2013/12/18/how-to-unlock-bootloader-of-sony-xperia-devices-guide/
and I think I just maybe spotted my mistake, I probably should hvae used this link instead but due to sleep deprivation I didnt
http://techbeasts.com/2014/03/20/install-cwm-6-recovery-xperia-z1-android-4-4-2-kitkat-681/
anyway I went ahead and download that boot.img file, renamed it copied it across and tried to flash and I get this error
error: cannot load 'boot.img': No error

antiskeptic said:
http://techbeasts.com/2014/02/19/in...ng-latest-14-2-a-1-136-firmware-how-to-guide/
thats the link I used.
and yes I unlocked the bootloader via adb and fastboot using this guide
http://techbeasts.com/2013/12/18/how-to-unlock-bootloader-of-sony-xperia-devices-guide/
and I think I just maybe spotted my mistake, I probably should hvae used this link instead but due to sleep deprivation I didnt
http://techbeasts.com/2014/03/20/install-cwm-6-recovery-xperia-z1-android-4-4-2-kitkat-681/
anyway I went ahead and download that boot.img file, renamed it copied it across and tried to flash and I get this error
error: cannot load 'boot.img': No error
Click to expand...
Click to collapse
Those non xda guides are crap...
If you have unlocked your bootloader (Did you make a TA backup first?) then just flash doomkernel
Doomkernel has recovery in it.
Once you have done that you are rooted and have recovery

gregbradley said:
Those non xda guides are crap...
If you have unlocked your bootloader (Did you make a TA backup first?) then just flash doomkernel
Doomkernel has recovery in it.
Once you have done that you are rooted and have recovery
Click to expand...
Click to collapse
No, I didnt back up the ta as I didnt have root in the first place.
I have doom kernal installed and can access cwm.
It is stuck in bootloop mode...how do I just get my phone to boot normally for now instead of bootlooping?
---------- Post added at 06:51 PM ---------- Previous post was at 06:39 PM ----------
i just tried all of this from xda university, still no luck at all, still boot looping
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.

antiskeptic said:
No, I didnt back up the ta as I didnt have root in the first place.
I have doom kernal installed and can access cwm.
It is stuck in bootloop mode...how do I just get my phone to boot normally for now instead of bootlooping?
---------- Post added at 06:51 PM ---------- Previous post was at 06:39 PM ----------
i just tried all of this from xda university, still no luck at all, still boot looping
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
Click to expand...
Click to collapse
Ok, flash SuperSU.zip from chainfires website (Google it)
Then flash a new rom of your choice.

gregbradley said:
Ok, flash SuperSU.zip from chainfires website (Google it)
Then flash a new rom of your choice.
Click to expand...
Click to collapse
Cool, ill get onto that. Ive noticed a cpl of roms floating around xda. Any suggestions on a good one or run with the
http://forum.xda-developers.com/showthread.php?t=2687275&page=8
option?
lol....might as well pick a good rom since i have stuffed my stock one.
I still will achieve my root! haha
thanks for the help so far, its always appreciated!

You do not need root to flash that.
Its a stock FTF, just flash it in flash tool

gregbradley said:
You do not need root to flash that.
Its a stock FTF, just flash it in flash tool
Click to expand...
Click to collapse
sorry I wasnt saying do i need root for this? i know i currently dont have root and can flash ftf anyway.
what i was saying was, once i have my phone back up, I will achieve root status on it...
so if I am correct flash the phone with supersu from sdcard via cwm6 then flash
[FTF] Xperia Z1 C6903 14.3.A.0.681 Commercial&Journalist
which I am downloading from http://forum.xda-developers.com/showthread.php?t=2687275
My phone should boot up now with root access, but I am only trying to fix it currently.
Cant see why I wouldnt have a working phone with root following these steps?
thanks , ill keep posting updates, might even help someone else in the process

But why are you insistent on backing up a system that is in bootloop? Why would you ever want to restore a bootlooping system?
I would just do a fresh system install and forget about backing up a non working system
Just flash the FTF of your choice, then the appropriate DooMKerneL version.
Then you are rooted and have CMW installed. 2 easy steps, I really don't understand your need to backup first, especially when your phone is bootlooping.
---------- Post added at 11:13 AM ---------- Previous post was at 11:07 AM ----------
antiskeptic said:
then flash
[FTF] Xperia Z1 C6903 14.3.A.0.681 Commercial&Journalist
which I am downloading from http://forum.xda-developers.com/showthread.php?t=2687275
My phone should boot up now with root access,
Click to expand...
Click to collapse
No, once you flash a FTF you lose root. You will need to reflash the appropriate DooMKerneL again
but I am only trying to fix it currently.
Cant see why I wouldnt have a working phone with root following these steps?
Click to expand...
Click to collapse
Because once you flash a FTF you lose root
thanks , ill keep posting updates, might even help someone else in the process
Click to expand...
Click to collapse

gregbradley said:
But why are you insistent on backing up a system that is in bootloop? Why would you ever want to restore a bootlooping system?
I would just do a fresh system install and forget about backing up a non working system
Just flash the FTF of your choice, then the appropriate DooMKerneL version.
Then you are rooted and have CMW installed. 2 easy steps, I really don't understand your need to backup first, especially when your phone is bootlooping.
---------- Post added at 11:13 AM ---------- Previous post was at 11:07 AM ----------
No, once you flash a FTF you lose root. You will need to reflash the appropriate DooMKerneL again Because once you flash a FTF you lose root
Click to expand...
Click to collapse
im not trying to backup the bootloop, i just want to fix my phone. I did not realise you were saying fresh install then start from scratch with the root process.
So I will flash the NEW ftf to my phone. Once phone is working I will flash doomlord kernel and supersu. thanks for the help. do you happen to know a link for the correct instructions for this, so I get it right this time.

[ROOT][SGP311][4.3] Update to 10.4.1.B.0.109 keeping Root + DualRecovery - Generic UK

Just a simple guide to update to the latest JB firmware (10.4.1.B.0.109) on locked bootloader. The customisation is Generic UK.
Please note that this is only compatible with the SGP311 model of the Tablet Z, and requires that you are already rooted with dual recovery.
Your tablet will NOT be wiped if this is performed correctly, but you are still strongly recommended to take a full backup INCLUDING INTERNAL SD.
Downloads:
http://dl.weeaboo.com/SGP311/sgp311-43-109-uk.flashable.zip
http://dl.weeaboo.com/SGP311/SGP311_10.4.1.B.0.109_Generic_uk-ie_stripped.ftf
http://download.chainfire.eu/supersu
Latest TabZ-lockeddualrecovery flashable zip from http://nut.xperia-files.com/
http://www.flashtool.net/download.php
Installation:
Put all zip files on external SD (must be FAT or FAT32 format)
Boot into TWRP (press vol down when LED turns green on boot)
Flash in this order: (DO NOT REBOOT BETWEEN)
sgp311-43-109-uk
TabZ-lockeddualrecovery
SuperSU
Go to Home -> Reboot -> Power Off
Using FlashTool, flash the stripped FTF (tick exclude UNKNOWN and untick all wipe)
You're done

thanks for this
i followed everything and its all upgraded now
i had a couple of squeaky bum moments as neither the recovery or supersu would flash
but i managed to sort that afterwards
thanks again
Sent from my SGP311 using Tapatalk

@Darkimmortal
Thanks for this!
Is there a way to change the Generic UK to a Generic US ftf but doing all of what is in your guide?
Thanks!

ndwgs said:
@Darkimmortal
Thanks for this!
Is there a way to change the Generic UK to a Generic US ftf but doing all of what is in your guide?
Thanks!
Click to expand...
Click to collapse
You have to create a flashable zip for it too

Darkimmortal said:
You have to create a flashable zip for it too
Click to expand...
Click to collapse
Create a flashable zip of the ftf file I is to create?
Isn't the ftf the only thing needed? A bit confused, sorry.

I have my xperia tab 311 all rooted and unlocked bootloader which I did a while back.
Now I forget what I used..... how do I know if I have dual recovery to use this update? apologies for the stupid question....

Darkimmortal said:
Just a simple guide to update to the latest JB firmware (10.4.1.B.0.109) on locked bootloader. The customisation is Generic UK.
Please note that this is only compatible with the SGP311 model of the Tablet Z, and requires that you are already rooted with dual recovery.
Your tablet will NOT be wiped if this is performed correctly, but you are still strongly recommended to take a full backup INCLUDING INTERNAL SD.
Downloads:
http://dl.weeaboo.com/SGP311/sgp311-43-109-uk.flashable.zip
http://dl.weeaboo.com/SGP311/SGP311_10.4.1.B.0.109_Generic_uk-ie_stripped.ftf
http://download.chainfire.eu/supersu
Latest TabZ-lockeddualrecovery flashable zip from http://nut.xperia-files.com/
http://www.flashtool.net/download.php
Installation:
Put all zip files on external SD (must be FAT or FAT32 format)
Boot into TWRP (press vol down when LED turns green on boot)
Flash in this order: (DO NOT REBOOT BETWEEN)
sgp311-43-109-uk
TabZ-lockeddualrecovery
SuperSU
Go to Home -> Reboot -> Power Off
Using FlashTool, flash the stripped FTF (tick exclude UNKNOWN and untick all wipe)
You're done
Click to expand...
Click to collapse
Ok I have done this, but I have lost TWRP , it doesn't show up anymore on pressing vol down at green LED, root is there but just cant get into TWRP.... any suggestions

Darkimmortal said:
You have to create a flashable zip for it too
Click to expand...
Click to collapse
And where can we find the basic zip file and how to the system in to tgz format?

exp13579 said:
And where can we find the basic zip file and how to the system in to tgz format?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=42135099&postcount=1

Darkimmortal said:
http://forum.xda-developers.com/showpost.php?p=42135099&postcount=1
Click to expand...
Click to collapse
Thanks, Pal.

wilx said:
Ok I have done this, but I have lost TWRP , it doesn't show up anymore on pressing vol down at green LED, root is there but just cant get into TWRP.... any suggestions
Click to expand...
Click to collapse
I have a same problem
It's a bug in the last version of DualRecovery....2.71....
I was on 370 rooted and all is working fine, I'm on 109 root perfect

[ROOT] J7 prime - CF AUTO ROOT [ SM-G610F - SM-G610M]

Here we have root for stock rom Thanks to the Chainfire Team.
Everything done by them so all thanks and credits are for them
Download
https://download.chainfire.eu/1036/CF-Root/CF-Auto-Root/CF-Auto-Root-on7xelte-on7xeltedd-smg610f.zip
Installation
-Enable USB debugging and OEM unlocking in the settings
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue
-Flash the CF-Auto-Root package as AP in ODIN(Comes within the zip file), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
I tested it on my device and it worked normally
I will not be responsible for any damage to your device, but following the steps will normally work normally
I just tested with ROM stock 6.0.1 with security patch from 1 July 2017
.

Hayleyw2 said:
Here we have root for stock rom Thanks to the Chainfire Team.
Everything done by them so all thanks and credits are for them
Download
https://download.chainfire.eu/1036/CF-Root/CF-Auto-Root/CF-Auto-Root-on7xelte-on7xeltedd-smg610f.zip
Installation
-Enable USB debugging and OEM unlocking in the settings
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue
-Flash the CF-Auto-Root package as AP in ODIN(Comes within the zip file), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
I tested it on my device and it worked normally
I will not be responsible for any damage to your device, but following the steps will normally work normally
I just tested with ROM stock 6.0.1 with security patch from 1 July 2017
.
Click to expand...
Click to collapse
Hi will it work for version 7.0 also

it's working fine for me
i have "G610FDDU1BRF2" with android version 7.0 and it gets installed successfully
thanks

How to change Supersu with Magisk?

Razortm said:
it's working fine for me
i have "G610FDDU1BRF2" with android version 7.0 and it gets installed successfully
thanks
Click to expand...
Click to collapse
How to restore stock recovery

Ryan.XM said:
How to restore stock recovery
Click to expand...
Click to collapse
Flash the cf auto root and it will automatically change your recovery into stock.

bjpp21 said:
Flash the cf auto root and it will automatically change your recovery into stock.
Click to expand...
Click to collapse
Ok thanks

I have J7 prime [SM-G610F] with stock andriod 8.1, samsung experience 9.5 and 1 November 2018 security patch will it still work?

I don't think so. I think the J7 with 8.1 is impossible to root? I can't seem to find an answer on this.

lordbaal19 said:
i don't think so. I think the j7 with 8.1 is impossible to root? I can't seem to find an answer on this.
Click to expand...
Click to collapse
its not impossible to root j7 on oreo..just search here in xda and you will find the impossible is really possible.

Well the TWRP thread has no real answers and this method doesn't work either.

I have done it
LordBaal19 said:
Well the TWRP thread has no real answers and this method doesn't work either.
Click to expand...
Click to collapse
yes, I have made root in my SM-G610m with Android 8.1 and it was with TWRP, and I have learned it from YouTube and in Spanish language.
For now I do not have available Super User. I think this post will work for me

ernestoi said:
yes, I have made root in my SM-G610m with Android 8.1 and it was with TWRP, and I have learned it from YouTube and in Spanish language.
For now I do not have available Super User. I think this post will work for me
Click to expand...
Click to collapse
Found a way:
LordBaal19 said:
Which one do you recommend? At which point do I have to install it and then I don't need to install no-verity-opt-encrypt-6.0?
EDIT: I think I finally got it. I did it like this:
1. Ok, so the phone as a fresh 8.1.0 system (just flashed the 7.0 and then it updated OTA in a matter of minutes). I enter the phone, enable the developer mode, enable OEM Unlocking and USB Debug.
2. Then I put the phone on download mode, flash the TWRP recovery disabling the auto-reboot on Odin so it doesn't boot to system automatically. This seem important since otherwise the recovery goes back to stock.
3. Then, to get out of download mode I press vol. down and power keys at the same time and the phone turn off. Then I turn on the phone into recovery mode, once in there I swipe into write mode and go to Wipe and select Format Data, type down yes and it says it's done. I go back to TWRP main menu.
4. I connect the cellphone to the PC and in storage I select Mount USB. Then drag the Magisk-v18.0.zip file into the storage that pops up on Windows. Then I saftely remove the device in Windows and go back to the main TWRP menu on the phone. I select Install and install the .zip file without selecting Signature verification or Reboot after is complete. It says is done installing and no errors seems to occur. I employ the button to wipe Cache and Dalvik.
5. I go back again o Wipe and select Format Data, type down yes and it says it's done, again.
5. Then I try to reboot to System, and choose to Do Not Install the TWRP app, and... SUCCESS!! The phone starts again, I config everything and then Magisk is there in the apps. I tried with an app that requires SU and it works!
Thanks for the help.
Click to expand...
Click to collapse
For the files and details check the OP on that thread.

LordBaal19 said:
Found a way:
For the files and details check the OP on that thread.
Click to expand...
Click to collapse
That's the way I have done it. But if you go on Z3X, select the device (SM-G610M), and you perform some activity like repair IMEI, Z3X detects the root, but it does not detect the Super User.

[Easy_Root/Unroot][Any_Oreo/Nougat_Firmware_V4_Bootloaders][Tmp_Twrp_Recovery]

EASY ROOT/UNROOT FOR S7 OR S7E ALL NOUGAT OR OREO STOCK ROMS
THANKS @klabit87 FOR OREO ROOT
TEMPORARY TWRP RECOVERY VIA ADB THANKS TO @afaneh92​
This is for AT&T, T-Mobile and Verizon and Sprint running V4 bootloaders only!​
This tool will allow you too easily root any stock rom allowing you to make any modifications you might want then easily unroot for better performance
This will Also give you a fully functional TWRP recovery that can be accessed via adb. TWRP is fully functional on OREO Roms but is limited on Nougat roms
The initial setup does require a data wipe.​
S7 G930T Flat Odin Factory FIrmware Downloads
G930TUVU4CRI2_8.0_4File_USA (T-Mobile).rar
ADB_Root Temporary Twrp Tool Download
S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z
S7 G935 Edge Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G935_EDGE_OREO.7z
SM_G935_EDGE_NOUGAT.7z
S7 G930 Flat Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G930_FLAT_OREO.7z
SM_G930_FLAT_NOUGAT.7z
Instructions
1. Download S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z and your model and version you want from above
2. Unzip S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z to S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
3. Unzip the Model/Version file you downloaded and copy the files to the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and place them in the Odin folder
4. Prepare your phone for a data wipe
5. Reboot your phone to download mode and flash the AP_ROOT_G93*.tar in the Odin AP slot and reboot your phone to recovery
6. Once phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
7. Now in the cmd window make sure your device is connected and choose Option (1) Launch TWRP
8. Your phone should launch TWRP leave phone plugged in and command window open on computer
9. Now In Twrp choose wipe and choose format data. Type yes in the box when it ask
10. Now in cmd window choose Option(8) Push Root.zip to Phone
11. Now in TWRP choose install and select the Root.zip
12. After zip is installed reboot and go through setup.
13. Once through setup make sure you are rooted
To Unroot Your Phone
1. In the Root Control app choose phone settings and unroot phone make sure phone is connected to computer
2. Now depending on the type of root you choose your phone will reboot to download if you chose system root or stock recovery if you chose systemless root. If your phone reboots to download mode skip to number 5
3. If your phone reboots to recovery once your phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
4. In cmd window choose Option(3) Unroot phone will reboot too download mode
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar
To Reroot Your Phone
1. Reboot to download in Odin AP slot flash AP_ROOT_G93***.tar
2. Phone will reboot then will reboot one more time and you will be rerooted
To Enter TWRP When Rooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Manually reboot phone to recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP
2. To Exit TWRP simply choose reboot
To Enter TWRP When Unrooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Put phone in download mode In Odin AP slot flash AP_ROOT_G93***.tar force phone to reboot to recovery. If you let phone boot it will reroot and you will have to run the unroot from the root control app.
2. In recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP.
3. Do whatever you need too do
4. To exit Twrp choose reboot to Download
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar

Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good

jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
I had to look this up so thought I'd share This is for Tmobile Versions
Example: G930TUVS8CRJ1 (5th # from right is 8, BL version - this is found in Settings>About Phone>Software Information>Baseband Version)
Which Oreo versions are safe (ver 4):
G930TUVU4CRI2 Oct 1, 2018
G930TUVU4CRF1 June 28, 2018
Not safe (ver 8):
G930TUVS8CRJ1 Oct 26, 2018 release date
---------- Post added at 02:55 AM ---------- Previous post was at 02:49 AM ----------
BTW nice work as always Jr! Oh, & almost forgot ...your last comment saved my @zz!!! I wasn't aware of the ver 8 issue, and the fact that u can't downgrade!! DAMN Samsung!!!!! I was seriously about to try this latest update just to try & figure out RCS not working on CRF1 & randomly came across this! THANKS! (BTW if you know anything about RCS on s7 or services/apks needed for functionality on CRF1 please pm me!)
On another note, let's have a contest to see who can hold on to the S7 the longest as their primary phone

It works perfectly , I had no problem installing it. But I have a question:
Could I replace the SuperSu with the Magisk?
I am also in the Rom Project L S7 of Lanc-City: 3

FranMLG said:
It works perfectly , I had no problem installing it. But I have a question:
Could I replace the SuperSu with the Magisk?
I am also in the Rom Project L S7 of Lanc-City: 3
Click to expand...
Click to collapse
No magisk requires custom boot.img
Sent using some kind of device I modified

jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
Thanks for the effort and providing root for T-Mobile. Perhaps I am an unlucky person. By the time I discovered this thread, my phone was already updated to G930TUVS8CRJ1 version. I am wondering if there is any hope for V8 bootloader to root their phone in near future. Here is my humble request if you could provide root for V8 update. TIA.

jrkruse said:
No magisk requires custom boot.img
Sent using some kind of device I modified
Click to expand...
Click to collapse
can we do full backup after setting up the phone and then restore it without any bugs and issues?

zfk110 said:
can we do full backup after setting up the phone and then restore it without any bugs and issues?
Click to expand...
Click to collapse
Do a system.img backup
Sent using some kind of device I modified

Thank you. It worked fine on my nougat s7 flat with v4 bootloader. Now I have nougat root. I have a question if I may, Can I use tmp twrp to flash Oreo or one of your, or other roms? Or would I need to upgrade the kernel or something because I can flash Oreo being that I'm on Nougat. Thanks.

boofbatch said:
Thank you. It worked fine on my nougat s7 flat with v4 bootloader. Now I have nougat root. I have a question if I may, Can I use tmp twrp to flash Oreo or one of your, or other roms? Or would I need to upgrade the kernel or something because I can flash Oreo being that I'm on Nougat. Thanks.
Click to expand...
Click to collapse
You have to update bootloaders and firmware as well so its better to update to oreo first
Sent using some kind of device I modified

working fine.
update: gonna have to switch back to u firmware because even when i unroot the phone, certain games wont work or connect to server. i cant install magisk to bypass safetynet or hide magisk after installing so root isnt even seeming worth it on this device. might as well stick to the u firmware and disable the apps I dont need and disable ota update so that i dont get the v8 bootloader update. It was fun while it lasted.

jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
Man, will you update the Recovery for the new security patch (CRJ1) ?, I've run out of Root , and I can no longer go back in the version.
---------- Post added at 04:50 PM ---------- Previous post was at 04:47 PM ----------
jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
That's exactly what happened to me, I did not know

FranMLG said:
Man, will you update the Recovery for the new security patch (CRJ1) ?, I've run out of Root , and I can no longer go back in the version.
---------- Post added at 04:50 PM ---------- Previous post was at 04:47 PM ----------
That's exactly what happened to me, I did not know
Click to expand...
Click to collapse
yikes sorry to hear that

jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
I bought a phone which is already to g930tuvs8crj1 I tried to down grade but it wont let me, what are my options? Thanks

zfk110 said:
I bought a phone which is already to g930tuvs8crj1 I tried to down grade but it wont let me, what are my options? Thanks
Click to expand...
Click to collapse
Enjoy Stock
Sent using some kind of device I modified

jrkruse said:
Enjoy Stock
Sent using some kind of device I modified
Click to expand...
Click to collapse
After looking around for 4 days I was finally able to find G930T U8 ENG ROOT Modem.bin file, but when I'm trying to flash it using odin it wont pass file Analyzing
I hope you can look more into it. if we can flash this then we can able to root U8 bootloaders too
https://drive.google.com/open?id=1dhHeYAPsCqKQ_eFfuzPaYbgFv0y1BSLr
These guys also selling Eng boot for $60
https://support.halabtech.com/index.php?a=downloads&b=file&id=90428

zfk110 said:
After looking around for 4 days I was finally able to find G930T U8 ENG ROOT Modem.bin file, but when I'm trying to flash it using odin it wont pass file Analyzing
I hope you can look more into it. if we can flash this then we can able to root U8 bootloaders too
https://drive.google.com/open?id=1dhHeYAPsCqKQ_eFfuzPaYbgFv0y1BSLr
These guys also selling Eng boot for $60
https://support.halabtech.com/index.php?a=downloads&b=file&id=90428
Click to expand...
Click to collapse
Im just waiting on them to email me the passwords
Sent using some kind of device I modified

Alright guys i really need your help...i just bought a used samsung. galaxy s7 G930T...the problem is it doesnt get any network...thr signal says searching and theres is nl network bar...the issue is i cant tell if it is unlocked or not..because it reads my sim...it displays the right access point....shoes sim tools...but just doesn't get network..i ve tried all sim cards...i tried using the tmobile unlock tool that came with the device butbit says unlock failed reboot device repeatedly....ive tried factory reset....i love this phone and would really like to use it...Pls any suggestions or help...the software version is 8.0. baseband version is G930TUVS8CRL1

marvelv94 said:
Alright guys i really need your help...i just bought a used samsung. galaxy s7 G930T...the problem is it doesnt get any network...thr signal says searching and theres is nl network bar...the issue is i cant tell if it is unlocked or not..because it reads my sim...it displays the right access point....shoes sim tools...but just doesn't get network..i ve tried all sim cards...i tried using the tmobile unlock tool that came with the device butbit says unlock failed reboot device repeatedly....ive tried factory reset....i love this phone and would really like to use it...Pls any suggestions or help...the software version is 8.0. baseband version is G930TUVS8CRL1
Click to expand...
Click to collapse
Sounds like you bought yourself a blacklisted phone
Sent using some kind of device I modified

jrkruse said:
Sounds like you bought yourself a blacklisted phone
Sent using some kind of device I modified
Click to expand...
Click to collapse
It is not blacklisted ...i already checked...any help?