Database Users

Restored i9020T ROM to i9020A

I was trying to restore my ATT Nexus S to the stock Android build following the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=1061855
However, I didn't realize that it was the wrong version, and now my Nexus will not boot. I've done considerable searching, but it will not turn on. I hope I don't have a brick, but if there are any tips that anyone can give to a major Android amateur, I would really appreciate them.

When you say will not boot what exactly are you describing? Does it power up? Can you get to the bootloader? Does your computer recognize the phone when connected via USB?
Sent from my PC36100 using XDA Premium App

I'm not that familiar with it, but use odin to reflash the stock firmware.
Sent from my Nexus One using Tapatalk

uansari1 said:
I'm not that familiar with it, but use odin to reflash the stock firmware.
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
I would recommend this only as a matter of last resort.

If your ROM that you flashed contained a radio IMG of the T version it may be bricked.. I know the only way you can pretty much brick an android device is by flashing the wrong radio or having a bad radio flash;/ But that was predominantly with HTC models, not 100 percent sure with sammy models...
JD

JupiterDroid said:
If your ROM that you flashed contained a radio IMG of the T version it may be bricked.. I know the only way you can pretty much brick an android device is by flashing the wrong radio or having a bad radio flash;/ But that was predominantly with HTC models, not 100 percent sure with sammy models...
JD
Click to expand...
Click to collapse
Yes I looked in the thread and the ROM he flashed did include radios.
However! It's mighty hard to brick a Nexus S
My suggestion to the OP. I do not have time right now to find these things for you, but a general outline of what you need to do is:
1. Get fastboot working
2. Use fastboot to flash ClockworkMod Recovery
3. Find the i9020A stock rom and flash it.
4. Do not try to boot phone
5. Find the i9020A radio and flash it.
Or you might even find a ROM for i9020A that includes the radio, in which case you could just flash that.
OR, if you find a Nandroid backup of i9023A stock ROM, you can restore that. But you will still need to flash the proper radio.

matt2053 said:
Yes I looked in the thread and the ROM he flashed did include radios.
However! It's mighty hard to brick a Nexus S
My suggestion to the OP. I do not have time right now to find these things for you, but a general outline of what you need to do is:
1. Get fastboot working
2. Use fastboot to flash ClockworkMod Recovery
3. Find the i9020A stock rom and flash it.
4. Do not try to boot phone
5. Find the i9020A radio and flash it.
Or you might even find a ROM for i9020A that includes the radio, in which case you could just flash that.
OR, if you find a Nandroid backup of i9023A stock ROM, you can restore that. But you will still need to flash the proper radio.
Click to expand...
Click to collapse
With HTC models if you flash a bad radio thats your superphone dead! Are you sure this is retrievable on sammy devices? I hope to god it is for the OP's sake
JD

jstennis1591 said:
I was trying to restore my ATT Nexus S to the stock Android build following the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=1061855
However, I didn't realize that it was the wrong version, and now my Nexus will not boot. I've done considerable searching, but it will not turn on. I hope I don't have a brick, but if there are any tips that anyone can give to a major Android amateur, I would really appreciate them.
Click to expand...
Click to collapse
I looked in the zip that you flashed, and what you did is flashed a bootloader.img that's not for your i9020a and thats why your phone isn't booting. The radio has nothing to do with the phone not booting.
To solve your problem, you're going to have to find a copy of the bootloader.img that belongs to the i9020a and flash it with Odin through download mode.
To get a copy of the bootloader.img someone with i9020a will have to dump it from there phone through adb. (I'll put the steps how later today)
To get into download mode, you'll need to hold the volume + & - buttons and plug the phone into the computer while the phone is off and Odin is running on the computer. And if that doesn't work you'll have to use jig 301k resistor connector to get into download mode (Search how to make one on nexus s or sgs forum)
That's the only way to save your phone is through Odin and download mode, sorry.
Sent from my Nexus S using XDA Premium App

For reference if you restored the i9020T bootloader to the i9020A it will hard brick. I can however fix a phone in that scenario even still with my JTAG repair. Just PM me if you need a hard bricked Nexus S of any model fixed.

I've regrettably done the same - gotten a i9020-non-A bootloader confused with the i9020A - and bricked my device by writing that incorrect bootloader (using 'fastboot flash bootloader <wrong bootloader here>.img'). The phone is now totally unresponsive (power button, vol+ & power, etc).
I don't have a Windows machine to hand, but do have a WinXP VM within a Linux host available. Based on a muddle of other XDA posts I fetched/installed Odin 1.82, the Samsung USB drivers and what I believe to be a valid i9020A image (details below).
reddv1 said:
...
To get into download mode, you'll need to hold the volume + & - buttons and plug the phone into the computer while the phone is off and Odin is running on the computer. And if that doesn't work you'll have to use jig 301k resistor connector to get into download mode ...
Click to expand...
Click to collapse
Problem is I get nada when plugging the phone in with vol button held down (pressing in the whole vol button, both + and - pressed) and plugging the phone in with Odin running and VM capturing USB devices. i.e. either I'm not using Odin correctly and/or running it within a VM doesn't work, or I need the hardware helper (USB adapter w/ resistor).
Could you offer any tips on how to drive Odin?
Plan B is to send the phone for JTAG recovery, though as I'm not in the US that's a bit of a pain.
I9020A image:
Android 2.3.3 (Build GRI54/UCKB2 Radio/KA3 Bootloader)
2.3.3 -> 2.3.4 (android.clients.google.com/packages/ota/google_crespoa/286d814dee5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip)

af3556 said:
I've regrettably done the same - gotten a i9020-non-A bootloader confused with the i9020A - and bricked my device by writing that incorrect bootloader (using 'fastboot flash bootloader <wrong bootloader here>.img'). The phone is now totally unresponsive (power button, vol+ & power, etc).
I don't have a Windows machine to hand, but do have a WinXP VM within a Linux host available. Based on a muddle of other XDA posts I fetched/installed Odin 1.82, the Samsung USB drivers and what I believe to be a valid i9020A image (details below).
Problem is I get nada when plugging the phone in with vol button held down (pressing in the whole vol button, both + and - pressed) and plugging the phone in with Odin running and VM capturing USB devices. i.e. either I'm not using Odin correctly and/or running it within a VM doesn't work, or I need the hardware helper (USB adapter w/ resistor).
Could you offer any tips on how to drive Odin?
Plan B is to send the phone for JTAG recovery, though as I'm not in the US that's a bit of a pain.
I9020A image:
Android 2.3.3 (Build GRI54/UCKB2 Radio/KA3 Bootloader)
2.3.3 -> 2.3.4 (android.clients.google.com/packages/ota/google_crespoa/286d814dee5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip)
Click to expand...
Click to collapse
I think you need a windows PC, where's the link to the i9020a Odin package
Sent from my Nexus S using XDA Premium App

I dunno if this will helpful... but I was in a very similiar situation 2 days ago... I wanted to unroot my phone and restore to stock .. so I found this Odin guide... which was for nexus 4G model.. I had non-4G i9020a. So during Odin process it failed on radio ..and I thought my phone was bricked but I took out the bettery and put it back in and the phone booted into android normally..however in about phone .. everything was showing unknown and I had no signal..so with the help of fellow xdaers. I first downloaded the FULL rom for i9020A and placed it on my sd card.. Downloaded CWM and got it onto my Phone..then wiped cache, system/data etc... and installed the rom from sd card and phone was back to normal.. so if ur able to boot into the phone I would suggest what I did.. and obviously if u need detailed guide of what I did.. don't hesitate to ask... hope your phone comes back to life... (Y)
Sent from my Nexus S using XDA App

G'Day reddv1: is odin specific to each model phone? The one I have I fetched from droidangel.blogspot.com/2011/05/odin-multi-downloader-flasher-program.html, that page lists a Odin3 v1.82.rar for the i9020a. However the exe therein is named I9003_Odin3 v1.82.exe.
Can you clarify the steps required to get Odin to recognise the phone? Is this correct:
1) phone is off, odin is running on the Windows PC (w/ Samsung USB drivers installed - yes?)
2) press and hold both volume +/- buttons (i.e. press the entire vol button in)
3) plug in USB
4) ?
5) profit
forpulse: problem is my phone is bricked, i.e. won't power on. The odin guides I've found so far use it in a way that assumes the phone can be put into recovery mode, which mine can't be. (e.g. http://forum.xda-developers.com/showthread.php?t=1088494)

