Help zte z998 bootloop problem

[dank memes714]

Basically ive been having a problem where when i turn on my phone it stays on the att logo and wont go any further. i tried the recovery option but its not working, the phone is rooted with kingroot but i havent done anything! i tried app2sd (i believe) so i could use my sd card which kitkat had screwed up, all it let me do was move some files to the sd card. after a while i turned off my phone and bam i turn it back on, bootloop! 20 hours later im in this situation so someone please help cause the only alternative is a new phone (no warranty)

 

[scary alien]

What does that mean that you "...tried the recovery option..."?

Do you have a custom recovery installed or the ability to install one?

Is your device getting far enough along in the boot-cycle that adb still responds? [you might be able to get a logcat and then maybe use adb to try to fix what is going on]

I'll go-ahead and say/ask it here (for the benefit of other/future readers): you took a Nandroid backup before changing anything on your /system partition, right? [i.e., apps2sd will change your device--changing your /system partition whilst being rooted and not having the ability to restore/recover from a Nandroid backup is obviously not a good idea]

Unless you can restore from a Nandroid backup, I'm not sure what else to suggest to you--we don't have a forum dedicated to your device here.

 

[dank memes714]

What does that mean that you "...tried the recovery option..."?

Do you have a custom recovery installed or the ability to install one?

Is your device getting far enough along in the boot-cycle that adb still responds? [you might be able to get a logcat and then maybe use adb to try to fix what is going on]

I'll go-ahead and say/ask it here (for the benefit of other/future readers): you took a Nandroid backup before changing anything on your /system partition, right? [i.e., apps2sd will change your device--changing your /system partition whilst being rooted and not having the ability to restore/recover from a Nandroid backup is obviously not a good idea]

Unless you can restore from a Nandroid backup, I'm not sure what else to suggest to you--we don't have a forum dedicated to your device here.

what i meant by recovery option is that I tried using android system recovery and it didnt work, I dont get what u mean by adb still responds, sorry all i know is that it turns on then the att logo and "powered by android" logo comes up then it goes to the att logo screen next and it stops working. and no i didnt change anything on my phone before using app2sd. unfortunately i never made a nandroid backup

 

[scary alien]

Yeah, the stock recovery won't do much for you (adb isn't enabled in it).

I asked about if adb will respond (i.e., adb devices shows you have a connected device or adb shell gives you a prompt, etc.) while your in a bootloop since it might have gotten far enough in the booting cycle to enable the adb daemon to allow adb to work (that might give you some options to fix things).

I'm guessing that your use of apps2sd did in fact make changes to your device for you--did it ever ask for root permission (i.e., did you get prompted by SuperUser/SuperSU to allow apps2sd to be granted root access)? If so, then that's the vehicle from which your device was changed and is indeed the likely culprit for your bootloop.

I had to ask about the Nandroid backup even in the off-case that you had an old one squirreled-away...

I'm not sure what else to suggest here unfortunately .

 

[dank memes714]

Yeah, the stock recovery won't do much for you (adb isn't enabled in it).

I asked about if adb will respond (i.e., adb devices shows you have a connected device or adb shell gives you a prompt, etc.) while your in a bootloop since it might have gotten far enough in the booting cycle to enable the adb daemon to allow adb to work (that might give you some options to fix things).

I'm guessing that your use of apps2sd did in fact make changes to your device for you--did it ever ask for root permission (i.e., did you get prompted by SuperUser/SuperSU to allow apps2sd to be granted root access)? If so, then that's the vehicle from which your device was changed and is indeed the likely culprit for your bootloop.

I had to ask about the Nandroid backup even in the off-case that you had an old one squirreled-away...

I'm not sure what else to suggest here unfortunately .

thanks for the help, i was dumb enough to try and root the damn thing without knowing everything u should know before rooting, anyways yes it did ask for root permission and it did work, it moved some of the files to my sd card, regarding the adb thing, do u think i could possibly connect to my computer and fix it or wipe everything?

 

[scary alien]

I would hope that you'd have an avenue for using some kind of ZTE stock/factory restore utility, but I'm not familiar at all with ZTE devices, although I'm pretty sure adb would not be the tool you'd be using.

 

[dank memes714]

I would hope that you'd have an avenue for using some kind of ZTE stock/factory restore utility, but I'm not familiar at all with ZTE devices, although I'm pretty sure adb would not be the tool you'd be using.

not any i can find unfortunately, would it be possible to plug it into a computer and wipe everything off from there? I heard people would flash their phones, could that work?

 

[scary alien]

not any i can find unfortunately, would it be possible to plug it into a computer and wipe everything off from there? I heard people would flash their phones, could that work?

You'd need some kind of flashing tool for your ZTE device (HTCs use something called an RUU; Samsung uses Kies/Odin; Nexus devices can directly restore factory images via the fastboot utility, etc.).

You'll have to identify something ZTE-specific for your specific device.

There's a bunch of ZTE devices in our Android phones area but none for your specific device. You could try to find something relevant/related in one of the root areas for a similar device (but not sure which one that might be).

I do see that this thread over on XDA implies that you've got an unlocked bootloader? If that's the case, then it should be straightforward to re-flash your stock partitions (if you can find someone that has the stock partitions--I can't help you with that ).

Edit: that thread cited references this area which might be helpful: http://unleashedprepaids.com/forum-1491.html (but I can't vouch for any of those thread/pages, etc.)

 

[dank memes714]

You'd need some kind of flashing tool for your ZTE device (HTCs use something called an RUU; Samsung uses Kies/Odin; Nexus devices can directly restore factory images via the fastboot utility, etc.).

You'll have to identify something ZTE-specific for your specific device.

There's a bunch of ZTE devices in our Android phones area but none for your specific device. You could try to find something relevant/related in one of the root areas for a similar device (but not sure which one that might be).

I do see that this thread over on XDA implies that you've got an unlocked bootloader? If that's the case, then it should be straightforward to re-flash your stock partitions (if you can find someone that has the stock partitions--I can't help you with that ).

Edit: that thread cited references this area which might be helpful: http://unleashedprepaids.com/forum-1491.html (but I can't vouch for any of those thread/pages, etc.)

i was able to find my phone in the phone area, its also called the zte mustang (sorry forgot to mention that) it didnt have anything that would help me, as for the thread on XDA it apparently doesnt for me but ill try again, it also seems that some guy in the unleashedprepaid forum had the same bootloop problem as me but alas had to resign to using the warranty. ill try to get on the xda forum but if that doesnt work ill go to an att and see if they can fix it, if not it'll be a new phone for me, thx for the help though, i really appreciate it