Database Info

(soft)bricked my device. Is there a fix?

Hi all,
I installed the TWRP recovery for my mate 7 - 09 version, with lollipop 5.1. But then I unknowingly wiped something I shouldn't have: I think it was the system folder. No backups were made
My phone keeps starting up to the huawei logo and then reboots\turns off. I can get into fastboot&rescue mode, but that's it. No recovery, no 3-button fix (as far as I know).
The second problem is that I cannot get my device to be recognised by my pc. adb devices doesn't give me any results.
I don't feel like I can install the drivers properly as well. Pherhaps thats the problem? How can I do this? I have a driversetup from a mate7 download, but double clicking it doesnt show any prompts.
Anyone who can help me in any way is more than welcome!

dekraan said:
Hi all,
I installed the TWRP recovery for my mate 7 - 09 version, with lollipop 5.1. But then I unknowingly wiped something I shouldn't have: I think it was the system folder. No backups were made
My phone keeps starting up to the huawei logo and then reboots\turns off. I can get into fastboot&rescue mode, but that's it. No recovery, no 3-button fix (as far as I know).
The second problem is that I cannot get my device to be recognised by my pc. adb devices doesn't give me any results.
I don't feel like I can install the drivers properly as well. Pherhaps thats the problem? How can I do this? I have a driversetup from a mate7 download, but double clicking it doesnt show any prompts.
Anyone who can help me in any way is more than welcome!
Click to expand...
Click to collapse
Hey Buddy, here's what you can try to do:
1.) Boot connect your phone to your computer.
2.) Next, boot your phone to fastboot.
3.) Next, open command prompt from the folder where your ADB files are stored.
4.)On CMD type:
fastboot devices
5.) If your device appears then you have 2 options now. You can either:
a.) Flash Stock recovery.img or
b.) Flash back TWRP
6.) If choosing option a.) you can then save stock firmware within dload folder on your external sd card then force upgrade via 3 btn method.
7.) If choosing option b.) you can boot to twrp then either sideload a custom rom or try to save on your external sd and flash

blitzkriegger said:
Hey Buddy, here's what you can try to do:
1.) Boot connect your phone to your computer.
2.) Next, boot your phone to fastboot.
3.) Next, open command prompt from the folder where your ADB files are stored.
4.)On CMD type:
fastboot devices
5.) If your device appears then you have 2 options now. You can either:
a.) Flash Stock recovery.img or
b.) Flash back TWRP
6.) If choosing option a.) you can then save stock firmware within dload folder on your external sd card then force upgrade via 3 btn method.
7.) If choosing option b.) you can boot to twrp then either sideload a custom rom or try to save on your external sd and flash
Click to expand...
Click to collapse
I'll give that a try, thank you. With step 1, you just mean: connect the phone through usb to the computer, right?
When I rooted the phone, I did so on my work laptop, so I am hoping I can get it recognised there, but lets see what happens at home.
EDIT:
Ok, i've typed in fastboot devices, and it gave me one line with a 16-digit code (numbers and letters) some white space and then the word fastboot. What does that mean?

That should meen it recognizes your phone in fastboot mode. Next step is to flash as stated in step 5 that in the instructions.
Sent from my HUAWEI MT7-L09 using Tapatalk

dekraan said:
I'll give that a try, thank you. With step 1, you just mean: connect the phone through usb to the computer, right?
When I rooted the phone, I did so on my work laptop, so I am hoping I can get it recognised there, but lets see what happens at home.
EDIT:
Ok, i've typed in fastboot devices, and it gave me one line with a 16-digit code (numbers and letters) some white space and then the word fastboot. What does that mean?
Click to expand...
Click to collapse
EDIT AGAIN:
Ok, this is what I did. I downloaded the well known mate7 package, extracted the b119 tools folder and I put the twrp_2.8.7.0_mate7_5.1.img file from this forum (the TWRP for 5.1) inside this folder.
Then, I open cmd inside the folder, and I typed: fastboot flash recovery twrp_2.8.7.0_mate7_5.1.img. This is what happens:
target reported max download size of 471859200 bytes
sending 'recovery'(12644 KB)...
OKAY [ 1.302s]
writing 'recovery'...
OKAY [ 0.455s]
finished. total time: 1.756s
Now, I finally managed to get back into TWRP! I've only got 2% battery though (but I see a + which I think means charging...EDIT: yes, it is on 3% now. Better leave it like this...).
It tells me this:
TWRP has detected an unmodified system partition.
TWRP can leave your system partition unmodified to make it easier for you to take official updates. TWRP will be unable to prevent the stock rom from replacing TWRP and will not offer to root your device. Installing zips or performing adb operations may still modify the system partition.
I decided to swipe, to allow modifications.
So, I've got twrp back! For lollipop. This probably means I have to flash the lollipop rom? I will download the update.zip file next and put it on my sd card (using my pc and a microsd adapter...)
Keep you posted!

