Zte N817 Assurance Phone - Is There A 2-sided Camera Setting?

jag9906 · Apr 10, 2017

First off doing this will void your warranty and can brick your device. Following these elementary steps should work for y'all. I will state here and farther down, make certain you download all programs needed and both recovery.img and recovery_orig.img. I am in no way resposible for your device being bricked.

**Only thing I have non tested is the external sd card, I make no promises that it works. I only have one sd micro card its installed in my master device. So install the recoveries and supersu to your internal sdcard.

This is for assurance wireless, I have seen one or two other n817 devices if the specs are the same, they "should" work with this twrp, but use partition backup and restore by wanam on Play store to get a recovery.img for your device. I do non use this programme for arrangement dorsum up, for some reason it does not piece of work properly but its fine for boot,aboot, recovery and other smaller partitions.

This is a ported twrp from kis3 twrp version 3.0.2-0 by KonstaT from here http://konstakang.com/devices/kis3/TWRP/. Also this version of chainfire su SR3-SuperSU-v2.79-SR3-20170114223742 download from here https://download.chainfire.eu/1021/. This twrp recovery has Supersu folder but I still installed the nil from recovery to be sure.

The twrp n817 recovery named: recovery.img along with the original n817 recovery named: recovery_orig.img go hither https://github.com/jag9906/n817_twrp

Other programs needed [ROOT]Rashr flash tool, online nandroid backup *root*, SD maid from Play Store. The Rashr flash tool is required, you can use any support you wish, I adopt SD maid for cleaning upward organisation and removing/freezing programs y'all can use whatsoever you employ, this is to remove your temp root after recovery and supersu is installed.

**Again I am stating here the Rashr flash tool is required this will allow you to install the recovery.img with a locked bootloader. This is a must to install this twrp recovery. The twrp app will not piece of work until you have supersu installed. In that location are other wink tools, but this worked flawless with kingo so its the only ane I will support for this guide. If you use another wink tool its on yous.

First make a back up prior to installing the twrp recovery. Utilise the online nandoird dorsum up of all partitions I salve them as twrp. If you have external SD bill of fare yous can do all at one time if non do all but information and system then copy to your reckoner and then back up system folder. Your pick on data, I dorsum up my apk so never data.

Next run Rashr flash tool from Play store the first option is recovery from storage, choose this option and then become to your location on sdcard and select recovery.img hit ok it volition take about x to 15 seconds and inquire if you lot want to reboot into recovery, hit yeah and so your device will reboot into recovery. In one case loaded swipe and go to install, tiptop left observe your SR3-SuperSU-v2.79-SR3-20170114223742.zip file and select that, then swipe to install. Once finished hit reboot and arrangement.

Then run SD Maid or any root tool to uninstall you accept. You can now delete/remove Kingo or any root you used prior to installing the recovery and have supersu past chainfire as your root for the device.

Y'all at present accept a twrp recovery, and chainfire's supersu installed on your n817 device.

thanks to KonstaT and Chainfire for the hard work they accept done.

stevenh512

Wow, thanks.

I was able to port KonstaT's CWM for the kis3 to this device and it works almost flawlessly, just when I tried to do the same with TWRP I simply got a white screen and had to pull the battery. This boots fine, so I'm interested in taking it apart and seeing what you changed.

External SD card doesn't piece of work on my phone. Since I plan on taking it autonomously anyway I'll expect at the fstab files, if I figure information technology out I'll be sure to share my changes.

jag9906 · Apr 17, 2017

Aye like I said in mail service I have no external sdcard and then I could not exam. With putting in external a few ttimes I was looping. I think I did 6 builds and on my device which is not used. I was able to create boot, system and data backups and flash again amd install supersu from chainfire. I have built a number of kernels but wont kick. I am simply going to become working kernel and nethunter it or maybe kexec hardboot for a linux. Also I rhink I used the original recovery kernel, might take gone stock.

