I've already asked this question before but I haven't gotten any progress, but did note some things.

First the problem again.

I soft bricked my phone by editing a line in build.prop, specifically this one.




My phone didn't like that apparantly. It supposedly fixes the xposed framework limited mode bug...

Now, I can boot into recovery and restore my phone to factory reset, but as you can imagine this is not something I'm very willing to do... Unless everything else fails... In recovery I'm unable to use ADB to connect to my phone, I can wipe things, reset and apply patches, but that's it.

Now, if I boot my phone and it gets stuck in the boot animation I can suddenly use adb fine. Hurray right? Just restore build.prop.bak...

Yeah, not. Nothing works.

chmod 777 build.prop -> Read-only

su chmod 777 build.prop -> nothing happens

su mv build.prop build.prop.back -> nothing happens

su -> nothing happens

su -s -> chainfire information ( from SuperSU )

mount -o remount,rw /system /system -> not permitted

su mount -o remount,rw /system /system -> nothing happens

All these commands were run in /system

Can someone help me out with this? I don't want to have to use my last resort...

I don't really think it matters, but it's a Huawei G700 running 4.2.1

So, what's changed?

Well, if I boot normally the phone functions fine in the background as if I didn't enter a pincode. It requests an ip-address from my router and connects fine, but as you can imagine something like web.watsapp won't work.

Volume Down + Power boots into... Fastboot? Well, kinda, not really. It just says two things



What I found on google isn't much and it isn't promising. No solutions.

When I boot the device fastboot does detect the device as a mt6589 with the boot image being secure.

SPFlasher does not work, it fails to detect my device in any mode and will not flash anything.

I tried updating from recovery with a zip file but everything fails. After some googling it appears to be likely that the zip file has to be signed by Huawei themselves, dang.

I tried installing adbd insecure v2 from Chainfire, but I have NO idea how to enable this from adb. I can't enable this the normal way.

So, here's what I thought. Can't I call the huawei theme manually from the adb shell? For that I need someone else who can check this.

If that doesn't work, do you guys have any other ideas?

If none of those work I could ask for an OEM key and flash another recovery but that seems like a terrible idea as I have no gui.

Then there are three things left, sending it to huawei / dropping it at a local repair shack, neither appeal as they are costly and mean I'll lose my phone for a while.

Or, and that's the thing I really don't want to, buy another phone. I'm content with the phone itself, curiosity merely killed it.

Just hit me up if I'm not allowed to do this. Just tell me to get a new one at least. I need some guidance here.

Big edit, I think I can't edit it because it's in use, not because I lack access as can be seen here http://i.snag.gy/FiFdQ.jpg

Cheered too early. http://i.snag.gy/ORxQJ.jpg

  • 1
    You will first need to mount /system in read-write mode, and then it's /system/build.prop you need to deal with. A factory-reset wouldn't help you anyway (doesn't touch /system).
    – Izzy
    Dec 16 '15 at 6:10
  • The problem is I can't, nothing works.
    – Nos
    Dec 16 '15 at 6:58
  • @Nos Do you have USB debugging turned on before this happened?
    – Aloha
    Dec 16 '15 at 8:07
  • Yes, it's on and working.
    – Nos
    Dec 16 '15 at 8:50
  • 1
    @Nos not even in recovery (which I was talking of)? Or can you do that via adb shell (first su, then mount -o remount,rw /system, then modify the build.prop)?
    – Izzy
    Dec 16 '15 at 12:44

Browse other questions tagged or ask your own question.