Database Info

Hardcore soft brick - no recovery, fastboot not working

I've searched, but the only similar problems either solely involved Windows or ended in a return/RMA. I'm really hoping someone can help me.
Story: I restored a backup using TWRP 2.2.1.3 (ICS). I'm honestly not sure which ROM it was, could have been stock. I was actually restoring it to find out what it was. Before the restore, I wiped data, cache, dalvik cache, and system. The restore went perfectly, no errors or anything out of the ordinary. When I rebooted into the system, it hung on the initial bootsplash. I waited a few minutes before giving up and booting back into recovery. I rebooted by holding down the power button for a while (30 seconds maybe?) and held Volume Down as the tablet booted.
Problem: Instead of the message to press Volume Up to boot into recovery, it just went directly to the screen that comes up after waiting where it counts down the cold boot time and gives you three options - except now, I only have two: Wipe Data and Fastboot. Great, at least I have fastboot. Right? Wrong, apparently. Selecting that option shows the message "Starting Fastboot USB download protocol", but the command
Code:
./fastboot devices
returns a blank line. Likewise,
Code:
./fastboot -i 0x0B05 flash recovery ./openrecovery-twrp-2.2.1.3-tf300t.blob
returns "<waiting for device>".
Attempted troubleshooting: I tried rebooting the device and starting fastboot while attached via USB, and I've tried starting fastboot before plugging in the USB cable. I tried rebooting to the system and using ADB at the hanging bootsplash. There was no ADB access. I've tried restarting the computer while the tablet is plugged in and in fastboot mode.
OS: Debian Testing; ia32-libs, ia32-libs-dev, and ia32-libs-gtk installed
Kernel: 3.5.2 from Debian repos + BFS + BFQ, self-compiled
Previous ROM: Blackbean 8/15
Other: I have not flashed the JB OTA yet (restoring the backup was actually in preparation for the JB OTA; I wanted to see if I had a rooted stock backup). I did not flash the JB version of TWRP. I have used ADB and Fastboot on my tablet successfully in the past on the same computer.
I hope I didn't forget anything relevant. If I think of something else, I'll post it.
Edit: Possible progress? I selected the Wipe Data option, and it loaded TWRP and wiped data. Unfortunately, it immediately attempted to boot the system, which just hung on the initial splashscreen. So, I still have a recovery. I just need a way to boot into it. I'll keep messing around, I guess.

Bump, plus an update.
I realized I should probably run lsusb to see if the computer is actually detecting the tablet. This is the output of "lsusb -v". The output is the same whether the tablet is in Fastboot mode or hanging at the bootsplash. ADB still won't recognize the connected device while on the bootsplash. Interestingly, the iProduct seems to be labeled "Fastboot" in both cases, but fastboot doesn't recognize the tablet either.
Code:
Bus 002 Device 004: ID 0b05:4daf ASUSTek Computer, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0b05 ASUSTek Computer, Inc.
idProduct 0x4daf
bcdDevice 0.00
iManufacturer 1 ASUSTeK COMPUTER INC.
iProduct 2 Fastboot
iSerial 3 00000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 32mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 66
bInterfaceProtocol 3
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 66
bDeviceProtocol 3
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
I'm really hoping this can help someone. If my computer is recognizing the tablet, there may be some way to bruteforce the tablet into recovery or something, I think.

you may have adb available during the wipe process, you can try to push an install instruction to /cache/recovery/command
Code:
install_package=path to your rescue zip
you could also try to delete /cache/recovery/command and may end up looking at the recovery UI
you would have to be very lucky for this to work
if TWRP uses an external executable to format partitions you could also try to attack that with chmod -x /sbin/mke2fs
and try to get an error screen to display, or replace it with a script that goes in the an endless loop so you have enough
time to
Code:
dd if=/sdcard/blob of=/dev/block/mmcblk0p4

untermensch said:
you may have adb available during the wipe process, you can try to push an install instruction to /cache/recovery/command
Code:
install_package=path to your rescue zip
Click to expand...
Click to collapse
Yeah, I tried that, actually, but forgot to add it to my attempted troubleshooting list. I ran "adb devices" before the wipe so it would be able to detect it ASAP, but I got nothing. It just sat on "<waiting for device>" during the whole process.
you could also try to delete /cache/recovery/command and may end up looking at the recovery UI
you would have to be very lucky for this to work
if TWRP uses an external executable to format partitions you could also try to attack that with chmod -x /sbin/mke2fs
and try to get an error screen to display, or replace it with a script that goes in the an endless loop so you have enough
time to
Code:
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
Click to expand...
Click to collapse
I'm assuming this part depends on the first part working. I'll fiddle with it when I get home from work in the morning.
This is so aggravating. I had no idea that restoring a backup could do this. And it's even more frustrating that my computer can see the tablet at a low level but can't seem to interface with it in userspace.
My next step was going to be to try to PM Asus_USA and Gary Key to see if they had any ideas, but I'm sure they would just tell me they can't help and I need to RMA it.
I may try to contact AndroidRoot.mobi to see if they've seen this or have any ideas, but I'm not sure how willing they would be to help, even if they could. If anyone besides Asus_USA can help, it's them. It may be my last hope before RMA.

i have the same problem ecept it wont even leave the asus logo screen when it first starts up can get into recovery fastboot adb apx nothing i cant even get a wipe device i installed the new jelly bean on mine and something whent wrong cause keyboard wifi ect. was malfunctioning so i factory restored it no help tried wiping data in recovery and now its stuck if any one has any ideas for us thanks

I'm sorry but i saw your title and just want to say thank God I'm not the only one! Good luck and i feel your pain. Gnex myself
*This Jedi master be a Ninj-ESS*

ditto
i flashed cwm touch with fastboot but didn't read the tread properly, it was for stock JB, so now it's stuck on asus boot logo with "this device is unlocked" text up top and when i press power + vol down it's stuck on " starting bootloader kernel image" :crying:

I'm going to lurk your thread. Different device and everything but if you figure something in adb maybe I can use it too.

