Database Info

[Q] Softbricked. What to do?

After a bad root-attempt it seems that my bootloader is damaged. It happens when I used Oneplus One toolkit 1.6. I need help!
The phone is stuck I a startup loop. I can’t enter recovery mode but I can come in to fastboot mode. When I use the command “fastboot oem device-info” I can see that the bootloader is tempered but not unlocked. It seems that I cant unlock it. Because when I use the command “fastboot oem unluck” the phone just reboot into a new loop. Under “Unlocking the device” stage 7 is says “A disclaimer will display on the device that must be accepted.” That never happens with my phone.
wiki.cyanogenmod.org/w/Install_CM_for_bacon
What can I do!?

gunvald89 said:
After a bad root-attempt it seems that my bootloader is damaged. It happens when I used Oneplus One toolkit 1.6. I need help!
The phone is stuck I a startup loop. I can’t enter recovery mode but I can come in to fastboot mode. When I use the command “fastboot oem device-info” I can see that the bootloader is tempered but not unlocked. It seems that I cant unlock it. Because when I use the command “fastboot oem unluck” the phone just reboot into a new loop. Under “Unlocking the device” stage 7 is says “A disclaimer will display on the device that must be accepted.” That never happens with my phone.
wiki.cyanogenmod.org/w/Install_CM_for_bacon
What can I do!?
Click to expand...
Click to collapse
I see this is you first post here in xda and wish it was a better one than this but there are threads on how to fix your issue. May I suggest in the future you do a little more research prior to doing anything with your expensive phones. Sorry to sound like an ass but I see this happen so often. Now to help you out
1 Download all the fastboot images for your phone and flash each other to restore your phone to stock http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
2 Here is the thread you should of read and used prior to doing anything http://forum.xda-developers.com/showthread.php?t=2788632
Good luck and be careful

playya said:
I see this is you first post here in xda and wish it was a better one than this but there are threads on how to fix your issue. May I suggest in the future you do a little more research prior to doing anything with your expensive phones. Sorry to sound like an ass but I see this happen so often. Now to help you out
1 Download all the fastboot images for your phone and flash each other to restore your phone to stock http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
2 Here is the thread you should of read and used prior to doing anything http://forum.xda-developers.com/showthread.php?t=2788632
Good luck and be careful
Click to expand...
Click to collapse
Yes you are absolutely right. I should have read more before trying to root it. What is done is done and now I try to learn from my misstates and save my phone from the garbage can. All help is very appreciated!
Regarding your links, they were unfortunately not helpful in my case. As every other guide I have read they all assume that the bootloader is unlocked or that is possible to unlock it with the “fastboot oem unluck” command. Which in my case seems impossible/hard to do. The question is why I can’t unlock the bootloader or/and how can it be done?

gunvald89 said:
After a bad root-attempt it seems that my bootloader is damaged. It happens when I used Oneplus One toolkit 1.6. I need help!
Click to expand...
Click to collapse
This is what happens when you use "toolkits".
It's much easier to learn what you should do vs clicking a button or hitting "1" on your keyboard.

mbudden said:
This is what happens when you use "toolkits".
It's much easier to learn what you should do vs clicking a button or hitting "1" on your keyboard.
Click to expand...
Click to collapse
^^^This
While toolkits may seem like they make things easier, they're not always reliable, and they allow the user to skip over some really crucial learning experience from doing things manually.
Transmitted via Bacon

http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909 is a good read.

timmaaa said:
^^^This
While toolkits may seem like they make things easier, they're not always reliable, and they allow the user to skip over some really crucial learning experience from doing things manually.
Transmitted via Bacon
Click to expand...
Click to collapse
To replay to the several message that is wrong to use toolkit. I understand you all and obviously now with results to hand it is obvious that it wasn’t the best thing to do. With my prior phone SGS3 I first did everything the manual way and then I was spoiled with a wonderful toolkit from the xda moderator, mskip, that did everything I did but faster.
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.

gunvald89 said:
To replay to the several message that is wrong to use toolkit. I understand you all and obviously now with results to hand it is obvious that it wasn’t the best thing to do. With my prior phone SGS3 I first did everything the manual way and then I was spoiled with a wonderful toolkit from the xda moderator, mskip, that did everything I did but faster.
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
Click to expand...
Click to collapse
Try reading this thread http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
I'm not entirely sure what is going on in the thread. It says toggle, so maybe you could toggle the tamper bit closes and try to unlock again.
It would also be possible to boot the recovery without loading it on the phone.
This uses the command "fastboot boot recovery.img" rather than flash. Then from there you could use TWRP's recover to to play with stuff.

