Database Info

Bricked MAXX, Need Help

Hello,
I have been crack flashing for a long time, but when I got the Droid Maxx from verizon I was disappointed at the lack of an unlocked bootloader. I had been running safestrap and was getting the phone ready to return for a refund so I can get the developer edition.
So, it looks like using safestrap I completely wiped the system partition. I can get the phone to boot to flashboot mode or to the safestrap flash screen but that is all.
Using RSDlite I attempted to flash 12.9.0, but get the return message "Failed flashing process. 2/17 flash partition "gpt.bin" -> Phone returned FAIL. On the phone it said:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT."
So it looks like the issue might be because I am flashing the FXZ file for 12.15.15, but I cannot find the FXZ file for it.
I also tried using House of Moto. Attached is a screen shot of what I get.
So basically it looks like I have no ROM whatsoever. Is there a way out of this so I can return the phone for a refund?
Thanks in advance!

I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?

kclantz said:
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
Click to expand...
Click to collapse
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.

ahjee said:
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
Click to expand...
Click to collapse
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.

rds217 said:
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
Click to expand...
Click to collapse
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing

So I just got back from the Verizon store, I went in to see if they could flash the files I need. They told me they couldn't but gave me a number at motorola to see if they would e-mail the files to me.
Unfortunately that didn't work. Motorola said I could send the phone in for a repair, and that was my only option.
I think I'll take the second option and wait until someone posts the files and flash them with RSD Lite.
I just hope that happens soon, as I am wanting to return the phone and get the developer edition. I have until Saturday to return it and I doubt they will give me a refund with it in this state.

ahjee said:
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
Click to expand...
Click to collapse
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
jcase said:
If you used 1.1 and have a problem with recovery coming back, run the following command:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse

rds217 said:
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
Click to expand...
Click to collapse
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.

kclantz said:
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
Click to expand...
Click to collapse
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk

erishasnobattery said:
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Thanks, that was what I was afraid of. I guess now I will check obsessively for the new FXZ files. Got have some way to spend my day (you know, as opposed to doing my job ).

[Q] Root for the One Plus One?

This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.

adambombz said:
This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.
Click to expand...
Click to collapse
It's not rooted out-of-the-box. Google doesn't allow this. But apparently, root will be very easy; just plug it into your computer and enter in a few command lines and you're set (so I've heard). Undoubtedly someone will make a one-click script that makes it even easier.

EDIT: Sorry for that one, was posting too fast without thinking first... Actually rooting includes unlocking bootloader and flashing the required binaries via recovery like said below my post.
Sent from my Desire X using XDA Premium 4 mobile app

dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Click to expand...
Click to collapse
Really? Sweet!

Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Naturally if you want to root the phone, it's only a quick USB cable plug into your computer and a few command line entries away.
Click to expand...
Click to collapse
Good read, BTW.
OnePlus One Review | Android Central

CafeKampuchia said:
Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Good read, BTW.
OnePlus One Review | Android Central
Click to expand...
Click to collapse
That's where I heard it. In any case, it'll be simple; that much was promised from the beginning.
What about SuperSU though? I'm honestly not sure how that gets installed to the right place; the only times I've rooted were with programs that did it for me.

I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk

dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Sent from my Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh really? Absolutely ridiculous.
tiny4579 said:
I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Correct - no retail device shipping with Google CTS/GMS can have root enabled, much less the ability to right OUT OF THE BOX. It has to be done manually by the user, at their discretion.

From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.

Chromium said:
From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.
Click to expand...
Click to collapse
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?

dmo580 said:
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?
Click to expand...
Click to collapse
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.

cyanogenmod has been planning to separate root for years. i think they are coming up with a simple method of root. maybe just an app install?

You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Cm I think opted to make root removal so they could get cts approval and install Google Apps.
Sent from my HTC One using Tapatalk

it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.

The Jack of Clubs said:
it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.
Click to expand...
Click to collapse
I wonder if they're using this recovery.
https://github.com/CyanogenMod/android_bootable_recovery-cm
Simple recovery is the working title.
You are correct that custom recoveries aren't always needed for root; however, in Android 4.3 and later, the two primary root applications need to install a superuser daemon which makes rooting outside of recovery more difficult.