I sent my bricked phone to MobileTechVideos and he was able to JTAG recover the phone (and left no marks, etc). However the bad news is the phone now has a very bad purple/pink tint to the screen (have tried a couple of ROMs).
{
"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"
}

connexion2005 said:
For reference if you restored the i9020T bootloader to the i9020A it will hard brick. I can however fix a phone in that scenario even still with my JTAG repair. Just PM me if you need a hard bricked Nexus S of any model fixed.
Click to expand...
Click to collapse
hey I've COMPLETELY inadvertantly flashed a i9020t radio on my i9020a, its as bricked as ive ever seena phone. wont turn on, black screen, nothing.
My question, will it go into download mode if I plug in a 301k resistor jig
or is jtag my only hope
thanks

Good to know I'm not the only one...
Anyone have ideas for my "Flashed I9020A ROM on a D720" thread over here? http://forum.xda-developers.com/showthread.php?t=1319865

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.

[HOWTO] Unbrick Hardbricked (stuck onUSB Logo) MeMo Pad ME170CX (and others)

This guide will help you unbrick your hardbricked MeMo pad or possibly other device. For the purpose of this guide, hardbricked will refer to a device's software being damaged to the point where standard procedures and utilities (adb, fastboot, recovery, etc.) will not be able to make the device functional again. In order to be hardbricked, you essentially need to erase or damage the bootloader. Without the bootloader, you can't use fastboot or recovery since all of those things require the bootloader. This guide addresses that situation (your device should be displaying nothing but the USB logo, as seen in the attachment). If you have a working bootloader and can run fastboot commands, THIS GUIDE IS NOT FOR YOU and will only possibly make things worse.
This guide is directed towards the ME170CX, which is also apparently called the ME70C or KO1A; however, the same process should work for other MeMo Pad devices and even other Intel devices. I cannot provide much help for other devices, so try at your own risk.
Do not follow this guide unless it is your last hope or you know what you are doing. I am not responsible for any damage you cause to your device in any way.
We will use the Intel Phone Flash tool, which can be used with a variety of Intel devices to flash firmware. You can use the Manufacturing Flash Tool instead if you'd like.
Here are the steps:
Obtain and install all drivers and software from the bottom of this post.
Download the factory image zip from the manufacturer's website; make sure it matches your device before flashing!. Extract the contents of the zip. Extract the contents of ifwi.zip into the same folder.
Plug in the device and open the Phone Flash tool. In the Phone Flash Tool window, click on "Custom Flash" on the left and pick "system (blankphone)" from the Type dropdown.
For each of the first four files, pick the one that matches:
CLVp_CSAX_FWR_DnX_20.3E.bin for FW DnX
IFWI_v64.25_CSAX_PROD.bin for IFWI
CLVp_CSAX_OS_DnX_20.3E.bin for OS DnX
fastboot.img for OS Image (this doesn't seem right, but it worked for me)
Once the four images are in place, click "Register flash file". At this point, your device should be displayed in the white rectangle on the page and the start flash button should now be clickable. Press the button, and flashing will commence. If you see "Windriver Error: 0x20000015, Timeout expired" in the console, try rebooting the device and flashing before the USB logo comes up (the device will appear in the Flash Tool before the logo comes up).
After a few seconds, you should see the Intel splash screen and you will be taken to droidboot. From there, it should be fairly easy to recover the device.
{
"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"
}
If you encounter any issues or corrections, please respond to this thread and let me know. Also, I was getting tons of driver errors (Windriver Error: 0x20000015, Timeout expired) the second time I tried to do this. The trick seems to be pressing the flash button before the USB logo appears.
I discovered most of this information from these two resources:
https://www.youtube.com/watch?v=jh89aiepcjQ
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
REQUIRED DRIVERS AND SOFTWARE
iSocUSB Driver
Intel USB Driver for Android Devices
Intel Phone Flash Tool

Hey @korockinout13!
1st of all, thanks for this, I have hard bricked my ME70cx and I needed a solution...
Unfortunately it is not working... I have followed your instructions but I keep getting the error "Windriver Error: 0x20000015, Timeout expired"
I have reinstalled the drivers (iSOC and Intel USB) but nothing changes, the same error keeps appearing.
You say "The trick seems to be pressing the flash button before the USB logo appears." BUT the start flash button is only clickable AFTER the USB logo appears
Any help shall be appreciated

Premie said:
Hey korockinout13!
1st of all, thanks for this, I have hard bricked my ME70cx and I needed a solution...
Unfortunately it is not working... I have followed your instructions but I keep getting the error "Windriver Error: 0x20000015, Timeout expired"
I have reinstalled the drivers (iSOC and Intel USB) but nothing changes, the same error keeps appearing.
You say "The trick seems to be pressing the flash button before the USB logo appears." BUT the start flash button is only clickable AFTER the USB logo appears
Any help shall be appreciated
Click to expand...
Click to collapse
I literally faught that error for a whole day. I tried 5 different computers, all had that issue. Usually my tablet would connect and disconnect once before the logo came up. Within that brief window, I was able to start the flash and it worked. I'm pretty sure that's what did it. If you aren't seeing this, turn up your PC's volume and listen for the USB sounds.
This whole thing is pretty annoying, but when it works, it works.

Thanks
I shall keep going at it until it works or I find another solution.

PLEASE help me!
korockinout13 said:
This guide will help you unbrick your hardbricked MeMo pad or possibly other device. For the purpose of this guide, hardbricked will refer to a device's software being damaged to the point where standard procedures and utilities (adb, fastboot, recovery, etc.) will not be able to make the device functional again. In order to be hardbricked, you essentially need to erase or damage the bootloader. Without the bootloader, you can't use fastboot or recovery since all of those things require the bootloader. This guide addresses that situation (your device should be displaying nothing but the USB logo, as seen in the attachment). If you have a working bootloader and can run fastboot commands, THIS GUIDE IS NOT FOR YOU and will only possibly make things worse.
This guide is directed towards the ME170CX, which is also apparently called the ME70C or KO1A; however, the same process should work for other MeMo Pad devices and even other Intel devices. I cannot provide much help for other devices, so try at your own risk.
Do not follow this guide unless it is your last hope or you know what you are doing. I am not responsible for any damage you cause to your device in any way.
We will use the Intel Phone Flash tool, which can be used with a variety of Intel devices to flash firmware. You can use the Manufacturing Flash Tool instead if you'd like.
Here are the steps:
Obtain and install all drivers and software from the bottom of this post.
Download the factory image zip from the manufacturer's website; make sure it matches your device before flashing!. Extract the contents of the zip. Extract the contents of ifwi.zip into the same folder.
Plug in the device and open the Phone Flash tool. In the Phone Flash Tool window, click on "Custom Flash" on the left and pick "system (blankphone)" from the Type dropdown.
For each of the first four files, pick the one that matches:
CLVp_CSAX_FWR_DnX_20.3E.bin for FW DnX
IFWI_v64.25_CSAX_PROD.bin for IFWI
CLVp_CSAX_OS_DnX_20.3E.bin for OS DnX
fastboot.img for OS Image (this doesn't seem right, but it worked for me)
Once the four images are in place, click "Register flash file". At this point, your device should be displayed in the white rectangle on the page and the start flash button should now be clickable. Press the button, and flashing will commence. If you see "Windriver Error: 0x20000015, Timeout expired" in the console, try rebooting the device and flashing before the USB logo comes up (the device will appear in the Flash Tool before the logo comes up).
After a few seconds, you should see the Intel splash screen and you will be taken to droidboot. From there, it should be fairly easy to recover the device.
If you encounter any issues or corrections, please respond to this thread and let me know. Also, I was getting tons of driver errors (Windriver Error: 0x20000015, Timeout expired) the second time I tried to do this. The trick seems to be pressing the flash button before the USB logo appears.
I discovered most of this information from these two resources:
https://www.youtube.com/watch?v=jh89aiepcjQ
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
REQUIRED DRIVERS AND SOFTWARE
iSocUSB Driver
Intel USB Driver for Android Devices
Intel Phone Flash Tool
Click to expand...
Click to collapse
Hello,
My device has a screwed up boot partition, but not the bootloader. My question is, how do I get this to flash without going into the USB mode?

Nandr0idC0nsumer said:
Hello,
My device has a screwed up boot partition, but not the bootloader. My question is, how do I get this to flash without going into the USB mode?
Click to expand...
Click to collapse
If you have a working boot loader, you don't need to do this.

korockinout13 said:
If you have a working boot loader, you don't need to do this.
Click to expand...
Click to collapse
Then how do I unbrick my device? I need to flash a new boot partition.
Some background: I installed the Lollipop update, then flashed the kitkat boot and fastboot IMG files (your average stupid Ryan). Can't get into fastboot anymore

Nandr0idC0nsumer said:
Then how do I unbrick my device? I need to flash a new boot partition.
Some background: I installed the Lollipop update, then flashed the kitkat boot and fastboot IMG files (your average stupid Ryan). Can't get into fastboot anymore
Click to expand...
Click to collapse
What happens instead of fastboot mode?

korockinout13 said:
What happens instead of fastboot mode?
Click to expand...
Click to collapse
"Fastboot Starting...
Fastboot Starting#1...
Fastboot Starting#2...
Fastboot Starting#3..."
Hangs there until rebooting after about 2 minutes."

Nandr0idC0nsumer said:
"Fastboot Starting...
Fastboot Starting#1...
Fastboot Starting#2...
Fastboot Starting#3..."
Hangs there until rebooting after about 2 minutes."
Click to expand...
Click to collapse
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.

korockinout13 said:
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.
Click to expand...
Click to collapse
Only thing I can think of is using "adb sideload" and making a ZIP to flash lollipop boot.img and droidboot.img
---------- Post added at 05:49 PM ---------- Previous post was at 05:28 PM ----------
korockinout13 said:
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.
Click to expand...
Click to collapse
Any other thoughts on what I could try? Leaving to eat in about an hour, and if this ain't fixed by then, I'll probably bring this to bestbuy as well

Nandr0idC0nsumer said:
Only thing I can think of is using "adb sideload" and making a ZIP to flash lollipop boot.img and droidboot.img
---------- Post added at 05:49 PM ---------- Previous post was at 05:28 PM ----------
Any other thoughts on what I could try? Leaving to eat in about an hour, and if this ain't fixed by then, I'll probably bring this to bestbuy as well
Click to expand...
Click to collapse
You have adb? That's not possible unless you are getting past the boot loader.

korockinout13 said:
You have adb? That's not possible unless you are getting past the boot loader.
Click to expand...
Click to collapse
Booting normally results in an "error" screen. randomly spamming vol up+vol down+power (SPAM!) brings up recovery, then do "apply update from adb." it puts it in a special adb where you can only use adb sideload

Nandr0idC0nsumer said:
Booting normally results in an "error" screen. randomly spamming vol up+vol down+power (SPAM!) brings up recovery, then do "apply update from adb." it puts it in a special adb where you can only use adb sideload
Click to expand...
Click to collapse
Hm... seems like you should be able to work with that if you have something flashable.

korockinout13 said:
Hm... seems like you should be able to work with that if you have something flashable.
Click to expand...
Click to collapse
Returned the tablet at Best Buy to get "fixed" (come on bestbuy, I know you mean replaced.) Thanks for your help

Repair
Hi,
I think i can help you out because i worked with the intel tool for weeks now to find a solution to root the me581cl.
Go to my thread and download a newer version of intelPhone tool.
http://forum.xda-developers.com/general/help/root-downgrade-asus-me581cl-t3075678
If you crashed your tab totaly, you must put the 4 OS IFWI,dnx files like in the first post and then also boot.img, fastboot.img, recovery.img.
Uncheck only the ifwi folder, but select it before. So its possible to check blank phone and on demand flash.
Then click start flash and the files get loadet up. Now push vol+ and vol- togehter and plug in the device.
(device must be off before you plug it in. If not, press 10 sec the power button.)
The reest you can read in my thread. A downgrade from Android 5 to 4.4 is also possible.
Good luck

Guys, my ME176CX is shafted after completing the L update, it boots to the android with the red exclamation box...i can get past this by using the volume + & power and arrive in the recovery. from there I have tried the wipe cache/wipe userdata (doesn't help) also i tried to adb sideload one of the roms in the collection of roms thread. no good. ideas??

Any solution?
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:
"FastBoot Starting...
FastBoot Starting...#1
FastBoot Starting...#2
FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.
Man I'm living in Venezuela a bad country to get damaged any gadget everything is 5 times expensive who your country and without any help in our soil by ASUS.

is this solution applicable to non-intel memopad? (e.g. me172V)

playinghier said:
is this solution applicable to non-intel memopad? (e.g. me172V)
Click to expand...
Click to collapse
No, this is very specific to the Intel chipset.

[FIX][Noob Friendly] No recovery, No download mode, No booting android, qhsusb_bulk?

No recovery, No download mode, No booting android, No fastboot? - In this case you are right here!
You are in the following situation:
If you power on your device, it goes to the LG logo and becomes black with running backlight quickly.
You have no access to the recovery mode.
You can't enter download mode.
There is no way to boot into the android system.
Usually your device is shown as qhsusb_bulk in Windows device manager.
Sometimes Windows recognizes about 13 partitions.
What you will need:
A working linux distribution (no way around that, but don't be afraid, e.g. slax)
If you want to run Linux in a Virtual Machine (no installation), preferably the VMWare Player (only for 64bit OSes) or an older Version of VMWare Player that supports 32bit.
A windows machine
A kdz for your device: 1, 2 or 3
The kdz extractor for WINDOWS!
Your broken G2
A micro USB cable
A little introduction:
We saw it a few times in the past months that people did weird things with their phone and didn't have anything more than a bootloader. This means no access to recovery nor download mode nor a booting android system. The last case was @petrasl27 (Thanks for the screenshots btw. ;D ). @bender_007 and @Art Vanderlay did an awesome job and helped petrasl27 to recover his phone within one hour. So thanks to those two! For those who want to read the original discussion, read a few pages here!
This thread here is similar to this one here, but I would say quite a bit easier to understand.
Disclaimer: I am not responsible for your phone. I did everything with my best knowledge, but I can't guarantee that your phone is working afterwards and every single command is written correctly. But I hope so, and it should ofc. If you have any issues, feel free to ask for help. We are kind, no worries. If you find mistakes, hit me up and I will correct them ASAP.
Let's start!
1) Install Linux
The easiest way is just do download the VMWare Player, installing, running it and using the .iso you downloaded before (pick other 3.x Linux Kernel if you downloaded slax). If you are unsure how to get Linux running, google it or ask here. Make sure, the usb port which you are going to use is linked through to the virtual machine.
You can also make the iso bootable and run the Linux as live system.
2) Extract the kdz
Switch to Windows, open the kdz extractor. Tick everything in the upper window, and click on extract kdz. Then open the .dz which just was created in the working directory of the kdz extractor. Tick "aboot_xxxxxx.bin", "boot_xxxxxx.bin" and "laf_xxxxxx.bin" in the lower window and hit extract dz. Then move the .bin files to your Linux desktop by using an USB stick, online storage or something like this.
Rename the files to "aboot.img", "boot.img" and "laf.img".
3) Preparing everything
Remove all your USB devices (except your G2 and your Keyboard & Mouse) from your computer, open a Terminal and type
Code:
ls /dev/sd*
The sda, sda1, sda2 etc. should be the partitions on your computer. But there should be a few others with sdb, sdb1, sdb2, etc. but no more. The sdb ones should be numbered from 1 to 36. This is your G2. Keep in mind how the three letters are (sdb, sdx, what so ever). (Make sure you run this as Super User, if you don't use slax!)
Then type
Code:
gdisk -l /dev/<insert the three letters you found out with the command above>
example:
Code:
gdisk -l /dev/sdb
It should now look something like 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"
}
Keep the numbers of the marked partitions in mind. In this case aboot=5, boot=7, laf=23.
4) Preparing everything
If you've managed it to get here, you are almost done. It's almost time for the final step now:
Open a terminal and type
Code:
cd Desktop
ls
You should now see the filenames of the 3 files (aboot.img, boot.img, laf.img) on your desktop in the terminal. If you do not, you either didn't type "cd Desktop" properly (The linux terminal is case sensitive!!!) or you haven't copied the files to the desktop.
5) Flashing the stuff
Code:
dd if=aboot.img of=/dev/<the 3 letters of your G2><the number of your aboot partition>
dd if=boot.img of=/dev/<the 3 letters of your G2><the number of your boot partition>
dd if=laf.img of=/dev/<the 3 letters of your G2><the number of your laf partition>
example (in my case):
Code:
dd if=aboot.img of=/dev/sdb5
dd if=boot.img of=/dev/sdb7
dd if=laf.img of=/dev/sdb23
6) Go back to stock using the kdz method
Now just follow this thread to get back to stock.

