Database Info

B70 bricked - is there no way out?

Been modding android devices since the G1 but never got stuck like this before. Already spent hours of searching and googling but couldn't find any definite answer.
My B70 got bricked when using a program to boot into recovery.
Is there any way out or should I just throw it away?
I have a feeling that the device is looking for a recovery on internal SD card and fails. I can see the unit as ADB unit but when trying to connect it says device is offline both in normal boot or in recovery boot.
Been trying putting stock roms on external SD but it never runs it.
Has anyone solved this problem?

Check your SBK version and try to NVFlash
Try to boot recovery/apx wipe permissions /data if possible
post questions in Q&A not Dev

After a lot of examination it has been decided that you have posted this in the wrong section and we shall place it where it should be. Please make sure you post correctly next time.

Like mentioned already, some B70 are SBKv1 meaning nvflashable.
What app did you use to get into recovery causing the "brick"
Can you still get into cwm recovery, ect.
you still have hope if ADB can see it, try to update your driver.
If it work use ADB to push the file you need.

Sorry for wrong thread.
I probably have SBK2 (how to check) because usb just disconnects as soon as I try to run any nvflash stuff.
I also believe that ADB could be the saviour but it says offline. So this could be due to driver issue? Interesting, I shall try on a 32 bit computer.
If I suceed to connect through ADB, can I then flash CWM recovery?

The app I used to get into recovery was just a random boot into recovery app. It worked many times before. I don't think taht app caused this, maybe the recovery files where deleted?

df9517 said:
Sorry for wrong thread.
I probably have SBK2 (how to check) because usb just disconnects as soon as I try to run any nvflash stuff.
I also believe that ADB could be the saviour but it says offline. So this could be due to driver issue? Interesting, I shall try on a 32 bit computer.
If I suceed to connect through ADB, can I then flash CWM recovery?
Click to expand...
Click to collapse
You can use SBKdetect to check your SBK version (linux)
Did you have CWM before? Are you rooted?
What is your tablet doing right now? Stuck at the start up screen?

My tablet was previously running rooted ICS WW .11 with CWM.
Now its just stuck at the first boot image. I can go into same image where it tries to run recovery image by holding vol down. I guess it is standard brick.

Not getting anywhere with ADB, device is offline

hmm.. can you cold boot? just hold vol-down and wait?

df9517 said:
Not getting anywhere with ADB, device is offline
Click to expand...
Click to collapse
Search on here for the universal naked driver. Try that or sometime if you can try a different usb port.

Can you get into CWM Manually?
Hold VOL DOWN and POWER for about 10-12 seconds until some small text appears.
Quickly (within 5 seconds) release both buttons and hit VOL UP to enter RCK (Recovery).
If you can get into CWM this way you should be able to clear some caches and see if it will boot. If need be, you may be able to flash a new ROM if need be.

I only got the naked ADB drivers to work. The real ASUS ones does not work. Only tries 64 bit though.
Of course I tried to go into recovery manually.
Actually I now remember that just before this happened I updated CWM through the clockwork app. Probably updated to a version that does not work.

Since you have ADB working, download a CWM flashable .zip from your favorite recovery thread and extract the recoveryblob.
adb push it to /temp/dd or something similar, then run adb shell, su, and (you will need root/busybox on here) dd if=/your/blob/here of=/dev/block/mmcblk0p4.
after running that, run reboot, you should see a blue line and be able to get into a good CWM recovery. never use rom manager.

Thing O doom.
It always says my device is offline using ADB. I have only got naked driver to work.
But now I saw the NVflash for B70+ devices in your post. I will try that tonight.
I have not given up.

Yes, that is probably your only hope if you can't get ADB working, and it just came out! Lucky day

Yes, thank you all!! Finally NVflash for B70+ devices saved my day. Reflashed original ROM.

Bricked and Stuck

