2 Problems at once - Transformer TF300T Q&A, Help & Troubleshooting

Hello! I was trying to flash BAM Rom for TF300T. Unfortunately, i forgot to update my recovery (TWRP) in order to flash the KitKat version of the rom, and basicly now i can't launch the device normally since the flashing failed, but in the other hand i can still open my recovery and do stuff.
PROBLEMS: 1. I can't flash the newest recovery because my drivers simply aren't working ( <waiting for device> etc. )! I have tried installing ASUS Suite and other drivers i found online, both on 2 different PCs, nothing worked.
2. I can't flash a new rom with the recovery since there's no way to access the tablets storage. TWRP won't recognize my MicroSD
(Error mounting MicroSD).
So, here's what I need: Some way to access the device's storage or mount my MicroSd, or some way to fix the drivers so fastboot recognises my Tab!

pansysk75 said:
Hello! I was trying to flash BAM Rom for TF300T. Unfortunately, i forgot to update my recovery (TWRP) in order to flash the KitKat version of the rom, and basicly now i can't launch the device normally since the flashing failed, but in the other hand i can still open my recovery and do stuff.
PROBLEMS: 1. I can't flash the newest recovery because my drivers simply aren't working ( <waiting for device> etc. )! I have tried installing ASUS Suite and other drivers i found online, both on 2 different PCs, nothing worked.
2. I can't flash a new rom with the recovery since there's no way to access the tablets storage. TWRP won't recognize my MicroSD
(Error mounting MicroSD).
So, here's what I need: Some way to access the device's storage or mount my MicroSd, or some way to fix the drivers so fastboot recognises my Tab!
Click to expand...
Click to collapse
Have you tried reinstalling the Universal Naked USB Drivers? That fixes the fastboot issue for may people.

cmendonc2 said:
Have you tried reinstalling the Universal Naked USB Drivers? That fixes the fastboot issue for may people.
Click to expand...
Click to collapse
I have tried multiple times but I'm not sure if I'm doing it right.

pansysk75 said:
I have tried multiple times but I'm not sure if I'm doing it right.
Click to expand...
Click to collapse
Are you using Windows 8? There is a different way to do it with that. If it still doesn't work, you can try installing linux mint or ubuntu and work from there.

cmendonc2 said:
Are you using Windows 8? There is a different way to do it with that. If it still doesn't work, you can try installing linux mint or ubuntu and work from there.
Click to expand...
Click to collapse
No, I'm using Windows 7 (64 bit). I'm downloading ubuntu now...

Related

[Q] TWRP problem