Reserved - just in case^^

bricked my lg g2 d802..plz help
i'm from india .
i had installed lollipop 5.0.2 v30b via kdz flash method on my lg g2 d802 (indian version ) .
since then i had issues wirth my bluetooth and wifi.both were not working .
in my attempts to flash back to stock 4.2.2 , i came across ur thread and i flashed "D802_PATCH_RETURN_KK_droidth" via philz latest cwm recovery ,
but after that everything went mayhem ..
i got boot error message repeatedly and was unable to enter even recovery .
after several tries i somehow managed to enter recovery mode , but stil phone wont go past it.
I GUESS I ACCIDENTALLY FLASHED A KERNEL FOR MY OLD GALAXY NOTE(due to confusion between the saved files in the download folder ) , On my g2 too....but not sure...
after i restatred the moB , it wont turn on .
battery was 85 % ..
i'm not a newbie to flashing roms and have done aTLEAST >50 times with my lg g2 and galaxy note 2 and previously sgs2 , but this is the first time i got into a hard brick mode.
when i took the phone to servie center, they told the mob is just out of warranty and so wont get any warrany related help.
they told that the EFS HAS BEEN CONVERTED TO READ ONLY mode somehow due to improper flahing and also added that the EFS IS BEING SHOWN AS 16 PARTITION S.
they tried to repair the boot sector and recovery using OCTOPLUS TOOL BOX , but failed and told me that the latest models like G2 is not supported as if now in their TOOL BOX.
THE ONE suggestion given by them was change of PCB which is almost same as a new mob.
I'M STUCK WITHOUT MY FAV MOB G2 .......PLS HELP ME OUT SOMEHOW AND HELP ME OUT...

