Database Develop

Avoid losing root with OTA update.

Warning: crawrj mentioned this wouldn't flash in TWRP. I use CWM, so not sure whether it's compatible with TWRP (or any other recoveries) at the moment. So, if you're not using CWM... I would suggest waiting a bit.
So as most people know, the new OTA update aims to kill root on the device and the motochopper root method. Once I received the update and saw that it removed root, I immediately set out to figure out what was causing the issue. I also noticed that I was getting the notice about an application performing unauthorized tasks, or something to that effect.
After doing a few file deletions and restores, I finally found the file (KNOXAgent.apk) that was causing the notice about unauthorized actions and needing to restart. I've been running the phone with the MDL update for a little over a week now, and I haven't had another notice. I did lose root during the update, but was able to easily root it again with the motochopper method once the KNOXAgent files were removed.
So, here are the steps I took to avoid losing my root.
1) adb shell
2) su
3) mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
4) rm /system/app/KNOXAgent.*
5) Reboot into recovery and flash the OTA zip provided below. It's the OTA update with the KNOXAgent patches removed from the updater-script. This will allow the update to continue installing without having an error about KNOXAgent not being found on the device.
The same process may have to be done with future OTA updates once KNOXAgent is removed, but it's better than losing your root method each time an OTA comes out. As I mentioned, I've been using this phone since May 13th with this being done. I also had to take out the My Files updates as well, since I have the CyanogenMod file browser (My Files doesn't have root support).
Unfortunately, it seems XDA has problems with filtering spam and requires that you have 10 posts before being able to post external links. Since I don't have anything else to post at the moment, and can't post on the development forums to report problems to developers in order to legitimately increase my count without having to spam threads I don't care about, you'll have to copy and paste the link to get the update package.
Update link: http://d-h.st/Dkl

RogueSly said:
So as most people know, the new OTA update aims to kill root on the device and the motochopper root method. Once I received the update and saw that it removed root, I immediately set out to figure out what was causing the issue. I also noticed that I was getting the notice about an application performing unauthorized tasks, or something to that effect.
After doing a few file deletions and restores, I finally found the file (KNOXAgent.apk) that was causing the notice about unauthorized actions and needing to restart. I've been running the phone with the MDL update for a little over a week now, and I haven't had another notice. I did lose root during the update, but was able to easily root it again with the motochopper method once the KNOXAgent files were removed.
So, here are the steps I took to avoid losing my root.
1) adb shell
2) su
3) mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
4) rm /system/app/KNOXAgent.*
5) Reboot into recovery and flash the OTA zip provided below. It's the OTA update with the KNOXAgent patches removed from the updater-script. This will allow the update to continue installing without having an error about KNOXAgent not being found on the device.
The same process may have to be done with future OTA updates once KNOXAgent is removed, but it's better than losing your root method each time an OTA comes out. As I mentioned, I've been using this phone since May 13th with this being done. I also had to take out the My Files updates as well, since I have the CyanogenMod file browser (My Files doesn't have root support).
Unfortunately, it seems XDA has problems with filtering spam and requires that you have 10 posts before being able to post external links. Since I don't have anything else to post at the moment, and can't post on the development forums to report problems to developers in order to legitimately increase my count without having to spam threads I don't care about, you'll have to copy and paste the link to get the update package.
Update link: d-h.st/Dkl
Click to expand...
Click to collapse
Nice find

travisw0204 said:
Nice find
Click to expand...
Click to collapse
Thanks. It took a bit to find, but I couldn't live without root. My battery is GAWD with the CPU limited. :3

OK I am messing around with this and providing feedback. It doesn't install on the stock recovery for obvious reasons. It doesn't install in TWRP. Gives update binary error. Have to backup my extsd so I can format to fat32 to test other recoveries.

crawrj said:
OK I am messing around with this and providing feedback. It doesn't install on the stock recovery for obvious reasons. It doesn't install in TWRP. Gives update binary error. Have to backup my extsd so I can format to fat32 to test other recoveries.
Click to expand...
Click to collapse
Weird. Flashed for me on CWM when I used it.

RogueSly said:
Weird. Flashed for me on CWM when I used it.
Click to expand...
Click to collapse
Yeah I am guessing it will work in CWM. But I have to backup and format first to test. Which recovery did you use?

crawrj said:
Yeah I am guessing it will work in CWM. But I have to backup and format first to test. Which recovery did you use?
Click to expand...
Click to collapse
I've been using http://forum.xda-developers.com/showthread.php?t=2254323. I tend to stay away from touch recoveries when there are 4 dogs in the house.

Lol, too little too late for me. :facepalm:

Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.

crawrj said:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
Click to expand...
Click to collapse
Awesome! Glad to hear it's fixed. Not sure why the modem didn't install. I didn't get any errors on my device after taking out the patches for My Files and KNOXAgent, as both were missing on my system. I'll try restoring back to MDC and updating to SuperSU 1.3 to test it.

crawrj said:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
Click to expand...
Click to collapse
I was going to ask an annoying question.... but decided it was annoying and did a search. here is what I found in the difference between SuperUser and SuperSU and SuperSU Pro ($2.49). Reference: http://android.stackexchange.com/qu...ruser-from-chainsdd-and-superuser-from-clockw
SuperSU improves everything about Superuser and adds more options. The free version offers faster notifications, there is possibility of disabling them for each app and a new interface, attractive and easy to handle. In addition, according to developer claims by using SuperSU you’ll enjoy higher speed from the apps that require root rights, especially on Android 4.0+. The paid version called SuperSU Pro provides the opportunity to keep root rights after a system update, which usually cancels these rights. Although the method is not guaranteed the option is very useful. We have password protection and advanced log configuration settings for each application.
You might also want to read SuperSU Brings Better SuperUser Root Permission Management to Android. Quoting from that article:
SuperSU is basically SuperUser on steroids. According to the developer, it “allows for advanced management of Superuser access rights for all the apps on your device that need root.”.
Edit: ::FacePalm:: What ever you do. Do not uninstall SuperUser after you install SuperSU. You will loose Root. LOL (Hey at least I can laugh at myself.) I am not worried about it yet... I know I will get it back eventually.
Edit 2: After reading the OP, all you have to do if you have TWRP Recovery installed is do the OTA, your update will install and you will automatically reboot into TWRP.
Go to Mount first and mount System.
Go to back to home and select Advanced.
Go to File Manager. NOTE: This can be very frustrating! Use BACK and Sort Options to reset Sorting if it keeps doing things you don't want it to do. Also (Up A Level) is handy. If you are on "/" directory, touch Sort Descending: Name and you will see System. Select Sysytem.
Now Sort Ascending you will see App. Select App.
Gentally and slowly Swipe down in the middle to reach Knox. I found 2 files. Select one at a time and delete them.
Reboot
Then rerun Motochopper Root method.
I am on Stock MDC still. So if you are on MDL I am not sure if this would work. Now follow the directions that I failed to see when you install SuperSU.
Install SuperSU. Open SuperSU and make sure SU binary is switched from SuperUser to SuperSU. Once you do that you can remove SuperUser.
Edit 3: Once you check to make sure SuperSU has Binary after a reboot... SuperSU will remove SuperUser for you. No need to do anything.
After all said and done... I am thinking that the TWRP stopped the OTA from installing. I have been extremely busy with work, so no time to read XDA lately has been stopping me from keeping up to date. I just need more time in the day.

crawrj said:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
Click to expand...
Click to collapse
Well, crawrj.. I just rawly patched the modem.bin with the modem.img.p, and the baseband version and such still hasn't increased. My software version and baseband version are still showing MDC, while build number is showing MDL. The weird thing about it is the kernel also updated from its original. How does the modem not update when it's being directly flashed onto the partition? Trying to get all of my stuff over to MDL, if that's what it's supposed to be. It has the new boot sound and such, but the inconsistent version numbers make me hesitant that the update fully applied.

RogueSly said:
Well, crawrj.. I just rawly patched the modem.bin with the modem.img.p, and the baseband version and such still hasn't increased. My software version and baseband version are still showing MDC, while build number is showing MDL. The weird thing about it is the kernel also updated from its original. How does the modem not update when it's being directly flashed onto the partition? Trying to get all of my stuff over to MDL, if that's what it's supposed to be. It has the new boot sound and such, but the inconsistent version numbers make me hesitant that the update fully applied.
Click to expand...
Click to collapse
There is some kind of write protection of security that locks the modem down. I have tried 100 different ways of installing the modem and can't. It looks like the official installs are the only ones that work. So right now the ota is the only way to get the modem. But I am sure we will get it figured out in time.
Sent from my SPH-L720 using xda premium

crawrj said:
There is some kind of write protection of security that locks the modem down. I have tried 100 different ways of installing the modem and can't. It looks like the official installs are the only ones that work. So right now the ota is the only way to get the modem. But I am sure we will get it figured out in time.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Well, that sucks. I guess I will give up trying to flash it for now. Already removed KNOXAgent again and dropped faux's kernel on here. It's showing my build as MDL, so at least I don't get pestered by the update message.

aww come on lol too late for me too. I went through hell rooting my phone when i upgraded to MDL. I flashed the stock rom like 3 times before getting my phone rooted and the last piece of the puzzle were the knox files. Instead of deleting the files i froze them using the system tuner off from the playstore after i installed shabbat's custom kernel.
Do we know of a way to avoid all these run arounds to root on MDL by keeping the stock kernel and without removing knox???

tones160 said:
aww come on lol too late for me too. I went through hell rooting my phone when i upgraded to MDL. I flashed the stock rom like 3 times before getting my phone rooted and the last piece of the puzzle were the knox files. Instead of deleting the files i froze them using the system tuner off from the playstore after i installed shabbat's custom kernel.
Do we know of a way to avoid all these run arounds to root on MDL by keeping the stock kernel and without removing knox???
Click to expand...
Click to collapse
I think there are a few posts in the development sections that will help out with getting root on MDL. If it were me, I would just pull the SuperSU apk and unzip it. Grab the su binary out of there, push it to /system/xbin/, and then install SuperSU on the phone once it restarted. Now, I can't confirm that works... because I haven't had to get that dirty with rooting my phone. Motochopper worked perfectly fine when KNOXAgent was removed, so it should work if you have KNOXAgent frozen too.

Cf autoroot

wanna make sure I understand this right. I'm gonna flash this no knox update on top of forcesrom (which has knox removed), I should be ok right? but the modern still not install this way, is that correct? and I won't be able to update my modem until a new method comes out. do I got it all right? thanks! :thumbup::what:

gershee said:
wanna make sure I understand this right. I'm gonna flash this no knox update on top of forcesrom (which has knox removed), I should be ok right? but the modern still not install this way, is that correct? and I won't be able to update my modem until a new method comes out. do I got it all right? thanks! :thumbup::what:
Click to expand...
Click to collapse
That's apparently right, for now. I'm working on figuring out why the MDM partition won't flash. I tried to patch the files manually, as mentioned previously and here, but it seems that it didn't flash as the baseband didn't change?
Hopefully figure it out soon.

Getting E:Error in /external_sd/OTA 5-13-2013 (No Knox Agent), Status 7. Any advice?

[Q] SuperSU Binary issue, root help!

Hi,
I have a T-Mobile LG G Flex that used to be rooted and after android system update now it doesn't have root access. Here's the thing: I ran TowelRoot and it displayed the following message: "This device isn't supported". Afterwards I downloaded and installed StumpRoot and when I run the app it displays a message saying: "Device is rooted" but when I run the Root Checker app it tells me device has no root access.
Heres the Software Information from the device:
Android Version
4.4.2
Baseband Version
M8974A-AAAANAZM-2.0.20064
Kernel Version
3.4.0
Build Number
KOT49I.D95920s
Software Version
D95920s
Can anyone point me towards a solution for this? I made a new thread regarding this matter because even though I've seen many people post similar situations they're for other type of devices. Any help will be deeply appreciated.
Thanks,

I'd say you might have to grab the tot for the d959, flash back to stock and run the updates again, then use stump.
ROGERS • LG G Flex D950G • Stock ROOT 4.4.2 • V4A • 180DPI • FLEXIN'

Eun-Hjzjined said:
I'd say you might have to grab the tot for the d959, flash back to stock and run the updates again, then use stump.
ROGERS • LG G Flex D950G • Stock ROOT 4.4.2 • V4A • 180DPI • FLEXIN'
Click to expand...
Click to collapse
What do you mean by 'tot'?

IamMAC said:
What do you mean by 'tot'?
Click to expand...
Click to collapse
Can someone answer this for me?
This always happens to me, I post a new thread and I get my questions answered once but after that no more help. Is this a forum rule?, do I need to help another user before receiving help again. I'd appreciate if someone could point me in the right track.
Thanks!,

IamMAC said:
Can someone answer this for me?
This always happens to me, I post a new thread and I get my questions answered once but after that no more help. Is this a forum rule?, do I need to help another user before receiving help again. I'd appreciate if someone could point me in the right track.
Thanks!,
Click to expand...
Click to collapse
Get back to stock using tot file following this guide:
http://forum.xda-developers.com/showthread.php?t=2644083

A lot of peep have been posting that they're not able to root the latest update with the previous methods. And also T-Mobile doesn't use a tot file. Its .kdz. But not gonna work due to the latest update doesn't have download mode. So if you're on the latest, I suggest find a root method ( try stumproot, safe root, I/o root, vroot, towel root, hell id try anything. But that's me. I don't suggest shoot blind if you don't know what you're doing) then install freedom flex get a custom recovery then make a backup and flash d'fuse's rooted KitKat and disable ota's.

mattwheat said:
A lot of peep have been posting that they're not able to root the latest update with the previous methods. And also T-Mobile doesn't use a tot file. Its .kdz. But not gonna work due to the latest update doesn't have download mode. So if you're on the latest, I suggest find a root method ( try stumproot, safe root, I/o root, vroot, towel root, hell id try anything. But that's me. I don't suggest shoot blind if you don't know what you're doing) then install freedom flex get a custom recovery then make a backup and flash d'fuse's rooted KitKat and disable ota's.
Click to expand...
Click to collapse
I'm having the same problem as OP, got any other methods that you think might work? tried all the ones I could find/ you listed and none have worked yet!

any update OP?

dmifsud44 said:
any update OP?
Click to expand...
Click to collapse
In my case I haven't been able to try anything because my tether app stopped working and I can't get any VPN service to work. Any suggestions on this other issue?

IamMAC said:
Hi,
I have a T-Mobile LG G Flex that used to be rooted and after android system update now it doesn't have root access. Here's the thing: I ran TowelRoot and it displayed the following message: "This device isn't supported". Afterwards I downloaded and installed StumpRoot and when I run the app it displays a message saying: "Device is rooted" but when I run the Root Checker app it tells me device has no root access.
Heres the Software Information from the device:
Android Version
4.4.2
Baseband Version
M8974A-AAAANAZM-2.0.20064
Kernel Version
3.4.0
Build Number
KOT49I.D95920s
Software Version
D95920s
Can anyone point me towards a solution for this? I made a new thread regarding this matter because even though I've seen many people post similar situations they're for other type of devices. Any help will be deeply appreciated.
Thanks,
Click to expand...
Click to collapse
No no no
Just install SU from playstore update binaries
P o o f there u'll have Root had same issue, you havta download SU AND INSTALL IT MANUALLY

fix
The fix for this problem is to download lg mobile support tool
on your pc
Click on options-upgrade recovery
Let it download
You will need to plug your phone
In via USB for the last 10 percent
You will now be unrooted and able to
Reroot with stumproots brute force
Oh and you will get download mode back
Power off-vol up+ plug in USB

damnrose said:
The fix for this problem is to download lg mobile support tool
on your pc
Click on options-upgrade recovery
Let it download
You will need to plug your phone
In via USB for the last 10 percent
You will now be unrooted and able to
Reroot with stumproots brute force
Oh and you will get download mode back
Power off-vol up+ plug in USB
Click to expand...
Click to collapse
I followed your steps and I was able to get the device up and running once again with ROOT access.
Thanks a million,

damnrose said:
The fix for this problem is to download lg mobile support tool
on your pc
Click on options-upgrade recovery
Let it download
You will need to plug your phone
In via USB for the last 10 percent
You will now be unrooted and able to
Reroot with stumproots brute force
Oh and you will get download mode back
Power off-vol up+ plug in USB
Click to expand...
Click to collapse
:good: This worked for me as well! Thanks

supersu problem
Hey! Rooted my phone yeasterday.
I have installed lateste version of SuperSU on play store, but still not working. says there is no binary fil to SU installed when I try to open the app.
My version is 4.4.2
device model
Samsung Galaxy GT 19505

Senzi said:
Hey! Rooted my phone yeasterday.
I have installed lateste version of SuperSU on play store, but still not working. says there is no binary fil to SU installed when I try to open the app.
My version is 4.4.2
device model
Samsung Galaxy GT 19505
Click to expand...
Click to collapse
This is a gflex thread not s4
But for your phone
if you have a recovery installed(If you don't you can flash it with Odin google it)
Boot into recovery
Flash the su zip from chainfires website
Should fix your issue

damnrose said:
This is a gflex thread not s4
But for your phone
if you have a recovery installed(If you don't you can flash it with Odin google it)
Boot into recovery
Flash the su zip from chainfires website
Should fix your issue
Click to expand...
Click to collapse
Dont think I got recovery installed, but I will try to flash it. But what does it mean "flash it"?

Senzi said:
Dont think I got recovery installed, but I will try to flash it. But what does it mean "flash it"?
Click to expand...
Click to collapse
"Flash It" or "Flashing" means to copy files to your device using an application such as ODIN.

Need help..
IamMAC said:
I followed your steps and I was able to get the device up and running once again with ROOT access.
Thanks a million,
Click to expand...
Click to collapse
Hi, so I am stuck without recovery or download mode. I know that the LG Mobile Support Tool should work but I tried it on two PCs and just as it finishes extracting the software after it downloads, the program runs into an error and closes. I am running D95920s like everyone else here. Just no luck. Any suggestions? I plugged in at 90% Not sure if im doing anything wrong.
Update: So the LG Mobile Tool has many security checks and it doesn't always allow for flashing. If anybody comes across this problem in the future. Refer to mattwheats instructions.
Here: http://forum.xda-developers.com/lg-g-flex/general/fyi-taking-ota-rooted-twrp-t2999344
It will force your phone to flash without download mode.

http://forum.xda-developers.com/showthread.php?p=60119946

su for remix not working and its diag mode (read cdma/qpst)

I know there is not much support for the remix, though it's essentially a mini 2...too. I have it s-off and unlocked. I have twrp recovery on it. The all in one utility on one of these threads didn't work well for twrp so I flashed it via fast boot. I've tried running the utility for gaining root but nothing shows up in twrp under sdcard. I have pushed it to another folder, I find it and flash the zip file but even though it says it finished fine, when I reboot nothing is there. Weak sauce2 works fine, but that's just temp. I want permanent root.
That said anyone know how to enable serial/modem communication to cdma/qpst on the remix? I've been trying forever. Im trying to backup the prl.

jobzombi said:
I know there is not much support for the remix, though it's essentially a mini 2...too. I have it s-off and unlocked. I have twrp recovery on it. The all in one utility on one of these threads didn't work well for twrp so I flashed it via fast boot. I've tried running the utility for gaining root but nothing shows up in twrp under sdcard. I have pushed it to another folder, I find it and flash the zip file but even though it says it finished fine, when I reboot nothing is there. Weak sauce2 works fine, but that's just temp. I want permanent root.
That said anyone know how to enable serial/modem communication to cdma/qpst on the remix? I've been trying forever. Im trying to backup the prl.
Click to expand...
Click to collapse
I had the same issue today and was able to chat with the creators of Sunshine. They are super helpful and offer great support for their product. It took me a few tries but I have root. After you flash the latest version of Chainfire's supersu HERE , you have download the app from the playstore.
Not sure if this was related but right before I did the steps above, I switch over the the Nova launcher. One of the creators told me the stock blinkfeed launcher may give issues.

on1wheel said:
I had the same issue today and was able to chat with the creators of Sunshine. They are super helpful and offer great support for their product. It took me a few tries but I have root. After you flash the latest version of Chainfire's supersu HERE , you have download the app from the playstore.
Not sure if this was related but right before I did the steps above, I switch over the the Nova launcher. One of the creators told me the stock blinkfeed launcher may give issues.
Click to expand...
Click to collapse
How exactly did you accomplish it? Did you push su from recovery mode? I've been trying from just regular, ready to make calls, mode. Did you run a script or do it all manually? xbin or bin? I know some people like symbolic links to xbin/su within bin.

jobzombi said:
How exactly did you accomplish it? Did you push su from recovery mode? I've been trying from just regular, ready to make calls, mode. Did you run a script or do it all manually? xbin or bin? I know some people like symbolic links to xbin/su within bin.
Click to expand...
Click to collapse
I flashed the zip I linked above in TWRP recovery. You can connect your phone to a computer or download the supersu from your phone. After it is flashed, go to the play store and download the supersu app. I thought flashing would install the app on my phone but it didn't. After installing the app, pen it and it will prompt to install the binaries. After that I had root.
I'm not sure what you meant by xbin, bin, or symbolic links. I don't deal with any of that.

on1wheel said:
I flashed the zip I linked above in TWRP recovery. You can connect your phone to a computer or download the supersu from your phone. After it is flashed, go to the play store and download the supersu app. I thought flashing would install the app on my phone but it didn't. After installing the app, pen it and it will prompt to install the binaries. After that I had root.
I'm not sure what you meant by xbin, bin, or symbolic links. I don't deal with any of that.
Click to expand...
Click to collapse
OK, thanks. The Zip usually takes care of all that. I was having no success with a the zip file provided in the Windroid toolkit, so I was trying to push the same su that the toolkit downloaded to the phone and was trying it manually. I tried it with the one Weaksauce puts in the xbin folder as well temporarily. Both didn't work. I'll give this a go.
Thank you again!

Your welcome. I didn't use any of the methods you mentioned. I waited for the Sunshine 3 release to work and then tried the newest supersu zip. That did it. Now I'm waiting for a dev to port a rom to the HTC One Remix.

on1wheel said:
Your welcome. I didn't use any of the methods you mentioned. I waited for the Sunshine 3 release to work and then tried the newest supersu zip. That did it. Now I'm waiting for a dev to port a rom to the HTC One Remix.
Click to expand...
Click to collapse
I'm currently working on figuring out how to port it. Doesn't look like it should be too hard, but we'll see.

Txjacob said:
I'm currently working on figuring out how to port it. Doesn't look like it should be too hard, but we'll see.
Click to expand...
Click to collapse
I'll check back regularly. Which rom are you planning on porting. CM?

Successfully unlocked and s-off with sunshine. Then used su installer by the same guys for root yay! Now just waiting for devs to make or either port some Roms for the remix.

diag?
Was anyone able to get diag working on this phone yet?
I'm assuming after root you could use this program to get into usb settings and enable it:
https://play.google.com/store/apps/details?id=org.vndnguyen.shortcutmaster.lite
But could someone confirm?

Device is dead?

Greetings,
I'm stuck in a very bad place with my Nexus 6 and was hoping someone could help me out of it. I obviously made a grave mistake in doing this so I'm hoping all is not lost. Here are the steps I performed that got me into this mess:
1) Downloaded the latest root .zip file from Chainfire, which notably, does not have a 6.0.
2) Flash Stock ROM to the device Marsh mellow 6.
3) Phone booted up just fine, I then unlocked developer options and then selected allow oem updates.
4) performed a reboot to the bootloader.
5) This is where I went wrong: executed the root-windows.bat script.
Now when the device boots I get an error stating the device is corrupt and cannot be trusted and it immediately shuts off.
UPDATE: I've re-flashed the marshmellow rom on to the device and now on boot I get the same error about the device being corrupt, however, the volume buttons allow me to select "Continue" and it's booting!
Thanks!
Eric

