Related
Hi All,
i have unlocked bootloader, Rooted ICS
now i installed the latest JB update via the SD card method (renaming it to E201_768_SDUPDATE).
did the power+vol down method. intstalled it and reboot.
now all i get is this message coming up.
"The Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image"
and it gets stuck there at the ASUS screen.
i have tried to install the APX driver from universal driver 0.7 TF700, and all i get is unknown device in win7 device manager.
hence i cant get into NVflash or Fastboot.
is there anything else that i can do to unbrick this tablet.
are there any other drivers that i need to install in win7 x64 or it to recognize that it is an asus tablet.??
Looks like the JB update didn't write everything properly - you still have the old bootloader. You should really have created backups for nvflash before trying to upgrade to JB.
But it's still not too late. Can you switch yout device to fastboot mode? If yes, then it's just a matter of getting your PC configuration right.
Then the next thing I would do: re-flash some custom recovery via fastboot, make sure it works and you have adb root access, check if /sdcard is ok, then install the AndroidRoot bootloader to create your blobs for nvflash, reboot into recovery, pull the blobs to your PC via adb, and only then try to upgrade to JB again.
_that said:
Looks like the JB update didn't write everything properly - you still have the old bootloader. You should really have created backups for nvflash before trying to upgrade to JB.
But it's still not too late. Can you switch yout device to fastboot mode? If yes, then it's just a matter of getting your PC configuration right.
Then the next thing I would do: re-flash some custom recovery via fastboot, make sure it works and you have adb root access, check if /sdcard is ok, then install the AndroidRoot bootloader to create your blobs for nvflash, reboot into recovery, pull the blobs to your PC via adb, and only then try to upgrade to JB again.
Click to expand...
Click to collapse
Hi, no unfortunately i cant access fastboot, i have tried using the TWRP method of and all i get it a message saying waiting for device. when i try to push the TWRP.blob file.
i think my problem is that the usb device drivers are not working hence win7 x64 cant recognize the tablet when it is turned off (APX mode i believe)
dazzyd said:
Hi, no unfortunately i cant access fastboot, i have tried using the TWRP method of and all i get it a message saying waiting for device. when i try to push the TWRP.blob file.
Click to expand...
Click to collapse
Let's check it step by step:
- On the device, can you still activate the fastboot mode (USB icon)?
- On your PC, you should see a USB device with vendor ID 0b05 and product ID 4daf. Should be visible somewhere in Device Manager under Windows, maybe someone else can give you details (under Linux everything is much simpler with lsusb).
- On the PC, "fastboot devices" should give you more than no output at all (some question marks, AFAIR).
_that said:
Let's check it step by step:
- On the device, can you still activate the fastboot mode (USB icon)?
- On your PC, you should see a USB device with vendor ID 0b05 and product ID 4daf. Should be visible somewhere in Device Manager under Windows, maybe someone else can give you details (under Linux everything is much simpler with lsusb).
- On the PC, "fastboot devices" should give you more than no output at all (some question marks, AFAIR).
Click to expand...
Click to collapse
Hi again, no i cant see the usb icon,
i am only getting this Asus screen
the Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image"
and it gets stuck there at the ASUS screen.
dazzyd said:
and it gets stuck there at the ASUS screen.
Click to expand...
Click to collapse
And if you hold down Volume-down while powering on, it's the same? In that case, 3 icons should appear before it tries to start the recovery kernel.
_that said:
And if you hold down Volume-down while powering on, it's the same? In that case, 3 icons should appear before it tries to start the recovery kernel.
Click to expand...
Click to collapse
yes i have tried holding down the volume-down while power on and still nothing. no icons appear.
dazzyd said:
yes i have tried holding down the volume-down while power on and still nothing. no icons appear.
Click to expand...
Click to collapse
Sorry, then I am out of ideas.
dazzyd said:
Hi All,
i have unlocked bootloader, Rooted ICS
now i installed the latest JB update via the SD card method (renaming it to E201_768_SDUPDATE).
did the power+vol down method. intstalled it and reboot.
now all i get is this message coming up.
"The Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image"
and it gets stuck there at the ASUS screen.
i have tried to install the APX driver from universal driver 0.7 TF700, and all i get is unknown device in win7 device manager.
hence i cant get into NVflash or Fastboot.
is there anything else that i can do to unbrick this tablet.
are there any other drivers that i need to install in win7 x64 or it to recognize that it is an asus tablet.??
Click to expand...
Click to collapse
You're done. You need to send out for repair. Sorry, but I haven't see any one here able to recover the device with the above message.
buhohitr said:
You're done. You need to send out for repair. Sorry, but I haven't see any one here able to recover the device with the above message.
Click to expand...
Click to collapse
hmm bummer.. no other way to force install a device driver to detect the tablet on my win7 pc.? all i need is a glimmer of hope that i can still talk to the tablet at the lowest level interface. ie APX mode.
dazzyd said:
hmm bummer.. no other way to force install a device driver to detect the tablet on my win7 pc.? all i need is a glimmer of hope that i can still talk to the tablet at the lowest level interface. ie APX mode.
Click to expand...
Click to collapse
The driver on your PC is not the problem. For using nvflash in APX mode you'd need the Secure Boot Key, which is unique for each device and which Asus does not give us, or the blob for the wheelie tool that can be created with the AndroidBoot hacked bootloader, which is also unique for each device. But for creating this blob, you need working fastboot access.
I updated to the newest version from asus site Version WW_V10.6.1.8 and then by mistake flashed the latest version of TWRP recovery. now the tablet is bricked. I cant access fast mode, no adb. it only boots into recovery each time but I cant restore anything and cant access external sd card. please help!!!
tainka said:
I updated to the newest version from asus site Version WW_V10.6.1.8 and then by mistake flashed the latest version of TWRP recovery. now the tablet is bricked. I cant access fast mode, no adb. it only boots into recovery each time but I cant restore anything and cant access external sd card. please help!!!
Click to expand...
Click to collapse
If the tablet is new and you still have the receipt my best advice is to try and take to the store and they will exchange it for you. other than that your only choice is to try and see if updating the drivers from Asus or even using another PC let's you gain access to Fastboot. Other than that the incompatible version of TWRP that you flashed most likely bricked your device.
Erik
When tablet will be in twrp, in connect tablet to PC and command "adb reboot bootloader". Now flash asus 4.2.1 via fastboot
Hazard17 said:
When tablet will be in twrp, in connect tablet to PC and command "adb reboot bootloader". Now flash asus 4.2.1 via fastboot
Click to expand...
Click to collapse
ok, this worked! I have fastboot but adb shell does not work. The weirdest thing is when I press the green android icon in boot loader screetn the system boots normally!!!! but!!! when i do restart it always boots into the twrp screen. the only way to boot the system is with your command. I tried to flash the patched recovery which works with the new firmware (the flash is ok) but i cant pass the recovery screen. How can I get rid of this recovery????
Hi,
I tried to install a ROM but it got stuck on the white screen with the HTC logo. I tried to do factory reset but it gets stuck again. I don't have clockwork recovery, and I rooted my phone using adb and ace recovery, which is not on my phone. I only temporarily used it to flash my rom, stupid I know. :-/ When I connect my phone to the PC it is not being recognized. I tried putting the PD98IMG.zip file on my sd card but it just says that it the image is incorrect. Is there anything I can do? Is this fixable?
brickdummy said:
Hi,
I tried to install a ROM but it got stuck on the white screen with the HTC logo. I tried to do factory reset but it gets stuck again. I don't have clockwork recovery, and I rooted my phone using adb and ace recovery, which is not on my phone. I only temporarily used it to flash my rom, stupid I know. :-/ When I connect my phone to the PC it is not being recognized. I tried putting the PD98IMG.zip file on my sd card but it just says that it the image is incorrect. Is there anything I can do? Is this fixable?
Click to expand...
Click to collapse
Flash a recovery.img from fastboot. What is an ace recovery? Read my signature for the HTC logo problem.
brickdummy said:
Hi,
I tried to install a ROM but it got stuck on the white screen with the HTC logo. I tried to do factory reset but it gets stuck again. I don't have clockwork recovery, and I rooted my phone using adb and ace recovery, which is not on my phone. I only temporarily used it to flash my rom, stupid I know. :-/ When I connect my phone to the PC it is not being recognized. I tried putting the PD98IMG.zip file on my sd card but it just says that it the image is incorrect. Is there anything I can do? Is this fixable?
Click to expand...
Click to collapse
I just went through some similar stuff. What type of computer are you using? PC/Mac? Are you using the original cable? What troubleshooting steps for connectivity have you done? Different cable? USB port?
Can you access the bootloader screen when you pull the battery and reboot while holding the volume button down and holding the power button? By accident, I found that the phone and PC will communicate with each other when "Fastboot" is selected on the bootloader screen (you should hear a connection chime and it should change to "Fastboot USB") except I could only get fastboot commands to work. The good news is that should be enough to flash a boot or whatever else you need to get back in business.
shadowboxx said:
I just went through some similar stuff. What type of computer are you using? PC/Mac? Are you using the original cable? What troubleshooting steps for connectivity have you done? Different cable? USB port?
Can you access the bootloader screen when you pull the battery and reboot while holding the volume button down and holding the power button? By accident, I found that the phone and PC will communicate with each other when "Fastboot" is selected on the bootloader screen (you should hear a connection chime and it should change to "Fastboot USB") except I could only get fastboot commands to work. The good news is that should be enough to flash a boot or whatever else you need to get back in business.
Click to expand...
Click to collapse
Hi, Thanks for the reply.I am using windows 7. I downloaded the drivers for HTC, and I am using a data cable and the USB port in the back of my computer, nearest the mother board. I do see "Fastboot USB" on the phone but when i type in the command prompt "adb devices" I get nothing.
brickdummy said:
Hi, Thanks for the reply.I am using windows 7. I downloaded the drivers for HTC, and I am using a data cable and the USB port in the back of my computer, nearest the mother board. I do see "Fastboot USB" on the phone but when i type in the command prompt "adb devices" I get nothing.
Click to expand...
Click to collapse
That's great you're getting the fastboot usb message! As long as you're not using a hub or some other usb extender, any functioning usb port on the pc will do. Again, I learned this by accident (ie the hard way) and found that in this mode, only fastboot commands will work, not adb. (on a side note, and others should correct me here, adb and fastboot work together when the phone is rebooted normally or in recovery but not in the bootloader screen)
Great test for connection: fastboot devices (if you get anything else except a serial # with fastboot after it, then close the cmd window, unplug, and pull battery/reboot to bootloader), fastboot reboot-bootloader. Once it reboots back into the bootloader screen, make sure you press the power button while fastboot is selected and you should again hear the chime and see fastboot usb come up. This is your phone saying it's ready to accept your fastboot commands.
Do let us know how it works.
bananagranola said:
Flash a recovery.img from fastboot. What is an ace recovery? Read my signature for the HTC logo problem.
Click to expand...
Click to collapse
Hi I actually saw your post earlier thank you. I will work on this. I found it in a tutorial when I rooted my phone with HTC dev, ace_recovery_ext_4.img. I'll post where i found it later.
bananagranola said:
Flash a recovery.img from fastboot. What is an ace recovery? Read my signature for the HTC logo problem.
Click to expand...
Click to collapse
when i flashboot the recovery.img file it goes to the red triangle.
brickdummy said:
Hi I actually saw your post earlier thank you. I will work on this. I found it in a tutorial when I rooted my phone with HTC dev, ace_recovery_ext_4.img. I'll post where i found it later.
Click to expand...
Click to collapse
Hi the program is actually called 4EXT Recovery Touch. I finally was able to open it through fastboot....Now all thats left is to find the right zip file to put my phone back to stock.
shadowboxx said:
That's great you're getting the fastboot usb message! As long as you're not using a hub or some other usb extender, any functioning usb port on the pc will do. Again, I learned this by accident (ie the hard way) and found that in this mode, only fastboot commands will work, not adb. (on a side note, and others should correct me here, adb and fastboot work together when the phone is rebooted normally or in recovery but not in the bootloader screen)
Great test for connection: fastboot devices (if you get anything else except a serial # with fastboot after it, then close the cmd window, unplug, and pull battery/reboot to bootloader), fastboot reboot-bootloader. Once it reboots back into the bootloader screen, make sure you press the power button while fastboot is selected and you should again hear the chime and see fastboot usb come up. This is your phone saying it's ready to accept your fastboot commands.
Do let us know how it works.
Click to expand...
Click to collapse
Hi, this did work, thank you. Would you happen to know how i can load the stock software on my phone? I had it rooted before im not sure if its still rooted. I also managed to get the 4ext recovery on my phone too.
shadowboxx said:
(on a side note, and others should correct me here, adb and fastboot work together when the phone is rebooted normally or in recovery but not in the bootloader screen)
Click to expand...
Click to collapse
As far as I know, fastboot only works when your phone is in fastboot mode. ADB works in recovery or system.
brickdummy said:
Hi, this did work, thank you. Would you happen to know how i can load the stock software on my phone? I had it rooted before im not sure if its still rooted. I also managed to get the 4ext recovery on my phone too.
Click to expand...
Click to collapse
Flash a rooted stock ROM from recovery. Whether you have root is in your system partition. Whether your bootloader is unlocked is in your bootloader. Whether you have a custom recovery is in your recovery partition. Three separate things.
As for your post in your other thread, read my signature.
bananagranola said:
As far as I know, fastboot only works when your phone is in fastboot mode. ADB works in recovery or system.
Flash a rooted stock ROM from recovery. Whether you have root is in your system partition. Whether your bootloader is unlocked is in your bootloader. Whether you have a custom recovery is in your recovery partition. Three separate things.
Click to expand...
Click to collapse
I'm sorry, I have no idea what I am doing. Can you show me the steps? When I try installing a stock rom zip file in my recovery from my sd card it aborts.
brickdummy said:
I'm sorry, I have no idea what I am doing. Can you show me the steps? When I try installing a stock rom zip file in my recovery from my sd card it aborts.
Click to expand...
Click to collapse
I'm guessing that you're trying to flash a PD98IMG.zip or a RUU. You need an actual stock rooted ROM, probably from here on the forum. Or just flash Android Revolution HD, an optimized rooted stock ROM, also from here on the forum in the development section. For more specific steps read the Ace Think Tank linked in my signature.
bananagranola said:
I'm guessing that you're trying to flash a PD98IMG.zip or a RUU. You need an actual stock rooted ROM, probably from here on the forum. Or just flash Android Revolution HD, an optimized rooted stock ROM, also from here on the forum in the development section. For more specific steps read the Ace Think Tank linked in my signature.
Click to expand...
Click to collapse
Ok, one more thing. I have S-ON. does that matter?
----
It did not, lol anyway it worked. Thank you everyone for you help. I really appreciate it.
-----
For those wondering I found the stock rooted rom here http://http://forum.xda-developers.com/showthread.php?t=996368
http://forum.xda-developers.com/showthread.php?p=26617631
Instructions to flash the rom
http://http://forum.xda-developers.com/showthread.php?t=2168500
brickdummy said:
Ok, one more thing. I have S-ON. does that matter?
Click to expand...
Click to collapse
Yes. You need to read the part in my signature about being stuck in the splash screen.
bananagranola said:
Yes. You need to read the part in my signature about being stuck in the splash screen.
Click to expand...
Click to collapse
ok, got it. Thank you again
Dear friends,
I have this problem: I got a brand new TCL S720 and the Google Play did not work, being a known rom issue. So, before doing anything, I've managed to make a backup of it's original rom with MTK Droid tools whichI supose it did it well. Then I've tried to install a CWM recovery to try a custom rom for it. The CWM recovery seemed to install succesfully but I didn't manage to install the new rom. If I remember well, it stucked on boot logo. Then tried to revert at it's original stock recovery, managed to have the phone back as it was in initial state, but doing more tries, It remained stucked on boot logo. The problem is that my computer doesn't recognise it anymore, when I connect it to USB it tries to install MTP usb driver but even before the driver was installed well, now it refuse to install, like the driver is not good or the proper driver doesn't exist. So the only thing I can do is to boot on stock recovery but even I tried to copy the original rom update.zip on external SD and to flash the phone using install update from sd card in recovery mode, It doesn't find the external sd card. So I'm stuck here, the computer doesn't detect the phone to try flashing it with SP flash tool or MTK Droid tool, and I also can't flash it from sd card. Have you any idea how to make it work again?
Thanks in advance.
hi guys,
i my shield is stuck on the nvidia logo when booting normally, if it brings up the bootloader, it shows unlocked but hitting continue caused it to freeze on the screen, recovery freezes on nvidia logo and fastboot protocol just brings it back to this screen. i orginally installed twrp and it confirmed successful flash of new os .... on reboot it bricked to its now state, i cant get into twrp or get my pc to see it to install a new copy
anyone got any ideas
thanks
@Fairmax don't click continue, it freezes because there is nothing to continue to, as long as you can enter bootloader your device isn't fully bricked. So, to fix your problem you will have to download official ROM from nvidia's site (https://developer.nvidia.com/shield-open-source find your model and click recovery images).
When you download latest ROM unzip it and follow the textual guide, but, there will be one file missing (i can't remember which one, user data maybe or something like that), don't worry and just continue with the next step. After you flash just reboot to system by holding power button. Good luck !
i cant seem to get it to be recognised by windows all i get is this-- Windows has stopped this device because it has reported problems. (Code 43) A request for the USB device descriptor failed.--
trying to install nvidia usb driver via have disk bring up an error that the file is not usable with x64 system
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Fairmax said:
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Click to expand...
Click to collapse
Which command did you type in?
fpozar said:
Which command did you type in?
Click to expand...
Click to collapse
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Fairmax said:
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Click to expand...
Click to collapse
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
fpozar said:
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
Click to expand...
Click to collapse
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Fairmax said:
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Click to expand...
Click to collapse
You can also try flashing twrp and then lineageos or something from twrp.
fpozar said:
You can also try flashing twrp and then lineageos or something from twrp.
Click to expand...
Click to collapse
good news after a few hours of trying (usb dropped connection a few times then battery died) it finally works again .....been over 2 years since iv had this shield running after nvidia did the recall , now goto put a different rom on there so it dosnt update and kill itself
Hello I had a similar issue with my k1 tablet and ended up flashing factory images via adb fastboot and all flashed fine. Now my tablet is stuck on the boot screen with the green and white nvidia logo. How long does it take to boot please?
I have same issue too. I can load TWRP and flash the other partitions but TWRP shows un-mountable partitions and even a full stock ROM flash will not allow it to boot. I have a similar issue with a recall tablet. what did you do to fix it?
I'm trying to install lineage OS 16 on my Sony Xperia Tablet Z LTE, in order for it to be up to date and able to use modern apps. I'm really not that tech savvy, but this far I've managed to unlock the bootloader, root the device and I believe I've managed to flash the recovery drive with the TWRP file meant for my device. I tried to flash the recovery from my windows PC, but every time I received "Failed "remote command not allowed" despite the device being unlocked at the bootloader and it is an A partition. So instead I went ahead and rooted the device and afterward flashed the tablet from the official TWRP app. At the end of the flash, I got "Flash completed successfully" which leads me to believe that I've flashed it correctly.
Now the issue is that no matter what I try, I can't boot into recovery mode. Every time I try, it just boots up regularly. I've tried via ADB terminal, through the TWRP app, and physically with the power button+volume down button, but everytime I get the same result.
This has me wondering, could I just download the Lineage image to my device and flash it directly to the boot partition or would this not work? Also what could be the reason I can't boot into recovery mode?
Sorry if this is not the forum for this topic, i just can't imagine who else would be able to advise me on this
luka0954 said:
I'm trying to install lineage OS 16 on my Sony Xperia Tablet Z LTE, in order for it to be up to date and able to use modern apps. I'm really not that tech savvy, but this far I've managed to unlock the bootloader, root the device and I believe I've managed to flash the recovery drive with the TWRP file meant for my device. I tried to flash the recovery from my windows PC, but every time I received "Failed "remote command not allowed" despite the device being unlocked at the bootloader and it is an A partition. So instead I went ahead and rooted the device and afterward flashed the tablet from the official TWRP app. At the end of the flash, I got "Flash completed successfully" which leads me to believe that I've flashed it correctly.
Now the issue is that no matter what I try, I can't boot into recovery mode. Every time I try, it just boots up regularly. I've tried via ADB terminal, through the TWRP app, and physically with the power button+volume down button, but everytime I get the same result.
This has me wondering, could I just download the Lineage image to my device and flash it directly to the boot partition or would this not work? Also what could be the reason I can't boot into recovery mode?
Sorry if this is not the forum for this topic, i just can't imagine who else would be able to advise me on this
Click to expand...
Click to collapse
Just to be sure, do you have USB debugging enabled?
Droidriven said:
Just to be sure, do you have USB debugging enabled?
Click to expand...
Click to collapse
I do, and of course I went and enabled it again after I bootloaded the device
Droidriven said:
Just to be sure, do you have USB debugging enabled?
Click to expand...
Click to collapse
You said you tried volume down+power, on most devices, that is the combination to boot into bootloader mode, fastboot mode or download mode, depending on the device. Volume up+power is generally the combination to boot into recovery mode. This doesn't seem to be your issue though. Are you sure you flashed TWRP to the correct partition? If your device is an A/B partitioned device, you may have flashed to one of these partitions when you needed to flash to the other partition.
Try flashing a copy of your stock recovery then see if that repairs the recovery partition and allows stock recovery to boot. If it works correctly after flashing stock recovery, you may not be flashing TWRP correctly or the actual flash might be being blocked by something that you're overlooking. Are you certain that your bootloader is unlocked?