[solved] bootloop - funny thing - Sony Xperia XZ2 Questions & Answers

Update (30 min) later: I tried flashtool on one of my windows 10 notebooks again, and suddenly it works (did not work before), drivers, adb, fastboot do not work but flashtool connects somehow to the phone
i was just writing a quide how i managed to unlock bootloader and root my new ZX2
i was very proud that i did (after 10 hours)!
After first boot i updated magisk, pressed reboot and now i am stuck in bootloop.
i can not boot into TWRP, i get into fastboot but booting into TWRP with "fastboot boot twrp-xz2.img"
i only have Win 10 computers, i cant get the drivers to work in Win10. So i have to do everything in a virtual linux machine.
I could install other windows versions on a computer of there is something i can only do older Windows versions.
suggestions or help would be really nice. (
at the moment i feel like throwing the phone against the wall is the best option
This is what i did (the guide i planed to post):
Virtual box →
install Zorin32 Linux in Virtual box→
Follow XDA Linux ADB Guide (https://forum.xda-developers.com/showthread.php?t=570452) →
open Terminal on Linux→
SET Password:
sudo passwd
Install Adb+Fastboot:
sudo apt-get install android-tools-adb
sudo apt-get install adb
sudo apt-get install android-tools-fastboot
sudo apt-get install fastboot
Maybe reboot computer →
Start Linux Machine →
Connect Phone in Fastboot mode→
Open Terminal→
Unlock Bootloader:
su
fastboot oem unlock <your unlock code>
first time I did this (it said OK in fastboot mode) I startet the phone and testet with *#*#7378423#*#* →it was not unloocked → So, I did:
Terminal (wile phone was on and usb debugging activatet) →
adb reboot bootloader
fastboot oem unlock <your unlock code>
fastboot oem unlock <your unlock code>
(I did it two times in a row, the second time it told me that bootloader is alreadyy unloocked)
fastboot boot twrp-xz2.img
(push phone button to start TWRP, I clicked around a bit in TWRP, than remembered that I have to factory reset and start the phone again)
Factory reset in TWRP →
start System →
activated developer options, usb debugging→
Copy magisk to Phone->
Terminal→
adb reboot bootloader
fastboot boot twrp-xz2.img
Install Magisk
I had to boot my computer and the virtual machine several times, dont know why.
I dont really understand what I did. I just followed guides and tips from other people. Credit goes to this people (MartinX3 and others)

Most likely could be the version of magisk you have installed. If you can still boot to recovery, I'd suggest to try another version of magisk, and also remember to wipe cache and dalvik in recovery before reboot as this can help alot

Pretty sure its either 18.1 or 19.4 you need to install for xz2.

Related

Help! Infinite bootloop, can't enter Recovery, and Fastboot usb doesnt work

Super noob here. I was trying to update my android revolution hd rom and somehow I screwed everything.
Do I have a chance to fix my phone or should I purchase a new one?
My unit is a HTC One m7 (sprint).
I understand that in order to fix this I need to install a new recovery (I have a CWM old version). The phone reboots in regular mode but as ROM is not working it reboots to recovery, but this doesn't work either I just see a 0,5s splash screen and the loop goes on.
I have read the "disaster recovery" thread but they assume Fastboot USB works. My problem is I dont even know how to connect my phone to my computer in order to work from there.
My bootloader is still unlocked (fortunately).
I have Hboot 1.44 should I update it?
A step-by-step dumb proof will be appreciated!
First download a toolkit for the HTC one m7. You can find it in the android development section. With that you can install a new recovery. I recommend twrp. After that push a ROM via adb to the device and flash that Rom. There are hundreds of sprint ROMs and even more threads "how to adb push"
http://forum.xda-developers.com/showthread.php?t=2265618
[GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013
Philipp_94 said:
First download a toolkit for the HTC one m7. You can find it in the android development section. With that you can install a new recovery. I recommend twrp. After that push a ROM via adb to the device and flash that Rom. There are hundreds of sprint ROMs and even more threads "how to adb push"
http://forum.xda-developers.com/showthread.php?t=2265618
[GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013
Click to expand...
Click to collapse
Thanks, downloaded this tool seems great, but my phone is not getting recognized by the system. Im using Windows 8.1
http://forum.xda-developers.com/showthread.php?t=2727913
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My drivers are installed, I have "HTC Sync Manager" installed. This is desperating.
Blocked ONE said:
Thanks, downloaded this tool seems great, but my phone is not getting recognized by the system. Im using Windows 8.1
http://forum.xda-developers.com/showthread.php?t=2727913
My drivers are installed, I have "HTC Sync Manager" installed. This is desperating.
Click to expand...
Click to collapse
First off if your running CWM and tried to install ARHD then your gonna have issues as ARHD is only compatible with TWRP recovery 2.6.3.3 or 2.7.1.1
If Windows 8 has stopped recognizing your phone and you can't boot to a Rom unfortunately there's little chance of you getting it working again.
So you have 2 good options. Get/make an otg cable and use it to install a Rom compatible with CWM.
Or create a Linux boot disk to use adb/fastboot. Linux doesn't need drivers for your phone so no detection problems then you can flash recovery or push a Rom whatever you want.
---------- Post added at 03:50 PM ---------- Previous post was at 03:27 PM ----------
Blocked ONE said:
I have read the "disaster recovery" thread but they assume Fastboot USB works. My problem is I dont even know how to connect my phone to my computer in order to work from there.
Click to expand...
Click to collapse
To use Fastboot :- boot the phone to the boot loader and select Fastboot from the menu. Then connect you phone via usb cable and Fastboot should change to fastbootusb.
Open the folder that contains adb and fast boot on your pc then hold Shift and right click on the empty white background space, from the menu that appears select "open command window here"
In the command window type
fastboot devices
If you get an output of your phone's serial no. Fastboot is working.
Danny201281 said:
First off if your running CWM and tried to install ARHD then your gonna have issues as ARHD is only compatible with TWRP recovery 2.6.3.3 or 2.7.1.1
If Windows 8 has stopped recognizing your phone and you can't boot to a Rom unfortunately there's little chance of you getting it working again.
So you have 2 good options. Get/make an otg cable and use it to install a Rom compatible with CWM.
Or create a Linux boot disk to use adb/fastboot. Linux doesn't need drivers for your phone so no detection problems then you can flash recovery or push a Rom whatever you want
To use Fastboot :- boot the phone to the boot loader and select Fastboot from the menu. Then connect you phone via usb cable and Fastboot should change to fastbootusb.
Open the folder that contains adb and fast boot on your pc then hold Shift and right click on the empty white background space, from the menu that appears select "open command window here"
In the command window type
fastboot devices
If you get an output of your phone's serial no. Fastboot is working.
Click to expand...
Click to collapse
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!
Blocked ONE said:
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!
Click to expand...
Click to collapse
Your not even close to being bricked
On Linux you will still need to install adb/fastboot but no drivers for your phone needed. As long as adb is working your on a winner
Also you will need to add sudo at the beginning of each command
E.g "adb devices" becomes " sudo adb devices" or "fastboot flash recovery" becomes " sudo fastboot flash recovery"
Blocked ONE said:
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!
Click to expand...
Click to collapse
Danny201281 said:
Your not even close to being bricked
On Linux you will still need to install adb/fastboot but no drivers for your phone needed. As long as adb is working your on a winner
Also you will need to add sudo at the beginning of each command
E.g "adb devices" becomes " sudo adb devices" or "fastboot flash recovery" becomes " sudo fastboot flash recovery"
Click to expand...
Click to collapse
also Sprint has a different partition structure you CANNOT use files for a GSM phone on yours ...please go to the sprint forums for the files and help you need
Sirs, ubuntu doesnt recognize it either!
While on the bootloop it says system can't mount the Android unit. This means the USB is working.
But on the bootloader/fastboot it doesn't even pop up this message, its like nothing is plugged. WTF I think it is bricked, can't connect anywhere. I feel stupid just trashed my phone for a non important ROM update.
Blocked ONE said:
Sirs, ubuntu doesnt recognize it either!
While on the bootloop it says system can't mount the Android unit. This means the USB is working.
But on the bootloader/fastboot it doesn't even pop up this message, its like nothing is plugged. WTF I think it is bricked, can't connect anywhere. I feel stupid just trashed my phone for a non important ROM update.
Click to expand...
Click to collapse
you need to calm down
first turn the phone off
hold power plus volume down
when the phone goes off keep holding volume down and let go of power
now your in the bootloader
use the volume key to select bootloader then power off
now wait
now hook the phone to the usb and hit power plus volume down
let go of both when you see the bootloader again
now your in fastboot USB
now you can flash the correct recovery to your phone.
next you need this >> http://forum.xda-developers.com/showthread.php?t=2658910
clsA said:
you need to calm down
first turn the phone off
hold power plus volume down
when the phone goes off keep holding volume down and let go of power
now your in the bootloader
use the volume key to select bootloader then power off
now wait
now hook the phone to the usb and hit power plus volume down
let go of both when you see the bootloader again
now your in fastboot USB
now you can flash the correct recovery to your phone.
next you need this >> http://forum.xda-developers.com/showthread.php?t=2658910
Click to expand...
Click to collapse
I followed your instructions but the device doesn't show up in Ubuntu.
But if I try to boot in regular mode, it shows! "Android Phone". The problem is I can't access this, since it just appears for some seconds because this is during the bootloop. Anyway during these seconds, if I click on "Android Phone" it says it cant access it... This is confusing.
I tried both USB 3.0 and 2.0 since I have read 3.0 has problems sometimes.
Should I install any kind of drivers on Ubuntu?
Blocked ONE said:
I followed your instructions but the device doesn't show up in Ubuntu.
But if I try to boot in regular mode, it shows! "Android Phone". The problem is I can't access this, since it just appears for some seconds because this is during the bootloop. Anyway during these seconds, if I click on "Android Phone" it says it cant access it... This is confusing.
I tried both USB 3.0 and 2.0 since I have read 3.0 has problems sometimes.
Should I install any kind of drivers on Ubuntu?
Click to expand...
Click to collapse
From @nkk71 Superguide
5) Q: How do I create a Linux Live USB
Windows users: http://click.xda-developers.com/api...ww.ubuntu.com/download/deskt...ick-on-windows
Mac users: http://www.ubuntu.com/download/deskt...ick-on-mac-osx
Ubuntu 12.04 LTS 32bit ISO from here: http://www.ubuntu.com/download/desktop
Once the Ubuntu Live USB is ready, shutdown your computer and restart from the USB
No need to install, just use the "Try Ubuntu" option
open a terminal
and install adb & fastboot using (copy/paste 1 line at a time into terminal):
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
you can then check version, by typing "adb version"
and check connection using "adb devices" in custom recovery or booted phone
and "sudo fastboot devices" in bootloader
you can also check @tobesedated guide for more info: [Guide]Suggestion For S-off On 1.55 HBoot Using Ubuntu---Step by step with pictures
Click to expand...
Click to collapse
OK i think im making some progress!!
I am running this ubuntu from USB, installed adb and fastboot, and I think its connected now. At console I type "fastboot devices" and it says: "HT359W90.... fastboot"
Then I downloaded the TWRP 2.7.1.1 and flashed it. Finally I rebooted the phone and now it enters recovery!!!!!! :good: Im now sure the one is not dead!! Thank you so much guys.
Now what? Should I make a factory reset or just go ahead and flash the ROM I intended to get? Don't want to screw it again...
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory". And from phone, the ADB Sideload feature doesnt work either, it gest stuck at "starting ADB sideload feature" even after 15 minutes...
Blocked ONE said:
OK i think im making some progress!!
I am running this ubuntu from USB, installed adb and fastboot, and I think its connected now. At console I type "fastboot devices" and it says: "HT359W90.... fastboot"
Then I downloaded the TWRP 2.7.1.1 and flashed it. Finally I rebooted the phone and now it enters recovery!!!!!! :good: Im now sure the one is not dead!! Thank you so much guys.
Now what? Should I make a factory reset or just go ahead and flash the ROM I intended to get? Don't want to screw it again...
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory". And from phone, the ADB Sideload feature doesnt work either, it gest stuck at "starting ADB sideload feature" even after 15 minutes...
Click to expand...
Click to collapse
Ok so you have usb Linux working that's great.
What method did you use to install adb/fastboot? Hopefully it was the Webupd8 repository install as this makes life easy.
Danny201281 said:
Ok so you have usb Linux working that's great.
What method did you use to install adb/fastboot? Hopefully it was the Webupd8 repository install as this makes life easy.
Click to expand...
Click to collapse
Yes I followed the method quoted by clsA
Make sure your Rom is compatible with Sprint then to push it to the phone do this.
Boot your Linux usb stick and select the try ubuntu option. Wait for the desktop to load. Open the Home folder. In the top left you should see other drives connected to your pc. Go into your hdd and copy the Rom to the Home folder of the Linux usb and rename it rom.zip.
Now reboot computer, and Wait for it to return to the try/install ubuntu screen. And press
Control + alt + F1 (this will take you to main Linux terminal)
Boot your phone into recovery and connect with usb and type
adb devices (to check phone is detected if phone is not detected see below)
Then
adb push rom.zip /sdcard
If phone is not detected type the following 3 commands waiting for each to complete there out put. Be patient it may seem stuck at some points and you may see some errors but just wait for the terminal to return to normal after each command I.E ready to accept another command. Once all 3 commands have completed try adb devices again.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Danny201281 said:
Make sure your Rom is compatible with Sprint then to push it to the phone do this.
Boot your Linux usb stick and select the try ubuntu option. Wait for the desktop to load. Open the Home folder. In the top left you should see other drives connected to your pc. Go into your hdd and copy the Rom to the Home folder of the Linux usb and rename it rom.zip.
Now reboot computer, and Wait for it to return to the try/install ubuntu screen. And press
Control + alt + F1 (this will take you to main Linux terminal)
Boot your phone into recovery and connect with usb and type
adb devices (to check phone is detected if phone is not detected see below)
Then
adb push rom.zip /sdcard
If phone is not detected type the following 3 commands waiting for each to complete there out put. Be patient it may seem stuck at some points and you may see some errors but just wait for the terminal to return to normal after each command I.E ready to accept another command. Once all 3 commands have completed try adb devices again.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
Ubuntu crashes whenever I press Ctrl+Alt+F1, tried twice and had to reboot.
I was using Ctrl+Alt+T for opening a console. Already did all those 3 commands but not working. This seems challenging! I have read something about 32-bits instructions needed for this? Im running under a 64bit computer and 64 bit linux distribution.
By the way a friend has got an OTG cable, would this work to get a ROM inside the SD-Card?
Blocked ONE said:
Ubuntu crashes whenever I press Ctrl+Alt+F1, tried twice and had to reboot.
I was using Ctrl+Alt+T for opening a console. Already did all those 3 commands but not working. This seems challenging! I have read something about 32-bits instructions needed for this? Im running under a 64bit computer and 64 bit linux distribution.
By the way a friend has got an OTG cable, would this work to get a ROM inside the SD-Card?
Click to expand...
Click to collapse
You should be using 32bit Linux it will run ok on a 64bit machine. But with 64bit Linux you will need to install 32bit libs I think.
Yes an otg cable can be used to copy the Rom to the phone
It's weird that you had Fastboot working but adb won't though. Try using adb without the sudo prefix. It should be working if Fastboot is. But remember you must be in recovery to use adb. Not the bootloader.
Fastboot = bootloader
Adb = recovery
Blocked ONE said:
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory".
Click to expand...
Click to collapse
Ok slight brain fart on my part lol. The error you got implies that adb is working but your Rom is not in the right place.
You can put the Rom in the home folder and use the adb push command from the terminal as it is when opened.
Or if the Rom is for instance in the downloads folder you must first use
cd Downloads (to take the terminal to the downloads folder)
Then adb push
More problems lol
Apparently I can't flash any ROM because it says I cant mount cache, data nor internal storage.
Im on TWRP 2.7.1.1
Blocked ONE said:
More problems lol
Apparently I can't flash any ROM because it says I cant mount cache, data nor internal storage.
Im on TWRP 2.7.1.1
Click to expand...
Click to collapse
So you've got the Rom on the phone but when go To recovery you can't see the rom because of this error?
It's normal to see these type of errors after using fastboot erase cache. But not normally with internal storage.
If you can see the Rom just flash it it should work.

[ROOT][UNLOCK BOOTLOADER][CUSTOM RECOVERY][TUTORIAL] Root Android One using Linux

Hello everyone,
I wrote this walkthrough to show you how to unlock the bootloader,install custom recovery and gain root privileges on your Android One by using Linux.
Some of the instructions in this guide are not mandatory to accomplish the task but I decided to include them anyway just for informational purposes because this guide is intended for novice users.
This is my personal method and I will provide you with detailed information to avoid mistakes so read carefully and have fun.
Requisites:
*Backup your data before proceeding!
*Android One
*A Linux distro (Debian/Ubuntu/Mint/ElementryOS or etc)
*android_one_root.zip (Download it from http ://goo.gl/B3LjRJ ) [Note: Remove spaces from the link ]
Let's begin.
Chapter 1: Developer options, Android debugging & Android Tools
​
Phase 1: Developer options and Android debugging.
Go to Settings > About phone and tap 7 times on Build number to enable Developer options. You will see a little pop-up that says "You have enabled development settings!".
Go back to Settings menu and scroll down to Developer options. Tap on it and then enable Android debugging. You will be asked to allow USB Debugging, confirm by tapping on OK.
​
Phase 2: Installing Android tools (ADB & Fastboot) on Linux. (I'm using Ubuntu 15.04 here)
Open Terminal and run this command to install ADB and Fastboot tools:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Chapter 2: Unlock the bootloader.
​
In this chapter we will focus on the Linux Terminal rather than the phone. Don't be scared, it will be easy enough and you will have the opportunity to learn something new. :fingers-crossed:
Now you can connect your Android One phone to your computer.
Once your phone has been connected to your pc, open the Terminal and run this command:
Code:
adb devices
​
Check the phone. Your computer's RSA fingerprint will be shown and you will be asked to allow USB debugging. Confirm by tapping on OK.
​
Note: If you see offline instead of device, run the adb devices command once again.
If adb devices output looks like this:
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
???????????? no permissions
Run these commands:
Code:
sudo adb kill-server
sudo adb start-server
sudo adb devices
Put yourphone in Fastboot Mode by running this command:
Code:
adb reboot-bootloader
EASY WAY: You can put your phone in Fastboot Mode by holding down Power button and Volume up simultaneously for few seconds (it works either phone on or off).
Commands in Fastboot Mode need Administrator privileges on your pc, that's why we will use sudo.
Run this command to make sure that Fastboot Mode is working correctly:
Code:
sudo fastboot devices
​
Next command will unlock the bootloader:
Code:
sudo fastboot oem unlock
The phone will reboot and it will restore factory settings. All personal data and settings will be lost.
Once the reboot is complete, download & extarct the "android_one_root.zip" file to your pc.Now copy both "eu.chainfire.supersu.apk" and "update.zip" file to your phones sd card.Then install "eu.chainfire.supersu.apk" in your phone.
Then put the device back in Fastboot Mode by holding down Power button and Volume up simultaneously for few seconds (it works either phone on or off).
Chapter 3: Install Custom Recovery.​
You will find three custom recovery in the archive.Choose one of them. (I'm using TWRP here)
So put the recovery's .img file on your pc's Desktop.
On Terminal, change the current working directory by running this command: (Change Desktop to ypur current working directory)
Code:
cd Desktop
nstall TWRP Recovery by running this command: (If you want to flash CWM/PHILZ recovery,just replace TWRP.img to CWM.img/PHILZ.img )
Code:
sudo fastboot flash recovery TWRP.img
Now it's time to enter Recovery Mode. To do that, hold down Power button and Volume up.
In TWRP Recovery tap on Install, scroll down to the update.zip archive and select it. Perform a swipe to confirm the installation and lastly reboot your phone.
Once the reboot is complete, go to google play store and install "Root Checker" to check your device root status.
Congratulations, you made it!
If you are using phliz recovery mode
before install custom recovery format userdata
code
sudo fastboot format userdata
otherwise it will stuck in recovery mode

Fastboot drivers not working - what to do?

I recently sold my HTC One M7 and I'm trying to take it back to stock. I followed the instructions on HERE to go back to stock and got to the point of flashing the appropriate RUU.zip, but during the flashing process the phone lost USB connectivity to my Windows 10 (tried 7 as well) PC and failed. I can see that it at least reverted the HBOOT from 1.54 to 1.44. I can still boot the phone all the way up into ARHD 93.0, it's still showing it has the latest firmware installed (7.19.401.51) and latest TWRP recovery (2.8.7.0), but if it keeps disconnecting from USB when I go into Fastboot how am I supposed to do anything?? I mean, I can't even flash back to a newer HBOOT without Fastboot working.... right?
/EDIT
Well, it's some kind of Windows driver issue, but hell if I can fix it. Under Device Manager on my Windows PC it says Android USB Devices > My HTC but it has a YELLOW triangle on it indicating it's not recognized. I've tried uninstalling the driver and doing some other things but I cannot for the life of me get it to recognize it properly on either Windows 10 or 7. Please help! I seriously don't understand why this is all of the sudden messed up.
Maybe not the simplest solution, but it is A solution if drivers are truly the problem-- use Linux-- no need for drivers. You can run it within Windows using Virtual Box (or install it on your hard drive alongside windows on a separate partition, but that might be a bit drastic just to use fastboot). The ISO files are available to download for free-- most recommend Ubuntu, I like Linux Mint, personally.. once you have the OS installed (whether it's in Virtual Box or your hard drive), all you have to do to install ADB and Fastboot is open a terminal window and type:
$ sudo apt-get install android-tools-adb (for adb; use android-tools-fastboot to install fastboot)
OR
$ su
# apt-get install android-tools-fastboot (or adb)
Then they are installed and ready to be used.. no drivers needed, no need to be in the directory containing the files-- just plug in your device and open a terminal window and you're good to go. Occasionally you will need to kill the server to get adb to recognise your device. Fastboot should always work. If fastboot returns with "no permissions," try running as root (or using "sudo fastboot).
Thanks, I forgot to post back here yesterday but that's effectively what I did except I used a Mac and everything went smoothly... stupid Windows

How to unlock, TWRP, root, etc from OSX Mavs - MacBook Air

somehow I managed to install the OTA MM update that I was holding off until I could unlock, root, blah, blah, blah.
I'm now on 20i.
And it responds to adb (v1.032) and fastboot commands from Terminal on my OSX MacBook Air.
Has anyone "authorized" (aka - fastboot oem unlock) their 811 and flashed TWRP from a Mavs Mac ?
Or do I need to go to my Bootcamp partition to accomplish?
Seems like to should work from Mavs direct, but …….
Bootcamp not needed.
system settings (tap on Build number until it says you’re a developer.)/developer/check oem unlock & USB debug
USB connect to Mac. I use Android File Transfer. I found it less annoying and very fast.
But it will not work with the LG drivers installed. aka LGUnitedMobileMacDriver_v4.23.zip, or LGMobileMacDriver_v5.2.zip, or LGBridge_Mac.dmg.
in Terminal:
adb devices - should reveal the devices serial - LGH811xxxxxxxxx. If not, your Mac and adb/fastboot are not set up properly.
adb reboot bootloader
fastboot devices - should reveal serial again. xxxxxxxx
fastboot oem unlock - this will WIPE the G4s internal SD that comes with the phone.
fastboot getvar unlocked - to confirm unlock
fastboot reboot - and set-up as a new device.
If you're on MM, and you set it up previously, restore should happen automatically upon reboot, after you enter your google or ID, etc.
If it seems to be taking too long, restart.
Make sure you recheck that USB debug is checked in developer options.
and then to flash TWRP and SuperSu so as to root.
Terminal:
adb reboot bootloader
fastboot boot (drag and drop the {I shortened the name of the file after duping} twrp.img into the Terminal window)
This will boot you into a temporary TWRP recovery. (v2.8.7.2)
Install twrp.img (select zip or img button bottom right)
Then install SuperSu 2.6.7.zip.
REBOOT SYSTEM
check root -
Terminal:
adb shell. should get #. if not - su. should get #.
troubleshooting.
May have to re-enter developer mode
sys settings/about/software/more/tap build number 7 times fast.
unplug USB.
Toggle USB debugging in Developer. Should get prompt about RSA.
re-plug USB
adb kill-server
adb devices
If TWRP isn't recognizing your b.u., write a new back-up. This creates the path TWRP wants to see. Copy your old b.u. into the new folder:
TWRP/BACKUPS/LGH811#########/2016-10-23--15-58-36_MRA58K
RenameÂ*the old b.u. the same as the new b.u. and toss the new one.
Reboot Recovery and you now should now able to to restore from the old b.u.

Rooted with kingroot and replaced with SuperSu, TWRP and Xposed

Hi everyone. My aim here is to present a more clear Tutorial... not sure if i'll succeed, but i want to try. :good: Good Luck. Your results may be different.
A word of Caution: These steps will soft brick the phone and erase all data from your phone. Proceed with caution.
A huge thanks to:
emowing
quyvinh
jemmini
John Hale
kingroot
I refered to these posts when I was rooting:
http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
Download the BLU Vivo XL Backup from https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip . This is required to unbrick the phone.
WARNING: THE METHOD I FOLLOWED WILL ERASE ALL DATA ON THE PHONE. I really didn't care for the data on the phone so I didn't create a backup. You could google for steps to make a backup before continuing.
I did these on a Windows 7 machine. I didn't take any screenshots. This was totally random effort.
1. Ensure ADB Universal Drivers, adb.exe and fastboot.exe are installed. Use google search. I used this one http://rootjunkysdl.com/?device=Amazon Fire 5th gen. Even though it is for Amazon 5th gen Fire tablet, it worked for BLU Vivo XL
2. Enable 'Developer Options'
3. Enable 'USB Debugging'
4. Connect the phone to the computer.
If you are doing this for the first time then...​
The phone will show up as a new 'cd' drive
Open that and you should see the software to install official drivers for the phone
Install the drivers using that software.
If you have previously connected the phone then it will show up like a 'USB flash storage' device with 2 partitions - Phone and SD Card​5. Run 'adb.exe' in command prompt ( i assume you know how to do this)
6. Run adb devices and make sure that adb is able to communicate with the phone.
At some point, there will be a pop up on the phone with a key to enable the computer to securely connect to the phone. I don't know what this is called , but it is needed. Make sure you choose to remember this key permanently on the phone.​
7. Root the phone with 'Kingroot' (Yes, this is odd, but this is required to get the TWRP recovery to load)
The reason i say this is needed is because without the root when I tried to install the TWRP recovery i got the error saying that there is no root access and therefore TWRP recovery file cannot be copied to the phone​
[a] go to kingroot (dot) net and get the latest kingroot apk
try to root with kingroot. the first time i did this it didn't work. kingroot app said there is 'root' method available but it couldn't root.
[c] i uninstalled kingroot
[d] then i installed purify from play store
[e] rebooted the phone
[f] installed kingroot again and tried root again and this time it worked. (go figure...)
[g] so YMMV.
if you rooted successfully with Kingroot, then you can continue, otherwise.... try again till you can root with kingroot
​
8. reboot the phone
9. Go to developer options and enable the option - 'Enable OEM Unlock'
CAUTION: The next steps will soft brick your phone.
10. Run adb.exe. check connectivity using command 'adb devices'
11. Run command 'adb reboot bootloader' (this will put the phone in fastboot mode)
12. Make sure the TWRP recovery is in the same folder as the adb.exe file. (get the twrp recovery from here http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601)
13. Run command 'fastboot oem unlock'. At this point, there will be a prompt on the phone to confirm the action. Read it carefully, it clearly says that this process will wipe all data.
14. Press 'volume up' on the phone to confirm. It should take a few seconds. Then the phone will become unresponsive. Pressing volume up/down buttons or power button doesn't do anything.
15. Run command 'fastboot reboot-bootloader'
16. Run command 'fastboot flash recovery recovery.img'
17. Run command 'fastboot reboot'. When the phone is rebooting press volume up. If everything went well, This will put the phone in TWRP recovery mode.
18. When the phone enters TWRP recovery mode, it'll ask for 'write permissions'. I swiped to enable the write permissions.
19. At this point, the phone has no OS.
20. On the PC, extract the files downloaded from https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip
21. With the phone connect to the PC and adb running. Run command adb devices. The phone must be listed as 'xxxxxxxxxxxxxxxxx recovery'
22. You will have to push the back up files to twrp backup using adb
23. The general command is 'adb push <local> <remote>'. This is what i did for each of the files. Be patient, this will take time.
adb push "C:\boot.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/boot.emmc.win
adb push "C:\logo.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/logo.emmc.win
adb push "C:\logo.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/logo.emmc.win.md5
adb push "C:\nvram.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/nvram.emmc.win
adb push "C:\nvram.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/nvram.emmc.win.md5
adb push "C:\secro.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/secro.emmc.win
adb push "C:\secro.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/secro.emmc.win.md5
adb push "C:\system.ext4.win000" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win000
adb push "C:\system.ext4.win000.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win000.md5
adb push "C:\system.ext4.win001" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win001
24. Once all the files are copied to the phone. Go to TWRP Restore option and then do a restore from the backup you just uploaded 2016-03-05.
25. After the restore is successfull and complete, TWRP will automatically ask to install 'SuperSu'.
26. Choose 'yes' and install SuperSu
27. TWRP will recover the phone and root the phone with SuperSu
If all of the above worked then install Xposed as per instructions in http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
GOOD LUCK !!! :good::good::good:
Please help me on rooting my Blu vivo XL I upgraded it to Android 6.0 and now it does not root. Please help.
hamilLewiston said:
Hi everyone. My aim here is to present a more clear Tutorial... not sure if i'll succeed, but i want to try. :good: Good Luck. Your results may be different.
A word of Caution: These steps will soft brick the phone and erase all data from your phone. Proceed with caution.
A huge thanks to:
emowing
quyvinh
jemmini
John Hale
kingroot
I refered to these posts when I was rooting:
http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
Download the BLU Vivo XL Backup from https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip . This is required to unbrick the phone.
WARNING: THE METHOD I FOLLOWED WILL ERASE ALL DATA ON THE PHONE. I really didn't care for the data on the phone so I didn't create a backup. You could google for steps to make a backup before continuing.
I did these on a Windows 7 machine. I didn't take any screenshots. This was totally random effort.
1. Ensure ADB Universal Drivers, adb.exe and fastboot.exe are installed. Use google search. I used this one http://rootjunkysdl.com/?device=Amazon Fire 5th gen. Even though it is for Amazon 5th gen Fire tablet, it worked for BLU Vivo XL
2. Enable 'Developer Options'
3. Enable 'USB Debugging'
4. Connect the phone to the computer.
If you are doing this for the first time then...​
The phone will show up as a new 'cd' drive
Open that and you should see the software to install official drivers for the phone
Install the drivers using that software.
If you have previously connected the phone then it will show up like a 'USB flash storage' device with 2 partitions - Phone and SD Card​5. Run 'adb.exe' in command prompt ( i assume you know how to do this)
6. Run adb devices and make sure that adb is able to communicate with the phone.
At some point, there will be a pop up on the phone with a key to enable the computer to securely connect to the phone. I don't know what this is called , but it is needed. Make sure you choose to remember this key permanently on the phone.​
7. Root the phone with 'Kingroot' (Yes, this is odd, but this is required to get the TWRP recovery to load)
The reason i say this is needed is because without the root when I tried to install the TWRP recovery i got the error saying that there is no root access and therefore TWRP recovery file cannot be copied to the phone​
[a] go to kingroot (dot) net and get the latest kingroot apk
try to root with kingroot. the first time i did this it didn't work. kingroot app said there is 'root' method available but it couldn't root.
[c] i uninstalled kingroot
[d] then i installed purify from play store
[e] rebooted the phone
[f] installed kingroot again and tried root again and this time it worked. (go figure...)
[g] so YMMV.
if you rooted successfully with Kingroot, then you can continue, otherwise.... try again till you can root with kingroot
​
8. reboot the phone
9. Go to developer options and enable the option - 'Enable OEM Unlock'
CAUTION: The next steps will soft brick your phone.
10. Run adb.exe. check connectivity using command 'adb devices'
11. Run command 'adb reboot bootloader' (this will put the phone in fastboot mode)
12. Make sure the TWRP recovery is in the same folder as the adb.exe file. (get the twrp recovery from here http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601)
13. Run command 'fastboot oem unlock'. At this point, there will be a prompt on the phone to confirm the action. Read it carefully, it clearly says that this process will wipe all data.
14. Press 'volume up' on the phone to confirm. It should take a few seconds. Then the phone will become unresponsive. Pressing volume up/down buttons or power button doesn't do anything.
15. Run command 'fastboot reboot-bootloader'
16. Run command 'fastboot flash recovery recovery.img'
17. Run command 'fastboot reboot'. When the phone is rebooting press volume up. If everything went well, This will put the phone in TWRP recovery mode.
18. When the phone enters TWRP recovery mode, it'll ask for 'write permissions'. I swiped to enable the write permissions.
19. At this point, the phone has no OS.
20. On the PC, extract the files downloaded from https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip
21. With the phone connect to the PC and adb running. Run command adb devices. The phone must be listed as 'xxxxxxxxxxxxxxxxx recovery'
22. You will have to push the back up files to twrp backup using adb
23. The general command is 'adb push <local> <remote>'. This is what i did for each of the files. Be patient, this will take time.
adb push "C:\boot.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/boot.emmc.win
adb push "C:\logo.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/logo.emmc.win
adb push "C:\logo.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/logo.emmc.win.md5
adb push "C:\nvram.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/nvram.emmc.win
adb push "C:\nvram.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/nvram.emmc.win.md5
adb push "C:\secro.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/secro.emmc.win
adb push "C:\secro.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/secro.emmc.win.md5
adb push "C:\system.ext4.win000" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win000
adb push "C:\system.ext4.win000.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win000.md5
adb push "C:\system.ext4.win001" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win001
24. Once all the files are copied to the phone. Go to TWRP Restore option and then do a restore from the backup you just uploaded 2016-03-05.
25. After the restore is successfull and complete, TWRP will automatically ask to install 'SuperSu'.
26. Choose 'yes' and install SuperSu
27. TWRP will recover the phone and root the phone with SuperSu
If all of the above worked then install Xposed as per instructions in http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
GOOD LUCK !!! :good::good::good:
Click to expand...
Click to collapse
..
is this post is about rooting on marshmallow or on lollipop? thank you
Yes
Sent from my chronos_ace using XDA Free mobile app
Yes, is it for marshmallow? Or yes, is it for lollipop? Or does it work for both? Please clarify.
Please help ME my phone vivo v 5 plus root How To
Gungho-sd said:
Yes, is it for marshmallow? Or yes, is it for lollipop? Or does it work for both? Please clarify.
Click to expand...
Click to collapse
From what I've read this would only work for Lollipop, as apparently kingroot no longer works on Marshmallow.

Categories

Resources