Ok, this is not working.
I put update.zip on my sd-card, and tried to install it. This is what I get:
Installing 'sd-ext/update.zip'...
checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:unknown command [errno]
file_getprop: failed to stat
E: error executing updater binary in zup 'sd-ext/update.zip'
Error flashing zip 'sd-ext/update.zip'...
Updating partition details...
...done
EDIT:
I tried to sideload but on my pc I get:
error: protocol fault (no status)
And on my TWRP I get:
You need adb 1.0.32 or newer to sideload to this device.
EDIT:
Updated my adb to 1.0.32 for windows, and rebooted everything. Now i'm at 6% of sideload. Hoping this will work!
EDITn the PC everything seems to go ok, but on my phone it says: E:Zip signature verification failed:1
What should I try next?

dekraan said:
Ok, this is not working.
I put update.zip on my sd-card, and tried to install it. This is what I get:
Installing 'sd-ext/update.zip'...
checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:unknown command [errno]
file_getprop: failed to stat
E: error executing updater binary in zup 'sd-ext/update.zip'
Error flashing zip 'sd-ext/update.zip'...
Updating partition details...
...done
EDIT:
I tried to sideload but on my pc I get:
error: protocol fault (no status)
And on my TWRP I get:
You need adb 1.0.32 or newer to sideload to this device.
EDIT:
Updated my adb to 1.0.32 for windows, and rebooted everything. Now i'm at 6% of sideload. Hoping this will work!
EDITn the PC everything seems to go ok, but on my phone it says: E:Zip signature verification failed:1
What should I try next?
Click to expand...
Click to collapse
I don't advise you to flash lollipop firmware first. It's more prudent to go back to kitkat first as I believe Lollipop needs kitkat as base
1.) Put stock kitkat update.app on dload folder of your memory card. Also make sure you have the LO9 stock kitkat recovery.
2.) With your phone connected to pc, go to twrp and reboot to bootloader.
3.) Once on bootloader open cmd on your tools folder then fastboot flash the stock kitkat recovery.
4.) Once done, fastboot reboot then force upgrade to install stock firmware.
5.) Once you have stock kitkat follow the drill to reach lollipop

blitzkriegger said:
I don't advise you to flash lollipop firmware first. It's more prudent to go back to kitkat first as I believe Lollipop needs kitkat as base
1.) Put stock kitkat update.app on dload folder of your memory card. Also make sure you have the LO9 stock kitkat recovery.
2.) With your phone connected to pc, go to twrp and reboot to bootloader.
3.) Once on bootloader open cmd on your tools folder then fastboot flash the stock kitkat recovery.
4.) Once done, fastboot reboot then force upgrade to install stock firmware.
5.) Once you have stock kitkat follow the drill to reach lollipop
Click to expand...
Click to collapse
Hi, thank you for your advice. I have but one question remaining: what stock kitkat update should I use? And where can I find the right recovery that goes with it?
I've tried several recovery_stock.img I found, and it does take away TWRP, so it might have done the trick. Only problem is that I cannot force upgrade to install whats on my sd-card....The phone keeps turning on (after a long push) and after seeing the logo for a little while, it turns off (short vibration)... Is there another way?

dekraan said:
Hi, thank you for your advice. I have but one question remaining: what stock kitkat update should I use? And where can I find the right recovery that goes with it?
I've tried several recovery_stock.img I found, and it does take away TWRP, so it might have done the trick. Only problem is that I cannot force upgrade to install whats on my sd-card....The phone keeps turning on (after a long push) and after seeing the logo for a little while, it turns off (short vibration)... Is there another way?
Click to expand...
Click to collapse
You should flash B137SP03 firmware. You can also refer to this guide:
http://forum.xda-developers.com/mate-7/help/5-1-to-4-4-2-bootloop-t3132888
1.)Prepare the Stock B137SP03 firmware on your SD card
2.)Download the fastboot.zip guide and extract it to a separate folder.
3.) next connect your phone to your computer and go to fastboot mode.
4.) Flash the boot.img and recovery.img you find on that guide.
5.) Once done, do the force upgrade with the B137 firmware.

