Related
My apologies for taking so long, life is hectic. This is a "root path" for the 4.4 update, and in this case you will retain your stock recovery so features like remote wipe will continue to work. It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4. Unlike hte MotoX, you can not downgrade. This Must be preformed while on 4.2.2 before updating to 4.4
First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update.
Step1)
Unzip SlapMyMoto-1,0.zip and push the jar file to your internal storage
Code:
adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar
Step2)
Use http://www.cydiaimpactor.com/ to open up a telnet session as system user on port 2222. We covered how to use Impactor and telnet in the RockMyMoto root, I won't be covering it again since this post is going to be long enough already, see here -> http://forum.xda-developers.com/showthread.php?t=2509590 or http://rootzwiki.com/topic/107098-root-rockmymoto-yes-even-the-first-ota/
Connecting over telnet, and run Stage1 with this command:
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
When the device tells you to reboot, do this manually with "adb reboot" or your power button. It will not auto reboot on this step
Step3)
Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
Once the device has rebooted, please take the 4.4 OTA.
Step4)
Now that we are on 4.4, we can finish the process with adb shell:
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Then either wait, or toggle your bluetooth. Once the device reboots, you will have root.
So, if I have a root that I've gained with RockMyMoto I just need to take an OTA and start from the step 4 ?)
Sent from my XT1080 using Tapatalk
I was going to say what if we used voodoo un root then take the update when it comes hopefully restore with it? I know voodoo doesn't support 4.3+ but what if we achieved root on 4.2.2?
Sent from my XT1080 using Tapatalk
No....make sure you have write protection off with the MotoWPNoMo procedure jcase linked, then start at step 1. It's my understanding that if you start from step 4 nothing will work because 4.4 can't currently be rooted, so you go through all these other steps to maintain a root via 4.2.2. Besides that, with the 4.2.2 root, there's no recovery so if you tried to take it right away you'd just boot loop your phone. Someone correct me if I'm wrong.
Has this been verified? I saw people in another thread getting a "security version downgraded" error but could not figure out exactly what they did
Sent from my XT1080 using XDA Premium 4 mobile app
Another question I got root through rockmynoto. When I got my maxx I took the update to 12.15.15 do I still have to do all the steps?
Sent from my XT1080 using Tapatalk
Well, upon flashing back to 4.2.2, my phone says I don't need the update. It can't be polled, so I have no idea when it'll prompt me to do it again.
With my luck I'll have to wait until after the push window closes and it becomes a freeforall.
jcase said:
God-like abilities
Click to expand...
Click to collapse
Does anyone have the update.zip?
EDIT:
MAXX Camera Update: http://sbf.droid-developers.org/download.php?device=4&file=1
Mini Camera Update: http://sbf.droid-developers.org/download.php?device=2&file=6
Ultra Camera Update: http://sbf.droid-developers.org/download.php?device=1&file=8
i really dont feel like going back to 4.2.2 to root lol.. battery life is great.. think ill stick with 4.4 /4.1/.2 until there's an exploit for it.
shouldnt there be an "adb push su /sdcard/" somewhere
TheWhiteChallenger said:
shouldnt there be an "adb push su /sdcard/" somewhere
Click to expand...
Click to collapse
Nope
Sent from my HTC Two
digitaloutsider said:
Well, upon flashing back to 4.2.2, my phone says I don't need the update. It can't be polled, so I have no idea when it'll prompt me to do it again.
With my luck I'll have to wait until after the push window closes and it becomes a freeforall.
Click to expand...
Click to collapse
That's what I'm afraid of..I'm going to wait.
ok so im having major issues, idk if its the root method or the fact that i push the ota via adb, so ima keep that conversation here: http://forum.xda-developers.com/showthread.php?p=48656238&posted=1#post48656238 for now in an effort not to clutter this thread needlessly
but i would really appreciate any help, especially if jcase would like to take a peek and see if he know wtf i did wrong.
on the lighter side can someone whos done this tell me if we were suposed to get the new dialer or did our kitkat get shorted out of that?
Just verifying for everyone that I run a Droid Maxx and I am part of the soak test and This did work I am on 4.4 with Root and Hotspot active used another mod on here for that and Also google wallet working with touch 2 pay !!!
Thanks Jcase As you know I think you are the best !!!!
jcase said:
My apologies for taking so long, life is hectic. This is a "root path" for the 4.4 update, and in this case you will retain your stock recovery so features like remote wipe will continue to work. It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4.
First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update.
SlapMyMoto requires you to be on the 4.2.2 Camera update, you can find the firmware for your device below:
<someone please post the appropriate firmware links below, I dont have the droid devices here>
Step1)
Unzip SlapMyMoto-1,0.zip and push the jar file to your internal storage
Code:
adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar
Step2)
Use http://www.cydiaimpactor.com/ to open up a telnet session as system user on port 2222. We covered how to use Impactor and telnet in the RockMyMoto root, I won't be covering it again since this post is going to be long enough already, see here -> http://forum.xda-developers.com/showthread.php?t=2509590 or http://rootzwiki.com/topic/107098-root-rockmymoto-yes-even-the-first-ota/
Connecting over telnet, and run Stage1 with this command:
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
When the device tells you to reboot, do this manually with "adb reboot" or your power button. It will not auto reboot on this step
Step3)
Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
Once the device has rebooted, please take the 4.4 OTA.
Step4)
Now that we are on 4.4, we can finish the process with adb shell:
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Then either wait, or toggle your bluetooth. Once the device reboots, you will have root.
Click to expand...
Click to collapse
---------- Post added at 11:14 PM ---------- Previous post was at 11:09 PM ----------
My Dialer looks the same !!
TheWhiteChallenger said:
ok so im having major issues, idk if its the root method or the fact that i push the ota via adb, so ima keep that conversation here: http://forum.xda-developers.com/showthread.php?p=48656238&posted=1#post48656238 for now in an effort not to clutter this thread needlessly
but i would really appreciate any help, especially if jcase would like to take a peek and see if he know wtf i did wrong.
on the lighter side can someone whos done this tell me if we were suposed to get the new dialer or did our kitkat get shorted out of that?
Click to expand...
Click to collapse
jcase said:
Nope
Sent from my HTC Two
Click to expand...
Click to collapse
I cannot downgrade. I get an error that the bootloader noticed it was a downgrade....
Oh well, I guess I'll wait for something else.
dtreth said:
I cannot downgrade. I get an error that the bootloader noticed it was a downgrade....
Oh well, I guess I'll wait for something else.
Click to expand...
Click to collapse
What was the exact erro, what were you downgrading to, and what specific device?
I did not confirm downgrade was possible, so it may only apply to those that already were on 4.2.2
jcase said:
What was the exact erro, what were you downgrading to, and what specific device?
I did not confirm downgrade was possible, so it may only apply to those that already were on 4.2.2
Click to expand...
Click to collapse
I took the OTA 4.4, tried to downgrade to the link I provided earlier in the thread, I have a Droid MAXX. I don't remember exactly what it said but it was the same error I got when I tried to FXZ my Razr MAXX HD to 4.1.2 unlockable after I took 4.1.2 locked forever. I don't really want to do it again but I will for exact text.
EDIT:
I did it again, it said
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
I DID do MotoWpNoMo and it survived the OTA even without root or anything, so I'd be willing to test any methods you cook up to remedy this, if you do indeed attempt anything (and I'd also probably try to hug you through the computer somehow)
jcase said:
It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4.
Click to expand...
Click to collapse
Correct me if if I'm wrong, but this looks like I need to be on STOCK 4.2.2, correct?
I'm currently rooted with WP off on 4.2.2 (XT1080M, MAXX). When I run SlapMyMoto, it says rooted devices are not supported. If I'm understanding these steps correctly, I need only go back to stock 4.2.2 and then complete all of these steps. Can anyone that has completed these steps confirm this?
j.bruha said:
Correct me if if I'm wrong, but this looks like I need to be on STOCK 4.2.2, correct?
I'm currently rooted with WP off on 4.2.2 (XT1080M, MAXX). When I run SlapMyMoto, it says rooted devices are not supported. If I'm understanding these steps correctly, I need only go back to stock 4.2.2 and then complete all of these steps. Can anyone that has completed these steps confirm this?
Click to expand...
Click to collapse
I suggest doing a FXZ (w/ Keep Data) with House of Moto to get back to 4.2.2 stock without root. Be sure to flash the 12.15.15 firmware. You will not lose "WP off". Then proceed with the SlapMyMoto steps.
UPDATE: Success! Followed jcase's steps exactly and had no issues. One exception is that I installed the update from internal storage instead of an OTA.
A few other things I've noticed:
1. Recovery is now true recovery and is no longer the normal boot with "write protection off" (like it was with RockMyMoto). Now you see the Android with the red exclamation point like stock recovery.
2. MotoWpNoMo survives the 4.4 OTA!!!
3. Google hotword detection ("OK Google") in the GEL and GoogleNow isn't working. Moto X users on KitKat are seeing the same thing, so hopefully a fix is coming soon. Of course, Moto's Touchless Controls ("OK Google Now") still works like a charm.
Question...
Currently I'm on 4.2.2 no root, no WP off...fresh from the box...
I am not yet able to pull the update from the servers...should I wait till I get notification that there is an update to take? Or can I preemptively do steps 1-3 and then take the OTA whenever it comes and finish the process?
Sent from my XT1080 using Tapatalk
Here are instructions on how to unlock and root your htc desire 610. These work for both models, but the files are for the AT&T version.
BEFORE WE BEGIN, SOME TERMINOLOGY:
Unlocked Bootloader: HTCDev website will help us do this. It's free. It allows you to flash a recovery and signed boot image, which we have. It does not allow you to flash unsigned images.
S-On: Security on. This is how our phones come stock. Htc will not allow us to flash unsigned images because of this.
S-off: once someone achieves this for us, it will allow us to modify anything and everything, signed or not. We can flash new boot image and radios without worry of version number or signature.
Root: Allows you "administrative access" to your device, to move files and do certain things. However, our phone also has...
System Write Protection: HTC included this in the kernel, and it basically means that unless you have a kernel or boot image that gets around it, any changes you make to the system partition (aside from flashing in recovery) won't stick through a reboot. Essentially they will be temporary in an effort to preserve the phone. We don't like this.
Now then, with that out of the way...
1) HTCDev Bootloader Unlock: Under "Select Your Device", scroll ALL THE WAY TO THE BOTTOM, and choose "All Other Supported Models". I know it works, because I just did it. IT WILL WIPE YOUR DEVICE DATA. If you want the data backed up beforehand, turn on USB Debugging and use this command through adb to make a backup:
Code:
adb backup -apk -shared -all -f C:\desirebackup.ab
2)Download ClearD's Root Tool V3(USE VERSION 2.1 BELOW, VERSION 3 DOESN'T WORK FOR MOST PEOPLE): After you have drivers installed for your desire (install htc sync, plug in your phone, then let them load, then uninstall htc sync), fastboot turned off in the battery options in settings, and USB debugging turned on through the hidden developers menu, read the disclaimer in red below, and download and run this exe on your Windows machine with your phone plugged in. It'll install twrp recovery 2.8.0.1, install the engineering boot image, install SuperSU and root, and then install jmz's system-unlocked kernel to make root work like it should. I'm still working out kinks, so if it doesn't work right the first time, run it a second time! Thanks go to jmz, deez_troy, AdriVelazquez, and chainfire for the pieces to make this work.
DISCLAIMER: ONCE YOU USE THIS TOOL, YOUR DEVICE WILL HAVE THE ROOTED ENGINEERING BOOT IMAGE, WHICH CANNOT BE REVERSED. THERE ARE NO SIDE EFFECTS TO THIS IMAGE EXCEPT THAT IT SHOWS A DISCLAIMER ON YOUR SPLASH SCREEN WHEN YOU BOOT THE PHONE. THIS CANNOT BE CHANGED UNTIL WE GAIN S-OFF, WHICH HAS BEEN ACCOMPLISHED, BUT IS NOT YET PUBLICLY AVAILABLE. IF YOU ARE OK WITH THIS, PROCEED.
IF V3 DOESN'T WORK, HERE IS VERSION 2.1: Download ClearD's Root Tool V2.1. THIS VERSION INSTALLS ENGINEERING BOOT IMAGE AND JMZ KERNEL.
Return to Stock (AT&T ONLY) :http://dl3.htc.com/application/RUU_...16_10.20.4187.00L_release_392486_signed_2.exe
This ruu will bring you back to complete stock, version 1.50.502.7. It has to be run through Windows, and you have to have a locked bootloader to run it. If you're unlocked, you can relock it in fastboot with the command:
Code:
fastboot oem lock
. Feel free to unlock it again after updating through the RUU. You can use your original unlock token or get it again through htcdev.
Older root tool version 1:
Download ClearD's Desire 610 Root Tool V1. This version does not contain the engineering boot image, and needs it to work fully, thus is buggy and probably won't root you with one click. It will fail to adb remount, which will fail to auto install the zip files in recovery. If you've already flashed the engineering boot image, then it will work properly without issue. Otherwise, it'll place the root zip files on your phone, but you'll have to flash them manually in recovery.
Click to expand...
Click to collapse
Old manual method:
2) Recovery: After you're unlocked, download TWRP recovery from this thread, rename the image file to "recovery.img", and flash through fastboot with the command:
Code:
fastboot flash recovery recovery.img
This will give you the official Team Win Recovery Project recovery for our device, which will allow you to root.
3) Insecure Boot Image and Root: Once you have recovery installed, the rest is easy. In recovery, if you try to reboot back into the rom, it will ask you if you wish to root. Select yes. It will do the rest I believe, and install SuperSU when you boot back into the rom. You'll also want to download and flash JMZ's insecure kernel, which unlocks the system file lock that htc places on their newer devices. Once flashed, you can then change system files and the changes will stick through reboots.
Click to expand...
Click to collapse
HTC Engineering Boot Image:
Once unlocked, download the root zip provided in this thread, then open it. We can't just flash the zip file because most of us have an updated rom version than the one it was intended for, and I'm not sure how to fix that. But no bother. Pull out the boot image file, and place it somewhere you can find it. I put it right in my MiniADB/Fastboot folder for easy access. Then, you need to flash it. Here's how:
Code:
fastboot flash boot boot_root.img
You'll then have an insecure boot image, and it will say so on your splash screen. Trust me, the words are pretty ominous.
To restore your backup you made before unlocking, use this in adb:
Code:
adb restore C:\desirebackup.ab
Click to expand...
Click to collapse
A few superstars are currently working on s-off, and this will be updated once that occurs.
Special thanks to:
-JMZ (Recovery and Kernel)
-Deez_Troy (officiating recovery)
-AdriVelazquez (Insecure boot image)
-Chainfire (SuperSu)
Also, to save this spot and before I forget it going to sleep tonight, I'm actually not sure if firewater or sunshine will work or not yet because I haven't gotten app root yet for them to function. I'll have to get that, then we'll try one or the other of those. /end thought
Edit: I do believe we will need the wp_mod to disable system write protection and allow su to stick before we continue. That'll allow us full root. Or, we could continue with a twrp build or a Clockworkmod build if someone can assist.
ClearD said:
Edit: I do believe we will need the wp_mod to disable system write protection and allow su to stick before we continue. That'll allow us full root. Or, we could continue with a twrp build or a Clockworkmod build if someone can assist.
Click to expand...
Click to collapse
I could help with that, but you will have to build, I currently don't have a cyanogenmod source around. I need outputs of:
cat /proc/emmc
mount
cat /system/build.prop #<-- root maybe required
and I need your stock recovery.img, try getting it from an ota, or using dd.
The kernel source for this phone is released, you don't need to use the wp_mod.
It is? Where did you find it released? And how would we go about getting system writable without wp_mod? I'm still trying to work out all the kinks and have never built from source.
The outputs you need should be in my dev info thread except for the build prop, but I can remount and pull that.
ClearD said:
It is? Where did you find it released? And how would we go about getting system writable without wp_mod? I'm still trying to work out all the kinks and have never built from source.
The outputs you need should be in my dev info thread except for the build prop, but I can remount and pull that.
Click to expand...
Click to collapse
? never built from source? You are RD!
http://www.htcdev.com/devcenter/downloads Filter device desire 610.
About the system write protection: https://github.com/dummie999/android_kernel_htc_z4u/commit/19626f6c38b56b715dcc0b005ec8b82ce8ca264a
Should work
Well, build.prop then,
Edit: I need your stock recovery. You can get this with:
Code:
dd if=/dev/block/mmcblk0p41 of=/path/to/file/recovery.img
But you'll need busybox installed.
Edit2: You play subwaysurf! :highfive:
dummie999 said:
? never built from source? You are RD!
http://www.htcdev.com/devcenter/downloads Filter device desire 610.
About the system write protection: https://github.com/dummie999/android_kernel_htc_z4u/commit/19626f6c38b56b715dcc0b005ec8b82ce8ca264a
Should work
Well, build.prop then,
Edit: I need your stock recovery. You can get this with:
Code:
dd if=/dev/block/mmcblk0p41 of=/path/to/file/recovery.img
But you'll need busybox installed.
Edit2: You play subwaysurf! :highfive:
Click to expand...
Click to collapse
I'll add this hear also since I was adding it to the rooted forum. But dummie999 is right.
AdriVelazquez said:
That logic is sound; however slight differences in the model maybe.
Currently in the M8 this file is located in block/blk-core.c, which has the following.
Code:
#ifdef CONFIG_MMC_MUST_PREVENT_WP_VIOLATION
sprintf(wp_ptn, "mmcblk0p%d", get_partition_num_by_name("system"));
if (!strcmp(bdevname(bio->bi_bdev, b), wp_ptn) && !board_mfg_mode() &&
(get_tamper_sf() == 1) && (bio->bi_rw & WRITE)) {
pr_info("blk-core: Attempt to write protected partition %s block %Lu \n",
bdevname(bio->bi_bdev, b), (unsigned long long)bio->bi_sector);
err = 0;
goto wp_end_io;
} else if (atomic_read(&emmc_reboot) && (bio->bi_rw & WRITE)) {
pr_info("%s: Attempt to write eMMC, %s block %Lu \n", current->comm,
bdevname(bio->bi_bdev, b), (unsigned long long)bio->bi_sector);
err = -EROFS;
goto wp_end_io;
}
#endif
That line of code will need to be intercepted at boot to allow permanent root.
I haven't checked recently, but is the source for desire 610 posted?
Click to expand...
Click to collapse
Also, you'll need to build from source for this.
Also, you can just create modules to intercept the data on boot, which would be easier.
AdriVelazquez said:
Also, you can just create modules to intercept the data on boot, which would be easier.
Click to expand...
Click to collapse
Lol, no I couldn't get that working , compiling from source was a lot easier, at least for my d500
Edit:
My company has actually done a lot of work with the desire 610 and HTC, unfortunately some proprietary. But other's aren't.
Click to expand...
Click to collapse
Just curious, where do you work?
I usually build from pre built stock, then change what I want through decompiling and recompiling, also do gui things and script things and theme things. This is new territory, but nothing I'm not uncomfortable doing by any means. I'll work on it tonight.
Also, those outputs were not from my device, but from an unlocked and s-off device of a friend lol. I noticed that also, but was too lazy to remove it.
ClearD said:
I usually build from pre built stock, then change what I want through decompiling and recompiling, also do gui things and script things and theme things. This is new territory, but nothing I'm not uncomfortable doing by any means. I'll work on it tonight.
Click to expand...
Click to collapse
Well, then I hope you have a linux pc/laptop somewhere around
Good luck!
dummie999 said:
Well, then I hope you have a linux pc/laptop somewhere around
Good luck!
Click to expand...
Click to collapse
One of each. we'll see what happens lol.
dummie999 said:
Lol, no I couldn't get that working , compiling from source was a lot easier, at least for my d500
Edit:
Just curious, where do you work?
Click to expand...
Click to collapse
Yonder Music. It's a new music streaming app.
ClearD said:
One of each. we'll see what happens lol.
Click to expand...
Click to collapse
http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source before I forget. There is also a readme included with your download.
AdriVelazquez said:
Yonder Music. It's a new music streaming app.
Click to expand...
Click to collapse
Why do you make your devices S-off? (the thread in general)
dummie999 said:
http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source before I forget. There is also a readme included with your download.
Why do you make your devices S-off? (the thread in general)
Click to expand...
Click to collapse
Instead of you paying a subscription fee every month, Yonder Music sells the app bundled with the phone which you have free streaming music for the lifetime of the device.
S-off let's us do all of that.
The only source code currently offered by HTC is:
Device Carrier Region Type Kernel Android Size Description
Desire 610
Vodafone
UK
CRC
3.4.0
v4.4.2 152 MB
1.29.161.2
Desire 610
Vodafone
CH GER
CRC
3.4.0
v4.4.2 155 MB
1.29.166.2
Any idea if either of those would work? :/
ClearD said:
The only source code currently offered by HTC is:
Device Carrier Region Type Kernel Android Size Description
Desire 610
Vodafone
UK
CRC
3.4.0
v4.4.2 152 MB
1.29.161.2
Desire 610
Vodafone
CH GER
CRC
3.4.0
v4.4.2 155 MB
1.29.166.2
Any idea if either of those would work? :/
Click to expand...
Click to collapse
They usually work, you just have to be sure that your software version (1.29.sth) matches. For example, if you are on 1.29.401.3, it should work. I'm not sure, but I think this usually is only a problem on high end smartphones (one m7&m8), because the carriers there modify the kernels of those devices.
Mine (and I assume others) are on 1.30.x.x
ClearD said:
Mine (and I assume others) are on 1.30.x.x
Click to expand...
Click to collapse
Try it anyway, it might work. For example:
On my phone, the kernel for 1.20 runs fine on 1.13 1.10 1.16, but it doesn't run on 1.26 1.32 1.34. You can't know if it works before you try it.
Root achieved thanks to jmz (confirmed on my unit after his) , s-off is being worked on (by pros, not by me). Jmz built us a twrp recovery that allows for an easy root. Hopefully it'll be released to the masses soon!
first post
Does this image works with At&t devices because I am running firmware 1.19.502.4 not sure if it would stop me from booting...I have attained root by using TWRP however nothing sticks whenever i restart my phone so I was hoping this would be a solution
Shattariff said:
Does this image works with At&t devices because I am running firmware 1.19.502.4 not sure if it would stop me from booting...I have attained root by using TWRP however nothing sticks whenever i restart my phone so I was hoping this would be a solution
Click to expand...
Click to collapse
Nope that wont fix it. I am working on a kernel that will solve that problem
General info:
There will be a lot of discussion, do not follow untested tuts in this thread. It could cause you to brick your phone into a Cool paperweight.
AS OF 9/1/2015
XT1528-Surnia_Verizon
Board- MSM8916
Bootloader-NOT UNLOCKABLE!- EVEN IF YOU GO THROUGH MOTO'S WEBSITE (Verizon Locked it, not moto. & verizon cant unlock it) Viewable by booting into recovery & reading the screen.
Android 5.0.2-armv7l-240 DPI
Updated to 5.1
200MHz-1.21GHz quad core-Qualcomm Snapdragon 400/410
Root- No Write/full access-Cant seem to uninstall system apps on Android 5.0?/5.1
Screenshot: Attached at bottom of KINGROOT APK(4.5) via One click root method working on my updated 5.1 lolipop xt1528.
KingRoot does not root your device, just allows for removal of pre installed software via kinguser.After uninstalling, it crashed my Google launcher app & was fixed via rebooting which caused my system to have to re-optimize all apps which took 5 minuets. Root access is denied. Autostart manager works
Unrootable, Locked bootloader, but excellent capability. I love 5.1 better. I wouldnt recommend this device for anonymous browsing (I like to use Tor as a VPN), torrenting, or sharing. But I love the battery (lasts all day without heavy gaming use), phone calls & txts, Browsing the web is good too. I love being able to take out my phone and say "Ok Google" to vocally search or open things (like cortana) and my phone talk back. As well as the easy-to Use feeling comes if you've expierienced 5.0 before, a little confusing if you've been stuck on <4.0.I feel comfortable with it & it fits in my pocket pretty well. I don't know how much radiation it throws off... I say 7/10 overall. No xposed, if your lucky to rebuild the APK & patch it you can do it.. 4g is awesome! & I'm happy I didn't go with a free phone. Although, i'll be getting one soon to play with.
Thank you, Thanks for reading, & Have a wonderful day! (ALL Useful info & credits to who said it will be added via a reserved spot below.)
LATEST Answers :SU-ME didnt work for me on 5.0, and even though KingRoot said i had root access, It wouldnt give it to anything or allow write access.... Also, I attempted to root 5.1 off the v4.1 apk. It said root strategy available-Gave me (nothing past words)root access-But caused a bunch of apps to continuously crash. (I'll try it again once i go through my dev settings, i also factory wiped it earlier). It said i could remove system apps, It couldnt though. I used the auto-start manager too (we'll see if that stuck). (pics below) Also, Anyone who provides any testing will get thanked & a name below.
_______________________________________
| RESERVED |
| Thank you, kmani.k78 |
| Whoareyou |
| DBlake1 |
Yep it is possible to root.
First download supersu.zip here-
https://download.chainfire.eu/696/SuperSU
Now install custom recovery on your device using adb and fastboot. (TWRP is preferred coz many reported cwn not working)
Once twrp is installed boot in recovery.
Then tap install and select the supersu.zip where u downloaded it.
Just flash it and tada!!
Reboot in system and your moto e with lollipop is rooted.
I rooted by same method.
#peace and hope it helped you.
The hardest part is unlocking the bootloader. Without that, it's impossible to root.
I wish I had seen this thread before I picked up this phone today. :/
As I did pick one up as something to play with and not necessarily just for custom roms, I'm not immediately returning it, but it's a strong possibility.
Manish_Sky said:
Yep it is possible to root.
First download supersu.zip here-
https://download.chainfire.eu/696/SuperSU
Now install custom recovery on your device using adb and fastboot. (TWRP is preferred coz many reported cwn not working)
Once twrp is installed boot in recovery.
Then tap install and select the supersu.zip where u downloaded it.
Just flash it and tada!!
Reboot in system and your moto e with lollipop is rooted.
I rooted by same method.
#peace and hope it helped you.
Click to expand...
Click to collapse
When I try installing twrp via fastboot I receive a preflash error. I have yet been able to boot into recovery., I just get a red triangle and "no command" . What am I doing incorrect?
I don't understand the recovery mode for this phone, I'm used to 4.0.4 lol. I'm not sure either. I thought I broke my system when I tried to adb flash twrp & found out you can't shut your phone off when its in recovery mode. (Also, you can't flash without unlocking the bootloader) DUH right?
Manish_Sky said:
Yep it is possible to root.
First download supersu.zip here-
Now install custom recovery on your device using adb and fastboot. (TWRP is preferred coz many reported cwn not working)
Once twrp is installed boot in recovery.
Then tap install and select the supersu.zip where u downloaded it.
Just flash it and tada!!
Reboot in system and your moto e with lollipop is rooted.
I rooted by same method.
#peace and hope it helped you.
Click to expand...
Click to collapse
You can't flash without an unlocked bootloader. The XT1528 isn't supported by Motorola for unlocking because its a Verizon phone. Verizon doesn't like giving out codes, and wouldn't even if you asked. I think unless someone can Dev the crap outta it, We're screwed XT1528 wise. But, I don't know much about anything lol. I'm still learning.
Manish_Sky said:
Yep it is possible to root.
First download supersu.zip here-
https://download.chainfire.eu/696/SuperSU
Now install custom recovery on your device using adb and fastboot. (TWRP is preferred coz many reported cwn not working)
Once twrp is installed boot in recovery.
Then tap install and select the supersu.zip where u downloaded it.
Just flash it and tada!!
Reboot in system and your moto e with lollipop is rooted.
I rooted by same method.
#peace and hope it helped you.
Click to expand...
Click to collapse
this is not possible on verizon version xt1528. bootloader is unlockable. will need an android 5 vulnerability to gain root which is the best the verizon version will ever get.
Most likely way to root this phone would be to use an app that has a Lollipop exploit, but they're getting harder according to this article:
http://www.androidpolice.com/2014/1...ew-modified-kernels-may-become-a-requirement/
Okay so now I have gone and picked up the AT&T XT 1527 version. I now have a XT 1528 I can test with. Question, should I go ahead and root the XT 1527? I am thinking about wiping everything off Verizon phone and installing Fedora on it, but if there are other suggesting, I now have a test sled that can be used. I am open to suggestions with the verizon phone, let me know what you all think.
XT1528 can be rooted by "Kingroot" method - a closed source app!
kmani.k78 said:
XT1528 can be rooted by "Kingroot" method - a closed source app!
Click to expand...
Click to collapse
Have you tried it yourself?
Sent from my XT1528
Ace42 said:
Have you tried it yourself?
Sent from my XT1528
Click to expand...
Click to collapse
Yes I have already rooted my xt1528.
kmani.k78 said:
Yes I have already rooted my xt1528.
Click to expand...
Click to collapse
Have you used any GSM sim in India with Verizon Moto E?
Are you getting 3G?
And if you are using with CDMA, atleast 3G working with that?
I will be receiving mine tomorrow, dunno if it works or not
kmani.k78 said:
Yes I have already rooted my xt1528.
Click to expand...
Click to collapse
Can somebody please confirm?
Thanks!
Just run on XT 1528 android 5.1..... not rooted according to root check
Harish_Kumar said:
Have you used any GSM sim in India with Verizon Moto E?
Are you getting 3G?
And if you are using with CDMA, atleast 3G working with that?
I will be receiving mine tomorrow, dunno if it works or not
Click to expand...
Click to collapse
I am using it on Reliance CDMA netowrk. When it was on 5.0.2, I could able to connect to 3G.
But After update to 5.1, I could not use 3G. Only call & sms working.
I have rooted xt1528 in android 5.1 to make modification in the system partition. Rooting works perfectly. but changes made to system partition revert backs to stock after reboot.
Could anyone help me to make permanent changes to /system/build.prop file?
kmani.k78 said:
I am using it on Reliance CDMA netowrk. When it was on 5.0.2, I could able to connect to 3G.
But After update to 5.1, I could not use 3G. Only call & sms working.
I have rooted xt1528 in android 5.1 to make modification in the system partition. Rooting works perfectly. but changes made to system partition revert backs to stock after reboot.
Could anyone help me to make permanent changes to /system/build.prop file?
Click to expand...
Click to collapse
How did you root your XT1528? Link?
Whyzor said:
How did you root your XT1528? Link?
Click to expand...
Click to collapse
I followed this video - https://www.youtube.com/watch?v=QicDqTKb_sU
kmani.k78 said:
I followed this video - https://www.youtube.com/watch?v=QicDqTKb_sU
Click to expand...
Click to collapse
kmani.k78 said:
I am using it on Reliance CDMA netowrk. When it was on 5.0.2, I could able to connect to 3G.
But After update to 5.1, I could not use 3G. Only call & sms working.
I have rooted xt1528 in android 5.1 to make modification in the system partition. Rooting works perfectly. but changes made to system partition revert backs to stock after reboot.
Could anyone help me to make permanent changes to /system/build.prop file?
Click to expand...
Click to collapse
Thanks for reporting root worked on your moto e, this is fairly new, Im waiting to see if others can repeat it, and whether it really does work. Have you tried some other apps that require root to see if they actually work with root?
For your specific /system/build.prop issue, some roms write that file from another location, /etc/build.prop or some other similar paths, so maybe need to find that file. Also you have to remount /system as read-write, assuming this worked otherwise there would be an error right away.
Usually I edit /system/build.prop files manually with terminal emulator app, then type these commands:
su (proper root needed)
mount -o rw,remount /system/build.prop
vi /system/build.prop ( may need to install busybox app)
Requirements:
[ROOT REQUIRED]
[OEM Unlocking must be allowed under the developer options before flashing this file AND stay activated
as long as you want the device to stay unlocked (OnePlus implemented security features which locks the device on reboot with the switch off)]
* I am not responsible for bricked devices, thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about this method before using it!
* YOU are choosing to make these modifications.
* And if you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
WARNING: THESE FILES ARE BASED ON THE OXYGEN OS 2.1.1 FIRMWARE, PLEASE ANALYZE YOUR DEVINFO IF THE VERSION IS DIFFERENT TO MAKE SURE NOT BRICKING SOMETHING!
I have not upgraded my device to 2.1.2 yet because there have been some issues with the newest firmware.
Tested and confirmed working on:
OxygenOS 2.2.0 - thanks to @pryggi
OxygenOS 2.1.1
Hydrogen OS 1.2.0 - thanks to @fareed_xtreme
I looked at this thread, thanks to Naman Bhalla for this great work.
and found out that the file attached to this post is the answer to my problem, described in another thread.
After the whole day of work analyzing and dumping and saving via adb from my device to the pc and the other way around i finally did it.
On the frist screenshot is my situation before flashing the new devinfo, on the second after flashing the devinfo from the thread mentioned above.
By changing the bits with a Hex Editor of your choice, or by flashing the files below via dd:
Code:
dd bs=4096 of=/dev/block/bootdevice/by-name/devinfo if=/sdcard/oneplus2-devinfo-factory.img
The output should look like the following:
Code:
0+1 records in
0+1 records out
1024 bytes transferred in 0.005 secs (204800 bytes/sec)
You can restore your OnePlus 2 to a factory state while still having root or unlock your phone again without having to wipe it! :highfive:
Credits:
Naman Bhalla
Also to segv11 who already managed this in the OnePlus One and Nexus devices
wow nice job m8
sent from rooted phone
Modified the same location using a HEX Editor (root) whilst on the Hydrogen OS 1.2.0 and I must say it works.
Screenshot Attached. Good Find @thedropdead
Thank you and thanks for testing it out on Hydrogen OS @fareed_xtreme
It is not a Revolution like CM13 on the 1+2, but its helpful for people like me who use their developer devices as daily drivers and still want to lock and unlock the device because of security reasons without wiping the whole device.
fareed_xtreme said:
Modified the same location using a HEX Editor (root) whilst on the Hydrogen OS 1.2.0 and I must say it works.
Screenshot Attached. Good Find @thedropdead
Click to expand...
Click to collapse
thedropdead said:
Thank you and thanks for testing it out on Hydrogen OS @fareed_xtreme
It is not a Revolution like CM13 on the 1+2, but its helpful for people like me who use their developer devices as daily drivers and still want to lock and unlock the device because of security reasons without wiping the whole device.
Click to expand...
Click to collapse
I needed it for resetting the tamper flag. I have certain issues with my phone and might have to return it in the near future and hence this was important. So thanks again.
fareed_xtreme said:
I needed it for resetting the tamper flag. I have certain issues with my phone and might have to return it in the near future and hence this was important. So thanks again.
Click to expand...
Click to collapse
Thats another good thing to do with it
It was a pleasure to help you out mate
Thanks, I was waiting for this for securing my OPT. Has anyone tested, if it works also on OOS 2.2.0?
Just to clarify, the dd command should be executed in TWRP console?
Would be cool if someone could make an app for this like the Nexus devices have:
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
pryggi said:
Thanks, I was waiting for this for securing my OPT. Has anyone tested, if it works also on OOS 2.2.0?
Just to clarify, the dd command should be executed in TWRP console?
Would be cool if someone could make an app for this like the Nexus devices have:
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Click to expand...
Click to collapse
Hello pryggi,
It should also work on OOS 2.2.0, you could check that by dumping the partition (by reversing the dd command) like this:
Code:
dd bs=4096 if=/dev/block/bootdevice/by-name/devinfo of=/sdcard/oneplus2-devinfo-oos220.img
And looking at the file in the hex editor for differences or by posting it here and i can check it for you.
I have executed the dd command from ADB Shell with the Phone connected via wireless ADB.
You can also execute dd in the Android Terminal Emulator App.
Thanks for your reply. My device is already unlocked. As I don't have a computer with ADB/drivers at hand right now, I managed to run the dd command in Terminal Emulator app after elevating with su. Result is attached. Viewing it in hex seems to confirm, that at least the locking bit seems to be in the same position.
pryggi said:
Thanks for your reply. My device is already unlocked. As I don't have a computer with ADB/drivers at hand right now, I managed to run the dd command in Terminal Emulator app after elevating with su. Result is attached. Viewing it in hex seems to confirm, that at least the locking bit seems to be in the same position.
Click to expand...
Click to collapse
Thank you for the Dump, i can confirm that the bit is at the same position and the unlock bit is the same.
I compared the file attached at my first post with yours and they are identical ( see attachment, sorry its german, meaning is they are identical).
So by flashing the factory.img from my first post or unchecking OEM Unlock allowed in the developer Settings your device should be locked again and can be unlocked by flashing the unlock.img via dd in ADB or the Android Terminal Emulator within the Phone.
Thanks for the further explanation. I was just wondering about this OEM Unlocking switch in dev options. What would happen, if one would use dd and the factory image file to lock the bootloader and leave the OEM Unlocking switch still unlocked...
I also am interested if this type of locking-unlocking can be done in TWRP... If it can be done there, then it does not offer any benefits in security, if my logic is correct. Although, I might be drifting off topic here.
pryggi said:
Thanks for the further explanation. I was just wondering about this OEM Unlocking switch in dev options. What would happen, if one would use dd and the factory image file to lock the bootloader and leave the OEM Unlocking switch still unlocked...
I also am interested if this type of locking-unlocking can be done in TWRP... If it can be done there, then it does not offer any benefits in security, if my logic is correct. Although, I might be drifting off topic here.
Click to expand...
Click to collapse
As i can remember i tried that too, by flashing the factory image partition via dd and leaving the switch on, the switch gets toggled off when rebooting, because the switch is just the representation of the unlocking bit in the partition. So when it is turned off, the software will set the bit to zero, means the device will get locked on reboot. Turning the switch on will not override the bit and the device can boot unlocked and the switch will stay on.
It is hard to explain
Your Idea about doing the same thing in TWRP since the ADB is available there is interesting.
I think the problem here is, that once you onlock and flash a custom recovery via fastboot, and relock the device, you already tampered with it, and twrp does provide much more options than the stock recovery image (ADB commands, ...).
So the problem here lies in flashing twrp.
I solved this problem by keeping the stock recovery and locking the device via the image file.
Once i want to use twrp, i unlock the phone by using the unlock.img and use "fastboot boot twrp.img" to boot twrp to backup my device or some other action.
I know that this means if my device gets bricked in this locked state with stock recovery i will have to unlock it normally, but before making any important changes to my software i always unlock my device first in case something goes wrong and with the stock recovery i could not even flash anything so making huge software changes requires me to unlock my device and boot twrp
Hope that this post helps somehow
FYI: The HEX hack must work on almost all OPT OS Releases.Kinda universal
fareed_xtreme said:
FYI: The HEX hack must work on almost all OPT OS Releases.Kinda universal
Click to expand...
Click to collapse
That is right, i just included the notice in the first post so nobody can tell me i have not told them
It is also possible that OnePlus changes the layout of that partition in one of the upcoming updates/releases and that is why it is still mentioned in the first post, thank you anyway.
@thedropdead I've a question: I should use the "modified" devinfo.img AFTER I go back to stock, if I want to unlock my phone without wiping data, right ? So I go back to stock, flash in fastboot or in terminal emulator the .img, and that's good ? I'me unlocked without data wiped ?
casual_kikoo said:
@thedropdead I've a question: I should use the "modified" devinfo.img AFTER I go back to stock, if I want to unlock my phone without wiping data, right ? So I go back to stock, flash in fastboot or in terminal emulator the .img, and that's good ? I'me unlocked without data wiped ?
Click to expand...
Click to collapse
That should be the plan if i have understood everything right.
So you are on the custom ROM, want to go back to the stock ROM?
If that is the case i do not see why you should want to flash any image.
You can use TWRP to wipe and then flash the stock ROM, your phone should still be unlocked right?
Please someone correct me if i am wrong.
It would be great if you could tell me what you are trying to achieve.
The unlock image had the purpose to help someone unlock their device if they have a rooted device but have locked it after flashing everything for security reasons.
thedropdead said:
That should be the plan if i have understood everything right.
So you are on the custom ROM, want to go back to the stock ROM?
If that is the case i do not see why you should want to flash any image.
You can use TWRP to wipe and then flash the stock ROM, your phone should still be unlocked right?
Please someone correct me if i am wrong.
It would be great if you could tell me what you are trying to achieve.
The unlock image had the purpose to help someone unlock their device if they have a rooted device but have locked it after flashing everything for security reasons.
Click to expand...
Click to collapse
Well, for now I'm under CM13, and, yeah, I know I could wipe and flash stock in TWRP, I just want to know in case .
casual_kikoo said:
Well, for now I'm under CM13, and, yeah, I know I could wipe and flash stock in TWRP, I just want to know in case .
Click to expand...
Click to collapse
Okay thanks for the clarification.
In the Case of using some unbrick Tool and thus resetting everything including recovery to stock your phone should lock on the first stock boot.
Once it is locked and you do not have root, which would be the case, you have no possibility to flash the img via fastboot or the emulator.
so in conclusion you are better off with wiping and flashing via twrp so you can still flash something if anything goes wrong
It works on OxygenOS 3.0.2 too. I edit the same location using a HEX Editor. And everything is fine.
Hey guys, sounds like this is exactly what I've been looking for. Thanks for figuring this out.
But, I'm a bit of a noob, so can you break it down into like a hundred very clear steps?
Has anyone found a way to get safestrap working on OF1 Lollipop 5.01? From what I've read you have to use flashfire, but most of the post were made back in 2014 so I wasn't sure if there was something new I just missed.
Thanks! :good:
People are working on it but no.
Hope for the best?
whowatchlist said:
People are working on it but no.
Hope for the best?
Click to expand...
Click to collapse
Damn. rip
That is ridiculous. It is right here dude: http://forum.xda-developers.com/galaxy-s4-verizon/development/stang5litre-ediition-5-0-t3132555
Use flashfire and OF1 Method but do NOT wipe. I wiped all the time and it did not work until I did that.
Let me know of your results.
rawfullz said:
That is ridiculous. It is right here dude: http://forum.xda-developers.com/galaxy-s4-verizon/development/stang5litre-ediition-5-0-t3132555
Use flashfire and OF1 Method but do NOT wipe. I wiped all the time and it did not work until I did that.
Let me know of your results.
Click to expand...
Click to collapse
That's not really safestrap though. If you bootloop it is still back to stock with Odin. You can make a backup with Flashfire but it is useless if you cannot boot into Android.
I was able to get safestrap to work on lollipop, but I was testing on an mdk device (lollipop rom, and mostly stock lollipop kernel, minor ramdisk modifications)
On stock kernel, rootfs and system are mounted read-only so you get errors like those in the screenshot attached. I didn't care enough to try to use /data or to attempt to mount system rw to test again but imagine someone could figure it out, and indeed safestrap does work on lollipop ramdisk if you can get system mounted rw
Sent from my Nexus 6P using XDA-Developers mobile app
Surge1223 said:
I was able to get safestrap to work on lollipop, but I was testing on an mdk device (lollipop rom, and mostly stock lollipop kernel, minor ramdisk modifications)
On stock kernel, rootfs and system are mounted read-only so you get errors like those in the screenshot attached. I didn't care enough to try to use /data or to attempt to mount system rw to test again but imagine someone could figure it out, and indeed safestrap does work on lollipop ramdisk if you can get system mounted rw
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Surge1223, thank you so much for all your hard work on GS4 safestrap and bootloader attempts.
Also, I understand that the GS4 is now an old device and hard to justify spending a lot of time getting Safestrap working... thank you for taking the time to answer the question and to let us know that it does not currently work.
While I would have no idea where to even start, can you provide a bit of a "hint" as to what you believe would be required to get it working on 5.0.1? Basically, can you write a sentence or two that someone smarter than me, could use as a starting point if they decide to attempt to update Safestrap for 5.0.1 on a ME7 + bootloader?
Thanks again