hbk4 said:
i'm from india .
i had installed lollipop 5.0.2 v30b via kdz flash method on my lg g2 d802 (indian version ) .
since then i had issues wirth my bluetooth and wifi.both were not working .
in my attempts to flash back to stock 4.2.2 , i came across ur thread and i flashed "D802_PATCH_RETURN_KK_droidth" via philz latest cwm recovery ,
but after that everything went mayhem ..
i got boot error message repeatedly and was unable to enter even recovery .
after several tries i somehow managed to enter recovery mode , but stil phone wont go past it.
I GUESS I ACCIDENTALLY FLASHED A KERNEL FOR MY OLD GALAXY NOTE(due to confusion between the saved files in the download folder ) , On my g2 too....but not sure...
after i restatred the moB , it wont turn on .
battery was 85 % ..
i'm not a newbie to flashing roms and have done aTLEAST >50 times with my lg g2 and galaxy note 2 and previously sgs2 , but this is the first time i got into a hard brick mode.
when i took the phone to servie center, they told the mob is just out of warranty and so wont get any warrany related help.
they told that the EFS HAS BEEN CONVERTED TO READ ONLY mode somehow due to improper flahing and also added that the EFS IS BEING SHOWN AS 16 PARTITION S.
they tried to repair the boot sector and recovery using OCTOPLUS TOOL BOX , but failed and told me that the latest models like G2 is not supported as if now in their TOOL BOX.
THE ONE suggestion given by them was change of PCB which is almost same as a new mob.
I'M STUCK WITHOUT MY FAV MOB G2 .......PLS HELP ME OUT SOMEHOW AND HELP ME OUT...
Click to expand...
Click to collapse
Did you follow the guide? Just do this. If things are unclear, just ask and someone will help you.