tiny4579 said:
You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Click to expand...
Click to collapse
You all guys keep saying that rooting is trivial, but nobody told how to root. I believe you that it's trivial but - anyway -please tell me how to do this step by step.

I'm actually having trouble getting my 64GB production unit to boot into TWRP or have it flash and stick. fastboot says everything is fine, then rebooting into recovery produces the stock simple recovery.
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
I'm sort of at a loss - I've done this to many Nexus devices before, and the idea is the same. My bootloader is unlocked, that went without any issues.
Booting a debug boot.img from https://cyngn.com/products/oneplusone via fastboot just ends up shutting down and showing the battery charging icon.
Volume Up + Power while booting ends up with a black screen - in fact, the only way I can get into recovery is from a booted OS.
Edit: After many tries, trying different cables and unchecking the Settings -> Development -> update recovery with system updates, the TWRP flash succeeded, and the subsequent SuperSU sideload went just fine. Now I'm rooted.
Another tip regarding using Power+VolDn or Power+VolUp - things happen so slowly that if you keep holding Power, it'll actually trip a reboot before it has a chance to load. Just hold the Power button for a few seconds when booting, then let go and keep the VolUp or VolDn pressed.

Chromium said:
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.
Click to expand...
Click to collapse
I just did this and it seems to have worked. TiBu just completed..
Used "Fastboot boot TWRP-2.7.1.0.zip" at ADB/Fastboot interface. It booted to TWRP. As I closed, it stated that it looks like "Your device isn't rooted, Do you want to install SuperSU?" To which I said Yes. It rebooted and I was able to open SuperSU, already on the phone, and get root. Then, opened TiBU and performed a full backup.

Archon810 said:
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
Click to expand...
Click to collapse
The first time I did this it hung for a while. it eventually boots into the recovery. I think it took about 2 minutes for it to finally boot into it.
Maybe that helps?

Root One+ fastboot devices hnags "waiting for device"
I amd trying to unlock bootlaoder, and install TWRP on my ONE+. I have tried both android SDK, and TOOLKIT FOR ONEPLUS FROM XDA, and I cannot get fastboot devices to recognize my One+.
What I have do so far:
My PC: windows 7 - 64bit
Installed SDK kit form developer.android.com, and installed the latest composite usb driver from Google.
Installed OnePLus toolkit and tried using that, no dice.
when I execute "fastboot devices" from my fastboot folder, my prompt hangs "waiting for device" FOREVER!!!
"ADB DEVICES" WORKS PERFECTLY, AND ECHOES MY SERIAL NUMBER BACK TO ME."

[Q] How to root this device without deleting any data?

Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.

yes, of course..
root doesn't delete any of your data

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.

timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?

pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon

The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!

But how is anything going to be written to the system partition if it is locked ?

timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?

pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?

bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?

pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help

bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?

pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?

Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!

I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!

zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.

How I gained root and CWM recovery on my MT7-L09 with out bootloader unlock.

