Database Users

[Q] Probelm installing v3 bootloader/recovery

I'm having a problem using the following guide, and I can't seem to find anyone asking the same question...
http://forum.xda-developers.com/showthread.php?t=1622425
Following all the instructions, at step 3 in the directions, I get all the info from checking my SBK number, however the last two lines read: file not found bootloader.img, command failure bootloader download failed.
As there was no bootloader.img and I couldn't find any info on such a file, I pushed ahead, thinking this was common.
I can get into APX mode without issue, its the following steps where I seem to have a problem.
Using the first method listed in step 6, I am never prompted with a "press any key to continue", it just launches straight into attempting the install, and freezes installing (I forget the exact file name but I believe it's the bootloader, it is right in the beginning) it stalls at 131702/78908 (I think those numbers are right)
Using blackthun3r's tool renders the same result. I've tried everything can't figure it out.
I am on a stock 033.00_PA_CUS1 rooted using blackthun3r's tool, which worked perfectly...
Also, I never see the tab entering download mode when in APX it just sits with a black screen.
Anyone have any clue where I'm going wrong here?

Are APX/Download mode drivers installed properly
killdevilfalls said:
I'm having a problem using the following guide, and I can't seem to find anyone asking the same question...
http://forum.xda-developers.com/showthread.php?t=1622425
Following all the instructions, at step 3 in the directions, I get all the info from checking my SBK number, however the last two lines read: file not found bootloader.img, command failure bootloader download failed.
Click to expand...
Click to collapse
the most important thing at step 3 is having the tool "see your uid" the rest...dont worry about.....
I can get into APX mode without issue................
............Also, I never see the tab entering download mode when in APX it just sits with a black screen.
Click to expand...
Click to collapse
ok, you must ensure the apx/download mode drivers are installed.
For your tab to enter download mode it needs the apx drivers...you should see the windows new hardware wizard installing them, and check out the guide again there's a picture of where to look for them in Device Manager....
Yes APX mode is a black screen AND the white led is lit on the power button.
with the apx flash tool, did you install the .apx files from the guide?
thats about all i can offer, dont know anything about step 6.
just make sure u have the boot/recovery aka apx aka download mode drivers installed and installed correctly...good luck

Right Driver
The driver listed when I connect the device in ATX mode is "Acer USB Boot-recovery driver"... is this the correct ATX driver or is there another, as the image shows "Acer Picasso USB-Boot-recovery driver"

killdevilfalls said:
The driver listed when I connect the device in ATX mode is "Acer USB Boot-recovery driver"... is this the correct ATX driver or is there another, as the image shows "Acer Picasso USB-Boot-recovery driver"
Click to expand...
Click to collapse
That, is a very good question!!! I dont know whether there is a dedicated APX driver or whether its a generic term for the 'Picasso' drivers as seen in the image.
All I know is that if these 'boot/recovery' Drivers are not installed then the flash wont work. Keep in mind too, that these nvflash methods are fairly new to most of us, so we're all on a steep learning curve -
I'd suggest going thru the process again, write out each step in your own words if you need to, and take your time - it can be difficult relating the instructions your eyes see on screen with what your fingers are tapping out on the keyboard AND having your head trying to make sense of it all!!! Pick one of the methods, it doesn;t matter which, and stick with it - switvhing between 2 or more can make things even more confusing....
I;m about to go on try civs method now, will let u know how i go
***************************************
UPDATE
steps 1-2-3 check
on getting into apx mode noticed driverrs didnt install
but checked dev man and they were listed as Acer not picasso
ran nvflash
entered 1
entered sbk
command window says nvflash starting.......
that was it couldnt get any further....no entering download mode on tab
uh-oh -
***************************************

Yes- there is a dedicated APX Driver
***************SUCCESS***********
What a mish!!!! Got it going on the 5th time.....flashing r14 as i write...woohoo!
If I knew how to post images then I would...took screenies all the way thru.
Reinstalled all drivers after the first fail.
On next start found new hardware wizard wanted to install drivers for APX!!!!
I have never seen that before
After poking around a bit got them installed with...wait for it...under adb???
They installed as Acer "FastBoot Interface".....
It never showed in my system tray or as Picasso USB etc....in dev man
my next try failed again....waiting for tab to enter download mode......
For my last go at for the nite I bbutton comb'ed to APX first a
nd connected cable 2nd.....within a minute or two Acer Logo on tab
followed by :"entering download mode....within 10 mins I was good to go......
All I can tell you is to keep trying till u get it!!!!!

Probelm installing v3 bootloader/recovery
I have the same problem tried everything your not the only one.

shenny585 said:
I have the same problem tried everything your not the only one.
Click to expand...
Click to collapse
Driverz reinstall them......each time u attempt a flash and it fails at some point, you must reinstall them.
After poking around a bit got them installed with...wait for it...under adb??? They installed as Acer "FastBoot Interface"..... It never showed in my system tray or as Picasso USB etc....in dev man my next try failed again....waiting for tab to enter download mode...... For my last go at for the nite I bbutton comb'ed to APX first a nd connected cable 2nd.....within a minute or two Acer Logo on tab followed by :"entering download mode....within 10 mins I was good to go....
Click to expand...
Click to collapse
If they don't show up in either device manager (under adb/apx or USB controllers) or the system tray "safely remove h/ware then they are not installed, if u continue with flash and it fails then u have to reinstall Acer drivers again!!!
install a500 boot manager u can check for a proper connection with this tool....
See link in my sig for a pictorial showing step by step instructions for using apxflash tool
If this still does not work then post back with the following:
What rom and bootloader u have now or began with
What rom u installed at step 4
R u rooted and do u have a custom recovery installed
On validating yr sbk, at step 3, the most important thing here is to see the system info in the command window,
Boot.img errors u see at the end IS A NORMAL PART OF THE VALIDATION in other words its what you're supposed to see. Correct me if I'm wrong but at that command window aren't u supposed to type: go

[Q] Can't get into recovery, can't get into bootloader download, am I bricked?

I am currently stuck without being able to get into bootloader or recovery. I have a rom that is currently working for about 10 minutes at a time (FLEXREAPER-RF1_rv3-CUSTOM-ICS for HC).
I was orignially on the HC bootloader, using CWM v5. I then used the file found here http://skrilax.droid-developers.org/a500/nvflash/images/a500_a501_bootloaders_apx_ics_v7.zip and installed it from CWM. It looked like it installed just fine.
The problem is that now, when I try to get into recovery, I just see this screen
{
"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"
}
Using Afterota, I was able to get my CPUID and the rest
Tablet Serial : 11920475015
Tablet Cpuid : 011920475015
Tablet Sbk : 0x6AA1E101 0x69CCD301 0x991D3003 0x07580203
Bootloader : 0.03.0X-HC
Android Build : FLEXREAPER-RF1_rv3_Acer_AV041_A500_1.031_033_041.00_CUS_WW_GEN1
But when I try to use blackthund3r or Timmydean, my tablet goes into APX just fine (with the screen blank and the power button white), but none of the tools can get my tablet to go into bootloader download mode.
I am totally stuck, and have no idea what to do. I have tried following instructions for http://forum.xda-developers.com/showthread.php?t=1622425 and http://forum.xda-developers.com/showthread.php?t=1516012, but neither of them can get me into bootloader. When I use the TimmyDean tool and put my tablet into APX manually, I get to the screen where I put in the CPUID, but i tells me that the CPUID I am entering is invalid. I've checked using multiple methods, and I always get my CPUID back at 011920475015. Is this a valid CPUID?
I am going crazy here.

I have the same problem,
i cant boot into recovery mode.
and i cant get it to boot into APX mode i just get a black screen.
and can not find any wifi networks wont even search.
Would love some help.

MrR0ng said:
I am currently stuck without being able to get into bootloader or recovery. I have a rom that is currently working for about 10 minutes at a time (FLEXREAPER-RF1_rv3-CUSTOM-ICS for HC).
I was orignially on the HC bootloader, using CWM v5. I then used the file found here http://skrilax.droid-developers.org/a500/nvflash/images/a500_a501_bootloaders_apx_ics_v7.zip and installed it from CWM. It looked like it installed just fine.
The problem is that now, when I try to get into recovery, I just see this screen
Using Afterota, I was able to get my CPUID and the rest
Tablet Serial : 11920475015
Tablet Cpuid : 011920475015
Tablet Sbk : 0x6AA1E101 0x69CCD301 0x991D3003 0x07580203
Bootloader : 0.03.0X-HC
Android Build : FLEXREAPER-RF1_rv3_Acer_AV041_A500_1.031_033_041.00_CUS_WW_GEN1
But when I try to use blackthund3r or Timmydean, my tablet goes into APX just fine (with the screen blank and the power button white), but none of the tools can get my tablet to go into bootloader download mode.
I am totally stuck, and have no idea what to do. I have tried following instructions for http://forum.xda-developers.com/showthread.php?t=1622425 and http://forum.xda-developers.com/showthread.php?t=1516012, but neither of them can get me into bootloader. When I use the TimmyDean tool and put my tablet into APX manually, I get to the screen where I put in the CPUID, but i tells me that the CPUID I am entering is invalid. I've checked using multiple methods, and I always get my CPUID back at 011920475015. Is this a valid CPUID?
I am going crazy here.
Click to expand...
Click to collapse
Well, first off, your UID is fine. For ICS that is. TimmyDeans tool requires an HC UID. So you can't use it in TimmyDeans. Theoretically the SBK is the same for both in a lot of cases, just the UID number changes. But you have your UID so all is not lost.
Probably just the recovery image got toasted. Also, there are reports that a small percentage of tablets don't get along well with certain version recoveries. No know reason for this.
Can you boot into fastboot mode? (vol+ amd PWR) if so, you can try to fastboot a new recovery image through the android SDK. You can access fastboot through the Android SDK/Platform-tools folder on your PC (open a command window there. Put the tab in fastboot mode, plug in to PC, make sure windows recognizes it as fastboot device.
fastboot flash recovery recovery.img
(recovery.img being the name of the recovery you wish to use)
or
You can try the manual method of NVFlash. Personally I use one of the older tools from BlackThund3r to do this. It's not listed anymore, so if you need it, I'll have to package it in a zip file and post it.
Anyhow, those are a couple of methods to use.
MD

Hi
i need more info on how to fastboot through the Android SDK/Platform-tools.
i have downloaded the android sdk but look like just a package DOWNLOADER developer.android.com/sdk/index.html
cant use the other methods ( NVFlash BlackThund3r) it just hang on the black screen

First off, you have to download and install the Android SDK. When finished, it should install (under Win7) C:\program files (x86)\android\android-sdk
When you install it. make sure you right mouse click and "install as administrator". A good practice to get into when installing things.
Everything you need to know about installing the SDK (including platform tools) can be found here;
http://developer.android.com/sdk/index.html
In there is a folder \Platform-tools. This is where you find Adb And Fastboot. If you hold SHIFT + Right mouse click, you can open a command window there. (win7)
But this is all dependent on whether you installed the correct drivers. Some say Acer Drivers will work. Personally I prefer to use the Google USB Drivers for Android. (google USB Drivers Android).
How do you know your drivers work? Easy, put your tab in APX mode, display will be black but you see the PWR button lit.
Check Windows Device manager with the tablet plugged in. Should list an APX device or Recovery Device. If it doesn't, you need to install the drivers manually by selecting the folder where you extracted the google drivers to. Ignore any incompatibility message.
Whether APX Mode, or Fastboot, Windows should load the specific drivers. If Device Manager doesn't reflect this, then you need to sort it out.
If you want to reflash something using Fastboot, like a boot.img or recovery.img, place the .img file in the same directory as the fastboot command. In most cases with the newer version SDK, it will be in Platform-tools.
The more common fastboot commands can be found in this thread, which I posted the command for recovery.img earlier.
http://forum.xda-developers.com/showthread.php?t=1619913

When i open fastboot.exe the window opens for 1 second and then closes again. am i missing something else.
i am starting to think i may have bricked my tab.

xgutterratx said:
When i open fastboot.exe the window opens for 1 second and then closes again. am i missing something else.
i am starting to think i may have bricked my tab.
Click to expand...
Click to collapse
Dude, you can't "double click" fastboot.exe. Don't work that way.
As I posted earlier, open a CMD window in the platform-tools folder on your PC.
Then put your tab in fastboot mode (vol+ and PWR) till your tab says "fastboot mode". Then plug it in, and check Windows loads the fastboot drivers. (you should see it loading drivers in the windows taskbar).
After that, then you can run the fastboot command to install a recovery image. "IN THE CMD WINDOW"
If you don't feel comfortable doing this, then don't. We can find some other method that may be more comfortable for you.
I can zip up the app that I use, and maybe you should try that first. It uses NVFlash. As I really don't want you to bork things up anymore than they are now. Especially if you're not comfortable with fastboot (you can really bork things up with this).
Give me a little bit, and I'll post something for you guys to try.

Now, this is the tool I generally use. It requires the tab be in APX mode.
http://www.4shared.com/zip/ycbdG0qY/Ver4_BL_and_CWM.html
Extract the zip to your PC. It contains ver4 unlocked bootloader and CWM. I know this combo works.
Put your tab in APX mode. Connect to PC and verify windows loads the correct APX drivers. Then unplug the tab.
Start the app by "right mouse clicking A500APXFLASH.exe, and select "run as administrator".
Plug your APX Mode Tab into the USB when the app tells you. ( i think you have to do this first, or the app will do it for you. Can't remember, an don't feel like flashing another bootloader to find out)
Get your SBK number (usually I have this in notepad so I can copy and paste it).
Usually I select Manual as I only want to select the Ver4 unlocked.bin and the Thor Recovery and none of the other stuff.
Then I select Automatic when prompted. And follow the prompts when asked.
NOTE: After plugging in your APX mode tab, you may still see a message at the bottom of the app stating "No APX Devices Detected" Ignore this and click Next.
This was a small bug.
Also, sometimes on Win7 you may get a windows error box. Ignore this also and close it.
DO NOT UNPLUG the tab until the apps says complete. The whole process takes about 5 minutes or so to complete.
Then it's safe to unplug the tab. Shut it down, and reboot to recovery to make sure it works.
Also something I want to mention. If you guys installed OTA's, make sure you delete the "boot to recovery.p" in your tabs System file as states in Civato's thread. Otherwise, when you boot normally, it will delete your Custom Recovery, and you'll be doing this again.
MD

Hi MD,
thx for trying to help out here, much appreciated.
I've just tried your steps, the apx flash utility stays put at "stage two - uploading image..." and the nvflash cmd prompt stays at "[resume mode]". Waited for 10 minutes...nothing.
Is there anything else to try ?
ta,
T

Tommmii said:
Hi MD,
thx for trying to help out here, much appreciated.
I've just tried your steps, the apx flash utility stays put at "stage two - uploading image..." and the nvflash cmd prompt stays at "[resume mode]". Waited for 10 minutes...nothing.
Is there anything else to try ?
ta,
T
Click to expand...
Click to collapse
Well, there's always some tricks to try.
Did you use the Google drivers and verify you tab is registered in Windows Device Manage as APX device or Recovery Device?
To manually go to APX, shut down tab. Put a paper clip in the reset button, and hold. With your other hand, press and hold PWR for 3 seconds, release PWR, then about 1 second later remove paper clip. You should have black display with pwr lite on. Plug in tab and check device manager.

apx flashutil claims "Acer APX Mode device detected"
device mgr shows "Acer USB Boot-recovery driver" under "Universal Serial Bus controllers"

Tommmii said:
apx flashutil claims "Acer APX Mode device detected"
device mgr shows "Acer USB Boot-recovery driver" under "Universal Serial Bus controllers"
Click to expand...
Click to collapse
OK, that's good (I had to double check with mine)
Now, did you run the package I posted earlier? Reason is, it uses a .bin file instead of an apx package.
Also, as I am dealing with several other folks, do you have a bootloader when you boot? Like Skirlax_CZ blah blah blah version xxxx?

I tried the bootloader_ics_v4.bin and the recovery you supplied.
There's no mention of a bootloader on the A501
Supposition : if my cpuid were wrong, would apxflash throw an error?

Tommmii said:
I tried the bootloader_ics_v4.bin and the recovery you supplied.
There's no mention of a bootloader on the A501
Supposition : if my cpuid were wrong, would apxflash throw an error?
Click to expand...
Click to collapse
@Tommmii, Which tablet do you have? a 500 0r 501?
Generally, if the UID/Sbk were wrong, the apps would throw an error.

A501
I'm beginning to suspect my UID (037c700140c0941) could be wrong.
If so, i'll be stuck up a creek without a paddle

Tommmii said:
A501
I'm beginning to suspect my UID (037c700140c0941) could be wrong.
If so, i'll be stuck up a creek without a paddle
Click to expand...
Click to collapse
Looks like an HC UID. But it doesn't matter. If this was the UID you pulled under HC. Basically, ICS will change the UID. As a matter of fact, it may change it several times when you install ISC Roms. What shouldn't change, in most cases, is the SBK. Usually the SBK is the same under HC and ICS. At least with my tab it was.
Naw,,,, you still got a paddle.
I got a 501 also.
So tell me, do you have any bootloader at all when you try to boot normally?
Also, you didn't tell me what happened when you tried running the app I posted with the Ver4 unlocked bootloader. Did it work? (don't worry if it said 500 or 501, can fix that later)
Attached is my 501 ver4.bin Throw it in the same directory as the tool I posted.

Power On gives the white Acer logo, followed by a bootlogo ("android" metallic type letters) From memmory that could be the stock HC bootlogo. Stuck in a loop though...
VolDown & PWR gives the HC Andy with an exclamation triangle dangling above his head.
edit : just tried renaming SD_Acer_A501_1.309.02_COM_GEN1 to update.zip , it updated the rom but no boot same as above
edit2 : didn't see your attachement...just tried it, stuck at [resume mode] in the nvflash debug window

You rock so hard!
The super ridiculous fastboot method worked PERFECT for me. Took me all of 2 minutes. I was pulling my hair out. Thanks so much for the AMAZING support. Love the android community.
Moscow Desire said:
Well, first off, your UID is fine. For ICS that is. TimmyDeans tool requires an HC UID. So you can't use it in TimmyDeans. Theoretically the SBK is the same for both in a lot of cases, just the UID number changes. But you have your UID so all is not lost.
Probably just the recovery image got toasted. Also, there are reports that a small percentage of tablets don't get along well with certain version recoveries. No know reason for this.
Can you boot into fastboot mode? (vol+ amd PWR) if so, you can try to fastboot a new recovery image through the android SDK. You can access fastboot through the Android SDK/Platform-tools folder on your PC (open a command window there. Put the tab in fastboot mode, plug in to PC, make sure windows recognizes it as fastboot device.
fastboot flash recovery recovery.img
(recovery.img being the name of the recovery you wish to use)
or
You can try the manual method of NVFlash. Personally I use one of the older tools from BlackThund3r to do this. It's not listed anymore, so if you need it, I'll have to package it in a zip file and post it.
Anyhow, those are a couple of methods to use.
MD
Click to expand...
Click to collapse

Tommmii said:
Power On gives the white Acer logo, followed by a bootlogo ("android" metallic type letters) From memmory that could be the stock HC bootlogo. Stuck in a loop though...
VolDown & PWR gives the HC Andy with an exclamation triangle dangling above his head.
edit : just tried renaming SD_Acer_A501_1.309.02_COM_GEN1 to update.zip , it updated the rom but no boot same as above
edit2 : didn't see your attachement...just tried it, stuck at [resume mode] in the nvflash debug window
Click to expand...
Click to collapse
Ewwww.... right now, I am at a loss for a plan of attack.
After running the rom, and it updating ok, the Acer with the metallic logo's tells me it's a modified bootloader (I saw this in the earlier unlocked bootloader logos. Ver3 I believe. However, this ver3 I don't believe had flashboot capability.
Ver3 is ok. You can run it. Why we can't get it updated to ver4 right now, is beyond me.
Hmmm.... will have to come up with a different plan.
One thing puzzles me, why when you ran that .... "update", it didn;t put a stock bootloader on it.
Ewwww... too bad you are not near Moscow. I would love to get my hands on it.

could i run nvflash manually when connected in APX mode ?
Perhaps it would show more debug info then...?

Need Help! Tablet Stuck and Fastboot Not Working

I am sitting dead in the water with an EVGA Tegra Note 7 that can't turn on Wireless and won't let me install drivers to move further or even do a restore.
First off I am using Tomsgt Super Tool: http://forum.xda-developers.com/showthread.php?t=2627654
So my device was continuing to fail an OTA update so I was going to use this device to reinstall the basic 4.4.2. However during the process Fastboot.exe gave a failed message in Windows, but it showed fastboot after the device name. I continued to let it Restore Tegra Note 7 to Android 4.4.2 and first of all it did it way too fast and once it was finished I couldn't get the Wireless to enable. I read another person with the same problem that had to redo the process. Well I can't get past reinstalling ADB and Fastboot, now not even ADB..
I tried uninstalling the device from Windows letting it reinstall and then checking it again. No matter what I do the USB Driver Scan fails over and over. I got this issue the first time, but somehow I got it to catch the device once and install ADB.
1) Yes USB Debugging in Enabled
2) Yes Anti-Virus is Off
3) Bootloader unlocked
4) Tried Different USB Ports
So what the hell is going on here?? All I wanted to do was run a damn OTA update.. Now I have a tablet with no wireless and I obviously can't do an OTA update now.
{
"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 was thinking about not using the tool and doing it all manually like I used to do, but all the tool does is auto execute files/folders in specific orders, basically an elaborate .bat file. So if it is failing at ADB, it is going to fail for me manually too.
Please give me some idea of what to do. I don't see how relocking the bootloader would do anything, but aside from that it was a non-rooted stock 4.4.2 OS running.
Is there something I need to do in order to get Impactor to work?
So then I plug the device into a 9 year old laptop with Windows XP and Impactor sees the device on the first try and installs the driver (it takes 2-3 minutes). Then it finishes and I close impactor, but I get an error next saying device not found. I restart the machine and now it is exactly like my desktop, Impactor can't see the device at all.
What in the hell is going on here? If I had known all this was going to happen I would have skipped their damn OTA update that continued to fail.
BTW with XP I can prevent Windows from installing any type of driver, so I did. Should I let XP search for a driver and see what happens?
Someone throw me some ideas, you can see a full explanation of what is happening if you scroll up to my screenshot. I basically have a dead device because I wanted to use this tool to do a recovery...
Wireless refuses to turn on, it just sits there for hours if I let it.
Someone please give me guidance, I was out of the Android scene for a while and I've forgotten a lot of the tricks I used to know.

If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.

share_needles said:
If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.
Click to expand...
Click to collapse
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again. I believe there is a quick message that flashes the first time I try to select Fastboot, however it's way too fast to read. When I do it again after that is when I will see a black flash, but apparently from what I have heard that is all Fastboot kernel is supposed to do??
How do I verify Fastboot is working before I flash the damn thing?

NCSUZoSo said:
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again.
How do I verify Fastboot is working before I flash the damn thing?
Click to expand...
Click to collapse
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.

share_needles said:
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.
Click to expand...
Click to collapse
Can I get some official links for the newest/compatible versions of TWRP and the latest stock ROM I can install that is the most up to date (with Google Apps)?
Sorry to ask, but I am short on time most of the time and I might have an hour or so to work on it tomorrow.

Sorry I don't have official links but it would take you 10mins to find them through google. Good luck.

I have two files which I believe are correct except the TWRP file has an odd extension..
"Shaky156-TWRP-recovery.img.exe"
the other that is supposed to have GApps is: Stock-4.4.2-2.5-TegraNote7.zip
If that zip is only like 440 MB is that even possible? Can someone point me in a better direction if this sounds wrong.
Sources, TWRP: http://forum.xda-developers.com/showthread.php?t=2586432
Actually thinking about it and I bet with having things specific to img files like IMGBurn and other software it may create a .exe so it's easier to emulate it as a disk.
Do we have any good custom ROMs these days you'd suggest over stock? Are any that stable yet? If not can anyone find me a complete download if a 440MB zip is too small to have GApps in it.

I used Fastboot commands to get TWRP installed and Android is "upgrading.." now, so hopefully this will fix it.
I have the tablet up and running going into Google Play now.
I used this thread's link for the latest TWRP (2.7.1.0): http://forum.xda-developers.com/showthread.php?t=2586432
I got a completely stock version of 4.4.2 and OTA shows this as the most up to date version. I got my copy of the 4.4.2 ROM out of the Super Tool's folder that you can find here: http://forum.xda-developers.com/showthread.php?t=2627654
The tricky part to this my first time was I forgot you can open a command window inside the folder that contains TWRP/Fastboot/etc. (hold Shift and Right Click in the folder where all the data is and hit open command window)
Obviously everything came off a SD Card installed into the TN7.

answer for dummies
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks

aimeymarie said:
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks
Click to expand...
Click to collapse
Your best bet is to find someone you know who the above is not a foreign language to. I mean it could be broken down step by step as basic as possible and you may still not understand parts.

Yoga Tab 2 8" 830f failed update led to soft lock

So I downloaded a 16mb OTA update and let the tablet do its thing without touching it. I waited for the tablet to boot up, but it was stuck in a black screen for about 12 minutes until I decided to turn it off and on. It didn't work, so I went to the recovery to do a factory reset and clear the cache, but it still didn't work. I later went to this Russian forum here from this thread. I downloaded a lollipop rom and proceeded to flash it using Phone Flash Tool Ver. 5.2. It went well until 16% in where it failed. Unfortunately, I don't have a screenshot of 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"
}
(image of the files in the rom I downloaded)
After all this happened, I tried to start it up but I got the message "Boot Failed. EFI Hard Drive. Boot Successful - Enter Setup"
And now it won't go into recovery mode, but it does go into fastboot and bios setup.
Since it does go into fastboot, I tried to use a tool from this thread (Temp recovery) to use a temporary cwm recovery to hopefully be able to at least boot into that, but that didn't end up working.
I got another rom from the same Russian site that had differently packaged files but still the same stock lollipop rom.
I tried to just use the recovery from there to manually flash it using fastboot, but it still failed.
I later found this thread with these instructions for this problem.
1. download and extract this file someplace on your pc
2. uninstall your existing Phone Flash Tool and from the drivers folder install both files (Intel Phone Flash Tool and Android Driver accepting defaults) reboot pc when finished
3. place your tab in DNX mode (from power off press and hold both volume keys then press pwr to start, in a few you screen will show "Fastboot starting..." message and hang on that. you must get that message on your tab screen, restart from power off until you have it)
4. start the installed Phone Flash Tool and load flash.xml from the extracted YT2-830L... folder then Start Flashing, it will reboot when done
Click to expand...
Click to collapse
The file he linked in his post (ionioni ) was gone but I still tried to do this with the roms I had. And guess what? It still didn't work. The instructions said to place the tablet in DNX mode (meaning fastboot), which I did do...only when I put it into fastboot, it was set to DNX_OS which came to say "Wrong device state" in Phone Flash Tool.
I've tried what I could, but failed. Anyone have any suggestions?

