yashsingh1/xdaforums huggingface dataset:
[Android General] 69Rixter:
I*'m not really sure what I did to subscribe to this thread, but, I want to tell everyone how I upgraded the ZTEn817.

RETURN TO SENDER

!!! This phone was/is the biggest P.O.S on the market today!!! Immediately, take it back to the distributor, get your money back and use that money towards purchasing a good, respectable phone from a good, respectable company. THAT's how you "upgrade" a ZTEn817

Shine On:

Rick
[Android General] doglog666:
Cool, thanks for the response. Getting the battery charged up to give this a try. I will let you know how things go
[Android General] doglog666:
This is the exactly what i get. This and boot into TWRP. adb sideload failed everytime, everything else just error:closed.
[Android General] slacker8135666:
In this thread I have my drive link posted several times. I have the full image from this phone the file name is backup. Img. I took that Img right out of the box. I had to root in order to get the image but that is all that was done to the phone.
[Android General] JAcktheick:
Dude I bricked my stuff if you could send me the rom for the zte n817 i would greatly appricate it. email me at chrisrelic@mail.com please
[Android General] BitaloBhudey:
Read the message directly above your comment bro lol. That's where you download the backup.
[Android General] Gborg3:
Working on Oppo Find 7 there were issues like that and you would have to go into Device Manager and uninstall the current driver installed with automatic updating turned off and make sure the right one is installed and that might or could change what it's called. If it does then things should work better.
[Android General] doglog666:
Im using Linux Mint. Also tried on a fresh windows install with Virtualbox, but same results. Think im gonna just break down and pay them the $25 for a new one
[Android General] y2kta00:
Any chance for 6.0 and up OS? I know you guys are working hard on this phone.
[Android General] slacker8135666:
6 is my next attempt since 4 is kicking me a** so y not have 6 burry me. I actually have 8 downloading now but I know that's a joke but what the hell
[Android General] Gborg3:
Just think of my 2010 HP TouchPad currently snappily running nightly releases of Evervolv N with alpha releases of O already out there. There's always a way.
[Android General] tonsdog:
If anyone is having trouble rooting I used the dirtycow method. Nothing else worked. If you google it the zip package is exploit_adb the password should be nox

You push the files to data local tmp then run the exploit.sh and it'll give root access. From there you can dd the recovery
[Android General] Gborg3:
Make sure with or without root you go to Developer Options and go to the bottom and set it to at most 1-2 background process. Has to be set each time it's booted up or with root can be automated with Rom Toolbox or 3C Toolbox in the scripting section.
[Android General] Figlet:
So I've successfully bricked mine, I think. The only USB connections I've found are the Qualcomm diagnostic ones. The only partition I replaced is recovery. Strangely enough, it bricked when I flashed my own backup image. Anyone know which Qualcomm tool to use to flash anything?
[Android General] Gborg3:
Can you get to recovery or fastboot?
[Android General] Figlet:
Nope. The only USB connection I have is either a blank white or blank black screen, both which result only in the QC diag interface. I found some new QC software, so I may give it another go
[Android General] Figlet:
I may have a qc tool that will allow partitioning & flashing. I have one I used to trip qc 9008 on an ftp locked LG earlier. I'll get back around to this phone eventually and share what I learn. I'm sure there are ZTE/qc recovery tools out there.
[Android General] slacker8135666:
read this thread https://www.leakite.com/2016/06/revised-how-to-unbrick-qualcomm-android.html thid id how i have unbricked a few of my phones. Sorry I havent been around much just loosing the rom battle. Hey if anyone wants to help or brainstorm on this I would so much appreciate the help cause I'm at the point of giving up but I refuse to let this phone beat me. So if ur interested pm me or e-mail me at slackerjim79ta@gmail.com. I did get a recovery working that everything works on it. Sideload doesn't fail and adb works on it also plus ext sdcard. the first recovery I had got off this thread didn't have those three things working so if anyone needs that file get a hold of me. I gave up on the cm11 I'm now trying cm12.1.
[Android General] Figlet:
I'll email you if I pick it back up. I'm working on lineageos for vzw desire 526 now so I'm fully invested in it, but I'll Polly get back to this after
[Android General] slacker8135666:
Definitely hmu im also working on an I phone and an LG tribute 2 I took our last year. So im around and haventt given up on this turn. Yet. Im try. When ever u want to run on baord u r more than 5
[Android General] Gborg3:
I would love a functional AOSP rom on this handset but in the time until that is available I'd simply suggest root and the app L Speed and removing and replacing any full version apps like Facebook with their lite versions. Getting rid of extra system apps could help too and I'd suggest adaway to keep data usage down.

