Related
Hello all. I'm a brand-noob (my phrase, thank you) here.
I have received a Verizon HTC Eris phone that boots to the red triangle with exclamation point (three droids on skateboards prior to the triangle screen). I have no information on what was done on this phone prior to my receiving it. I have read here that the three droids means that it has been rooted, and that the red triangle means a stock recovery is on it.
I can only "Up Volume + Power" to get this - "E:Can't open /cache/recovery/command". Other than that, I can't seem to get to anything else on the phone.
Now, upon connecting via usb to my computer (Windows 7), I can get Windows to recognize the "Android Phone", but not specifically an HTC Eris. I do not have HTC Sync installed. I have used ADB to root another phone (MyTouch), but this phone does not show up when I check for devices via "adb devices".
I am hoping someone can offer some simple steps that I can do to work towards fixing the phone. Thanks everyone for your time. !
This may help you:
http://forum.xda-developers.com/showthread.php?t=992916
Good luck.
Thanks for the reply phone_cell. I had already read/seen that post.
I cannot see any boot information at all, it shows the skateboarders, then the red triangle. The phone shows up on my computer, but only as an "android storage device". I'm not sure how I can check anything via my computer. I have installed PDAnet prior, and read that it should have installed the phone drivers. ? I installed HTCSync on a different computer and it doesn't see the phone.
If there is no way to fix this phone, then I understand. I would like to think that there are ways (standard methods ?) to check and/or re-install a phone (any phone) back from something like this. ? ...Thanks again for your time and expertise!
I was happy to try to help you. I recommend you send a PM to bftb0. If your Eris can be brought back to life, bftb0 will know what to do.
Bummer. bftb0 does not receive private messages, or at least not from me. Maybe someone could relay the forum post.
I am still digging and digging to try and figure something out. If I could get my computer to communicate properly with the phone, I'm sure I could re-install/fix the boot problem.
Anyone have ideas on how to install a usb device that's stuck in recovery?
As always, thanks thanks thanks. And thanks.
I made a post asking bftb0 to lend you a hand.
http://forum.xda-developers.com/showpost.php?p=15386610&postcount=33
Are you able to get it into fastboot mode? To do so, the phone needs to be completely off first...pulling the battery if needed. From there, first hold down the green send/call button then press and hold the red power/end button at the same time. Holding both should bring you to the fastboot screen which has three small skateboard andy's at the bottom and the word FASTBOOT highlighted in red. If you get there, post what the top two green lines say. Post #4 in the thread phone_cell gave shows an example of what you'll see. I would also try and follow bftb0's directions in post #5 about using the "Official" RUU utility to install usb drivers but make sure to stop before actually flashing anything to the phone. After that, download the fastboot tool and then with the phone connected through usb, see if the command "fastboot devices" lists your device ID.
Getting that far is promising and you can proceed with bftb0's directions in that thread to flash with HBOOT, load a recovery, hopefully eventually get a custom ROM flashed.
Hey MongooseHelix (great nick). Thanks for your reply.
No, the phone does not boot into fastboot, or anything else. There's plenty of resources here for all the different methods for booting and such. I've read hundreds of threads and pages. I've tried them all (and to success on other phones). It only gives me the recovery-stuck-ness.
The more I think about it, the more I think it has something to do with me not having this certain phone installed on my computer prior to receiving it. ? What would other people do to remedy something like that..? Find a working model to get the drivers working? Hmmm. Thanks and thanks again folks.
If you haven't already, how about installing the android-sdk(try the exe if on windows):
http://developer.android.com/sdk/index.html
Then run the SDK Manager.exe from the SDK directory. I'd download the latest SDK tools, SDK platform-tools, and the USB driver for Windows. Make sure to add the tools and platform-tools directories to your path...instructions at the end of Step 5:
http://developer.android.com/sdk/installing.html#sdkContents
With the phone on and connected through usb, see if running "adb devices" from the command prompt recognizes the Eris.
Yes, I had the android-sdk installed prior to receiving this phone. I did run it and update everything within it (per everything I researched online). But, the phone still doesn't show up via "adb devices". I feel like because the phone is stuck in recovery, it's not letting the computer do anything hardware-wise with it. ? Not sure.
Not sure what else to suggest. Without access to recovery, fastboot, or hboot along with not being able to connect through a comp, it unfortunately sounds like it might be hard-bricked. I'm certainly no expert at reviving an Eris so someone may know a way to to fix things...maybe bftb0 will come work his magic. Good luck and if I find or think of anything else I'll let you know.
The red triangle screen is indeed a splash screen for the stock recovery.
The next question is whether you are able to proceed beyond the "splash screen" and attempt to perform a "factory reset" procedure using the stock recovery menus.
There are two ways you get past the stock recovery splash screen, and it depends on which version of the stock recovery is installed on your phone have.
(1) press & hold Vol-Up+End simultaneously (with the "red triangle" splash screen showing)
or
(2) press the Home(soft-key)+End simultaneously (with the "red triangle" splash screen showing)
Do either of those cause the <2e> recovery menu to appear on the screen? If so, perform a "factory reset" using that menu, and THEN see if you can get alternate startup modes to occur (after powering off the phone before each trial):
End (only) => Does anything boot now?
VolDown+End => HBOOT
Send+End => FASTBOOT
VolUp+End => Recovery boot (red triangle screen again) **only works if HBOOT > 1.49.xxxx
Please do not say "I tried everything" in your reply. It is extremely non-specific, and conveys no information about what you actually attempted.
bftb0
Many thanks for the reply. !
With the recovery splash screen showing, upon holding "Volume Up + End (power)" I get = E:Can't open /cache/recovery/command Now, I am able to clear that message by pressing "Volume Up + End" again, however it just goes back to the recovery splash screen.
I held down Home (on the glass) + End (power) and nothing happened.
?? Any suggestions ?
Also... my reference to "tried them all" in my earlier post meant that I have tried just about every combination of simultaneous key pressing upon powering up (booting from no power) the phone. I am also familiar with the recovery menus on other phones - I have not seen it show up on this one (per my most recent post as well).
cjslugbug said:
I get = E:Can't open /cache/recovery/command
Click to expand...
Click to collapse
That message is quite normal. However, what usually happens is that the (stock) recovery <2e> menus appear immediately after that message.
I guess this suggests that there is something wrong with the phone (hardware) or the recovery.
I'll give it some thought (check this thread every so often), but I don't see an immediate way out of your situation.
bftb0
Well, I certainly appreciate the replies. Thanks!
Does
VolDown+Send+End
do anything interesting - either from a phone off condition, or when the "can't open /cache/recovery/command" message is on the screen?
Was there a (properly formatted) SD card in the phone when you performed all the prior button-pressing experiments?
Booted with "Volume Down + Send + End" = same, straight to recovery splash screen.
I then "Volume Up + End" to get "e:can't open /cache...." and tried "Volume Down + Send + End" = no changes.
I have an sd card in it that I used to root a MyTouchSlide recently. It has ClockworkMod recovery on it (update.zip). I have done every procedure I've mentioned in this thread with and without the sd card in the phone.
I just reread the whole thread.
I understand that you tried all the standard button-press-startup methods, and the only thing you can get to work (partially) is the first part of the standard recovery boot. What you didn't say explicitly is, what exactly happens when the standard button-press operations fail:
- nothing at all (screen stays black, not a single LED blips, etc)? or,
- every start sequence results in the recovery splash screen? or,
- the three skating droids appear but the screen freezes that way? or,
- other?
Here is what you are up against:
The standard recovery does not start up an "adbd" daemon, so worrying about drivers is not likely to get you anywhere: under normal circumstances, "adb" simply doesn't work with a standard recovery.
There are two exceptions to this:
(1) The (leaked) HTC "Root ROM" does start an adbd daemon (but "adb shell" won't work)
(2) The Leak-V2 recovery had a race condition that allowed less than 20% of the folks who tried it to get an adbd daemon to persist. (Search for "tereg" root). It's a huge long shot.
Whether either of these apply to you is indeterminate, as we know neither the bootloader version that is on your phone, nor the version ofthe (damaged?) recovery on the phone.
One more question, and then some straws to grasp at:
- when you plug the phone into the charger, do you see the amber/green LED light up?
- repeat every one of the "standard-button-press" sequences, but make sure that before each start sequence, you pull the battery, press all buttons, wait 10 secs, and then reinsert the battery. Long shot, but what have you got to lose?
bftb0
- what exactly happens when the standard button-press operations fail:
The three skating droids appear (for a few seconds, as per a normal-type boot is beginning) but then the screen freezes to the recovery splash screen.
- when you plug the phone into the charger, do you see the amber/green LED light up?
Yes, I see the amber/green light. The light seems to operate as if it is charging normally.
I will try your 10 + second-battery-pull-button-combinations method here in a while.
Really appreciate the thoughts/help on the matter. !!!
I have a fairly generic Chinese tablet, a Neutab N7 (not a Nexus 7), but I have no idea how to enter the bootloader/fastboot mode.
Using adb, "adb reboot bootloader" or "adb reboot-bootloader" just makes it reboot normally.
From a shell, doing "su reboot bootloader" also reboots normally.
I tried Quick Boot from Google Play which has an option to reboot into the bootloader, but it also just ends up rebooting normally.
While powered off, I tried holding power and volume up, power and volume down, and power and both volume up and down, but they all just boot normally.
Doing "adb reboot recovery" does boot me into recovery mode, but the menu doesn't have a bootloader/fastboot option.
Does anyone have any idea how to enter the bootloader/fastboot mode for this tablet? Any help would be appreciated.
knismaps said:
I have a fairly generic Chinese tablet, a Neutab N7 (not a Nexus 7), but I have no idea how to enter the bootloader/fastboot mode.
Using adb, "adb reboot bootloader" or "adb reboot-bootloader" just makes it reboot normally.
From a shell, doing "su reboot bootloader" also reboots normally.
I tried Quick Boot from Google Play which has an option to reboot into the bootloader, but it also just ends up rebooting normally.
While powered off, I tried holding power and volume up, power and volume down, and power and both volume up and down, but they all just boot normally.
Doing "adb reboot recovery" does boot me into recovery mode, but the menu doesn't have a bootloader/fastboot option.
Does anyone have any idea how to enter the bootloader/fastboot mode for this tablet? Any help would be appreciated.
Click to expand...
Click to collapse
why do you want to enter the bootloader? and have they made any roms or cwm recovery for these types of generic android tablets?
[RESOLVED] finally, ROOT for Neutab N7 pro tablet.
knismaps said:
I have a fairly generic Chinese tablet, a Neutab N7 (not a Nexus 7), but I have no idea how to enter the bootloader/fastboot mode.
Using adb, "adb reboot bootloader" or "adb reboot-bootloader" just makes it reboot normally.
From a shell, doing "su reboot bootloader" also reboots normally.
I tried Quick Boot from Google Play which has an option to reboot into the bootloader, but it also just ends up rebooting normally.
While powered off, I tried holding power and volume up, power and volume down, and power and both volume up and down, but they all just boot normally.
Doing "adb reboot recovery" does boot me into recovery mode, but the menu doesn't have a bootloader/fastboot option.
Does anyone have any idea how to enter the bootloader/fastboot mode for this tablet? Any help would be appreciated.
Click to expand...
Click to collapse
Having been looking for this information myself i'm sharing real quick here what i've found. Scouring the net all over i've found NOTHING specific for these Chinese tablets but after finally getting on the scent of VROOT I downloaded and tried iROOT essentially a one-click rooter the .APK **DID NOT WORK** but the PC version **DID** can be found by googling iroot or vroot.
RE: bootloader, i've still found no way or any good info on entering the bootloader AFAIK this is locked and may not be possible without some good hard hacking on the firmware, I DO KNOW that if you try entering the "bootloader" with a reboot manager on the device u will find yourself at the "NeuTab" welcome screen and stuck. Fortunately at least in my experience, letting the tablet battery run down low you can boot back into it and root condition is still good.
Hope this helps somewhat I know its an old post but a lot of people have been looking for this info have yet to post on authors site confirming that the NeuTab also works with his software.
peace.
VE3UND
BTW I forgot to mention the site and the software (ALTHOUGH IT STATES OTHERWISE) is in Chinese. A leap of faith needed there I know but i confirm this method works. l8z
BTW^2 ALSO the android version was KitKat as received from the mfg, also have been told that Jellybean will install on the tablet after rooting and maybe is now included with device but don't quote me on that.
all in all a really nice tab for the price, especially now we have root biggest missing option: GPS but you can tether to another device with gps if you need to. Also no built in USB HOST MODE. //out
I've got the NeuTab N10 and can't get ADB to see it at all. How did you get ADB to work with your N7, were you able to find NeuTab ADB drivers somewhere?
So i recently came across this tablet in my stuff... something i picked up for the wife a few years back.
I also came across this website.... http://neutab.com/info-detail.php?InfoId=11
It has all the tools and programs that the company uses. includes all files for development of their entire line of tablets.
Thought this may be useful. just click on the link that says pheonixtools.zip and it will take you to a back end file server... This tablet is about as open sourced as it gets... so... this leads me to ask a question i have been struggling with for the last 2 years of being a member on this website...
can anyone... please... help me develop my first recovery and custom rom for this tablet? I just have never done it all the way... i have set up a couple things here and there... figured out how to strip the stock recovery and boot... but never got further than that.
Thanks for the help.
• Unzip phoenix tool.zip you just downloaded; (to open a .zip file, download WinRAR)
• In the folder of phoenix tool you just unzipped, depending on your system specs, select "drvinstaller_X64", "drvinstaller_x86" or "drvinstaller_IA64" to install tablet driver; Or you can run all three driver installer and at least one will work;
• Run "PhoenixSuit.exe", select "firmware" tab;
• Click on "Image" button, choose the firmware you just downloaded;
• Turn your tablet completely off (by press and hold power button for 20 seconds), press and hold "volume -" button, connect tablet to computer via usb cable, keep volume button held, press power button 10 times repeatedly；
• The phoenix tool should recognize the tablet. On pop-up dialog window, select if you want to format and wipe out everything on your tablet；
• The phoenix tool will start flash the firmware to the tablet. Wait till it is done；
• When upgrade is finished, disconnect your tablet from computer, press and hold power button for 10 seconds to quit upgrade mode. then press and hold power button for 2-4 seconds to turn tablet on；
Congratulations! Your tablet is now refreshed.
Ok so I have a NueTab Air 7 Android and I have talked toto their customer support which did neurologist absolutely no good. I have been trying to hard reset my tablet and do a factory reset by holding down the volume up and down keys and the power keys until it gives me the option of rebooting. However, there is no option for a factory reset. Only a Recovery mode, Fastboot mode, and Normal mode. I tired the Normal and Recovery an both sent me back to enter password that I can't rremember, which isthe why I'm resetting it lol. Finally I chose the Fastboot option and now it is stuck on that option and has been for almost an hour. It willwas not let me power off, try to hard reset, it is literally stuck. And it is a hundred percent charged. I do jot hav the optiontime to connectbe the tablet to acall Windows computer at this timetime, as the forums I have read say can possibly fix the issue. And what a surprise the customer service phone number for this specific tablet does not know how to fix it!!!!! Not surprised at all. If anyone at allthe has any ideas or knows what to do or howsomething to fix it please help meme. I'm very frustrated to say thethat least and in desperate need of help. Anything would be immensely appreciated. ~Melissa
How to identify the exact firmware of the N7 after this page (Oficial NEUTAB), I have 3 options but that IMEI series is nowhere in the table.
---------- Post added at 11:35 PM ---------- Previous post was at 11:35 PM ----------
this page http://neutab.com/info-detail.php?InfoId=11
n7s root
therealtaynak said:
So i recently came across this tablet in my stuff... something i picked up for the wife a few years back.
I also came across this website.... http://neutab.com/info-detail.php?InfoId=11
It has all the tools and programs that the company uses. includes all files for development of their entire line of tablets.
Thought this may be useful. just click on the link that says pheonixtools.zip and it will take you to a back end file server... This tablet is about as open sourced as it gets... so... this leads me to ask a question i have been struggling with for the last 2 years of being a member on this website...
can anyone... please... help me develop my first recovery and custom rom for this tablet? I just have never done it all the way... i have set up a couple things here and there... figured out how to strip the stock recovery and boot... but never got further than that.
Thanks for the help.
Click to expand...
Click to collapse
I would love to root this tablet purely because it's my daughter's and some of the games she likes has some real funky permissions That they want! A custom rom would be nice but I will be satisfied with being able to revoke some of the permissions that the apps want to have access to.
n7s software download issue
therealtaynak said:
• Unzip phoenix tool.zip you just downloaded; (to open a .zip file, download WinRAR)
• In the folder of phoenix tool you just unzipped, depending on your system specs, select "drvinstaller_X64", "drvinstaller_x86" or "drvinstaller_IA64" to install tablet driver; Or you can run all three driver installer and at least one will work;
• Run "PhoenixSuit.exe", select "firmware" tab;
• Click on "Image" button, choose the firmware you just downloaded;
• Turn your tablet completely off (by press and hold power button for 20 seconds), press and hold "volume -" button, connect tablet to computer via usb cable, keep volume button held, press power button 10 times repeatedly；
• The phoenix tool should recognize the tablet. On pop-up dialog window, select if you want to format and wipe out everything on your tablet；
• The phoenix tool will start flash the firmware to the tablet. Wait till it is done；
• When upgrade is finished, disconnect your tablet from computer, press and hold power button for 10 seconds to quit upgrade mode. then press and hold power button for 2-4 seconds to turn tablet on；
Congratulations! Your tablet is now refreshed.
Click to expand...
Click to collapse
I have yet to be able to download the zip or the firmware software. i got root with kingo pc version but that's pretty much it and I can't change the route manager because once I delete that then I don't have root anymore and can't add another one. Also I have yet to been able to get into or see download mode on this either. It just stays on the screen with the name on it and that's pretty much it. no bootloader unlock either
Help! I have a newer HDX 7 that is stuck trying to reboot. The device powers up to the gray kindle fire screen but sits there for a minute or so and then the screen flashes and it starts all over. The device does not recognize the power button. I've tried the hold the button for 40 seconds to reset but it just keeps going through this loop while holding the power button. When I connected it to my PC (Win7), it does not see the device. If I connect another Andriod device, it sees it imeadiately.
I'm a complete noob with this but I'm actually in IT, just not in this area. This is my sons device so I'm not sure exactly what he was doing at the time it started this but my guess would be playing MineCraft. Amazon's wonderful support says it just needs to be replaced but it's out of warranty. My son and I were just about to start an online coding course so I'd like to get this back up and running so we can start that. Any help would be appreciated. After searching the web, you guys seem to be the only ones able to root or fix any software/os issues with these devices.
Thanks,
Doug
Leav320 said:
Help! I have a newer HDX 7 that is stuck trying to reboot. The device powers up to the gray kindle fire screen but sits there for a minute or so and then the screen flashes and it starts all over. The device does not recognize the power button. I've tried the hold the button for 40 seconds to reset but it just keeps going through this loop while holding the power button. When I connected it to my PC (Win7), it does not see the device. If I connect another Andriod device, it sees it imeadiately.
I'm a complete noob with this but I'm actually in IT, just not in this area. This is my sons device so I'm not sure exactly what he was doing at the time it started this but my guess would be playing MineCraft. Amazon''s wonderful support says it just needs to be replaced but it's out of warranty. My son and I were just about to start an online coding course so I'd like to get this back up and running so we can start that. Any help would be appreciated. After searching the web, you guys seem to be the only ones able to root or fix any software/os issues with these devices.
Thanks,
Doug
Click to expand...
Click to collapse
Your options are limited given the device is largely invisible via tether (even then there would be little recourse as adb is probably disabled). Did you try a factory reset? Amazon's crippled recovery environment can be accessed via power + vol-up from a cold start. Release the power button after the gray Kindle logo appears. If the recovery menu comes up the only option is 'factory reset'. I realize you may not be able to access recovery given the non-responsive power button.
Any chance you son is old/savvy enough to trying rooting the device? The symptoms suggest either a failed automatic update (rare but it does happen) or botched attempt to root via the wrong method. Obviously a spontaneous hardware failure is also possible albeit unlikely.
Do you know what version of Fire OS was running just prior to the boot loop?
There is still a small chance adb may help even if the device is not recognized by Windows explorer. However, if as Davey said, it is disabled, things are limited.
Again, do you know what version is you were running?
Have you installed adb?
Have you tried recovery?
Sent from my KFTHWI using Tapatalk
Davey126 said:
Your options are limited given the device is largely invisible via tether (even then there would be little recourse as adb is probably disabled). Did you try a factory reset? Amazon's crippled recovery environment can be accessed via power + vol-up from a cold start. Release the power button after the gray Kindle logo appears. If the recovery menu comes up the only option is 'factory reset'. I realize you may not be able to access recovery given the non-responsive power button.
Any chance you son is old/savvy enough to trying rooting the device? The symptoms suggest either a failed automatic update (rare but it does happen) or botched attempt to root via the wrong method. Obviously a spontaneous hardware failure is also possible albeit unlikely.
Do you know what version of Fire OS was running just prior to the boot loop?
Click to expand...
Click to collapse
No, Unless it updated automatically, it was the same version that was on there when it was delivered around 4/14.
No, My son would not have tried rooting this on his own.
I was incorrect when I stated that the system wasn't recognizing the power button. When I try the hold the power button for 40 secs or the Power button + Vol up button to restart, the boot loop gets shorter.
lekofraggle said:
There is still a small chance adb may help even if the device is not recognized by Windows explorer. However, if as Davey said, it is disabled, things are limited.
Again, do you know what version is you were running?
Have you installed adb?
Have you tried recovery?
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
I have installed ADB on my PC but it doesn't see the device (although I'm not sure I'm using it correctly). What command should I be issuing to see if the device is connected. If I use "adb devices" I get the response in the attached screen shot.
If by recovery, you mean the recovery on the device, the power+volume up button doesn't work.
I appreciate all of the help!
Leav320 said:
No, Unless it updated automatically, it was the same version that was on there when it was delivered around 4/14.
No, My son would not have tried rooting this on his own.
I was incorrect when I stated that the system wasn't recognizing the power button. When I try the hold the power button for 40 secs or the Power button + Vol up button to restart, the boot loop gets shorter.
I have installed ADB on my PC but it doesn't see the device (although I'm not sure I'm using it correctly). What command should I be issuing to see if the device is connected. If I use "adb devices" I get the response in the attached screen shot.
If by recovery, you mean the recovery on the device, the power+volume up button doesn't work.
I appreciate all of the help!
Click to expand...
Click to collapse
Given the delivery date and age of device I STRONGLY recommend you reach out to Amazon for a replacement vs trying to resolve on your own. A new version of Fire OS is currently rolling out which MAY have triggered the behavior you are seeing. Bit of a bummer given your son's course plans but a worthwhile delay IMHO.
I agree with Davey.
Sent from my KFTHWI using Tapatalk
I got the fire hd6 so I could use my own apps on it, only to my discovery it uses the horrendous amazon store, and so I wanted to root it and done so using some root junky thing. It worked fully rooted for a day, but the next time I started it up, I got the infinite "Optimizing system storage and applications" loader.
This is where things get funky,
Factory reset using volume up+ power allows the hd 6 to work once (It boots to setup, but when I turn it off and back on, its stuck on optimizing system storage loader). Once I boot it up, the home screen is blank, and will freeze the tablet. However, if I push the power button off and back on the lock screen works fine, and from the lock screen I can open settings and turn on developer mode and enable adb debugging.
I did all the steps with android studio and got my drivers working for when the tablet is turned on (its on the list of adb devices), however when I volume up+power and try to boot with new firmware, my pc suddenly can't recognize it.
It's a shame because it's barely been used, and there are no guides online that could help me with this, the closest is root junky's guide, but his seems aimed towards later generations, and he doesn't have the issue of the pc not recognizing the adb device when its in the boot mode. I really don't want to trash it, but it's not like there are too many options.
So I have already unlocked and installed "[Guide/tutorial] Asus Transformer Prime/TF201 stock to Android 7.1 Nougat" using the thread and have been very happy.
I ordered a new battery and after putting in I noticed the touch screen wasn't well...ok I didn't get the ribbon cable in correctly no biggy.
I opened back up and indeed the cable wasn't in properly. I reinserted and put back together. I pressed the power button and the transformer would power cycle. I pressed the power and + button and got to the TEAMWIN screen and that has where it has remained.
No matter what i do with the power and volume I can't get to any other screen.
I did do this:
4 - PREVENT BRICK : NVFlash
This step is optional but highly highly highly recommended, your tab will never be bricked after it !!!.
I have read other threads about the getting stuck on the splash screen but they all say to plug into computer, connect to tablet and power cycle and Start your device in APX mode [Power On + Volume Up]. But i can't get to the selection page at boot-up.
Any ideas? I thought maybe I disconnected a cable when I opened back up but i have since opened back up looking for any ribbon that came out.
I am going to try this.....https://forum.xda-developers.com/showthread.php?t=1927818
used this to get in APX mode:
https://forum.xda-developers.com/showthread.php?t=2034866
and after trying https://forum.xda-developers.com/showthread.php?t=1927818 multiple times I could get the "nvflash.exe -r --go" to work so I tried "If you device does not reboot after you see the text, force a reboot (long press the Power button)" also no go. I did learn that every time I ran a blob and the Tab rebooted I would have to rerun "wheelie --blob blob.bin" to get back into nvflash mode.
I tried a new tactic and used this thread, https://forum.xda-developers.com/showthread.php?t=2538028, and even though it was for a TF700 I used substituted my files from, 4 - PREVENT BRICK at this thread, https://forum.xda-developers.com/tr...uide-tutorial-asus-transformer-prime-t3486237.
and happy days when I did this, At this point if it will not reboot or shut down do this
hold power button and volume down to boot into fastboot, it actually went into fastboot!! which was what I was not able to do before.
Hopefully some of my learning and searching is helping someone. oh another learned point, I don't do as well after having whiskey, beer, or wine!
Now I am back to, [Guide/tutorial] Asus Transformer Prime/TF201 stock to Android 7.1 Nougat, and Tab DID NOT reboot and launch the HairyBean TWRP recovery (androwook). It also does not want to recognize ADB it wants to be an MPX device. I tried this:
"2 - INSTALL WINDOWS DRIVERS FOR ASUS TRANSFORMER PRIME TF201
- Windows 8/10 :
On keyboard, type combo : "Windows key + R"
In the command prompt, type :
Code: shutdown -o -r -t 0
It opens Windows Recovery menu:
Go to Troubleshoot -> Advanced Options -> Startup settings -> Restart.
At reboot, hit 7 (Disable driver control) and follow instructions for Windows Vista/7.
Once driver installation is completed, reboot PC as usual."
but it did not like both INF files. On Win 7 I did not have a problem but with WIN 10 it is being more difficult. So I have some more troubleshooting to do. Unless of course someone has found a way to get both android_winusb.inf AND android_apxusb.inf to work correctly.
I fully recovered to stock by back to backing the two threads, first this one..https://forum.xda-developers.com/showthread.php?t=1927818 then this one..https://forum.xda-developers.com/showthread.php?t=2538028
Whatever i did worked as I am back to unlocked stock.