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

Root [FIX]Soft Brick One Click Fix

You need some Rom, in the form of a zip file. You can download it from your phones forums. However I'm not entirely sure how you would've flashed a recovery unknowingly and not known what you were doing it for.
 
Blah..... Well RB, anyway you could just hook it up with the steps and commands on here? I can't get access to a computer again anytime soon to get on IRC and all. I'm just wanting to know what you have in mind. I'm thinking maybe If I would've done phenoms thing and added just a couple extra steps, maybe it would've worked. I was looking at a forum on xda, that had the same type of mkfs.ext4 push going on. However at the end, they formated and mounted /data through a shell. I didn't, I rebooted recovery and then tried to mount and format data, like phenom told me to. I super trust that phenom knows what he's doing, but maybe it would've helped to do those extra steps.... Who knows :confused:
 
DsyMnapTic said:
Blah..... Well RB, anyway you could just hook it up with the steps and commands on here? I can't get access to a computer again anytime soon to get on IRC and all. I'm just wanting to know what you have in mind. I'm thinking maybe If I would've done phenoms thing and added just a couple extra steps, maybe it would've worked. I was looking at a forum on xda, that had the same type of mkfs.ext4 push going on. However at the end, they formated and mounted /data through a shell. I didn't, I rebooted recovery and then tried to mount and format data, like phenom told me to. I super trust that phenom knows what he's doing, but maybe it would've helped to do those extra steps.... Who knows :confused:
Click to expand...

I hope you get your phone back in working order soon. I'm still looking for possible fixes but I'm starting to get stuck in a loop of the same search results and forum pages. It would be nice if there were a piece of software like odin for the zte. I wish I were of more help to you too.
 
That's alright man, I just really appreciate your efforts. The only thing I can think of is to do what phenom told me, again and just try to add the extra steps of mounting data through adb shell. As of always though, I need to wait for access to a computer.
 
Hello everyone I am very new to this area of computing (and this forum). However I have still ended up in a similar hole as you guys are describing the solution for although it happened for a completely different reason. (BTW: I am rooted)

one day I tryed to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' error. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).

if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.
 
Can you post your recovery log? I believe it's under advance and will copy it to your SD card. Also are you running the latest twrp? Also try the steps above to get a logcat and post it here as well.
 
Thanks for the reply DarkSky.

I will load my log shortly. Allow me to give a brief background on what I'm doing.

TWRP v2.6.3.0 recovery installed. I can access at any time. My goal is to revert to stock so I can activate. (I have multiple awe's for family and only did one backup so noob me cannot use this route)

I am attempting to install the update.zip from ZTE to revert to stock.("unable to open zip file") I do notice that it says you must be using CWM for this. I have attempted to flash the CWM.zip from TWRP and I get the same message "unable to open zip file". I have tried the ADB commands for bootloader. Once I get it to the bootloader(black screen) and input the fastboot boot command in the cmd prompt, it errors out saying "not recognized as an internal or external command..."

I am able to flash the latest CM Rom in TWRP and runs fine. Anything else I try to flash (.zip) I get the "unable to open zip file" error.

One of the Awe's was dropping calls immediately upon call connecting. I figured I would revert to stock, re-activate, and then try installing the CM Rom again thinking something might have gone wrong the first time around.

I'm working on the log as we speak. Any help is always greatly appreciated.
 
It appears that maybe your zip files are corrupted. Try to see what it says with zip verification on and off. Also see if you can open and test the zips on a pc. Also try to verify the md5's. I am not a developer so I am not sure if this will help you but it's worth looking into as your log mentions having a problem opening the zip. There is an updated twrp that was posted today. Give it a try.
 
You hit it on the head Dark! Thanks for looking this over.

I read a similar post off yonder where someone had corrupted zips. For some reason when I copy straight from pc to sd card(installed in phone and used as MTP device), and properly "safely removing hardware" and unmounting, it still corrupted the zips. First time this has happened and not sure the cause but I learned a hard lesson here.

I'm back to stock finally! Thanks to everyone for their contributions. Phenom, Dark, Brittnearl, Mod, and everyone else. You make this as easy as it possibly could be! Now if I would just think outside the box for a minute and realize my zips are corrupt!

Now let me see if I can remove that log. :smokingsomb:
 
Hi guys,

I've got what I believe to be a soft bricked ZTE Awe, so you can imagine how happy I was to find this thread. But I'm sort of stumbling around in the dark in these forums, as I just learned about rooting 2 weeks ago (KingoRoot worked well). When I download the files that edodson84 posted, I open a terminal in that window and just type 'brickfix.bat' without the quotes.
This is what I see in the terminal window:
**Awe Soft Brick Fix**
error: closed
Rebooting to TWRP Recovery...
< waiting for device >
http://androidforums.com/members/edodson84.1666880/
If I type 'adb devices' I see:
adb server is out of date. killilng ...
*daemon started successfully *
List of devices attached
[bunch of numbers] sideload

I had been trying to install this ROM. In following those directions I typed 'adb sideload awe.zip' without quotes and I see:
Finding update package ...
Opening update package ...
Verifying update package ...
Installation aborted.

Since I'm not able to get into my phone's settings, I think the USB debugging could be one of my problems. Any help very much appreciated!
 
edodson84 said:
Can u access recovery?? Is it stock recovery??
Click to expand...

I can access the "Android system recovery <3e>"

I'm not sure if it's stock. Besides rooting, I had not successfully changed my ROM (if that's the right way to say it). It was in the process of trying to install the ROM I linked to above that I had this issue.

Thanks in advance for any thoughts!
 
edodson84 said:
@Brian85 all u have to do is fastboot twrp then flash ur desired recovery/rom... U cant sideload in 3e recovery due to signatures being checked
Click to expand...

It seems like my device is not recognized unless I press the option 'apply update from ADB'. My understanding is that to get to fastboot mode, I'd type 'adb reboot bootloader' without quotes. When I do that, I see an error message: 'error: device not found'. :(
 
You must log in or register to reply here.
Back
Top Bottom