• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Help!]Encryption Unsuccesful

nitestalkr

nitestalkr

Android Enthusiast
Every time the phone boots, it only displays the "Encryption Unsuccesful" screen. I can still boot to FTM mode, and the stock Android Recovery, and from FTM mode I've managed to temp boot it to a TWRP recovery, although /data in unable to mount, and I do not have Root access so I assume I cannot flash a new ROM. When I reboot the TWRP recovery, it goes back into the useless stock android recovery. I cannot get adb to recognize that the phone is in recovery mode using "adb devices" so I'm at a bit of a stand still.

This isn't a rooted phone, completely 100% stock, and there is no SD card available for this phone. I was given the phone with a "If you can fix it, it's yours" type deal.

Any help on resolving this issue is greatly appreciated.
 
This phone was basically given to me just to see if it's possible to fix, the original owner already bought a new one and handed this one off to me. Its a project phone for me. I've got my trusty 4-5 yr old LG Optimus V running KitKat so I'm not too worried.

All that needs to be done for this ZTE is to find a way to recreate the /data partition so it can be mounted, or maybe find a way to completely wipe this phone clean to a manufacture state, and repartition the phone itself and start from the ground up. If I can somehow gain SU while the phone is in it's current state, I may be able to fiddle around a bit more, but I've had no luck so far. I was hoping for some insight or tips on what can and cannot be done for this phone.
 
I've tried the Soft unbrick kit, then yes, that is how I was able to boot it into a temporary TWRP recovery. Although from there, there isnt much I can do cause I cannot mount /data still. I've also tried installing the update.zip via stock recovery, and had an installation aborted.
I'm thinking that it may be possible to fix the /data partition with a series of ADB commands/tools, rebuilding the /data with a default .img file, or some how rebuilding the partition altogether since it reads as 0mb. It may be possible that since its the "Encryption Unsuccessful" error, to find out what made it unsuccessful and fix it so that it can successfully encrypt it, so I can then successfully factory reset it.

All I have at this point are ideas, but no knowledge of how to go about it. I am also not worried what-so-ever what potential harm can possibly happen from any method that can be provided. Think of this phone as the test dummy for solving this issue for others. You suggest it, I test it.
 
rbheromax said:
you're gonna need a computer with ADB installed
boot into TWRP and I can help out
Click to expand...

Check, check, and check.
I've already managed to boot into TWRP through fastboot, but from there, I can't do much at all. Can't do anything that requires mounting /data, or editing anything in /system cause I do not have root access.
I'm not 100% if I even have USB debugging or not, for this phone was given to me after the "Encryption Unsuccessful" message started happening. Although, I am still willing to do anything you suggest.
 
once in twrp...
from computer:

adb shell

it should give you a # prompt
run:

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/data

then try and format /data from twrp menu
if not, report back
 
Still a no go on formatting it through TWRP after adb
here's the log as seen on screen after TWRP says "successful" for formatting data
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/data'
E:Unable to mount internal storage.
E:Unable to mount /data/media during GUI startup
E:Unable to mount /data/media/TWRP/.twrps when t
E:Failed to mount external storage, using intern
E:Unable to mount '/data'
E:Unable to mount '/data'
E:Unable to mount '/data'
E:Unable to mount '/data'
Formatting Data using make_ext4fs function.
E:Unable to mount '/data'
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
You may need to reboot recovery to be able to us
Updating partition details...
E:Unable to mount '/data'
E:Unable to mount internal storage.
Click to expand...

Here's what ADB showed after inputting that command

C:\android-sdk\platform-tools>adb shell
~ # ←[6ndd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/data
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/data
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/data': No space left on devi
ce
856353+0 records in
856352+0 records out
438452224 bytes (418.1MB) copied, 7.155074 seconds, 58.4MB/s
~ # ←[6ndd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/data[/QUOTE]
Click to expand...
 
connect to freenode from here:
webchat.freenode.net

enter channel #zte8930

it'll allow much faster comm
 
for those wondering....
ig we can say problem solved
i crafted a ramdisk (to boot stock rom) and recovery (cwm based so we can fomat sdcard for this hackaround)
together it makes a /data partition and /sdcard partition on only your sdcard. if u have a slow sdcard rom will be slow, but still usable!
every works as it should, no major problems i am aware of
this is only needed if you have messed up your /data partition beyond repair (such as this where u try and encrypt and it fails). it'll create bad blocks on emmc chip sort of like emmc brick bug on galaxy s2 and galaxy note devices during the ics timeframe.
 
I heard of a program that u put on PC then hook up ur phone and reburn the chip then it can put back all stock data if u can get all that data info I heard of some one doing it and worked just what I read some were
 
all the devs sitting in #zte8930 came up with something like that
that wouldnt fix this. it'd lock up upon reaching the part of his bad emmc