Did you do recovery or cm 11. I tried near 5 builds of cm11 furthest i got to was loading applications screen and locking. Did you lot flash this twrp. With rashr app. Non certain how information technology will handle it beingness locked kick. Each of the port guides useless being locked. Days off this week might expect into delving into it more. But after 5 months of headaches with exynos kernel and rom might need a break. Tired of these corps releasing broken code to stall people. iii or iv from scratch begings with samdung kernel between 2,000 and vi,,000 files edited on each try and still borked, with even.trying to dorsum port newer versions of drivers. I accept one solid kernel running simply just above stock because I removed there fuelgague and charger commuter with a Script for deepsleep, might be my best however earlier I get a new phone in a few months. Samsung and zte plus any mediatek I'm over them at present and swearing off.

stevenh512

I notice the line for the sdcard is commented out in twrp.fstab, I'll try uncommenting that and see what happens, just I retrieve to get the sdcard working correctly under CWM I had to use vold. The line for CWM was:

/devices/msm_sdcc.2/mmc_host auto auto defaults voldmanaged=sdcard0:auto,noemulatedsd

This seems to work with or without an sd-ext partition (mounting sd-ext normally as /dev/block/mmcblk1p2 works, no need to apply vold for that).

Did you do recovery or cm 11. I tried near 5 builds of cm11 furthest i got to was loading applications screen and locking. Did you flash this twrp. With rashr app.

I did KonstaT's CWM recovery from the kis3. I think the only things I had to modify were the kernel (from stock recovery), fstab (based on stock recovery, with some trial and error) and default.prop

Haven't tried flashing CM11 to this phone yet, I accept tried edifice the device/vendor trees to build CM11 from source, but ZTE'south kernel source for this device doesn't compile and KnostaT'southward ZTE msm8610 kernel source doesn't boot, and so that's equally far every bit I've managed to get.

I flashed this TWRP with the rashr app, just when I flashed CWM I had no trouble using (from a root adb crush) "dd if=/path/to/recovery.img of=/dev/cake/platform/msm_sdcc.1/past-name/recovery"

I did need to (once) reboot the device with "adb reboot disemmcwp" when I initially got root earlier I could mount system rw and install SuperSU.

jag9906

Yeah that was the effect when.I did stuff with my main phone, I but take one sdcard in principal telephone so I didn't become around to testung vold. That sould set the issue. I learned that lesson a few weeks ago with my samsung phone. If it works listen posting that fike so.I tin.update this twrp.and then people cam atleast take a touch backup with supersu non those roots that auto install garbage apks and have ads.

I found another cm11 I will check later afyer work tomorrow and post link since kis3 is gms this one was cmda for porting rom.

jag9906

ok can effort porting the cm11 unofficial condor, or carbon KK unofficial condor both I think I found through xda, in that location is an AOPK condor MM nightly if you want to try to up to that or the lineage Bone condor 14.ane with a new kernel. can google this cm-11-20140808-UNOFFICIAL-condor to get the link from xda or search hither.

stevenh512 · Apr 17, 2017

I got my sdcard (with sd-ext partitioning) working with this twrp.fstab:

                                  # mount betoken	fstype		device						[device2, parameters] /boot		emmc		/dev/block/platform/msm_sdcc.1/by-proper name/kicking	flags=fill-in=1; /recovery	emmc		/dev/cake/platform/msm_sdcc.i/by-proper noun/recovery flags=backup=i; /system		ext4		/dev/block/platform/msm_sdcc.ane/by-name/organisation	flags=fill-in=i; /cache		ext4		/dev/cake/platform/msm_sdcc.ane/by-name/cache	flags=backup=1; /data		ext4		/dev/block/platform/msm_sdcc.1/by-name/userdata	flags=backup=1; length=-16384 /sdcard		vfat		/dev/block/mmcblk1p1 /dev/block/mmcblk1		flags=display="MicroSD";storage;wipeingui;removable /sd-ext		auto		/dev/block/mmcblk1p2				flags=wipeingui;removable;backup=one