Let me start off by saying I'm new to the Huawei Ascend Mate 7 but I'm no newcomer to Android. I've been a member of XDA for some years now. Since before IceCream sandwich. I've done my far share to help out this community as it has helped me. I'm originally a themer, but lately been working on a few ROMs. Mostly tweaked based on stock, deodexed, zip aligned, debloated, and build prop mods.
My worth I bring to the table is I'm just BALLSY and experienced enough to try anything and flash just about anything. (With in reason of course). I seem to have acquired a unique talent to be able to unbrick every device that's been laid before me over the passed year or so as well as a few of my own. And have aided in the unbricking of several peoples device that have reached out to me on here.
So with this uncanny ability to be able to unbrick devices I took it upon myself to take a few stabs at gaining root and flashing CWM to my MT7-L09 without unlocking the boot loader. Due to reading post after post of people not getting replies from their emails to Huawei asking for an unlock code.
So now to the point......
I can in NO way take credit for this development nor do I take any responsibility for your actions or decisions to follow this guide unsuccessfully.
1. First I downloaded the 141 update with Supersu built in thats posted here in this forum and the Mate7.zip posted here as well.
Moved the 141 update with SU titled Update.zip to my sdcard/dload.
2. Went to settings/updater clocked MENU at the bottom, then selected LOCAL UPDATE.
3. After it completed (which took about 5 mins) I rebooted installed SuoerSu from the play store and SuperSu Pro. And opened to update binary.
4. Then used a Root Browser to locate the Mate7.zip that I downloaded earlier in the same forum. I then extracted its contents.
5. Download FLASHIFY from the play store. Grant SuperSU permission. And use FLASHIFY to flash the CWMRECOVERY.zip that was also in the Mate7.zip file that you extracted earlier.
6. And this is the most important thing. I don't know how many times I've seen people start modding and flashing then brick and ask for help only to realize "no I didn't make a backup". ALWAYS MAKE A BACKUP IMMEDIATELY AFTER INSTALLING A CUSTOM RECOVERY. If you don't then you have no one to blame but yourself when you can restore.
So as stated above I had no hand in developing any of this. Its just a method I used to gain root, update, and gain CWM recovery WITHOUT boot loader unlock.
And here's the copied text from URYLDOR's forum where I found all the essential pieces I used to gain all this. I did not unlock my boot loader though. This method nor any other would work for me so I took a shot in the dark at my method just to get root, CWM, and update as well.
ALL THANKS SHOULD BE GIVEN TO HIM FOR HIS DEVELOPMENT and if my method works for you then youre welcome to thank me for it and it alone but thank @Uryldor too.
...............................................................
Here is the translated guide to unlock bootloader on European model from the link I posted earlier.
I’m not responsible of any damage made to your device.
Download, unzip and run the Huawei product ID generator then select Huawei Y300-0000 in the product model field. Paste your IMEI in the product IMEI field and it should give you a product ID. We will use it later.
Go to http://en.club.vmall.com/emotiondownload.php?mod=unlock&action=apply tick the box at the end of the Unlocking Agreement and click next.
Here is what to choose/write in the form:
Product type: Smartphone
Product model: Huawei Y300-0000
Product SN: The SN of your Mate 7
Product IMEI/MEID: The IMEI of your Mate 7
Product ID: The number Product ID Generator gave you.
Enter the captcha and click submit.
Now it should give you your unlock code.
Download mate7.zip from https://mega.co.nz/#!aB8mRATA!nY7VJPUEESxBv5iRZ95vORbcjUQwLoyEyHagPi6RMGI and unzip it.
Install the driver if needed by running Driver\all\DriverSetup.exe
Copy SuperSU-PRO-V2.09.zip to your sd card.
Reboot your Mate in fastboot by holding Volume Down+Power for 10 seconds and plug it.
Unzip Recovery_b119.zip, go to tools, hold Shift and right click then choose “Open command windows here.
Type:
Now your bootloader is unlocked. Don’t close the command windows, now we will install the ClockWorkMod recovery.
In the window type:
You can flash recovery_stock.img with the same command if you want to revert back to the stock recovery.
Now go into recovery by holding Volume Up+Power for 10 seconds.
Then go to:
Install zip>choose zip from /storage/sdcard1> SuperSU-PRO-V2.09.zip and select yes.
Reboot.
Your Mate 7 is now unlocked and rooted!

Thanks you save my life and my mate 7... work fine here

Did you not have to flash using the force update method? I installed 141 via the local update method (came from 137) and SuperSU fails to update the binary.