blitzkriegger said:
You should flash B137SP03 firmware. You can also refer to this guide:
http://forum.xda-developers.com/mate-7/help/5-1-to-4-4-2-bootloop-t3132888
1.)Prepare the Stock B137SP03 firmware on your SD card
2.)Download the fastboot.zip guide and extract it to a separate folder.
3.) next connect your phone to your computer and go to fastboot mode.
4.) Flash the boot.img and recovery.img you find on that guide.
5.) Once done, do the force upgrade with the B137 firmware.
Click to expand...
Click to collapse
I've followed the guide you are reffering to. And I flashed the boot and recovery, and managed to get the roll back force installed. But for the life of me, I cannot get my phone to force install the B137 zip. I just can't get into force install mode. Are there tips or tricks? I am holding power up and down, and then press power untill I feel a short vibration. But all it does it show me the huawei logo screen and then shuts down again.
Very frustrating!
EDIT:
ok, I noticed that when my sd-card is not inserted, the phone easily boots into the force install mode. It shows the logo for a couple of seconds, screen goes black and then the force install loads. So this is what I did: insert the sd card half way, press vol up and down, and power on. Then after the logo when the screen goes black, insert the sd-card all the way and when the phone goes to force install mode, it can find the update!
Now installing.... hope this helps someone else out there!

Worked! And I am up and running again! Thank you for saving my mate

I got my Mate bricked and i've been trying to figure out how to solve it. I tried lots of things from different guides, but just an hour ago I found this guide and it worked! I can't tell you how happy I am right now, thanks guys!

aleksik said:
I got my Mate bricked and i've been trying to figure out how to solve it. I tried lots of things from different guides, but just an hour ago I found this guide and it worked! I can't tell you how happy I am right now, thanks guys!
Click to expand...
Click to collapse
Glad to hear both of you guys have your mates up and running again. As long as a phone turns on and is not dead as a brick there's always hope it can be restored

Hi everyone, I have the same problem with my mate 7, i was messing with unlocking bootloader(which I succesfully have done), couldn't get my phone rooted so installed TWRP recovery for Lollipop(which was already installed when i bought the phone). Ended up with soft bricked phone(no OS, no recovery at all).
I tried different tutorials how to fix it, none of them worked(including that one unfortunatelly).
I have taken some pictures to show you what the problem is but cannot post them until reach 10 posts on forum
Basically, i can get into fastboot mode by holding volume down with power button. Windows and Hisuite don't recognise my device but in fastboot mode i can check devices connected. Typing "fastboot devices" i get "P6Q7M14A15008421 fastboot", which i guess is my device indeed.
After that i try flashing boot.img and recovery.img(which are reported OK). Then rebooting with 3 button(vol up and down, power) and Huawei logo screen appears for a bit and goes into white screen saying "rescue mode" and at the bottom: "Error Func NO: 10(FUNC_BOOT_RECOVERY) Error NO:2". Trying rebooting into recovery mode(vol up and power) it shows similar "recovery mode" screen but with different errors: "Error! Func NO:12(FUNC_LOAD_IOM3) Error NO:1".
That's it! It seems like i cannot flash my device successfully for some reason. What Windows version did you guys use?? I tried Win 8.0 and Win 10, maybe i should use older systems? Please help, i had my phone for a week only and broke it(

I can't help you much because I don't have enough knowledge about these kind of things.. I use Windows 7 and from my previous experiences I can say that working with Windows 8 can be frustrating. PS. I bricked my Mate 12hrs after buying it

muzammil84 said:
Hi everyone, I have the same problem with my mate 7, i was messing with unlocking bootloader(which I succesfully have done), couldn't get my phone rooted so installed TWRP recovery for Lollipop(which was already installed when i bought the phone). Ended up with soft bricked phone(no OS, no recovery at all).
I tried different tutorials how to fix it, none of them worked(including that one unfortunatelly).
I have taken some pictures to show you what the problem is but cannot post them until reach 10 posts on forum
Basically, i can get into fastboot mode by holding volume down with power button. Windows and Hisuite don't recognise my device but in fastboot mode i can check devices connected. Typing "fastboot devices" i get "P6Q7M14A15008421 fastboot", which i guess is my device indeed.
After that i try flashing boot.img and recovery.img(which are reported OK). Then rebooting with 3 button(vol up and down, power) and Huawei logo screen appears for a bit and goes into white screen saying "rescue mode" and at the bottom: "Error Func NO: 10(FUNC_BOOT_RECOVERY) Error NO:2". Trying rebooting into recovery mode(vol up and power) it shows similar "recovery mode" screen but with different errors: "Error! Func NO:12(FUNC_LOAD_IOM3) Error NO:1".
That's it! It seems like i cannot flash my device successfully for some reason. What Windows version did you guys use?? I tried Win 8.0 and Win 10, maybe i should use older systems? Please help, i had my phone for a week only and broke it(
Click to expand...
Click to collapse
Sounds like the wrong boot.img or recovery.img has been flashed. May I know what Mate 7 model you have and which Lollipop firmwre version your phone came last with?
Try to obtain boot.img and revoery.img for your lollipop version then flash that via fastboot