abcarter said:
Try reading this thread http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
I'm not entirely sure what is going on in the thread. It says toggle, so maybe you could toggle the tamper bit closes and try to unlock again.
It would also be possible to boot the recovery without loading it on the phone.
This uses the command "fastboot boot recovery.img" rather than flash. Then from there you could use TWRP's recover to to play with stuff.
Click to expand...
Click to collapse
Thanks for your replay! I’m looking in to this now

gunvald89 said:
To replay to the several message that is wrong to use toolkit. I understand you all and obviously now with results to hand it is obvious that it wasn’t the best thing to do. With my prior phone SGS3 I first did everything the manual way and then I was spoiled with a wonderful toolkit from the xda moderator, mskip, that did everything I did but faster.
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
Click to expand...
Click to collapse
On further reading, It seems you'd push the zip to reset the tamper flag:
adb push FILENAME.zip /sdcard/
Then you'd boot TWRP
"fastboot boot recover.img"
Then you'd flash the file.
I've not used this personally, I have booted a recovery through adb, which is how I rooted my phone without unlocking the bootloader.

I'm sure it is just a typo, but as you spelled it several times in this thread like this I just have to ask.
You're not actually typing "fastboot oem unluck" when trying to unlock your phone, are you? :silly:
Cause that would kinda explain why you're so unlocky with it.

gunvald89 said:
To replay to the several message that is wrong to use toolkit. I understand you all and obviously now with results to hand it is obvious that it wasn’t the best thing to do. With my prior phone SGS3 I first did everything the manual way and then I was spoiled with a wonderful toolkit from the xda moderator, mskip, that did everything I did but faster.
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
Click to expand...
Click to collapse
Nobody is kicking you when you're down, just providing good information for people to learn from.
Transmitted via Bacon

I really hope that you will find your solution mate...Just read here and there and be confident.
Anyways, this is my second experience with phone rooting (prior my OPO i had a SGS4) and at the moment of rooting the phone i did not trust all these toolkits, i just dont feel safe using commands written by other people.
I guess i was right...
Best of luck!

gunvald89 said:
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
Click to expand...
Click to collapse
Who's kicking you when you're down?
We're just replying just in case someone else comes by this thread and doesn't understand the risks of "toolkits".
Just because something is faster, doesn't mean it's the best route.
Just like the toll on the highway. Faster but gonna cost you in the end.

[armitage] said:
I'm sure it is just a typo, but as you spelled it several times in this thread like this I just have to ask.
You're not actually typing "fastboot oem unluck" when trying to unlock your phone, are you? :silly:
Cause that would kinda explain why you're so unlocky with it.
Click to expand...
Click to collapse
Hehe that right my spelling is quite bad. Unfortunately that was not the problem here even if my spelling in this thread is really bad… Have to start reading more books or something
Following this guide right now
https://forums.oneplus.net/threads/install-adb-drivers-for-windows-8-1-64-bits.51264/

abcarter said:
On further reading, It seems you'd push the zip to reset the tamper flag:
adb push FILENAME.zip /sdcard/
Then you'd boot TWRP
"fastboot boot recover.img"
Then you'd flash the file.
I've not used this personally, I have booted a recovery through adb, which is how I rooted my phone without unlocking the bootloader.
Click to expand...
Click to collapse
Fist of. Thanks for all your help!
I am trying to push it but now it seems that my mobile isn’t correctly connected. When I run adb devices my phone doesn’t come up the list. It has been there before but I believe I have to fix this before anything else

gunvald89 said:
Fist of. Thanks for all your help!
I am trying to push it but now it seems that my mobile isn’t correctly connected. When I run adb devices my phone doesn’t come up the list. It has been there before but I believe I have to fix this before anything else
Click to expand...
Click to collapse
Download this: theyre the drivers for USB from Google.
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Then unpack the file and go into Hardware manager. Right click on your android device connected with USB and select upgrade drivers. Select the folder that you previously unpacked and select ADB drivers.
Do the same but in this case for Fastboot-bootloader driver version if you cant find your fastboot device after rebooting into bootloader via ADB.
It's not fully detailed as a guide but if you're at least a minimum used to manage peripherals in windows you will not have any problem in using the drivers.

Well done....
The first person who bricked the Opo, writing three lines of code...
Dont know how is that possible

gunvald89 said:
Yes you are absolutely right. I should have read more before trying to root it. What is done is done and now I try to learn from my misstates and save my phone from the garbage can. All help is very appreciated!
Regarding your links, they were unfortunately not helpful in my case. As every other guide I have read they all assume that the bootloader is unlocked or that is possible to unlock it with the “fastboot oem unluck” command. Which in my case seems impossible/hard to do. The question is why I can’t unlock the bootloader or/and how can it be done?
Click to expand...
Click to collapse
The guide I provided does not require you to have a unlocked bootloader. This is to restore phone to 100% stock and is done in fastboot with fastboot commands. Are you sure you read it right
Straight from Cyanogen themselves right here
Code:
Instructions:
First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?
Download the file cm-11.0-XNPH25R-bacon-signed-fastboot.zip to your PC from the links below
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update cm-11.0-XNPH25R-bacon-signed-fastboot.zip

