Question TA-1188 in red state, can't unlock bootloader and OS won't start

Question TA-1188 in red state, can't unlock bootloader and OS won't start - Nokia 2.2

I tried to downgrade from Android 11 to Android 10 a few months ago. Back then I had no knowledge about everything related to Bootloader Unlocking and other things.
I followed a tutorial. But my phone got bricked. So I followed an unbrick guide a few months later. I got it back to a state where I have basic Fastboot access.
But when I try to start the phone, is says Red State, Your device has failed verification. Incorrect Signature. Please download Image with correct signature or disable secure boot.
Now I don't have the Bootloader unlocked. I also can't do that with Fastboot. Results in the error that I am not permitted to do that. I also tried flashing TWRP but it says:
'download for partition 'recovery' is not allowed'.
Is there a way to get it working again? I would really need this phone again.
I have not made any backups. Also It says in Fastboot that my device is called: 0123456789ABCDEF. I dont think that is good because other phones I used fastboot on had a normal name.

J_029 said:
I tried to downgrade from Android 11 to Android 10 a few months ago. Back then I had no knowledge about everything related to Bootloader Unlocking and other things.
I followed a tutorial. But my phone got bricked. So I followed an unbrick guide a few months later. I got it back to a state where I have basic Fastboot access.
But when I try to start the phone, is says Red State, Your device has failed verification. Incorrect Signature. Please download Image with correct signature or disable secure boot.
Now I don't have the Bootloader unlocked. I also can't do that with Fastboot. Results in the error that I am not permitted to do that. I also tried flashing TWRP but it says:
'download for partition 'recovery' is not allowed'.
Is there a way to get it working again? I would really need this phone again.
I have not made any backups. Also It says in Fastboot that my device is called: 0123456789ABCDEF. I dont think that is good because other phones I used fastboot on had a normal name.
Click to expand...
Click to collapse
I'm dealing with that issue right now and my device won't even charge or turn on. Let me know if you find a fix. Did you try mtkclient already?

I have found a solution to fix red state. I also unlocked the bootloader afterwards and rooted the device.
The solution to fix red state is as following:
1. Go to: https://androidfilehost.com/?fid=2188818919693749336 and download the firmware (Its from FIH-Firmware.HikariCalyx.com Tutorial how to unlock bootloader)
2. Open SP Flash tool and load the firmware using the scatter file called MT6761_Android_scatter.txt
3. Select Format + Download and klick the download button
4. Now take your phone (Make sure to have it connected to a charger for over an hour bevore doing this, even tho the charging symbol might not show up) and hold down the volume buttons and while holding them, connect the phone to the pc using usb cable.
5. Wait for it to finish downloading.
6. When complete you should be able to start into fastboot. That can take up to one minute. Try putting the battery back in if it doesnt start after holding buttons over a minute.
7. When in fastboot, make sure the drivers are loaded. For this go into Device Manager. If there is an unknown device called Android, select update Driver > Search on my Computer > Select from a list. Then scroll down to TCL and then select Android ADB Interface. The device manager might tell you that it might not be the correct driver, but just continue.
8. Type into ADB and Fastboot window:
fastboot reboot recovery
9. When you see android laying on its back, hold power button and press volume up button (sometimes you have to press it 6 times), then the recovery menu should open up. Now select Wipe Data Factory reset. Select Yes and let it reset. After that start the phone again.
10. Your phone should start normal now. The startup can take up to 10 minutes. if it hasnt started after 30 minutes, repeat the procedure to reset it.
11. To get IMEI back, you have to unlock the bootloader and root the device. If you want to do that tell me. Its a bit complicated but i can tell you.
Make sure to follow the steps exactly

Thanks for the response, my device is a mt8163 and I have mtkclient if I can find the proper firmware what command would I use to flash the file

Related

Fastboot Mode Issue