blitzkriegger said:
Sounds like the wrong boot.img -recovery.img has been flashed. May I know what Mate 7 model you have and which Lollipop firmwre version your phone came last with?
Try to obtain boot.img and revoery.img for your lollipop version then flash that via fastboot
Click to expand...
Click to collapse
My phone mt7-09l, european version 16gb. Came with lollipop 5.1 when I bought it but I think I have formatted it via twrp recovery so it shouldn't matter what boot and recovery version I am trying to flash, should it? I'll extract boot and recovery from b308 today andtry that, see if this works. If not, only thing I can try is using win7 and that's it really, no more possibilities

dekraan said:
I've followed the guide you are reffering to. And I flashed the boot and recovery, and managed to get the roll back force installed. But for the life of me, I cannot get my phone to force install the B137 zip. I just can't get into force install mode. Are there tips or tricks? I am holding power up and down, and then press power untill I feel a short vibration. But all it does it show me the huawei logo screen and then shuts down again.
Very frustrating!
EDIT:
ok, I noticed that when my sd-card is not inserted, the phone easily boots into the force install mode. It shows the logo for a couple of seconds, screen goes black and then the force install loads. So this is what I did: insert the sd card half way, press vol up and down, and power on. Then after the logo when the screen goes black, insert the sd-card all the way and when the phone goes to force install mode, it can find the update!
Now installing.... hope this helps someone else out there!
Click to expand...
Click to collapse
I'm stuck on this stage, no errors while flashing but no boot either. Shows logo then like a spark a bit of music and animation (1 sec maybe) and reboot, so on and on and on...

muzammil84 said:
My phone mt7-09l, european version 16gb. Came with lollipop 5.1 when I bought it but I think I have formatted it via twrp recovery so it shouldn't matter what boot and recovery version I am trying to flash, should it? I'll extract boot and recovery from b308 today andtry that, see if this works. If not, only thing I can try is using win7 and that's it really, no more possibilities
Click to expand...
Click to collapse
If you were on Lollipop when everything went sour, you should do what I did, thanks to advice from @blitzkriegger:
You should flash B137SP03 firmware. You can also refer to this guide:
http://forum.xda-developers.com/mate...tloop-t3132888
1.)Prepare the Stock B137SP03 firmware on your SD card
2.)Download the fastboot.zip guide and extract it to a separate folder.
3.) next connect your phone to your computer and go to fastboot mode.
4.) Flash the boot.img and recovery.img you find on that guide.
5.) Once done, do the force upgrade with the B137 firmware.
I used the full steps from the link in there: flashed the right boot and recovery through fastboot. Then I flashed the rollback zip from my sd-card, and then I flashed the B137 zip from my sd-card. I can't tell you more about it, obviously

brack11 said:
I'm stuck on this stage, no errors while flashing but no boot either. Shows logo then like a spark a bit of music and animation (1 sec maybe) and reboot, so on and on and on...
Click to expand...
Click to collapse
Been there, done that. Very frustrating! I've tried several things, none of which are probably the right way, but they worked for me. sometimes....
Can you get into stock recovery (vol+ and power)? What I tried several times was wipe cache, and then hold the powerbutton untill my phone turned off. That worked occasionally to get the device totally turned off. Then try to get to force update with your sd-card half way in, and flip it in totally when the logo dissapears and the screen is black. I also tried to shut down the constant starting up by going into fastboot/recovery mode and then holding power down. As long as it takes. Good luck! And hopefully someone can give you proper advice...

New replacement tablet stopped working properly! Help!

