Database Info

[Q] Do I need the USB cable to root?

Just got me new-to-me TF700 this afternoon. Trying to root it.
Unlocking was easy (all manufacturers should do it this way).
Now trying to root.
I've downloaded (and copied to /sdcard0) CWM touch for KK (recovery-kk-touch-6046.img)
Press [pwr] +[vol-down] gets me to what appears to be a fastboot screen. I have 3 options "RCK", "Android", and "Wipe data".
None of these lets me run recovery on the CWM image.
I'd just go into ADB and run from there, but the tablet came without the stock USB cable (the one that plugs in the keyboard port).
Is there another way to do this - of am I doing the wrong thing anyway?
Not a major deal if I need to order a cable and wait.
Thanks!
PS: tablet is on stock 4.2.1. There are a lot of instructions that say, basically, select 'USB' from the fastboot screen. That's not appearing.

bobkoure said:
I'd just go into ADB and run from there, but the tablet came without the stock USB cable (the one that plugs in the keyboard port).
Click to expand...
Click to collapse
Without that cable, how do you connect it to the charger?
bobkoure said:
There are a lot of instructions that say, basically, select 'USB' from the fastboot screen. That's not appearing.
Click to expand...
Click to collapse
There are also instructions updated for the current bootloader that tell you that fastboot is already active in the bootloader menu.
bobkoure said:
Also. What the heck is the port next to the headphone jack that looks mike a micro USB, but isn't?
Click to expand...
Click to collapse
Micro HDMI.
You could try if the recently released towelroot works for you until you get your cable.

It came with an aftermarket charger; charger and cable are a single piece. I'm not sure the separate chargers are available at all now.
I saw those instructions - and it looked like I was in fastboot. What I mostly wanted to do was install the CWM image. I think there's a way to do that as recovery, as well, but the img has to get packaged in a zip file with instructions and then named whatever recovery is looking for. Not something I'm going to be able to whack together.
Yeah, realized it was micro HDMI just as soon as I started looking at "tf700 cable". Duh! Removed it from my OP, didn't realize someone had already looked at it and was looking to save someone (you?) some typing. Didn't work.
Time to get a cable.

Found one of the OEM chargers. $55 + shipping. Not planning to buy.

bobkoure said:
Found one of the OEM chargers. $55 + shipping. Not planning to buy.
Click to expand...
Click to collapse
If Towelroot works (it probably will since it does work on the TF701) and you get root, you can use the dd command in terminal to flash the custom recovery. But better do some reading on that! One little typo and you could have yourself a brick.
You cannot flash a custom recovery using the stock recovery however - or did I misunderstand?
You can get by without a USB cable if you can get it rooted, but what if something goes wrong? What if you cannot enter recovery and only fastboot is available?
I would not flash custom software without a working ADB and fastboot connection! And for those you need the USB cable. Get it - you'll regret it if you don't.

berndblb said:
! And for those you need the USB cable. Get it - you'll regret it if you don't.
Click to expand...
Click to collapse
Oh, I got one. Just was itchin' to get a new ROM. Hoping KK's a bit speedier (it had ought to be) - and it's desperately slow now.
Towelroot, indeed, worked fine. Mixed feelings on that one. It working means basically any app that gets installed can get root. But I'm happy I got root to play with in the couple of days it took Newegg to get a cable to me

bobkoure said:
Oh, I got one. Just was itchin' to get a new ROM. Hoping KK's a bit speedier (it had ought to be) - and it's desperately slow now.
Towelroot, indeed, worked fine. Mixed feelings on that one. It working means basically any app that gets installed can get root. But I'm happy I got root to play with in the couple of days it took Newegg to get a cable to me
Click to expand...
Click to collapse
Good choice getting the cable.
Install SuperSU from the Play Store. That will allow you to control which apps get root.

berndblb said:
Good choice getting the cable.
Install SuperSU from the Play Store.
Click to expand...
Click to collapse
Did that immediately. Paid for pro ages ago
Now trying to get fastboot via USB.
power off (or reset)
power & [vol dn]
stock JB so it goes right into fastboot (3 selectable icons, no "USB" icon)
connect USB
on win pc cmd line go to adb/fastboot directory
"fastboot devices" gets me... nothing.
Not sure how to get CWM installed without fastboot (?)
Trying to figure out if I maybe have bad win drivers. adb works (e.g. "adb shell" works fine) - not when in fastboot mode, of course.
Any ideas? Pointers to the right drivers (win 64)?
Thanks!