Hello, first time posted, long time browser...
So, I have a bricked (or almost totally bricked) LG G2X. Here is what I did:
I had flashed the Hellfire Sandwich 1.9 rom and was just fine...until my phone started turning off randomly. After reading somewhere here that I should nullify my phone and the re-flash the rom in order to fix my issue.
So, I backed up my data and downloaded the Aroma Nullifier from Volk (thanks for all you do). I booted to recovery and ran the Nullifier. Once the Nullifier had stopped, still while in Recovery, I tried to access my sdcard to re-flash my Rom...well, I couldn't access my SD card. Furthermore, I couldn't unmount the SD or mount the USB Storage.
Here comes the big mistake:
So, as I was doing some research about how to proceed, my USB cord wiggled out of the phone and my phone lost power. Now, since I had read from Volk not to let that happen, I knew I was in trouble.
At this point, I can only load into the LG Boot Screen and my computer loads drivers for "Asus Android Device" (I have the Asus Transformer Prime Tablet) and under that title "Asus Android Bootloader Interface". No APX, No USB Controller....no other communication.
Last little note, I took the phone to the Tmobile store on a hunch one of the guys who works there had some experience (which he did), and while he was trying to boot into recovery from battery power (something I have been unable to do) he got the USB communication interface...something like "S/W Do not disconnect".... Since then, I have not been able to reproduce that interface.
I am at the end of my abilities...I haven't seen anything that addresses this particular problem though I have tried a bunch of solutions without success. I have looked all through XDA forums, but if there is one I missed, please let me know.
Any thoughts would be very helpful.
Kickingcans

If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:

Thanks much...but...
therealnexion said:
If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:
Click to expand...
Click to collapse
Thanks for the thoughts. I will try that all again, but I have tried nvflash and tried updating APX drivers. My computer only recognizes the phone as an "Android Bootloader Interface". When I try to manually update/change the drivers for the "Android Device", there is a problem with 64-Bit operating System (Windows 7 Home Premium). I was going to try to boot the computer in Safe Mode, but I don't know if that will help.
I haven't been able to communicate with the phone, and only saw the S/W Upgrade screen once and that was in the Tmobile store without access to my computer.
I am going to try those suggested steps again. Thanks again.
Leigh

Got it going....
THANKS SO MUCH. I knew I was missing something stupid. I kept reading the nvflash instructions and pressing the Power and Volume Down button instead of Volume Up and Down.
Things are going again. Thanks so much.
Kickingcans

[Q] [HELP NEEDED] Asus TF101 Stuck on splash screen ADB doesn't work!

Right, I searched on numerous pages on these wonderful forums, but couldn't quite find what I was looking for. So I'll try my luck here. I'll describe my problem.
My TF101 was rooted using the CWM recovery. After doing more research I found out I shouldn't be doing this. But, unfortunately the damage has already been done. After several succesful ROM installations I wasn't quite happy with, I tried one last CM10 install. That's when it all went to ****. My TF101 has been stuck on the Eee Pad splash screen for nearly 2 months now.
Normally when going into the recovery mode I can simply select install from SD card and install a new rom. Now it can't seem to mount and displays E:Can't mount \SD card or whatever.
Further on, I tried using the ADB tools to manually restore system files. Without luck. After which I tried to install the naked USB drivers using http://forum.xda-developers.com/showthread.php?t=1426502. Without luck as well. I simply ran out of ideas.
The thing is, in Device manager I do see a device called Android. But, for some reason I can't seem to install any drivers for it. I guesse this would be the first step towards getting it back to work? Or perhaps I should just get it fixed at the computer store?
Any sugestions would be more than welcome!

Easy Flasher will get you back to stock as long as you can access APX. You will lose all data however.

1st mistake read forum before you do something, coz you would have learnt abt CWM issues, anyway thatsvan old story
You got Two options, find an flash able twrp.zip and flash it using current recovery if its still working otherwise as the other guy says easyflasher
To use easy flash you need
Easy flash software from forum
Universal naked driver installed
Asus firmware and PATIENCE
Follow the steps given in the forum and you should get back a tablet running stock rom, then if you want then use easy flash to root your device again but this time use TWRP recovery.....
Sent from my Transformer TF101 using xda app-developers app

