Daughter loves her xoom but a few days ago her password quit working- same password she has used since she got it in 2012, plus it doesn't show my wifi network on the unlock screen anymore. Xoom is bone stock with all current updates.
I figure it was stuck in a loop and attempted soft reboot-no luck...on to hard reset, pwr+down vol., goes to android recovery but no selection available just a picture of android on it's back with access hatch open and a large red triangle containing an exclamation point...froze up at that point but would soft reset and reboot to unlock screen but still no-go on the password and no-go on identifying the network.
I have gone through this 5-6 time since with no luck but now it will not go to android recovery, but instead "starting fastboot protocol support" comes up every time in LH corner of the screen.
I have exhausted my limited knowledge...any ideas??? Motorola support online was a waste of time and they want $100 if I send it in.
Thank you in advance.
Leatherneck2111 said:
Daughter loves her xoom but a few days ago her password quit working- same password she has used since she got it in 2012, plus it doesn't show my wifi network on the unlock screen anymore. Xoom is bone stock with all current updates.
I figure it was stuck in a loop and attempted soft reboot-no luck...on to hard reset, pwr+down vol., goes to android recovery but no selection available just a picture of android on it's back with access hatch open and a large red triangle containing an exclamation point...froze up at that point but would soft reset and reboot to unlock screen but still no-go on the password and no-go on identifying the network.
I have gone through this 5-6 time since with no luck but now it will not go to android recovery, but instead "starting fastboot protocol support" comes up every time in LH corner of the screen.
I have exhausted my limited knowledge...any ideas??? Motorola support online was a waste of time and they want $100 if I send it in.
Thank you in advance.
Click to expand...
Click to collapse
When you are in the android robot screen, press both volume up and power button and the recovery option will appear. You can do factory reset from there and delete user data to reset the password as well
superbay said:
When you are in the android robot, press both volume up and down and the recovery option will appear
Click to expand...
Click to collapse
Tried it when the robot appeared...nothing. It was frozen and I had to soft boot to get out. Now it won't even go to recovery, it goes dtraight to "starting fastboot protocol support" and then freezes.
Leatherneck2111 said:
Tried it when the robot appeared...nothing. It was frozen and I had to soft boot to get out. Now it won't even go to recovery, it goes dtraight to "starting fastboot protocol support" and then freezes.
Click to expand...
Click to collapse
Ah just edited my post just now. Try it when you can go to recovery
superbay said:
Ah just edited my post just now. Try it when you can go to recovery
Click to expand...
Click to collapse
Thanks, but it won't even go to recovery anymore- just to fastboot protocol support. No matter what I do. Should I try a complete battery drain and then recharge and see if something resets and allows access to recovery again? I'm out of ideas.
Thank you again for the suggestions.
Leatherneck2111 said:
Thanks, but it won't even go to recovery anymore- just to fastboot protocol support. No matter what I do. Should I try a complete battery drain and then recharge and see if something resets and allows access to recovery again? I'm out of ideas.
Thank you again for the suggestions.
Click to expand...
Click to collapse
Hmmm that's odd. If i may suggest, maybe you can try sbf too since it requires you to go to fastboot as well. But that's the very last resort everyone could ever do to their device. Never knew about battery drain method but you can try your way if you want to
Leatherneck2111 said:
Tried it when the robot appeared...nothing. It was frozen and I had to soft boot to get out. Now it won't even go to recovery, it goes dtraight to "starting fastboot protocol support" and then freezes.
Click to expand...
Click to collapse
Since you still can get to "starting fastboot protocol support", you can still use fastboot from command line.
Go google this "Motorola Xoom final rescue". It will teach you how to flash it back to
Stock Rom (Honeycomb).
Once your Xoom back in action, you can always upgrade it back to Jellybean.
You can boot into recovery using below command if USB debugging is enabled.
> adb reboot recovery
Related
Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks
crozuk said:
Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks
Click to expand...
Click to collapse
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.
okantomi said:
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.
Click to expand...
Click to collapse
Thanks for your reply - tried numerous times getting into recovery - get stuck with one line of 'starting fastboot protocol' and seems to hang there.
Have experience rooting and flash etc. and have obviously used adb in the past.
If I could just get to recovery - or a state where I could use adb I would be fine. But as I said in my first post - looks like I can only access an 'RSD' state.
Is there any other way of getting adb access from my PC? All the help for bricked xooms seems to concern US models - and don't want to try anything that will completely write it off!
Thanks again for your help.
Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!
crozuk said:
Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!
Click to expand...
Click to collapse
If you are still rooted and all, just for safety's sake, make sure to do another nandroid backup and save it to your micro sdcard. Backup, backup, backup. Then also make sure that you have a compatible cwm recovery installed, that will let you access your microsd card. It sounds like you're alright, so, cool.
Greetings! First of all, I would like to thank anyone who takes the time to help me diagnose and resolve this issues, let alone anyone who takes the time to read this thread.
I've been having issues with my Xoom (ICS 4.0.0) for about 3 weeks now.
A brief history of the issue's occurrence:
-I unrooted the device and returned it to stock.
-Everything was fine and dandy until one day it spontaneously said something along the lines of 'Android is upgrading..', and then performed a reset.
-Since resetting, it bootloops.
The device only turns on when plugged into a charger and hard reset.
The device only turns off when allowed to boot loop for minutes and then hard reset (it simply does not reset, and just turns off).
I'm not the most technically-savvy person with android devices but here are some things I've done/noted.
When trying to use adb commands, it does not recognize the device or properly issue commands.
I've tried wiping data/clearing cache to no avail.
EDIT: I've tried fastbooting, but the bootloader will not unlock. When trying to unlock, it simply resets and then acts as though it was never unlocked.
I have no idea how to return it to a stock image. All I know is that I have a micro-SD and some spare time.
Could anyone help me understand what exactly is going on with my Xoom?
If I can provide you with any more information, please let me know.
Thanks again. (=
If it was stock and spontaneously upgraded it sounds like a bad OTA upgrade. I've been rooted from the start so never have taken an OTA upgrade...don't you need to accept it or can it just upgrade on it's own?
Anyway, can you get it into fastboot mode?
Volume up and power, then at dual core screen, press volume down...if you see something like "entering fastboot mode" you're not bricked. You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
If you haven't done so, just google 'recovering Xoom using fastboot' and you should get some good information.
Good luck!
Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools -
http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
As Always If This Was Helpful Hit the Thanks!
Yeah, what Mjamocha said...
okantomi said:
Yeah, what Mjamocha said...
Click to expand...
Click to collapse
LOL Thanks.
okantomi said:
Anyway, can you get it into fastboot mode?
Click to expand...
Click to collapse
Yes, I can. But so far nothing has been successful in terms of fastboot commands.
okantomi said:
You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
Click to expand...
Click to collapse
When I try to execute fastboot commands such as 'fastboot flash boot boot.img'.. it says the following:
Device still locked. Device must be unlocked first. Failed to process command error(0x8)
Whenever I try to unlock the bootloader, it appears to be successful at first and then the device reboots. But it just reboots to a bootloop, and the bootloader still says its locked. Perhaps I made a mistake in communication. The bootloader is currently locked and will not unlock, as just described.
When I try to unlock it and it reboots, even if I access the fastboot menu right away, it still says the device is still locked.
Thoughts?
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
slacka-vt said:
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
Click to expand...
Click to collapse
Yes, I can get into android recovery. However, within a second of switching into recovery mode, the robot falls down and there appears to be a red triangle caution sign containing an exclamation point.
When trying to do a factory reset, it says all data is wiped (as normal). Upon rebooting, it continues to bootloop. So essentially the factory reset and cache clear options in the Android Recovery menu do not produce the expected results.
Pretty odd. I didn't mess with the Xoom at all prior to this issue.
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
slacka-vt said:
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
Click to expand...
Click to collapse
Yeah, just tried it to no avail. Thanks so much for your help anyway. (=
I'm not sure what to do now.
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
slacka-vt said:
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
Click to expand...
Click to collapse
I hear ya. I've tried 2 different cords and 3 different computers. I'm using a Mac (10.6.8) right now, but have used 2 PCs (Vista + 7).
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
slacka-vt said:
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
Click to expand...
Click to collapse
I got the 'device still locked' error. Weird, huh?
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
slacka-vt said:
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
Click to expand...
Click to collapse
Yeah I tried that. Won't lock or unlock successfully. Locking produces no difference, and unlocking produces the same 'device still locked' error. This is getting out of hand! Thanks so much for your advice. You think I should open it up?
I hate to be so persistently annoying about this, but could anyone possibly suggest a method of working around the locked bootloader?
Is there anything I can do with an SD card to remedy the device's stubborn foolery?
I think you should give it a try, I have bricked my xoom a few times and have always been able to flash the stock imagine to recover. You really have nothing to lose by pulling the battery pin just be careful.
Sent from my Xoom using xda premium
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
cherlamperter said:
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
Click to expand...
Click to collapse
I have looking for a utube how to guide but no luck, I just might make one for you so you will know what to expect. Give me a few and I will get back to ya.
Sent from my Xoom using xda premium
Hi there. I set a homescreen ealier today to use a vpn. I wanted to turn it off but the "none" option was greyed out. I then go to security, and clear all installed credentials. Now when I tried texting, the messenger app would close upon opening. so I went to security and clicked system reset. I left "Erase Personal Data" unchecked. Then my phone rebooted and never moved past the "HTC Quietly Brilliant" screen. I forced it to reboot by holding the power button, and I proceeded to go to the bootloader! Great, it works. Go to recovery... as soon as I open it, my phone goes dark. I turn it back on, boot loop. and now my phone is stuck kinda "bricked". I have access to the bootloader and fastboot. I'm guessing the reset button that I clicked is looking for the stock recovery to restore the phone, but because it is replaced with clockworkmod's recovery, it closes on launch. Any way I can fix this mess without going to the at&t store or getting a new phone?
Specs prior to incident:
CleanRom 7.0R2 and Rooted
Hboot 2.41
S-Off
If I need to respecify anything, please let me know.
I wonder if I should try and reflash Recovery through fastboot. I still have the files backed up from when I rooted a year ago. what command would I type though.
jackzilla241 said:
Hi there. I set a homescreen ealier today to use a vpn. I wanted to turn it off but the "none" option was greyed out. I then go to security, and clear all installed credentials. Now when I tried texting, the messenger app would close upon opening. so I went to security and clicked system reset. I left "Erase Personal Data" unchecked. Then my phone rebooted and never moved past the "HTC Quietly Brilliant" screen. I forced it to reboot by holding the power button, and I proceeded to go to the bootloader! Great, it works. Go to recovery... as soon as I open it, my phone goes dark. I turn it back on, boot loop. and No my phone is stuck kinda "bricked". I have access to the bootloader and fastboot. I'm guessing the reset button that I clicked is looking for the stock recovery to restore the phone, but because it is replaced with clockworkmod's recovery, it closes on launch. Any way I can fix this mess without going to the at&t store or getting a new phone?
Specs prior to incident:
CleanRom 7.0R2 and Rooted
Hboot 2.41
S-Off
If I need to respecify anything, please let me know.
I wonder if I should try and reflash Recovery through fastboot. I still have the files backed up from when I rooted a year ago. what command would I type though.
Click to expand...
Click to collapse
fastboot flash recovery recoveryfilename.img
you can try wiping everything and then restoring your backup.
exad said:
fastboot flash recovery recoveryfilename.img
you can try wiping everything and then restoring your backup.
Click to expand...
Click to collapse
Got a window saying compatibility issues with 64-Bit windows.
jackzilla241 said:
Got a window saying compatibility issues with 64-Bit windows.
Click to expand...
Click to collapse
I have no idea what you are talking about. Can you be more specific as to when or how you got this message?
IE: Explain what you were doing that brought it up?
exad said:
I have no idea what you are talking about. Can you be more specific as to when or how you got this message?
IE: Explain what you were doing that brought it up?
Click to expand...
Click to collapse
In pic 5, I am on my desktop running Windows 7 Ultimate x64
In pic 6, I am on my laptop running Windows 7 Home Premium x86
neither of those show you typing fastboot flash recovery recoveryfilename.img
also there should not be a compatibility issue at all.
Try these adb/fastboot files: https://dl.dropboxusercontent.com/u/19685555/fb-adb.zip
exad said:
neither of those show you typing fastboot flash recovery recoveryfilename.img
also there should not be a compatibility issue at all.
Try these adb/fastboot files: https://dl.dropboxusercontent.com/u/19685555/fb-adb.zip
Click to expand...
Click to collapse
Got new files. Wiped cache, installed new recovery! BOOM! Recovery works now. Thanks for the help Saved me from tons of stress
Oh and also... My storage for my phone is corrupt, so I'll just reformat it. Luckily I backed up everything just an hour ago.
exad said:
Try these adb/fastboot files: https://dl.dropboxusercontent.com/u/19685555/fb-adb.zip
Click to expand...
Click to collapse
Why not use Google to download the files? I personally hate dropbox and rapidshare mirrors of often outdated files that would be better got from the original source.
Fastboot/adb
http://dl-ssl.google.com/android/repository/repository-8.xml
That links:
http://dl-ssl.google.com/android/repository/platform-tools_r19.0.1-windows.zip
Google adb driver:
http://dl-ssl.google.com/android/repository/addon.xml
That links:
http://dl-ssl.google.com/android/repository/usb_driver_r09-windows.zip
apktool:
https://code.google.com/p/android-apktool/downloads/list
If Google, HTC, Samsung, Sony etc host the original files, just get them from there
Hello Guys, Im new in the foro and I would like to have your help! Due to I called Asus Official Service in Argentina and they wanna charge me with a 100 USD for soft services out of warranty.
The thing is that my dad put a MicroSD card in his TFT700t and when he whipped it out (without proper procedure), the tablet showed the following sign "Encryption unsuccessfull" and when you press "reset tablet" button, Android start thinking (5 seconds) and then you receive the error screen.
"Encryption unsuccessful
Encryption was interrupted and can't complete. As a result, the data on your tablet is not longer accessible.
To resume using your tablet, you need to perform a factory reset. Whn you set up your tablet after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account"
And a "Reset Table button"
When you hit it... there is an Android Robot image that says "Installing system upgrade" and 2 seconds later you have a Dead Android Robot with a ! sign and it says "ERROR"
I have triyed the following things:
- Hard reset by putting a clip on "reset switch"
- VOL DOWN + POWER BUTTON and Android or Wipe Data option... neither worked out.
- VOL DOWN + POWER BUTTON and put Asus Official firmware on a SDCArd renamed "EP201_768_SDUPADTE.zip"... then choose RCK option (I do not have USB Sign button).... nothing happend... the tablet looks to reset, and then they start again with "Encryption Unsuccessfull"screen.
- Finally I tryed to use Minimal ADB and Fastboot, but I used some commands to load firmware from Asus and reboot it and nothing... still the same screen.
As I said it is my old man tablet... it is standard as hell! Stock firmware, not unlocked, not rooted!
When I get into bootloader it shows:
"Androi cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.8-20130514" A03
Key driver not found.. Booting OS
staring fastboot USD download protocol
Im freaking out!! Would you please help me? I really want to fix this problem for my dad.
Thanks dudes!
luisgarino said:
Hello Guys, Im new in the foro and I would like to have your help! Due to I called Asus Official Service in Argentina and they wanna charge me with a 100 USD for soft services out of warranty.
The thing is that my dad put a MicroSD card in his TFT700t and when he whipped it out (without proper procedure), the tablet showed the following sign "Encryption unsuccessfull" and when you press "reset tablet" button, Android start thinking (5 seconds) and then you receive the error screen.
"Encryption unsuccessful
Encryption was interrupted and can't complete. As a result, the data on your tablet is not longer accessible.
To resume using your tablet, you need to perform a factory reset. Whn you set up your tablet after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account"
And a "Reset Table button"
When you hit it... there is an Android Robot image that says "Installing system upgrade" and 2 seconds later you have a Dead Android Robot with a ! sign and it says "ERROR"
I have triyed the following things:
- Hard reset by putting a clip on "reset switch"
- VOL DOWN + POWER BUTTON and Android or Wipe Data option... neither worked out.
- VOL DOWN + POWER BUTTON and put Asus Official firmware on a SDCArd renamed "EP201_768_SDUPADTE.zip"... then choose RCK option (I do not have USB Sign button).... nothing happend... the tablet looks to reset, and then they start again with "Encryption Unsuccessfull"screen.
- Finally I tryed to use Minimal ADB and Fastboot, but I used some commands to load firmware from Asus and reboot it and nothing... still the same screen.
As I said it is my old man tablet... it is standard as hell! Stock firmware, not unlocked, not rooted!
When I get into bootloader it shows:
"Androi cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.8-20130514" A03
Key driver not found.. Booting OS
staring fastboot USD download protocol
Im freaking out!! Would you please help me? I really want to fix this problem for my dad.
Thanks dudes!
Click to expand...
Click to collapse
I am getting the same thing after a recent update to Cromi 4.4
bender_123 said:
I am getting the same thing after a recent update to Cromi 4.4
Click to expand...
Click to collapse
CROMi 4.4??? That rom is quite old. What did you update from?
What recovery are you using?
Sent from my K00C using Tapatalk
berndblb said:
CROMi 4.4??? That rom is quite old. What did you update from?
What recovery are you using?
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Sorry for not labeling it properly. It is the latest version listed in the Dev section. I have been on custom Roms since day one and have never had this issue with any device. The button commands to get to recovery or fastboot seem non responsive and it will boot through a splash screen for the OS and then give this screen (sorry stole the pic from someone else having the problem on a phone, but the text is the same). My PC can see the tablet when it is in this state, but adb commands to reboot to fastboot just loop back around to the same Encryption failed screen...
http://imgur.com/AABbF14
bender_123 said:
Sorry for not labeling it properly. It is the latest version listed in the Dev section. I have been on custom Roms since day one and have never had this issue with any device. The button commands to get to recovery or fastboot seem non responsive and it will boot through a splash screen for the OS and then give this screen (sorry stole the pic from someone else having the problem on a phone, but the text is the same). My PC can see the tablet when it is in this state, but adb commands to reboot to fastboot just loop back around to the same Encryption failed screen...
yEAP... That's the screen... I have a stock tablet,stock firmware, not unlocked, not rooted.
The buttons do respond... but nothing seems to work...
thanks.
Click to expand...
Click to collapse
Try to boot into fastboot: Hold Power and Volume Down buttons until you see three icons.
If you can get into the bootloader (see above) you have a fighting chance to get this solved. Although I have not tried the fastboot/adb commands I have in mind on a locked device. No idea if they would work but no harm in trying.
You can also try to get adb access while in recovery, but you need to set up fastboot/adb on your computer first.
Let me know if you need help with either.
Sent from my K00C using Tapatalk
Sound like you need to reinstall the os. You can find info here
http://forum.xda-developers.com/showthread.php?t=1946456
Hello, so i have a problem. I've installed KingRoot on my LG Spirit H-420 and it worked great, then i searched a bit about this and saw some bad reviews and decided to uninstall it. Then i started searching more and saw some tutorial for rooting with kingroot and then using app called super su-me that uninstalls kingroot and installs SuperSU. So i did this and after installing SuperSU and rebooting my device my signal bar was showing nothing and i was unable to enter settings. Basically when i clicked my settings cog it opened and immediatly closed saying "Unfortunatly settings has stopped working" so i was unable to make calls and access my settings (although i was able to access my wifi/bluetooth/location settings by clicking them in my taskbar). So i unrooted with my superSU and did hard reset by turning off the device and holding vol down and power button to do the factory defaults. After it there was android logo saying working (like always i did the factory reset through my settings) but then its stuck on the boot screen for 30mins, before it hardly took 1min to reset to factory. How ****ed is my device and is there a chance to get it back to working ?
If the bootloader is at least showing the animation, then I don't think you need to worry much. Try the following to begin with:
1. Charge your device for a few hours if it is underpowered.
2. After that, go to your OEM recovery (by long pressing UpVolume + Power buttons) and clear the cache (there usually is the option to do it).
This should solve most issues with bootloop, etc. Try this and report back.
Its not showing the animation, its stuck on the first screen, the one thats showing LG logo and on the bottom there is "Powered by android" and there are no animations in it.
a7ogpl said:
Its not showing the animation, its stuck on the first screen, the one thats showing LG logo and on the bottom there is "Powered by android" and there are no animations in it.
Click to expand...
Click to collapse
Did you try the following:
1. Long press UpVol+Power buttons and see if it goes to stock recovery.
2. Long press DnVol+Power buttons and see if it goes to Fastboot recovery.
Are any of these working?
(Remember charging your device for a few hours as the first measure).
prahladyeri said:
Did you try the following:
1. Long press UpVol+Power buttons and see if it goes to stock recovery.
2. Long press DnVol+Power buttons and see if it goes to Fastboot recovery.
Are any of these working?
(Remember charging your device for a few hours as the first measure).
Click to expand...
Click to collapse
upvol is not doing anything and dnvol is going into the reset to factory defaults menu wheere i can choose yes or no. I still have the warranty and as far as i know rooting is not voiding warranty but flashing rom with kdz can void my warranty.
a7ogpl said:
upvol is not doing anything and dnvol is going into the reset to factory defaults menu wheere i can choose yes or no. I still have the warranty and as far as i know rooting is not voiding warranty but flashing rom with kdz can void my warranty.
Click to expand...
Click to collapse
>> and dnvol is going into the reset to factory defaults menu wheere i can choose yes or no
Then why don't you simply do a factory-reset and start using the device? Is it the case that you want to backup existing app data before that or something?
prahladyeri said:
>> and dnvol is going into the reset to factory defaults menu wheere i can choose yes or no
Then why don't you simply do a factory-reset and start using the device? Is it the case that you want to backup existing app data before that or something?
Click to expand...
Click to collapse
The thing i did it and it got into bootloop. If i click yes then there is an android logo with caption "deleting" and then it goes into booting screen [the one with LG Powered by android without animations] and stays like this forever
What happens when you connect to pc using usb? Is something detected using "adb devices" or "fastboot devices"?
prahladyeri said:
What happens when you connect to pc using usb? Is something detected using "adb devices" or "fastboot devices"?
Click to expand...
Click to collapse
Its saying lg h420 when i connect it and it is in the booting screen (the phone), so i basically could be able to flash it but i dont have my computer and the one here is not powerful enough so i dont trust it. I decided i will just try to give it with warranty and if they refuse then i will flash it. There is no other way now to rvive it. Thanks for help tho