bobkoure said:
Did that immediately. Paid for pro ages ago
Now trying to get fastboot via USB.
power off (or reset)
power & [vol dn]
stock JB so it goes right into fastboot (3 selectable icons, no "USB" icon)
connect USB
on win pc cmd line go to adb/fastboot directory
"fastboot devices" gets me... nothing.
Not sure how to get CWM installed without fastboot (?)
Trying to figure out if I maybe have bad win drivers. adb works (e.g. "adb shell" works fine) - not when in fastboot mode, of course.
Any ideas? Pointers to the right drivers (win 64)?
Thanks!
Click to expand...
Click to collapse
Windows is infamous for driver problems.....
Connect the tab in fastboot and open device manager. Near the top you should have an entry for Android device, bootloader mode or something similar, and probably a yellow ! next to it.
Right click it and choose "update driver", let Windows search for it.
If you're lucky it'll install the driver by itself.
If not: What Windows version are you running?

berndblb said:
If not: What Windows version are you running?
Click to expand...
Click to collapse
Win 7 Pro / 64.
If you don't mind, I'm going to re-ask this in the general forum - if it's like other forums, when the question changes tack, often people who might know the exact answer never read it because the title was about the original question.
I put it here
BTW, Got CROMBi-KK on there without fastboot (so without a USB cable ) as follows
towelroot - got root
installed supersu, loaded binaries, uninstalled towelroot
goo.im - open bootloader - installed TWRP
installed CROMBi-KK by copying zip to sdcard0, then install from TWRP.
Even without booting / using a fast external SD card, it's perceptibly faster than the stock JB ROM. I did kind'a like the way the stock JB screen was laid out to make it easy to use while attached to a keyboard (controls at L & R bottom corners where you can easily poke 'em with a thumb.) Ah, well.

Ah yes - forgot about Goo. For quite a while it didn't support flashing TWRP anymore, but it's back.
There's also TWRP Manager (which I haven't tried yet) and Flashify which I really like.
It does make flashing a recovery easier, but.....
Call me old-fashioned, but all of those require Android to run. What if you're stuck in a bootloop and need to flash a recovery, clear partitions in fastboot etc? To get drivers working when the tablet is already compromised can be a challenge - to say the least.
I wouldn't be surprised if we see more and more users here who went your route, never got ADB and fastboot going and find themselves stuck when Android does not boot....
That said, I'm glad you can experience KK goodness now and I'll head over to your new thread - maybe I have another idea

Black Screen-Data Recovery. Possible?

I'm checking out my sister's phone that she dropped and broke the screen. Device boots up, since I can feel the vibration and hear alarms but the screen is dead. Debugging was not enabled, bone stock. I can see it in fastboot, but I'm not sure if there is a specific mode to be in to allow ADB for this device. I've read Downloader mode, which should be 3 spots below where Fastboot drops you, but I get no change. Anyone have a suggestion on how to pull the old data off?

Atemi1337 said:
I'm checking out my sister's phone that she dropped and broke the screen. Device boots up, since I can feel the vibration and hear alarms but the screen is dead. Debugging was not enabled, bone stock. I can see it in fastboot, but I'm not sure if there is a specific mode to be in to allow ADB for this device. I've read Downloader mode, which should be 3 spots below where Fastboot drops you, but I get no change. Anyone have a suggestion on how to pull the old data off?
Click to expand...
Click to collapse
You can only have adb connectivity when booted in the OS and usb debugging must be ON. You must also allow your computer RSA key from your phone at the first attempt to use adb.
adb can also be used form a custom recovery (even with debbug off) but if the phone was still stock it's bootloader is probably locked... Unlocking the bootloader will wipe data (and a working screen is also needed to unlock it).
At this point I think replacing the display would be the only option...
Sorry

alray said:
You can only have adb connectivity when booted in the OS and usb debugging must be ON. You must also allow your computer RSA key from your phone at the first attempt to use adb.
adb can also be used form a custom recovery (even with debbug off) but if the phone was still stock it's bootloader is probably locked... Unlocking the bootloader will wipe data (and a working screen is also needed to unlock it).
Sorry
Click to expand...
Click to collapse
Pretty much confirmed my thought. Thanks for the glance.