DuckMcQUack said:
Download this: theyre the drivers for USB from Google.
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Then unpack the file and go into Hardware manager. Right click on your android device connected with USB and select upgrade drivers. Select the folder that you previously unpacked and select ADB drivers.
Do the same but in this case for Fastboot-bootloader driver version if you cant find your fastboot device after rebooting into bootloader via ADB.
It's not fully detailed as a guide but if you're at least a minimum used to manage peripherals in windows you will not have any problem in using the drivers.
Click to expand...
Click to collapse
Thanks your suggestion. I tried that and is just says that I have the same driver installed. Also tried to uninstall every driver that has anything to do with google android and phones and then reinstall. I also tied to install from my Android SDK folder but I got the same message.
playya said:
The guide I provided does not require you to have a unlocked bootloader. This is to restore phone to 100% stock and is done in fastboot with fastboot commands. Are you sure you read it right
Straight from Cyanogen themselves right here
Code:
Instructions:
First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?
Download the file cm-11.0-XNPH25R-bacon-signed-fastboot.zip to your PC from the links below
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update cm-11.0-XNPH25R-bacon-signed-fastboot.zip
Click to expand...
Click to collapse
Oh nice. I will try that after i get the drivers up and running!

Softbricked my nexus 5? Any help?

So i'm not super competent in adb and what not, but just competent to use wuggs toolkit. I went to google's website to download lollipop 5.0 for my nexus 5. Then i set the phone back to stock, flash 5.0 and its running well. Then i go back in to settings, developer options, and to root my nexus 5 and install TWRP on it through wuggs. Now it has twrp, but will not boot up past the google name with the unlock. I only have the fastboot page and TWRP. The big kicker here is that my pc says does not recognize device and it flickers back and forth with connection every two seconds to my PC. When i go into device manager it shows android device though. So well hey i figure since i have a softbricked nexus i'll just click the button for it and reset. Well it wont do it, it pulls up fastboot.exe goes through a few commands, some saying it failed then it stops and windows tells me to close fastboot.exe
Any help from the very respected XDA?

oh, gawd.. fastbooting a factory img would have been so much faster. sorry, toolkit, i cant help you with it.

hayden55 said:
So i'm not super competent in adb
Click to expand...
Click to collapse
There's your answer right there. That's how ppl like Op brick their devices everyday

Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.

jayRokk said:
Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.
Click to expand...
Click to collapse
aww but i really wanted a hand hold.

hayden55 said:
aww but i really wanted a hand hold.
Click to expand...
Click to collapse
here is an extra long :highfive: for your hand holding

chapelfreak said:
here is an extra long :highfive: for your hand holding
Click to expand...
Click to collapse
Hey thanks bud! Problem was it couldnt connect to the computer for more than 5 seconds...
SOO.... i messed with mounting an OTG jump drive and it had my old TWRP back with android 4.4.4. IT Worked!
p.s. i tried just mounting system data etc... the turn on mtp connection button and it Would show up better than just plugging in but couldnt download anything big. and no adb connection

dicecuber said:
There's your answer right there. That's how ppl like Op brick their devices everyday
Click to expand...
Click to collapse
i do not need your input if you aren't going to contribute to the problem just antagonize the op

Current problem at hand: phone now will only connect to pc for 5 seconds at a time. What could do this and how do I reflash to normal?

Still using toolkits?

hayden55 said:
i do not need your input if you aren't going to contribute to the problem just antagonize the op
Click to expand...
Click to collapse
It's a suggestion

