To begin. My device, as mentioned in the title, is the Samsung Galaxy J3 sm-J320W8 running Android 7.1.1.
I tried to root it with the CF-Auto-Root. I matched all the info as needed, that being Model number and android version, and continued with the root as you normally would with Oden. After Oden says it passes. My device reboots, but instead of going into recovery and installing SuperSU it gives me the "Recovery is not seandroid enforcing" error at the top left of the screen. It then reboots once again and the phone starts as normal so thankfully I didn't break anything. But SuperSU was not installed and my device remains unrooted. I did notice that the SuperSU zip was transferred to my SD card though.
Does anyone know what the problem is? Hopefully with a solution as well.
MissCherry1241 said:
To begin. My device, as mentioned in the title, is the Samsung Galaxy J3 sm-J320W8 running Android 7.1.1.
I tried to root it with the CF-Auto-Root. I matched all the info as needed, that being Model number and android version, and continued with the root as you normally would with Oden. After Oden says it passes. My device reboots, but instead of going into recovery and installing SuperSU it gives me the "Recovery is not seandroid enforcing" error at the top left of the screen. It then reboots once again and the phone starts as normal so thankfully I didn't break anything. But SuperSU was not installed and my device remains unrooted. I did notice that the SuperSU zip was transferred to my SD card though.
Does anyone know what the problem is? Hopefully with a solution as well.
Click to expand...
Click to collapse
Just use twrp to install SuperSU.
ashyx said:
Just use twrp to install SuperSU.
Click to expand...
Click to collapse
I have yet to find twrp available for my device and I don't know how to compile one myself. CF-Auto-Root is the only root I have found so far for the j320w8
MissCherry1241 said:
I have yet to find twrp available for my device and I don't know how to compile one myself. CF-Auto-Root is the only root I have found so far for the j320w8
Click to expand...
Click to collapse
Looking back over some posts it seems it was unclear whether this device has a locked bootloader or not.
I never actually got a real confirmation.
Check out the thread below, you will find a root method as yet unconfirmed!
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-j3-root-t3544157/page15
ashyx said:
Looking back over some posts it seems it was unclear whether this device has a locked bootloader or not.
I never actually got a real confirmation.
Check out the thread below, you will find a root method as yet unconfirmed!
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-j3-root-t3544157/page15
Click to expand...
Click to collapse
From what I can tell in that thread since I have seen it prior to posting this one they have yet to have any confirmed rooting methods. And the j320w8 rooted boot file from what I remember is the one that soft bricked my device last time. I can try again though. I have a backup and recovery image so it's not a big deal if I get soft bricked again.
I could also check if there is a way to unlock the bootloader on my device... If that's even a thing. I'm still trying to learn what some of this stuff means.
MissCherry1241 said:
From what I can tell in that thread since I have seen it prior to posting this one they have yet to have any confirmed rooting methods. And the j320w8 rooted boot file from what I remember is the one that soft bricked my device last time. I can try again though. I have a backup and recovery image so it's not a big deal if I get soft bricked again.
I could also check if there is a way to unlock the bootloader on my device... If that's even a thing. I'm still trying to learn what some of this stuff means.
Click to expand...
Click to collapse
If the bootloader is locked there's no way to unlock it.
What was the soft brick, gave you got details?
ashyx said:
If the bootloader is locked there's no way to unlock it.
What was the soft brick, gave you got details?
Click to expand...
Click to collapse
After installing one of the files through oden it just got stuck and wouldn't turn on. Couldn't access the Android Recovery and trying to turn on the device basically just made it get stuck on the samsung loading screen. I did still have access to the Download so I was able to reflash the original 7.1.1 firmware back into it
MissCherry1241 said:
After installing one of the files through oden it just got stuck and wouldn't turn on. Couldn't access the Android Recovery and trying to turn on the device basically just made it get stuck on the samsung loading screen. I did still have access to the Download so I was able to reflash the original 7.1.1 firmware back into it
Click to expand...
Click to collapse
It wouldn't have worked as it's a Marshmallow firmware and you are running Nougat. The 2 are not compatible.
ashyx said:
It wouldn't have worked as it's a Marshmallow firmware and you are running Nougat. The 2 are not compatible.
Click to expand...
Click to collapse
Ah. Would it be possible for me to downgrade firmwares in order to get the root? I'll take older rooted firmware over newer unrooted any day
MissCherry1241 said:
Ah. Would it be possible for me to downgrade firmwares in order to get the root? I'll take older rooted firmware over newer unrooted any day
Click to expand...
Click to collapse
What is your current firmware build?
ashyx said:
What is your current firmware build?
Click to expand...
Click to collapse
Right now I am on Android version 7.1.1
MissCherry1241 said:
Right now I am on Android version 7.1.1
Click to expand...
Click to collapse
No, please post the firmware build version in settings/about.
ashyx said:
No, please post the firmware build version in settings/about.
Click to expand...
Click to collapse
Sorry. I'm not familiar with what that is. Here's a screenshot of my software information.
https://imgur.com/EL0E84O
https://imgur.com/46m4P8L
MissCherry1241 said:
Sorry. I'm not familiar with what that is. Here's a screenshot of my software information.
https://imgur.com/EL0E84O
https://imgur.com/46m4P8L
Click to expand...
Click to collapse
OK you should be able to downgrade to J320w8VLU2AQA1 then flash the rooted boot with odin.
ashyx said:
OK you should be able to downgrade to J320w8VLU2AQA1 then flash the rooted boot with odin.
Click to expand...
Click to collapse
Goodie! I'll try that out now and come back to confirm whether or not it works
MissCherry1241 said:
Goodie! I'll try that out now and come back to confirm whether or not it works
Click to expand...
Click to collapse
OK. Ensure you make a note of what odin and the device screen reports.
ashyx said:
OK. Ensure you make a note of what odin and the device screen reports.
Click to expand...
Click to collapse
I seem to have run into an Issue. I reinstalled Android 6.0.1 successfully and set up my device. Made sure that it was J320w8VLU2AQA1 and confirmed it through the about section.
Then I flashed the rooted boot that you linked. Oden showed success and my device rebooted as normal. But... My phone started as if nothing happened. No SuperSU installed and when I go into recovery mode it just has the basic Android Recovery. No TWRP.
MissCherry1241 said:
I seem to have run into an Issue. I reinstalled Android 6.0.1 successfully and set up my device. Made sure that it was J320w8VLU2AQA1 and confirmed it through the about section.
Then I flashed the rooted boot that you linked. Oden showed success and my device rebooted as normal. But... My phone started as if nothing happened. No SuperSU installed and when I go into recovery mode it just has the basic Android Recovery. No TWRP.
Click to expand...
Click to collapse
It's not TWRP its a rooted boot image.
Install the Superuser app from the Play store and hopefully you should have root priveledges.
After installing, open the Superuser app and report back its status.
ashyx said:
It's not TWRP its a rooted boot image.
Install the Superuser app from the Play store and hopefully you should have root priveledges.
After installing, open the Superuser app and report back its status.
Click to expand...
Click to collapse
Alright. I installed SuperSU. It did an update and rebooted my device. Checked with Root checker app and I am in fact rooted!
I didn't realize that's what I had to do. So all of this is working and I have rooted my J320W8
MissCherry1241 said:
Alright. I installed SuperSU. It did an update and rebooted my device. Checked with Root checker app and I am in fact rooted!
I didn't realize that's what I had to do. So all of this is working and I have rooted my J320W8
Click to expand...
Click to collapse
Finally a proper confirmation.
Glad its worked for you. :good: You MAY be able to update to Nougat by flashing the stock firmware with FLASHFIRE.
Just ensure EverRoot is enabled.
Related
Hi folks! I have a Galaxy S4 GPE, rooted and unlocked, but stock otherwise. When I try to run the OTA update for 4.4.3, the phone reboots into TeamWin recovery and appears to start installing. The install errors out though. Can I not install the OTA update because I'm rooted? If so, would reverting the rooting allow me to install? Thanks in advance for any help you can provide!
Install Stock recovery and then try again
Aamirx12 said:
Install Stock recovery and then try again
Click to expand...
Click to collapse
Is there a thread on how to do that? I seem to remember when I installed this recovery tool to root the phone, it wiped everything. Is it going to do that again? Because I don't want to have to keep wiping my phone every time a new Android update comes out just to be rooted.
1337squirrel said:
Is there a thread on how to do that? I seem to remember when I installed this recovery tool to root the phone, it wiped everything. Is it going to do that again? Because I don't want to have to keep wiping my phone every time a new Android update comes out just to be rooted.
Click to expand...
Click to collapse
Flash it via Odin or simply restore recovery from Nandroid backup..
http://forum.xda-developers.com/showthread.php?t=2265477
this may help you..
1337squirrel said:
Hi folks! I have a Galaxy S4 GPE, rooted and unlocked, but stock otherwise. When I try to run the OTA update for 4.4.3, the phone reboots into TeamWin recovery and appears to start installing. The install errors out though. Can I not install the OTA update because I'm rooted? If so, would reverting the rooting allow me to install? Thanks in advance for any help you can provide!
Click to expand...
Click to collapse
Follow this GUIDE (Method 1: Update Via Custom Recovery).
Joku1981 said:
Follow this GUIDE (Method 1: Update Via Custom Recovery).
Click to expand...
Click to collapse
I went through that method, and it's essentially the same thing, except that I'm downloading the actual update file myself and not letting Android handle it. Needless to say it didn't work. I also updated my TWRP to 2.7.1.0 and tried; no luck. I also uninstalled SuperSU to see if removing root would help. It didn't.
1337squirrel said:
I went through that method, and it's essentially the same thing, except that I'm downloading the actual update file myself and not letting Android handle it. Needless to say it didn't work. I also updated my TWRP to 2.7.1.0 and tried; no luck. I also uninstalled SuperSU to see if removing root would help. It didn't.
Click to expand...
Click to collapse
It's the problem of no read for be vague. It worked perfectly on the GPE of my sister. The update that appears in the website is ready for install it through custom recovery. Read all the guide:
Hello everyone. Finally i found it. I want to help everyone who search along time this recovery.
This is twrp recovery for One M8 Eye. First please unlock bootloader via HTC DEV. Than ( fastboot flash recovery twrp-m8eye-2.8.0.3.img ) After that flash UPDATE-SuperSU-v2.46.zip ( http://download.chainfire.eu/supersu). Now you have root :good::good:
Thanks Iman Mark and Chainfire
Link: https://drive.google.com/file/d/0B71KxMi9guCSN0V5bU1DSUNaX2c/view?usp=sharing
Please don't forget thanks
This update supersu no longer works. I installed that twrp and did the process for that version of supersu and it said successful. Upon checking supersu, it says the binary files are missing. Then I installed the newer supersu verison through twrp, without deleting the old supersu and now the phone is stuck on htc boot screen. This may work for some, but DO NOT install another supersu over an old one without deleting it first. You WILL get stuck on boot.
Weisheit7 said:
Then I installed the newer supersu verison through twrp
Click to expand...
Click to collapse
"Newer" meaning what? Always be specific, otherwise we can only guess. For all we know, you flashed 2.47, which is "newer" than 2.46.
You should be using the latest stable version, which is currently 2.78, which you can obtain the zip from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Try flashing this, and hopefully that works. I'm not certain, but as far as I know, you don't need to delete an old SuperSU app, in order for the proper updated one to work.
Also, a word of basic good practice when modding any Android device: Always make sure you are using the current updated methods according to your OS version.
The files in the OP are from July 15, 2015. That is well before Marshmallow existing. Root methods almost always need to be updated with each major OS version update. There is really no reason to have thought SuperSU from over a year ago would work on a current OS version device.
redpoint73 said:
"Newer" meaning what? Always be specific, otherwise we can only guess. For all we know, you flashed 2.47, which is "newer" than 2.46.
You should be using the latest stable version, which is currently 2.78, which you can obtain the zip from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Try flashing this, and hopefully that works. I'm not certain, but as far as I know, you don't need to delete an old SuperSU app, in order for the proper updated one to work.
Also, a word of basic good practice when modding any Android device: Always make sure you are using the current updated methods according to your OS version.
The files in the OP are from July 15, 2015. That is well before Marshmallow existing. Root methods almost always need to be updated with each major OS version update. There is really no reason to have thought SuperSU from over a year ago would work on a current OS version device.
Click to expand...
Click to collapse
You're right, and as of right now I have a different issue. I found a link for the Chinese ROM of the htc m8 eye and I successfully installed it. Now the device is on 4.4.4 rooted. I've tried to do the OTA update but each time in stock recovery it fails after about 20-25% and says "system/bin/reboot has unexpected contents" and fails every time. I have uninstalled supersu from the app itself, deleted all of the residual files and checked the phone for root. Root checker says it's not rooted.
How can I fix the OTA problem through stock recovery? I checked the /system/bin/reboot file and there's nothing there specifically that I can see is corrupted or changed. Is there any possibility that supersu has system permissions and is causing this error? If so, how do I fix the /reboot has unexpected contents problem? How can I delete supersu (su) from having system permissions over everything?
I cannot find a stock Chinese ROM for this device, only the rooted one. I'm at a loss here..
Weisheit7 said:
I've tried to do the OTA update but each time in stock recovery it fails after about 20-25% and says "system/bin/reboot has unexpected contents" and fails every time. I have uninstalled supersu from the app itself, deleted all of the residual files and checked the phone for root. Root checker says it's not rooted.
Click to expand...
Click to collapse
Unrooting in order to OTA doesn't work, you need the stock never rooted ROM.
redpoint73 said:
Unrooting in order to OTA doesn't work, you need the stock never rooted ROM.
Click to expand...
Click to collapse
I've read online that if you unroot it the OTA update should go through. It depends on how the root was done, correct? If root has (owner) permissions over system files, how can I put it back to stock? Are you aware of any HTC One M8 eye mels_tuhl stock rom China region? I've scoured the internet forever and cannot find one. If you need my getvar info I'll post it here and I appreciate any help you can potentially give me.
Weisheit7 said:
I've read online that if you unroot it the OTA update should go through.
Click to expand...
Click to collapse
I can't speak to what you read, if you are vague and don't reference any specific website.
What you read is not correct. Its been verified in the M8 forums many times (at least on the "regular" M8). The fact you unrooted, and the OTA doesn't work, also proved it.
Weisheit7 said:
It depends on how the root was done, correct?
Click to expand...
Click to collapse
Incorrect. I haven't seen any root method on the M8, which allows OTA updates after unrooting.
Weisheit7 said:
Are you aware of any HTC One M8 eye mels_tuhl stock rom China region?
Click to expand...
Click to collapse
Unfortunately, no.
redpoint73 said:
I can't speak to what you read, if you are vague and don't reference any specific website.
What you read is not correct. Its been verified in the M8 forums many times (at least on the "regular" M8). The fact you unrooted, and the OTA doesn't work, also proved it.
Incorrect. I haven't seen any root method on the M8, which allows OTA updates after unrooting.
Unfortunately, no.
Click to expand...
Click to collapse
Thanks for taking the time to reply. Since then I have corrected the problem. I downloaded a TWRP backup of Marshmallow from another user on here in a different thread, placed it into my TWRP backup folder, wiped system, internal storage, cache etc and then flashed the backup. Everything went well...marshmallow is on the phone and root is gone.
necaticetinkaya said:
Hello everyone. Finally i found it. I want to help everyone who search along time this recovery.
This is twrp recovery for One M8 Eye. First please unlock bootloader via HTC DEV. Than ( fastboot flash recovery twrp-m8eye-2.8.0.3.img ) After that flash UPDATE-SuperSU-v2.46.zip ( http://download.chainfire.eu/supersu). Now you have root :good::good:
Thanks Iman Mark and Chainfire
Link: https://drive.google.com/file/d/0B71KxMi9guCSN0V5bU1DSUNaX2c/view?usp=sharing
Please don't forget thanks
Click to expand...
Click to collapse
Can you provide another share of the file? The previous link has expired
Tried twrp, but always says I don't have busybox and says loading, but never does, then on install recov, it DL's, but then comes up with an error: Flashing recovery was unsuccessful.
Gives partition as: /dev/block/bootdevice/by-name/recovery
No such partition on LG Leon LTE (h345, flashed from MPCS to T-Mob h345d, only way to get a working root)
Anyone else having this issue?
SOLVED: had to set "OEM Unlock" to enabled in Developer Options..., DUH!!!
This is off-topic, but as you wrote you've flashed a kdz from other variant: is it safe to try flashing different kdz'd just to try? I have a lot of possibilities, but i have only flashed the one from my country and exact same model and v10a. But it's impossible to root. Thanks!
leandeganis said:
This is off-topic, but as you wrote you've flashed a kdz from other variant: is it safe to try flashing different kdz'd just to try? I have a lot of possibilities, but i have only flashed the one from my country and exact same model and v10a. But it's impossible to root. Thanks!
Click to expand...
Click to collapse
I had to downgrade to an h345d kdz variant in order to get a working root. That worked, but it was a MPCS phone (on Tmo network) flashed to a Tmo kdz. Worked. I'd think if you Sbrick it, you could still re-flash with stock from recov., so not that big a deal.
It's not the only way to get root, I rooted my 10e:
http://forum.xda-developers.com/android/help/android-forums-account-rehost-file-t3211801
zowpow said:
It's not the only way to get root, I rooted my 10e:
http://forum.xda-developers.com/android/help/android-forums-account-rehost-file-t3211801
Click to expand...
Click to collapse
Ive tried that also and didnt work. No root method worked on my rom for h340ar
zowpow said:
It's not the only way to get root, I rooted my 10e:
http://forum.xda-developers.com/android/help/android-forums-account-rehost-file-t3211801
Click to expand...
Click to collapse
I can confirm it works with tmobile lg leon h34510f.
To Tomj2
Can you explain how you got twrp on it? Thanks in advance:good:
Edit: figured it out downloaded the img then used flashify to flash the image. Thanks anyways
http://androidforums.com/threads/twrp-2-8-7-0-ms345-twrp-for-lg-leon-metropcs.922379/
I can confirm this works, I have it on my T-Mobile variant.
bzzybfrm313 said:
I can confirm it works with tmobile lg leon h34510f.
To Tomj2
Can you explain how you got twrp on it? Thanks in advance:good:
Edit: figured it out downloaded the img then used flashify to flash the image. Thanks anyways
Click to expand...
Click to collapse
Yeah, that's how I got it on (the latest "blue" TWRP) to be able to load CM12.1
Working twrp recovery 2.8.7.0 on ms34510f rooted using king root installed twrp with twrp manager and then in terminal emulater command reboot oem-unlock oh and check oem-unlock in developer options but cant seem to install cm12
jmarpel said:
Working twrp recovery 2.8.7.0 on ms34510f rooted using king root installed twrp with twrp manager and then in terminal emulater command reboot oem-unlock oh and check oem-unlock in developer options but cant seem to install cm12
Click to expand...
Click to collapse
Are you using the correct twrp? We've got a basic yellow guy which won't flash cm12 and then we've got a blue guy which does.
Why did you use kingroot though? There are better methods for attaining root on your phone.
ninjasinabag said:
Are you using the correct twrp? We've got a basic yellow guy which won't flash cm12 and then we've got a blue guy which does.
Why did you use kingroot though? There are better methods for attaining root on your phone.
Click to expand...
Click to collapse
I didn't have a working pc and King root worked I tried many others and still it's the only one that works. I think I have the yellow one how do I get the blue?
Rooting LG Leon H34510e
I'm a newbie when it comes to rooting however I successfully rooted my H34510e using KingRoot. I verified root and BusyBox installation using Root Checker Basic. I installed TWRP but found that my device was not supported so, I uninstalled TWRO and installed CWM Rom Manager and that's where I'm at today. I'm looking for a custom rom but am not sure CWM is the right manager for my phone.
leandeganis said:
Ive tried that also and didnt work. No root method worked on my rom for h340ar
Click to expand...
Click to collapse
Take your phone, open your internet browser and go to http://www.kingroot.net/
Download the app, open it, follow the steps and you're root!
I have the same phone H340AR v10a ROM, from Uruguay.
Try that, it worked for me.
About TWRP I tried c50 version of TWRP Team, but it doesn't work.. You install the image and when reboot it shows the android robot opened up and nothing comes up.. I installed the TWRP using the "dd if=/dev/ bla bla bla" command..
Some help it wouldn't be bad.
Thanks!
Can't find OEM unlock
I already activated developer options, but..... CANT FIND IT!
EDIT: First of all, thanks for the responses. Second of all, I messed up. I ran a script that I found online called root.sh (I can't link anything until I get to 10 posts). I used that and it didn't work and unrooted me. I tried rebooting my phone(worst idea every) and now it's in a bootloop. I don't think I have root access and I've tried a factory reset. I didn't get any custom recovery and my phone is stuck in a bootloop. I have no idea how to get out of this. Any help is 100% appreciated.
I'm sorry if this is the wrong section but, I couldn't find a section for the M919V. So I recently rooted my Galaxy S4 SGH-M919V running lollipop 5.0.1 using the PC version of Kingoroot. I've been looking for a way to replace Kingo Superuser with SuperSu. I can only seem to find anything about replacing Kinguser/Kingroot (not Kingo Superuser). I would keep Kingo Superuser but, after a reboot it doesn't allow any apps to use root access even though it says it is. I have to keep uninstalling and reinstalling Kingo Superuser and waiting then it finally fixes by it's self (currently it's broken) . SuperSu-Me says I don't have Kingroot (once again, not Kingoroot). I've also tried a script but, once again, it didn't work. I know next to nothing about the inner workings of android phones so please keep any answers simple please.
Flash custom recovery.
Flash SuperSU.
Can't get any simpler.
The sgh-m919v is basically the same phone as the T-mobile S4. The sgh-m919v was issued by Canadian varriers that run an AWS network: https://www.sammobile.com/firmwares/database/SGH-M919V/
The t-mobile s4 forum is here: http://forum.xda-developers.com/galaxy-s4-tmobile
Here's what I would do: flash a stock ROM via Odin to bring the phone back to a stock state and then root using cfautoroot if you want stock recovery or flash TWRP and flash supersu from TWRP.
First of all, thanks for the responses. Second of all, I messed up. I ran a script that I found online called root.sh (I can't link anything until I get to 10 posts). I used that and it didn't work and unrooted me. I tried rebooting my phone(worst idea every) and now it's in a bootloop. I don't think I have root access and I've tried a factory reset. I didn't get any custom recovery and my phone is stuck in a bootloop. I have no idea how to get out of this. Any help is 100% appreciated.
Flash the stock ROM.
Pwnycorn said:
Flash the stock ROM.
Click to expand...
Click to collapse
Could you link me to a good tutorial to do this?
Pwnycorn said:
Flash the stock ROM.
Click to expand...
Click to collapse
Hey man, I got the flash to work. Thank you so much!
ben3759 said:
Hey man, I got the flash to work. Thank you so much!
Click to expand...
Click to collapse
Now, if you still want SuperSU, flash CF-Auto-Root.
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
I would recommend nuking it... wipe the phone data and then install the latest full official firmware over whatever you have now. Then you can go back and start modding.
Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse
Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?
Should be, but it's not safe since you do not know the current root method.
Odds are fairly high that you have malware on the device. Be safe, nuke it.
Jay_Nz said:
Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?
Click to expand...
Click to collapse
Ok thanks for replying. Anti-virus shows device is clean. I'll do a clean one then as recommended . Flash official firmware first then flash twrp and probably will go for magisk root. Wish me luck as power button is mushed in and have to poke it real hard. I don't even know if bootloader is unlocked or not.. Haha
tdm said:
The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
Click to expand...
Click to collapse
where to find these solutions??
Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Druboo666 said:
where to find these solutions??
Click to expand...
Click to collapse
tdm said:
Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Click to expand...
Click to collapse
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??
Druboo666 said:
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??
Click to expand...
Click to collapse
I don't know, you can try.
Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse
I just posted some huge verbose $hit on your previous post, just sayin
Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you
Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Jay_Nz said:
Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you
Click to expand...
Click to collapse
Hi thanks for the reply. I downloaded zip from zte and did an update from phone settings, it pumped me to marshmallow but next release version of zte up. Then another Ota and now I'm on nougat. Checked and root access is gone as expected but funnily enough app shows no root access but busy box binary yes.. Don't know if that's normal. Did a full factory reset too. Now I'm on full Chinese variant stock rom unrooted hence getting Ota. I pressed volume and power button together and managed to get to the screen with start in green and text screen. Other options included restart, power off, reboot to recovery and bootloader and it did show bootloader is locked. I'm thinking of unlocking bootloader, installing TWRP, then root through magisk and perhaps change to A2017U (usa firmware)... Fingers crossed. Thanks again..
tdm said:
Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Click to expand...
Click to collapse
But that's for the A2017U... Be careful with that, he can brick his phone or lose signal