I want to root my tablet so I flashed TWRP 2.6.0.0 using fastboot everything works fine.
But now I want to install the zip to root the tablet, problem is TWRP cannot mount any storage, internal sdcard external sdcard nothing at all is alway says E:Can't mount 'xxx' on anything I tap.
I tried CWM, and 2.5.0.0 and nothing seems to work.
I can boot fine in the stock OS, everything works fine but that
My bootloader is 10.6.1.27.1-20130711
Can anyone help me?
Ok now it is bad, I tried to factory reset using the bootloader (power + volume down)
It booted in the buged TWRP and now it keeps booting in TWRP and I cannot even reach the bootloader
Try using adb commands to boot into bootloader.
ADB reboot-bootloader is the command that I think you must use. Of course, use adb devices to see if your tab is listed.
______________________________
HTC Evo 4G LTE
aarsyl said:
Try using adb commands to boot into bootloader.
ADB reboot-bootloader is the command that I think you must use. Of course, use adb devices to see if your tab is listed.
______________________________
HTC Evo 4G LTE
Click to expand...
Click to collapse
I cannot get this to work on Windows 8, I have Asus Transformer ADB interface lister in device manager but I cannot see my device with the adb devices command.
Also, in TWRP when I try adb sideload it says failed.
win 8 is the worst OS you want to use when it comes to fastboot/adb (even with secpol.msc full admin access)
get your hands on a win7 / vista /xp
oh and TWRP2.6 is kinda bugged - flash 2.5 or lower
check this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 but skip the steps you dont need (system, data userdata etc.)
cheers & gl
-Buster
Buster99 said:
win 8 is the worst OS you want to use when it comes to fastboot/adb (even with secpol.msc full admin access)
get your hands on a win7 / vista /xp
oh and TWRP2.6 is kinda bugged - flash 2.5 or lower
check this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 but skip the steps you dont need (system, data userdata etc.)
cheers & gl
-Buster
Click to expand...
Click to collapse
I'm now on my laptop with Win7,
Ok so I tried to reset my device with a needle, but I cannot get it to the bootloader.
Still stuck in TWRP, I tried to go with ADB, I installer google usb driver from Android SDK, I cannot get it to be recognized by ADB, in the device manager I only see Transformer with a yellow "!", I tried with the Asus usb driver, nothing either.
Is there something else I can do to get this recognized with ADB? (fastboot doesn't work either)
I tried unpluging all, uninstalling all and reinstalling like 3 times.
Thanks for your help
Matiosse said:
I'm now on my laptop with Win7,
Ok so I tried to reset my device with a needle, but I cannot get it to the bootloader.
Still stuck in TWRP, I tried to go with ADB, I installer google usb driver from Android SDK, I cannot get it to be recognized by ADB, in the device manager I only see Transformer with a yellow "!", I tried with the Asus usb driver, nothing either.
Is there something else I can do to get this recognized with ADB? (fastboot doesn't work either)
I tried unpluging all, uninstalling all and reinstalling like 3 times.
Thanks for your help
Click to expand...
Click to collapse
fastboot should work. hold Vol-down and reset the device and keep vol-down pressed. it should go to fastboot. when you're in fastboot connect it to your laptop and see if the OS recognized your device - if not you have a driver issue. resolve that by installing the asus driver or the newest google generic drivers.
when you can see your device on dosprompt/powershel with fastboot devices then continue with getting recovery to work.
btw- stuck in twrp means? booting twrp (teamwin screen) but not responding?
good luck
-Buster
The problem is I cannot even get into fastboot, it keeps booting into TWRP, I tried to reset the tab with a needle, but I cannot reach fastboot in any ways
Matiosse said:
The problem is I cannot even get into fastboot, it keeps booting into TWRP, I tried to reset the tab with a needle, but I cannot reach fastboot in any ways
Click to expand...
Click to collapse
but you are still able to boot into android?
I was until I tried a factory reset, it wasn't working in Android so I did it in the fastboot menu.
Matiosse said:
I was until I tried a factory reset, it wasn't working in Android so I did it in the fastboot menu.
Click to expand...
Click to collapse
can you boot into twrp? and i mean just boot into it? so that you see install, backup, restore etc. buttons?
if yes - twrp has an adb mode
connect your tab in twrp to your pc (check that you can see it - adb devices) if yes type: adb reboot bootloader
and you should boot into that. test it with fastboot devices.
most important thing is that you get into fastboot or a working recovery to flash or prepare to flash a (custom) rom back onto your device.
Buster
I can get in TWRP on 2.5.0.0
But when I try ADB sideload it fails
The message is ADB sideload complete - Failed in red + lots of errors like Unable to mount '/data' '/cache' /system' pratically everything (note that I had the same problem of mounting when I was able to boot into Android)
Matiosse said:
I can get in TWRP on 2.5.0.0
But when I try ADB sideload it fails
The message is ADB sideload complete - Failed in red + lots of errors like Unable to mount '/data' '/cache' /system' pratically everything (note that I had the same problem of mounting when I was able to boot into Android)
Click to expand...
Click to collapse
learn to crawl before you run :angel:
Well I rooted 4 different android device and not a single one of them wasn't able to mount anything in recovery mod. I knew exactly what I was doing until I got in the recovery mod who won't even recognize my internal storage meanwhile I was able to perfectly boot in Android
Matiosse said:
Well I rooted 4 different android device and not a single one of them wasn't able to mount anything in recovery mod. I knew exactly what I was doing until I got in the recovery mod who won't even recognize my internal storage meanwhile I was able to perfectly boot in Android
Click to expand...
Click to collapse
dude - you can't boot into android anymore, you can't boot into fastboot to your own accord - yet you try to sideload stuff in twrp for what ever reason.
i gave you more hints and tips in my previous posts and link to get it to work yet it eems you did none.
so don't get me wrong - but what excactly is your goal here?
My goal is to get it working again...
I don't know if you've been reading my post but I did try everything you told me without sucess.
None of the tips I tried got me adb or fastboot working the sideload mode of TWRP doesn't work.
Matiosse said:
My goal is to get it working again...
I don't know if you've been reading my post but I did try everything you told me without sucess.
None of the tips I tried got me adb or fastboot working the sideload mode of TWRP doesn't work.
Click to expand...
Click to collapse
yes i read your posts - but im still unclear what you are trying to accomplish with sideload?
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?) "adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
-B
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?)
Windows isn't working with it, I tried Google usb driver, asus usb driver, universal adb driver, none of them work, this is where i'm stuck
"adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
Matiosse said:
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?)
Windows isn't working with it, I tried Google usb driver, asus usb driver, universal adb driver, none of them work, this is where i'm stuck
"adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
Click to expand...
Click to collapse
when its connected - is device manager at least showing it as faulty or not at all? (yellow triangle exclamation mark thingy, i just installed asus on my VM) -> see attached file
UPDATE: I succeeded to go in fastboot mode
I couldn't get my tab to be recognized by windows so I installer my Nexus 4 using the toolkit, when it was succesfully installed I could manually install my tab since the "android devices" option appeared in the list when you want to manually install a driver in the devices manager. So I could choose Asus ADB interface.
Now I can boot into Android, but it will go into TWRP as soon as I restart my tablet.
Now I will try the link you sent me to get TWRP recognize my storage so I can flash a new rom, I will let you know if something go wrong.
Thanks for helping