I'm sure that's not quite right, there are probably some flags I'1000 missing and definitely some other partitions you'd want to back upward. I likewise have TWRP 3.1.0-0 compiling for this device from source (against LineageOS cm-eleven.0 tree with precompiled kernel from stock recovery) and booting with internal "emulated" SD and external SD both working, but I need to tweak my BoardConfig.mk a bit more to solve a couple minor issues. If I can get that 100% working I might endeavor to "make bacon" and see what happens, I'm pretty sure the rest of my device tree is correct and I've pulled all of the vendor files from the device. I didn't recollect to accept a backup of my stock ROM when I rooted, but I do have a full fill-in of my device in its current state.

pyrohydrosmok · Apr 21, 2017

First off doing this will void your warranty and tin brick your device. Following these unproblematic steps should piece of work for you. I will state hither and further downward, make sure you download all programs needed and both recovery.img and recovery_orig.img. I am in no fashion resposible for your device beingness bricked.
**Only thing I have not tested is the external sd card, I make no promises that it works. I only have ane sd micro carte du jour its installed in my main device. So install the recoveries and supersu to your internal sdcard.

This is for assurance wireless, I accept seen ane or two other n817 devices if the specs are the same, they "should" work with this twrp, but use partition backup and restore by wanam on Play store to get a recovery.img for your device. I do not use this program for system back up, for some reason it does not work properly merely its fine for boot,aboot, recovery and other smaller partitions.

This is a ported twrp from kis3 twrp version 3.0.two-0 by KonstaT from here http://konstakang.com/devices/kis3/TWRP/. Also this version of chainfire su SR3-SuperSU-v2.79-SR3-20170114223742 download from here https://download.chainfire.european union/1021/. This twrp recovery has Supersu folder but I nevertheless installed the nada from recovery to be sure.

The twrp n817 recovery named: recovery.img forth with the original n817 recovery named: recovery_orig.img go here https://github.com/jag9906/n817_twrp

Other programs needed [ROOT]Rashr flash tool, online nandroid fill-in *root*, SD maid from Play Store. The Rashr flash tool is required, y'all can utilise any back upwardly you lot wish, I prefer SD maid for cleaning up system and removing/freezing programs you tin use any you utilize, this is to remove your temp root after recovery and supersu is installed.

**Once again I am stating here the Rashr flash tool is required this will permit you lot to install the recovery.img with a locked bootloader. This is a must to install this twrp recovery. The twrp app will non work until you have supersu installed. There are other flash tools, but this worked flawless with kingo and so its the just one I will support for this guide. If you use another wink tool its on y'all.

First make a support prior to installing the twrp recovery. Employ the online nandoird support of all partitions I relieve them as twrp. If you lot have external SD menu you can do all at in one case if not practice all but information and organization then re-create to your computer and and so back upwardly system folder. Your option on information, I back upward my apk and so never data.

Next run Rashr flash tool from Play shop the first option is recovery from storage, choose this choice then go to your location on sdcard and select recovery.img hitting ok it will accept almost 10 to 15 seconds and ask if you want to reboot into recovery, hitting yes then your device will reboot into recovery. Once loaded swipe and go to install, top left observe your SR3-SuperSU-v2.79-SR3-20170114223742.zip file and select that, then swipe to install. Once finished hit reboot and organization.

Then run SD Maid or any root tool to uninstall you have. Y'all can now delete/remove Kingo or whatever root you used prior to installing the recovery and have supersu by chainfire equally your root for the device.

Yous now have a twrp recovery, and chainfire'southward supersu installed on your n817 device.

cheers to KonstaT and Chainfire for the hard piece of work they have washed.

Unfortunately Kingo can't root my device and neither can anything else...... Sucks but hey the telephone was free. Hopefully something can work in the future *shrugs*

