Related
thHello all,
This is a known way to root any android phone with an unlocked bootloader. I tested it on my ZR, it just works fine and is easy & fast to follow !
It works for all firmwares and it's a good way to root the latest stock rom (eg .67 / .244 or even KitKat firmwares).
Note: I'm not responsible if something happens to your device ! Just follow the procedure and all'd be fine !
Quick instructions
Unlock bootloader
Flash any CWM-containing kernel
Boot into recovery and flash su-bin-arm-signed.zip (or this one that worked for me on KitKat)
Revert back to stock kernel
Install SuperSU and update su.bin
Enjoy
Instructions for noobies (yes I didn't forget you !)
Unlock your bootloader.
You may want to backup your TA before. In this case you need an already rooted phone. I personnaly downgraded mine to .310 then rooted it with Doom's toolkit to be able to backup my TA.
Download and copy the following file to your phone: su-bin-arm-signed.zip (or this one for 4.3)
Install the firmware you want to be on when the phone gets rooted
Flash a kernel that contains CWM, for example this one which comes from CM 10.1 FXP234a (you can also try to hotboot it, didn't work for me).
You can flash it with a command line or a soft like FlashTool:
In FlashTool select Flash > Fastboot mode
Connect the phone in fastboot mode : when powered off, connect it to your laptop while pressing Volume + key. You can release the key when the LED turns blue
Select the kernel to flash and run the operation
> Now do not try to boot normally the phone because it won't boot, as the kernel's not compatible with the stock rom.
Boot into recovery:
Power on the phone
When the led turns violet at boot for 3", press Volume +
Now you are in recovery. Use Volume buttons to navigate and Power to confirm.
Select Install zip > Choose zip from sdcard or external sdcard (depending where you put the .zip to flash)
Choose su-bin-arm-signed.zip
Confirm
Go to Advanded > Power off
Flash back the stock kernel corresponding to the firmware installed on the phone (.244 -> .244 kernel). You can for example use Flashtool:
Download the .ftf of the build installed on your phone (no matter the location of the firmware)
Run Flashtool
Do Flash > Flashmode and select the .ftf you downloaded
Uncheck anything on the "Wipe" colon
Check everything on the "Exclude" colon except "KERNEL"
You should now only have kernel.sin and loader.sin on the content colon.
Click on Flash
Connect the phone in flash mode : when powered off, connect it to your laptop while pressing Volume - key. You can release the key when the LED turns green
Reboot the phone, install SuperSU, run it and update the su binary
You can relock the bootloader with Backup TA to recover warranty or Bravia Engine 2 without losing root.
May help:
- Stock .310 kernel
- Stock .244 kernel
- Stock .67 kernel
- Stock .569 kernel for C5503 / C5502
- Instructions by gspbeetle
Thanks to:
- Team FXP for the kernel
Sorry for my bad english and I hope I helped
NeoJeo said:
Hello all,
This is a known way to root any android phone with an unlocked bootloader. I tested it on my ZR, it just works fine and is easy & fast to follow !
It works for all firmwares and it's a good way to root the latest stock rom (eg .244).
Note: I'm not responsible if something happens to your device ! Just follow the procedure and all'd be fine !
Quick instructions
Unlock bootloader
Flash any CWM-containing kernel
Boot into recovery and flash su-bin-arm-signed.zip
Revert back to stock kernel
Install SuperSU and update su.bin
Enjoy
Instructions for noobies (yes I didn't forget you !)
Unlock your bootloader.
You may want to backup your TA before. In this case you need an already rooted phone. I personnaly downgraded mine to .310 then rooted it with Doom's toolkit to be able to backup my TA.
Download and copy the following file to your phone: su-bin-arm-signed.zip
Install the firmware you want to be on when the phone gets rooted
Flash a kernel that contains CWM, for example this one which comes from CM 10.1 FXP234a (you can also try to hotboot it, didn't work for me).
You can flash it with a command line or a soft like FlashTool:
In FlashTool select Flash > Fastboot mode
Connect the phone in fastboot mode : when powered off, connect it to your laptop while pressing Volume + key. You can release the key when the LED turns blue
Select the kernel to flash and run the operation
> Now do not try to boot normally the phone because it won't boot, as the kernel's not compatible with the stock rom.
Boot into recovery:
Power on the phone
When the led turns violet at boot for 3", press Volume +
Now you are in recovery. Use Volume buttons to navigate and Power to confirm.
Select Install zip > Choose zip from sdcard or external sdcard (depending where you put the .zip to flash)
Choose su-bin-arm-signed.zip
Confirm
Go to Advanded > Power off
Flash back the stock kernel corresponding to the firmware installed on the phone (.244 -> .244 kernel). You can for example use Flashtool:
Download the .ftf of the build installed on your phone (no matter the location of the firmware)
Run Flashtool
Do Flash > Flashmode and select the .ftf you downloaded
Uncheck anything on the "Wipe" colon
Check everything on the "Exclude" colon except "KERNEL"
You should now only have kernel.sin and loader.sin on the content colon.
Click on Flash
Connect the phone in flash mode : when powered off, connect it to your laptop while pressing Volume - key. You can release the key when the LED turns green
Reboot the phone, install SuperSU, run it and update the su binary
You can relock the bootloader with Backup TA to recover warranty or Bravia Engine 2 without losing root.
May help:
- Stock .310 kernel
- Stock .244 kernel
Thanks to:
- Team FXP for the kernel
Sorry for my bad english and I hope I helped
Click to expand...
Click to collapse
Sounds good. Testing this. Will let you know of the end results
akash4357 said:
Sounds good. Testing this. Will let you know of the end results
Click to expand...
Click to collapse
Thanks ! Did it work as expected ?
NeoJeo said:
Thanks ! Did it work as expected ?
Click to expand...
Click to collapse
Yes! It worked brilliant. Excellent find NeoJeo. Appreciate your help.
akash4357 said:
Yes! It worked brilliant. Excellent find NeoJeo. Appreciate your help.
Click to expand...
Click to collapse
Glad I helped
I wish had nown this before doing it the long way
Backing up with pc companion, downgrading with flashtool, rooting and then wait for OTA update and after that restore the backup with pc companion.
Skickat från min C5503 med Tapatalk 4
Mario.D said:
I wish had nown this before doing it the long way
Backing up with pc companion, downgrading with flashtool, rooting and then wait for OTA update and after that restore the backup with pc companion.
Skickat från min C5503 med Tapatalk 4
Click to expand...
Click to collapse
I also found the long ways to long... mostly with a slow connection. That's why I thought to this one
Regarding backup of TA partition, does it have to revert to original firmware or can I back it up even after flashing 4.2.2 with root?
grim_ripper said:
Regarding backup of TA partition, does it have to revert to original firmware or can I back it up even after flashing 4.2.2 with root?
Click to expand...
Click to collapse
Backing up TA Partition can only be done BEFORE you unlocked bootloader.
Thanks NeoJeo for this awesome rooting method! Flashed the Nordic 4.2.2 ROM on my Xperia ZR and it is working like a charm .
I've backed up my phone's TA partition just in case something goes wrong and I need to re-lock it and give it for servicing .
@ Grim_ripper: Is your bootloader already unlocked ?
@ su1979: You're welcome, glad I helped !
su1979 said:
I've backed up my phone's TA partition just in case something goes wrong and I need to re-lock it and give it for servicing .
Click to expand...
Click to collapse
I did the same ^^
thanks!! I'm testing !
Is it possible to re-lock the BL if I didn't do any TA backup before?
awwer2002 said:
thanks!! I'm testing !
Is it possible to re-lock the BL if I didn't do any TA backup before?
Click to expand...
Click to collapse
Hello,
No, not possible for the moment. For other devices such as the Xperia Z we can relock the bootloader by flashing a .ftf but without recovering the drm.
The backup and restore tool is the better way to reloock but it needs a backup before you unlock the BL.
I cant acces to the recovery mode even i press vol+ when i see the green light
Did i do something wrong？
The device is working good so far by this rooting method.
I just want the recovery mode back:cyclops:
Sorry for my bad english
awwer2002 said:
I cant acces to the recovery mode even i press vol+ when i see the green light
Did i do something wrong？
The device is working good so far by this rooting method.
I just want the recovery mode back:cyclops:
Sorry for my bad english
Click to expand...
Click to collapse
Green light? weird. Do the cyanogenmod logo displays at boot?
awwer2002 said:
I cant acces to the recovery mode even i press vol+ when i see the green light
Did i do something wrong？
The device is working good so far by this rooting method.
I just want the recovery mode back:cyclops:
Sorry for my bad english
Click to expand...
Click to collapse
If "select kernel to flash" says something like
"writing 'boot'...
FAILED (remote: Command not allowed)"
It means your bootloader is not unlocked yet.
NeoJeo said:
Green light? weird. Do the cyanogenmod logo displays at boot?
Click to expand...
Click to collapse
oh, I mean after I flashed back the stock kernel.
sorry I am new to android
---------- Post added at 09:50 PM ---------- Previous post was at 09:47 PM ----------
NeoJeo said:
Green light? weird. Do the cyanogenmod logo displays at boot?
Click to expand...
Click to collapse
gspbeetle said:
If "select kernel to flash" says something like
"writing 'boot'...
FAILED (remote: Command not allowed)"
It means your bootloader is not unlocked yet.
Click to expand...
Click to collapse
I am sure the BL is unlocked already as I flashed CM10.1 before.
anyway, Thanks for your advise
Edit: Use PRFCreated method for lollipop 5.0.2->5.1.1
Edit: For windows 8/10, you need to enable test mode for S1Boot fastboot driver install, you can also sign it with Zadig afterwards and turn off test mode.
Code:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
(reboot)
Thanks NeoJeo for the method!
For some reason, my friend's new machine have to use flashtool to create a ftf backup first after updating the official firmware . Using other kernels will fail and creates a bootloop. (Maybe carrier locked? No idea.)
Bootloop can be solved by re-flashing the stock firmware completely and redo all the steps again, so its quite safe.
Stock roms:
You can always download the latest with firmware with xperifirm.
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
HK stock roms seem to be less bloated.
Old roms for research purpose:
C5503_10.1.1.A.1.310 (HK) (4.1.2)
https://docs.google.com/file/d/0B-WWAl17NsavUWJRZldCZVdpNTQ/edit?pli=1
* (Doomlord rooter for this rom:
http://forum.xda-developers.com/showthread.php?t=2327472)
Pre-rooted 10.4.B.0.569 (4.3.0) rom by Sijav:
http://forum.xda-developers.com/showthread.php?t=2590174
C5503_10.5.A.0.230 (HK) (4.4.2)
https://www.dropbox.com/s/phqyx3awwpjr1ab/C5503_10.5.A.0.230_Generic HK.rar
C5503_10.5.A.0.230 (NORDIC) (4.4.2):
http://forum.xda-developers.com/showthread.php?t=2774540
C5503_10.6.A.0.454 (HK) (5.0.2):
https://drive.google.com/file/d/0B7l5nu0bqYuGWUk3WkpQbm9EQm8/view?usp=sharing
Tools:
Flashtool:
http://flashtool.net/download.html
(Remember to install drivers as well from C:\Flashtool\drivers)
Backup TA:
http://forum.xda-developers.com/showthread.php?t=2292598
or https://www.dropbox.com/s/xjm6t08xy946lee/Backup-TA-9.10.zip
SDK Platfom tools:
http://developer.android.com/
or https://www.dropbox.com/s/lgs2m90p1et87hx/platform-tools.7z
Super SU zip install:
http://download.chainfire.eu/supersu
or
https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
Boot.img:
http://forum.xda-developers.com/showthread.php?t=2774540
or
https://www.dropbox.com/s/0n62ripm00u4z78/boot_v8.img
UPDATE FOR 5.0.2, new boot.img:
(ref: http://forum.xda-developers.com/xperia-zr/general/c5502-unlock-bootloader-rom-c5502stock5-t3115901)
https://drive.google.com/file/d/0B7l5nu0bqYuGX19QcUl5VWdKOXc/view
Step by step reference for my friends:
1. download & install flashtool http://flashtool.net/download.html
^if doesnt work, then try https://www.dropbox.com/s/xyk493qa8psydrf/flashtool-0.9.13.0-windows.exe
2. install flashmode and fastboot drivers from C:\Flashtool\drivers
3. plugin your phone, make sure settings->security->unknown source and settings->developer options->usb debugging is checked at all times
(if cant find developer options, go to settings->about phone->build number, keep tapping build number to see what happens)
4. - If your already phone upgraded, then:
4.1 If you want to keep your current kernel for later use, see: http://forum.xda-developers.com/showthread.php?t=2334653)
4.2 download 31x kernel (4.1.2) from http://forum.xda-developers.com/showthread.php?t=2384512
4.3 save it to \Flashtool\firmwares
4.4 open FlashTool.exe, click Flash device -> Flashmode
^ to enter flashmode, either plugin usb without battery or plugin usb with Volume - while your phone is OFF
4.5 select the 31x kernel and downgrade
4.6 kill FlashTool.exe
5. download and run doomlord's rooter from http://forum.xda-developers.com/showthread.php?t=2327472
6. use task manager or cmd to kill adb.exe, if it is still running
- Now you have a rooted phone
7. download and run backup ta from http://forum.xda-developers.com/showthread.php?t=2292598 , keep the zip file for later use
- Backup TA only works with rooted rom
- If you want to use the latest andriod continue below:
7 download the latest firmware with xperifirm and bundle it with flashtool.
8. upgrade / flash your system to the latest version (see step 4, but use the latest firmware file instead)
9. get unlock key from http://unlockbootloader.sonymobile.com/unlock/step1
11. download andriod sdk from google and install http://developer.android.com/
12. open SDK manager, scroll down and check Google USB Driver then click install packages
^ if doesnt work, then try: https://www.dropbox.com/s/lgs2m90p1et87hx/platform-tools.7z
^ USB drivers is also avaible under flashtools/drivers
13. go to \sdk\platform-tools
(replace %key% below with the key from sony's email)
run fastboot.exe -i 0x0fce oem unlock 0x%key% in cmd
or create a plain text file and save it as a .bat with
Code:
fastboot.exe -i 0x0fce oem unlock 0x[B][I]%key%[/I][/B] [user=607132]@pause[/user]
^ If stuck at 'waiting for device', you can use flashtool.exe to enter 'fastboot mode via adb' (run Flashtool.exe -> Flash device -> fastbootmode
), then re-try the command above
^ while in fastboot mode, your phone screen is off and led is blue
- Now you bootloader is unlocked.
14. put this zip file into your external sd from http://download.chainfire.eu/supers...om/s/sy1vzzq9ygfvqvb/UPDATE-SuperSU-v2.01.zip
15. run Flashtool.exe -> Flash device -> fastbootmode
16. reboot into fastboot mode (via ADB)
17. after led turns blue, select kernel to flash and choose boot.img from http://www.mediafire.com/download/4bs9zy3z4sl1lvl/boot.img
^ if doesnt work, try: https://www.dropbox.com/s/y5is541wd5lck79/boot.img
18 click reboot device into system while pressing Volume +
- if LED does not turn purple at all, something must be wrong
- press Volume + as long as but NOT before the LED turn purple.
^ return to step 4 if needed, bootloader may be not properly unlocked.
19 select install zip -> choose zip from external sdcard
^ Volume+ - is up and down, Power is select
20 confirm
21 go to advance -> power off
22 remove battery and plugin usb to enter flash mode
^ Flashtool.exe should show the phone is connected in flash mode
^ But there seems to be a time limit where CM 10.1 remount itself automatically with the wired blue thing popping up and then crash
23 return to Flashtool.exe -> Flash device -> Flashmode
24 choose the .ftf either from the one in step 8 or the one you have downloaded
25 Uncheck anything on the "Wipe" colon
26 Check everything on the "Exclude" colon except "KERNEL"
^ You should now only have kernel.sin and loader.sin on the content colon
27 FLASH!
- if bootloop occurs, return to step 4 lol
^ alternatively you can just redo step 24, but this time "Wipe" everything and "Include" everything. If it boots, then jump right to step 14 and retry installing the zip
28 Install super su in google play
^ first boot may need battery in and usb removed
29 (optional) Re-run backup-ta to restore the zip from step 7 for Relocking bootloader (and check for rooted at the same time)
- if backup ta failed because of no su rights, return to step 4 lol
EDIT: do not re-lock bootloader if using the new img
EDIT:
Upgrading should keep your settings and stuff, unless something went wrong that you have to wipe data for a clean install.
Quick check list:
1. Most Important. Make sure you still have your bootloader backups.
Run Backup-TA to backup your current bootlocker if needed (new version here:http://forum.xda-developers.com/showthread.php?t=2292598). Backup-TA only works on rooted.
2. If you somehow lost it, re-obtain your unlock key from http://unlockbootloader.sonymobile.com/unlock/step1
3. Have your Flashtool and SDK ready (https://www.dropbox.com/s/xyk493qa8psydrf/flashtool-0.9.13.0-windows.exe, https://www.dropbox.com/s/lgs2m90p1et87hx/platform-tools.7z)
4. If you need the stock firmware from your carrier, remember to clear contents in something like: C:\ProgramData\Sony Ericsson\Update Engine\db\13740270\blob_fs and/or C:\ProgramData\Sony Mobile\Update Engine\db\13740270\blob_fs (or something similar in %appdata% for windows XP)
5. You can use any ADB backup tool or Sony Companion to backup your settings, best timing is right after OS update but before rooting.
To do:
1. Either upgrade with Sony Companion and use Flashtool -> SEUS Decrypt, or download by XperiFirm to create your own firmware (Will take a while to load depending on the power level of your PC.)
or just use the firmware people uploaded
2. open Flashtool.exe -> Flash device -> fastbootmode
3. reboot into fastboot mode (via ADB)
4. Unlock you bootlocker by running "fastboot.exe -i 0x0fce oem unlock 0x%key%" (%key% is your unlock key from Sony's email)
^ (Last time I checked, some people say they need to update SDK first.)
^ (unlock key may change after new firmware is flashed)
^ you need to enter fastboot mode via ADB first, or it will get stuck at 'waiting for device'
5. select kernel to flash and choose boot.img
6. click reboot device into system while pressing Volume + (press Volume + after the LED turn purple)
7. select install zip -> choose zip from external sdcard -> your-su-zip-file (http://download.chainfire.eu/supersu)
^ 'Volume+' 'Volume-' and 'Power'.
8. go to advance -> power off
^ If you get a boot loop, simply remove battery and plugin usb cable to enter flashmode and re-flash the new firmware again.
^ remember to re-enable "Usb debugging" under "Developer options"
^ tap "About phone" -> "Build number" 10 times to unlock "Developer options"
[/hide]
Thanks this works great but I am unable to successfully install a recovery with this method. Has anyone had the same issues??
Sent from my C5503 using xda app-developers app
Hello,
@awwer2002: After you succeed rooting the device did you install any recovery ? If yes, which one ?
@gmengass: Which recovery are you trying to install ?
Hello all,
I rooted my Xperia SP and had installed the Cyanogenmod 11 (last stable-ish release, milestone or something) successfully.
After being encouraged by a co-worker that the nightly builds are pretty safe too, I installed a 12.1 nightly (can't remember which, though).
After that I couldn't reboot to bootloader any more to back up my phone.
I can select it in the reboot menu, but the phone will just cycle into a normal reboot and start Cyanogen.
Being brave I installed another nightly (current version: 12.1-20151010-NIGHTLY-huashan), hoping that would help.
It didn't, but luckily that version works, too.
Otherwise the phone works well, but I would like to be able to reboot into the bootloader to create a system backup, before I install more nightlies.
Rebooting into recovery works. However, have no backup option there.
To clarify: booting into bootloader is not necessarily what I want, it's the backup option that I'm after.
On the other hand, this not working properly is kind of a red flag, so I want to make sure nothing is going sideways...
Any advice would be much appreciated!
Thanks!
Merlin
centaury02 said:
Hello all,
I rooted my Xperia SP and had installed the Cyanogenmod 11 (last stable-ish release, milestone or something) successfully.
After being encouraged by a co-worker that the nightly builds are pretty safe too, I installed a 12.1 nightly (can't remember which, though).
After that I couldn't reboot to bootloader any more to back up my phone.
I can select it in the reboot menu, but the phone will just cycle into a normal reboot and start Cyanogen.
Being brave I installed another nightly (current version: 12.1-20151010-NIGHTLY-huashan), hoping that would help.
It didn't, but luckily that version works, too.
Otherwise the phone works well, but I would like to be able to reboot into the bootloader to create a system backup, before I install more nightlies.
Rebooting into recovery works. However, have no backup option there.
To clarify: booting into bootloader is not necessarily what I want, it's the backup option that I'm after.
On the other hand, this not working properly is kind of a red flag, so I want to make sure nothing is going sideways...
Any advice would be much appreciated!
Thanks!
Merlin
Click to expand...
Click to collapse
I guess you're confusing recovery with bootloader,
The default recovery CM12.1 and other CM based ROMs come with is "Cyanogen Recovery" which is not very popular coz it lacks many features.
Anyways, TWRP is a pretty good recovery that allows you to backup, restore, etc, and it even has it's own file manager. Download the latest recovery from here and flash it via CM recovery, it will replace CM recovery with TWRP.
Zenith said:
I guess you're confusing recovery with bootloader,
...
Download the latest recovery from here and flash it via CM recovery, it will replace CM recovery with TWRP.
Click to expand...
Click to collapse
Hi Zenith,
thanks for your quick reply! I'll give it a shot and report here if it worked.
I don't think I confuse the two, though.
When I choose reboot, I get to select (amongst the usual) "Bootloader" or "Recovery".
"Recovery" gives me a menu (after reboot) where I could theoretically roll back to a previous backup for example.
"Bootloader" earlier gave me a text-based menu, where I could back my system up, now I can't reach this any more. The phone simply boots Cyanogenmod again.
Anyway, thanks and I'll try out TWRP!
centaury02 said:
Hi Zenith,
thanks for your quick reply! I'll give it a shot and report here if it worked.
I don't think I confuse the two, though.
When I choose reboot, I get to select (amongst the usual) "Bootloader" or "Recovery".
"Recovery" gives me a menu (after reboot) where I could theoretically roll back to a previous backup for example.
"Bootloader" earlier gave me a text-based menu, where I could back my system up, now I can't reach this any more. The phone simply boots Cyanogenmod again.
Anyway, thanks and I'll try out TWRP!
Click to expand...
Click to collapse
well... the TWRP recovery is all you need if you wanna backup your system and restore later.
You won't need to use the 'Reboot to bootloader' option.
and Welcome
Hit the "Thanks" button if I helped.
Hi Zenith again,
I downloaded the zip-file and booted my cell phone into recovery mode.
Then I chose "Apply update" and the zip-file I had just downloaded.
It showed me a success, rebooting into recovery mode gave me the exact same menu ("Cyanogen recovery").
I probably did something wrong, but what?
Can you point me in the right direction, please?
Thx!
Edit: choosing "reboot to bootloader" in the recovery menu reboots the phone as before (not into bootloader)
Make sure you didn't select 'update cyanogenmod recovery' in the developer option, then go to http://forum.xda-developers.com/xpe...-twrp-f2fs-support-xperia-sp-huashan-t3150230 ,download the zip and flash it with cyanogenmod recovery. You can now live happily ever after with cyanogenmod and twrp recovey.
flash it back to stock rom and then root it via towelroot and installa superSU also check with any app if your phone is rooted or not then check if bootloader is unlocked and after that flash doomkernel (latest verson) after that flash any rom you want to test
steveglowplunk said:
Make sure you didn't select 'update cyanogenmod recovery' in the developer option, then go to http://forum.xda-developers.com/xpe...-twrp-f2fs-support-xperia-sp-huashan-t3150230 ,download the zip and flash it with cyanogenmod recovery. You can now live happily ever after with cyanogenmod and twrp recovey.
Click to expand...
Click to collapse
@steveglowplunk:
Thanks, that was what obviously kept replacing the recovery module.
I used the zip-file that Zenith linked to initially, though. It worked fine after that (hence the thank you to both of you).
@electro_nik:
I didn't want to go through the whole process again. I'm sure your way would give me back the original bootloader, but as long as I can create a backup, I think I'm fine. Thanks though!
Also never forget to CHECK ROOT ACCESS FOR ADB and USB DEBUGGING in the developer option. It can always save both your life and your phone's life when your phone is bricked
This is an unofficial TWRP port for LG-H960A.
Thanks to @KAsp3rd and @GROGG88
I DON'T TAKE ANY RESPONSIBILITY. YOU DO EVERYTHING AT YOUR OWN RISK.
READ EVERYTHING and MAKE A BACKUP BEFORE YOU START.
Instructions:
1. You must be on newest stock Marshmallow: H960A20a_00_0316.kdz
You can use LG Bridge to install official update, or download .kdz file HERE
2. You need to have bootloader ulocked.
Official instructions are here: ( Unlocking the Bootloader @ LG Developer )
Remember that this will completely WIPE YOUR DATA, you will LOSE WARRANTY and this operation is IRREVERSIBLE.
3. Flash TWRP.
I assume you got ADB and FASTBOOT drivers working and adb is paired (it should be if you completed step 2).
Connect your phone to your pc, open command prompt and reboot to bootloader:
Code:
adb reboot bootloader
Your phone should reboot and you should be welcomed by Fastboot Mode screen.
Now download the recovery file (below) to your pc, unpack (to get .img) and rename it to recovery.img and put it in folder where you got command prompt open and:
Code:
fastboot flash recovery recovery.img
4. Boot to TWRP.
As on Marshmallow some fastboot commands are not working and LG is restoring recovery on every boot (so you cant use "adb reboot recovery" right now) you need to use one trick.
DO NOT REBOOT YOUR PHONE.
When still in fastboot from step 3 you need to turn off your phone completely. You can do that by holding power button or if that is not working take the battery out.
Now (put the battery in) and press POWER + VOL DOWN buttons. When you see LG logo release the POWER button (while still holding VOL DOWN) and press POWER button again.
You should see a screen which is asking you if you want to factory reset your phone. Don't worry - if you made everything correctly it should not wipe your phone.
Use volume and power buttons to choose YES (twice) - and you should see a TWRP screen (after a while)
WARNING: IF YOU REBOOTED YOUR PHONE AFTER FLASHING RECOVERY THIS STEP WILL REALLY ERASE ALL DATA. You need to flash recovery again (step 3)
5. (optional) flash SuperSU to get root.
Get SuperSU from official thread and put it in your phone.
While in TWRP from step 4 your phone should be recognized by ADB. Use below to move file to sdcard.
Code:
adb push BETA-SuperSU-v2.74-2-20160519174328.zip /sdcard/supersu.zip
Now in TWRP click Install, go to /sdcard/ and chooose supersu.zip. Follow instructions. After install you should choose to wipe cache/dalvik and reboot to system.
Your phone should be rooted now.
Download:
twrp-3.0.2.0-0-h960a.img.zip
(unpack .zip to get flashable .img)
Issues:
- Layout is wrong, status bar is being drawn on second screen.
- Date/time is wrong.
broken url
OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty?
11868 said:
broken url
Click to expand...
Click to collapse
Oh, true. Fixed.
rascal0pl said:
OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty?
Click to expand...
Click to collapse
Maybe.
Thank You it worked!
Great. Just bought it 2 days ago for good price. Will try it.
Sent from my LG-H955 using Tapatalk
Hi,
that's just great, thanks a lot.
As root is now possible has anyone tried to install xposed on th H960A?
I'm wondering if the second screen fix for the Telekom V10 also works with the H960A.
What about Viper4Android and AdAway?
rudi666 said:
This is an unofficial TWRP port for LG-H960A.
Thanks to @KAsp3rd and @GROGG88
I DON'T TAKE ANY RESPONSIBILITY. YOU DO EVERYTHING AT YOUR OWN RISK.
READ EVERYTHING and MAKE A BACKUP BEFORE YOU START.
Instructions:
1. You must be on newest stock Marshmallow: H960A20a_00_0316.kdz
You can use LG Bridge to install official update, or download .kdz file HERE
2. You need to have bootloader ulocked.
Official instructions are here: ( Unlocking the Bootloader @ LG Developer )
Remember that this will completely WIPE YOUR DATA, you will LOSE WARRANTY and this operation is IRREVERSIBLE.
3. Flash TWRP.
I assume you got ADB and FASTBOOT drivers working and adb is paired (it should be if you completed step 2).
Connect your phone to your pc, open command prompt and reboot to bootloader:
Code:
adb reboot bootloader
Your phone should reboot and you should be welcomed by Fastboot Mode screen.
Now download the recovery file (below) to your pc, unpack (to get .img) and rename it to recovery.img and put it in folder where you got command prompt open and:
Code:
fastboot flash recovery recovery.img
4. Boot to TWRP.
As on Marshmallow some fastboot commands are not working and LG is restoring recovery on every boot (so you cant use "adb reboot recovery" right now) you need to use one trick.
DO NOT REBOOT YOUR PHONE.
When still in fastboot from step 3 you need to turn off your phone completely. You can do that by holding power button or if that is not working take the battery out.
Now (put the battery in) and press POWER + VOL DOWN buttons. When you see LG logo release the POWER button (while still holding VOL DOWN) and press POWER button again.
You should see a screen which is asking you if you want to factory reset your phone. Don't worry - if you made everything correctly it should not wipe your phone.
Use volume and power buttons to choose YES (twice) - and you should see a TWRP screen (after a while)
WARNING: IF YOU REBOOTED YOUR PHONE AFTER FLASHING RECOVERY THIS STEP WILL REALLY ERASE ALL DATA. You need to flash recovery again (step 3)
5. (optional) flash SuperSU to get root.
Get SuperSU from official thread and put it in your phone.
While in TWRP from step 4 your phone should be recognized by ADB. Use below to move file to sdcard.
Code:
adb push BETA-SuperSU-v2.74-2-20160519174328.zip /sdcard/supersu.zip
Now in TWRP click Install, go to /sdcard/ and chooose supersu.zip. Follow instructions. After install you should choose to wipe cache/dalvik and reboot to system.
Your phone should be rooted now.
Download:
twrp-3.0.2.0-0-h960a.img.zip
(unpack .zip to get flashable .img)
Issues:
- Layout is wrong, status bar is being drawn on second screen.
- Date/time is wrong.
Click to expand...
Click to collapse
Are there any other known issues? I don`t need to install any custom roms. I need it only for root and xposed on Marshmallow. Is there something that can surprise me?
Hi,
"OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty? "
Ohh, thats sounds nice if this realy possible.
i love my v10.
orbitandre said:
hi,
"ok, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty? "
ohh, thats sounds nice if this realy possible.
i love my v10.
Click to expand...
Click to collapse
+1 ??
cyvr1 said:
As root is now possible has anyone tried to install xposed on th H960A?
I'm wondering if the second screen fix for the Telekom V10 also works with the H960A.
What about Viper4Android and AdAway?
Click to expand...
Click to collapse
Didn't try xposed but I think it should work (if it's working on other V10 models - they are not that different). I just recently bought V10 and was disappointed in dpi, so I needed root to patch second screen to be dpi-independent.
Also: why would you want things like Viper4Android when you got really good sounding hifi dac onboard?
fixxxer102 said:
Are there any other known issues? I don`t need to install any custom roms. I need it only for root and xposed on Marshmallow. Is there something that can surprise me?
Click to expand...
Click to collapse
For sure it's enough to flash packages and get root. Xposed is independent from recovery so I can't say anything about that.
Testing are up to you guys. Don't be afraid as this phone is not easy to brick.
rudi666 said:
Also: why would you want things like Viper4Android when you got really good sounding hifi dac on board?
Click to expand...
Click to collapse
Quite simple answer. The onboard Hifi DAC only works with cable headphones. Viper4Android also supports Bluetooth devices.
rudi666 said:
I just recently bought V10 and was disappointed in dpi, so I needed root to patch second screen to be dpi-independent.
Click to expand...
Click to collapse
Could you write a small guide about the dpi change (I prefer 540-580)?
Thanks in advance.
cyvr1 said:
Quite simple answer. The onboard Hifi DAC only works with cable headphones. Viper4Android also supports Bluetooth devices.
Click to expand...
Click to collapse
Ah, you are right, that makes perfect sense. Sorry, I forgot about that.
paschalism said:
Could you write a small guide about the dpi change (I prefer 540-580)?
Click to expand...
Click to collapse
There is still a long way, right now second screen FCs are fixed, but layouts are still wrong. I don't know if I can fix it to be truly dpi-independent but I think 560 is optimal value for this screen.
Is this working with
H960a
V20a-AME-xx??
1k views and only 11 "thanks"??? Really? Guys! We need support devs! Big THANK YOU for ur hard work @rudi666. I haven't try ur method yet but I am happy with the fact that something is beginning to happen with v10
Wysłane z mojego LG-H960 przy użyciu Tapatalka
asmoroth said:
I haven't try ur method yet but I am happy with the fact that something is beginning to happen with v10
Click to expand...
Click to collapse
I did try his method and it worked like a charm. Ok, you'll have to reflash TWRP if you want to use it but I'm sure it's just a matter of time until we have permanent TWRP like th T-Mobile V10 obviously has.
Thanks to rudi666 I have root, xposed, adaway and viper4audio up and running on my V10. And as there are no interesting custom roms to flash in my opinion it does not matter that I'd need to reflash TWRP. If you plan your flashing in advance you can flash all zip files in one go. No real need for TWRP afterwards.
Thanks guys. Unfortunately I see there is not much going on in V10 scene, and it's a shame.
cyvr1 said:
Ok, you'll have to reflash TWRP if you want to use it but I'm sure it's just a matter of time until we have permanent TWRP like th T-Mobile V10 obviously has.
Click to expand...
Click to collapse
Hm.. if you follow instructions you should get permanent TWRP, just try "adb reboot recovery" to test it if you don't want to risk clearing data when using button combination. There is a file called /system/boot-from-recovery.p which is 'restoring recovery' on every boot (that's why there is an info in instruction about not rebooting your phone the first time), but after all the steps this file will be patched. I don't remember if the first use of TWRP or flashing SuperSU does it, but you should get permanent recovery. If not you can always rename this file manually.
rudi666 said:
Hm.. if you follow instructions you should get permanent TWRP, just try "adb reboot recovery" to test it if you don't want to risk clearing data when using button combination. There is a file called /system/boot-from-recovery.p which is 'restoring recovery' on every boot (that's why there is an info in instruction about not rebooting your phone the first time), but after all the steps this file will be patched. I don't remember if the first use of TWRP or flashing SuperSU does it, but you should get permanent recovery. If not you can always rename this file manually.
Click to expand...
Click to collapse
Hi,
I will try that again and see if I can get permanent TWRP. But as I said currently there is no real requirement for that. I flashed SuperSU and both files for xposed when I first booted into recovery and that is all I need at the moment.
i cant enter bootloader
h960A
after adb reboot booloader it keeb restart to soft
Hey guys,
I recently purchased a Mi5 in China and had a hellish experience trying to get a working rooted international ROM on it even though I am definitely not a noob at android. I found out that most issues I had were result of small/stupid mistakes that can be easily avoided with the proper knowledge, so I decided to write a super quick how to on the process for anyone that might need it in the future. There are similar guides out there, and I will refer to some (all credit goes to original posters) but I found that most are incomplete/not updated/plain wrong. Please also note that this guide is updated to June 20th, newer ROM versions might require different steps.
This how to assumes you are familiar with the standard ROM flashing process, in case anyone needs a more detailed explaination of some of the steps, you can reply or search XDA elsewhere, most of the stuff has been mentioned here and there before.
1. Check that your hardware is ok (dial *#*#64663#*#* in dialer, you will enter hardware test mode, check every single item carefully)
2. Request a bootloader unlock from Xiaomi, unlock the bootloader: follow instructions here http://forum.xda-developers.com/mi-5/how-to/unlocking-xiaomi-mi-5-bootloader-t3336243
3. Now that Your bootloader is unlocked, you have 3 main options for working ROMs: Xiaomi's Global Stable, Xiaomi's Global Dev, Xiaomi.eu's unofficial Stable. If you want to play it safe, I suggest to go with the Xiaomi's Global Stable, otherwise choose Xiaomi.eu's unofficial Stable. I did not test extensively all three, so this is just a general recommendation.
4. In any case, you will need to use the official Xiaomi's flashing tool (Miflash) to do your first ROM flash. Just follow the process here: http://en.miui.com/a-234.html and you'll have flashed your new ROM. In case you want to flash Xiaomi.eu's unofficial Stable, follow the same process but get the flashable ROM here: https://xiaomi.eu/community/threads/xiaomi-eu-multilang-rom-for-xiaomi-mi5-unlocked-bl-only-released.31231/
5. Boot into your newly flashed ROM, check once again that hardware is ok (see step 1.). Please also see step 10b for a tidbit of additional info if You're in China.
6. Reboot into bootloader, boot (only boot, no need to install) TWRP, which you can find here as part of Xiaomi.eu's thread above in step 4. inside a zip packaged with a modded bootloader image. do NOT install the modded bootloader image. Also, this is the only version of TWRP that I found working for my device. There are a couple more versions from chinese developers (cofface, ganfan), but booting either resulted in blank screen.
7. Once you are in TWRP, the recovery will ask you for a decryption password, just press cancel, then "Swipe to allow modifications"
8. Sideload (you cannot install from internal storage since you will not be able to access it at the moment) the latest SuperSU stable, which you can find here: http://forum.xda-developers.com/showthread.php?t=1538053. Please note that you WILL need the latest version, anything earlier might just get you a bootloop. And please do NOT format /Data to make it accessible to TWRP as that will also likely result in bootloop. Just sideload whatever you need.
9. Do NOT wipe Dalvik or Cache, reboot into System.
10. Congrats, You're done. Have a beer/coffee/tea and pat yourself on the back.
10b. In case You're in China, and this is Your first Android 5.0+ ROM, you will happen into a "bug" (it's not really a bug, but a result of China's Great Firewall), where whenever you connect to a Wifi, the phone will think you have no internet access and that will cause a whole host of issues (won't reconnect automatically, will try to default to 4G etc.). If so, just enable ADB Debugging and type adb shell "settings put global captive_portal_server httpstat.us/204" . That will mostly solve it (you might still get some weird result with some APs, but toggling Wifi should solve the problem for that AP forever.
Lazer Bear said:
6. Reboot into bootloader, boot (only boot, no need to install) TWRP, which you can find here as part of Xiaomi.eu's thread above in step 4. inside a zip packaged with a modded bootloader image. do NOT install the modded bootloader image. Also, this is the only version of TWRP that I found working for my device. There are a couple more versions from chinese developers (cofface, ganfan), but booting either resulted in blank screen.
Click to expand...
Click to collapse
How do you boot into twrp without flashing it? fastboot boot recovery.img doesn't work for me.. the command was successfull, downloading to the phone, then it's telling me booting, but the phone stay in fastboot.. thx
m_adnan said:
How do you boot into twrp without flashing it? fastboot boot recovery.img doesn't work for me.. the command was successfull, downloading to the phone, then it's telling me booting, but the phone stay in fastboot.. thx
Click to expand...
Click to collapse
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?
Lazer Bear said:
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?
Click to expand...
Click to collapse
no, nothing happens on the screen, it stays in fb mode without any reaction. adb and fb devices doesn't return any device connected.. if i do an fb reboot it told me "waiting for any device" so the only option to get it run again is to power off.. yes of course, it's the recovery.img with the modified boot.img..
Lazer Bear said:
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?
Click to expand...
Click to collapse
i want only to inform you, i get it to work.. the problem was my rom, miui 8.. for miui 8 you will need a new version of twrp, which you can download here: https://yadi.sk/d/oj6Z-0u7sXdw6 after that, i was able to boot to the twrp recovery without flashing it, so i keept everything original like it was and was able to sideload the supersu and get root without to format my data.. when you start the recovery it came in chinese, but when you click on the right button you can choose your language.. that's it.. thank you for you support dude!!
Is it only way to switch from chinese ROM to official global ROM to have unlocked bootloader? If it is, is there any other way of unlocking it, waiting 15 days to get permission seems ridiculous.
Lovely step by step guide. But, any idea if it will wipe the user data and/or internal sdcard when moving from the chinese to international version?
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 G935T Edge Odin Factory FIrmware Downloads
G935TUVU4CRI2_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
Thank you sir. Amazing is you, works great much better than safestrap and much easier to get into and out of. I hope one day im able to return the favor and help you out with something to make your life easier as you have done with countless people, much appreciated
Thank you so much for all the work you have done here and for injecting this phone with a much needed revitalization.
Now for the first dumb question, what can be flashed? ROMs? Custom Kernel? (Nethunter?) Any idea would ve helpful. Thanks again!
how to know that which version v4 or v8 on are we?
Rehan Ul Hsaan said:
how to know that which version v4 or v8 on are we?
Click to expand...
Click to collapse
The bootloader version is the 5th to last number in the build version
G935XXXX4XXXX
Sent using some kind of device I modified
gdfdedh8d said:
Thank you so much for all the work you have done here and for injecting this phone with a much needed revitalization.
Now for the first dumb question, what can be flashed? ROMs? Custom Kernel? (Nethunter?) Any idea would ve helpful. Thanks again!
Click to expand...
Click to collapse
No custom boot.img can be flashed
Sent using some kind of device I modified
jrkruse said:
The bootloader version is the 5th to last number in the build version
G935XXXX4XXXX
Sent using some kind of device I modified
Click to expand...
Click to collapse
i thinks i updated to "G935TUVS8CRJ1" can i be flash on it?
Quick question. I just used this method to root my phone (v4 bootloader, CRI2 firmware if I'm reading it right). I had been looking at the post [Rom][ALL+CARRIERS_CRF1][Stock_Oreo_Hybrid][Safestrap_Preinstalled]. That one seemed like a good deal because of the followup post on Safestrap flashable zips, like Xposed framework, Extreme Debloater, Dual Speaker, etc....
I didn't consider that ROM because of the big warning Must Be On Stock CRF1, whereas I'm on CRI2 and this looked nicer anyway.
So, just to be sure I understand, now that I've used this method to root my phone I can install all those things and more by using this technique to get into TWRP on my phone. Correct? Further, I can use TWRP in this way to flash anything except a custom bootloader. Yes?
More specifically, all those ROMs listed over in the general Tools Samsung Galaxy S7 Edge ROMs, Kernels, Recoveries, & Other Development forum that say "for G9350 only", I can use this TWRP to flash those on my G935T ?? Is that right?
Rehan Ul Hsaan said:
i thinks i updated to "G935TUVS8CRJ1" can i be flash on it?
Click to expand...
Click to collapse
Nope that's v8
jrkruse said:
Nope that's v8
Click to expand...
Click to collapse
My bad luck ?
Rehan Ul Hsaan said:
My bad luck
Click to expand...
Click to collapse
Should have been aware of what you are flashing a bootloader update is always an attempt to patch something. Usually root related. It is never to benefit the user. The first indication to me would have been a 4 version jump in bootloader versions all in one shot. I warned people all along that a bootloader change would come one of these days and kill root. Sprint seen it months ago. Tmobile and Sprint can now have there cozy little relationship with one another. I feel bad for you tmobile people. Remember when tmobile was the friendly carrier in the dev community along with sprint as well now they are the most unfriendly carrier in the dev community.
SailorJoe6 said:
Quick question. I just used this method to root my phone (v4 bootloader, CRI2 firmware if I'm reading it right). I had been looking at the post [Rom][ALL+CARRIERS_CRF1][Stock_Oreo_Hybrid][Safestrap_Preinstalled]. That one seemed like a good deal because of the followup post on Safestrap flashable zips, like Xposed framework, Extreme Debloater, Dual Speaker, etc....
I didn't consider that ROM because of the big warning Must Be On Stock CRF1, whereas I'm on CRI2 and this looked nicer anyway.
So, just to be sure I understand, now that I've used this method to root my phone I can install all those things and more by using this technique to get into TWRP on my phone. Correct? Further, I can use TWRP in this way to flash anything except a custom bootloader. Yes?
More specifically, all those ROMs listed over in the general Tools Samsung Galaxy S7 Edge ROMs, Kernels, Recoveries, & Other Development forum that say "for G9350 only", I can use this TWRP to flash those on my G935T ?? Is that right?
Click to expand...
Click to collapse
Twrp gives you no more options than you had before. You cannot just magically go flashing anything you want just because you have twrp. You can run a stock rom and mod it a little and that is it
How do you know what bootloader you're running?
i can not install this metod .
i have problem with sw. rev check faiL device, can any dody help me & please
i use OS G935TUVS8CRJ1
Does this require the fixes for lag/battery life?
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
im exactly onthis s7 verizon heroltevzw sm g930v latest firmware oreo8.0
v8 bootloader locked:laugh:
can i downgrade and follow your path,s?
if no f9vk it
then time to move on upgrade, please can you recomend me some decent device better/much better than s7 that i can root without bricked it down to paperweight?
thankyou
much appreciated
cheers
omgaruda said:
can i downgrade and follow your path,s?
if no f9vk it
then time to move on upgrade, please can you recomend me some decent device better/much better than s7 that i can root without bricked it down to paperweight?
Click to expand...
Click to collapse
No, if your build number indicates that you're on the v8 bootloader, you're screwed for now. If you like the S7's features, you can grab an Exynos. Those you can root and modify to your heart's content. Plenty of custom ROMs available. It's not too expensive either. It's what I'm going to upgrade to, since I'm tired of this bull with the bootloader, and my glass is cracked anyway. Would probably cost nearly as much to repair as to just buy an Exynos.
S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z this is a trojan
Ihavetodothis said:
S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z this is a trojan
Click to expand...
Click to collapse
That's a false positive by a single antivirus program. VirusTotal gives it clean on 54 out of 56 antivirus programs, and one of those is merely "suspicious," probably because it's a rooting tool.