So after I got my new tabby, I proceeded to update it to 3.1. When it finished downloading, the tablet froze and rebooted, but the screen did not come back on! Literately, the pixels were not on (tested by going into a dark room and seeing if the pixels were on but colored black)
So I held power for 15 secs, rebooted, updated, and all that. Then, I decided to root using Kingroot. The first 3 times, it failed. It stopped at around 17-21%. The fourth time it just...worked. Then, shortly after replacing it's root with supersu using the kingroot replacement app, I went to DL titanium backup so I could restore stuff.
Then, out of nowhere, the tablet reboots, and shows the nvidia boot screen like normal.... But it was frozen. The tablet will NOT get past this screen! I tried going into the bootloader using VOL Down + Power, which works! I then tried "fastboot protocol", but when I select it, it just goes black, then takes me back to the bootloader!
I then tried recovery, but I forgot to install twrp, so all it shows is "No command" underneath a android! Help! I don't know what to do!
I did not enable usb debugging in dev options either, because I did not think to do that first when getting a brand freaking new tablet that should not be doing this!!!
My old one works! (Albeit with unstable audio glitches and general lagginess)

I would try to flash all new from recovery images (via fastboot, you can download from Nvidia page), then flash latest TWRP (MultiROM patched, if you prefer....) and from TWRP flash latest SuperSU.zip...

Lynco said:
I then tried "fastboot protocol", but when I select it, it just goes black, then takes me back to the bootloader!
Click to expand...
Click to collapse
that's what is supposed to happen

@BitOBSessiOn @Bogdacutu
But how would I flash via fastboot? What tool should I use?
I completely forgot how to do all of that stuff.

Lynco said:
@BitOBSessiOn @Bogdacutu
But how would I flash via fastboot? What tool should I use?
I completely forgot how to do all of that stuff.
Click to expand...
Click to collapse
First step: If you have downloaded recovery image, and unpacked everything, you get a script named "flash-all.sh" (for linux, flash-all.bat for win), execute it while in fastboot mode and connected to PC...

Lynco said:
@BitOBSessiOn @Bogdacutu
But how would I flash via fastboot? What tool should I use?
I completely forgot how to do all of that stuff.
Click to expand...
Click to collapse
Are you running linux or windows? Either way you'll need to get fastboot and adb. Download twrp and put the img file in the same directory as the fastboot and adb files. Put the tablet in bootloader mode. In a terminal window run fastboot flash recovery recovery.img (or whatever the filename for your twrp file you downloaded is). After it's done, run 'fastboot reboot-bootloader' and then go into recovery. From there you can either sideload a rom zip file or use adb to push it over to the tablet and then flash it. If you want stock, just download and flash a zip from the stock rom thread. Or if you want 100% stock, just flash the factory images from bootloader as described here

Flashed stock recovery and thought I soft bricked my shield tablet.

First I'll give credit where it is due. From two threads on this site is where I got help with this issue:
I followed THIS guys steps for manually erasing and got the recovery images and lots of other useful information from HERE. Thank you guys very much!
OK, so, hopefully I can help someone with my little story as well. I was having issues with apps and programs crashing on me with lollipop and the new marshmallow update. The tablet just wasn't working properly and moving slow. I even had the SD card holding all my apps and larger files so I didn't overload the internal storage. So, I decided I wanted to flash back to factory/stock recovery and go from there. I did this using THIS method. I flashed via the "flash-all.bat" file (the command in fastboot is the same as the file name). I should note that there was one instance that failed during the install (I did try it again and got the same failure). Said something about “did you mean you wanted to flash this partition” or something, then showed it failed. After flashing I hit continue on the bootloader screen of the tablet and it said it was "cold booting." After about 5 minutes or so it started to boot but never made it past the NVidia screen. I tried wiping the phone with factory reset, wiping the cache, etc. and then re-flashing the recovery (again with the .bat file). I tried flashing TWRP but it didn't install apparently, because it still went to factory recovery. I even re-locked and then unlocked my bootloader to see if that would set everything straight. Nothing seemed to work. I knew I would eventually find a solution though so I kept looking. Stumbled on some other people that had the same issues but no solution (hope those people got it figured out). So here's what I did after some more research:
First, if you're in this situation and you did factory reset to try and resolve the problem, you may feel like you can no longer communicate with the device via fastboot/adb, but as long as you have the usb drive and your SDK tools installed (I used CodeWorks for Android all-in-one program) that shouldn't be a problem. You'll just have to be in the bootloader on the tablet.
-If for some reason you deleted or uninstalled your drivers and tools you'll have to download them again and then, the computer should still be able to communicate with the tablet. In the device manager under portable devices it will still show up as Module something or other. So the computer still sees the device but doesn't fully recognize it yet. Don't worry, this should still work! Just make sure you that fastboot is seeing the device by inputting "fastboot devices" in the command window and a 14 digit serial number should pop up. If it just says "list of devices" or there's nothing then you wont be communicating with the tablet.
Your device should be connected to your computer and started in bootloader mode. On your computer you should have the command prompt for adb/fastboot open. I just go to the folder where the .exe files are located and hold shift and right click in the white space of the folder, then select "open command window here."
From here follow the erase steps: stolen from manigault! :highfive:
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase recovery
fastboot erase cache
Then flash your recovery MANUALLY:
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
You can download whatever recovery version you wish. I downloaded 2.2.2 because that's what my device came with out of the box on Christmas 2014. It will more then likely be a .zip file. To make this whole process a little easier simply extract the files in the .zip file where the adb.exe and fastboot.exe files are located (folder should be named platform-tools) and you can completely eliminate typing the whole directory before the file name. ***After your done flashing everything you can go back and delete those files if you want. Just double check that you're deleting the right files by looking at the original zip file. Not sure if it makes a difference but I deleted them anyway.
For example the commands in fastboot will look like this exactly :
(after extracting recovery files into platform-tools folder)
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Note: Do NOT use the flash-all.bat command as this doesn't seem to work for this situation. Do it manually like shown above. And let each individual process complete before attempting to input another command.
After this step I didn't select continue on the bootloader. You can either select reboot or simply input "fastboot reboot" into the command window. It may take about 5 minutes to start installing everything but just be patient, it should start. Sometimes with these things you have to do things twice before it works. If for some reason it doesn't work the first time then start from the beginning and try it again. It took two times for me, but that's because I installed system.img twice and was getting double screen. Newb error... and I was a bit inebriated last night when I did this.
Hope this helps someone!
Thanks again to manigault and MidgetMob!
NVIDIA download files HERE!