AgentXGhost said:
So I downloaded a 16mb OTA update and let the tablet do its thing without touching it. I waited for the tablet to boot up, but it was stuck in a black screen for about 12 minutes until I decided to turn it off and on. It didn't work, so I went to the recovery to do a factory reset and clear the cache, but it still didn't work. I later went to this Russian forum here from this thread. I downloaded a lollipop rom and proceeded to flash it using Phone Flash Tool Ver. 5.2. It went well until 16% in where it failed. Unfortunately, I don't have a screenshot of this.
(image of the files in the rom I downloaded)
After all this happened, I tried to start it up but I got the message "Boot Failed. EFI Hard Drive. Boot Successful - Enter Setup"
And now it won't go into recovery mode, but it does go into fastboot and bios setup.
Since it does go into fastboot, I tried to use a tool from this thread (Temp recovery) to use a temporary cwm recovery to hopefully be able to at least boot into that, but that didn't end up working.
I got another rom from the same Russian site that had differently packaged files but still the same stock lollipop rom.
I tried to just use the recovery from there to manually flash it using fastboot, but it still failed.
I later found this thread with these instructions for this problem.
The file he linked in his post (ionioni ) was gone but I still tried to do this with the roms I had. And guess what? It still didn't work. The instructions said to place the tablet in DNX mode (meaning fastboot), which I did do...only when I put it into fastboot, it was set to DNX_OS which came to say "Wrong device state" in Phone Flash Tool.
I've tried what I could, but failed. Anyone have any suggestions?
Click to expand...
Click to collapse
This is the file you need https://drive.google.com/file/d/0B1LaMEhefCBgYzNTOUxJZmtWQ0E/view
And this https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
Ignore the oops error warning, it's something to do with what G drive can scan.