Disclaimer: I use OS X/Terminal to fix these things normally and honestly found that after the initial learning curve, it's easier than using Windows or Wugfresh. I'm not a developer, just a hobbyist user.
Make sure you're using an OEM cable to connect to the computer if you're getting dropouts. Also, attempt to uninstall and reinstall OEM drivers (I believe Wugfresh has instructions on how to do this) for Windows.
If you have confirmed that you have TWRP 2.8.1.0 installed, try to boot to TWRP --> ADB Sideload. Connect phone to computer, open Terminal/Console and type the command 'adb devices' (without the apostrophes. I haven't used Windows since I stop using Wugfresh, so the command probably differs). If the device can be seen through this, you should be able to return to the bootloader and start issuing fastboot commands to flash the image.
Let me know how I can help!

Retard in need of Help. Weird problem with recovery of my OPO

Alright have read the first 30 pages of comments on http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 and I starting to feel like I'm dumber then a brick.
Okay here is my problem: Just bought a used OPO with the classic boot logo loop error. I have tried to just simply Factory reset it (both Full and wipe cache) and it gives me E: failed to mount /cache (invalid argument) error. Then I googled it and most of the results said that I need to simply reinstall the software with adb. Okay got adb up and running and installed my phones drivers and booted into fastboot.
Then when I try to install it gave me "device not unlocked" error... Fine googled it tried "fastboot oem unlock" and it was still not unlocked.
Googled that and read the posts about tampered bits and after running the "fastboot oem device-info" It gives me "Device tampering: true" "Device unlocked: false" so damn.
Then I read the posts and tried to sideload OnePlusOne-BootUnlocker.zip (used the "apply update" in cyanogen recovery to get the ADB sideload) but it comes up with E: failed to mount /cache (invalid argument) and fails all the other things.
Have tried "fastboot boot recovery recovery.img" but that have the have a unlocked bootloader.
I'm abit lost ATM because I discovered that wile I can get fastboot and Sideload (from update) to show my device the normal adb can't see it when just being in the menu.
So if one of you could point me in the right way or if you got time guide me then I would be greatfull.
Regards Magnus/Mjallo
PS. Please don't burn me for asking

Can post pictures of the screen if it is needed

@Mjallo google "Bacon Toolkit."
Does literally all the things you are trying to do in a matter of a few clicks. Walks you through everything step by step.

h11wiscan said:
@Mjallo google "Bacon Toolkit."
Does literally all the things you are trying to do in a matter of a few clicks. Walks you through everything step by step.
Click to expand...
Click to collapse
Okay have played around with the program abit more and all it does is that same as me doing it in CMD.
I still have the problem with Device tampering and device unlock state. Where is the tools for fixing that?
Have tried to fix the cache but it still make the invalid argument.

might could fastboot flash official images to get the phone back to normal. you dont have to have bootloader unlocked to flash official boot images. you can go here https://cyngn.com/support and download the cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip (scroll down to opo section) and/or go to http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and get the download and follow directions in that post to flash phone

Mjallo said:
Okay have played around with the program abit more and all it does is that same as me doing it in CMD.
I still have the problem with Device tampering and device unlock state. Where is the tools for fixing that?
Have tried to fix the cache but it still make the invalid argument.
Click to expand...
Click to collapse
Yeah idk then. Need more screenshots or info to help. Could be a million things.
-Are you using OEM USB cable?
-Did you install ALL drivers properly?
-Have you rebooted since installing ALL drivers?
-Have you tried using bacon toolkit on another computer? Sometimes simply switching computers can help.
-Did you try resetting phone to factory state using ABD/Bacon Toolkit?
-In Bacon Toolkit did you select the proper firmware and software version before attempting to use the program?
A few questions to ask yourself before we go further.

kenboyles72 said:
might could fastboot flash official images to get the phone back to normal. you dont have to have bootloader unlocked to flash official boot images. you can go here https://cyngn.com/support and download the cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip (scroll down to opo section) and/or go to http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and get the download and follow directions in that post to flash phone
Click to expand...
Click to collapse
Have tried with both Normal Cyanogen and CyanogenMOD (that is what the bootlogo says on this phone) and both of them give the Device not unlocked error both on screen and in CMD

h11wiscan said:
Yeah idk then. Need more screenshots or info to help. Could be a million things.
-Are you using OEM USB cable?
-Did you install ALL drivers properly?
-Have you rebooted since installing ALL drivers?
-Have you tried using bacon toolkit on another computer? Sometimes simply switching computers can help.
-Did you try resetting phone to factory state using ABD/Bacon Toolkit?
-In Bacon Toolkit did you select the proper firmware and software version before attempting to use the program?
A few questions to ask yourself before we go further.
Click to expand...
Click to collapse
Okay I'm using the OEM cable (have tried both the one I got with this phone and the one I got with my Orginal OPO)
Have gone through the steps checking my drivers and they should be working and A OKAY, reboot and all.
Don't have access to another pc ATM but will look after the option.
Have tried all the option in Bacon toolkit to reset the phone to factory setting and non is working, tried to then use the recovery option to maybe get it to work that way but no dice. Have also tried sideloading both with Toolkit and with CMD and no luck their either. Took a picture of the screen when the sideload tries to work.
http://imgur.com/6L74N6J
The Firmware question is up in the air because I have never got it booted so I have no clue what firmware it has only hint that the boot screen is Cyanogen MOD READY and not just Cyanogen like on my other OPO
Hope it helps finding the problem

I super hard bricked my phone a while back, even lost a partition. I was finally able to get it back by flashing colorOS. took a few tries to get the program to recognize my phone, but finally got it flashed. The phone never booted all the way up with colorOs, but it fixed what needed fixed and I was then able to fastboot flash CM13, unlock bootloader and go from there. don't have that thread bookmarked, but it's here in the forums.
Edit: found thread http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

kenboyles72 said:
I super hard bricked my phone a while back, even lost a partition. I was finally able to get it back by flashing colorOS. took a few tries to get the program to recognize my phone, but finally got it flashed. The phone never booted all the way up with colorOs, but it fixed what needed fixed and I was then able to fastboot flash CM13, unlock bootloader and go from there. don't have that thread bookmarked, but it's here in the forums.
Edit: found thread http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
It sadly did not fix the problem it gives this problem and just stops working (need to close it in taskmanger) http://imgur.com/w1zOQFU.
Well the quest goes on

Mjallo said:
It sadly did not fix the problem it gives this problem and just stops working (need to close it in taskmanger) http://imgur.com/w1zOQFU.
Well the quest goes on
Click to expand...
Click to collapse
when you run the program, one of the columns should have a few random characters and "com" in it. if you dont see com in any of the columns, then the program is not seeing you phone. if you do see com, the click on that row and press start and it will show files being written in green showing progress. if phone is not being seen, follow that guide to the letter, specially if this is on a win7/8 machine. i will get my lappy out in a bit and give a few screenies on what it should look like, i wont actually flash my phone though.

kenboyles72 said:
when you run the program, one of the columns should have a few random characters and "com" in it. if you dont see com in any of the columns, then the program is not seeing you phone. if you do see com, the click on that row and press start and it will show files being written in green showing progress. if phone is not being seen, follow that guide to the letter, specially if this is on a win7/8 machine. i will get my lappy out in a bit and give a few screenies on what it should look like, i wont actually flash my phone though.
Click to expand...
Click to collapse
It sees it (you can see it in COM5 in the picture) and when the progress bar shows it just make a little green tip then just stops showing

are you running the program as administrator? right click on exe and select run as administrator? other than that, don't see why it's not flashing and I'm out of ideas, sorry.

TWRP Bootloop [SOLVED]

Hi all
I've had my Tf700 for a long time now. I've had it unlocked and rooted and had CROMBi before trying OMNIRom and then finally moved to KatKiss7.1 last year. All was well until today when, having enabled screen rotation, the background went a strange looking pink colour and would flicker back and forth to black. Then the WiFi started to misbehave so I rebooted it. But instead of rebooting, it just went into a bootloop.
I used power + VolumeDown to access the recovery mode and tried to get to TWRP (2.8.7.4) via the RCK option but without any luck. At that stage, all it was doing was resuming the loop. I tried booting into Android but got the same result. I tried for TWRP a few times and it always failed.
My next move was the Wipe Data option. Turned out to be a bad one. I hadn't done anything with the device in so long that I forgot about the "don't use the Wipe Data" instruction and I didn't read up before doing anything else. The device rebooted itself and then appeared to be going into TWRP - I could see the logo coming up - but my hope was short-lived as the device then proceeded to go into a bootloop where it displays the TWRP splash screen, but then reboots.
About the only thing I seem to be able to do is access APX, but I didn't know about APX or NVFlash until today when I started trying to read everything to do with anything that might help.
I run Linux on my PCs and have installed ADB so that I can try to use fastboot or adb. Neither seem to work in that nothing shows up when issuing either "fastboot devices" or "adb devices". But on a more basic level, nothing shows up in lsusb. The mouse is listed, as is my card-reader, but the TF700 isn't. The thing is, I haven't connected the device to a PC in a long time and the last time, it was windows, so I can't say for sure that the PC is definitely seeing it or not.
And so to my questions:
1) Should the TF700 show up in Linux using the lsusb command when connected via the cable. (maybe I need a new cable? maybe I need Windows )
2) If I got a new cable, is it likely that I'd be able to push a recovery image back to the device to allow me to start to rebuild?
3) When APX is available, is it possible to transplant someone elses NVFlash backups, or whatever is just enough to get it running again so that I can re-install recovery and maybe reload an earlier TWRP backup?
(I've seen instructions for the TF201, but can't see anything for the TF700)
Any help would be really appreciated.
With thanks,
Scouser27