EricSB said:
Greetings,
I'm stuck in a very bad place with my Nexus 6 and was hoping someone could help me out of it. I obviously made a grave mistake in doing this so I'm hoping all is not lost. Here are the steps I performed that got me into this mess:
1) Downloaded the latest root .zip file from Chainfire, which notably, does not have a 6.0.
2) Flash Stock ROM to the device Marsh mellow 6.
3) Phone booted up just fine, I then unlocked developer options and then selected allow oem updates.
4) performed a reboot to the bootloader.
5) This is where I went wrong: executed the root-windows.bat script.
Now when the device boots I get an error stating the device is corrupt and cannot be trusted and it immediately shuts off.
UPDATE: I've re-flashed the marshmellow rom on to the device and now on boot I get the same error about the device being corrupt, however, the volume buttons allow me to select "Continue" and it's booting!
Thanks!
Eric
Click to expand...
Click to collapse
1. use supersu v2.5 or v2.51 for root, not chainfires old .
if you flash marshmallow via factory image, via fastboot. boot up, then back into your bootloader to flash the twrp . flash the recovery, then boot into the recovery and flash a custom kernel for marshmallow, and the supersu file. tgen boot up with root. that message is something that everybody gets. it because of your unlicked , just ignore it.

simms22 said:
1. use supersu v2.5 or v2.51 for root, not chainfires old .
if you flash marshmallow via factory image, via fastboot. boot up, then back into your bootloader to flash the twrp . flash the recovery, then boot into the recovery and flash a custom kernel for marshmallow, and the supersu file. tgen boot up with root. that message is something that everybody gets. it because of your unlicked , just ignore it.
Click to expand...
Click to collapse
Thank you very much! Going to walk through these steps but wanted to tell you thank you before doing so as I imagine it's going to take a bit of time.
I very much appreciate your help!
-Eric