i think i done the same thing
but the problem i now have is i cnt get tablet into fastboot on pc. i can load fastboot on tablet with power and volume down , but the tablet only shows as MTP device in device manager. i have downloaded drivers from nvidia and no matter what i try i cant install them i have been through all instructions but scince it went to mtp device i cant get device showing in adb. The only way i can get device showing in adb on pc ist to select apply update from adb ! but none of these commands listed in your post will work because its in sideload. is there anyway i cn reset , flash custom rom ect bu using commands while device is in adb sideload.
all i get is now send the package you want to apply to the device with "adb sideload <filename>".....
if you could shed any light on this it would be much appreciated , thanks , lester

did you update official android 6.0 before? then, not working stock recovery, stock boot...
If you can enter bootloader mode, download unofficial twrp 3.0.0.0 (here http://forum.xda-developers.com/shield-tablet/development/wip-twrp-2-8-0-1-unofficial-t2877117) and flash it.
i have a working boot.img file on marshmallow if you want.. please reply.

Sorry for the late response! I have no clue how you got into sideload??? Are you talking about through the recovery on your device? You're not able to get adb/ fastboot to recognize the device, right? It doesn't matter how you get the tablet into the bootloader. Whenever you have the phone in the bootloader then you'll use the fastboot command to "talk to" the device; i.e. "fastboot devices" without the quotes. That command should show your device if it shows as an MTP device whenever you open your "device manager" in windows. That's the same exact situation I was in. Download the codeworks from nvidia like I linked above. Hopefully then you should be able to recognize your device through the bootloader. If not DM me and I'll try to help you.

I'm having the exact problem as Lester. Tablet boots into bootloader but won't connect to computer. So I go into recovery mode and nothing works except apply update from adb. Which brings up the side load message that Lester quoted. And bootloader is showing "device=locked". I am attempting to fix this tablet for a friend that messed it up trying to flash a custom rom. Problem is he had no idea what he was doing and I'm not exactly sure what he did. I do however have a lot of experience with rooted android devices and flashing so any help would be GREATLY APPRECIATED!
---------- Post added at 05:59 PM ---------- Previous post was at 05:55 PM ----------
Also, I've already tried flashing stock rom back onto the tablet by applying update from sd card function in the recovery but when I try to do that the tablet for some reason can't mount the sd card.

rom fiend said:
Tablet boots into bootloader but won't connect to computer.
Click to expand...
Click to collapse
If you've got the device in bootloader then you need to use fastboot, not adb. Try the command 'fastboot devices' and see if the device id is listed. If so then grab a factory image, unzip it and use fastboot to flash the .img files using the commands 'fastboot flash system system.img'. Just make sure to match the partition names to the files.

Hello i have similar issue except when i try flash something i get this error ''remote: file write failed''
and i have to reboot into fastboot to get it flashing fully
but even though i managed to flash everything by rebooting when i boot system nothing shows up, i can just see the back light coming on and turning off after a while
Please help

I somehow broke TWRP

I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.

mattlokk said:
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
Click to expand...
Click to collapse
Did you set:
Allow oem unlock in dev opt.
Fastboot protocol into BL?
Twrp app & manager need root to work.

Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link

thanks for the help, i'll try and work through this soon.

fpozar said:
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
Click to expand...
Click to collapse
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.

mattlokk said:
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
Click to expand...
Click to collapse
Okay so I'm guessing you have stock ROM.
To flash TWRP you have to enter fastboot mode (vol down + power I believe) and flash the twrp image with fastboot flash recovery twrp.img (rename the shield tablet twrp to just twrp.img and place it into your easy adb and fastboot folder)
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck

fpozar said:
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
Click to expand...
Click to collapse
Agreed. This is probably what is happening (as described on the TWRP webpage here:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Alternately, immediately rooting (flash SuperSU or Magisk) right after flashing TWRP, will prevent TWRP from being replaced with stock recovery.
Although the inconsistent fastboot connection, and how much trouble you had flashing TWRP initially, is a bit worrisome. Try using a different cable (maybe the one you are using is not connecting well?) try another USB port on the computer, and don't use a USB hub (connect direct to the PC).

Well, like they say: persistence is key. I kept pushing and trying new things until eventually.... I bricked the device. No, not really, it's working great now on LineageOS.
Thanks again to everyone who helped me out :good:. I'm still not sure exactly what caused TWRP to stop working on my device, however following this guide helped me fix it: https://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
The "flash-all.bat" restored everything to stock (including the recovery mode) and after that I was able to flash the latest TWRP and install Lineage.

No OS Installed!!! Help Please!

I tried to get magisk to work after installing the latest OTA and I did something wrong and had to wipe all the data from the Oneplus recovery menu. Towards the end in TWRP while wiping, I wiped off the OS by mistake. After clicking reboot, it just rebooted to the fastboot menu and when I click 'Go to recovery' on the fastboot menu it just boots back to the fastboot menu. My device is not being detected in powershell when I type in adb devices and it might be because after the first wipe that happened I didnt turn on adb debugging. I do not have twrp and my device is not being detected by my pc in powershell for me to adb push the whole os and twrp and flash them. I am literally freaking my skin off at this moment. Please help me. If I didnt mention any important detail please ask, Im super frightened so I might have missed something.
tl dr: No OS, no TWRP and locked in fastboot. (thanks to null0seven)

prathk said:
I tried to get magisk to work after installing the latest OTA and I did something wrong and had to wipe all the data from the Oneplus recovery menu. Towards the end in TWRP while wiping, I wiped off the OS by mistake. After clicking reboot, it just rebooted to the fastboot menu and when I click 'Go to recovery' on the fastboot menu it just boots back to the fastboot menu. My device is not being detected in powershell when I type in adb devices and it might be because after the first wipe that happened I didnt turn on adb debugging. I do not have twrp and my device is not being detected by my pc in powershell for me to adb push the whole os and twrp and flash them. I am literally freaking my skin off at this moment. Please help me. If I didnt mention any important detail please ask, Im super frightened so I might have missed something.
Click to expand...
Click to collapse
You should be able to use TWRP to reflash the OS. Personally, I would put the device in EDL mode and use the MSM Tool to put the device back to factory stock. Once back to stock, you can get your OTA and then reflash TWRP and root your device once again.

jcsww said:
You should be able to use TWRP to reflash the OS. Personally, I would put the device in EDL mode and use the MSM Tool to put the device back to factory stock. Once back to stock, you can get your OTA and then reflash TWRP and root your device once again.
Click to expand...
Click to collapse
I am not able to use TWRP. In the fastboot menu when I enter the 'Go to Recovery' option it just reboots back to the fastboot menu.
I'm relatively a noob in all this so if there's any other way please mention it.
UPDATE: I am currently downloading the stuffs required for the MSM tool, the download is extremely slow. Will check back once the download is done and I tried it. Thanks for atleast giving me some hope in the time being.

jcsww said:
You should be able to use TWRP to reflash the OS. Personally, I would put the device in EDL mode and use the MSM Tool to put the device back to factory stock. Once back to stock, you can get your OTA and then reflash TWRP and root your device once again.
Click to expand...
Click to collapse
While in the MSM tool after clicking 'Start', I got a 'Sahara Communication Failed' error. What do I do now?
UPDATE: Another problem right now is that after holding the volume up and down buttons simultaneously for a few seconds and inserting the cable to enter EDL mode (it shows as Qualcomm HS-USB QDLoader 9008 in device manager), within a few seconds the phone reboots into the fastboot again.

Sahara error it's not a real error. After that MSM does not finish installing OS?
But first try FastBoot rom :
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
Choose the one you need. For example i need GM31BA (european version)

null0seven said:
But first try FastBoot rom :
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
Click to expand...
Click to collapse
This.
---------- Post added at 02:02 PM ---------- Previous post was at 02:00 PM ----------
prathk said:
IAfter clicking reboot, it just rebooted to the fastboot menu and when I click 'Go to recovery' on the fastboot menu it just boots back to the fastboot menu. My device is not being detected in powershell when I type in adb devices and it might be because after the first wipe that happened I didnt turn on adb debugging.
Click to expand...
Click to collapse
adb won't work in fastboot, by definition (only works in OS and TWRP). Fastboot mode is for fastboot (and fastboot does not need debugging to be on). And fastboot is what you want, to flash the stock ROM.

null0seven said:
Sahara error it's not a real error. After that MSM does not finish installing OS?
But first try FastBoot rom :
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
Choose the one you need. For example i need GM31BA (european version)
Click to expand...
Click to collapse
No, its written waiting for communication with device and the app stops responding. I would attach a screenshot of the error but I myself am not able to try this method again (Check the update in my previous post).
UPDATE: I'm currently downloading the fastboot ROM. Hope it works.

He, prathk,
write that it's locked on Fastboot. NO twrp, no OS. That's why i suggest Fastboot rom, before MSM tool.
---------- Post added at 07:11 PM ---------- Previous post was at 07:06 PM ----------
(it shows as Qualcomm HS-USB QDLoader 9008 in device manager),
this is GOOD. youre phone drivers are corect. Remove the cable from phone.
Do this :
With phone off hold both volume buttons only and plug cable into computer .
Or power off the phone. Press vol. UP, 5to 10 seconds, plug the cable.
Youre problem with MSM tool it's that the phone it's not shut OFF !

null0seven said:
He, prathk,
write that it's locked on Fastboot. NO twrp, no OS. That's why i suggest Fastboot rom, before MSM tool.
---------- Post added at 07:11 PM ---------- Previous post was at 07:06 PM ----------
(it shows as Qualcomm HS-USB QDLoader 9008 in device manager),
this is GOOD. youre phone drivers are corect. Remove the cable from phone.
Do this :
With phone off hold both volume buttons only and plug cable into computer .
Or power off the phone. Press vol. UP, 5to 10 seconds, plug the cable.
Youre problem with MSM tool it's that the phone it's not shut OFF !
Click to expand...
Click to collapse
Thanks for the suggestion in your previous post, I added it.
I tried both the methods and both resulted in 'Sahara Communication Failed'.
And now even on trying both the methods it keeps restarting to the fastboot menu.

If the phone it's not off MSM not working.
Alternatively you can force your OnePlus 7 Pro to boot to EDL mode by the following steps:
Power off the phone.
Plug in the USB cable your computer but do not connect the other end to the phone.
Hold down Volume Up and Volume Down buttons for a few seconds, and plug in the cable while you are continuing to hold them.
You should see the anticipated EDL mode.

As advised before, you need to download the fastboot package made by @mauronofrio
Run the "flash-all-partitions.bat" while in fastboot.
You seemed mebbe confused before, adb and fastboot are different, adb is only to be used either within the rom or while in recovery. Fastboot is to be used while you're in Fastboot mode. It will still let you flash multiple partitions, hence why the fastboot fix should work.
For future reference, the best way to wipe data while leaving the rom intact is "fastboot -w", that will also remove encryption. (The flash-all-partitions batch file will do this too)
As long as you get a result after typing "fastboot devices" then you should be ok.

I flashed the Fastboot ROM as many of you suggested and it worked. Thanks to everyone who helped out and also thanks for correcting my knowledge. I just want to know if I'll still be getting OTA updates as usual or should I manually download it and flash it from now onwards.

prathk said:
I flashed the Fastboot ROM as many of you suggested and it worked. Thanks to everyone who helped out and also thanks for correcting my knowledge. I just want to know if I'll still be getting OTA updates as usual or should I manually download it and flash it from now onwards.
Click to expand...
Click to collapse
If you've flashed the default partitions you should get OTA, if you flash TWRP and root then you'll download the entire new rom, you don't get an OTA option.