Urgent mistake needs a fix..

Hi there people,
Well I did a big BS tbh. I was running AOSiP(20190407) but I was still having proximity issues now and there (doesn't matter what rom, I've got this for a while), so I flash a miui from time to time(maybe for a driver proximity fix).
Yesterday I remove the password(temporary), booted TWRP, flash miui 9.4.18(latest dev) and because I was in road, I've tried to flash AOSiP(20190407) back which stuck on the AOSiP logo, then I remember I did have the previous version 20190328? if I remember well, BIGGGGG mistake trying to flash that, phone can't boot and goes to TWRP recovery which is fine but when I see the data, well encrypted(scrambled that is) - doesn't asks for password of course
Tried to place a file via MTP(e.g. LineageOS latest or MIUI) without success ..tries to copy it but doesn't really do anything, my thought is to:
Buy a USB Type-C OTG cable or adapter and try to flash LineageOS or MIUI through that, if data are still encrypted then I'd try to put the very same password I had and maybe be lucky?
Any other thoughts? (of course deleting data would solve this but my latest backup is 1-2 months back which will make me very sad to lose 1-2 months of pictures, videos etc)
P.S. I've made a custom microusb OTG cable but using a usb type-c adapter doesn't make it work so I guess it's a pin-issue ..OTG microusb can't work with usb type-c that way, that's why I'm thinking of a usb type-c otg cable/adapter. I have a few microusb jacks laying around, that's why I tried that

Try to boot with latest twrp and see if it unscrabled partition...

AOSP roms do not boot with the latest vendor and firmware. If you flash an older version in twrp you should be good to go.

hocuspocus69 said:
Try to boot with latest twrp and see if it unscrabled partition...
Click to expand...
Click to collapse
I've got the latest TWRP for a while now
hmmm 3.3.0.0 is release but since I can't move the recovery in order to flash it I should do it via fastboot
EDIT: Can't do it via fastboot, doesn't work. I tried I see the device when I run the command well it does nothing hmmm I guess my only hope is with the solution I mention and MAYBE I'd be lucky
EDIT2: Tried again and again now it says "press any key to shutdown" when I issue the command ..maybe USB debugging issue? not sure, well if I can flash miui or something similar via OTG(I'll have the cable/adapter in a couple of days, no phone until then hhahahaha), if I keep trying it's either the first(doing nothing) or the second "change display black display with tiny letters on top left corner saying "press any key to shutdown" - oh well sht happen

M1chiel said:
AOSP roms do not boot with the latest vendor and firmware. If you flash an older version in twrp you should be good to go.
Click to expand...
Click to collapse
The part where I can't access data or write data in the internal memory is an issue so I can't do any "flash" ...I can try with OTG adapter/cable when I get my hands on it
Wish it will work as I'm out of options

I also got the tiny letters in fastboot mode. It turned out that fastboot commands only worked for one of the three usb ports of my laptop. I guess usb 3.0 didn't work.

M1chiel said:
I also got the tiny letters in fastboot mode. It turned out that fastboot commands only worked for one of the three usb ports of my laptop. I guess usb 3.0 didn't work.
Click to expand...
Click to collapse
Well different pc, original cable I flashboot recovery, now on 3.3.0.0 ...still data scrambled
Yeah, new recovery ...pretty same result
I guess I'll have to way an try the "OTG" method I was thinking about
P.S. Trying to move miui in internal storage still does nothing, well I tried. Now I only hope OTG would save me
Not sure if I could fastboot miui without losing data, it's been a while since I use fastboot

I tried with USB OTG adaptor, no luck. It doesn't work(can't see any usb stick) ..FML

Phone Bricked After Installing OTA Update

I recently purchased an Oneplus 7 pro from Ebay and the phone was working fine. It's locked to T-Mobile and it prompted me to take an update, I believe the update was for November 2019 and was almost 2 gb in size. I rebooted the phone when it said to reboot to install the new features, and the phone never came back on after that. I tried charging it for hours, tried holding the power button + volume up/down buttons to get it to reboot, and none of this has done anything for the phone. There's no sign of life, the phone was working great prior to the update.
Is there any suggestions for fixing this?
Thanks.