ritdaw said:
Did you not have to flash using the force update method? I installed 141 via the local update method (came from 137) and SuperSU fails to update the binary.
Click to expand...
Click to collapse
Yeah but I downloaded the 141 update that has root built in. I then used "FLASHIFY" From the play store to flash the cwm.IMG. I then booted to CWM then flashed the SuperSU.zip that's mentioned in the above thread. Then made a back up in CWM. Rebooted and didn't have to update binary after all that.
Warning. Do not flash CM-11 if you used my method to root and install CWM. I did and now I'm soft bricked. I think it has something to do with the boot loader not being unlocked. I'm stuck at the "Rescue Mode" screen with the error
Error!
Func NO : 12 ( Func_load_iom3)
Error NO : 1
It took cm-11 OK. Just didn't ever boot fully so when I went to reflash the 141 update to restore it or my backup it acted like it took that fine but upon first boot back to stock I ended up stuck in "Rescue Mode" and getting the above code. ADB not recognizing it since its in "Rescue Mode" which is basically fast boot. Some fast boot commands work like Fastboot update ....... And fastboot reboot. But not " fastboot flash " does not. And that's where I think the boot loader being locked is preventing me from fast booting anything to it.
Any suggestions are appreciated.

Mmmmm... bad news men... I hope you can bring to life your Huawei mate again... I use you method and works fine... but I don't think flash any Rom... maybe you can try unlock your boot loader or use Huawei hi suite?

i was able to flash the 141 with supersu - but i wasn't able to update it, nor to flash anything with flashify because there are no root-rights - at least the phone still works
i successfully applied steps 1 and 2
3 downwards not usable (update supersu not working, even after reboot)
UPDATE: with the force update it worked

There is no cwmrecovery in the mate7 folder. Are you referring to the other recovery that isn't the stock one?

charlieb620 said:
There is no cwmrecovery in the mate7 folder. Are you referring to the other recovery that isn't the stock one?
Click to expand...
Click to collapse
Yeah it says its a modified version of stock. Its cwm. Even has the logo

Question??? I installed this Rom and everything works fine... but if I delete a system app (Google maps for example)... the app is gone but when the phone reboot the apps appears again??? I use a root browser to delete the app... which should be the problem??? I am the only whit this trouble??

Will this method also work when you;ve updated to lollipop? I cannot get the unlock code from huawei for my mate 7, and do want to root!

djzero86 said:
Question??? I installed this Rom and everything works fine... but if I delete a system app (Google maps for example)... the app is gone but when the phone reboot the apps appears again??? I use a root browser to delete the app... which should be the problem??? I am the only whit this trouble??
Click to expand...
Click to collapse
Its because you have to also go into data/app and delete it there, and data/data and delete it there too. Then wipe dalvik and cache. Reboot. Done.

mattwheat said:
Its because you have to also go into data/app and delete it there, and data/data and delete it there too. Then wipe dalvik and cache. Reboot. Done.
Click to expand...
Click to collapse
I will try....

On my ham 7 don't work... I tried doing that you say and can't delete the apps

mattwheat said:
Its because you have to also go into data/app and delete it there, and data/data and delete it there too. Then wipe dalvik and cache. Reboot. Done.
Click to expand...
Click to collapse
Well matt somes guys never learn like me.LOL I went and bought another Lg g flex. I still have My Mate 7 and mate 2 galaxy mega, note 3 , note 2 Did you see where Huawei may get the next Nexus line..

dekraan said:
Will this method also work when you;ve updated to lollipop? I cannot get the unlock code from huawei for my mate 7, and do want to root!
Click to expand...
Click to collapse
Yes, worked for me on 5.1
EDIT: !!DONT FLASH!! on 5.1, phone boots, i can get into recovery, but can't install anything
does anyone have stock recovery for B308 5.1??

Will unlock bootloader on this devices break up some features, as on Xperia devices (like DRM keys and so)?
Thank you!

your warranty, but as far as i can tell it doesn't break any features

KennyLG123 said:
Well matt somes guys never learn like me.LOL I went and bought another Lg g flex. I still have My Mate 7 and mate 2 galaxy mega, note 3 , note 2 Did you see where Huawei may get the next Nexus line..
Click to expand...
Click to collapse
Sorry just seeing this message. Yeah it was just released for pre sale yesterday. Huawei does in fact make the Nexus 6p and LG makes the 5x. I'm seriously considering getting the 6p....

Are you sure it works?
It works without unlock bootloader?
The 141, that the Russian guys, only the SuperSU app, but without the superuser binary, which will start during the boot process, it is not worth anything.
So much power could be any other rom.
The stock bootloader available in the boot process, and does not allow only the stock recovery.
Are you sure it works?