I don't like the sound of this. This "background went a strange looking pink colour and would flicker back and forth to black" business makes me suspect a hardware failure. Maybe something got fried on the board - don't know.
1) Should the TF700 show up in Linux using the lsusb command when connected via the cable. (maybe I need a new cable? maybe I need Windows )
Click to expand...
Click to collapse
Yes, it should, something like this:
Code:
...
Bus 003 Device 009: ID 0bda:57af Realtek Semiconductor Corp.
Bus 003 Device 016: ID 0b05:4d01 ASUSTek Computer, Inc. Transformer Prime TF201 (debug mode)
Windows is not going to help you. If it doesn't connect in Linux it definitely won't in Windows....
2) If I got a new cable, is it likely that I'd be able to push a recovery image back to the device to allow me to start to rebuild?
Click to expand...
Click to collapse
Not unless you get a connection in either fastboot or adb
3) When APX is available, is it possible to transplant someone elses NVFlash backups, or whatever is just enough to get it running again so that I can re-install recovery and maybe reload an earlier TWRP backup? (I've seen instructions for the TF201, but can't see anything for the TF700)
Click to expand...
Click to collapse
No, nvflash files are device specific
If you cannot get it to boot into fastboot or get an adb connection - however briefly - it is a brick.
Install Hardinfo in Linux - it is very similar to Windows Device Manager - and open the USB page. Then reboot into TWRP. If you are lucky you may get a few seconds before TWRP loops where the PC has an adb connection and sees the tablet. If that works, follow this: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Still a tiny chance but better than nothing.
If bootit.ko kicks it into the bootloader and you get fastboot you can reflash the recovery, format data in fastboot and all that good stuff.
But my guess is: No dice
Try it anyway - good practice.
I still have a couple of TF700 lying around, one with a so so screen. If you want it, you can have it for the cost of shipping. You can either swap the screens or m-boards...
PM me if you want to go that route.
Good luck

