Database Develop

Xperia T not rooting?

Hello forums!
Well, this my be a noob-like question, or not, I have no idea. So, here it goes...
My Sony Xperia T does not want to be rooted no matter what method I use. Bootlocker unlock is not allowed, but I have seen many root when they have this too, so it's not that causing the problem.
I used DoomLord's rooting toolkit first of all, to be told by the application that my phone LT30p is not accepted, even though the root includes that phone...
I then used Bin4ry's root with restore, and once again, that didn't work. I was taken to the service menu and had to click on Display, but that didn't work. The rooting toolkit just didn't do anything, just sat there...
Then I tried SRS Root, and that didn't work either.
I have PC companion, and I have USB Debugging and Unknown sources all enabled AND I have the ADB drivers... what is the problem!
This has been bugging me for a long time, I could do with some help!
Thanks in advance,
Joe.

Install ADB Driver first -_-
What is your OS on PC ?

Yenkazu said:
Install ADB Driver first -_-
What is your OS on PC ?
Click to expand...
Click to collapse
Yeah I have installed the ADB Driver, and I am running Windows 8.

CommandoOS said:
Yeah I have installed the ADB Driver, and I am running Windows 8.
Click to expand...
Click to collapse
Known issue, ADB driver cannot working under Windows 8
Just switch to older OS
Or find another PC without Windows 8 inside
XD

Yenkazu said:
Known issue, ADB driver cannot working under Windows 8
Just switch to older OS
Or find another PC without Windows 8 inside
XD
Click to expand...
Click to collapse
Aweeeeesome!
Thanks man, let me go test this on my laptop!

Okay, new problem. On my laptop, I have installed PC Companion, the device drivers have installed but now, when I try to add adb drivers it will not let me, and when I use the ADB Installer, it is not recognizing my device.

CommandoOS said:
Okay, new problem. On my laptop, I have installed PC Companion, the device drivers have installed but now, when I try to add adb drivers it will not let me, and when I use the ADB Installer, it is not recognizing my device.
Click to expand...
Click to collapse
Try disable any antivirus or similar program like that
Don't use non specific ADB driver
I guess, installing PCC it's enough
Btw, I never use any Sony software now
The best ADB driver you can find, by using ADB driver from flashtool
XD

Okay well, I got the drivers working (thanks to you) but...
dom...dom. doooooooooooom!
Still not working. For example, when using Bin4ry's root, I get to the part where you have to sit on service tests>display and nothing happens, and after about 10 minutes, it simply says root failed in console, but device does restart, but is not rooted.

CommandoOS said:
Okay well, I got the drivers working (thanks to you) but...
dom...dom. doooooooooooom!
Still not working. For example, when using Bin4ry's root, I get to the part where you have to sit on service tests>display and nothing happens, and after about 10 minutes, it simply says root failed in console, but device does restart, but is not rooted.
Click to expand...
Click to collapse
I had same problem as you
I installed flashtool then installed all driver, and i used the root thing on flashtool and it worked perfectly

CommandoOS said:
Okay well, I got the drivers working (thanks to you) but...
dom...dom. doooooooooooom!
Still not working. For example, when using Bin4ry's root, I get to the part where you have to sit on service tests>display and nothing happens, and after about 10 minutes, it simply says root failed in console, but device does restart, but is not rooted.
Click to expand...
Click to collapse
Don't use Binary method
Using Doomlord easy root
What the Build number your current OS ?

Yeah I have tried that, even though it clearly says that the Xperia T can be used with it:

Hi, I recently got a Xperia T and couldn't get it to root.
After messing around I finally got it to Root. What I had to do was use Bin4ry's root method first choosing option 2.
Once that was done, I then had to use Doomlord's easy root. After that was done I ran SU which deleted the version from Bin4ry's root and success, my phone was rooted.
I don't know why I have to use Bin4ry's method and the Dommlord's but I do know the only way to get my phone to root is by doing both root methods starting with Bin4ry's first.
I know for a fact this is the case because I re-flashed my phone to stock, trying different methods, in different orders. The only way to get it to root was to do Bin4ry's and then Doomlord's one after the other.

Tried it, it didn't work for me Thanks anyway dude.