[Q] Asus TF101 Soft Brick Re-loop HELP!

Hi everyone,
after days of researching this issue I'm finally at wits end. After installing the Playstore version of ROM Manager, my Asus has been stuck in CWM recovery mode with the inability to mount any drives. When I re-boot the tablet gets stuck on the load screen. I have tried several methods to flash the tablet using:
- NVFLASH
- EASY FLASHER
- FASTBOOT
- ONE CLICK RECOVERY
- ADB PUSH
The recurring issue that I seem to be encountering using these methods is that my PC recognizes the tablet in APX mode (I have tried both naked & usbpcdrivers) but the utility software does not. When I boot into recovery mode ADB recognizes my device but does not in APX mode. When I run NVFLASH while in APX mode my tablet gets disconnected from the PC and I receive a USB write error from NVFLASH.
Prior to the failure I successfully rooted my device using Baidu Root. At this point I don't even know how to power off the device as the only way to exit the loop is to boot into recovery or APX mode.
Any help would be greatly appreciated, as my experience with these matters are limited.
Thanks
roniinn said:
Hi everyone,
after days of researching this issue I'm finally at wits end. After installing the Playstore version of ROM Manager, my Asus has been stuck in CWM recovery mode with the inability to mount any drives. When I re-boot the tablet gets stuck on the load screen. I have tried several methods to flash the tablet using:
- NVFLASH
- EASY FLASHER
- FASTBOOT
- ONE CLICK RECOVERY
- ADB PUSH
The recurring issue that I seem to be encountering using these methods is that my PC recognizes the tablet in APX mode (I have tried both naked & usbpcdrivers) but the utility software does not. When I boot into recovery mode ADB recognizes my device but does not in APX mode. When I run NVFLASH while in APX mode my tablet gets disconnected from the PC and I receive a USB write error from NVFLASH.
Prior to the failure I successfully rooted my device using Baidu Root. At this point I don't even know how to power off the device as the only way to exit the loop is to boot into recovery or APX mode.
Any help would be greatly appreciated, as my experience with these matters are limited.
Thanks
Click to expand...
Click to collapse
First recommendation, stay away from ROM Manager, our device doesn't like it. You need to try and uninstall all usb drivers associated with tf101 and start over. I used the drivers from BRK's v.8 Tool Kit. You may need to find some newer adb files to swap out with his, but try first. To clean all the drivers may require connecting the tab to pc in different modes to even see some of the drivers, but see what's in Programs & Features - Remove function in Windows. You will also need the stock ROM downloaded from Asus site before you start. If you can get into recovery, then you should have an option in there to power off the device. If you get that far, then his tool has the nvflash pieces to start from scratch and get rooted and install an older custom recovery. Go with the CWM version there and, ultimately, change it out to the latest TWRP as soon as possible. Getting the drivers for Windows working is the hardest part, assuming everything else works. Conflicting USB drivers will be nothing but headaches, as you've found out.
Hi,
just to be clear, when the tablet is in APX mode, is ADB supposed to be able to detect it when the adb devices command is used?
roniinn said:
Hi,
just to be clear, when the tablet is in APX mode, is ADB supposed to be able to detect it when the adb devices command is used?
Click to expand...
Click to collapse
I don't think so. It's like download mode on other Android devices. You should be able to access via adb in Android, with USB debugging enabled, or in some custom recoveries, my TWRP builds for one. I believe nvflash is the only method to communicate with APX mode.
Sent from my SM-N900T using XDA Premium HD app
Hi,
I have re-installed drivers, but the PC still disconnects my tablet when running NVFLASH, I have read that a utility named WHEELIE might assist in unlocking the bootloader on my device allowing NVFLASH to run successfully. The problem is I can not locate the windows version of this file anywhere. All of the links point to a website named AndroidRoots, but the file seems to have been removed from the site.
Any Ideas where I can locate this program?
Thanks again.
roniinn said:
Hi,
I have re-installed drivers, but the PC still disconnects my tablet when running NVFLASH, I have read that a utility named WHEELIE might assist in unlocking the bootloader on my device allowing NVFLASH to run successfully. The problem is I can not locate the windows version of this file anywhere. All of the links point to a website named AndroidRoots, but the file seems to have been removed from the site.
Any Ideas where I can locate this program?
Thanks again.
Click to expand...
Click to collapse
BRK's version 8 tool I referenced uses wheelie to cover all possible skus of tf101 and works well for me. As far as drivers, you have to make sure there's only one set installed for tf101.
Sent from my SM-N900T using XDA Premium HD app
Does the wheelie script run automatically when I invoke the rootkit app, or do I have to manually run it from a CMD window?
Thanks for all your help,
roniinn said:
Does the wheelie script run automatically when I invoke the rootkit app, or do I have to manually run it from a CMD window?
Thanks for all your help,
Click to expand...
Click to collapse
It runs it where needed within a windows app interface, completely transparent once you start the program executable by double clicking it. You'll see a command window, but it just shows you the progress.
Sent from my SM-N900T using XDA Premium HD app
Thanks for your help,
I have finally got my device up and running again.
My next step is to flash the new KatKiss ROM, can I do this using BRK's toolkit by substituting my stock rom file with the new one, or is it to better to install the new rom from recovery and external SD card?
roniinn said:
Thanks for your help,
I have finally got my device up and running again.
My next step is to flash the new KatKiss ROM, can I do this using BRK's toolkit by substituting my stock rom file with the new one, or is it to better to install the new rom from recovery and external SD card?
Click to expand...
Click to collapse
I would just install it from recovery and ext sdcard, easier if you've already cleaned and repartitioned, etc with a stock rom.
Sent from my SM-N900T using XDA Premium HD app