---------- Post added at 04:25 PM ---------- Previous post was at 03:46 PM ----------

I'd enjoy a copy copy of the recovery and once the holidays are over I'll have have access to a computer again. I've been helping troubleshoot Evervolv N builds builds on the TouchPad but I have plenty of free time. I'll email you so you can send recovery.
[Android General] slacker8135666:
Well everyone I finally got the cm11 completed for this phone. I will be testing it for now. If anyone else wants to test it let me know and I will be willing to share it. I will post updates about it.
[Android General] swear000:
Phone Test

The only method that works for rooting the N817 (Wellington) is the one described in this thread. If your phone does not root, you may want to strongly consider a different phone. It is not possible to recover the phone if it is bricked because none of the software for this phone can generate the necessary scatter file. I am currently trying QPST to interact with the phone.

Search online if you need a better explaination.
[Android General] KittenSauce:
I would love to test. The stock firmware is painfully slow, and I would think that even a buggy mess would work better. I found this phone in a recycle bin, anyway, so I haven't got much to lose. Thanks for all your work on this phone.
[Android General] RebelLion_:
Which method? I only see a way to install recovery in this thread unless I missed the post later on. I have tried every imaginable method for the past few months and had no luck
[Android General] slacker8135666:
The way I rooted 6 of these phones was with PC and kingoroot. It fails the first time so then I do from adb reboot disemmwrp and then it usually goes. The apk apps do not root this phone. Now onto the second thing the cm11 is not ready for release yet. I have encountered a problem with it. But I think I know how to fix it. I just got to get time to get on the computer.
[Android General] wmhaganjr1013:
Having trouble rooting N817 with kingo what version is needed I deleted it and just downloaded newest version. I am going to try older versions
[Android General] slacker8135666:
Ok here's the update with the cm11 rom for this device . I fixed the black screen issue and now im just waiting for this to finish up and it should be good. It should be done in a hr or 2 so just hang in there. We r so close to a working cm11 rom for this slow phone. As soon as it gets done I'll post my results
[Android General] ZeDingo:
Go to Settings >> About phone, and check your SW Version. If it's N817V1.0.0B13 then you have the 2017-09-01 security patch and root is not possible for now.