Nvidia Shield- How Can I Avoid The Kill Switch?

I have my old Nvidia shield tablet and i have WiFi off and powered off.
I've been reading you can stop the kill switch from i guess changing the boot loader or operating system?
I new to this stuff.
Could someone just give me some directions on how to go threw this process please.
I don't know if it's to late cause i have the most recent update? but like i said it's turned off and WiFi is off and i heard that the kill switch is sent over the internet to your device and you don't have to confirm it.
So i hope my system is safe until i can do what ever you guys advise me to do.
Thank you...

treat your old tablet before connecting the new one to internet
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)

If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.

I used my new tablet and the both were working for the day, both have no problems so far.
I've been reading that they are sending out kill switches in 4 segments, by using the last 2 digits of the serial numbers system.
So mine hasn't gone threw yet i don't think.
So i need to root it?
Then delete the OTA file?
Then flash a custom firmware?
Thanks guys...

Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.

Jarocks said:
If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.
Click to expand...
Click to collapse
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.

Snah001 said:
Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.
Click to expand...
Click to collapse
I see lots of root programs, is there a best one?
Can you flash with TWRP?
And someone said all i have to do is...
"Full Process
1) Unlock Bootloader.
2) Flash TWRP Recovery.
3) Get the no more OTA.zip from XDA and flash it via TWRP
4) Check if the update option is removed from Settings, if not flash it again.
Done! "
Is that ok also?
Thank you...

You need to root to flash twrp?

EowynCarter said:
You need to root to flash twrp?
Click to expand...
Click to collapse
No, but you do need an unlocked bootloader to fastboot flash anything.

amartolos said:
No, but you do need an unlocked bootloader to fastboot flash anything.
Click to expand...
Click to collapse
Yeah, that the conclusion i reached.
Flash done, now runing bliss pop. First start got me loads of errors. I went until i realized i had forgotten to wipe. It's been a while since i last played with custom roms.

oliwek said:
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.
Click to expand...
Click to collapse
Well, that's disappointing

oleg77 said:
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)
Click to expand...
Click to collapse
Ok i followed the http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
I got to "On the tablet, select "recovery reboot"
But i didn't see it so i selected reboot, i rebooted and was on stock i think?
1) I can see that a few more steps and i'm rooted.
But i'm nervous to try this again from that point.
Should i just start at unlocking the boot loader?
2) Is rooting the device permanently unlocking the boot loader?
3) can i just no OTA from unlocking the boot loader part?

Ok i got to side loader and in the command it says error can't find device and there's an android guy on his back with a red statement mark.
So I'm in developer USB.
I have unlocked the boot loader
I'm flashing the recovery
And i get to restart in recovery.
Then i get the menus to side load the supersu.zip
I renamed it with out caps, i even made a folder in C:\Program Files\Minimal ADB and Fastboot.
Cause it installed at C:\Program Files (x86)\Minimal ADB and Fastboot.
just to avoid the (x86)
when i try and leave the menu to reset it asked me to root, but i had the error so don't want to brick it if rooting with an error on side loading supersu.zip
What do i do?
Thank you...

says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.

l337g0g0 said:
says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.
Click to expand...
Click to collapse
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk

frenziedfemale said:
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I don't have an SD card ATM. LOL
Why is the command with ADB not working?

l337g0g0 said:
I don't have an SD card ATM. LOL
Why is the command with ADB not working?
Click to expand...
Click to collapse
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.

frenziedfemale said:
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.
Click to expand...
Click to collapse
Ok that installed it.
WOW thank for that.
I guess I'm rooted, how do i test it and what does being rooted do for me?
Thank you....

Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk

frenziedfemale said:
Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok i just flashed nomoreOTA.zip.
It said the file was deleted and was a success.
I guess i can use the internet now?
I'm so nervous to turn the internet on and have the thing reset...
Did i need to run supersu to keep it rooted or always rooted until i use supersu to full unroot.
Thank you...