tf700 not recognized by pc

I trying to flash my tf700 with a custom rom, since it's terribly slow and barely usable. I've unlocked the device with the asus tool. But when i'm trying to install trwp tablet isn't recognized.
I've installed sdk, naked usb drivers, asus drivers. But nothing works. Is there a way to flash a different rom with having to install a new bootloader?
Depending on what you have now, you may not have to install a different bootloader. But you do have to install a custom recovery and you need fastboot for that.
Driver issues in Windows are frustrating to solve, but don't give up.
1. Try a different USB port. I know, sounds lame, but it has worked for quite a few people.
2. Uninstall Asus Sync and all drivers you have tried so far. Also drivers for older phones/tablets you may still have
3. Try this cool little tool: http://forum.xda-developers.com/showthread.php?t=2588979
When I start the bootloader with powerbutton and volume down I see the following message, is this correct?
Key driver not found.. booting os
Android cardhu-user bootloader (1.00 e) released by "WW_epad-10.6.1.14.10-20130801" a03
Starting fastboot usb download protocol.
Yes, that is the bootloader screen and the tablet is in fastboot mode. Never mind the "key driver not found". That's also normal....
berndblb said:
Yes, that is the bootloader screen and the tablet is in fastboot mode. Never mind the "key driver not found". That's also normal....
Click to expand...
Click to collapse
I have tried several things, installed asus sync, sdk, google usb drivers and a different pc. Nothing works. Is there a different way to install a different rom?
UPDATE:
I did a new install of windows 7 and now my tablet is recognized by the pc. But when I try to install the twrp.blob file with the fastboot method, I get the error invalid argument and nothing happens. And again I'm having the problem that the tablet is not recognized by the pc.
UPDATE 2:
somehow I managed to flash twrp to the tablet after numerous invalid argument errors after using fastboot. I'm now running crombi kk.