adrunkenmess1 said:
I recently purchased an Oneplus 7 pro from Ebay and the phone was working fine. It's locked to T-Mobile and it prompted me to take an update, I believe the update was for November 2019 and was almost 2 gb in size. I rebooted the phone when it said to reboot to install the new features, and the phone never came back on after that. I tried charging it for hours, tried holding the power button + volume up/down buttons to get it to reboot, and none of this has done anything for the phone. There's no sign of life, the phone was working great prior to the update.
Is there any suggestions for fixing this?
Thanks.
Click to expand...
Click to collapse
go here https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659 and use the global version. that will allow you bootloader unlock phone when done.

MrSteelX said:
go here https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659 and use the global version. that will allow you bootloader unlock phone when done.
Click to expand...
Click to collapse
Thanks for the link, I downloaded everything and disabled driver enforcement but my phone is still not showing up in Device Manager. The computer makes a noise as I connect it to the USB port, but other than that it isn't doing anything.

adrunkenmess1 said:
Thanks for the link, I downloaded everything and disabled driver enforcement but my phone is still not showing up in Device Manager. The computer makes a noise as I connect it to the USB port, but other than that it isn't doing anything.
Click to expand...
Click to collapse
with the phone off, hold vol up and plug usb cable in. It should boot to edi mode then.

MrSteelX said:
with the phone off, hold vol up and plug usb cable in. It should boot to edi mode then.
Click to expand...
Click to collapse
I think it was the cable I was using that was causing it....used a better usb cable and it recognized in the Device Manager.
I can't flash it though as it gives error "param preload device not match image"

Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
adrunkenmess1 said:
I think it was the cable I was using that was causing it....used a better usb cable and it recognized in the Device Manager.
I can't flash it though as it gives error "param preload device not match image"
Click to expand...
Click to collapse

amirage said:
Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
Click to expand...
Click to collapse
I was able to get it to flash successfully. I used the files from the tmobile to international conversion since it required a hacked MSM tool. I'm a complete Noob at phone flashing and really spent a LOT of time reading tonight to figure it out. Phone flashed successfully but said the battery was now too low to turn on. At least it says something!
I'm charging it up now and hopefully it works after this!

amirage said:
Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
Click to expand...
Click to collapse
I use a USB 3.0 and USB c port on my computer and no issues

OK so I manage to get the phone flashed to the international version using the MSM tool. I then downloaded the DP 3 developer file like suggested. I put it in the root for my phone, went to system settings, system update, and got to install it locally. It installed 100% and then asked me to reboot for the changes to take effect.
I reboot the phone and then nothing, it's black and unresponsive the way it was when this whole thing started.
I'm sure I can just reflash the international file with MSM to get it working, but is there any reason why updating my phone in this manner always fails and a way for me to fix it?

jamescable said:
I use a USB 3.0 and USB c port on my computer and no issues
Click to expand...
Click to collapse
Really, I couldn't get the phone to come up on the MSM tool in the Qualcomm mode on USB 3 port. But when I connected the cable to the USB port, it appeared there.

adrunkenmess1 said:
OK so I manage to get the phone flashed to the international version using the MSM tool. I then downloaded the DP 3 developer file like suggested. I put it in the root for my phone, went to system settings, system update, and got to install it locally. It installed 100% and then asked me to reboot for the changes to take effect.
I reboot the phone and then nothing, it's black and unresponsive the way it was when this whole thing started.
I'm sure I can just reflash the international file with MSM to get it working, but is there any reason why updating my phone in this manner always fails and a way for me to fix it?
Click to expand...
Click to collapse
MSM phone, unlock bootloader and flash twrp. Use twrp to flash system update and see if it works

Question I can't access the download mode

So here is the deal.
This device (Galaxy A32 5G - SM A326B - Android 12) does not let me boot into the download mode in order to unlock bootloader and for eventually rooting it.
OEM unlock has been selected in the dev options.
No button pressing configuration is working.
Trying to access the fastboot mode in the recovery mode only shows a black screen with a red writing on top that fastboot mode is being loaded, but nothing is happening and Odin doesn't recognize the device.
I just want that turquoise, blueish download mode screen, but for the love of it, it just doesn't work getting there.
This is my backup device and I just want to root it. Coming from OnePlus I am spoiled but the fact that I can't access this mode with all kinds of button tryouts is just nagging on me.
Anyone experienced something similar?
Some help would be greatly appreciated.
Cheers