Right, so far I've done everything I could find. I have installed the naked ADB files and thus was able to make a connection through USB. However, I wasn't able to push any files onto the tablet through ADB commands.
I entered the (what I assumed to be) APX mode and tried to use EasyFlasher. It seemed to have worked, because a DOS screen asked me whether or not I wanted to overwrite several files. After ending the procedure I rebooted my tablet. And guesse what: CWM is still there and the tab is still stuck on the Splash screen. Also the internal SD still can't be mounted.
What am I doing wrong. I'm slowly but surely going mad here....

hmmm, easyflasher should not prompt you to overwrite anything, it should just wipe it clean. The only prompt is when you select SBK1 or SBK2.
Can you post screenshots? It'd help us understand what exactly is going on...

Lethe6 said:
hmmm, easyflasher should not prompt you to overwrite anything, it should just wipe it clean. The only prompt is when you select SBK1 or SBK2.
Can you post screenshots? It'd help us understand what exactly is going on...
Click to expand...
Click to collapse
Right. Apparently I didn't put it in APX mode correctly. Windows asked me to install APX drivers. Which I now did. I then (I assume) was able to install the new recovery. The screen says !!!!phone update succes!!!!!. As we speak I am trying to install the stock ROM. Fingers crossed.....

AlbertGJBos said:
Right. Apparently I didn't put it in APX mode correctly. Windows asked me to install APX drivers. Which I now did. I then (I assume) was able to install the new recovery. The screen says !!!!phone update succes!!!!!. As we speak I am trying to install the stock ROM. Fingers crossed.....
Click to expand...
Click to collapse
I'll just sum up what I've been doing so far, because it still ain't working for me....
1) Put the TF101 in APX mode using POWER + VOLUME UP
2) Started up EasyFlasher 0.8.3 and selected "Flash Asus stock zip / Unbrick"
3) When prompted "file ..\temp\META-INF\MANIFEST.MF" already exists I selected "A(u)to rename all"
4) And then starts doing it's thing
5) Stuck at creating and formatting 15 partitions with several three letter codes.
I've ran the program three times now, but without luck. Any sugestions?~
[EDIT]Alright, managed to get it to work! Ended the tasks in through task manager about 4 times, but the 5th time was a charm. Exactly work as said. All thanks to EasyFlasher![/EDIT]

Help pls!!!! 20$ in it!!!

New that would get attention. Is there anyone out there that is dedicated to helping for a lil cabbage? I have this tf101 transformer that i cant seem to get rooted. Why is it so gosh dern hard to root one? I have followed all methods and tryed diff methods. The emulator runs but root is still not acheived. I have not bricked it. Its running ics. Ive rooted phones and tablets since the evo 4g..... this garbage a$$ tablet is without a doubt one of the worst i have ever had the displeasure of owning. Nexus 7,,,samsung note 1,,,note 2,,,,,,note 10.1,,,,,htc first,,,,evo 4g,,,,blackberry tour....AND NONE HAVE EVER BEEN THIS HARD TO ROOT. I wont buy another asus anything.
So,if som1 could explain what im doing wrong thatwould be great...also 20 buck in the paypal acct.....if you can think of it. Ive done it. Next is taking it apart to see what makes it tick

