OK, first, I have searched the internet and XDA for help.
Currently, I'm stuck on The black screen with Google. It shows the unlocked Bootloader icon as well. Earlier today I was stuck in a boot with CM boot animation, but that's apparently gone now. I can fastboot, so I'm pretty sure it's recoverable. In TWRP, it says unable to mount /system, /data/ cache/ storage, basically everything. Using NRT i've flashed stock everything, which didn't work, so I tried flashing the kernel, which also didn't work, so I tried the bootloader and system, but they all result in the google splash screen. I am completely out of ideas.
Question: How do i fix it?
Edit: It stayed on the splash screen for at least 4 hours and it wasn't caused by anything I did. No ROM flashes, nothing. It was working then it wasn't.
a.child said:
OK, first, I have searched the internet and XDA for help.
Currently, I'm stuck on The black screen with Google. It shows the unlocked Bootloader icon as well. Earlier today I was stuck in a boot with CM boot animation, but that's apparently gone now. I can fastboot, so I'm pretty sure it's recoverable. In TWRP, it says unable to mount /system, /data/ cache/ storage, basically everything. Using NRT i've flashed stock everything, which didn't work, so I tried flashing the kernel, which also didn't work, so I tried the bootloader and system, but they all result in the google splash screen. I am completely out of ideas.
Question: How do i fix it?
Edit: It stayed on the splash screen for at least 4 hours and it wasn't caused by anything I did. No ROM flashes, nothing. It was working then it wasn't.
Click to expand...
Click to collapse
If you are using NRT, try to flash stock with soft-bricked/Bootloop option.
{
"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"
}
After restore, perform a wipe data/factory reset in stock recovery before booting to android.
Best of luck
joegestes said:
If you are using NRT, try to flash stock with soft-bricked/Bootloop option.
After restore, perform a wipe data/factory reset in stock recovery before booting to android.
Best of luck
Click to expand...
Click to collapse
Thanks for the help, you even edited a screenshot :') haha unfortunately, no luck. But some interesting stuff happens when I do the stock flash.
First time I tried (yesterday), I went through the instructions just how they're listed, I erased all user data and rebooted, still stuck. This time, though, I couldn't get it to boot the stock recovery. Tried pwr+Vol Up like the directions say, but it gets stuck on splash. Tried Pwr+Vol down and I could boot into TWRP which informed me that it was still unable to mount any partitions and that there was no OS installed.
Edit: Looked closer at the command prompt log from the flash and noticed it failed to write any of the images. Sending is OKAY but writing FAILED.
a.child said:
Thanks for the help, you even edited a screenshot :') haha unfortunately, no luck. But some interesting stuff happens when I do the stock flash.
First time I tried (yesterday), I went through the instructions just how they're listed, I erased all user data and rebooted, still stuck. This time, though, I couldn't get it to boot the stock recovery. Tried pwr+Vol Up like the directions say, but it gets stuck on splash. Tried Pwr+Vol down and I could boot into TWRP which informed me that it was still unable to mount any partitions and that there was no OS installed.
Edit: Looked closer at the command prompt log from the flash and noticed it failed to write any of the images. Sending is OKAY but writing FAILED.
Click to expand...
Click to collapse
Hmmm.
Its possible your cable is no good, but it could be something else like a driver issue or charging port failure.
Try using a known good, high quality data cable. Also try connecting to a different USB port on PC.
Just so I understand better.
What version of android did you attempt to flash?
Were you using NRT to flash when the flashing's failed?
Was Force Flash enabled in NRT? .......Try that.
Did you try flashing a different version of STOCK android?
Do you have Android ADB/fastboot installed on PC aside from the one in NRT?
If so, does fastboot detect your phone when running the command "fastboot devices" while in the bootloader?
Is ADB able to detect your phone when running the command "ADB devices" while in TWRP?
I'm at work now, but I'll try new cables and ports when I get home as well as the adb commands.
I was trying to flash 5.0.1 , and was running some CM12 nightly when it failed. To be clear, the ROM was working fine until it wasn't.
I was using NRT and I had force flash selected (recommended settings I think), but I'm not 100% sure post flash factory reset was checked but in the CMD log I did see it wipe and attempt to write userdata.
I have not tried a different version of stock.
I believe ADB is installed outside of NRT abd i have to manually set my path variable to C:/ADB (which screws up normal command prompt, but idk how to fix that) for NRT to work. I have a 2013 nexus 7 and used the same setup to flash PA a while back without any issues.
NRT doesn't detect my phone when displaying the splash screen, but idk about TWRP.
joegestes said:
Hmmm.
Its possible your cable is no good, but it could be something else like a driver issue or charging port failure.
Try using a known good, high quality data cable. Also try connecting to a different USB port on PC.
Just so I understand better.
What version of android did you attempt to flash?
Were you using NRT to flash when the flashing's failed?
Was Force Flash enabled in NRT? .......Try that.
Did you try flashing a different version of STOCK android?
Do you have Android ADB/fastboot installed on PC aside from the one in NRT?
If so, does fastboot detect your phone when running the command "fastboot devices" while in the bootloader?
Is ADB able to detect your phone when running the command "ADB devices" while in TWRP?
Click to expand...
Click to collapse
So the computer does not recognize a fastboot device while in TWRP, but does in the BL.
I attempted to flash 5.0 with the settings mentioned, no luck
a.child said:
So the computer does not recognize a fastboot device while in TWRP, but does in the BL.
I attempted to flash 5.0 with the settings mentioned, no luck
Click to expand...
Click to collapse
If you are absolutely certain your cable is a good one, it is possible you have a driver issue, but I doubt it.
You could try deleting/uninstalling you current ADB driver set and then install the following ADB clockworkmod universal drivers . It might help.
64bit
32bit
If you decide to install the drivers. make sure you select "Android Composite ADB Interface"
after installing the driver set
If that does not help, I am sorry to say, you are likely looking at a hardware failure of the charging port(Dock Connector &Flex Cable)
It looks easy and economical to replace. I found the part here, but you could Google around. I have no experience with the following site.
http://www.repairsuniverse.com/lg-nexus-4-e960-dock-connector-flex-cable-replacement.html
If it were my N4(still great phone), I'd replace the part and attempt to re-flash.
Best of luck.
joegestes said:
If you are absolutely certain your cable is a good one, it is possible you have a driver issue, but I doubt it.
You could try deleting/uninstalling you current ADB driver set and then install the following ADB clockworkmod universal drivers . It might help.
64bit
32bit
If you decide to install the drivers. make sure you select "Android Composite ADB Interface"
after installing the driver set
If that does not help, I am sorry to say, you are likely looking at a hardware failure of the charging port(Dock Connector &Flex Cable)
It looks easy and economical to replace. I found the part here, but you could Google around. I have no experience with the following site.
http://www.repairsuniverse.com/lg-nexus-4-e960-dock-connector-flex-cable-replacement.html
If it were my N4(still great phone), I'd replace the part and attempt to re-flash.
Best of luck.
Click to expand...
Click to collapse
Thanks for the links, I might give it a go.
I bought an original Moto x last night for $100 and I was going to root the potatoes out of it, but who knew non-nexus phones were so difficult to unlock? Damn AT&T....
I sort of suspected it was a hardware issue when I was getting nowhere with NRT, but I wanted confirmation from someone more knowledgeable than me. Any idea on the likelyhood it is something other than the port? The bit that concerns me is that TWRP was unable to mount any partitions, but then again, if i couldn't connect while in TWRP, sort of sounds like a port issue.
oh well...
a.child said:
Thanks for the links, I might give it a go.
I bought an original Moto x last night for $100 and I was going to root the potatoes out of it, but who knew non-nexus phones were so difficult to unlock? Damn AT&T....
Click to expand...
Click to collapse
LOL....That's why I mostly stick with Nexus devices. No carrier garbage, global bands, unlockable and plenty of potatoes:laugh:
a.child said:
Any idea on the likelyhood it is something other than the port?.
Click to expand...
Click to collapse
Could be a bad eMMC but I doubt that. Port failure is more likely to be the issue based on your inability to ADB devices in TWRP.
a.child said:
The bit that concerns me is that TWRP was unable to mount any partitions, but then again, if i couldn't connect while in TWRP, sort of sounds like a port issue
Click to expand...
Click to collapse
Its harder know exactly when using NRT.
That is one reason why, IMO, it is far better to use Fastboot commands to flash instead of relying on toolkit automation.(I do think NRT is the best toolkit)
My guess is NRT sends erase commands to a partition before flash attempts which then failed or sometimes, when a port goes bad,
it is intermittent, a partial flash occurs which would also explain why TWRP can,t mount a particular partition.
For ten bucks delivered on eBay its a no brainier to change out the port. It will probably fix it and if not, you'll have learned something.
joegestes said:
LOL....That's why I mostly stick with Nexus devices. No carrier garbage, global bands, unlockable and plenty of potatoes:laugh:
Could be a bad eMMC but I doubt that. Port failure is more likely to be the issue based on your inability to ADB devices in TWRP.
Its harder know exactly when using NRT.
That is one reason why, IMO, it is far better to use Fastboot commands to flash instead of relying on toolkit automation.(I do think NRT is the best toolkit)
My guess is NRT sends erase commands to a partition before flash attempts which then failed or sometimes, when a port goes bad,
it is intermittent, a partial flash occurs which would also explain why TWRP can,t mount a particular partition.
For ten bucks delivered on eBay its a no brainier to change out the port. It will probably fix it and if not, you'll have learned something.
Click to expand...
Click to collapse
Well i replaced the port and the battery and i'm having the same problem. And I did check to make sure I didn't reinstall the old port.
Guess she's dead :'(
Hmmm... You can connect in fastboot mode, right?
How about re-locking and unlocking the bootloader? It helped me several times...
You'll have to search about how to use fastboot. Connect your phone to your pc while in fastboot mode, and type this into terminal window :
fastboot oem lock
(Press enter)
(bootloader will be locked)
fastboot oem unlock
(Press enter)
(Phone's screen will display sth, use volume keys and power keys to unlock the bootloader)
(It will erase itself)
ddaggebi said:
Hmmm... You can connect in fastboot mode, right?
How about re-locking and unlocking the bootloader? It helped me several times...
You'll have to search about how to use fastboot. Connect your phone to your pc while in fastboot mode, and type this into terminal window :
fastboot oem lock
(Press enter)
(bootloader will be locked)
fastboot oem unlock
(Press enter)
(Phone's screen will display sth, use volume keys and power keys to unlock the bootloader)
(It will erase itself)
Click to expand...
Click to collapse
Thanks for the suggestion, but it didn't work. I was able to lock and unlock the bootloaded again, but it didn't have any effect.
Have you tried flashing Jellybean or kitkat stock rom by fastboot?
If that doesn't work, then the problem is within EMMC. You'll have to let her go...
ddaggebi said:
Have you tried flashing Jellybean or kitkat stock rom by fastboot?
If that doesn't work, then the problem is within EMMC. You'll have to let her go...
Click to expand...
Click to collapse
Looking at other forums, pretty sure the emmc is dead, but I'll try flashing an older version.
Related
Tried my best to search the forums for anyone else having this issue, couldn't find much.
My N7 isn't rooted at all. It worked fine until last night, the screen wouldn't turn on so I held the power button down to turn it off, booted it back up and it goes into a screen with a red triangle and says "No Command". It sits on this screen for a while and then reboots, and does the same over and over. I can get into fastboot (it also throws the "No Command" when trying to get into recovery), but I'm not sure what my options are. I'm hoping I don't have to resort to wiping the device, so any suggestions would be appreciated, thanks!
AW: [Q] Boots Into "No Command" Screen
When you boot in recovery and the red triangle appears, have you tried to press volume down and power again? It should boot in recovery
Sent from my SK17i running Android 4.1.2
Use fastboot to flash a custom recovery, and then do a nandroid backup. From there, you can mess around without fear of losing your data. Perhaps you will need to re-flash the boot or system image, but I can't imagine what could have happened to it in the first place.
AW: [Q] Boots Into "No Command" Screen
korockinout13 said:
Use fastboot to flash a custom recovery, and then do a nandroid backup. From there, you can mess around without fear of losing your data. Perhaps you will need to re-flash the boot or system image, but I can't imagine what could have happened to it in the first place.
Click to expand...
Click to collapse
He said he has no root and so I guess the bl is locked so he would loose his data while unlocking, right?
Sent from my SK17i running Android 4.1.2
I contacted support and they pretty much immediately started to process an RMA. She said someone had called in earlier today with the same problem and they couldn't figure anything out. I have a feeling they don't send new ones for these types of things, so I'm still going to try to fix mine. Thanks for the suggestions.
Here's a pic, I'm still confused on how little I've found about this "No Command" 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"
}
mihahn said:
When you boot in recovery and the red triangle appears, have you tried to press volume down and power again? It should boot in recovery
Sent from my SK17i running Android 4.1.2
Click to expand...
Click to collapse
Woah, did you mean power and volume UP? Because that works... it brings up the recovery menu.....
Am I missing something? Is it normal to have to press power + volume up to see the recovery menu?
Okay, so I guess the real problem is that I'm stuck booting into recovery. Was there an OTA update?
I ended up fixing this. Once I realized what I was seeing was recovery mode, I tried clearing data + cache, but that didn't work. Still booted into recovery mode every time. I went through the mess of installing the right drivers (no idea if it's just me but I always have issues with my computer recognizing my devices), and I used the android SDK to unlock the bootloader and then flashed the factory image. Lost all my data but oh well, better than going through the RMA process.
Thanks again for the help. I seriously would have never realized that silly screen was recovery. Why can't it just show the menu by default...
edit: one other thing, the biggest hurdle I ran into was that I didn't have the drivers installed at all. but since I couldn't boot up I couldn't install the adb driver. I was able to install the fastboot one just fine, but the fastboot commands didn't work until I installed the adb driver. only way I was able to install the adb driver was to go into the 'sideload using adb' option in recovery, at that point windows prompted for the drivers. not sure if there's a manual way of installing the driver but yeah. hopefully that made some sense.
Leadsuit said:
Woah, did you mean power and volume UP? Because that works... it brings up the recovery menu.....
Click to expand...
Click to collapse
Just for future reference, when at the red triangle, you can get into recovery by holding vol up and power?
Sent from my SGH-I777 using xda premium
From efrants android 101 sticky:*I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:/system/etc/install-recovery.sh <== this is the script that installs the patch file/system/recovery-from-boot.p <== this is the patchYou have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my GT-I9300 using xda premium
---------- Post added at 06:17 AM ---------- Previous post was at 06:10 AM ----------
That is the cause of the No Comnand screen.
Sent from my GT-I9300 using xda premium
please explain the steps to fix the NO COMMAND on your tablet
Leadsuit said:
I ended up fixing this. Once I realized what I was seeing was recovery mode, I tried clearing data + cache, but that didn't work. Still booted into recovery mode every time. I went through the mess of installing the right drivers (no idea if it's just me but I always have issues with my computer recognizing my devices), and I used the android SDK to unlock the bootloader and then flashed the factory image. Lost all my data but oh well, better than going through the RMA process.
Thanks again for the help. I seriously would have never realized that silly screen was recovery. Why can't it just show the menu by default...
edit: one other thing, the biggest hurdle I ran into was that I didn't have the drivers installed at all. but since I couldn't boot up I couldn't install the adb driver. I was able to install the fastboot one just fine, but the fastboot commands didn't work until I installed the adb driver. only way I was able to install the adb driver was to go into the 'sideload using adb' option in recovery, at that point windows prompted for the drivers. not sure if there's a manual way of installing the driver but yeah. hopefully that made some sense.
Click to expand...
Click to collapse
please explain the steps to fix the NO COMMAND on your tablet?
tHanks
help please
Leadsuit said:
I ended up fixing this. Once I realized what I was seeing was recovery mode, I tried clearing data + cache, but that didn't work. Still booted into recovery mode every time. I went through the mess of installing the right drivers (no idea if it's just me but I always have issues with my computer recognizing my devices), and I used the android SDK to unlock the bootloader and then flashed the factory image. Lost all my data but oh well, better than going through the RMA process.
Thanks again for the help. I seriously would have never realized that silly screen was recovery. Why can't it just show the menu by default...
edit: one other thing, the biggest hurdle I ran into was that I didn't have the drivers installed at all. but since I couldn't boot up I couldn't install the adb driver. I was able to install the fastboot one just fine, but the fastboot commands didn't work until I installed the adb driver. only way I was able to install the adb driver was to go into the 'sideload using adb' option in recovery, at that point windows prompted for the drivers. not sure if there's a manual way of installing the driver but yeah. hopefully that made some sense.
Click to expand...
Click to collapse
hi Sir! I'm having the same problem, please help me. i dont know anything about adb drivers..
please tell me steps to use adb side load my android spice dream uno mi498
Leadsuit said:
I ended up fixing this. Once I realized what I was seeing was recovery mode, I tried clearing data + cache, but that didn't work. Still booted into recovery mode every time. I went through the mess of installing the right drivers (no idea if it's just me but I always have issues with my computer recognizing my devices), and I used the android SDK to unlock the bootloader and then flashed the factory image. Lost all my data but oh well, better than going through the RMA process.
Thanks again for the help. I seriously would have never realized that silly screen was recovery. Why can't it just show the menu by default...
edit: one other thing, the biggest hurdle I ran into was that I didn't have the drivers installed at all. but since I couldn't boot up I couldn't install the adb driver. I was able to install the fastboot one just fine, but the fastboot commands didn't work until I installed the adb driver. only way I was able to install the adb driver was to go into the 'sideload using adb' option in recovery, at that point windows prompted for the drivers. not sure if there's a manual way of installing the driver but yeah. hopefully that made some sense.
Click to expand...
Click to collapse
I have spice dream uno 498 6.0.1 my phone showing no command Pls tell me steps of using adb +command to give via pc
I know fastboot issues are probably a common thing to be asked, but I've had fastboot issues before and I've always been able to fix them. This time I just can't and I've been trying to fix it for several hours now to no avail.
I can't get my Nexus 4 to be recognized by adb in Fastboot mode. I've managed to figure out that it's definitely an issue on the Nexus 4's side, cause I can get my Nexus 7 to be recognized in fastboot mode. I've installed the latest Google drivers, uninstalled them, reinstalled them over and over again, tried installing drivers through Nexus Root Toolkit, EVERYTHING. But nothing seems to work. It recognizes fine when it's running a ROM itself. typing "adb devices" shows the device find, I can reboot into the bootloader with "adb reboot bootloader", all that works fine, but once in the bootloader it just doesn't work. I've made to sure to reinstall the drivers while in the bootloader, and nothing seems to do the trick.
What's interesting is that I did a driver test with Nexus Root Toolkit, and it actually recognized it while it was in Fastboot mode and went through the whole test successfully. It reset out of bootloader mode and booted up, so I'm confused as to how it recognized it but I can't.
I tried flashing the Kit Kat factory image through Nexus Root Toolkit, and I thought it worked, but then it gave a random error at the end and rebooted and I was still running the ROM that I flashed a few days ago.
I'm really at a loss for what I can do. Without fastboot the device is stuck on custom ROMs. Nothing seems to work. I'm honestly baffled, I can usually figure this stuff out on my own but NOTHING is working anymore.
Any ideas?
Try turning off MTP
Sent from my Nexus 4 using xda app-developers app
This is just a wild guess, but maybe its between your bootloader version and the fastboot version. Try to use the latest ADT package from Google. If you post the exact error the toolkit give might be easier to diagnose. Also when you connected the N4 in bootloader mode, what is the name of it in Device Manager? Mine is "Google Nexus 4 Bootloader Interface" under the category of "Android Device", using the latest Universal Naked Driver. If your isn't the same try reinstalling it with UND.
kboya said:
Try turning off MTP
Click to expand...
Click to collapse
Nope. Plus I don't see how that would effect it, considering the MTP/PTP is only for toggling between accessing the full storage and having the device recognized as a camera from my understanding. In bootloader mode it wouldn't even recognize which mode it's in. At least I think.
Regardless, tried it in both and it didn't work.
eksasol said:
This is just a wild guess, but maybe its between your bootloader version and the fastboot version. Try to use the latest ADT package from Google.
Click to expand...
Click to collapse
Redownloaded the whole adt package. Didn't help.
eksasol said:
If you post the exact error the toolkit give might be easier to diagnose.
Click to expand...
Click to collapse
It was kinda weird, I think it thought it was flashing the factory image but it wasn't actually doing anything. I'm pretty sure the the error was just some weird error in the program itself, it didn't really say anything usefu;.
eksasol said:
Also when you connected the N4 in bootloader mode, what is the name of it in Device Manager? Mine is "Google Nexus 4 Bootloader Interface" under the category of "Android Device", using the latest Universal Naked Driver. If your isn't the same try reinstalling it with UND.
Click to expand...
Click to collapse
"Android Bootloader Interface" under the category of "Android Device". Drivers are the official ones from Google. I don't think I've tried the Universal Naked Driver. I'll try that and report back.
Tried installing the Universal Naked USB Drivers from this thread, and got this error:
{
"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"
}
Ashanmaril said:
Tried installing the Universal Naked USB Drivers from this thread, and got this error:
Click to expand...
Click to collapse
It means you are using Windows 8 and is trying to install an unsigned driver (not sanctioned by the almighty Microsoft). You need to restart Windows 8 into Advance Startup and press F7 at the menu to disable driver signing: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Ah, okay. Thanks, I'll try that tomorrow. Heading to bed right now.
Sent from my Nexus 5 using Tapatalk
Ashanmaril said:
Ah, okay. Thanks, I'll try that tomorrow. Heading to bed right now.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Actually here's the link to the latest UND version which has Nexus 5 support as well: http://forum.xda-developers.com/showthread.php?t=2513339
Alright, managed to install the driver, but it still won't recognize the Nexus 4.
The driver DID manage to make adb notice my Nexus 7 in adb sideload mode so I was able to update to Kit Kat on that.
I'm really at a loss for what to do on the Nexus 4 though...
Ashanmaril said:
Alright, managed to install the driver, but it still won't recognize the Nexus 4.
The driver DID manage to make adb notice my Nexus 7 in adb sideload mode so I was able to update to Kit Kat on that.
I'm really at a loss for what to do on the Nexus 4 though...
Click to expand...
Click to collapse
stopped Reading here "I can't get my Nexus 4 to be recognized by adb in Fastboot mode". adb never Works on fastboot mode, if it Works then its a oem modified bootloader to work with that.
Adb works in Fastboot mode. That's how you flash factory images on Nexus devices.
See this video.
Sent from my Nexus 7 using Tapatalk 4
Ashanmaril said:
Adb works in Fastboot mode. That's how you flash factory images on Nexus devices.
See this video.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
facotry images use "fastboot flash partitonname file".
Example, fastboot flash system system.img or fastboot flash bootloader bootloader-mako-z30i.img
Ashanmaril said:
Adb works in Fastboot mode. That's how you flash factory images on Nexus devices.
See this video.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
No he's right, it's called bootloader mode actually and it only work with fastboot, ADB only work in custom recovery. Fastboot is the main method to flash factory image.
sent from xda premium app
Oh, shoot. Sorry, I just realized I've been calling it fastboot mode this whole time. I meant bootloader mode.
Either way, yeah. Still haven't figured out what's going on.
Ashanmaril said:
Oh, shoot. Sorry, I just realized I've been calling it fastboot mode this whole time. I meant bootloader mode.
Either way, yeah. Still haven't figured out what's going on.
Click to expand...
Click to collapse
bootloader mode where u can select between power off,rstart,start,recovery ?
Yep. Typing "adb devices" never shows the device while it's in the bootloader. It works fine when it's powered on, I can even do commands like "adb reboot bootloader" and whatnot and they work fine, but it just doesn't work in bootloader mode.
Ashanmaril said:
Yep. Typing "adb devices" never shows the device while it's in the bootloader. It works fine when it's powered on, I can even do commands like "adb reboot bootloader" and whatnot and they work fine, but it just doesn't work in bootloader mode.
Click to expand...
Click to collapse
that is fastboot mode(it dosent looks like a normal fastboot mode because google modified it)but.as i said adb never worked on dat because its disabled, if u wanna adb on dat mode, either u get another phone or install modified bootloader(im using unlocked bootloader from att lg og because i like lg logo + adb Works on dat, but u cant install any 4.4 rom or kernel :/)
But it works with all my other Nexus devices. And it used to work.
Watch the video I linked earlier. He demonstrates using adb commands in the bootloader to flash a factory image. I've done it multiple times.
Sent from my Nexus 5 using Tapatalk
Ashanmaril said:
But it works with all my other Nexus devices. And it used to work.
Watch the video I linked earlier. He demonstrates using adb commands in the bootloader to flash a factory image. I've done it multiple times.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
that is not nexus 4 + he only used FASTBOOT commands, i seriously didnt see any adb command, can u gimme the time? he showed the .imgs on folder he showed the nexus(it looked like the 10) and he done fastboot flash blablabla.
print: http://prntscr.com/24fbm0
Oh. My. Gosh.
I am so stupid.
This whole time I've been typing "adb devices" to test to see if it was recognizing the devices. I was supposed to be typing "fastboot devices"
I have no words. I tried every complex solution I could think of... And it was just me being stupid...
Sorry about that. I guess this is solved. I'm gonna go hit my head against the wall for a bit.
* I don't know enough to be messing with this, but here I am.
** My device is rooted, but I got into this mess by updating (device was working fine, did not use 3rd party software) and when it restarted after install it went to boot loader.
*** Device only turns on when its plug into wall outlit for 20 seconds. I can not get it to turn on with power button or when its plugged into laptop. Not sure if this is normal or not.
**** Something similar happened to this before but I just used twrp and fixed it. I can not flash a recovery unless my nexus is working normally.
***** Yes, I read other threads, on this forums and others, havnt found anything that has helped. I figured i could post specific details that other threads were lacking.
My nexus 10 is currently stuck in boot loader. If I select recovery mode, it does not switch to the smaller green android, that you can press down power, volume down/up and get into TWRP. Nothing I have done has gotten me anywhere except boot loader. I have tried to use Nexus Root Tool Kit and use the Flash Stock + Unroot and Flash Image to various partitions. No success. Today, downloaded Odin 3.07, but it crashed when file analysis in message box.
Im downloading SDK tools right now, but Im not quite sure what those are, will have to experiment.
See attached files please.
{
"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 recovery that I can not get to.
Current state of device. can not get anywhere else.
Close up of date.
Picture of odin failing. I tried to flash using the option called PDA by the way.
Picture of options Im trying to use on NRT. I also tired flash stock +unroot but no change to device.
solved - cant find where to set this thread to solved thought.
Any help is greatly appreciated.
Nyreb said:
* I don't know enough to be messing with this, but here I am.
** My device is rooted, but I got into this mess by updating (device was working fine, did not use 3rd party software) and when it restarted after install it went to boot loader.
*** Device only turns on when its plug into wall outlit for 20 seconds. I can not get it to turn on with power button or when its plugged into laptop. Not sure if this is normal or not.
**** Something similar happened to this before but I just used twrp and fixed it. I can not flash a recovery unless my nexus is working normally.
***** Yes, I read other threads, on this forums and others, havnt found anything that has helped. I figured i could post specific details that other threads were lacking.
My nexus 10 is currently stuck in boot loader. If I select recovery mode, it does not switch to the smaller green android, that you can press down power, volume down/up and get into TWRP. Nothing I have done has gotten me anywhere except boot loader. I have tried to use Nexus Root Tool Kit and use the Flash Stock + Unroot and Flash Image to various partitions. No success. Today, downloaded Odin 3.07, but it crashed when file analysis in message box.
Im downloading SDK tools right now, but Im not quite sure what those are, will have to experiment.
See attached files please.
View attachment 2637629
Image of recovery that I can not get to.
View attachment 2637596
Current state of device. can not get anywhere else.
View attachment 2637598
Close up of date.
View attachment 2637611
Picture of odin failing. I tried to flash using the option called PDA by the way.
View attachment 2637622
Picture of options Im trying to use on NRT. I also tired flash stock +unroot but no change to device.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Shoot me a email at [email protected]... We can talk more about your issues there..... Thx lj
Solution
Thanks to lj50036, my nexus now actually works.
Here's what he told me to do:
----------
1.) start here http://forum.xda-developers.com/showthread.php?t=2588979
This will install abd fastboot and the drivers for your tablet just follow instructions.
2.) Now open cmd as admin and type
fastboot
should see commands and options listed
3.) now type
cd /
this will move root to c drive.
4.) plug in tablet, boot into bootloader (holding down power, volume up and down I think) and type
fastboot devices
this output serial number of device and then type of device (Fastboot)
5.) go to https://developers.google.com/android/nexus/images#mantaray or google factory images and find Nexus 10. use what ever version you want. download, unzip and you should see something along the lines of this (the kot49h will be what ever version of the image you used.)
6,) move everything but the 2 .sh files to root of c drive (c:/)
and then in cmd prompt type
dir
this will print out file names, data, and other information of c:/. make sure you see the 3 files you moved from the factory image you unzipped.
7.) if so, make sure tablet is in bootloader still, and type
flash-all.bat in cmd prompt.
--About halfway through it reboots your nexus and because my nexus wont reboot its self, and will only come on when its plugged into wall outlet for a bit, I just did that and plugged in and it worked fine.
-- once the whole process runs, my nexus rebooted into recovery mode, and after a minute rebooted correctly and I was able to start setting up.
----------------
Thank you again to lj50036
@Nyreb
Change the forum name to include (SOLVED)
@lj50036
So I had mostly the same problem happen, except I tried to get into recovery to flash a CM11, but I was completely stock. It would get stuck on the screen below. I did what you said to do above and it still sticks at the same screen it did before, except sometimes it shows the Google logo before getting stuck. It used to just show the android on it's back right off the bat. Not sure what to do anymore.
spudsmac said:
@lj50036
So I had mostly the same problem happen, except I tried to get into recovery to flash a CM11, but I was completely stock. It would get stuck on the screen below. I did what you said to do above and it still sticks at the same screen it did before, except sometimes it shows the Google logo before getting stuck. It used to just show the android on it's back right off the bat. Not sure what to do anymore.
Click to expand...
Click to collapse
Shoot me a email.... Sounds like you need some help....
So I ended up emailing @lj50036 and we went back and forth and had to reflash everything, including custom recovery, TWRP. I think the recovery was messed up.
Finally works again!
spudsmac said:
So I ended up emailing @lj50036 and we went back and forth and had to reflash everything, including custom recovery, TWRP. I think the recovery was messed up.
Finally works again!
Click to expand...
Click to collapse
What happen in android some time, and I may be way off in left field here but, it has happened this way on the tf700, tf300, tf201, and the nexus 10... Just what I have help people with is that....
The storage no matter what command you issue in fastboot e.g
Code:
fastboot erase boot
fastboot erase system
fastboot -w
It just will not erase everything, and by doing these commands your really only telling the tab and or phone that you are going to be putting other
data in those partitions, so if you just flash exactly what was already on the tablet it does not like it...
@spudsmac had upgraded to 4.4.2 and was trying to install cm11 when things went wrong
So by us trying to reset the tablet to factory 4.4.2 firmware it would not take it... Just froze at android guy with x
So when, we went one version older on the firmware... Magic happened and he was golden....
Thx Josh
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.
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.