mrjuniork said:
OEM unlock has been selected in the dev options.
Click to expand...
Click to collapse
I have the SM A326U but unfortunately I tried to see if I had the OEM Unlock options in the Developer Options Activity, and it's not there.
Do you know what the hidden activity might be when you click on the OEM Unlock? Maybe we can bring it up with an Activity Launcher?

mrjuniork said:
So here is the deal.
This device (Galaxy A32 5G - SM A326B - Android 12) does not let me boot into the download mode in order to unlock bootloader and for eventually rooting it.
OEM unlock has been selected in the dev options.
No button pressing configuration is working.
Trying to access the fastboot mode in the recovery mode only shows a black screen with a red writing on top that fastboot mode is being loaded, but nothing is happening and Odin doesn't recognize the device.
I just want that turquoise, blueish download mode screen, but for the love of it, it just doesn't work getting there.
This is my backup device and I just want to root it. Coming from OnePlus I am spoiled but the fact that I can't access this mode with all kinds of button tryouts is just nagging on me.
Anyone experienced something similar?
Some help would be greatly appreciated.
Cheers
Click to expand...
Click to collapse
Did you try plugging into usb while holding down the buttons?

TimmyP said:
Did you try plugging into usb while holding down the buttons?
Click to expand...
Click to collapse
Yes, among other things. It just never enters that mode. It either restarts, goes into charging mode or reboots to recovery.
It's weird

maybe try "Samsung 300k Tool?" It looks like its designed specifically to reboot Samsungs into Download mode

TimmyP said:
maybe try "Samsung 300k Tool?" It looks like its designed specifically to reboot Samsungs into Download mode
Click to expand...
Click to collapse
Thx for this useful information. I could enter the download mode with this program but interestingly there is no way to use volume up button for proceeding to unlock the bootloader. Odin recognized the device properly but no way to unlock the bootloader. Isn't that strange? Also I did not see the warning screen, it went straight to the download mode screen.
I did not expect this to be such a pain...

Glad it worked! Samsungs always seem to have some sort of strange issue. I was recently stuck in a bootloop for a half hour until I finally got the key combo for recovery to work. Since it never turns off it becomes a pain!

TimmyP said:
Glad it worked! Samsungs always seem to have some sort of strange issue. I was recently stuck in a bootloop for a half hour until I finally got the key combo for recovery to work. Since it never turns off it becomes a pain!
Click to expand...
Click to collapse
I actually figured it out without the need of any 3rd part software.
There was obviously one option that I haven't tried yet. Pressing both volume buttons and then plugging in the USB cable till the warning screen shows up. That's it
Anyway, thx for taking your time to reply.
Cheers

mrjuniork said:
I actually figured it out without the need of any 3rd part software.
There was obviously one option that I haven't tried yet. Pressing both volume buttons and then plugging in the USB cable till the warning screen shows up. That's it
Anyway, thx for taking your time to reply.
Cheers
Click to expand...
Click to collapse
Hello Pal, were you able to root the device? I have bought an A33 5G, not sure if I will be able to root it. Extracting the boot.img file from original rom, patching it with Magisk and flashing back to the phone works? Can you use fastboot for it or do you need ODIN?

GauchoTche said:
Hello Pal, were you able to root the device? I have bought an A33 5G, not sure if I will be able to root it. Extracting the boot.img file from original rom, patching it with Magisk and flashing back to the phone works? Can you use fastboot for it or do you need ODIN?
Click to expand...
Click to collapse
Hello again.
Yes, I managed to root the device.
I used Odin for flashing the patched boot image. AFAIK, using fastboot isn't possible, hence Odin.
But make sure you have a backup in place, coz in my case, initially applying a patched image, led to another factory reset (the second one after unlocking the bootloader).

mrjuniork said:
Hello again.
Yes, I managed to root the device.
I used Odin for flashing the patched boot image. AFAIK, using fastboot isn't possible, hence Odin.
But make sure you have a backup in place, coz in my case, initially applying a patched image, led to another factory reset (the second one after unlocking the bootloader).
Click to expand...
Click to collapse
Hello, I need help with unlocking the bootloader as well. I can't find the Oem option and there is no unlock the bootloader option in download mode.