Holy Sh!t. this just absolutely worked!! I didn't think I could bring this thing back to life, but the files you linked just did it! Really, I don't know how to thank you enough for this.

corasman said:
This is the file you need https://drive.google.com/file/d/0B1LaMEhefCBgYzNTOUxJZmtWQ0E/view
And this https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
Ignore the oops error warning, it's something to do with what G drive can scan.
Click to expand...
Click to collapse
Hi folks,
had the exact same issue and indeed the 1st link offered (https://drive.google.com/file/d/0B1LaMEhefCBgYzNTOUxJZmtWQ0E/view) worked like a charm.
The second link is to download the "Intel platform flash tool lite", but I used my existing version of the Intel Phone Flash Tool (5.2.1-0) which worked fine with the image.
In other words, Corasman, it appears you have saved 2 people's life (or at least tablets) with your solution, so Thanks ! :good:
Regards.

Make that 3 people! Thank you so much corasman - your post has finally fixed my yoga 2 tablet, which I was sure would be going in the bin. Can't overstate how grateful I am - Cheers!

update 830f with 1050f rom?
updating 830f with 1050 rom? does it work?

hello. I have the same problem. I update OTA to lolipop. Since the table is slow, i tried flashing some ROM (which i cannot recall) and the tablet stopped working. Now, I am trying to flash the link you provided and it succeed. However after that i get blank Screen. what Could be wrong. My table is YT2 830LC. Please help

I am typing this all over again after my full report vanished. Do not have the patience of typing all that again. Suffice to say I had a similar situation with the boot failed EFI Hard Drive. Boot Successful - Enter Setup" message on my 830LC.
I had even found the bios restore tool for moving back from lollipop to kitkat but it too would hang. And attempts to flash lollipop would fail immediately with the same message as the OP, wrong device state.
So, in spite of it seeming completely counter-intuitive, I flashed the 1050F rom in the link shared by Corasman. Strange as it may seem, my tablet is now alive and working. No calling function, but it is working and calling itself a 1050F.
Now my research has to shift to whether the 830 LC rom can be flashed now.

i have a same problem with yoga 2 pro 1380f mr corasmancan help me

prabuddhadg said:
I am typing this all over again after my full report vanished. Do not have the patience of typing all that again. Suffice to say I had a similar situation with the boot failed EFI Hard Drive. Boot Successful - Enter Setup" message on my 830LC.
I had even found the bios restore tool for moving back from lollipop to kitkat but it too would hang. And attempts to flash lollipop would fail immediately with the same message as the OP, wrong device state.
So, in spite of it seeming completely counter-intuitive, I flashed the 1050F rom in the link shared by Corasman. Strange as it may seem, my tablet is now alive and working. No calling function, but it is working and calling itself a 1050F.
Now my research has to shift to whether the 830 LC rom can be flashed now.
Click to expand...
Click to collapse
i have same problem with my yoga 830lc this rom not work help me to run my tab agian
---------- Post added at 10:55 AM ---------- Previous post was at 10:47 AM ----------
corasman said:
This is the file you need
And this
Ignore the oops error warning, it's something to do with what G drive can scan.
Click to expand...
Click to collapse
hy sir downlod the rom from google drive but unable to download 2nd link (link not working)
i use latest intel flas tool light but the rom no flash to my device its show errors. plese sir help me to run my tab again

Apply update from sdcard FAILED : Rooted Crosscall Trekker M1 on BOOTLOOP

Hi there ! Hope you're doing all right
I had a lot of issues recently with my phone : Crosscall Trekker M1
It all begin when I started to remove entirely Google from the phone.
I rooted it and took the liberty to delete all that mention google.
I unfortunately delete a system file and that how my problems began.
(I called couple of times the Technique Assistance from Crosscall's Website but they weren't able to help me and I had the same story with the SAV --> the after selling's services. I gave up about asking them help and I decided to solve the issue by my own.)
So for now the phone start on bootloop, (I cannot use the OS anymore) so I can launch it in Recovery mod only.
After days of researchs I found the original stock rom for the Trekker M1 !!
On the recovery : After I wiped data and cache of course :
I tried to install the Rom with the option : "Apply update from sd card" but it didn't worked.
So I tried to install differents Custom Recovery like CWM and even renamed them update.zip but I had the exact same issue:
"E : failed to verify whole-file signature
E : signature verification failed
Installation aborted."
I also wanted to try Odin but apparently Crosscall's phones doesn't have a recuperation mod (I dream that someone got me wrong on this :crying: )
I've got a few clues about all this :
I guess the Debugging USB Mod isn't enable anymore on the phone
Maybe the versions of ClockWorkMod weren't compatible at all with my phone.
All I know is that the phone is rooted;
The recovery's version is : "Android system recovery <3e> LMY47V release-keys"
So know you know everything
Does someone think, he or she can help me with this ?
Thank you for your attention !

Brazyxs said:
Hi there ! Hope you're doing all right
I had a lot of issues recently with my phone : Crosscall Trekker M1
It all begin when I started to remove entirely Google from the phone.
I rooted it and took the liberty to delete all that mention google.
I unfortunately delete a system file and that how my problems began.
(I called couple of times the Technique Assistance from Crosscall's Website but they weren't able to help me and I had the same story with the SAV --> the after selling's services. I gave up about asking them help and I decided to solve the issue by my own.)
So for now the phone start on bootloop, (I cannot use the OS anymore) so I can launch it in Recovery mod only.
After days of researchs I found the original stock rom for the Trekker M1 !!
On the recovery : After I wiped data and cache of course :
I tried to install the Rom with the option : "Apply update from sd card" but it didn't worked.
So I tried to install differents Custom Recovery like CWM and even renamed them update.zip but I had the exact same issue:
"E : failed to verify whole-file signature
E : signature verification failed
Installation aborted."
I also wanted to try Odin but apparently Crosscall's phones doesn't have a recuperation mod (I dream that someone got me wrong on this :crying: )
I've got a few clues about all this :
I guess the Debugging USB Mod isn't enable anymore on the phone
Maybe the versions of ClockWorkMod weren't compatible at all with my phone.
All I know is that the phone is rooted;
The recovery's version is : "Android system recovery <3e> LMY47V release-keys"
So know you know everything
Does someone think, he or she can help me with this ?
Thank you for your attention !
Click to expand...
Click to collapse
Hello,
Can you capture files included in update.zip?

-Hope- said:
Hello,
Can you capture files included in update.zip?
Click to expand...
Click to collapse
By uptade.zip do you think about the Rom or the Custom Recovery ?
And yes I can

Brazyxs said:
By uptade.zip do you think about the Rom or the Custom Recovery ?
And yes I can
Click to expand...
Click to collapse
Can u copy the stock ROM name before renaming it to update.zip and yeah I meant the update.zip

-Hope- said:
Can u copy the stock ROM name before renaming it to update.zip and yeah I meant the update.zip
Click to expand...
Click to collapse
Here's the name of the stock rom :
LU652R(HS-L635)_L1185.6.02.00.EU00_MultiDownload_201601292005_user.tar.gz
To correct what I said first : I didn't renamed the Rom in fact, I did it only with the CWM file who was actually in zip format
(Sorry about that)
I couldn't even try to install the Rom because the Recovery doesn't recognize it

Brazyxs said:
Here's the name of the stock rom :
LU652R(HS-L635)_L1185.6.02.00.EU00_MultiDownload_201601292005_user.tar.gz
To correct what I said first : I didn't renamed the Rom in fact, I did it only with the CWM file who was actually in zip format
(Sorry about that)
I couldn't even try to install the Rom because the Recovery doesn't recognize it
Click to expand...
Click to collapse
Can u provide me with a pic of the tar.gz file (the files inside it)

-Hope- said:
Can u provide me with a pic of the tar.gz file (the files inside it)
Click to expand...
Click to collapse
Here's 4 captures of the tar.gz opened with Winzip
{
"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"
}
View attachment 4279786
View attachment 4279787
View attachment 4279788

Brazyxs said:
Here's 4 captures of the tar.gz opened with Winzip
View attachment 4279785
View attachment 4279786
View attachment 4279787
View attachment 4279788
Click to expand...
Click to collapse
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil

-Hope- said:
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil
Click to expand...
Click to collapse
Thank you very much ! I will check about QFIL by myself. For now I'm happy that someone care about my issues
I tell you if there is something new !

-Hope- said:
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil
Click to expand...
Click to collapse
So it appear that the Crosscall M1 got an emergency mode. I can launch it by pressing Vol + and Vol - when I'm plugging the phone to a computer by USB.
At this moment a message show up :
"Authority indentification not found !"
"Long press power key to continue ..."
and if I do it :
No update file in TFcard!
X
Update failed!
Long press power key to power off.
If I start the phone on Emergency Mode with QFIL working (what I need to do) nothing happen.
I still have the message No Port Available on the top of QFIL.
So I'm wondering,
Do you think I can fix in some ways that problem of unrecognized device ?
or
Is there a way that I can install the Rom by choosing to install it as an update with the Emergency Mode. The Rom files would be the update that i put before in a "TFcard" in some format ?

Brazyxs said:
So it appear that the Crosscall M1 got an emergency mode. I can launch it by pressing Vol + and Vol - when I'm plugging the phone to a computer by USB.
At this moment a message show up :
"Authority indentification not found !"
"Long press power key to continue ..."
and if I do it :
No update file in TFcard!
X
Update failed!
Long press power key to power off.
If I start the phone on Emergency Mode with QFIL working (what I need to do) nothing happen.
I still have the message No Port Available on the top of QFIL.
So I'm wondering,
Do you think I can fix in some ways that problem of unrecognized device ?
or
Is there a way that I can install the Rom by choosing to install it as an update with the Emergency Mode. The Rom files would be the update that i put before in a "TFcard" in some format ?
Click to expand...
Click to collapse
Can you try to run it as an admin then choose the right com and try again ?

-Hope- said:
Can you try to run it as an admin then choose the right com and try again ?
Click to expand...
Click to collapse
I tried to run QFIL as an admin but it doesn't make a difference. The thing is that my device isn't recognize at all by my computer.
I sorry but what do you mean what "choose the right com" ?

Brazyxs said:
I tried to run QFIL as an admin but it doesn't make a difference. The thing is that my device isn't recognize at all by my computer.
I sorry but what do you mean what "choose the right com" ?
Click to expand...
Click to collapse
Did you install the qcom drivers

-Hope- said:
Did you install the qcom drivers ?
Click to expand...
Click to collapse
Hi, Here's the list of all the drivers I installed :
Qualcomm_USB_Driver_V1.0
MTK_USB_All_V1.0.8
ADBDriverInstaller
I also installed :
Android-sdk
Java SE Development Kit

After a lot of research my device still isn't showing on QFIL.
But for a time he showed up on "ADB Driver installer". I plugged the phone by USB and started it with a special combinaison (almost like the Emergency Mode's combinaison) that I'm still trying to remember.
There is also another a new thing. If I start my device that I plug before by USB and only with the power button :
My computer recognize it and the Driver Software Installation try to install MTP USB Device.
The operation failed everytime but for now I'm happy that the device is recognize.

Brazyxs said:
After a lot of research my device still isn't showing on QFIL.
But for a time he showed up on "ADB Driver installer". I plugged the phone by USB and started it with a special combinaison (almost like the Emergency Mode's combinaison) that I'm still trying to remember.
There is also another a new thing. If I start my device that I plug before by USB and only with the power button :
My computer recognize it and the Driver Software Installation try to install MTP USB Device.
The operation failed everytime but for now I'm happy that the device is recognize.
View attachment 4284734
Click to expand...
Click to collapse
Just reread the post, try to do a factory reset

-Hope- said:
Just reread the post, try to do a factory reset
Click to expand...
Click to collapse
The factory reset isn't working (and I just tried one more time), that is why I need to flash my rom.

Brazyxs said:
The factory reset isn't working (and I just tried one more time), that is why I need to flash my rom.
Click to expand...
Click to collapse
wait you said that adb works, if you can find the file system from an exact phone uploaded or you know that its common you can push it using adb if you are rooted

-Hope- said:
wait you said that adb works, if you can find the file system from an exact phone uploaded or you know that its common you can push it using adb if you are rooted
Click to expand...
Click to collapse
Yes I did said that, adb worked for a time.
I'm not sure to understand what you mean by "the file system" and "push it " with adb
The thing I'm sure of is that I'm rooted :good:
I'll continue my researchs.