CommandoOS said:
Tried it, it didn't work for me Thanks anyway dude.
Click to expand...
Click to collapse
Sorry Mate
Just use this
http://forum.xda-developers.com/showthread.php?t=2378400

I already am running that firmware?

CommandoOS said:
I already am running that firmware?
Click to expand...
Click to collapse
It's a little different
Already rooted
=)
Just find what suitable for you
Odexed or Deodexed

How do I add it. I am new to this, I understand I must seem like a noob but I guess everyone has to start somewhere.
Could you please tell me how I can add it safely?

CommandoOS said:
How do I add it. I am new to this, I understand I must seem like a noob but I guess everyone has to start somewhere.
Could you please tell me how I can add it safely?
Click to expand...
Click to collapse
you must downgrade to JB firmware that can be rooted using Binary or Doomlord method
After that, root, install CWM for locked bootloader
Then, follow instruction from the OP ( link above )
Just Google if you need more information

Yes but how can I downgrade? What do I need to do? I have looked for tutorials, I can't seem to find any.

CommandoOS said:
Yes but how can I downgrade? What do I need to do? I have looked for tutorials, I can't seem to find any.
Click to expand...
Click to collapse
All in One Thread
Just find what info you need
http://forum.xda-developers.com/showthread.php?t=1903137

[Q] Update witout PC

Hello,
Maybe this has already been answered, but does anyone know if it's possible to flash an updated radio.img, system.img, bootoader.img and boot.img? I'm a bit of a noob, and I want to upgrade my Nexus 6 to 5.1 once the factory images are released (and the modified boot.img to remove encryption). However, I'd like to do this without the use of a computer. I would use the Nexus Root Toolkit, but for some reason my PC no longer recognizes my device (even though I've tried EVERYTHING to fix, including different cables, ports, drivers, restarts etc.). Maybe the 5.1 update will fix, but I think I have a faulty micro usb port on the device.
I don't want to wipe my data or lose root, which is why I would only update the above images. I thought it could be done through Flashify, but the dev said I'd have to flash an entire .zip through TRWP, but I need the files along with the correct commands. I would lose root, but would use the Towelroot apk to get it back.
Please let me know if this is correct or if I'm missing something. Or if there is an easier way (like maybe Nexus Update Checker).
Thanks

ryan4a said:
Hello,
Maybe this has already been answered, but does anyone know if it's possible to flash an updated radio.img, system.img, bootoader.img and boot.img? I'm a bit of a noob, and I want to upgrade my Nexus 6 to 5.1 once the factory images are released (and the modified boot.img to remove encryption). However, I'd like to do this without the use of a computer. I would use the Nexus Root Toolkit, but for some reason my PC no longer recognizes my device (even though I've tried EVERYTHING to fix, including different cables, ports, drivers, restarts etc.). Maybe the 5.1 update will fix, but I think I have a faulty micro usb port on the device.
I don't want to wipe my data or lose root, which is why I would only update the above images. I thought it could be done through Flashify, but the dev said I'd have to flash an entire .zip through TRWP, but I need the files along with the correct commands. I would lose root, but would use the Towelroot apk to get it back.
Please let me know if this is correct or if I'm missing something. Or if there is an easier way (like maybe Nexus Update Checker).
Thanks
Click to expand...
Click to collapse
first off, towelroot doesnt work in android 5.0+. 2ndly, if you are planning on flashing the official 5.1, you need a computer. if you are planning on updating a custom rom, and you have twrp recovery, download the rom and flash it via twrp.

simms22 said:
first off, towelroot doesnt work in android 5.0+. 2ndly, if you are planning on flashing the official 5.1, you need a computer. if you are planning on updating a custom rom, and you have twrp recovery, download the rom and flash it via twrp.
Click to expand...
Click to collapse
Thanks. I don't have a custom ROM. So I guess I'll wait for one to get updated, then install it. Like I said, using a computer is not an option

ryan4a said:
Thanks. I don't have a custom ROM. So I guess I'll wait for one to get updated, then install it. Like I said, using a computer is not an option
Click to expand...
Click to collapse
thats the easiest way. i dont own a computer nor laptop, so i try to do everything from the phone. but its easier to update via recovery anyways. one thing though, since you are on the stock rom, you will have to wipe your data before flashing a custom rom, since the majority are aosp based, and wont flash over stock.

