I would gladly appreciate and donate to anyone who can step-by-step guide Me to reviving My Shield Tablet 32GB LTE US! I had TWRP but somehow cannot make it back into it, all i get is the bootloop or the Fastboot screen. My laptop runs on Win8 and most of the time can't or won't recognize the tablet and when it does, it can never seem to find the files I'm trying to push to it. Someone told Me it can never be truly or permanently bricked and for about 6 months I gave up but I miss having a bigger screen, games, all the storage, etc. I need My tablet back and NOBODY is giving Me a clear way to do it as I AM pretty much a noob at all this. This is the absolute most stressful/tedious root I had ever had to do and shortly after getting TWRP and achieving root access through KingRoot, I accidentally wiped My partition and then locked Myself out of recovery... If ANYONE can help, I would ULTIMATELY appreciate it. Thank You.
Mmmmmmmh your tablet have unlocked bootloader?
If yes probably you can do something with ADB....
if not...i think you can trash your tablet ;_; at least if you don't solder an eprom flasher, but it's out of my possibility and need sort of reverse engeneering
If you can actually get to the fastboot menu, you should be good to go. You'll have to unlock your bootloader, but once you do that you can flash the recovery partition or flash an entire recovery image. Do respond if you're looking to do so.
I unlocking the bootloader was the very first thing I did. Yes, i need to know exactly where to get the image, where to save it, and how to push it thru adb please.
I do have accidental insurance... But i don't want to do that.
If you go to the link in my signature, you will find guides for flashing the recovery partition (among other things) as well as download links for the recovery images.
If you lack installations for adb/fastboot, there's a tool on XDA called Minimal ADB and Fastboot. I'd recommend using it.
can you help me? I have same issue.
My tablet only shows up as APX in device manager.
Cant boot up to NVIDIA logo, Cant boot up to fastboot nothing.
It was unlocked before now.
No bootloader, no luck. Only NVIDIA can help you now.
http://forum.xda-developers.com/shield-tablet/help/help-help-bricked-shield-tablet-original-t3313428
I believe I can get it working again somehow by puting the recovery on the SD card seeing how mine came with a usb adapter
Reflash twrp via fastboot
Related
Hello Everyone,
I am a Noob, Yes. Please help. I was trying to install TWRP onto my TF300T. I installed it Via ADB. Had it installed with my stock ROM. I tried to do a backup so I could flash CM10. It said it wasn't mounted. I tried again and then it reboot and now goes straight to TWRP. I can get my device on ADB via the cmd screen but it says that the device is attached in recovery and my serial number is now 01233456789ABCD. Have I completely bricked my tablet? Is there anything I can do? I have been searching the forums for literally hours and am at wits end. Any suggestions would be appreciated. Sorry if this has been gone over time and time again but I can't figure it out. Please help. Thanks
Marc
To add,
When I try to do anything via fastboot it just hangs waiting for device. I can't get it to go to the fastboot page on my tablet, it just goes straight to the TWRP page.
Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...
splashg said:
Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...
Click to expand...
Click to collapse
Yes, that would be correct. So I managed to reset the device and cold boot back to a working device. Now i'm still wanting to flash a custom recovery and change ROMS to cyanogenmod (had it on my S1 and loved it) but am a bit nervous. How do I reset my partition and clear the old TWRP and flash a working version of CWR via fastboot or a version of TWRP that will work with my OTA rom. I thought I had done quite a bit of research before hand but am feeling a bit overwhelmed now. I don't want to go through another twelve hours of trying every trick I can find on the internet to unbrick my device.
Thanks
Just a few other things to add. So now when i have my device connected to my computer in normal function i can recognize it when I enter adb devices on my cmd prompt. Then I do the fastboot reboot bootloader which it then sends it into the fastboot screen. type in adb devices and it doesn't recognize the device anymore. I try the commands to install the cwm recovery.img and my cmd screen goes through the normal steps saying it's completed it. Then i try to reboot the device through fastboot and it freezes on the bootload screen with the green box no longer flashing on the rck box. Hold power button for six seconds to reboot and i have a working device again. So now i'm lost. How do I reset everything so I can start over, repartition so I can flash a custom recovery and carry on. any help is appreciated.
I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.
splashg said:
I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.
Click to expand...
Click to collapse
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.
lomoski said:
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.
Click to expand...
Click to collapse
I finally gave up, sent mine in today, it will cost but what the hell, i want my tablet in working order. I've tried the remedies myself, to no avail.
So off to ASUS.
Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.
steveb05 said:
Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.
Click to expand...
Click to collapse
I won't know how much it will cost until the unit is in their hands. I initiated my RMA online as well, they told me i will be contacted by phone after they examine it, I'm prepared to invest another 100 bucks as i got the unit for $299. I'll be hesitant to go much higher. I will post a number when i hear from them, if they haven't replied back to you.
I've got the same problem on my TF300T.
I'm going to try to get it working.
Not entirely sure what caused it, since I had used encryption in cm10.1 prior to flashing Asus stock 4.2.1.
BTW, I've been able to get back to fastboot by running adb reboot bootloader when TWRP is loaded.
Update: Seems to be that new 10.6.x.x bootloader... gotta love Asus :-/
--- Update II----
I can't flash anything in fastboot anymore :-/
Hi, I have a friend who has just smashed their Desire S whilst out on Sat.
Unfortunately, as the title says, they have no screen (touch doesnt appear to work either but no real way of telling!), not root, no USB debug and I have already checked and they didnt have their contacts set to sync with their google account but with the phone! :-/
Can anyone give any suggestions other than a screen replacement? They have already got an S3 on the way today so just want to be able to restore their contacts.
Cheers and thanks in advance!
I think this is definitely possible, but it may get very complicated.
Do you have adb in recovery (you'll have to boot into fastboot and blindly navigate to the recovery option)? Is the bootloader unlocked?
Aquous said:
I think this is definitely possible, but it may get very complicated.
Do you have adb in recovery (you'll have to boot into fastboot and blindly navigate to the recovery option)? Is the bootloader unlocked?
Click to expand...
Click to collapse
Thanks for replying Aquous!
I have just been given the phone today from a friend to try and help them out so im not sure on either? Do you have a desire s and would be able to tell me the button sequence to get into recovery to find out? As for the bootloader being unlocked, i very much doubt it as the phone was running a stock orange rom.
Any ideas?
Cheers,
It is unlikely indeed that you will be able to recover the data as the phone is. If you're in the UK (possible as the phone is on Orange) and fancy posting it then I can stick my LCD and touch panel on it for you so I can recover the data.
Also if u r in the uk, try a phone repair shop that has jtag, they should be able to pull any data off the phone.
radeonorama said:
Thanks for replying Aquous!
I have just been given the phone today from a friend to try and help them out so im not sure on either? Do you have a desire s and would be able to tell me the button sequence to get into recovery to find out? As for the bootloader being unlocked, i very much doubt it as the phone was running a stock orange rom.
Any ideas?
Cheers,
Click to expand...
Click to collapse
Then you probably don't have adb in recovery either.
We can try the easy way first: from the Google Play website (on your computer), download TalkBack to your phone and see if you can launch it blind. From there on, your phone will read to you what's on the screen
If you can't manage to do that, I have another option in mind but it's complicated and you may not be able to recover your contacts:
Unlock the bootloader via htcdev. This will wipe your data, but if you don't allow the rom to boot after the unlocking, this is OK.
Immediately after issuing the fastboot oem unlock command, HOLD DOWN THAT VOLUME - BUTTON. If the ROM is allowed to load, your data will be significantly harder, if not impossible, to recover.
If you held Vol - correctly after the unlock, you'll be in fastboot (if the phone vibrated, quickly pull the battery before the rom starts writing to the data partition).
From fastboot, boot a custom recovery ('fastboot boot recovery.img')
In this custom recovery, you have adb. Pull the data partition and run file recovery software to try to reconstruct the data that was on it but was wiped by the unlock process.
Purposefully not giving any clearer instructions than this, because if you don't know what you're doing the chances are very high that you're going to do it wrong and won't be able to recover the data.
Aquous said:
Then you probably don't have adb in recovery either.
We can try the easy way first: from the Google Play website (on your computer), download TalkBack to your phone and see if you can launch it blind. From there on, your phone will read to you what's on the screen
If you can't manage to do that, I have another option in mind but it's complicated and you may not be able to recover your contacts:
Unlock the bootloader via htcdev. This will wipe your data, but if you don't allow the rom to boot after the unlocking, this is OK.
Immediately after issuing the fastboot oem unlock command, HOLD DOWN THAT VOLUME - BUTTON. If the ROM is allowed to load, your data will be significantly harder, if not impossible, to recover.
If you held Vol - correctly after the unlock, you'll be in fastboot (if the phone vibrated, quickly pull the battery before the rom starts writing to the data partition).
From fastboot, boot a custom recovery ('fastboot boot recovery.img')
In this custom recovery, you have adb. Pull the data partition and run file recovery software to try to reconstruct the data that was on it but was wiped by the unlock process.
Purposefully not giving any clearer instructions than this, because if you don't know what you're doing the chances are very high that you're going to do it wrong and won't be able to recover the data.
Click to expand...
Click to collapse
Bloody legend!
Using the above coupled with Droid explorer i managed to pull everything she needed! Thanks so much for taking the time to help me out!
All the best!
radeonorama said:
Bloody legend!
Using the above coupled with Droid explorer i managed to pull everything she needed! Thanks so much for taking the time to help me out!
All the best!
Click to expand...
Click to collapse
Holy ****, you actually did this? And it WORKED? You, sir, have some serious balls! Gratz!
By the way, this has HUGE privacy implications
Aquous said:
Holy ****, you actually did this? And it WORKED? You, sir, have some serious balls! Gratz!
By the way, this has HUGE privacy implications
Click to expand...
Click to collapse
Yup, everything i needed off it worked.
I left it for a while as a last resort because of the risk of total data loss and bought a replacement screen which was DOA!
So you plan came into play and it really worked. It wasnt so hard as the steps you gave just helped me get the order right in my head rather than trying something and mucking it up even more!
Thanks again good sir! She was very pleased!
Basically I was using TWRP to wipe my TF700T and I wiped the OS. Luckily I made a recovery on my SD, but the problem is that I can't get it to boot back into TWRP in order to run it. All the Power + Volume Down does is just cause the device to rumble. Powering on the device just lets it sit in the bootscreen. If I can get into the bootloader I can basically fix the machine. Problem I have remaining is that I can't seem to get into the bootloader.
The device calls itself APX when plugged into my computer now, if that means anything. I'm gonna try to drain the battery by leaving it on over night without the flash card. Maybe that'll do something.
Any suggestions on how to unbrick this thing? Or did I just succeed in turning a very expensive tablet into a very expensive paperweight?
JunoZXV said:
Basically I was using TWRP to wipe my TF700T and I wiped the OS. Luckily I made a recovery on my SD, but the problem is that I can't get it to boot back into TWRP in order to run it. All the Power + Volume Down does is just cause the device to rumble. Powering on the device just lets it sit in the bootscreen. If I can get into the bootloader I can basically fix the machine. Problem I have remaining is that I can't seem to get into the bootloader.
The device calls itself APX when plugged into my computer now, if that means anything. I'm gonna try to drain the battery by leaving it on over night without the flash card. Maybe that'll do something.
Any suggestions on how to unbrick this thing? Or did I just succeed in turning a very expensive tablet into a very expensive paperweight?
Click to expand...
Click to collapse
Im having exactly the same problem, did you find a solution to this?
So far no results yet. I tried hitting the reset button on the side but all that did was lead me back to the boot screen. I read something about undoing the the hard boot using a series of override programs. But the problem is the documentation is so cluttered that I can't fathom the instructions (I'll try it again just in case.)
Bump update: So I called Asus and it turns out it's gonna cost 288$ to get the thing fixed by them. So I'm not doing that. I'm looking into other ways of recovery. I've got other multiple options I'm exploring at the moment. Like looking for a recycling program or a way to use the technology in a new way.
UPDATE X2
So I talked to a friend and the very fact that it sits at APX was a tipoff. Basically it means the recovery is shot but the Bootloader is OK. Meaning that the device isn't as bricked as I thought. What needs to be done is to download the android ADT bundle (google it) and from there get into the platform tools under command prompt, type "adb" then "adb devices" and finally "adb reboot recovery"
if it works the recovery should reflash and then using the backup restore the OS.
Granted I'm having trouble getting my comptuer to say "APX has been connected" due to a faulty data cable but I should be home free after this
JunoZXV said:
UPDATE X2
So I talked to a friend and the very fact that it sits at APX was a tipoff. Basically it means the recovery is shot but the Bootloader is OK. Meaning that the device isn't as bricked as I thought. What needs to be done is to download the android ADT bundle (google it) and from there get into the platform tools under command prompt, type "adb" then "adb devices" and finally "adb reboot recovery"
if it works the recovery should reflash and then using the backup restore the OS.
Granted I'm having trouble getting my comptuer to say "APX has been connected" due to a faulty data cable but I should be home free after this
Click to expand...
Click to collapse
Unfortunately if you can only get to APX mode and you don't have nvflash specific blobs for your device you are hard bricked...
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
JunoZXV said:
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
Click to expand...
Click to collapse
Sorry it really doesn't look good, Maybe i can corrected but the device will fallback to APX mode if the bootloader is corrupted, without a bootloader you cant install/fix a recovery and without NvFlash blobs you cant fix the bootloader. Your two options are buy a new motherboard and replace it yourself or send it in for repair with Asus
JunoZXV said:
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
Click to expand...
Click to collapse
As JTR says I'm pretty sure you can't fix this without replacing the hardware now. I don't think your friend really understands what APX mode is. YOu can't access the bootloader nor recovery. Without NVflash backup blobs you can't recover anything, there is no way to get your TWRP backups back on to the device and even if you could you have no working bootloader......
hi . I have a asus tf700 model with the silver metallic back. for some reason the tablet is locked on the asus boot screen with the "this device unlocked" lettering on the top left corner.
i'm sorry if this is a double post but ive been searching for weeks and been hit with brick walls.
if there are any links specific to revive the tablet post them please...
all I know is that my pc does see it as a apx device in apx mode but I have no access to the recovery bootloader or any other menu. I got adb and fastboot installed and I need to know how to upload a new twrp or bootloader and rom.
I'm not a noob as far as bricked devices I did have a htc m7 bricked and samsung galaxy note3 that are working quite awesome right now.
Thanks for any help...
I am sorry to tell you this, but if you cannot get into either fastboot or recovery your tablet is a brick.
Unless you have your NVflash files squared away, but I think you would have mentioned if you did.... If you hadn't heard about those, never mind. They are device specific and have to be generated when the device still works....
I've heard a minor miracle where someone just let the battery die, leave it alone for a day or so and then trickle charge it through USB and then was able to boot into fastboot, but I wouldn't count on it....
Ok. So even in abx mode there is not much to do?
Oh well i guess i have to get a new logic board then..
thanks for the reply. If there is anything that can revive it im open to suggestions
APX mode is where you can use Nvflash to restore the tablet. Sorry...
berndblb said:
APX mode is where you can use Nvflash to restore the tablet. Sorry...
Click to expand...
Click to collapse
so i spoke to the prior owner and here is what he did.... maybe this could save me but probably not....
We unlocked and tried to root through the official tool. My wife then tried to flash a rom using cyanogen but must have used the wrong one and it bricked.
It was definitely clockwork mod and we did wipe more than once. Wish we knew which step we messed up!
can this be undone?
:fingers-crossed:
Not without Nvflash blobs - sorry.
Hope you got it for free. You can get used mainboard on eBay for $50 or so. For that money it's a nice tablet once you custom rom'd it.....
Would a twrp blob work?
If you could boot into the bootloader it might. You could try lots of stuff it could boot into it. But you can't....
Ok, I've been reading around the forum for about a week, trying to solve a problem with an original moto g (falcon). Basically my cousin got the moto g a few years back, and I, in my ignorance, tried to root the device for him. What I can remember was oem unlocking the bootloader with Motorola's unlock code through their website and adb. then my cousin freaked about the warranty warning on the boot animation, and decided against it. So cut to now, I'm a little more experienced, the phone's years old now, and he'd like to refresh it with a new rom, which I suggested, trying to help him. So forgetting what I'd originally done those years ago, I started the process of rooting the phone, installing a custom recovery, to hopefully put a lighter rom on it for him.
OK so it's a UK Retail on tesco mobile, moto g xt1032 running Android 5.1.
in bootloader menu it says "Device Locked status 2", dunno what this is in relation to.
first I checked the bootloader was still unlocked, and adb said it was. so I tried to use CF-autoroot to finish the job, but there was issues. it restarted the phone into fastboot mode, but when the script started, pc end did nothing, on the phone it said, "flashing unlock" and just sat there for 10-15mins doing nothing (i left it the time, just incase it was doing it).
So i read a little more, and found because i'd already unlocked the bootloader, I could just flash a custom recovery and root from adb? so I downloaded the latest twrp and tried. I was unable to do so. it said the partition wasn't the right size? should have documented it, but really didn't expect to run into any problems.
So I restarted and tried to do my usual fallback, and flash the factory image and start again, But couldn't find a source for the specific img, and tried to keep fighting on.
So I noticed that the phone wouldn't respond to adb or fastboot once in fastboot mode, when in android with usb debugging, no problems, in fastboot, didn't show up as adb devices?
I tried booting into the recovery from the bootloader menu, and got a no command. So there isn't a recovery, and I can't flash a new one? if i could find the stock recovery, I would try that.
so apart from deleting all his apps and settings, I hadn't solved the problem at all, and had to leave the job there as I couldn't find a solution.
I know this isn't the most detailed, but I've done this with quiet a few phones now, and felt I was pretty competent. I see everyday as an excuse to learn more, and like to think I have humility. So, I'm assuming I did something those years ago to damage the recovery? I'm running out of ideas, and was hoping someone could point me in the right direction?
I've lurked on xda for years, and learned so much about this kind of thing through my past experiences, but I'm stumped this time, and feel obliged to resolve the problem, as it was me who caused it.
TL DR
Can't flash recovery, no command when I try to open recovery, trying to either factory image back, or root/custom recovery it.
any insight would be much appreciated.
Hi. I just rooted and installed CM13 on an old XT1034 about two days ago. I am also sort of a ROM noob, I have ROMed a few devices, but usually but following strict step by step guides I have found here on XDA. Over the years I have some minor understanding of the process now.
I also got the "No command screen" when trying to get into TWRP recovery. The issue seems to be that if you reboot via ADB and the ROM launches it will automatically rewrite the recovery to the stock one, and when you try to go to recovery from fastboot, it gives you the "no command" error. Apparently you can get to the stock recovery from there by a hardware key combo, something like holding up vol for 10 sec then a quick press of power (I can't remeber the exact key sequence or what forum I read it in). If it does this you have to reflash TWRP again. This issue is mentioned here (http://wiki.cyanogenmod.org/w/Install_CM_for_falcon) in step 8 about installing recovery. What I ended up doing was after the flash of TWRP via ADB, I manually powered down, then manually bood into fastboot by holding volume down and power, and selecting recovery. This was a bit fiddly and I had to attempt it a few times but eventually it worked and TWRP installed.
The issue with the phone not being recognized may be due to incorrect drivers. I had no issue with this because I installed the official driver package from Motorola. It is available in their website in the developer section. I don't have the URL right now.
Hopefully this helps, for me CM13 Official has been an a stable fresh start for this old device.