I want to download the first linux programme but it is just for windows 64bits. I'm running windows 7 OS 32Bits..

Soufiansky said:
I want to download the first linux programme but it is just for windows 64bits. I'm running windows 7 OS 32Bits..
Click to expand...
Click to collapse
Which one are you refering to?
NVM, adjusted the OP. Either use VirtualBox or download an older version of VMPlayer (which supports 32bit obviously) by picking Version 6.0 as major version.

Sunandroid said:
Which one are you refering to?
Click to expand...
Click to collapse
VMWAREplayer

Soufiansky said:
VMWAREplayer
Click to expand...
Click to collapse
read my post above (edited it).

Sunandroid said:
read my post above (edited it).
Click to expand...
Click to collapse
I can see that it will install Linux OS on my computer , which mean i will have 2OS . Is this safe ? I mean on every boot i should choose the OS to use or what ? Because i never used Linux as i don't need it , but this time it's a must.
Thanks.

Soufiansky said:
I can see that it will install Linux OS on my computer , which mean i will have 2OS . Is this safe ? I mean on every boot i should choose the OS to use or what ? Because i never used Linux as i don't need it , but this time it's a must.
Thanks.
Click to expand...
Click to collapse
No, if you are running it as a virtual machine (in VMWare Player or VirtualBox or whatever), it's like a programm you can start on your windows system. After you've unbricked your device, you can easily uninstall the VMWare Player and there is nothing from Linux anymore.

Sunandroid said:
No, if you are running it as a virtual machine (in VMWare Player or VirtualBox or whatever), it's like a programm you can start on your windows system. After you've unbricked your device, you can easily uninstall the VMWare Player and there is nothing from Linux anymore.
Click to expand...
Click to collapse
I get it , like a virtual OS in the main OS. Installing , will report back.
---------- Post added at 09:40 PM ---------- Previous post was at 09:18 PM ----------
@sunandroid My phone is booting at LG logo and download mode is working , so i see this method isn't for me BUT .kdz method doesn't work , firmware stuck at 24% or 49% , and one LP firmware worked but it just keep rebooting after the process.
Factory reset doesn't work , the blue line down isn't there and it reboot again and again.. Is there a way to boot in fastboot using buttons combinations ? Tried multiple things but didn't work.

Soufiansky said:
I get it , like a virtual OS in the main OS. Installing , will report back.
---------- Post added at 09:40 PM ---------- Previous post was at 09:18 PM ----------
@sunandroid My phone is booting at LG logo and download mode is working , so i see this method isn't for me BUT .kdz method doesn't work , firmware stuck at 24% or 49% , and one LP firmware worked but it just keep rebooting after the process.
Factory reset doesn't work , the blue line down isn't there and it reboot again and again.. Is there a way to boot in fastboot using buttons combinations ? Tried multiple things but didn't work.
Click to expand...
Click to collapse
What button combo do you use to factory reset?

Sunandroid said:
What button combo do you use to factory reset?
Click to expand...
Click to collapse
Volume down + power button , just after LG logo i press them again , then yes , yes , it shows the green android but there is no factory reset ( the blue line isn't there if you know what i'm talking about)
Tried also the same thing then power 3 times , same also..