Dear All,
Please help me regarding fastboot. When I press 3 keys (vol-up, vol-down and power key) while phone is off. I see the black and white screen written boot modes. From there when I select AP Fastbood device is restart with red Motorola logo and end up on home screen.. I have tried several times to turn off the device and repeat this process but no issue still there..
Moreover, if I did not select any options from boot modes than device automatically rebooted after 3 or 4 seconds..
Please help me out.. I want to unlock the boot loader root and install custom ROM..
Currently Model Number is XT925 and device is completely stock.. never rooted before...
thanks and regards,

akkay1 said:
Dear All,
Please help me regarding fastboot. When I press 3 keys (vol-up, vol-down and power key) while phone is off. I see the black and white screen written boot modes. From there when I select AP Fastbood device is restart with red Motorola logo and end up on home screen.. I have tried several times to turn off the device and repeat this process but no issue still there..
Moreover, if I did not select any options from boot modes than device automatically rebooted after 3 or 4 seconds..
Please help me out.. I want to unlock the boot loader root and install custom ROM..
Currently Model Number is XT925 and device is completely stock.. never rooted before...
thanks and regards,
Click to expand...
Click to collapse
After you use the volume down key to highlight "Fastboot", do you then press the volume up key to select it? If you just sit there and wait it will reboot normally. You must press the volume up key after you've highlighted the menu option.

akkay1 said:
Dear All,
Please help me regarding fastboot. When I press 3 keys (vol-up, vol-down and power key) while phone is off. I see the black and white screen written boot modes. From there when I select AP Fastbood device is restart with red Motorola logo and end up on home screen.. I have tried several times to turn off the device and repeat this process but no issue still there..
Moreover, if I did not select any options from boot modes than device automatically rebooted after 3 or 4 seconds..
Please help me out.. I want to unlock the boot loader root and install custom ROM..
Currently Model Number is XT925 and device is completely stock.. never rooted before...
thanks and regards,
Click to expand...
Click to collapse
try this,
-install adb on your pc
-plug in phone when powered up
- open a command prompt in your adb dir
- type in: adb devices then enter. it should show your phone in the prompt. also check your phone, there may be a popup to acknowledge.
- rerun adb devices until it shows your phone properly or you cant proceed
-now type in: adb reboot bootloader
if it works, the phone should reboot to the fastboot screen.
if it doesnt stick in fastboot, im sorry but i dont know what else to tell you to try.

Thank-you for the Response
bweN diorD said:
try this,
-install adb on your pc
-plug in phone when powered up
- open a command prompt in your adb dir
- type in: adb devices then enter. it should show your phone in the prompt. also check your phone, there may be a popup to acknowledge.
- rerun adb devices until it shows your phone properly or you cant proceed
-now type in: adb reboot bootloader
if it works, the phone should reboot to the fastboot screen.
if it doesnt stick in fastboot, im sorry but i dont know what else to tell you to try.
Click to expand...
Click to collapse
Thankyou so much for the reply, i followed your instructions and finally get in fastboot mode and unlocked the boot loader. However, is there any way from which I can go into recovery.. because through hardware way I am unable to go in recovery. Thanks
EDIT: I have tried entering command adb reboot recovery, then phone was rebooted and there was green android on screen with chest open.. thats it... i have waited for few minutes and rebooted the device mannually.

akkay1 said:
Thankyou so much for the reply, i followed your instructions and finally get in fastboot mode and unlocked the boot loader. However, is there any way from which I can go into recovery.. because through hardware way I am unable to go in recovery. Thanks
EDIT: I have tried entering command adb reboot recovery, then phone was rebooted and there was green android on screen with chest open.. thats it... i have waited for few minutes and rebooted the device mannually.
Click to expand...
Click to collapse
That's the entry to stock recovery. You have to push a combination of buttons from there to get into recovery. I forget the button combination, it has been posted many times, try searching or wait for someone else to jump in with the answer.
Sent from my LG-VS980 using XDA Premium 4 mobile app