Update
Thought I'd post something in case it's useful to anyone having similar trouble to what I described. This applies to my instance of TWRP booting in a loop and never exiting until the battery was flat.
Ensure your cable is working correctly.
If it's not, you won't see anything on your pc. (I use linux and nothing was showing up in lsusb or dmesg)
If this is the case, borrow a cable if you can or invest in one. I did - best 5 Euro ever.
Get the bootit.ko file that's mentioned in a few places such as here.
While you're getting that file, read the instructions there a few times and also have a look at the details over at this page (same one @berndblb links above)
Connect your tablet and boot it. As soon as you see the TWRP logo, it's time to try to run commands.
If you use linux, you can issue all commands at once like this:
Code:
sudo adb devices; sudo adb push bootit.ko / ; sudo adb shell insmod bootit.ko
Note the "/" after "push bootit.ko" - that's not a typo. If you leave it out, it won't work.
I don't know if sudo was strictly needed, but I wanted it to work and it didn't cause any trouble.
I haven't used Windows in a long time so I don't remember if you can do the same, but you could put the various adb commands into a batch file and run that. Don't forget to drop the sudo.
If it has worked, the tablet will reboot. You should now be able to get back to the bootloader.
Follow the fastboot erase instructions at this thread.
I found it useful to write the commands as
Code:
fastboot -i 0x0b05 erase boot
The last version of TWRP that I was using was KANG TWRP
I downloaded that, extracted the blob file and flashed it:
Code:
fastboot -i 0x0b05 flash recovery boot.blob
I used that because I wanted to install TimDuru's KatKiss 7, but you could presumably install whatever Recovery you wanted and proceed as normal.
And that's it. I flashed KatKiss7 and SU and all was well again:laugh:
Big thanks go to @berndblb for his help on this - If, like me, you didn't read his posts before, you really need to read them now. And maybe, just maybe, you'll be able to recover.
Thanks to all other contributors whose post's I've linked or whose work contributes to this solution - you've all just saved me having to buy a new tablet. Nice one!:victory:

OP7 Pro Fastboot Bootloop! [HELP]

This may be a simple solution, but I am completely puzzled on how to fix this.
SO i recently rooted my phone & used the twrp "twrp-3.3.1-4-guacamole". Installed magisk via that twrp and continued with my day.
I accidentally got a virus by trying to get a full free vpn, me being a terrible pirate, i accidentally got a virus! Silly me.
It was annoying me and I decided to factory reset my phone... not via twrp. I remembered after I clicked "Reset all" on oxygenos that it's not the way how to do it with a root device, and well.. it didn't exactly work.
Every time I power/reboot the phone it just brings me to the fastboot menu of "START", "POWER OFF", "RECOVERY MODE", & "RESTART BOOT LOADER". I thought since TWP is recovery mode I try to access that... no luck, it just brings me back to that fastboot menu. I tried going on CMD via adb by saying "fastboot flash boot twrp-3.3.1-4-guacamole.img". It will say it's finished and successful, but when i reboot and try to access recovery mode it just does not work.
TL;DR: Think I bricked my phone, there is no OS installed and I can only access the fastboot.
Any help? Much appreciated