Before you give up, try a different computer (preferably running Linux), or booting the one you have on a livecd/usb.
If the USB plug on the phone is, in fact, broken, try calling motorola. The phone is still under warranty....

doitright said:
Before you give up, try a different computer (preferably running Linux), or booting the one you have on a livecd/usb.
If the USB plug on the phone is, in fact, broken, try calling motorola. The phone is still under warranty....
Click to expand...
Click to collapse
Thanks. I've tried on multiple computers (PC & Mac, but not Linux). Nothing works. I originally thought it was one of the modifications I made to the device, like root, unlock, custom boot.img, custom recovery, modified build.prop, etc. The more I search, the more I think it's hardware. I'd like to not have to warranty it because I'd have to wipe everything, restore to factory settings, unroot, etc. It's just a big hassle. Plus I'd be without a phone until the replacement arrives. I may end up just living with staying on lollipop 5.0.1 forever. It's just super frustrating.

ryan4a said:
Thanks. I've tried on multiple computers (PC & Mac, but not Linux). Nothing works. I originally thought it was one of the modifications I made to the device, like root, unlock, custom boot.img, custom recovery, modified build.prop, etc. The more I search, the more I think it's hardware. I'd like to not have to warranty it because I'd have to wipe everything, restore to factory settings, unroot, etc. It's just a big hassle. Plus I'd be without a phone until the replacement arrives. I may end up just living with staying on lollipop 5.0.1 forever. It's just super frustrating.
Click to expand...
Click to collapse
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.

simms22 said:
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
Click to expand...
Click to collapse
For a driver, it isn't a question of seeing it. Its a question of knowing how to talk to it. Further, one of the reasons I suggest he use something that runs linux, is because it avoids this whole driver problem altogether. The other reason is that it is actually consistent, and trivial to determine whether the devices itself actually made a connection, i.e. "dmesg -w", plug it, and see if it says anything.

simms22 said:
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
Click to expand...
Click to collapse
I've deleted and reinstalled the google driver, and installed the ADB driver. No dice. I'm telling you...I've tried everything. That's why I think it's hardware, however unlikely.

ryan4a said:
I've deleted and reinstalled the google driver, and installed the ADB driver. No dice. I'm telling you...I've tried everything. That's why I think it's hardware, however unlikely.
Click to expand...
Click to collapse
when getting adb to work, thats the #1 issue, installing and getting the driver to work. so, i can tell you, many people dont get the driver working without help in manually installing it. it seems those with older windows have less issues then those with newer windows. i really doubt that its a hardware issue.

simms22 said:
when getting adb to work, thats the #1 issue, installing and getting the driver to work. so, i can tell you, many people dont get the driver working without help in manually installing it. it seems those with older windows have less issues then those with newer windows. i really doubt that its a hardware issue.
Click to expand...
Click to collapse
Man I hope you're right. But my PC doesn't even recognize my device. Like it's not even showing up in the device manager. At best, I can sometimes get the PC to recognize it as an "unknown device". When I try to automatically update the driver, it says complete. But nothing changes. What do I do at that point? I haven't been successful in manually updating the driver.

As a matter of fact, I thought my new Turbo charger was broken because it stopped charging my phone. But when I unchecked USB debugging AND unchecked the MTP connection, the charger started working again. Very strange!

ryan4a said:
Man I hope you're right. But my PC doesn't even recognize my device. Like it's not even showing up in the device manager. At best, I can sometimes get the PC to recognize it as an "unknown device". When I try to automatically update the driver, it says complete. But nothing changes. What do I do at that point? I haven't been successful in manually updating the driver.
Click to expand...
Click to collapse
i wouldnt be able to help you there, as i dont own a computer. but there are many that can help out. maybe someone else will see this thread..

ryan4a said:
As a matter of fact, I thought my new Turbo charger was broken because it stopped charging my phone. But when I unchecked USB debugging AND unchecked the MTP connection, the charger started working again. Very strange!
Click to expand...
Click to collapse
Like I said, TRY LINUX.
No drivers required. Everything is built into the kernel.
Fedora even has an "android-tools" package that includes adb. You just install it with "yum install android-tools" -- even on the livecd (it will install to ramdisk).
Quit screwing around with wondoze and TRY IT.