my device was the first test dummy for that as i found the method by accident after my awe just shut off one day and didnt fully boot back up. i investigated. cdz found partition locations. i used my linux knowlegde and tried some things. my phone worked again like magic and we worked to make it automated
 
So you're saying the only way right now known to solve this issue is to boot a "fake" /data partition from your SD card?
 
thats what we're doing here
i did also make a recovery and ramdisk that took away cache, made cache into /data and moved cache to ram since we have 1gb of ram to play with.....there are alot of things we can do, we could even resize /data to be smaller than than the area where the corruption is.
 
rbheromax said:
thats what we're doing here
i did also make a recovery and ramdisk that took away cache, made cache into /data and moved cache to ram since we have 1gb of ram to play with.....there are alot of things we can do, we could even resize /data to be smaller than than the area where the corruption is.
Click to expand...

All of the system ROM space is hardly ever used, could you take the remainder of that and form a new data partition I think most people would want something closer to a repair than a phone with half jacked missing partitions.... I mean I for one wouldn't want any of my ram to be taken away and maybe cache is bigger than it needs to be, but it's there for a reason and makes things faster by not having to completely recall items.
 
rbheromax said:
thats what we're doing here
i did also make a recovery and ramdisk that took away cache, made cache into /data and moved cache to ram since we have 1gb of ram to play with.....there are alot of things we can do, we could even resize /data to be smaller than than the area where the corruption is.
Click to expand...
Glad u got it working... So do u end up making the SD ext?? Then just redirected data there??
 
I actually just thought of something... In my 360 moding days u had to reprogram the nand(emmc) sometimes u would get bad blocks on read so u had to remap them to different locations b4 write (usually to the end) is there a way to do this with android instead of redirecting entire partition??
 
brittnearl said:
I actually just thought of something... In my 360 moding days u had to reprogram the nand(emmc) sometimes u would get bad blocks on read so u had to remap them to different locations b4 write (usually to the end) is there a way to do this with android instead of redirecting entire partition??
Click to expand...
Here you'd have to do it through the kennel and I have the patches, I just don't have to disk space to compile atm. I'm running my Linux from 1 16gb USB setup with LLVM. I only have ~1.3gb after wine, my tools, and some apps. I'll be getting a 64gb class 10 SD to use for compiling. I refuse to get a HDD/sdd . I want portability

brittnearl said:
Glad u got it working... So do u end up making the SD ext?? Then just redirected data there??
Click to expand...
It sees mmcblk1p1 as data and p2 as sdcard thru fstab like its supposed to and mounts on boot
 
Well so far, I can still only boot up temporarily. Still trying to figure out a way to permanently install the custom kernel and recovery, along with trying to root the device/get superuser.

Towelroot seems to hang, i let it "rain" from 10am till 6pm, and it was still "raining". Flashing the super user zip also doesn't stick. I've had no luck with installing anything through side-load so far, even though it says "successful" installs but seem to not stick. Framaroot doesn't work, because it reboots the phone into the stock kernel and not the modified one that I need to use to access android. Cydia Impactor doesnt work, I get "signature bugs unavailable". SuperOneClick fails, it just flat out fails lol.

Other than that, being able to access the OS through the new kernel is great, and everything seems to be working, although a bit sluggish with my class 4 sdcard, but still very much usable.

It's almost solved, but not entirely just yet. Although it is usable, it's just not for practical use yet. Until I get a faster sdcard, and get the recovery, kernel, and superuser to install, it will still be a work in progress.

Out of absolute curiosity, would this even work on the ZTE AWE?
http://www.bestbuy.com/site/sandisk-ultra-128gb-microsdxc-class-10-memory-card/4471009.p?id=1219098340181&skuId=4471009&st=micro%20sd%20card&cp=20&lp=18
 
The stock kernel doesn't support card over 32gb but I can't build u one that does. (I love bigger cards like that anyways) It'll work just fine.
 
When you get the chance, get onto freenode, I've got Ubuntu 14 on virtual box, so maybe we can poke around a bit more using that.
 
It'll be later tonight. I got Ubuntu dual booting on my hackintosh right now, so I can build you that kernel for that SD. I'll also set it to have much more readahead to see if it'll speed u up a bit
 
I won't need the kernel for that sdcard haha. I was just wondering if it was possible. Although, I might be getting a class10 32GB or a 64GB sdcard in a couple weeks. Right now, I'm more focused on getting the current Kernel you made for me and the recovery to stick, along with gaining root access.
 
rbheromax said:
It'll be later tonight. I got Ubuntu dual booting on my hackintosh right now, so I can build you that kernel for that SD. I'll also set it to have much more readahead to see if it'll speed u up a bit
Click to expand...
I run 2048 internal and external ;) done through postboot
 
You must log in or register to reply here.
Back
Top Bottom