[Q] HELP Urgent No OS only Recovery

No OS only recovery, i can't flash a new rom, someone knows how to flash by adb or fastboot? i'm desperate. I can't mount on otg, recovery says Interna storage 0mb OTG 0mb, before of this i've have installed firmare of sense 6 but i've lost all... please help me
Acticus said:
No OS only recovery, i can't flash a new rom, someone knows how to flash by adb or fastboot? i'm desperate. I can't mount on otg, recovery says Interna storage 0mb OTG 0mb, before of this i've have installed firmare of sense 6 but i've lost all... please help me
Click to expand...
Click to collapse
Yes I know that...
Is your adb and fastboot working...???
Please post BOOTLOADER output....
What recovery are you using...?
greets
shivasrage said:
Yes I know that...
Is your adb and fastboot working...???
Please post BOOTLOADER output....
What recovery are you using...?
greets
Click to expand...
Click to collapse
HBoot 2.22
Super Cid
Relocked
Recovery is CWM now, thnaks for answer
i'm trying flash with sideload.. but it's slowly
Acticus said:
HBoot 2.22
Super Cid
Relocked
Recovery is CWM now, thnaks for answer
i'm trying flash with sideload.. but it's slowly
Click to expand...
Click to collapse
OK in short terms:
I highly recommend to change to TWRP 2.7.1.1 or latest philz recovery. (first I think you have to unlock your bootloader)
Next ...like you allready posted... try to sideload or push your sense 6 ROM
And yes I know sideload needs some patience...
greets
shivasrage said:
OK in short terms:
I highly recommend to change to TWRP 2.7.1.1 or latest philz recovery. (first I think you have to unlock your bootloader)
Next ...like you allready posted... try to sideload or push your sense 6 ROM
And yes I know sideload needs some patience...
greets
Click to expand...
Click to collapse
fastboot does not work well, do not respond to commands
Acticus said:
fastboot does not work well, do not respond to commands
Click to expand...
Click to collapse
now when i plug the usb the computer respond uknown device
Acticus said:
now when i plug the usb the computer respond uknown device
Click to expand...
Click to collapse
I think its an driver issue....check your drivers first..
Lo0k into device manager in windows what your HTC M_4 is listed.
Is there maybee an (!) ?
Your device should be listed under "my HTC" then fastboot should work correct.
Don´t use Windows 8 many driver problems reported rather use Windows 7
shivasrage said:
I think its an driver issue....check your drivers first..
Lo0k into device manager in windows what your HTC M_4 is listed.
Is there maybee an (!) ?
Your device should be listed under "my HTC" then fastboot should work correct.
Don´t use Windows 8 many driver problems reported rather use Windows 7
Click to expand...
Click to collapse
nope i have reinstalled drivers but same result
this
Acticus said:
nope i have reinstalled drivers but same result
Click to expand...
Click to collapse
You never said which OS you're using. Just re-installing the drivers usually won't fix an issue with usb.
Have you tried another cable? Tried plugging into a different USB port?
When you go into device manager, do you see any android, or HTC devices?
Acticus said:
nope i have reinstalled drivers but same result
Click to expand...
Click to collapse
Have you tried to format all partitions in recovery if not you can try this ...the problem is
whitout working fastboot connection there is no chance to fix your problem also RUU and FUU
will fail...
jollywhitefoot said:
You never said which OS you're using. Just re-installing the drivers usually won't fix an issue with usb.
Have you tried another cable? Tried plugging into a different USB port?
When you go into device manager, do you see any android, or HTC devices?
Click to expand...
Click to collapse
Win 7, i have tried 3 different cable and 4 different port. Before i opened this thread work, and now don't work...
Acticus said:
Win 7, i have tried 3 different cable and 4 different port. Before i opened this thread work, and now don't work...
Click to expand...
Click to collapse
Which drivers are you using? Have you tried to right-click on that unknown device and selecting update driver and manually navigate to the location of your drivers.
jollywhitefoot said:
Which drivers are you using? Have you tried to right-click on that unknown device and selecting update driver and manually navigate to the location of your drivers.
Click to expand...
Click to collapse
driver of htc sync manager, my god.. i have threw away € 400.... i'm so f*** stupid
Acticus said:
driver of htc sync manager, my god.. i have threw away € 400.... i'm so f*** stupid
Click to expand...
Click to collapse
don't despair and do something rash. I doubt your phone is ruined. I had a lot of trouble getting drivers to work in Windows 7 and thought I had ruined my phone too. Once I got drivers working it was super easy to get my phone running again.
shivasrage said:
Have you tried to format all partitions in recovery if not you can try this ...the problem is
whitout working fastboot connection there is no chance to fix your problem also RUU and FUU
will fail...
Click to expand...
Click to collapse
i have formatted each partition in recovery, but same result
Acticus said:
i have formatted each partition in recovery, but same result
Click to expand...
Click to collapse
That's the something rash i was warning of.
Do you have access to another computer? Preferably windows XP? Or can you install a clean copy of Windows 7 onto your current computer? I've read other people have success booting to Ubuntu from a disc as well.
I haven't tried this, but others have said it eliminated Windows USB issues
https://help.ubuntu.com/community/BootFromCD
https://help.ubuntu.com/community/LiveCD
jollywhitefoot said:
That's the something rash i was warning of.
Do you have access to another computer? Preferably windows XP? Or can you install a clean copy of Windows 7 onto your current computer? I've read other people have success booting to Ubuntu from a disc as well.
I haven't tried this, but others have said it eliminated Windows USB issues
https://help.ubuntu.com/community/BootFromCD
https://help.ubuntu.com/community/LiveCD
Click to expand...
Click to collapse
i have just tried this, ubuntu don know the command fastboot or adb
jollywhitefoot said:
That's the something rash i was warning of.
Do you have access to another computer? Preferably windows XP? Or can you install a clean copy of Windows 7 onto your current computer? I've read other people have success booting to Ubuntu from a disc as well.
I haven't tried this, but others have said it eliminated Windows USB issues
https://help.ubuntu.com/community/BootFromCD
https://help.ubuntu.com/community/LiveCD
Click to expand...
Click to collapse
So,
Mr jollywhitefoot If you read carefully you will see that he write in first post:
" I can't mount on otg, recovery says Internal storage 0mb OTG 0mb" so why do you think this will happen.???"
Yes because the partitions are messed up and if you not format them, you will never ever get them to work.
All others that have resurrected their phones here have formatted partitions before or flashed a firmawre where it will be done also.
So if I recommend to try formatting partitions there is a reason for....nothing to warn of for you in this case!!!
And if you recommend this guy to setup a linux distribution from a live cd then advise him also to setup adb + fastboot in linux correctly.
shivasrage said:
So,
Mr jollywhitefoot If you read carefully you will see that he write in first post:
" I can't mount on otg, recovery says Internal storage 0mb OTG 0mb" so why do you think this will happen.???"
Yes because the partitions are messed up and if you not format them, you will never ever get them to work.
All others that have resurrected their phones here have formatted partitions before or flashed a firmawre where it will be done also.
So if I recommend to try formatting partitions there is a reason for....nothing to warn of for you in this case!!!
And if you recommend this guy to setup a linux distribution from a live cd then advise him also to setup adb + fastboot in linux correctly.
Click to expand...
Click to collapse
thank you shivasrage, so i can't do anything to resuscitate it? nor send it to htc assistance?