Linux is a mega pita. Nothing is intuitive or easy. All these commands that have to be typed in, yuk. Give me good ol' Windows any day. Lol.
To the OP. Are you on windows 8.1? Have you disabled 'driver signature verification'?

killall said:
Linux is a mega pita. Nothing is intuitive or easy. All these commands that have to be typed in, yuk. Give me good ol' Windows any day. Lol.
To the OP. Are you on windows 8.1? Have you disabled 'driver signature verification'?
Click to expand...
Click to collapse
I'm using Windows 7. Don't think I'll be using Linux either. I'm running out of options for upgrading android versions without a PC. I'm highly considering installing CM12. I'd rather not because it's seems unnecessary on a Nexus device, but don't know what else to do.

There is also about a 5 second delay from the time I plug my device into any charger, to when it actually begins charging. I'm thinking these two issues are related, which leads to believe it's hardware.

Definitely sounding more and more like hardware

ryan4a said:
There is also about a 5 second delay from the time I plug my device into any charger, to when it actually begins charging. I'm thinking these two issues are related, which leads to believe it's hardware.
Click to expand...
Click to collapse
I have the same delay when plugging in a charger. But my PC recognizes my N6 without any problems.

On my Droid Maxx I had driver issues. I asked on XDA and got it figured out. I can't check now but have a look at my posts and you may find your answer.
Back to V-Day.

How to Root my N6 w/o PC?

Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!

shabydog said:
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
Click to expand...
Click to collapse
AFAIK you will need a pc to 1)unlock your bootloader and 2)flash TWRP. After that the rest can be done locally. I also never used any toolkit. Making it easy is making it more dangerous IMHO.

Droidphilev said:
I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Click to expand...
Click to collapse
Second that.
shabydog said:
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Click to expand...
Click to collapse
So at least once you need to connect your phone to a desktop computer. It can be practically running anything, within reason of course: Wiindows. Mac OSX, Linux (almost any distro).
You need to unlock your bootloader with one command, but a warning here: Unlocking the bootloader will erase everything from your phone..
Then you need to install a custom recovery, preferably TWRP. After that everything can be done from the phone itself. Well at least until you soft brick it somehow, then you'll might have to use the PC again.
Also two things:
1. No OTAs for rooted phones
2. Don't lock your bootloader if you want to mess with it, because with a locked bootloader, and Enable OEM Unlocking set to off, and without TWRP, if you soft brick it accidentally, you are boned.

Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use?
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
And i really prefer to do it on the device and not by ADB commands.
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!

shabydog said:
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
Click to expand...
Click to collapse
Well, you still will have to unlock it, if you want root, or want to flash a custom recovery.
Sent from my Nexus 6 running cyosp using Tapatalk

shabydog said:
......I really don't like the issue of trying to set the drivers of fastboot/google and so on!
Click to expand...
Click to collapse
Than do not 'root' your phone.

hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:

simms22 said:
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
Click to expand...
Click to collapse
Ha ha, or I don't want my birthday to be on the day I was born every year ?

I can recommend the NTRT, the Nexus Telepathic Rooting Tools.

OK.
I want to do that with a toolkit, only bcs it install the drivers.
What Is the most recommended and easiest to use?
I do looking for the 1 click do all.
Does NTRT do that?
Thank you all.

we are eventually goung to have a "my n6 is bricked, how do i fix it with one click" thread here. seriously though, thats what happens when you use toolkits, but do no real research about modding your device.

Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Sent from my Nexus 6 using Tapatalk

shabydog said:
Could anybody guide me through the steps, if needed?
Click to expand...
Click to collapse
<prev> step <next>

simms22 said:
seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Click to expand...
Click to collapse
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
wtherrell said:
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Click to expand...
Click to collapse
It is fairly enough to read directions and slowly-slowly.
NLBeev said:
<prev> step <next>
Click to expand...
Click to collapse
Thanks!
==========================================================
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?

shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
Click to expand...
Click to collapse
i agree with you. if there is somebody who knows the ins and outs already, a one click root would be great. and there will be. problem is that marshmallow just came out, and a few things have changed, like like yoe also need a custom kernel to have root on marshmallow.

shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
It is fairly enough to read directions and slowly-slowly.
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
Click to expand...
Click to collapse
There is a reason you're pushing this topic, and I'm quite sure it's because you would feel safer, if there was a tool that did the scary things instead of you. Well, there's no such tool. If you were willing to search XDA, you would find out that the first two weeks after Marshmallow came out were about people bricking their Nexus 6s with toolkits. Then the toolkit got updated and suddenly it knew that is has to flash a modified boot.img too for the root not to brick the phone. But for two weeks it didn't know, because it wasn't necessary for Lollipop. And it will only work until the next security update comes out. And that's once a month.
Meanwhile those who were willing to use the search function, and learned the five minute procedure, were able to update their rooted phones to the next security update and were able to root it as soon as the new modified boot image came out.
And this above is not something somebody will put in a help, or instructions for future updates.

Actually, this is my first time and I was able to do it pretty easily.
fastboot devices
fastboot oem unlock
my bootloader was unlocked within 30 seconds of turning it on.
then, you can easily root via CF Auto root. Just put it into fastboot then doubleclick on the windows, then root, etc....
or.............go into fastboot flash recovery twrpxxxx.img, then it always offers to run SuperSU, and you get custom recovery and root at the same time, etc......
actually the biggest pain is unlocking the bootloader. My Galaxy S4 already was unlocked, so all I did was use goomanager, flash TWRP which always offers to run SuperSU if you don't have it.
Pretty easy, I did unlock bootloader, root, and custom recovery in 10 min.
---------- Post added at 01:48 AM ---------- Previous post was at 01:44 AM ----------
............................Then I got sick of stock Google's ROM in 15 min and wiped it and put a custom ROM instead.

Thank you all so much...
@mikeprius
Thank you so much for the info'!
But, could you plz write more details? such as:
1. How did you installed the drivers? (from my expirience, many times the pc dosent install this easily).
I just need the Google oem driver and that's it?
2. When drivers was set - did you made anything in your phones settings? Which?
3. What did you had to do before pushing the files? (Like...put all the files in the same folder? *which files?)
4. And then entered to fastboot mode and typed in these commands in pc:
fastboot devices
fastboot oem unlock
Regarding your last sentence ("or...."):
If i just flash the recovery via fastbot mode I can enter to twrp recovery and it offers to flash the SuperSU?
Sounds to me the best option.
Thanks!

1. The drivers were set from a previous device, so I didn't have to set them, but they can be downloaded and set though.
2. You need to enable developer options and select OEM unlock and USB debugging.
3. I didn't push the files, I just had them on my computer and ran fastboot commands.
4. Those commands are to unlock the bootloader.
There are a lot of different ways to do the same thing (Root, custom recovery, unlock bootloader)
1. Run CF Auto Root on a locked bootloader. It will unlock it automatically (Chainfire has it set that way), root, then download Flashify app and flash the latest img of TWRP.
2. Run fastboot commands to manually unlock the bootloader, flash TWRP, then use TWRP's SuperSU which will root it.
3. Run fastboot commands to unlock bootloader, run CF Autoroot which will root and load SuperSU, then flash TWRP via Flashify or fastboot.
There are many different ways to do the same thing. I actually just googled youtube videos and watched them.
TWRP has SuperSU and root built in. TWRP knows if you don't have it and offers to load it for you.
I went the scenic route just because, but presumably you can achieve all (3) using Option #1 without having to deal with fastboot, adb, etc.....Chainfire's script runs automatically.

I realy try to help people but users that run into problems because of the usage of tookits (and innability to solve problems and/or even lack the most basic knowledge needed) should ask the toolkit dev. for support imo, and not boughter users that have invested time and effort to gain that knowledge to clean up their mess. Period

blu advance 5.0 hd compatible?

Hey so do you think the blu advance 5.0 hd will be compatible with the work being done on the R1 hd? I would really like to jump on this hype train with my similar but slightly less powerful phone.
I am hoping that I will be able to install a custom rom like R1 users. I also want to root my phone to disable google services in the meantime.

xda123455 said:
Hey so do you think the blu advance 5.0 hd will be compatible with the work being done on the R1 hd? I would really like to jump on this hype train with my similar but slightly less powerful phone.
I am hoping that I will be able to install a custom rom like R1 users. I also want to root my phone to disable google services in the meantime.
Click to expand...
Click to collapse
That phone is based on the 6580 SoC, the R1 uses a 6735. There is a site that lists some roms for blu products that may help, I don't know how reliable they are, I have never used them, but if you want to check it out...
http://www.blu-dev.com

