Related
Hello Everyone. Normally I´m the quiet Reader and not the Active Poster but I need your help guys.
I have a problem since yesterday and I tried to fix it by myself with searching everywhere but couldn´t do it by myself.
What I had before:
Optipop 5.0.2 with Racer Kernel (both had Builds from January) + TWRP 2.8.1
What I wanted to do:
Flash Grogg's AOSP 5.1 and newest Code Blue Kernel
What happenend:
I factory resetted and successfully flashed Grogg's AOSP 5.1 and Code Blue Kernel but had Problems with FCing Clock and Dialer so I tried to reflash both after wiping completely (even internal storage), mounted it and put the needed new files on the internal storage.
I reflashed the Custom Rom + Custom Kernel and the newest Radio, wiped Cache/Dalvik and rebooted. It booted and the notification screen with 'optimizing apps' appeared. After that that screen went black and nothing else.
It was lit so I´knew that the device wasn´t shut down and tried to rebbot sincee nothing happened. I noticed that it was possible to reboot or shut down the device normally so there might have been a Problem with the Rom.
I retried the whole procedure and this time the notification screen didn´t show up after the boot logo and went directly to the black blank screen but i still had the possibility to rebbot/shut down the device normally. This time I didn´t wipe the whole storage and this time it got stuck at the boot logo and the Custom Recovery seems to be broken, too. The screen shows the dead Android with the red triangle.
My Problem is that I can´t connect my device to the computer, find it with 'adb devices' and reflash the Recovery with fastboot. The device is shown as 'android' in device manager in Windows 7 and nothing else. I already tried to un- and reinstall the Google drivers and that whole stuff but it doesn´t work for God's sake. adb doesn´t list my device and the 'list of devices attached' is blank although my device is connected.
I know my phone is soft bricked and that it is possible to fix that although I don´t know why it even broke the OS and Custom Recovery.
Can anyone help me out with a step-for-step-guide to fix the adb Problem and explain me why that blank screen even happenend?
Edit: If I´m in fastboot mode the device is shown as >Android Bootloader Interface< and isn´t listed with 'adb devices'. If it is powered off it is shown as >Android Composite ADB Interface< but is listed with 'adb devices' but I can´t flash the Custom Recovery.
Beyazid said:
My Problem is that I can´t connect my device to the adb to reflash the Recovery.
Click to expand...
Click to collapse
You don't use adb to flash a custom recovery. You use fastboot. That's your first problem.
I actually meant that it isn´t shown with the command 'adb devices' I will change that in the text
Edit: I also noticed that the fastboot mode is always on in the bootloader although the device isn´t connected to the pc. Shouldn´t it only be active if it´s connected?
Beyazid said:
I actually meant that it isn´t shown with the command 'adb devices' I will change that in the text
Edit: I also noticed that the fastboot mode is always on in the bootloader although the device isn´t connected to the pc. Shouldn´t it only be active if it´s connected?
Click to expand...
Click to collapse
I see a couple problems here.
First one is use the newest version of TWRP. You can get that from my signature.
Second is Code_Blue may not be compatible with the ROM you are testing.
You don't need ADB at all for this, you need fastboot.
As I said. I just use adb to make sure that my device is found by and connected to the pc. I know that fastboot is used to flash everything but my Nexus 5 isn´t even shown. So how can I get my phone connected to flash the custom recovery?
And it seems like it is compatible since it worked the after the first installation and boot
FFS, XDA. I had just written a huge ass post on how to use fastboot properly, with the proper commands and ****, and you logged me out, making me lose all that. F U.
Beyazid said:
and the Custom Recovery seems to be broken, too. The screen shows the dead Android with the red triangle.
Click to expand...
Click to collapse
This is the stock recovery.
You need to put your device in fastboot mode, REFLASH TWRP again with fastboot, then STRAIGHT FROM FASTBOOT select (with vol keys and Power) "Restart recovery". When you're in TWRP, wipe data/factory reset, reflash rom, gapps, REBOOT, PROFIT.
`fastboot devices` and `adb devices` are two commands to check if an active connection exists, between the host interface (on the PC, look at it as servers) and the device interface (look at it as clients). both commands will only return your device's SN IF drivers are correctly installed (speaking on a basic level, and about Windows). If you execute those commands, no SN comes up, then you need to fix drivers FIRST. Not even worth trying to do other commands.
`fastboot devices` only works here -> http://bazalabs.com/wp-content/uploads/2014/07/20140705_215603.jpg
`adb devices` works in TWRP/CWM (NOT in stock recovery) and in Android itself (needs USB Debugging active).
Thanks for the help. I was able to flash the Custom Recovery and the Custom Rom with and without Code Blue Kernel but in both ways the phone loads, sets up at the boot logo and goes straight into the blank black screen which appears without the notification screen of the apps that get optimized.
I can manually turn off, reboot.or take a screenshot which clearly indicates that the Rom itself is installed.
How can I fix that problem?
Thanks in advance
Edit: Tried with the Blue Code Kernel which gave that blank screen and wiped everything but internal storage and reflashed just the Custom Rom which gave me the same result
Could it be because the system.img or boot.img are missing??
Beyazid said:
Thanks for the help. I was able to flash the Custom Recovery and the Custom Rom with and without Code Blue Kernel but in both ways the phone loads, sets up at the boot logo and goes straight into the blank black screen which appears without the notification screen of the apps that get optimized.
I can manually turn off, reboot.or take a screenshot which clearly indicates that the Rom itself is installed.
How can I fix that problem?
Thanks in advance
Edit: Tried with the Blue Code Kernel which gave that blank screen and wiped everything but internal storage and reflashed just the Custom Rom which gave me the same result
Could it be because the system.img or boot.img are missing??
Click to expand...
Click to collapse
Try another ROM.
System.img .. boot.img.. comes with the ROM you flashed (well, not exactly, but both partitions do get written to), so no, they're not missing.
I gave it another try and fixed it.
I'll write it down so anybody who ever faces that problem can solve that, too.
Follow that guide (http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701) step by step and after a few minutes of flashing and a few minutes of booting you should get a clean and fresh Android Version on your device. It removes all the old files and installs the newest files.
And thanks guys for helping me out with that adb/fastboot mistake. Kudos to you
Hey guys.
Some issues right now....
I can't get the phone to boot. It gets stuck on boot logo. I can get it into fastboot, but not recovery.
If I try to enter recovery, it shows boot logo, then change brightness level a little bit for some reason, then nothing. Back to boot logo after screen goes black.
So it appears that the TWRP isn't installed correctly, but I've reinstalled it several times, but it never actually seems to work.
I can see the device in fastboot. Bootloader is also unlocked.
So, does anyone have a solution for this issue?
I can get it into fastboot
Click to expand...
Click to collapse
This is good news as it means you should be able to just flash the recovery from fastboot.
1. Download the latest TWRP Recovery: http://twrp.me/devices/bacon (I believe this is the link, it's blocked at school )
2. type the command
fastboot flash recovery /location/of/twrp/img
Click to expand...
Click to collapse
3. Wait for it to complete and then reboot the device by holding down power and volume down.
4. Then if it boots into TWRP you should be able to mount it on the computer you plug it into and then carry over a ROM and/or GApps files.
I'm in the exact same boat, happened after I tried an OTA update. I can't flash anything into the phone via ADB because my phone isn't recognised. isn't recognised in ADB. This is while I am in Fastboot. I'm on OSX.
Rorys-MBP:~ Rory$ adb devices
List of devices attached
Click to expand...
Click to collapse
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.
So today my new One Plus 6 arrived. I tested it out for a bit made sure everything seemed to be working ok.
Then I unlocked bootloader, flashed twrp, magisk, all without issue. (I followed a guide I found on google) While setting everything up, I noticed that there was an update avaliable. So I installed that and got a message that the update will remove root. I thought "ok, i'll just have to do that again after. Update installed, rebooted device to recovery and realize TWRP is also gone after the update. So then I rebooted again to the bootloader and do fastboot devices command on my pc. Phone is there. Next I do the fastboot flash boot twrp.img command.
Sending.. Writing.. Finished... But I was still on the bootloader on the phone. I tried it a couple more times with no result. Restarted the phone only to boot into TWRP now. I thought to myself "hmm I'm not sure that's what's supposed to happen" but I continued to flash twrp.zip anyway. Rebooted the device.. TWRP booted again. Tried rebooting a couple more times with the same result.
Now, maybe this is where I messed things up more seriously. I'll also mention I foolishly didn't perform a backup on TWRP before doing all this. Not sure what to do, I flashed magisk as well. And I tried rebooting system, then when that didn't work I think I rebooted "slot B' for some reason.... After that it would only show the oneplus boot animation for a seemingly indefinite period of time.
I found I could get int the bootloader menu by holding vol up and power. Tried flashing TWRP, seemed to work on my computer's end but didn't boot recovery on phone. I rebooted into recovery from bootloader menu, brought me to endless oneplus boot animation again. Selecting start on the boot loader booted to TWRP. From there I rebooted back to slot A. Now it boots straight into TWRP.
I'm not sure what went wrong. I've rooted, installed various roms, etc on previous devices. Never had any issues before. But as I'm sure you can tell I don't really know what I'm doing. Does anyone have any advice? Thanks.
Your not supposed to fastboot flash the twrp, youre supposed to fastboot boot it. Just reflash stock boot.img and you'll be good
usernameisausername said:
I'm not sure what went wrong. I've rooted, installed various roms, etc on previous devices. Never had any issues before. But as I'm sure you can tell I don't really know what I'm doing. Does anyone have any advice? Thanks.
Click to expand...
Click to collapse
A number of things work differently on this phone. Don't assume any of your previous knowledge transfers over. There is a steep learning curve.
Stay away from random guides on Google. There are reliable guides here that, if you follow them to the letter, will keep you out of trouble.
fastboot flash boot [.IMG]
Is the issue. Should be
fastboot boot [.IMG]
On www.twrp.me/Devices you'll find the OnePlus 6 plus a corresponding how-to, directly from the source.
Your best bet:
1. Download the full ROM zip from either OnePlus directly or one of the links here on XDA.
2. Download latest TWRP files from twrp.me
3. fastboot boot [.IMG]
4. If in TWRP, connect to your PC and send the ROM over to your phone (MTP should work I think. Else, just ADB push it)
5. Flash the ROM in TWRP as you would flash any other ROM.
6. Should work, your system is now back to stock (also recovery). Let it boot once to be sure and then retry magisk but with the right fastboot commands.
To flash TWRP permanently, move the installer.zip you find on TWRP.me to your phone, fastboot boot the .IMG and flash the installer.zip in recovery.
Let me know if it worked
schwarzerfleck said:
4. If in TWRP, connect to your PC and send the ROM over to your phone (MTP should work I think. Else, just ADB push it))
Click to expand...
Click to collapse
MTP is disabled on most versions of twrp including official. There is an unofficial version with MTP working though it's a bit wonky.
iElvis said:
MTP is disabled on most versions of twrp including official. There is an unofficial version with MTP working though it's a bit wonky.
Click to expand...
Click to collapse
Yeah that's why I suggested the ADB push
schwarzerfleck said:
Yeah that's why I suggested the ADB push
Click to expand...
Click to collapse
So I'm having the same issue as OP currently and am somewhat a noob to this. I'm stuck booting into recovery, how do I adb push to the phone? its not showing up in adb devices at all
Eilermoon said:
So I'm having the same issue as OP currently and am somewhat a noob to this. I'm stuck booting into recovery, how do I adb push to the phone? its not showing up in adb devices at all
Click to expand...
Click to collapse
If you have USB debugging enabled, it's probably a driver problem. Windows 10 has issue with driver signatures and there's a setting that needs to be disabled. Do a search as it's been discussed (I use a Mac so I'm not certain what).
iElvis said:
If you have USB debugging enabled, it's probably a driver problem. Windows 10 has issue with driver signatures and there's a setting that needs to be disabled. Do a search as it's been discussed (I use a Mac so I'm not certain what).
Click to expand...
Click to collapse
Thanks for the info! If anyone has a source for this, that'd be awesome
I'm sure my drivers are fine cuz i messed this up via fastboot.
so i got android 10 on my op7p. There were some magisk modules that caused a bootloop. But i cant uninstall those modules without twrp. So i decided to flash twrp into a boot slot via fastboot. then, i set the active-slot to that. but then I still don't get twrp idk why. Now, I can get into fastboot but my pc doesnt detect it, I cant boot into the system either. The only thing my pc detects is when i power the phone off and plug it in, it automatically boots into the unlocked bootloader screen and gets stuck in there. PC detectes an "unknown usb mass storage device". HELP!!!
xnegra80 said:
I'm sure my drivers are fine cuz i messed this up via fastboot.
so i got android 10 on my op7p. There were some magisk modules that caused a bootloop. But i cant uninstall those modules without twrp. So i decided to flash twrp into a boot slot via fastboot. then, i set the active-slot to that. but then I still don't get twrp idk why. Now, I can get into fastboot but my pc doesnt detect it, I cant boot into the system either. The only thing my pc detects is when i power the phone off and plug it in, it automatically boots into the unlocked bootloader screen and gets stuck in there. PC detectes an "unknown usb mass storage device". HELP!!!
Click to expand...
Click to collapse
How did you flash twrp? On A/B devices like the OP7P you can't simply fastboot flash twrp since that will cause you bootloops. To install twrp you have to fastboot boot the image and when TWRP is booted you have to flash the installer zip file. Since you are now stuck in a bootloop, you can try to recover your boot image with something like this https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345 (no guarantees on this).
Fastboot flash this image and see if you can boot again. If that does also not work I believe the best thing you could do is reset everything with the MSMDownloadTool.
Did you use this command: fastboot flash recovery filename.img?
If yes, you'll have to use MSM to restore it
THREAD CLOSED! If interested in the subject please follow this thread: https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997
Relevant posts have been copied to that thread.