I don't have any other bootloader except stock, my pad was rooted....
I tried the update and it failed, rebooted and ICS popped back up and I received a message stating that the update failed and ICS was being restored.
I put a copy of the update file in the CACHE folder and tried to update again - this event failed as well, but now my computer won't recognize my pad, and the USB option doesn't show up on the stock recovery (pic below).
Checked device manager and the ASUS PAD is showing error code 10 (device stopped)... downloaded new drivers, rebooted computer, tried to figure out how to load Motorola drivers ( http://forum.xda-developers.com/showthread.php?t=1685540 ), but nothing worked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like we have similar problems... Hope we don't have to send the pads in to get fixed.

I have gnex and same thing almost. I did a restore from job to pics and its like adb installs drivers backwards.
Sent from my Galaxy Nexus using xda app-developers app

newowner said:
I don't have any other bootloader except stock, my pad was rooted....
I tried the update and it failed, rebooted and ICS popped back up and I received a message stating that the update failed and ICS was being restored.
I put a copy of the update file in the CACHE folder and tried to update again - this event failed as well, but now my computer won't recognize my pad, and the USB option doesn't show up on the stock recovery (pic below).
Checked device manager and the ASUS PAD is showing error code 10 (device stopped)... downloaded new drivers, rebooted computer, tried to figure out how to load Motorola drivers ( http://forum.xda-developers.com/showthread.php?t=1685540 ), but nothing worked.
Looks like we have similar problems... Hope we don't have to send the pads in to get fixed.
Click to expand...
Click to collapse
Hmmm... I was gonna focus on getting fastboot to work, personally. I'll try some things with ADB and the wipe data option like untermensch suggested, too. Maybe there's some kind of exploit we can use to get to the point that we can use untermensch's exploit. I'm gonna compile a new kernel in the morning with USB debugging enabled and see if I can get anything useful from the logs.
Be aware, though, that if anything good comes about, it will be Linux-centric since that's my preferred OS, and I don't really know anything about Windows, especially the changes since XP.
Edit: I see you have the "Android" option. If you select that, what happens? Does the OS boot? Can you access ADB?

EndlessDissent said:
Hmmm... I was gonna focus on getting fastboot to work, personally. I'll try some things with ADB and the wipe data option like untermensch suggested, too. Maybe there's some kind of exploit we can use to get to the point that we can use untermensch's exploit. I'm gonna compile a new kernel in the morning with USB debugging enabled and see if I can get anything useful from the logs.
Be aware, though, that if anything good comes about, it will be Linux-centric since that's my preferred OS, and I don't really know anything about Windows, especially the changes since XP.
Edit: I see you have the "Android" option. If you select that, what happens? Does the OS boot? Can you access ADB?
Click to expand...
Click to collapse
The pad is stuck in boot... with the logo and the rotating circle.

newowner said:
The pad is stuck in boot... with the logo and the rotating circle.
Click to expand...
Click to collapse
Does ADB work for you? I would expect it to at that point in the boot process, but I'm no expert.

How do I get ADB to work with out being connected to the device? The device is not recognized by my computer.
EndlessDissent said:
Does ADB work for you? I would expect it to at that point in the boot process, but I'm no expert.
Click to expand...
Click to collapse
Sent from my DROID RAZR using Tapatalk 2

newowner said:
How do I get ADB to work with out being connected to the device? The device is not recognized by my computer.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
What do you mean it's not recognized by the computer? Did you install the drivers for the device? When the tablet is connected to the computer, does anything show up in Device Manager?

mikeseguin said:
i flashed cwm touch with fastboot but didn't read the tread properly, it was for stock JB, so now it's stuck on asus boot logo with "this device is unlocked" text up top and when i press power + vol down it's stuck on " starting bootloader kernel image" :crying:
Click to expand...
Click to collapse
Same thing here ...
with this message :
Device not seen by the PC ... no usb connection ...
adb devices show nothing ...

EndlessDissent said:
What do you mean it's not recognized by the computer? Did you install the drivers for the device? When the tablet is connected to the computer, does anything show up in Device Manager?
Click to expand...
Click to collapse
Pad is hooked up to computer, via usb, and device manager reads "error code 10 (device stopped)"
Computer has been rebooted, drivers have been reloaded/updated, computer rebooted again, and the pad drivers still don't properly install.

newowner said:
Pad is hooked up to computer, via usb, and device manager reads "error code 10 (device stopped)"
Computer has been rebooted, drivers have been reloaded/updated, computer rebooted again, and the pad drivers still don't properly install.
Click to expand...
Click to collapse
Well, if it shows up in Device Manager, the computer sees it, but I don't know exactly what that error means. I have no idea if it's a driver issue. What drivers have you tried? Did you use the Asus drivers? The universal drivers (I've seen some on XDA; look for "naked universal" drivers)? Others have used Motorola drivers when the Asus ones didn't work.
I really don't know why your tablet would boot all the way to the animation but without ADB access. That's why I think (and hope) it might be a driver issue.

dude, I fixed mine! I had to manually input the driver stuff into the setup.inf file in the drivers folder of sdk because it wasnt in there!! check your hardware id under device manager and then check it against the inf file.

Uh?

Rooting Double Power (DOPO) M7088 Jelly Bean 4.1.1 Tablet

As always Any information I give is free and this information is to be used at your own risk I take no responsibility for your device this is just my experience and i hope it helps someone with the same problem i had
I recently bought the Double Power (DOPO) M7088 Jelly Bean 4.1.1 Tablet from Walmart.com After a few days of searching and many failed Attempts I finally found out how to root this device and would like to share it to those having the same problem.
After doing some digging i descover the Dopo tablets are nothing more than a rebranded generic rock ship tablets so after some searching here is what i found.
Things you will Need.
1.Pdanet+ for android installer (just type in pdanet+ in your search engine of choice)
2.Your device and usb cable
3.The free download of unlockrootpro (Just type unlockroot into your search engine of choice
Steps.
1. Download and install Pdanet+
2 Download and install unlockrootpro free Version
a. you must be connected to the internet for the installer to work.
b. the unlockroot pro will download a file to your computer that is in itself a down loader it is safe but it does try to get you to install some 3rd part software. if you click the close button it will give you the option to skip the 3rd party software and install just the unlockroot software. it does this 2 or 3 times just click close and skip each time.
3. Connect your Tablet up to the PC and allow all the drivers to install.
4. Once connected start unlockrootpro once it is ope click the green root button it should detect your device and bring up a box just click the button and it will install the root.
a. Now i noticed after it installed the root and say rebooting device my device would not reboot. I unplugged my device and then plugged it right back in and the device immediately rebooted
5. Once your table has rebooted download root checker or the app of your choice to verify root access.
I hope this helped anyone with a Dopo m7088
I don't know if this method will work for any of the other Double Power Tablets so i honestly cannot answer any questions other than what i have stated but feel free to try it if you cannot find any other method.
If this method does Work for you please post a coment on your steps and what device you used this method on so that you can help the community.

M7088
Well i have found out that there is a way to ROOT the M7088 from walmart with out internet connection
Download Moborobo in order to load drivers for the M7088
Just download the same software as you would for the PIPO S1 Its all over the net now and also this M7088 has an attitude about rooting so you might have to click root a couple time to force it to but it does work quite well the Chinese software ( ZhuoDaShi ) after its done you will get a message window in Chinese just copy and paste that text into Google translator and it will tell you ROOT is good Ha Ha ha have fun
backslashx said:
As always Any information I give is free and this information is to be used at your own risk I take no responsibility for your device this is just my experience and i hope it helps someone with the same problem i had
I recently bought the Double Power (DOPO) M7088 Jelly Bean 4.1.1 Tablet from Walmart.com After a few days of searching and many failed Attempts I finally found out how to root this device and would like to share it to those having the same problem.
After doing some digging i descover the Dopo tablets are nothing more than a rebranded generic rock ship tablets so after some searching here is what i found.
Things you will Need.
1.Pdanet+ for android installer (just type in pdanet+ in your search engine of choice)
2.Your device and usb cable
3.The free download of unlockrootpro (Just type unlockroot into your search engine of choice
Steps.
1. Download and install Pdanet+
2 Download and install unlockrootpro free Version
a. you must be connected to the internet for the installer to work.
b. the unlockroot pro will download a file to your computer that is in itself a down loader it is safe but it does try to get you to install some 3rd part software. if you click the close button it will give you the option to skip the 3rd party software and install just the unlockroot software. it does this 2 or 3 times just click close and skip each time.
3. Connect your Tablet up to the PC and allow all the drivers to install.
4. Once connected start unlockrootpro once it is ope click the green root button it should detect your device and bring up a box just click the button and it will install the root.
a. Now i noticed after it installed the root and say rebooting device my device would not reboot. I unplugged my device and then plugged it right back in and the device immediately rebooted
5. Once your table has rebooted download root checker or the app of your choice to verify root access.
I hope this helped anyone with a Dopo m7088
I don't know if this method will work for any of the other Double Power Tablets so i honestly cannot answer any questions other than what i have stated but feel free to try it if you cannot find any other method.
If this method does Work for you please post a coment on your steps and what device you used this method on so that you can help the community.
Click to expand...
Click to collapse

Firmware
Hey awesome i may have a chance to try that method out on my tablet soon if i am lucky. I was wondering if anyone or the one that commented on my original post. I need a copy of the firmware for this tablet mine crashed after lending it out to a friend i am afraid he tried to modify it and somehow corrupted the system it is stuck on the dopo start up screen. if there is anyone who can provide a clean copy of this or even maybe dump a copy of theirs for me i would greatly appreciate it.
.
zxhwk said:
Well i have found out that there is a way to ROOT the M7088 from walmart with out internet connection
Download Moborobo in order to load drivers for the M7088
Just download the same software as you would for the PIPO S1 Its all over the net now and also this M7088 has an attitude about rooting so you might have to click root a couple time to force it to but it does work quite well the Chinese software ( ZhuoDaShi ) after its done you will get a message window in Chinese just copy and paste that text into Google translator and it will tell you ROOT is good Ha Ha ha have fun
Click to expand...
Click to collapse

hey this is great news and I thank you !!!
I was wondering if the m7088 caan be upgraded to CM10/4.2.2?
thanks

I don't know if you can install any form of CM on it as of yet. I have successfully I believe Dumped a copy of the system and recovery images from my M7088. Unfortunately my last unit was toast but being under warrantee i sent it back and they replaced it. Soon as I had it i researched how to back up the system just in case. I can provide my copy of the dump or show the process i used to do it.
I don't know if the dump I have is what is exactly a proper form of back up or recovery. I also don't know what is needed to mod it for CM but at least this is a start to anyone who would like to try.
If there is anyone who would like to and would like the Files I have dumped or any help I can provide let me know. I would like to see Cm/4.2.2 working on this device.

Easy way to root any Dopo tablet
I am not responsible for anything. Use this at your on risk.
Download and install Exynos abuse .
Then Uninstall and get any kind of root checker to verify root access.
And that's it.
Worked for me with no problems. NOW My Dopo tablet is faster than when I got it out the box. With minor tweaking apps and my 32 gb external SD card as my internal SD card and you can find the thread on how to do this on xda forums. Running games like NFS MW, Modern Combat 2 and 3,Nba Jam for android.To run good games like these I had to get a system app freezer like titanium backup to freeze a few useless apps. So now these games run very smooth and flawlessly.Good luck.

backslashx said:
I don't know if you can install any form of CM on it as of yet. I have successfully I believe Dumped a copy of the system and recovery images from my M7088. Unfortunately my last unit was toast but being under warrantee i sent it back and they replaced it. Soon as I had it i researched how to back up the system just in case. I can provide my copy of the dump or show the process i used to do it.
I don't know if the dump I have is what is exactly a proper form of back up or recovery. I also don't know what is needed to mod it for CM but at least this is a start to anyone who would like to try.
If there is anyone who would like to and would like the Files I have dumped or any help I can provide let me know. I would like to see Cm/4.2.2 working on this device.
Click to expand...
Click to collapse
I ran across this post and was wondering if you have the original system and recovery images, as I rooted my M7088 and lost my backup files

m7088 firmware
I am looking for a copy of the firmware for my m7008 tablet.
I am trying to fix a problem of it not starting up its stuck on the DOPO screen.
I believe I can re flash it but DOPO will not send me the file they want me to send in.
Any help will be appreciated.

DOPO logo screen-freeze
putertim said:
I am looking for a copy of the firmware for my m7008 tablet.
I am trying to fix a problem of it not starting up its stuck on the DOPO screen.
I believe I can re flash it but DOPO will not send me the file they want me to send in.
Any help will be appreciated.
Click to expand...
Click to collapse
Joining just to make a couple comments here. I find that DOPO logo screen-freeze seems to be common problem.
My story - This passed Christmas 2012 my son purchased a DOPO M7088 for his 12y/o son, and talked me into a like purchase for myself this past March 2013. Here in Jul 2013, the grandson is visiting with his tablet. When it became frozen with the DOPO screen one night - we tried everything that we could think of to restore. Even pointing fingers at him... to what surprise the following morning my tablet froze updating apps. When I tried to restart, reboot, reset... even tried Vol+/PwrUP, Vol-/PwrUP... allowing the power in the battery to drain to a point that the screen would not light up or flash. Then recharging - nothing worked passed the DOPO screen-freeze.
For reference - I have worked in electronics/computers from the late 60s - so I’m not a rookie here.
Fortunately – I purchased insurance with Wal-Mart, their tech-line made same suggestions as I had done to restore the system, and came to the conclusion that they will completely return/refund my purchase.
Strange that within 12hrs two like tablets crash following app updates, where one is for a young man (games) and the other for adult (general usage). The finger pointing had three other fingers pointing back at us. So apologies to the grandson.
My son may root/re-install the grandson’s system when they return home – for myself I’m going to upgrade to a better brand (now that I'm missing the tablet).
Hope this helps others to understand that the DOPO screen-freeze problem may not be their personal tablet problem but a product problem (I.E. firmware). /TDos

Need dump of 7088 rom
backslashx said:
I don't know if you can install any form of CM on it as of yet. I have successfully I believe Dumped a copy of the system and recovery images from my M7088. Unfortunately my last unit was toast but being under warrantee i sent it back and they replaced it. Soon as I had it i researched how to back up the system just in case. I can provide my copy of the dump or show the process i used to do it.
I don't know if the dump I have is what is exactly a proper form of back up or recovery. I also don't know what is needed to mod it for CM but at least this is a start to anyone who would like to try.
If there is anyone who would like to and would like the Files I have dumped or any help I can provide let me know. I would like to see Cm/4.2.2 working on this device.
Click to expand...
Click to collapse
Hello, I have damaged the ROM by a an installed app after rooting. I see you said that you made a dump of the ROM. If possible, can I get a copy of these files as this would help me greatly. I have rkAndroidTool.exe working. If it works out, I will post the procedure.
Thanks

Dump and Flash the dopo M7088 and other RK3066 based ROMs
Any information I give is to be used at your own risk. I take no responsibility for any damage to your device.
Here's my story: I installed an application to change the fonts after I rooted. This damaged the system and created a boot loop. At this point I had not worked out a reliable method to backup and restore the ROM and in the process of trying to fix, I wound up damaging the partitions trying to push a file back into the tablet with adb.
So in my research to restore the ROM, I came across several methods to flash the ROM, but very few methods to dump the complete ROM and I wanted to be able to extract and restore the entire ROM. In another thread, I found scripts to dump the rk3066 chipset. I expanded this idea and modified the scripts to flash the ROM as well. Also, I created an installer script to simplify the process.
These scripts need to use the Ubuntu Linux live DVD to dump and flash the ROM. The advantages of Linux is you can directly connect to the tablet in flash mode without the trouble of having to install drivers or the android SDK.
Download the Linux 12.04 LTS version from the following Link http://www.ubuntu.com/download/desktop .
Once downloaded, burn this ISO file to a DVD using your favorite DVD burning software. Most burning software have the ability to decode ISO files. If needed, here is a free ISO burner. Link: http://download.cnet.com/ImgBurn/3000-2646_4-10847481.html?tag=mncol;2
Download the attached zip file and copy the zip to the USB drive. Do not decompress in windows as we need to do this under linux to preserve the stored permissions.
Boot the PC from the DVD drive. This should start the Linux. You may need to press an “F” key during the BIOS boot to bring up a menu to select which drive to boot from. You should see a purple screen. This is Linux loading. Select the “Try Ubuntu” option and the Linux should boot to the Linux Desktop.
OK, we are in Linux!
Insert the USB drive into the PC wait for the Linux to open a window. It may take a little bit as we are running off a DVD and some resources need to load. Be patient and watch the light to finish blinking on the USB stick! Drag the “ExtractRomRK3066.zip” file in the USB window to the desktop.
Write down the name of the USB in the title bar of the window.
For example, My USB window says: F490-4740 in the title bar. Write this down, then move the USB window to the side.
Double click on the zip file, this opens the zip in a window. Drag the “ExtractRomRK3066“ folder in the zip window to the desktop. When the copy is finished, close the zip window.
Click on the “Dash Home” icon on the top left of the desktop, Type “Terminal” in the search box and select the terminal application icon.
In the Terminal Window type exactly as shown while observing the caps:
cd ~/Desktop/Ex*
Type the command:
ls -l
You should see a file named “install.sh” along with other commands ending with “.sh”.
Type the line as shown below including the “./”:
./install.sh
The required libraries should install to Linux. Don't worry this is only in memory as we are not installing anything to your hard drive. Make sure everything completed without Errors. If you only see warnings, this is OK!
Let's connect the Tablet to the USB port and put into flash mode. With the Tablet power off and the all cables removed, hold the Vol– button and plug in the USB cable. Continue to hold the Vol- button for 5 seconds. Let go of the Vol- button and connect the power cable. We should now be in flash mode.
We can test if we connected to flash mode by typing:
lsusb
You should see a list of USB devices. Within this list you should see a entry that has the ID:
ID: 2207:300a
If you see the ID, great we are connected to the tablet. If not, make sure the tablet is off and do the above Tablet procedure again.
OK we are connected!
Dumping the ROM
Type the following command replacing the “F490-4740” with your USB name we wrote down earlier from the USB title bar and follow the prompts. This will start the dump of the tablet:
sudo ./dumpall.sh /media/F490-4740/output
YAY! We are dumping the ROM!
Now we wait for “done...”, hopefully without any errors.
Double click on the “ output” folder in the USB drive window.
Verify that we have “backup.img”, “boot.img”, “kernel.img”, “misc.img”, “parm.img”, “recovery.img”, “system.img and userdata.img.
Now in the left panel of the USB window. Click on the ^ icon next to the USB drive description. This will unmount the USB drive for removal.
We are done!
Flashing the ROM
To flash a file you will notice other commands with the extension “.sh”. You may use any of these commands to restore all or part of the ROM.
For example:
To flash the below stock rom, extract the zip file to a USB drive and type the command changing the “F490-4740” to the name of your USB drive:
sudo ./flashall-user.sh /media/F490-4740/dopo7088stock
To flash a backup of all files including the userdata.img, type the command changing the “F490-4740” to the name of your USB drive:
sudo ./flashall.sh /media/F490-4740/dopo7088stock
To flash just the recovery, do the same as above only with the command:
sudo ./flashrecovery.sh /media/F490-4740/dopo7088stock
To flash just the system, do the same as above only with the command:
sudo ./flashsystem.sh /media/F490-4740/dopo7088stock
The valid command are:
sudo ./dump?.sh
or
sudo ./flash?.sh
replacing ? With:
all, all-user, backup, boot. cache, kernel, kpanic, misc, recovery, system, user, userdata
----------------------
Hope this helps somebody create a full backup.
Thanks.
UPDATE: I got another dopo m7088 tablet, created a backup using the above method and flashed my bricked m7088 tablet. Everything works again. YAY!
Below is the dumped stock rom for the dopo m7088. Hopes this help's sombody unbrick their tablet.
Extract the dopo7088stk.zip to a USB drive and follow the above instructions.
Thanks
Stock Rom Link: https://docs.google.com/file/d/0B8YnQA1FX-_yUU1ERXh1TjNUbnc/edit?usp=sharing

Thanks
I now have my M7088 again. Thank you . Your instructions where 100% right on.

Partition table not correct in stock M7088 ROM!
After I created the dump of the M7088 ROM and I flashed my tablet, I was looking at the parameter file and realized it was wrong from the factory!
There are several problems that may be the reason some people (including me) has had their devices brick for no apparent reason.
Below is the factory partition table. There is a blank space at address 118000 for a length of 11E000 bytes, this is not a problem. However, the "userdata" partition overruns the "kpanic" and "system" partition as well as the "system" partition overruns the "user" partition. This could lead to data corruption in the partitions.
Factory Partition Table: (length @ start)
[email protected](misc), (2000 + 2000 = 4000)
[email protected](kernel), (4000 + 4000 = 8000)
[email protected](boot), (8000 + 8000 = 10000)
[email protected](recovery), (10000 + 8000 = 18000)
[email protected](backup), (18000 + C0000 = D8000)
[email protected](cache), (D8000 + 40000 = 118000)
(ERROR - Space between 118000 and 236000)
[email protected](userdata), (236000 + 400000 = 636000)
(ERROR - 636000 is past 618000 and 61A000)
0x000020[email protected](kpanic), (618000 + 2000 = 61A000)
[email protected](system), (61A000 + 200000 = 81A000)
(ERROR - 81A000 is past 73A000)
[email protected](user) (73A000 -> end)
It looks like someone made a mistake and/or adjusted the partition sizes and never finished the job!
The only way to fix this is to correct the partition table and re-flash the entire device.
Before I corrected the "parameter" and "parm.img" file, I examined other RK3066 roms as well as the dopo TD1010. The TD1010 has a shorter "system" partition so the fixed partition table below is the same as the TD1010 all the way through the "kpanic" partition.
Fixed Partition Table: (length @ start)
[email protected](misc), (2000 + 2000 = 4000)
[email protected](kernel), (4000 + 4000 = 8000)
[email protected](boot), (8000 + 8000 = 10000)
[email protected](recovery), (10000 + 8000 = 18000)
[email protected](backup), (18000 + C0000 = D8000)
[email protected](cache), (D8000 + 40000 = 118000)
[email protected](userdata), (118000 + 400000 = 518000)
[email protected](kpanic), (518000 + 2000 = 51A000)
[email protected](system), (51A000 + 200000 = 71A000)
[email protected](user) (71A000 -> end)
I corrected the stock firmware and repacked it as dopo7088stkfixed.zip. This file can be flashed with the procedure in the earlier post, replacing the original zip package with this one.
Fixed Firmware Link: https://docs.google.com/file/d/0B8YnQA1FX-_yRmhIN1dCT245R2c/edit?usp=sharing
Also, remember to do a full wipe after flashing.
Thanks
---------- Post added at 02:12 PM ---------- Previous post was at 01:51 PM ----------
putertim said:
I now have my M7088 again. Thank you . Your instructions where 100% right on.
Click to expand...
Click to collapse
No problem. Check my above post. I discovered the partition tables from the factory are wrong which could cause data corruption.
Thanks

i keep on getting this error when trying to reflash i follow the steps i dont know what im doing wrong? ..please help.
[can't open input file 'parm.img': No such file or directory
Error: mkkrnlimg could not decode partition table
[email protected]:~/Desktop/ExtractRomRK3066$

bird56duce said:
i keep on getting this error when trying to reflash i follow the steps i dont know what im doing wrong? ..please help.
[can't open input file 'parm.img': No such file or directory
Error: mkkrnlimg could not decode partition table
[email protected]:~/Desktop/ExtractRomRK3066$
Click to expand...
Click to collapse
Sounds like the path to the files is incorrect.
The command "sudo ./flashall-user.sh /media/F490-4740/dopo7088stock" will look for the media in the path specified.
The "sudo ./flashall-user.sh" is the command part of the line.
The path can be interpreted as "/media/" + "The USB Drive Name in the title bar of the window" + "/" + "The Folder the media is in that has the parm.img file."
For example: if you have the files that includes the parm.img file on the USB drive in a folder called "ROM" and the name of the USB drive at the top of the USB drive window is "ABCD-0123", the line would look like:
sudo ./flashall-user.sh /media/ABCD-0123/ROM
Hope this helps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

opening awsfai
mikeopi said:
Sounds like the path to the files is incorrect.
The command "sudo ./flashall-user.sh /media/F490-4740/dopo7088stock" will look for the media in the path specified.
The "sudo ./flashall-user.sh" is the command part of the line.
The path can be interpreted as "/media/" + "The USB Drive Name in the title bar of the window" + "/" + "The Folder the media is in that has the parm.img file."
For example: if you have the files that includes the parm.img file on the USB drive in a folder called "ROM" and the name of the USB drive at the top of the USB drive window is "ABCD-0123", the line would look like:
sudo ./flashall-user.sh /media/ABCD-0123/ROM
Hope this helps.
Click to expand...
Click to collapse
:good: I figured it out. thank you. I have another question what are the proper steps after flashing a new rom? I followed all your steps from dumping to flashing the new fixed rom, but cant get the device out of that stupid DOPO screen. After flashing with the new rom do you unplug it and reboot? BTW its not rooted. thanks

bird56duce said:
:good: I figured it out. thank you. I have another question what are the proper steps after flashing a new rom? I followed all your steps from dumping to flashing the new fixed rom, but cant get the device out of that stupid DOPO screen. After flashing with the new rom do you unplug it and reboot? BTW its not rooted. thanks
Click to expand...
Click to collapse
Hold the power key for about 15 seconds to force a shut down.
After shutting down, do you still get a stuck dopo screen?
If so, try a different USB port on the PC and try the procedure again. Sometime it does not seem to always take.
Make sure you are using the command sudo ./flashall.sh with the fixed rom. For the fixed rom to work, you have to flash all partitions. Then do a factory reset once it is fully booted.
Also, do a wipe. With the power off, hold the vol- and power key. This should bring you into the recovery menu. Do a wipe cache & wipe data/factory reset & reboot.

I have tried your technique at least 4 times and it doesn't work. I can't get through the Linux part with the downloaded file that you offer in your post. I get errors and I cannot go any further.
Either the file that you posted is not good or there is something else going on here. Any idea's? I have also seen other posts saying they cannot get past the errors.

mvalent000 said:
I have tried your technique at least 4 times and it doesn't work. I can't get through the Linux part with the downloaded file that you offer in your post. I get errors and I cannot go any further.
Either the file that you posted is not good or there is something else going on here. Any idea's? I have also seen other posts saying they cannot get past the errors.
Click to expand...
Click to collapse
Please give me more info on what the errors are and what command are they after?

mikeopi said:
Any information I give is to be used at your own risk. I take no responsibility for any damage to your device.
Here's my story: I installed an application to change the fonts after I rooted. This damaged the system and created a boot loop. At this point I had not worked out a reliable method to backup and restore the ROM and in the process of trying to fix, I wound up damaging the partitions trying to push a file back into the tablet with adb.
So in my research to restore the ROM, I came across several methods to flash the ROM, but very few methods to dump the complete ROM and I wanted to be able to extract and restore the entire ROM. In another thread, I found scripts to dump the rk3066 chipset. I expanded this idea and modified the scripts to flash the ROM as well. Also, I created an installer script to simplify the process.
These scripts need to use the Ubuntu Linux live DVD to dump and flash the ROM. The advantages of Linux is you can directly connect to the tablet in flash mode without the trouble of having to install drivers or the android SDK.
Download the Linux 12.04 LTS version from the following Link .
Once downloaded, burn this ISO file to a DVD using your favorite DVD burning software. Most burning software have the ability to decode ISO files. If needed, here is a free ISO burner. Link:
Download the attached zip file and copy the zip to the USB drive. Do not decompress in windows as we need to do this under linux to preserve the stored permissions.
Boot the PC from the DVD drive. This should start the Linux. You may need to press an “F” key during the BIOS boot to bring up a menu to select which drive to boot from. You should see a purple screen. This is Linux loading. Select the “Try Ubuntu” option and the Linux should boot to the Linux Desktop.
OK, we are in Linux!
Insert the USB drive into the PC wait for the Linux to open a window. It may take a little bit as we are running off a DVD and some resources need to load. Be patient and watch the light to finish blinking on the USB stick! Drag the “ExtractRomRK3066.zip” file in the USB window to the desktop.
Write down the name of the USB in the title bar of the window.
For example, My USB window says: F490-4740 in the title bar. Write this down, then move the USB window to the side.
Double click on the zip file, this opens the zip in a window. Drag the “ExtractRomRK3066“ folder in the zip window to the desktop. When the copy is finished, close the zip window.
Click on the “Dash Home” icon on the top left of the desktop, Type “Terminal” in the search box and select the terminal application icon.
In the Terminal Window type exactly as shown while observing the caps:
cd ~/Desktop/Ex*
Type the command:
ls -l
You should see a file named “install.sh” along with other commands ending with “.sh”.
Type the line as shown below including the “./”:
./install.sh
The required libraries should install to Linux. Don't worry this is only in memory as we are not installing anything to your hard drive. Make sure everything completed without Errors. If you only see warnings, this is OK!
Let's connect the Tablet to the USB port and put into flash mode. With the Tablet power off and the all cables removed, hold the Vol– button and plug in the USB cable. Continue to hold the Vol- button for 5 seconds. Let go of the Vol- button and connect the power cable. We should now be in flash mode.
We can test if we connected to flash mode by typing:
lsusb
You should see a list of USB devices. Within this list you should see a entry that has the ID:
ID: 2207:300a
If you see the ID, great we are connected to the tablet. If not, make sure the tablet is off and do the above Tablet procedure again.
OK we are connected!
Dumping the ROM
Type the following command replacing the “F490-4740” with your USB name we wrote down earlier from the USB title bar and follow the prompts. This will start the dump of the tablet:
sudo ./dumpall.sh /media/F490-4740/output
YAY! We are dumping the ROM!
Now we wait for “done...”, hopefully without any errors.
Double click on the “ output” folder in the USB drive window.
Verify that we have “backup.img”, “boot.img”, “kernel.img”, “misc.img”, “parm.img”, “recovery.img”, “system.img and userdata.img.
Now in the left panel of the USB window. Click on the ^ icon next to the USB drive description. This will unmount the USB drive for removal.
We are done!
Flashing the ROM
To flash a file you will notice other commands with the extension “.sh”. You may use any of these commands to restore all or part of the ROM.
For example:
To flash the below stock rom, extract the zip file to a USB drive and type the command changing the “F490-4740” to the name of your USB drive:
sudo ./flashall-user.sh /media/F490-4740/dopo7088stock
To flash a backup of all files including the userdata.img, type the command changing the “F490-4740” to the name of your USB drive:
sudo ./flashall.sh /media/F490-4740/dopo7088stock
To flash just the recovery, do the same as above only with the command:
sudo ./flashrecovery.sh /media/F490-4740/dopo7088stock
To flash just the system, do the same as above only with the command:
sudo ./flashsystem.sh /media/F490-4740/dopo7088stock
The valid command are:
sudo ./dump?.sh
or
sudo ./flash?.sh
replacing ? With:
all, all-user, backup, boot. cache, kernel, kpanic, misc, recovery, system, user, userdata
----------------------
Hope this helps somebody create a full backup.
Thanks.
UPDATE: I got another dopo m7088 tablet, created a backup using the above method and flashed my bricked m7088 tablet. Everything works again. YAY!
Below is the dumped stock rom for the dopo m7088. Hopes this help's sombody unbrick their tablet.
Extract the dopo7088stk.zip to a USB drive and follow the above instructions.
Thanks
Stock Rom Link:
Click to expand...
Click to collapse
I have tried this today about 8 times today. 4 with each folder you supplied in every usb port on my computer. I could do it all the way down to the dumping. I couldn't get any of the flashing working and my m7088 tablet is still stuck on the dopo screen. Please help as I would like to have this tablet working for my way home in a week.
I have Linux as a second os on my laptop so the first part was easy.
Thanks for your help so far. Good info

[Q] TWRP in a start-loop on my TF700

With the latest version of TWRP (2.8.5.0) I installed that zombi 5.02 rom a few days ago. It was running VERY slow, so I went back into TWRP a few hours ago and figured I would clean up the device and then re-install the rom.
So I used TWRP to wipe the device clean (I selected every partition to wipe, which I suspect is what the problem is). After doing this, I ran the install of the rom which seemed to run fine (although oddly, it seemed to install too fast, as opposed to when I installed it before).
Once I rebooted the device, I saw a quick message about a missing partition, and then it booted into TWRP recovery. but here is where the problem started. TWRP loads as far as you see the blue curtain background with test "teamwin" and then the screen clears for a sec, and then the blue curtain background appears again with the "teamwin" text.
This repeats forever. I can't get it to stop doing this.
I booted into fastboot, and via adb I re-installed the 2.8.5.0 twrp blob file. No errors during the install at all, however after rebooting the device, I am having the exact same issue.
I've tried re-installing twrp 3 times this way, but no matter what I do, I cannot get twrp to get out of this boot cycle.
It is odd that I can install twrp via adb over and over, yet it still has the same problem as before.
Even if i messed up by wiping every partition, why would the TWRP install succeeed, yet the program not run?
Anybody have an idea as to what I can do in order to get twrp back up and running? And if I do, is there something else I need to do to get all the partitions back up, or in theory will installing a rom re-create everything as needed?
Thanks for any help you guys can provide!

gbako said:
Once I rebooted the device, I saw a quick message about a missing partition, and then it booted into TWRP recovery. but here is where the problem started. TWRP loads as far as you see the blue curtain background with test "teamwin" and then the screen clears for a sec, and then the blue curtain background appears again with the "teamwin" text.
This repeats forever. I can't get it to stop doing this.
Click to expand...
Click to collapse
While TWRP is in the restart loop, you can try this on your connected PC:
Code:
adb pull /tmp/recovery.log
adb shell cat /proc/partitions > partitions.txt
The first gets TWRP's log file from which we should be able to see why it fails to start, the second gets a list of all partitions to see if mmcblk0p1 to ...p8 or ...p10 are there.

_that said:
While TWRP is in the restart loop, you can try this on your connected PC:
Code:
adb pull /tmp/recovery.log
adb shell cat /proc/partitions > partitions.txt
The first gets TWRP's log file from which we should be able to see why it fails to start, the second gets a list of all partitions to see if mmcblk0p1 to ...p8 or ...p10 are there.
Click to expand...
Click to collapse
--
I retrieved the logs as you suggested. I did this twice because after I retrieved the logs, I was looking at the partitions.log file and saw that only 3 partitions appeared. I know there should be more partitions (I don't know what they are called, but I know there should be more). So I was playing around with the fastboot.exe command, and I saw a command (fastboot -w). It said this command "erases userdata and cache". Well, it looked like something good to try, so I ran the command I've attached a file to this post called "fastboot.txt" that shows the output of this command.
Anyways, after doing this (thinking maybe this would do something), I went back into fastbook, and re-installed TWRP once again. Then I rebooted the tablet, and viola! It booted into twrp. Think I was so smart, I figured I would try to install my rom once again, so I started the installer of the rom, but at the very first screen of the installer where it shows device information, I saw what was obviously an issue. System size was showed as -1 MB, and Data Size was also shown as -1 MB. Not looking good, I exited the installer which puts me back into TWRP, and now I see a bunch of error messages about missing partitions.
On a hunch, I rebooted the tablet (back into reovery), and now I am back to the same thing, where TWRP will constantly load the blue curtain backgroud, show the word "teamwin" and then clear the screen, and repeat the process endlessly. So I now re-ran the two commands to retreive the partition info and the recovery log. The recovery log doesn't make much sense to me, but interestingly the partition log now shows a whole bunch more partitions. However, TWRP is once again back to it's boot loop.
So rather than re-trying my silly "fastbook -w" attempt, I will post this message, provide the request log info, and hope one of the experts here have a kind suggestion for me to try
Thanks guys for any help!
P.S. All the logs are in the ZIP file. I also attached a pic I took of the zombi rom installer, showing the partition size being -1 MB
The files "partitions1.txt" and "recovery1.log" are the files I retrieved from the tablet prior to using that "fastboot -w" command, the "partitions2.txt" and "recover2.log" are the files I retrrieved from the tablet after running that command, re-installing twrp and then having it go back into it's endless boot loop.

gbako said:
The files "partitions1.txt" and "recovery1.log" are the files I retrieved from the tablet prior to using that "fastboot -w" command, the "partitions2.txt" and "recover2.log" are the files I retrrieved from the tablet after running that command, re-installing twrp and then having it go back into it's endless boot loop.
Click to expand...
Click to collapse
Your logs indicate a problem with the "cache" partition. TWRP seems to crash after "Full SELinux support is present", and the next thing it does is trying to mount the cache partition. Your Fastboot log indicates a problem with cache too.
Try this:
Code:
adb shell make_ext4fs /dev/block/mmcblk0p2
(make sure you get the "p2" right *before* you press Enter!)
If this doesn't help, I also need the kernel log - do this after the previous command failed or within the first 3 minutes of a fresh boot into TWRP:
Code:
adb shell dmesg > dmesg.txt

That worked! Tablet works once again!
_that said:
Your logs indicate a problem with the "cache" partition. TWRP seems to crash after "Full SELinux support is present", and the next thing it does is trying to mount the cache partition. Your Fastboot log indicates a problem with cache too.
Try this:
Code:
adb shell make_ext4fs /dev/block/mmcblk0p2
(make sure you get the "p2" right *before* you press Enter!)
If this doesn't help, I also need the kernel log - do this after the previous command failed or within the first 3 minutes of a fresh boot into TWRP:
Code:
adb shell dmesg > dmesg.txt
Click to expand...
Click to collapse
---
That worked! Shortly after running that "adb shell make_ext4fs /dev/block/mmcblk0p2" command you had suggested, the tablet rebooted it self and the last ROM I had installed in it automatically booted up. It acted as though I had just installed it, so I went thru the standard setup (enter Google ID, etc...). The rom still runs pretty horribly (very slow and sluggish), but that's an issue with the rom hehe I am also able to boot back into TWRP without any problems. It seems that partition was the problem.
Thank you very much for your help; much appreciated!

I had the same problem with my TF700T with an endless loop in the TWRP start screen. I found an unkown device in my device manager called "TRANSFORMER" and i installed the Universal_Naked_Driver. Now i had access with ADB and i could clean the cache with the command here. Now my TF700T is back to life. Thanks a lot !

I seem to have a similar problem. The pad started having random reboots but it managed to fully boot. Since yesterday it is in the reboot loop. When trying to boot into twrp 2.8.7.4 it shows the teamwin screen for a short while and then reboots again.
I pulled the files requested above:
recovery.log
partitions.txt
dmesg.txt
I also tried:
Code:
adb shell make_ext4fs /dev/block/mmcblk0p2
which shows:
Code:
C:\adb>adb shell make_ext4fs /dev/block/mmcblk0p2
Creating filesystem with parameters:
Size: 448790528
Block size: 4096
Blocks per group: 32768
Inodes per group: 6848
Inode size: 256
Journal blocks: 1712
Label:
Blocks: 109568
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27392 inodes and 3534/109568 blocks
However the recommended steps don't seem to help in my case.
I'll attach the log files. (If I can find the attachment icon that is)
Thanks for any help you guys can provide!

Rom and bootloader version please. To attach the logs use your browser to access XDA

Hi berndblb,
thanks for the quick reply.
Rom version is : KatKiss-6.0_TF700T_022.zip
Boot loader taken from the fastboot screen: Android cardhu-user bootloader <1.00e> released by "ww_epad-10.6.1.14.10-20130801" A03
As to attaching the files I think I'm blind as I'm not seeing the option to do so.
Looks like this is only an issue in this threat as I do have the icon in other posts.

Yeahh I think I got it.
After much trying various recommendations I did
fastboot erase misc
fastboot erase userdata
This allowed me finally to go into recovery without a reboot.
I could flash the new KatKiss-6.0_TF700T_024.zip and now the pad is on it's first startup. So far so good. Crossing fingers.
Is it possible that a recently installed app could cause such a problem?

Cathrin said:
Yeahh I think I got it.
After much trying various recommendations I did
fastboot erase misc
fastboot erase userdata
This allowed me finally to go into recovery without a reboot.
I could flash the new KatKiss-6.0_TF700T_024.zip and now the pad is on it's first startup. So far so good. Crossing fingers.
Is it possible that a recently installed app could cause such a problem?
Click to expand...
Click to collapse
Hard to say... Could be...
I am not very good at reading logs but the only problem I see in dmsg is a failure to set cpu frquency. Were you running Zombi-Pop? Looks as if you were running a _that kernel at least. Did you overclock?

berndblb said:
Hard to say... Could be...
I am not very good at reading logs but the only problem I see in dmsg is a failure to set cpu frquency. Were you running Zombi-Pop? Looks as if you were running a _that kernel at least. Did you overclock?
Click to expand...
Click to collapse
I think my very first upgade to 5.1.1. lolli pop has been a Zombi-Pop and a overclocking yes. But since then only the KatKiss versions.
At least everything works fine again now.
So thanks for the help.

Looks like I have this constantly boot to twrp issue. It doesn't stay into twrp long enough to do anything.
adb pull /tmp/recovery.log
Gives me error: Protocol fault (couldnt read status: no error
adb shell cat /proc/partitions > partitions.txt
Gives me the same error above.
adb shell make_ext4fs /dev/block/mmcblk0p2
Gives me filesystem with parameters----created filesystem with 11/27392 inodes and 3534/109568 blocks
fastboot erase misc
Gives me waiting for device
I was on Katkiss 22 before this happened.
Any help would be appreciated.

Hi Isham.padron,
yes that sounds familiar.
I could only get the logs with adb shell or put when I hit return at a very specific moment.
It did fetch the files only when the blue teamwin window has been shown.
Though my recovery.log always looked a bit too short as if the reboot was coming in the way.
for me in the end only fastboot erase userdata did the trick. Everything else failed.

fastboot erase userdata cause it to wait but then nothing happens. ADB seems to be more responsive. IDK, I loved my TF700 and Katkiss gave it new life.

If you get 'waiting for device' your pc does not recognize the tablet. You may have to install fastboot drivers. Check the entry in Device Manager. How does the tablet show up?

In device manager is shows up as ADB. That kind of explains it. I'm using a windows 10 pro machine and I installed ADB/Fast boot with this http://forum.xda-developers.com/showthread.php?t=2588979
Are there issues with Win 10? I dont know how to proceed.
When I do the vol up(left) and power combo and it boots into twrp and then reboots regardless. I don't have the option screen anymore

Did you disable driver verification in Windows before running the tool? Otherwise they probably did not install properly. Windows is a pain with drivers and Win 8 and 10 are very finicky with fastboot...
Although if you have the adb composite interface showing up that's kinda good news. Watch the tablet and Device Manager at the same time and try to get a feeling for when the adb connection is there. Try to hit enter on the already typed 'adb devices' command and see what you get.
This could be tricky and rake many tries but you want to try is to push a small file to the tablet (bootit. ko) and then ins is that file to kick the tablet back into the bootloader. Probably your only chance..
Read this: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Good luck!

I am able to do this.
adb push bootit.ko /
results are (27690 bytes in .023s)
When I run "adb shell insmod bootit.ko" I get Error : protocol fault (no status)
I see that on windows it starts installing MTP USB but then it fails when the reboot happens. Tablet continues to reboot.

Any ideas? I miss the TF700

[Guide] How to Root LG v10 - Easy [1 Jan 2016]

Root Guide for the T-Mobile LG V10
Read Post #2 - Great Info​
Before we start, I like to mention that I did not create any of these files and I do not take credit for the work done. All I am doing is putting everything in one place and some helpful things that I had to google. This effort is mainly to make the process easier and more efficient as opposed to having to have several tabs or windows open to do it. I will make sure the proper thanks are given at the bottom
Click to expand...
Click to collapse
Instructions Start Here:
Warning - This will erase user data so you will have to set everything back up again! Always BACK UP YOUR DEVICE!!
1. Download the following tools for this process: adb-setup-1.4.3.exe, & twrp-2.8.7.1-h901.img, & UPDATE-SuperSU-v2.46.zip
Alternative ADB and Fastboot Option - (I Prefer) [GUIDE] Install Android SDK Standalone [ADB][30 Dec 2015] for Android SDK Standalone if you are interested
2. Install adb-set-up-1.4.3.exe to install the universal adb driver (Creates adb folder in C:\ if you don't already have adb setup)
3. Go to settings, about phone, software info and tap build number 5x to enable Developer Options
4. Check the Enable OEM unlock box to enable OEM Unlock
5. Enable USB debugging
6. Plug phone into the computer
7. Click on USB options on the phone and change it to PTP (USB Debugging will connect - Authorize Your Computer when prompted from phone)
Screenshots of Enabling USB Debugging and OEM Unlock
1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.
3.
4.
5.
6.
7. Open a Command Window and change directory to
Code:
[B]C:\adb[/B]
or if you have Android SDK type this below
Code:
[B]C:\Android\platform-tools[/B]
and type
Code:
[B][SIZE="3"]adb devices[/SIZE][/B]
8. You will Get Prompted after adb runs - Allow USB Debugging
8. From the Command Prompt, verify adb sees the device connected -
Open Command Prompt
Code:
cd C:\adb
Code:
adb devices
9. Reboot into the bootloader in command prompt by typing: adb reboot bootloader
10. You will now unlock the bootloader, verify, and Install TWRP
Note* - Make sure you copied twrp-2.8.7.1-h901.img into the C:\adb Folder already
Code:
[SIZE="3"]fastboot oem unlock
fastboot getvar unlocked
fastboot reboot-bootloader
fastboot flash recovery twrp-2.8.7.1-h901.img
fastboot boot twrp-2.8.7.1-h901.img[/SIZE]
11. You should be in TWRP Currently.
12. Reboot the device, it will delete user settings, so you need to repeat steps 3-8 to get adb set-up again
13. Now place UPDATE-SuperSU-v2.46.zip om your phone
14. Reboot into recovery
15. Back up YOUR EFS PARTITION
16. Wipe Cache and Dalvick Cache 3x
17. Flash UPDATE-SuperSU-v2.46.zip
18. You have successfully Unlocked the bootloader and Rooted your Device!!
19. SuperSU will prompt you to give tmobile.pr.adapt root privlidges, DENY
20. Navigate with Root Explorer to /system/priv-app/AdaptClient and rename AdaptClient.apk to AdaptClient.apk.bak and reboot
21. Finally, All done
Click to expand...
Click to collapse
USEFUL ROOTING LG V10 - by: Glenn Silvasy
Give Thanks To:
@KAsp3rd - http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740
@Chainfire - For Super User
@mikeyinid - Flashable Stock Image
@TheJesus - Providing img files for stock ROM, and OEM unlock Guide
@Snoop05 - ADB Drivers and Fastboot
And Anyone else that was missed!

Updated [31 Dec 2015]
References, Guides and Great Information - Please Read​
LG-H901 Stock .img Files (Boot, System, and Recovery)
Go Here
LG-H901 Stock Flashable ZIP in TWRP
Go Herehttp://forum.xda-developers.com/lg-v10/development/lg-h901-stock-images-device-restore-t3241170http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-images-device-restore-t3241170
TWRP
Go Here
ADB and Fastboot
Go Here #1
Go Here #2 - This can be reached from Go Here #1, but I posted it for a direct link to the tool just in case you miss it!
Android SDK Standalone Tools for ADB and Fastboot Devlopment Setup Guide
Go Here
Can't Get Into the Bootloader - Enter Fastboot Mode
Go Here
These links will have all the files you need in case you encounter any issues and I will also try to answer any questions within the scope of my knowledge. I been doing this for a while and there are tons of smart people on XDA. Please search for the question you want to ask to avoid issues, however, I do not believe in biting someones head off either. Researching is how you learn!! :good:

16. Wipe Cache and Dalvick Cache 3x
Click to expand...
Click to collapse
You seriously do not need to do that, this isn't 2010. In fact, if you ever do that when Xposed is installed, you'll cause a bootloop.

siraltus said:
You seriously do not need to do that, this isn't 2010. In fact, if you ever do that when Xposed is installed, you'll cause a bootloop.
Click to expand...
Click to collapse
Actually never caused a bootloop period...at worse it optimized all the apps installed which takes time, but hey thanks for the uneeded criticism
Edit: Also good thing xposed is not even a factor anyway. Sometimes you can not help being ignorant
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Actually never caused a bootloop period...at worse it optimized all the apps installed which takes time, but hey thanks for the uneeded criticism
Edit: Also good thing xposed is not even a factor anyway. Sometimes you can not help being ignorant
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
I'm opening my prompt within the folder adb installed to (C:\adb), adb devices command isn't finding anything. I have the necessary things ticked in developer options. Driver issue maybe? thanks

I never did numbers 15, 16 & 20. Not even sure what number 20 is for. Care to explain?

baySF said:
I never did numbers 15, 16 & 20. Not even sure what number 20 is for. Care to explain?
Click to expand...
Click to collapse
Your EFS partition contains your IMEI number and modem partition that allows you to connect to LTE and data services. This happens on Samsung devices, although rare, it does happen. It is good to just back it up just in case you flash and something happens to that partition, your phone essentially becomes a paper weight. I have always wiped cache and dalvick before flashing anything, feel free to do it if you like, not required.. Lastly, when you have root, that app is a T-Mobile app trying to request root permissions, do not allow it. It is an uneeded app. The only useful T-Mobile apps are the Visual Voicemail, Mobile Hot Spot and T-Mobile My Account.

sleekgreek said:
I'm opening my prompt within the folder adb installed to (C:\adb), adb devices command isn't finding anything. I have the necessary things ticked in developer options. Driver issue maybe? thanks
Click to expand...
Click to collapse
After you unlocked developer settings and checked USB Debugging, did you remember to change your connection from MTP to PTP, once you do that it should prompt you on the phone to allow the connection

bdorr1105 said:
After you unlocked developer settings and checked USB Debugging, did you remember to change your connection from MTP to PTP, once you do that it should prompt you on the phone to allow the connection
Click to expand...
Click to collapse
Yes all checked, I never get the prompt though. Also in the device manager I'm seeing The yellow exclamation for "abd interface". This is such a simple process And I've been jacking with it for awhile. I've run the 15 sec ADB several times already. On windows 10 btw
edit: changing to PTP also

sleekgreek said:
Yes all checked, I never get the prompt though. Also in the device manager I'm seeing The yellow exclamation for "abd interface". This is such a simple process And I've been jacking with it for awhile. I've run the 15 sec ADB several times already. On windows 10 btw
edit: changing to PTP also
Click to expand...
Click to collapse
I am on windows 10, so the adb driver is not installed. Did you run the universal adb driver I have posted in the OP. Run that, then ensure your phone is on PTP. If you still have that yellow exclamation point, right click, uninstall driver, then scan for hardware changes and once the driver is installed correctly, you will be good to go

bdorr1105 said:
I am on windows 10, so the adb driver is not installed. Did you run the universal adb driver I have posted in the OP. Run that, then ensure your phone is on PTP. If you still have that yellow exclamation point, right click, uninstall driver, then scan for hardware changes and once the driver is installed correctly, you will be good to go
Click to expand...
Click to collapse
adb-set-up-1.4.3.exe , yes I've installed that several times. I go to that installed folder (C:abd) and open my command prompt from within it. Maybe I'll just get the sdk again, seems like a real simple issue I can't get sorted. Freaking aggravating

sleekgreek said:
adb-set-up-1.4.3.exe , yes I've installed that several times. I go to that installed folder (C:abd) and open my command prompt from within it. Maybe I'll just get the sdk again, seems like a real simple issue I can't get sorted. Freaking aggravating
Click to expand...
Click to collapse
Well adb wont work unless the driver is working, in device manager, if you have the yellow exclamation point, it wont work. You should have seen the Google ADB driver installer come up like a normal windows program installation. Your driver is giving you problems
Try the attached drivers, just extract the zip and point the computer to look in the location of the extracted folder. See if it makes the exclamation go away

bdorr1105 said:
Well adb wont work unless the driver is working, in device manager, if you have the yellow exclamation point, it wont work. You should have seen the Google ADB driver installer come up like a normal windows program installation. Your driver is giving you problems
Try the attached drivers, just extract the zip and point the computer to look in the location of the extracted folder. See if it makes the exclamation go away
Click to expand...
Click to collapse
Thats a no go also, it's saying windows was unable to install. Thanks for the help, I have to crash though, down to 4 hours sleep before work because of this phone lol. I've never had this issue before, maybe tomorrow I can get it sorted out. thanks again

Running fastboot oem unlock will always wipe your user data

KAsp3rd said:
Running fastboot oem unlock will always wipe your user data
Click to expand...
Click to collapse
Thanks for that info, I am surprised it wipes your data or even touches the user partition. Never would have guessed it was from oem unlock
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Your EFS partition contains your IMEI number and modem partition that allows you to connect to LTE and data services. This happens on Samsung devices, although rare, it does happen. It is good to just back it up just in case you flash and something happens to that partition, your phone essentially becomes a paper weight. I have always wiped cache and dalvick before flashing anything, feel free to do it if you like, not required.. Lastly, when you have root, that app is a T-Mobile app trying to request root permissions, do not allow it. It is an uneeded app. The only useful T-Mobile apps are the Visual Voicemail, Mobile Hot Spot and T-Mobile My Account.
Click to expand...
Click to collapse
Is there a way to check if your IMEI was wiped? I still have data and can still send messages and makes calls but whenever I'm at work, I'll always get "voice access restricted" and I never got that on my nexus 5. I also lose connection to my Wi-Fi at work and at home randomly because it says "avoided poor connection". Granted all I have to do is turn Wi-Fi off then back on but it's very annoying. Again, never happened on my nexus 5.

baySF said:
Is there a way to check if your IMEI was wiped? I still have data and can still send messages and makes calls but whenever I'm at work, I'll always get "voice access restricted" and I never got that on my nexus 5. I also lose connection to my Wi-Fi at work and at home randomly because it says "avoided poor connection". Granted all I have to do is turn Wi-Fi off then back on but it's very annoying. Again, never happened on my nexus 5.
Click to expand...
Click to collapse
If you can access LTE than you are solid.. Trust me you will know, you will get rejected from the network.. It is in settings>about>status it will say 0 or be blank if it missing... Rather be safe than sorry
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Actually never caused a bootloop period...at worse it optimized all the apps installed which takes time, but hey thanks for the uneeded criticism
Edit: Also good thing xposed is not even a factor anyway. Sometimes you can not help being ignorant
Click to expand...
Click to collapse
Clearing Dalvik bootlooped both my G4 and my V10 as well as others with Xposed installed, so I'm passing the warning, no need to be butthurt. Thanks for calling me ignorant, stay classy!

siraltus said:
Clearing Dalvik bootlooped both my G4 and my V10 as well as others with Xposed installed, so I'm passing the warning, no need to be butthurt. Thanks for calling me ignorant, stay classy!
Click to expand...
Click to collapse
I cleared cache and dalvick 3 times after installing xposed, but xposed was updated... Look at how you decided to tell me, in a condescending manner so maybe when I explained my side in the aggressive manner you did which was unnecessary, but anyway, learn to be classy before you ask someone else to be classy. Have a great week and merry Christmas bud
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
I cleared cache and dalvick 3 times after installing xposed, but xposed was updated... Look at how you decided to tell me, in a condescending manner so maybe when I explained my side in the aggressive manner you did which was unnecessary, but anyway, learn to be classy before you ask someone else to be classy. Have a great week and merry Christmas bud
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Aggressive? Condescending? Wow. You need to check your ego at the door, buddy, it gets bruised way too easily.

Oneplus 7 pro keep going into fastboot mode

Hi,
I am in huge trouble. I bought this phone 2 weeks ago and 2 days ago installed android Q. This was mistake because after a some time phone was going to something called "Qualcomm dump mode" and that was it. Only thing to do was wait to battery goes down and restart.
So, I tried to go back, nothing from official ways works so I decided to go with TWRP and unblocking bootloader. And now I think I totally bricked my phone...
After command: "fastboot boot flash twrp.img" my phone only is restarting to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
( I don't know how to insert picture here)
Is it can be saved?? Or I screwed up all the way? Anyway thank you in advance for any kind of help.
My phone details:
Oneplus 7 pro ver. GM1910

you need the drivers id believe and in device manager on pc what you show is mtp with ! orob delete that restart device get drivers

I had the same. You can install the rom again via fastboot with Guac recovery (search on this forum)

Solex49 said:
I had the same. You can install the rom again via fastboot with Guac recovery (search on this forum)
Click to expand...
Click to collapse
I am getting:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.946s
Click to expand...
Click to collapse
ecompton59 said:
you need the drivers id believe and in device manager on pc what you show is mtp with ! orob delete that restart device get drivers
Click to expand...
Click to collapse
I kinda don't understand. And I no longer can find my device in Device manager
@edit
Also I have this info:

Connect your phone to your computer in Fastboot mode
Ensure you have installed the drivers for the phone : https://www.androidfilehost.com/?fid=3556969557455274390 (I've uploaded the drivers from Android 10 Open Beta 1 here too : https://www.androidfilehost.com/?fid=1899786940962579686)
Open a command window in the folder that the fastboot/adb tools have been installed to (By default the OnePlus drivers install those here : C:\Program Files (x86)\OnePlus USB Drivers\Android )
Enter the command fastboot devices
If you see a result from that command then the computer can see the phone correctly, if it's a blank line then it can't. In that case, try another usb port or cable.
Go here : https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Download the relevant package for the version you want to use
Extract the package and then run the flash-all.bat file
The script will then apply all default partitions for the version you have specified, this will wipe your data partition on the phone but, if you couldn't get into the phone in the first place, that's no big deal.
For good measure, once you have completed the install go into recovery and wipe the cache partition, I would actually use the factory default wipe option to start completely from scratch
Bear in mind though, you will still have an unlocked bootloader, to lock the bootloader again you would need to go into the developer settings and lock it and use the oem lock command
If you really want TWRP/Magisk back in then you'll likely need to use my workaround from here : https://forum.xda-developers.com/showpost.php?p=79961624&postcount=1210
Just use the fastboot getvar current-slot and fastboot set_active a or fastboot set_active b to track the active boot partition, that's very important for situations where the phone isn't booting correctly, a lot of the time it will be because you have the incorrect active slot enabled, in that case use the set_active command and the fastboot reboot command.
I would definitely recommend getting a usb drive you can use with the phone, there was an issue where TWRP couldn't see storage sometimes due to the difference between Android 9/10, using a usb drive to host the files you wanted to flash would help bystep encryption issues as the usb drive isn't encrypted.
I personally use these :
USB C to USB 3.0 Male Adapter : https://www.amazon.co.uk/gp/product/B07KXHNY5F
SanDisk Ultra USB Type-C 16 GB up to 130 MB/s USB 3.1 Flash Drive : https://www.amazon.co.uk/gp/product/B01BUSMYHC
When you use the drive it will make an "Android" folder, just throw your stuff in there, when you go to Install in TWRP you'll have a "SELECT STORAGE" button on the bottom left, that will let you use the usb drive, If you're using the File Manager in TWRP then it's listed under "usbstorage" in the main list.

djsubterrain said:
Connect your phone to your computer in Fastboot mode
Ensure you have installed the drivers for the phone : https://www.androidfilehost.com/?fid=3556969557455274390 (I've uploaded the drivers from Android 10 Open Beta 1 here too : https://www.androidfilehost.com/?fid=1899786940962579686)
Open a command window in the folder that the fastboot/adb tools have been installed to (By default the OnePlus drivers install those here : C:\Program Files (x86)\OnePlus USB Drivers\Android )
Enter the command fastboot devices
If you see a result from that command then the computer can see the phone correctly, if it's a blank line then it can't. In that case, try another usb port or cable.
Go here : https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Download the relevant package for the version you want to use
Extract the package and then run the flash-all.bat file
The script will then apply all default partitions for the version you have specified, this will wipe your data partition on the phone but, if you couldn't get into the phone in the first place, that's no big deal.
For good measure, once you have completed the install go into recovery and wipe the cache partition, I would actually use the factory default wipe option to start completely from scratch
Bear in mind though, you will still have an unlocked bootloader, to lock the bootloader again you would need to go into the developer settings and lock it and use the oem lock command
If you really want TWRP/Magisk back in then you'll likely need to use my workaround from here : https://forum.xda-developers.com/showpost.php?p=79961624&postcount=1210
Just use the fastboot getvar current-slot and fastboot set_active a or fastboot set_active b to track the active boot partition, that's very important for situations where the phone isn't booting correctly, a lot of the time it will be because you have the incorrect active slot enabled, in that case use the set_active command and the fastboot reboot command.
I would definitely recommend getting a usb drive you can use with the phone, there was an issue where TWRP couldn't see storage sometimes due to the difference between Android 9/10, using a usb drive to host the files you wanted to flash would help bystep encryption issues as the usb drive isn't encrypted.
I personally use these :
USB C to USB 3.0 Male Adapter : https://www.amazon.co.uk/gp/product/B07KXHNY5F
SanDisk Ultra USB Type-C 16 GB up to 130 MB/s USB 3.1 Flash Drive : https://www.amazon.co.uk/gp/product/B01BUSMYHC
When you use the drive it will make an "Android" folder, just throw your stuff in there, when you go to Install in TWRP you'll have a "SELECT STORAGE" button on the bottom left, that will let you use the usb drive, If you're using the File Manager in TWRP then it's listed under "usbstorage" in the main list.
Click to expand...
Click to collapse
Unfortunately, it is not working and I read that: These ROMs can't be used to update or downgrade your phone but just to restore your phone[...].
I am, I think, I am, at andorid Q and want to back to android 9
Yep, I am getting this:
@edit
Ok, had 100MB free space on my hdd... Sorry about that.
@edit2
Ok, thank You men, I managed to go throgu, but now after booting I have black screen. Should I now try to install some roms?

KramarSenior said:
Unfortunately, it is not working and I read that: These ROMs can't be used to update or downgrade your phone but just to restore your phone[...].
I am, I think, I am, at andorid Q and want to back to android 9
Yep, I am getting this:
@edit
Ok, had 100MB free space on my hdd... Sorry about that.
@edit2
Ok, thank You men, I managed to go throgu, but now after booting I have black screen. Should I now try to install some roms?
Click to expand...
Click to collapse
Due to the change in version you should really go to recovery and do a factory reset. See what happens after reboot then.

djsubterrain said:
Due to the change in version you should really go to recovery and do a factory reset. See what happens after reboot then.
Click to expand...
Click to collapse
Still black screen. At least I have no problems with booting an .img files. Already installed TWRP from offical but when I copied zip file with rom it is not see it.
@edit
Ok, I installed a rom but now phone is still loading (this red dot with 2 white dots running around) and nothing is happaning

djsubterrain said:
Due to the change in version you should really go to recovery and do a factory reset. See what happens after reboot then.
Click to expand...
Click to collapse
Ok, dude, love You, phone is working fine now. Andoid 9, and all I need to to is install updates. Thank You very much for help. I will press "thank you" buttons as soon as I get home.
Thread can be closed.

djsubterrain said:
Connect your phone to your computer in Fastboot mode
Ensure you have installed the drivers for the phone : https://www.androidfilehost.com/?fid=3556969557455274390 (I've uploaded the drivers from Android 10 Open Beta 1 here too : https://www.androidfilehost.com/?fid=1899786940962579686)
Open a command window in the folder that the fastboot/adb tools have been installed to (By default the OnePlus drivers install those here : C:\Program Files (x86)\OnePlus USB Drivers\Android )
Enter the command fastboot devices
If you see a result from that command then the computer can see the phone correctly, if it's a blank line then it can't. In that case, try another usb port or cable.
Go here : https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Download the relevant package for the version you want to use
Extract the package and then run the flash-all.bat file
The script will then apply all default partitions for the version you have specified, this will wipe your data partition on the phone but, if you couldn't get into the phone in the first place, that's no big deal.
For good measure, once you have completed the install go into recovery and wipe the cache partition, I would actually use the factory default wipe option to start completely from scratch
Bear in mind though, you will still have an unlocked bootloader, to lock the bootloader again you would need to go into the developer settings and lock it and use the oem lock command
If you really want TWRP/Magisk back in then you'll likely need to use my workaround from here : https://forum.xda-developers.com/showpost.php?p=79961624&postcount=1210
Just use the fastboot getvar current-slot and fastboot set_active a or fastboot set_active b to track the active boot partition, that's very important for situations where the phone isn't booting correctly, a lot of the time it will be because you have the incorrect active slot enabled, in that case use the set_active command and the fastboot reboot command.
I would definitely recommend getting a usb drive you can use with the phone, there was an issue where TWRP couldn't see storage sometimes due to the difference between Android 9/10, using a usb drive to host the files you wanted to flash would help bystep encryption issues as the usb drive isn't encrypted.
I personally use these :
USB C to USB 3.0 Male Adapter : https://www.amazon.co.uk/gp/product/B07KXHNY5F
SanDisk Ultra USB Type-C 16 GB up to 130 MB/s USB 3.1 Flash Drive : https://www.amazon.co.uk/gp/product/B01BUSMYHC
When you use the drive it will make an "Android" folder, just throw your stuff in there, when you go to Install in TWRP you'll have a "SELECT STORAGE" button on the bottom left, that will let you use the usb drive, If you're using the File Manager in TWRP then it's listed under "usbstorage" in the main list.
Click to expand...
Click to collapse
My current slot is "a" but if I try to use fastboot set_active b or fastboot --set-active=b it shows: usage: fastboot [ <option> ] <command> and shows me all the fastboot commands
also if I try : fastboot boot "recovery_name".img it shows : downloading 'boot.img'...
OKAY [ 2.119s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 2.162s
of course I tried fastboot flash boot "recovery_name".img and it flashes ok but when I try to reboot to recovery the bootloader pops up again
any ideas ?

Maybe try this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424