Edit: rebooted "adb reboot disemmcwp" and Kingo worked ._.

stevenh512 · April 22, 2017

Yeah, this telephone was pretty hard before Male monarch/Kingo supported it, and with no fastboot I don't call back at that place's whatsoever manner other than a ZTE signed update to alter the /organization division without rebooting with "adb reboot disemmcwp" first. Before I discovered a post mentioning using that control to disable the write-protection on some other ZTE device I was able to get a root prompt with the correct SELinux context but I however couldn't write anything to /arrangement. Once I got the write-protection disabled, I didn't even bother with whatever of the 1-click rooting apps. I just got a root shell, mounted /organisation rw and proceeded to put all of the SuperSU files where they become and set their permissions by hand, rebooted and I was good to go. Of course, once I got a recovery installed I did re-wink SuperSU from an update zip merely to make sure it was right.

morpheous1777

does anyone accept a stock backup, i don't kn0w what i did, only now the standard android recovery tells me there are missing files when i exercise md5 check and it kick loops correct dorsum to recovery, anyone have and recommendations for repair, i can go to stock recovery, i can adb side load updates or choose from cache or sd card, when i popular out the battery and plug in its recognized as:
ZTE WCDMA Technologies MSM

right before kicking loop to recovery:
Product: ZTE HSUSB Device Manufacturer: ZTE Incorporated (dmesg)

while in recovery in adb sideload manner
Product: N817 Manufacturer: ZTE (dmesg)
18d1:d001 Google Inc. Nexus 4 (fastboot)(lsusb)

whitout battery blackness screen:
QSHSUSB_BULK qualcom CDMA technologies MSM

i dont know if im in ftm mode, screen but stays black and shows up as higher up? when in recovery

leetree2001 · May 14, 2017

I got my sdcard (with sd-ext partitioning) working with this twrp.fstab:
                                      # mountain point	fstype		device						[device2, parameters] /boot		emmc		/dev/block/platform/msm_sdcc.1/by-name/kicking	flags=fill-in=1; /recovery	emmc		/dev/block/platform/msm_sdcc.i/by-name/recovery flags=backup=1; /system		ext4		/dev/block/platform/msm_sdcc.1/by-proper name/system	flags=backup=1; /cache		ext4		/dev/cake/platform/msm_sdcc.1/by-name/enshroud	flags=backup=1; /data		ext4		/dev/block/platform/msm_sdcc.1/past-name/userdata	flags=backup=1; length=-16384 /sdcard		vfat		/dev/block/mmcblk1p1 /dev/block/mmcblk1		flags=display="MicroSD";storage;wipeingui;removable /sd-ext		auto		/dev/cake/mmcblk1p2				flags=wipeingui;removable;backup=ane                                    
I'1000 sure that's non quite right, in that location are probably some flags I'chiliad missing and definitely some other partitions you'd want to support. I as well have TWRP three.1.0-0 compiling for this device from source (against LineageOS cm-xi.0 tree with precompiled kernel from stock recovery) and booting with internal "emulated" SD and external SD both working, but I need to tweak my BoardConfig.mk a bit more to solve a couple modest issues. If I can get that 100% working I might try to "make bacon" and come across what happens, I'yard pretty sure the rest of my device tree is right and I've pulled all of the vendor files from the device. I didn't remember to accept a backup of my stock ROM when I rooted, but I do accept a full backup of my device in its current state.[/Q
Modify sdcard to sdcard1

stevenh512

does anyone have a stock backup

I likewise wouldn't mind having a stock fill-in, unfortunately I didn't remember to have a fill-in earlier I started tinkering with my system division, just thankfully I haven't managed to break annihilation I couldn't ready.

while in recovery in adb sideload style
Production: N817 Manufacturer: ZTE (dmesg)
18d1:d001 Google Inc. Nexus iv (fastboot)(lsusb)

