Hi guys I manage to brick my shield (2017 16gb on latest Oreo 7.2.3) I unlock the bootloader, flash twrp and lineage os as well gapps but the rom doesn't boot as it should it keep boot looping (I forgot to do the wipe but the system was clean anyway becouse I unlock the bootloader 5 minutes before..) I was not able to launch the recovery too. So I try to flash the twrp again... the result was bad. Now restarts to the nvidia logo and boots again. I'm able to put it in fastboot (Using A+B on the joystick plug and unplug and plug power cable) but the pc no longer see shield. Adb device's doesn't show it. Device manager says only Android device - Android Fastboot. Any Ideas how to make the pc to see it again. I have installed all the drivers and everything. Any option I give from the recovery ceep restarting the device endless.. I download the official nvidia shield recovery rom for my device but without seeing it in adb is worthless. Any Ideas ?
Related
Hi all,
first of all - sorry for my bad english.
I have the following problem with my nexus 7:
the device is rooted and has the clockworkmod recovery installed, the Android version is 4.1.1.
My Computer stopped to recognize the tablet when i connected it, and it is not listed in the device manager anymore.
I tried different USB-ports, cables and even computers with no result, but OTG with Stickmount still worked.
So i tried to install a rom via clockwork mod, but the installation process aborded.
When rebooting the device stucked at the white google logo and still does.
I can go into fastboot mode but if i choose "recovery" i will get back to the google logo forever again.
I found this thread (http://forum.xda-developers.com/showthread.php?t=1773431&highlight=no+usb&page=2)
with instructions to flash the factory image via fastboot mode.
Now the fastboot command from the console shows also no result.
But i can´t install the driver, because my tablet isn´t recognized by my pc in any way evon not listed in the device manager.
Any Ideas?
Hey,
Very strange query but here goes. Rooted phone a while back and installed CM13 along with recovery. Was trying to update TWRP{ by downloading .img from their website, went to flashing, selected the file and hit recovery. Said it was succesful so attempted to reboot. Plugged in to charge and was charging but when I tried to switch it on, it was stuck in Cyanogen Bootloop (blue alien stayed on the screen for 10+ minutes). Tried rebooting to recovery by hitting power + volume down and instead of booting to TWRP, it takes me to a Cyanogen recovery screen where I see the following options:
Cyanogen Recovery.
- Reboot system now
- Apply update
- - -apply from ADB
- - -choose from emulated
- Factory reset
- - -system reset
- - -full factory reset
- - -wipe cache
- Advanced
- - -reboot recovery
- - -reboot to bootloader
- - -Wipe system partition
- - -view recovery logs
Here's what I tried as troubleshooting. Tried to do a system reset, factory reset and wiped cache and tried to restart my phone but no luck. Still stuck in boot loop with CM logo. Tried to reboot to bootloader but the screen is stuck with the 1+ logo for about 5 mins so gave up on that.
Basically, right now I can't access anything on the phone, can't find any way to reinstall a ROM and when I plug it into my Macbook, it is not recognised. So I'm screwed sideways. I had TWRP recovery set up so I have no clue how this happened but can anyone please help me with this.
If data isn't at risk try the Qualcomm recovery tool one the oneplus forum it's by nammand bhal (definitely butchered the name) but all data is lost and resets the phone to out of box conditions locked bootloader and Oos 2.2.1 so this is often a last measure (tool is Windows but may have Mac variant and the file is quite big)
My suggestion is to try to boot to bootloader again and flash TWRP
hmm mac book I don't have much experience with those
If you have a Windows pc you can use adb or on Mac if it has it. Also when it come to being found by a computer in recovery it should but again don't have a mac
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
AJay27 said:
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
Click to expand...
Click to collapse
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
justicesourglide said:
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
Click to expand...
Click to collapse
Actually I don't think the issue was with the Macbook since I have unlocked, flashed custom recoveries and sideloaded ROMs on several devices including OP2, OP3, Nexus 5, etc on mine. It might have been some accidental flashing error, which unfortunately ended up bricking your device.
My phone is a6000 plus variant and was running on CM 12.1 update 19 prior to getting bricked. I have flashed the same ROM before, however, this time I ended up flashing it twice-the second flash without clearing cache, data and the like and on top of the same ROM.
The problem is that the phone is not booting into recovery (just showing the lenovo logo).
It is however booting into fast boot mode. (Hold power key for reboot).
Now, I would just use adb to flash the phone but with cyanogenmod 12.1 with no update, the device is not showing in adb. (The USB worked fine before this, however I had USB connected during flashing and noticed that CM 12.1 with no update would not be detected on my PC.)
The phone is alive and well just not being detected in adb. Every time I connect the device to my PC via USB, the drivers install but fail.
I tried updating the drivers with device manager but error 10 is showing.
If I remove the battery the phone shuts down, until I power it up again, which results in the lenovo android logo on the screen.
What are my options in such a case?
Timeline of events:
I boot my phone into twrp with adb and flash CM 12.1 no update.
I see that the PC adb is not working and drivers fail to install.
I boot the phone into recovery using advanced recovery and notice that in twrp recovery the adb devices detect my phone.
I flash a queue of CM 12.1, update 20 and super user zip.
I recall that I had forgotten to clear data, cache and the like and end up dirty flashing.
I reboot the phone thinking it will fix it but the device just boots up the android and lenovo logo.
Furthermore, the device is not being detected in adb and drivers fail to install.
AsCi1 said:
I boot my phone into twrp with adb and flash CM 12.1 no update.
I see that the PC adb is not working and drivers fail to install.
I boot the phone into recovery using advanced recovery and notice that in twrp recovery the adb devices detect my phone.
I flash a queue of CM 12.1, update 20 and super user zip.
I recall that I had forgotten to clear data, cache and the like and end up dirty flashing.
I reboot the phone thinking it will fix it but the device just boots up the android and lenovo logo.
Furthermore, the device is not being detected in adb and drivers fail to install.
Click to expand...
Click to collapse
First of all remove your sd card and use a sd card reader or put it in another phone.
Then on the other phone/PC download a stock CM12 or 13 ROM and Gapps.
Save the ROM on the sd card.
Put the sd card on your phone and go to recovery
Wipe everything except SD CARD and then flast the ROM and GApps
Hey guys.
After the time I spent trying to unbrick my softbricked shield 2015 16gb, I decided to share how I was able to solve it.
I was on 5.2 and decided to update to 6.1 since the developer image was released and my previous upgrade from 5.1 to 5.2 with flashfire run so smoothly so what could go wrong??
After install lastest flashfire 0.73, I select all but data on the flash firmware package, and let it run.
I had my shield on 5.2 rooted and with TWRP as recovery.
After flashing vendor.img it restart and get stucked on the nvidia logo, and there was where
my problems started.
After 30 min I switched off and on again and same thing. Nvidia logo and nothing more. 1 hour after that I finally was able to go into bootloader mode.
I needed to use the default USB cable that came with the shield connected to OTG and USB on my computer. As soon as I connect the power and the led goes on I pressed the power button until I was
able to see the menu.
From there I was able to run fastboot. I reinstall every build and the shield refused to back to life. Flashed successfully but wont go through nvidia logo.
I enter recovery and did a reset assuming I had some problem with my data. No luck. I start to assume my shield has a hardware problem.
I downloaded both the stock recovery and the developer image 6.1, 6.0, 5.2, 5.1.
Tried to flash all of them one by one. Nothing worked. It complete the flash process but after reboot keep stucked on the logo.
Lots of time reading XDA and googling it I found a TWRP 5.1 flashable zip image, and in last resort I download it, reflash TWRP and flashed the 5.1 zip image.
It worked!!
I run the wizard as a new shield, and return to TWRP and flashed SuperSu 2.79. Rebooted, and install flashfire and run again the process with the 6.1 developer image.
This time flashed ok, and I finally get 6.1 rooted and working perfectly.
So resuming all the steps for those who dont want to read all
If you are stuck on Nvidia logo after flash 6.1
1 - Download firmware 5.1 zip TWRP flashable (search on XDA)
2 - enter bootloader on your shield hardware mode. Connect the OTG port on Shield using the default USB cable, and after connecting the power and the green light turn on press the power button until the bootloader menu appears.
3 - Assuming you already had the shield drivers and ADB installed on your computer, go to TWRP recovery or install it. I flashed TWRP 3.02 (once again search for it on XDA). fastboot flash recovery "twrp filename.img"
4 - Boot to TWRP and upload the firmware with the command adb push "firmware filename.zip" /sdcard/
5 - Upload also the SuperSu 2.79 binaries. adb push "supersu filename" /sdcard/
5 - from TWRP install the firmware and let it run. It will generate some errors but it will work.
6 - Reboot and complete the wizard.
7 - Reboot to TWRP (you can activating developer mode, and run adb reboot recovery from inside the androidsytem) and flash the SuperSU
8 - Reboot again and install the latest flashfire.
9 - Download the 6.1 developer image (search XDA for it)
10- Run flashfire and install the firmware package. Thats it!
Hope this will help someone
Hey their. So i jsut bought a one plus 6t and started playing around iwth it. I tried to get twrp and i got it but when i rebooted to os i had no wifi. So i download magisk zip and flashed it. After this i got stuck in bootloop and so i wne to twrp and wiped everything except system. Then i rebooted and got this message Qualcomm CrashDump Mode Attempted to kill init! exit code=0x0000000b do_exit. Then i freaked out and accidently wipes system too. Now i think i have a complete brick as adb still works but i cant transfer any file from pc to phone because theirs no system. Please help!!!
Never wipe system and vendor on A/B devices, literally, never.
Boot twrp and flash OOS or use msmdownloadtool.
What do you mean flash OOS. Like flash a fastboot file? And what version of msmdownloadtool should I get as their is no system. Should I get 10 cause that was my last system or it doesn't matter.
Update. I left twrp after flashing a stock image and now adb doesn't recognize my phone. When booting into recovery I go into the one plus recovery. Now I'm really screwed.
Okay now im really screwed. Whenever I boot with power up or power down I get sent to the bootlaoder page that says fastboot mode products name. I cant leave this page however. On the options above the information I click reboot recovery I get sent back to this page.
UPDATE. My phone is a literal brick now. It won't even turn on. I tried to force reboot it before and after it powered off it wont turn on. Its fully charged and when connecting to charger of holding buttons nothing happens. I have no warranty so Im hoping that someone can help me.
The "bootloader page" is fastboot and that's normal because there's no system to boot, you wiped that partition... and ADB only recognizes the phone when the boot process ends and ADB is enabled in the phone.
If you press vol up + down when you connect the usb cable the phone boots in EDL (Emergency Download Mode) mode, long press power + vol up to leave that state.
Now, download msmdownloadtool from here, extract the file, power off you phone, conect the usb cable to your pc, press vol up + down and connect the usb cable to the phone, open msmdownloadtool and flash the OS.
Edit: Read this thread for more detailed instructions.
What do you mean by flash the OS. The OS in the system or do I have to download one?
whenever I plug in my device it vibrates and then goes into the fastboot page. Also adb can detect it if I type in fastboot devices.
So i go the device to work and MsM worked until 4 seconds and then It said param preload for status of connection and status of last communication says device not match image
Try with the fastboot ROM.
When i downloaded another version of MsM it did not say no image match instead it stays at 4sec and says recording download time
Can you give me instructions on how to use the fastboot room? Like after i download it what should i do with it?
Download the rom, unpack it, boot your phone in fastboot (Power + vol up + vol down), connect the phone to your pc and execute the "flash-all.bat" file, and just wait.
um what is flash-all... How does it work what am i supposed to do.
what does unpack it mean?
Hey their im going to assume you meant to unzip the file and then open the file called falsh-all.bash. In that case when i do that i get this message "error: failed to load 'images.zip': No such file or directory
Press any key to exit..." In a CMD window