If it's not B13, then any version of Kingo should work. It downloads its strategies from Root Genius cloud servers. You MUST do "adb reboot disemmcwp" first!
[Android General] RebelLion_:
Is there any way to downgrade this phone and possibly achieve root? I don't even care if I can upgrade back to this version. Any kind of root access to improve the system is all I'm after with this.
[Android General] KittenSauce:
Hmm, Dirty CoW wasn't *fully* patched until November of 2017, so I wonder if a modified version of the exploit would work? I've tried running the exploit on this phone before, unsuccessfully, but maybe even an unmodified version would work with "adb reboot disemmcwp" (I hadn't known about that command at the time).
[Android General] wmhaganjr1013:
look please

adb reboot disemmcwrp ???????? disemmcwp?????

---------- Post added at 04:14 AM ---------- Previous post was at 04:12 AM ----------

i did this by accident ???? anyway to fix this not rooted black screen now

---------- Post added at 04:15 AM ---------- Previous post was at 04:14 AM ----------

factory reset from factory recovery but still no root with kingo

---------- Post added at 04:17 AM ---------- Previous post was at 04:15 AM ----------

what about dirty cow i would like details please i cant find it anywhere

---------- Post added at 04:18 AM ---------- Previous post was at 04:17 AM ----------

sorry for slow response i have been working on a computer with bad virus
[Android General] swear000:
Write protection

The phone is write protected. This is a basic security measure for this phone. Most individuals access their android phones via adb. This allows the computer to communicate with the phone. The command "adb reboot disemmcwp" is used to disable write protection. To re-enable write protection issue this command "adb reboot emmcwpenab". Not every phone is rootable since the device manufacturers don't anticipate individuals to utilize this feature.
[Android General] slacker8135666:
Update on the cm11 rom. Still having a problem with flashing it. I keep getting mount data failed but it says at the end system installed successfully. I've got 3 of these roms done with some changes to each one thinking it would fix my issue. If anyone has any ideas I would appreciate the help. Im going to try from terminal in twrp mount -0 rw,remout /system and see if that helps
[Android General] swear000:
Format

Formatting the storage space prior to installing the ROM is suggested by some who have encountered similar problems.
[Android General] slacker8135666:
I was able to get past the error on flashing the rom. You just have to go-to mount and unmount system data and cache. Now im having another issue that im recompiling again with some changes. Should know in a couple hrs
[Android General] DoodleTooth:
Hey there, I have the ZTE N817 with a SW N817V1.0.0B11 and it's also a 4.4.4 version. We all know that this model of phone has extremely limited internal storage space; I want to be able to download and install apps onto my sd card. I've never rooted a phone before and would greatly appreciate some help because I cannot find that specific how-to anywhere (unless I missed it in this thread). SOS please help.
[Android General] slacker8135666:
Read the beginning of this thread for how to root and install custom recovery. I have used apps2sd program to make room but you have to be very careful when using that program because it is very easy to brick your phone. After you get root and install recovery make sure to boot into recovery and make a backup before you make changes to anything. Just in case something goes wrong. In this thread there is a link to my Google drive which has the ext-sdcard working so use that for your recovery
[Android General] Gborg3:
Any word on CM11? L Speed and Adaway can only help a terrible stock firmware so much.
[Android General] slacker8135666:
No luck with the cm11 rom. I hope to have it done soon just too much to deal with at the moment
[Android General] slacker8135666:
I am having to start all over again on the rom. I can't get passed the bootloop issue. I hope sometime soon I will figure it out but with my daughter being in and out of the hospital I havent had the time to mess with it
[Android General] swear000:
I used to clear the cache and davlik cache when installing a new ROM. That usually did the trick but it sounds like there may be deeper issues.
[Android General] c3p0u812:
How do you get this phone into download mode?
[Android General] KittenSauce:
You don't. Recovery mode is POWER + VOL DOWN, if I recall correctly, and FTM is POWER + VOL UP. It may be the reverse, however.
[Android General] c3p0u812:
How do you install twrp without download mode? Don't I need to be in dl mode to use odin?
[Android General] KittenSauce:
Ah, that would be much easier, wouldn't it...

In short, you have to send the command "adb reboot disemmcwp" to the phone, to disable EMMC write-protection (supposedly). You then must run the Windows version of KingoRoot (not the APK) to root the phone. Finally, you can flash the TWRP image from the Google Drive link below using an application like Flashify.

https://drive.google.com/drive/mobile/folders/0BzsO7AY9apEzUWlUNXpvOXFhWXM

Only Samsung phones can use Odin, if I recall correctly.
[Android General] c3p0u812:
minimal adb and fastboot says my version 31 is incorrect. :( I'm dl'ing android studio to see if that helps
[Android General] KittenSauce:
I'm pretty sure that the Minimal ADB and Fastboot package is outdated by now (not that it should matter; the phone is still on Android Kitkat). You can download Google's official ADB/Fastboot package at the bottom of this article: https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
[Android General] c3p0u812:
Thanks. That's better it works. lol

I opened cmd with adm privileges. Ran the adb reboot disemmcwp. Downloaded latest kingo but it failed. I'm stumped :(

EDIT:I have the security patch...
[Android General] swear000:
The Phone

You seem to be doing everything correctly. The problem is not with what is being done. It is the phone itself. It is a very locked phone and sometimes KingoRoot will work. Sometimes it will not. From what I have witnessed, It would have been better for phone manufacturers to allow root access from the beginning. Most phones are packed full of bloatware and the ability to root the phone and install a custom ROM helps free up space.
[Android General] The5thSurvivor:
My girlfriend has the ZTE Quest N817 phone from Assurance Wireless (SW N817V1.0.0B11). It's pretty damn slow to say the least. :( When was this phone originally released? 2014? 2015? :confused: In my opinion it doesn't have sufficient RAM to run KitKat smoothly once you open more than one app. It feels like this phone was meant for GingerBread with the amount of RAM it has. I've tried stopping as many of the running apps that aren't needed as possible, which helps with an increase in speed, but not good enough.

Are there any options to unlock the bootloader available? I haven't found any after extensive searching. :rolleyes:

Some documents for this phone mention it has a SIM card. However, I don't see one anywhere after opening it. Do any variants of this phone (such as the SafeLink, QLink, LifeLine, ect...) utilize a SIM card? :confused: The reason I ask this is because I was hoping that the Assurance Wireless version could be used with T-Mobile.

Currently her phone has the following apps disabled: Cloud Print, Google Drive, Google Play Movies & TV, Google Music, Google+, Google Hangouts. What bloatware apps are safe to remove once you have root access? I think the Mobile ID app is what Assurance Wireless/Virgin Mobile use to provide service to the phone, so that one probably can't be removed.

slacker8135666 is the only person I've came across that mentions a custom ROM for this phone. Where you able to get any up and running? I was hoping to be able to update to at least Android 5.1 on this turtle of a phone. :fingers-crossed:

If one were to use a custom ROM on this phone, would that mean you can no longer have the service from the provider that originally issued you the phone?

And lastly, is it possible to put the Ice Cream Sandwich version of HTC Sense on this phone? LOL, :laugh: probably not, but I'd love to see that. :victory:
[Android General] The5thSurvivor:
Those are the kindest words I've seen for this device :laugh: It must be an error in the documentation stating that this phone can use SIM cards.

Any list of those specific apps? Or an amount of them?

If I install that ROM, will the service with Assurance Wireless still be active? :confused:

That's unfortunate as this device really needs improvement. And I'm sorry to hear about your daughter. :( Definitely take priority in taking care of her and not this not so great device.

I see. Thanks you. :good: I'll be sure to use that recovery in the event I ended up flashing the custom one. But first I need to know if service from the provider will still be active or not.
[Android General] slacker8135666:
Yes service will stay. On my soon to be coaster I almost deleted everything even most Google apps but don't go crazy like I did cause you will have a pile of these coasters just like I do. I even got rid of chrome and put chrome Dev in it's place and got rid of the browser from zte took out launcher and only have Nova launcher in it now BUT the first thing that had to go was that touchpal keyboard with all the stupid emojis. I only have play services play store chrome Dev Google and Gboard that's all the Google apps that I kept oh yeah and YouTube
[Android General] Gborg3:
The one thing I've done other than remove bloatware is install Adaway. I booted into TWRP the other day and cleared cache and dalvik to help with some hiccups. The phone refused to work after that so I factory reset in TWRP and that actually slightly improved usability so far. Such an odd antique device being given as new.. My TouchPad is even looking at it strangely.

Debloated and L Speed with most things set to increase speed over battery seems to help too. Can't do much with Kernel Adiutor with stock kernel.
[Android General] The5thSurvivor:
I didn't that after installing a custom recovery the service would be gone, just wanted confirmation. Thank you. :highfive: But I'm really surprised that after installing an edited ROM the service is still active :eek:

I'll be very careful with I remove. But why are the other phones you have coasters? If you remove a system app and end up bricking your phone, wouldn't you be able to restore a nandroid from the custom recovery and make the phone useable again? Or install a ROM either from recovery or call up customer service to install their version of the ROM over the air? The reason I say that is because I just remembered that when my girlfriend got this phone the service wasn't active. She had to call them up got get it activated. They walked her through a series of steps to do on the phone. After she did that, the ROM seems to have been changed. The boot up logo now had Assurance Wireless logo on it (that wasn't there before) and the interface changed a bit. Meaning the phone she received in the mail had a different ROM, maybe the real stock ROM from ZTE.

Nice! :cool: I will definitely have to do the same. About the "can't update system error" you had mentioned before, did you remove the Mobile ID app? Or is it unrelated?
[Android General] slacker8135666:
I had pulled the mobile id app before and had some problems from removing it so now I just leave it in the phone. I can't recall what the problem was from removing it since it was months ago. I also use nova launcher for more speed and to customize my phone. Color status bar app is also nice to customize the status bar.

---------- Post added 18th February 2018 at 12:47 AM ---------- Previous post was 17th February 2018 at 11:49 PM ----------

Nice! :cool: I will definitely have to do the same. About the "can't update system error" you had mentioned before, did you remove the Mobile ID app? Or is it unrelated?[/QUOTE]

That error is due to the system update for the security patch. It doesn't update because it doesn't verify it correctly. It's no big deal as far as I know not to have the update. It's just annoying having that icon in the status bar. Also as far as I have seen so far with that update applied people are not able to get root.
[Android General] slacker8135666:
update on the cm11 rom for this phone. I had recompiled the rom a few hours ago and I am currently testing it. I am passed the bootloop and phone is booted up. I will continue to test and if all is good I will release it. I don't want to rush it since this is the 10 th time I recompiled it. But I never got it to boot all the way so I hope it's almost done. So I can throw this phone in the trash and move on to the next device.
[Android General] The5thSurvivor:
Wow I could have sworn you mentioned giving up on cm11. Hope you get it working bro :) This phone sure as hell can use custom ROMs.

Since my girlfriend won't be using this phone for a few days, now is a good time for me to root it and and install a custom recovery. However, I want to be very careful since slacker8135666 and other users have reported this bricking this device. So, do I take the following steps below in the order that they are in?

https://drive.google.com/drive/folders/0BzsO7AY9apEzUWlUNXpvOXFhWXM

1) Root the phone with kingO root (or is there a better option?). Reboot with "adb reboot disemmcwp" command first

