Database Users

FroYo Problem

I plugged my phone in, to be greeted by a message from Kies saying an update is available, which is of course froYo. So I started the process of upgrading, and I went away, and came back about an hour later, to find my phone sitting on a blank screen, but the two capacitive lights still lit up when touched. On Kies it said 'Your phone will reboot when process is complete' or something like that, so I assume that the phone attempted to reboot but failed. I pulled the battery and tried manually booting it, and it passed the two boot up screens, but I was again left with a blank screen. I then decided to try and put it into recovery, but I am presented with the 'Downloading...Do not turn of target!!!!!!!!!!!!!' screen. Any help on how to fix this, if it is even possible, would be greatly appreciated.

I would read the guide here and reflash it using Odin.
http://forum.xda-developers.com/showthread.php?t=723596
It's really not difficult and and takes a couple of minutes.

Okay, thanks alot.

[Q] Desperate Cry for Help :(

Heya XDA - I have no idea WTF happened to my tab. Received notification of a OTA upgrade yesterday, taking me to one of the most recent 3.1 builds (.10 if I remember) - this morning woke up to another OTA update message offering me to go to .11 - accepted, downloaded, tablet hung up during the OTA process.
Now here's where it gets tricky. No matter what I do, when powering up my tablet I get the "Power Off - Shutting down" screen, and a endless spinning circle as the tablet claims to be shutting down. I cannot access any part of the system - all on screen commands are dead, except for the Settings icon in the lower right hand corner - i can click it, enter settings - but the moment I try to select a catagory or change any setting, the system goes right back to the "Power off - Shutting down" screen.
I am way outside the 30 days I can get a trade in - really don't want to have to mail this thing off to Acer.
Here's what I have tried:
One of Vache's full ROM images for my Region - flashed via power and vol process- fails about 1/4 of the way through.
Clearing cache/data - managed to get the vol/power+rotation lock combo going that clears cache and data. Still cannot boot - once I power on no matter what I do I get the "Power Off - Shutting Down" screen.
Tried to do the factory reset via USB keyboard + "Home"??? button? Heard mention this opens up a menu of some sort that I can factory reset from, I have two different USB keyboards and cannot manage to make this happen. Anyone able to explain this? Can this help me?
What's so weird about this - once I power up, I get the "Power Off - Shutting Down" screen no matter what I do. During this time, my battery shows up as %15 - this a500 has been on the charger for hours and hours, overnight last night, was 100% this morning before I applied the OTA update. Even with tablet plugged in, the battery shows as only 15%. What's even weirder - with tablet power off and plugged in, I do not get the red or blue charging light from the power button.
Totally freaking out here, no idea what to do. Anyone able to help?
Edit: When trying to manually flash a update.zip - I am getting the Clockwork Mod (I think?) flash screen - a green droid guy with gears turning. This fails about half way through. I have installed ClockWorkMod before this problem - but cannot enter the clockwork menu by the normal vol/power combo - I am so confused
Edit again: From browsing other posts - seems I am not the only one with this problem. The most recent OTA update failed, every single reboot since then is useless - all I can get is the "Shutting Down.." screen. Trying yet another update.zip via MicroSD to see if I can actually restore my tablet
Edit Yet once more (Problem Resolved!) - no idea how - but after a lot of searching I found a full package with build number 4.010.40_COM_GEN1 - this update.zip flashed with no problems, and my Iconcia is UNBRICKED! Sorry for the panic, everyone

OTA .13 Failure
I have the same problem, but got there by a different path. After many attempts to upgrade to .11 from .7, I downloaded the full file .02 to .11, decrypted and moved update.zip into the external sd card. Used the power / vol- combination and the update to version .11 went on without a hitch. Shortly after that, I received a notice that .13 OTA was available. It appeared to install without a hitch but after it rebooted (automatically) the tablet came back and immediately displayed the never ending Power Off screen described above. I would add that a two gears with a belt icon is sitting in the top left corner and "Android System" is noted beside that icon. I have tried every trick I have found in the forums to fix this:
1. Removed the SD card and shut down the tablet
2. Used power / vol- with portrait rotation lock turned on
3. Put the SD Card (with the .11 update.zip file ) back in and tried 1 and 2 again (no change: never ending power Off)
4. Tried power / vol+ with rotation lock. Saw the cach clear and looked very promising. Came back up with the rotating gears guy, but still went back to Power Off.
As soon as the power button is pressed the power icon goes red and stays there. Looks like the .13 update fools the device into thinking the battery is dean and it tries to shut down but never completes the cycle.
Acer A500
Rooted
Acer Recovery installed
.11 last successful update
US (Texas)
Failed .13 OTA

alamotx said:
I have the same proble,, (trim) I would add that a two gears with a belt icon is sitting in the top left corner and "Android System" is noted beside that icon. I have tried every trick I have found in the forums to fix this:
1. Removed the SD card and shut down the tablet
2. Used power / vol- with portrait rotation lock turned on
3. Put the SD Card (with the .11 update.zip file ) back in and tried 1 and 2 again (no change: never ending power Off)
4. Tried power / vol+ with rotation lock. Saw the cach clear and looked very promising. Came back up with the rotating gears guy, but still went back to Power Off.
As soon as the power button is pressed the power icon goes red and stays there. Looks like the .13 update fools the device into thinking the battery is dean and it tries to shut down but never completes the cycle.
Acer A500
Rooted
Acer Recovery installed
.11 last successful update
US (Texas)
Failed .13 OTA
Click to expand...
Click to collapse
Exact same problem here. Downloading update.zip files like mad trying to find one that will work. Anyone have any idea what the hell is going on?

Moving to Q&A.
PS: Every Q? thread should be posted in Q&A.

Thanks for that - sorry for mispost. Again, as noted in my original post - question answered, issue resolved. Total panic this morning

entropy.of.avarice said:
Exact same problem here. Downloading update.zip files like mad trying to find one that will work. Anyone have any idea what the hell is going on?
Click to expand...
Click to collapse
Me too... Ive tried 104.02, 4.010.22, 141.07, 141.02 none of them are getting me back... I can boot the tablet, but I now have no launcher icons for back, tabs, and home, and of course no clock and settings tab at the bottom. I have no root, and no CWM now. HELP!!!!

entropy.of.avarice said:
Thanks for that - sorry for mispost. Again, as noted in my original post - question answered, issue resolved. Total panic this morning
Click to expand...
Click to collapse
Please share your solution for the rest of the community.. if the solution is in a different thread, could you put a link here to the other thread with your solution?
Thanks

Euclid's Brother said:
Please share your solution for the rest of the community.. if the solution is in a different thread, could you put a link here to the other thread with your solution?
Thanks
Click to expand...
Click to collapse
For sure - sorry about the delay on that, was just so excited to be unbricked after a day of futile effort, I needed a break.
Anyway - here's what I have figured out. Somehow during the ota update I received this morning something failed - the tablet rebooted, and regardless of what I did the moment I booted up I would get the powering down notification. System access was not possible. This was on a 100% stock official 3.1 version - even unrooted before letting the update run.
Tried one of the full ROMS from Vache's thread in the dev section, as well as a bunch of other backup images I was able to find. Every single one failed at about 25%.
After a lot of fail - I gave this thread a try:
http://forum.xda-developers.com/showthread.php?t=1187578
"Bricked Tablet...help!"
I used the link on the bottom of page one - the unencrypted update.zip user kjy2010 was kind enough to upload - here is the direct link - http://www.multiupload.com/WCT2FYLMQC
This one worked - put on MicroSD card and flashed via vol/power method - result - 4.10.40_COM_GEN1 - and I am unbricked! Iconiaroot 1.3 worked for getting root after install - slowing getting my tab back to normal now

[Q] I am very stuck - Please Help Me

Hi All,
OK, I am both new and stuck, I have read every page in the unlocking Atrix thread and the one click root thread but I still do not know what is wrong.
I started off by running the one click root listed here, the root went fine and seemed to work, so I proceeded to install ROM Manager but when I tried to back up my phone the process failed.
I googled the error and it turned out that I did not unlock the Boot Loader, so I followed all the instructions that explained how to do it and nothing worked.
Thinking something must have gone wrong I went back to the one click root tool and unrooted my phone, I checked and everything was working and the phone seemed fine.
So then I started down the longer process of unlocking/rooting here , following the steps to the letter and here is where I come unstuck.
I have a UK carrier free phone so after downloading and installing the RSD Lite software I used the SBF_Flash file but when I selected this file the “Start” button remained greyed out.
I researched this issue and found the international flash called intl-fix-try1.sbf, this file looked like it was going to work, the start button became clickable and the process looked ok.
Once I clicked start the flashing started and percentage done went straight up to 98% in a matter of seconds, then as per the instructions the phone reboots but starts to reboot fully, the process % resets and starts from zero going up in increments of 3%, by the time the process is at 65% my phone has fully booted and is sitting at the lock screen, if I leave it there the process will go up to 100% but the status will still say "in progress" until I swipe the lock screen and then it says complete.
I was doubtful that the root had worked but just to make sure I proceeded to move the phone into Fastboot mode and go through the OEM Unlock process but once I have typed in fastbook oem unlock and hit enter the command prompt just comes up with a message waiting for device to respond and nothing more.
Please help as I am really stuck, I followed your guide to rooting my Galaxy tab 10.1 and had it sorted in minutes, my ICS rom installed and everything backed up via ROM Manager so I am not a total dummy.
Any suggestions?
Kind Regards
Chris

when you tried to flash the sbf on rsd lite did you have the phone pluged into the pc and have it put into rsd lite mode
prolly not if you still seen the lock screen
turn phone off then turn on by holding power button down and volume down
when u see fastboot word on the atrix use volume down to scroll to rsd mode then hit volume up and proceed with rsd lite and the sbf

Here might explain it little more..
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader

That is exactly what I did, I have just done it again now . . . .
I clicked start
The console/flash starts,
The phones screen goes black,
Then the Red Motorola M appears
The flash progress jumps to 98%
Console Status says something about USB Pass through/phone rebooting
Then reboots and the Red Motorola M appears again
Then progress carries on and goes up and at 16% by now the phone is now fully in its boot process and by 26% it is at the swipe screen
I have the phone in USB debug mode and the usb connection set to mass storage. Could I be using the wrong SBF file?
Thanks

I have tried that method as well as it is uses a different sbf file called zomgunocklite.sbf when I use that file I an error saying sec_exception: febe, 35, 35 I googled that and it came up with a similar issue but it did not help.

So since my first post I have been speaking to ltdanno360 on here, I just wanted to take the time out to say a MASSIVE THANK YOU.
He has taken me through getting my phone back to a usable state and then all the way through fixing up with the latest bits and pieces.
I have taken up a good few hours of his time and I am now a very, very happy Atrix owner.
It is people like ltdanno360 that make this forum and the internet community such an amazing place. Just imagine driving home from work one day and you car breaks down on the freeway, a stranger stops and spends two hours of his day fixing your car before sending you on your way.
Things like that do not happen often in the real world but people like Danno are great examples of what humanity often misses.
Big Thanks Bro
Awesome guy, awesome forum.

Nexus 4.3 update failed, "no command"

So i got the new 4.3 update notification on my phone today. Eager to get it i started the installation (battery level was about 90%). After a while the installation went into a constant reboot, always went untill halfway of the progress bar and then phone went off and started again to same screen. I knew it was ****ed up so i went into recovery mode but then it starts to do the update again and i got the "ERROR" message. So i went into recovery again and now i get the "NO COMMAND". I was running 4.2.2 with everything stock, device was not even rooted...
Any ideas?

ybuedts said:
So i got the new 4.3 update notification on my phone today. Eager to get it i started the installation (battery level was about 90%). After a while the installation went into a constant reboot, always went untill halfway of the progress bar and then phone went off and started again to same screen. I knew it was ****ed up so i went into recovery mode but then it starts to do the update again and i got the "ERROR" message. So i went into recovery again and now i get the "NO COMMAND". I was running 4.2.2 with everything stock, device was not even rooted...
Any ideas?
Click to expand...
Click to collapse
Unlock your bootloader, and flash the stock 4.3 image manually. Download it from here
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
After that, you can relock your bootloader if you want.

abaaaabbbb63 said:
Unlock your bootloader, and flash the stock 4.3 image manually. Download it from here
After that, you can relock your bootloader if you want.
Click to expand...
Click to collapse
I've got very basic knowledge of android so i don't really know what to do... I imagine if i flash the stock manually i will lose all my data? Because in that case i might aswell go to the store and ask a new one since i still have my warranty...

ybuedts said:
I've got very basic knowledge of android so i don't really know what to do... I imagine if i flash the stock manually i will lose all my data? Because in that case i might aswell go to the store and ask a new one since i still have my warranty...
Click to expand...
Click to collapse
Ok, if you have a store nearby, go to them. They will fix it properly. With basic knowledge, it's pretty dangerous.

Similar Prob
Hey guys,
I have a similar problem. Tried the upgrade to 4.3 and it stucked.... well now i constantly see the Google-X-symbol and thats all. Tried to unlock the bootloader via developer tools (for later flashing to Stock ROM) but there's no connection. Tried to replug it, etc.
When I start the bootlaoder (via Vol-Down and On-Button) I can choose the options (but recovery is not possible) But hm, the bootloader doesn't seem to be broken.
Can anyone help me? I'm not really a developer (although I work for a software-company) but I already unlocked and rooted devices and I have experiences in changing deep settings.
Help would be great!!! I don't want to sent it to google - I am lost without my S-Phone....
Thanks!

I have a similar issue, I found the update notification on my phone, went ahead with the update and it took ages! The battery was nearly full and the battery fully discharged while it was updating. I was at a friends house so no charger. When I got home I fully charged the phone and switched the phone on and got the nexus cross animation and thats all. I tried to enter recovery mode but got the no command icon.
Any help would be appreciated, I do have experience of rooting and flashing custom roms on my HTC Desire but have not touched the nexus since I got it. So everything on the phone is stock
Heres interesting, My wife tagged me into a facebook post telling peeps my phone was out of order, as she did it, the facebook app on my phone notified me of the tag!! Still got the nexus boot animation showing on the screen!

waynehardy said:
I have a similar issue, I found the update notification on my phone, went ahead with the update and it took ages! The battery was nearly full and the battery fully discharged while it was updating. I was at a friends house so no charger. When I got home I fully charged the phone and switched the phone on and got the nexus cross animation and thats all. I tried to enter recovery mode but got the no command icon.
Any help would be appreciated, I do have experience of rooting and flashing custom roms on my HTC Desire but have not touched the nexus since I got it. So everything on the phone is stock
Heres interesting, My wife tagged me into a facebook post telling peeps my phone was out of order, as she did it, the facebook app on my phone notified me of the tag!! Still got the nexus boot animation showing on the screen!
Click to expand...
Click to collapse
Ha, that's exactly the same issue.... Thank God I'm not the only one (sorry )

I got the "no command" error after my update this morning. My battery was pretty low, but the phone was docked. I just left the phone alone while I came here to investigate, and it eventually rebooted itself. Then it stuck on the loading X for around 5 minutes, but now it is optimizing my apps. Looks like it is going to work after all.

Mine has been on for a while but its not seeming to play. what mkes no sense is that it is switched on in the background but the nexus animation is the only thing it shows

I'm having the exact issue. I got my update notification this morning and it failed, going into an endless loop. I called google and they didn't know what was happening, so they're sending me a new phone. I don't want to wait for the new one, so I'm trying to fix this one still. I can start the bootloader, but I can't get into recovery. Is there a way to correct this through ADB?

justin1701 said:
I'm having the exact issue. I got my update notification this morning and it failed, going into an endless loop. I called google and they didn't know what was happening, so they're sending me a new phone. I don't want to wait for the new one, so I'm trying to fix this one still. I can start the bootloader, but I can't get into recovery. Is there a way to correct this through ADB?
Click to expand...
Click to collapse
When you get to the screen with "NoCommand" on it.
1. Press and hold power button
2. Then once you pressing the power button, press the Vol - Up
Thats it
OrangeNik

Here is the fix for everyone
Ok, I just got off a chat with an Asus rep.
Step 1: Hold the power and volume up/down to get the android with the "start" option
Step 2: Use the volume down to select "recovery mode" It will now power off and power back up with the dead android and "no command" below it
Step 3: While holding the power button TAP, but DO NOT hold the volume up button. You will get an option to wipe all data. Do that.
Blammo the world's problems are solved

LG Nexus 4 E960
Work perfectly for me
Nexus Root Toolkit v2.1.4
I can't post a link because I don't have 10 posts!!!

[Q] My phone is dead on stock...(due to rooting/unlocked failure?) Please help!

Hello XDAers,
I am a real noob at rooting or android-related, and a true one voided of any knowledge regarding anything IT- related.
So dear veterans, please go easy on me.
Due to my prior success of rooting and flashing my Nexus 4 successfully a few months back with no issues, I decided to give it a try to flash a custom ROM for my dad's LG Optimus L7 - which seemed an easy task compared to configuring my Nexus 4 - since there was no need for inputting any command lines or any dealing with the abd (using the easy shortcut, that is).
So, I followed the guide here: http://forum.xda-developers.com/showthread.php?t=1906133 ...
I first factory resettled the phone because it was bloated, then applied the "RunMe.bat" from the "What you desire!" folder. (Everything was already backed-up beforehand.) But the process didn't success until I've retried again and again by re-plugging the USB in because the application/PC couldn't detect the phone. In the same time, I was running KDZ_FW_UPD.exe in the background, so unexpectedly for me the phone shut itself and pushed itself to a vividly green emergency screen, then in a few seconds switched back to a screen of purple-white-blue glitches. I had to close KDZ_FW_UPD.exe without knowing what quite happened since it seemed to be the cause and restarted the process with RunMe.bat.
I didn't manage to "Restore" it first due to the fact that the phone stopped responding due to a lag asking for an encryption key. It was lagging so hard and I had to close the cmd around 5 tries while it was processing, but succeeded later on.
And then, to verify whether I've actually suceeded in rooting L7, I installed Root Checker from the Play Store. And again, for the first few tries the program froze on screen for a long period of time due to "system performance", but after rebooting and restarting the app a few times again, the ROOTING proves to be a success. Just to be sure, around this time I've reloaded KDZ_FW_UPD.exe and it suceeded.
So I went to install CWM and ES. CWM for recovery boot and ES for removing pre-installed system apps as the phone was lagging so badly. I've downloaded the CWM restoring(something like ~6.0.28?) first and tried fastbooting immediately right after, but instead of getting the fastboot menu I got a screen emptied in black with these words:
[5020] "Secure booting error"
[5020] "Cause: boot certification verify"
No hard keys could do anything on the presumed "fastboot", and so I had to hard boot again. I thought that it might be due to the lack of memory(checked on ES later on that it was 310~MB/2GB), and so I've used ES to uninstall a lot of system apps which I deemed uneccessary. So I've Googled a bit and it became apparent to me that that I've didn't unlock the device properly, so lurked around and found a file called L7CWM that is supposedly to resolve my problem, but I presume that it's the CWM recovery image that I've installed. So in the end, I didn't bother with it but kept it on tab just in case.
I repeated the same process with CWM again, but this time, the screen was joined with all kinds of flowery glitches. Restarted the device, and it went only downhill: now the Home launcher stayed all pitch black and nothing appeared. I waited a few minutes, but nothing there until the notification bar appeared. The home screen is apparently dead, and so are the menu keys. Switched to Nova Launcher(installed it just in case Home Launcher fails), and still dead. I couldn't access using any of the menu keys and had unusable launchers.
Hopefully I could still access to the settings from my status bar, but when I did, it started crashing immediately.
I've repeated the attempt a few times after restarting the device a few times, but nothing helped. It only got worse that the when the launcher did SEEM to work. It only showed the wallpaper without showing any of the icons/apps. And crashes again.
I could still access to the App menu via the settings, but couldn't open any of them and when I tried to uninstall them, the screen frozes immediately right after I gain access to the page (white page though) and gain this message: "Unfortunately Package Uninstaller Stopped!"
Then I convinced myself that the only thing I could do at the time was to factory reset the phone and then everything would go alright since I've just had to restore the system apps.
But then the black screen of death came right along with it:
"Secure booting error"
It seems that I'm out of luck... ... But just to check if I'm still left with resorts, I've downloaded the L7CWM file online...
... ...but it still didn't help.
So now I'm being left with no other choices other than asking for help. I never really understand what KDZ_FW_UPD.exe does since I had the LG Driver already before installing it, which I presume was for updating the phone to a newer or older version. And too complex tech articles are kind of alien for me.
EDIT(1 hour later): Okay, now I figured out the reason why L7CWM didn't work was because I didn't extract it to the right folder (after double checked via notepad that I was supposed to directly put it into the C:\ drive). Now it worked(?), but then it didn't.
After launching Flash_Bootloader.bat:
This message now appeared on the L7:
"Sorry!"
"SuperSU is not responding.
Would you like to close it?"
"Wait - Report - Close"
and a few minutes later
"Sorry!"
"Unfortunately, SuperSU has stopped."
"Report - OK"
Now I think the bugs till now happened was due to the fact that I've deleted a file that was required for me to launch apps... Now I just need the right fix.
After 5 minutes of screen inactivity the phone restarted by itself, kind of creepy... ...
Flash_Recovery.bat did nothing.
Reboot2Recovery.bat made it reboot but still struck on the same menu.
Nothing seems to be effective via the phone anymore, seems like I have to rely on abd but then again I don't know how... ... My dad is also f*cking pissed off ^ ^;...
__________________________________
I think that I explained the logs pretty precisely in case I missed something... I'll be very very very very very very thankful if someone could tell me what has caused my phone to fail though.
For references, here are the phone's specifications:
Model Number: LG-P705g
Android version: 4.0.3 (Stock)
Rooted:Yes (root checker)
Baseband version: MSM7227A-1-AA
Kernel version: 3.0.8-perf
Build number: IML74K
Software version: V10e-AUG-10-2012
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...

remove the battery for 10 seconds,put it back pres VOL+ and VOL - same time and than press the power button.when you feel a vibration press for many times the button wich is down in right,try for many times and maybe it will working :}

Cydes said:
Hello XDAers,
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
Click to expand...
Click to collapse
simple answer for your
just download your stock rom
go to emergency mode
and flash that stock rom