kal250 said:
That phone is based on the 6580 SoC, the R1 uses a 6735. There is a site that lists some roms for blu products that may help, I don't know how reliable they are, I have never used them, but if you want to check it out...
http://www.blu-dev.com
Click to expand...
Click to collapse
Thanks I checked out the site and it seems like there is no blue advance 5.0 roms and no forum activity =/

xda123455 said:
Thanks I checked out the site and it seems like there is no blue advance 5.0 roms and no forum activity =/
Click to expand...
Click to collapse
If your wanting to root it, I'm hearing Kingroot is working, never used it though, so I can't say if it works or if it's safe??

kal250 said:
If your wanting to root it, I'm hearing Kingroot is working, never used it though, so I can't say if it works or if it's safe??
Click to expand...
Click to collapse
I've tried Kingroot, Kingo Root and Frama root. All with no luck.

devanttrio said:
I've tried Kingroot, Kingo Root and Frama root. All with no luck.
Click to expand...
Click to collapse
Did you use the desktop versions? Those have higher success rates. I tried rooting an HTC that way and it worked flawlessly even when the apk didn't.

Autolounge said:
Did you use the desktop versions? Those have higher success rates. I tried rooting an HTC that way and it worked flawlessly even when the apk didn't.
Click to expand...
Click to collapse
I did.
I also tried the apps, of the ones that have apps.

devanttrio said:
I did.
I also tried the apps, of the ones that have apps.
Click to expand...
Click to collapse
You're going to have to do it manually.

no go on kingo
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??

trc117 said:
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
Click to expand...
Click to collapse
consider yourself blessed my friend, i'd like to root mine just to get marshmallow.... i have lollipop and checked for updates and says i'm up to date, i can only install 1 app at a time because there is no room on the internal storage, i have to move every app to sd card and then clean cache for each and every app i want.. never recommending blu to anyone

trc117 said:
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
Click to expand...
Click to collapse
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - https://bluroms.info . Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in

zjr8 said:
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - https://bluroms.info . Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
Click to expand...
Click to collapse
I've been trying to root a Blu Advance 5.0 HD for a while now and stumbled on this post. I visited your site but am not sure what a 'Scatter File' is, or in what order I need to do things in order to get root.
If you could provide a little more detailed info that would be very much appreciated.
Thanks!
rAy
EDIT: Sorry, to clarify I tried all of the other PC and APK rooting solutions but was able to unlock the bootloader using ADB. I guess I'm just looking for the proper way to root and add TWRP. Thanks!

ray2jerry said:
I've been trying to root a Blu Advance 5.0 HD for a while now and stumbled on this post. I visited your site but am not sure what a 'Scatter File' is, or in what order I need to do things in order to get root.
If you could provide a little more detailed info that would be very much appreciated.
Thanks!
rAy
EDIT: Sorry, to clarify I tried all of the other PC and APK rooting solutions but was able to unlock the bootloader using ADB. I guess I'm just looking for the proper way to root and add TWRP. Thanks!
Click to expand...
Click to collapse
I found a option in developer settings that is "Enable OEM unlocking" and it makes it so you can unlock the bootloader from fastboot, if you do adb reboot-bootloader and then fastboot unlock it should undo the bootloader for you

zjr8 said:
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
Click to expand...
Click to collapse
Like the others said, I would really appreciate if you could give an explanation or tutorial on how to use these files that you uploaded to root the phone. I'm willing to donate some money if required. I only know basic technical stuff haha.

CreativiTimothy said:
Like the others said, I would really appreciate if you could give an explanation or tutorial on how to use these files that you uploaded to root the phone. I'm willing to donate some money if required. I only know basic technical stuff haha.
Click to expand...
Click to collapse
I too am trying to root this device, and am unclear on a few of the steps here. I actually found your site with the recovery and boot images independently, really appreciated! I am at the point where I just need to patch the boot image, though I am not sure how to do this. If you could help me out with this step I might be able to put together some sort of list of steps to get through the whole process if you don't have the time.
Any help would be appreciated, thanks!

