Related
Is there a way I can root with 4.4? I have an unlocked bootloader but the SlapMyMoto method fails me everytime at the impactor 2222 step & even when I try to troubleshoot by using the small windows guide method provided by Jcase. I might be wrong entirely and there isn't yet a root for 4.4, if so let me know that way I don't sound too ignorant. :good:
Demorthus said:
Is there a way I can root with 4.4? I have an unlocked bootloader but the SlapMyMoto method fails me everytime at the impactor 2222 step & even when I try to troubleshoot by using the small windows guide method provided by Jcase. I might be wrong entirely and there isn't yet a root for 4.4, if so let me know that way I don't sound too ignorant. :good:
Click to expand...
Click to collapse
Flash twrp recovery by hashcode and flash supersu zip and you're all done
Sent on my Moto X
Is there any possibility there's a way I can root it without a custom recovery though? I understand that it is the easiest way to root, but I'd like to try and keep it stock, that's been my main difficulty thus far.
Demorthus said:
Is there any possibility there's a way I can root it without a custom recovery though? I understand that it is the easiest way to root, but I'd like to try and keep it stock, that's been my main difficulty thus far.
Click to expand...
Click to collapse
No, you already unlocked your boot loader , so you're already swimming in the swallow end so you may as well swim over to the deep end
Sent on my Moto X
flashallthetime said:
No, you already unlocked your boot loader , so you're already swimming in the swallow end so you may as well swim over to the deep end
Sent on my Moto X
Click to expand...
Click to collapse
Alright I'll get right on it then! Thanks x2 . Just as a side question since I've only had my Moto X for about a week and a half, will I still be able to continue to use touchless control and updates for it just as so long as I dont flash a custom rom? I want this puppy as stock as possible
Demorthus said:
Alright I'll get right on it then! Thanks x2 . Just as a side question since I've only had my Moto X for about a week and a half, will I still be able to continue to use touchless control and updates for it just as so long as I dont flash a custom rom? I want this puppy as stock as possible
Click to expand...
Click to collapse
As long as you run the stock ROM you'll have all the great features , if you use xposed framework and gravity box you'll have all the features that cyanogenmod has plus all moto's great features too, win win
Sent on my Moto X
Demorthus said:
I want this puppy as stock as possible
Click to expand...
Click to collapse
Why did you unlock your bootloader then?
http://forum.xda-developers.com/showthread.php?t=2573212
From what I was following it appeared to be as though it was necessary, but I misinterpreted it. But, it's too late now for any changes, sadly and unfortunately.
get TWRP, xposed framework, with gravitybox and google search api. learn to use tasker and all of its major plugins, you will have a blast with the moto x. the possibilities are endless.
Does it present any security issues to unlock a bootloader without rooting? I don't mean if you lose your phone, I mean is there a security issue with any apps you install?
That's always a risk. Read playstore comments before installing anything.
Has nothing to do with being rooted or not...or boot loader state.
Sent from my Moto X cellular telephone...
Cozume said:
Does it present any security issues to unlock a bootloader without rooting? I don't mean if you lose your phone, I mean is there a security issue with any apps you install?
Click to expand...
Click to collapse
You could have asked at AC and I would answer it over there.
Unlocking bootloader and/or running custom recovery is a big risk. When you unlocked bootloader, all the partitions in your phone can be accessed and modified. I can flash custom recovery to your phone. Custom recovery give full root access to the phone. It is then easily possible to copy all your data from the phone and also disable the lock for your phone. Although if you encrypt your phone, then custom recovery will require the password to give access to the /data partition, which is where all the user datas are. I guess if someone is determine enough, then they can make an image copy of your phone and try to decrypt it.
If you want to keep your data safe, disable USB Debugging (because exploits can be used with ADB to gain access to the phone), use stock recovery and lock bootloader. However, if the phone brick then you can't get back your data in the phone.
eksasol said:
Unlocking bootloader and/or running custom recovery is a big risk. When you unlocked bootloader, all the partitions in your phone can be accessed and modified.
Click to expand...
Click to collapse
but can an app do this? And if so, what permissions would the app need to do this. Also, I am not talking about flashing a custom recovery; just an unlocked bootloader.
eksasol said:
If you want to keep your data safe, disable USB Debugging (because exploits can be used with ADB to gain access to the phone), use stock recovery and lock bootloader.
Click to expand...
Click to collapse
but can an app do harm to your phone if you have USB debugging enabled? I know a person who finds your phone can. I am asking about apps.
Cozume said:
but can an app do this? And if so, what permissions would the app need to do this. Also, I am not talking about flashing a custom recovery; just an unlocked bootloader.
Click to expand...
Click to collapse
If the phone isn't root, then probably not, unless there is some security holes it can exploit. With root it is possible to modify the whole system. Motorola and HTC have an extra layer to prevent simple root to modify the system partition, but as you can see, just visit dev section if you want to remove it.
but can an app do harm to your phone if you have USB debugging enabled? I know a person who finds your phone can. I am asking about apps.
Click to expand...
Click to collapse
It is possible for apps to get access to sensitive data and change system settings with USB Debugging enabled. Helium required it turned on to make backup of your contacts, sms and apps data for example.
If you have an older Android phone, you don't need to do anything except to enable USB Debugging and run a program to install root. But we're trusting apps like SuperUser and SuperSU to control apps access to root, so that's a layer of protection. But KitKat is much safer now.
You don't need root to install malware and virus to your phone. Just download an infected app or use unreliable app stores like Aptoide. Also if you have the option "Unknown sources" enabled, which almost all of us do, the app can utilize it to automatically install other apps in the background.
Point I'm trying to make is, if the phone have unlocked bootloader, or even locked bootloader with custom recovery, and someone else have a hold of it, then all bets are off.
eksasol said:
If the phone isn't root, then probably not, unless there is some security holes it can exploit. With root it is possible to modify the whole system.
Click to expand...
Click to collapse
great, that is what I want to know. I knew a human being in possession of your phone could do more damage if it were unlocked, which is why I got rid of the bootloader unlocked warning message.
BTW - do you know if flashing the original kit kat boot logo to replace the bootloader warning message presents a problem for accepting the OTA update to 4.4.2?
eksasol said:
Motorola and HTC have an extra layer to prevent simple root to modify the system partition, but as you can see, just visit dev section if you want to remove it.
Click to expand...
Click to collapse
Ok so then on my Moto X, since flashing a new logo doesn't even require root, it shouldn't have affected any system files and then it would be safe to take the OTA after removing the bootloader unlocked warning?
eksasol said:
It is possible for apps to get access to sensitive data and change system settings with USB Debugging enabled. Helium required it turned on to make backup of your contacts, sms and apps data for example.
Click to expand...
Click to collapse
good to know!
eksasol said:
But we're trusting apps like SuperUser and SuperSU to control apps access to root, so that's a layer of protection.
Click to expand...
Click to collapse
ok, that is how I understand it. Unless I give the app access to root through SuperSU, it can't.
eksasol said:
But KitKat is much safer now.
Click to expand...
Click to collapse
why is this?
eksasol said:
Also if you have the option "Unknown sources" enabled, which almost all of us do, the app can utilize it to automatically install other apps in the background.
Click to expand...
Click to collapse
thanks, Amazon app store required that to be enabled to load apps from their app store.
Cozume said:
great, that is what I want to know. I knew a human being in possession of your phone could do more damage if it were unlocked, which is why I got rid of the bootloader unlocked warning message.
Click to expand...
Click to collapse
BTW - do you know if flashing the original kit kat boot logo to replace the bootloader warning message presents a problem for accepting the OTA update to 4.4.2?
Ok so then on my Moto X, since flashing a new logo doesn't even require root, it shouldn't have affected any system files and then it would be safe to take the OTA after removing the bootloader unlocked warning?
Click to expand...
Click to collapse
That depend on the checking that the dev put in the OTA package. On the Nexus device, if you are missing any original system APK, modify the radio partition, modify GPS setting file, or modify the build.prop, etc, the OTA will fail. So I assume the same with Moto X OTA. The safest bet is to make sure all the partition are original first (except the /data partition where your data resides) before receiving an OTA.
ok, that is how I understand it. Unless I give the app access to root through SuperSU, it can't.
Click to expand...
Click to collapse
Yes. The actual component of root isn't the SuperSU app, but a 'su' binary. Without the SuperSU app, anything can have full fledged root access. You need SuperSU to control that access.
why is this?
Click to expand...
Click to collapse
For many reason, I'm not a developer so I can only talk about what I know and seen from a user perspective. It used to be that you can flash an exploited update.zip to modify the stock recovery of Android, in order to make it ignore the package signatures, so the recovery could flash any package without the correct signature. Now there are no such exploits for latest stock recovery. With USB Debugging enabled in Android 4.3 or newer, it would not even allow access when connected to a PC unless you accept to trust that PC in a pop up dialog in the phone, I'm not sure if it's mean the phone is totally invulnerable to exploits (like memory overflow), you'll have to ask someone smarter. Also apps like Framaroot that I just linked won't work anymore.
eksasol said:
That depend on the checking that the dev put in the OTA package. On the Nexus device, if you are missing any original system APK, modify the radio partition, modify GPS setting file, or modify the build.prop, etc, the OTA will fail. So I assume the same with Moto X OTA. The safest bet is to make sure all the partition are original first (except the /data partition where your data resides) before receiving an OTA. My guess is if you tried it with modified logo it will either fail or overwrite it.
Click to expand...
Click to collapse
OK, I think I am going to unroot and flash back to stock just to be sure.
Thanks again! I would hit the thanks button but I used up all my thanks today and it won't let me.
Cozume said:
OK, I think I am going to unroot and flash back to stock just to be sure.
Thanks again! I would hit the thanks button but I used up all my thanks today and it won't let me.
Click to expand...
Click to collapse
You already gave me enough thanks at AC.
eksasol said:
You already gave me enough thanks at AC.
Click to expand...
Click to collapse
what is your user name there?
Cozume said:
what is your user name there?
Click to expand...
Click to collapse
someguy
Why so paranoid? Have you read any posts on xda of such things....I haven't.
If you are sideloading apps the risk increases for sure. But apps on the play store would have tonnes of comments about it if the app was screwing up the system.
Sent from my Moto X cellular telephone...
eksasol said:
someguy
Click to expand...
Click to collapse
ok great!
kj2112 said:
Why so paranoid? Have you read any posts on xda of such things....I haven't.
If you are sideloading apps the risk increases for sure. But apps on the play store would have tonnes of comments about it if the app was screwing up the system.
Click to expand...
Click to collapse
I am just trying to understand how all of this works.
Okay one thing why are you trying to unlock the bootloader without rooting?? Or did I read everything wrong? And yes unlocking the bootloader allows you to write to every partition of the phone. Except when HTC and you're s-on you have to manually flash the boot.img via fastboot. But with moto. There is no point in unlocking the bootloader if you're not doing anything. Two it voids your warranty. Three it can disable functions on your phone like features, camera options I think and yeah etc. But if you follow instructions you won't have any problems ever rooting or shouldn't if you semi have a brain and know how to follow instructions if not well you can somewhat brick :$ I don't mess with moto much but I have. Sorry this thread was in my latest and scrolling through xda. Lol. You can unlock you're phone straight from the moto website. But if you're not rooting. Eh no point.
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off
I just read this thread, particularly page 2 why we can't relock the Motorola bootloader (yet it seems), unlike Nexus devices, I think it's really bad for security.
edit: link: http://forum.xda-developers.com/showthread.php?t=2575586&page=2
pball52998 said:
Okay one thing why are you trying to unlock the bootloader without rooting??
Click to expand...
Click to collapse
I rooted but a friend of mine is unlocked but not rooted. She wanted to be unlocked because it wipes your device so wanted to do it before she got the phone all set up. She is afraid of rooting. Anyhow, maybe she shouldn't have unlocked but she did.
pball52998 said:
There is no point in unlocking the bootloader if you're not doing anything. Two it voids your warranty.
Click to expand...
Click to collapse
She has the dev ed so it doesn't void her warranty. And she may want to Wifi tether in the future so I told her she needs to unlock and root for that so get the dev ed. She did and unlocked but is afraid to go any further.
pball52998 said:
You can unlock you're phone straight from the moto website. But if you're not rooting. Eh no point.
Click to expand...
Click to collapse
It increases the phone's resale value to unlock it.
eksasol said:
I just read this thread, particularly page 2 why we can't relock the Motorola bootloader (yet it seems), unlike Nexus devices, I think it's really bad for security.
Click to expand...
Click to collapse
I thought I saw a thread where someone could relock the Moto X bootloader.
And what about this?
Re-Lock Your Bootloader
It should just be a command like fastboot_oem_lock or something but idk. And two if she has the dev edition. Root that thing!!! XD that's what it's for!! Just install twrp via goo manager. Wipe factory reset all that good stuff. After making a back up. Notice after backing up. Then flashing rom and gapps In that order. I mean its a lot easier than htc rezound or htc one, htc in general and such lol.
Sent from my crappy apple iPad.....
pball52998 said:
Wipe factory reset all that good stuff. After making a back up.
Click to expand...
Click to collapse
well, I didn't wipe and do a factory reset when I rooted so I guess I did it wrong, lol! That is what she is afraid of - not doing it right and messing up her phone.
And I don't have a backup, but do I really need one if I can flash the factory images?
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
With the new features in Marshmallow, what are the remaining reasons to still root it?
Thanks.
jsk108 said:
With the new features in Marshmallow, what are the remaining reasons to still root it?
Thanks.
Click to expand...
Click to collapse
Well if you like to theme layers works naively on M. You just need root and a kernel that allows r/w. That's one good reason for it.
Sent from my Nexus 6 using Tapatalk
jsk108 said:
With the new features in Marshmallow, what are the remaining reasons to still root it?
Thanks.
Click to expand...
Click to collapse
For me, adaway and debloating are big. Custom kernal so I can properly adjust my screen calibration to. Its way to yellow on the nexus 6.
jsk108 said:
With the new features in Marshmallow, what are the remaining reasons to still root it?
Thanks.
Click to expand...
Click to collapse
to access system files, to change or delete them. cant do it without root. to make sure that my n6 is the fastest n6 around. but thats just one if many reasons. no, you do not need root to flash roms or kernels. you do need root to use the apps to control them.
Mr Patchy Patch said:
For me, adaway and debloating are big. Custom kernal so I can properly adjust my screen calibration to. Its way to yellow on the nexus 6.
Click to expand...
Click to collapse
Can you have an expanded desktop and pie controls without rooting on M? Those would be amongst my main reasons at this point. Thanks!
jsk108 said:
Can you have an expanded desktop and pie controls without rooting on M? Those would be amongst my main reasons at this point. Thanks!
Click to expand...
Click to collapse
yes. you can flash a rom that has them included. you do not need root to flash a recovery, nor do you need root to flash roms/kernels.
Root is a necessity for since I need to block ads. So basically for Adaway.
Sent from my Nexus 6 using Tapatalk
One word: Xposed
Astro file manager can't seem to access my internal sdcard suddenly. Also life without Adaway is intolerable. Don't they realize we escaped to the internet to get away from overbearing ads?
change build.prop to allow wifi tethering and add few other items I think my phone should have that the carrier doesnt
simms22 said:
yes. you can flash a rom that has them included. you do not need root to flash a recovery, nor do you need root to flash roms/kernels.
Click to expand...
Click to collapse
I really had no clue that you didn't need Root to flash a Rom.. This is my first Nexus device. I have owned 5 android devices and always rooted to flash custom roms. You just blew my mind.
tj_ona said:
I really had no clue that you didn't need Root to flash a Rom.. This is my first Nexus device. I have owned 5 android devices and always rooted to flash custom roms. You just blew my mind.
Click to expand...
Click to collapse
you do not need root, but you need an unlocked bootloader and to fastboot flash twrp recovery(so you can flash roms or kernels). the only thing that you would need root for is an app to control kernels. but if youre not into controlling kernels, then no root is needed
I didn't even root my phone on Lollipop. Made a few changes in recovery, and had custom recovery, but that was the extent of my changes.
Sent from my Nexus 6
sansnil said:
One word: Xposed
Click to expand...
Click to collapse
Unfortunately, Xposed isn't out for Marshmallow yet.
I unencrypted and the only benefit I see to not having root is that you can do OTA's but since unencrypting and custom recovery took that away I might as well get root and enjoy viper4android, ad-block, custom kernels, play music exporter, no nag tethering (yes I pay for it, just hate when the checking subscription stalls cuz AT&T can't be bothered to fix it), etc.
JimSmith94 said:
Unfortunately, Xposed isn't out for Marshmallow yet.
Click to expand...
Click to collapse
I know that, but it will be eventually.
Titanium Backup.
Pretty much the same reason to root L.
Can't think of a single root function that's now stock?
jsk108 said:
With the new features in Marshmallow, what are the remaining reasons to still root it?
Thanks.
Click to expand...
Click to collapse
If you're not sure if you want to root it, then don't.
scryan said:
Pretty much the same reason to root L.
Can't think of a single root function that's now stock?
Click to expand...
Click to collapse
App permissions management used to require root and is now stock on 6.0. That's the first thing that pops into my head....
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!