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?
Related
Hey there,
My Asus Transformer TF101 was working fine yesterday... I recently updated to ICS without any problem. I then rooted my device using viperMOD PrimeTime v4.5. Once again, everything worked without any problem.
After rooting, I ran the V6 SuperCharger script. The device rebooted and everything was fine... Then according to the instructions, I downloaded a modified version of the services.odex file and I replaced the original system file (I did kept the original file by changing the extention to .tmp). This is the last time I've seen my Transformer booting. I did this because of the reply from bsoplinger on this post:
http://forum.xda-developers.com/showthread.php?t=991276&page=906
The thing is that I forgot to change the owner:group to root:root and to chmod 644. I believe this is where I failed.
Asus Transformer TF101 B80
Rooted ICS with viperMOD PrimeTime v4.5
V6 SuperCharger Script activated (Choose Option #8)
Replaced original services.odex with a new "empty" one
Now, when booting it gets stuck on the Asus Logo with the rotating loading circles... they keep rotating forever until the battery is drained out.
This is what I tried:
Booting with Power button & Volume down then Volume down again (tried Cold boot and Wipe)
Booting with Power button & Volume down then Volume up (Recovery)
Booting with Power button & Volume up + NVFlash (won't work because it is not a B50-B60-B70)
Drained the battery to 0%
Put an official firmware update zip file on a microSD and booted with it
So.... this is pretty much it... As of now, I'm out of ressources and I don't know what else I can do... 40$ via Paypal to the first persone who gives me a working solution.
Thank you for your time!
If you have the original saved on your PC, try pushing it to your TF with ADB
So you can boot into recovery? If you can get into there I'm sure there are ways to fix your bricked device.
Which recovery are you using? If you don't have it already, I'd recommend installing CWM recovery and flashing a new kernal/rom.
There are plenty guides on how to do that, or I can try to walk you through it but if you managed to do that other stuff to your transformer I think you'd be able to follow the current online guides.
baseballfanz said:
If you have the original saved on your PC, try pushing it to your TF with ADB
Click to expand...
Click to collapse
Actually, the renamed original file is only on the internal SD card of the Transformer. I don't have a copy.
I am currently trying to ADB work... I installed the proper APX drivers but I get a message from Windows saying that the ASUS Android MTP Drivers failed to install and all I get from ADB/Fastboot is a "- waiting for device -" message...
I'm using Windows 7 Pro 64bit
Jfuginay said:
So you can boot into recovery? If you can get into there I'm sure there are ways to fix your bricked device.
Which recovery are you using? If you don't have it already, I'd recommend installing CWM recovery and flashing a new kernal/rom.
There are plenty guides on how to do that, or I can try to walk you through it but if you managed to do that other stuff to your transformer I think you'd be able to follow the current online guides.
Click to expand...
Click to collapse
Thanks for your reply. I am new to Android but as far as I know I can only get into the stock Asus recovery mode. I can't get (or don't know how to get into CWN recovery). CWM was supposed to be included in viperMOD PrimeTime v4.5 root but I am unable to boot in it.... I am trying to make ADB/Fastboot work to see if I can launch it from there but so far I can't make it communicate with my device...
When I press Power + Volume Down and then Volume Up, all I get is a green android robot with a black "!" in a red triangle...
I had the same issue for a while, on my windows 7, it seems there are multiple things that may be using the same resources you need for this process to work. Try ctr + alt + delete to view running processes, and shut down anything that may be using adb. It is crucial to shut down Asus sync, asus webstorage, etc, as they tie up your adb line when trying these methods.
I had bricked my transformer as well, and all the processes to fix it weren't working because of "waiting for device" messages.
They finally started working once I closed all other programs using adb.
Plus, with nvflash, make sure to unpack the Rom into the folder, rather than just having the rom's zip in the folder.
After fixing the "waiting for device" error, I still couldn't get mine to work because the rom wouldn't flash over as is, I had to take the "Prime" rom's tar located with in nvflash, and extract the files into the same folder.
Once I did that, I ran nvflash, and the rom transfered over fine and I was able to unbrick my device.
Yeah you are still on stock recovery.
Your best bet is to get adb working, you can then pull the file, renamed and push it back.
bArDBQ said:
Thanks for your reply. I am new to Android but as far as I know I can only get into the stock Asus recovery mode. I can't get (or don't know how to get into CWN recovery). CWM was supposed to be included in viperMOD PrimeTime v4.5 root but I am unable to boot in it.... I am trying to make ADB/Fastboot work to see if I can launch it from there but so far I can't make it communicate with my device...
When I press Power + Volume Down and then Volume Up, all I get is a green android robot with a black "!" in a red triangle...
Click to expand...
Click to collapse
Try what I mentioned about shutting down processes and hold down Volume up plus power when booting. You'll see a black screen but that's ok, you can verify that there is actually something going on because your computer should make the sound stating a new device has been connected to your pc.
From that black screen, you should be able to get nvflash to work, assuming you've shut down other programs that could be using adb, and have installed the correct driver for nvflash, and have also unpacked the prime rom into the nvflashf folder.
Jfuginay said:
I had the same issue for a while, on my windows 7, it seems there are multiple things that may be using the same resources you need for this process to work. Try ctr + alt + delete to view running processes, and shut down anything that may be using adb. It is crucial to shut down Asus sync, asus webstorage, etc, as they tie up your adb line when trying these methods.
I had bricked my transformer as well, and all the processes to fix it weren't working because of "waiting for device" messages.
They finally started working once I closed all other programs using adb.
Plus, with nvflash, make sure to unpack the Rom into the folder, rather than just having the rom's zip in the folder.
After fixing the "waiting for device" error, I still couldn't get mine to work because the rom wouldn't flash over as is, I had to take the "Prime" rom's tar located with in nvflash, and extract the files into the same folder.
Once I did that, I ran nvflash, and the rom transfered over fine and I was able to unbrick my device.
Click to expand...
Click to collapse
I will try to close all process that might use ADB but I already know that NVFlash will not help me since my device is a B80 and that NVFlash won't work with anything over B70
baseballfanz said:
Yeah you are still on stock recovery.
Your best bet is to get adb working, you can then pull the file, renamed and push it back.
Click to expand...
Click to collapse
I will make ADB working and see what I can do from that... Should not be that difficult.
I am installing Asus PC Suite since it seems to be the best way to get the missing drivers...
baseballfanz said:
Yeah you are still on stock recovery.
Your best bet is to get adb working, you can then pull the file, renamed and push it back.
Click to expand...
Click to collapse
I just can't get ADB to see my device...
I installed Asus PC Suite, it does detect the device and show it as "Nvidia USB Boot-recovery driver for Mobile device" in Window's device list when I boot using Power Button + Volume UP... When I launch adb from command prompt deamon starts but when I type "adb devices" it shows: "List of devices attached" but that's it... no devices in the list.
I deleted the "Nvidia USB Boot-recovery driver for Mobile device" and installed the default ASUSTeK Computer Inc. drivers I already had in Windows drivers list "ASUS Android ADB Device" but I get the exact same result.
I also tried to install the USB Drivers from ASUS website "ASUS_Android_USB_drivers_for_Windows.zip" but it seems like they are not made for Windows 7 64bits... The OS doesn't see them or won't install them...
AAAAAAAAAAAAHHHHHHH
When using ADB you do NOT put it into APX mode.
Try cold booting your TF, once it get to the Eee Pad screen where it's stuck.
See if ADB can recognize your device there.
baseballfanz said:
When using ADB you do NOT put it into APX mode.
Try cold booting your TF, once it get to the Eee Pad screen where it's stuck.
See if ADB can recognize your device there.
Click to expand...
Click to collapse
......... I installed Asus PC Suite, Droid Explorer... Installed/Reinstalled drivers... nothing works... I get the nVidia APX drivers to work but I just can't get the MTP Drivers to work... it is always saying that the Device can't start...
I don't know what to do.
bArDBQ said:
......... I installed Asus PC Suite, Droid Explorer... Installed/Reinstalled drivers... nothing works... I get the nVidia APX drivers to work but I just can't get the MTP Drivers to work... it is always saying that the Device can't start...
I don't know what to do.
Click to expand...
Click to collapse
{
"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"
}
Hi bArDBQ,
First of all, the driver pkg 'ASUS_Android_USB_drivers_for_Windows.zip' IS the correct pkg and contains both 32 and 64 bit drivers; the .INF (installer file will enumerate/choose the correct files)
The image you posted (Device Manager) isn't even showing ADB 'mode'; 'Android Device/Phone' should be at the top of the list, if you've already manually installed the drivers or 'Other devices|Unknown device' if you have not .
Make sure you have USB debugging enabled in Settings on the device
After enabling, when you connect to your PC you will have an ?unknown? device in Device Manager under 'Other devices' and have to install/update the drivers manually (unless the files from ASUS PC Suite are still in Windows driver store).
Right-click 'Unknown device' > Update Driver Software... > Browse my computer for driver software > Browse | Include subfolders - (choose the extracted folder 'Android' e.g., [ ASUS Android USB drivers for Windows_20110321\Android ] )
You can also update 'ASUS Android MTP Device' the same way; just choose the 'MTP' driver sub-folder instead of 'Android'
You probably could just choose the top-level folder (extracted USB Driver folder) when choosing for each driver (because we chose 'Include subfolders') but that's up to you.
HTH,
-JR-
baseballfanz said:
When using ADB you do NOT put it into APX mode.
Try cold booting your TF, once it get to the Eee Pad screen where it's stuck.
See if ADB can recognize your device there.
Click to expand...
Click to collapse
So, cold-booting did not help, when I do this, the device manager shows that the "ASUS Android MTP device" drivers failed to install. I get the Code 10 (This device cannot start)
jazzruby said:
Hi bArDBQ,
First of all, the driver pkg 'ASUS_Android_USB_drivers_for_Windows.zip' IS the correct pkg and contains both 32 and 64 bit drivers; the .INF (installer file will enumerate/choose the correct files)
The image you posted (Device Manager) isn't even showing ADB 'mode'; 'Android Device/Phone' should be at the top of the list, if you've already manually installed the drivers or 'Other devices|Unknown device' if you have not .
Make sure you have USB debugging enabled in Settings on the device
After enabling, when you connect to your PC you will have an ?unknown? device in Device Manager under 'Other devices' and have to install/update the drivers manually (unless the files from ASUS PC Suite are still in Windows driver store).
Right-click 'Unknown device' > Update Driver Software... > Browse my computer for driver software > Browse | Include subfolders - (choose the extracted folder 'Android' e.g., [ ASUS Android USB drivers for Windows_20110321\Android ] )
You can also update 'ASUS Android MTP Device' the same way; just choose the 'MTP' driver sub-folder instead of 'Android'
You probably could just choose the top-level folder (extracted USB Driver folder) when choosing for each driver (because we chose 'Include subfolders') but that's up to you.
HTH,
-JR-
Click to expand...
Click to collapse
Hello JR,
Thanks for the reply.
I manage to show the ghost devices and hidden device in the device manager. I deleted everything, and rebooted the computer. I connected the Transformer and cold-booted. Windows detected the device and I choose the MTP drivers from ASUS_Android_USB_drivers_for_Windows.zip but I got the same result. When I was booting using the Power Button + Volume Up Windows was detecting the device in ADB mode and I was able to install the proper drivers and make it work.
This said, it was impossible for me to get the Transformer in the device list in ADB. My computer simply can't connect to the tablet.
I can't make sure USB debugging is enabled in Settings on the device since the device do not boot but it was before it was bricked.
bArDBQ , did you ever get this working. it seems i'm in the same boat your in except i'm on b70
BiohazardPL said:
bArDBQ , did you ever get this working. it seems i'm in the same boat your in except i'm on b70
Click to expand...
Click to collapse
Hey,
No, I was unable to fix the problem. I returned the device to ASUS and my replacement unit is on its way. I guess I was lucky they were not able to fix it.
Since you are on a B70 you might be able to use NVFlash. You should try it if not already done.
Good Luck!
SON OF A BBBBBBbbbbb
Son of a bbbb... Son of a BBBB.... Son of a BBBB... hot damn. Ok Rooted, stock TF101. I was beta testing an app, and got the andy on his back with red triangle for my TF101 (us variant). I can see the Eee pad logo start, then nothing, only the back light stays on. Recovery leads to andy on his back. I tried Vol down + Power until reboot, then let it settle and come up with either choose to enter android or wipe data. Either one does nothing. Only the back light stays lit.
Recovery option is a no go.
Normal cold boot is a no go,
Hot boot is a no go.
PERI is a no go.
NVFlash is not tried yet.
ODIN is a no go.
12 pack of beer is a GO. Need more though I think.
Any assistance would be helpful.
UPDATE : Easyflash with the latest OFFICIAL Asus 4.0.3 update worked perfectly. NOTE : there was a simple partial file error that caused the problem.
Hi guys,
EDIT: Making some progress, the USB port was corrupted, now I can see my device in the adb devices list, yay!
EDIT2: After changing the USB port I was able to install the usb driver and after I connected with ADB I only run this code to get it working: http://forum.xda-developers.com/showpost.php?p=23339963&postcount=249
Sorry to bother you with this in a separate thread, however I am getting nowhere solving this and I've read through a lot of threads already without a clear solution. I am stuck in the CWM bootloop. I am using CWM 5.5.0.4, I am not able to get to the APX mode (if I understand correctly, that the APX mode is entered during boot presing the volume up button (with the two white lines of text appearing with a dead droid as background image)) (the tf101 is always booting to CWM). I've tried to install the naked drivers (http://forum.xda-developers.com/showthread.php?t=1379875) however my system won't accept them (I am getting an error message that the drivers aren't compatible with my device and that I have to make sure the drivers are for a 32bit OS, regrettably I am using a localized copy of windows so I can't paste the english error message). I've tried also other drivers like the one supplied with the android SDK (C:\Program Files\Android\android-sdk\extras\google\usb_driver\) and the ones coming with ViperMOD (http://forum.xda-developers.com/showthread.php?t=1427125), however the outcome is still the same. I've read somewhere to try to use a linux live cd (ubuntu) to flash an another version of CWM (recovery roach), however I couldn't find any guide on this approach.
So to summarize:
0) caused by Boot to recovery option (damn you!)
1) Stuck in CWM loop.
2) No access to SD card to flash another recovery from there
3) tf101 listed under USB in device manager as Unrecognized device with yellow triangle
4) Using win 7 32 bit
5) tried different usb drivers (sdk, naked, viperMOD), they don't install (used the select from list option in device manager, have disk...)
6) no access to external source (sdcard) to flash zip
7) adb not seeing device (adb devices gives empty list, adb remount gives device not found)
8) Tried EasyFlasher (but since the device isn't visible...)
9) installed asus synch and uninstalled afterwards as it didn't seem to help
Hopefuly I included everything I tried. Thanks in advance for any pointers.
I have a CM-10 nighty rom on the internal storage available, but I don't think this will help.
Jokob
{
"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"
}
jokob.sk said:
Hi guys,
EDIT: Making some progress, the USB port was corrupted, now I can see my device in the adb devices list, yay!
EDIT2: After changing the USB port I was able to install the usb driver and after I connected with ADB I only run this code to get it working: http://forum.xda-developers.com/showpost.php?p=23339963&postcount=249
Sorry to bother you with this in a separate thread, however I am getting nowhere solving this and I've read through a lot of threads already without a clear solution. I am stuck in the CWM bootloop. I am using CWM 5.5.0.4, I am not able to get to the APX mode (if I understand correctly, that the APX mode is entered during boot presing the volume up button (with the two white lines of text appearing with a dead droid as background image)) (the tf101 is always booting to CWM). I've tried to install the naked drivers (http://forum.xda-developers.com/showthread.php?t=1379875) however my system won't accept them (I am getting an error message that the drivers aren't compatible with my device and that I have to make sure the drivers are for a 32bit OS, regrettably I am using a localized copy of windows so I can't paste the english error message). I've tried also other drivers like the one supplied with the android SDK (C:\Program Files\Android\android-sdk\extras\google\usb_driver\) and the ones coming with ViperMOD (http://forum.xda-developers.com/showthread.php?t=1427125), however the outcome is still the same. I've read somewhere to try to use a linux live cd (ubuntu) to flash an another version of CWM (recovery roach), however I couldn't find any guide on this approach.
So to summarize:
0) caused by Boot to recovery option (damn you!)
1) Stuck in CWM loop.
2) No access to SD card to flash another recovery from there
3) tf101 listed under USB in device manager as Unrecognized device with yellow triangle
4) Using win 7 32 bit
5) tried different usb drivers (sdk, naked, viperMOD), they don't install (used the select from list option in device manager, have disk...)
6) no access to external source (sdcard) to flash zip
7) adb not seeing device (adb devices gives empty list, adb remount gives device not found)
8) Tried EasyFlasher (but since the device isn't visible...)
9) installed asus synch and uninstalled afterwards as it didn't seem to help
Hopefuly I included everything I tried. Thanks in advance for any pointers.
I have a CM-10 nighty rom on the internal storage available, but I don't think this will help.
Jokob
Click to expand...
Click to collapse
Give naked drivers one more shot... remove/uninstall/delete all existing drivers... restart you laptop.. unzip naked drivers into a folder, go to device manager and refresh, windows will try to install Asus driver, if you can stop it then do otherwise once its installed go back, right click and select upgrade/update... once this is done you should see 1st image attached. Now turn off your tablet while cable its to the laptop, press power+ volume up buttons together for say 10 secs and u will be in apx mode, laptop will show either installing apx drivers or unknown device found. If windows installs apx driver, again go back to device manager and delete that driver and manually install naked driver and when completed you should see image 2nd image... as you know while in apx mode tablet screen doesn't show much, now run easy flash and select SBK1 or SBK2 so that you can flash recovery, remember flash either rogue recovery of twrp but not cwm 5.x.x.x as it again blocks the access to external memory..... good luck
PS: windows will say "drivers r not safe/digital signatures are missing" or something like that when you try to install universal naked driver, don't worry just continue and finish it.
Sent from my Transformer TF101 using xda app-developers app
jokob.sk said:
I am not able to get to the APX mode (if I understand correctly, that the APX mode is entered during boot presing the volume up button (with the two white lines of text appearing with a dead droid as background image))
Click to expand...
Click to collapse
No, this is wrong.
Hold down the VOLUP + POWER Button until your tablet turns off and boots into APX mode (APX mode has no display - the screen will stay off)
It's working now. The culprint was the broken usb port. I tried an another one and I was able to proceed to fix my tf101 with help of the naked drivers and the fixed cwm 5.5.0.4 package and transfering it to the internal memory using ADB, so everything is fine now. Thanks for the response!
Sent from my Transformer using Tapatalk 2
AT&T Pantech Discover / Pantech Magnus / Pantech P9090
This thread will contain all info, resources, and tutorials about hacking and modifying your Pantech Discover. As our device shares much of its hardware with the One XL & Galaxy S III, I was able to port some things to our device. Not much, but some.
Useful Links
Pantech Discover ICS Kernel Source
Rooting Your Device
This method is very manual and very messy, hopefully I'll discover an easier method but for now this is the only way to do it.
1. Download the HTC One X ClockworkMod Recovery img.
2. Download the Superuser apk and the su binary, and copy them both to your sdcard (internal sd).
2. Turn off your phone. Hold down both volume buttons while pressing the power button to turn it on again. You'll get to a screen where you can use the volume keys to select fastboot mode, and press power to select it.
3. Once in fastboot mode, plug your device into your computer, and ensure that fastboot detects it.
4. Run the command "fastboot boot recovery-evita.img" to boot into the recovery.
5. Your device will stay at a blank screen, leave it plugged into your computer and wait about a minute for the computer to detect an "HTC device" in ADB recovery mode.
6. Type "adb shell", you should be presented with the # symbol, indicating that you have root access.
7. Run these commands to mount your partitions and copy the root files to your /system partition.
Code:
mount /dev/block/mmcblk0p14 /system
mount /dev/block/mmcblk0p25 /data
mount /data/media /sdcard
cd /sdcard
cp Superuser.apk /system/app/
cp su /system/xbin/
chmod 4755 /system/xbin/su
8. At this point, you can exit the adb shell and type 'adb reboot' to boot back into your ROM. You should see the Superuser app in your app drawer, open it to confirm you have root!
----------------------------------------
Partition Info/Dump, Custom Recovery Progress
The Pantech Discover has a total of 26 partitions in /dev/block, and they are as follows.
Code:
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 69.2MB 1573kB sbl1
3 69.2MB 70.8MB 1573kB sbl2
4 70.8MB 72.4MB 1573kB sbl3
5 72.4MB 75.0MB 2621kB aboot
6 75.0MB 76.5MB 1573kB rpm
7 77.1MB 86.5MB 9437kB boot
8 86.5MB 88.1MB 1573kB tz
9 88.1MB 88.6MB 524kB pad
10 88.6MB 92.8MB 4194kB rawdata
11 92.8MB 95.9MB 3146kB modemst1
12 95.9MB 99.1MB 3146kB modemst2
13 99.1MB 309MB 210MB ext4 preload
14 309MB 1568MB 1258MB ext4 system
15 1568MB 1569MB 1049kB dummy
16 1569MB 1578MB 8389kB ext4 persist
17 1578MB 1919MB 341MB ext4 cache
18 1919MB 2187MB 268MB tombstones
19 2187MB 2188MB 1049kB misc
20 2189MB 2199MB 10.5MB recovery
21 2200MB 2203MB 3146kB fsg
22 2203MB 2204MB 524kB ssd
23 2204MB 2225MB 21.0MB fat16 log
24 2225MB 2277MB 52.4MB fota
25 2278MB 15.6GB 13.4GB ext4 userdata
26 15.6GB 15.6GB 5226kB grow
Here is a link to a folder containing all of the partitions (excluding /data, obviously) to download. http://ul.to/f/hms3tr
Despite my best efforts, I've been unable to get CWM recovery running on this phone. I've dumped the recovery and built a CWM recovery image from the CM9 source, but the recovery.img that is produced does not boot properly. I've tried tons of different CWM recoveries for tons of different devices, and the only one that was successful was the evita CWM recovery.
Since there is no bootloader unlock for this phone, fastboot can't flash any partitions. I've attempted to dd multiple different recovery images to the recovery partition, but after a reboot the dd doesn't stick and the device boots into its original recovery. Maybe there needs to be something changed in the boot.img as well?
My custom ROM
Due to my inability to get CWM running in any form, CM9/10 is impossible so far. So, I've done the next best thing and manually decompiled and modded the stock ROM's framework/SystemUI. I gave the system an AOSP look with resources from the MattedBlues AOSP theme. As there is no way to provide a flashable zip with either my modded ROM or an installer for my theme, the best I can do is provide my system.img that you can download and dd to your system partition (dd if=systemTheme.img of=/dev/block/mmcblk0p14). So, here's my themed system.img.
Screenshots
{
"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"
}
See OP
See OP
keep up the good work
I just got the Pantech Discover and I love it! I might wait a little while longer until I root it, but I will continue to read your posts. Thanks for taking this project on.
See OP
Okay, here is the link to a folder containing all partitions in /dev/block, and a .rar of my themed ROM you see in the screenshots here (systemTheme.img.rar). http://ul.to/folder/hms3tr
It looks amazing! Keep up the awesome work!
First post updated, consolidated, and rewritten!
so i just switched to android from iphone. jailbreaking is what im used to.
sorry for being a noob or whatever.
i followed these directions. i get to where my phone goes black and then nothing. adb doesn't see any htc device. i like this phone. i want to unleash it unto the world... but alas im stuck at black.
any help would be fantastic.
thanks
jstnmlls said:
so i just switched to android from iphone. jailbreaking is what im used to.
sorry for being a noob or whatever.
i followed these directions. i get to where my phone goes black and then nothing. adb doesn't see any htc device. i like this phone. i want to unleash it unto the world... but alas im stuck at black.
any help would be fantastic.
thanks
Click to expand...
Click to collapse
Download pdanet for drivers probably. This link might help http://www.topnotchtablets.com/installADBdriver
Sent from my PantechP9070
jstnmlls said:
so i just switched to android from iphone. jailbreaking is what im used to.
sorry for being a noob or whatever.
i followed these directions. i get to where my phone goes black and then nothing. adb doesn't see any htc device. i like this phone. i want to unleash it unto the world... but alas im stuck at black.
any help would be fantastic.
thanks
Click to expand...
Click to collapse
mikey199 said:
Download pdanet for drivers probably. This link might help http://www.topnotchtablets.com/installADBdriver
Sent from my PantechP9070
Click to expand...
Click to collapse
Install the Universal Naked Driver. Right click the .inf's in the folder, and click install. Then try it, and be sure to wait a minute or two. Check Device Manager once you hear the Windows "device plugged in" sound.
nothing happens after fastboot boot recovery-evita.img
My phone is connected to my Windows 7 32 bit system and the drivers have installed successfully...well...all but one. It's the PC Data mode that fails during it's driver installation. The three other USB options that appear on the Pantech Discover's 'USB connection options menu' [Media device (MTP), Camera (PTP), and External memory (SD card)] have successfully installed and were each followed by an 'ADB Shell installation successful' confirmation as well.
I verified USB Debugging was selected within developer options and made sure the superuser and su binary files were saved to my internal SD card NOT my removable sd card.
At the command prompt i typed: cd c:\android (where my android files are located) > then 'fastboot boot recovery-evita.img' > the command window says its downloading boot.img...OKAY then booting...OKAY and then my phone simply turns off. I let it sit almost 30 min before attempting to power it back on. I had to remove the battery and USB cord before it would reboot. No damage done, my phone still functions properly.
Please help.
Oh! the name of the driver that fails installtion is titled 'Pantech P9090' in the device manager on my computer. When I turn the phone off the driver disappears after it shuts down, and just as it starts to charge while connected to the usb port on my computer, it suddenly attempts to install drivers for a generic 'Android' driver. Yes, as if my computer is detecting a totally seperate driver while it's in USB charge mode. don't know if it matters, just wierd is all.
any ideas?
thanks in advance,
- akafarmer
ShotSkydiver please can you check it Photo Sphere on device. It's work???
Many thanks!
Means if install it... or it's impossible.
And what do you think about 4.2 on it in future.
akafarmer said:
My phone is connected to my Windows 7 32 bit system and the drivers have installed successfully...well...all but one. It's the PC Data mode that fails during it's driver installation. The three other USB options that appear on the Pantech Discover's 'USB connection options menu' [Media device (MTP), Camera (PTP), and External memory (SD card)] have successfully installed and were each followed by an 'ADB Shell installation successful' confirmation as well.
I verified USB Debugging was selected within developer options and made sure the superuser and su binary files were saved to my internal SD card NOT my removable sd card.
At the command prompt i typed: cd c:\android (where my android files are located) > then 'fastboot boot recovery-evita.img' > the command window says its downloading boot.img...OKAY then booting...OKAY and then my phone simply turns off. I let it sit almost 30 min before attempting to power it back on. I had to remove the battery and USB cord before it would reboot. No damage done, my phone still functions properly.
Please help.
Oh! the name of the driver that fails installtion is titled 'Pantech P9090' in the device manager on my computer. When I turn the phone off the driver disappears after it shuts down, and just as it starts to charge while connected to the usb port on my computer, it suddenly attempts to install drivers for a generic 'Android' driver. Yes, as if my computer is detecting a totally seperate driver while it's in USB charge mode. don't know if it matters, just wierd is all.
any ideas?
thanks in advance,
- akafarmer
Click to expand...
Click to collapse
If you plug in/unplug your phone while it's on the black screen after booting the recovery image, does the computer make the sound that indicates a device is being plugged in/unplugged? Does any device, known or unknown, show up in the Device Manager?
I went through all the steps, everything went okay but I don't have root.
SuperUser opens, but when I checked with RootChecker, it doesn't have root - any ideas?
Also, how can we get back to complete stock?
Same here
Alekos said:
I went through all the steps, everything went okay but I don't have root.
SuperUser opens, but when I checked with RootChecker, it doesn't have root - any ideas?
Also, how can we get back to complete stock?
Click to expand...
Click to collapse
Unfortunately, I'm having the same issue. I went through all the steps with no issues at all, but when I rebooted my device and installed Titanium Backup, it said it couldn't obtain root access. I was really hoping this would work so I could restore some of my programs from my old phone. OP, any idea why it may not be working?
Also, if we can figure out why this isn't working, I've got another wish... Google Now. I've seen info online about flashing Now to ICS devices with CWM, but I know we don't have access to that yet. Is there any way we can do it via this same method. I'm not an ADB/Shell guru at all, so I'm not sure how to make it work. Any advise would be greatly appreciated.
Thanks in advance for on both topics!
Wow...
Wow, these look amazing. Very impressed. I'm hesitant about getting a Discover because it only has ICS. Keep it up and I'd love to throw on what you have going. Good luck.
Wow! Maybe I'm not as dumb at this as I thought... I reviewed the initial instructions and then did some searching. I found several instances where the CHMOD command was used with 4755 instead of 0755 as listed in the instructions. I know that CHMOD is used to change the permissions a file has (read, write, execute), so I figured maybe the "0" wasn't setting the correct permissions. I went through the instructions again and changed it to CHMOD 4755, rebooted, and... tah-dah! I have root access. Yay!
Oh... one other thing. I also didn't check the "USB debug" option in developer options before, so I did that too. I'm not sure if that had something to do with it, but I really think it was the read/write accesses.
Now... if someone could help with my "Google Now" request, that would be AWESOME!! Loving this phone so far!
Any more progress?
I just go my Pentech Discover yesterday. I was wondering if there was any more progress on this phone. I can't do much until my trial period runs out, but I would be willing to test after that. It seems like a very quick, responsive phone. Also, do you have an IRC channel on freenode or anything like that? Thanks.
What about TWRP?
I was also wondering if you had tried to install TWRP on the Pantech Discover? There is an HTC One X Evita image on their web site. I have a Kindle Fire 2, and I have Cyanogenmod Jelly Bean 4.2.2 on it by having the locked bootloader jump to TWRP and then to Cyanogenmod. I don't know much about actual development, but I thought this might be a possible solution as you had used the CWM evita image.
First of all this is my first post and I am a complete NOOB.
Also I apologize in advance if I break any rules with this post and please excuse my terrible grammar and spelling.
Computer 1:Windows 7 Ultimate 32bit
Computer 2:Ubuntu 12.04 LTS
Device: Amazon Kindle Fire 2nd Gen
I will try to provide as much information as I can stating how I got here
Eastern Time:
11:00pm : Decided to root and flash a custom rom on my friends kindle fire hd 10.4.6 have rooted and flashed my first gen kindle and a galaxy s before successfully. So i looked around the forums and found this http://forum.xda-developers.com/showthread.php?t=2494232 The last comment lead me to this site staticchaos.freeoda.com/fire/ where I downloaded the following files
1)Kindle Fire USB driver
2) RootFire.zip
The RootFire.zip had http://imgur.com/uqFGWyu
and i rooted the device using the RunME shown http://imgur.com/OCYoM9p
11:49pm: Happy and dandy rooted and superuser was installed no problem now I had to install TWRP so I followed http://forum.xda-developers.com/showthread.php?t=2404120 and
I thought everything was fine until I realized that in the post the version he says to download is CM-10.1 and I had downloaded cm-11-20140106-NIGHTLY-otter2.zip from the link he provided. I realized that after I was in TWRP after wiping all the caches and the system I went to install it and it gave me an error which i don't remember what it said.
12:40am: So now im trying to figure how the hell to mount the kindle back so I can transfer the rom out and put the correct one in. I see there is a mount option in TWRP but it would always show up as a hidden removeable disk and when i looked at the command line it said
"E: unable to locate volume information for usb storage mode"
So i googled that and found this post http://forum.xda-developers.com/showthread.php?t=2274315
I figured okay I don't have a fastboot cable so let me try the sideboot loader. But now my computer running windows 7 ultimate 32 bit was not recognizing the kindle like before. It came up as kindle fire2 and the previous drivers werent working
so when i ran cmd an issued the adb devices command nothing showed and I was unable to sideload anything.
So then i got to thinking the error said it could not locate volume information, there was an option in TWRP that said format or partition I don't remember so the idea in my noob brain was ill partition a small part of the memory inside to hold the correct ROM and than flash it using TWRP and problem solved. until this point I could turn my kindle off and on and be able to get into TWRP no problem just hitting the power button.
After the third try of partitioning and each time failing because it could not mount "/data"
i got fustrated and went looking for answers but the kindle was dying at 3% so i shut it off and let it charge while i looked. MISTAKE
i powered it off via the power button and the light disappeared when I went to turn it on again I had no luck BLACK SCREEN and nothing
SO i turned on my xbox and decided Ill play while it charges.
1:40am: no luck nothing on the screen cant get it to come up on the computer F Me i bricked this thing. Finally wiggle the usb around plug out of the hub and directly into the computer and BAM OMAP4430 is being connected and disconnected continuously
YES WE HAVE LIFE. So i began looking at what it is and found several post
http://forum.xda-developers.com/showthread.php?t=1413951
http://forum.xda-developers.com/showthread.php?p=20565446
http://forum.xda-developers.com/showpost.php?p=19800610&postcount=74
First i found out that im in the "cpu's USB boot mode. You need to send the cpu something to boot over usb or it will loop forever trying to find something to boot off flash".
so I powered up my vmware and transfered all the files in I would need to run 2) Open a terminal and sudo or su to root. It's easier that way.
3) Unplug the USB or AC adapter if it's plugged into the KF. But have the USB cable's A end plugged into the PC. This is very important.
4) Turn the power completely off. Do a shutdown if actually running Android, or hold the power button until there's no LED or backlight.
5) Pry open the back cover. The iFixit teardown (Google it) gives some ideas on how to do it, but be really careful because it's easy to snap the tabs along the long sides. DID NOT DO THIS SINCE I HAD READ ELSEWHERE I WAS ALREADY IN THIS MODE
6) The power must still be off. If you accidentally powered it back on, turn it back off.
7) Run:
Code:
./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img
This will chain load aboot, FIREFIREFIRE, then TWRP.
This got me nothing expect waiting for
OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
unexpected 2ndstage response
< waiting for device >
and then the terminal just stood there so then on another thread I read
http://forum.xda-developers.com/showthread.php?t=1413358
" run the script usb_fix_parts_and_install_fff_twrp and plug your device in while off when it says <waiting for omap44xx device> in the terminal. The script should run when your device boots up because it`s in this state. I don`t believe you will even need the short trick"
yes a solution finally after looking for so long!
3:37am: download the files run the script run the
[email protected]:/home/orlando/Desktop/rekindle/rekindle# ./fk
5837+1 records in
5837+1 records out
5977554 bytes (6.0 MB) copied, 4.69615 s, 1.3 MB/s
Stopping any running adb servers...
Done. Tools are in /root/firekit. Files copied to USB are likely in /cdrom
Scripts:
install_fff_twrp_from_stock - install FFF and TWRP while in stock Android
install_fff_twrp - install FFF and TWRP while in fastboot
fix_parts - restore partition table to stock while in fastboot
normal_boot - set the bootmode to boot android and reboot while in fastboot
usb_boot_twrp - USB boot TWRP without installing
usb_install_fff_twrp - USB boot FFF, install FFF and TWRP
usb_fix_parts_and_install_fff_twrp - USB boot FFF, restore partition
table to stock, install FFF and TWRP
Good luck. -pokey9000
[email protected]:~/firekit#
[email protected]:~/firekit#
[email protected]:~/firekit#
[email protected]:~/firekit# usb_fix_parts_and_install_fff_twrp
Loading FFF through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
unexpected 2ndstage response
Fixing partitions...
< waiting for device >
"YES ITS GONNA FIX IT"
20 mins later
"NOPE"
It froze there and the kindle kept connecting and disconnecting it is now 4:30am
it will still only connect and disconnect as OMAP4430
If the developers or someone who knows more than me would be kind enough to lead me in the right direction I would appreciate it
I have tried hard to fix this thing and no luck.
+1
+1
Is this considered as terminal?
As a super hard core bricked?
*i'm here now all ill be doing now buying is broken Screen Kindle and assemble with my good screen
Try search on YouTube for Tekify lollipop or marshmallow on Kindle fire HD. He has a real easy to follow step by step. I used him on 2 kindles both with success in minutes.
Or: www.tekify.co.uk/kindle-fire-hd/roms/cyanogenmod-13-6-0-marshmallow
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