2) Install BusyBox (Required for the next app)

3) Install Online Nandroid Backup * ROOT and make a Nandroid back up

4) Install Partitions Backup and Restore to back up the stock recovery.img

5) Download the TWRP recovery that has support for the external SD card

6) Download Chainfire's SuperUser APK (SR3-SuperSU-v2.79-SR3-20170114223742)

7) Download the TWRP ZTE N817 recovery (named "recovery.img") and the stock recovery (named: "recovery_orig.img") from here

8) Install [ROOT] Rashr - Flash Tool to be able to install the TWRP recovery.img and Chainfire's SuperUser

9) Install SD Maid - System Cleaning Tool to remove KingO root.

Is that all that needs to be done? Some of the instructions in this thread are either out of order or unclear due to posts being edited.
[Android General] The5thSurvivor:
Now I'm trying to root the phone with KingO root, but adb doesn't detect the device :(

I installed the drivers straight from the phone, killed the adb server, then restarted it and nothing. How did you guys get it to detect the phone? :confused:

EDIT: Well I finally got adb to detect the phone. I followed this guide here and reinstalled the driver from the phone itself and adb picked it up. Then I gained root with Kingo Root. :victory:

I also followed steps 1-7 from my post above, but now I'm stuck at step 8 where Rashr keeps crashing :eek: Mind you, I had no other open apps running.

EDIT 2: After trying Rashr a few times (why does it keep crashing?), I was able to install the TWRP recovery image. It's refreshing to see TWRP running on this phone :D

So... do I add Super User before removing Kingo Root or after? I want to make sure root access isn't lost.
[Android General] slacker8135666:
The way I did my phone was so much easier than this. I rooted with kingoroot from pc. Then I installed root rasher (but twrp also will flash) then I flashed the twrp recovery with extsdcard fix. Then I booted into recovery did a backup in twrp recovery also flashed supersu (chainfire of course I would never use any other super app) Then booted back up and you have to remove kingo's superuser. The problem is that it gets installed as a system app so disable it force close and I always install supersu as a system app. Then what I did is remove kingo's superuser with a app to remove system apps. Then finally ran sdmaid just to clean up junk laying around from all the steps i took. Hope this helps you and not confuse you more!!!