Not sure where to post this question been reading so many post my eyes are tired......
- XT926 upgraded to kitkat 183.46 last week via flash in RSD from JB 4.1.2
- Root went well DONE (Towel root .apk)
- Unlock went well DONE (Motopocalypse .apk) yes fastboot shows the #3
- Flashed TWRP 2.7.1 DONE (did it using the adb in motopocolypse)
- Backed up my current stock ROM in TWRP seemed to go well the program confirmed the backup was successful...So I thought
- Got confident and wanted to try flashing CM11 (Kitkat version)
- After flashing CM11 my phone got stuck at boot like many others have.... no problem I backed up my stock ROM in TWRP.....So I thought
- Went to restore my stock ROM using TWRP and yup you guessed it like many others the restore failed half way through
Not a big deal starting fresh can be a good thing BUT I really need my old text messages and all I have is a USB backup of the phone (Internal/SDcard) on my PC and of course the TWRP back-up on the SDcard that won’t restore ...... Is there any way to get these messages back to my phone????

wonka144 said:
Not a big deal starting fresh can be a good thing BUT I really need my old text messages and all I have is a USB backup of the phone (Internal/SDcard) on my PC and of course the TWRP back-up on the SDcard that won’t restore ...... Is there any way to get these messages back to my phone????
Click to expand...
Click to collapse
Not sure how to help you with your immediate problem at hand, but going forward, I definitely recommend the sms backup + from the Google Play Store. Nice thing with that app is, you can link it to your gmail account, and all your text messages are backed up to your gmail.

bricked huawei g730

hello there,
I have huawei g730-u10
"MTK6582, quadcore cortex A7, 1GB Ram, 4GB Rom"
last week, I was trying to install a CWM recovery using "mobile uncle" app. after it finished , a prompt for restarting appears and I pressed "yes".
it was the last time seeing my phone alive!!! it restarts to huawei logo for about 20 seconds and restarts again and again and again....
unfortunately my device doesn't have a rom online, even on HUAWEI website, so, I downloaded a similar phone ROM "hdc-s5-gold" to use its preloader, cache, boot , etc
the problem is when I connect the phone to SP flashtools the red bar appears and then it holds for seconds and a message with connection loss appears while the phone is going in its infinite restart.. so the flashtools seems to find the phone for a while but fails to write to it thanks to power loss.
notes:
1. I have tried many flashtool versions
2. I have tried with and without battery connection, and with and without volume up holding.
3. the phone can't access to CWM, download mode or factory reset mode.
4. the drivers are installed shows: "MT65xx preloader" and I think there is no driver problem
5. even when I connect the phone to charger, it keeps restarting and the charging logo doesn't appear
I appreciate any help

SP log files attached
thanks

I have same problem.How to solve it.

same problem, what to do???