While in this mode, are you able to actually apply fastboot? I ask for two reasons. First, if y'all're on a stock recovery, the only way you lot're going to exist able to restore a stock ROM (or install whatever other ROM) from recovery is if information technology'southward signed by ZTE, otherwise you'll need some other way (like fastboot). 2d, as far equally I can tell, there is no fastboot on my phone.

pyrohydrosmok

I got my sdcard (with sd-ext partition) working with this twrp.fstab:
                                        # mountain point	fstype		device						[device2, parameters] /boot		emmc		/dev/block/platform/msm_sdcc.1/by-proper name/boot	flags=fill-in=i; /recovery	emmc		/dev/cake/platform/msm_sdcc.1/by-name/recovery flags=backup=one; /system		ext4		/dev/block/platform/msm_sdcc.1/past-proper noun/arrangement	flags=backup=1; /cache		ext4		/dev/block/platform/msm_sdcc.ane/by-name/cache	flags=fill-in=1; /data		ext4		/dev/block/platform/msm_sdcc.i/past-proper noun/userdata	flags=fill-in=1; length=-16384 /sdcard		vfat		/dev/cake/mmcblk1p1 /dev/block/mmcblk1		flags=display="MicroSD";storage;wipeingui;removable /sd-ext		auto		/dev/block/mmcblk1p2				flags=wipeingui;removable;backup=1                                      
I'thousand certain that's not quite right, there are probably some flags I'm missing and definitely some other partitions y'all'd desire to back up. I likewise have TWRP three.1.0-0 compiling for this device from source (against LineageOS cm-xi.0 tree with precompiled kernel from stock recovery) and booting with internal "emulated" SD and external SD both working, but I demand to tweak my BoardConfig.mk a scrap more to solve a couple minor issues. If I can go that 100% working I might try to "make salary" and encounter what happens, I'thousand pretty sure the rest of my device tree is correct and I've pulled all of the vendor files from the device. I didn't retrieve to take a backup of my stock ROM when I rooted, but I do have a full backup of my device in its current state.[/Q
Modify sdcard to sdcard1
I'd actually dear this and I'd love information technology more than if I could contribute in some style... this phone is painfully boring on the stock Bone.

tnomtlaw

Have nothing to contribute right now.But want to Thank all you guys for your unselfish work!!!

Sent from my LGLS770 using Tapatalk

tnomtlaw

Does anyone have the stock rom?? The recovery bricked my assurance n817.Please help

equitube

This worked great, thank you

---------- Post added at x:03 PM ---------- Previous mail service was at 09:32 PM ----------

It works, but my organization is very unstable right now. I take a feeling information technology'southward that KingCrap . It doesn't similar to be replaced with another SU. That stuff is malware and I never apply it unless I"m desperate. I'k going to try to push 3c toolbox to it. It won't stay up long enough to install it from playstore.

slacker8135666

Member96 posts Cheers: 16

Does anyone have the stock rom?? The recovery bricked my assurance n817.Delight help

I did a total backup of my zte n817. information technology'south in .img format. pm me and I'll transport it to my google drive and give you the link. Practice y'all know what partition goes where? I also have that info too !! After 3 bricked phones I take learned somewhat of a lesson

equitube

I tin can't do annihilation with it now. It won't stay upwardly long plenty. I accept a nandroid backup but it's on the external sd which this TWRP can't meet. There isn't enough space on the internal to copy it to. I'm giving up for now, I"ve spent mode besides much time on a $20 phone

tnomtlaw

Member96 posts Thank you: 16
Does anyone take the stock rom?? The recovery bricked my assurance n817.Please assist

I did a full backup of my zte n817. it's in .img format. pm me and I'll transport it to my google bulldoze and give yous the link. Practice you know what partition goes where? I also have that info too !! After 3 bricked phones I have learned somewhat of a lesson

Sent from my LGLS770 using Tapatalk