EricSB said:
Thank you very much! Going to walk through these steps but wanted to tell you thank you before doing so as I imagine it's going to take a bit of time.
I very much appreciate your help!
-Eric
Click to expand...
Click to collapse
so far ive used despair and elementalx kernels on marshmellow. if you want root, youre going to have to use a custom kernel.

simms22 said:
so far ive used despair and elementalx kernels on marshmellow. if you want root, youre going to have to use a custom kernel.
Click to expand...
Click to collapse
Bummer - Seem's Google is shying away from root. I imagine it's for security reasons. I've not used a custom kernel before so now is as good a time as any to learn. Which do you prefer despair or elementalx?
Thanks again for all your help!
-Eric

If all else fails use the nexus root toolkit to flash back to stock.

EricSB said:
Bummer - Seem's Google is shying away from root. I imagine it's for security reasons. I've not used a custom kernel before so now is as good a time as any to learn. Which do you prefer despair or elementalx?
Thanks again for all your help!
-Eric
Click to expand...
Click to collapse
they both are fine. elemental uses a different installer that gives you options when flashing via twrp. despair would be simpler. plus, youll need to downliad a kernel control app from thd play store. there are many free and paid versions.

kclive said:
If all else fails use the nexus root toolkit to flash back to stock.
Click to expand...
Click to collapse
That is useful to know, I didn't actually realize there was a toolkit for doing this. I will bookmark it in case I REALLY screw up. Thanks for the help!
I used to be a Windows Phone user, so having all this control and ability to customize down to the kernel level is all very new to me, suffice it to say, I've been missing out and am glad I made the switch and won't ever go back.
-Eric

simms22 said:
they both are fine. elemental uses a different installer that gives you options when flashing via twrp. despair would be simpler. plus, youll need to downliad a kernel control app from thd play store. there are many free and paid versions.
Click to expand...
Click to collapse
You've been a tremendous help and I can't thank you enough. I'm so happy to have my phone back to a working state! I feel like such a n00b, but I guess I've got to start some where. I hate to keep bugging you, but what kernel management app do you prefer to use? I like to make sure I get input from people who know what they are doing and I don't want to choose an app that is going to wind up causing me more issues.
Thanks again!
-Eric

EricSB said:
You've been a tremendous help and I can't thank you enough. I'm so happy to have my phone back to a working state! I feel like such a n00b, but I guess I've got to start some where. I hate to keep bugging you, but what kernel management app do you prefer to use? I like to make sure I get input from people who know what they are doing and I don't want to choose an app that is going to wind up causing me more issues.
Thanks again!
-Eric
Click to expand...
Click to collapse
i use the older elementalx kernel control app. but google pulled it from the store. i bought it, and had a copy, so i use it. trickstermod is a decent free kernek control app

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!