elkhopoa said:
hello there,
I have huawei g730-u10
"MTK6582, quadcore cortex A7, 1GB Ram, 4GB Rom"
last week, I was trying to install a CWM recovery using "mobile uncle" app. after it finished , a prompt for restarting appears and I pressed "yes".
it was the last time seeing my phone alive!!! it restarts to huawei logo for about 20 seconds and restarts again and again and again....
unfortunately my device doesn't have a rom online, even on HUAWEI website, so, I downloaded a similar phone ROM "hdc-s5-gold" to use its preloader, cache, boot , etc
the problem is when I connect the phone to SP flashtools the red bar appears and then it holds for seconds and a message with connection loss appears while the phone is going in its infinite restart.. so the flashtools seems to find the phone for a while but fails to write to it thanks to power loss.
notes:
1. I have tried many flashtool versions
2. I have tried with and without battery connection, and with and without volume up holding.
3. the phone can't access to CWM, download mode or factory reset mode.
4. the drivers are installed shows: "MT65xx preloader" and I think there is no driver problem
5. even when I connect the phone to charger, it keeps restarting and the charging logo doesn't appear
I appreciate any help
Click to expand...
Click to collapse
Universal unbrick guide:
Terminology - types of bricks:
Soft brick - often occurs in the shape of a bootloop or any other problems with booting such as always getting to recovery or not getting past the carrier logo. This type of a brick, which shows some signs of life, can in most cases be fixed.
Hard brick - As the name implies, your phone can essentially used as a brick and it shows no signs of life. This kind of a brick is rare and in theory should be unfixable. However there are advanced methods of fixing your phones such as JTAG, but they require extra tools and accessories.
The decision:
Is my phone soft or hard bricked?
If you answer yes to all of the questions below you probably have a hard birck:
Test as said in order!
Nothing happenes when you hold or press the power button
You cannot get the screen to even turn on by pressing or holding any combination of buttons on your phone
Nothing happenes if you do the same as about but with your phone plugged into a charger
Nothing happenes when you plug your phone into a computer
When you plug in your phone into a computer it does not recognize it as a phone, storage or any other media device
Nothing happenes when you try all of the above again, but with removing the battery in between steps for 10 seconds and putting it back in again
Nothing happenes when you try all of the above again, but after leaving the phone plugged into a charger for 2 hours
If all of the questions are a "yes", then you either have a broken charging port and and a discharged battery or you have a hard brick.
The unbricking:
There are many methods of unbricking and they are all different to each phone. Here I will list the most common methods that often succeed.
Samsung users skip to 4. method.
1. If you have access to a stock recovery:
Method 1:
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Choose “Wipe Cache Partition”.
5. Choose “Wipe Data / Factory Reset” to delete all your settings and apps, using the correct ROM.
6. Reboot your device.
Method 2:
Download the stock rom for your phone. It should be in ".zip" format. Make sure it's the official version
(Find it by Googling something like "[your phone model] stock rom")
Put the file on your phone's external SD card.
Make sure that the rom is for your exact phone model.
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Select "apply update from external storage"
5. Navigate to the zip file you copied to your phone
6. Install it.
If you get Status Error 7 that means you didn't download an official stock rom.
2. If you have access to a custom recovery:
Method 1:
Try stock recovery method 1
Method 2:
1. Find a stable custom rom for your phone or if you want to download the stock rom
Make sure that the rom is for your exact phone model.
2.. Copy the zip file to the phone's external SD.
3. Install the zip
(If you have a custom recovery you probably know the drill)
3. If you have access to fastboot mode:
First install ADB and fastboot drivers (if you haven't already):
To install it on windows there is a handy tool called the 15 Second ADB installer which will install pretty much everything you need.
On Ubuntu install with:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On Fedora:
Code:
sudo dnf install android-tools
On OS X using Homebrew:
Code:
brew install android-platform-tools
Once you have the drivers installed you have to find a recovery image for your phone to install a custom recovery.
You can try one of the popular recoveries such as CWM or TWRP.
You need to get the recoveryNameHere.img file for your phone.
Find it by Googling:
"[your phone model] TWRP recovery"
or
"[your phone model] CWM recovery"
Make sure that the recovery is for your exact phone model.
Now on your phone enter fastboot mode:
Turn your phone off.
You can try different button combinations. For my phone it's holding power and volume down buttons.
Once you're in fastboot mode plug your phone into a computer and open your terminal/cmd.
Type in:
Code:
fastboot devices
You should see a list of devices. There should be only one device ID number.
If you see the ID it's working. If you don't you didn't install the Google USB driver properly (on Windows) and if it says "'fastboot' is not a recognized command" or "No command 'fastboot' found" then you didn't even install your drivers.
If you have problems with installing Google "how to install adb and fastboot drivers"
Now that you know fastboot is working type in:
Code:
fastboot flash recovery C:\Path\To\Recovery.img
Replace "C:\Path\To\Recovery.img" with an actuall path of the recovery file you downloaded.
It should say success.
If it doesn't try to execute:
Code:
fastboot oem unlock
This will delete all data you had on your phone (games, game progress, apps...).
Now try
Code:
fastboot flash recovery C:\Path\To\Recovery.img
again.
Once you're done type in:
Code:
fastboot reboot
And your phone should still not work. Now what you have to do it try the custom recovery method above (number 2.)
4. If you have a Samsung device:
Try this tutorial of unbricking with Odin: click here

Bricked my Mate 8 when trying to go from NXT-L29C636B180 to NXT-L29C636B211

Hello everybody,
I managed to brick my mate 8 as per the title, honestly thinking why did i even bother, that whole saying "If it ain't broke, don't fix it." applies here 100%.
So i have been in the NXT-L29C636B180 which i put with the dload method (original was C636B103) and since then everything was good, all except the video camera that is.
So i wanted to try to get to the nougat update (561?) but i read that you need the 211 first. As i couldn't find it i used the android app: firmware finder, and using the proxy method i told basically the system that a new update is up and download it - so this is the update option in the settings..
So after it downloaded NXT-L29C636B211 then it restarted, starting unpacking, and the installation stopped at around 5% when it restarted by it self. And that was it...
I am in a screen where i cannot use the touch, but only the buttons on the side and have the options
"Reboot system now"
"Wipe data/ factory reset"
"Wipe cache partition"
Tried the cache and rebooting, didn't do anything.
Tried wiping, and reboot, then i go in another page
"Huawei eRecovery" where it asks to connect to the wifi and download but then throws an error message "Getting package info failed"
That is pretty much it, i tried putting the update.app in the dload folder in the sd card and tried to use that method but it wouldnt boot that (used the volume + and - and power buttons) but it took me back to one of the above.
Am i out of hope? Is there anything i can do to restore it?
I really appreciate the help.

same problem!

kaelthuzad said:
Hello everybody,
I managed to brick my mate 8 as per the title, honestly thinking why did i even bother, that whole saying "If it ain't broke, don't fix it." applies here 100%.
So i have been in the NXT-L29C636B180 which i put with the dload method (original was C636B103) and since then everything was good, all except the video camera that is.
So i wanted to try to get to the nougat update (561?) but i read that you need the 211 first. As i couldn't find it i used the android app: firmware finder, and using the proxy method i told basically the system that a new update is up and download it - so this is the update option in the settings..
So after it downloaded NXT-L29C636B211 then it restarted, starting unpacking, and the installation stopped at around 5% when it restarted by it self. And that was it...
I am in a screen where i cannot use the touch, but only the buttons on the side and have the options
"Reboot system now"
"Wipe data/ factory reset"
"Wipe cache partition"
Tried the cache and rebooting, didn't do anything.
Tried wiping, and reboot, then i go in another page
"Huawei eRecovery" where it asks to connect to the wifi and download but then throws an error message "Getting package info failed"
That is pretty much it, i tried putting the update.app in the dload folder in the sd card and tried to use that method but it wouldnt boot that (used the volume + and - and power buttons) but it took me back to one of the above.
Am i out of hope? Is there anything i can do to restore it?
I really appreciate the help.
Click to expand...
Click to collapse
That happened to me too. you will still be able to enter fastboot. plug your phone to your pc and and press and hold the power and volume down. that should take you to the fastboot screen.
find the appropriate twrp recovery for your phone and use the command
fastboot flash recovery "recovery name".img. wait till its done.
press and hold the power and volume down button till the phone reboots. that will takeyou to twrp recovery. there you could either flash b210 or the beta b521 -- which i am on.

crazynitro said:
That happened to me too. you will still be able to enter fastboot. plug your phone to your pc and and press and hold the power and volume down. that should take you to the fastboot screen.
find the appropriate twrp recovery for your phone and use the command
fastboot flash recovery "recovery name".img. wait till its done.
press and hold the power and volume down button till the phone reboots. that will takeyou to twrp recovery. there you could either flash b210 or the beta b521 -- which i am on.
Click to expand...
Click to collapse
Thank you for the response. I will give it a try today after work i am a complete noob so its the first time for me to see what fastboot is, never heard of TWRP, i was always stock so never needed to mess with my phones.
If i recall doing power and volume down while plugged it was taking me to the page i mentioned to wipe the data, reboot or wipe the cache.
I managed to go to the fastboot page on the phone by pressing volume - and then plugging the phone to the pc. Now in the white page on the phone it shows, Phone unlocked in red. Does this mean just it is carrier unlocked?
So do i need to have the bootloader unlocked to do anything here? How do i do that? I cannot buy the code i suppose now since my phone is bricked i will have to go the Huawei way? And how do i do that, i saw a site to create a HUawei ID but in the registration page it didn't mention UK anywhere (where i live), mentioned Hong Kong and other Asian territories. I bought the phone from Wonda mobile, and being the 636 i would think its the asian model anyway.
Regarding TWRP, i didnt install it from before the phone was bricked will i still be able to do what you mentioned? And for the image i need to use, do i need to go to the firmware i was in before (636B180) or the one i tried to go to (636B211)? I can't seem to find the 180 anymore anywhere.
Sorry for the mass amount of questions, trying to sort it i have the phone for less than a year and i am gutted for messing it up like that.

kaelthuzad said:
Thank you for the response. I will give it a try today after work i am a complete noob so its the first time for me to see what fastboot is, never heard of TWRP, i was always stock so never needed to mess with my phones.
If i recall doing power and volume down while plugged it was taking me to the page i mentioned to wipe the data, reboot or wipe the cache.
I managed to go to the fastboot page on the phone by pressing volume - and then plugging the phone to the pc. Now in the white page on the phone it shows, Phone unlocked in red. Does this mean just it is carrier unlocked?
So do i need to have the bootloader unlocked to do anything here? How do i do that? I cannot buy the code i suppose now since my phone is bricked i will have to go the Huawei way? And how do i do that, i saw a site to create a HUawei ID but in the registration page it didn't mention UK anywhere (where i live), mentioned Hong Kong and other Asian territories. I bought the phone from Wonda mobile, and being the 636 i would think its the asian model anyway.
Regarding TWRP, i didnt install it from before the phone was bricked will i still be able to do what you mentioned? And for the image i need to use, do i need to go to the firmware i was in before (636B180) or the one i tried to go to (636B211)? I can't seem to find the 180 anymore anywhere.
Sorry for the mass amount of questions, trying to sort it i have the phone for less than a year and i am gutted for messing it up like that.
Click to expand...
Click to collapse
did u solve it plz i have same problem

first download NXT-L29C636B170 here: https://goo.gl/dHk8r8 , download Huawei extractor here: https://forum.xda-developers.com/showthread.php?t=2433454 ,unzip update.zip from B170 firmware downloaded, go to huawei extractor and choose UPDATE.APP (from B170 firmware extracted), and extract only recovery.img, download ADB Command here: https://goo.gl/05Rx06 unrar and copy recovery.img into ADB Command folder, put your phone in fastboot mode, turn off your device, then hold volume - and fast plug your phone into PC, now you are in fastboot mode,go to ADB Command folder and hold shift, holding shift key do click right with the mouse,and click on: open command window, now write: fastboot devices, enter, and you can see your device are connect, now write: fastboot flash recovery recovery.img, enter, when it finished write: fastboot reboot, and enter, then the system reboot, turn off your phone, now put UPDATE.APP (from B170 firmware) into dload folder in sdcard, with your phone off hold volume +, volume -, and power at the same time, then you can update by dload method,wait it finish and the phone reboot, now you're running NXT-L29C636B170, and if you want update to NXT-L29C636B211 you can find here: https://forum.xda-developers.com/mate-8/general/huawei-mate-8-stock-firmware-official-t3391727/amp/ unzip the update.zip and put UPDATE.APP (from B211) into dload folder in sdcard (obviously you need delete the UPDATE.APP from B170), now go to dialler and press *#*#2846579#*#* and project menu open, choose Software upgrade>SDCard Upgrate and yes, the system reboot , wait it finish and reboot, and you're now running NXT-L29C636B211. if you have any problem just tell me.
sorry for my bad english.

Shield Tablet problems: ADB, Recovery Mode, Fastboot... = DEAD?

I can imagine that you all are tired of reading this headline, but seriously, ME TOO.
I have been looking for information about this issue during several weeks and I have not found any solution, so I would extremely thank you if you take your time reading this problem and trying to help me finding a solution.
Some months ago I tried to flash a ROM on my Shield Tablet, I followed all the steps from a topic in this forum: [Complete Guide] SHIELD Tablet K1 Root, Custom Rom and Xposed Framework but I wanted to try a different ROM: CARBON-CR-5.1-MOO-WEEKLY-shieldtablet-20170216-0454 (the name of the file) And now I have a tablet that is stuck on the Carbon launch screen every time I turn it on, when I press volumen down + power it goes into the screen buttt as soon as I press recovery mode the only thing it does is to restart itself and stays stuck in the NVIDIA screen. The Minimal ADB and Fastboot do not recognize the tablet with the adb devices command.
When I turn on the tablet (and stays stuck into the IOS icon as I mentioned before) and connect it to the PC the device manager recognize the tablet as a Portable device with the name: MTP USB device, when I press the power+volumen down the PC recognize the tablet as an Android Device -> Android Bootloader Interface. And this is all the information I have about my problem...
May you help me?
Thank you in advance. I hope your knowledge will help me and other people with the same problem. If you need more information of this problem let me know and I'll answer ASAP. If you have any idea tell me and I'll try it.

Warlain said:
when I press volumen down + power it goes into the screen buttt as soon as I press recovery mode the only thing it does is to restart itself and stays stuck in the NVIDIA screen. The Minimal ADB and Fastboot do not recognize the tablet with the adb devices command.
When I turn on the tablet (and stays stuck into the IOS icon as I mentioned before) and connect it to the PC the device manager recognize the tablet as a Portable device with the name: MTP USB device, when I press the power+volumen down the PC recognize the tablet as an Android Device -> Android Bootloader Interface. And this is all the information I have about my problem...
May you help me?
Click to expand...
Click to collapse
Your device is not, dead, it's only taking some time to reflect
First of all, I understood that you're able to access to the device's bootloader menu, through the button combo (black screen with white text, "continue","restart bootloader","recovery mode"), and you selected "recovery mode".
Now, unless you have flashed a custom recovery, there's nothing to do with the shield's stock recovery, so, just enter in the bootloader menu as you did, without selecting any option.
You are now in "fastboot mode", in order to check your device's connection you have to write in the adb shell
Code:
fastboot devices
If you see your device you can now boot a custom recovery that will help you to fix the problems you caused, I would follow this link: (copy-paste, can't post links)
"nvidiashieldzone.com/shield-tablet/shield-tablet-root/root-shield-tablet-v1-marshmallow/"
And do the 8th step, in "Root procedure"
Fastboot with TWRP
Type “fastboot devices” Copy and make sure your Shield Tablet is visible.
If your Shield Tablet is listed, type “fastboot boot twrp-20151227-EXPERIMENTAL-shieldtablet-m.img” Copy (or whatever you named it) and hit enter. If your TRWP image filename has a space in it, you may have issues.
After 15 seconds or so (be patient), you should see the TWRP Recovery screen. Note: This experimental version has some UI issues, just keep at it.
You may be prompted with something to do with the system being READ ONLY. Accept the default and swipe.
Click to expand...
Click to collapse

Use fastboot to wipe cache (fastboot erase cache) then try to flash TWRP (with fastboot) again. This will often clear up issues with being unable to boot to TWRP (at least on other devices).
If you are able to boot TWRP, restore the TWRP backup (if you made one) or put another ROM on the phone, and flash it.

I also have this kind of problem. After i update twrp by flashing it and restore a backup the sistem doesnt show. Stucks on nvidia logo. I tried even restore my recent backup but nothing also. Any idea ?

'Artemis' said:
Your device is not, dead, it's only taking some time to reflect
First of all, I understood that you're able to access to the device's bootloader menu, through the button combo (black screen with white text, "continue","restart bootloader","recovery mode"), and you selected "recovery mode".
Now, unless you have flashed a custom recovery, there's nothing to do with the shield's stock recovery, so, just enter in the bootloader menu as you did, without selecting any option.
You are now in "fastboot mode", in order to check your device's connection you have to write in the adb shell
Code:
fastboot devices
If you see your device you can now boot a custom recovery that will help you to fix the problems you caused, I would follow this link: (copy-paste, can't post links)
"nvidiashieldzone.com/shield-tablet/shield-tablet-root/root-shield-tablet-v1-marshmallow/"
And do the 8th step, in "Root procedure"
Click to expand...
Click to collapse
Done, Thank you a lot! It starts working again!!!

Question Last effort for bricked phone LE2117

Hello,
I followed the steps for the T-Mobile unlock...unlocked the SIM and the bootloader with the unlock token from OnePlus. When I rebooted after running 'fastboot oem unlock', I did not have root yet, I was not able to backup my partitions. Apps like Maps would crash immediately.
Stupidly, I decided to move forward with installing the latest global open beta rom using https://forum.xda-developers.com/t/convert-t-mobile-oneplus-9-to-global-or-other-firmware.4277169/
Once i executed flash_all, I saw errors for being unable to write to partitions and most of the .img files failed to install.... due to me not having root. At this point I was stuck in fastboot mode. I was NOT in fastbootd, I did not run 'fastboot reboot fastboot'. I was in the bootloader instead.
Since I'm on linux i went ahead and downloaded the Tmo MSM tool on my windows box and went to bed.
Even more stupidly I did not plug in my phone, and it died overnight
I can get it to boot for a second or two holding down the power button + volume down. Neither ADB nor fastboot can see my device.
I'm pretty sure I hosed the phone, just checking with you guys to make sure.
I'd appreciate any help.....

Update: When I use the MSM tool, i see the qualcom driver being used. However I'm not sure how to get the phone to be seen, i've tried holding down the volume up/down + power button at the same time.
MSM tool can't see the COM....Is there another way to enter the LDS or whatever?

You need the correct drivers and will need to go to advanced reboot, troubleshooting, allow unsigned driver option to be able to install the driver.
GLOBAL OnePlus 9 MSM TOOL UPDATED
Frist off Im not responsible for anything that happens to your phone!!! VERY SIMPLE IF YOU ARE BICKED,BOOTLOOPED OR JUST WANT TO GO BACK TO 100% STOCK THIS WILL WIPE ALL DATA!!! AN RELOCK BOOTLOADER OOS 11.2.4.4.LE25AA MUST HAVE QAULCOMM...
forum.xda-developers.com
I had similar issue and had to hold power and volume up to reconize the device. I thought it just wouldn't power on.

Yetry vol+ and Power for like 20sec.
Just an idea.

I'm in the same situation. Got my unlock token, ran it, and then....
EDIT: I just read something about using the OnePlus 9 Pro India MSM tool, and click "Lite Firehose"
onepluscommunityserver.com/list/Unbrick_Tools/
we shall see....

Fixed using Tmo MSM. Switched Firehose on/off. Thanks everyone!

Database Info

welcome