Related
So, I
got myself an i9023 (yay!),
unlocked the bootloader,
updated it to 2.3.4 (GRJ22),
booted (not flashed) recovery-clockwork-3.0.2.4-crespo.img and applied su-2.3.6.1-ef-signed.zip from there and rebooted --> root.
Then I installed Superuser from Market and verifed that it works and
celebrated ...
... - as it turns out, rather prematurely. Apparently this doesn't give adb root because for that "ro.secure" in default.prop needs to be 0, and that file sits in the ro rootfs, which in turn is a part of the boot image ... ...
I guess my question is, how can I get root access for adb?
Is there an easy way to extract the boot image, change that detail and repack it?
EDIT: Solved, see http://forum.xda-developers.com/showthread.php?p=14219782.
fallenguru said:
So, I
got myself an i9023 (yay!),
unlocked the bootloader,
updated it to 2.3.4 (GRJ22),
booted (not flashed) recovery-clockwork-3.0.2.4-crespo.img and applied su-2.3.6.1-ef-signed.zip from there and rebooted --> root.
Then I installed Superuser from Market and verifed that it works and
celebrated ...
... - as it turns out, rather prematurely. Apparently this doesn't give adb root because for that "ro.secure" in default.prop needs to be 0, and that file sits in the ro rootfs, which in turn is a part of the boot image ... ...
I guess my question is, how can I get root access for adb?
Is there an easy way to extract the boot image, change that detail and repack it?
Click to expand...
Click to collapse
flash a custom rom through the recovery. they all pretty much have root.
I'm sure there's a way to get what you want exactly. I don't know it exactly though.
If it was my phone and i wanted to keep it stock. I would flash ~This Rom~. It's a stock deodexed zipaligned rom with a few minor tweaks.
I'm not 100 percent here but i believe if you just wanted the boot.img you could extract it from that rom then flash it using "fastboot flash boot boot.img" If you're running a stock build the boot image from a stock rom should work for you. but like i said i'm not 100% sure. I'm only a moderately well informed nub.
fallenguru said:
So, I
got myself an i9023 (yay!),
unlocked the bootloader,
updated it to 2.3.4 (GRJ22),
booted (not flashed) recovery-clockwork-3.0.2.4-crespo.img and applied su-2.3.6.1-ef-signed.zip from there and rebooted --> root.
Then I installed Superuser from Market and verifed that it works and
celebrated ...
... - as it turns out, rather prematurely. Apparently this doesn't give adb root because for that "ro.secure" in default.prop needs to be 0, and that file sits in the ro rootfs, which in turn is a part of the boot image ... ...
I guess my question is, how can I get root access for adb?
Is there an easy way to extract the boot image, change that detail and repack it?
Click to expand...
Click to collapse
If you type “su” in a terminal emulator, do you get a “$” or “#”? # means that you have root, otherwise you only have su app installed, nothing more. Same thing goes for “adb shell” "su" in your command prompt (in windows). If this is your situation then you could try this procedure:
-Flash or boot into clockwork recovery
-mount system partition (this part does the trick, I don’t see this steep in you post)
-install su-2.3.6.1-ef-signed.zip
-reboot
-enable USB debugging
simms22 said:
flash a custom rom through the recovery. they all pretty have root.
Click to expand...
Click to collapse
I'd rather stay with the stock ROM (+Voodoo module) for now, I'm not bored yet.
NVMENOR said:
If you type “su” in a terminal emulator, do you get a ...
Click to expand...
Click to collapse
#. Root on the phone and within adb shell is working fine, it's just adb itself that doesn't have root access. I'm used to modifying system files using adb pull - modify - adb push and uninstalling system apps via adb ... ...
Solved, see http://forum.xda-developers.com/showthread.php?p=14219782.
Excellent!
Thank you! Thank you! I've been trying for weeks to figure out why my rooted nexus s 4g was getting permission denied when trying to use push/pull (among other adb commands). Now I can backup my app's sqlite database using pull!
For my own education, what might the downside of flashing this boot image be? I know there is an obvious security vulnerability since adb runs as root by default now on the device. I'm willing to tolerate that for the time being. Are there any other possible issues or gotchas to be aware of?
peterwbeck said:
Thank you!
Click to expand...
Click to collapse
You're welcome.
peterwbeck said:
For my own education, what might the downside of flashing this boot image be?
Click to expand...
Click to collapse
As opposed to just booting it? I don't think there are any but I'm far from sure - maybe some incremental OTA updates won't work, for example.
Since the change only affects adb and you need to connect the phone to a computer for that anyway you might as well just boot the image whenever you need full adb access.
I have a Sprint HTC Hero (200), it has already been flashed for boost mobile, I am not sure if that means it has a custom ROM but I believe so
I cant download anything from Market (for some reason wont connect, probably from the flash)
I would like to put it to Cyanogen, but would like to set it back to original factory settings (and rom) before i do so...
I tried putting the phone into recovery, used the adb shell command to do it, just sends me to a black screen with a phone with a red triangle/exclamation point overlapping it...
and i figured out that holding the volume down while pressing the volume opens this (assuming its a custom recovery, but not sure how to use it or if it even supports the functions i need)
at the bottom of the recovery there is 3 pictures of android skating (like the cyanogen mod logo), and also...
this is what the custom recovery menu shows
(in green writing)
HERC XC SHIP S-ON
HBOOT-1.47.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-2.42.02.10.29
Mar 1 2010, 16:02:39
then says
HBOOT
<VOL UP> FastBoot Mode
<BACK> Simlock
<HOME> Recovery
when i push volume up it then changes to say...
FASTBOOT
<VOL DOWN> HBoot Mode
<MENU> Reset Device
<ACTION> Restart to HBoot
im not sure what the recovery is, can anybody help me?
when i HOME in HBoot Mode (Recovery) it just send me to that black screen withe the phone and the red exclamation point
THANKS IN ADVANCE! ANY HELP GREATLY APPRECIATED!
(anybody know how i can check to see if the phone is rooted without having access to the android market? i think if it IS rooted i might be able to just install ClockWorkMod, right?)
It has the original recovery image. Do you have the superuser app in your app drawer?
私のEVO 3Dから送信される。
no i do not have it, and i tried the clockwork install and when i type the su command it says could not grant permission or something along those lines
so i am not sure why i am getting the adb errors, it wont let me root through adb (cant figure out why, everything seems to be functioning correctly, just some commands dont go through, says permission not granted or something similar...
and i tried installing z4root for some reason the phone is saying that it has no program to run the apk... but i just tried downloading a different apk and it installed fine...
any ideas?
i am following this tutorial
http://wiki.cyanogenmod.com/wiki/HTC_Hero_(CDMA):_Full_Update_Guide
and under "rooting the hero (cdma)"
on step 5, i have tried this many times many different ways, i tried doing abd push rageagainstthecage-arm5.bin /data/local/tmp/ (like it says) but it doesnt work, so i do it without the space between .bin and /data, and it works (also tried without the /data..ect.. completely, same result)
then i type adb shell and a $ appears, and then i type chmod 755 (also tried chmod 755 /data...ect... and chmod 755/data...ect...) and it says "Usage: chmod <MODE> <FILE>
so i put in /data/local/tmp/rageagainstthecage-arm5.bin like it says to, but it says not found, and if i try to just do rageagainstthecage-arm5.bin it says permission denied...
why is it saying permission denied? when i use the /data..ect... string (with a space between) its "not found" but if i do the same thing without the string or with the string attached, it works up untill the last part of step 5
any help greatly appreciated, this is really bothing me =/
Untraumatized said:
i am following this tutorial
http://wiki.cyanogenmod.com/wiki/HTC_Hero_(CDMA):_Full_Update_Guide
and under "rooting the hero (cdma)"
on step 5, i have tried this many times many different ways, i tried doing abd push rageagainstthecage-arm5.bin /data/local/tmp/ (like it says) but it doesnt work, so i do it without the space between .bin and /data, and it works (also tried without the /data..ect.. completely, same result)
then i type adb shell and a $ appears, and then i type chmod 755 (also tried chmod 755 /data...ect... and chmod 755/data...ect...) and it says "Usage: chmod <MODE> <FILE>
so i put in /data/local/tmp/rageagainstthecage-arm5.bin like it says to, but it says not found, and if i try to just do rageagainstthecage-arm5.bin it says permission denied...
why is it saying permission denied? when i use the /data..ect... string (with a space between) its "not found" but if i do the same thing without the string or with the string attached, it works up untill the last part of step 5
any help greatly appreciated, this is really bothing me =/
Click to expand...
Click to collapse
Download and install this: http://db.tt/Bltsa73
When it says rebooting you need to turn your phone off and then turn it back on. You should be rooted then
thanks i acctually managed to get z4root on it (did factory reset and it made market work again) so i got z4root and used astro from market to install it and then had root, got clockworkmod from rom manager, and flashed CM7, its nice
but in the process i ended up messing up my motorola defy, and now im kinda worried (the defy is mine, the hero is my friends)
after doing all the adb shell stuff and everything to get the hero working, after i finished i plugged my defy into my computer to charge, and now its stuck in bootloader mode... (and the battery is too low)
so im charging my battery in my friends broken defy he left here for me to fix (broken screen) and when its a good amount charged i can do something, but what should i do? i almost bricked it once, dont wanna do the same thing, i just want my CM7 back lol...
if you dont know its ok, just looking for somebody who may have some help, i need my defy =/
Untraumatized said:
thanks i acctually managed to get z4root on it (did factory reset and it made market work again) so i got z4root and used astro from market to install it and then had root, got clockworkmod from rom manager, and flashed CM7, its nice
but in the process i ended up messing up my motorola defy, and now im kinda worried (the defy is mine, the hero is my friends)
after doing all the adb shell stuff and everything to get the hero working, after i finished i plugged my defy into my computer to charge, and now its stuck in bootloader mode... (and the battery is too low)
so im charging my battery in my friends broken defy he left here for me to fix (broken screen) and when its a good amount charged i can do something, but what should i do? i almost bricked it once, dont wanna do the same thing, i just want my CM7 back lol...
if you dont know its ok, just looking for somebody who may have some help, i need my defy =/
Click to expand...
Click to collapse
try doing an sbf restore just look it up?
I need to know the opposite, how do I flash my hero to metro pcs?
Sent from my SPH-D710 using xda premium
It looks to me like the best phone $80 can buy I spent couple hours trying to figure out how to enable Multi User module.
My understanding is that adding this to /system/build.prop would bring users module back:
fw.max_users=3
fw.show_multiuserui=1
None of the commonly used apps can root this phone.
Without root I cannot remount /system to read-write to edit build.prop
Stock recovery can mount /system
There are options in recovery to run update from sd card or to update via adb sideload but the phone does not show in adb devices while in recovery. There is also fastboot option.
I also tried dirty cow exploit but it fails with "only position independent executables (PIE) are supported"
I am into this for only couple hours, so I know I am missing a lot. Any pointers that could get me closer to enabling Users module would be welcome.
So, after some reading, i figured I should be able to apply update form recovery that will replace build.prop with modified one. For start, to test things out, I just want to copy file from update.zip to /system/build.prop.test
I created update.zip with update-script and the file I want to add to /system.
Here is update.zip: www . filedropper.com /update_10
I signed update.zip using this:
www . learn2crack.com /2014/02/sign-android-apk-zip.html
I get error "Signature verification failed". Is the problem that keys are test keys or that they are outdated? Is some special manufacturer key required to sign updates?
I am not looking for someone to do this, I just need to be pointed in the right direction.
I have multiple users now :
- downloaded TWRP from bluroms.info
- connected the phone, enabled USB debugging and OEM unlocking in developer options
- run "adb reboot bootloader"
- after phone booted in fastboot mode
fastboot oem unlock (followed instructions on screen / all data wiped)
fastboot boot blutwrp.img (downloaded TWRP)
- twrp started...
- mounted /system
adb pull /system/build.prop
- edited build.prop
adb push build.prop /system/build.prop
adb reboot
- phone got stuck on logo after reboot
removed battery and started the phone again and all seems good
@sasha_ Hey I know this isn't about how to root but could you tell me exactly how you managed to root your Blu Advance 5.0 HD? PM me.
mrfunnybone said:
@sasha_ Hey I know this isn't about how to root but could you tell me exactly how you managed to root your Blu Advance 5.0 HD? PM me.
Click to expand...
Click to collapse
If by rooting you mean, installing supersu so that apps can request root access, i did not do that, because i do not need it. There must be some tutorial around about installing supersu once you root access to the /system - and the steps I described can you get there.
sasha_ said:
If by rooting you mean, installing supersu so that apps can request root access, i did not do that, because i do not need it. There must be some tutorial around about installing supersu once you root access to the /system - and the steps I described can you get there.
Click to expand...
Click to collapse
So is getting root access to system like booting recovery TWRP? then pressing the Mount button and checking System? Sorry I'm a newb at this.
I'd love to gain root on this phone I have twrp installed but can't seem to find a root method that works
Just in case you guys are still watching this, I posted my experience with this phone here
https://forum.xda-developers.com/showpost.php?p=75164672&postcount=26
Here's how I got my zte maven 2 (ATT) rooted.
Disclaimer: This method worked for me but may not work for others, I am not responsible if your device is bricked as a result of this. Also, this method does seem to be a bit finicky and inconsistent.
I rooted this phone twice, and it took about 15-20 tries each time for it to finally work. This is not a root you can do in 5 minutes (unless you are extremely lucky) Plan to set aside an hour or two, and a lot of patience, if you want this to work.
Credit to @madvane20 his post here helped me get root for this phone. He also got his phone rooted before I did, be sure to give him thanks.
Credit to @ZTE Girl for finding a way to remove ads from King root and keeping perm root.
With KingRoot you can get perm root, but personally I hate KingRoot, so at the end there is a method to replace KingRoot with SuperSu. Unfortunately SuperSu root resets on reboot, but a quick, 10 second adb command will reroot your phone with SuperSu
Edit: @ZTE Girl found that using lucky patcher to remove ads from King root worked for her and kept permroot.
Step 1: Enable USB debugging on your phone, and download adb and ZTE drivers to your PC.
2: Download KingRoot from KingRoot.net (download the apk for android)
3: Connect your phone to ADB, and run this command in terminal adb shell make sure you get no errors and accept any USB debugging requests.
4: Now type reboot disemmcwp This will reboot your phone without write protection.
5: When your phone reboots, run adb shell again, and install the kingroot APK. Google will give you a warning about this app being unsafe, install it anyways.
6: Now, here's the finicky part, sometimes KingRoot works, sometimes it doesn't, you just have to keep trying. Make sure your phone is still connected to the computer through adb shell, and then click try root in KingRoot. While KingRoot is attempting to get root: in adb shell keep typing su and pressing enter. Just spam this, It will keep giving errors, but eventually it (should) work. Make sure to accept any prompts on your device while you do this.
7: When you are able to successfully get into su, wait a bit, just to make sure your device doesn't restart
8: Now type getprop ro.product.name, the response should be Z831
9: Now type setprop persist.sys.k Z831, then type getprop persist.sys.k It should say Z831
10: Now type cd /dev/block/platform/soc.0/7824900.sdhci/by-name/
11: Then type dd if=recovery of=/sdcard/recovery.img This will backup your recovery, I highly recommend that you copy the backup to your computer in case something goes wrong.
12: Now type dd if=boot of=recovery, this will write boot to recovery. This part can be risky, it worked for me, but if it bricks your device, you can't say I didn't warn you with that said, don't let that scare you away from finally rooting this device and getting all the advantages that come with it
13: Now type this reboot recovery Your device my blackscreen and not boot after this, personally mine did, and I fixed it by removing the battery, and after puttting it back in, it booted normally.
14: When your phone boots up, type adb shell again, and then type su
15: Type id response should be "uid=0(root) gid=0(root) context=u:r:shell:s0" Note: I don't think my uid showed when I did this, if yours doesn't show, don't worry, it should work fine.
16: Now type setenforce 0
17: After that, type getenforce, it should respond back with "permissive"
18: To test if system is writable, type mount -o remount,rw /system, if you get no errors, everything is working , if you get an error, type reboot disemmcwp, and then try to mount system RW again.
19: I would recommend removing the update service now, so an update doesn't come and screw up your root.
20: Read this: Now you should have permroot with kingroot, however, as you will soon find, kingroot has a ton of ads, and can get very annoying. So, if you want SuperSu and no kingroot, keep reading. If you want to keep KingRoot, then you are done, have fun with your rooted Maven 2
Edit: @ZTE Girl found that you can use lucky patcher to remove ads from Kingroot while still keeping permroot.
21: Download the KingToSuperSu zip in attachments, I have modified it slightly from the original zip so it works better. You will see a folder inside the zip named "mrw" copy this folder to the root of your /sdcard (must be copied to the root of /sdcard)
22: Now go into adb shell again, and then type su
23: Type mount -o remount,rw /system
24: If you get no errors, simply type sh /sdcard/mrw/root.sh, you will see a lot of errors in the script, no need to worry, now you should have SuperSu. Note: sometimes you get a notification saying "com.eu.chainfireSuperSu has stopped" or something like that, run the command again, and it should work.
25: SuperSu will say binary needs to be updated, but the update always fails, however you can click no thanks, and it will work fine.
26: SuperSu root will go away after you reboot, however, to get root back, simply type adb shell (while connected to your computer of course) then su and then sh /sdcard/mrw/root.sh and just like that, you're rooted again. Note: I couldn't get this to work in a terminal emulator, and it would only work in adb shell for me.
Edit: If you want stock recovery back, run this command in adb shell with su dd of=recovery if=/sdcard/recovery.img. I haven't tested this, and it might unroot/brick your device. This is at your own risk.
This guide was long and complicated, sorry for that, if you need any help, just ask me and I will try to help the best I can.
If this guide helped, please clicks thanks, it means a lot to me
Proof: http://imgur.com/a/zecyU
btw easy way to get rid of ads diasbale the charging thing in king settings and adaway its what i did on the warp 7
carrier iq
this phone has carrier iq, i was able to get temp root without write using kingroot, so i was able to delete, disable apps, and also, remove carrier iq with the quide you can find on the: androidexplained website. i could not actually delete the files in the last two steps but it seemed to work anyway. this is my first post so i can't put links.
Question1: i don't like typing cause i make stupid mistakes, but im assuming i could put all your command in individual batch files ending with a pause on each, and prefixing all you commands with "adb.exe shell su". that way i could stop and see what happened and then continue.
Question2:
dd if=recovery of=/sdcard/recovery.img
seems to mean copy the boot partion to an image file on the internal sd card. am i correct?
and
dd if=boot of=recovery
seems to mean overwrite the boot partition with an image- (file)?
if so what image file?
sorry, im new to all this, i guess i probably don't have enough confidence to do this, my z831 works very well without all the bloat anyway. and yes i understand the risks if i do decide to proceed, anyway. i have 3 $10 and $20 phones that are not bricked but i forgot to reenable the system apps before i removed root and reset, so they might as well be bricked cause they cant do anything after they boot.
btw, you mentioned in one step to wait, to see if it reboots, to see if it is stable before continuing:
for me i remember that either having too many apps running or stopping too many system apps, seemed to make this z831 unstable and reboot, while it had temp root.
Question last: do i need to start the process as you said while kingroot is in the process of rooting, or can i wait till it is finished getting it's root?
duane2064 said:
this phone has carrier iq, i was able to get temp root without write using kingroot, so i was able to delete, disable apps, and also, remove carrier iq with the quide you can find on the: androidexplained website. i could not actually delete the files in the last two steps but it seemed to work anyway. this is my first post so i can't put links.
Question1: i don't like typing cause i make stupid mistakes, but im assuming i could put all your command in individual batch files ending with a pause on each, and prefixing all you commands with "adb.exe shell su". that way i could stop and see what happened and then continue.
Question2:
dd if=recovery of=/sdcard/recovery.img
seems to mean copy the boot partion to an image file on the internal sd card. am i correct?
and
dd if=boot of=recovery
seems to mean overwrite the boot partition with an image- (file)?
if so what image file?
sorry, im new to all this, i guess i probably don't have enough confidence to do this, my z831 works very well without all the bloat anyway. and yes i understand the risks if i do decide to proceed, anyway. i have 3 $10 and $20 phones that are not bricked but i forgot to reenable the system apps before i removed root and reset, so they might as well be bricked cause they cant do anything after they boot.
btw, you mentioned in one step to wait, to see if it reboots, to see if it is stable before continuing:
for me i remember that either having too many apps running or stopping too many system apps, seemed to make this z831 unstable and reboot, while it had temp root.
Question last: do i need to start the process as you said while kingroot is in the process of rooting, or can i wait till it is finished getting it's root?
Click to expand...
Click to collapse
i have a batch script i made for the warp 7 that i think will work for this phone but i never posted any of it cause he released the guide first so i told him to keep it and no the boot to recovery overwrites recovery with boot image from boot then after everything has perm root u can flash the recovery back to recovery. do we need a batch script no do we need to mess with other files risking a brick no kingroot is fine til we can find a way to get access to bootloader for fastboot as well as get a twrp built for the phone. theres ways to make kingroot not as annoying ad blocker disable notifications from kingroot and disable fastcharging lock screen. but u more than welcome to tamper just be aware u brick ur phone in the process theres no fix. as well if it makes it easier for people i will write a batch script that walks them through the process with the pauses shows them what it does so they can learn for future purpose but i m0ean the guides pretty simple
---------- Post added at 01:55 PM ---------- Previous post was at 01:51 PM ----------
wait is this thread maven or maven 2?
step 9 is different than yours, why?
Question for madvane20
XCnathan32's step 9: "Now type
setprop persist.sys.k Z831
BUT in your bat file:
adb.exe shell su
setprop ro.product.name Z831
of course swaping out ZTE_BEAM for Z831
is one better than the other or should they both be done?
yea i think i need to maybe fix the bat but im working on stuff atm got rl stuff im busy with but once im done i will finish a bat for the warp 7 and one for this phone. but yes u swap the name of the phone out for what phone u have.
---------- Post added at 03:26 PM ---------- Previous post was at 03:25 PM ----------
the warp 7 has different name etc so yea the warp 7 post is different im trying to work on everything as well keep working on my huawei ascend xt as well real life stuff
Question for madvane20, im sorry, i meant persist.sys.k OR setprop ro.product.name, this is the discrepancy in the two instructions.
did u read the guide for the zte maven 2 and also look at the guide for the warp 7 u will see the difference it just takes u to read them then u shouldnt have any questions
is this syntax correct, before i try it?
batch.txt:
https://dl.xda-developers.com/4/2/2/0/4/0/3/batchfiles.txt?key=NgPk58hMrJO5QXnvDcnCPw&ts=1500762566
if anyone wants to ask me questions just pm me or get ahole of me on hangouts im listed as dav ril or madvane20
I have used Wugfresh's NRT with my previous Nexus devices with stellar results and I downloaded ADB to try your guys method with a Z831 however, I need ti know if this guide is Android version specific? I recently went from 5.1.1 to 7.1.1 in like 3 OTA AT&T updates, so this device is running Nougat. Also, is PIE something new to 7.0 ? I read somewhere this affects the root process. Why do they have "Unlock bootloader" option in Dev settings ? Can I just run an ADB command to enable Write permission to delete 40-50 #/System/App .apk's?
Yo OP, I genuinely appreciate you sharing this. I found that everything has worked perfectly. I managed to get perm root and I just tried to install SU, gonna see if it worked. Thanks bro
Sent from my N9519 using Tapatalk
So, is it working? please let me know because i also want to root it.
---------- Post added at 04:36 AM ---------- Previous post was at 04:27 AM ----------
How to install adb and Zte drivers on your computer? please reply
379068 said:
So, is it working? please let me know because i also want to root it.
---------- Post added at 04:36 AM ---------- Previous post was at 04:27 AM ----------
How to install adb and Zte drivers on your computer? please reply
Click to expand...
Click to collapse
The ZTE drivers should be on your phone. One of the mount options, when you plug in your phone is to install drivers.
This method really works. You can copy your recovery back after, you do not loose root. You are also able to re-root and make it permanent again after a factory reset, it is just takes many more exploit attempts. You can also install Xposed through Xposed Installer.
Anybody bought and tried Super-Sume Pro with this phone yet?
can thsi be done on other mavens?
Can you do this on a Maven 3 running nougat?
Is the root method working with ZTE Maven 3?
Anyone tried this on ZTE Maven 3? Got 2 from Bestbuy, would like to have them rooted.
Thanks.
Logos Ascetic said:
Can you do this on a Maven 3 running nougat?
Click to expand...
Click to collapse
I recently dissected the partition index and firmware structure of the ZTE Maven 3, in hopes of discovering a viable root exploit. Because it ships with stock Android Nougat, systemless root via patched boot image would be preferable. But, because the bootloader does not appear to be unlockable by any known method or exploit, systemless root is not currently an option. Accordingly, I focused on the less desirable method of system-mode rooting, which injects the SU daemon and corresponding root binaries to the Android OS by way of the /system partition directly. Again, an obstacle ensued: the stock kernel of the ZTE Maven 3 is secured by AVB 2.0/dm-verity (device mapping), which checks the /system partition for any modifications whatsoever prior to allowing the OS to boot. So, if /system is modified in any way, or so much as mounted r/w, a perpetual boot loop will commence via dm-verity.
So, in short, due to the locked bootloader state and verified boot/device mapping, safely & effectively rooting the stock Android Nougat OS of the ZTE Maven 3 doesn't presently appear to be feasible.
Note: I realize that the OP designated this as a ZTE Maven 2 thread, and I apologize to the OP if I'm off topic. I only addressed the Maven 3 because of the number of questions in the thread.
I have the z831 through at&t. I'm pretty sure I unlocked the bootloader in developer options as nothing would root the phone until I turned it on. Everything worked, but is there a custom recovery or rom?
kingroot.net even if you choose english gives you a chinese app
Guys I need some help !!
I have official firmware in my phone S7 edge ( Android 7.0 G935F ) but once i tried to root it and it was stuck in boot logo so i went to a store for a suppose unroot ,but know e cant use Samsung health app because gives me an error. I already searched this error and just have to change the tima value to 0 in build.prop
My real question is can I edit build.prop to fix this error without root or do i have to root my device again to fix this error ??
Please help
thanksssss, waiting 4 answers
Your phone KNOX is ticked 0X1 that's why not working, you must root your phone and edit built prob, edit line TIMA=0 and will work
so i have to root it again ?? i have some problems (fear) doing it again because i don't know how to do it right
Or othe way to make it work. But need to be Root. Delete v5 restar install v4. Loging abd update. Done
I would recommend you the recovery mode if you don't want root the phone again. You have full access to system files in recovery mode, but only if it is mounted.*
Many stock recoveries don't have option to mount system partition or don't have adb access for commands. You might want a custom recovery for this. And no, you don't need root for custom recovery. So now all you need to do is, boot into recovery (custom preferred), mount system and then using adb, pull the build.prop file:
adb pull /system/build.prop <path to save file>
Now edit the file you just extracted and save it*
Push it back to your phone via adb
adb push <path to your file> /system/build.prop
You're not done yet. You need to set permissions too. So open she'll via terminal
adb shell
Now from shell, set the right permissions
chmod 644 /system/build.prop
And you're done
Reboot your phone and see the changes