https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691

trapcoder666 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
Thank you for the guap recovery as i didn't know it existed. However, what are the steps? when i go on the MSM download tool it doesn't detect my phone.
that being said, i can't access any of my files through my pc using fast boot. on MSM it's just saying "waiting for device" even when plugged in so thats annoying.

trapcoder666 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
I downloaded the one you sent, and after a while as my internet is bad. It still does not work.
Whenever I try to install the qualcomm drivers it never shows up, and when i try and boot it up so the gual recover detects my phone it never works. It's still saying "waiting for device".
Does anyone know how to fix this? it's doing my head in that it's not as easy as it should be.

MOweenSalah said:
I downloaded the one you sent, and after a while as my internet is bad. It still does not work.
Whenever I try to install the qualcomm drivers it never shows up, and when i try and boot it up so the gual recover detects my phone it never works. It's still saying "waiting for device".
Does anyone know how to fix this? it's doing my head in that it's not as easy as it should be.
Click to expand...
Click to collapse
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
A few things to note:
- Works perfectly fine for unbricking GM1917 modeled OnePlus 7 Pros.
- Use the original cable and try to plug it into a USB 2.0 port. I've found that this is the most ideal condition.
- Make sure your device is charged up. If you can't see how much charge it has, leave it charged via the 30W warp charger for 40 minutes and that should be good enough.
- In the L2 drivers folder found in the archive, navigate to the 32 or 64 folder depending on your system's architecture, and click on the file that ends in the extension ".cat". Then, click "view signature", then "View certificate", then "Install." This is IMPORTANT.
- Then, make sure your device is powered OFF, then, plug in the USB-A side of the cable (big head) into your computer and do NOT connect the USB-C (small head) into your phone yet.
- Hold down Volume up AND volume down for five seconds, and while you're continuing to hold, plug the USB-C side into your phone. The drivers should automatically download, and you should see a "Qualcomm QD loader" device in Device Manager. If you see an exclamation mark or you don't see this, you are doing it wrong and you need to repeat the above steps.
- Open up MSMTool.exe as an administrator and click 'start' only. Should take a few minutes, but you will have a good-as-new OnePlus 7 Pro.
Click to expand...
Click to collapse

Krsmqn said:
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
Click to expand...
Click to collapse
I did yes, i pressed all buttons and the power button for 5 seconds and plugged my charger in. Then after that went on the MSM tool and it went straight to the fastboot. I really don't know but it loves this fastboot tool haha

Krsmqn said:
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
Click to expand...
Click to collapse
Add: I made a video showing what I mean with the fastboot. Basically if i do anything with the phone fastboot it will just go back to the menu (sorry for bad quality)
https://www.youtube.com/watch?v=jU8a6kDXNNs&feature=youtu.be

MOweenSalah said:
Add: I made a video showing what I mean with the fastboot. Basically if i do anything with the phone fastboot it will just go back to the menu (sorry for bad quality)
&feature=youtu.be
Click to expand...
Click to collapse
It's one of those things where if someone was there with you, it'd likely get figured out. I've seen this kind of situation hundreds of times on XDA, and with all due respect, the problem is most always at the hands of the user. These phones are cookie cutter made, so there's nothing different (besides individual variants) that would make thee tools not function correctly, unless it's operator error. But that's not set in stone. Just don't give up. Try setting up your camera for an overhead view. I couldn't tell if you were plugging in your cord. And it seemed to reboot, instead of power off. Repeat the steps carefully, and see if you can achieve better results.
Don't give up! We're here for you ?

Make sure phone is powered off before plugging it in. Launch msm tool, Press the vol up and down key for a few seconds then plug in.
Edit : make sure your drivers are up to date too.

I don't know about msm tools never tried it but I know your situation.
Don't do fastboot flash boot twrp-3.3.1-4-guacamole.img
Remove the word flash. You are supposed to boot into twrp then flash the zip file to the phone.
look at this

Command in Fastboot mode is:
Fastboot boot "name of the recovery".img. Phone should boot to twrp. Then flash twrp.zip
or try Fastboot roms:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Choose the one for youre phone (region)
MSM tool it's the last option.

Can't you just switch slots from fastboot or did you mess up both?

trapcoder666 said:
Make sure phone is powered off before plugging it in. Launch msm tool, Press the vol up and down key for a few seconds then plug in.
Edit : make sure your drivers are up to date too.
Click to expand...
Click to collapse
Firstly I'm terribly sorry for no response (same goes to everyone else looking into this matter for me. THANK YOU!)
However, I have done this multiple times in the past and it instantly goes back to boot menu. it sucks :/

