Related
My Oneplus One - 64GB was running LiquidSmooth's Alpha ROM.
I hadn't used the phone in like a month. A couple of days ago i thought there'd be an updated version so i just downloaded a later version. I think I flashed the 01-22 Build.
I did not do a full wipe however. (I realize now that It would have been a good idea to do a full wipe before the flash. :s )
I assumed that since the base of the ROM was the same lollipop, all I had to do was wipe cache/dalvik and flash the update.
Installation proceeded as usual and I wiped cache/dalvik(I'm never sure when to do this so i do it before and after install) once more and then Reboot System.
But the phone went on a bootloop for like 10minutes or so.
I tried to get into Recovery but it just wouldn't. It would just show the 1+ Logo and Powered by android screen and then turn off..
I did however manage to get into the fastboot mode by pressing power +vol up.
Now the problem is, the device doesn't show up in the command prompt when i type
Code:
fastboot devices
I uninstalled all the usb drivers from my pc.
Installed the Universal ADB drivers from kouch's site but still no progress..
Device manager still shows the phone as an unknown device.
What am I doing wrong? What can i do to get the phone to be recognized so I can flash the recovery and flash a new ROM?
It's related of firmware change. After 01.17.2015 you must flash the latest CM12 rom and then flash the rom you want.
That's a known "issue". Hope it helps.
Problem is:
1. I no longer have a working recovery(can't boot into recovery).
2. Rom doesn't boot, stuck in a bootloop.
3. Can get into fastboot mode, but pc doesn't recognize device and it doesn't show up when i type "fastboot devices".
I've already installed "Universal ADB Drivers from here -> http://www.koushikdutta.com/post/universal-adb-driver
What can i do to be able to access phone via fastboot?
Should i remove these drivers and try another driver? If so, which other driver should i install and test with?
I don't have any critical data on the phone, I just want to get it working again so my family members can decide who wants the phone.
thetearer said:
Problem is:
1. I no longer have a working recovery(can't boot into recovery).
2. Rom doesn't boot, stuck in a bootloop.
3. Can get into fastboot mode, but pc doesn't recognize device and it doesn't show up when i type "fastboot devices".
I've already installed "Universal ADB Drivers from here -> http://www.koushikdutta.com/post/universal-adb-driver
What can i do to be able to access phone via fastboot?
Should i remove these drivers and try another driver? If so, which other driver should i install and test with?
I don't have any critical data on the phone, I just want to get it working again so my family members can decide who wants the phone.
Click to expand...
Click to collapse
Uninstall all drivers, reboot PC, install those universal drivers again, reboot PC, connect phone in fastboot mode, try fastboot again.
timmaaa said:
Uninstall all drivers, reboot PC, install those universal drivers again, reboot PC, connect phone in fastboot mode, try fastboot again.
Click to expand...
Click to collapse
That's the order I did stuff in last time I believe. I'll try it again and report back
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 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.
Hey guys!
So, my OnePlus 6 won't boot! My problems started when I tried to flash MIUI 10 port. Idk what I did, and appeared to me "your device is corrupted". But ok, i could boot normally.
Then, I tried to downgrade, as there is a tutorial here in XDA, I was in OOS 9.0.4, then rollback to 5.1.1 (i guess) with appropriate file. Installed it, and rebooted it. But it was taking longer than I expected, and I rebooted it into fastboot mode to flash stock image into fastboot (as there is a tutorial here too). And after this, the ROM install, in my computer everything seems to be ok, but as soon as the CMD reboots it, the message "unlocked bootloader" appears, and then, goes black. Only that. Oh, the notification LED also lights up white!
I connected it into my pc, and i can hear the sound that "something is plugged in", but I can do nothing. I can access fastboot mode normally though.
Tried the tutorial in msm download tool, but had some problems... I mean, it doesn't recognize my phone, but if I put in PowerShell, and type "fastboot devices", it recognizes it.
Could you please help me?
aw4y_ said:
Hey guys!
So, my OnePlus 6 won't boot! My problems started when I tried to flash MIUI 10 port. Idk what I did, and appeared to me "your device is corrupted". But ok, i could boot normally.
Then, I tried to downgrade, as there is a tutorial here in XDA, I was in OOS 9.0.4, then rollback to 5.1.1 (i guess) with appropriate file. Installed it, and rebooted it. But it was taking longer than I expected, and I rebooted it into fastboot mode to flash stock image into fastboot (as there is a tutorial here too). And after this, the ROM install, in my computer everything seems to be ok, but as soon as the CMD reboots it, the message "unlocked bootloader" appears, and then, goes black. Only that. Oh, the notification LED also lights up white!
I connected it into my pc, and i can hear the sound that "something is plugged in", but I can do nothing. I can access fastboot mode normally though.
Tried the tutorial in msm download tool, but had some problems... I mean, it doesn't recognize my phone, but if I put in PowerShell, and type "fastboot devices", it recognizes it.
Could you please help me?
Click to expand...
Click to collapse
Did you installed fastboot adb drivers and oneplus drivers?
Or maybe try to wipe everything in fastboot and then install fastboot stock rom...
Follow the guide of msmdownloadtool, it's the best way to recover your phone, it's a pain the part of install the qualcom driver, but persist
only way to recover stock receovery and back to normal is to install msmdownload tool you can see the videos available on you tube
---------- Post added at 12:36 PM ---------- Previous post was at 12:34 PM ----------
https://drive.google.com/open?id=19CzsxB-ew088fPqrn_KSZ9Wkh5mru6Pe
download from my google drive
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Use this method
siddhrsh said:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Use this method
Click to expand...
Click to collapse
I tried this method before, and find this method to be simpler. If the PC is not recognizing your phone, try powering completely off, then press Volume Up button for at least 5 secs before plugging into the PC and going into the MSM flashing tool. You don't need OnePlus drivers preinstalled for the PC to recognize your phone in this state. From there, just click "Start" on the MSM flashing tool, and wait for your phone to boot back to life. Take note any data inside will be completely wiped clean, like it was flashed from the factory. This YouTube guide here will help you better understand this.
aw4y_ said:
Hey guys!
So, my OnePlus 6 won't boot! My problems started when I tried to flash MIUI 10 port. Idk what I did, and appeared to me "your device is corrupted". But ok, i could boot normally.
Then, I tried to downgrade, as there is a tutorial here in XDA, I was in OOS 9.0.4, then rollback to 5.1.1 (i guess) with appropriate file. Installed it, and rebooted it. But it was taking longer than I expected, and I rebooted it into fastboot mode to flash stock image into fastboot (as there is a tutorial here too). And after this, the ROM install, in my computer everything seems to be ok, but as soon as the CMD reboots it, the message "unlocked bootloader" appears, and then, goes black. Only that. Oh, the notification LED also lights up white!
I connected it into my pc, and i can hear the sound that "something is plugged in", but I can do nothing. I can access fastboot mode normally though.
Tried the tutorial in msm download tool, but had some problems... I mean, it doesn't recognize my phone, but if I put in PowerShell, and type "fastboot devices", it recognizes it.
Could you please help me?
Click to expand...
Click to collapse
If you are able to use fastboot, can you download the latest compatibly TWRP for your device from the official website (twrp.me) get the IMG & ZIP files ( you can use just the image for both, but to keep it simple get both).
Boot into TWRP using the image you just downloaded by running
Code:
fastboot boot <img file name>
Your device should reboot into TWRP.
With your device in TWRPyou should be able to push the file to the phone using ADB push.
Code:
adb push <twrp zip file.zip> /sdcard/
From within TWRP install this zip image. * Now you should have a permanent TWRP recovery, until another OS/recovery flash.
To get the OS on the phone now -
Download the most recent official release for Stable OOS.
Code:
adb push <full os image.zip> /sdcard/
*That should put the file in the root of the SD card folder.
Again use TWRP to install this zip file on to the phone. * This will wipe the TWRP image we had just installed.
To get TWRP again, just flash TWRP after the OS image flash.
I would also suggest, reboot back into TWRP and install the OS & TWRP again as above.
Flashing the OS twice will flash the same version on both Partition A & B. This is essential.
If you find these steps confusing then the simple solution would be to use the MSM downlad tool it does everything for you with a few clicks.
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.