Trying to restore my oneplus.

So i recently decided to update my Oneplus 7 Pro from the public stable release to the OxygenOS 11 Open Beta 3 on a whim. Tried to go back to the old stable release by flashing fastboot roms from Tool All In One and it somehow broke everything, even though I did it multiple times before.
Phone can't boot into anything -- even with stock roms installed. Simply shows the bootloader is unlocked screen and nothing after. I can get into recovery and edl and fastboot, but nothing else. I think I flashed an older version from TAIO's fastboot rom flasher, making it impossible (!) for my computer to interact with my phone.
MSM Tool also doesn't work. Param preload, even though I have the QC and OP drivers installed.
Anything I can do?
You could try, moving the 10 stable on to a usb drive you could plug into the phone, then fastboot boot twrp.img via fastboot . Once in, format and install A10 from usb drive, done it many times
@soka said:
You could try, moving the 10 stable on to a usb drive you could plug into the phone, then fastboot boot twrp.img via fastboot . Once in, format and install A10 from usb drive, done it many times
Click to expand...
Click to collapse
That's just it -- I can't fastboot anything. Be it roms or TWRP.
Besides, my phone doesn't really interact with my computer so no adb. Only edl (i think).
VictimOfMagic said:
That's just it -- I can't fastboot anything. Be it roms or TWRP.
Besides, my phone doesn't really interact with my computer so no adb. Only edl (i think).
Thanks for replying
Click to expand...
Click to collapse
Sorry about that bud, sounds like your drivers are not installed properly. Maybe start there. I used the tool in one app to install the needed drivers. Worth a shot.
Try this post
Fastboot waiting for any device
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay...
forum.xda-developers.com
@soka said:
Sorry about that bud, sounds like your drivers are not installed properly. Maybe start there. I used the tool in one app to install the needed drivers. Worth a shot.
Try this post
Fastboot waiting for any device
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay...
forum.xda-developers.com
Click to expand...
Click to collapse
Well, TIAO only installs google's WinUSB. I already had that installed. I just don't know why I keep getting stuck on the param preload, even with all the drivers that could be needed being installed. Maybe it has something to do with the OOS version? I have GM1915, fastboot flashed to 10.0.4 Global.
Also, I think i messed up my msm tool since now it always says connected lmao
VictimOfMagic said:
Well, TIAO only installs google's WinUSB. I already had that installed. I just don't know why I keep getting stuck on the param preload, even with all the drivers that could be needed being installed. Maybe it has something to do with the OOS version? I have GM1915, fastboot flashed to 10.0.4 Global.
Also, I think i messed up my msm tool since now it always says connected lmao
Thanks for replying.
Click to expand...
Click to collapse
I had the same problem with drivers. (I tried the ones that come with the device (in an .iso image I think?) and then I tried with the patched L2 drivers.)
What worked for me: installing the ALL IN ONE tool (on windows) then runing it as administrator*, then installing the drivers from within the All In One Tool program.
md5hasher said:
I had the same problem with drivers. (I tried the ones that come with the device (in an .iso image I think?) and then I tried with the patched L2 drivers.)
What worked for me: installing the ALL IN ONE tool (on windows) then runing it as administrator*, then installing the drivers from within the All In One Tool program.
Click to expand...
Click to collapse
Running TAIO as an admin? That still only downloads WinUSB.
Can you expand on what you mean?
Under windows 10 open CMD as admin and enter bcdedit /set testsigning on
now reboot. This resolved for me the driver issue and phone was then correctly seen by msm unbrick tool

Categories

Resources