IronSingh said:
I don't know about msm tools never tried it but I know your situation.
Don't do fastboot flash boot twrp-3.3.1-4-guacamole.img
Remove the word flash. You are supposed to boot into twrp then flash the zip file to the phone.
look at this
Click to expand...
Click to collapse
Okay. I shall go and look into this situation when I receive my phone back (going to explain that in a later quote)

larsdennert said:
Can't you just switch slots from fastboot or did you mess up both?
Click to expand...
Click to collapse
If i'm honest with you.. i'm not sure in the slightest. My only assumption is no because the only thing I can access is only the fastboot. if i attempt to go into recovery mode it will go back to fastboot. when I flash twrp it will flash but it won't boot into it. It's confusing as hell.
Just to add to this whole situation:
Since I have no idea and just wanted it fixed in the day; i was willingly to give money for this phone to be fixed, but thanks to the person, he just made it a slower process by doing things i've already done.. going to pick the phone back up in an hour of this message.
I haven't used the fastboot boot twrp cmd yet, but from how everything else has been so far i feel like that won't work, but i will update everyone on that situation.
Just to add additional things that I may have not mentioned in the past will be below:
- Whenever i type in "ADB Devices" in cmd, it will not show up with anything. However, when I type in "fastboot devices" it shows it's serial and in "fastboot". It will only show as fastboot and i can't access the phone via file explorer in windows.
When i say "ADB Devices" it says *devices attached* and will show none of my phones details, but when i say fastboot devices it will then show the devices.
^ what i said above means I can't use the guap recover, or anything which means the phone has to be detected in windows, because other than fastboot, it won't work at all.
- So far I can't access twrp as a whole, so if anyone knows how to give me a guide on how to install it from where I am at, that would be amazing (if not, i'll try and reiterate what to do with the one given from a previous comment, so thank you )
- There was one time I was allowed in TWRP but i completely forgot how i entered it (so i can't explain), So i feel like there is hope in that aspect. I feel like i entered something via cmd so maybe there's a way?
In terms of hardware my phone is completely fine, there's not a single problem other than the software being a pain in the ***!!
if anyone can just spew out a bunch of help in different explanations it means the world because so far all I can see is that I wasted about £600 on an amazing phone because of dumb *** haha.
Thank you to everyone who has helped, and is helping

From your comments, you are not familiar with how Android functions. Not knowing the difference between adb and fastboot is an indicator that you should just endeavour to have a stock phone until you understand whats going one. It's also hard for people to help as no one has hands on and can see what is broken. Everyone here will be working blind like trying to fix your car for you from across the country.
Start the phone into fastboot and connect it to a pc. From a pc command prompt in your fastboot directory enter the command:
fastboot getvar current-slot
If the current slot is A then:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
then fastboot reboot and see if you boot into the other slot.
Not knowing what phone you have makes it even tougher but I suspect you will have to reflash a clean complete rom via fastboot.
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop

larsdennert said:
From your comments, you are not familiar with how Android functions. Not knowing the difference between adb and fastboot is an indicator that you should just endeavour to have a stock phone until you understand whats going one. It's also hard for people to help as no one has hands on and can see what is broken. Everyone here will be working blind like trying to fix your car for you from across the country.
Start the phone into fastboot and connect it to a pc. From a pc command prompt in your fastboot directory enter the command:
fastboot getvar current-slot
If the current slot is A then:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
then fastboot reboot and see if you boot into the other slot.
Not knowing what phone you have makes it even tougher but I suspect you will have to reflash a clean complete rom via fastboot.
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
Click to expand...
Click to collapse
I do appreciate the help. If i'm honest with you the only reason I did this is to increase my data speeds (which from look of things is outdated now), and a longer battery life. I don't know much about rooting/jailbreaking but believe me that I have been in the scene for years, but not even knowing everything haha!
that being said.. i'm in twrp! thank you so much mate, i'll try and go and install the rom now. thank you!

Now install the zip twrp

Thankfully.. IT'S FIXED!
I didn't have to install twrp again or any of that. I simply changed the slot from A to B and pressed all buttons when it was showing the "! Your decide is unlocked" orange/black screen.
I had msm tools up and it detected and instantly installed the OS to the latest one and boom. It works again!
I got to thank everyone for helping me because without you people I wouldn't of been able to fix it. I looked everywhere and no help anywhere as I feel like it's pretty dumb to do what I did haha!
Thank you again people!

Oh you gave up on root?
You are supposed to read the instructions and follow them to the letter. When I read your post I realized you tried to install twrp like you would pre Oreo but it changed you have to boot into twrp then install it via zip file.
Anyways just remember that for next time.