Help Please!!

Hello and Thank you for viewing my post!
I am New to Android Devices and the "Rooting" Process. I am a regular Apple user and use a Jailbroken iPhone and Use a Mac as well but have Windows Mirroring Capabilities on my Mac.
I just bought the Kindle Fire HD 8 (6th Generation) (2016) and it came with os 5.1.1 installed but once i connected to wifi it automatically updated me to 5.3.1.1.
I do not like the OS it includes as there are too many annoyances present (Ads, Unwanted OEM Applications, Etc.) and would like to Root my device and Run a "Real" Android OS and in other words, convert my Kindle Fire HD 8 into a Android Tablet as many do but i am unable to root because i am on 5.3.1.1.
If someone could please help walk me through the steps i need to take to root and all the tools ill need to do so, as well as ways to avoid bricking the device in the process.
Thank you in advance!
-Elijah

ElijahJ777 said:
Hello and Thank you for viewing my post!
I am New to Android Devices and the "Rooting" Process. I am a regular Apple user and use a Jailbroken iPhone and Use a Mac as well but have Windows Mirroring Capabilities on my Mac.
I just bought the Kindle Fire HD 8 (6th Generation) (2016) and it came with os 5.1.1 installed but once i connected to wifi it automatically updated me to 5.3.1.1.
I do not like the OS it includes as there are too many annoyances present (Ads, Unwanted OEM Applications, Etc.) and would like to Root my device and Run a "Real" Android OS and in other words, convert my Kindle Fire HD 8 into a Android Tablet as many do but i am unable to root because i am on 5.3.1.1.
If someone could please help walk me through the steps i need to take to root and all the tools ill need to do so, as well as ways to avoid bricking the device in the process.
Thank you in advance!
-Elijah
Click to expand...
Click to collapse
You can flash an older stock version with fastboot. You may need a fastboot cable to do it though.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
You can flash an older stock version with fastboot. You may need a fastboot cable to do it though.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Ive heard rollingback from 5.3.1.1. will brick the Tablet due to the Bootloader(s), Correct?

ElijahJ777 said:
Ive heard rollingback from 5.3.1.1. will brick the Tablet due to the Bootloader(s), Correct?
Click to expand...
Click to collapse
Downgrading bootloader on some devices can brick them, it depends on the software though, not the device. Some devices with locked bootloader that can't be downgraded can sometimes extract the bootloader from the newer locked firmware and replace it in the older firmware, this allows the older firmware to be flashed without downgrading the bootloader because it has been modified so that it has the same bootloader. Not all locked devices can do this though, and even the ones that can still can't flash anything custom because of the bootloader, it does allow for downgrading to use things that won't work in the newer firmware. Whether or not that can be done on this or that device is hit or miss though, some can and some can't, it just requires research and trial and error.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
Downgrading bootloader on some devices can brick them, it depends on the software though, not the device. Some devices with locked bootloader that can't be downgraded can sometimes extract the bootloader from the newer locked firmware and replace it in the older firmware, this allows the older firmware to be flashed without downgrading the bootloader because it has been modified so that it has the same bootloader. Not all locked devices can do this though, and even the ones that can still can't flash anything custom because of the bootloader, it does allow for downgrading to use things that won't work in the newer firmware. Whether or not that can be done on this or that device is hit or miss though, some can and some can't, it just requires research and trail and error.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
My Kindle Fire HD 8 (2016) allows me to unlock the Boot loader (OEM Unlock) from the settings menu, Im no sure if this is a good thing? (Easy way to downgrade boot loader alongside OS?) or not but not exactly sure. Would you recommend any tactics with this in mind or to just wait for kingroot or someone to crack 5.3.1.1. and create a Root?
Thank you!

ElijahJ777 said:
My Kindle Fire HD 8 (2016) allows me to unlock the Boot loader (OEM Unlock) from the settings menu, Im no sure if this is a good thing? (Easy way to downgrade boot loader alongside OS?) or not but not exactly sure. Would you recommend any tactics with this in mind or to just wait for kingroot or someone to crack 5.3.1.1. and create a Root?
Thank you!
Click to expand...
Click to collapse
I would wait for root
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
I would wait for root
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Alright, Appreciate the help!
Have a good day!
-Elijah