First thing - Does your tablet get seen by your PC in either APX or ADB mode? And did you update the driver using the Naked Drivers?
Last time I rooted I used Wolf's Method 3. Here is what I did:
Plugged in my tablet to my PC via USB (win 7 PC).
After the device was detected, I went to Settings - Developer Options - Debugging (tick the box).
It should install new hardware and show 2 devices, an MTP and an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: http://forum.xda-developers.com/showthread.php?t=1998650
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite recovery. I strongly recommend TWRP. The latest official release is here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save this at c:\adb\TWRP.blob. You can use a different recovery method if you have the blob file (such as CWM) but TWRP is far superior unless you are looking to install Android Revolution HD.
Next, run the following commands (from Wolf's Exploit, Method 3)
Code:
adb push TWRP.blob /sdcard/
adb shell
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p4 /data/local/tmp
adb reboot
exit
It will reboot. Once you see the ASUS loading screen, you can continue:
Code:
adb shell
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
Wait until you see it succesfully transfer data.
Then:
Code:
adb reboot
exit
Once it reboots, you should see a progress bar at the ASUS screen. Once this completes you will have TWRP (or some other custom recovery installed)
Now you can install your favorite SuperUser app.
Download a zip flashable SuperUser
ChainsDD SuperUser: http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
ClockWorkMod SuperUser: http://download.clockworkmod.com/superuser/superuser.zip
Chainfire SuperSU: http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip
I like the CWM SuperUser at the moment, but all three will work.
Put these where you can see them from the recovery you flashed. If using TWRP, it needs to be in the /sdcard/ directory or on the microSD card.
Next, reboot to recovery. Hold VOL DOWN and POWER for 12-15 seconds until you see some white text in the upper left of the screen. Release both buttons and tap VOL UP to enter RCK (Recovery).
Once in recovery, tap Install and choose the SuperUser.zip file to install. Once installed, you are rooted.
Another time I rooted, I used EasyFlasher and here is the thread on my rooting guide for that if you are interested: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
Once again, if you cannot get your tablet detected by ADB or APX, chances are it is a bad USB cable.

harley1rocker said:
-snip-
Click to expand...
Click to collapse
If you've 'tried everything', then it's likely Bad drivers or a bad USB cable, I'll assume you've tried my tool, the idcrisis tool, Easyflasher and wolf's method (Described by Fred) above.
If you'd like me to remote desktop you with Teamviewer to make sure your drivers are good I can do that, but if you've really tried everything then it's likely a bad cable.
ToD

To test the cable, simply transfer a file through USB with a known md5 signature, then verify it again after it's been transferred. You can use something like AFV to check the md5 once on the device. The bigger the file the better; the more chances it has to fail.

I GOT IT! holy crap! Ive gotta windows 7 comp. It turns out, it was the computer!. I completely wiped my laptop and started over. Still failed to flash recovery. I borrowed a friends computer and wah lah. Went into apx mode, got the new device found notification and installed the naked driver from device maneger. They finally took! This tablet is pretty old so I figure SBK1, nope, command wudnt run. No harm done. Went back and did SBK2 and FINALLY! Anyway, the first thing I do on any rooted device ready for a custom rom is do a nand back up. I kept gettin the "error path not known" or sumthin. This was on rogue. No offense to them, I never liked the lay out from the epic 4g touch days. So I loaded twrp. And now im able to do a back up.
And if I could not of gotten it, yes I would have let u remotely access my comp. It was the computer though. I trashed it and got me another this morning.
HUGE FREAKIN THANX TO ALL WHO RESPONDED. I still say this tablet is the toughest ive encountered by far. THANX FELLAS

harley1rocker said:
I GOT IT! holy crap! Ive gotta windows 7 comp. It turns out, it was the computer!. I completely wiped my laptop and started over. Still failed to flash recovery. I borrowed a friends computer and wah lah. Went into apx mode, got the new device found notification and installed the naked driver from device maneger. They finally took! This tablet is pretty old so I figure SBK1, nope, command wudnt run. No harm done. Went back and did SBK2 and FINALLY! Anyway, the first thing I do on any rooted device ready for a custom rom is do a nand back up. I kept gettin the "error path not known" or sumthin. This was on rogue. No offense to them, I never liked the lay out from the epic 4g touch days. So I loaded twrp. And now im able to do a back up.
And if I could not of gotten it, yes I would have let u remotely access my comp. It was the computer though. I trashed it and got me another this morning.
HUGE FREAKIN THANX TO ALL WHO RESPONDED. I still say this tablet is the toughest ive encountered by far. THANX FELLAS
Click to expand...
Click to collapse
Glad you got it sorted.

who got the 20 dollars
Sent from my Transformer TF101 using xda premium

stesteste said:
who got the 20 dollars
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Wasn't me. But I did not respond for the $20, I am just a good guy.

No one....yet. right after i posted that i got another comp. Installed naked drivers and wah lah. APX mode was recognized . But,if any1....fredreco. thanx for the info u posted.

harley1rocker said:
No one....yet. right after i posted that i got another comp. Installed naked drivers and wah lah. APX mode was recognized . But,if any1....fredreco. thanx for the info u posted.
Click to expand...
Click to collapse
We're all here to help, it really isn't about $, for me really it's just seeing that someone cares to donate that makes my day.. It's all about the passion of android though As fred will probably tell you.

[Q] Asus tf700 JB 4.2 NOT WORKING

Hey guys, first time on here.
I've been trying to root my unlocked Asus tf700 running JB 4.2.1 for days and have been following all the xda guides with no luck.
I've tried to flash CMW on it through fastboot to no avail. Everything I see says, once you get into the bootloader or whatever, to press Vol Down until you get to the USB icon and then press volume up but there isn't any USB icon. Right when I get into the bootloader, after I hold Vol Down and Pwr, the first thing it reads on the top left corner of the screen is "Key driver missing." But I have downloaded the drivers from the asus website. Any suggestions about why this is happening? I also tried just using Motochopper (http://forum.xda-developers.com/showthread.php?t=2230763) but when it ran it said failure. I booted it up and I had SuperSU but I tried to open it and it said "no SU binary found! This is a problem!". Any suggestions on how to root this and flash a recovery on it would be greatly appreciated, because none of the other forums guides seem to work? help out a noob!

npf24 said:
Hey guys, first time on here.
I've been trying to root my unlocked Asus tf700 running JB 4.2.1 for days and have been following all the xda guides with no luck.
I've tried to flash CMW on it through fastboot to no avail. Everything I see says, once you get into the bootloader or whatever, to press Vol Down until you get to the USB icon and then press volume up but there isn't any USB icon. Right when I get into the bootloader, after I hold Vol Down and Pwr, the first thing it reads on the top left corner of the screen is "Key driver missing." But I have downloaded the drivers from the asus website. Any suggestions about why this is happening? I also tried just using Motochopper (http://forum.xda-developers.com/showthread.php?t=2230763) but when it ran it said failure. I booted it up and I had SuperSU but I tried to open it and it said "no SU binary found! This is a problem!". Any suggestions on how to root this and flash a recovery on it would be greatly appreciated, because none of the other forums guides seem to work? help out a noob!
Click to expand...
Click to collapse
If your device is unlocked you don’t need MotoChopper for rooting, just flash TWRP Recovery and it will ask you if you want to root your device (in case it detect that root is missing).
For the "Key driver missing" error, just ignore it, Fastboot will work just fine as long as you are sure that the drivers are installed just fine.

Pretoriano80 said:
If your device is unlocked you don’t need MotoChopper for rooting, just flash TWRP Recovery and it will ask you if you want to root your device (in case it detect that root is missing).
For the "Key driver missing" error, just ignore it, Fastboot will work just fine as long as you are sure that the drivers are installed just fine.
Click to expand...
Click to collapse
Thanks, but I'm still confused. I thought you needed GooManager to install TWRP, and GooManager won't work unless you have a rooted device.

npf24 said:
Thanks, but I'm still confused. I thought you needed GooManager to install TWRP, and GooManager won't work unless you have a rooted device.
Click to expand...
Click to collapse
Goo Manager is not mandatory, you can still flash the TWRP via fastboot.You can find more info on the TWRP website.

Sounds like a driver issue to me. If you can't fastboot cwm or use motochopper something is up.
Could also be your usb connection. Try another cable or port or another pc.

lafester said:
Sounds like a driver issue to me. If you can't fastboot cwm or use motochopper something is up.
Could also be your usb connection. Try another cable or port or another pc.
Click to expand...
Click to collapse
yeah ive tried two differ pcs already so I dont think its that. It definitely could be the drivers. Ive tried to install them from the asus site a bunch of times though so idk whats up.

npf24 said:
yeah ive tried two differ pcs already so I dont think its that. It definitely could be the drivers. Ive tried to install them from the asus site a bunch of times though so idk whats up.
Click to expand...
Click to collapse
If you have recently updated your firmware to xxxx.10, you will "not" be able to run motochopper (there is nothing wrong with your PC or cables), Ausus closed the Moto root opening with the latest firmware. However, you can still root following the TWRP instructions.....as indicated above.

just some more info
So i tried re installing the drivers one more time to my PC, and everything went okay, so I'm sure it can't be the drivers, although the error still comes up. And just to tell you guys, when moto chopper runs it says, "waiting for device, daemon not running, starting it now on port 5057, daemon started successfully." Don't know if that helps at all to what the problem is, but just some more info. Now I'll try flashing twrp and rooting that way.

Nothing works at all
dishinit said:
If you have recently updated your firmware to xxxx.10, you will "not" be able to run motochopper (there is nothing wrong with your PC or cables), Ausus closed the Moto root opening with the latest firmware. However, you can still root following the TWRP instructions.....as indicated above.
Click to expand...
Click to collapse
So I went to the TWRP website to try and install twrp 2.6.0. The three options on how to do this were:
1. Via GooManager - which I can't do because my device isn't rooted.
2. Through fastboot (it says to click on the usb icon) - there isn't any usb icon.
3. The terminal method.
I just tried the terminal method, and that didn't work either because when I typed in what it said I was supposed to type in, it said "permission denied."
So yeah.

npf24 said:
So I went to the TWRP website to try and install twrp 2.6.0. The three options on how to do this were:
1. Via GooManager - which I can't do because my device isn't rooted.
2. Through fastboot (it says to click on the usb icon) - there isn't any usb icon.
3. The terminal method.
I just tried the terminal method, and that didn't work either because when I typed in what it said I was supposed to type in, it said "permission denied."
So yeah.
Click to expand...
Click to collapse
I vaguely remember running Motochopper & getting the same message.....it you are on .8 or earlier firmware (in 4.2.1), Motochopper should run.
I think I turned off my tablet, left it connected to PC & then ran motochopper & tablet self booted.....lots of ABD's out of date messages, but Moto worked it's way through them and rooted my device.
I have read of problems with Win 7 (my OS) & Motochopper, but none if used with XP.
Good luck, & Let us know how t goes

npf24 said:
2. Through fastboot (it says to click on the usb icon) - there isn't any usb icon.
Click to expand...
Click to collapse
Recent bootloaders do not have a USB icon because they activate fastboot already while the boot menu is visible (read the tiny text in the top left corner).

dishinit said:
I vaguely remember running Motochopper & getting the same message.....it you are on .8 or earlier firmware (in 4.2.1), Motochopper should run.
I think I turned off my tablet, left it connected to PC & then ran motochopper & tablet self booted.....lots of ABD's out of date messages, but Moto worked it's way through them and rooted my device.
I have read of problems with Win 7 (my OS) & Motochopper, but none if used with XP.
Good luck, & Let us know how t goes
Click to expand...
Click to collapse
I tried what you said. The tablet didn't self-boot when I ran Motochopper again. It just stayed powered off. I turned it on, and the exact same thing happened. except there was another error in motochopper this time. it said "FAILURE ALREADY EXISTS." any other suggestions?

_that said:
Recent bootloaders do not have a USB icon because they activate fastboot already while the boot menu is visible (read the tiny text in the top left corner).
Click to expand...
Click to collapse
Okay that's what I thought. So if I do that second method on twrp, I guess I should just skip when it says to press the USB icon because fast boot is already running??

npf24 said:
Okay that's what I thought. So if I do that second method on twrp, I guess I should just skip when it says to press the USB icon because fast boot is already running??
Click to expand...
Click to collapse
Correct.

_that beat me to it - again. )