problem soleved.....finally
Sunandroid said:
Did you follow the guide? Just do this. If things are unclear, just ask and someone will help you.
Click to expand...
Click to collapse
finally , i solved the problem..
with the help of soombons (droidth) , i was able to fix my d802 in just 2 minutes. - USING SRK 2.0 TOOL ...
sharing the link for people with same problems
---
[LG-G2] Unbrick (qhsusb_bulk) by SRK Tool 2.0 (D8…: https://youtu.be/ERZvlJIC9dE
tonnes of thanks to SOOMBONS for the prompt help !..
CHEERS !!!

Can anyone help me out on a D801?
The phone goes into bootloop... the LG logo appears for a few seconds, disappears, then reappears. I'm not able to go into download mode, no fastboot, and also no recovery. When I do the volume down + power button combo I can get to the factory reset screen but selecting Yes both times just sends me back to the same LG logo bootloop.
What is weird is that my phone use to display as QHSUSB_BULK and it would bring up a bunch of drives... but now that doesn't happen and my phone isnt even showing in device manager anymore. Also, my phone used to show the first "Download Mode" splash screen when I held the volume up button while plugging it into my comp but it just does the same bootloop. No more errors... just bootloops...
Do I have to short the capacitors like in this thread: http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
or this one: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404

Soufiansky said:
Volume down + power button , just after LG logo i press them again , then yes , yes , it shows the green android but there is no factory reset ( the blue line isn't there if you know what i'm talking about)
Tried also the same thing then power 3 times , same also..
Click to expand...
Click to collapse
Weird. Did you use this method to go back to stock: http://forum.xda-developers.com/showthread.php?t=2432476
This worked fine for me every time I used it. Try to flash a KK ROM again, but do a CSE flash.
chaitea said:
Can anyone help me out on a D801?
The phone goes into bootloop... the LG logo appears for a few seconds, disappears, then reappears. I'm not able to go into download mode, no fastboot, and also no recovery. When I do the volume down + power button combo I can get to the factory reset screen but selecting Yes both times just sends me back to the same LG logo bootloop.
What is weird is that my phone use to display as QHSUSB_BULK and it would bring up a bunch of drives... but now that doesn't happen and my phone isnt even showing in device manager anymore. Also, my phone used to show the first "Download Mode" splash screen when I held the volume up button while plugging it into my comp but it just does the same bootloop. No more errors... just bootloops...
Do I have to short the capacitors like in this thread: http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
or this one: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
Yeah I guess you have to do as you mentioned. Only thing you could try before doing so:
Hold down the power button for 20 secs. Then wait a few secs and try to get into download mode. Maybe the device shows up as qhusb_bulk again.

Please help, Im stuck!!!
Since yesterday my phone is stuck, only LG Logo, no download mode, no factory mode, no recovery, no nothing but the lg logo.
I tried thw mentioned tool and what the OP posted here, but in both methods I get stuck:
The LG G2 is not recognized as as drive anymore, the one thats supposed to have many partitions, sdb, sdx, what so ever, numbered from 1 to 36.
Without this I cant continue.
Any help? Using D802 international version
Thanks

Batou069 said:
Please help, Im stuck!!!
Since yesterday my phone is stuck, only LG Logo, no download mode, no factory mode, no recovery, no nothing but the lg logo.
I tried thw mentioned tool and what the OP posted here, but in both methods I get stuck:
The LG G2 is not recognized as as drive anymore, the one thats supposed to have many partitions, sdb, sdx, what so ever, numbered from 1 to 36.
Without this I cant continue.
Any help? Using D802 international version
Thanks
Click to expand...
Click to collapse
Do you have a windows machine?
If yes, try this http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2 and see if it is displayed as qhusb_bulk in device manager after you've done this.

Sunandroid said:
Do you have a windows machine?
If yes, try this http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2 and see if it is displayed as qhusb_bulk in device manager after you've done this.
Click to expand...
Click to collapse
Hi, thanks for the quick reply
I have a windows machine, yes, but no idea how to open my device. I hope this wont be necessary...
What happened last: After using a very laggy rom for over a week, I decided to flash PA. I wiped everything except the format, so data/media is kept... i guess that the flash didnt went well, and after reboot im stuck at LG logo... manually putting it into recovery isnt working anymore.
When I connect the phone to the pc only the "LGE Android MTP Device" is identified but with a fail (yellow triangle and exclemation mark in device manager).
SRK Tool -> Disk Managment Tool shows only Disk0 which is c:
In the virtual machine, under VM> removable devices I can see the LGE Android, and when I connect it (disconnect from host) nothing changes, no sdx, sdb or anything like this, only sda (C
I installed the LG Drivers but it wont help. Here I am, with a bricked phone
What do you think?
Thanks

Batou069 said:
Hi, thanks for the quick reply
I have a windows machine, yes, but no idea how to open my device. I hope this wont be necessary...
What happened last: After using a very laggy rom for over a week, I decided to flash PA. I wiped everything except the format, so data/media is kept... i guess that the flash didnt went well, and after reboot im stuck at LG logo... manually putting it into recovery isnt working anymore.
When I connect the phone to the pc only the "LGE Android MTP Device" is identified but with a fail (yellow triangle and exclemation mark in device manager).
SRK Tool -> Disk Managment Tool shows only Disk0 which is c:
In the virtual machine, under VM> removable devices I can see the LGE Android, and when I connect it (disconnect from host) nothing changes, no sdx, sdb or anything like this, only sda (C
I installed the LG Drivers but it wont help. Here I am, with a bricked phone
What do you think?
Thanks
Click to expand...
Click to collapse
Are you sure you can't get into download mode? (hold down the power button for 20 seconds (not shorter!), then holding the vol+ button and connect the phone to a computer)?
I could imagine that you can enter the recovery after holding down the powerbutton for 20 seconds with the button combo. I think so, because the kernel must be working somehow since it still manages to get shown properly on windows.
If none of the options above is working, the pin shortage is probably the easiest way to get into qhsusb_bulk and start freshly (following this thread).

Lenovo Yoga 2 1050F Bricked

Hello,
A friend give to me his Yoga2 1050F Tab, because it's bricked...
"After a kind of upgrade he said"
So, here's the situation,
Tab is really bricked, stuck on Lenovo Android Screen.
I've tried to factory restore, no success.
I've searched all the web after factory image to flash, I've found 3 of them... But nothing works !!
The 1st one, the only we can still found here, is a factory image from 2015. And the result is, no more lenovo android screen, i'm stuck on a kind of Bios (?) And can't do anything more...
2nd one, (YT2-1050F_S100196_151123_ROW-fastboot), best result, back to an android boot, but stuck on recovery screen, without any possibility to boot...
3rd one (YT2-1050F_S0198_150422_ROW) impossible to flash, it's always failed at "flash easyimage.zip" step.
Other thing, I don't know what xml file I need to use (flash, flash-blankphone, flash-factory ... )
Here, i'm totally lost. Tab is stuck, And I've no idea what can I do next...
Maybe here anyone can help me ?
Many Many thanks !

Hello,
It seem's i got the same problem.
The tablet downloaded an upgrade by it's own.
The tablet rebooted alone and the try to apply the upgrade but never success.
Now i'm booting on a BIOS type screen.
"VALLEYVIEW C0 PLATFORM"
I can access to different options but the tablet is not reconized by my PC anymore.
I can flash anything on it.
If someone have a solution, it would be great !

Hey @NeedaVirus,
Sorry to hear that the device is bricked. Just this past weekend, I've been sifting through all my old resources because a recent OTA (Yep, a 2020 update!) left both me and my partner's 1050F devices in an unbootable state. You can see we're not alone by checking out the thread on the Lenovo forums (https://forums.lenovo.com/t5/Androi...Tablet-2-1050f-system-update-2020/m-p/5007166). Unfortunately a large number of the very helpful resources on xda seem to have been redacted/removed over the past few years, which leaves a few people scratching their heads (I was for a while too).
Basically, the way I've always done this on the 1050F (and what worked yesterday again), is as follows:
1. Install the "IntelAndroidDrvSetup1.10.0". Google will find this easy enough.
2. Install the flash tool. Nowadays, "Intel Platform Flash Tool Lite 5.8.4.0" (might also be called Phone Flash Tool Lite v5.8.4.0 and again google will find this for you) seems to come bundled with all required drivers, so it's a simple process to install.
3. Plug the device in and put it in DNX mode. This mode is achieved by holding vol up + vol down and pressing the power button until the device vibrates. When you feel the buzz, let go of power but hold the other two until you see a "Fastboot starting..." message on a black screen. This is DNX mode.
4. Restore stock KitKat bios using the "restore-kitkat-bios-830-1050-v2" tool. This one might take a little finding and I'm not sure if sharing it here is acceptable any more. Provided the device is plugged in and in DNX mode (and you have the Intel Platform Flash Tool closed too), it's just a matter of running the bios restore tool and following the prompts. Make sure the flash tool is running on your local drive (usually C).
5. Once the bios is pushed, we need to restore the stock KitKat ROM using the platform flash tool.
First we need to set up the Platform Flash Tool, so open that and select "File" -> "Options". Under "Flash options" tick the "Force fastboot sparsing" option and select "500MB" for the size.
6. Now, we want to use the "YT2-1050F_S0198_150422_ROW" image and you'll need to extract it first. It sounds like you already have the right archive file for this, which is good because I'm not sure if a copy still exists here still.
In the Platform Flash Tool, hit "Browse" and the file we're looking for is "target_bin\flash.xml". Select that. (Side note: I suspect that if your device has been updated to Lollipop in the past, you wouldn't have had any luck flashing this rom without rolling the bios back first).
7. Put the device into DNX mode again, and the Platform Flash Tool should see it (a "Baytrail" device is listed).
Now it's just a matter of starting the flash process by clicking the button.
8. Once the device is flashed, you'll need to reboot it (via the device) but wait for the flash process to report 100% first. Hitting the device power button is the way to confirm this reboot btw. It might take a few mins to get into Android here. This is normal.
9. Now, the device will boot into stock KitKat. We need to set the region though:
Open contacts, add new contact (only if you have none, we just need one).
Now, using the contact search, enter ####6020# and you'll be prompted to select your region. The device will reboot and you'll need to set a few things up again.
10. Run all the OTA updates to get right up to date. Just do this via android itself.
Optional: Do any other crazy bootloader unlocks, roots as desired. A lot of the original resources have been removed for these processes, but where there's a will, there's a way.
I'm sure there are other shortcuts to this process too. I think tontonfraguer was able to just flash a newer rom directly to resolve his bootloop, judging by his forum post over on the Lenovo thread. This is just the process I use, any feedback/improvements are most welcome!
Hopefully it helps someone being hit by the recent bootloops.
Cheers

OMG ! OMG ! OMG !!!
Man, you're THE MAN !!!
I've followed all your explanations, and... IT WORKS !!!
Yes it was hard to find again the "restore-kitkat-bios-830-1050-v2" (China links to Russian Servers...) But I've finded it !
Many many MAAAAANYYYY Thanks my friend !!!
Thanks a lot !
And thanks a lot to All XDA DEV !

dallivadr said:
Hey @NeedaVirus,
Sorry to hear that the device is bricked. Just this past weekend, I've been sifting through all my old resources because a recent OTA (Yep, a 2020 update!) left both me and my partner's 1050F devices in an unbootable state. You can see we're not alone by checking out the thread on the Lenovo forums (https://forums.lenovo.com/t5/Androi...Tablet-2-1050f-system-update-2020/m-p/5007166). Unfortunately a large number of the very helpful resources on xda seem to have been redacted/removed over the past few years, which leaves a few people scratching their heads (I was for a while too).
Basically, the way I've always done this on the 1050F (and what worked yesterday again), is as follows:
1. Install the "IntelAndroidDrvSetup1.10.0". Google will find this easy enough.
2. Install the flash tool. Nowadays, "Intel Platform Flash Tool Lite 5.8.4.0" (might also be called Phone Flash Tool Lite v5.8.4.0 and again google will find this for you) seems to come bundled with all required drivers, so it's a simple process to install.
3. Plug the device in and put it in DNX mode. This mode is achieved by holding vol up + vol down and pressing the power button until the device vibrates. When you feel the buzz, let go of power but hold the other two until you see a "Fastboot starting..." message on a black screen. This is DNX mode.
4. Restore stock KitKat bios using the "restore-kitkat-bios-830-1050-v2" tool. This one might take a little finding and I'm not sure if sharing it here is acceptable any more. Provided the device is plugged in and in DNX mode (and you have the Intel Platform Flash Tool closed too), it's just a matter of running the bios restore tool and following the prompts.
5. Once the bios is pushed, we need to restore the stock KitKat ROM using the platform flash tool.
First we need to set up the Platform Flash Tool, so open that and select "File" -> "Options". Under "Flash options" tick the "Force fastboot sparsing" option and select "500MB" for the size.
6. Now, we want to use the "YT2-1050F_S0198_150422_ROW" image and you'll need to extract it first. It sounds like you already have the right archive file for this, which is good because I'm not sure if a copy still exists here still.
In the Platform Flash Tool, hit "Browse" and the file we're looking for is "target_bin\flash.xml". Select that. (Side note: I suspect that if your device has been updated to Lollipop in the past, you wouldn't have had any luck flashing this rom without rolling the bios back first).
7. Put the device into DNX mode again, and the Platform Flash Tool should see it (a "Baytrail" device is listed).
Now it's just a matter of starting the flash process by clicking the button.
8. Once the device is flashed, you'll need to reboot it (via the device) but wait for the flash process to report 100% first. Hitting the device power button is the way to confirm this reboot btw. It might take a few mins to get into Android here. This is normal.
9. Now, the device will boot into stock KitKat. We need to set the region though:
Open contacts, add new contact (only if you have none, we just need one).
Now, using the contact search, enter ####6020# and you'll be prompted to select your region. The device will reboot and you'll need to set a few things up again.
10. Run all the OTA updates to get right up to date. Just do this via android itself.
Optional: Do any other crazy bootloader unlocks, roots as desired. A lot of the original resources have been removed for these processes, but where there's a will, there's a way.
I'm sure there are other shortcuts to this process too. I think tontonfraguer was able to just flash a newer rom directly to resolve his bootloop, judging by his forum post over on the Lenovo thread. This is just the process I use, any feedback/improvements are most welcome!
Hopefully it helps someone being hit by the recent bootloops.
Cheers
Click to expand...
Click to collapse
Cant find anywhere to download restore-kitkat-bios-830-1050-v2 file. Any chance you could pm a Google drive link?
Thanks

Sansiro2 said:
Cant find anywhere to download restore-kitkat-bios-830-1050-v2 file. Any chance you could pm a Google drive link?
Thanks
Click to expand...
Click to collapse
Managed to sort it out - many thanks for your guide. One thing to note is the Kitkit restore file needs to be in the root of the C drive and also the file for the flash in my case was the flash.xml file

Glad the post helped you guys out and that you were able to get back up and running. If the post was helpful, why not click the 'thank' button under my post

Hi Hi Hiiii
For those who need the famous "restore-kitkat-bios-830-1050-v2"
HERE'S THE LINK (Personal re-upload) : https://drive.google.com/file/d/13vV6fpNAbWWZUk9_fzmJpMAMax2tlyyB/view?usp=sharing
Be aware that you probably need to do this if your OTA updates Fails :
If system update fails do the following:
1. Flash stock firmware
2. Optionally you can wipe user data (I never did that) from DROIDBOOT
3. Go to contacts manager. Create some dummy contact if list is empty.
4. Go to Search / Find Contacts and enter ####6020#. It will ask you to select country code (first two latin letters, ignore Chinese).
5. Select what you want, then reboot.
6. Go to System Update
7. Install OTA update
(Original Post here : https://forum.xda-developers.com/showpost.php?p=57846051&postcount=233)
Enjoy Friends

NeedaVirus said:
Hi Hi Hiiii
For those who need the famous "restore-kitkat-bios-830-1050-v2"
HERE'S THE LINK (Personal re-upload) : https://drive.google.com/file/d/13vV6fpNAbWWZUk9_fzmJpMAMax2tlyyB/view?usp=sharing
Be aware that you probably need to do this if your OTA updates Fails :
If system update fails do the following:
1. Flash stock firmware
2. Optionally you can wipe user data (I never did that) from DROIDBOOT
3. Go to contacts manager. Create some dummy contact if list is empty.
4. Go to Search / Find Contacts and enter ####6020#. It will ask you to select country code (first two latin letters, ignore Chinese).
5. Select what you want, then reboot.
6. Go to System Update
7. Install OTA update
(Original Post here : https://forum.xda-developers.com/showpost.php?p=57846051&postcount=233)
Enjoy Friends
Click to expand...
Click to collapse
Thanks - when setting the country code if you get the 'ERROR : could not read factory ota patch from sd card,or the patch is not correct.' then you need to take the easyimage.zip from the extracted rom folder and copy it on the sdcard (on the root of it not in some folder) then try again (with at least 30% battery level).

Guys,
If someone wants to ROOT his tablet, I can write the procedure. (Many try for me before it really works...)
See ya !

hi everyone , i hope someone be able to help me with this , i also just got this tablet as one that does not even turn on , ive played with it a bit and managed to get some writings on the display, then i found this topic here and tried to follow as instructed, nothing happens, and the screen with fastboot starting goes off. any suggestion ?
thank you in advance.
{
"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"
}

THANK YOU!!
i have been battling with the TY2 1380f for a whole week with just a black screen. This helped as I was able to find the kit kat restore for the 1380 and following your guide, got things back to normal.
Life Saver!!!
dallivadr said:
Hey @NeedaVirus,
Sorry to hear that the device is bricked. Just this past weekend, I've been sifting through all my old resources because a recent OTA (Yep, a 2020 update!) left both me and my partner's 1050F devices in an unbootable state. You can see we're not alone by checking out the thread on the Lenovo forums (https://forums.lenovo.com/t5/Androi...Tablet-2-1050f-system-update-2020/m-p/5007166). Unfortunately a large number of the very helpful resources on xda seem to have been redacted/removed over the past few years, which leaves a few people scratching their heads (I was for a while too).
Basically, the way I've always done this on the 1050F (and what worked yesterday again), is as follows:
1. Install the "IntelAndroidDrvSetup1.10.0". Google will find this easy enough.
2. Install the flash tool. Nowadays, "Intel Platform Flash Tool Lite 5.8.4.0" (might also be called Phone Flash Tool Lite v5.8.4.0 and again google will find this for you) seems to come bundled with all required drivers, so it's a simple process to install.
3. Plug the device in and put it in DNX mode. This mode is achieved by holding vol up + vol down and pressing the power button until the device vibrates. When you feel the buzz, let go of power but hold the other two until you see a "Fastboot starting..." message on a black screen. This is DNX mode.
4. Restore stock KitKat bios using the "restore-kitkat-bios-830-1050-v2" tool. This one might take a little finding and I'm not sure if sharing it here is acceptable any more. Provided the device is plugged in and in DNX mode (and you have the Intel Platform Flash Tool closed too), it's just a matter of running the bios restore tool and following the prompts. Make sure the flash tool is running on your local drive (usually C).
5. Once the bios is pushed, we need to restore the stock KitKat ROM using the platform flash tool.
First we need to set up the Platform Flash Tool, so open that and select "File" -> "Options". Under "Flash options" tick the "Force fastboot sparsing" option and select "500MB" for the size.
6. Now, we want to use the "YT2-1050F_S0198_150422_ROW" image and you'll need to extract it first. It sounds like you already have the right archive file for this, which is good because I'm not sure if a copy still exists here still.
In the Platform Flash Tool, hit "Browse" and the file we're looking for is "target_bin\flash.xml". Select that. (Side note: I suspect that if your device has been updated to Lollipop in the past, you wouldn't have had any luck flashing this rom without rolling the bios back first).
7. Put the device into DNX mode again, and the Platform Flash Tool should see it (a "Baytrail" device is listed).
Now it's just a matter of starting the flash process by clicking the button.
8. Once the device is flashed, you'll need to reboot it (via the device) but wait for the flash process to report 100% first. Hitting the device power button is the way to confirm this reboot btw. It might take a few mins to get into Android here. This is normal.
9. Now, the device will boot into stock KitKat. We need to set the region though:
Open contacts, add new contact (only if you have none, we just need one).
Now, using the contact search, enter ####6020# and you'll be prompted to select your region. The device will reboot and you'll need to set a few things up again.
10. Run all the OTA updates to get right up to date. Just do this via android itself.
Optional: Do any other crazy bootloader unlocks, roots as desired. A lot of the original resources have been removed for these processes, but where there's a will, there's a way.
I'm sure there are other shortcuts to this process too. I think tontonfraguer was able to just flash a newer rom directly to resolve his bootloop, judging by his forum post over on the Lenovo thread. This is just the process I use, any feedback/improvements are most welcome!
Hopefully it helps someone being hit by the recent bootloops.
Cheers
Click to expand...
Click to collapse

hello

hoooman008 said:
hi everyone , i hope someone be able to help me with this , i also just got this tablet as one that does not even turn on , ive played with it a bit and managed to get some writings on the display, then i found this topic here and tried to follow as instructed, nothing happens, and the screen with fastboot starting goes off. any suggestion ?
thank you in advance.View attachment 5176433View attachment 5176431
Click to expand...
Click to collapse
any help would be greatly appreciated

hoooman008 said:
any help would be greatly appreciated
Click to expand...
Click to collapse
on your screen, attached, at device manager, i can see the driver for intel adb fastboot blabla is not correctly installed, try:
1. restarting windows while holding SHIFT button till it restarts
2. go through advanced restart option and select startup settings
3. when it reboots and offers to select in black-white options 1-8, select wit button F7 the "driver signature.." part
( you are now allowing to installing unsigned drivers )
4. wehn it reboots, INSTALL intel plattform flash tool.exe again and re-install everyting, this time u will see windows pop-ups in red notifiying you installing unsigned extra extra drama drivers, say yes to all of them
5. flash again, using above instructions, make sure to change intel plattform flash tool settings to force flash 500MB
6. go everyting that is instructed above - step by step - through and report, i had exact same problem and solved it remembering the driver-stuffs weirdness on windows, still not a problem at all, just anoying extra steps

NeedaVirus said:
Hello,
A friend give to me his Yoga2 1050F Tab, because it's bricked...
"After a kind of upgrade he said"
So, here's the situation,
Tab is really bricked, stuck on Lenovo Android Screen.
I've tried to factory restore, no success.
I've searched all the web after factory image to flash, I've found 3 of them... But nothing works !!
The 1st one, the only we can still found here, is a factory image from 2015. And the result is, no more lenovo android screen, i'm stuck on a kind of Bios (?) And can't do anything more...
2nd one, (YT2-1050F_S100196_151123_ROW-fastboot), best result, back to an android boot, but stuck on recovery screen, without any possibility to boot...
3rd one (YT2-1050F_S0198_150422_ROW) impossible to flash, it's always failed at "flash easyimage.zip" step.
Other thing, I don't know what xml file I need to use (flash, flash-blankphone, flash-factory ... )
Here, i'm totally lost. Tab is stuck, And I've no idea what can I do next...
Maybe here anyone can help me ?
Many Many thanks !
Click to expand...
Click to collapse
Download Lenovo's official "Rescue and Smart Assistant" it reflashes stock rom for you.